> Is a jar containing nested ear's and war's really a valid thing? We > were just discussing jar's containing jar's last week and ruled them > out. > > ...ant >
Well in this particular case I was trying to show the ear just as a standard thing with wars/jars inside it. As for the ear's relationship with the SCA contribution. The spec says "This specification defines the integration of SCA and Java EE within the context of a Java EE application, the use of Java EE components as service component implementations, and the deployment of Java EE archives either within or as SCA contributions. " Now, in terms of this particular classloader conundrum it doesn't actually make any difference if the ear is the contribution, is inside the contribution or indeed is somewhere else. It still comes down to the question of whether we need to worry about using war classloaders. And if we do how to we distinguish which one to use. I'm trying to think of why we would but I'm coming to the conclusion that maybe we don't have to. Or is that just wishful thinking? Simon
