Re: intermittent stack trace

I guess there's a cleaner way to do the same thing. In addition, page request context is being preserved: https://gist.github.com/xfyre/a8aab5ff9428961b252f On Sat, Mar 23, 2013 at 3:56 PM, Geoff Callender < geoff.callender.jumpst...@gmail.com> wrote: > See > http://apache-tapestry-mailing-list

Re: Book proposal withdrawn :-(

No problem. Its just that server push is crucial in the new area of the internet and socket.io seams to became the standard of how to do it right now. Polling is so zeroish (2000+). So in the end this Atmosphere integration would be a good start for tapestry to support server push right out of the

Re: Book proposal withdrawn :-(

I'm sorry, my messages above ended up way harsher then I intended. I don't have anything that would earn me some money from next month on and it took a toll on my humor. :( I've taken a look at Socket.IO. If I got it right, it has two parts: server and client. The server one is written in J

Re: Book proposal withdrawn :-(

On Fri, 23 Aug 2013 16:06:06 -0300, Thiago H de Paula Figueiredo wrote: On Fri, 23 Aug 2013 14:37:59 -0300, Martin Kersten wrote: So if you have some free time please try to bring Atmosphere to Tapestry :). Is number one on my wishlist. With that It would be even possible to back a javas

Re: Book proposal withdrawn :-(

On Fri, 23 Aug 2013 14:37:59 -0300, Martin Kersten wrote: So if you have some free time please try to bring Atmosphere to Tapestry :). Is number one on my wishlist. With that It would be even possible to back a javascript single page application using jquery UI + socket.io. Would be awesome.

Re: Book proposal withdrawn :-(

I would love to see an Atmoshere support ready made and build into Tapestry. I lack some knowledge but having Socket.io support out of the box would be a huge plus for me. I had to put my own afford out of hands since currently I have a too narrow schedule but wanted to come back to it once I can d

Book proposal withdrawn :-(

Hi! Thanks everyone for the amazing discussion and suggestions we had in the book proposal thread. It's got invaluable feedback and insights, for me and for the Tapestry project itself. Thanks again! As I already feared before starting the book thread, there wouldn't be enough interest fo

Re: Transactions and AfterCommit

http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/Transactions-and-AfterCommit-td5722996.html If you look at this solution, I also ask myself why there is no direct support. I can not believe that this is not needed in any way. Why should I go for spring or fuddle with my code to

Re: Proposal for a new book: Mastering Apache Tapestry

Back to the discussion. :) On Thu, 08 Aug 2013 06:50:16 -0300, Geoff Callender wrote: I completely agree. If the aim is to help Tapestry then why not do as described below by Alessi? Alessi's suggestion looks quite good to me. I'd describe it as releasing minibooks. :) I'm just afraid

Re: Transactions and AfterCommit

By the way one might rename it from isNested to isNestedOrNoTransaction. Same behavior more precise in the naming 2013/8/23 Martin Kersten > >>> I disagree. @CommitAfter never claimed to implement nested > transactions, so, if someone expects it with @CommitAfter, they're wrong, > not @CommitAf

Re: Transactions and AfterCommit

>>> I disagree. @CommitAfter never claimed to implement nested transactions, so, if someone expects it with @CommitAfter, they're wrong, not @CommitAfter. I agree that its documentation should be more explicit. <<< We had this conversation in 2008 already, if I remember correctly. Same problem, sa

Re: Transactions and AfterCommit

On Fri, Aug 23, 2013 at 5:45 PM, Martin Kersten wrote: > @Dimitry > But using this annotation would introduce a good chance that later in your > project you introduce bugs this way. So I would consider @CommitAfter to be > a harmful feature. The problem with this transaction behavior it introduce

Re: Transactions and AfterCommit

On Fri, 23 Aug 2013 10:45:27 -0300, Martin Kersten wrote: @Dimitry But using this annotation would introduce a good chance that later in your project you introduce bugs this way. So I would consider @CommitAfter to be a harmful feature. The problem with this transaction behavior it intr

Re: Transactions and AfterCommit

@Dimitry But using this annotation would introduce a good chance that later in your project you introduce bugs this way. So I would consider @CommitAfter to be a harmful feature. The problem with this transaction behavior it introduces bugs that might happen in so rare circumstances that you always

Re: Need help: in displaying text with html character entities and new line

Thank you for the reply. If I use raw=true, I again has to replace <'> in my input string as well. I found a way to make insert text to work for my \n. I replaced all my \n in my input string with java.lang.System.getProperty("line.separator"). After the above replacement, InsertText worked for

Re: Need help: in displaying text with html character entities and new line

On Thu, 22 Aug 2013 23:04:26 -0300, Giridhar reddy wrote: Hello, Hi! I have the input string which contains "price range<10-100>\n least price = 20" I need the output as: price range<10-100> least price=20 I tried jwcid=@InsertText. But, it is still printing the output in one line

Re: Transactions and AfterCommit

TAP5-2159 2013/8/23 Taha Hafeez Siddiqi > Hi Martin > > You are right. Please file a jira. I will look into it this weekend. > > regards > Taha > > On 23-Aug-2013, at 12:41 PM, Martin Kersten > wrote: > > > I review some code and I ran into the

Re: Transactions and AfterCommit

Thanks for taking care. Please add a post here if you find something out. I wait for using the mentioned version to manage my transactions. 2013/8/23 Martin Kersten > TAP5-2159 > > > 2013/8/23 Taha Hafeez Siddiqi > >> Hi Martin >> >> You are ri

Re: Transactions and AfterCommit

I have to correct myself, you won't get nested transactions with @CommitAfter, because its implementation checks if another transaction is active -- it won't start another transaction: https://github.com/apache/tapestry-5/blob/master/tapestry-jpa/src/main/java/org/apache/tapestry5/internal/jpa/Com

Re: Transactions and AfterCommit

On Fri, Aug 23, 2013 at 11:11 AM, Martin Kersten < martin.kersten...@gmail.com> wrote: > I review some code and I ran into the transaction issue. Annotating a > service @CommitAfter seams to be inappropriate if you have another service > method using it and is itself annotated with the @CommitAfte

Re: Transactions and AfterCommit

Last line of my post should read "Tapestry doesn't support nested transactions" So to answer your question: you are right. On Aug 23, 2013, at 3:44 AM, Lenny Primak wrote: > Tapestry transaction support isn't meant to be a comprehensive solution. > It can be used as a starter mechanism but if

Re: Transactions and AfterCommit

Tapestry transaction support isn't meant to be a comprehensive solution. It can be used as a starter mechanism but if you want true transaction management, I would recommend using full JEE server. It doesn't support nested transactions. On Aug 23, 2013, at 3:11 AM, Martin Kersten wrote: > I

Re: Transactions and AfterCommit

Hi Martin You are right. Please file a jira. I will look into it this weekend. regards Taha On 23-Aug-2013, at 12:41 PM, Martin Kersten wrote: > I review some code and I ran into the transaction issue. Annotating a > service @CommitAfter seams to be inappropriate if you have another service >

Transactions and AfterCommit

I review some code and I ran into the transaction issue. Annotating a service @CommitAfter seams to be inappropriate if you have another service method using it and is itself annotated with the @CommitAfter. The problem I have seams within the documentation. For @CommitAfter the documentation stat