I?m using XMLBeans in a project running on:
[ ] jdk 1.3
[ ] jdk 1.4
[ ] jdk 1.5
[X] jdk 1.6
Cezar Andrei cezar.and...@oracle.com
05/11/2009 01:58 PM
Please respond to
user@xmlbeans.apache.org
To
d...@xmlbeans.apache.org, user@xmlbeans.apache.org
cc
Subject
[POOL] jdk 1.4 support
You'll need to execute it in one of the following ways:
./scomp -out catalog.jar catalog.xsd
or
~/Library/xmlbeans-2.4.0/bin/scomp -out catalog.jar catalog.xsd
This is a PATH issue, not an issue with XmlBeans. The problem is that
scomp is not in your PATH so you must specify where it can
I would open a cursor and perform a select. All objects
that you are working with extend XmlObject, so you have complete access to the
API's. But this assumes that you would have knowledge of the XPath that you want
to access, so you would need to know the structure of the document and where
I think what you actually want to be doing is the
following:
Object result =
null; Class destClass =
Class.forName(beanId); Class[] innerClasses =
destClass.getClasses(); Class factory =
null; for (int i = 0; i
innerClasses.length; i++) { if
I found it.
XmlDocumentProperties props =
confirmDoc.documentProperties();props.setVersion(orderRequest.documentProperties().getVersion());props.setEncoding(orderRequest.documentProperties().getEncoding());props.setDoctypeSystemId(DOCTYPE_SYSTEM_ID);props.setDoctypeName(DOCTYPE_NAME);
From:
This is a challenge. Xml Spy does a fair job at this but
you must remember that some of the data types defined in dtd don't always map
well to schema. I ran into this converting the RosettaNet dtd into a schema.
This was an enormous challenge and took a great deal of patience and time.
I have a schema that
defines a request and a confirmation as it's root elements. Many of the data
types contained under these two root elements are the same and are defined as
global. The problem I'm having is when I create a confirmation document and copy
objects from the request document
This problem, per the documentation, is attributed to
calling a setXXX method on your XmlBean objects and assigning a null value. If
you don't want the elements to appear in your document then you should not call
the setXXX method passing in a null. If the null has been assigned and you do
I'm having a bit of trouble getting my queries to work correctly. I have a
rather complex XML schema that is deep. I want to perform a query to get
all of the CustomerInformation elements throughout the document. This I
accomplish very easily:
custInfoCursor =
9 matches
Mail list logo