[ http://jira.andromda.org/browse/SPRING-129?page=comments#action_12231 ] Peter Friese commented on SPRING-129: -------------------------------------
The problem can be solved with a mini-patch in the applicationcontext.vsl file (I already have it at hand): instead of turning off DAO references alltogether when the entity outlets have not been set, we should generate DAO references whenever there is at least one entity in the model. > Services should refer to DAOs even if DAOs will not be generated > ---------------------------------------------------------------- > > Key: SPRING-129 > URL: http://jira.andromda.org/browse/SPRING-129 > Project: Spring Cartridge > Type: Improvement > Versions: 3.1RC1 > Reporter: Peter Friese > Assignee: Chad Brandon > Fix For: 3.1RC1 > > I have a model containing some entities and some services. Let's asume > ServiceA depends on EntityA and EntityB, while ServiceB only depends on > EntityB. Since I want to deploy my application to more than just one node, I > have the generator run twice in order to achieve the following behaviour: > 1) all Entity code gets rendered into a project named "domaindata" > 2) ServiceA gets rendered into a project named "coreserver" > 3) ServiceB gets rendered into a project named "optimizationserver" > All Entity stuff will be packaged as a JAR file, whereas the services stuff > will be packaged as a WAR file. In order to let the Services access the > database, we need to copy the domaindata.jar file into the WEB-INF/lib > directory of the services WAR files. > So far, so good. However, the applicationcontext.xml files in the server > projects do not contain the references to the DAOs. Which makes accessing the > database quite cumbersome ;-) ------------------------------------------------------- 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 Visit http://www.jboss.com/services/certification for more information
