On Nov 15, 2007, at 3:30 PM, Mike Schrag wrote:
> In Velocity, you can just use ${attribute.documentation} (and
> entity.documentation, model.documentation, etc). Entity Modeler
> exposes these as top level properties that just happen to be stored
> in userInfo.
You rock.
For those using "Mike's Version", this is what the top of my
_Entity.java looks like:
#if ($entity.documentation)
/**
${entity.documentation}
*/
#end
public abstract class ${entity.prefixClassNameWithoutPackage} extends
#if ($entity.parentSet)${entity.parent.classNameWithDefault}#elseif
($EOGenericRecord)${EOGenericRecord}#else EOGenericRecord#end {
public static final String ENTITY_NAME = "$entity.name";
// Attributes
#foreach ($attribute in $entity.sortedClassAttributes)
#if ($attribute.documentation)
/**
$attribute.documentation
*/
#end
public static final String $
{attribute.uppercaseUnderscoreName}_KEY = "$attribute.name";
#end
// Relationships
#foreach ($relationship in $entity.sortedClassRelationships)
#if ($relationship.documentation)
/**
$relationship.documentation
*/
#end
public static final String $
{relationship.uppercaseUnderscoreName}_KEY = "$relationship.name";
#end
So if the documentation is set, it spits out the java doc for the
class, attributes, and relationships.
This archive was generated by hypermail 2.0.0 : Thu Nov 15 2007 - 17:51:31 EST