Support for remotely deployed EJBs

[wv-javacoder]

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.

Any thoughts on that idea? Shall we open a feature request in JIRA?

[iradix]

I'm a little lost on how this would be useful. Granted, I shunned EJB before Seam and am definitely no expert, but wouldn't remote services generally be used by your local EJB actions rather than resolved via EL within pages? I'm pretty sure you can inject a remote EJB using the @EJB annotation and I'd imagine if you really need one from within a JSF page it would be pretty simple to write your own resolver...

[norman.richards]

I've heard this request several times. You should definitely put in JIRA for consideration.