Typo in Developer XML/Parsing XML Efficiently ?

Hi !
On this web page :
http://otn.oracle.com/oramag/oracle/03-sep/o53devxml.html
If you look at the "Figure 1: A DOM Tree" for the book example from an XML piece above on that page you'll see that in a second from the bottom line, box, second from the left has element named "author" and then text box underneath says "XML in a Nutshell".
Shoouldn't that element be a "title" ? And then level five in that tree should look like :
Attr | Element | Element | Element
id = 121 | title | author | Price
Thank you !
Vladimir Bogak,
DB Developer, LucasFilm, CA

You could try re-installing JWSDP 1.3 but this time include Tomcat and ant, and then develop your application with help of the JWSDP Tutorial[1]. Then, port ing your app to your external Tomcat shouldn't be hard.
Regards,
-- Ed
[1] http://java.sun.com/webservices/docs/1.3/tutorial/doc/index.html

Similar Messages

JSF - XML - Parse XML Document in backing bean.

Hello:
I'm trying to parse an XML text, readed from DB Table, everything was working OK
until somebody adds and XML with some values that makes the DOMParser raise
an exception, but, are valid values to our applications.
This is the example:
<Audit>
<PreviousValues>
<Table name="OFFICES">
<Column theName="ID" theValue="1"/>
<Column theName="OFFICE_NAME" theValue="TEST"/>
<Column theName="STATUS" theValue="AC"/>
<Column theName="ADDRESS" theValue="&&"/>
<Column theName="MANAGER" theValue="AA"/>
</Table>
</PreviousValues>
</Audit>
Note the value in bold, this chars are valid in this field, so we can't restrict the user
to type before the xml is generated, and when we try to parse it, we got an
exception like this:
XMLParseException: Expected name instead of &
When we remove this values manually in the DB and put some numbers, and try
to parse it again, it works ok. This is the code that parse the xml.
String xml = (String)requesScope.get("xml");
DOMParser theParser = new DOMParser();
theParser.setValidationMode(theParser.NONVALIDATING);
theParser.setPreserveWhitespace(false);
theParser.retainCDATASection(true);
Reader r = new StringReader(xml);
System.out.println(theParser.nameSpaceSeparator);
theParser.parse(r);
the last line is the one that raise the exception.
Please help.
thnks in advance.

repost
help please

XML Parsing with XSL Performance lag

Hi there
I should qualify this post by saying I am fairly new to EJB's and have based the below on a Java Working with XML Tutorial I read.
I have an EJB which is being developed to parse XML documents with an XSL stylesheet and return HTML for display. The code is working fine however there is a fairly hefty performance lag when using the EJB to generate the HTML as opposed to the straight HTML. I am getting an average response time of 95000ms using the EJB as opposed to 45000ms when viewing the straight HTML. The code I am using to do the parsing is :
DocumentBuilder builder = factory.newDocumentBuilder();
Document document = builder.parse(dataFile);
// Convert docs into StreamSource
StreamSource stylesource = new StreamSource(styleSheet);
StreamSource source = new StreamSource(dataFile);
StringWriter strWrite = new StringWriter();
StreamResult result = new StreamResult(strWrite);
// Use a Transformer for output
TransformerFactory tFactory = TransformerFactory.newInstance();
Transformer transformer = tFactory.newTransformer(stylesource);
transformer.transform(source, result);
There is then some error handling and the strWrite object is placed into an array to be returned.
I am really looking to find out if the performance lag I am experiencing is normal or if there is anything I can do to improve the speed of the code.
All comments and help is most appreciated.
Cheers
Justin.

You should be able to increase performance by caching Templates objects in memory as a previous post suggested.
Here is some untested code:public final class TransformerCache
     private static Map cache = new Vector();
     private TransformerCache(){}
     public static Transformer getTransformer( String filename )
          if( ! cache.containsKey( filename ) )
               TransformerFactory tf = TransformerFactory.newInstance();
               Templates template = tf.newTemplates( new StreamSource( filename ) );
               cache.put( filename, template );
          return ( ( Templates ) cache.get( filename ) ).newTransformer();
}This aproach works in a clustered environment, just bear in ming that there will be an instance of the cache on each server instance (virtual machine).

XML parser causes memory leakage, help!

