I have never found a use for it, as we can plainly see, it causes a great
deal of confusion and problems. I say remove it.
----- Original Message -----
From: "Howard Lewis Ship" <[EMAIL PROTECTED]>
To: "Tapestry development" <[email protected]>
Sent: Tuesday, August 16, 2005 7:14 PM
Subject: [DISCUSS] Deprecate the action service
I just saw another spat of user problems related to use of the action
service. I say "use", not "misuse" because, in my opinion, it can't be
used correctly. The clever tricks for maintaining client and server
synchronization that have evolved in Tapestry 2.x - 4.0 just aren't
possible with the action service.
I would very much like to deprecate the action service and the
ActionLink component. Who out there is using it and why?
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
