It seems Weblogic changes the contextPath for an included servlet to the
contextPath of the servlet itself.

According to the servlet spec 2.3 SRV.8.3.1 Included Request Parameters:
"Except for servlets obtained by using the getNamedDispatcher method, a servlet
being used from within an include has access to the path by which it was 
invoked."

Jetspeed does *NOT* invoke portlets using getNamedDispatcher so the contextPath
for the Portlet should still be that of the portal itself (/jetspeed).

In the login portlet the form is posted to <c:url value="/login/proxy"/>.
The url tag will prefix this with the contextPath so it should be 
/jetspeed/login/proxy.

You could temporarily fix this for Weblogic by adding attribute 
context="/jetspeed"
to the tag: <c:url context="/jetspeed" value="/login/proxy"/>
You can find the login.jsp in webapp security/WEB-INF/security/login/login.jsp.

If you do, don't forget to also fix the <:url value="/login/logout"/> link 
which is
a few lines above it.

That should allow you to login and logout, but of course this isn't a real 
solution.

I suggest you create a JIRA ticket for this problem so.
I don't have Weblogic available but maybe one of the other developers does.


Ate

romain bisse wrote:
Hi,
I've just installed Jetspeed2-M1 on Weblogic 8.1
Most of the modules work fine, however, I can't log in.
I obtain a 404 error when I clik on the login button.
There is no exception, neither in jetspeed nor in weblogic logs.
The URL in my browser at this moment is
"http://localhost:7001/security/login/proxy";
Did I forget something during the installation process?
Thanks in advance if you have any clue!




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to