http://nagoya.apache.org/wiki/apachewiki.cgi?HiveMind/HiveMindAndAvalon
Overly simplistic question, perhaps, but based upon what you said, it would almost sound like Hivemind could live under an Avalon container. I don't know what, if any, benefits would acrue from such an approach.
Sure thing. In, above, under, next, around, through. You can probably spend a week coding and be able to run spring in hivemind in jetty in merlin in merlin in geronimo in eclipse.
Consider:
+--Geronimo-----------------------------------------------------------+ |+--Loom-------------------------------------------------------------+| ||+-----+ || |||James| || ||+-----+ +-------------------------------------------------------+|| || |Jetty +--Tapestry-+----------+ +--Tapestry----------+||| || | | | HiveMind | | | Spring |||| || | | | | | | |||| || | +-----------+----------+ +--------------------+||| || +-------------------------------------------------------+|| ||-------------------------------------------------------------------|| || PicoContainer | HiveMind || |+-------------------------------------------------------------------+| | | |+--Merlin-----------------------------------------------------------+| ||+--OpenORB-----------++--EOB-----------------++--Persistor--------+|| ||| ||+--BusinessObj+ ||+-----------------+||| |||+------------------+||| | ||| Hybernate |||| |||| |||| | ||+-----------------+||| |||| JNDI Registry ||||-------------| ||+-----------------+||| |||| |||| HiveMind | ||| HypersonicSQL |||| |||+------------------+||+-------------+ ||+-----------------+||| ||| || ||+-----------------+||| ||| ||----------------------||| Prevayler |||| ||| || PicoContainer ||+-----------------+||| ||+--------------------++----------------------++-------------------+|| |+-------------------------------------------------------------------+| |---------------------------------------------------------------------| | PicoContainer | HiveMind | JMX | +---------------------------------------------------------------------+
its possible and probably feasible. Add some smart mixins using some AOP framework that export all the contents of any particular framework over JMX, add a asynchronous mapping from JMX into JNDI, use some smart aggregrate containers to obtain subsets of some of all hosted components to do dynamic relayering.
It is all possible. The problem is that with every layer or box, conceptual, code- or projectwise, everything starts becoming less clear. Until you end up with what feels like:
+---------------------------------------------------------------------+ | <<some container / framework / glue>> | |---------------------------------------------------------------------| | _.--------------. | | ,---'' `----. | | ,,-' `-.. | | ,,-' `-.. | | ,;' `:. | | ,;' `:. | | ,' `. | | ,/ \. | | ;; GIANT COMPONENT CLOUD GOES HERE :: | | ;;,-------. :: | | ;,'Imported `. :: | | (| over SOAP ) || | | ::. ,' FRAMEWORK THERE ;; | | ::`-------' ;; | | :: CONTAINER HERE,---------. ;; | | `\ ,-' `-. /' | | `. / \ ,' | | `:. / BYTECODE- \ ,;' | | `:. ( MODIFIED ) ,;' | | ``-. \ / ,-'' | | ``-. \ / ,-'' | | `-`-.. ,-' _.---' | | `---------'-----'' | | | | | | | +---------------------------------------------------------------------+
IMO It makes more sense to focus on component reuse and container interoperability than on container reuse. The former is a common goal while the latter brings us many barriers to conquer and battles to fight.
Lets focus on sharing ideas and specifications first. Any sharing of code can come later.
cheers and goodnight!
- Leo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
