+1
Seems also good to me to have the possibility to give the
ContextResolver also the reqired media type. So you need no extra entity
provider for json and so on.
best regards
Stephan
Marcel Thibault schrieb:
>
> > Makes sense that you might want to have different JAXBContext for >
> the same type and different mime format. (A Jettison enabled/ >
> configured JAXBContext for JSON for example). >
>
>
> Sounds like an interesting idea.
>
>
> +1
>
>
> Marcel...
>
> >>> Marc Hadley <Marc.Hadley_at_Sun.COM> 06/10/08 2:11 PM >>>
> On Jun 10, 2008, at 10:57 AM, Bill Burke wrote:
> >>> One thing we could consider is to make the JAXBContext usage more
> >>> obvious.
> >> I have also to say that I need time to understand what the
> >> ContextResolver is for. You could add some javadoc, that an example
> >> use is for JAXBContext.
> >
> > Question: Is the container supposed to search for and use
> > @ProduceMime/_at_ConsumeMime annotations on a ContextResolver?
> >
> Not currently.
>
> > Makes sense that you might want to have different JAXBContext for
> > the same type and different mime format. (A Jettison enabled/
> > configured JAXBContext for JSON for example).
> >
> Sounds like an interesting idea.
>
> Marc.
>