-
1. Re: Weld-Spec: A managed bean with a public field has to be dependent???
nickarls Jun 14, 2010 2:30 PM (in response to asiandub)If it would be other than @Dependent scoped, we would be talking proxies. And proxying field access is... apparently nontrivial.
-
2. Re: Weld-Spec: A managed bean with a public field has to be dependent???
asiandub Jun 14, 2010 5:44 PM (in response to 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
-
3. Re: Weld-Spec: A managed bean with a public field has to be dependent???
nickarls Jun 15, 2010 7:39 AM (in response to asiandub)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).
-
4. Re: Weld-Spec: A managed bean with a public field has to be dependent???
asiandub Jun 15, 2010 7:54 AM (in response to asiandub)a proxy for a proxy - i'm just discovering that my company seems to make intensive use of this pattern :-)
-
5. Re: Weld-Spec: A managed bean with a public field has to be dependent???
nickarls Jun 15, 2010 7:56 AM (in response to asiandub)At some point there where plans for a GUF (Grand Unified Proxy) but the complexity didn't have enough ROI to warrant it.