[seam-issues] [JBoss JIRA] Closed: (JBSEAM-1269) Support for remotely deployed EJBs

[Pete Muir (JIRA)]

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

Pete Muir closed JBSEAM-1269.
-----------------------------

    Resolution: Out of Date
      Assignee: Pete Muir


Superseded by CDI

> Support for remotely deployed EJBs
> ----------------------------------
>
>                 Key: JBSEAM-1269
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-1269
>             Project: Seam
>          Issue Type: Feature Request
>          Components: EJB3
>    Affects Versions: 1.2.1.GA
>            Reporter: Roland Räz
>            Assignee: Pete Muir
>
> We found that Seam currently has only weak support for remotely located EJBs. The only way to get to a remotely located EJB reference is to use a façade or a factory, which forces us to write unnecessary glue code. A typical use case would be a stateless SOA service, which is usually deployed remotely. This remote service might not even use Seam.
> We would like to see Seam support component declarations for interfaces + jndi-name in components.xml (as opposed to class + jndi-name). This would allow Seam to find remote components, which could be referenced through the EL. Obviously no in-/outjection would work, which is usually not required for stateless remote services.
> This feature request has been already discussed in the Seam Forum.

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