> To have a closure on this can somebody from the JAXB dev group please
> tell me whether the JAXB class-name/method name mappings are somehow
> accessible at the moment, or at least, if there are plans to make them
> accessible in future releases. I feel this would be an a very useful
> thing in cases when you work with schemas for which you generate and
> compile JAXB classes at runtime and you need to populate them with data.
> Obviously read-only access would be sufficient.
Like Aleksei wrote, much information is available at the compile-time
but not in the generated code.
I'm not trying to discourage you or anything, but I still don't
understand --- if you are building a framework and if you can't bind to
a particular schema at the compile time, what's the point of doing that
at the runtime?
Isn't it better to have a type-annotated DOM? In that way, you as the
framework can do any XML operations you want on it. If a particular user
of your framework wants to access it in a strongly-typed fashion, they
can always do that by using JAXB, but why does your framework want to
access its data in such a circuitous way?
Or is there any problem with an approach like this?
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