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.
Error when switching to java 1.5

Error when switching to java 1.5

2006-10-26       - By Erin Harris
Reply:     1     2     3     4     5  

Hi,

I couldn't get this to fail when running from the command line:

java -Djava.endorsed.dirs=d:\xalan-j_2_7_0 org.apache.xalan.xslt.Process
-xsl test.xsl -in test.xml

Does it fail for you when running from the command line as well or only
when running within Tomcat?  Are you using the Tomcat endorsed directory (
<Tomcat_Home>\common\endorsed )?

Did you get a stack trace with the exception?


Thanks.


Erin Harris





footh <footh@(protected)>
25/10/2006 05:47 PM

To
xalan-j-users@(protected)
cc

Subject
Error when switching to java 1.5






I am using an identity template that removes
namespaces in a Cocoon application that runs under
Tomcat.  Previously, I was using Java 1.4.2 but once I
switched to Java 1.5 I receive a null pointer
TransformerException.  Following is the identity
template that matches all nodes.  The error occurs on
the "apply-templates" tag.  On the "select" attribute,
the presence of the "@*" symbol causes the error.  If
I remove it, everything is fine.  However, then
attributes of nodes are not rendered.  Has anyone
encountered this problem before?  Any suggestions?

 <xsl:template match="*">
  <xsl:element name="{name()}"
namespace="{namespace-uri()}">
    <xsl:apply-templates select="@*|node()" />
  </xsl:element>
 </xsl:template>

I've tried throwing in different versions of Xalan
jars  to no avail.  Currently, I'm using 2.7.0.

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com



<br><font size=2 face="sans-serif">Hi,</font>
<br>
<br><font size=2 face="sans-serif">I couldn't get this to fail when running
from the command line:</font>
<br>
<br><font size=2 face="Courier">java -Djava.endorsed.dirs=d:\xalan-j_2_7_0
org.apache.xalan.xslt.Process -xsl test.xsl -in test.xml</font>
<br><font size=2 face="sans-serif"><br>
Does it fail for you when running from the command line as well or only
when running within Tomcat? &nbsp;Are you using the Tomcat endorsed directory
(</font><font size=2 face="Arial">&lt;Tomcat_Home&gt;\common\endorsed</font>
<font size=3>
</font><font size=2 face="sans-serif">)?</font>
<br>
<br><font size=2 face="sans-serif">Did you get a stack trace with the exception
?</font>
<br>
<br>
<br><font size=2 face="sans-serif">Thanks.</font>
<br>
<br><font size=2 face="sans-serif"><br>
Erin Harris<br>
<br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>footh &lt;footh@(protected)&gt;<
/b>
</font>
<p><font size=1 face="sans-serif">25/10/2006 05:47 PM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">xalan-j-users@(protected)</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Error when switching to java 1.5</font><
/table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>I am using an identity template that removes<br>
namespaces in a Cocoon application that runs under<br>
Tomcat. &nbsp;Previously, I was using Java 1.4.2 but once I<br>
switched to Java 1.5 I receive a null pointer<br>
TransformerException. &nbsp;Following is the identity<br>
template that matches all nodes. &nbsp;The error occurs on<br>
the &quot;apply-templates&quot; tag. &nbsp;On the &quot;select&quot; attribute,
<br>
the presence of the &quot;@*&quot; symbol causes the error. &nbsp;If<br>
I remove it, everything is fine. &nbsp;However, then<br>
attributes of nodes are not rendered. &nbsp;Has anyone<br>
encountered this problem before? &nbsp;Any suggestions? &nbsp;<br>
<br>
&nbsp;&lt;xsl:template match=&quot;*&quot;&gt;<br>
&nbsp; &lt;xsl:element name=&quot;{name()}&quot;<br>
namespace=&quot;{namespace-uri()}&quot;&gt;<br>
&nbsp; &nbsp; &lt;xsl:apply-templates select=&quot;@*|node()&quot; /&gt;<br>
&nbsp; &lt;/xsl:element&gt;<br>
&nbsp;&lt;/xsl:template&gt;<br>
<br>
I've tried throwing in different versions of Xalan<br>
jars &nbsp;to no avail. &nbsp;Currently, I'm using 2.7.0.<br>
<br>
__________________________________________________<br>
Do You Yahoo!?<br>
Tired of spam? &nbsp;Yahoo! Mail has the best spam protection around <br>
http://mail.yahoo.com <br>
</font></tt>
<br>