Hm It could be a problem with escaped or unescaped ampersands (&)
in the URL. It's hard do tell what might be wrong without seeing some
code and example URLs. I would consider attaching a remote debugger
to the JSR168Dispatcher and see what's going on inside it. What if you
try it in a differe
I placed the portlet on a new page by itself, but the same problems exist.
Is there anything that i might be doing that would make the urls
unnecessarily long? Or maybe the problem is something else? I will
consider any idea, even if it seems far-fetched :)
On 11/5/07, Nils-Helge Garli Hegvik <[
That's odd. The Struts 2 URLs are created through the Portlet API, so
there shouldn't be anything special about them. Is this your only
portlet on the page? If not, have you tried removing all the other
portlets portlets and see if it still fails?
Nils-H
On Nov 5, 2007 3:54 AM, Brian Relph <[EMAI
So i have written a portlet in struts2 that runs on a Websphere Application
Server 6.1. I consume the portlet on Websphere portal v 6.0 through WSRP.
Internet Explorer seems to have some problems with the urls that are
generated - everything runs fun using firefox, opera, safari. I think this
is
4 matches
Mail list logo
