[gatein-issues] [JBoss JIRA] (GTNPORTAL-2317) InitiateLoginServlet uses wrong Instance of WCIController

[Marek Posolda (Resolved) (JIRA)]

     [ https://issues.jboss.org/browse/GTNPORTAL-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Posolda resolved GTNPORTAL-2317.
--------------------------------------

    Fix Version/s: 3.2.0-CR01
       Resolution: Duplicate Issue


Thanks for detailed report. 

This issue was already fixed recently in GateIn trunk because of very similar issue GTNPORTAL-2296, which has same cause. It was causing that first HTTP request to container "myportal" can be bound to default portal container "portal".

You can try with latest GateIn trunk to verify fix.
                
> InitiateLoginServlet uses wrong Instance of WCIController
> ---------------------------------------------------------
>
>                 Key: GTNPORTAL-2317
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-2317
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.2.0-Beta01
>            Reporter: Stefan Seidel
>            Assignee: Marek Posolda
>             Fix For: 3.2.0-CR01
>
>
> Situation:
>  - I have set up a new portal container.
>  - I want to customize the login page, so I make changes to /login/jsp/login.jsp in my portal WAR
>  - I access a private page, e.g. /myportal/private/classic
> Problem:
>  - I get the login.jsp from the default portal container (/portal), not my customized version.
> I can get my customized login.jsp to show up when I enter a wrong username/password. This is because in the ErrorLoginServlet, a new GateinWCIController is created with the current ServletContext, so it uses my custom JSP.
> On the other hand, the InitiateLoginServlet does not create a new GateinWCIController instance, but re-uses a previously created one, which is the wrong one (using the default PortalContainer).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira