Xmlparsercover fails to parse supplied family.xml

Question

I have downloaded the XML parser for PLSQL and installed it as
per the instructions. However, when try to execute the supplied
Domsample, providing the supplied family.xml, I get 'Error
occurred while parsing' error, following by the full path name of
the error file I have supplied.
I have checked the installation carefully and have confirmed that
I am passing in full file paths but to no avail.
I have tried asimplied piece of PL/SQL, documented below, which
as can be seen is falling over in the same way.
What has been missed ?
The error is coming back from the Java class that implements
Xmlparsercover.parse so I cannot investigate any further as do
not have the source.
declare
err varchar2(512);
p xmlparser.parser;
begin
p := xmlparser.newparser;
xmlparser.setvalidationmode(p,FALSE);
xmlparser.seterrorlog(p,
'/u06/home/dev22c/ghicks/xml_for_plsql/sample/error.txt');
xmlparser.setbasedir(p,
'/u06/home/dev22c/ghicks/xml_for_plsql/sample');
xmlparsercover.parse(p.ID
,'/u06/home/dev22c/ghicks/xml_for_plsql/sample/family.xml'
,err);
-- now print out the returned error
dbms_output.put_line (err);
end;
On running the above file the following value is printed out
for the contents of err :
/u06/home/dev22c/ghicks/xml_for_plsql/sample/error.txt
I can confirm that the directory called sample in which the
file family.xml resides and to which the file error.txt is meant
to be written has full privileges granted on it. The file
error.txt does not exist prior to running the above and is not
created by the above.
Basically, I need someone in the Oracle XML team to look at the
source code in Java and tell me under what circumstances the
returned err code can be set to the full pathname of the error
file. This may then give a further clue as to the problem.
null

Answer 1

Hi All,
When i transformed or parsed many XML Files of huge
size...I am getting java.lang.OutOfMemory error for
all the huge xml files. It is working fine for files
which is of small size.Of course it is.
>
I've 2GB ram in my system. I have also set heapsize for the JVM.
-Xms512M -Xmx1800M (or) -Xms512M -Xmx1500MYou can't always get what you want. Your JVM is competing with all the other processes on your machine, including the OS, for RAM.
I like to know what are the drawbacks of JDOM parser ?You just discovered it: all DOM parsers create an in-memory representation of the entire document. A SAX parser does not.
What is the maximum size of the Xml which JDOM can parse ?The max amount of memory that you have available to you.
I've read a long time before that parsers have
certain limitations. Can anybody tell me the
limitations of the parses?See above.
Please help. i'm currently using jdom.jar to parse the xml files.You can try a SAX parser or a streaming parser. Maybe those can help.
%