Re: Tapestry 5.0.14-SNAPSHOT
Thanks for the feedback Howard! +1 for releasing .14 as beta... would releasing it even affect the final release date either way? if not, then why not? Angelo, no worries! I do understand your point of view. Tapestry 5 is looking very solid now, in fact I would go so far as to say Tapestry 5 as a beta is more stable than any Tapestry 4 release I can remember we have replaced all our production T4 apps with T5. cheers, Peter - Original Message - From: "Howard Lewis Ship" <[EMAIL PROTECTED]> To: "Tapestry users" Sent: Tuesday, 5 August, 2008 9:16:20 PM GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: Tapestry 5.0.14-SNAPSHOT I was hoping that .14 would be the release candidate; I'm now leaning towards releasing .14 as is and having .15 (with a few modest Ajax and validation API changes) be the release candidate. This hasn't been discussed on the Tapestry dev mailing list, it's just my inclination. On Tue, Aug 5, 2008 at 3:08 AM, Peter Stavrinides <[EMAIL PROTECTED]> wrote: > Angelo > > Please don't use my post as a platform for your debate about the beta status > of Tapestry, personally I don't mind that its a beta, whenever Howard decides > to release is just fine by me, all I am curious about right now is the > current snapshot, as I have a pending bug fix... just trying to get my work > done. > > cheers, > Peter > > - Original Message - > From: "Angelo Chen" <[EMAIL PROTECTED]> > To: users@tapestry.apache.org > Sent: Monday, 4 August, 2008 12:59:45 PM GMT +02:00 Athens, Beirut, > Bucharest, Istanbul > Subject: Re: Tapestry 5.0.14-SNAPSHOT > > > Hi Peter, > > Then again back to my previous answer as well, T5 is good, better than other > released frameworks, but it has the weakest point, it is a beta. within > community we know what the t5 status is, but when we want to communicate > with the outside world, this is really a problem, how to convince people to > use T5? there are developers who can decide for the user, that's a lucky > group. there are developers working under a company, how to help them to > convince the employer to go with the best framework in the world? the boss > will simply say, no, we don't work with beta. and there are a group of > independent developers that need to get projects from companies, this group > is difficult, the competitor might simply say, that's beta, and they got the > project. > > Now in your case, I believe you have been convinced T5 is the framework > suitable for the coming production app, what difficulties you encountered so > far to put t5 into use? if you can share with us your real experience, might > finally convince our t5 community leaders to release the t5. > > I started Tapestry one year ago, I tried first t4, but did not like it, > tried T5 and I'm hooked to it, what a nice framework! reading the roadmap, > it said that will be released soon, then again it was said to be released > early 2008 and I told myself that's good timing, my app might be ready by > that time, time passed, and T5 is not released, my solution to this is, i > just tell my user, this is a java based app, I did not mention tapestry 5 > framework:( otherwise they might google tapestry 5 and find out beta:) > > > Peter Stavrinides wrote: >> >> >> 1. Its a production app & company policy (quite correctly) is not to run >> on a snapshot >> 2. Its not up to me. >> >> Peter >> >> - Original Message - >> From: "Angelo Chen" <[EMAIL PROTECTED]> >> To: users@tapestry.apache.org >> Sent: Monday, 4 August, 2008 11:03:00 AM GMT +02:00 Athens, Beirut, >> Bucharest, Istanbul >> Subject: Re: Tapestry 5.0.14-SNAPSHOT >> >> >> why not just pull down the nightly built version? it's just ok for me. >> >> >> Peter Stavrinides wrote: >>> >>> Back to the original question, anyone got any clue when 5.0.14-SNAPSHOT >>> might be ready? >>> >>> >> >> > > -- > View this message in context: > http://www.nabble.com/Tapestry-5.0.14-SNAPSHOT-tp18770439p18808457.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tapestry 5.0.14-SNAPSHOT
I was hoping that .14 would be the release candidate; I'm now leaning towards releasing .14 as is and having .15 (with a few modest Ajax and validation API changes) be the release candidate. This hasn't been discussed on the Tapestry dev mailing list, it's just my inclination. On Tue, Aug 5, 2008 at 3:08 AM, Peter Stavrinides <[EMAIL PROTECTED]> wrote: > Angelo > > Please don't use my post as a platform for your debate about the beta status > of Tapestry, personally I don't mind that its a beta, whenever Howard decides > to release is just fine by me, all I am curious about right now is the > current snapshot, as I have a pending bug fix... just trying to get my work > done. > > cheers, > Peter > > - Original Message - > From: "Angelo Chen" <[EMAIL PROTECTED]> > To: users@tapestry.apache.org > Sent: Monday, 4 August, 2008 12:59:45 PM GMT +02:00 Athens, Beirut, > Bucharest, Istanbul > Subject: Re: Tapestry 5.0.14-SNAPSHOT > > > Hi Peter, > > Then again back to my previous answer as well, T5 is good, better than other > released frameworks, but it has the weakest point, it is a beta. within > community we know what the t5 status is, but when we want to communicate > with the outside world, this is really a problem, how to convince people to > use T5? there are developers who can decide for the user, that's a lucky > group. there are developers working under a company, how to help them to > convince the employer to go with the best framework in the world? the boss > will simply say, no, we don't work with beta. and there are a group of > independent developers that need to get projects from companies, this group > is difficult, the competitor might simply say, that's beta, and they got the > project. > > Now in your case, I believe you have been convinced T5 is the framework > suitable for the coming production app, what difficulties you encountered so > far to put t5 into use? if you can share with us your real experience, might > finally convince our t5 community leaders to release the t5. > > I started Tapestry one year ago, I tried first t4, but did not like it, > tried T5 and I'm hooked to it, what a nice framework! reading the roadmap, > it said that will be released soon, then again it was said to be released > early 2008 and I told myself that's good timing, my app might be ready by > that time, time passed, and T5 is not released, my solution to this is, i > just tell my user, this is a java based app, I did not mention tapestry 5 > framework:( otherwise they might google tapestry 5 and find out beta:) > > > Peter Stavrinides wrote: >> >> >> 1. Its a production app & company policy (quite correctly) is not to run >> on a snapshot >> 2. Its not up to me. >> >> Peter >> >> - Original Message - >> From: "Angelo Chen" <[EMAIL PROTECTED]> >> To: users@tapestry.apache.org >> Sent: Monday, 4 August, 2008 11:03:00 AM GMT +02:00 Athens, Beirut, >> Bucharest, Istanbul >> Subject: Re: Tapestry 5.0.14-SNAPSHOT >> >> >> why not just pull down the nightly built version? it's just ok for me. >> >> >> Peter Stavrinides wrote: >>> >>> Back to the original question, anyone got any clue when 5.0.14-SNAPSHOT >>> might be ready? >>> >>> >> >> > > -- > View this message in context: > http://www.nabble.com/Tapestry-5.0.14-SNAPSHOT-tp18770439p18808457.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tapestry 5.0.14-SNAPSHOT
Angelo Please don't use my post as a platform for your debate about the beta status of Tapestry, personally I don't mind that its a beta, whenever Howard decides to release is just fine by me, all I am curious about right now is the current snapshot, as I have a pending bug fix... just trying to get my work done. cheers, Peter - Original Message - From: "Angelo Chen" <[EMAIL PROTECTED]> To: users@tapestry.apache.org Sent: Monday, 4 August, 2008 12:59:45 PM GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: Tapestry 5.0.14-SNAPSHOT Hi Peter, Then again back to my previous answer as well, T5 is good, better than other released frameworks, but it has the weakest point, it is a beta. within community we know what the t5 status is, but when we want to communicate with the outside world, this is really a problem, how to convince people to use T5? there are developers who can decide for the user, that's a lucky group. there are developers working under a company, how to help them to convince the employer to go with the best framework in the world? the boss will simply say, no, we don't work with beta. and there are a group of independent developers that need to get projects from companies, this group is difficult, the competitor might simply say, that's beta, and they got the project. Now in your case, I believe you have been convinced T5 is the framework suitable for the coming production app, what difficulties you encountered so far to put t5 into use? if you can share with us your real experience, might finally convince our t5 community leaders to release the t5. I started Tapestry one year ago, I tried first t4, but did not like it, tried T5 and I'm hooked to it, what a nice framework! reading the roadmap, it said that will be released soon, then again it was said to be released early 2008 and I told myself that's good timing, my app might be ready by that time, time passed, and T5 is not released, my solution to this is, i just tell my user, this is a java based app, I did not mention tapestry 5 framework:( otherwise they might google tapestry 5 and find out beta:) Peter Stavrinides wrote: > > > 1. Its a production app & company policy (quite correctly) is not to run > on a snapshot > 2. Its not up to me. > > Peter > > - Original Message - > From: "Angelo Chen" <[EMAIL PROTECTED]> > To: users@tapestry.apache.org > Sent: Monday, 4 August, 2008 11:03:00 AM GMT +02:00 Athens, Beirut, > Bucharest, Istanbul > Subject: Re: Tapestry 5.0.14-SNAPSHOT > > > why not just pull down the nightly built version? it's just ok for me. > > > Peter Stavrinides wrote: >> >> Back to the original question, anyone got any clue when 5.0.14-SNAPSHOT >> might be ready? >> >> > > -- View this message in context: http://www.nabble.com/Tapestry-5.0.14-SNAPSHOT-tp18770439p18808457.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tapestry 5.0.14-SNAPSHOT
Hi Peter, Then again back to my previous answer as well, T5 is good, better than other released frameworks, but it has the weakest point, it is a beta. within community we know what the t5 status is, but when we want to communicate with the outside world, this is really a problem, how to convince people to use T5? there are developers who can decide for the user, that's a lucky group. there are developers working under a company, how to help them to convince the employer to go with the best framework in the world? the boss will simply say, no, we don't work with beta. and there are a group of independent developers that need to get projects from companies, this group is difficult, the competitor might simply say, that's beta, and they got the project. Now in your case, I believe you have been convinced T5 is the framework suitable for the coming production app, what difficulties you encountered so far to put t5 into use? if you can share with us your real experience, might finally convince our t5 community leaders to release the t5. I started Tapestry one year ago, I tried first t4, but did not like it, tried T5 and I'm hooked to it, what a nice framework! reading the roadmap, it said that will be released soon, then again it was said to be released early 2008 and I told myself that's good timing, my app might be ready by that time, time passed, and T5 is not released, my solution to this is, i just tell my user, this is a java based app, I did not mention tapestry 5 framework:( otherwise they might google tapestry 5 and find out beta:) Peter Stavrinides wrote: > > > 1. Its a production app & company policy (quite correctly) is not to run > on a snapshot > 2. Its not up to me. > > Peter > > - Original Message - > From: "Angelo Chen" <[EMAIL PROTECTED]> > To: users@tapestry.apache.org > Sent: Monday, 4 August, 2008 11:03:00 AM GMT +02:00 Athens, Beirut, > Bucharest, Istanbul > Subject: Re: Tapestry 5.0.14-SNAPSHOT > > > why not just pull down the nightly built version? it's just ok for me. > > > Peter Stavrinides wrote: >> >> Back to the original question, anyone got any clue when 5.0.14-SNAPSHOT >> might be ready? >> >> > > -- View this message in context: http://www.nabble.com/Tapestry-5.0.14-SNAPSHOT-tp18770439p18808457.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tapestry 5.0.14-SNAPSHOT
1. Its a production app & company policy (quite correctly) is not to run on a snapshot 2. Its not up to me. Peter - Original Message - From: "Angelo Chen" <[EMAIL PROTECTED]> To: users@tapestry.apache.org Sent: Monday, 4 August, 2008 11:03:00 AM GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: Tapestry 5.0.14-SNAPSHOT why not just pull down the nightly built version? it's just ok for me. Peter Stavrinides wrote: > > Back to the original question, anyone got any clue when 5.0.14-SNAPSHOT > might be ready? > > > > -- View this message in context: http://www.nabble.com/Tapestry-5.0.14-SNAPSHOT-tp18770439p18807159.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tapestry 5.0.14-SNAPSHOT
why not just pull down the nightly built version? it's just ok for me. Peter Stavrinides wrote: > > Back to the original question, anyone got any clue when 5.0.14-SNAPSHOT > might be ready? > > > > -- View this message in context: http://www.nabble.com/Tapestry-5.0.14-SNAPSHOT-tp18770439p18807159.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tapestry 5.0.14-SNAPSHOT
Back to the original question, anyone got any clue when 5.0.14-SNAPSHOT might be ready? - Original Message - From: "Angelo Chen" <[EMAIL PROTECTED]> To: users@tapestry.apache.org Sent: Sunday, 3 August, 2008 7:10:45 AM GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: Tapestry 5.0.14-SNAPSHOT Hi Daniel, I meant the way that a new transaction is acquired after the commit, in the 5.0.14, it always call: transaction = session.beginTransaction() to get a new transaction. I don't know if this really fix to all my problems, but i do have some bugs that i can't understand, example, I have dispatcher, page and service, dispatcher create a persisted log object, page created a persisted parent record while service created a child record, this was working until i found out that i need to commit in the dispatcher in order to persist the object, now everything wrong, Referential Integrity exceptions pop out, removing the cp30 works, putting it back failed, until I put a commit also in the page class before calling the service method to make it work, and I don't know why I have to put a commit in the page while page and service transactions are actually the same one, this trial and error approach took several days, a workaround is found, but not so sure why. upgraded to 5.0.14, and I removed the commit in the page, everything works, at least I can explain this time that I don't need a manual commit in the page before calling service method as eventually it will be commited due to the @CommitAfter in the page class. I guess, if you use hibernate in a normal way, say, purely in the page, or you do not put referential integrity in the table level, 5.0.13 might work, otherwise it's really very frustrating to trace those problems without really knowing what the problem is. I believe this problem was there in the early versions, remember I have a post http://www.nabble.com/T5%3A-how-to-use-Hibernate-properly--to15580722.html#a15580722 How to use Hibernate properly before? rule no. 1 in that post is:1. Don't commit, let Tapestry-Hibernate take care of that. I think that's actually due to this bug, it really kind of disappointing when you have no control over the transaction, that actually means you have no control over the integrity of the data. if you use tapestry-hibernate heavily and this bug is there, really a problem, taking time to debug, actually you are just trying to find a workaround:( glad 5.0.14 finally solved this problem and it has to be released asap. Angelo Daniel Jue wrote: > > Do you mean the "bug" of not committing automatically? If so, there > have been posts about that one, because it was actually a fix. > > > On Fri, Aug 1, 2008 at 9:37 PM, Angelo Chen <[EMAIL PROTECTED]> > wrote: >> >> I strongly recommend to release this 5.0.14-SNAPSHOT as soon as possible, >> 5.0.13 has a serious bug in its commit method with hibernate, it >> generates >> unpredictable results making debugging very difficult, switching to >> 5.0.14 >> solves the problem, I'd say quite impossible to proceed in 5.0.13 if you >> have some hibernate code. >> >> >> >> Peter Stavrinides wrote: >>> >>> Hi >>> >>> I am just curious to know if the 14 snapshot is due for release anytime >>> soon? >>> >>> Thanks, >>> Peter >>> >>> >>> - >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> >> >> -- >> View this message in context: >> http://www.nabble.com/Tapestry-5.0.14-SNAPSHOT-tp18770439p18785186.html >> Sent from the Tapestry - User mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Tapestry-5.0.14-SNAPSHOT-tp18770439p18795792.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tapestry 5.0.14-SNAPSHOT
Hi Daniel, I meant the way that a new transaction is acquired after the commit, in the 5.0.14, it always call: transaction = session.beginTransaction() to get a new transaction. I don't know if this really fix to all my problems, but i do have some bugs that i can't understand, example, I have dispatcher, page and service, dispatcher create a persisted log object, page created a persisted parent record while service created a child record, this was working until i found out that i need to commit in the dispatcher in order to persist the object, now everything wrong, Referential Integrity exceptions pop out, removing the cp30 works, putting it back failed, until I put a commit also in the page class before calling the service method to make it work, and I don't know why I have to put a commit in the page while page and service transactions are actually the same one, this trial and error approach took several days, a workaround is found, but not so sure why. upgraded to 5.0.14, and I removed the commit in the page, everything works, at least I can explain this time that I don't need a manual commit in the page before calling service method as eventually it will be commited due to the @CommitAfter in the page class. I guess, if you use hibernate in a normal way, say, purely in the page, or you do not put referential integrity in the table level, 5.0.13 might work, otherwise it's really very frustrating to trace those problems without really knowing what the problem is. I believe this problem was there in the early versions, remember I have a post http://www.nabble.com/T5%3A-how-to-use-Hibernate-properly--to15580722.html#a15580722 How to use Hibernate properly before? rule no. 1 in that post is:1. Don't commit, let Tapestry-Hibernate take care of that. I think that's actually due to this bug, it really kind of disappointing when you have no control over the transaction, that actually means you have no control over the integrity of the data. if you use tapestry-hibernate heavily and this bug is there, really a problem, taking time to debug, actually you are just trying to find a workaround:( glad 5.0.14 finally solved this problem and it has to be released asap. Angelo Daniel Jue wrote: > > Do you mean the "bug" of not committing automatically? If so, there > have been posts about that one, because it was actually a fix. > > > On Fri, Aug 1, 2008 at 9:37 PM, Angelo Chen <[EMAIL PROTECTED]> > wrote: >> >> I strongly recommend to release this 5.0.14-SNAPSHOT as soon as possible, >> 5.0.13 has a serious bug in its commit method with hibernate, it >> generates >> unpredictable results making debugging very difficult, switching to >> 5.0.14 >> solves the problem, I'd say quite impossible to proceed in 5.0.13 if you >> have some hibernate code. >> >> >> >> Peter Stavrinides wrote: >>> >>> Hi >>> >>> I am just curious to know if the 14 snapshot is due for release anytime >>> soon? >>> >>> Thanks, >>> Peter >>> >>> >>> - >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> >> >> -- >> View this message in context: >> http://www.nabble.com/Tapestry-5.0.14-SNAPSHOT-tp18770439p18785186.html >> Sent from the Tapestry - User mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Tapestry-5.0.14-SNAPSHOT-tp18770439p18795792.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tapestry 5.0.14-SNAPSHOT
Do you mean the "bug" of not committing automatically? If so, there have been posts about that one, because it was actually a fix. On Fri, Aug 1, 2008 at 9:37 PM, Angelo Chen <[EMAIL PROTECTED]> wrote: > > I strongly recommend to release this 5.0.14-SNAPSHOT as soon as possible, > 5.0.13 has a serious bug in its commit method with hibernate, it generates > unpredictable results making debugging very difficult, switching to 5.0.14 > solves the problem, I'd say quite impossible to proceed in 5.0.13 if you > have some hibernate code. > > > > Peter Stavrinides wrote: >> >> Hi >> >> I am just curious to know if the 14 snapshot is due for release anytime >> soon? >> >> Thanks, >> Peter >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > -- > View this message in context: > http://www.nabble.com/Tapestry-5.0.14-SNAPSHOT-tp18770439p18785186.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tapestry 5.0.14-SNAPSHOT
Hi Angelo, What is this bug? Does it only affect debugging, or might it also affect production? Is there a JIRA for it? Thanks, Andy (on 5.0.13 in production, and worried) On Fri, 2008-08-01 at 18:37 -0700, Angelo Chen wrote: > I strongly recommend to release this 5.0.14-SNAPSHOT as soon as possible, > 5.0.13 has a serious bug in its commit method with hibernate, it generates > unpredictable results making debugging very difficult, switching to 5.0.14 > solves the problem, I'd say quite impossible to proceed in 5.0.13 if you > have some hibernate code. > > > > Peter Stavrinides wrote: > > > > Hi > > > > I am just curious to know if the 14 snapshot is due for release anytime > > soon? > > > > Thanks, > > Peter > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tapestry 5.0.14-SNAPSHOT
I strongly recommend to release this 5.0.14-SNAPSHOT as soon as possible, 5.0.13 has a serious bug in its commit method with hibernate, it generates unpredictable results making debugging very difficult, switching to 5.0.14 solves the problem, I'd say quite impossible to proceed in 5.0.13 if you have some hibernate code. Peter Stavrinides wrote: > > Hi > > I am just curious to know if the 14 snapshot is due for release anytime > soon? > > Thanks, > Peter > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Tapestry-5.0.14-SNAPSHOT-tp18770439p18785186.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]