[
https://jira.jboss.org/jira/browse/TEIID-917?page=com.atlassian.jira.plug...
]
Steven Hawkins resolved TEIID-917.
----------------------------------
Fix Version/s: 7.0
(was: 7.1)
Resolution: Done
Changed streamable to accept a InputStreamFactory source, which allowed the client to also
use SQLXMLImpl. Created a FileStore interface to hold large results, which autodeletes
when the SQLXML reference is garbage collected.
xml stream handling is inconsistent
-----------------------------------
Key: TEIID-917
URL:
https://jira.jboss.org/jira/browse/TEIID-917
Project: Teiid
Issue Type: Bug
Components: Common
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 7.0
Our SQLXMLImpl allows for a variety of source types - such as a streamsource coming from
the xml source connector. However if the resulting SQLXML is used by the client (and not
immediately consumed by something like XQuery) then the stream can only be read once.
Also all of the conversion routines in the XMLTranslator logic (and in the xml document
stylesheet application) are based upon full materialization. This may lead to memory
problems. In general our SQLXMLImpl should be backed by a string if small and a (temp)
file if large. Conversions from DOM and SAX sources would also need to create temp files
to protect memory and allow for multiple reads respectively.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira