Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
v1m1, 1.0, 1.0.1, 1.0.2
-
None
Description
The EJB System control's documentation incorrectly references a 'jndi:' protocol when discussing how the @EJBHome's jndiName attribute can be set. Beehive does not have a 'jndi' protocol handler and cannot support this. Below is the offending text:
Accessing EJBs on a Different Server
You can access EJBs on a different server with an EJB control, provided the server hosting the EJB control and the server to which the target EJB is deployed are in the same domain. You access EJBs on a different server by using special JNDI syntax in the EJBHome annotation's jndiName attribute.
For example:
@EJBHome(jndiName="jndi://username:password@host:7001/my.resource.jndi.object")
You can also use environment properties to specify configuration information, such as:
@EJBHome(jndiName="jndi://host:7001/MyEJBHome?SECURITY_PRINCIPAL=me&SECURITY_CREDENTIALS=passwd")
The doc needs to be udpated to remove the reference to the 'jndi' protocol.
The proper way to achieve this behavior is to use the EJB control's JNDIContextEnv annotation to specifcy the security settings.