ingo schuster wrote:
>
> I tested the WAR support with Websphere 3.52 and it worked (almost...).
>
> Two things:
> * Websphere has no generic way of invoking servlets (unless you install a
> servlet invoker servlet which is not created by our WAR).
> This means that the URL /servlet/jetspeed doesn't work. Raphael, can you
> map the Turbine servlet to the webpath "/jetspeed" ? Looks better anyway...
> The addition in the web.xml should be something like:
>
> <servlet-mapping>
> <servlet-name>
> jetspeed
> </servlet-name>
> <url-pattern>
> /jetspeed/*
> </url-pattern>
> </servlet-mapping>
>
I agree on the principale, but that would create URLs like:
http://localhost:8080/jetspeed/jetspeed/screen/Home
isn't it ?
What about using this ?
http://localhost:8080/jetspeed/portal/screen/Home
using this web.xml fragment
<servlet-mapping>
<servlet-name>
jetspeed
</servlet-name>
<url-pattern>
/portal/*
</url-pattern>
</servlet-mapping>
> * With Websphere, you have to make sure that xerces and xalan are first in
> the classpath. This is done by setting on the "server/general" panel the
> "command line arguments" to:
> "-classpath D:\WebSphere\AppServer\classes; <path to xerces-1.1.3.jar>;
> <path to xalan_1_1_D01.jar>"
>
> I think that's something for the documentation (or the FAQ/instalation
> problems list).
>
Yes, I don't see how we can fix it.
--
Rapha�l Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Services Manager / Paris
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
