users@jaxb.java.net

Issues with Binder<Node>

From: Kevin Wooten <kevin_at_wooten.com>
Date: Sun, 23 Sep 2007 23:22:13 -0700

I tried posting this on the forum but got no response, can somebody
please shed some light on my situation?

 From the look of the code (and its actions when using it)
Binder<Node>.marshal does no "binding" at all; it appears to just use
a standard marshaller with no association. Is this true? If it is
true is there a workaround for "injecting" programmatically created
objects into the binder (i.e simulating associated marshalling).

Also, from looking through the code after getting an NPE in
popCoordinator, I have gleaned that binder.unmarshal is not designed
to allow its use in a recursive manner; which I was doing. This seems
mainly due to the cached Unmarshaller the binder is using. What would
be the consequence of changing the getUnmarshaller/Marshaller
functions so that they just create new instances always? Basically
removing the caching of the instances (and obviously cleaning up
properly on exit from the marshal and unmarshal functions). It seems
this would allow a recursive call to marshal/unmarshal; which would
really simplify my (and maybe other developers) usage of JAXB.

Thanks,
Kevin Wooten