Christian has a point. Basically, existing code (from a third party library) that call getService() expects to see the signature getService(Class), but that method not longer exists, instead its getService(Class,Class[]) (give or take).
I think this is serious enough to justify another RC. On Wed, Nov 2, 2011 at 9:22 AM, Thiago H. de Paula Figueiredo <thiag...@gmail.com> wrote: > 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 > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
