It's possible that there is some overlap. You might be able to register Commands as HiveMind services. But HiveMind has a much broader scope than Commons Chain.

Commons Chain is an implementation of the classic Chain of Command pattern. Period. It has no other scope or aspirations. People can drop it in wherever you might want to implement a Chain of Command. No muss, no fuss.

HiveMind is a configuration framework that you could use throughout an application and within a Command. You might, for example, register the Catalog as a HiveMind service, and the Commands might use HiveMind to find the Catalog(s). But, that would be up to the developer. Commons Chain does not need to decided how the Catalog is discovered. People might also use HiveMind to load the Chain configuration file as an alternative to the Digester.

Struts Chain is whiteboard reimplementation of the Request Processor using Commons Chain. I don't believe that the Request Processor would be easier to implement as a nest of HiveMind services.

-Ted.

Vic Cekvenich wrote:
Struts Chain... seams similar to HiveMind ?
Am I wrong?
.V



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-- Ted Husted, Junit in Action - <http://www.manning.com/massol/>, Struts in Action - <http://husted.com/struts/book.html>, JSP Site Design - <http://www.amazon.com/exec/obidos/ISBN=1861005512>.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to