Maybe you could use a custom annotation on the service... just like those used for disambiguate services and make that anntotation only visible to the service that needs the private service...
I 'm not really sure about this... in fact i haven't tested it and... most important i think this way of doing this seems quite hacky... perhaps someone else got better invoice on this subject. just throwing my ideas on the list... Nicolás.- On Tue, Mar 27, 2012 at 7:04 AM, fmaylinch <ferranmayli...@gmail.com> wrote: > Hello, > > We've found that some times we would like to define a service that will > only > be used from some specific services (for example, services inside the same > package). > > Is there any way to do this in Tapestry? This way, the developer won't use > that "private" service from places where it is not supposed to be used. > > We tried to declare its interface as "package-private" but it seems that > Tapestry can't find a package-private interface even when the module (where > the interface is binded) is inside the same package. > > Thank you! > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/How-to-define-a-private-service-a-service-only-for-another-service-tp5597443p5597443.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
