You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Daniel (JIRA)" <de...@tapestry.apache.org> on 2008/02/25 17:52:51 UTC
[jira] Created: (TAPESTRY-2196) Exception output is vague and
misleading.
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAPESTRY-2196) Protected field in a component
class does not generate an understandable exception, instead
NoClassDefFound
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-2196:
-------------------------------------------
Summary: Protected field in a component class does not generate an understandable exception, instead NoClassDefFound (was: Exception output is vague and misleading.)
You'd think you see a bunch of nested exceptions with something to the effect of "protected fields are not allowed" at the root.
> Protected field in a component class does not generate an understandable exception, instead NoClassDefFound
> -----------------------------------------------------------------------------------------------------------
>
> 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Assigned: (TAPESTRY-2196) Protected field in a component
class does not generate an understandable exception, instead
NoClassDefFound
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAPESTRY-2196:
----------------------------------------------
Assignee: Howard M. Lewis Ship
> Protected field in a component class does not generate an understandable exception, instead NoClassDefFound
> -----------------------------------------------------------------------------------------------------------
>
> 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
> Assignee: Howard M. Lewis Ship
> 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Closed: (TAPESTRY-2196) Protected field in a component class
does not generate an understandable exception, instead NoClassDefFound
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-2196.
------------------------------------------
Resolution: Cannot Reproduce
I've tried to duplicate your situation as best as I can and get the correct and detailed exception report page each time. I've added a test for this. I can't explain the issue you had with the mysterious failure.
> Protected field in a component class does not generate an understandable exception, instead NoClassDefFound
> -----------------------------------------------------------------------------------------------------------
>
> 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
> Assignee: Howard M. Lewis Ship
> 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org