Hi John (and the rest )
This morning I was going to write:
I thought (and hoped ) it was that simple ... but apperently it isn't
(with OC4J ) ...
But now I have to write:
... well after all it is ...
Instead of putting the xalan jars in the applib directory of OC4J, I
had to include the xalan 2.7.0 jars (xalan.jar, serializer.jar,
xercesImpl.jar and xml-apis.jar) in the WEB-INF/lib of my war file. And
.... I had to include the next line in my orion-web.xml:
<web-app-class-loader search-local-classes-first="true"
include-war-manifest-class-path="true" />
This old OC4J uses an ancient JDK, and the endored lib-trick
http://xml.apache.org/xalan-j/faq.html#faq-N100D6 didn't work.
Without this, the ancient xalan out of the JDK's rt.jar was taken, and
that one doesn't know about the JNDIConnectionPool at all.
Greetings, Joris
John Gentilin wrote:
Hi Joris,
Connecting the Xalan SQL extension to a JNDI data source should be
very easy.... What you need to do is look at the source Xalan source
for ConnectionPool code along with the External Connection Pool
example.... The attached zip for has code that implements a JNDI
connection pool... I don't remember its origin, or if it is a complete
example... but I am passing it along for your reference..
Regards
John Gentilin
Joris Jansen wrote:
Hi there,
I looked at the sql extension a copule of times, and I like to use it in
some project.
I played around with the DB credentials inside the XSLT and it works
like a charm, but ...
Now I want to connect to a JNDI datasource in my container, an OC4J
10.1.0.2 container to be more precise.
Is there anyone who can help me on this one?
Thanx, Joris
--
I couldn't afford a cool signature, so I just got this one.
[EMAIL PROTECTED]
M +31 (0)6 1091 4504
Cumquat Information Technology BV
De Dreef 19
3706 BR Zeist
http://www.cumquat.nl
