Weld-Spec: A managed bean with a public field has to be dependent???

[asiandub]

found this in the Weld documentation (2.2.1. Managed Beans, towards the end)

If a managed bean has a public field, it must have the default scope @Dependent.

Can anybody clarify on this? I have absolutely no clue why this could make any sense...

cheers,

jan

[nickarls]

If it would be other than @Dependent scoped, we would be talking proxies. And proxying field access is... apparently nontrivial.

[asiandub]

Well, I knew about the proxies, of course, but I thought that proxies are somehow used to obtain the correct instance of the managed bean. What I get from your answer is that Weld / CDI is providing a proxy for the complete access to the managed bean.

Thanks for making this clear.

Jan

[nickarls]

For normal-scoped stuff, we have proxies that when invoked, look up (or create) the instance in the corresponding scope and invokes the desired method. And that instance which is kept in the scope is also a proxy (manufactured from the interceptors/decorators etc that the bean describes).

[asiandub]

a proxy for a proxy - i'm just discovering that my company seems to make intensive use of this pattern :-)

[nickarls]

At some point there where plans for a GUF (Grand Unified Proxy) but the complexity didn't have enough ROI to warrant it.