Re: formComponentPanel with content generated by RepeatingView

Override convertInput is a good option. Keep in mind that at this point of the form processing (converting input), component models will not be updated yet. So you need to rely on children converted data (see FormComponet#getConvertedInput) in order to assemble the FormComponentPanel converted inpu

formComponentPanel with content generated by RepeatingView

hi, Im trying to implement a simple form component that accepts List of Strings *public class AccountsPanel extends FormComponentPanel> { ****public AccountsPanel(String id, ArrayList accounts) { ******super(id, new Model(accounts)); buildComponents(); } } *and I am using

RE: ModalWindow patch for 1.4.x

Martin, I have attached a quickstart to the JIRA issue which demonstrates an alternate implementation of WindowClosedBehavior, using an AjaxFormSubmitBehavior extension. RUSSELL E. MORRISEY Programmer Analyst Professional Mission Solutions Engineering, LLC | r

Re: terrain view in gmap2

Hi, The best way is to checkout the existing code and add in the changes needed to allow you to access the new type (probably both Javascript and Java changes will be needed). GMap2 is in wicketstuff core here: https://github.com/wicketstuff/core (https://github.com/wicketstuff/core/tree/co

Re: terrain view in gmap2

As I can see in the wicket-map.js, the types are hardcoded as following: this.getMapTypeString = function(mapType){ switch (mapType) { case G_NORMAL_MAP: return 'G_NORMAL_MAP'; break; case G_SATELLITE_MAP: return 'G_SATELLITE_MAP'; break; case G_HYBRID_MAP: return 'G_HYBRID_MAP'; break; default: r

Re: DropDownChoice sorted choice rendered Values

A simple solution is to create a custom model which stores the result of Locale.getAvailableLocales() in a list, and you sort that list with a custom comparator. You can then pass this model to your DropDownChoice and have the result you were looking for. Bas Op 21-4-2011 16:46, schreef xF

DropDownChoice sorted choice rendered Values

Hi all, I've used quite intensively the DropDownChoice component on my forms. But in some cases, I've added to some of those DropDownChoices some ChoiceRenderer. The choices Model I could pass to CTOR could easily be sorted, but in this case, not the rendered values behind this list . As an exa

Re: Migrating from 1.4.16 to 1.5 RC3 - problem when trying to avoid pages caching (not calling the constructor of the java pages)

Hi Martin, > AFAIU Ismael wanted each request to instantiate a new page instance. ah, ok. I thought he did this to avoid the same exception like me ... > Recently I wrote such integration between Wicket and > http://tkyk.github.com/jquery-history-plugin/ for a client. I guess nothing open s

RE: ModalWindow patch for 1.4.x

Martin, Thanks for your reply. I created a JIRA issue with the .patch file: https://issues.apache.org/jira/browse/WICKET-3630 I will work on creating an example. Thanks, RUSSELL E. MORRISEY Programmer Analyst Professional Mission Solutions Engineering, LLC | russell.morri...@missionse.com | w

terrain view in gmap2

Hi, How can I show the terrain view in google maps using gmap2? As of now, I can only see the hybrid and satellite views by adding the respective controls using map.addConrol(GControl.GMapTypeControl). I am using the 1.4.16 version of gmap and wicket. Thanks you in advance. Daku

Re: Migrating from 1.4.16 to 1.5 RC3 - problem when trying to avoid pages caching (not calling the constructor of the java pages)

Hi Peter, AFAIU Ismael wanted each request to instantiate a new page instance. That's why I suggested either use completely stateless page or use a mapper which will create a new instance every time. And this should be combined with #disableCaching() so that the browser hits the server every time.

Re: Migrating from 1.4.16 to 1.5 RC3 - problem when trying to avoid pages caching (not calling the constructor of the java pages)

Hi Martin, I'm using the same technic in 1.4 to avoid exceptions with ajax + backbutton(not sure if this is true for Ismael too): * click on an ajax linkA, and click another one. * hitting back button * clicking again ajax linkA * WicketRuntimeException: component filterPanel:filterNames:1:f

Re: Migrating from 1.4.16 to 1.5 RC3 - problem when trying to avoid pages caching (not calling the constructor of the java pages)

Hi, In 1.5 there is org.apache.wicket.request.http.WebResponse.disableCaching() which does the same as you did. But this is not related to your problem. When reloading the page Wicket will re-render the same page if it is stateful, i.e. there is a special parameter in the URL, e.g. ?2&something=e

Re: Wicket requests

Hi Yes, wicket usually handles such things internally, saving you the overhead of multiple redirects. However, if you need to modify cookie data and you must rely on getting these infos back in the following request, you need to force a round trip to the client using setRedirect(true). HOWEVE

Wicket requests

Hi, I am quite new to wicket, and I am trying to better understand how the requests are handled. My problem is this: I have a landing page in my application, where I check if the session is a correct one(I have a parameter called sessionId which dictates the user's session). If the session is