I've been using Tapestry actively since version 5.0 and still think it's on of the best in terms of overall design and approach.
However latest updates (since 5.4-beta22 I guess) is a total mess. I was hoping that final release should clean up things, but apparently that didn't happen. I have to stick to 5.4-beta6 for now - I use it in production for over a year and it doesn't have any major issues. On Thu, Feb 11, 2016 at 7:47 PM, Emmanuel Sowah <eso...@gmail.com> wrote: > Folks, > > This is why you should drop Tapestry ASAP, and head to a more serious and > state of the art frameworks. Tapestry is meant for POCs and prototypes that > you plan to throw away. Even Howard doesn't use Tapestry anymore. He uses > Wicket. Tapestry is just a joke. > > Cheers > > On Thu, Feb 11, 2016 at 4:29 PM, Ilya Obshadko <ilya.obsha...@gmail.com> > wrote: > > > FormFragments are inside a loop. > > > > On Thu, Feb 11, 2016 at 5:12 PM, JumpStart < > > geoff.callender.jumpst...@gmail.com> wrote: > > > > > How does your code differ from JumpStart’s Wizard Using Form Fragments > > > example? > > > > > > > > > > > > http://jumpstart.doublenegative.com.au/jumpstart7/examples/wizard/usingformfragments/$N/$N > > > > > > Geoff > > > > > > > On 11 Feb 2016, at 10:55 PM, Ilya Obshadko <ilya.obsha...@gmail.com> > > > wrote: > > > > > > > > Just found another issue: it throws validation errors for a form > > fragment > > > > that's hidden during form submission: > > > > https://monosnap.com/file/t9Hh48KeLUOBIha8PLPvGrOu29TUnn.png > > > > > > > > This is very frustrating. All complex things that were working out of > > the > > > > box now seem to be broken in unexpected places. > > > > > > > > On Thu, Feb 11, 2016 at 4:13 PM, Ilya Obshadko < > > ilya.obsha...@gmail.com> > > > > wrote: > > > > > > > >> I'll try to gather more evidence. > > > >> > > > >> From the first glance, validation messages don't show up at all > > without > > > >> setting *simpleIds=true* (as per TAP-2391). Setting *simpleIds=true* > > > >> helps to fix this for simple forms, but completely breaks more > complex > > > ones > > > >> (when validated fields are inside AjaxFormLoop, for example). > > > >> > > > >> Looks like something was also changed in the way AjaxFormLoop > > submission > > > >> is processed, and now I'm getting NPEs in places that work just fine > > on > > > >> beta6. > > > >> > > > >> Also, there are occasional Bootstrap JS errors (something like > > > 'popover.js > > > >> requires tooltip.js to work'; needless to say that both are loaded). > > > >> > > > >> > > > >> > > > >> > > > >> On Thu, Feb 11, 2016 at 11:12 AM, JumpStart < > > > >> geoff.callender.jumpst...@gmail.com> wrote: > > > >> > > > >>> Are you sure it’s 5.4.0? I’m running 5.4.0 in JumpStart > > > >>> > > > >>> http://jumpstart.doublenegative.com.au/jumpstart7/ > > > >>> > > > >>> Can you point to the problem there? > > > >>> > > > >>> Also, in a production site I’m running its last predecessor, > > > 5.4-beta-35, > > > >>> with AJAX Forms and Zones throughout without a problem. > > > >>> > > > >>> Can you be more specific? > > > >>> > > > >>> Geoff > > > >>> > > > >>>> On 11 Feb 2016, at 4:42 PM, Ilya Obshadko < > ilya.obsha...@gmail.com> > > > >>> wrote: > > > >>>> > > > >>>> Just tried to switch to 5.4 release from 5.4-beta6 (which I've > been > > > >>> using > > > >>>> for over a year). > > > >>>> > > > >>>> At least AJAX forms are seriously broken. > > > >>>> > > > >>>> The most critical issue is > > > >>> https://issues.apache.org/jira/browse/TAP5-2391 > > > >>>> (which is marked as 'Solved', but actually far from being solved). > > > >>>> > > > >>>> There's a number of other glitches, but this one is the worst. > > Setting > > > >>>> *simpleIds* to true for zones doesn't help much, as this results > in > > > >>> other > > > >>>> problems in complex forms. > > > >>>> > > > >>>> Are there any other workarounds? > > > >>>> > > > >>>> > > > >>>> On Sat, Jan 9, 2016 at 12:53 PM, Basile Chandesris <ba...@free.fr > > > > > >>> wrote: > > > >>>> > > > >>>>> Hi, > > > >>>>> > > > >>>>> I noticed that the 'Tapestry 5.4 Announce' is not available on > > Apache > > > >>>>> www-announce mailing list. > > > >>>>> > > > >>>>> > > > >>>>> The Apache News Round-up: week ending 8 January 2016: > > > >>>>> > > > >>> > > > > > > http://mail-archives.apache.org/mod_mbox/www-announce/201601.mbox/browser > > > >>>>> > > > >>>>> https://blogs.apache.org/ > > > >>>>> https://blogs.apache.org/foundation/search?q=tapestry > > > >>>>> > > > >>>>> regards, > > > >>>>> Basile > > > >>>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> -- > > > >>>> Ilya Obshadko > > > >>> > > > >>> > > > >>> > --------------------------------------------------------------------- > > > >>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > > >>> For additional commands, e-mail: users-h...@tapestry.apache.org > > > >>> > > > >>> > > > >> > > > >> > > > >> -- > > > >> Ilya Obshadko > > > >> > > > >> > > > > > > > > > > > > -- > > > > Ilya Obshadko > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > > > > > > > > > -- > > Ilya Obshadko > > > -- Ilya Obshadko
