Thanks for the answers. I understand that ServiceBinder (and all the stuff behind it) come from tapestry packages cannot invoke my package-private constructors. By now I code builder methods for all implementations. That works for me and is not too much more code than calling the bind() methods.
One idea that came to my mind is an abstract implementation of thesServiceBinder interface. A programmer could put a subclass of that into the package containing the implementations and use it as the parameter to the bind-Method. That way it would have access to the package-private stuff. I've surfed a bit through the tapestry classes. But understanding, what's going on behind the scenes is sth. that goes beyond my skills ;-)). Good to be here again, nillehammer ----- original Nachricht -------- Betreff: Re: T5.2.2 IOC: Non public service implementations Gesendet: Do, 04. Nov 2010 Von: Thiago H. de Paula Figueiredo<thiag...@gmail.com> > On Thu, 04 Nov 2010 11:44:57 -0200, Tom van Dijk <t...@tvandijk.nl> wrote: > > > I think there is a problem with invoking constructors of package private > > classes. There would be IllegalAccessExceptions. > > I agree. The code that instantiates the services are in a Tapestry package > > and using a package-private constructor from another package is illegal. > > -- > 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 > > --- original Nachricht Ende ---- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
