There might indeed be a way of doing this without changing the AndroMDA code. I am not looking at the code right now, but I can give you some hints about where to investigate more.
Have a look at the <repository> tag for ANT on the following page. You might be able to use it to solve your problem. http://www.andromda.org/pages/buildtags.html One of the classes, either the repository class, or the helper class, has a method 'getStereotypeNames' implemented on it. It might be possible for you to subclasses AndroMDA's default version of this implementation, and replace it with your own. Your implementation could then fiddle with the case of the stereotype names. Your UML model could have a stereotype like <<primaryKey>>, and your implementation of getStereotypeNames could transform <<primaryKey>> to <<PrimaryKey>> or the collection {<<primaryKey>>, <<PrimaryKey>>}. It is a hack, but it would at least stop you from having to change the AndroMDA core and let you write your model the way you want it. - Tony > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Lofi > Dewanto > Sent: Monday, December 15, 2003 1:50 PM > To: [EMAIL PROTECTED] > Subject: Re: [Andromda-user] Bug: > $transform.getPrimaryKeyAttribute($class) > > > > If it's easily possible, I'd say we go all the way and use case > insensitive > > stereotype names. That way, AndroMDA users can use whatever > case convention > > they want in their models. > > > > Sure, we'd lose the ability to distinguish between 'entity', > 'Entity' and > > 'EnTiTy', but anyone actually expecting these three strings to > have different > > meanings is quite insane IMO, and we shouldn't further insanity in > > AndroMDA :-) > > Actually a good idea! > > > working but it avoids loading resources bundles with constants > (adding > complexity) > > Although I think the idea from Wouter was also not bad, > just to add a resource bundle within the META-INF or so, which > defines the stereotypes... So you can use stereotypes you want > to use ;-) > > Anyway, I would be thankful if any core developers of AndroMDA > can give me a hint, what is the best way to do this *now* ;-) > (instead of using <<PrimaryKey>> -> <<primaryKey>>, etc): > > - Change the core code and recompile AndroMDA > - Extend with my own ScriptHelper? If yes, how? > > I'm using AndroMDA 2.x. Thanks a lot! > > Greets, > -- > --------------------------------------------------- > Blasius Lofi Dewanto > --------------------------------------------------- > OpenUSS - Open University Support System > http://openuss.sourceforge.net > --------------------------------------------------- > E-Mail : [EMAIL PROTECTED] > ICQ : 39343280 > --------------------------------------------------- > > > > > ------------------------------------------------------- > 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 ------------------------------------------------------- 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
