But that's not the case. The issue is with the implementation of the forAllMethods tag handler logic. It switches the class context as it traverses the class hierarchy. So if, for example, you have shared methods in your base classes that you want to make transactional then the transactional attributes get marked up in the deployment descriptor with the ejbname attribute of the base class. This would hold true of any template using this tag. If you wish to access members of a base class while retrieving the name of the current class then you will always get the name of the base class rather than the name of the class you began iterating methods on. What I'm looking for is a way to flatten this view and make all members of base classes appear as if they were implemented in the sub-classes. I'd be surprised if nobody else has ever run into this situation.
Clifton C. Craig, Software Engineer Intelligent Computer Systems - A Division of GBG 2101 Embassy Drive Lancaster, PA 17603
Phone: 717-295-7977 ext. 621 Fax: 717-295-7683 [EMAIL PROTECTED] [EMAIL PROTECTED]
Shaun wrote:
Have you tried keeping the <entitycmp/>, <session/>, and <deploymentdescriptor/> subtasks together within the same <ejbdoclet/> task? I have found that if they are not kept in the same <ejbdoclet/> task, the entity bean class names in the deployment descriptor turn out to reference nonexistent classes. (ie. EntityCMPCMP)
Hope this helps,
Shaun
------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
