Hi all,
We are using xml beans 1.0.4, latest binary release. We're
having a really horrible problem on WebSphere 5.1 trying to
validate
xml requests coming in on our web services.
What seems to be randomly, different components (in our
ear's
Robert,
.selectPath returns live objects from the original tree which was
executed on.
.execPath will always return new documents, sometimes copies of the
original.
In order to avoid loosing the results once you modify the document you
should:
1. run select path with a cursor: XmlCursor.selectPat
Did you try using scomp script directly;
it might be a bug in the ant task implementation.
Cezar
From: Siegfried Baiz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 10, 2006
10:54 AM
To: user@xmlbeans.apache.org
Subject: Re: JDK 1.5 Generics rsp.
Enumerations in generat
Robert,
you can accomplish what you want using XmlObject.selectPath().
Take a look at the samples under XQueryXPath, in particular,
org.apache.xmlbeans.samples.xquery.SelectPath.
- Wing Yew
-Original Message-
From: Robert W. Wade [mailto:[EMAIL PROTECTED]
Sent: Monday, October 09, 2006 8:
Hallo,
I really would be thankful for any comments.
Is this below a stupid question?
If not, I wonder why nobody pays any attention on this?
Thank in advance
Siggi
Siegfried Baiz schrieb:
Hallo All,
I' m using XmlBeans 2.2.0 for compiling XSD-Files to Java-Classes.
I've read
I do not believe you are correct, at least with the version of
XMLBeans that I am using. I am using 2.2.0, JKD 1.4.2.
The java class I used is attached. The output is listed below:
first string
second string
Process finished with exit code 0
Rob
--- Ophir Bleiberg <[EMAIL PROTECTED]>
Title: Newbie question: XMLBeans does not order 'sequence' elements according to the schema definitions?!
It appears that the when creating a document through the Java API, the order of the elements in a sequence in the produced document is the order in which 'set' was called, and not the ord
7 matches
Mail list logo
