This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
NB 6.0 200709200000 & GF v2 b58g & jdk 1.6u1: did the test on solaris-sparc Negative test: << 3) Include a bogus entry for a module in application.xml descriptor of an otherwise valid application archive. Deploy. Check error messages for validity, and usefulness >> Was able to deploy an Java EE 5 EAR with good ejb (1 session bean ) web (jsp and html) and a bad java module added in application.xml as: <module> <java> MyJar file toto.jar </java> </module> How to produce: ---------------- 1- start a registered domain (used a personal cluster) 2- create an EAR Java EE 5 with ejb and web modules 3- add a session bean stateless to the ejb 4- add a html file for the web 5- add application.xml to the EAR: Projects/New/Standard Deployment Descriptor 6- edit the application.xml and add the bad java module 7- build and deploy ==>> the EAR is deployed with the bad module, but few messages & exception can be seen in the server.log will attach the application-output (run-deploy), and the server log.
Created attachment 49344 [details] run_deploy output
Created attachment 49345 [details] server.log for the domain
I was able to replicate this issue. I was also able to replicate it using asadmin deploydir. The server allows the user to directory deploy an app like this. The server provides a warning. That warning is integrated into the output that the NB user sees when they do a deploy from inside NetBeans. By being "forgiving", the IDE and server allow folks to make progress despite their errors while providing feedback that there is something wrong. That seems like a good thing to me. Note: asadmin's archive deployment fails in this situation. I don't know if that is good or bad.