For BMP, is it the intention of the Xdoclet designers to have us:
1. Modify the default entity-body.xdt template, adding persistence logic to the template inside of methods such as ejbStore, ejbLoad, ejbPassivate, etc.
2. Use the call in the generated BMP to super.ejbXXXX. This appears to be the "hook" provided by the designers, if not using DAOs. super.ejbXXXX would contain persistence logic.
In either case the persistence logic could be as simple as a calling other BMP methods generated from entity-custom.xdt. These methods would contain the bulk of the logic. In 1) the call would be inserted by modifying entity-body.xdt. In 2) the call would utilize the call to super, super would call the subclass (BMP) implementation of an abstract method, generated from entity-custom.xdt
Argument for 1:
Don't have to include any implementation for ejbXXXX at all in the handcoded super class. Don't have to add abstract custom methods to handcoded superclass that are implemented in generated BMP.
Argument for 2:
Don't have to modify the default entity-body.xdt. All custom code goes in entity-custom.xdt.
Objective views on this are appreciated.
