Hi all,
the solution to my problem turned out to be to upgrade to XDoclet
1.2.3 - I guess the lesson learned is to never trust code given
to you by one of your colleagues :-)
However, upgrading leads to a new problem. The generated session
layer classes for my stateless session beans, which were previously
basically empty, now contain syntactically invalid method
definitions.
The examples below show how an interface method is turned into a
method on the session class.
Does anybody happen to have an idea about what causes this? I'm
guessing that I'm missing out on an attribute on the class or
method definition, but I haven't been able to find out which by
going through the documentation.
Best regards & thanks,
Mikkel Lauritsen
---
Original TestBean.java:
/**
* @ejb.interface-method view-type="both"
* @ejb.transaction type="Required"
* @ejb.resource-ref res-auth="Application"
* @websphere.resource-ref isolation-level="TRANSACTION_READ_COMMITTED"
*/
public com.test.Resultset Foobar(com.test.Request request) {
...
}
Generated TestSession.java:
private com.test.Resultset Foobar;
public com.test.Resultset Foobar(com.test.Request)
{
return Foobar;
}
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
xdoclet-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
