Hmm ok. When I inspected the classloader when loading the class for the attribute type, I remember seeing that the parent classloader contained XMLObject. Do you know why the other gbean's loaded successfully? Would setting the context classloader help the situation?On Nov 3, 2006, at 4:18 AM, D
I think either removing geronimo-deployment from the manifest cp or adding xmlbeans jar will solve this problem. I don't think the former will work and I really don't like the latter. Maybe we can split up geronimo-deployment jar into a remote piece and a local piece? This may take some more in
So after being able to bootstrap the j2ee-system configuration, we are running into a NoClassDef exception on XMLObject when attempting to start the gbean-deployer configuration. Comparing the gbean-deployer config to 1.1.1, it looks like a GBeanBuilder bean was introduced in the plan, and this ha
I came up with a proposed solution and put it in GERONIMO-2539. I think I'm about to need this facility also :-)Take a look, see if it can be improved, see if it works :-)jdillon, does this look OK to you?thanksdavid jencksOn Nov 1, 2006, at 11:15 AM, Sachin Patel wrote:I'm trying to get the offli
I'm trying to get the offline deployer back working in trunk, the problem is when starting the kernel with the using j2ee-system as the bootstrap configuration, when locating "META-INF"/config.ser" resources only deployer.jar is located having this resource and thus the j2ee-system config cannot be
