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
