Bill Burke wrote:
>> Jersey provides a JSON specific JAXBContext implementation that
>> inherits from JAXBContext. So far there has been no need to utilize
>> produce/consume for such support.
>>
>> An alternative may be to include the media type as an argument to the
>> get method i.e. is the direction, consuming or producing important?
>>
>> It may also be useful to consider using context resolver for obtaining
>> the JAXB unmarshaller/marshaller for a type as well since properties
>> can be set of these. This straightforward to support.
>>
>
> I still think ContextResolver is an implementation detail and ad-hoc
> dependency injection. We would be doing this very very differently if
> we were building on top of an existing DI mechanism. We would not be
> adding a new component type.
>
Say for instance we had an existing DI mechanism. How would you go about
specifying a portable solution for obtaining of an application specific
JAXBContext for a JAXB type?
Paul.
--
| ? + ? = To question
----------------\
Paul Sandoz
x38109
+33-4-76188109