"smies" wrote : So you are saying that I could use the same Action classes to create a non-web application with? I don't really see that. You already add a lot of annotations to the Action class to let it communicate with the view, like the @In, @Out, @DataModel, @DataModelSelection, etc...
Yes, you can create a non-web application with those actions. I haven't seen it yet, but I'm sure that someone will come up with a pure client/server ViewHandler suitable for Swing apps. The real difference would be that rendering happens on the client instead of the server, but the response from the action would work just fine as-is. Notice that the JSF/Seam scopes are not even tied to servlet/web technology. None of those annotations have anything to do with a particular view technology. They are about managing state that any view is free to access. The question is, why would you want to hide this state behind another layer? There were good reasons for it in J2EE 1.4, but with EJB3/Seam those reasons go away. Stan View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3966354#3966354 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3966354 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
