Re: SQL Extension Driver Name

[Tobias McNulty]

Title: Re: SQL Extension Driver Name

So here's the deal:

I'm using J2SDK 1.4, in which Sun thoughtfully decided to include all of the Xerces/Xalan code in rt.jar.  To account for the _possibility_ of updates to Xerces/Xalan, Sun introduced the "Endorsed Standards Override Mechanism" (http://java.sun.com/j2se/1.4/docs/guide/standards/).

I'm using the SQL Extension with my own JDBC driver in an attempt to display data using XSL from a legacy database-like program.  It works great when I manually nuke the entire org.apache package from rt.jar (so that java can find the xerces/xalan jars I provide).  But, when I leave rt.jar untouched, and place the xerces/xalan jars in the 'endorsed' folder as Sun indicates we should do, the SQL extension cannot find my JDBC driver ("Invalid Driver Name Specified!", SQL extension reports).

Does anyone have experience with the 'endorsed' mechanism, or have any other thoughts that might assist in solving this problem?

Thanks,

Toby

At 12:04 PM -0500 4/3/02, Tobias McNulty wrote:

After I finally got the SQL Extension working last week, I've managed to break it again.  At least now I get some errors:

Is the "Invalid Driver Name Specified!" error in reference to the package & class name of the driver?  The driver is in my classpath, and I tested it by instantiating a copy of the driver in the Java code, but the XSL still can't find it!

Is there something else I might be missing here?

Thanks much,
Toby
--
Tobias McNulty

Data Description, Inc.
840 Hanshaw Road, Suite 9
Ithaca, NY 14850
Phone: (607) 257-1000
E-mail: [EMAIL PROTECTED]
Web: www.datadesk.com

-- 

Tobias McNulty
Data Description, Inc.
840 Hanshaw Road, Suite 9
Ithaca, NY 14850
Phone: (607) 257-1000
E-mail: [EMAIL PROTECTED]
Web: www.datadesk.com