At 13:21 2000-12-21, [EMAIL PROTECTED] wrote:
>ingo schuster wrote:
> >
> > At 19:01 2000-12-20, [EMAIL PROTECTED] wrote:
> > >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 ?
> >
> > No, it is a extra mechanism that allows you to adress jetspeed under
> > http://localhost:8080/servlet/jetspeed. If the "URI-Root" starts with
> > "servlet", Tomcat tries to find a servlet ith the name that follows
> > /servlet/. If you define the mapping I proposed above, the URL is (for both
> > Tomcat and Websphere):
> >
> > http://localhost:8080/jetspeed/
> >
> > No "servlet" needed any more! I checked it - it works. The
> > <servlet-mapping> section has to be outside the <servlet> section.
> >
>
>It doesn't work that way under Tomcat. The uri-mapping is always
>pefixed by the webapp name, defining your mapping allows this
>URL to be mapped to the servlet:
>
>http://localhost:8080/jetspeed/jetspeed/*
>
>What you're saying is that under Webspher it allows
>
>http://localhost:8080/jetspeed/ to be used. Is that really the case ?
>
>How can you then retrieve the documents that are located inside the webapp
>like http://localhost:8080/jetspeed/images/max.gif ?
>
>I greatly confused by Websphere way of doing this...
Ok, no I get the point of misunderstanding! I was talking of a setup where
the wabapp root is set to "/" in this case with my mapping the jetspeed URL is
http://localhost:8080/jetspeed/
and the image would be retrieved as
http://localhost:8080/images/max.gif
If you webappname is jetspeed, then you're right, the path would be
http://localhost:8080/jetspeed/jetspeed. Not nice, true.But
"/servlet/jetspeed" is not so nice either... What about a different
mapping, e.g. portal/* ? Then (with a webapp called "jetspeed") we had
following links.
The Portal Home page: http://localhost:8080/jetspeed/portal
The image: http://localhost:8080/jetspeed/images.max.gif
You see, my point is: without a <servlet-mapping> the installation requires
manual configuration on websphere, so I would really want *some* mapping. I
don't care which actual name.
ingo.
>--
>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]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
