Hi Richard,

I absolutly agree with you. I had the same problem, when we implemented
Jetset (a similar tool to andromda, which we gave up in favour of andromda).
Jetset only wrote a file if the buffer created by velocity was not empty, just
like you described your solution. 
I think this feature is a must for andromda, as the rigid mapping
template->file is too inflexible. Here are two examples, why this is helpful:

1) The Struts cartridge needs one class with a stereotype like
"StrutsConfig" or something similar. This is just needed so the cartridge can produce 
the
mandatory config file. Why not have this file created implicitly, as it is
needed anyway.

2) We are currently working on a cartridge that defines a stereotype
"persistent", which denotes some kind of persistent object which is independant of
any persistent layer like JDO or EntityBeans. "Persistent" allows relations
and even inheritance. Our implementation on EntityBeans creates only one
EntityBean for an object hierarchy of persistent objects. Therefore we need to map
a list of persistent stereotypes to one EntityBean file.
Our current solution uses Andromda to create an EntityBean file for each
persistent stereotype and then we delete all empty files with the <delete> task.

So my conclusion is that this is a really important feature. But I'm not
quite sure if the solution (not to write empty files) is a good solution. It is
simple and easy to implement. But what if we could define this behaviour
within the cartridge descriptor?

Matthias, Anthony what do you think?

Regards,
 Matthias D.



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
Andromda-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/andromda-devel

Reply via email to