On Wed, 31 Oct 2007 09:39:36 -0200, Ognen Ivanovski
<[EMAIL PROTECTED]> wrote:
b) decoration of multiple services might not be as expressive as one
would like it to be if one would like use declarative transaction
management. Work is being done here
(http://tapestry.apache.org/tapestry5/tapestry-ioc/decorator.html see
Targetting multiple services).
That page says:
"Note: Another idea will be other ways of matching services: base on
inheritance of the service interface and/or based on the presence of
particular class annotations on the service interface. None of this has
been implemented yet, and can readily be accompllished inside the
decorator method (which will return null if it decides the service doesn't
need decoration)."
Well, it's not entirely true. If you write a @Match("*"), Tapestry-IoC
throws an exception telling that you cannot decorate internal Tapestry-IoC
services. I'll file a JIRA about this.
--
Thiago H. de Paula Figueiredo
Desenvolvedor, Instrutor e Consultor de Tecnologia
Eteg Tecnologia da Informação Ltda.
http://www.eteg.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
