Hi Farrukh,
On 26/06/2010, at 2:05 PM, Farrukh Ijaz wrote:
I don't know why installPatches() didn't bring the change. Although I'm using Wonder's latest stable release so the change mentioned in the WONDER-389 should be reflected.
So are you using WO5.3.3 or WO5.4.3?
Well, let's confirm a few things first:
@Override
public WOResponse dispatchRequest(WORequest request) {
LOG.warn("worequest class:" + request.getClass().getName());
LOG.warn("wocontext class:" + request.context().getClass().getName());
...
}
What do you get?
However, I did my work around and thought to share with you as I found it to be flexible and dynamic and perhaps wonder team could implement something like this. <...snip custom application code...>
No. That's custom code. See below.
And defined following rewrite rules:
RewriteRule ^/app/(.*)$ /Application/WebObjects/MyApplication.woa/$1?_alias=/app [L,PT,QSA]
RewriteRule ^/xyz/(.*)$ /Application/WebObjects/MyApplication.woa/$1?_alias=/xyz [L,PT,QSA]
RewriteRule ^/abc/(.*)$ /Application/WebObjects/MyApplication.woa/$1?_alias=/abc [L,PT,QSA]
Now my application be accessed with three different aliases /app, /xyz and /abc and the response contains the corresponding rewritten url. No need to set the properties in the Properties for pattern and replace as that can be directly controlled with apache config file.
However, I would like to know I've implemented this change at right place or there is any other method which more appropriate such as _rewriteURL but that is still not working for me.
Yes, _rewriteURL is intended to be overridden by your subclasses for custom rewrite rules.
with regards,
--
Lachlan Deck