Red Hat Bugzilla – Bug 1014678
Add link to JNDI names reference
Last modified: 2014-08-14 11:23:31 EDT
Procedure 7.8. Obtain a Bean Proxy using JNDI and Invoke Methods of the Bean
At the end of step 3, there is the note 'Session bean JNDI names are defined using a special syntax.' I think it would be useful to add a link to the reference documentation for this syntax. It is here: http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/6.2/html/Development_Guide/sect-Reference-2.html
Darrin, I will take this one since I made other fixes to it.
Topic 5719 "Invoke a Session Bean Remotely Using JNDI" topic is included in multiple guides:
These have revisions, so I don't believe they are impacted:
14875, Development Guide, JBoss Enterprise Application Platform, 6.2 (beta?)
14877, Migration Guide, JBoss Enterprise Application Platform, 6.2 (Beta?)
I am not clear what this one is for or if it is used:
11637, Migration Guide , JBoss Portal Platform, 6 (Is this even used?)
These seem to be the current guides:
22509, Development Guide, JBoss Enterprise Application Platform, 6.2
22507, Migration Guide, JBoss Enterprise Application Platform, 6.2
The Development Guide content spec contains topic 5119 "EJB JNDI Naming Reference":
EJB JNDI Naming Reference [5119, rev: 459907]
None of the Migration Guide content specs contain this topic. I need to check with Russell to make sure I can change the content specs for 11637 and 22507 before I can change this topic.
Russell, is it too late to update the maps?
Is map 11637 even valid?
Modified topic 5719 to refer to topic 4119:
Invoke a Session Bean Remotely using JNDI [5719, rev: 593715]
Modified content spec 22507 for the Migration Guide for 6.3: 22507
Section: Remote Invocation Changes
Migrate JBoss EAP 5 Deployed Applications That Make Remote Invocations to JBoss EAP 6 
Invoke a Session Bean Remotely using JNDI 
EJB JNDI Naming Reference 
I am rebuilding the Migration Guide for 6.2 for other issues, so I will modify the map 14877 for the 6.2 Migration Guide.
Moving to ON_QA.
The changes should be available for review on the documentation stage within an hour or so from this comment.