[ http://issues.apache.org/jira/browse/BEEHIVE-956?page=all ]
Eddie O'Neil resolved BEEHIVE-956:
----------------------------------
Fix Version: 1.1
Resolution: Fixed
Great catch, David. I've expanded / fixed the Javadoc on that annotation in
SVN 345028.
> Javadoc has syntax of ejbLink property reversed
> -----------------------------------------------
>
> Key: BEEHIVE-956
> URL: http://issues.apache.org/jira/browse/BEEHIVE-956
> Project: Beehive
> Type: Improvement
> Components: System Controls
> Versions: V1
> Environment: N/A
> Reporter: David Read
> Priority: Minor
> Fix For: 1.1
>
> javadoc for EJBControl says (in part) ... The naming syntax is
> BeanName#EJBJAR (e.g. CreditCard#CustomerData.jar).
> I think that's actually backwards. The syntax is jarFile.jar#ejb-name with
> the path to the jar file being relative to the referencing compponent. It
> might also be helpful to document that the runtime uses the fully qualified
> name of the control inteface with suffix "jcx" to build the comp:env entry
> lookup. So a control extension controls.HelloEjbControl would resolve using
> the following entry in web.xml ... assuming the EJB was in a jar named
> ejbModule.jar in the root of the application.
> <ejb-ref>
> <ejb-ref-name>controls.HelloEjbControl.jcx</ejb-ref-name>
> <ejb-ref-type>Session</ejb-ref-type>
> <home>ejbs.HelloBeanHome</home>
> <remote>ejbs.HelloBeanRemote</remote>
> <ejb-link>ejbModule.jar#HelloBean</ejb-link>
> </ejb-ref>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
