[weld-dev] Question regarding behavior of Decorated dependent scoped beans
Pete Muir
pmuir at redhat.com
Fri Feb 5 13:39:07 EST 2010
Sorry, we lost this email.
On 18 Jan 2010, at 23:07, Joseph Bergmark wrote:
> While verifying the behavior of decorated dependent scoped beans on OpenWebBeans, Gurkan mentioned that he observed the same behavior on WELD. While verifying myself I noticed two behaviors that seem to conflict with the spec.
>
> 1) Non-normal scoped beans don't have any restrictions on public fields. A quick test showed that changes made to public fields directly are not reflected when a call to a getter method that returns that value of the public field is made. Presumably this is because there is an proxy like object in the middle.
>
> For example
>
> @Inject MyBean myBean;
>
> myBean.number = 7;
> myBean.getNumber(); //would return the default value for number and not 7 which it was just set to.
Correct, I don't think the spec covers this.
>
> 2) Non-normal scoped beans don't require a public no-args constructor. If the dependent scoped bean instead had a constructor annotated with @Inject (as per 3.1.1), an InstantiationException was thrown.
>
> Are these expected restrictions once that dependent scoped bean is Decorated?
No, this seems like a bug.
More information about the weld-dev
mailing list