indeed your right:
[EMAIL PROTECTED]:/opt/j2sdk1.4.2_06/bin] ./javap org.apache.xalan.xslt.Process
Compiled from "Process.java"
public class org.apache.xalan.xslt.Process extends java.lang.Object{
public org.apache.xalan.xslt.Process();
static void doExit(int);
public static void main(java.lang.String[]);
protected static void printArgOptions(java.util.ResourceBundle);
}
what does underscore mean ?
I guess I am still confused about their release notes. If they didn't
want us to use the command line options, it should be stated
somewhere.
If anyone can shed light on that it would be great.
thanks Kevin for clearing things up a bit more. I will try adding the
jars and see. I think I'll use the "endoresed" method mentioned in the
documentation for xalan as the doc says just adding them to CLASSPATH
wont work:
here..
http://xml.apache.org/xalan-j/faq.html#environmentcheck
On 6/1/06, Kevin Cormier <[EMAIL PROTECTED]> wrote:
Hi again,
On 6/1/06, John Lukar <[EMAIL PROTECTED]> wrote:
> My underestanding was that the xalan, xerces and jaxp are all roled
> into the JDK 1.5 and hence no need for me to add them to the
> classpath.
Ah, I see. In 1.5, if I run "javap
com/sun/org/apache/xalan/internal/xslt/Process" I get the
following output:
Compiled from "Process.java"
public class
com.sun.org.apache.xalan.internal.xslt.Process extends
java.lang.Object{
public
com.sun.org.apache.xalan.internal.xslt.Process();
protected static void printArgOptions(java.util.ResourceBundle);
public static void _main(java.lang.String[]);
static void doExit(int);
}
Note how there's an underscore in front of the main() method. I'm guessing
that if you try this with your 1.4 version of the JDK (which I don't have
installed) that it won't be there.
Seems like they want you to be able to access Xalan through the JAXP API,
but they do not want you to be able to use the extras in Xalan like the
command line applications.
The included version is out-of-date anyways, so it might be best just to
download the latest version from the Xalan site.
-Kevin
