Hi Brian,
We've been thinking of adding something on these lines to XMLBeans but I
couldn't find the time for it.
We've been thinking to use the pull parser model of Stax and to be able
to filter (custom or XPath) small pieces in and out of an XmlObject.
This should be working for both reading an
You are very close. Keep in mind that defaults are not
associated with types, but with elements/attributes. Other than that, once you
use it in the context of an enclosing element, it should work like you
expect.
If you're still having trouble, could you post a code
sample and we'll go from
Looks like a forward-compatibility problem: the version of
XmlBeans used to generate the classes is newer than the version used to run them
(probably 2.1.0 vs 2.0.0).
Radu
From: Ziv Zeira [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 13, 2006 7:49 AMTo:
user@xmlbeans.apache.orgSubject: P
You can't alter this limit currently, I'm attaching my
reply to a different thread, I think it also makes sense in this
thread.
Thanks,
Radu
From: Larner, Ross S
[mailto:[EMAIL PROTECTED] Sent: Thursday, June 08, 2006
10:41 AMTo: user@xmlbeans.apache.orgSubject: RE: passing
xml as a str
Actually there is a JIRA talking about this:
http://issues.apache.org/jira/browse/XMLBEANS-176 (whose priority I have
just updated).
I would want to point out though that "conversion" is not the right way
to think about it, since XmlBeans doesn't 'remember' whether originally
the text was encoded
5 matches
Mail list logo