Version of bsf.jar

Subjects

•	Home
•	Xalan extension functions
•	Fomatting question serializing DOM with pretty print
•	xalan with pull parser
•	Cannot find the declaration
•	Apache Xalan drop support to run on JRE 1 1 x
•	Why does Doctype change processing of a document
•	Node set to XML string via Java extensions in Xalan J: possible?
•	Templates/Transformers + thread safety???
•	Problem evaluating xpath with muliple prefix with different namespace
•	remove an arbitrary attribute from xsl output
•	Xalan3 XSLT 2 0 XPath 2 0 support?
•	Problem using compiled translets with Xalan !!
•	Xalan and jstl 1 1 problem with transform tag
•	NullPointer in DOM2DTM getLocalName
•	URIResolvers base parameter with xsltc and cascaded imports
•	Performance problem for Xalan J on intel dual core
•	Standard libraries in JAXP?
•	Serializing a DOM tree to XML file, customize entities replacement
•	Library Conflict Involving BCEL Library
•	A question on how users are using <xsl:message >
•	Kevin Cormier as a new Apache Xalan J committer
•	Struggling to iterate over tokenized string
•	Xalan count() trouble
•	Problem with recursive xpath
•	Error when switching to java 1 5
•	document( ' ')
•	Problem with Xalan2 7 0 transformation
•	cr/lf options
•	entity encoded XML
•	can xalan transform 2 xml using one xslt?
•	Xalan J JIRA defect review Monday October 16, 2006 from 2:00 to 3:30 pm ED
•	xsl transform with cdata section elements
•	xslt parameters not expanded
•	Weird behavior of XPath evaluate()
•	How to avoid <xsl:message > instruction prints stylesheet file informations ?
•	Cannot find SimpleTransform subdirectory after installing Xalan J
•	recover from document not found exceptions
•	jdk1 5 and Xalan jar differences?
•	Performance Issue
•	Error/Bug adding floating point numbers
•	XPathAPI: eval exp using nodes with default namespace
•	modifying xalan to output invalid XML
•	NullPointerException
•	mege two separate xml nodes into one
•	Is this a XALAN document identification bug?
•	is StylesheetRoot really java io Serializable ?
•	transform() fails for DOMSource but succeeds for StreamSource
•	Thoughts on Transformer parameter passing
•	HELP, Xalan and jstl 1 1 problem with transformer
•	Problem with XPath namespace axis?
•	string utils:replace deleting search string if replacement string is an HTML
•	help with enumeration values pls
•	xalan 2 5 1 vs 2 7 performance question
•	How to insert/update in XML document
•	HTML Serialization and Handling of Ampersands in HREF Attributes
•	XHTML link tag stripping
•	SystemId Unknown; Line #24; Column #49; java lang NullPointerException
•	xpath text() help
•	Apostrophe problem with xalan 2 7 0
•	How to set variables in XML document?

Links

Home

Oracle database error code ...

Version of bsf.jar

Version of bsf.jar

2003-04-08 - By Gary Gregory

Reply: 1 2 3 4 5

Karen,

You should log a bug with the BSF project such that the version is included
in future versions of the manifest.

Gary

-----Original Message-----
From: Karen Alexander [mailto:Karen.Alexander@(protected)]
Sent: Tuesday, April 08, 2003 11:23 AM
To: 'Gary Gregory'; 'xalan-j-users@(protected)'
Subject: RE: Version of bsf.jar

Thanks for your response.

The manifest only seems to have information about the version of ant that is
used. It doesn't have the version of the bsf jar itself.

Perhaps one of the developers can answer my question?

Thanks for your help,

- Karen

-----Original Message-----
From: Gary Gregory [mailto:ggregory@(protected)]
Sent: Monday, April 07, 2003 11:04 AM
To: 'xalan-j-users@(protected)'
Subject: RE: Version of bsf.jar

The jar's MANIFEST.MF file may contain version information.

GAryt

-----Original Message-----
From: Karen Alexander [mailto:Karen.Alexander@(protected)]
Sent: Monday, April 07, 2003 10:10 AM
To: 'xalan-j-users@(protected)'
Subject: Version of bsf.jar

Hi,

Is there a way to determine the version of the bsf.jar that comes with the
Xalan releases?

I have a customer that need to know the version of BSF.jar that was
distributed with Xalan 1.2.2

thanks,
- Karen

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">

<meta name=Generator content="Microsoft Word 10 (filtered)">
<title>Message</title>

<style>

</style>

</head>

<body lang=EN-US link=blue vlink=purple>

<div class=Section1>

Karen,

 

You should log a bug with the BSF project
such that the version is included in future versions of the manifest.

 

Gary

 

-----Original Message----- 
From: Karen Alexander
[mailto:Karen.Alexander@(protected)] 
Sent: Tuesday, April 08, 2003
11:23 AM 
To: 'Gary Gregory';
'xalan-j-users@(protected)' 
Subject: RE: Version of bsf.jar

 

<div>

Thanks for your response.  

</div>

<div>

The manifest only seems to have information about the version of
ant that is used.  It doesn't have the version of the bsf jar itself.

</div>

<div>

Perhaps one of the developers can answer my question?

</div>

<div>

Thanks for your help,

</div>

<div>

 - Karen

</div>

-----Original
Message----- 
From: Gary Gregory
[mailto:ggregory@(protected)] 
Sent: Monday, April 07, 2003 11:04
AM 
To: 'xalan-j-users@(protected)'
 
Subject: RE: Version of bsf.jar


The jar's MANIFEST.MF
file may contain version information.

 


GAryt

 

-----Original Message----- 
From: Karen Alexander
[mailto:Karen.Alexander@(protected)] 
Sent: Monday, April 07, 2003 10:10
AM 
To: 'xalan-j-users@(protected)'
 
Subject: Version of bsf.jar


 

<div>


Hi,

</div>

<div>


Is there a way to
determine the version of the bsf.jar that comes with the Xalan releases?


</div>

<div>


I have a customer that
need to know the version of BSF.jar that was distributed with Xalan 1.2.2

</div>

<div>


thanks, 
 - Karen 

</div>

<div>

 

</div>

</div>

</body>

</html>