[cdi-dev] [JBoss JIRA] (CDI-400) 5.4.1 Client proxy invocation section contradicts EJB spec section 3.4.7Session Object Identity

Thu Sep 12 17:51:03 EDT 2013

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

Marina Vatkina updated CDI-400:
-------------------------------

    Description: 
CDI 1.1

5.4.1 Client proxy invocation

"The behavior of all methods declared by java.lang.Object, except for toString(), is undefined for a client proxy.
Portable applications should not invoke any method declared by java.lang.Object, except for toString(), on a client
proxy."

EJB 3.2 

3.4.7Session Object Identity

"A client can test two EJB 3.x remote or local view references for identity by means of the Object.equals and Object.hashCode methods."

Subsections define it further.

> 5.4.1 Client proxy invocation section contradicts EJB spec section 3.4.7Session Object Identity
> -----------------------------------------------------------------------------------------------
>
>                 Key: CDI-400
>                 URL: https://issues.jboss.org/browse/CDI-400
>             Project: CDI Specification Issues
>          Issue Type: Bug
>            Reporter: Marina Vatkina
>
> CDI 1.1
> 5.4.1 Client proxy invocation
> "The behavior of all methods declared by java.lang.Object, except for toString(), is undefined for a client proxy.
> Portable applications should not invoke any method declared by java.lang.Object, except for toString(), on a client
> proxy."
> EJB 3.2 
> 3.4.7Session Object Identity
> "A client can test two EJB 3.x remote or local view references for identity by means of the Object.equals and Object.hashCode methods."
> Subsections define it further.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira