I caught up with Vamsi off list and it seems that a clearer way of specifying the classloaders that get applied to the in memory JEE model is in order.
I'm reminded that the TCCL approach is taken currently so that containers (such as Geronimo) can push classloaders into this JEE model from outside of Tuscany and in this code you can see the temporary classloaders are being replaced with TCCL (albeit by reflection). Its made a little more opaque because this JavaEEModuleHelper is called multiple times in the Geronimo plugin for different levels of the JEE model (EAR, JAR, WAR) depending on the contents of the JEE app being processed as a contribution. I don't have specific answers yet but we need to document the end to end operation of classloading in this space and make sure that we understand how the code can work in all the situations we need it to. It's particularly tricky making the JEE and SCA sides of the classloading story work together I suggest we extend this thread for a while as we exchange thoughts/ideas. Simon
