[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1814) DataModel wrapped data is set to null by ManagedEntityIdentityInterceptor

Alex Savitsky (JIRA) jira-events at lists.jboss.org
Fri Mar 7 14:34:57 EST 2008

    [ http://jira.jboss.com/jira/browse/JBSEAM-1814?page=comments#action_12401827 ] 
Alex Savitsky commented on JBSEAM-1814:

Do I understand correctly, that the ManagedEntityIdentityInterceptor is only useful for environments supporting EJBs and passivation? Is there any use of having this interceptor in Tomcat? If not, then maybe it makes sense not to activate it where it doesn't provide any value?

I tried to stub the interceptor (leaving only "return ctx.proceed()" in the aroundInvoke() body), and haven't seen any problems so far, not to mention that all properties of EntityQuery suddenly started to work predictably. I'll try this approach in a real app, and will let you guys know...

> DataModel wrapped data is set to null by ManagedEntityIdentityInterceptor
> -------------------------------------------------------------------------
>                 Key: JBSEAM-1814
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1814
>             Project: JBoss Seam
>          Issue Type: Bug
>    Affects Versions: 2.0.0.BETA1
>         Environment: seam cvs (20070816.1709)
>            Reporter: Matt Drees
>         Assigned To: Norman Richards
>            Priority: Minor
>             Fix For: 2.1.x
> The following test fails:
> @Name("dataModelComponent")
> @Scope(ScopeType.CONVERSATION)
> public class DataModelComponent extends EntityQuery {
>    @Override
>    public String getEjbql() {
>       return "from java.lang.Object o";
>    }
> }
> public class DataModelComponentTest extends SeamTest {
>    @Test
>    public void test() throws Exception {
>       new FacesRequest() {
>          @Override
>          protected void renderResponse() throws Exception {
>             DataModel model = (DataModel) getValue("#{dataModelComponent.dataModel}");
>             assert model.getWrappedData() != null;
>          }
>       }.run();
>    }
> }
> Because the component is conversation-scoped, a ManagedEntityIdentityInterceptor is attached, which nulls the wrapped List after getDataModel() is called.
> In the referenced forum, Gavin indicated he hadn't decided whether this should be expected behavior or not, and asked for a jira issue.  
> If it is expected behavior (I hope not), I think either EntityQuery should not have a getDataModel() attribute, or it should be documented and/or programmatically enforced that EntityQuerys should not be conversation-scoped.

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


More information about the seam-issues mailing list