[seam-issues] [JBoss JIRA] Commented: (JBSEAM-4808) Wicket integration - Conversation lifecycle is broken when onPageAttached() is overridden.

[Rob Shepherd (JIRA)]

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

Rob Shepherd commented on JBSEAM-4808:
--------------------------------------

10MB limit on file attachments to example SEAM project is available from: 

http://www.datacymru.net/demo/WicketAjaxConvIssue.zip

> Wicket integration - Conversation lifecycle is broken when onPageAttached() is overridden.
> ------------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-4808
>                 URL: https://issues.jboss.org/browse/JBSEAM-4808
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Wicket
>    Affects Versions: 2.2.2.Final
>         Environment: MAC OS X
> Java 1.6.0_24
> JBoss AS 5.1.0.GA
> JBoss SEAM 2.2.2.FINAL
>            Reporter: Rob Shepherd
>
> Primarily - see the seam framework forum post.
> Under the hood of course, onPageAttached() will have been instrumented to:
> onPageAttached100() and the original method name then providing a SEAM request lifecycle wrapper, to perform injection and other interceptor functions around the original method content.
> It looks like the seam manager has not yet begun delivering the request and retrieved the conversation ID from the previously rendered 
> page's page map and switched the conversation.
> In the failure mode - I'm unclear how a conversationally scoped re-injected instance can exist when the current conversation ID is seen to change.
> The original use-case for overriding the onPageAttached() was - when re-rendering page instances from the page map - to detect changes in other injected session-scoped context variables and mark a page as expired if changes have occurred - or proceed if no changes have occurred.
> Any @In-jected conversational bean is replaced by a new instance - even if (later in the request) the conversation ID seems to revert back to the proper ID.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira