[seam-issues] [JBoss JIRA] (SEAMSECURITY-137) IdentitySessionProducer.createIdentitySession doesn't put anything in sessionOptions for JpaIdentityStoreSession

[John Schneider (Updated) (JIRA)]

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

John Schneider updated SEAMSECURITY-137:
----------------------------------------

    Priority: Minor  (was: Major)

    
> IdentitySessionProducer.createIdentitySession doesn't put anything in sessionOptions for JpaIdentityStoreSession
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: SEAMSECURITY-137
>                 URL: https://issues.jboss.org/browse/SEAMSECURITY-137
>             Project: Seam Security
>          Issue Type: Bug
>    Affects Versions: 3.1.0.CR1
>         Environment: Glassfish 3.1.1 and built in EclipseLink
>            Reporter: John Schneider
>            Priority: Minor
>
> IdentitySessionProducer.createIdentitySession checks entityManagerInstance.isUnsatisfied and entityManagerInstance.isAmbiguous() before putting anything in the sessionOptions map, which is later used in JpaIdentityStore.createIdentityStoreSession.  With Glassfish 3.1.1 using builtin EclipseLink, entityManagerInstance is represented by org.jboss.weld.bean.builtin.InstanceImpl.  Invocation of isUnsatisfied is not working.  When I look at it in a debugger, isUnsatistfied doesn't execute; instead readObject executes and throws InvalidObjectException(PROXY_REQUIRED).  I can't tell whether this is just because I'm in a debugger or if this happens during normal execution and is the cause of the problem.

--
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