I have the following function which called by other package to transfer xml. But every time it is called oracle will consume 600 to 700k memory and never release them. Any thought about it?
Function Transform(xml Clob,xsl Clob) Return Clob is
p xmlparser.Parser;
xmldoc xmldom.DOMDocument;
xsldoc xmldom.DOMDocument;
proc xslprocessor.Processor;
ss xslprocessor.Stylesheet;
cl Clob;
begin
p := xmlparser.newParser;
xmlparser.setValidationMode(p, FALSE);
xmlparser.setPreserveWhiteSpace(p, TRUE);
xmlparser.parseClob(p, xml); -- parse xml
xmldoc := xmlparser.getDocument(p);
xmlparser.parseClob(p, xsl); -- parse xsl
xsldoc := xmlparser.getDocument(p);
proc := xslprocessor.newProcessor;
ss := xslprocessor.newStylesheet(xsldoc, '');
dbms_lob.createtemporary(cl, TRUE);
xslprocessor.processXSL(proc, ss, xmldoc,cl);
xslprocessor.freeProcessor(proc);
xslprocessor.freeStyleSheet(ss);
xmlparser.freeParser(p);
return cl;
exception -- deal with exceptions
when xmldom.INDEX_SIZE_ERR then
raise_application_error(-20120, 'Index Size error');
when xmldom.DOMSTRING_SIZE_ERR then
raise_application_error(-20120, 'String Size error');
when xmldom.HIERARCHY_REQUEST_ERR then
raise_application_error(-20120, 'Hierarchy request error');
when xmldom.WRONG_DOCUMENT_ERR then
raise_application_error(-20120, 'Wrong doc error');
when xmldom.INVALID_CHARACTER_ERR then
raise_application_error(-20120, 'Invalid Char error');
when xmldom.NO_DATA_ALLOWED_ERR then
raise_application_error(-20120, 'Nod data allowed error');
when xmldom.NO_MODIFICATION_ALLOWED_ERR then
raise_application_error(-20120, 'No mod allowed error');
when xmldom.NOT_FOUND_ERR then
raise_application_error(-20120, 'Not found error');
when xmldom.NOT_SUPPORTED_ERR then
raise_application_error(-20120, 'Not supported error');
when xmldom.INUSE_ATTRIBUTE_ERR then
raise_application_error(-20120, 'In use attr error');
end Transform;
null

Would you try to free the alloced temporary lob whenever get Exception and try?
dbms_lob.createtemporary(cl, TRUE);
dbms_lob.freetemporary(cl);
Thanks.
null

XML parsing failed - Works in Oracle Developer fails in SQLplus

Hello,
I am trying to figure out what could possibly be causing my XML parsing to fail from sqlplus. Basically the exact same sql script fails with the following error when run from sqlplus but works fine in Oracle Developer.
Now I have read a number of posts talking about the NLS_Lang and characterset issues. But these are all running on the same machine.
Error Message Received:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00222: error received from SAX callback function
ORA-06512: at "SYS.DBMS_XMLSTORE", line 78
ORA-06512: at line 53
Exact SQL Script
DECLARE
insCtx DBMS_XMLStore.ctxType;
rows NUMBER;
xmldoc CLOB :=
'<DepotData DepotCode="B106">
<tblPoint_of_Call>
<DEPOTCODE>B106</DEPOTCODE>
<MASTERKEY>2077</MASTERKEY>
<ADDR_ID>45286159</ADDR_ID>
<ADDR_MAIL_ID>45286160</ADDR_MAIL_ID>
<STREETBLOCK_KEY>45</STREETBLOCK_KEY>
<PC_ID>19603417</PC_ID>
<ST_ID>40034414</ST_ID>
<BUILDING_KEY>0</BUILDING_KEY>
<ADDR_NUM>505</ADDR_NUM>
<POCTYPE>154</POCTYPE>
<RECEPTACLETYPE>964</RECEPTACLETYPE>
<TOTALPOCS>1</TOTALPOCS>
<TOTALPOCSOCCUPIED>1</TOTALPOCSOCCUPIED>
<TOTALADMAIL>1</TOTALADMAIL>
<OLD038POC>0</OLD038POC>
<OCCUPIED>1</OCCUPIED>
<ADMAIL>1</ADMAIL>
<BAGGER>0</BAGGER>
<SORTED>1</SORTED>
<DELIVERED>1</DELIVERED>
<AMOBLIGATORY>0</AMOBLIGATORY>
<POCICANDIDATE>0</POCICANDIDATE>
<DELIVERYSEQUENCE>10</DELIVERYSEQUENCE>
<NUMSEPARATIONS>0.50</NUMSEPARATIONS>
<SEPSGROUPID>0</SEPSGROUPID>
<DELETED>0</DELETED>
<CARDID>0</CARDID>
<CARD>0</CARD>
<FORCECARD>0</FORCECARD>
<DNC>0</DNC>
<PRINTED>0</PRINTED>
<A12CARD>0</A12CARD>
<EXTRACARDS>0</EXTRACARDS>
<DSOUPDATECODE>0</DSOUPDATECODE>
<TRANSACTION_TYPE>0</TRANSACTION_TYPE>
<UPDATE_TYPE>0</UPDATE_TYPE>
<SORTSEQUENCE>10</SORTSEQUENCE>
<BUILDINGBASE>0</BUILDINGBASE>
</tblPoint_of_Call>
</DepotData>';
BEGIN
insCtx := DBMS_XMLStore.newContext('AIMPRIME.TBLPOINT_OF_CALL'); -- get saved context
-- set the columns to be updated as a list of values
-- Now insert the doc.
-- This will only insert into EMPNO, SAL and HIREDATE columns
DBMS_XMLStore.setRowTag(insCtx,'tblPoint_of_Call');
rows := DBMS_XMLStore.insertXML(insCtx, xmlDoc);
-- Close the context
DBMS_XMLStore.closeContext(insCtx);
END;
System Information:
Oracle XE on windows XP. Everything is running on the same machine, sqlplus, Oracle Developer and the database are all on the same machine.
If you need any more information please let me know, and how to get the information you want. I am not a DBA so I don't know how to do a lot of things with oracle, but I do know that this SQL should be working.

NLS...read up on them
on the same machine, yeah and...?
(1) c:\> set NLS_LANG=.....
(2) c:\> sqlplus
-- sqlplus has the active nls settings set from (1)
3) you now connect to a database
- this database has an NLS character settings that where set during using a spfile or pfile
- or, as in the case of the characterset, was defined and set once, during the creation of the database.
So...
Your NLS settings in (1) can be different from the ones that are active in the database (3).
Your NLS settings are / can be set on windows on 5 levels
In the registry under /software/oracle:
1) on HKEY_LOCAL_MACHINE
2) on HKEY LOCAL USER
In the envionment settings from windows under control panel, system, advanced, environment settings:
3) on system level
4) on user level
5) On command level via explicitly setting the parameter before starting the actual program
So in all, you can have the case where the NLS settings from sqlplus or Oracle Developer or the database are all different.
http://www.oracle.com/technology/tech/globalization/htdocs/nls_lang%20faq.htm

Efficient XML parsing?

