With some more logging: The second time around, the action method in AjaxModalDialog does not get called. But the action method in AjaxModalDialogOpener does get called.
So the page is already messed up the second time it opens. This could point the finger at the update container. Thanks. On Oct 18, 2013, at 2:53 PM, Chuck Hill <[email protected]> wrote: > The dialog not closing should mean either a JavaScript error on the page or > an exception on the back end resulting in the wrong (or or likely no) > JavaScript getting returned to the client. Seeing the same data again > makes me suspect the second but then I would expect the same result in > Eclipse. > > I recall a problem with some JavaScript going out of scope in the page after > an AjaxUpdate, but the details are not coming to me. > > Chuck > > > On 2013-10-17 9:40 PM, "Klaus Berkling" wrote: > > > I have a page that has a page wrapper and on that page is also a reusable > component. > There is nothing but simple strings in the page and it's wrapper. > > The reusable component does have a number of Ajax things on it. > - There are three AjaxModalDialog outside of everything, outer to inner: a > WOForm, an AjaxUpdateContainer, an AjaxObserveField, and a WORepetition. > - For all three dialogs I use AjaxModalDialogOpener. > - Two of the three dialog openers are inside the repetition. One is inside > the observe field. > > The repetition is an array of people, each person has a one-to-many > additional records. > One dialog edits the person's record, another dialog edits the additional > records for that person, and the third is to create a new person record. > Each of the dialogs is a component, a new person and edit person share the > same component. > > Alles klar? > > So here is the problem. > - When I run the app and view the list of persons, open the dialog to edit > the additional records then cancel or save, it works the first time. > > - If I do the same edit again for any other person I get the information of > the first person in the dialog. > > - The submit buttons (cancel, save) do not close the dialog the second time > (calling AjaxModalDialog.close(context());). > Clicking the buttons in the dialog cause awake() to be called on all three > components (page, page wrapper, reusable component). > > For extra pain, this only happens when deployed, not when debugging in > Eclipse. > When first deployed I had to add WOFrameworksBaseURL because the Ajax > frameworks javascripts didn't load (404 errors). > Fixed that and now there are no errors on the page in the browser. I'm still > suspicious that my problem has to do with a bad reference on the page, some > incorrect URL. > > It's a build with embedded frameworks. > > Anyone have any suggestions on what the problem might be? Am I putting too > mach Ajax on the page? > > TIA > > kib > > Klaus Berkling > www.berkling.us | @kiberkli > > > > > > -- > Chuck Hill > Executive Managing Partner, VP Development and Technical Services > > Practical WebObjects - for developers who want to increase their overall > knowledge of WebObjects or who are trying to solve specific problems. > http://www.global-village.net/gvc/practical_webobjects > > Global Village Consulting ranks 13th in 2012 in BIV's Top 100 Fastest Growing > Companies in B.C! > > Global Village Consulting ranks 44th in 25th annual PROFIT 500 ranking of > Canada’s Fastest-Growing Companies by PROFIT Magazine! kib Klaus Berkling www.berkling.us | @kiberkli
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
