XML Parser, Class Generator demo problem

Hello,
I have downloaded today the XML Parser and the Class Generator. I have successfully compiled the SampleMain.java coming with the kit. When running it there is a problem with the expected DTD filename input.
The program prints out the needed format as:
Usage: java SampleMain [-root <rootName>] <fileName>
fileName Input file, XML document or external DTD file
-root <rootName> Name of the root Element (required if the input file is an external DTD)
Whatever I try as DTD filename input fails.
I work on Windows-NT!
I have tried running with JDK 1.1.7.a and JDK 1.2.2.
Thanks, Yigal.

java SampleMain Widl.xml
or
java SampleMain -root WIDL Widl.dtd
Make you have Widl.xml and Widl.dtd are
in the current directory. Also, remember
Java is case sensitive.
If you are still getting errors, please
post the error message.
null

Similar Messages

XML Schema Class Generator Problem compiling generated java programs

Hi,
I ran oracg on the po.xsd schema from X3Cs XML Schema Part 0: Primer which successfully generated the java codes. I ran into problems when I compile the generated classes. Here's what I'm getting:
C:\oracle\xml\xdk\demo\java\classgen\Po2>javac -classpath ".;C:\oracle\xml/lib/xmlparserv2.jar;C:\oracle\xml/lib/xschema.jar;C:\oracle\xml/l
ib/classgen.jar;.;C:\Program Files\VicunaJ521\java\lib\collections.jar;C:\Program Files\VicunaJ521\java\lib\vicunalite.jar;C:\Program Files\
XConverter\XConverter.jar;C:\Program Files\XConverter\IDLGenerator.jar; c:\jdk1.2.2\lib\dt.jar;c:\jdk1.2.2\lib\jvm.jar;c:\jdk1.2.2\lib\tools
.jar;c:\oracle\ora81\jdbc\lib\classes12.zip;c:\oracle\ora81\jdbc\nls_charset12.zip;C:\oracle\xml\lib\classgen.jar;C:\oracle\xml\lib\xmlparse
rv2.jar" *.java
.\types\PurchaseOrderType.java:75: Type expected.
public void addComment(null.Comment thecomment)
^
.\types\Items.java:141: Type expected.
public void addComment(null.Comment thecomment)
^
2 errors
Running the demo which comes with oracles version of po.xsd was OK. What's the difference between the po.xsd from oracle and the po.xsd from W3C? Are there any W3C recommendation for XML Schema not supported by Oracle's class generator?

Which po.xsd do you use? Would you post it?
Thanks. Here's the copy of the po.xsd from the W3C website. (http://www.w3.org/TR/xmlschema-0/#po.xsd)
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Purchase order schema for Example.com.
Copyright 2000 Example.com. All rights reserved.
</xsd:documentation>
</xsd:annotation>
<xsd:element name="purchaseOrder" type="PurchaseOrderType"/>
<xsd:element name="comment" type="xsd:string"/>
<xsd:complexType name="PurchaseOrderType">
<xsd:sequence>
<xsd:element name="shipTo" type="USAddress"/>
<xsd:element name="billTo" type="USAddress"/>
<xsd:element ref="comment" minOccurs="0"/>
<xsd:element name="items" type="Items"/>
</xsd:sequence>
<xsd:attribute name="orderDate" type="xsd:date"/>
</xsd:complexType>
<xsd:complexType name="USAddress">
<xsd:sequence>
<xsd:element name="name" type="xsd:string"/>
<xsd:element name="street" type="xsd:string"/>
<xsd:element name="city" type="xsd:string"/>
<xsd:element name="state" type="xsd:string"/>
<xsd:element name="zip" type="xsd:decimal"/>
</xsd:sequence>
<xsd:attribute name="country" type="xsd:NMTOKEN"
fixed="US"/>
</xsd:complexType>
<xsd:complexType name="Items">
<xsd:sequence>
<xsd:element name="item" minOccurs="0" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="productName" type="xsd:string"/>
<xsd:element name="quantity">
<xsd:simpleType>
<xsd:restriction base="xsd:positiveInteger">
<xsd:maxExclusive value="100"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="USPrice" type="xsd:decimal"/>
<xsd:element ref="comment" minOccurs="0"/>
<xsd:element name="shipDate" type="xsd:date" minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="partNum" type="SKU" use="required"/>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>

<xsd:simpleType name="SKU">
<xsd:restriction base="xsd:string">
<xsd:pattern value="\d{3}-[A-Z]{2}"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>

Documentation for Oracle XML parser Classes and Interfaces

I would like to use the oracle XMLParser V2 classes with JDeveloper 3.1, but I cannot find any reference documentation for the classes and interfaces in help.
I am especially interested in a documentation for the XSLProcessor class. The only information I found was provided with the few provided samples.

I don't think the javadoc for this was included in the release. You can get the Javadoc (as well as the latest version of the XML Parser v2) here on OTN.
Take Care,
Rob
null

XML parser for C++ - encoding problem

when I trying parse xml data
XMLParser xP;
xP.xmlinit((oratext*)"ISO-8859-5");
err = xP.xmlparseBuffer((oratext*)buff, len, (oratext*)"ISO-8859-5", (ub4)0);
I got the error 217 defined as
#define XMLERR_END_QUOTE 217 /* No ending quote was seen */
ORACLE_HOME and ORA_NLS variables set correctly.
What the problem?

Please specify the XDK version and send the sample test case.

Oracle.xml.parser.v2 generating tags

We are creating an XML DOM from java and are having trouble getting the tags created as we want. When we use XMLText it creates the tag as <tagName/>value rather than <tagName>value</tagName>. We want separate open and close tags. Any ideas?
Lori

You have to create an element named tagName and then append a child text node with the value value.

XMl parser version problem for running struts project in jdeveloper 10.1.3

