You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-users@xalan.apache.org by "Eric R. Rath" <er...@boxerlearning.com> on 2002/05/21 18:03:51 UTC

problem with Xalan 2.3.1 jar?

Hi,

I've been using an older version of Xalan (pre-2.2D14) with no problems on a
Linux machine with Apache, Jserv, and Xerces.  Because I'm not sure which
version of Xalan (or Xerces) I've been using (I didn't set it up), I tried
to upgrade to Xalan 2.3.1, and the version of Xerces that ships with it.

I put xalan.jar, xercesImpl.jar, and xml-apis.jar into the classpath for the
application, and tried to start it up.  When the application first tries to
call TransformerFactory.newInstance(), I get the following message:

[21/05/2002 09:44:54:103] (ERROR) ajp12: Servlet Error:
javax.xml.transform.TransformerFactoryConfigurationError: Provider for
javax.xml.transform.TransformerFactory cannot be found: Provider for
javax.xml.transform.TransformerFactory cannot be found

I'm pretty sure that jserv is finding all the jars, as it complains when a
jar cannot be found.  I also checked that the new xalan.jar and xerces.jar
included the service provider configuration files, and that they were
correct; everything looked okay.

I haven't seen anyone else with this problem, so it seems unlikely that this
is a problem with the xalan or xerces jars, but then again, the only thing
that changed were the jars.  Does anyone have any suggestions for things to
check that I might be doing wrong?

Eric


position() function problems on xalan 2.3.1

Posted by Florin Dragu <fl...@memiq.ro>.
Hi *,
I used xalan 2.0.0 and I'm trying to upgrade to xalan 2.3.1 (or any version
bigger than 2.0.1 so that I can use XSLTC - translets), but I have problems
with some stylesheets because of some XPath changes.
I have a XML that looks like the one bellow and an xslt in which I am trying
to select, let's say, the third (absolute) 'call' element.
In xalan 2.0.0 I did it like this: //call[position() = $current_call], where
current_call = 3, and it selected the call element from '<calls
type="D2-CorporateLink" header="Verbindungen aus dem D2-Netz">'.
In xalan 2.3.1 if I do the same I get all the call elements (or if
'current_call=1' I get 3 call elements, the first from each calls sub-tree).
If I change this to "//call[(count(preceding::call) + 1) = $current_call]" I
get the call element I want, but for big XML files (about 500 call elements)
it takes a lot of time (more than 10 times the time with xalan 2.0.0).
Does anybody know a different approach/solution to this?

Any ideea is welcomed.
Thanks,
Florin

<?xml version="1.0" encoding="UTF-8"?>
<telcoCallList>
	<calls type="Anrufe zu Sonderrufnummern" header="Verbindungen aus dem
D2-Netz">
		<call>
			<netValue>14.53</netValue>
		</call>
		<call>
			<netValue>14.53</netValue>
		</call>
	</calls>
	<calls type="D2-CorporateLink" header="Verbindungen aus dem D2-Netz">
		<call>
			<netValue>14.53</netValue>
		</call>
	</calls>
	<calls type="Gespräche - D2 zu D2 gruppenintern" header="Verbindungen aus
dem D2-Netz">
		<call>
			<netValue>14.53</netValue>
		</call>
		<call>
			<netValue>14.53</netValue>
		</call>
	</calls>
</telcoCallList>


RE: problem with Xalan 2.3.1 jar?

Posted by "Eric R. Rath" <er...@boxerlearning.com>.
Hi,

We figured out the problem - moving xalan.jar, xercesImpl.jar, and
xml-apis.jar into the jdk's jre/lib/ext directory meant that we didn't have
to include them explicitly in any classpaths, and the "self-registration" as
service providers seemed to work.  Before, the files were in a directory
outside the jdk, and included manually in the application's classpath.

Eric

:-----Original Message-----
:From: Eric R. Rath [mailto:ericr@boxerlearning.com]
:Sent: Tuesday, May 21, 2002 12:04 PM
:To: xalan-j-users
:Subject: problem with Xalan 2.3.1 jar?
:
:
:Hi,
:
:I've been using an older version of Xalan (pre-2.2D14) with no
:problems on a
:Linux machine with Apache, Jserv, and Xerces.  Because I'm not sure which
:version of Xalan (or Xerces) I've been using (I didn't set it up), I tried
:to upgrade to Xalan 2.3.1, and the version of Xerces that ships with it.
:
:I put xalan.jar, xercesImpl.jar, and xml-apis.jar into the
:classpath for the
:application, and tried to start it up.  When the application first tries to
:call TransformerFactory.newInstance(), I get the following message:
:
:[21/05/2002 09:44:54:103] (ERROR) ajp12: Servlet Error:
:javax.xml.transform.TransformerFactoryConfigurationError: Provider for
:javax.xml.transform.TransformerFactory cannot be found: Provider for
:javax.xml.transform.TransformerFactory cannot be found
:
:I'm pretty sure that jserv is finding all the jars, as it complains when a
:jar cannot be found.  I also checked that the new xalan.jar and xerces.jar
:included the service provider configuration files, and that they were
:correct; everything looked okay.
:
:I haven't seen anyone else with this problem, so it seems unlikely
:that this
:is a problem with the xalan or xerces jars, but then again, the only thing
:that changed were the jars.  Does anyone have any suggestions for things to
:check that I might be doing wrong?
:
:Eric