Thanks for the example.  It makes perfect sense now that I see it.  I
can even run the sample as its own project and see it working.  Now, I
took your example and put it into my project's codebase and the submit
button in the modal panel does not cause the form to be submitted.
Obviously I have something  wrong with my code.  Any ideas on why the
submit button does not cause any code to fire.  The ajax debugger is
showing that my button is not returning any data.

 

In the Ajax Debugger for my app I see:

INFO: Initiating Ajax POST request on
?wicket:interface=:2:irf:form:view:modalWindow:content:modifyPerson:save
::IActivePageBehaviorListener:0:1&wicket:ignoreIfNotActive=true&random=0
.6665615341811421

INFO: Invoking pre-call handler(s)...

INFO: Received ajax response (69 characters)

INFO:

<?xml version="1.0" encoding="UTF-8"?><ajax-response></ajax-response>

INFO: Response parsed. Now invoking steps...

 

 

In the Ajax Debugger for the sample app I see:

 

INFO: Initiating Ajax POST request on
?wicket:interface=:0:wizard:form:view:modalWindow:content:form:submit::I
ActivePageBehaviorListener:0:-1&wicket:ignoreIfNotActive=true&random=0.3
515502192017532

INFO: Invoking pre-call handler(s)...

INFO: Received ajax response (1985 characters)

INFO:

<?xml version="1.0"
encoding="UTF-8"?><ajax-response><header-contribution encoding="wicket1"
><![CDATA[<head xmlns:wicket="http://wicket.apache.org";><script
type="text/javascript"
src="resources/org.apache.wicket.markup.html.WicketEventReference/wicket
-event.js"></script>

<script type="text/javascript"
src="resources/org.apache.wicket.ajax.WicketAjaxReference/wicket-ajax.js
"></script>

<script type="text/javascript"
src="resources/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/wicket
-ajax-debug.js"></script>

<script type="text/javascript"
id="wicket-ajax-debug-enable"><!--/*--><![CDATA[/*><!--*/

wicketAjaxDebugEnable=true;

/*-->]^]^>*/</script>

 

<script type="text/javascript"
src="resources/org.apache.wicket.extensions.ajax.markup.html.modal.Modal
Window/res/modal.js"></script>

<link rel="stylesheet" type="text/css"
href="resources/org.apache.wicket.extensions.ajax.markup.html.modal.Moda
lWindow/res/modal.css" />

</head>]]></header-contribution><component id="view3" ><![CDATA[<div
class="wicketExtensionsWizardViewInner" id="view3">

 

name: <label>t</label><br />

description: <label>t</label><br />

<span id="modalWindow4" style="display:none">

    <div id="content5" style="display:none"></div>

</span><br />

<a id="showModal6" href="#" onclick="var
wcall=wicketAjaxGet('?wicket:interface=:0:wizard:form:view:showModal::IB
ehaviorListener:0:-1',null,null, function() {return
Wicket.$('showModal6') != null;}.bind(this));return !wcall;">show
modal</a>

</div>]]></component><evaluate><![CDATA[var win;

try {

    win = window.parent.Wicket.Window;

} catch (ignore) {

}

if (typeof(win) == "undefined" || typeof(win.current) == "undefined") {

  try {

     win = window.Wicket.Window;

  } catch (ignore) {

  }

}

if (typeof(win) != "undefined" && typeof(win.current) != "undefined") {

 var close = function(w) { w.setTimeout(function() {

        win.current.close();

    }, 0);  } 

    try { close(window.parent); } catch (ignore) { close(window); };

}]]></evaluate></ajax-response>

INFO: Response parsed. Now invoking steps...

 

 

 

 

From: Pedro Santos [mailto:pedros...@gmail.com] 
Sent: Friday, October 09, 2009 1:15 PM
To: users@wicket.apache.org
Subject: Re: Showing Modal window within a wizard step

 

I am completely lost.  I have no idea what this means.  How can the
resolution to my problem be a JIRA issue that was created earlier today?
It is just an "wish" for javadoc improvements, not the solution.

Sending an example attached

On Fri, Oct 9, 2009 at 1:49 PM, Jeremy Thomerson
<jer...@wickettraining.com> wrote:

Sorry - typo on that step.  The intent was that you use "new
Model(model.getObject())" to pull an object out of any potential
loadable /
detachable model that may be passed in.


--
Jeremy Thomerson
http://www.wickettraining.com



 

Reply via email to