On 07/13/2011 02:41 AM, Taha Hafeez wrote:
This is an unfair comment. I always check any comments and try to respond to
them as soon as possible. It is not possible to remember which of my article
is outdated. All you have to do is add a comment at the bottom of the
It would have been a truly unfair comment, if I put it on your site and
complained on your site that your article is not up2date with some
future technology - T5.3.0.
Your article (on Perf4J integration) is more than fine and easy to
follow and it worked out fine with my application in 5.2.6.
But, this is THE mailing list to discuss tapestry, and since 5.3 is on
it's way, I guess this is the right place to discuss some future migrations.
So you don't have any problem with it, you are just fine.
So, when I upgraded the application to 5.3.0, i get that for example these:
org.apache.tapestry5.services.ClassTransformation;
org.apache.tapestry5.services.ComponentClassTransformWorker;
org.apache.tapestry5.services.ComponentMethodAdvice;
org.apache.tapestry5.services.ComponentMethodInvocation;
org.apache.tapestry5.services.TransformMethod;
are all deprecated.
Unfortunately I don't undestand the docs well enough to be able to code
it all in the new way.
Again this is not your problem, or problem with your article. It is my
problem.
That is why I will have to wait until a new version of the article.
So you see this is just an encouragement. :)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
