I describe here a few steps that a naive user would do to remove the need for EJBs in her project:
When andromdapp:generate runs, it creates a project with support for EJB 2.0, even if the user selects Spring as the preferred way to structure the application. In the generated andromda.xml, it says:
<!-- to remove any dependency on EJB, comment the following property -->
If the user comments the property and wants to rebuild, she gets an error message concerning ejb-jar.xml because the packaging type of the core project is still ejb. So, the user changes core/pom.xml like this:
Now, the whole project builds fine. However, it does not run in JBoss because the library jars are not on the classpath any more. Before, they were on the EJB manifest classpath. See this forum entry for the problem: http://galaxy.andromda.org/forum/viewtopic.php?p=16864
So, I suggest to add one more question to the project generator:
"Do you want to run Spring with EJB? yes/no"
If yes, generate everything as it is now. If no, generate everything without EJBs and still make sure that the jars are on the classpath, again.