[ http://jira.andromda.org/browse/SPRING-107?page=comments#action_12306 ] Joel Kozikowski commented on SPRING-107: ----------------------------------------
Per my discussion on the <a href="http://galaxy.andromda.org/forum/viewtopic.php?t=1066";>forums here</a>, I have added support for Rich Client development, with additional support for those using Eclipse as their IDE. The attached file richClient1.0.txt is a patch to AndroMDA 3.2 RC1 that adds the following: 1. Modifies the Spring cartridge to support a cleaner code structure. In particular, additional outlets are defined to allow source code directories for client specific code and server specific code. This is in addition to the current outlets (where "common" code is located). These new outlets are only activated if the "richClient" namespace property is set to "true." 2. Modifies the Spring cartridge to generate a web.xml file specific for use of server side code that is NOT web based. This file is only generated if the "richClient" namespace property is set to "true" 3. Adds generated JUnit unit test shell code for creating client side test modules. This allows the developer to quickly test the remote communication functionality of their services. 4. Modified the Ant based project generator to allow for generation of a project with a structure appropriate for Rich Client development. Source code and targets are segregated by client, common, and server modules. 5. The resulting project generated by the Ant based project generator has additional files created for support of development using Eclipse. In particular, a single build.xml is generated that allows easy generation of code from models, .jar and .war files from compiled code, and deployment of .war files on a local server, all from within Eclipse WITHOUT the need for a Maven add-on. .project and .classpath files are also created, to allow for quickly "importing" the project into Eclipse and immediately start developing after the project is created. 6. The Ant based project generator was modified slightly to allow for the selection of a "project template". Two such templates currently exist: the old J2EE template, and the new rcp-app template. This sets us up for the future to support "project cartridges", which will allow the developer to select from a variety of project templates that suites their needs and desires. > Rich Client Support > ------------------- > > Key: SPRING-107 > URL: http://jira.andromda.org/browse/SPRING-107 > Project: Spring Cartridge > Type: New Feature > Versions: 3.1RC1 > Environment: Java: 1.4.2_08 > Spring: 1.2.3 > Maven: 1.0.2 > OS: Windows XP Pro > Reporter: Diego Bendlin > Assignee: Peter Friese > > When generating a fresh new Spring project by default it's build to be > dependent on EJB, it is possible to disable this dependencies by commenting > the necesary namespace properties and adding others like remoting type, > remote server and remote port. > When trying to build a non web app some code needs to me manually edited in > the generated web.xml file in order to have the spring dispatcherServlet load > the application context and thus getting the services published on the > specified server and port. > It would be nice if andromda generation process could generate this code > automaticaly, and also consider that users might not be building a web based > app. > For a complete reference please see > http://galaxy.andromda.org/forum/viewtopic.php?t=715 > Peter Freise (freter) said he was already thinking how to implement this and > wanned me to asign this issue to him, but im not able to do so due to > andromda's JIRA settings ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
