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.
Xalan 2.7 compilation

Xalan 2.7 compilation

2006-05-25       - By Joaquín Sánchez Jiménez

Hi all:

I am packaging xalan.jar with pack200 (with rsa signature). When verifing
extracted (and signed) xalan2.7.jar from pack.gz file jarsigner shows something
like this:

jarsigner: java.lang.SecurityException: SHA1 digest error for org/apache/xalan
/xsltc/compiler/ApplyImports.class

In fact there are some package that cannot be verified, so I must use --pass
-file option to exclude this packages from compression.

Exluding this packages and classes from pack200 I can use xalan2.7.jar.pack.gz
file:

  org/apache/xalan/templates
  org/apache/xalan/trace
  org/apache/xalan/transformer
  org/apache/xalan/Version.class
  org/apache/xalan/xslt
  org/apache/xalan/xsltc/cmdline
  org/apache/xalan/xsltc/compiler


What javac version/manufacturer was used to compile and make xalan2.7.jar? Is
there any compilation attribute that may cause the Packer to malfunction?

Thanks.

Bye.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1528" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hi all:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>I am packaging xalan.jar with pack200 (with rsa
signature). When verifing extracted (and signed) xalan2.7.jar from pack.gz file
jarsigner shows something like this:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>jarsigner: java.lang.SecurityException: SHA1
digest
error for org/apache/xalan/xsltc/compiler/ApplyImports.class</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>In fact there are some package that cannot be
verified, so I must use --pass-file option to exclude this packages from
compression.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Exluding this packages and classes from pack200 I
can use xalan2.7.jar.pack.gz file:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial
size=2>&nbsp;&nbsp;&nbsp;org/apache/xalan/templates<BR>&nbsp;&nbsp;&nbsp;org
/apache/xalan/trace<BR>&nbsp;&nbsp;&nbsp;org/apache/xalan/transformer<BR>&nbsp;
&nbsp;&nbsp;org/apache/xalan/Version.class</FONT></DIV>
<DIV><FONT face=Arial
size=2>&nbsp;&nbsp;&nbsp;org/apache/xalan/xslt<BR>&nbsp;&nbsp;&nbsp;org/apache
/xalan/xsltc/cmdline<BR>&nbsp;&nbsp;&nbsp;org/apache/xalan/xsltc/compiler</FONT>
</DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>&nbsp;</DIV>
<DIV>What javac version/manufacturer was used to compile and make xalan2.7.jar?
Is there any compilation attribute that may cause the Packer to
malfunction?<BR></DIV>
<DIV>Thanks.</DIV></FONT>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Bye.</FONT></DIV></BODY></HTML>