Redirection on URLMapping after login with Seam Faces

Splash Forums PrettyFaces Users Redirection on URLMapping after login with Seam Faces

This topic contains 4 replies, has 2 voices, and was last updated by  Christian Kaltepoth 10 years, 3 months ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
  • #18039

    Hey Jeremy,

    I don’t know much about the page protection features of Seam Faces, so I’m only guessing here. But I think the problem is that PrettyFaces internally forwards requests to the correct JSF viewId if a request to the REST URL is detected. So Seam Faces only sees the JSF view id and doesn’t know anything about the original REST URL. So of cause Seam Faces is redirecting to the view id.

    I don’t know how the Seam Faces page protection stuff is implemented. If there is something happening in a servlet filter, you could try to change the order of the PrettyFilter and this filter.




    Hi Christian,

    you’re right, Seam Faces receives the final JSF view id, so the REST url is lost.

    As Seam Faces use PrettyFaces to handle url mapping, I thought there was an elegant solution to this problem.

    May be I can look to PrettyFaces filter to add the original REST url has a query param of the forwarded request.




    OK, problem solved.

    I didn’t see that you could put a name to custom regex path parameter.

    For example :

    @URLMapping(id="myurlmapping", pattern="/vertical/#{/[a-z\.]+/ nameOfTheQueryParam : verticalBean.alias}",


    which transforms ‘/vertical/jeremy’ in ‘/private/vertical.jsf?nameOfTheQueryParam=jeremy’

    I thought that only Named Path Parameters and EL-injected path parameters could received a name.

    Hope this will be helpful for others.

    Thanks PrettyFaces :-)


    I’m glad to here you fixed the problem! Thanks for sharing your solution! :)

Viewing 5 posts - 1 through 5 (of 5 total)

The forum ‘PrettyFaces Users’ is closed to new topics and replies.

Comments are closed.