You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <de...@geronimo.apache.org> on 2004/11/10 02:40:25 UTC

[jira] Resolved: (GERONIMO-464) Split out common geronimo-security.xsd processing code

     [ http://nagoya.apache.org/jira/browse/GERONIMO-464?page=history ]
     
David Jencks resolved GERONIMO-464:
-----------------------------------

     Resolution: Fixed
    Fix Version: 1.0-M3
                     (was: 1.0-M2)

Security schema moved to security-builder module.  Schema modified to insist on its own namespace, and users of the schema modified to expect that namespace.  SchemaConversionUtils extended to convert "security" element to security namespace.  One set of code written to copy info into pojo model, used from openejb and jetty module deployers.

> Split out common geronimo-security.xsd processing code
> ------------------------------------------------------
>
>          Key: GERONIMO-464
>          URL: http://nagoya.apache.org/jira/browse/GERONIMO-464
>      Project: Apache Geronimo
>         Type: Improvement
>   Components: deployment, security
>     Reporter: Aaron Mulder
>     Assignee: David Jencks
>     Priority: Minor
>      Fix For: 1.0-M3

>
> It would be nice to have one set of code to process geronimo-security.xsd, like we have for geronimo-naming.xsd.  That would go in a security-builder module, I assume, based on our current architecture strategy.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira