× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Paul,

I thought Tomcat had a setting that would let you share the session data
across contexts?  Just a thought, might help.

Mark



      To:   "'Websphere Development Studio Client for iSeries'"
<wdsci-l@xxxxxxxxxxxx>
      cc:
      bcc:
      Subject:    RE: RE: [WDSCI-L] Re: Re: EAR/WAR Deployment
"Paul Nicolay" <Paul.Nicolay@xxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
07/08/2003 10:31 PM ZE2
Please respond to Websphere Development Studio Client for iSeries
<font size=-1></font>





















Hi Mark,

I have a little problem with the combination of Tomcat (guess WAS will be
no
different) and Apache. Since I need all my Tomcat applications under the
same context (talking about how such a thing can influence my external web
structure, but otherwise I can't share a session between them) I was trying
to solve the issue that I want different directories being used by the
outside world (just consider that I have a lot of other sites linking to
/test1 and /test2... which I don't want to change).

As a test I tried to map /test1 and /test2 to my Tomcat context called
/mycontext with the following config...

RewriteRule ^/test1(.*) /mycontext$1 [R]
RewriteRule ^/test2(.*) /mycontext$1 [R]

... which works fine, apart from the issue that it forces an external
redirect (ie. status 302, resource has moved).  First of all this exposes
my
context (not a big deal), but more important it is a round trip via the
client which is useless.

I tried a few other flags on the RewriteRule, but none of them seems to
work. So far I haven't found a diagram neither that shows when what is
done,
and where the Tomcat plugin traps the requests.   Basic issue is that I
need to change the URL before Tomcat jumps in.

I hope I'm not getting off-topic with this, but it all demonstrates how
directory structures influence application design, and even how you present
your application to the outside world.

Kind regards,
Paul

-----Original Message-----
From: wdsci-l-bounces+paul.nicolay=pandora.be@xxxxxxxxxxxx
[mailto:wdsci-l-bounces+paul.nicolay=pandora.be@xxxxxxxxxxxx] On Behalf Of
Mark Phippard
Sent: dinsdag 8 juli 2003 17:43
To: Websphere Development Studio Client for iSeries
Subject: Re: RE: [WDSCI-L] Re: Re: EAR/WAR Deployment


Paul,

Can you provide some examples?

I would think that if you could isolate the J2EE part under its own
context root then it should not effect the structure of the rest of the
app.

Mark

_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.



_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.







As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.