portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ate Douma (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Resolved: (JS2-1019) Several import/export mapping bugs in the JetspeedSerializer implementations
Date Wed, 20 May 2009 14:04:45 GMT

     [ https://issues.apache.org/jira/browse/JS2-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ate Douma resolved JS2-1019.
----------------------------

    Resolution: Fixed

I committed a bunch of fixed and improvements to the JetspeedSerializer implementations and
the used OM mapping.
Most importantly: now it actually is possible to import/export custom JetspeedPrincipal extension,
while before only *one* extension was "supported", else it would crash.

Additionally, I've added a major optimization to the xml format of SecurityAttributes and
Preferences.
The old-style format still is supported on import but on export only the new format is (now)
used.

Example of the old-style format for SecurityAttributes (note: Jetspeed-2.1.3 didn't even have
SecurityAttributes yet):

  <SecurityAttributes>
    <SecurityAttribute readonly='false'>
      <name value="org.apache.jetspeed.profiler.refreshUserHomepage"/>
      <value value="true"/>
    </SecurityAttribute>
  </SecurityAttributes>
  <userinfo>
    <preference>
      <name value="user.name.given"/>
      <value value="Dev"/>
    </preference>
    <preference>
      <name value="user.name.family"/>
      <value value="Manager"/>
    </preference>
  </userinfo>

Same data in the new format:

  <SecurityAttributes>
    <SecurityAttribute readonly="false" datatype="STRING" registered="true" required="false"
category="info" name="user.name.family" value="Manager"/>
    <SecurityAttribute readonly="false" datatype="STRING" registered="true" required="false"
category="info" name="user.name.given" value="Dev"/>
    <SecurityAttribute readonly="false" datatype="STRING" registered="true" required="false"
category="jetspeed" name="org.apache.jetspeed.profiler.refreshUserHomepage" value="true"/>
  </SecurityAttributes>

Same kind of format is now used for preferences, and if a preference is multivalued, multiple
child <value/> elements (like before) will be written instead of the value attribute.

> Several import/export mapping bugs in the JetspeedSerializer implementations
> ----------------------------------------------------------------------------
>
>                 Key: JS2-1019
>                 URL: https://issues.apache.org/jira/browse/JS2-1019
>             Project: Jetspeed 2
>          Issue Type: Bug
>          Components: Import/Export
>    Affects Versions: 2.2.0
>            Reporter: Ate Douma
>             Fix For: 2.2.0
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Mime
View raw message