Is there a simpler and more efficient way to parse XML than with SAX? I'm currently using it but I really don't like having to hard-code everything (or at least that's the way I'm doing it), and I'd rather not write my own (which I started doing- extending HandlerBase, etc- until I realized I'd probably be better off simply hard-coding everything).
This is generally the code I'm using. If someone knows of a better parser or a way to simplify this, thats what I'm looking for.
class Parser extends HandlerBase {
    private boolean isSomeElement = false;
    public void startElement(String name, ...) {
        if (name.equals("someElement") {
            isSomeElement = true;
    public void endElement(String name) {
        if (name.equals("someElement") {
            isSomeElement = false;
    public void characters(...) {
        if (isSomeElement) {
            //process the data in the element...
}Thanks!

You need to distinguish between the parser (which just deciphers XML) and the code that you put next to it (which is what you are asking about). I'm assuming you used the word "efficiency" to refer to the perceived ugliness of your code rather than speed or anything like that.
In any case you are going to have code that says "For an ABC element, do this, for a PUTZ element do that". There are ways you can write the code so it doesn't look so much like hard-coding, for example you could have a Map for which "ABC" is the key and the value is some object that processes the content of the element. That way it looks more object-oriented, and it does have the advantage of getting all the ABC-processing code into one place.

Is this a bug or a typo of XML Parser for PL/SQL or something else?

Hello,
Below is a piece of codes I copied from the sample that comes with the XML parser for PL/SQL. I found that this sample could not be compiled since:
1- the method printElements takes in a parameter 'doc' of type 'xmldom.DOMDocument'
2- then this 'doc' is refered to in API method
xmldom.getElementsByTagName which takes two parameter, one of type DOMElement, the other of type char.
Are these tow types compatible?
where can i get a better documentation for the XML parser for PLSQ, the one come with the zip fileis not up to date since the miss documentation for DOM. thank you.
BM
-- prints elements in a document
procedure printElements(doc xmldom.DOMDocument) is
nl xmldom.DOMNodeList;
len number;
n xmldom.DOMNode;
begin
-- get all elements
nl := xmldom.getElementsByTagName(doc, '*');
len := xmldom.getLength(nl);
-- loop through elements
for i in 0..len-1 loop
n := xmldom.item(nl, i);
dbms_output.put(xmldom.getNodeName(n) | | ' ');
end loop;
dbms_output.put_line('');
end printElements;

public class HelpIcon extends Image
The attached snippets showed it extending "mx:Image.
class HelpIcon extends Image
[Embed(source="/assets/Info.png")]public var thisIcon:Class;
The attached snippets showed a type of class.
Not precisely sure what you are asking. I added the code as you suggested, it still will not honor the click event on the image.
Here is the code modified as you suggested;
public class HelpIcon extends Image
[Embed(source="/assets/Info.png")]
public var thisIcon:Class;
public function HelpIcon()
   super();
   this.source = new thisIcon();
   this.addEventListener(FlexEvent.CREATION_COMPLETE,initHelp)
private function initHelp(event:Event):void
   this.removeEventListener(FlexEvent.CREATION_COMPLETE,initHelp);
   this.addEventListener(MouseEvent.CLICK, helpClicked,true,5);
It still does not honor the click event.
Paul

Oracle reports developer 11g java.lang.NoClassDefFoundError oracle/xml/parser/v2/XMLParserException

Hi All,
Need expertise help to resolve the issue I am getting with Oracle Report builder.
I have installed and configured Oracle Forms and Reports Builder 11g on my Windows 7 & 64 bit machine.
Oracle Forms are working fine and I am getting an error while I am launching the Oracle Report Builder.
It says
The error is;
java.lang.NoClassDefFoundError:
oracle/xml/parser/v2/XMLParserException
once I close th eabove error window, then it says java.lang.NullPOinterException.
I have done all modifications to Middleware\as_1\bin rwbuilder.bat file as below
@echo off
@echo INFO: The Reports Builder is only supported on the Linux x86 and Windows x86 operating systems, for further information, please refer to the Release Notes ...
@echo Starting Reports 11g Builder...
setlocal
call C:\Oracle\Middleware\asinst_1\config\reports\bin\reports.bat
@echo on
start C:\Oracle\Middleware\as_1\bin\rwbuilder.exe %*
@echo off
endlocal
:end
@echo on
But report builder is not working. (Error comes when launching the Report Builder ).
Quick support is highly appreciated.
Thanks
Muditha

Hi All,
Need expertise help to resolve the issue I am getting with Oracle Report builder.
I have installed and configured Oracle Forms and Reports Builder 11g on my Windows 7 & 64 bit machine.
Oracle Forms are working fine and I am getting an error while I am launching the Oracle Report Builder.
It says
The error is;
java.lang.NoClassDefFoundError:
oracle/xml/parser/v2/XMLParserException
once I close th eabove error window, then it says java.lang.NullPOinterException.
I have done all modifications to Middleware\as_1\bin rwbuilder.bat file as below
@echo off
@echo INFO: The Reports Builder is only supported on the Linux x86 and Windows x86 operating systems, for further information, please refer to the Release Notes ...
@echo Starting Reports 11g Builder...
setlocal
call C:\Oracle\Middleware\asinst_1\config\reports\bin\reports.bat
@echo on
start C:\Oracle\Middleware\as_1\bin\rwbuilder.exe %*
@echo off
endlocal
:end
@echo on
But report builder is not working. (Error comes when launching the Report Builder ).
Quick support is highly appreciated.
Thanks
Muditha

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

HOW TO: Use the XML parser in Oracle 8.1.7

I am trying to figure out how to use the xml parser provided in oracle 8.1.7. all i want to do is parse a xml report that is defined using a schema, and place the data into the proper tables. i am totally unfamiliar with the xml parser and how it works. i have done some reading on the subject, but seem to be getting some conflicting infromation about which utilites i need and how to invoke them. can someone please tell me what utilities i need, how to invoke them, and what i need to do to get a xml document to parse and insert to a table? I would greatly appreciate any help anybody could offer. thanks.

You can parse the XML Document with XML Parser and place the data into database using XSU(XML SQL Utility).
Both of these are included in XDK for Java at:
http://otn.oracle.com/tech/xml/xdk_java
The following document could also help:
Oracle9i XML Developer's Guide--XDK [PDF] at http://otn.oracle.com/tech/xml/doc.html

XML Parser Error while creating Web service Client using JAX RPC

hello evryone,
Im facing XML Parser Error while creating web service client using JAX RPC. Im using Net Beans IDE for development purpose. I have wrote configuration file for client. Now i want to create Client stub. However i dont know how to do this in Net Beans. So i tried to do it from Command promt using command :
wscompile -gen:client -d build -classpath build config-wsdl.xml
here im getting Error:
error parsing configuration file: XML parsing error: com.sun.xml.rpc.sp.ParseException:10: XML declaration may only begin entities
Please help me out.
Many thanks in advance,
Kacee

Can i use the client generated using jdeveloper 11g to import into the oracle forms 10g, i.e., form builder 10g. Currently this is the version we have in our office.

Xml parsing error while selecting whole result set for sql query

Hi All,
I am having xml parsing error while selecting whole query result set. The data is coming fine for default result set of 50 rows.
My exception is below.
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00234: namespace prefix "xsi" is not declared
Error at line 1
ORA-06512: at "SYS.XMLTYPE", line 254
ORA-06512: at line 1
*31011. 00000 - "XML parsing failed"*
**Cause: XML parser returned an error while trying to parse the document.*
**Action: Check if the document to be parsed is valid.*
My sql query is below that is giving results for default result set of 50 rows.
select extract(xmlType(clob_xml_colm_name), '//v2:node1//childnode/text()','xmlns:v2="namespace_url"').getStringVal() from table_name
My sql developer version is below.
Java(TM) Platform     1.7.0_04
Oracle IDE     3.1.07.42
Versioning Support     3.1.07.42
My database version is below.
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit
Please could any one help me urgently as the sql query is supposed to be correct as it is returning query results, but the problem happening when i try to select whole result set.
Thanks and regards,

What does the XML look like? It appears that some of the supposed XML stored as a CLOB is not really valid XML. Find the row in the table that is causing your issue and review the "XML" in it.

Why the oracle XML parser "parses" the DTD comments?

Hi all,
I always use the header
<?xml version = '1.0' encoding='ISO-8859-1' ?>
to be able to use foreign characters in the XML documents.
The oracle xml parser handles this correctly.
My problem is, when I write comments inside the DTD, the
parser reports "Invalid UTF8 encoding".
Why the parser "parse" the comments? (protected by )
How do I say that the DTD encoding is different from UTF, like
ISO-8859-1?
Example of a correct DTD and corresponding XML, reporting
problems, related to the 2nd comment in the DTD specification,
written with ISO-8859-1 characters.
The DTD:

<!ELEMENT valid ( B, C ) >

<!ELEMENT B (#PCDATA) >
<!ELEMENT C (#PCDATA) >
The XML:
<?xml version = '1.0' encoding='ISO-8859-1' ?>
<!DOCTYPE valid SYSTEM 'valid.dtd'>
<valid>
<B>How are you, Conceigco</B>
<C>I'm fine, thank you.</C>
</valid>
The parser output:
[jgr@frontera test-dtd]$ java oracle.xml.parser.v2.oraxml -v
valid.xml
Error while parsing input sourcevalid.xml(Invalid UTF8 encoding.)
Thank you for any help.
Jorge Gustavo Rocha

I was wrong in saying that the attributes are not added to the element.My main aim is to add a array of elements to the root node.
Is there a efficient manner in adding the elements , rather than adding them individually with the help of appendChild method.
Thanks in advance.
null

Caused by: oracle.xml.parser.v2.XMLParseException: '=' missing in attribute

This is a Bursting problem under EBS 5.6.3. In production we have 5.6.2 and since our development system to 5.6.3 has been upgraded, the following error occurs on every single Burst being done using the Concurrent Manager only:
Caused by: oracle.xml.parser.v2.XMLParseException: '=' missing in attribute.
     at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:205)
     at oracle.xml.parser.v2.NonValidatingParser.parseAttrValue(NonValidatingParser.java:1502)
     at oracle.xml.parser.v2.NonValidatingParser.parseAttr(NonValidatingParser.java:1408)
     at oracle.xml.parser.v2.NonValidatingParser.parseAttributes(NonValidatingParser.java:1350)
     at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1180)
     at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:301)
     at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:268)
     at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:201)
     at oracle.apps.xdo.batch.BurstingProcessorEngine.burstingConfigParser(BurstingProcessorEngine.java:1340)
     at oracle.apps.xdo.batch.BurstingProcessorEngine.process(BurstingProcessorEngine.java:1297)
     at oracle.apps.xdo.batch.DocumentProcessor.process(DocumentProcessor.java:213)
     at xxwel.ebs.xmlp.XXWELBurster.processDocuments(XXWELBurster.java:143)
I can run the same file through 5.6.3 ($JAVA_TOP) libraries mounted on my JDev with no problems. Also the same XML file runs fine on Production under 5.6.2 - no problems. I have also checked the XML file using a syntax checker. I know this is not a syntax issue even though it looks like it.
Could someone point me in the right direction - explain what this means. Getting desperate as 5.6.3 will be going into production soon and all Bursting will fail with this error. I can't get the simplest XML File to Burst - NOTE this is only occurring on the EBS system (even running without the CM ie. a standalone java main it fails). I think this has something to do with the XML parser version and the EBS environment.
Please help...

Hi Tim, good thinking - wouldn't have thought to check this file. Anyway can confirm that the problem is happening with multiple burst control files so I haven't checked the files themselves as the problem seems systemic. anyway here is an example.
<?xml version="1.0" encoding="UTF-8"?>
<xapi:requestset xmlns:xapi="http://xmlns.oracle.com/oxp/xapi">
<xapi:request select="/XXWEL_BIP_UNI_INVOICES/LIST_G_CUSTOMER_NUMBER/G_CUSTOMER_NUMBER">
<xapi:delivery>
<xapi:email server="mailwa01" port="25"
from="${ADMIN_EMAIL}" reply-to ="${ADMIN_EMAIL}">
<xapi:message id="111" to="${ADMIN_EMAIL}" attachment="true" subject="Unigas Inv
oice No: ${TRX_NUMBER}">
</xapi:message>
</xapi:email>
</xapi:delivery>
<xapi:document output-type="pdf" delivery="111">
<xapi:template type="rtf" location="/u02/prod/prodappl/wel/11.5.0/interface/bip/templates/uni_invoice_template.rtf">
</xapi:template>
</xapi:document>
</xapi:request>
</xapi:requestset>
I will start stripping the control files to make sure they are not the problem in the meantime.

Options for XML parsing in WAS 6.20 ABAP and higher

Hello Experts,
   What options are available to me for working with XML documents in SAP R/3 4.7? I am working on SAP WAS 6.20 ABAP and was wondering which tools/techniques I can use for parsing XML files?
   I am developing an ABAP program and primarily need to be able to parse XML documents. I need to be able to traverse up and down their data structures (trees/nodes/elements/etc.).
   In SAP R/3 4.6 I used to use the iXML library but it seems that there are many advanced and powerful features included in SAP WAS 6.20 ABAP and up.
   Could someone please give me a summary of and their opinions on some these "newer" options?
Thanks,
- Vik.

Hi Vik,
   There are two ways you can parse/interpret XML documents in ABAP -
   1. iXML - Which you have already used in 46 release. It wasn't easy to use set of functions but still it was possible to parse documents using iXML library. In WAS 6.20 you can now use class CL_XML_DOCUMENT which is much more easier to use than iXML library. It is bilt on top of iXML using the same DOM model.
2. XSLT - Useing XSLT_TOOLS or XSLT transaction you can create XSLT programs to transform XML to ABAP data objects and then work with ABAP data objects. In this case you have the option of using some other tool like XMLSPY to write the XSLT and then copy that to SAP.
From your post it looks like you will probably have to traverse the tree in unpridictable way, probably DOM based parsing using CL_XML_DOCUMENT is more suitable for you.
Cheers,
Sanjeev

Typo in Developer XML/Parsing XML Efficiently ?

Similar Messages

Maybe you are looking for