I did not get it working with a WAR file, even though it probably should
work, since Orion even supports J2EE EAR files. Anyway, since I want to be
able to modify things and immediately see the results, I don't want to
package the web application into a WAR file. I also can't get it working in
Resin, which supports WAR files - again, it is probably a simple
configuration issue. I just thought somebody might have already tried this.
I tried it again in Tomcat (3.2.1), and basically everything seems to work
fine, but I get a lot of IOExceptions on the index page. On the first hit,
everything works fine, but when I refresh the page or follow some links and
then go back, I get the following error messages:
2001-01-18 11:46:43 - Ctx( /jetspeed ): IOException in: R( /jetspeed +
/images/jetspeed-logo.gif + null) Connection aborted by peer: socket write
error
2001-01-18 11:47:29 - Ctx( /jetspeed ): IOException in: R( /jetspeed +
/images/jetspeed-logo.gif + null) Connection aborted by peer: socket write
error
2001-01-18 11:47:29 - Ctx( /jetspeed ): IOException in: R( /jetspeed +
/css/default.css + null) Connection aborted by peer: socket write error
2001-01-18 11:47:30 - Ctx( /jetspeed ): IOException in: R( /jetspeed +
images/topics/jetspeed.gif + null) Connection aborted by peer: socket write
error
2001-01-18 11:47:30 - Ctx( /jetspeed ): IOException in: R( /jetspeed +
/images/jetspeed-powered.gif + null) Connection aborted by peer: socket
write error
Any ideas what could be causing this? Oh, I should mention that I am running
Tomcat 3.2.1 and the latest Jetspeed alpha version on Windows 2000.
-Mirko
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Dave Carlson
> Sent: Wednesday, January 17, 2001 8:40 AM
> To: JetSpeed
> Subject: Re: Orion Server
>
>
> From: <[EMAIL PROTECTED]>
> > If orion supports WAR files, you should be able to take the
> 1.3a1 binary
> WAR,
> > drop it in whatever appropriate directory and run...
> >
>
> Although, I still have frequent problems with the WAR servlet
> classpath and
> its separation from the primary server classpath. Each uses
> a different
> class loader, and vendors have different interpretations of
> this concept.
> I have not yet tried Jetspeed 1.3a1 on Allaire JRun, but with
> 1.2b I was
> forced to move all of the Jetspeed jar libraries into the
> main server /lib
> directory before it would run (I had created a WAR for the
> 1.2b release).
> Otherwise, the SAX interfaces were loaded from a JAR in the
> main server
> (not Xerces), and I had conflicts with the use of SAX by Xerces.jar in
> Jetspeed's WAR. Two class loaders are like ships passing in
> the night...
>
> However, 1.3a1 works great in Tomcat!
>
> Dave
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/[email protected]/>
> List Help?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
