Re: Strange behaviour in WicketTester when Ajax-clicking on a deselected checkbox
On 01.04.2011 00:25, Pedro Santos wrote: Hi David, looks like a bug, please create a ticket + upload the quickstart. As a side note, wicket tester do not encode the form state between requests. If you submit a form a second time, the request parameters for fields you didn't set will be empty, and will look like the user had cleared the form. https://issues.apache.org/jira/browse/WICKET-1826 Thanks Pedro, upon further investigation, I found out, that I was wrong... I was under the delusion, that with an AjaxCheckBox executing the onClick would be sufficient and thus didn't call FormTester.setValue(), which resulted in the Model being false after my test in any case (which looked OK for deselecting checkboxes). Thanks for your reply anyway, I really appreciate the help one can get on this list. David Hendrix - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Strange behaviour in WicketTester when Ajax-clicking on a deselected checkbox
Hi there, I'm experiencing some weird behaviour in WicketTester. Running the code in jetty gives the expected results. I've got an AjaxCheckbox with a PropertyModel. When ajax-clicking in in WicketTester, when the model is true, everything works as expected but ajax-clicking it when the model is false doesn't result in a call of the model's setter even in onUpdate is executed (Breakpoints and jUnit-Asserts) Is this some known issue or am I doing something wrong? I created a quickstart replicating this for Wicket 1.4.15, didn't try another version yet... Thanks for your help David - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Replicating tinyMCE
05.09.2010 13:49, Bas Gooren: Hi Bas, thanks a lot! This looks like the missing part. As soon as I got this working, I'll come back to you with the results (it's a weekend project so I didn't try this right now). David David, You can see an example (plus javascript code required to remove the editor in the page source) of removing TinyMCE on the following page: http://tinymce.moxiecode.com/examples/example_01.php Try prepending the necessary javascript code to the AJAX request to fix your problem. Bas - Original Message - From: David Hendrix wicket-us...@unbewaff.net To: users@wicket.apache.org Sent: Sunday, September 05, 2010 1:43 PM Subject: Re: Replicating tinyMCE Hi, I tried to add tinyMCE to my application, which seems easy enough using the wicketstuff project. The point where I got stuck (for some hours now) is where I start adding the component carrying the TinyMceBehavior to any Ajax-Targets. What I'm trying to do is to populate the textarea based on selections from several DropDownChoices. But whenever an onChange-Event is called that adds the textarea to it's target, another editor appears right above the existing one containing the new content while the other editor gets moved down, still displaying the old values. Unfortunately I can't figure out what I'm doing wrong here... Any ideas would be greatly appreciated thanks David Nobody? It's not that strange (at least that's what I think). So it has to be done before. Anything that I didn't provide? David - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Replicating tinyMCE
Hi, I tried to add tinyMCE to my application, which seems easy enough using the wicketstuff project. The point where I got stuck (for some hours now) is where I start adding the component carrying the TinyMceBehavior to any Ajax-Targets. What I'm trying to do is to populate the textarea based on selections from several DropDownChoices. But whenever an onChange-Event is called that adds the textarea to it's target, another editor appears right above the existing one containing the new content while the other editor gets moved down, still displaying the old values. Unfortunately I can't figure out what I'm doing wrong here... Any ideas would be greatly appreciated thanks David Nobody? It's not that strange (at least that's what I think). So it has to be done before. Anything that I didn't provide? David - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Replicating tinyMCE
Hi, I tried to add tinyMCE to my application, which seems easy enough using the wicketstuff project. The point where I got stuck (for some hours now) is where I start adding the component carrying the TinyMceBehavior to any Ajax-Targets. What I'm trying to do is to populate the textarea based on selections from several DropDownChoices. But whenever an onChange-Event is called that adds the textarea to it's target, another editor appears right above the existing one containing the new content while the other editor gets moved down, still displaying the old values. Unfortunately I can't figure out what I'm doing wrong here... Any ideas would be greatly appreciated thanks David - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
FW: WicketTester, ListView, Hibernate and a custom WebRequestCycle
Hi, we're using a custom WebRequestCycle in our application to handle our Hibernate session. In onBeginRequest() the session is opened and closes in onEndRequest(). This works just fine when using Tomcat but fails with WicketTester. WicketTester is constructed using our application and the target directory to use the custom made classes, which is fine for most of our components except when using hibernate objects to populate ListViews. Logfiles indicate that onEndRequest() is called before populateItems() is run, so any use of an uninitialized hibernate proxy inside a ListView causes an Hibernate Exception (org.hibernate.LazyInitializationException: could not initialize proxy - no Session) and result in a failed test. A quickstart showing the failure is hard to cough up since it would involve an oracle database (I didn't had the time to check any other databases), but here's an excerpt from the logfile: 2008-07-17 15:25:33,783 DEBUG [main] com.dr.e5: adding startup configuration to session -- This is onBeginRequest() opening the sessions 2008-07-17 15:25:33,939 INFO [main] com.dr.e5: committing hibernate session: dev -- This is onEndRequest() committing the sessions 2008-07-17 15:25:33,955 DEBUG [main] com.dr.e5: adding startup configuration to session -- This is onbeginRequest opening another set of sessions 2008-07-17 15:25:34,002 ERROR [main] org.hibernate.LazyInitializationException: could not initialize proxy - no Session -- and this is finally hibernate failing to load from a proxy formerly attached tot he first set of sessions... Why is onEndRequest() called that early and why is onBeginRequest() called twice? Is there any way around this except checking and possibly reattaching every proxy just for testing since it works just fine in 'real life'? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: FW: WicketTester, ListView, Hibernate and a custom WebRequestCycle
Hi, thanks for your quick answer but since iolite doesn't seem to use a custom WebRequestCycle to manage the persistence sessions and we're not using spring at all I can't find any first-glance-similarities but haven't had the time to dive deeper into iolite yet. -Original Message- From: Nino Saturnino Martinez Vazquez Wael [mailto:[EMAIL PROTECTED] Sent: Thursday, July 17, 2008 5:42 PM To: users@wicket.apache.org Subject: Re: FW: WicketTester, ListView, Hibernate and a custom WebRequestCycle See the wicket iolite maven archetype, are it setup like that? David Hendrix wrote: Hi, we're using a custom WebRequestCycle in our application to handle our Hibernate session. In onBeginRequest() the session is opened and closes in onEndRequest(). This works just fine when using Tomcat but fails with WicketTester. WicketTester is constructed using our application and the target directory to use the custom made classes, which is fine for most of our components except when using hibernate objects to populate ListViews. Logfiles indicate that onEndRequest() is called before populateItems() is run, so any use of an uninitialized hibernate proxy inside a ListView causes an Hibernate Exception (org.hibernate.LazyInitializationException: could not initialize proxy - no Session) and result in a failed test. A quickstart showing the failure is hard to cough up since it would involve an oracle database (I didn't had the time to check any other databases), but here's an excerpt from the logfile: 2008-07-17 15:25:33,783 DEBUG [main] com.dr.e5: adding startup configuration to session -- This is onBeginRequest() opening the sessions 2008-07-17 15:25:33,939 INFO [main] com.dr.e5: committing hibernate session: dev -- This is onEndRequest() committing the sessions 2008-07-17 15:25:33,955 DEBUG [main] com.dr.e5: adding startup configuration to session -- This is onbeginRequest opening another set of sessions 2008-07-17 15:25:34,002 ERROR [main] org.hibernate.LazyInitializationException: could not initialize proxy - no Session -- and this is finally hibernate failing to load from a proxy formerly attached tot he first set of sessions... Why is onEndRequest() called that early and why is onBeginRequest() called twice? Is there any way around this except checking and possibly reattaching every proxy just for testing since it works just fine in 'real life'? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- -Wicket for love Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -David Hendrix - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
