]
Jason Greene commented on AS7-1338:
-----------------------------------
To clarify, Remote EJB and remote app client connectivity is targeted for 7.1 (it's
part of the EE full profile). Remotely exposing the server's entire JNDI tree, which
is what the title of this JIRA is about is something that we want to avoid. Instead we
will have something more along the lines of a distributed model.
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: David Lloyd
Priority: Blocker
Fix For: No Release
<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 ;)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: