[
https://issues.jboss.org/browse/AS7-2361?page=com.atlassian.jira.plugin.s...
]
Jason Greene updated AS7-2361:
------------------------------
Summary: Remove JNDI port from standalone.xml/domain.xml (was: Remove JNDI port
from standalone.xml)
Component/s: Domain Management
(was: Naming)
Remove JNDI port from standalone.xml/domain.xml
-----------------------------------------------
Key: AS7-2361
URL:
https://issues.jboss.org/browse/AS7-2361
Project: Application Server 7
Issue Type: Task
Components: Domain Management
Reporter: Jim Tyrrell
Assignee: John Bailey
Labels: eap6-ux
Attachments: Screen shot 2011-10-26 at 3.08.19 PM.png
Many many customers use client lookups of JNDI contexts to get at what used to be called
remote interfaces to invoke EJBs on a JBoss instance. Where and how does this work? Is
this be design? If so, this is going to be a problem for many current customers, as they
do this today.
--
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