>> Now I have no idea if we support wars inside a contribution (anyone >> care to comment?). I suspect not at the moment. So I would be more >> comfortable with documenting a restriction here. > > implementation.web is to be used only inside a WAR or an EAR. If the WAR is > packaged in another contribution, implementation.jee should be used. >
Interesting Vamsi. I hadn't appreciated from the spec that the archive attribute of implmementation.jee could refer to a war or ejb jar archive. I'll add some notes to the scenario list. As an aside to this I've just checked in changes to allow for contribution type specific classloading so, using this scheme, an EAR, WAR or even JAR can all exploit different classloading schemes. Simon
