<div>
you may use postMessage to communicate between Modal and caling page :<br />
<a href="https://developer.mozilla.org/fr/docs/Web/API/Window/postMessage" rel="ugc">https://developer.mozilla.org/fr/docs/Web/API/Window/postMessage</a>
</div>


you may use postMessage to communicate between Modal and caling page :
https://developer.mozilla.org/fr/docs/Web/API/Window/postMessage [https://developer.mozilla.org/fr/docs/Web/API/Window/postMessage]

<div>
<div class="content wysiwyg-content">
I recently migrate the Wicket 1.4 application to 1.5<br />
In 1.5 I was using inter-component event to pass value from the ModalWindow's page to the calling page (in 1.4 ModalWindow.WindowClosedCa<wbr />llback was used for this purpose).<br />
The problem : in onEvent I can't update the container from the calling page's panel because AjaxRequestTarget provided with event belongs to ModalWindow, not to the calling page.<br />
I tried to update the calling page with setResponsePage(getPage())<wbr /> in onEvent, but it reloads the right data in ModalWindow first (I issued close for it before), and then after clicking on close button in ModalWindow, the target container would be refreshed (in the calling page)
</div>
</div>


I recently migrate the Wicket 1.4 application to 1.5
In 1.5 I was using inter-component event to pass value from the ModalWindow's page to the calling page (in 1.4 ModalWindow.WindowClosedCallback was used for this purpose).
The problem : in onEvent I can't update the container from the calling page's panel because AjaxRequestTarget provided with event belongs to ModalWindow, not to the calling page.
I tried to update the calling page with setResponsePage(getPage()) in onEvent, but it reloads the right data in ModalWindow first (I issued close for it before), and then after clicking on close button in ModalWindow, the target container would be refreshed (in the calling page)

Wicket 1.5 : inter-component event with ModalWindow

Web Components are a set of standards currently being produced by Google engineers as a W3C specification that allow for the creation of reusable widgets or components in web documents and web applications. The intention behind them is to bring component-based software engineering to the World Wide Web. The components model allows for encapsulation and interoperability of individual HTML elements. Support for Web Components is present in Chrome and Opera and is in Firefox (with a manual configuration change). Microsoft's Internet Explorer has not implemented any Web Components specifications yet. Web Components consist of 4 main elements: Custom Elements, Shadow DOM, HTML Imports and HTML Templates.

Web Components

Java is a platform-independent, object-oriented programming language and run-time environment, designed to have as few implementation dependencies as possible such that developers can write one set of code across all platforms using libraries. Most devices will not run Java natively, and require a run-time component to be installed in order to execute a Java program.

Java

Asynchronous JavaScript and XML (AJAX) is a group of interrelated Web development techniques used on the client-side to create asynchronous Web applications. With AJAX, web applications can send data to and retrieve from a server asynchronously (in the background) without interfering with the display and behavior of the existing page. HTML and CSS can be used in combination to mark up and style information. The Document Object Model (DOM) is accessed with JavaScript to dynamically display and allow interaction with the information presented.