Dan Diephouse wrote:
> Any ideas on how to get around this without specifying all the
> individual subclasses/packages?
Unfortunately, no. The best we can do today is to defer the decision
until you invoke JAXBContext.newInstance(); that means you need to
define a way to enumerate all the interesting packages and classes.
It's nice if there's a resolver like mechanism to allow JAXBContext to
add more classes as it does unmarshalling/marshalling, but that's not
implemented today (besides it has some tricky semantic implication.)
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com