You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org> on 2005/06/23 20:34:10 UTC
[jira] Created: (TAPESTRY-355) Annotations bypass line precise exception reporting
Annotations bypass line precise exception reporting
---------------------------------------------------
Key: TAPESTRY-355
URL: http://issues.apache.org/jira/browse/TAPESTRY-355
Project: Tapestry
Type: Improvement
Components: Annotations
Versions: 4.0
Reporter: Howard M. Lewis Ship
Biggest problem with annotations is that, once you start using them, you lose line precise exception reporting (that you had with the XML).
It would be nice if annotations include a Location object, even if it exists only for reporting of errors. That is, it could return null for getResource(), as long as it produced a toString() of "public abstract method getValue() of class org.foo.MyComponent" or such.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Assigned: (TAPESTRY-355) Annotations bypass line precise exception reporting
Posted by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-355?page=all ]
Howard M. Lewis Ship reassigned TAPESTRY-355:
---------------------------------------------
Assign To: Howard M. Lewis Ship
> Annotations bypass line precise exception reporting
> ---------------------------------------------------
>
> Key: TAPESTRY-355
> URL: http://issues.apache.org/jira/browse/TAPESTRY-355
> Project: Tapestry
> Type: Improvement
> Components: Annotations
> Versions: 4.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> Biggest problem with annotations is that, once you start using them, you lose line precise exception reporting (that you had with the XML).
> It would be nice if annotations include a Location object, even if it exists only for reporting of errors. That is, it could return null for getResource(), as long as it produced a toString() of "public abstract method getValue() of class org.foo.MyComponent" or such.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Closed: (TAPESTRY-355) Annotations bypass line precise exception reporting
Posted by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-355?page=all ]
Howard M. Lewis Ship closed TAPESTRY-355:
-----------------------------------------
Fix Version: 4.0
Resolution: Fixed
> Annotations bypass line precise exception reporting
> ---------------------------------------------------
>
> Key: TAPESTRY-355
> URL: http://issues.apache.org/jira/browse/TAPESTRY-355
> Project: Tapestry
> Type: Improvement
> Components: Annotations
> Versions: 4.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 4.0
>
> Biggest problem with annotations is that, once you start using them, you lose line precise exception reporting (that you had with the XML).
> It would be nice if annotations include a Location object, even if it exists only for reporting of errors. That is, it could return null for getResource(), as long as it produced a toString() of "public abstract method getValue() of class org.foo.MyComponent" or such.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Commented: (TAPESTRY-355) Annotations bypass line precise exception reporting
Posted by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-355?page=comments#action_12314343 ]
Howard M. Lewis Ship commented on TAPESTRY-355:
-----------------------------------------------
In case that's not clear, it would be nice if the annotations, when they create some kind of specification object, attach a meaningful Location to it.
> Annotations bypass line precise exception reporting
> ---------------------------------------------------
>
> Key: TAPESTRY-355
> URL: http://issues.apache.org/jira/browse/TAPESTRY-355
> Project: Tapestry
> Type: Improvement
> Components: Annotations
> Versions: 4.0
> Reporter: Howard M. Lewis Ship
>
> Biggest problem with annotations is that, once you start using them, you lose line precise exception reporting (that you had with the XML).
> It would be nice if annotations include a Location object, even if it exists only for reporting of errors. That is, it could return null for getResource(), as long as it produced a toString() of "public abstract method getValue() of class org.foo.MyComponent" or such.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org