[jboss-jira] [JBoss JIRA] (EJBTHREE-2166) no-interface view implementation based on MC constructs is brittle

[jaikiran pai (JIRA)]

     [ https://issues.jboss.org/browse/EJBTHREE-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jaikiran pai resolved EJBTHREE-2166.
------------------------------------

    Resolution: Out of Date

    
> no-interface view implementation based on MC constructs is brittle
> ------------------------------------------------------------------
>
>                 Key: EJBTHREE-2166
>                 URL: https://issues.jboss.org/browse/EJBTHREE-2166
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: nointerface
>    Affects Versions: depchain-1.0.0-alpha-4
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>            Priority: Critical
>             Fix For: EJB 3.1
>
>         Attachments: EJBTHREE-2166-trimmed.log
>
>
> Currently the no-interface view proxy that gets bound into JNDI, internally uses a KernelControllerContext (MC construct) corresponding to the endpoint container of the EJB. The proxy depends just on DESCRIBED state of the endpoint.  The invocation handler of that proxy, on first invocation, pushes the context to INSTALLED state (if not already in INSTALLED stated) and then invokes on the endpoint. 
> This approach won't work out because MC returns an UnModifiable kernel controller context which throws an exception when we try to change the state of that context. More on this in the "Important" note at the end of this MC chapter http://docs.jboss.org/jbossmc/docs/2.0.x/userGuide/ch11s04.html:
> <quote>
> All context information is wrapped into unmodifiable objects to prevent the user from changing anything outside of the microcontainer's control. 
> </quote>
> It's just plain luck that no-interface view works currently, because the first invocation on the nointerface view happens after the context has already been set to INSTALLED state by MC.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira