[jira] [Updated] (PIVOT-864) Add a pluggable file system architecture to FileBrowser so remote browsing can be done
[ https://issues.apache.org/jira/browse/PIVOT-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Whitcomb updated PIVOT-864: - Due Date: 31/Dec/12 (was: 28/Sep/12) Add a pluggable file system architecture to FileBrowser so remote browsing can be done -- Key: PIVOT-864 URL: https://issues.apache.org/jira/browse/PIVOT-864 Project: Pivot Issue Type: New Feature Components: wtk Affects Versions: 2.0.2 Environment: Windows, Linux, OSX Reporter: Roger Whitcomb Assignee: Roger Whitcomb Labels: filebrowser Fix For: 2.1 Original Estimate: 336h Remaining Estimate: 336h Our application requires the ability to be able to browse (for instance) a Linux machine from the Windows desktop. For this I would like to add (somehow) a pluggable file system architecture so that I could (for instance) implement an FTP protocol underneath the FileBrowser so that I can browse through directories and files on something other than the local machine. We would also need to be able to type in a host name or TCP/IP address to start browsing the remote machine. -- 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
[jira] [Closed] (PIVOT-536) BXMLSerializer should provide a structure error object when a serializer error occurs
[ https://issues.apache.org/jira/browse/PIVOT-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Whitcomb closed PIVOT-536. Resolution: Not A Problem Fix Version/s: (was: 2.1) 2.0.3 Closing as the feature is already available, so not a problem. 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 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
[jira] [Reopened] (PIVOT-536) BXMLSerializer should provide a structure error object when a serializer error occurs
[ https://issues.apache.org/jira/browse/PIVOT-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Whitcomb reopened PIVOT-536: -- Assignee: Roger Whitcomb 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
