On Sat, 2007-12-29 at 16:40 -0800, Knute Johnson wrote:
> >On Sat, 2007-12-29 at 15:04 -0800, Knute Johnson wrote:
> >> >> Actually, Sun's Java is very easy to install and configure on
both 32
> >> >> and 64 bit. The only real problem is the lack of a 64bit browser
> >> >> plugin and as far as I can tell nspluginwrapper doesn't work
with the
> >> >> 32bit version.
> >> >>
> >> >> I did a short page on how to set up Sun's Java on F8;
> >> >>
> >> >>
http://www.knutejohnson.com/sun-java-on-F8.html
> >> >----
> >> >I agree with the following notations...
> >> >
> >> >you should probably install the compat-libstdc++-33 PRIOR to installing
> >> >the Sun JRE/JDK shouldn't you? If you do a 'yum localinstall
> >> >jre/jdk-VERSION' it will automatically install requisite packages
such
> >> >as the compaat-libstdc++-33
> >>
> >> I works if you do it after, I never tried before.
> >>
> >> >Your notations don't provide methodologies for setting
> >> >JAVA_HOME/JRE_HOME/CLASSPATH environment variables which are necessary
> >> >for virtually everything other than the java web browser plugin. This
of
> >> >course was the crux of the OP - java's bin isn't installed in a
users
> >> >$PATH.
> >>
> >> If you use the JPackage none of that is required. In fact setting
> >> the CLASSPATH is almost never required in any installation.
> >----
> >docbook-XSL for xalan/xerces/fop etc. Otherwise, you have to locate them
> >with each call.
> >
> >Probably others too...
>
> Sorry, I have no idea what that means.
----
that means that executing a java command such as this...
java org.apache.xalan.xslt.Process \
-out some_output_file.html \
-in some_input_file.xml \
-xsl /var/www/html/docbook/docbook.xsl \
-param use.extentions 1
or this...
java \
-Djavax.xml.parsers.DocumentBuilderFactory=\
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl \
-Djavax.xml.parsers.SAXParserFactory=\
org.apache.xerces.jaxp.SAXParserFactoryImpl \
com.icl.saxon.StyleSheet \
-o myfile.html \
some_input_file.xml \
/var/www/html/docbook/docbook.xsl \
use.extensions=1
only works if the full path to xalan.jar/xerces.jar/saxon.jar are
located in $CLASSPATH environmental variable, otherwise, you have to
spell it out longhand with path within your usage command each time you
invoke it. It is Java's equivalent to the shell $PATH variable.
As you start to amass jar files, it can be really useful to manage them
with a CLASSPATH declaration. I'm presuming that is what most
applications such as a Tomcat or Alfreso are going to do (I gather they
build it on the fly based upon jar files in particular directories).
Could be and in the case you cite using the enviroment variable makes
a lot of sense. Users that are not that experienced seem to have
more trouble with the environment variable than without it. It is
one of the tricky parts of Java.
--
Knute Johnson
Molon Labe...