I have removed the get methods from the LoginAction of /Context2 and that seems
to solve the problem. So seems like the LoginAction objects created because of
FORWARD some how are in the stack while a
LoginAction is created due to a REQUEST. Wondering if this can be replicated
without having
On 4/23/2018 11:50 PM, Prasanth Pasala wrote:
> Get rid of the get methods in LoginAction, is this in /Context2 (application
> where the issue is occurring) or /Context1 (which forwards the requests to
> /Context2)?
>
That contexts who forwards request (Context1 I think) but you may do for
2 matches
Mail list logo
