Re: classloader problems

[Dean Hiller]

unfortunately, every package is in a different classloader so I would need an array of classloaders as well as packages.  Also, this is a very dynamic platform and the packages are not known ahead of time.  You can deploy a service after the platform is running just like J2EE.  I am going to take a shot at adding a method to JAXBContextImpl in Jaxme and see how it turns out.  I just want to be able to dynamically register and unregister new jaxb.property files.  This platform also handles unloading of a service.  You can even update the code without restarting the JVM.  Unfortunately, JAXB can't handle all this dynamic coming and going, but JaxME looks like it was a nice enough design that I can just add a little and be off and running. dean Jochen Wiedmann wrote: On 9/12/05, Dean Hiller <[EMAIL PROTECTED]> wrote: For unmarshalling, I get xml, and have no idea which handler to use to unmarshal the xml without parsing the xml first. I would hate to parse the xml twice. It looks like the JMUnmarshallerHandler can do that for me though as it looks up the manager it needs after parsing the first element. Am I even explaining this right? I'd assume that you get the same affect by concatenating all the package names into a single string and pass that to JAXBContext.newInstance(). That should give you a context (and thus an Unmarshaller) who knows about all of your classes. Jochen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]