David Newton wrote:Ugh.
Indeed. This is stupid, but gotta do.
David Newton wrote:
In any case, I don't see how session is "out of the question"--just because there's no entry point doesn't mean that it can't be captured a single time then stored in session,
Yes, you're right. In reality I'll put the parameter to HttpSession when first encountered but I need to keep it in the URL also. This is needed because the URL must be usable as a link for other users also. E.g. /fooApp/showProduct?id=123&db=foo
David Newton wrote:
perhaps using a filter or a custom request processor to put it back into the request if that's *really* necessary. I can't think of why it would be.
In any case, I'd look into a filter or a custom request processor.
Thanks, I'll check it out.
To clarify things little more, the problem is that a single .war on a single server (
Tomcat 6.x) serves multiple stores. Stores have their own databases with products and content etc. So far the app has been password protected, thus providing the "entrypoint" for stores and the problem above has not existed.
In the future the app must be "open" and the problem is how to identify the store in the URL.
- Lari