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/07/03 00:34:12 UTC

[jira] Assigned: (TAPESTRY-355) Annotations bypass line precise exception reporting

     [ 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