Hi Eelco, On Nov 22, 2007 2:44 PM, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > Thanks for explaining. A few questions... > > > Why i do not use proxies: > > 1. Seam injected Ejbs and JNDI resources are already proxies, so i > > don't want a proxy of the proxy of the proxy ...... > > 2. Because proxies are not outjection frendly in this case. > > Pardon me for maybe not getting it, but I don't really understand how > outjection would help Wicket developers. After all, everything works > with regular Java objects, so when I did the first pass of Seam > integration, I didn't really see the use case for 'exporting back' > values to the seam context. Isn't it enough to change the values > (which are passed by reference) if you want to have changes applied? I > somewhat understand the merit of outjection if you pass around request > parameters from request to request and if you don't work with a > construct like Wicket's models, but I'm missing the benefit of > outjection for Wicket applications. > > Would it be possible to give us a short primer on what outjection is > and what it is good for when building Wicket webapps? >
Remember that there are many stateful contexts in Seam, not only the session or request, but also Business process context and conversation context which has no equivalent in other frameworks. Oujection is the possibility to export references from a component to one of the stateful contexts. For example you can export any value from a wicket page to a running business process which is accessed by other web application too. > > 3. Because it is important that you can inject/outject null references. > > Why is that important? If it is memory consumption, those proxies null > their references at the end of a request. > > > Thanks, > > Eelco > The injection/outjection of null references importance is not related with memory consumption: Some times you need to take decisions based on the value of an injected resource and sometimes the null value is a meaningful case in your logic. Specially if you are using injected values coming form other complex components/services. The same applies if you want to tell to other external component that it must set to null some shared variable. Maybe wicket-seam integration is more important to Seam users than to wicket users :( Maybe wicket is very well without seam at all, but i think seam users appreciate good alternatives to JSF. And Wicket is a very good alternative. Regards, Frank. -- Frank D. Martínez M. Asimov Technologies Ltda. Blog: http://www.ibstaff.net/fmartinez/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
