You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Howard Lewis Ship <hl...@gmail.com> on 2011/10/14 01:16:19 UTC
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-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
Posted by Massimo Lusetti <ml...@gmail.com>.
On Mon, Oct 17, 2011 at 10:45 PM, Geoff Callender
<ge...@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-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
Posted by Geoff Callender <ge...@gmail.com>.
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
>
> <groupId>nu.localhost.tapestry</groupId>
> <artifactId>tapestry-spring-security</artifactId>
> <version>3.0.0</version>
>
>
> And
>
> http://www.chenillekit.org/
>
> <groupId>org.chenillekit</groupId>
> <artifactId>chenillekit-tapestry</artifactId>
> <version>1.3.2</version>
>
>
> Altough the later could already have a snapshot available ?
>
> Oh.. actually there are 3
>
>
> <groupId>us.antera</groupId>
> <artifactId>t5-restful-webservices</artifactId>
> <version>0.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-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
Posted by antalk <an...@intercommit.nl>.
http://www.localhost.nu/java/tapestry-spring-security/index.html Im using
<groupId>nu.localhost.tapestry</groupId>
<artifactId>tapestry-spring-security</artifactId>
<version>3.0.0</version>
And
http://www.chenillekit.org/
<groupId>org.chenillekit</groupId>
<artifactId>chenillekit-tapestry</artifactId>
<version>1.3.2</version>
Altough the later could already have a snapshot available ?
Oh.. actually there are 3
<groupId>us.antera</groupId>
<artifactId>t5-restful-webservices</artifactId>
<version>0.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-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
Posted by Bob Harner <bo...@gmail.com>.
Which 2 libraries?
On Oct 17, 2011 3:33 AM, "antalk" <an...@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-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: An Appeal To Use the Latest Betas
Posted by antalk <an...@intercommit.nl>.
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-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
Posted by Greg Pagendam-Turner <gr...@liftyourgame.com>.
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-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
Posted by Mark <ma...@xeric.net>.
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 <hl...@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-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
Posted by Serge Eby <sd...@hotmail.com>.
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-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
Posted by Howard Lewis Ship <hl...@gmail.com>.
Generating 5.3-beta-23 right now.
On Tue, Oct 18, 2011 at 8:16 AM, Howard Lewis Ship <hl...@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-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@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-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
Posted by Howard Lewis Ship <hl...@gmail.com>.
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-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@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-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
Posted by Serge Eby <sd...@hotmail.com>.
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-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
Posted by jesse <je...@hotmail.com>.
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-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
Posted by Steve Eynon <st...@alienfactory.co.uk>.
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...@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-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
Posted by Christian Riedel <cr...@googlemail.com>.
...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-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
Posted by Tony Nelson <tn...@starpoint.com>.
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.eynon@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 <wu...@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:hlship@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-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
RE: An Appeal To Use the Latest Betas
Posted by "Wechsung, Wulf" <wu...@sap.com>.
Awesome, thanks! Learning something new every day :)
-----Original Message-----
From: Steve Eynon [mailto:steve.eynon@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 <wu...@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:hlship@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-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
Posted by Steve Eynon <st...@alienfactory.co.uk>.
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 <wu...@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:hlship@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-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
RE: An Appeal To Use the Latest Betas
Posted by "Wechsung, Wulf" <wu...@sap.com>.
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:hlship@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-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
Posted by Howard Lewis Ship <hl...@gmail.com>.
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
<ma...@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-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: An Appeal To Use the Latest Betas
Posted by Manuel Sugawara <ma...@gmail.com>.
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.