Yeah, I get that. The problem with that is that I can't reproduce the issue locally with the FULL APPLICATION, so I am reasonably certain that I won't be able to reproduce it with a quickstart. It only happens on the server AND when this panel is visible. I attached the panel as a file if that would help. I did this through nabble's upload file interface, so I am not sure how that arrives to you...I would hope as an email attachment?
My next step was that I set all org.apache.wicket to DEBUG in log4j. This produces quite alot of noise, but I am mostly confident that I got the statements for that request figured out. There's a bunch of these before and after: 2013-12-19 07:27:57,035 - org.apache.wicket.util.thread.Task - DEBUG - Run the job: org.apache.wicket.util.watch.ModificationWatcher$1@65586558 2013-12-19 07:27:57,036 - org.apache.wicket.util.thread.Task - DEBUG - Finished with job: org.apache.wicket.util.watch.ModificationWatcher$1@65586558 But i don't think those are relevant. The block then begins: 2013-12-19 07:27:57,054 - org.apache.wicket.Session - DEBUG - Getting page [path = 6:form, versionNumber = 0] 2013-12-19 07:27:57,055 - org.apache.wicket.Component - DEBUG - Begin render [Page class = gov.usdoj.afms.umc.modules.UM10.Step2_Criteria, id = 6, version = 0] 2013-12-19 07:27:57,056 - org.apache.wicket.MarkupContainer - DEBUG - Rendering raw markup 2013-12-19 07:27:57,056 - org.apache.wicket.MarkupContainer - DEBUG - Add _header_16 to [Page class = gov.usdoj.afms.umc.modules.UM10.Step2_Criteria, id = 6, version = 0] 2013-12-19 07:27:57,056 - org.apache.wicket.Component - DEBUG - Begin render [MarkupContainer [Component id = _header_16]] 2013-12-19 07:27:57,057 - org.apache.wicket.MarkupContainer - DEBUG - Rendering raw markup 2013-12-19 07:27:57,057 - org.apache.wicket.MarkupContainer - DEBUG - Add _relative_path_prefix_17 to [MarkupContainer [Component id = _header_16]] After the first line, this "Begin Render" pattern repeats itself many times with varying components. But what I found interesting is that the only line between the modifcation block and the render block was that "Getting page" line. This implies to me that wicket didn't forward the event to any application code, it just repainted the page as if it were a refresh. I also notice that the URL never changes. It is: http://dev-catsapp-01:9085/ManagementCenter/?wicket:interface=:6:::: both before and after the request. I am used to seeing wicket increment that number, like a request counter, excepting when I am on a bookmarkable page. That is how it works in localhost as well. DocTypeSelect.java <http://apache-wicket.1842946.n4.nabble.com/file/n4663130/DocTypeSelect.java> -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/1-4-7-app-form-does-not-submit-on-server-when-panel-is-not-visible-tp4663114p4663130.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
