Releases: vaadin/portlet
Vaadin 23 Portlet Support release 2.1.0
2.1.0.rc1
What's Changed
- chore: Upgrade to license checker 1.5.1 by @Artur- in #232
- test: setup webdrivermanager and headless chrome for local development by @mcollovati in #233
- Add CvdlName to manifest by @Artur- in #236
- chore: Update versions by @mshabarov in #237
- chore: Update version to next minor by @mshabarov in #242
- chore: update vaadin license by @ZheSun88 in #241
New Contributors
Full Changelog: 2.0.0...2.1.0.rc1
Contributors
Assets 2
Vaadin 23 Portlet Support pre-release 2.1.0.beta1
Vaadin 23 Portlet Support pre-release 2.1.0.beta1 allows development of Portlet applications based on Vaadin 23.3+.
Changes:
- Update Vaadin license to "Vaadin Commercial License and Service Terms" (#241)
Vaadin 23 Portlet Support release 2.0.0
Vaadin 23 Portlet Support release 2.0.0 allows development of Portlet applications based on Vaadin 23.1+.
No user-facing changes since 2.0.0.rc1.
Vaadin 23 Portlet Support pre-release 2.0.0.rc1
Vaadin 23 Portlet Support pre-release 2.0.0.rc1 allows development of Portlet applications based on Vaadin 23.1+.
No user-facing changes since 2.0.0.beta1.
Vaadin 23 Portlet Support pre-release 2.0.0.beta1
Vaadin 23 Portlet Support pre-release 2.0.0.beta1 allows development of Portlet applications based on Vaadin 23.1+.
Limitations and known issues
- Vaadin Portlet add-on doesn't yet support Integration with OSGi.
Please vote for Integration with OSGi if you need it in your project and please leave a comment with description of your use cases, this will help us to understand what should be included in this feature. - Vaadin Push feature is not supported at the moment. As a workaround you can use client-to-server polling if it's an option for your project.
- Portlet's mode and state change through Portlet Hub API doesn’t work with Liferay, see the issue in Vaadin Portlet issue tracker for more details. As a workaround, one can use Liferay's "native" mode and state change menu options to change the rendering state of the portlet.
- Liferay's SPA feature needs to be disabled currently (https://help.liferay.com/hc/en-us/articles/360030752391-Disabling-SPA)
- Liferay 7.x uses JNA dependencies older than Vaadin uses, this causes a version conflict. Please follow deployment instructions to fix this.
Vaadin 23 Portlet Support pre-release 2.0.0.alpha1
Vaadin 23 Portlet Support pre-release 2.0.0.alpha1 allows development of Portlet applications based on Vaadin 23.1+.
Vaadin Portlet is built on top of the Portlet 3.0 Specification and provides an opportunity to build Portlet's UI in the same manner as for plain Vaadin 23+ applications.
Vaadin Portlet developed and tested with Liferay 7, but can be run in other portals supporting Portlet 3.0. Note that Apache Pluto container is not supported, because Pluto doesn't support JDK 7 yes, see this ticket.
Limitations and known issues
- Vaadin Portlet add-on doesn't yet support Integration with OSGi.
Please vote for Integration with OSGi if you need it in your project and please leave a comment with description of your use cases, this will help us to understand what should be included in this feature. - Vaadin Push feature is not supported at the moment. As a workaround you can use client-to-server polling if it's an option for your project.
- Portlet's mode and state change through Portlet Hub API doesn’t work with Liferay, see the issue in Vaadin Portlet issue tracker for more details. As a workaround, one can use Liferay's "native" mode and state change menu options to change the rendering state of the portlet.
- Liferay's SPA feature needs to be disabled currently (https://help.liferay.com/hc/en-us/articles/360030752391-Disabling-SPA)
- Liferay 7.x uses JNA dependencies older than Vaadin uses, this causes a version conflict. Please follow deployment instructions to fix this.
Vaadin 14 Portlet Support release 1.0.0
Vaadin 14 Portlet Support release 1.0.0 is a final release allowing development of Portlet applications based on Vaadin 14.
Vaadin 14 Portlet is built on top of the Portlet 3.0 Specification and provides an opportunity to build Portlet's UI in the same manner as for plain Vaadin 14 applications.
Vaadin 14 Portlet developed and tested with Liferay 7 and Apache Pluto Portal 3.1.0 (reference implementation for Portlet 3.0 API), but can be run in other portals supporting Portlet 3.0.
For more information please read documentation and try our starter project examples:
Limitations and known issues
- Vaadin 14 Portlet add-on doesn't yet support Integration with OSGi.
Please vote for Integration with OSGi if you need it in your project and please leave a comment with description of your use cases, this will help us to understand what should be included in this feature. - Vaadin Push feature is not supported at the moment. As a workaround you can use client-to-server polling if it's an option for your project.
- Portlet's mode and state change through Portlet Hub API doesn’t work with Liferay, see the issue in Vaadin Portlet issue tracker for more details. As a workaround, one can use Liferay's "native" mode and state change menu options to change the rendering state of the portlet.
- Liferay's SPA feature needs to be disabled currently (https://help.liferay.com/hc/en-us/articles/360030752391-Disabling-SPA)
- Liferay 7.x uses JNA dependencies older than Vaadin uses, this causes a version conflict. Please follow deployment instructions to fix this.
Vaadin 14 Portlet Support release 1.0.0.beta5
Vaadin 14 Portlet Support release 1.0.0.beta5 is a beta release allowing development of Portlet applications based on Vaadin 14.
Changes since 1.0.0.beta4
Fixes
-
Fix uploading on Pluto portlets (#207)(#190)
Do not send extra url that gets partially duplicated. Update Pluto to 3.1.1 for security fixes. -
Copy headers from StreamResource to VaadinResponse (#203)
Copy all headers set on a StreamResource to VaadinResponse before writing contents. -
Support absolute URLs in PortletStreamResourceRegistry
Resource URL from MimeResponse can be either an absolute (e.g. in Liferay) or a relative URL.
For absolute URLs, PortletStreamResourceRegistry does not need to alter URL after resourceID is set. -
Ensure necessary scripts are loaded into page (#210)(#202)
In Liferay "Content Page" edit mode, Vaadin portlets are not directly added to the main page, but loaded into an iframe requesting the same page in preview mode, and then added to the main page through javascript, but they are detached from iframe before initialization is completed. This way, scripts needed to register the portlet web component are not added to the main document, so the webcomponent is not correctly rendered. This patch add an additional script to BootstrapHandler response that takes care to add needed script to main page and to postpone element registration until they are loaded. -
Not write UIDL sync message when RPC handling throws (#215)(#213)
Liferay container is so strict regards ServletResponse::setContentLength comparing to normal servlet containers and Apache Pluto portal, thus the PortalUidlRequestHandler works incorrectly in case of exception in the server-side listener: it writes the error meta info JSON into response, then appends sync UIDL JSON message, then calls setContentLength with the length of the sync UIDL message. Which in turn leads to an unpredictable JSON sent to client.
When this change is applied, UidlRequestHandler doesn't write sync UIDL message to the response once the RPC handler execution throws, but instead sends only an error message to the client.
Vaadin 14 Portlet Support release 1.0.0.beta4
Vaadin 14 Portlet Support release 1.0.0.beta4 is a beta release allowing development of Portlet applications based on Vaadin 14.
Changes since 1.0.0.beta3
New features
-
Liferay 7.x support for plain portlets
Vaadin 14 Portlet add-on can now be used for creating a widgets/plugins for Liferay DXP 7.x containers. For more information on the changes made within this enhancement, see #196.
As an example how to build a Liferay plugin with Vaadin Portlet add-on please try the Portlet Address Book example project and use documentation.
Fixes
- Update override of VaadinContext::setAttribute to new signature (#173)
- Set container home to downloaded pluto to avoid triggering Tomcat download (#176)
- Fail server-side if trying to fire a hub event in Portlet 2.0 or older (#175)
Also corrected the Portlet 3.0 identification logic and a client bug reloading the Portlet Hub.
Limitations and known issues
- Vaadin Portlet add-on doesn't have an integration with OSGi features provided by Liferay (vaadin/flow#10939)
- Vaadin Push feature is not supported at the moment. As a workaround you can use client-to-server polling if it's an option for your project.
- Liferay's SPA feature needs to be disabled currently (https://help.liferay.com/hc/en-us/articles/360030752391-Disabling-SPA)
- Due to an issue in Vaadin Portlet release process, this and older versions use Flow and CDI add-on SNAPSHOT versions. Please use dependency exclusion as described here to avoid unexpected issues with version conflicts. Will be fixed in the further releases.
- Liferay 7.x uses JNA dependencies older than Vaadin uses, this causes an exception in Vaadin License Checker in dev mode. Please follow instructions in README to use proper versions in your Liferay bundle.