What you want to achieve is been able to click on your labels (created via <wicket:translation key="home:nameField">) and replace then with some editable components? If so, maybe you could do it as follows.
1-Place some abstract ajax behavior (AAB) on your "base" page so that you have some unique context to submit back changes on your labels texts 2-Modify you wicket:transforms so that it generates a new input field via JavaScript plus some link to submit or cancel you changes. You could use the URL of AAB to summit back to the server your changes via wicektAjaxGet() plus appending the text of the modified label as a parameter (plus a parameter identifying your key). 3-You process the result on the AAB (you will have your key and the modified message posted by step 2). Although I haven't tried the above myself, it seems to me that it could be easily achievable... Ernesto On Sun, Sep 26, 2010 at 8:40 PM, Mihai Postelnicu <[email protected]> wrote: > Any idea how can we approach this differently ? we need a component spawned > in html (because we have some default translatable text in the html that we > have to enclose and also acts as the key) with callbacks and two states > (edit mode and read only, much like ajaxeditablelablel). > > Any idea is welcome ! > > Thanks > Mihai > > > On 09/26/2010 10:51 AM, Igor Vaynberg wrote: >> >> it can modify hierarchy, but the components it adds only exist during >> the render phase - so those components cannot receive callbacks or >> hold state. >> >> -igor >> >> On Sat, Sep 25, 2010 at 10:41 PM, Alexander Morozov >> <[email protected]> wrote: >> >>> >>> So IComponentResolver cannot modify component hierarchy. Right ? And >>> there is >>> no way for the author to create and handle "special" >>> tag<translate>. >>> >>> >>> -- >>> View this message in >>> context:http://apache-wicket.1842946.n4.nabble.com/Saving-a-component-in-session-tp2551649p2714088.html >>> Sent from the Users forum mailing list archive at Nabble.com. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail:[email protected] >>> For additional commands, e-mail:[email protected] >>> >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail:[email protected] >> For additional commands, e-mail:[email protected] >> >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
