Bugs item #485430, was opened at 2001-11-25 16:35
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=402704&aid=485430&group_id=31602

Category: ejbdoclet
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Aslak Helles�y (rinkrank)
>Assigned to: Nobody/Anonymous (nobody)
Summary: Hardcoded method-intf

Initial Comment:
In asm-descriptor.j the many method-intf elements are 
hardcoded to Home, but according to the EJB20 spec, it 
can be LocalHome too. In fact, the legal values for 
this element is (taken from spec):

The method-intf element must be one of the following:
<method-intf>Home</method-intf>
<method-intf>Remote</method-intf>
<method-intf>LocalHome</method-intf>
<method-intf>Local</method-intf>

Therefore, the InterfaceTagsHandler.methodIntf() 
method should handle the local cases too, and the 
hardcoded Home should be replaced with 
<XDtEjbIntf:methodIntf/>

----------------------------------------------------------------------

>Comment By: Aslak Helles�y (rinkrank)
Date: 2002-01-09 09:45

Message:
Logged In: YES 
user_id=49846

Taken from Chris Shaw's mail on January 9, 2001:

<snip>

In a Session Bean I have the following:
    /**
     * Retrieves next value in specified sequence
     *
     * @param name name of sequence
     * @return     next number from sequence
     *
     * @ejb:interface-method view-type="local"
     *
     * @ejb:transaction
     *     type="RequiresNew"
     *
     */
    public Integer getNextNumberInSequence(String name) {

and in ejb-jar.xml it creates:
   <container-transaction>
      <method>
         <ejb-name>SequenceGenerator</ejb-name>
         <method-intf>Remote</method-intf>
         <method-name>getNextNumberInSequence</method-name>
         <method-params>
            <method-param>java.lang.String</method-param>
         </method-params>
      </method>
      <trans-attribute>RequiresNew</trans-attribute>
   </container-transaction>

shouldn't the method-intf tag be created as:
         <method-intf>Local</method-intf>

</snip>

He's right. Aslak.

----------------------------------------------------------------------

Comment By: Aslak Helles�y (rinkrank)
Date: 2002-01-05 12:45

Message:
Logged In: YES 
user_id=49846

No, we can't close it. InterfaceTagsHandler.methodIntf() 
still only supports remote EJBs, and 
<XDtMethod:methodIntf/> is still being used in weblogic-ejb-
jar.xml, and it return "Local" or "LocalHome" for local 
EJBs/Local homes.


----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2001-12-23 22:46

Message:
Logged In: NO 

I think the latest cvs code fixes this problem (?). Could we 
close this bug?

Ara.

----------------------------------------------------------------------

Comment By: Aslak Helles�y (rinkrank)
Date: 2001-11-25 16:51

Message:
Logged In: YES 
user_id=49846

After looking into it a bit closer, I realise that the 
hardcoded Home occurs for finder methods. These are defined 
at the class level, so <XDtEjbIntf:methodIntf/> is not a 
good replacement.

In stead, I suggest we add an extra finder-intf parameter 
that can take the values Home or LocalHome to the 
@ejb:finder and @ejb:pk tags. Then we should replace 
hardcoded Home with <XDtClass:classTagValue 
tagName="ejb:finder" paramName="finder-intf"/>.

Comments?

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=402704&aid=485430&group_id=31602

_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel

Reply via email to