[seam-issues] [JBoss JIRA] Commented: (JBSEAM-4674) Secured resources does not work with RESTEasy and seam 2.2.1-SNAPSHOT : 403 returned

Ray Soto (JIRA) jira-events at lists.jboss.org
Wed Aug 4 03:34:49 EDT 2010

    [ https://jira.jboss.org/browse/JBSEAM-4674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12542906#action_12542906 ] 

Ray Soto commented on JBSEAM-4674:

Feedback from end user, this does work with 2.2.1-SNAPSHOT, i currently have it deployed on development servers. It will however fail to work if debug is set to true. When debug is disabled in components.xml (and no jboss-seam-debug.jar) is included in archive, this works without issue.

> Secured resources does not work with RESTEasy and seam 2.2.1-SNAPSHOT : 403 returned
> ------------------------------------------------------------------------------------
>                 Key: JBSEAM-4674
>                 URL: https://jira.jboss.org/browse/JBSEAM-4674
>             Project: Seam
>          Issue Type: Bug
>          Components: Remoting
>    Affects Versions: 2.2.1.CR1
>         Environment: JBoss 4.2.3
> Seam 2.2.1-SNAPSHOT
>            Reporter: Gaël Beaudoin
> Securing resources like this : http://docs.jboss.org/seam/2.2.1.CR1/reference/en-US/html_single/#d0e22406
> It works fine with the released seam 2.2.0 (RESTeasy 1.1x) but not with seam 2.2.1-SNAPSHOT (from a few days ago) (RESTeasy 2.0-beta).
> The authentication works, debugging the application I can see I am logged in, but then seam return a 403 http code, unauthorized.
> Switch to seam 2.2.0 without changing anything else makes the secured resource work as expected.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the seam-issues mailing list