Because Tapestry 5 IoC is defined partially in terms of itself, there's some "bootstrapping" that's going on. Most of the services in T5 IoC, inlcuding TypeCoercer, are so fundamental that allows decoration on them would result in cyclic dependencies just instantiating them. A few aren't even instantiated as services; they are instantiated as instances and simply exposed as services.
Oh, and it's Java's limited concept of Generics and extended types that's failing you; there is no way to "sniff" an instance of Collection and determine what generic types apply to it. On Thu, May 28, 2009 at 8:33 AM, formpost <[email protected]> wrote: > > I've been trying to decorate the TypeCoercer Service with no luck, and then I > found this little line in the online docs. > > It is not possible to decorate the services of the TapestryIOCModule. > > Why are these services so special? > > Why would I want to, well.... > > I'm trying to coerce between a collection of domain types and their Ids and > back again. I can do it with a single type, but handling collections is a > different matter and basically tapestry 5 isn't allowing me to. > > Any thoughts? > > > -- > View this message in context: > http://www.nabble.com/Decorating-IOC-Services-tp23764254p23764254.html > Sent from the Tapestry - Dev mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator of Apache Tapestry Director of Open Source Technology at Formos --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
