Re: Wicket 1.5 Page Expired in JMeter

when changing the page inside my application (setResponsePage). I tested a Wicket application without page change, but with panel exchanges - no problem! rawe -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-1-5-Page-Expired-in-JMeter-tp4661732p4661769.html

Wicket 1.5 Page Expired in JMeter

the Apache JMeter/Wicket Page and did some research about this topic, but I got no answer what the problem is. Maybe I can get some help or hints here!? Thanks! rawe -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-1-5-Page-Expired-in-JMeter-tp4661732.html Sent

Re: Forms marked as multipart do not work with ajax and IE9

We had the same problem with IE9 Our solution. Set the starting page markup to: meta http-equiv=X-UA-Compatible content=IE=edge/ -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Forms-marked-as-multipart-do-not-work-with-ajax-and-IE9-tp3502174p4606081.html Sent from

404 error using Wicket 1.5.4 and Websphere 6.1

Hi, after updating from Wicket 1.4 to 1.5.4 I get a 404 error when doing a form submit. I get this error when calling a SubmitLink or a normal page submit. It's working in Tomcat 6, but not with Websphere 6.1 My Log output is empty - no error log ! The only message is (german): Error 404:

Re: 404 error using Wicket 1.5.4 and Websphere 6.1

What I see in Firebug on tab network, when running the application under tomcat is: /POST page?9-3.IFormSubmitListener-frmOrderDetail 302 Moved Temporarily localhost:8080 0 127.0.0.1:8080/ Normally I get a status of 200. That's why Websphere can't find the page : 302 Moved Temporarily

Re: 404 error using Wicket 1.5.4 and Websphere 6.1

Yes, also when a redirect is a normal operation it seems that Websphere 6.1 cannot handle it. see also the known problem with glassfish: https://issues.apache.org/jira/browse/WICKET-2732 https://issues.apache.org/jira/browse/WICKET-2732 -- View this message in context:

Re: 404 error using Wicket 1.5.4 and Websphere 6.1

Yes, I think the problem could be the servlet-api version. WAS 6.1 is running with servlet-api 2.4, so I won't install a wicket 1.5 application on it! Thanks for your help! Ralph -- View this message in context:

Re: Markup not found when upgrading from 1.4.18 to 1.5

Hi, you wrote / ... you should pass the form as parent container of the fragment instance. / The problem is that I have multiple fragments within my form. And if I pass the form as parent container for each fragment I get an ... child already exists... exception. That's why I'm inserted

Re: Markup not found when upgrading from 1.4.18 to 1.5

Thanks for your hints, Martin! Now I found the solution. Two changes I had to do: *1)* The difference now is, that the parent component passed to the fragment must be the exact parent. e.g. I used the same fragments for display and edit mode. I passed the page as parentComponent to fragment. /new

Markup not found when upgrading from 1.4.18 to 1.5

I changed my app from wicket 1.4.18 to 1.5.4 Now I get a MarkupNotFound Exception. In 1.4. the app was running without warnings/errors Does somebody have a hint? I'm using a form within a page. The form has a fragment child. *MarkupCode*: /div wicket:id=contentFragment1/ wicket:fragment

Re: Markup not found when upgrading from 1.4.18 to 1.5

Martin, do you mean something like ?? / div wicket:id=contentFragment1/ wicket:child wicket:fragment wicket:id=orderFragment1 fieldset ... /fieldset /wicket:fragment /wicket:child / Doesn't work! But normally I don't need a child tag due I don't include markup from a subclass

WiQuery 1.5.4 and Wicket 1.5.4 Problem

Hi, I changed my WiQuery version from 1.5M2 to 1.5.4 I'm running Wicket 1.5.4. I had no problem running my application with tomcat when using Wiquery 1.5M2. Now after I changed to Wiquery 1.5.4 my tomcat (5.0) fails starting with following error: java.lang.ClassCastException:

RE: WiQuery 1.5.4 and Wicket 1.5.4 Problem

Yes, this was the right hint! I included also the same version (1.5.4) of wiquery-jquery-ui and wiquery-core jar files in WEB-INF/lib but I didn't delte the old versions of 1.5-M2 It's running now! Thank you! Ralph -- View this message in context:

Re: Validating in form returns always error but textfield has a value

Here are some code snippets. When clicking on a tree node I validate the form.. If no errors I update the form component models. The class MyMutableTreeNode extends DefaultMutableTreeNode. Each node references an own panel component. getNodeEntryDetail() returns the panel referenced by the node.

Re: Using SubmitLink as a tree node ?

Hi Martin, thank you! This was the helping hint! works perfectly! Ralph -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Using-SubmitLink-as-a-tree-node-tp3914407p3914691.html Sent from the Users forum mailing list archive at Nabble.com.

Re: Validating in form returns always error but textfield has a value

Yes, I'm using the form default setting (DefaultFormProcessing = true). But for form processing you have to use a submit button or a SubmitLink or you can call the form validate() method programmatic. See also Wicket API Doc of Form: (

Re: Validating in form returns always error but textfield has a value

Got it ! Thank you! Ralph -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Validating-in-form-returns-always-error-but-textfield-has-a-value-tp3912361p3914841.html Sent from the Users forum mailing list archive at Nabble.com.

