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: Aslak Helles�y (rinkrank) 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: 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
