Hi Martin, MG>no insult intended this authors tag is throughout the codebase I was also unsure how to read your original post. I'm glad to read that no insult was intended.
I'll take this opportunity to remind everyone that item 5 in the open source definition [1] specifically states "The license must not discriminate against any person or group of persons." In my opinion open and equal collaboration is a guiding principle for all open source projects. MG>why do the latest AXIOM and AXIS specifically exclude xerces-impl and implement their own xml-schema parsers? My understanding (anyone with more knowledge feel free to correct me) is that for performance reasons Axis relies on a StAX [2] based parser now instead of a DOM based parser. The implementation of XmlSchema in the WS project was to provide a model that fits in better with the WS use cases. MG>if you can exclude the political noise.. how do you account for the NPEs that dag is seeing? Sagara recently responded, "I have tested your code with provided WSDL file without any issue. I'm pretty much sure you have some incorrect dependencies on your classpath , as I mentioned please look at the lib directory in the Woden distribution package to identify required dependencies." [1] http://www.opensource.org/docs/osd [2] http://en.wikipedia.org/wiki/StAX Lawrence From: Martin Gainty <[email protected]> To: <[email protected]>, <[email protected]>, <[email protected]> Date: 04/29/2011 10:53 AM Subject: RE: woden and xerces Xerces2 Java 2.11.0 (XML Schema 1.1) (Beta) compatibility question From: [email protected] To: [email protected]; [email protected]; [email protected] Date: Thu, 28 Apr 2011 13:27:51 -0700 Subject: RE: woden and xerces Xerces2 Java 2.11.0 (XML Schema 1.1) (Beta) compatibility question I am not sure what you are talking about Martin, but “Xerces” is a fully active Apache Top Level Project: http://xerces.apache.org/ MG>agreed I am vaguely insulted by your continued use of the phrase “indians who worked on the code” and I am 1) not from India and 2) never worked on Xerces. MG>no insult intended this authors tag is throughout the codebase MG>* @author Rajiv Mordani MG>? You may be trying to reference “Crimson”, which was the default XML parser in the JRE until it was replaced by Xerces around Java 5 or 6. Crimson did the job mostly OK, but had some serious problems and most folks didn’t use it and used Xerces instead – hence the JDK replacement. I don’t know the full history on Crimson, but Wikipedia claims it was also part of the Apache XML project. See http://en.wikipedia.org/wiki/Apache_XML “No longer developed projects Crimson: A Java XML parser derived from the Sun Project X Parser” In any case, it doesn’t seem like you have all the facts straight here and as far as I know, Xerces supports XML Schema to the extent documented just fine (i.e. XSD validation). MG>why do the latest AXIOM and AXIS specifically exclude xerces-impl and implement their own xml-schema parsers? MG>if you can exclude the political noise.. how do you account for the NPEs that dag is seeing? Tom Jordahl From: Martin Gainty [mailto:[email protected]] Sent: Thursday, April 28, 2011 3:51 PM To: [email protected]; [email protected]; [email protected] Subject: RE: woden and xerces Xerces2 Java 2.11.0 (XML Schema 1.1) (Beta) compatibility question as i explained in my response i wrote last nite you are doing nothing wrong the original IBM Xerces codebase was geared to processing DTD based XML when XSD 1.0 was published ibm made a half-hearted attempt to accomodate XSD schema which worked for simple-type elements only but failed miserably with ComplexType Element Declarations since that time IBM has opensourced the xerces project to sourceforge (thats a fancy way of saying abandoned xerces) and any necessary additions to the code base (such as accomodating XMLSchema 1.1) have gone un-addressed since 2006 the end result is that you will see NPE NullPointerExceptions popping up all over the place because the indians who worked on the code never anticipated any of the test scenarios for XML Schema 1.1..there was no architect and no project lead and general mayhem took over the project..which is the primary reason xerces became an abandoned project currently i have a refactor in the works which implements and extends the original xerces codebase from Sun Microsystems JAXP parser deploy.jar from the original Sun Microsystems JDK distributions implementing specifically com.sun.org.apache.xerces package which DOES work and whose parse routines are implemented extensively by both Glassfish and Weblogic Application Servers should be ready for beta by 1 May (in case you're interested) let me know if you're willing to test I'll send you ca copy next week Martin Gainty ______________________________________________ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > To: [email protected] > From: [email protected] > Subject: woden and xerces Xerces2 Java 2.11.0 (XML Schema 1.1) (Beta) compatibility question > Date: Thu, 28 Apr 2011 18:11:07 +0000 > > I am using woden to parse wsdl files and Xerces2 Java 2.11.0 (XML Schema 1.1) > (Beta) to parse xsd documents. > WSDLFactory factory = WSDLFactory.newInstance(); > WSDLReader reader = factory.newWSDLReader(); > reader.setFeature(WSDLReader.FEATURE_VALIDATION, true); > String wsdlurl = "E://apps//metacenter_home//xsd//greath.wsdl"; > Description descComp = reader.readWSDL(wsdlurl); > > When I do so I get the following exception while execution the above code. > > java.lang.NullPointerException > at java.util.StringTokenizer.<init>(StringTokenizer.java:182) > at java.util.StringTokenizer.<init>(StringTokenizer.java:204) > at org.apache.xerces.impl.dv.xs.XSSimpleTypeDecl.getActualValue(Unknown > Source) > at org.apache.xerces.impl.dv.xs.XSSimpleTypeDecl.validate(Unknown Source) > at org.apache.xerces.impl.xs.util.XSTypeHelper.isValueValidForASimpleType > (Unknown Source) > at > org.apache.xerces.impl.xs.util.XSTypeHelper.isAtomicValueValidForAnUnion > (Unknown Source) > at org.apache.xerces.impl.xs.XMLSchemaValidator.addDefaultAttributes > (Unknown Source) > at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement > (Unknown Source) > at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown > Source) > at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement > (Unknown Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher. > dispatch(Unknown Source) > at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument > (Unknown Source) > at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) > at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) > at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) > at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) > at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) > at org.apache.woden.internal.DOMWSDLReader.getDocument > (DOMWSDLReader.java:796) > at org.apache.woden.internal.DOMWSDLReader.readWSDL > (DOMWSDLReader.java:296) > at org.apache.woden.internal.DOMWSDLReader.readWSDL > (DOMWSDLReader.java:157) > Link: > Xerces2 Java 2.11.0 (XML Schema 1.1) (Beta) - zip > > Could you tell me what I am doing wrong? > > Thanks > Rachna > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
