[
https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.s...
]
David Lloyd updated AS7-1338:
-----------------------------
Fix Version/s: No Release
(was: 7.1.0.CR1)
Description:
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.
was:
<opalka> wolfc, dmlloyd I'm not able to connect to JNDI on AS7. in the AS7
config I see it should be running on 1099, but I'm getting
http://fpaste.org/wgy8/ :(
<opalka> wolfc, dmlloyd in the config I see the following ports defined
<opalka> ---
<opalka> <socket-binding name="jndi" port="1099"/>
<opalka> <socket-binding name="jmx-connector-registry"
port="1090"/>
<opalka> <socket-binding name="jmx-connector-server"
port="1091"/>
<opalka> ---
<dmlloyd> we don't do JNDI over RMI anymore
<dmlloyd> that listing is an error
<opalka> dmlloyd, So we're not able to do JNDI lookups to AS7 anymore and
don't plan to?
<opalka> dmlloyd, or we'll be doing JNDI over different binary protocol?
<dmlloyd> no, we will be able to, it'll just work somewhat differently
<opalka> dmlloyd, ok, I'm excluding the tests then ...
<opalka> dmlloyd, Is there a JIRA covering this issue so I can use it in my
excludes comment?
<dmlloyd> not that I'm aware of, it's just an outstanding task
<dmlloyd> remote invocation is not planned to be covered in next months' beta
release
<opalka> dmlloyd, ok, thx for info ;)
Forum Reference:
http://community.jboss.org/message/619784#619784 (was:
http://community.jboss.org/message/619784#619784)
Was previously rejected:
<opalka> wolfc, dmlloyd I'm not able to connect to JNDI on AS7. in the AS7
config I see it should be running on 1099, but I'm getting
http://fpaste.org/wgy8/ :(
<opalka> wolfc, dmlloyd in the config I see the following ports defined
<opalka> ---
<opalka> <socket-binding name="jndi" port="1099"/>
<opalka> <socket-binding name="jmx-connector-registry"
port="1090"/>
<opalka> <socket-binding name="jmx-connector-server"
port="1091"/>
<opalka> ---
<dmlloyd> we don't do JNDI over RMI anymore
<dmlloyd> that listing is an error
<opalka> dmlloyd, So we're not able to do JNDI lookups to AS7 anymore and
don't plan to?
<opalka> dmlloyd, or we'll be doing JNDI over different binary protocol?
<dmlloyd> no, we will be able to, it'll just work somewhat differently
<opalka> dmlloyd, ok, I'm excluding the tests then ...
<opalka> dmlloyd, Is there a JIRA covering this issue so I can use it in my
excludes comment?
<dmlloyd> not that I'm aware of, it's just an outstanding task
<dmlloyd> remote invocation is not planned to be covered in next months' beta
release
<opalka> dmlloyd, ok, thx for info ;)
But now it's back :)
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: Blocker
Fix For: No Release
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