I will need to do a little research on this. It was quite a while ago that I submitted this and I have long since forgotten the details. I just remember that it had something to do with results coming back (or not) or something like that. I am also fairly certain that slightly different versions were needed for Xalan 2.4 and 2.5. I thought that I had described the details at the time in an e-mail. I will see if I can find that somewhere. Maybe I will also do some DIFFs to figure out what I changed. Unfortunately, unless I was particularly diligent in an e-mail that I can find (or it is obvious from the code change) the rational may be lost.
It could be that this fixes the rowset problem described earlier... at least the version of Xalan that I am running does not exhibit that problem - but that could be because all my XConnections have multiple-results enabled. At least I think so, personally I have not used the Xalan SQL extension in a long time, other members of my team have been doing all of that. I will try to get to this in the next few days... maybe tonight if I finish the stuff I am working on early - or if curiosity gets the better of me... Art -----Original Message----- From: John Gentilin [mailto:[EMAIL PROTECTED] Sent: Monday, July 14, 2003 5:45 PM To: [EMAIL PROTECTED] Subject: Re: SQL XConnection Art, I see why I did not check in the XNodeSet fix, I did not realize that you were submitting a fix for another package in Xalan. I mistakenly assumed that this was some test code and since there were no direct references to it, it was not needed. What we need to do is create a separate thread, posting the changes and why. That way some who maintains that could comment on how it would affect Xalan globally. I have your original source changes, would that help you create the new thread. I am not sure what the original rational was for the change. Regards John G [EMAIL PROTECTED] wrote: >John, > >Could the problem be fixed by the XNodeSet fix? It seems as if the >xsl:for-each may have been one of the cases that it resolved >(unfortunately I do not remember the details of what was changed - it >does seem as though slightly different versions of the fix were needed >for 2.4 and 2.5). I do not know about closing and reopening the >connection. Why should this be necessary. > >Art > >-----Original Message----- >From: Phil Friedman [mailto:[EMAIL PROTECTED] >Sent: Friday, July 11, 2003 1:12 PM >To: John Gentilin >Cc: [EMAIL PROTECTED] >Subject: Re: SQL XConnection > > >John, > >I've removed the dependencies on other files. I've attached a new >version WMAllOut201.xsl that yields correct results with Xalan 2.0.1 >and another WMAllOut251.xsl which is my attempt to get it working under >2.5.1. I have only been able to get it to work by 1) copying the >results before accessing them with xsl:for-each. 2) closing and >reopening the connection between each query. > >Both style sheets work, but 2.0.1 is immensely faster and I've got >other situations where these changes would be unworkable. > >Regards, Philip Friedman -- Terralink Software Systems -- 207-772-6500 >x101 > >On Fri, 11 Jul 2003 00:34:56 -0700, John Gentilin ><[EMAIL PROTECTED]> may have written: > >|Phil, >| >|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 >|> >|> >| >| > > -- -------------------------------------- John Gentilin Eye Catching Solutions Inc. 18314 Carlwyn Drive Castro Valley CA 94546 Contact Info [EMAIL PROTECTED] Ca Office 1-510-881-4821 NJ Office 1-732-422-4917
