On Fri, Apr 17, 2009 at 4:12 PM, Simon Laws <[email protected]> wrote: > Ok, well if I can discount the ear as a problematic case due to the > way that ears are naturally structured then the problematic case > becomes one of multiple wars in a contribution. I.e. > > my.jar - a contribution > WAR1Nested.war/ > META-INF/ > MANIFEST.MF > classpath=EJBNested.jar > WEB-INF > Web.xml > lib/ > classes/ > packageb > ServletA.class > has reference "serviceReference" of type ServiceA.class > tags/ > page1.jsp > > WAR2Nested.war/ > META-INF/ > MANIFEST.MF > classpath=EJBNested.jar > WEB-INF > Web.xml > lib/ > classes/ > packageb > ServletA.class > has reference "serviceReference" of type ServiceA.class > tags/ > page2.jsp > > myContribution.contribution > <component name="componentA"> > <implementation.web web-uri="WAR1Nested.war"/> > <reference name="serviceReference"> > <interface.java interface="packagea.ServiceA"/> > </reference> > </component> > > <component name="componentB"> > <implementation.web web-uri="WAR2Nested.war"/> > <reference name="serviceReference"> > <interface.java interface="packagea.ServiceA"/> > </reference> > </component> > > > Now I have no idea if we support wars inside a contribution (anyone > care to comment?). I suspect not at the moment.
I suspect not too though i've not tried. A war inside a jar contribution doesn't seem to me like something we should be trying to support, a war inside a zip contribution on the other hand seems better. ...ant
