PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2920 *** shadow/2920 Tue Jul 31 08:09:07 2001 --- shadow/2920.tmp.11991 Tue Jul 31 08:09:07 2001 *************** *** 0 **** --- 1,39 ---- + +============================================================================+ + | XSP pages having thrown runtime exceptions during the execution of constru | + +----------------------------------------------------------------------------+ + | Bug #: 2920 Product: Cocoon 2 | + | Status: NEW Version: 2.0b1 | + | Resolution: Platform: All | + | Severity: Normal OS/Version: All | + | Priority: Other Component: general components | + +----------------------------------------------------------------------------+ + | Assigned To: [EMAIL PROTECTED] | + | Reported By: [EMAIL PROTECTED] | + | CC list: Cc: | + +----------------------------------------------------------------------------+ + | URL: | + +============================================================================+ + | DESCRIPTION | + First, modify an XSP sample included in the distribution to throw a runtime + exception during the execution of the constructor. Let's pick simple.xsp in the + docs/samples/xsp/. + + Add the following codes directly below the <xsp:page> tag: + + <xsp:logic> + String a = parameters.getParameter("data-dir", "."); + </xsp:logic> + + That will cause a runtime exception is thrown since the variable 'parameters' + is not initialized at the time of the initialization of the variable 'a'. + + After doing this, if we don't remove the contents of work directory manually, + the XSP page won't reload even though we remove the above lines. + + Also this bug indicates that there should be a way to handle exceptions + occuring in the course of instance initialization. At this time, no messages + are provided even though NullPointerException is thrown. I spent a whole day to + figure out what's wrong, without knowing that it's because of the initial + trivial bug that was fixed earlier. + + Thanks... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
