Hi, Something else breaks the behavior. Create a quickstart app and you will see that AjaxEditableLabel works fine in Production mode.
On Wed, Sep 26, 2012 at 6:58 PM, Corbin, James <[email protected]> wrote: > Hi Martin, > > Thanks for the feedback. What is a bit confusing to me is how the > behavior changes when running wicket in Production Mode (doesn't work) vs. > Development Mode (works). I don't see why the wicket application mode > would cause this behavior to change. > > In our situation the AjaxEditableLabel component is nested in a table cell > and the table itself is parented by a Form. > > I will look for JS errors as you suggest. > > Thanks, > J.D. > > > > > > > > On 9/26/12 12:59 AM, "Martin Grigorov" <[email protected]> wrote: > >>Hi, >> >>It sounds like a JavaScript related problem. >>It could be that there is blocked Ajax channel and the click cannot >>make it to the server. Or something similar happened once, this leaded >>to different state at the server and the client and since then it >>cannot re-synchronizes the states. >> >>Reload the page and look for JavaScript errors. >>In Firebug do: Wicket.Log.error = function(text) {console.log(text);} >> >>On Tue, Sep 25, 2012 at 9:25 PM, Corbin, James <[email protected]> >>wrote: >>> I have an interesting issue that crept up in the use of the >>>AjaxEditableLabel component in Wicket 1.4.13 (I know, ancient). >>> >>> The component stopped processing the click event that is supposed to >>>cause the editor to render. I was seeing different behavior depending >>>upon the mode of the Wicket Application and wondered if anyone might >>>have a clue as to what was going on. >>> >>> With the exact same source code, when the Wicket Application was >>>configured to run in Production Mode, the AjaxEditableLabel would not, >>>when clicked, render the editor, but when in Development mode, it worked >>>as expected. >>> >>> In the server log there is a warning that the component is either not >>>visible or not enabled, which I know isn't true because it works >>>perfectly fine when the Wicket Application is in Development Mode. >>> >>> The only behavior that is being overridden on the AjaxEditableLabel >>>instance is the onSubmit. >>> >>> I searched the forums and google and could not find anything that would >>>explain the different behavior of this component when the application >>>mode was changed from development to production. >>> >>> Interesting enough, the AjaxEditableLabel does work fine in Production >>>mode in other areas of the application when no behaviors are overridden. >>> Not sure if that has anything whatsoever to do with this issue. >>> >>> Ideas? >>> >>> J.D. >> >> >> >>-- >>Martin Grigorov >>jWeekend >>Training, Consulting, Development >>http://jWeekend.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] > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