Validating in form returns always error but textfield has a value

I'm using a LinkTree and to each node a panel is referenced. Both is embedded in a form component. The panels have textfields. When using a submit button or a SubmitLink the input of the textfields is valid and then also validation is valid. But: My intension is also to validate the form each

Re: Validating in form returns always error but textfield has a value

Yes, each time I change the node the form is submitted. The textfields in the panel are initialized via PropertyModel and are set to required. When I want to change the node I call validate() but the rawInput of textfields is null. -- form.hasError() is always true, but there are values in the

Selenium Problem

I'm trying to do functional tests using Selenium IDE. I did getDebugSettings().setOutputComponentPath(true); to solve the problem with dynamic ids. see also: http://www.inforw.de/content/doku.php/blog/300 It works for most actions in my application, but after recording the usage of

Re: Selenium Problem

Thank you for your hint! It's working if I explecitly set the ID to DropDownChoice component foo.setMarkupId(fooId); Thanks! Ralph -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Selenium-Problem-tp3514063p3514214.html Sent from the Users forum mailing list archive

Re: Problem using dynamic select with optgroups and Firefox

see solution in http://apache-wicket.1842946.n4.nabble.com/Dynamic-Select-and-SelectOptions-tp1872483p3310381.html It's also working with firefox. My problem before was just a javascript failure. greetings Ralph -- View this message in context:

Problem get selected value using dynamic select with optgroup

I'm using the select component due to realizing a dynamic optgroup and option list. It works rather fine but my problem is to get the selected value. I tried to use an ajax behavior (AjaxComponentUpdatingBehavior, OnChangeBehavior) but the onUpdate methode is never called -- doesn't work! Maybe

Re: Dynamic Select and SelectOptions

The solution is to nest the ListViews: Markup: select wicket:id=selectId wicket:container wicket:id=optGroups optgroup wicket:id=optGroup wicket:container wicket:id=options option wicket:id=option/option

Re: Dynamic Select and SelectOptions

It's working fine with IE, safari, Chrome, Opera but not with Firefox (FF) The optgroup closing tag is set wrong. The options are not enclosed in the optgroup tags. Firebug shows following rendering optgroup label=German Cars wicket:id=optGroup/optgroup option

Problem using dynamic select with optgroups and Firefox

Problem or bug in Firefox when using a dynamic wicket select component. Firefox can't handle ListView and right placing of optgroup tags! Please See following thread: http://apache-wicket.1842946.n4.nabble.com/Dynamic-Select-and-SelectOptions-tc1872483.html#a3310381

Re: Problem using dynamic select with optgroups and Firefox

Yes, when just using a list of options a dropdownchoice ist the best way! But in my case I need a dynamic select with optgoups and dynamic options. My problem is solved now. I found a css error in my code. The solution works fine now also with firfox! ralph -- View this message in context:

Re: Dynamic Select and SelectOptions

Hi, good solution, but how does it work using a ListView ?? I tried: Select select = new Select(selectId); select.add(new ListView(selGrpId, list) { OptGroup optGrp = null; @Override protected void populateItem(ListItem

Re: DatePicker configuration isn't always working

Yes, I solved it! When displaying the calendar the first time it's mandatory to call its clear method (Clears the selected dates in the current calendar widget and sets the calendar to the current month and year. ) My solution: @Override protected String getAdditionalJavascript() { if

Re: Renderer does not work when DatePicker is initially displayed

Here is the solution: Just use calendar's clear method: e.g. @Override protected String getAdditionalJavascript() { if (additionalJavascript == null) additionalJavascript = ; additionalJavascript += ${calendar}.addWeekdayRenderer(1,

Re: How can override calendar formatting at initialization using DatePicker? getAdditionalJavascript not always working...

Yes, I solved it! When displaying the calendar the first time it's mandatory to call its clear method (Clears the selected dates in the current calendar widget and sets the calendar to the current month and year. ) My solution: @Override protected String getAdditionalJavascript() { if

Re: DatePicker configuration isn't always working

Did you already solve your problem? I got the same problem. Thanks for any help! Ralph Weyers -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/DatePicker-configuration-isn-t-always-working-tp1878188p2247457.html Sent from the Wicket - User mailing list archive at

Closing modalWindow outside the dialog window by mouse click

Maybe a solution was already posted, I didn't find an answer ! I want to close a modal window just by mouse click outside the modal window (dialog). I tried some javascript code: var win = window.Wicket.Window; if (typeof(win.current) != undefined) { win.current.close(); }

Re: How can override calendar formatting at initialization using DatePicker? getAdditionalJavascript not always working...

I got the same problem! Did you solve it already? If yes, I would be glad to get some help! I just disabled the weekend days in DatePicker by overriding the method @Override protected String getAdditionalJavascript() { additionalJavascript +=

Renderer does not work when datePicker is initially displayed

);; // disable sundays additionalJavascript += ${calendar}.addWeekdayRenderer(7, ${calendar}.renderOutOfBoundsDate);; // disable saturdays return additionalJavascript; } Thanks for any help! rawe -- View this message in context: http://apache-wicket.1842946.n4.nabble.com