Exception output is vague and misleading.
-----------------------------------------
Key: TAPESTRY-2196
URL: https://issues.apache.org/jira/browse/TAPESTRY-2196
Project: Tapestry
Issue Type: Bug
Components: Framework
Affects Versions: 5.0.10
Environment: Windows XP, Eclipse, Tapestry 5, Hibernate, Maven, Jetty
Reporter: Daniel
Priority: Minor
The exception output I received was a No Class Definition exception. All the
jar files were in their appropriate directories, so to debug the issue I had to
either follow the debugger deep into Tapestry code or revert my local changes
entirely.
The problem was that I had a protected boolean instance variable in a class
representing a form to edit a database object. The variable had no getter or
setter because it was never supposed to be referenced by Tapestry, and though
it was protected, the class of which it was part was neither extended anywhere
nor meant to be.
The startup form was called TaskList.java. The form with the problem was called
ProjectForm.java. The exception output displayed a line from TaskList.tml with
a message that ProjectForm.java was without a class definition. This occurred
before the TaskList was displayed, one more step before ProjectForm could be
displayed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
