-
Type:
Task
-
Status: Resolved (View Workflow)
-
Priority:
Critical
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 7.1.0.Final
-
Component/s: Naming
-
Labels:
-
Forum Reference:
Add support for remote JNDI after all. It was agreed that:
- Remote JNDI would run over Remoting
- Remote JNDI for EJB is strictly a legacy access protocol, deprecated in favor of "ejb:"
- The Remote JNDI service would proxy to a specific Context of the server JNDI tree - maybe "java:jboss/shared", maybe something else
- Server-side services would opt-in to Remote JNDI; initially we'd only support:
- Remote EJB interfaces
- HornetQ connection factories
- In the future we may support:
- User bindings, so long as they're serializable
- In the future we will never support:
- Proxied DataSources
- Proxied JMS invocations
Initial project tree is at https://github.com/dmlloyd/jboss-remote-jndi for now.
- is duplicated by
-
AS7-3437 JMS clients - Remote JNDI lookup does not work in EAP6/AS7
-
- Closed
-
- is related to
-
AS7-3437 JMS clients - Remote JNDI lookup does not work in EAP6/AS7
-
- Closed
-
-
JBPAPP6-264 JMS clients - Remote JNDI lookup does not work in EAP6/AS7
-
- Closed
-
-
AS7-423 Remote EJB (non-IIOP)
-
- Resolved
-
-
AS7-1709 Client JNDI support for AS7
-
- Closed
-
- relates to
-
JBWS-3454 Additional tests for SOAP-over-JMS and AS7 remote connection factory
-
- Closed
-