>>> It separates the business contract from the technical
>>> contract, so you don't have ejbActivate, ejbPassivate etc.
>>> cluttering up your code
>>
>> If I leave those methods out, it complains that my class isn't
>> implementing the SessionBean interface. If I don't implement
>> that interface, ejbdoclet passes over my session bean entirely.
>
> So you give xdoclet an ordinary class and expect a session bean
> subclass?
No, no, I don't expect that. I understand perfectly well why
it's looking for the session bean interface.
My question is (still): what good does the subclass do? It does
*not* separate the business methods from the "technical"
methods -- if I implement the SessionBean interface, I need to
have ejbActive and friends cluttering up my code, as you put it.
How can I rephrase this question so it makes sense? It is a Catch-22:
no "implements SessionBean" => xdoclet doesn't generate a subclass
"implements SessionBean" => subclass is useless
Paul
_____________________________________________________________________
"At the level of bits, censorship and digital-rights management are
technologically identical." Hal R. Varian, _The New York Times_
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Oh, it's good to be a geek.
http://thinkgeek.com/sf
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
