beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chad Schoettger (JIRA)" <j...@apache.org>
Subject [jira] Created: (BEEHIVE-1192) EJB system control's programmer's guide incorrectly references a 'jndi:' protocol
Date Tue, 24 Apr 2007 16:28:15 GMT
EJB system control's programmer's guide incorrectly references a 'jndi:' protocol
---------------------------------------------------------------------------------

                 Key: BEEHIVE-1192
                 URL: https://issues.apache.org/jira/browse/BEEHIVE-1192
             Project: Beehive
          Issue Type: Bug
          Components: Documentation
    Affects Versions: 1.0.2, 1.0.1, 1.0, v1m1
            Reporter: Chad Schoettger
         Assigned To: Chad Schoettger
             Fix For: V.Next


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.

            



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message