|OK, you saw my last email ( in the "JSR/SAR (Jetty)
|Undeployment..." thread)
|right?
yes i did,
|> In fact I need the following
|> 1- how would you package it? where?
|> 2- how would you specify it? needed?
|> 3- what happens on redeploy.
|
|1- keep it simple. in a sar you can have a directory called "root" in the
|META-INF dir, everything that is in this directory is copied exactly to
|${jboss.system.deployed}\sarname\root
ok, how do you specify that the directory should be removed upon
deploy/undeploy?
|I think we then add a method to ServiceMBeanSupport that looks up this
|directory, this way it can be set by the ServiceDeployer if the mbean being
|deployed extends ServiceMBeanSupport (or implements the ServiceMBean
|interface) and is easy for clients to find.
And sets the variables that are specific to the classes he is MBean'ifying
yes... good idea.
|All the jars in the sar are also copied to ${jboss.system.deployed}\sarname
|to avoid the file sharing violations that prevent the user from simply
|moving the original file to undeploy. This is under the
|assumption that all
|required classes are now in jars, I guess we can copy plain class
|files too,
|but jars would be neater I reckon.
We agree on the problem and the solution. I am not sure it should be put in
the "work" areas as it is a hack to solve a bug that might be gone, also it
will be a source of confusion... "do I need to overwrite the jar in the
directory?"... David did you make any progress on this?
|2- not sure what you mean? the above paragraph maybe.
I am talking about the metadata on the directory... most notably "undeploy"
that's it the other features I don't think we need (although "security"
comes to mind).
|3- I think (again going for simple) that when the sar is redeployed nothing
|from the directory structure is overwritten, but the jars are.
|This way any
|persistent data in the directory structure is kept and any configuration
|files the user wants to update manually can be updated in the expanded
|directory structure and when the sar is redeployed the new configuration
|will take effect. If the user wants the files from the sar to be copied
|over all they have to do is delete the ones in the deployed
|directory before
|they redeploy their app.
sure that sounds simple enough it also does away with the metadata
requirement of removing or not
What about
META-INF/root/temporary
META-INF/root/permanent
and you can have directories undeploy in "temporary" and stay there in
"permanent"
|I think this will pretty much allow us to do we want to do.
yes I am ok with the one directory approach. All permanent data will need
to be copied over.
|This is something I am begining to learn the hard way. *wry grin*
|so its not really looking good. I do have time today to look at
|some simple
|stuff. In fact I think I can come up with a simple dependency
|mechanism for
|the AutoDeployer which will clean up a lot of those issues by handling it
|all in one place. That will just leave the service deployer changes to do.
|
|If people don't mind leaving it a couple of weeks I might be able to get
|back to it.
|
|That's the best I can do at the moment, my priorities have to be keeping on
|top of any reported bugs in JBossMQ and our developments at work.
you do what you have to do, I am going back to JMX stuff myself. If djencks
has some time we might put this in sooner
marcf
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
