Uploaded image for project: 'GPII - Global Public Inclusive Infrastructure'
  1. GPII - Global Public Inclusive Infrastructure
  2. GPII-32

XML settings handler unable to statements with the similar name only distinct by their parameters

    Details

      Description

      XML settings handler unable to statements with the similar name only distinct by their parameters – so eg:

      <outer>
      ..<inner id=1></inner>
      ..<inner id=2></inner>
      <outer>

      Here the settings handler would not be able to refer to the inner statement with id=1.

      Taking a real life example encountered by SILO with their Microsoft Surface implementation: taking a snippet of the settings that we want to change:

      <Sociable.Launcher.Properties.Settings>
      <setting name="GameResources" serializeAs="String">
      <value>C:\Sociable\Games\Resources</value>
      </setting>
      <setting name="Resources" serializeAs="String">
      <value>C:\Sociable\Games\Resources\Launcher</value>
      </setting>
      <setting name="AutoLogin" serializeAs="String">
      <value>0</value>
      </setting>
      (...)
      </Sociable.Launcher.Properties.Settings>

      This cannot be handled by the current XML implementation, because we have a set of <setting ...> blocks, that are indistinguishable unless you look at it's parameter 'name'. There is currently no way to express this in the EL notation used by the XML settings handler. What we would need is some way to tell which <setting .. > block we refer to.. For example:

      Sociable\\.Launcher\\.Properties
      .Settings.setting[name=Resources].value.$t

      Which would refer to C:\Sociable\Games\Resources\Launcher in the above code snippet

      This is a blocking issue for SILO to properly implement the Microsoft Surface and as well for setting all the settings for Read Write Gold.

        Attachments

          Activity

            People

            • Assignee:
              kasper Kasper Markus
              Reporter:
              kasper Kasper Markus
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: