Re: An Appeal To Use the Latest Betas
I am running into a problem getting the betas using maven and nexus. My setup is that everything points to my instance of nexus and it in turn points to all the other repositories. I have setup a Release proxy and a Snapshot proxy both pointing to: https://repository.apache.org/content/groups/staging/ For some reason the betas are not showing up in either repository. They are showing up when I browse the remote from within my instance of nexus, but when I click over to browse the index they aren't there. It is almost as if the betas are getting put in the right directory, but the index is not being updated. Another theory is that these betas are being marked as a SNAPSHOT so they don't show up in the Release index, but aren't following the Snapshot naming convention so they don't show up there either. Has anyone run into any similar issues or have any suggestion? Mark On Thu, Oct 13, 2011 at 6:16 PM, Howard Lewis Ship hls...@gmail.com wrote: If you've been following the discussions here and elsewhere, you may be aware that Tapestry 5.3 is nearly done, with big improvements to every aspect of Tapestry, including speed and memory utilization. Our goal is to deliver an upgrade that is as seamless as possible. The PMC would dearly like to get a final release out and available before December (that is, within one year of the release 5.2). However, we can't do it without YOU: We need people actively using Tapestry to upgrade to the latest betas (5.3-beta-20 is the latest, but we're releasing new updates almost every day). We are looking for broken features or problems upgrading ... all the things that will get in the way of a release candidate and then a final release. Your feedback is essential ... without are community, we don't know for sure that Tapestry is ready to go to the next stage. Please budget some time, as soon as possible, to run you application under 5.3 and report back here about any problems you find. Without accurate (and hopefully, positive) feedback, we will not be able to progress to a final release ... and that means we'll be delayed adding the next layer of amazing features in Tapestry 5.4! Please see these notes on how to make use of the latest beta preview releases: http://tapestry.apache.org/2011/08/27/tapestry-53-beta-preview.html http://tapestryjava.blogspot.com/2011/10/tapestry-53-maven-archetype.html I've been posing on twitter each time a new preview is made available: http://twitter.com/#!/search/%23tapestry5 ... and note that by the time you do you upgreade, the exact version number may have changed (don't worry, beta-20 will still be available when beta-21 is made available). Your support is deeply appreciated ... now get back to coding less and delivering more! -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
Hi all, A member of my team tried to upgrade our application and almost everything worked out except for one bit: classes for services which name contain accents are not longer accepted (ej, HorarioSalón). This is a big problem for us since many classes have accents in theirs names. Hope this can be solved. Regards, Manuel.
Re: An Appeal To Use the Latest Betas
Please add a JIRA issue. The workaround is likely to disable service reloading, see the documentation for this. On Mon, Oct 24, 2011 at 8:52 AM, Manuel Sugawara manuel.sugaw...@gmail.com wrote: Hi all, A member of my team tried to upgrade our application and almost everything worked out except for one bit: classes for services which name contain accents are not longer accepted (ej, HorarioSalón). This is a big problem for us since many classes have accents in theirs names. Hope this can be solved. Regards, Manuel. -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
Hi Thiago, So the problem itself was Prototype's backward compatibility instead of Tapestry's? Kind of yes, but I see it as the same thing while Tapestry ships with prototype (excuse the pun Howard)... its the age old problem with using 3rd party libraries, which is why I am so stoked about the abstraction layer. Will it include memory consumption data? That would be very, very interesting. ;) Some, but not sure if its useful.. Our sole purpose of monitoring is to catch an increase / spike in the memory footprint on Tomcat... its a bit difficult for us the get an accurate baseline since we have 6 Tapestry apps running on Tomcat behind Apache (which also has its own apps), the load will vary significantly by the hour; day; and month end, and there are also frequent patches going out. I used to be more diligent about performance monitoring, but I just can't keep up these days. Cheers, Peter - Original Message - From: Thiago H. de Paula Figueiredo thiag...@gmail.com To: Tapestry users users@tapestry.apache.org, P Stavrinides p.stavrini...@albourne.com Sent: Tuesday, 18 October, 2011 15:48:20 GMT +02:00 Athens, Bucharest, Istanbul Subject: Re: An Appeal To Use the Latest Betas On Tue, 18 Oct 2011 10:33:18 -0200, p.stavrini...@albourne.com wrote: After several failed attempts in the past, I finally managed to upgrade from 5.1 to 5.3. I have one application to do the same upgrade, but I still haven't time for it yet. The second was the new Tapestry ajax features and some updates to the prototype library. These effectively broke a lot of ajax components and pages we wrote based on 5.1, firebug to the rescue though. So the problem itself was Prototype's backward compatibility instead of Tapestry's? Overall I am impressed with 5.3, its noticeably faster, and appears to be robust. Nice! :) I will begin load testing next, just before moving over to 5.3 in production. Will it include memory consumption data? That would be very, very interesting. ;) -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
I tried beta-23 and it worked. Thanks, /Serge -- View this message in context: http://tapestry-users.832.n2.nabble.com/An-Appeal-To-Use-the-Latest-Betas-tp6890825p6908988.html Sent from the Tapestry Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
After several failed attempts in the past, I finally managed to upgrade from 5.1 to 5.3. I found two areas had changed significantly... in some respects breaking backwards compatibility. The first being IoC service reloading, which after a good explanation from Howard about how service reloading affects the classloaders, packages and non public members, I did manage to fix by switching it off on the relevant members. The second was the new Tapestry ajax features and some updates to the prototype library. These effectively broke a lot of ajax components and pages we wrote based on 5.1, firebug to the rescue though. Overall I am impressed with 5.3, its noticeably faster, and appears to be robust. Next I will be revisiting the configuration documentation since its been years since I did so, but also because pages are no longer pooled so part of my old configuration is now redundant. I will begin load testing next, just before moving over to 5.3 in production. I am very much looking forward to the next set of features, but particularly JavaScript abstraction layer to follow in 5.4. Cheers, Peter - Original Message - From: Geoff Callender geoff.callender.jumpst...@gmail.com To: Tapestry users users@tapestry.apache.org Sent: Monday, 17 October, 2011 23:45:42 GMT +02:00 Athens, Bucharest, Istanbul Subject: Re: An Appeal To Use the Latest Betas chenille-kit is a blocker for me, too. On 17/10/2011, at 9:56 PM, antalk wrote: http://www.localhost.nu/java/tapestry-spring-security/index.html Im using groupIdnu.localhost.tapestry/groupId artifactIdtapestry-spring-security/artifactId version3.0.0/version And http://www.chenillekit.org/ groupIdorg.chenillekit/groupId artifactIdchenillekit-tapestry/artifactId version1.3.2/version Altough the later could already have a snapshot available ? Oh.. actually there are 3 groupIdus.antera/groupId artifactIdt5-restful-webservices/artifactId version0.2.1/version -- View this message in context: http://tapestry.1045711.n5.nabble.com/An-Appeal-To-Use-the-Latest-Betas-tp4900917p4909469.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
On Tue, 18 Oct 2011 10:33:18 -0200, p.stavrini...@albourne.com wrote: After several failed attempts in the past, I finally managed to upgrade from 5.1 to 5.3. I have one application to do the same upgrade, but I still haven't time for it yet. The second was the new Tapestry ajax features and some updates to the prototype library. These effectively broke a lot of ajax components and pages we wrote based on 5.1, firebug to the rescue though. So the problem itself was Prototype's backward compatibility instead of Tapestry's? Overall I am impressed with 5.3, its noticeably faster, and appears to be robust. Nice! :) I will begin load testing next, just before moving over to 5.3 in production. Will it include memory consumption data? That would be very, very interesting. ;) -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
Hi, The issue I am facing with the upgrade is described here: http://tapestry-users.832.n2.nabble.com/T5-3-x-Service-IDs-Conflict-td6896451.html Any hints to get past this would be appreciated. Thanks, /Serge -- View this message in context: http://tapestry-users.832.n2.nabble.com/An-Appeal-To-Use-the-Latest-Betas-tp6890825p6904506.html Sent from the Tapestry Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
On Mon, Oct 17, 2011 at 10:45 PM, Geoff Callender geoff.callender.jumpst...@gmail.com wrote: chenille-kit is a blocker for me, too. I'm really willing to give an update to chenillekit this coming weekend... hopefully I will be able to respect my plans Cheers -- Massimo http://meridio.blogspot.com - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
I'm renaming the Tapestry SessionFactory to be TapestrySessionFactory. That should help. On Tue, Oct 18, 2011 at 5:59 AM, Serge Eby sd...@hotmail.com wrote: Hi, The issue I am facing with the upgrade is described here: http://tapestry-users.832.n2.nabble.com/T5-3-x-Service-IDs-Conflict-td6896451.html Any hints to get past this would be appreciated. Thanks, /Serge -- View this message in context: http://tapestry-users.832.n2.nabble.com/An-Appeal-To-Use-the-Latest-Betas-tp6890825p6904506.html Sent from the Tapestry Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
Generating 5.3-beta-23 right now. On Tue, Oct 18, 2011 at 8:16 AM, Howard Lewis Ship hls...@gmail.com wrote: I'm renaming the Tapestry SessionFactory to be TapestrySessionFactory. That should help. On Tue, Oct 18, 2011 at 5:59 AM, Serge Eby sd...@hotmail.com wrote: Hi, The issue I am facing with the upgrade is described here: http://tapestry-users.832.n2.nabble.com/T5-3-x-Service-IDs-Conflict-td6896451.html Any hints to get past this would be appreciated. Thanks, /Serge -- View this message in context: http://tapestry-users.832.n2.nabble.com/An-Appeal-To-Use-the-Latest-Betas-tp6890825p6904506.html Sent from the Tapestry Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
I would love too, but our 2 Tapestry applications are heavily dependent on 2 extra libraries that are not in sync with Tap5.3 and thus fail to start/run. Without these libraries our application is pretty much useless so i'll have to wait for the final version or update these libraries myself (but we dont have the time for that) , which leads to being not really a drop-in replacement... -- View this message in context: http://tapestry.1045711.n5.nabble.com/An-Appeal-To-Use-the-Latest-Betas-tp4900917p4908984.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
Which 2 libraries? On Oct 17, 2011 3:33 AM, antalk ant...@intercommit.nl wrote: I would love too, but our 2 Tapestry applications are heavily dependent on 2 extra libraries that are not in sync with Tap5.3 and thus fail to start/run. Without these libraries our application is pretty much useless so i'll have to wait for the final version or update these libraries myself (but we dont have the time for that) , which leads to being not really a drop-in replacement... -- View this message in context: http://tapestry.1045711.n5.nabble.com/An-Appeal-To-Use-the-Latest-Betas-tp4900917p4908984.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
http://www.localhost.nu/java/tapestry-spring-security/index.html Im using groupIdnu.localhost.tapestry/groupId artifactIdtapestry-spring-security/artifactId version3.0.0/version And http://www.chenillekit.org/ groupIdorg.chenillekit/groupId artifactIdchenillekit-tapestry/artifactId version1.3.2/version Altough the later could already have a snapshot available ? Oh.. actually there are 3 groupIdus.antera/groupId artifactIdt5-restful-webservices/artifactId version0.2.1/version -- View this message in context: http://tapestry.1045711.n5.nabble.com/An-Appeal-To-Use-the-Latest-Betas-tp4900917p4909469.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
I would love to be using the latest version of tapestry, but sadly can't due to the jpa issue I'm having with it, described here: http://tapestry-users.832.n2.nabble.com/Problems-using-JPA-with-5-3-td6898469.html -- View this message in context: http://tapestry-users.832.n2.nabble.com/An-Appeal-To-Use-the-Latest-Betas-tp6890825p6901448.html Sent from the Tapestry Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
chenille-kit is a blocker for me, too. On 17/10/2011, at 9:56 PM, antalk wrote: http://www.localhost.nu/java/tapestry-spring-security/index.html Im using groupIdnu.localhost.tapestry/groupId artifactIdtapestry-spring-security/artifactId version3.0.0/version And http://www.chenillekit.org/ groupIdorg.chenillekit/groupId artifactIdchenillekit-tapestry/artifactId version1.3.2/version Altough the later could already have a snapshot available ? Oh.. actually there are 3 groupIdus.antera/groupId artifactIdt5-restful-webservices/artifactId version0.2.1/version -- View this message in context: http://tapestry.1045711.n5.nabble.com/An-Appeal-To-Use-the-Latest-Betas-tp4900917p4909469.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
...using beta-20 and I can't blame you for the bugs in my apps :-) Am 14.10.2011 um 01:16 schrieb Howard Lewis Ship: If you've been following the discussions here and elsewhere, you may be aware that Tapestry 5.3 is nearly done, with big improvements to every aspect of Tapestry, including speed and memory utilization. Our goal is to deliver an upgrade that is as seamless as possible. The PMC would dearly like to get a final release out and available before December (that is, within one year of the release 5.2). However, we can't do it without YOU: We need people actively using Tapestry to upgrade to the latest betas (5.3-beta-20 is the latest, but we're releasing new updates almost every day). We are looking for broken features or problems upgrading ... all the things that will get in the way of a release candidate and then a final release. Your feedback is essential ... without are community, we don't know for sure that Tapestry is ready to go to the next stage. Please budget some time, as soon as possible, to run you application under 5.3 and report back here about any problems you find. Without accurate (and hopefully, positive) feedback, we will not be able to progress to a final release ... and that means we'll be delayed adding the next layer of amazing features in Tapestry 5.4! Please see these notes on how to make use of the latest beta preview releases: http://tapestry.apache.org/2011/08/27/tapestry-53-beta-preview.html http://tapestryjava.blogspot.com/2011/10/tapestry-53-maven-archetype.html I've been posing on twitter each time a new preview is made available: http://twitter.com/#!/search/%23tapestry5 ... and note that by the time you do you upgreade, the exact version number may have changed (don't worry, beta-20 will still be available when beta-21 is made available). Your support is deeply appreciated ... now get back to coding less and delivering more! -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
A question I've been meaning to ask for a wee while now... How do I find out what updates go into each beta release? I've tried poking around JIRA but have not been able to come up with a successful query. (I also admit my JIRA foo is lacking.) You mention Twitter but I've resisted that (and mobile phones!) for so long now that, if possible, I'd rather not! Are there any alternatives? Cheers, Steve. On 14 October 2011 15:59, Christian Riedel cr.ml...@googlemail.com wrote: ...using beta-20 and I can't blame you for the bugs in my apps :-) Am 14.10.2011 um 01:16 schrieb Howard Lewis Ship: If you've been following the discussions here and elsewhere, you may be aware that Tapestry 5.3 is nearly done, with big improvements to every aspect of Tapestry, including speed and memory utilization. Our goal is to deliver an upgrade that is as seamless as possible. The PMC would dearly like to get a final release out and available before December (that is, within one year of the release 5.2). However, we can't do it without YOU: We need people actively using Tapestry to upgrade to the latest betas (5.3-beta-20 is the latest, but we're releasing new updates almost every day). We are looking for broken features or problems upgrading ... all the things that will get in the way of a release candidate and then a final release. Your feedback is essential ... without are community, we don't know for sure that Tapestry is ready to go to the next stage. Please budget some time, as soon as possible, to run you application under 5.3 and report back here about any problems you find. Without accurate (and hopefully, positive) feedback, we will not be able to progress to a final release ... and that means we'll be delayed adding the next layer of amazing features in Tapestry 5.4! Please see these notes on how to make use of the latest beta preview releases: http://tapestry.apache.org/2011/08/27/tapestry-53-beta-preview.html http://tapestryjava.blogspot.com/2011/10/tapestry-53-maven-archetype.html I've been posing on twitter each time a new preview is made available: http://twitter.com/#!/search/%23tapestry5 ... and note that by the time you do you upgreade, the exact version number may have changed (don't worry, beta-20 will still be available when beta-21 is made available). Your support is deeply appreciated ... now get back to coding less and delivering more! -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
RE: An Appeal To Use the Latest Betas
I've taken 5 minutes to try out the beta with my integration test project and besides noticing that chenillekit doesn't declare its dependency on tapestry as provided which leads to an IncompatibleClassChangeError I found the beta-21 to be much stricter about the location of non-managed classes. In 5.2.6 you could still have an interface in the components package (now yields plastics error java.lang.ClassFormatError: Illegal field modifiers in class 0x12) or an enum in the mixin package ( gave an error stating that is should be moved to the base package). I also noticed the new event handler verification. All in all, I think these are acceptable changes if they find their way in the user docs. I also think it would be great if tapestry came repacked with a web-app validation suite that 1) attempts to realize all registered services 2) checks all classes in the managed package for the class format and tapestry-required visibility 3) checks templates of all pages and components known to tapestry Framework errors are a great way to let the developer know that he isn't making any sense or in the case of event handlers that he probably made an error in the functional implementation. However, webapps are usually user-facing and it's a little bit embarrassing to have the webapp barf all over the user just because an empty event handler isn't attached to a form or because an interface isn't in the correct package. Giving the developer a tool to avoid this before deployment would be a great way for the framework cto enhance productivity by essentially prepackaging a crash and burn test. -Original Message- From: Howard Lewis Ship [mailto:hls...@gmail.com] Sent: Freitag, 14. Oktober 2011 01:16 To: Tapestry users Subject: An Appeal To Use the Latest Betas If you've been following the discussions here and elsewhere, you may be aware that Tapestry 5.3 is nearly done, with big improvements to every aspect of Tapestry, including speed and memory utilization. Our goal is to deliver an upgrade that is as seamless as possible. The PMC would dearly like to get a final release out and available before December (that is, within one year of the release 5.2). However, we can't do it without YOU: We need people actively using Tapestry to upgrade to the latest betas (5.3-beta-20 is the latest, but we're releasing new updates almost every day). We are looking for broken features or problems upgrading ... all the things that will get in the way of a release candidate and then a final release. Your feedback is essential ... without are community, we don't know for sure that Tapestry is ready to go to the next stage. Please budget some time, as soon as possible, to run you application under 5.3 and report back here about any problems you find. Without accurate (and hopefully, positive) feedback, we will not be able to progress to a final release ... and that means we'll be delayed adding the next layer of amazing features in Tapestry 5.4! Please see these notes on how to make use of the latest beta preview releases: http://tapestry.apache.org/2011/08/27/tapestry-53-beta-preview.html http://tapestryjava.blogspot.com/2011/10/tapestry-53-maven-archetype.html I've been posing on twitter each time a new preview is made available: http://twitter.com/#!/search/%23tapestry5 ... and note that by the time you do you upgreade, the exact version number may have changed (don't worry, beta-20 will still be available when beta-21 is made available). Your support is deeply appreciated ... now get back to coding less and delivering more! -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
For point 3, try viewing the new PageCatalog page. e.g. http://localhost:8080/PageCatalog There's a button there to load all pages. Steve. On 14 October 2011 19:47, Wechsung, Wulf wulf.wechs...@sap.com wrote: I've taken 5 minutes to try out the beta with my integration test project and besides noticing that chenillekit doesn't declare its dependency on tapestry as provided which leads to an IncompatibleClassChangeError I found the beta-21 to be much stricter about the location of non-managed classes. In 5.2.6 you could still have an interface in the components package (now yields plastics error java.lang.ClassFormatError: Illegal field modifiers in class 0x12) or an enum in the mixin package ( gave an error stating that is should be moved to the base package). I also noticed the new event handler verification. All in all, I think these are acceptable changes if they find their way in the user docs. I also think it would be great if tapestry came repacked with a web-app validation suite that 1) attempts to realize all registered services 2) checks all classes in the managed package for the class format and tapestry-required visibility 3) checks templates of all pages and components known to tapestry Framework errors are a great way to let the developer know that he isn't making any sense or in the case of event handlers that he probably made an error in the functional implementation. However, webapps are usually user-facing and it's a little bit embarrassing to have the webapp barf all over the user just because an empty event handler isn't attached to a form or because an interface isn't in the correct package. Giving the developer a tool to avoid this before deployment would be a great way for the framework cto enhance productivity by essentially prepackaging a crash and burn test. -Original Message- From: Howard Lewis Ship [mailto:hls...@gmail.com] Sent: Freitag, 14. Oktober 2011 01:16 To: Tapestry users Subject: An Appeal To Use the Latest Betas If you've been following the discussions here and elsewhere, you may be aware that Tapestry 5.3 is nearly done, with big improvements to every aspect of Tapestry, including speed and memory utilization. Our goal is to deliver an upgrade that is as seamless as possible. The PMC would dearly like to get a final release out and available before December (that is, within one year of the release 5.2). However, we can't do it without YOU: We need people actively using Tapestry to upgrade to the latest betas (5.3-beta-20 is the latest, but we're releasing new updates almost every day). We are looking for broken features or problems upgrading ... all the things that will get in the way of a release candidate and then a final release. Your feedback is essential ... without are community, we don't know for sure that Tapestry is ready to go to the next stage. Please budget some time, as soon as possible, to run you application under 5.3 and report back here about any problems you find. Without accurate (and hopefully, positive) feedback, we will not be able to progress to a final release ... and that means we'll be delayed adding the next layer of amazing features in Tapestry 5.4! Please see these notes on how to make use of the latest beta preview releases: http://tapestry.apache.org/2011/08/27/tapestry-53-beta-preview.html http://tapestryjava.blogspot.com/2011/10/tapestry-53-maven-archetype.html I've been posing on twitter each time a new preview is made available: http://twitter.com/#!/search/%23tapestry5 ... and note that by the time you do you upgreade, the exact version number may have changed (don't worry, beta-20 will still be available when beta-21 is made available). Your support is deeply appreciated ... now get back to coding less and delivering more! -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
On Fri, 14 Oct 2011 08:47:52 -0300, Wechsung, Wulf wulf.wechs...@sap.com wrote: I've taken 5 minutes to try out the beta with my integration test project and besides noticing that chenillekit doesn't declare its dependency on tapestry as provided which leads to an IncompatibleClassChangeError I found the beta-21 to be much stricter about the location of non-managed classes. In 5.2.6 you could still have an interface in the components package (now yields plastics error java.lang.ClassFormatError: Illegal field modifiers in class 0x12) or an enum in the mixin package ( gave an error stating that is should be moved to the base package). I'm sorry, but putting interfaces and classes that aren't pages in the pages packages, that aren't components in the components package, that aren't mixins in the mixins package and that aren't superclasses of pages, components or mixins have been wrong since the first Tapestry 5.0 snapshot. Committing this kind of error leads to hard to understand errors, so Tapestry catching it and throwing an exception outright is a very Good Thing. ;) I also think it would be great if tapestry came repacked with a web-app validation suite that It could be just another package or even something built in tapestry-core. 1) attempts to realize all registered services Agreed. 2) checks all classes in the managed package for the class format and tapestry-required visibility This is done by the JVM, so I don't know why Tapestry should do that too. 3) checks templates of all pages and components known to tapestry Agreed. Framework errors are a great way to let the developer know that he isn't making any sense or in the case of event handlers that he probably made an error in the functional implementation. However, webapps are usually user-facing and it's a little bit embarrassing to have the webapp barf all over the user just because an empty event handler isn't attached to a form or because an interface isn't in the correct package. If a person deploy an application to the live server without checking for errors first, manually or through automated tests, then I think the problem is responsibility of this person. -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
RE: An Appeal To Use the Latest Betas
Awesome, thanks! Learning something new every day :) -Original Message- From: Steve Eynon [mailto:steve.ey...@alienfactory.co.uk] Sent: Freitag, 14. Oktober 2011 14:18 To: Tapestry users Subject: Re: An Appeal To Use the Latest Betas For point 3, try viewing the new PageCatalog page. e.g. http://localhost:8080/PageCatalog There's a button there to load all pages. Steve. On 14 October 2011 19:47, Wechsung, Wulf wulf.wechs...@sap.com wrote: I've taken 5 minutes to try out the beta with my integration test project and besides noticing that chenillekit doesn't declare its dependency on tapestry as provided which leads to an IncompatibleClassChangeError I found the beta-21 to be much stricter about the location of non-managed classes. In 5.2.6 you could still have an interface in the components package (now yields plastics error java.lang.ClassFormatError: Illegal field modifiers in class 0x12) or an enum in the mixin package ( gave an error stating that is should be moved to the base package). I also noticed the new event handler verification. All in all, I think these are acceptable changes if they find their way in the user docs. I also think it would be great if tapestry came repacked with a web-app validation suite that 1) attempts to realize all registered services 2) checks all classes in the managed package for the class format and tapestry-required visibility 3) checks templates of all pages and components known to tapestry Framework errors are a great way to let the developer know that he isn't making any sense or in the case of event handlers that he probably made an error in the functional implementation. However, webapps are usually user-facing and it's a little bit embarrassing to have the webapp barf all over the user just because an empty event handler isn't attached to a form or because an interface isn't in the correct package. Giving the developer a tool to avoid this before deployment would be a great way for the framework cto enhance productivity by essentially prepackaging a crash and burn test. -Original Message- From: Howard Lewis Ship [mailto:hls...@gmail.com] Sent: Freitag, 14. Oktober 2011 01:16 To: Tapestry users Subject: An Appeal To Use the Latest Betas If you've been following the discussions here and elsewhere, you may be aware that Tapestry 5.3 is nearly done, with big improvements to every aspect of Tapestry, including speed and memory utilization. Our goal is to deliver an upgrade that is as seamless as possible. The PMC would dearly like to get a final release out and available before December (that is, within one year of the release 5.2). However, we can't do it without YOU: We need people actively using Tapestry to upgrade to the latest betas (5.3-beta-20 is the latest, but we're releasing new updates almost every day). We are looking for broken features or problems upgrading ... all the things that will get in the way of a release candidate and then a final release. Your feedback is essential ... without are community, we don't know for sure that Tapestry is ready to go to the next stage. Please budget some time, as soon as possible, to run you application under 5.3 and report back here about any problems you find. Without accurate (and hopefully, positive) feedback, we will not be able to progress to a final release ... and that means we'll be delayed adding the next layer of amazing features in Tapestry 5.4! Please see these notes on how to make use of the latest beta preview releases: http://tapestry.apache.org/2011/08/27/tapestry-53-beta-preview.html http://tapestryjava.blogspot.com/2011/10/tapestry-53-maven-archetype.html I've been posing on twitter each time a new preview is made available: http://twitter.com/#!/search/%23tapestry5 ... and note that by the time you do you upgreade, the exact version number may have changed (don't worry, beta-20 will still be available when beta-21 is made available). Your support is deeply appreciated ... now get back to coding less and delivering more! -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
I saw the following notification in my tomcat log after a tomcat:redeploy SEVERE: The web application [/instihire] registered the JDBC driver [org.postgresql.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered. Oct 14, 2011 12:02:30 PM org.apache.catalina.startup.HostConfig checkResources INFO: Undeploying context [/instihire] To be sure it was beta-21, I completely removed the app from webapps, did a tomcat:deploy followed by a tomcat:redeploy. The same error was logged. Hope this helps. Tony On Oct 14, 2011, at 10:35 AM, Wechsung, Wulf wrote: Awesome, thanks! Learning something new every day :) -Original Message- From: Steve Eynon [mailto:steve.ey...@alienfactory.co.uk] Sent: Freitag, 14. Oktober 2011 14:18 To: Tapestry users Subject: Re: An Appeal To Use the Latest Betas For point 3, try viewing the new PageCatalog page. e.g. http://localhost:8080/PageCatalog There's a button there to load all pages. Steve. On 14 October 2011 19:47, Wechsung, Wulf wulf.wechs...@sap.com wrote: I've taken 5 minutes to try out the beta with my integration test project and besides noticing that chenillekit doesn't declare its dependency on tapestry as provided which leads to an IncompatibleClassChangeError I found the beta-21 to be much stricter about the location of non-managed classes. In 5.2.6 you could still have an interface in the components package (now yields plastics error java.lang.ClassFormatError: Illegal field modifiers in class 0x12) or an enum in the mixin package ( gave an error stating that is should be moved to the base package). I also noticed the new event handler verification. All in all, I think these are acceptable changes if they find their way in the user docs. I also think it would be great if tapestry came repacked with a web-app validation suite that 1) attempts to realize all registered services 2) checks all classes in the managed package for the class format and tapestry-required visibility 3) checks templates of all pages and components known to tapestry Framework errors are a great way to let the developer know that he isn't making any sense or in the case of event handlers that he probably made an error in the functional implementation. However, webapps are usually user-facing and it's a little bit embarrassing to have the webapp barf all over the user just because an empty event handler isn't attached to a form or because an interface isn't in the correct package. Giving the developer a tool to avoid this before deployment would be a great way for the framework cto enhance productivity by essentially prepackaging a crash and burn test. -Original Message- From: Howard Lewis Ship [mailto:hls...@gmail.com] Sent: Freitag, 14. Oktober 2011 01:16 To: Tapestry users Subject: An Appeal To Use the Latest Betas If you've been following the discussions here and elsewhere, you may be aware that Tapestry 5.3 is nearly done, with big improvements to every aspect of Tapestry, including speed and memory utilization. Our goal is to deliver an upgrade that is as seamless as possible. The PMC would dearly like to get a final release out and available before December (that is, within one year of the release 5.2). However, we can't do it without YOU: We need people actively using Tapestry to upgrade to the latest betas (5.3-beta-20 is the latest, but we're releasing new updates almost every day). We are looking for broken features or problems upgrading ... all the things that will get in the way of a release candidate and then a final release. Your feedback is essential ... without are community, we don't know for sure that Tapestry is ready to go to the next stage. Please budget some time, as soon as possible, to run you application under 5.3 and report back here about any problems you find. Without accurate (and hopefully, positive) feedback, we will not be able to progress to a final release ... and that means we'll be delayed adding the next layer of amazing features in Tapestry 5.4! Please see these notes on how to make use of the latest beta preview releases: http://tapestry.apache.org/2011/08/27/tapestry-53-beta-preview.html http://tapestryjava.blogspot.com/2011/10/tapestry-53-maven-archetype.html I've been posing on twitter each time a new preview is made available: http://twitter.com/#!/search/%23tapestry5 ... and note that by the time you do you upgreade, the exact version number may have changed (don't worry, beta-20 will still be available when beta-21 is made available). Your support is deeply appreciated ... now get back to coding less and delivering more! -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry
Re: An Appeal To Use the Latest Betas
On Fri, 14 Oct 2011 11:31:13 -0300, Wechsung, Wulf wulf.wechs...@sap.com wrote: 2) checks all classes in the managed package for the class format and tapestry-required visibility This is done by the JVM, so I don't know why Tapestry should do that too. I specifically mean it should test ( if possible) that: * only thing which should be in the managed packages (comps, pages, mixins, services) are in the managed packages I can't see how Tapestry can check if a give concrete class in the components, pages or mixins package is a real component, page or mixin. A check for interfaces and enums can (and should!) be done, though. The services package isn't controlled by Tapestry, so there's nothing to check. * tapestry imposed visibility rules (eg. component and page fields must be private) Tapestry already does that. If a person deploy an application to the live server without checking for errors first, manually or through automated tests, then I think the problem is responsibility of this person. Of course! Everything about the app is the responsibility of the dev. I'm just saying, the framework could increase productivity by providing a tool that automatically test for these types of errors which lets the project focus on testing their specific functionality. Agreed. :) -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
An Appeal To Use the Latest Betas
If you've been following the discussions here and elsewhere, you may be aware that Tapestry 5.3 is nearly done, with big improvements to every aspect of Tapestry, including speed and memory utilization. Our goal is to deliver an upgrade that is as seamless as possible. The PMC would dearly like to get a final release out and available before December (that is, within one year of the release 5.2). However, we can't do it without YOU: We need people actively using Tapestry to upgrade to the latest betas (5.3-beta-20 is the latest, but we're releasing new updates almost every day). We are looking for broken features or problems upgrading ... all the things that will get in the way of a release candidate and then a final release. Your feedback is essential ... without are community, we don't know for sure that Tapestry is ready to go to the next stage. Please budget some time, as soon as possible, to run you application under 5.3 and report back here about any problems you find. Without accurate (and hopefully, positive) feedback, we will not be able to progress to a final release ... and that means we'll be delayed adding the next layer of amazing features in Tapestry 5.4! Please see these notes on how to make use of the latest beta preview releases: http://tapestry.apache.org/2011/08/27/tapestry-53-beta-preview.html http://tapestryjava.blogspot.com/2011/10/tapestry-53-maven-archetype.html I've been posing on twitter each time a new preview is made available: http://twitter.com/#!/search/%23tapestry5 ... and note that by the time you do you upgreade, the exact version number may have changed (don't worry, beta-20 will still be available when beta-21 is made available). Your support is deeply appreciated ... now get back to coding less and delivering more! -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
Howard, My site seems to work fine under beta 19. Regards, Greg Pagendam-Turner. On 14/10/11 09:16, Howard Lewis Ship wrote: If you've been following the discussions here and elsewhere, you may be aware that Tapestry 5.3 is nearly done, with big improvements to every aspect of Tapestry, including speed and memory utilization. Our goal is to deliver an upgrade that is as seamless as possible. The PMC would dearly like to get a final release out and available before December (that is, within one year of the release 5.2). However, we can't do it without YOU: We need people actively using Tapestry to upgrade to the latest betas (5.3-beta-20 is the latest, but we're releasing new updates almost every day). We are looking for broken features or problems upgrading ... all the things that will get in the way of a release candidate and then a final release. Your feedback is essential ... without are community, we don't know for sure that Tapestry is ready to go to the next stage. Please budget some time, as soon as possible, to run you application under 5.3 and report back here about any problems you find. Without accurate (and hopefully, positive) feedback, we will not be able to progress to a final release ... and that means we'll be delayed adding the next layer of amazing features in Tapestry 5.4! Please see these notes on how to make use of the latest beta preview releases: http://tapestry.apache.org/2011/08/27/tapestry-53-beta-preview.html http://tapestryjava.blogspot.com/2011/10/tapestry-53-maven-archetype.html I've been posing on twitter each time a new preview is made available: http://twitter.com/#!/search/%23tapestry5 ... and note that by the time you do you upgreade, the exact version number may have changed (don't worry, beta-20 will still be available when beta-21 is made available). Your support is deeply appreciated ... now get back to coding less and delivering more! - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
