[jdom-interest] JDOM and Oracle V2 Parser

[Andrew Schneider]

I'm sorry...too many exceptions today. :-)  I meant to say the IllegalTargetException issue, not the IllegalAccessException.  I have been doing some research and noticed this issue in the mailing list archives, and I do indeed get it when attempting to use the Oracle DOM parser using the DOMBuilder demo class.  That's what I wanted clarification on whether there was a way to work around the IllegalTargetException using Oracle's parser.

The SAX issue is just to clarify that if we use a different SAX parser, we no longer have to have the xerces.jar file in the classpath.  The FAQ is not clear on this (in fact states that we DO have to have it in the classpath), and I haven't found anything on the mailing list regarding this issue.

Thanks,
Andrew

>>> "Andres March"  07/02/02 01:39PM >>>
I never used the Oracle Sax parser, so I cannot comment on its workability with JDOM but I do know about the IllegalAccessException.  Have you encountered this error or are you just doing research?

Obviously, you must have all the classes necessary for your program in the classpath. No getting around that.  The IllegalAccessException comes into play because in many appservers there more than one classloader.  Usually, there will be at least a classloader for the appserver libs and one for each application.  This is good because it will partition your application environments.  I don't know the OAS but I would guess that the ORacle Parser is in the appserver lib.  And I bet you will have JDOM in one of your application libs.  The problem is that JDOM will try to access a parser and will find one (the Oracle Parser) but won't have rights to access it, hence the IllegalAccessException.

If any of the above is true, I would recommend placing a duplicate copy of the OracleParser in your application's lib directory.  Hopefully, the classpath is built such that this one gets picked up before the one in the appserver lib.

Via con Dios.


-----Original Message-----
From: Andrew Schneider [mailto:Andrew.Schneider at doj.ca.gov] 
Sent: Tuesday, July 02, 2002 12:38 PM
To: jdom-interest at jdom.org 
Subject: [jdom-interest] JDOM and Oracle V2 Parser


Hi All,

We are evaluating JDOM to utilize on a project.  It has been decided to use Oracle's parser here on the project (it is a full Oracle shop from database to app server).  I have read through the archives about the issue regarding IllegalAccessException and the reasons behind why it is occurring.  My question is, is there a work around to this, so we can use JDOM in conjunction with the Oracle Parser?  I searched the archives, but could find nothing addressing this.

Also, since we will be using the Oracle parser exclusively, will there be any need to have the xerces.jar in the classpath?  The FAQ is kind of confusing on this respect stating that xerces.jar has to be in there first.  However, if we use a SAX parser and specify the use of Oracle's either in JAXP or in the code, will we need xerces at all?  This is kind of a sticking point on the team, only having the Oracle parser library in the classpath.

Thanks,
Andrew Schneider

*******************************************************************
Confidentiality Notice: This e-mail message, including any
attachments, is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender
by reply e-mail and destroy all copies of the original message.
*******************************************************************

_______________________________________________
To control your jdom-interest membership:
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhost.com

*******************************************************************
Confidentiality Notice: This e-mail message, including any
attachments, is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender
by reply e-mail and destroy all copies of the original message.
*******************************************************************