|
Quick Lists
|
|
Bug ID:
|
4740355
|
|
Votes
|
0
|
|
Synopsis
|
Pkg renaming in J2SE (Mantis)
|
|
Category
|
jaxp:other
|
|
Reported Against
|
hopper
|
|
Release Fixed
|
1.5(tiger-beta)
|
|
State
|
10-Fix Delivered,
Verified,
request for enhancement
|
|
Priority:
|
3-Medium
|
|
Related Bugs
|
|
|
Submit Date
|
02-SEP-2002
|
|
Description
|
To avoid the confusion btw SUN shipped vs open source @ customer --latest and greatest-- code base. It was decided to rename the pkges in J2SE-Mantis ( plus J2EE and other products).
|
|
Work Around
|
N/A
|
|
Evaluation
|
In J2SE (Mantis), we need to rename the pkging of parser (Xerces instead of Crimson) and transformation engine(s) (Xalan/XSLTC).
|
|
Comments
|
Submitted On 08-NOV-2006
dirk.reinhold@heidelberg.com
When I invoke XSLT from the Windows Command Line with "java.exe org.apache.xalan.xslt.Process -IN OldFile.xml -XSL StyleSheet.xsl -OUT NewFile.xml" it worked fine with JRE1.4.
Then I installed JRE1.5.0_09. The class "org.apache.xalan.xslt.Process" was moved to "com.sun.org.apache.xalan.internal.xslt.Process". But when I call it with "java.exe com.sun.org.apache.xalan.internal.xslt.Process -IN OldFile.xml -XSL StyleSheet.xsl -OUT NewFile.xml" I get the error "Exception in thread "main" java.lang.NoSuchMethodError: main". When I look into the Process class there is no "main", but a "public static void _main(String argv[])".
The "JAXP Compatibility Guide for the J2SE Platform, versions 1.4 and 1.5" on "http://java.sun.com/webservices/docs/1.6/jaxp/JAXP-Compatibility_150.html" chapter "Invoking XSLT from the Command Line" claims it should work.
Is there no more chance to invoke XSLT from the Windows Command Line? Why is "main" renamed to "_main"? Is the documentation wrong or is this a bug?
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
