Web Beans seems like a waste to me. You can already do all of this (and
better) using Guice and (I assume) Spring. I like the constructor-based
injection Guice enables. Classic JavaBeans forces me to scatter
integrity-checking logic all over the place.
WebBeans and others should just define hooks for Spring and Guice to
implement. Just my 2 cents.
Gili
Bill Burke wrote:
> I don't know if we need something like this. I know there is a high
> probability that the default JAX-RS component model will be Web Beans
> and I'm pretty sure you can biject that information to and from the
> REQUEST scope.
>
> Stephan Koops wrote:
>> Hi Sergey,
>>
>> what kind of use case do you have in mind for the MessageContext
>> interface? Perhaps you could give a code snippet.
>>
>> best regards
>> Stephan
>>> 2. Introduce a message context interface MessageContext with a single
>>> method
>>>
>>> Object get(Object key)
>>>
>>> for users be able to retrieve properties which might've been set as
>>> hints either by the underlying JAX-RS implementation or filters. One
>>> can argue that in this case a user would actually write the
>>> unportable code but one could also say that products which use
>>> multiple JAX-RS implementations under the hood will ensure that the
>>> same code which relies on message properties not otherwise available
>>> in other JAX-RS contexts will be portable
>>>
>>> JAXWS provides similar context implementations.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_jsr311.dev.java.net
>> For additional commands, e-mail: users-help_at_jsr311.dev.java.net
>>
>