Thanks Vangel, that's very helpful information. Best of luck with your upgrade.
Anyone else have experiences to share? Regards, Jim. -----Original Message----- From: Vangel V. Ajanovski [mailto:a...@ii.edu.mk] Sent: 22 May 2010 10:55 To: Tapestry users Subject: Re: > 5.1.0.5 in production anywhere? On 05/22/2010 10:16 AM, Jim O'Callaghan wrote: > Is anyone using a version newer than 5.1.0.5 in production for their > application? There are a few nice to have more recent additions that would > be useful in our application but it would be interesting to hear first-hand > experience of any stability issues. > I intend to run the latest version of our app build arround the latest 5.2.0-SNAPSHOT in production from next week with a selected group of a 200-300 users, but at this moment there is just one small bug that stops me that I should try to fix, for which I am not sure if it is a problem with our application or with Tapestry, and I don't yet have the time to check. In BeanEditForm one should not "add" properties that already exist. But when such properties are not atomic like string or int, for example a property I have is of the class FacilityType, they are not visible. Of course they are not because Tapestry does not know how to show them and you have to create a "parameter" block to specifiy how to display them. But this is not enough for some pages, and is enough for others in our version with 5.2.0-snapshot. Under 5.1.0.5 it was all ok. In 5.2.0 i have to "add" these properties alhough they already exist. But when I "add" them, then Tapestry only runs OK for the first time I submit the form. The next time I open the same page Tapestry complains that the property already exists in the model, but after a refresh in the browser everything seems normal and you can continue working. On the other hand there are other pages where I am not forced to "add" the already existing property and the "parameter" block is enough. This is just a first report and I am not yet sure if this is a problem with Tapestry or with how our pages are built. But since it's not a stopper bug, and you can continue working after a refresh, it is down the priority for us at this moment and I will not try to find it and state the nature til I am sure and that will happen only after several days. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
