Re: exemples are down

Yes, this is known. We work on the new hosting - a VM managed by Apache Infra. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Oct 11, 2017 at 10:06 PM, Francois Meillet < francois.meil...@gmail.com> wrote: > Hi, > >

RE: Wicket 8 GA for production

Recently I mentioned Wicket to a product manager - and his reply indicated that he thought Wicket was for UI's but was actually a different programming language! I quickly pointed out that it's the SAME language as they've used forever - Java! And that's the point! You can build your domain

exemples are down

Hi, https://examples8x.wicket.apache.org/app got 404 https://examples7x.wicket.apache.org/app connection is not secure https://examples6x.wicket.apache.org/app connection is not secure François - To unsubscribe, e-mail:

Re: Wicket 8 GA for production

Hi, I just started using Wicket recently and I quite like what I've seen so far. To me, it is superior to JSF because it let's you spend more time writing nice Java code instead of scratching your head whether the correct hmtl attribute is "render" or "reRender". I do think Wicket has a

Re: Wicket 8 GA for production

I agree with this wholeheartedly…I was just having this discussion with my boss yesterday. I do not understand (mostly) this drive to push stateless frameworks (client or server). Obviously your framework needs to support stateless as to not waste resources, but almost every application I write

Re: back button difference 7.6.0, 7.7.0, 7.8.0 and 7.9.0?

As a follow up: Is there a way to test the back-button (without firing up jetty and resorting to selenium / htmlunit)? btw: I know WicketTester has trimmed-down versions of certain components (MockApplication(), MockPageManager etc). Maybe there is an implementation that keeps track of the

RE: AjaxFormComponentUpdatingBehavior not triggering ListChoice model update in Firefox in Wicket 7.9.0

Dang! I thought the app was doing a continueToOriginalDestination(); to return from the login page to the home page at "/" but it wasn't so there's no problem with continueToOriginalDestination(). It was actually doing a setResponse(new HomePage()); from a the LogonPage that had no

RE: AjaxFormComponentUpdatingBehavior not triggering ListChoice model update in Firefox in Wicket 7.9.0

Found it It seems FireFox does have an issue with the actions that start with ..? The page I was going to (localhost/myapp) had a mount path at "/" i.e. @MountPath(value = "/", alt = "/home") Now this mount path annotation was also in the test app that didn't exhibit the problem but

Re: Wicket 8 GA for production

On Wed, Oct 11, 2017 at 6:58 AM, Илья Нарыжный wrote: > Andrea, > > We would be happy to help with: > 1) Translation of any articles/slides to russian and posting that on famous > russian IT resources. If you have any articles even right now which worst > to be translated: please

RE: AjaxFormComponentUpdatingBehavior not triggering ListChoice model update in Firefox in Wicket 7.9.0

I found an interesting difference between the quickstart that works and the app that doesn't work in FF: The action parameter of the form is generated with a .. prefix instead of ./ So in the app that doesn't work: The form's action attribute is defined as:

RE: AjaxFormComponentUpdatingBehavior not triggering ListChoice model update in Firefox in Wicket 7.9.0

I'm trying to create a quickstart but so far it doesn't reproduce the problem in the main app - all day I've been pulling in aspects of the main app in an attempt to replicate the exact scenario. I have now managed to get the quickstart to produce JS in the same order that the main app does so

Re: AjaxFormComponentUpdatingBehavior not triggering ListChoice model update in Firefox in Wicket 7.9.0

Is there any kind of defer or async on any of these JS script resources? Maybe you want to publish the quickstart? - Ursprüngliche Mail - > Von: "Chris Colman" > An: users@wicket.apache.org > Gesendet: Mittwoch, 11. Oktober 2017 10:06:23 > Betreff: RE:

RE: AjaxFormComponentUpdatingBehavior not triggering ListChoice model update in Firefox in Wicket 7.9.0

The cut down app that works fine in FireFox also has both jquery.js and bootstrap.js so this probably means that it's ok to have both of these together. ./wicket/resource/org.apache.wicket.resource.JQueryResourceReference/jquery/jquery-1.12.4.js

RE: AjaxFormComponentUpdatingBehavior not triggering ListChoice model update in Firefox in Wicket 7.9.0

Thanks Korginian - I'll check out that theory. All the JS included are done automatically by a combo of Wicket itself and the Wicket-Bootstrap project which I'm using in this app. Is there an easy way to tell which component is contributing which .js to the "header" (which is actually in the

Re: AjaxFormComponentUpdatingBehavior not triggering ListChoice model update in Firefox in Wicket 7.9.0

Hi Chris, can it be that you have 2 instances of jQuery in your page? - bootstrap.js often comes with embedded jQuery and then you would overwrite the wicket one with the bootstrap one, that will lead to problems where you dont get notfied at all. I know this from foundation / sites, where you