You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Uli Mayring <ul...@denic.de> on 2000/07/28 17:44:49 UTC
Tomcat on MacOS problem
Hi folks,
I installed MRJ SDK 2.2 and MRJ runtime 2.2.2 and Tomcat3.1. I added all
the jars from Tomcat's lib directory (plus the cocoon jars) to JBindery's
classpath and included in the command section
org.apache.tomcat.startup.Tomcat with optional parameter startup.
So, I did everything as described by Mike Engelhart recently. But when I
launch the built Tomcat application a popup comes up and tells me that the
main class org.apache.tomcat.startup.Tomcat could not be found.
I even included a Tomcat.properties in the same directory as the Tomcat
app, which contains the classpath etc. again, but that didn't change
anything.
Trying the same properties file with the MRJ Application builder by
dragging it and the contents from Tomcat/lib to its icon was not
successful either. I got numerous Java Exceptions when building, most of
the complaining about bit-length in the ZIP files or something similar. So
perhaps the jars I downloaded from Tomcat are corrupt? How can I verify
that?
thanks for any help,
Ulrich
--
Ulrich Mayring
DENIC eG, Softwareentwicklung
Re: Tomcat on MacOS problem
Posted by Uli Mayring <ul...@denic.de>.
On Sat, 29 Jul 2000, Jesse Reynolds wrote:
> Check also that the .jar files have untared as binary files, not
> text. If you use stuffit expander to untar, then you need to tell it
> to handle .jar files as binary... I had this problem. Although I got
> around it by using the program suntar, which works a treat, before
> someone suggested adding the .jar - binary setting to stuffit.
I downloaded the ZIP archive, so there should be no problem.
I have set .jar in my Internet Config Panel as you described earlier,
anyway.
Ulrich
Re: Tomcat on MacOS problem
Posted by Mike Engelhart <me...@earthtrip.com>.
on 7/29/00 10:53 AM, Jesse Reynolds at lizst@va.com.au wrote:
> Check also that the .jar files have untared as binary files, not
> text. If you use stuffit expander to untar, then you need to tell it
> to handle .jar files as binary... I had this problem. Although I got
> around it by using the program suntar, which works a treat, before
> someone suggested adding the .jar - binary setting to stuffit.
>
> A way to check that the .jar file is sane, is to open it in Zipit,
> and check the validity of some of the class files within. I found
> that in particular my whole xerces.jar file was bad, and fixed it by
> untar'ing again with suntar.
>
> cheers
>
> jesse
Actually the best way to fix this I've found (so that you can continue using
Stuffit Expander) is to go into the Internet control panel and add .jar
files to it. Go to the Edit menu and select User Mode and make sure it's
selected to be at least Advanced. Then go to the Advanced tab in the
control panel and click on File Mapping and click the "Add..." button.
Then in the "Add Mapping" field, add ".jar" and for file type put "ZIP "
(space at the end is important) and "java" as the creator type and when the
dialog asking for a creator name comes up just put "java" again. Click on
"Show Advanced Options" and make sure that the checkboxes "Map Incoming"
and "Map Outgoing" are checked and that the default format is binary data.
Then click the Add button and close the internet control panel and save
changes.
This will cause the system to deal with .jar files the correct way.
Mike
Re: Tomcat on MacOS problem
Posted by Jesse Reynolds <li...@va.com.au>.
Check also that the .jar files have untared as binary files, not
text. If you use stuffit expander to untar, then you need to tell it
to handle .jar files as binary... I had this problem. Although I got
around it by using the program suntar, which works a treat, before
someone suggested adding the .jar - binary setting to stuffit.
A way to check that the .jar file is sane, is to open it in Zipit,
and check the validity of some of the class files within. I found
that in particular my whole xerces.jar file was bad, and fixed it by
untar'ing again with suntar.
cheers
jesse
At 11:09 -0500 28/7/00, Mike Engelhart wrote:
>on 7/28/00 10:44 AM, Uli Mayring at ulim@denic.de wrote:
>
>> Hi folks,
>>
>> I installed MRJ SDK 2.2 and MRJ runtime 2.2.2 and Tomcat3.1. I added all
>> the jars from Tomcat's lib directory (plus the cocoon jars) to JBindery's
>> classpath and included in the command section
>> org.apache.tomcat.startup.Tomcat with optional parameter startup.
>>
>> So, I did everything as described by Mike Engelhart recently. But when I
>> launch the built Tomcat application a popup comes up and tells me that the
>> main class org.apache.tomcat.startup.Tomcat could not be found.
>>
>> I even included a Tomcat.properties in the same directory as the Tomcat
>> app, which contains the classpath etc. again, but that didn't change
>> anything.
>>
>> Trying the same properties file with the MRJ Application builder by
>> dragging it and the contents from Tomcat/lib to its icon was not
>> successful either. I got numerous Java Exceptions when building, most of
>> the complaining about bit-length in the ZIP files or something similar. So
>> perhaps the jars I downloaded from Tomcat are corrupt? How can I verify
>> that?
>>
>> thanks for any help,
>>
>> Ulrich
>
>Strange...
>I just downloaded a fresh Tomcat 3.1 and unzipped/untarred it and went into
>the lib directory and dragged and dropped the following:
>jasper.jar
>servlet.jar
>xml.jar
>webserver.jar
>
>onto the JBindery application.
>
>Then I put:
>org.apache.tomcat.startup.Tomcat
>
>into the "Class Name" field
>
>and put the word "startup" into the "Optional Parameters" field and saved
>it as an application.
>
>Double-clicking it works just fine. Try it only with those jar files. You
>don't need ant.jar because you're not building anything with it. Also try
>getting Tomcat running before you try adding all the Cocoon specific
>libraries.
>
>Mike
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
>For additional commands, e-mail: cocoon-users-help@xml.apache.org
--
--
Jesse Reynolds - Virtual Artists Pty Ltd - http://www.va.com.au
Email: jesse (at) va.com.au - http://virtual.artists
Re: Tomcat on MacOS problem
Posted by Mike Engelhart <me...@earthtrip.com>.
on 7/28/00 10:44 AM, Uli Mayring at ulim@denic.de wrote:
> Hi folks,
>
> I installed MRJ SDK 2.2 and MRJ runtime 2.2.2 and Tomcat3.1. I added all
> the jars from Tomcat's lib directory (plus the cocoon jars) to JBindery's
> classpath and included in the command section
> org.apache.tomcat.startup.Tomcat with optional parameter startup.
>
> So, I did everything as described by Mike Engelhart recently. But when I
> launch the built Tomcat application a popup comes up and tells me that the
> main class org.apache.tomcat.startup.Tomcat could not be found.
>
> I even included a Tomcat.properties in the same directory as the Tomcat
> app, which contains the classpath etc. again, but that didn't change
> anything.
>
> Trying the same properties file with the MRJ Application builder by
> dragging it and the contents from Tomcat/lib to its icon was not
> successful either. I got numerous Java Exceptions when building, most of
> the complaining about bit-length in the ZIP files or something similar. So
> perhaps the jars I downloaded from Tomcat are corrupt? How can I verify
> that?
>
> thanks for any help,
>
> Ulrich
Strange...
I just downloaded a fresh Tomcat 3.1 and unzipped/untarred it and went into
the lib directory and dragged and dropped the following:
jasper.jar
servlet.jar
xml.jar
webserver.jar
onto the JBindery application.
Then I put:
org.apache.tomcat.startup.Tomcat
into the "Class Name" field
and put the word "startup" into the "Optional Parameters" field and saved
it as an application.
Double-clicking it works just fine. Try it only with those jar files. You
don't need ant.jar because you're not building anything with it. Also try
getting Tomcat running before you try adding all the Cocoon specific
libraries.
Mike