Re: _rewriteURL is not called in Tomcat Deployment
Re: _rewriteURL is not called in Tomcat Deployment
- Subject: Re: _rewriteURL is not called in Tomcat Deployment
- From: WebObjects - Anazys <email@hidden>
- Date: Thu, 5 Nov 2009 09:23:01 +0100
WO 5.3 and Wonder 5.0.0.9537
I do it a different way and I think it's currently working :
- I add a call to finishInitilization() in my Application()
initialization
- I put this method in Application.java :
public void finishInitilization(){
super.finishInitialization();
setContextClassName
(my.application.framework.ERXWOServletContext.class.getName());
}
- And I create a ERXWOServletContext class wich extends WOContext and
override _urlWithRequestHandlerKey.
I don't think I'm doing something wrong. Can you confirm that ?
Thanks
Cedric
Le 5 nov. 09 à 06:49, Lachlan Deck a écrit :
On 05/11/2009, at 8:40 AM, WebObjects - Anazys wrote:
I have the same problem on Tomcat, how could I use this patch, I
don't really understand ?
Wow .. this is from a long time ago.
Apply the patch to Wonder source, rebuild wonder, test, report back :)
Preferably someone who does use servlets can quickly test this out
(for both WO53 and WO54) before I commit these....
Or maybe an update of wonder is sufficient ?
I create a class ERXWOServletContext which extends
com.webobjects.appserver.WOContext
No. There's already this class in Wonder. 'It' needs to be patched.
Or if using WO54 then the other patch creates an
ERXWOServletContext54 class which subclasses ERXWOServletContext.
Then I put the given code (override _urlWithRequestHandlerKey). And
last the finishInitialization method in Application.
But it didn't seems to work : I placed debug statements at the
beginning of _rewriteUrl(String _url), but nothing appear in Tomcat
deployment.
I placed other debug statements in my class loader and at the
beginning of _urlWithRequestHandlerKey, but still nothing...
Did I miss something ?
What version of WO and Wonder are you using?
Thanks for your help.
Cedric
Le 15 oct. 08 à 16:34, Lachlan Deck a écrit :
Hi again,
On 16/10/2008, at 12:31 AM, Lachlan Deck wrote:
On 15/10/2008, at 10:59 PM, Mike Schrag wrote:
I've attached a patch for ERXWOServletContext (Mike, if you'd
like to apply this... it's a project relative patch).
The problem with this is that this method call changed between
5.3 and 5.4 in an API-incompatible way, which means we actually
now have to have an ERXWOServletContext53 and
ERXWOServletContext54. This is actually exactly the reason we
have that stupid ERXWOContext54 -- it's only for this one method.
in 5.4:
public String _urlWithRequestHandlerKey(String
requestHandlerKey, String requestHandlerPath, String
queryString, boolean isSecure, int somePort) {
in 5.3:
public String _urlWithRequestHandlerKey(String
requestHandlerKey, String requestHandlerPath, String
queryString, boolean secure) {
Ah. I overlooked that.
The problem is that you have to call "super." and you can't call
super with reflection, which means you can't build a version
that works in 5.4 against 5.3 API's.
Updated patches attached...
Woops, missed the patch for ERXApplication.installPatches() also.
Here they all are again with this one too.
<ERXWOServletContext.java.patch><ERXWOServletContext54.java.patch>
with regards,
--
Lachlan Deck
<
ERXApplication
.java
.patch
>
<ERXWOServletContext.java.patch><ERXWOServletContext54.java.patch>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
with regards,
--
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden