I'm thinking about what to do about it.
Is there really a mismatch between the domain and server on the 2 names? (joe/geronimo)
In this particular case I think it would be a good idea to put the deployment gbeans in a separate gbean-only plan, similar to the geronimo runtime-deployer-plan. However, even if this solves the immediate problem there is still a bug.
Thanks for finding this.
david jencks
On Mar 10, 2005, at 9:25 PM, Dondi Imperial wrote:
Not sure if this is a bug but I thought I'd post it here.
<?xml version="1.0" encoding="UTF-8"?>
<application
xmlns="http://geronimo.apache.org/xml/ns/j2ee/application";
configId="app"
parentId="org/apache/geronimo/System"
application-name="null">
...=
<gbean name="ConnectorBuilder" class="org.apache.geronimo.connector.deployment.ConnectorModuleBuilder" >
...
</gbean>
<gbean name="somename" class="some_class">
<reference name="ConnectorModuleBuilder"><name>ConnectorBuilder</name></ reference>
</gbean>
</application>
The gbean "somename" will not start because it will look for the gbean named
geronimo.server: J2EEApplication=null,J2EEServer=geronimo,j2eeType=ModuleBuilder,name=Co nnectorBuilder,null=null (note the null=null attribute/value pair at the end)
but the running gbean is named joe.server: name=ConnectorBuilder,J2EEServer=joe,J2EEApplication=null,j2eeType=Modu leBuilder (no null=null).
Intended behaviour or bug?
TIA,
-- Dondi Imperial Software Engineer Exist Software Labs 1907, The Orient Square Emerald Avenue, Ortigas Center Pasig City 1605 Philippines +632.687.7653 www.exist.com
