[EMAIL PROTECTED] wrote: > Hi, > > We have done something very similar using Struts where the web sends > an Action (a Command and a Data) to the EJB Tier. Here we have a > Command Pattern EJB that analyse this action, do some fine grained > security check and then call a set of session beans. These one > talk to entity beans using local interfaces. The command is mapped > to a class using xml, this class implements the call to the > specific session beans (and other things).
The WebWork approach is to actually instantiate the command on the client, and call set-methods for parameters that the command is going to need. There is then no logic needed on the server besides get/execute/return. If the command needs security, then it will implement it itself (using patterns that allow the checks to be reused of course). > What surprise me (well until today ;-) ) is that there is a bunch of > patterns that tells "calls your entity beans via a session bean", > "use business interface to abstract your client from ejb", but > there is none saying "abstract your session bean call through a > command pattern" which seems to me as critical to reduce the number > of calls between web tier and ejb tier. This commander can then > be used from web services client without a change to the session > bean (may be I am going too far but the idea is not far) Well, I've been saying this for some time now, and this pattern is indeed discussed on TheServerSide, right here: http://www.theserverside.com/home/thread.jsp?thread_id=9257 /Rickard -- Rickard �berg _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
