Xdk and xml parser[JAVA]

Hi !
I have been trying to compile the example about the XML class Generator but everytime I get the following error:
SampleMain.java:61: Incompatible type for method. Can't convert oracle.xml.parse
r.DTD to oracle.xml.parser.v2.DTD.
generator.generate(dtd, doctype_name);
^
The problem is that I can't find the appropriate XML parser Library.
My question is Which JAR file is it ?
Or which version ?
Thanx for any help!

Please use xmlparserv2.jar

Similar Messages

XDK for PL/SQL and XML Parser for PL/SQL

Is there a difference between the terms:
XDK for PL/SQL
and
XML Parser for PL/SQL V2
or are they the same thing...?
cheers,

XDK stands for XML Developer's Kit. There are Oracle XDKs for Java, C, C++, and PL/SQL. These development kits contain building blocks for reading, manipulating, transforming, and viewing XML documents.
XML Parser is one component of XDK. Other components of XDK are
XSLT Processor, XSU, XSQL Servlet, XML Class Generator, etc.
For more information on XDK and its components please refer to:
http://otn.oracle.com/docs/products/oracle9i/doc_library/release2/appdev.920/a96621/adx01bas.htm#1656
Regards,
Anupama
http://otn.oracle.com/sample_code/content.html

Java and XML Parser. Please guide.

Hello there,
I need to pass an XML document using the SAX Parser.
Please does any one have an XML Parser routine to parse
the document or can some one guide me as to what to do?

any sax parsers?What version of Java are you using? With Java 1.4 the XML parser is included in the SDK / JRE.
If you're using an older version of Java, go to http://xml.apache.org and get the Xerces parser.

Abstract Method Error and XML Parsing

I am using wl6sp1. I am parsing an XML file from within the
servlet using jaxp1.1 and crimson.
Following is code:
1- SAXParserFactory spf = SAXParserFactory.newInstance();
2- sp = spf.newSAXParser();
3- xr = sp.getXMLReader();
4- xr.setContentHandler(new ParseXML());
5- xr.parse( new InputSource("Example3.xml"));
This program works fine when execute from command line but in servlet on line
3 it says:
"Abstract Method Error"
I have created XML Registry to use Crimson as XML parser rather than default.
I think somehow wl is still using jaxp1.0 which is built in
support in wlsp1.
Whats wrong with the code...or what configuration i am missing???

I'm assuming you have already put crimson.jar first in the classpath for the java
command you use to start WebLogic. If so, have you tried putting the servlet in
a .war file with the crimson.jar in its' WEB-INF/lib directory?
Regards,
Mike Wooten
"anyz" <[email protected]> wrote:
>
I am using wl6sp1. I am parsing an XML file from within the
servlet using jaxp1.1 and crimson.
Following is code:
1- SAXParserFactory spf = SAXParserFactory.newInstance();
2- sp = spf.newSAXParser();
3- xr = sp.getXMLReader();
4- xr.setContentHandler(new ParseXML());
5- xr.parse( new InputSource("Example3.xml"));
This program works fine when execute from command line but in servlet
on line
3 it says:
"Abstract Method Error"
I have created XML Registry to use Crimson as XML parser rather than
default.
I think somehow wl is still using jaxp1.0 which is built in
support in wlsp1.
Whats wrong with the code...or what configuration i am missing???

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

_03 runtime env and XML parsing in applet

Hi all,
weird and annoying problem with an applet set up to read an XML file on the same server to create graph. Recently graduated to runtime 1_4_03 from 1_4_02. No issues at all reading the file with _02 but getting permission denied with _03.
Tracked it down to lines below. There seems to now be a security violation reading the contents of the XML file. Both as I said are sitting in the same dir on the server. Has anyone else had this happen and if so did any solutions come to mind?
URL u = new URL(getCodeBase(), XMLDOC);
String us = url.toString();
saxParser.parse(urlString, parser);
Thanks, Mike

This is the error that is being returned
Exception in init parser: java.security.AccessControlException: access denied (java.util.PropertyPermission entityExpansionLimit read)
hmm?

Oracle and XML Parser

Hi friends
I'm trying to load xmlparserv2.jar into the database using loadjava..it is creating and loading the classes successfully but while resolving it's giving an error i.e. referenced object SCOTT.oracle/xml/parser/v2/<ClassName> could not be resolved..
When i tried to resolve the class using the Alter Java Class command it's resolving..but while using the class in a program...at the time of compilation it shows The class is not resolved..
Please Help...If there is any other way to resolve a class...or to load a parser in to the database..
Thanks

