Thanks, I've added that one too. (These should appear at
http://tapestry.apache.org/release-notes-52.html within an hour or
two, after the documentation site export occurs.)
On Mon, Jan 17, 2011 at 4:13 PM, Donny Nadolny wrote:
> There's another one I came across looking through JIRA.
>
> Copied
There's another one I came across looking through JIRA.
Copied from https://issues.apache.org/jira/browse/TAP5-1401
In Tapestry 5.1.0.5, you can have code such as:
@Component
private Form inputs;
...
if (inputs.getDefaultTracker().getHasErrors())
...
This fails in 5.2.4 because getDefaultTracke
I took Donny's recommendations from last month as the basis for a new
"Breaking Changes" section at the top of the
https://cwiki.apache.org/confluence/display/TAPESTRY/Release+Notes+5.2
page. Does anybody know of any other "breaking" changes going from
5.1 to 5.2?
On Fri, Dec 17, 2010 at 12:29 PM
> Here are the ones I know of right now:
> 1. Necessary changes for all applications
> - Page classes with instance variables that are not thread safe must
> be created in a method rather than declared. For example, creating an
> instance variable "private final DateFormat format =
> DateFormat.get
There's been a few backwards-incompatible changes from 5.1 to 5.2, I
think it would be helpful to have a place where these are documented.
Since you can't edit the wiki until you sign and mail/fax/scan & email
a license agreement, we can document them here and let someone with
access make the wiki
