Thanks for idea of eliminating chance of a struts problem.
> Do you mean to say, when you make a request > "context1/location/page.jsp" and > "context2/location/page.jsp" you get the same page even if you update > context1 and not context2? Yes. This is the way it works. This is definetly a BEA WebLogig 6.2 problem. I configured test.jsp pages to both applications. "context1/location/test.jsp" and "context2/location/test.jsp". And added entries to web.xml defining test.jsp as servlet with pattern *.test, so every request ending with .test would be directed for test.jsp. What happened was that I modified test.jsp file in both applications to ensure recompiling. Then started up WebLogic. Then I accessed "context1/location/test.test" with browser, resulting WebLogic to compile test.jsp. After that when I accessed "context2/location/test.test" result was the one produced by "context1/location/test.jsp". So the one that is compiled first after startup or deploying, will be used to produce response. This apperars in both cases with startup and re-deploying, so I think this is actually related to application deploying which is also part of startup. At this point no matter how many times I try to refresh browser and no matter web context I access, I receive result of the first compiled jsp page. When I modify or touch "context2/location/test.jsp" so that modified timestamp changes resulting weblogic to compile jsp page, and after that access "context2/location/test.test" result is OK, produced by "context2/location/test.jsp". After many tests it is obvious that WebLogic works right when first page is compiled and after that the second will be modified to forse re-compiling. Now both URL's "context1/location/test.test" and "context2/location/test.test" produce their own content. Problem appears when application is deployed and JSP files are modified, resulting only first JSP accessed (compiled) to produce content for both web applications "context2/location/test.test". Kind regards, Aki > -----Original Message----- > From: Alex Paransky [mailto:[EMAIL PROTECTED]] > Sent: 21. tammikuuta 2002 22:15 > To: Struts Users Mailing List > Cc: Salonen, Aki > Subject: RE: Struts and multiple Web applications on same application > server > > > Do you mean to say, when you make a request > "context1/location/page.jsp" and > "context2/location/page.jsp" you get the same page even if you update > context1 and not context2? > > Seems like a server problem to me. > > You should be able to remove struts from the equation by > creating a simple > .jsp page without using any struts tags. Besides, I don't > think that the > struts servlet gets involved with every request you make. > Only requires > that have the mapping specified to map to the servlet in > web.xml (usually > something with the .do) extension get mapped to the servlet > (I could be > wrong, I have not used it for too long). > > -AP_ > > -----Original Message----- > From: Salonen, Aki [mailto:[EMAIL PROTECTED]] > Sent: Monday, January 21, 2002 2:09 AM > To: '[EMAIL PROTECTED]' > Subject: Struts and multiple Web applications on same > application server > > > Hello, > > We have been facing problems when using > struts with multiple enterprise applications. > > It seems that struts supports only one > struts application on same application server. > > Application server we are using is BEA WebLogic 6.2 SP2. > > Scenario is as described: > One enterprise application containing for EJB:s providing > business logics. > Two enterprise applications containg two distinct user interfaces > for business logics. > > We use same action servlet classes in both web applications, > inherited from Struts ActionServlet. > > Web application context roots are of course different, but > relative URL's used are same for both web applications. > So web.xml and struts-config.xml are exact copies. > > Both web applications have own physical copies of all jars used. > > If I have understood right, two distinct enterprise > applications should > have no knowledge of each other, so there should be own > instaces of struts > for each enterprise application. > > What happens is that server returns responses (JSP generated pages), > like there would be only one web application. > Also JSP-page result returned is the one from that web > application that has > latest modifed JSP page. > > It seems that application server does not distinct calls to different > web applications, but serves pages as if there would be only > one "mixed" web application. > > > Is this a struts or application server related issue? > > I know that struts does not support multiple action servlets. > > Has somebody faced similar problems or does someone know what > this all is > about? > > I can provide more details about if needed. > > > Kind regards, > > Aki > > > > ______________________________________________________________________ > Aki Salonen > Wincor Nixdorf Oy > System Analyst > web: http://www.wincor-nixdorf.com > > -- > To unsubscribe, e-mail: > <mailto:[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]>
