Yeah, my comments weren't the best. I suck at coming up with concise, descriptive
comments. Anyway:
> 1. indefinitely nested deployments are useful and
> used. I don't see any
> reason to restrict the depth. The spec requires jar
> in rar in ear.
This is of course still allowed. Here is an example of what I restricted:
[code]
foo.jar <- deployed
+- temp (directory)
| +- bar.jar (used to be deployed, but no longer)
+- sub.jar (still deployed)
+- junk (directory)
| +- stuff.jar (used to be deployed, but no longer)
+- abc.jar (still deployed)
...
[/code]
I needed to do this to allow, for example, the ejb-jar to remain exploded within the
ear. Then the sub-directory itself is deplyed.
I'm sorry if this explanation is not clear - let me know if you have questions.
> 2. As I recall deploymentInfo had the info on what to
> watch. Is this
> otherwise inaccessible to the deployment scanner?
The deploymentInfo is maintained in the deployers, and exposed via the
getDeploymentInfo method of the MainDeployer. I could have used that, though I would
have had to mark the method as a jmx-operation to do so. (The scanner accesses its
deployer via JMX). Since the scanner was developed with no knowledge of
DeploymentInfo, I thought it would be good to keep that separation, so I added a
method that just returns what the scanner needs - the URL to watch. Of course, I'm
happy to change this if you like.
-Larry
_________________________________________________________
View thread online: http://main.jboss.org/thread.jsp?forum=66&thread=12665
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
