[ http://issues.apache.org/jira/browse/TAPESTRY-651?page=all ]
Jesse Kuhnert resolved TAPESTRY-651.
------------------------------------
Resolution: Won't Fix
Though an admirable idea, the component / page enhancement worker chain in
hivemind seems to provide more than enough support for adding your own custom
processing rules on classes. (like annotations)
> Bind Interceptors to Tapestry Listeners
> ---------------------------------------
>
> Key: TAPESTRY-651
> URL: http://issues.apache.org/jira/browse/TAPESTRY-651
> Project: Tapestry
> Issue Type: New Feature
> Components: Framework
> Affects Versions: 4.0
> Reporter: Jian Sun
> Priority: Minor
>
> It will be very helpful to add "Interceptor" property injection in Tapestry
> pages. such as:
> @InjectInterceptor ("util.TimerInterceptor,
> transaction.TransactionInterceptor")
> public void formSubmit() {
> getDao1().save();
> getDao2().save();
> getDao3().delete();
> }
> It not only looked more intuitive, It will make the whole application more
> flexiable.
> I knew there is a way to write a page enhancer, but definitely it need you to
> dig into very basic of Tapestry and increase the learning time.
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
