Me too.
I used to write classes that ALWAYS implemented runnable (I think I picked up
the habit from needing to renegotiate layer 2 stuff at some point in comms
land) - this allowed me to dump classes into any thread pool to do a task.
I've found tapestry to be able to give me that level of "
That's cool - I like the idea of multiple sub-projects. It prevents
Tapestry from turning into "Bloat Ware".
(e.g. I never did understand why Sun decided to ship all the javax
packages with standard java!??)
Steve.
On 3 September 2011 22:34, Dragan Sahpaski wrote:
> Hi,
> There is a separate pr
Hi,
There is a separate project called tapestry-kaptcha. That's what you are
looking for.
They are not part of tapestry-core due to the discussion here
http://tapestry.1045711.n5.nabble.com/T5-3-and-tapx-tt4627854.html
Just add it to your app as a dependency.
Cheers
On Sat, Sep 3, 2011 at 4:10 P
Hello,
I have recently updated one of my webapps from 5.2.6 to the recently
released 5.3. beta. The only thing I had to change was code using the
Predicate, because it is an interface and not an abstract class anymore.
Based on the information posted here http://tapestry5.de/ and here
https://git
