I am guessing from digging into the code. All I have to do is addManager on JAXBContextImpl for JaxME for each new service. I can then control which classloader my JMManager is using. Am I on the right track or way off? If on the write track, I may experiment more with this.....with any luck, I won't even need to change JaxME to do what I need to do.
thanks,
dean

Dean Hiller wrote:

I have a very difficult problem to figure out. Wondering if you can be of help. At the very least, it will make you really think :).

I have a platform which is using osgi as the container. All services are divided in different classloaders by osgi. I want to make a router that marshal's outgoing xml and unmarshal's incoming xml using JaxME......would like to use JAXB but that won't work after studying JAXBContext.java. Every service will have JaxME objects in the api. Every service is in a different classloader from JaxME. JaxME is visible to these objects(osgi can import other class's into the service classloader), but these objects are not visible to JaxME except if somehow I register these objects with JaxME which I would like to do. Ideally, I want this router to have a JaxME context and when services are deployed, they are registered with this instance. When xml comes in, I call unmarshal and get an object of which I look up the type in a hashtable and route it to the correct service.

Is this going to be possible with JaxME. My plan is to try to make it happen by modifying JaxME(while keeping JaxME JAXB compliant of course) and to stay as close to JAXB as possible which I already know some parts will not be compliant. Castor seemed to support this before as you just registered the handlers with Castor and those handlers could come from any classloader.
thanks for any opinions and direction on this,
thanks,
dean



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to