Jetspeed works great with Tomcat 4 (Catalina)
Been using it for a long time now.
Whats the problem?

> your server. The theory should be the software can be made to 
> work with 
> the server, not visa versa... anyway..

Im not sure if I agree with that statement. 
Both the application server and the servlet must conform to a contract:
the servlet api standard.
Could you please explain how Jetspeed is breaking this contract?
AFAIK, we are doing our part in following the standard servlet api.

The goal is "write once deploy anywhere"
Minor problems come in since the spec is open to interpretation by
application servers.
The differences in interpretation is where the problems begin.
Overall though, the problems are usually relatively minor.

Ensuring that it works on Tomcat, the ref.impl., doesn't guarantee it
will work straight from the war elsewhere.
Tomcat is just another interpretation of the spec.
One problem is that Jetspeed writes to the db, log files, and psml all
inside the war.
What happens if the war isn't expanded to the file system by the
app.server?
>From what I can understand from the spec., expanding to the file system
is optional.


> -----Original Message-----
> From: todd tredeau [mailto:[EMAIL PROTECTED]] 
> Sent: Wednesday, February 20, 2002 7:02 PM
> To: [EMAIL PROTECTED]
> Subject: Jetspeed and Tomcat 4
> 
> 
> I want to use Jetspeed with Tomcat 4.02 and JVM 1.3.1. I 
> don't want to 
> modify the "standard" Tomcat. I don't think you should have to modify 
> your server. The theory should be the software can be made to 
> work with 
> the server, not visa versa... anyway..
> 
> Q: Has anyone managed to get Jetspeed working with TC4
> Q: What modifications or build procedure to do this.
> 
> greetings
> 
> todd
> http://www.wiserlabz.com
> collaborative effort to promote Novell and Open Source Solutions
> 
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:jetspeed-user-> [EMAIL PROTECTED]>
> For 
> additional commands, 
> e-mail: <mailto:[EMAIL PROTECTED]>
> 
> 



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to