> 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.
Ok, I think I understand. > 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. Ok. > Maybe wicket-seam integration is more important to Seam users than to > wicket users :( Don't let my questions discourage you though. I just want to understand the choices. My first pass was basically meant to just get something started, without ever having used Seam nor understand it very well :-) > 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. I can imagine that Seam works well for Wicket users in at least a couple of occasions, like when you want to integrate with JBMP and you don't want to use it's API directly. Anyway, thanks for your effort, and I hope more people will pick it up! Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
