And even better if articles get updated :)
For example, your article was my first encounter with Perf4J and
implemented it in the same way, unfortunately after move to T5.3.0 I get
several dozens of warnings about things that are deprecated. I tried to
fix them all and after one hour, I understood that I don't know Tapestry
well enough to be able to overcome these changes and perform them myself.
Why? Because the documentation says this is deprecated, insteal use
_this_, but sometimes they even don't have similar signature. So now I
have to wait for a new version of your article :)
And I think this is a general problem with Tapestry, there are some
tutorials for beginners, but the more complex stuff is not well
explained or sometimes it is outdated and not fully working with new
version.
One typical example is the user guide for tapestry-hibernate which ends
like this:
"Here, we're using the Hibernate Session object to find all Address
objects in the database. Any sorting that takes place will be done in
memory. This is fine for now (with only a handful of Address objects in
the database). Later we'll see how to optimize this for very large
result sets."
And we have not seen yet this "later" or advanced chapter.
On 07/13/2011 01:59 AM, Taha Hafeez wrote:
resources on internet. We need more blog posts to appear in a search
than mailing list discussions. regards Taha On Wednesday, June 29,
2011, Taha Tapestry
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
