Woa this is neat!!... but I am having a little trouble understanding how/why this scenario works:
1. I create "service A" (but unbound in my AppModule) 2. Then create "service B" inheriting from Service A (bound in AppModule) Tapestry not only allows me to Inject service A, but allows me to use it as if it has been bound? is Tapestry creating the proxy for the supertype? cheers, Peter --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