Dear All.
I am trying to run a struts (v 1.2.9) based project in Jdeveloper 10.1.3.1.0.The struts version in Jdeveloper is 1.1.
when i am trying to run the index.jsp i get an error:
org.xml.sax.SAXNotRecognizedException: http://apache.org/xml/features/validation/dynamic
I think the XML parser version is a problem.Jdeveloper has OracleXMLParser v2 and i think the XML Parser apis used in building the project is different.I have placedcustiom xml parser apis and the xerces.jar in the jdevbin/jdev/lib folder and included these jar in the bootclasspath as follows:
AddVMOption -Xbootclasspath/p:../lib/xml-apis.jar
AddVMOption -Xbootclasspath/p:../lib/xerces-2.6.2.jar
But even then the Exception persists.Is the syntax for Xbootclasspath wrong or i need to place these custom api's in some other location of jdev.
I am not being able to figure out the XMl parser problem.
Any help wud be great.
Is it that i cant run the project in jdeveloper.Just to mention the application is deployed in OC4J on the server and runs fine..But its only that i kant run it locally through jdeveloper

I am also facing the same issue on my laptop. I searched for forum but no luck.
appreciate if anybody can throw some light on this.

How use XML-Parser in Web Dypro (how get filename)

Hi everybody,
i want to use the saxparser to read a xml-file via a Fileupload-UI element. In Web Dynpro it is not possible to get the path of a file which was on a client through the Fileupload-UI. So how can i use a xml-parser when i have to give it the file name?
Is it possible to use the "resource" of the Fileupload-UI instead ot the filename? How can i call the parser?
 SAXParser saxParser= null;
 try{
 SAXParserFactory factory = SAXParserFactory.newInstance();
 saxParser = factory.newSAXParser();
 saxParser.parse( new File(??????), new Gaeb());
 }catch (Exception ex){
 ex.printStackTrace();
regards,
Sid

Hi Siarhei,
i bind the resource property to my context of type IWDResource, the xml-file is now uploaded to KM-Content : /documents/GSW/Upload_UT_Sample_A.xml.
I create with resource.getURL() the path of the xml-file and give it to my xml-parser class, but i cannot get any value
from my parser (value returns "null"). Now i don't know if i have a mistake in creating the path of my file or a mistake in my parser??
Could you please have a look to my source code:
I try to get the path with:
 /* Get Path of "/documents/GSW/XML/Upload_UT_Sample_A.xml" */
 String urlToFile = resource.getUrl(WDFileDownloadBehaviour.AUTO.ordinal());
 /* Call the Parser Class with path*/
 MyXMLParser myParser= new MyXMLParser ( urlToFile );
 /* Get one value from xml-class*/
 wdComponentAPI.getMessageManager().reportSuccess("Value: " + myParser.getValue()); <-- returns "null"
My XML-Class:
public class MyXMLParser extends DefaultHandler {
 private String path = null;
 private String fName = null;
 public String lValue;
 private boolean lSupplier = false;
 private boolean lQuoteNumber = false;
 public Gaeb(){ }
 public Gaeb(String path){
 SAXParserFactory factory = null;
 SAXParser saxParser = null;
 try {
 factory = SAXParserFactory.newInstance();
 saxParser = factory.newSAXParser();
 saxParser.parse( path , new MyXMLParser () ); <-- i try also new File(path) instead of path.
 } catch (Exception ex){
 ex.printStackTrace();
 public void startElement(String uri, String localName,
 String qName, Attributes attributes)
 throws SAXException {
 lSupplier = true;
 public void characters(char[] ch, int start, int length)
 throws SAXException {
 if (lSupplier){
 this.lValue = new String (ch,start,length);
 public String getValue(){
 return this.lValue;
regards,
Sid
Edited by: Sid on Dec 2, 2009 2:47 PM

Cannot create controls/constants/indicators from XML parser

Is there any reason I cannot create (by right clicking) a control/constant/indicator of a XML ref from the XML parser function? I need to make subvi's to build/read xml files, and that is really impossible without that ability.
Labview 2012 f3
Solved!
Go to Solution.

This bug has already been reported (CAR 357092), and is scheduled to be fixed in the next service pack release. For now, here's a workaround:
1. Create a reference indicator from Functions » Programming » File I/O » XML » XML Parser » New.vi.
2. Right click on the new "DOM Document Out" indicator terminal and select Create > Control (or Indicator).
3. Right click on the new control/indicator and choose Select XML Parser Class. Then, you can select whatever class you need.
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

ANN: XML Class Generator for Java Available

The Oracle XMCL Class Generator for Java is now available as an
initial beta release on the Oracle Technology Network at
http://technet.oracle.com. Select 'xml' from the Technology menu.
The XML Class Generator will generate a set of Java source files
based on an input DTD. The generated Java source files can then
be used to construct, optionally validate, and print a XML
document that is compliant to the DTD specified. This is an early
beta release and has the following features:
* Creates Java Classes from DTDs to enable the programmatic
construction of XML documents.
* Supports validation mode to assist debugging.
* Works with the Oracle XML Parser in Java.
* Creates documents conforming to the W3C XML 1.0
Recommendation.
* Supports creating documents in the following encodings:
UTF-8
UTF-16
ISO-10646-UCS-2
ISO-10646-UCS-4
US-ASCII
EBCDIC-CP-US
ISO-8859-1
Shift_SJIS
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
null

Thanks,
Rob
Oracle XML Team wrote:
: First, the link has been fixed. As to your access exception,
we
: have traced it to a difference between JDK 1.1.x and JDK 1.2.
: You can solve it by using a 1.1.x version of the JDK or wait
till
: our production version of our XML Parser becomes available
within
: a week which will work with 1.2.
: Oracle XML Team
: http://technet.oracle.com
: Rob Edagr (guest) wrote:
: : 1) The HREF on the download page for the NT version points
to
: : the version 102 parser not the classgen.
: : 2) After downloading and installing the classgen (by
guessing
: : what the url was) I ran it and get the following
: : C:\jdk1.2\xml\ora\classgen\sample>java SampleMain -root
: : wddxPacket wddx_0090.dtd
: : Exception in thread "main" java.lang.IllegalAccessError: try
to
: : access class oracle/xml/parser/XMLNode from class
: : oracle/xml/classgen/ClassGenerator
: : at oracle.xml.classgen.ClassGenerator.generate
(Compiled
: : Code)
: : at SampleMain.main(SampleMain.java:65)
: : Any idea on what the problem is (same error with sample dtd)
: : Rob
: : Oracle XML Team wrote:
: : : The Oracle XMCL Class Generator for Java is now available
as
: : an
: : : initial beta release on the Oracle Technology Network at
: : : http://technet.oracle.com. Select 'xml' from the
Technology
: : menu.
: : : The XML Class Generator will generate a set of Java source
: : files
: : : based on an input DTD. The generated Java source files can
: : then
: : : be used to construct, optionally validate, and print a XML
: : : document that is compliant to the DTD specified. This is
an
: : early
: : : beta release and has the following features:
: : : * Creates Java Classes from DTDs to enable the
programmatic
: : : construction of XML documents.
: : : * Supports validation mode to assist debugging.
: : : * Works with the Oracle XML Parser in Java.
: : : * Creates documents conforming to the W3C XML 1.0
: : : Recommendation.
: : : * Supports creating documents in the following
encodings:
: : : UTF-8
: : : UTF-16
: : : ISO-10646-UCS-2
: : : ISO-10646-UCS-4
: : : US-ASCII
: : : EBCDIC-CP-US
: : : ISO-8859-1
: : : Shift_SJIS
: : : Oracle XML Team
: : : http://technet.oracle.com
: : : Oracle Technology Network
: Oracle Technology Network
null

Problem in IAS Server with generation of PDF with FOP and XML parsing

Dear co.forumers :
We are developing an application that generates a pdf document with FOP Apache utilities, and this PDf is stored in a folder of the server. Firts of all, a DDBB data is retrieved using java ( jdbc) middleware classes ( servlets ), and with these data, the pdf is generated using FOP. In these process, he data retrieved from the DDBB is converted in a XML file , and the with the XSL FOP utility, the pdf is generated.
In the other hand, we have another application that consults data from a java beans, using a JSP, generates a XML with the data of the beans, and with this XML, and with a XSL file generates and html , with the data and fixed text.
Both applications have been deployed as a separated WebApp in the IAS. Both use Xalan as XML parser amb Xerces is used aswell.
So, the problem is , after generating a pdf with the firts application, every html generated via JSP-XML-XSL transformation in the second application is shown completelly bad formated. All fixed text are wrongly composed, and the text that should appear in textFields and ComboBoxes is also bad formated. The XML with the data is well generated, so the problem is in the parsing of these XML and the conversion in html through XSL. We have to re-initiate the server and then everything goes well again. If no pdf is launched, no problem occurs with the other application.
How an a WEB APP pplication can affect to another, installed both in different folders of the IAS ? We tried to change Xalan version and FOP version, but no result.
Is this a Poltergeist ?? and X file , maybe ?
Has anyone had the same problem ?
Pleae, any help will be very wellcomed.

A PDF document may be generated in the JDeveloper OC4J server.
http://www.oracle.com/technology/pub/notes/technote_vohra_fop.html

JSR 172 XML parser in WTK 2.5: problems compared to 2.2

Hi,
I'm experiencing 2 problems with the WTK 2.5 JSR 172 XML parser that do not occur with:
-WTK 2.2
-Sony-Ericsson Emulator WTK2
-Sony-Ericsson devices.
They are:
- attributes.getLocalName(i) always returns an empty string
- documents with multiple roots cause a parser panic
Anyone has a hunch?
Thanks a lot,
Philippe
Message was edited by:
philippelaporte

I wonder if anyone has encountered the same problem as I and has found a workaround about it. I am trying to create a UI builder that generates itself by reading an XML file.
One of the elements is a Combo Box, which should be read from the following structure:
<form>
 <combobox>
 <value>My first value</value>
 <value>My second value</value>
 <value>My third value </value>
 </combobox>
</form>Then I proceed to generate a vector of UI Elements, and process the Combobox, for example, as follows:
import org.xml.sax.*;
import org.xml.sax.helpers.*;
import java.util.*;
public class UIConfHandler extends DefaultHandler{
 //For knowing to which element am I adding content
 private Stack tagStack = new Stack();
 //An interface that allows me to access content to my elements
 private UIElement element;
 //A container of the elements retrieved from the file
 private Vector envelope;
 public UIConfHandler(){
 public void startDocument() throws SAXException {
 envelope = new Vector();
 public void endDocument() throws SAXException {
 public void startElement(String uri, String localName, String qName, Attributes attributes) throws SAXException{
 System.out.println("Beginning of the element");
 if(qName.equals("combobox")){
 //I just cast my element as a Combo Box element, and add specific content from within the attributes of the tag
 element = new ComboBoxElement(attributes.getValue("id"),attributes.getValue("label"),attributes.getValue("type"),"");
 else{
 //And I add the reference to which element am I currently in via the stack
 tagStack.push(qName);
 public void characters(char[] ch, int start, int length) throws SAXException{
 String chars = new String(ch, start, length).trim();
 if(chars.length() > 0){
 if((qName.equals("value"))){
 if (element instanceof ComboBoxElement ){
 //I add a specific value to a Vector inside my ComboBox content
 ((ComboBoxElement) element).addElementToVector(chars);
 else{
 System.out.println("Content with no action specified.");
 public void endElement(String uri, String localName, String qName, Attributes attributes) throws SAXException{
 System.out.println("End of the element");
 if(qName.equals("combobox")){
 //After all the values are added inside the internal vector of the element, add the element to the container
 envelope.addElement(element);
 //And remove the combobox element from the stack
 tagStack.pop();
 public Vector getEnvelope() {
 return envelope;
}Afterwards, I would use this element to create a ChoiceGroup to be viewed in a MIDlet. The problem is that the code in endElement is never called. Does somebody know what this could be?
/C�sar
Message was edited by:
Sigurdvh

Problem to swap XML parser

Hi all,
I am trying to replace the official oracle XML library by apache xerces on a soa suite 10.1.3.1 developper hosted on a linux red hat platform.
I have found a how to on oracle web site (http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/how-to-swapxmlparser/doc/readme.html). I hadn't found any archive containing the source so I have buid a simple test using EJB 3 (In fact, I have created a "hello word" session bean that return a String containing the Dom builder factory class name).
I have create the shared library using Entreprise manager as described in the how to.
My test works fine if I deploy it with the default XML factory but if I add the following lines to the orion-application.xml, the deployment process ends with a null pointer exception :
<imported-shared-libraries>
<import-shared-library name="apache.xml" />
<remove-inherited name="oracle.xml" />
</imported-shared-libraries>
I have tried to deploy the test using the entreprise manager web UI (as explain in how to) but the result was the same.
I have tried to remove the "<remove-inherited name="oracle.xml" />" line but in this case, the XML parser still the oracle one.
Do you know if the library specification is available in the last soa suite ?
Thank in advance for your responses.
Alexandre CUCUMEL
PS: I can send the test code source if needed
PS2: here is the complete opmn stack trace when I try to deploy the test application
08/08/08 15:46:36 java.lang.RuntimeException: javax.xml.parsers.FactoryConfigurationError: Provider oracle.xml.jaxp.JXDocumentBuilderFactory could not
be instantiated: java.lang.NullPointerException
08/08/08 15:46:36 at oracle.j2ee.ws.common.processor.Processor.runActions(Processor.java:105)
08/08/08 15:46:36 at oracle.j2ee.ws.common.metadata.annotation.DeploymentGenerator$DeploymentCompileTool.run(DeploymentGenerator.java:205)
08/08/08 15:46:36 at oracle.j2ee.ws.common.metadata.annotation.DeploymentGenerator.generateDeploymentArtifacts(DeploymentGenerator.java:131)
08/08/08 15:46:36 at oracle.j2ee.ws.common.metadata.annotation.EJBWebServiceAnnotationParser.parseAnnotatedBean(EJBWebServiceAnnotationParser.ja
va:165)
08/08/08 15:46:36 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
08/08/08 15:46:36 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
08/08/08 15:46:36 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
08/08/08 15:46:36 at java.lang.reflect.Method.invoke(Method.java:585)
08/08/08 15:46:36 at oracle.j2ee.ws.server.deployment.oc4j.WebServiceAnnotationListener.parseAnnotatedClass(WebServiceAnnotationListener.java:85
08/08/08 15:46:36 at com.evermind.server.ejb.AnnotationParser.notifyAnnotationListeners(AnnotationParser.java:201)
08/08/08 15:46:36 at com.evermind.server.ejb.AnnotationParser.parseAnnotations(AnnotationParser.java:73)
08/08/08 15:46:36 at com.evermind.server.ejb.EJBPackageDeployment.parseMetaData(EJBPackageDeployment.java:939)
08/08/08 15:46:36 at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:832)
08/08/08 15:46:36 at com.evermind.server.ApplicationStateRunning.initializeApplication(ApplicationStateRunning.java:217)
08/08/08 15:46:36 at com.evermind.server.Application.setConfig(Application.java:413)
08/08/08 15:46:36 at com.evermind.server.Application.setConfig(Application.java:314)
08/08/08 15:46:36 at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1853)
08/08/08 15:46:36 at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(ApplicationDeployer.java:512)
08/08/08 15:46:36 at oracle.oc4j.admin.internal.ApplicationDeployer.doDeploy(ApplicationDeployer.java:196)
08/08/08 15:46:36 at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:93)
08/08/08 15:46:36 at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeployerRunnable.doRun(OC4JDeployerRunnable.java:52)
08/08/08 15:46:36 at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRunnable.run(DeployerRunnable.java:81)
08/08/08 15:46:36 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
08/08/08 15:46:36 at java.lang.Thread.run(Thread.java:595)
08/08/08 15:46:36 Caused by: javax.xml.parsers.FactoryConfigurationError: Provider oracle.xml.jaxp.JXDocumentBuilderFactory could not be instantiated:
java.lang.NullPointerException
08/08/08 15:46:36 at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:104)
08/08/08 15:46:36 at oracle.j2ee.ws.wsdl.extensions.oracle.schema.SchemaSchemaElement.<init>(SchemaSchemaElement.java:37)
08/08/08 15:46:36 at oracle.j2ee.ws.common.processor.generator.wsdl.WSDLTypeGenerator.generateSchema(WSDLTypeGenerator.java:435)
08/08/08 15:46:36 at oracle.j2ee.ws.common.processor.generator.wsdl.WSDLTypeGenerator.processElement(WSDLTypeGenerator.java:735)
08/08/08 15:46:36 at oracle.j2ee.ws.common.processor.generator.wsdl.WSDLTypeGenerator.processElementsInMessage(WSDLTypeGenerator.java:352)
08/08/08 15:46:36 at oracle.j2ee.ws.common.processor.generator.wsdl.WSDLTypeGenerator.run(WSDLTypeGenerator.java:207)
08/08/08 15:46:36 at oracle.j2ee.ws.common.processor.generator.wsdl.WSDLGenerator.generateTypes(WSDLGenerator.java:291)
08/08/08 15:46:36 at oracle.j2ee.ws.common.processor.generator.wsdl.WSDLGenerator.generateDocument(WSDLGenerator.java:242)
08/08/08 15:46:36 at oracle.j2ee.ws.common.processor.generator.wsdl.WSDLGenerator.doGeneration(WSDLGenerator.java:176)
08/08/08 15:46:36 at oracle.j2ee.ws.common.processor.generator.wsdl.WSDLGenerator.doGeneration(WSDLGenerator.java:141)
08/08/08 15:46:36 at oracle.j2ee.ws.common.processor.generator.wsdl.WSDLGenerator.perform(WSDLGenerator.java:126)
08/08/08 15:46:36 at oracle.j2ee.ws.common.processor.Processor.runActions(Processor.java:97)
08/08/08 15:46:36 ... 23 more
08/08/08 15:46:36 WARNING: Application.setConfig Application: testDeployement is in failed state as initialization failed.
java.lang.InstantiationException: Error initializing ejb-modules: nested exception is: java.lang.NullPointerException
08/08/08 15:46:36 oracle.oc4j.admin.internal.DeployerException: java.lang.InstantiationException: Application: testDeployement is in failed state as i
nitialization failed
08/08/08 15:46:36 at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(ApplicationDeployer.java:515)
08/08/08 15:46:36 at oracle.oc4j.admin.internal.ApplicationDeployer.doDeploy(ApplicationDeployer.java:196)
08/08/08 15:46:36 at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:93)
08/08/08 15:46:36 at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeployerRunnable.doRun(OC4JDeployerRunnable.java:52)
08/08/08 15:46:36 at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRunnable.run(DeployerRunnable.java:81)
08/08/08 15:46:36 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
08/08/08 15:46:36 at java.lang.Thread.run(Thread.java:595)
08/08/08 15:46:36 Caused by: java.lang.InstantiationException: Application: testDeployement is in failed state as initialization failed
08/08/08 15:46:36 at com.evermind.server.Application.setConfig(Application.java:471)
08/08/08 15:46:36 at com.evermind.server.Application.setConfig(Application.java:314)
08/08/08 15:46:36 at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1853)
08/08/08 15:46:36 at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(ApplicationDeployer.java:512)
08/08/08 15:46:36 ... 6 more
08/08/08 15:46:36 Caused by: java.lang.InstantiationException: Error initializing ejb-modules: nested exception is: java.lang.NullPointerException
08/08/08 15:46:36 at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:1064)
08/08/08 15:46:36 at com.evermind.server.ApplicationStateRunning.initializeApplication(ApplicationStateRunning.java:217)
08/08/08 15:46:36 at com.evermind.server.Application.setConfig(Application.java:413)
08/08/08 15:46:36 ... 9 more
08/08/08 15:46:36 Caused by: javax.ejb.EJBException: nested exception is: java.lang.NullPointerException
08/08/08 15:46:36 at com.evermind.server.ejb.EJBUtils.createEJBException(EJBUtils.java:365)
08/08/08 15:46:36 at com.evermind.server.ejb.EJBUtils.createEJBException(EJBUtils.java:356)
08/08/08 15:46:36 at oracle.j2ee.ws.server.deployment.oc4j.WebServiceAnnotationListener.parseAnnotatedClass(WebServiceAnnotationListener.java:92
08/08/08 15:46:36 at com.evermind.server.ejb.AnnotationParser.notifyAnnotationListeners(AnnotationParser.java:201)
08/08/08 15:46:36 at com.evermind.server.ejb.AnnotationParser.parseAnnotations(AnnotationParser.java:73)
08/08/08 15:46:36 at com.evermind.server.ejb.EJBPackageDeployment.parseMetaData(EJBPackageDeployment.java:939)
08/08/08 15:46:36 at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:832)
08/08/08 15:46:36 ... 11 more
08/08/08 15:46:36 Caused by: java.lang.NullPointerException
08/08/08 15:46:36 at oracle.j2ee.ws.common.metadata.annotation.DeploymentGenerator.generateDeploymentArtifacts(DeploymentGenerator.java:138)
08/08/08 15:46:36 at oracle.j2ee.ws.common.metadata.annotation.EJBWebServiceAnnotationParser.parseAnnotatedBean(EJBWebServiceAnnotationParser.ja
va:165)
08/08/08 15:46:36 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
08/08/08 15:46:36 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
08/08/08 15:46:36 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
08/08/08 15:46:36 at java.lang.reflect.Method.invoke(Method.java:585)
08/08/08 15:46:36 at oracle.j2ee.ws.server.deployment.oc4j.WebServiceAnnotationListener.parseAnnotatedClass(WebServiceAnnotationListener.java:85
08/08/08 15:46:36 ... 15 more
08/08/08 15:46:36 WARNING: DeployerRunnable.run java.lang.InstantiationException: Application: testDeployement is in failed state as initialization fa
iledoracle.oc4j.admin.internal.DeployerException: java.lang.InstantiationException: Application: testDeployement is in failed state as initialization
failed
at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:126)
at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeployerRunnable.doRun(OC4JDeployerRunnable.java:52)
at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRunnable.run(DeployerRunnable.java:81)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.InstantiationException: Application: testDeployement is in failed state as initialization failed
at com.evermind.server.Application.setConfig(Application.java:471)
at com.evermind.server.Application.setConfig(Application.java:314)
at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1853)
at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(ApplicationDeployer.java:512)
at oracle.oc4j.admin.internal.ApplicationDeployer.doDeploy(ApplicationDeployer.java:196)
at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:93)
... 4 more
Caused by: java.lang.InstantiationException: Error initializing ejb-modules: nested exception is: java.lang.NullPointerException
at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:1064)
at com.evermind.server.ApplicationStateRunning.initializeApplication(ApplicationStateRunning.java:217)
at com.evermind.server.Application.setConfig(Application.java:413)
... 9 more
Caused by: javax.ejb.EJBException: nested exception is: java.lang.NullPointerException
at com.evermind.server.ejb.EJBUtils.createEJBException(EJBUtils.java:365)
at com.evermind.server.ejb.EJBUtils.createEJBException(EJBUtils.java:356)
at oracle.j2ee.ws.server.deployment.oc4j.WebServiceAnnotationListener.parseAnnotatedClass(WebServiceAnnotationListener.java:92)
at com.evermind.server.ejb.AnnotationParser.notifyAnnotationListeners(AnnotationParser.java:201)
at com.evermind.server.ejb.AnnotationParser.parseAnnotations(AnnotationParser.java:73)
at com.evermind.server.ejb.EJBPackageDeployment.parseMetaData(EJBPackageDeployment.java:939)
at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:832)
... 11 more
Caused by: java.lang.NullPointerException
at oracle.j2ee.ws.common.metadata.annotation.DeploymentGenerator.generateDeploymentArtifacts(DeploymentGenerator.java:138)
at oracle.j2ee.ws.common.metadata.annotation.EJBWebServiceAnnotationParser.parseAnnotatedBean(EJBWebServiceAnnotationParser.java:165)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at oracle.j2ee.ws.server.deployment.oc4j.WebServiceAnnotationListener.parseAnnotatedClass(WebServiceAnnotationListener.java:85)
... 15 more

Andre,
Thanks for your interest on my problem.
In fact, I have created a test with just an interface and a class. No additional jars are added at compilation or ejb creation time.
My java code is very simple (I have just copied the example main method and convert it to a SOAP method :
package be.test;
import javax.ejb.Stateless;
import javax.jws.WebService;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
@Stateless
@WebService(endpointInterface = "be.test.Test")
public class TestImpl implements Test {
 public String test() {
 DocumentBuilder builder=null;
 DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
 try
 builder = factory.newDocumentBuilder();
 return " DocumentBuilderFactory Instance: " + factory.getClass().getName() +
 " DocumentBuilder Instance: " + builder.getClass().getName() +" "; }
 catch (Exception e)
 return "Error processing DOM -- " + e.getMessage();
Unfortunately, I think that the problem may come from EJB 3 stack that does not support an other XML library.
Thanks again for your help.
Best regards,
Alexandre
PS: appologies for the message formatting... I don't understand why the new line caracters are not corrects.

XML Parser Problem

am using XML parser for PL/SQL in Oracle9i Enterprise Edition Release 9.0.1.1.1
When i run the sample xml program, i get error which is as follows. While compiling no errors. But while executing it reports error as given below.
SQL> execute domsample('c:\xml', 'family.xml', 'errors.txt');
begin domsample('c:\xml', 'family.xml', 'errors.txt'); end;
ORA-20100: Error occurred while parsing: No such file or directory
ORA-06512: at "COMMODITYBACKCONNECT.XMLPARSER", line 22
ORA-06512: at "COMMODITYBACKCONNECT.XMLPARSER", line 79
ORA-06512: at "COMMODITYBACKCONNECT.DOMSAMPLE", line 80
ORA-06512: at line 1
What need to be done to rectify the above problem.
when i do the following validation check
SQL>
SQL> select substr(dbms_java.longname(object_name),1,30) as class, status
2 from all_objects
3 where object_type = 'JAVA CLASS'
4 and object_name = dbms_java.shortname('oracle/xml/parser/v2/DOMParser')
5 ;
CLASS STATUS
oracle/xml/parser/v2/DOMParser VALID
oracle/xml/parser/v2/DOMParser VALID
Please advice to how remove the following error:
ORA-20100: Error occurred while parsing: No such file or directory

Found the solution on metalink. There is a file under /$ORACLE_HOME/javavm/install/init_security.sql
which needs to be run under username where you are installing xml parser.
This step is not in readme.txt file provided as a part of download from the OTN website.

Error in parsing: SAX2 driver class com.sun.xml.parser not found

Hi I have this exception
Error in parsing: SAX2 driver class com.sun.xml.parser not found
when I try to run the examples from the book xml and java
I have added the following jar files to the class path that i have download form java.sun.com
xml.jar
xalan.jar
jaxp.jar
crimson.jar
Please can anyone tell me what is missing or wrong..the code must be right since written by oreilly... please have u any ideA
XMLReaderFactory.createXMLReader(
// "org.apache.xerces.parsers.SAXParser");
"com.sun.xml.parser");//
I HAVE ONLY CHANGED THIS LINE FROM THE apache parser..to com.sun.xml.parser
THIS IS THE ALL CODE
import java.io.IOException;
import org.xml.sax.Attributes;
import org.xml.sax.ContentHandler;
import org.xml.sax.ErrorHandler;
import org.xml.sax.Locator;
import org.xml.sax.SAXException;
import org.xml.sax.SAXParseException;
import org.xml.sax.XMLReader;
import org.xml.sax.helpers.XMLReaderFactory;
import org.xml.sax.*;
* <code>SAXParserDemo</code> will take an XML file and parse it using SAX,
* displaying the callbacks in the parsing lifecycle.
* @author Brett McLaughlin
* @version 1.0
public class SAXParserDemo {
* 
* This parses the file, using registered SAX handlers, and output
* the events in the parsing process cycle.
* 
* @param uri <code>String</code> URI of file to parse.
public void performDemo(String uri) {
System.out.println("Parsing XML File: " + uri + "\n\n");
// Get instances of our handlers
ContentHandler contentHandler = new MyContentHandler();
ErrorHandler errorHandler = new MyErrorHandler();
try {
// Instantiate a parser
XMLReader parser =
XMLReaderFactory.createXMLReader(
// "org.apache.xerces.parsers.SAXParser");
"com.sun.xml.parser");// I HAVE ONLY CHANGED THIS LINE FROM THE apache parser..
// Register the content handler
parser.setContentHandler(contentHandler);
// Register the error handler
parser.setErrorHandler(errorHandler);
// Parse the document
parser.parse(uri);
} catch (IOException e) {
System.out.println("Error reading URI: " + e.getMessage());
} catch (SAXException e) {
System.out.println("Error in parsing: " + e.getMessage());
* 
* This provides a command line entry point for this demo.
* 
public static void main(String[] args) {
// if (args.length != 1) {
// System.out.println("Usage: java SAXParserDemo [XML URI]");
// System.exit(0);
//String uri = args[0];
SAXParserDemo parserDemo = new SAXParserDemo();
parserDemo.performDemo("content.xml");
* <code>MyContentHandler</code> implements the SAX
* <code>ContentHandler</code> interface and defines callback
* behavior for the SAX callbacks associated with an XML
* document's content.
class MyContentHandler implements ContentHandler {
/** Hold onto the locator for location information */
private Locator locator;
* 
* Provide reference to <code>Locator</code> which provides
* information about where in a document callbacks occur.
* 
* @param locator <code>Locator</code> object tied to callback
* process
public void setDocumentLocator(Locator locator) {
System.out.println(" * setDocumentLocator() called");
// We save this for later use if desired.
this.locator = locator;
* 
* This indicates the start of a Document parse - this precedes
* all callbacks in all SAX Handlers with the sole exception
* of <code>{@link #setDocumentLocator}</code>.
* 
* @throws <code>SAXException</code> when things go wrong
public void startDocument() throws SAXException {
System.out.println("Parsing begins...");
* 
* This indicates the end of a Document parse - this occurs after
* all callbacks in all SAX Handlers.</code>.
* 
* @throws <code>SAXException</code> when things go wrong
public void endDocument() throws SAXException {
System.out.println("...Parsing ends.");
* 
* This will indicate that a processing instruction (other than
* the XML declaration) has been encountered.
* 
* @param target <code>String</code> target of PI
* @param data <code>String</code containing all data sent to the PI.
* This typically looks like one or more attribute value
* pairs.
* @throws <code>SAXException</code> when things go wrong
public void processingInstruction(String target, String data)
throws SAXException {
System.out.println("PI: Target:" + target + " and Data:" + data);
* 
* This will indicate the beginning of an XML Namespace prefix
* mapping. Although this typically occur within the root element
* of an XML document, it can occur at any point within the
* document. Note that a prefix mapping on an element triggers
* this callback before the callback for the actual element
* itself (<code>{@link #startElement}</code>) occurs.
* 
* @param prefix <code>String</code> prefix used for the namespace
* being reported
* @param uri <code>String</code> URI for the namespace
* being reported
* @throws <code>SAXException</code> when things go wrong
public void startPrefixMapping(String prefix, String uri) {
System.out.println("Mapping starts for prefix " + prefix +
" mapped to URI " + uri);
* 
* This indicates the end of a prefix mapping, when the namespace
* reported in a <code>{@link #startPrefixMapping}</code> callback
* is no longer available.
* 
* @param prefix <code>String</code> of namespace being reported
* @throws <code>SAXException</code> when things go wrong
public void endPrefixMapping(String prefix) {
System.out.println("Mapping ends for prefix " + prefix);
* 
* This reports the occurrence of an actual element. It will include
* the element's attributes, with the exception of XML vocabulary
* specific attributes, such as
* <code>xmlns:[namespace prefix]</code> and
* <code>xsi:schemaLocation</code>.
* 
* @param namespaceURI <code>String</code> namespace URI this element
* is associated with, or an empty
* <code>String</code>
* @param localName <code>String</code> name of element (with no
* namespace prefix, if one is present)
* @param rawName <code>String</code> XML 1.0 version of element name:
* [namespace prefix]:[localName]
* @param atts <code>Attributes</code> list for this element
* @throws <code>SAXException</code> when things go wrong
public void startElement(String namespaceURI, String localName,
String rawName, Attributes atts)
throws SAXException {
System.out.print("startElement: " + localName);
if (!namespaceURI.equals("")) {
System.out.println(" in namespace " + namespaceURI +
" (" + rawName + ")");
} else {
System.out.println(" has no associated namespace");
for (int i=0; i<atts.getLength(); i++)
System.out.println(" Attribute: " + atts.getLocalName(i) +
"=" + atts.getValue(i));
* 
* Indicates the end of an element
* (<code></[element name]></code>) is reached. Note that
* the parser does not distinguish between empty
* elements and non-empty elements, so this will occur uniformly.
* 
* @param namespaceURI <code>String</code> URI of namespace this
* element is associated with
* @param localName <code>String</code> name of element without prefix
* @param rawName <code>String</code> name of element in XML 1.0 form
* @throws <code>SAXException</code> when things go wrong
public void endElement(String namespaceURI, String localName,
String rawName)
throws SAXException {
System.out.println("endElement: " + localName + "\n");
* 
* This will report character data (within an element).
* 
* @param ch <code>char[]</code> character array with character data
* @param start <code>int</code> index in array where data starts.
* @param end <code>int</code> index in array where data ends.
* @throws <code>SAXException</code> when things go wrong
public void characters(char[] ch, int start, int end)
throws SAXException {
String s = new String(ch, start, end);
System.out.println("characters: " + s);
* 
* This will report whitespace that can be ignored in the
* originating document. This is typically only invoked when
* validation is ocurring in the parsing process.
* 
* @param ch <code>char[]</code> character array with character data
* @param start <code>int</code> index in array where data starts.
* @param end <code>int</code> index in array where data ends.
* @throws <code>SAXException</code> when things go wrong
public void ignorableWhitespace(char[] ch, int start, int end)
throws SAXException {
String s = new String(ch, start, end);
System.out.println("ignorableWhitespace: [" + s + "]");
* 
* This will report an entity that is skipped by the parser. This
* should only occur for non-validating parsers, and then is still
* implementation-dependent behavior.
* 
* @param name <code>String</code> name of entity being skipped
* @throws <code>SAXException</code> when things go wrong
public void skippedEntity(String name) throws SAXException {
System.out.println("Skipping entity " + name);
* <code>MyErrorHandler</code> implements the SAX
* <code>ErrorHandler</code> interface and defines callback
* behavior for the SAX callbacks associated with an XML
* document's errors.
class MyErrorHandler implements ErrorHandler {
* 
* This will report a warning that has occurred; this indicates
* that while no XML rules were "broken", something appears
* to be incorrect or missing.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void warning(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Warning**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Warning encountered");
* 
* This will report an error that has occurred; this indicates
* that a rule was broken, typically in validation, but that
* parsing can reasonably continue.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void error(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Error**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Error encountered");
* 
* This will report a fatal error that has occurred; this indicates
* that a rule has been broken that makes continued parsing either
* impossible or an almost certain waste of time.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void fatalError(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Fatal Error**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Fatal Error encountered");

I have seen this error when I'm executing inside one of the (j2ee sun reference implementation) server containers (either web or ejb). I believe its caused by "something" having previously loaded the "sax 1 driver class". In my case, I think the container or server is loading the sax parser from a jar that contains a sax 1 version. If you can, ensure that nothing is loading the sax 1 parser from another jar on your system. Verify that you are loading the sax parser from a jar containing the latest version so that you get the sax 2 compliant parser. Good luck!

Still problems serializing xml-docs with xml-parser for java v2.0.2.7

Hi !
I'm using the Oracle XML Parser 2.0.2.7.0 and get some problems when serializing the XMLDocument.
In one class (DOMOut) I parse a xml-file with the oracle.xml.parser.v2.DOMParser, then obtain the XMLDocument and write it to System.out
In another class (DOMIn) I fetch the XMLDocument from System.in, search for a given Element and print it's TextValue (if existing) to System.out
That is where the error occurs.
I get the XMLDocument from System.in but the returning NodeList from doc.getElementsByTagName() is empty. [nl.getLength()==0] even if it shouldn't be.
Look at this code and output:
[DOMOut]
DOMParser parser = new DOMParser();
parser.parse(url);
XMLDocument doc = (XMLDocument)parser.getDocument();
ObjectOutputStream out = new ObjectOutputStream(System.out);
out.writeObject(doc); out.flush();
[DOMIn]
ObjectInputStream in = new ObjectInputStream(System.in);
XMLDocument doc = (XMLDocument)in.readObject();
doc.print(System.out);
NodeList nl = doc.getElementsByTagName("Name");
System.out.println("Length of NodeList: "+nl.getLength());
if (nl.getLength()==0)
System.out.println(argv[0] + ": not in this document!");
else {
XMLNode node = (XMLNode) nl.item(nl.getLength()-1);
System.out.println(node.getNodeName() + ": " + (node.getFirstChild()).getNodeValue());
This is the relevant code.
I javac both classes and then do this:
java DOMOut xmltestfile.xml > xx
java DOMIn Name < xx
And get this as output:
<?xml version = '1.0'?>
<!DOCTYPE course [
<!ELEMENT course (Name,Dept,Instructor,Student)>
<!ELEMENT Name ((#PCDATA)*)*>
<!ELEMENT Dept ((#PCDATA)*)*>
<!ELEMENT Instructor (Name)>
<!ELEMENT Student (Name)*>
]>
<course>
<Name>Calculus</Name>
<Dept>Math</Dept>
<Instructor>
<Name>Jim Green</Name>
</Instructor>
<Student>
<Name>Jack</Name>
<Name>Mary</Name>
<Name>Paul</Name>
</Student>
</course>
Length of NodeList: 0
Name: not in this document!
Has anyone an idea?
If I do all this stuff without serializing it works.
If I do not search for argv[0], but the string "Name" it fails.
If I do search for "*" it works fine!
I'm very confused could anybody please help me a bit??
Stefan.
[[email protected]]

The link has been fixed. You will go to the v2 download page
now. Sorry for the inconvience.
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
Renilton Oliveira (guest) wrote:
: I didn't find the file for version 2.0.0.0 as well.
: Renilton
: Andrei Filimonov (guest) wrote:
: : I tried to download XML Parser for Java v2 it seems that
only
: v
: : 1.0.1.4 is available. Could you please give an exact URL for
: v2
: : download?
: : Andrei Filimonov
: : Oracle XML Team wrote:
: : : The Oracle XML v2 parser is now available for download
here
: as
: : : an early beta release and is written in Java. It features
: an
: : : improved architecture over the Oracle XML v1 parser and
has
: : : shown better performance on small to large XML documents.
: It
: : : will also be able to format the XML document according to
a
: : : stylesheet, having integrated an XSLT processor.
: : : Version 2 of the XML Parser for Java, besides
incorporating
: an
: : : XSLT processor, has been re-architected from version 1.
This
: : has
: : : resulted in a number of changes to the class names
: especially
: : : those that support Namespaces. See v2changes.txt and
: the .diff
: : : difference files in the sample directory.
: : : Oracle XML Team
: : : http://technet.oracle.com
: : : Oracle Technology Network
null

XML Parser, Class Generator demo problem

Similar Messages

Maybe you are looking for