Hi David,
On 27 Mar 2006, at 22:28, David Jencks wrote:
I think what you will need to do is to write new gbeans for
celtix. That will let you store the necessary information in the
gbeans in an optimal-for-celtix way. In particular I suspect that
you may want to wrap the transport in a
On 27 Mar 2006, at 22:55, David Blevins wrote:
On Mar 27, 2006, at 1:34 PM, Dain Sundstrom wrote:
I thought this ugly hack was necessary to get around the web class
loader being a different class loader than the configuration class
loader. IIRC the trick was to leave the object as a
Howdy,
In the AxisBuilder, when the configurePOJO method constructs an
AxisWebServiceContainer it is set as an attribute in a GBeanData
object but is also wrapped in a StoredObject:
targetGBean.setAttribute(webServiceContainer, new StoredObject
(axisWebServiceContainer));
// Hack!
It's
On Mar 27, 2006, at 12:58 PM, Conrad O'Dea wrote:
Howdy,
In the AxisBuilder, when the configurePOJO method constructs an
AxisWebServiceContainer it is set as an attribute in a GBeanData
object but is also wrapped in a StoredObject:
targetGBean.setAttribute(webServiceContainer, new
I thought this ugly hack was necessary to get around the web class
loader being a different class loader than the configuration class
loader. IIRC the trick was to leave the object as a byte array
until the actual web class loader was passed in via the TCCL and then
deserialized.
-dain
On Mar 27, 2006, at 1:34 PM, Dain Sundstrom wrote:
I thought this ugly hack was necessary to get around the web class
loader being a different class loader than the configuration class
loader. IIRC the trick was to leave the object as a byte array
until the actual web class loader was
