Rob Walker wrote:
I can answer part 2
- If OSGi is using custom class loaders and JAXB is using different
class loaders, will JAXB ever work in OSGi?
Yes it will and it does - we did it some time ago and it worked fine
(as per my earlier post)
In fact, I seem now to recall that JAX-B only actually has a very
small set of runtime classes - from memory mostly it's a build-time,
generation tool. The Java classes it creates are mostly standalone
with needs largely on things like XML parsers. I seem to remember some
namespace handling and RI classes, and that was about it. So it's
mostly about bundling your generated classes in a correct with all the
necessary imports and exports.
-- Rob
Sorry. I meant to respond to you previous post. So far, I've been
unable to duplicate what you've done by putting the JAXB libs in the
same bundle as my schema generated classes. Although this isn't the
best solution, I wanted to have some small success by duplicating your
solution. What I'd really like to see is a solution that allows JAXB to
be bundled and added to the Felix commons.
I do appreciate your response. It tells me that I'm not fighting a
losing battle. I just need to learn more about how imports, exports,
and class loading work in OSGi.
Tim
