[
https://issues.apache.org/jira/browse/WICKET-6411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Grigorov updated WICKET-6411:
------------------------------------
Priority: Minor (was: Major)
> Easy to embed wicket widgets into 3rd party pages
> -------------------------------------------------
>
> Key: WICKET-6411
> URL: https://issues.apache.org/jira/browse/WICKET-6411
> Project: Wicket
> Issue Type: New Feature
> Components: wicket
> Reporter: Vaclav Slovacek
> Priority: Minor
>
> Until recently iframes were the primary method of embedding 3rd party
> widgets/components/content into your pages. However recent trends in
> JavaScript frameworks such as Angular and React enable to seamlessly embed
> 3rd party widgets directly into the original page DOM. This overcomes several
> limitations of iframes including ability to render outside of the iframe.
> Ideally you would like to tell the author of the parent page to embed some
> code like this:
> {code:html}
> <head>
> <script src="https://myApplication.com/allYouNeed.js";></script>
> </head>
> <body>
> <div wicket:embed="id/path or something identifying the component"></div>
> </body>
> {code}
> The included JS would contain bootstrap that finds all embedded Wicket
> components and does AJAX requests to get HTML content to render in the divs.
> There are couple of things that would need to be done like contributing to
> the parent page header items. Making sure the content from wicket is returned
> without <html><head><body> wrapping tags.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
