geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Hogstrom (JIRA)" <>
Subject [jira] Updated: (GERONIMO-2105) When redeploying with no version number, new entries in config.xml break
Date Tue, 13 Jun 2006 02:04:30 GMT
     [ ]

Matt Hogstrom updated GERONIMO-2105:

    Fix Version: 1.1.1
                     (was: 1.1)

> When redeploying with no version number, new entries in config.xml break
> ------------------------------------------------------------------------
>          Key: GERONIMO-2105
>          URL:
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>   Components: kernel
>     Versions: 1.1
>     Reporter: Aaron Mulder
>     Priority: Blocker
>      Fix For: 1.1.1

> 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