Hi Chad;


My comments are not directed at the concept of AndroMDA and approach, but at 
its state with regard to handeling large models. When you say that:



"AndroMDA is an MDA generator..."



then you are talking about all generation tasks (Model Driven Architecture 
Artifacts Generator), including DB Schema artifact generation. My understanding 
is the goal of an MDA tool is to work as much as possible with Models and let 
the MDA tool automate the generation tasks which is exactly what AndroMDA is 
trying to do, isn't it? If I to start running Hibernate, Spring, Struts, and 
what have you outside AndroMDA then where is the code generation promise of 
AndroMDA.



When you say:



"You continue to confuse andromda with Hibernate and Maven. AndroMDA != Maven, 
AndroMDA != Hibernate. "



I think we all agree on that AndroMDA != Maven, AndroMDA != Hibernate. The 
issue is that you are looking at AndroMDA on equal footings with its components 
which is not my understanding and I don't feel alone in this. It is not that 
AndroMDA!=Maven and AndroMDA!=Hibernate, that is a given when talking about 
whole-part relationship; It is about AndroMDA=Maven+Hibernate+Spring+... when 
one part breaks the whole thing is considered broken.



An example analogy is when one says that my car stopped working in the middle 
of the road and I can't go to my destination, one come along and says not to 
blame the care, just blame this or that part, the car is fine. Well you can see 
that is an akward statement. It doesnot work that way. You are using a car 
(AndroMDA) with all of its parts to chieve a goal (develope an MDA based 
application) and not using a collection of parts (Hibernate, Spring, maven, 
etc.). The parts has to fit with each other such that when the whole thing work 
it does so because all the parts are working and the whole thing is broken when 
even one part is broken.



Again, it is probably a simple fix to Maven or Hibernate to bring back AndroMDA 
to work flawlessly as a whole but that is what we as users are trying to do, 
find the issues and address them, nothing more and nothing less. 



AndroMDA is a great tool and I spend lots of time trying to learn it and try 
using it and will continue to do so.



Thanks to you and Wouter and other contributors the tool is getting better and 
better everyday.



Best regards



Safaa
--
Safaa Hashim
_________________________________________________________
Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=3773#3773
Posting to http://forum.andromda.org/ is preferred over posting to the mailing 
list!


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Andromda-user mailing list
Andromda-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/andromda-user

Reply via email to