|
Creates "entity bean classes" for BMP entity EJBs. The classes are derived from the abstract entity bean class.
Attention:
To give the developer more control over when the EJB becomes dirty (data changed) there is now a method called "makeDirty()" in the generated wrapper class. To use this please add to your EJB an abstract method called "makeDirty" and call it when you change data w/o using the setter methods. As example you could store the Data Object instead of storing all the attributes one by one (be aware that you have to clone the data object before storing to avoid side effects).
Attribute |
Description |
Required |
pattern |
The pattern by which the BMP implementation classes are named. {0} designates the EJB name. |
No, defaults to {0}BMP |
acceptAbstractClasses |
Indicates whether or not to generate for abstract classes. |
No, default is "true" |
acceptInterfaces |
Indicates whether or not to generate for interfaces. |
No, default is "true" |
havingClassTag |
Sets the HavingClassTag attribute of the TemplateSubTask object |
No. |
ofType |
|
No. |
packageSubstitutionInheritanceSupported |
Indicates whether or not package substitution should be inherited |
No, default is "true" |
packageSubstitutions |
Sets the PackageSubstitutions attribute of the TemplateSubTask object |
No. |
prefixWithPackageStructure |
Indicates whether or not to prefix with package structure. |
No, default is "true" |
subTaskClassName |
Sets a different name for the subtask which will be seen in the log messages. |
No. |
templateFile |
Sets the name of the template file to use for generation |
Yes if its a nested
element. |
destDir |
Sets the directory where the generated file will be written. |
No. |
mergeDir |
Specifies the location of the merge directory. This is where XDoclet will look for merge files. |
No. |
subTaskName |
Sets an optional name for the subtask that will be seen in XDoclet's debug messages. |
No. |
File name |
Description |
entitybmp-custom.xdt |
The file where custom code can be included. |
|