Currently you can use module tag with a module id. But thats not the 80% of cases i want to cover here and we are not limited in future to extend it. Im fine to get the same tag in different section. We spoke of a webapp tag too
Wdyt? Le 12 sept. 2012 04:10, "David Blevins" <[email protected]> a écrit : > > On Sep 9, 2012, at 11:25 PM, Romain Manni-Bucau wrote: > > > <application> <!-- i'd ignore the name in the parsing for the moment --> > > <Properties> > > <!-- nested or not, just use what you need/want/like --> > > </Properties> > > > > <!-- here are the choices --> > > <Ejb> > > <Properties> > > foo = bar > > </Properties> > > </Ejb> > > <Pojo> > > <Properties> > > foo = bar > > </Properties> > > </Pojo> > > > > </application> > > Ignoring EJBs for a moment and focusing just on pojos. How would I > configure this: > > colors.ear > META-INF/app-ctx.xml > orange.war > WEB-INF/classes/org.superbiz.ColorWebService > red.war > WEB-INF/classes/org.superbiz.ColorWebService > > > > > <application> > <Pojo class="org.superbiz.ColorWebService"> > <Properties> > color = rojo > </Properties> > </Pojo> > <Pojo class="org.superbiz.ColorWebService"> > <Properties> > color = anaranjado > </Properties> > </Pojo> > </application> > > > How do I uniquely configure the ColorWebService for each module? > > > -David
