Wouter:
Your statement: "You're basically saying that if there's a bug in commons-lang which makes your application throw a runtime Exception it's the responsability of the AndroMDA developers to get it fixed (same story for all the other dependencies) " Is not what I am saying. Here is what I am BASICALLY SAYING: -- I don't think there is a bug in any o fthe tools that AndroMDA uses such as Hibernate, commons, Maven, etc. The bug is in AndroMDA glue code, that is what I am saying. - The glue code the AndroMDA uses to fire tools or wrap tools such as maven build scripts, Hibernate commands in those scripts, etc. could be the culprit in MY CASE and I have a prove of this. That is what I am saying. By glue code, I mean things like the Maven scripts, the hibernate cartridge scripts, and whatever an AndroMDA code means. What prove I have to backup my claim? well I said it before and I will say it again: -- When I use AndroMDA to generate schema from a model I can only go as far as generating the code and then the jar:jar goal gets into a Java Error which I reported that is probably (AGAIN I SAY PROBABLY) due to string buffer overflow in the SchemaExport command or something else. Well after 4 days of trying to fix it and trying different things I was able to run teh same export command using the same code that was generated by AndroMDA and using the same version of Hibernate and Ant, I was able to move beyond the point that AndroMDA crashed. In fact you can see my other threads related to issues I am dealing with as a resullt of using the manual approach to generate the Schema directly using Hibernate and Ant outside AndroMDA. -- So I am confident it is somewhere in AndroMDA, the maven.xml build script or somewhere else the problem lies, in Fact Carlos Cuenca has pointed out someting that I will try to explore as a way to make the build process uses a different way to fire the SchemaExport command. In my mind this is a scalibility issue for AndroMDA. This problem doesnot occure for medium and small sized models. In fact for the last2-3 weeks you and Chad helped me addresss similar scalibility issues in AndroMDA when Chad made changes to the way static blocks are written in the generated code if you remember. This current issue is just one of many that I am facing as I keep working with such a large model and trying to finish the development cycle in AndroMDA. Thanks Safaa _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=3815#3815 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
