[
https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.s...
]
Tobias Frech commented on AS7-1338:
-----------------------------------
If the jndi.properties file on the client needs to be adapted for AS 7 (I guess so), it
also could be discussed if the port 1099 is changed. On one hand this port maybe be
already open on firewalls for remote clients to access the AS. On the other hand on
Windows you could experience problems with this port because it is already used by a
mounted share.
Also it would be nice if the implementation would allow to securely expose JNDI to the
internet without risking someone unauthorized accessing and changing anything in it.
Remote JNDI support for AS7
---------------------------
Key: AS7-1338
URL:
https://issues.jboss.org/browse/AS7-1338
Project: Application Server 7
Issue Type: Task
Components: Naming
Reporter: Richard Opalka
Assignee: John Bailey
Priority: Critical
Labels: eap6-req
Fix For: 7.1.0.Final
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira