Hi Wouter, well, it's a tricky design decision. My thoughts were as follows: If you look at the ejb-ref, you will see this:
<ejb-ref > <ejb-ref-name>DecisionServiceRef</ejb-ref-name> <ejb-ref-type>Session</ejb-ref-type> <home>org.andromda.samples.animalquiz.decisiontree.DecisionServiceHome</ home> <remote>org.andromda.samples.animalquiz.decisiontree.DecisionService</re mote> <ejb-link>DecisionService</ejb-link> </ejb-ref> <ejb-ref> <ejb-ref-name>DecisionServiceRef</ejb-ref-name> <jndi-name>ejb/org.andromda.samples.animalquiz.decisiontree/DecisionServ ice/Remote</jndi-name> </ejb-ref> There is much information that the EJB cartridge already knows, in fact, all of the above! If you replicate all this knowledge in bpm4struts and if one day you change any of the naming rules, you will have to modify two cartridges (EJB, bpm4struts) where one would be sufficient (EJB). > I say: Let the web generate dependencies for each technology > it can connect to, not the otherway around. No, I'd prefer a separation of concerns: + Let the EJB cartridge be responsible for generating the <ejb-ref> in a merge file. + Let bpm4struts generate a "slot" for the merge file (if necessary at all). + Let the build file (maven.xml?) of the application being built (animal-quiz) be responsible to push the generated merge file into the "slot" of the web application. So, bpm4struts and the app's maven.xml file will only have to know that there *are* merge files but do not need to know anything about their *syntax and contents*. I think, this gives us and the user the easiest way to maintain the various cartridges because changes will always affect one cartridge at a time! Just my 2 cents, Matthias > -----Original Message----- > From: Wouter Zoons [mailto:[EMAIL PROTECTED] > Sent: Monday, March 22, 2004 9:52 PM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: about moving ejb-refs elsewhere > > > Matthias, > > Chad told me you wanted to move part of the web.xml into the > ejb-cartridge and generate it there > > Okay, I understand, and even considered it too when I first > added that code > > I don't like it because what will you do after you have the > file generated ? will the ejb cartridge copy it into the web > dirs, or will the web module fetch the file from the ejb dirs ? > > One way or the other one tier will depend on the other, I > prefer the web to depend on the ejb, mainly because that's > how it is in the specs: The web.xml contains ejb-refs > > I say: Let the web generate dependencies for each technology > it can connect to, not the otherway around. > > I prefer to keep things as they are, unless someone comes > with an absolute clean solution of course. > > Comments ? suggestions ? > > regards > Wouter. > > > > ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click _______________________________________________ Andromda-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-devel
