[jboss-jira] [JBoss JIRA] Resolved: (JBMETA-37) Expand determineResolvedJndiName behavior to handle targeted business interfaces

Scott M Stark (JIRA) jira-events at lists.jboss.org
Fri May 9 03:24:21 EDT 2008


     [ http://jira.jboss.com/jira/browse/JBMETA-37?page=all ]

Scott M Stark resolved JBMETA-37.
---------------------------------

    Fix Version/s: 1.0.0.Beta14
       Resolution: Done

> Expand determineResolvedJndiName behavior to handle targeted business interfaces
> --------------------------------------------------------------------------------
>
>                 Key: JBMETA-37
>                 URL: http://jira.jboss.com/jira/browse/JBMETA-37
>             Project: JBoss Metadata
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.0.0.Beta13
>            Reporter: Scott M Stark
>         Assigned To: Scott M Stark
>             Fix For: 1.0.0.Beta14
>
>
> The ejb3 proxy factory needs to know the specific business local or remote interface a reference resolves to, so the determineResolvedJndiName needs to build jndi names of the form:
> base-name/remote-FQN
> base-name/local-FQN
> where FQN is the fully qualified name of the business interface. Input interfaces need to be mapped to the local/remote business interface for this to be done.

-- 
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 jboss-jira mailing list