Matthew Peters wrote:
Thanks for the encouragement, all. I'll let you know how I get on.
This probably off topic for this list, but the choice between
and is an interesting one.
The page Jean-Sebastien refers to says that is the
current thinking, but has its virtues too. It
rather depend
After building a fresh checkout and using initially empty maven repo, all
except testEncoding(org.apache.tuscany.sdo.test.XMLHelperTestCase)
failed. Is this a known issue? This is due to encoding mismatch between the
one coming from org.eclipse.emf.ecore.xmi.XMLResource
is ASCII and the expected on
Some more questions about website content changes - Please refer to 1)..9)
from
http://www.mail-archive.com/tuscany-user@ws.apache.org/msg02417.html
*Q*1) Could not find any other page with SDO Java specific get involved
*Q*4) sdo-project-code-structure.html - menu and new project structure added
Amita
>
> So I guess I can open a JIRA and fix variable HTML_HEADER from
> sample-sdo/DocumentSamples to contain the above and it will do the trick.
> Does this sound OK?
sounds good, thanks
Kelvin.
Guy,
no I'm afraid we don't have any lazy parsing capabilities at the moment.
Are you accessing the elements of the file through the data graph in the
order they appear in the instance document? There is a way behind the
scenes that I think we could begin to provide this kind of capability, by
Hi,
Is there a way (when iterating) to avoid that the entire XML file is
read in RAM at once? We want to read a large XML file with efficient
memory use (like Stax should allow).
Thanks
Guy
-
To unsubscribe, e-mail: [EMAIL
