Thanks for the info, John. I'll give that a shot.

-Dan Feather

-----Original Message-----
From: John Gentilin [mailto:[EMAIL PROTECTED] 
Sent: Thursday, June 30, 2005 7:52 PM
To: Dan Feather
Cc: [email protected]
Subject: Re: SQL Extension - No suitable driver found

Dan,

I have seen this problem before with the Oracle driver and I am not sure

what it
is. We have looked into it, and it is definitely a class loader problem 
that acts differently
in different environment. However, what I do know is; if you implement 
the external
connection pool, it is never a problem. The default connection pool was 
added mainly
to provide code symmetry. I usually view it as a security risk, and a 
deployment headache
by adding in connection information in the stylesheet, but it works well

if you just want to
give it a test drive. The external connection pool allows you to 
establish the JDBC connection
outside of the transformation process and reference the DB connection by

name inside the
transformation process. This is similar to the JNDI named connections 
and after this weekend,
the SQL extensions will support the JNDI connection type. This is 
probably not what you wanted
to hear, but implementing the external connection pool probably only 
adds 6-10 lines to you current
Java file. There should be example code in the sample directory.

Regards
John G

Dan Feather wrote:

>I am running into an issue, and it doesn't make sense to me.
>
>I have a simple java program that runs my XSLT that uses the SQL
>Extension. It runs fine on my PC. No problem, works like a champ...
good
>stuff.
>
>I put this same code on an iSeries (AS/400), I put xalan.jar,
>xml-apis.jar, jt400.jar, etc. in my classpath and execute the code and
>it doesn't work. I get the "No suitable driver found" error I am sure
>you all have seen before. My driver is
>com.ibm.as400.access.AS400JDBCDriver and it is in jt400.jar... which is
>in my classpath.
>
>I have seen people mention the Xalan classloader and I am wondering
what
>that is all about. Is there something special in Xalan for loading
>classes that is different from other things one usually runs across?
>
>Also, what can I do to get better exception information from my
>stylesheet when things like this happen. Right now I am just using the
>xsl:message and xsl:copy elements like those that are found in the SQL
>Extension examples. I would like to get a full stack trace. Do I need
to
>write a custom ErrorHandler to do this? Thanks for your help.
>
>-Dan Feather
>  
>





NOTICE: This electronic mail message and any files transmitted with it are 
intended exclusively for the individual or entity to which it is addressed. The 
message, together with any attachment, may contain confidential and/or 
privileged information. Any unauthorized review, use, printing, saving, 
copying, disclosure or distribution is strictly prohibited. If you have 
received this message in error, please immediately advise the sender by reply 
email and delete all copies.



Reply via email to