Maybe I missed a message about this. But I am wondering, is war deployment broken?
Here is all that gets logged about the war (when inside an EAR, or when placed directly in deploy) Auto deploying: file:/home/david/proxeno/jboss/tmp/deploy/proxeno.war New UCL with url file:/home/david/proxeno/jboss/tmp/deploy/proxeno.war Libraries adding UnifiedClassLoader -1615549336 key URL file:/home/david/proxeno/jboss/tmp/deploy/proxeno.war NO DEPLOYER for url file:/home/david/proxeno/jboss/tmp/deploy/proxeno.war Watching new file: file:/home/david/proxeno/jboss/tmp/deploy/proxeno.war Done deploying proxeno.war To me this looks like the type of archive was unknown, so it will just watch, and attempt to re-deploy if it changes. But has no knowledge of the purpose of the file. With all these changes to the deployment scheme, does anyone have a short description of what is/isnot possible now. ie: Before the change, I was putting *.class in a sar, and making classless(descriptor only) EAR/war/jar. And this worked fine. Is this still possible? -David _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
