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.
Steps to reproduce: - Take any Enterprise Application - Edit application.xml to malformed state. I just removed one of quotation marks as following: <application version="1.4" xmlns="http://java.sun.com/xml/ns/j2ee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"> - Try to run application - RESULT: The following is shown in the build.xml log: Applicaton Deployed run-display-browser: Browsing: ${client.url} C:\Documents and Settings\ak153254\J2EEAppRun2\nbproject\build-impl.xml:225: java.net.MalformedURLException: no protocol: ${client.url} BUILD FAILED (total time: 1 minute 19 seconds)
I am not sure whether we are able to report something better because after copying the archive the server is loding the archive and we would have to parse its log to discover the problem. I will look at where we are setting the client.url property and why it is not set. Maybe there is right place to report the problem. However the message about malformed URL will stay there, it is at least a sign that something has gone wrong.
I explored the behaviour. j2eeserver module is responsible for catching all exceptions thrown from the involved modules during the deployment. If some exception is thrown then j2eeserver reports the exception writing it into the message log. The problem with the example above (removed quotation mark) is that deployment itself went well but JBoss could not load the module because of the error in the deployment descriptor. It threw the exception which was written into the server log. We are not able to discover this kind of error, the only symptom of things going wrong is the unset value of the client.url property. It is reported into the Output console by the run-display-browser Ant task. It is a user's responsibility to look at the message log or the server output and discover the original problem. All information is in these three sources.