What are the specific ORA-XXX error messages you're getting?

Weblogic 6.1 and xml parser empty elements

FYI, It looks like Weblogic changed there xml parser in the transition from
6.0sp2 to 6.1. Example : The empty Extra Info Class produced and error,
because it is empty. Where in 6.0sp2 it did not produce and error:
<taglib>
<tag>
<name>indexProperty</name>
<info>
some info..
</info>
<tagclass>com.pssg.jsp.tags.IndexPropertyTag</tagclass>
<teiclass></teiclass>
</tag>
</taglib>
####<Aug 20, 2001 12:20:52 PM PDT> <Info> <HTTP> <devlwebejb1> <camserver>
<ExecuteThread: '14' for queue: 'default'> <> <> <101047>
<[WebAppServletContext(7008653,cam,/cam)] resolved taglib uri '/pssglibtags'
to taglib-location /WEB-INF/tlds/pssgtaglib.tld:>
####<Aug 20, 2001 12:20:53 PM PDT> <Info> <HTTP> <devlwebejb1> <camserver>
<ExecuteThread: '14' for queue: 'default'> <> <> <101160> <Deployment
descriptor is malformed, check against the DTD:
org.xml.sax.SAXParseException: The content of element type "tag" must match
"(name,tagclass,teiclass?,bodycontent?,info?,attribute*)"..>
####<Aug 20, 2001 12:20:53 PM PDT> <Error> <HTTP> <devlwebejb1> <camserver>
<ExecuteThread: '14' for queue: 'default'> <> <> <101020>
<[WebAppServletContext(7008653,cam,/cam)] Servlet failed with Exception>
weblogic.servlet.jsp.JspException: (line 1): Error in using tag library
uri='/pssglibtags' prefix='pssglibtag': For tag 'indexProperty', cannot load
extra info class ''
at
weblogic.servlet.jsp.StandardTagLib.tld_jspException(StandardTagLib.java:901
-Scot

hi,
there are two versions of ldap supported in wls6.1 , ldapv1 and ldavp2
ldap v1 only has the functionality of listing groups.
but where ldapv2 doesn't have that functionality,
by looking at your config , it seems you are using ldap v2..
if u need that functionality u can use ldapv1.
thanks
kiran
"Bert Cliche" <[email protected]> wrote in message
news:[email protected]..
Per a proof of concept, I am having trouble getting WL6.1 to see
group members as defined in iPlanet LDAP. I can see the groups,
but modifies to create groups only create them in the local DB.
Created users also only get placed in the local DB. I can bind
for searches as Directory Manager via ldapsearch and run queries,
and the DS gateway works fine. I can dump the LDIF file and the
entries look fine.
I copied and modified the template for the Netscape server and
have the realm setup per the GUI.
For sanity, everything is very generic as:
the Root DN is "o=test.org"
and my "Configuration" part from the config.xml looks like:
server.authprotocol=simple;
server.host=localhost;
membership.filter=(&(uniquemember=%M)(objectclass=groupofuniquenames));
server.port=390;
group.dn=o=test.org;
group.filter=(&(cn=%g)(objectclass=groupofuniquenames));
server.principal=cn=Directory Manager;
user.dn=o=test.org;
server.groupiscontext=false;
user.filter=(&(uid=%u))
I added the "authprotocol" as a guess. Note that the server is
running on port 390, this is not a typo.
Any ideas what is going wrong?

Oracle8.1.5 and XML parser for PL/SQL

Hi,
Does XML parser for PL/SQL work with Oracle 8.1.5? Did any one install the
same and if so what are steps to follow? I ran initjvm.sql to install
JServer and then tried to load jar files using loadjava, but it's giving
error. It's working fine with Oracle8.1.6.
Any idea?
Thanks,
Jayanta
null

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Jayanta Ghosh ([email protected]):
Hi,
Does XML parser for PL/SQL work with Oracle 8.1.5? Did any one install the
same and if so what are steps to follow? I ran initjvm.sql to install
JServer and then tried to load jar files using loadjava, but it's giving
error. It's working fine with Oracle8.1.6.
Any idea?
Thanks,
Jayanta<HR></BLOCKQUOTE>
Oracle XML Parser has differents distributions for 8.1.5 and 8.1.6 databases, try the correct version, then runs the oraclexmlsqlload.csh from the lib directory of XSU distribution.
Best regards, Marcelo.
null

Xsl processor and xml parser?

Hello,
Can someone tell me wich is the xsl processor and the xml parser used by Livecycle ES? And their versions?
Thank you

XML Parser parses the text representation of an XML 1.0-compliant document to make the document's information set -- elements, attributes, text, comments, processing instructions, namespace declarations -- available for access to a comptuter program.
Without a parser, a program cannot make heads or tails of the tree of information contained in your tags.
An XSL Processor is a program that takes an XML Document as input, along with an XSLT transformation definition (also known as a stylesheet), and effects the transformation of the source document as instructed by the stylesheet. This might mean transforming:
<ROWSET>
<ROW>
<ENAME>Steve</ENAME>
</ROW>
</ROWSET>
into
<human-resources>
<employee name="Steve"/>
</human-resources>
or alternatively into:
<html>
<body>
<b>Steve</b>
</body>
</html>
In both cases, the source XML document
is the same, but when transformed by
one stylesheet, it might become
the <human-resources> XML document.
When transformed by another stylesheet,
it can become pretty HTML.
To put the two terms in context, an XSL processor uses an XML parser to read the source XML document and to read the XSL transformation definition (aka stylesheet) -- since it, too, is an XML document -- and then it proceeds to transform the source into the target.

XDK and XML Schema

Hello All!
I am using standalone Oracle XDK for C 9.2.0.2.0 on Windows NT 4.0. The fragment of my XML schema is shown below:
<xsd:simpleType name="Text30">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="30"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="CCode">
<xsd:restriction base="xsd:string">
<xsd:pattern value="\d{5}|\d{8}|\d{12}"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="ReferenceNo">
<xsd:simpleContent>
<xsd:extension base="Text30">
<xsd:attribute name="cCode" type="CCode" use="required"/>
<xsd:attribute name="docDate" type="xsd:date" use="required"/>
<xsd:attribute name="TIRPageNo" type="TIRGreenPageNo" use="optional"/>
<xsd:attributeGroup ref="DeclarType"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
And the part of the instance document looks like:
<DocNo cCode="10501000 ... />, where "DocNo" is of type "ReferenceNo".
Then validating my XML document I am always getting error that my "cCode" attribute doesn't match
pattern. After removing <xsd:pattern value="\d{5}|\d{8}|\d{12}"/> from schema all seems to be OK.
Why? Where is the error? "\d{5}|\d{8}|\d{12}" is a valid regexp according the W3C XML Schema specification.
Any help will be appreciated. Thanks.
Egor Pervouninski
[email protected]

Hello All!
I have localized the problem. Seems to be a bug in XDK for C/C++ 9_2_0_2_0 (and for Java too)!
Create three files:
--- error.xsd ---
<?xml version="1.0" encoding="Windows-1251"?>
<xsd:schema targetNamespace="urn:xdk:error" xmlns="urn:xdk:error" xmlns:xsd="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xsd:simpleType name="Code">
<xsd:restriction base="xsd:string">
<xsd:pattern value="\d{1}|\d{2}|\d{3}"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="Root">
<xsd:attribute name="code" type="Code"/>
</xsd:complexType>
<xsd:element name="root" type="Root"/>
</xsd:schema>
--- error.xsd ---
-- error1.xml ---
<?xml version="1.0" encoding="Windows-1251"?>
<root xmlns="urn:xdk:error" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:xdk:error
error.xsd" code="1"/>
--- error1.xml ---
--- error2.xml ---
<?xml version="1.0" encoding="Windows-1251"?>
<root xmlns="urn:xdk:error" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:xdk:error
error.xsd" code="12"/>
--- error2.xml ---
Execute: schema.exe error1.xml error.xsd (Java: oraxml.bat -schema error1.xml)
All OK!
Execute: schema.exe error2.xml error.xsd (Java: oraxml.bat -schema error2.xml)
In line 3 of error2.xml:
LSX-00333: literal "12" is not valid with respect to the pattern
I have tested the same examples with XML Spy 4.4, MSXML 4.0 and Xerces-C 1.7.0.
All parsers have validated this examples without any errors... except XDK.
Egor Pervouninski
[email protected]

Xml parsing java

i am reading one xml doc in java
DocumentBuilderFactory docBuilderFactory =DocumentBuilderFactory.newInstance();
   DocumentBuilder docBuilder = docBuilderFactory.newDocumentBuilder();
File exportFormatXmlCheck = new File(xmlPath); Document doc = docBuilder.parse (exportFormatXmlCheck);
      //Get all the <map> nodes in a nodelist - strMap
                 NodeList partialMap = doc.getElementsByTagName("partial");
                   //Here facing problem
          xml doc contains
<TransCheck>
<partial source="English" target="French">
<Min>100</Min>
<Max>130</Max>
</partial>
</TransCheck>
How to access inner elements from <partial > in given xml ?????
Suggest solution
thanks
Message was edited by:
AmitChalwade123456

NodeList partialMap = doc.getElementsByTagName("partial");similarly you have methods in the API that will get you the attribute...
explore the API .....

OracleRowSet/Javax.SQL.Rowset and XML data (Java 1.4)

Does anybody know if it is possible to fetch xml data with an Oracle Row Set (or a hint how to do it)
Or it is obligatory to use the OracleResultSet to make use of the xml methods.
Thanks in advance
Sebastian Schardt

OracleWebRowSet has the writeXml method to output an XML String.
http://www.oracle.com/technology/sample_code/tech/java/sqlj_jdbc/files/oracle10g/webrowset/GetWebRowSet.java.html
Also refer
http://www.oracle.com/technology/sample_code/tutorials/rowset/rowsettoc.html
http://www.oracle.com/technology/sample_code/tech/java/sqlj_jdbc/files/advanced/DMLSample/Readme.html

How to parse XML to Java object... please help really stuck

Thank you for reading this email...
If I have a **DTD** like:
<!ELEMENT person (name, age)>
<!ATTLIST person
     id ID #REQUIRED
>
<!ELEMENT name ((family, given) | (given, family))>
<!ELEMENT age (#PCDATA)>
<!ELEMENT family (#PCDATA)>
<!ELEMENT given (#PCDATA)>
the **XML** like:
<person id="a1">
<name>
     <family> Yoshi </family>
     <given> Samurai </given>
</name>
<age> 21 </age>
</person>
**** Could you help me to write a simple parser to parse my DTD and XML to Java object, and how can I use those objects... sorry if the problem is too basic, I am a beginner and very stuck... I am very confuse with SAXParserFactory, SAXParser, ParserAdapter and DOM has its own Factory and Parser, so confuse...
Thank you for your help, Yo

Hi, Yo,
Thank you very much for your help. And I Wish you are there...I'm. And I plan to stay - It's sunny and warm here in Honolulu and the waves are up :)
A bit more question for dear people:
In the notes, it's mainly focus on JAXB,
1. Is that mean JAXB is most popular parser for
parsing XML into Java object? With me, definitely. There are essentially 3 technologies that allow you to parse XML documents:
1) "Callbacks" (e.g. SAX in JAXP): You write a class that overrides 3 methods that will be called i) whenever the parser encounters a start tag, ii) an end tag, or iii) PCDATA. Drawback: You have to figure out where the heck in the document hierarchy you are when such a callback happens, because the same method is called on EACH start tag and similarly for the end tag and the PCDATA. You have to create the objects and put them into your own data structure - it's very tedious, but you have complete control. (Well, more or less.)
2) "Tree" (e.g. DOM in JAXP, or it's better cousin JDOM): You call a parser that in one swoop creates an entire hierarchy that corresponds to the XML document. You don't get called on each tag as with SAX, you just get the root of the resulting tree. Drawback: All the nodes in the tree have the same type! You probably want to know which tags are in the document, don't you? Well, you'll have to traverse the tree and ask each node: What tag do you represent? And what are your attributes? (You get only strings in response even though your attributes often represent numbers.) Unless you want to display the tree - that's a nice application, you can do it as a tree model for JTree -, or otherwise don't care about the individual tags, DOM is not of much help, because you have to keep track where in the tree you are while you traverse it.
3) Enter JAXB (or Castor, or ...): You give it a grammar of the XML documents you want to parse, or "unmarshall" as the fashion dictates to call it. (Actually the name isn't that bad, because "parsing" focuses on the input text while "unmarshalling" focuses on the objects you get, even though I'd reason that it should be marshalling that converts into objects and unmarshalling that converts objects to something else, and not vice versa but that's just my opinion.) The JAXB compiler creates a bunch of source files each with one (or now more) class(es) (and now interfaces) that correspond to the elements/tags of your grammar. (Now "compiler" is a true jevel of a misnomer, try to explain to students that after they run the "compiler", they still need to compile the sources the "compiler" generated with the real Java compiler!). Ok, you've got these sources compiled. Now you call one single method, unmarshall() and as a result you get the root node of the hierarchy that corresponds to the XML document. Sounds like DOM, but it's much better - the objects in the resulting tree don't have all the same type, but their type depends on the tag they represent. E.g if there is the tag <ball-game> then there will be an object of type myPackage.BallGame in your data structure. It gets better, if there is <score> inside <ball-game> and you have an object ballGame (of type BallGame) that you can simply call ballGame.getScore() and you get an object of type myPackage.Score. In other words, the child tags become properties of the parent object. Even better, the attributes become properties, too, so as far as your program is concerned there is no difference whether the property value was originally a tag or an attribute. On top of that, you can tell in your schema that the property has an int value - or another primitive type (that's like that in 1.0, in the early release you'll have to do it in the additional xjs file). So this is a very natural way to explore the data structure of the XML document. Of course there are drawbacks, but they are minor: daunting complexity and, as a consequence, very steep learning curve, documentation that leaves much to reader's phantasy - read trial and error - (the user's guide is too simplicistic and the examples too primitive, e.g. they don't even tell you how to make a schema where a tag has only attributes) and reference manual that has ~200 pages full of technicalities and you have to look with magnifying glas for the really usefull stuff, huge number of generated classes, some of which you may not need at all (and in 1.0 the number has doubled because each class has an accompanying interface), etc., etc. But overall, all that pales compared to the drastically improved efficiency of the programmer's efforts, i.e. your time. The time you'll spend learning the intricacies is well spent, you'll learn it once and then it will shorten your programming time all the time you use it. It's like C and Java, Java is order of magnitude more complex, but you'd probably never be sorry you gave up C.
Of course the above essay leaves out lots and lots of detail, but I think that it touches the most important points.
A word about JAXB 1.0 vs. Early Release (EA) version. If you have time, definitively learn 1.0, they are quite different and the main advantage is that the schema combines all the info that you had to formulate in the DTD and in the xjs file when using the EA version. I suggested EA was because you had a DTD already, but in retrospect, you better start from scratch with 1.0. The concepts in 1.0 are here to stay and once your surmounted the learning curve, you'll be glad that you don't have to switch concepts.
When parser job is done,
what kind of Java Object we will get? (String,
InputStream or ...)See above, typically it's an object whose type is defined as a class (and interface in 1.0) within the sources that JABX generates. Or it can be a String or one of the primitive types - you tell the "compiler" in the schema (xjs file in EA) what you want!
2. If we want to use JAXB, we have to contain a
XJS-file? Something like:In EA, yes. In 1.0 no - it's all in the schema.
I am very new to XML, is there any simpler way to get
around them? It has already take me 4 days to find a
simple parser which give it XML and DTD, then return
to me Java objects ... I mean if that kind of parser
exists....It'll take you probably magnitude longer that that to get really familiar with JAXB, but believe me it's worth it. You'll save countless days if not weeks once you'll start developing serious software with it. How long did it take you to learn Java and it's main APIs? You'll either invest the time learning how to use the software others have written, or you invest it writing it yourself. I'll take the former any time. But it's only my opinion...
Jan

Message processing failed in XML parser

This is IDoc to file integration. When I test (WE19), I did not put any value in the 'Quantity' field (which is 6 characters long).In the message mapping I put a condition to see if the value is empty then put zero, and it did not give any error. I have given all the fixed field lengths in the file adapter but still getting the following error:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Column value 'TABLERO DE CONTROL' too long (>6 for 2. column) - must stop', probably configuration error in file adapter (XML parser error)': java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Column value 'TABLERO DE CONTROL' too long (>6 for 2. column) - must stop', probably configuration error in file adapter (XML parser error)'

When I enter value in the 'Quantity' field, the integration works fine. The value 'tablero de control' is the 'Description' which is the next field. My Content Conversion is like;
Field1, Field2, Quantity, Description
(where Field1 and Field2 are mandatory and Quantity and Description are optional)
When I provide all 4 values, the integration work just fine, when I do not provide 'Quantity' it fails.

Xdk and xml parser[JAVA]

Similar Messages

Maybe you are looking for