Ryan LeCompte wrote:
> Sorry for bombarding the group with so many messages in one day, but
> one last question. J Does the Provider API in JAX-WS 2.0 also support
> using JAXB for the data bindings, or is that only available with Dispatch?
>
Provider doesn't have direct support of JAXB. But once the endpoint is
invoked, you can always use JAXB to process the Source.
Jitu
> Thanks,
>
> Ryan
>
> ------------------------------------------------------------------------
>
> *From:* Ryan LeCompte
> *Sent:* Friday, December 02, 2005 9:09 AM
> *To:* Ryan LeCompte; JAX-WS (users_at_jax-ws.dev.java.net)
> *Subject:* RE: JAX-WS and JAXB
>
> 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.
>
> 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
>