Lance Java wrote > > Perhaps a solution is to setup a second, private Tapestry IOC registry for > defining your private services. Your public service then looks up the > private service from the private registry instead of from the public > registry. >
Interesting solution... any help on how to do that will be appreciated. Anyway, I think that this solution means there would be many private services together, and they will be available to services they don't belong to. For example, if A1 needs A2 and B1 needs B2, your solution is to put A1 and B1 in the "public" default registry and A2 and B2 in another "private" registry. But that way A1 could access B2 when that is not our intention. But thank you! Maybe we could use that idea somehow. As I said, can you explain me how to do that or give me some ideas? -- View this message in context: http://tapestry.1045711.n5.nabble.com/How-to-define-a-private-service-a-service-only-for-another-service-tp5597443p5600049.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
