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 ...
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Endorsed Standards Override (was RE: redirect extension uri problem)

Endorsed Standards Override (was RE: redirect extension uri problem)

2003-02-26       - By Slinkster

Thanks to Morris and Cyril for your help. I've got everything working with 2.4
.1 now.

To anybody who may use Sun's endorsed standards override mechanism with JDK 1.4
.1, you have to place the jars in JAVA_HOME/jre/lib/endorsed. Even if your path
points to JAVA_HOME/bin, the JDK 1.4.1 is configured by default only to check
for overrides in the jre directory. [I screwed this up several times]

Cheers,

JWS

-----Original Message-----
From: Cyril Bouteille [mailto:cbouteille@(protected)]
Sent: Wednesday, February 26, 2003 3:36 PM
To: Slinkster
Cc: mkwan@(protected); xalan-j-users@(protected)
Subject: Re: redirect extension uri problem


You can add the -Xbootclasspath java command line option to prepend the
2.4.1 xalan.jar, xercesImpl.jar, and xml-apis.jar to the boot class path
and override the version embedded in the jdk.

See http://xml.apache.org/xalan-j/faq.html#faq-N100C3 for more info.

jsolinsky@(protected) wrote:
> I have Xalan 2.4.1 in my path, but I am using the Sun JDK 1.4.1. Based on
your message, I infer that classes packaged with the JDK are being used in lieu
of the Xalan on the classpath.
>
> What is the recommended method for getting JDK 1.4.1 to use Xalan 2.4.1?
>
> Also, will Xalan 2.4.1 still recognize the older extension?
>
> Thanks,
>
> JWS
>
> -----Original Message-----
> From: mkwan@(protected) [mailto:mkwan@(protected)]
> Sent: Wednesday, February 26, 2003 9:50 AM
> To: Slinkster
> Cc: xalan-j-users@(protected)
> Subject: Re: redirect extension uri problem
>
>
> The documentation was updated in accordance with Xalan 2.4.1. The namespace
> for the redirect extension was changed in Xalan 2.4.1. If you use an older
> Xalan version, you will see the problem.
>
> Morris Kwan
> XSLT Development
> IBM Toronto Lab
> Tel: (905)413-3729
> Email: mkwan@(protected)
>
>
>
>
>                       "Slinkster"
>                       <jsolinsky@(protected)        To:       <xalan-j-users@(protected)
.apache.org>
>                       y-labs.com>              cc:       "Slinkster"
<jsolinsky@(protected)>
>                                                Subject:  redirect extension
uri problem
>                       02/25/2003 06:06
>                       PM
>
>
>
>
>
> I recently found that the redirect extension does not work when I use the
> documented:
>
> xmlns:redirect="http://xml.apache.org/xalan/redirect"
>
> but does work when I use:
>
> xmlns:redirect="org.apache.xalan.lib.Redirect"
>
> Is this because:
>
> A: The documentation is out of date
> B: Because of Sun's "bundling" of xalan in the 1.4.1 JDK or
> C: Something else
>
> If B, is there a simple way to use 1.4.1 while using the Xalan
> implementation that is on my classpath?
>
> Thanks,
>
> JWS
>
>


--
Cyril Bouteille
Enterprise Java Architect
Hotwire
333 Market Street Suite 100
San Francisco, CA 94105

------------------------------------------------------------------------
Take the Hotwire Travel Challenge(sm)!
Check a Hotwire Hot-Fare(sm) at www.hotwire.com <http://www.hotwire.com>
------------------------------------------------------------------------
This e-mail message contains information that is confidential, may be
protected by the attorney/client or other applicable privileges, and may
constitute non-public information. It is intended to be conveyed only to
the designated recipient(s). If you are not an intended recipient of
this message, please notify the sender at 415-343-8405. Unauthorized use
dissemination, distribution, or reproduction of this message is strictly
prohibited and may be unlawful.