[JBoss-dev] [Design of JBoss's Web Services Implementation] - Re: XML Schema capabilities

2005-04-21 Thread [EMAIL PROTECTED]
It seems that parsing a schema to any object model would require creating instances of that object model and populate the state of those instances. This will probably be done through API methods on those object instances. Can you show us examples of the actual issues that you are having? Why can

[JBoss-dev] [Design of JBoss's Web Services Implementation] - Re: XML Schema capabilities

2005-04-20 Thread [EMAIL PROTECTED]
I just found out that the Xerces-2 Implementation is not useful for general use and is subject to change soon. http://issues.apache.org/jira/browse/XERCESJ-1067 The Xerces Schema API is not going to change. The Xerces-2 Implementation is good for parsing schema files and building an object mode

[JBoss-dev] [Design of JBoss's Web Services Implementation] - Re: XML Schema capabilities

2005-04-15 Thread [EMAIL PROTECTED]
Finally I managed to make Xerces schema infrastructure to help me create a test schema object graph as shown by this testcase - test: | /** | * Test Xerces ability to create XML schema | * @throws Exception | */ |public void testSchemaCreation() throws Exception |

[JBoss-dev] [Design of JBoss's Web Services Implementation] - Re: XML Schema capabilities

2005-04-14 Thread [EMAIL PROTECTED]
Requirements for Eclipse XSD are | * Please note: As of 2005/04/07 (Build 2.1.0.I200504070700), you will require the Eclipse 3.1 SDK M6 or newer. Earlier Integration builds should run on earlier Eclipse 3.1 builds. | * Please note: Use of XSD requires the EMF Runtime (RT) Package, or the c

[JBoss-dev] [Design of JBoss's Web Services Implementation] - Re: XML Schema capabilities

2005-04-14 Thread [EMAIL PROTECTED]
"[EMAIL PROTECTED]" wrote : It looks like you can construct a model from here: | | http://xml.apache.org/xerces2-j/javadocs/xerces2/org/apache/xerces/impl/xs/SchemaGrammar.html Thanks Jason. I am looking at it. But having a simpler API would have been better. I dont understand why they

[JBoss-dev] [Design of JBoss's Web Services Implementation] - Re: XML Schema capabilities

2005-04-14 Thread [EMAIL PROTECTED]
Plus an additional thing I noticed is that Xerces Schema Parser wants you to have just one schema element per file. If I have two schema elements, then it throws an error. No big deal. Can work around this. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873

[JBoss-dev] [Design of JBoss's Web Services Implementation] - Re: XML Schema capabilities

2005-04-14 Thread [EMAIL PROTECTED]
It looks like you can construct a model from here: http://xml.apache.org/xerces2-j/javadocs/xerces2/org/apache/xerces/impl/xs/SchemaGrammar.html View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873946#3873946 Reply to the post : http://www.jboss.org/index.html

[JBoss-dev] [Design of JBoss's Web Services Implementation] - Re: XML Schema capabilities

2005-04-14 Thread [EMAIL PROTECTED]
XSModel is the root when you have a schema file as input. I want to do the reverse. Create a schema file from scratch. Xerces has no facility to SET something on the XSModel http://xml.apache.org/xerces2-j/javadocs/xerces2/org/apache/xerces/impl/xs/XSModelImpl.html Xerces is a pure schema par

[JBoss-dev] [Design of JBoss's Web Services Implementation] - Re: XML Schema capabilities

2005-04-14 Thread [EMAIL PROTECTED]
What you are saying about the missing root element seems unlikely. The XSLoader cretes instances of XSModel, which should be the root the schema. anonymous wrote : | XSModel load(org.w3c.dom.ls.LSInput is) | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic

[JBoss-dev] [Design of JBoss's Web Services Implementation] - Re: XML Schema capabilities

2005-04-13 Thread [EMAIL PROTECTED]
Thanks to Jason Greene for pointing this out to me. There is a Eclipse project going on that provides an object graph to create a schema graph and serialize it into a file. http://download.eclipse.org/technology/xsd/scripts/home.php This brings us to a good question: JavaToWSDL uses the Eclip