They can! And method-intf is exactly for that scenario, to let you distinguish between methods with the same name in local/remote/homte/interface. Lines 68-70 of asm-descriptor are wrong, no need for ifNotRemoveMethod. What we should do for ejbRemove/ejbCreate/ejbFind/ejbHome generally is to check if method=remote/local interface then remove the ejb prefix from the name, else if home/localhome (create-method/no interface-method for ejbRemove/etc) then no change in method name. Probably a guru like Rickard can say the final word.
Another thing worth to mention: currently xdoclet supports "Remote" and "Local" as the valid values for method-intf. It's correct up to and including ejb2pfd3 but the final spec has LocalHome/Home/Remote/Local if I recall correctly. Obviously we should change methodIntf() and support it correctly for all cases :o) Ara. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:xdoclet-devel- > [EMAIL PROTECTED]] On Behalf Of Aslak Helles�y > Sent: Tuesday, October 09, 2001 11:06 PM > To: [EMAIL PROTECTED] > Subject: RE: [Xdoclet-devel] @ejb:transaction method level tag bug? > > Forget my suspicion about AbstractEjbSubTask.getInterfaceMethodName( > String ) > > I think the bug is in AbstractEjbSubTask.isInterfaceMethod( MethodDoc ). > The or statement shouldn't contain isRemoveMethod( method ). Home > interfaces > aren't supposed to have remove() methods, are they? > > Am I right? > > <aslak/> > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Aslak > Helles�y > Sent: 9. oktober 2001 20:15 > To: [EMAIL PROTECTED] > Subject: [Xdoclet-devel] @ejb:transaction method level tag bug? > > > Hi again, > > Still problems with the examples on WLS. AccountBean, CustomerBean and > TellerBean all have @ejb:transaction type="Mandatory" on their > ejbRemove(). > > AbstractEjbSubTask.getInterfaceMethodName( String ) returns "create" as > the > method name for "ejbCreate" and "remove" for "ejbRemove". WLS6.1 sp1's > ejbc > doesn't like that: > > weblogic-ejb-jar: > [java] > [java] ERROR: Error from ejbc: Unable to set the transaction > attribute > for method "remove()". No matching method could be found. Plea > se verify the method signature specified in the ejb-jar.xml file matches > that of your EJB. > [java] ERROR: ejbc found errors > [java] Java Result: 1 > > Why is getInterfaceMethodName so "smart"? It seems intentional, but I > can't > see why, as the code doesn't document why. > Enlighten me please. > > <aslak/> > > > _______________________________________________ > Xdoclet-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-devel > > > _______________________________________________ > Xdoclet-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-devel _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
