geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <...@geronimo.apache.org>
Subject [jira] Commented: (GERONIMO-1462) Finish implementing inverseClassloading attribute in plan schemas
Date Thu, 12 Jan 2006 21:27:20 GMT
    [ http://issues.apache.org/jira/browse/GERONIMO-1462?page=comments#action_12362569 ] 

David Jencks commented on GERONIMO-1462:
----------------------------------------

I'm not sure what to think about minor changes to schemas that are backward compatible (because
the changes only allow more optional stuff).

The convenience argument is kind of weak as long as we use xmlbeans, since we can have it
translate namespaces on loading.  we are already using this so you can still use the version-free
namespaces.

> Finish implementing inverseClassloading attribute in plan schemas
> -----------------------------------------------------------------
>
>          Key: GERONIMO-1462
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1462
>      Project: Geronimo
>         Type: Bug
>     Versions: 1.0
>     Reporter: Aaron Mulder
>      Fix For: 1.0.1, 1.1

>
> The inverseClassloading attribute is declared in geronimo-config-1.0.xsd.
> It appears to be used in:
>  - geronimo-application-1.0
>  - geronimo-connector-1.0
>  - geronimo-jetty-1.0
>  - openejb-jar-2.0
> It should be added to:
>  - geronimo-web-1.0
>  - geronimo-tomcat-1.0
>  - geronimo-application-client-1.0 (not totally sure about this one)
> However, we need to decide whether to rev the version numbers of those schemas when we
make the change.  I would be inclined to not change the namespace or version in the file name,
but to add an internal version history in the header comment of the schemas.  Mainly because
that's how Sun does it with the J2EE schemas, and I think it would be a huge pain to try to
get people to update their namespaces every time we have a tiny change.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message