Re: Wicket CDI Status

Edmond, Please when you assembly the package for the new CDI version, use scope provided for javax.* and org.jboss.* dependencies. I'm fixing the plumbing of my project and several undesired packages are being assembled because of current wicket-cdi. Thank you for your efforts! - Diogo On Thu, D

Re: response headers in Wicket 6

Thanks Francois, Second question: In 1.4.7 the page object supported a removePersistedFormData() method and the TextField has a method setPersistent() on it. Both appear gone, and I don't see anything in the 6 or 1.5 conversion guides about them. What is the replacement? -- View this messag

Re: response headers in Wicket 6

Just remove them. Wicket do not persist the form components' values anymore. On Tue, Dec 10, 2013 at 4:10 PM, Entropy wrote: > Thanks Francois, > > Second question: > > In 1.4.7 the page object supported a removePersistedFormData() method and > the TextField has a method setPersistent() on it.

Re: Wicket CDI Status

Hi Diogo, It already is: https://github.com/apache/wicket/blob/wicket-6.x/wicket-experimental/wicket-cdi-1.1/pom.xml#L45 There are no dependencies on weld packages, as wicket-cdi-1.1 is fully portable. It only has a testing dependency on cdi-unit, which depends on weld. Emond On Tuesday 10 De

user activity disabled during page load

Dear all, I have been having trouble with a page that is heavy in loading, especially at client locations with low bandwidth. The main problem is that fields that are updated by the user before load has completed are not saved in their edited form. I have made an attempt to solve this problem wit

Converting 1.4.7 to 6.12

Hi, it's me again. I'm still converting to 6.12 from 1.4.7. Thanks for your help on previous questions. Here's the next item I didn't see in the conversion docs. In one of our pages, someone did this: setResponsePage(getApplication().getSessionSettings().getPageFactory().newPage(loginService.g

Re: Converting 1.4.7 to 6.12

Hello, I think you can use getSession().getPageFactory().newPage(); Depending on your context you could use Session.get() or getSession() Hope that helps -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Converting-1-4-7-to-6-12-tp4662892p4662893.html Sent from t

RE: Components can no longer be added

Sven, " once rendering of components via Ajax has started, you cannot update components." But at the moment when this happens, we are in the onConfigure() part of the lifecycle. Which is before onBeforeRender(), and hence components should've have started rendering... but that is minor as...

Re: user activity disabled during page load

In your getWindowOpenJavaScript() you need to set one property to disable the confirmation dialog: Wicket.Window.unloadConfirmation = false; See here: http://stackoverflow.com/questions/8013364/how-to-defeat-browser-dialog-popup-when-calling-wicket-setresponsepage-from-mo -- View this message