the bpm4struts cartridge also has some stereotype names coded in the scripthelper, it's not the most beautiful way of working but it avoids loading resources bundles with constants (adding complexity).. anyway, it should not be too difficult (at least in this cartridge) to switch to a more flexible approach,
one thing though, if Lofi is right and the convention is to use lowercase names shouldn't we put this in the 3.0 release ?
greetz Wouter.
as for any workarounds, I don't see any except compiling your changes in the Andromda code.
Lofi Dewanto wrote:
Hi All,
I found this wyrd stuff:
Why can't I write the <<PrimaryKey>> stereotype in <<primaryKey>>? I would like to use small caps on the "p"...
Changing everything in templates works fine but this following method: #set ($primKey = $transform.getPrimaryKeyAttribute($class)) won't work.
It seems that in the file SimpleOOHelper.java both "PrimaryKey" and "Entity" keywords have been "hardcoded":
public class SimpleOOHelper extends UMLStaticHelper { private final static String PRIMARY_KEY = "PrimaryKey"; private final static String ENTITY_BEAN = "Entity"; ...
I'm not complaining ;-) but I think AndroMDA should use the standard UML notation and as far as I know all the stereotypes should use small caps for the first word:
Instead of <<Entity>> use <<entity>>, <<PrimaryKey>> use <<primaryKey>>
If I want to make this happens in my templates, does this mean that I cannot use the SimpleOOHelper? Any workarounds available?
Any ideas or comments?
Thanks a lot!
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Andromda-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-user
