On Wed, 06 Nov 2013 12:11:48 -0200, Muhammad Gelbana <m.gelb...@gmail.com>
wrote:
I can't currently think of an example. But there must be one.
What I can really think of an example now would be to treat one annotation
as if it was another, so you can, for example, use an annotation you wrote
inside your project, say, @MyTransactionalAnnotation, it treated like it
was @CommitAfter automatically inside T-IoC. And, of course, we need to
fix https://issues.apache.org/jira/browse/TAP5-2029 first. I'm on it, I
know how it can implemented, but no ETA yet.
*---------------------*
*Muhammad Gelbana*
http://www.linkedin.com/in/mgelbana
On Mon, Nov 4, 2013 at 10:13 PM, Thiago H de Paula Figueiredo <
thiag...@gmail.com> wrote:
On Mon, 04 Nov 2013 17:49:05 -0200, Muhammad Gelbana
<m.gelb...@gmail.com>
wrote:
What I understand out of this is that it's just a Java EE standard,
that
an annotation may imply other annotations. Personally I like the idea.
Do you have any concrete examples for Tapestry or Tapestry-IoC in which
we
would benefit of that?
I've looked into the AnnotationProvider, thanks for the hint :)
It may not be an eventual implementation, but it'll definetely be part
of
that.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
