So the solution is a Module class in the same package and use builder methods?
----- original Nachricht -------- Betreff: Re: T5.2.2 IOC: Non public service implementations Gesendet: Do, 04. Nov 2010 Von: Tom van Dijk<t...@tvandijk.nl> > I think there is a problem with invoking constructors of package private > classes. There would be IllegalAccessExceptions. > > > On Thu, 4 Nov 2010 14:37:21 +0100 (MET), "nille hammer" > <tapestry.nilleham...@winfonet.eu> wrote: > > Hi List, > > > > long time no write. > > > > I have got used to defining a public interface for my services paired > with > > a package-private implementation. Tapestry's autobinding with > ServiceBinder > > complains about the implementations not being public. I do not want to > make > > the implementations public. So I am afraid I will have to write builder > > methods in the Module class. Can someone confirm that or perhaps show me > a > > way to use autobinding with non public implementations? > > > > Thanks in advance, > > nillehammer > > > > == > > http://www.winfonet.eu > > --------------------------------------------------------------------- > 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