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

Vamsavardhana Reddy closed GERONIMO-2105.
-----------------------------------------

    Resolution: Fixed

Entries in config.xml are proper now.  I don't think there is any more work to 
be done in the scope of this JIRA.  Reopen if you think there is more to be 
done.

> When redeploying with no version number, new entries in config.xml break
> ------------------------------------------------------------------------
>
>                 Key: GERONIMO-2105
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-2105
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: kernel
>    Affects Versions: 1.1, 1.1.2, 1.2, 2.0
>            Reporter: Aaron Mulder
>            Priority: Blocker
>             Fix For: 1.1.2, 1.x, 2.0
>
>         Attachments: g2105-1.2.war, g2105.war
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.

Reply via email to