Ok, we've had a chance to dig into this a little more. It appears that
in Websphere 5.1.1.8, 5.1.1.13 and 6.1, the behavior of the
getQueryString() is different from Jetty/Tomcat. Under websphere, after
a forward, getQueryString() will always return null. Whereas on
Jetty/Tomcat, the getQueryString() will return the query string of the
original request after a forward. I also found out, that after a
forward under Websphere 6.1 (haven't tried 5.1 at all with this yet)
that the original query string is available by calling
request.getAttribute("javax.servlet.forward.query_string"). Anyone have
any idea why no one has run into this before? It seems like it would
have been something someone would encounted before.
Now for the fix, we could either patch this in URL.java or override the
getQueryString method of WebworkRequestWrapper. I'm in favor of the
latter since it might fix other cases where we might run into this issue.
Tom
Tom Schneider wrote:
Hello,
I ran into an issue in webwork with the URL tag. I checked the code
and it's exactly the same code in struts2, so I thought I would post
it here. The issue is that when we run our application under
Websphere 5.1.1.8 <http://5.1.1.8>, in URL.java, line 203 in the
extractQueryString() method, a call to
String query = req.getQueryString();
is being made. Under jboss this call returns the query string as
expected. Under Websphere, this method always returns null. So that
means that in places where we are expecting the url parameters to be
automatically propagated, they are not. Anyone have any insight into
this? It seems like a pretty basic issue and I'm not finding any
online info about this. (I found an issue on IBM's website about
this, but 5.1.1.8 <http://5.1.1.8> supposedly has the fixes for this)
Thanks,
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
