I thought 3.0 had this same behavior. In the last training someone had created a server/all/deploy/farm directory and placed an ejb-jar into this directory and it was deployed. I can see both behaviors being useful in different situations, but I'm not aware of what change in 3.2 would cause the behavior to differ if in fact it does.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Adrian Brock" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, February 12, 2003 9:33 PM Subject: [JBoss-dev] JAR Deployer deploys subfolders in deploy > Hi, > > Just a heads up to see whether this change is deliberate? > > In 3.2, if you create a subfolder in server/[config]/deploy with > deployables in it, the JARDeployer deploys them. > > e.g. server/default/deploy/dead/http-invoker.sar > > It doesn't deploy xml files. > > This doesn't happen in 3.0 > > I only noticed it because I sometimes move services > into a "dead" folder within deploy to speed up reboot times > when changing server code. > > Regards, > Adrian > > > _________________________________________________________________ > Overloaded with spam? With MSN 8, you can filter it out > http://join.msn.com/?page=features/junkmail&pgmarket=en-gb&XAPID=32&DI=1059 > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development