geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Cabrera (JIRA)" <>
Subject [jira] Updated: (GERONIMO-2105) When redeploying with no version number, new entries in config.xml break
Date Sun, 16 Jul 2006 07:06:40 GMT
     [ ]

Alan Cabrera updated GERONIMO-2105:

    Fix Version/s: 1.1.x
                       (was: 1.1.1)

Moving unassigned issues over to the 1.1.x pool where they can be worked on for the, in all
probability, 1.1.2 patch.

> When redeploying with no version number, new entries in config.xml break
> ------------------------------------------------------------------------
>                 Key: GERONIMO-2105
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: kernel
>    Affects Versions: 1.1
>            Reporter: Aaron Mulder
>            Priority: Blocker
>             Fix For: 1.1.x
> Let's say you deploy foo with no version number and config.xml content.  Then through
the console or some other mechanism, you set a property on a previously unlisted GBean.  Now
you get something like this:
>   <module name="default/foo/1149955208117/war">
>     <gbean name="default/foo/1149955208117/war?J2EEApplication=null,WebModule=default/foo/1149955208117/war,j2eeType=GBean,name=MyGBean">
>       <attribute name="bar">value</attribute>
> Now you redeploy foo, and it migrates the config.xml entry to the new version number.
 However, what you actually get is this:
>   <module name="default/foo/1149955408117/war">
>     <gbean name="default/foo/1149955223470/war?J2EEApplication=null,WebModule=default/foo/1149955223470/war,j2eeType=GBean,name=MyGBean">
>       <attribute name="bar">value</attribute>
> Note the different version numbers between module and gbean elements.  In other words,
the version in the main config.xml entry is updated, but the version in the GBean entries
is not.  This means that the module will fail to start, as it will treat the GBean as a brand
new GBean declaration and crap out when it has no GBeanInfo defined.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message