> Rather than a specialized SubDirSubDeployer, how about having the SAR
> report multiple watch-urls?
Yes, that would be an idea.
> It may also be possible to have the SAR start its own
> URLDeploymentScanner for its content rather than explicitly sub-deploy
> it. This would support automatic redeployment of unpacked sar content
> over the web as well; for the packed case, I think it would be easy to
> have a URLLister that scans a jar: URL as well as the current
> file: and
> http: ones.
>
> Yes, you would need a real jboss-service.xml to start the nested
> URLDeploymentScanner, but that would be mostly boilerplate if we made
> the default scanned URL the SAR's root.
OK, so no easy answer ;)
My point was to say: let's not focus on the package types (even if
exploded), but rather, let's say that the URLs passed to the
URLDeploymentScanner should not only scan for packages at the first level,
but also in sub-directory (=> we flatten the view). That would NOT be the
case for the JarDeployer, SarDeployer, etc. (as we don't want to scan all
directories of a JAR!!!), but only for the directories (not ending in a
.xar) at the root of the URLs passed to URLDeploymentScanner to be scanned
as well.
Cheers,
Sacha
-------------------------------------------------------
This SF.net email is sponsored by: Tablet PC.
Does your code think in ink? You could win a Tablet PC.
Get a free Tablet PC hat just for playing. What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
