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? > 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
