This week's book giveaway is in the OCPJP forum. We're giving away four copies of OCA/OCP Java SE 7 Programmer I & II Study Guide and have Kathy Sierra & Bert Bates on-line! See this thread for details.
I'm currently working on a telecoms implementation for a proof of concept project. This involves writing a simulation for an EMS system to manage a network element, for example a network switch or router.
The command pattern looks like something I could use for thread management and queueing etc
Question is that I have dozens of diverse objects that model equipment, traffic, housekeeping and so on, each object can have a dozen or so methods.
Would I implement a single "command set" or would I have several instances of the pattern deployed according to the methods that the command executes.
This might not answer your question - did you consider jmx to manage your resources? [ June 08, 2005: Message edited by: Sathvathsan Sampath ]
- Sathvathsan Sampath
Joined: May 31, 2005
Perhaps I should explain a little of the nature of my task. I'm actually involved in setting Telecoms standards, eg MTNM, MTOSI so I am attempting to show how they may be implemented. (This need not necessarily be in Java). There is also relation to OSS/J in that I could implement OSS/J interfaces
I'm not a developer but tend to work mainly in OSS design but a common anti-pattern is that designers tend to suffer from legacy or j2ee fever and the developers often question the low level implementation detail of a design. If I actually resort to coding myself then I have a better knowledge of the low level implementation detail for an industrial design
I actually have the objects/methods defined by the standard, its more to do with what is the most efficient way of implementing these (the standard is not prescriptive on the application internals, only the J2EE/CORBA interfaces)
So for example what I am looking for in the command pattern is a way of executing methods from object EMS() interacting with other objects such as ManagedElement(), Equipment(), SubnetworkConnection, TerminationPoint(), Log(), GUI() etc.
Of course I could just leave my commands un-encapsulated
Thanks for the heads-up on JMX, its always nice to know of potentially useful tools