On Thu, Jan 14, 2010 at 7:55 PM, Luciano Resende <[email protected]> wrote: > On Thu, Jan 14, 2010 at 4:23 AM, ant elder <[email protected]> wrote: >> It turns out that the Tuscany webapp runtime is only working with Java >> classes in the webapp as the web-inf/classes folder is in the Tuscany >> parent classpath and they're not being used from the Tuscany >> ClassLoaderModelResolver. Thats because we're using the root webapp >> folder as the contribution root so all the Java resource names get >> prefixed with "WEB-INF/classes/" in the contribution artifacts so the >> they're never found by the Tuscany resolver when the artifact is being >> looked for. It may be possible to fix that by simply changing the >> contribution root to be WEB-INF/classes/ (should work, but not tried >> yet) but that would break any Tuscany extension that tries to use >> resources outside of there (eg implementation.widget). That does seem >> like the best fix for now, it certainly looks like the easiest, does >> anyone have any alternatives? >> >> ...ant >> > > We had this discussion in the past, and [1] describe various reasons > why we shouldn't go into this direction... > BTW, I thought we had fixed this issue in the past, do you know if we > still have the same issue in 1.x ? > > [1] http://markmail.org/thread/r6ab6p6t2xghjowr > >
Yes this has come up a number of times that i can remember, though its hard to work out if there's any conlusions in that thread you reference. I guess we just need to understand what we say the contribution and contribution classloader is in the webapp runtime. It turns out though that the problem I'm having is actually caused by a bug or feature of ServiceDiscovery.getContextClassLoader, I'll post about that in a new thread. ...ant
