Thanks for your answer.

I fixed the "login.jsp" the way you suggested.

I have no 404 error anymore.
But instead, when I click on the "Login" button, the url turns to
/jetspeed/login/login, then the browser reloads the default page (My
first PSML page) and I'm still anonymous.

Any idea?

-----Message d'origine-----
De : Ate Douma [mailto:[EMAIL PROTECTED] 
Envoyé : mercredi 26 janvier 2005 23:57
À : Jetspeed Users List
Objet : Re: [J2] Newbie: Error 404 with login portlet


Ate Douma wrote:
> 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."
I should also have quoted the following part of SRV.8.3.1 I think:

"The following request attributes are set:
      javax.servlet.include.request_uri
      javax.servlet.include.context_path
      javax.servlet.include.servlet_path
      javax.servlet.include.path_info
      javax.servlet.include.query_string

   These attributes are accessible from the included servlet via the
getAttribute
method on the request object.
   If the included servlet was obtained by using the getNamedDispatcher
method these attributes are not set."

After rereading this paragraph three times over, I must admit it does
not
explicitly say the request.getContextPath() for an included servlet
should
remain the same. But, if that would not be the intention of this
paragraph,
then one would never *need* the javax.servlet.include._context_path
attribute
or the others.
So, my interpretation of this is that the request.getContextPath()
*should*
remain the same. Seems the Weblogic developers think differently...

> 
> 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]
> 
> 
> 
> 
> 


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



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

Reply via email to