I can't say that I've used generic services before. I was assuming that under the hood, Tapestry would think that there were two instances of the same interface (due to type erasure). I have provided you with a way of dealing with two services of the same interface. Tapestry also supports custom marker annotations which I did not mention instead of using a name.
I'm not sure what the consequences of ASM not supporting generics are... whether things blow up or whether they gracefully degrade to non-generics. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Using-generics-in-tapestry-service-tp5700399p5700569.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
