It's ok if you have one project and replace Tapestry 5.1 with 5.3. But if you compile your classes against 5.1 the signature in the .class file is the old one. Without recompiling the code against 5.3 it will throw the mentioned exception.
There's no conflicting jars in the classpath and there's no custom implementation of ObjectLocator. It's just a simple class incompatibility, not a compile one. Am 02.11.2011 um 17:22 schrieb Thiago H. de Paula Figueiredo: > On Wed, 02 Nov 2011 14:18:12 -0200, Christian Riedel > <cr.ml...@googlemail.com> wrote: > >> Hi > > Hi! > >> Can't you support both methods? >> >> <T> T getService(Class<T> serviceInterface, Class<? extends >> Annotation>... markerTypes); >> and >> <T> T getService(Class<T> serviceInterface); > > Isn't a getService(SomeClass.class) call valid for T getService(Class<T> > serviceInterface, Class<? extends> Annotation>... markerTypes)? I think so. > Don't you have any class implementing ObjectLocator? > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and > instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
