Mixin name

This is a minor issue but just wanted to let you know in case it wasn't noticed: The release notes / javadocs talks about "FieldGroup" mixin but in the current implementation, it's "FormGroup" as defined in Bootstrap 3. /Serge -- View this message in context: http://tapestry-developers.2216

Build failed in Jenkins: tapestry-trunk-freestyle #1140

See Changes: [hlship] Temporarily disable test that fails at command line only [hlship] Add a little sleep for a test to make it work -- [...truncated 32599 lines...]

Re: Transactions and AfterCommit

Yes I am aware that JEE has evolved hugely and have used Glassfish, the days of it's over complexity are gone. I still don't see much of a business case for it unless I have need of EJBs to provide distributed transactions, or message queues and so forth. Rewriting the wheel for transactions wo

Re: Transactions and AfterCommit

John, have you really, actually looked at the state of JEE these days? It's trivial to set up, trivial to develop in, and IMHO, easier to learn than many other things in Java. Yes, the "old pre-JEE5 days were bad" but JEE 5,6,7 are a whole different animal. You can get it up and running in les

Re: Tapestry Tests Wack-A-Mole

On Mon, Aug 26, 2013 at 10:26 AM, Dimitris Zenios wrote: I already posted on a previous thread regarding the CI failure on issute > TAP5-1007 but most probably nobody saw it. Re posting again here > > This is a legitimate bug. > > If your filesystem is case sensitive like most linux os are > the

Re: Transactions and AfterCommit

1) and 2) agreed - CommitAfter is ok for the trivial applications (still don't like it on the interface) 3) I like reuse and familiarity, but I'm not sure that adopting EJB lingo will increase or decrease potential for confusion? 4) yes, fully features set of something JTA yes please! In an id

Build failed in Jenkins: tapestry-trunk-freestyle #1139

See Changes: [hlship] Correct typo [hlship] Always render the data-page-initialized attribute [hlship] Simplify Checklist component and update for Bootstrap 3 [hlship] Allow DynamicTest to launch independently [hlship] Remo

Re: Transactions and AfterCommit

I'm reluctant to move my small/medium sized pure Tapestry project into a JEE environment even though I am updating accross multiple databases and have non-trivial needs for transactions. I don't see sufficient justifcation to use JEE unless there is substantial need of EJBs. So far I have got a