> for the second, i'll start playing around with turning on type
> substitution. that sounds like it may be a good way to do what i need.
> the copy constructor idea sounds okay, but i'll see if the existing
> machinery works. the other option (the copy constructor) would be
> suitable as well (my guess is that an implementation would be along the
> lines of a recursive reflective walk? or maybe the xjc actually
> produces code with all of that statically built in?).
I don't have guts to do that, so it's likely going to be a shallow copy...
regards,
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
For additional commands, e-mail: users-help_at_jaxb.dev.java.net