Ryan LeCompte wrote:
> By the way, why does the build.xml for samples/provider actually
> generate code when you run the “server” target? It looks like the
> actual AddNumbersImpl class doesn’t use any of the auto-generated
> objects, but rather parses the payload XML manually.
>
Yes it doesn't use. It was there because other samples use similar ant
targets.
But it could use those objects to process the XML. It is better to use
xjc target (instead wsimport) to generate portable JAXB artifacts and
use them to process XML.
Jitu
> Thanks,
>
> Ryan
>
> ------------------------------------------------------------------------
>
> *From:* Ryan LeCompte
> *Sent:* Friday, December 02, 2005 9:02 AM
> *To:* JAX-WS (users_at_jax-ws.dev.java.net)
> *Subject:* JAX-WS and JAXB
>
> Hello all,
>
> When using the dispatch/provider features of JAX WS 2.0, is it
> possible to utilize these interfaces with JAXB in a more “dynamic”
> mode? To be more specific, JAXB currently seems to only generate Java
> objects based on the WSDL/XML in a static fashion (at build time). Is
> there a more dynamic approach to unmarshalling payload messages via
> the Provider (with JAXB support) interfaces that don’t require me to
> manually walk the whole DOM model in memory? (As the provider sample
> code demonstrates in the JAX-WS nightly distribution). If I have to
> walk the whole DOM model in memory, what is the easiest/most developer
> friendly way to deal with the message payload?
>
> Thanks,
>
> Ryan
>