Static or final fields might be appropriate, as would moving logic out
to a service.
The point of deprecating @Retain is that you can no longer trust that
objects in component fields will only be visible to one thread at a
time.
Making the field final at least prevents race conditions related to
The type Retain is deprecated,what else can we use,or just use the static
fields?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/As-the-type-Retain-is-deprecated-what-else-can-we-use-in-tapestry5-2-tp2643223p2643223.html
Sent from the Tapestry - User mailing list archive
Thanks! I'll look into this as soon as I can.
On Sat, Aug 21, 2010 at 5:03 AM, Paul Field wrote:
> FYI, Tapestry360/tapestry.formos.com has two problems:
>
> The JIRA instance does not seem to be working:
> http://tapestry.formos.com/jira/ returns a blank page
>
> Most of the nightly builds are
I'd like to announce the latest snapshot of the Tapestry Testify project at
Tapestry 360:
http://tapestry.formos.com/nightly/tapestry-testify/
Tapestry Testify is an extension to Tapestry that allows you to write page
and component tests very easily and have them run very efficiently.
** Release
FYI, Tapestry360/tapestry.formos.com has two problems:
The JIRA instance does not seem to be working:
http://tapestry.formos.com/jira/ returns a blank page
Most of the nightly builds are broken:
http://tapestry.formos.com/bamboo/start.action
This seems to be bacause of a change in Maven that re
