Bug 999524
| Summary: | Incorrect examples of JNDI syntax | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Ondrej Chaloupka <ochaloup> |
| Component: | Documentation | Assignee: | sgilda |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Russell Dickenson <rdickens> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.1.0 | CC: | lcosti, ochaloup |
| Target Milestone: | GA | ||
| Target Release: | EAP 6.1.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: |
Build: CSProcessor Builder Version 1.12
Build Name: 11863, Migration Guide-6.1-4
Build Date: 15-08-2013 13:16:01
Topic ID: 5419-308868 [Specified]
|
|
| Last Closed: | 2013-09-16 20:23:09 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Ondrej Chaloupka
2013-08-21 13:29:40 UTC
Ondrej, I got the information on 'Portable JNDI Syntax' from the Oracle tutorial here: http://docs.oracle.com/javaee/6/tutorial/doc/gipjf.html#girgn It says: "Three JNDI namespaces are used for portable JNDI lookups: java:global, java:module, and java:app." Is that information outdated? I assumed the 'java:jboss/' namespace is not portable. Isn't that only valid for the JBoss server? Made updates to topic 5419, "Portable JNDI Naming Syntax", revision 499751. Ondrej, I spoke with Stuart Douglas today. It appears that this topic title is misleading. The topic was meant to discuss EJB bindings, not namespaces. A more appropriate title would be " Portable EJB JNDI Names" but it may be too late to change the title as it impacts all the books. I changed the introductory paragraph to the following: There are four logical namespaces, each with its own scope, but portable EJB names only get bound to three of them. The following table details when and how to use each namespace. I changed the java:global description: Names in this namespace are shared by all applications deployed in an application server instance. Use names in this namespace to find EJBs external archives deployed to the same server. As for the '.jar' in the JNDI names, they were taken from a migrated Seam application. The developer used the '.jar' to distinquish between the JAR and WAR with the same name in the EAR. I changed the '.jar' to '-jar' to be less confusing. Changed the topic title from Portable JNDI Naming Syntax to 'Portable EJB JNDI Names' Topic 5419, rev 499807 Modified the following CSP maps: 14877 - 6.2 Migration Guide 19236 - 6.1.1 Migration Guide Also changed: 13710 - 6.2 WebLogic Migration Guide 22175 - 6.2 WebSphere Migration Guide Hi, thanks for changes. I agree in principle with the text, but I would have one request for the change. I think that would be nicer to use "Java EE platform specification defines" then the "There are four logical namespaces". Otherwise it seems to me fine. I see your point about the ".jar" suffix. I didn't understand it before. I'm just thinking that I will create a new bugzilla about migration guide as I think that it would be nice to mention the change for client remote ejb lookups. I'm not able to find such chapter around. The second thing is that we (as QA) are supposed to put the bz as verified after the content is put on documentation-devel site. Thank you Ondra Agreed. Modfified the opening text to: he Java EE 6 specification defines four logical namespaces, each with its own scope, but portable EJB names only get bound to three of them. The following table details when and how to use each namespace. Topic 5419, 'Portable EJB JNDI Names' is now at revision 500563. Does the section on 'Remote Invocation Changes' address the cliet remote EJB lookup changes? http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBoss_Enterprise_Application_Platform/6.1.1/html-single/Migration_Guide/index.html#sect-Remote_Invocation_Changes If not, when you enter the new bug, could you be specific about what you are looking for? I understand that you need to wait for it to be staged, but we are getting down to the wire and I wanted to be sure you reviewed this before it was too late. I will move it back to ON_QA after the next docstage build. I've already found the part about the ejb remoting invocation. Sorry for mystification. I'm fine with the text and when it will be prepared for review I'll just move it to verified. Thank you The changes are on-stage and ready for review (from Revision 1.0-65) http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBoss_Enterprise_Application_Platform/6.1.1/html/Migration_Guide/chap-Migrate_Your_Application.html#Portable_JNDI_Naming_Syntax |