Is that the entire XSL file, seems to be missing some of the templates. From what I can see, the XConnection#new is being called inside a template that may be losing scope, you may need to declare the template in a higher level template. Also the new() operator that takes parameters is being depreciated, the newer style is a new() then the connect() method.
i.e.
<xsl:variable name="Xcon1" select="sql:new()"/>
<xsl:variable name="dbConResult" select="sql:connect($Xcon1,'DQP_ConnPool')"/>
Also do you have any other XSL files that may be a little more straight forward.
Each call to query creates a new JDBC Connection and that connection is maintained
throughout the life of the SQLDocument, the object returned from query/pquery.
The current code is CVS may be a bit unstable since I just checked in some major
changes to support in-line variables.
-JG
Phil Friedman wrote:
Once again I'm trying to upgrade from Xalan 2.0.1, this time to 2.5.1.
We use the SQL XConnection extensively to access Fox Pro, Sybase and MS
SQL Server databases. All of our original .xsl works fine with 2.0.1,
but not with 2.5.1.
Basically, we have only been able to get correct results with a new connection for each query, and must copy the results before using them. Both of these seem to be performance and resource hits.
In the attached file, see comments starting with '<!--!' for some of the problems and work-arounds we have found. This .xsl connects to Fox Pro, but we have similar problems with the real databases as well.
Regards, Philip Friedman -- Terralink Software Systems -- 207-772-6500 x101
