|Yep, that's exactly whay I was trying to get at. I feel that I'm lacking
|in vision on the general "J2EE deployment" side of things, but I'm happy
|to code something like this up if it's agreed that it's right direction.
keep it simple.
otherwise you end up with acyclic graphs with bidirectional (bipolar)
dependencies on dog doodoo.
Define the MLet MBean (based on the new schema) and pass the "war, jar, jcx,
xxx" argument as the extension seen by the deployer for a particular
service.
When such a service comes up he registers with the ApplicationManager,
please hook up with Cristoph on the exact logic for when particular jars are
redeployed within one application. I do believe his "large app with many
dependent jars" problem needs a flexible "only redeploy this but not the
whole application" solution. You have the knowledge of what CL is
associated with what, that rests with the Application Management or even
deeper (CL service anyone?).
Essentialy you then call the different targets with the right jar, war,
jcx...
go home you are done
marc
|
|Toby.
|
|> he he
|>
|> marc
|>
|> |
|> |/Rickard
|> |
|> |--
|> |Rickard �berg
|> |
|> |Email: [EMAIL PROTECTED]
|> |
|> |
|
|--
|Toby Allsopp
|Research
|Peace Software International Ltd
|Ph +64-9-3730400
|
|
