[ 
https://issues.apache.org/jira/browse/PIVOT-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488891#comment-13488891
 ] 

Roger Whitcomb edited comment on PIVOT-536 at 11/1/12 6:08 PM:
---------------------------------------------------------------

I'm going to reopen it myself to add (as Noel suggested) a method to return the 
location of the xmlStreamReader, which could be called at any time, but most 
needed in the event of some other error.
                
      was (Author: rwhitcomb):
    I'm going to reopen it myself to add (as Noel suggested) a method to return 
the location of the xmlStreamReader, which could be called at any time, but in 
the event of some other error.
                  
> BXMLSerializer should provide a structure error object when a serializer 
> error occurs
> -------------------------------------------------------------------------------------
>
>                 Key: PIVOT-536
>                 URL: https://issues.apache.org/jira/browse/PIVOT-536
>             Project: Pivot
>          Issue Type: Improvement
>          Components: wtk
>            Reporter: Appddevvv
>            Assignee: Roger Whitcomb
>            Priority: Trivial
>             Fix For: 2.0.3
>
>
> When an error occurs in the serializer, logException() is typically called. 
> The error message, line number and other information is typically not 
> available for use by tooling.  WTKXSerializer should provide a structured 
> object with the error information in it e.g. the line number.
> I don't have a patch for this but I think a simple error object and a 
> property accessor would be all that's needed. The error object could be 
> accessed as part of exception handling.
> I came across when writing pivotpad (xamlpad like tool) and wanted to 
> highlight the error in the bxml text.
> This improvement is  targeted towards tooling support and has no other 
> apparent use.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to