Quote: I deleted the entire project again and started over, copying the model file, my project.properties, and project.xml files into the newly generated project. I ran maven and it went through the entire process successfully this time. (end of quote)
In that case, that null file was probably just left over from a previous run, you need to delete Impl files since they are generated once into the src/java directory. Quote: to see if there is model errors. Is this what I should be doing? (end of quote) Sure, I do that sometimes as well, in fact in 3.1 (in CVS) I moved model validation to the beginning of model processing so that it now fails before you generate anything (meaning you don't have to wait to find out if something is wrong with your model). Also added an andromda server you can start that keeps your model loaded and performs validation on it every time you save it, this saves time since you just keep the server running and you can see right away if anything is wrong, then when andromda runs it just connects to the server and doesn't have to initialize or re-load the model again or anything (so much faster), see this for more information on that: http://team.andromda.org/docs/configuration/server-howto.html Quote: This leaves issues with classes that aren't implmenting the method signatures correctly, not deleting things it should and most commonly not adding newly declared methods in interfaces into the *impl.java files. (end of quote) Yes, this is because impl files are only generated once to your src/java file (they aren't overwritten since that's where your business logic will be placed). To get around this you can set the <overwrite>true</overwrite> in your mda/project.xml in the maven-andromda-plugin dependency's properties (until you're ready to start implementing your business logic). About roundtripping, forget about that, you'll go from your model to code, not from code to model, MDA allows us to model things at a higher level of abstraction therefore if you wanted to have code to model you'd need to have very complex mappings for any type of technology you're using, whcih is much more work than it's worth. Your model should be your primary artfact driving your development process. The tools that are good with roundtripping (like together, etc) are basically putting their java code in the model which is completely opposite of what we're trying to accomplish with MDA (which is to abstract us away from the technology). -- Chad Brandon - [EMAIL PROTECTED] http://www.andromda.org _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=853#853 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
