Cannot add InputHintFormBehavior to a form element

Hi, i'm trying to migrate my application from Wicket 1.4 to 6.13 and getting a compilation error when trying to add a InputHintFormBehavior to a form element. private final Form form = new Form(); form.add(new InputHintFormBehavior(component.getMarkupId())); how this is achieved in wicket 6.

Re: Cannot add InputHintFormBehavior to a form element

Hi, Showing us the error would help. InputHintFormBehavior is not from Wicket distro. It is your own class, or from a third party library. Martin Grigorov Wicket Training and Consulting On Fri, Jan 24, 2014 at 10:12 AM, chathuraka.waas chathuraka.w...@gmail.com wrote: Hi, i'm trying to

Cannot add InputHintFormBehavior to a form element

Hi, got the issue fixed. it was due to a error in my own class. thanks for the reply. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Cannot-add-InputHintFormBehavior-to-a-form-element-tp4663928p4663931.html Sent from the Users forum mailing list archive at

timing for Wicket 7?

Hi, What's the estimated release date for Wicket 7? Why? In a couple of weeks I will start a new Wicket project and the estimated time to complete it is one month (at least for the initial release). I've thought maybe I could start it using current Wicket 7 and 1) provide feedback, 2) contribute

how to implement AjaxPagingNavigator.newNavigation in wicket 6

hi, i'm trying to migrate my app from wicket 1.4 to 6.13. and it seems AjaxPagingNavigator.newNavigation method has been deprecated. what should be used in wicket to get the same functionality. Thanks in advance. -- View this message in context:

Re: timing for Wicket 7?

Hi Ernesto, There won't be 7.0.0 in the next month. We will make a milestone release so users can try it and give feedback. The only thing to do before the milestone is to make the voted experimental modules stable. With this milestone release we want to get feedback for the small API changes we

Re: how to implement AjaxPagingNavigator.newNavigation in wicket 6

Hi, https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/ajax/markup/html/navigation/paging/AjaxPagingNavigator.java?source=cc#L124 It is not deprecated... Martin Grigorov Wicket Training and Consulting On Fri, Jan 24, 2014 at 11:01 AM, chathuraka.waas

Re: timing for Wicket 7?

Martin, Tanks for your answer. On Fri, Jan 24, 2014 at 10:04 AM, Martin Grigorov mgrigo...@apache.orgwrote: Hi Ernesto, There won't be 7.0.0 in the next month. Ok. We will make a milestone release so users can try it and give feedback. The only thing to do before the milestone is to

Re: how to implement AjaxPagingNavigator.newNavigation in wicket 6

thanks for the reply. my mistake its just that the method signature has been changed. On Fri, Jan 24, 2014 at 3:24 PM, Martin Grigorov-4 [via Apache Wicket] ml-node+s1842946n4663936...@n4.nabble.com wrote: Hi,

Re: timing for Wicket 7?

I'm hoping to finalise wicket 7 somewhere before the summer. But I can't guarantee that. My reasoning: - I expect Wicket 8 to be Java 8 based (lambda expressions and the new date/time APIs would make good additions to Wicket) - Wicket 8/Java 8 development should start when Java 8 is out and has

Re: timing for Wicket 7?

On Fri, Jan 24, 2014 at 2:30 PM, Martijn Dashorst martijn.dasho...@gmail.com wrote: I'm hoping to finalise wicket 7 somewhere before the summer. But I can't guarantee that. My reasoning: - I expect Wicket 8 to be Java 8 based (lambda expressions and the new date/time APIs would make good

Re: timing for Wicket 7?

Hi, On Fri, Jan 24, 2014 at 1:39 PM, Martin Grigorov mgrigo...@apache.orgwrote: On Fri, Jan 24, 2014 at 2:30 PM, Martijn Dashorst martijn.dasho...@gmail.com wrote: I'm hoping to finalise wicket 7 somewhere before the summer. But I can't guarantee that. My reasoning: - I expect

Re: Wicket 6 - JavaScriptHeaderItem renders too early

I am still having this problem. The wicket:container solution leads me to the following exception. Note that this exception is different than the one in the prior post. I think I had a publish/refresh quirk. This is the exception that is occurring now. java.lang.IllegalStateException: No

Re: Bunch of Page Expired exceptions in Wicket 6.10.0

Yes, but in my example, I was referring to how 2 different apps with different cookies are both running on localhost with different ports. I get this issue all the time on chromium when I test multiple apps all on location with different ports. I keep having to login whenever I refresh a different

continueToOriginalDestination hacks

I'm building an app that uses oauth to login but I found that continueToOriginalDestination doesn't work when I login via twitter but it works when I use google to login. The user instead ends up in the fallback value I used: continueToOriginalDestination(); setResponsePage(MemberHome.class);