Re: any ideas why the APPCATALOG resource being injected would not be getting resolved?..

For what it's worth... I had a similar issue (different error message, but caused mismatched versions of the jars in my classpath). I discovered that in my pom.xml, I had a dependency on tapestry-hibernate, but I didn't have any dependency on tapestry-core. It was pulling in 5.1.0.5 of tapestry-h

Re: any ideas why the APPCATALOG resource being injected would not be getting resolved?..

Looked through the classpath and everything is using 5.1.0.5 Thiago H. de Paula Figueiredo wrote: Em Fri, 22 May 2009 22:59:16 -0300, Tom Zurkan escreveu: i am upgrading from 5.0.18 to 5.1.05. any ideas would be appreciated. Make sure you only have 5.0.1.5 JARs in your classpath. A mi

Re: any ideas why the APPCATALOG resource being injected would not be getting resolved?..

Em Fri, 22 May 2009 22:59:16 -0300, Tom Zurkan escreveu: i am upgrading from 5.0.18 to 5.1.05. any ideas would be appreciated. Make sure you only have 5.0.1.5 JARs in your classpath. A mix of versions can cause problemas similitar to the one you're having. thanks, tom 2009-05-22 18

any ideas why the APPCATALOG resource being injected would not be getting resolved?..

i am upgrading from 5.0.18 to 5.1.05. any ideas would be appreciated. thanks, tom 2009-05-22 18:51:34,709 [btpool0-1] ERROR org.apache.tapestry5.ioc.Registry - No service implements the interface org.apache.tapestry5.ioc.Resource. 2009-05-22 18:51:34,709 [btpool0-1] ERROR org.apache.tapestr