--------Original Message-----
From: Greg Nudelman [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 30, 2003 5:35 PM
To: jdjlist
Subject: [jdjlist] Servlets Design Question: Command Design Pattern?Are you guys talking about a "Command" design pattern? i.e. you make a specific instance of the "CommandXXX" class (from a Factory, passing in a parameter) and then you call commandXXX.execute(). CommandXXX class ether extends (or implements) Command that has an abstract execute() that all the XXX subclasses need to implement.
Is that it?
How is that better then the big case statement in the ControllerServlet and RemoteCallManager.callRemoteXXX()? I don't really have any re-try strategy implemented in my callRemoteXXX(), they are all pretty simple, set and fire kind of affairs... [READ: LEGACY STUFF] :-)
If you use the command design pattern, you would still have the big case statement (or hashmap retrieval), but it would be instead in the CommandFactory class...
I guess that might be a little cleaner, but it just seems less understandable, at least in the Servlet context.
I'll take a look, though... Thanks guys!
Greg
---
You are currently subscribed to jdjlist as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
http://www.sys-con.com/fusetalk
You are currently subscribed to jdjlist as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
http://www.sys-con.com/fusetalk
