Hi, Pid! How are you? As I said, we now have a working solution, currently in tests, but so far so good.
Nevertheless this is always a good exercice to better understand the inner workings of our fellow Tom, the cat! Cheers! On 7/13/09, Pid <p...@pidster.com> wrote: > On 13/7/09 20:51, Ivo Silva wrote: >> Hi again, Christopher! >> >> Yes, but that is the last resort! >> >> We are still testing this approach but all is working as expected. >> The main reason to adopt this is to provide the possibility to deploy >> the legacy application in a portal environment (as a portlet) and to >> allow instatiation whitout requiring the deployment of new portlet for >> each instance. > > I hate to say this, but you'll soon be approaching the point where you > might as well have rewritten a (or, the URL) portion of the legacy app > to cope with the new use case, given the time you're expending trying to > solve a problem with two conflicting requirements. > > p > > >> Best regards! >> >> On 7/13/09, Christopher Schultz<ch...@christopherschultz.net> wrote: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> Ivo, >>> >>> On 7/13/2009 2:28 PM, Ivo Silva wrote: >>>> I cannot use a request parameter because the "legacy" application is >>>> inside an iframe. >>>> If I passed it as a request parameter in the iframe it would only work >>>> the first time, because once you click a link inside the iframe the >>>> parameter wouldn't be there. >>> Hmm... what about deploying a separate application into a sub-URI of >>> your main application. Something like this: >>> >>> mainapp.war -> /mainApp >>> legacy.war -> /mainApp/X >>> legacy.war -> /mainApp/Y >>> legacy.war -> /mainApp/Z >>> >>> This will actually give you separate sessions and getContextPath will >>> always work correctly, even when called from the legacy webapp. >>> >>> - -chris >>> -----BEGIN PGP SIGNATURE----- >>> Version: GnuPG v1.4.9 (MingW32) >>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ >>> >>> iEYEARECAAYFAkpbhAkACgkQ9CaO5/Lv0PAdJQCfdEJuPGVinHBl76jaQA9bNaRV >>> nPQAn0R2Ip3/S19j5Xyoa4lyA0c0Y/Gz >>> =2hKX >>> -----END PGP SIGNATURE----- >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >>> For additional commands, e-mail: users-h...@tomcat.apache.org >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
