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 gbean and provide a gbean
reference from the web service gbean (that I'm telling you to write
2 of, one for jetty and one for tomcat) to that transport gbean.
When the web service gbean starts, it can construct whatever it
needs to from its attributes and references and in particular
insert the transport into whatever other data structures need it.
Hope this makes at least minimal sense :-)
Makes sense. I thought it was something to do with the classloader.
It's not a big problem: I can gather the required information in the
builder and defer the construction of the Celtix transport until the
WebServiceContainer GBean activates.
thanks for the info
Conrad
