Re: RadioGroup selected model value

Hi Sven, Thanks for the clarification . Now I understand much more. I tried out your code your code with the following modification. Now when the page is shown , * the object with value debut2 is effectively selected as expected*. I Thanks you . - Selom -- View this message

Re: Why org.apache.wicket.pageStore.memory.PageTable isn't public?

Improved with https://issues.apache.org/jira/browse/WICKET-5444 Thanks ! Martin Grigorov Wicket Training Consulting On Fri, Dec 13, 2013 at 8:31 PM, tomask79 tomas.klou...@embedit.cz wrote: Hi Martin, ok I will, thanks for answer and apology for kind of angry post..:) Best wishes Tomas

Script Error is getting in IE8 while selecting DatePicker in Modal Window

Hi, i'm getting script error, when trying to provide the Date picker in modal window on IE8 browser, this works fine in IE9 IE10 without any issues. Script error is getting at the below code in calendar-min.js at line no. 18, the bold one below from the code. try {

a little question about add(new XComponent(id).setVisible(false))

Hi First, the scenario (a simplified version): I have a XPage (extends WebPage) and in the constructor of this page I want to add a YPanel (extends Panel) but depending on a condition. if (condiiton) { add(new YPanel(panel)); } else { add(new WebMarkupContainer(panel).setVisible(false));

Re: Script Error is getting in IE8 while selecting DatePicker in Modal Window

The first thing I would check is that the ModalWindow is wrapped in a Wicket Form (see the end of the class-level Javadoc for ModalWindow: If you want to use form in modal window component make sure that you put the modal window itself in another form). If it's not, the date picker doesn't work

Re: a little question about add(new XComponent(id).setVisible(false))

i think what you need is onbeforerender() and not oninintialize, before rendering visibility is determined( if curious check the source in component#internalbeforer()) , also i am assuming when you will create/add 100 labels,you will use a repeater like dataview/listview which creates and adds

Re: a little question about add(new XComponent(id).setVisible(false))

I tested with: public class MyPanel extends Panel { public MyPanel(String id) { super(id); } @Override protected void onBeforeRender() { super.onBeforeRender(); add(new MyLabel(l1,

RE: Wicket session in a Resource

Thanks Martin, knowing that it is safe to access the session is a real comfort. Sorry for responding so late, but due to illness I haven't been in the office the end of previous week. We will look into the patch. With kind regards, -Stijn -Original Message- From: Martin Grigorov

AutoComplete stopped working in 6.12

Converting from 1.4.7 to 6.12. The page runs, but the autocomplete field has stopped working. It never produces an autocomplete, acting as if it were simply a normal . More strangely, no code in the containing panel was changed, nor do I see anything in the migration guide about

Re: AutoComplete stopped working in 6.12

Hi, Look for : Wicket.Ajax.get( ..., c: agcy, ...) in the generated html for the page. Also check whether an Ajax call is made when typing something in the input field. Better use Firebug or Google Chrome's Dev Tools than IE. Martin Grigorov Wicket Training Consulting On Mon, Dec 16, 2013 at

Re: AutoComplete stopped working in 6.12

Solved. Not long after posting this I found http://stackoverflow.com/questions/14481767/wicket-autocomplete-in-wicket-6-2-0 which explains that Wicket now includes it's own jQuery...which I'd read, but hadn't made the connection to this problem. When I took out the jQuery base js include, the

Component render flag inconsistency after exception during Ajax update

Hi Am using Wicket 1.5.10. In Component's render() method I note the finally block to ensure afterRender() is run which always sets FLAG_RENDERING to false, regardless of what might have occurred during render or afterRender(). However I can't see any similar cleanup code for the

Re: a little question about add(new XComponent(id).setVisible(false))

I think it's fine to change the hierarchy in onBeforeRender(), as long as you do it before calling super.onBeforeRender(), since that calls OBR on the children of your panel. And (you gotta love wicket), this is even made explicit in the source code of MarkupContainer#onBeforeRender(): /**

Re: Component render flag inconsistency after exception during Ajax update

Hi, Please create a quickstart/test case and attach it to a ticket in JIRA. Thanks! Martin Grigorov Wicket Training Consulting On Tue, Dec 17, 2013 at 1:30 AM, Sam Holmes sbhol...@gmail.com wrote: Hi Am using Wicket 1.5.10. In Component's render() method I note the finally block to