You can use the register(user) approach if you like. Seam 1.1 lets you write
"#{register.register(user)}" as a method binding expression. (Plain JSF does
not.) It all depends upon whether you view the user as "contextual state" or
just a transient argument to a method. In this case its just a matter of taste.
If you have a need to expose the functionality as a web service, then by all
means layer your application to separate "business logic" from "interaction
logic". But most applications do not start out with this requirement, it is
something that comes later. People think just because maybe they will need the
layering at some unspecified future date, that they had better introduce it
*now*. But of course, this is a classic case of YAGNI. The easiest thing on
earth (assuming modern refactoring tools) is to introduce extra layering into
an existing application. The idea that this was difficult originated prior to
the existence of "extract method".
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980326#3980326
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980326
_______________________________________________
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
