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 model defined by the Xerces Schema API. But if a user wants to use the Xerces-2 implementation to build a schema file (lets say from a Java Interface/Class), it is buggy and inflexible. So I am at a crossroad. For the WSDL to Java subsystem where schema parsing is required, I am going to use the Xerces-2 implementation. In this case, I am only interested in the Xerces Schema API. For the Java to WSDL subsystem, where I need to generate the schema files, I will implement the interfaces defined by the Xerces Schema API. This provides me more control in generating the schema files. Talked to Jason about this and he concurred that this approach seems reasonable. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3874751#3874751 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3874751 ------------------------------------------------------- This SF.Net email is sponsored by: New Crystal Reports XI. Version 11 adds new functionality designed to reduce time involved in creating, integrating, and deploying reporting solutions. Free runtime info, new features, or free trial, at: http://www.businessobjects.com/devxi/728 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
