Re: JSR311: Re: ContextResolver removal

From: Paul Sandoz <Paul.Sandoz_at_Sun.COM>
Date: Tue, 10 Jun 2008 09:36:44 +0200

On Jun 9, 2008, at 11:37 PM, Bill Burke wrote:

> Marc Hadley wrote:
>> Again, I believe Web Beans, Spring, or Guice is a better solution to
>>> fill in these gaps here.
>> The main use-case for this interface is JAXBContext customization
>> and this is driven by the inclusion of a standard JAXB entity
>> provider. If we drop ContextResolver<T> then I think we still need
>> some standard way for an application to provide a customized
>> JAXBContext and for an entity provider to access it. Agreed ?
> I think configuration and lifecycle of both providers and resources
> is the root of the issue. Its frustrating that such a fundamental
> service (DI) is undefined in EE 5


> and earlier and is meeting resistence in EE 6 (Web beans).

Any more details on the nature of the resistance and by whom?


> Ya I agree though, whether or not you keep ContextResolver,
> mandating JAXBContext pluggability is probably a good idea.