summaryrefslogtreecommitdiffstats
path: root/osgi-integration
Commit message (Collapse)AuthorAgeFilesLines
* Update to 8.10-SNAPSHOT (#11657)Zhe Sun2019-07-291-1/+1
|
* OSGi: Removed static VaadinResourceService access in liferay-integration, ↵S.W2019-06-271-30/+85
| | | | | | | | osgi-integration (#11335) * Made VaadinResourceService a OSGi component, removed static access of OsgiVaadinResources
* Update to 8.9 (#11535)Sun Zhe2019-04-181-1/+1
| | | | | | * Update to 8.9-SNAPSHOT * update in bom module
* Update snapshot to 8.8-snapshot (#11397)Sun Zhe2018-12-281-1/+1
|
* Update master to 8.7-SNAPSHOT (#11208)Sun Zhe2018-09-271-1/+1
|
* Update project version to 8.6-SNAPSHOT (#11011)Mehdi Javan2018-06-291-1/+1
|
* Update snapshot version to 8.5 (#10818)Teemu Suo-Anttila2018-04-121-1/+1
|
* Update copyright year (#10761)Ilia Motornyi2018-03-271-1/+1
|
* Change log level for "VaadinServlet Registration" message from WARNING to ↵Ilia Motornyi2018-02-071-1/+1
| | | | INFO (#10613)
* Upgrade minor version in the project to 8.4 (#10520)Teemu Suo-Anttila2018-01-241-1/+1
|
* Update version number to 8.3-SNAPSHOT (#10348)Teemu Suo-Anttila2017-11-221-1/+1
|
* Update version to 8.2-SNAPSHOT (#9946)Teemu Suo-Anttila2017-09-081-1/+1
|
* Tidy up the Vaadin OSGi whiteboard component (#9648)Tim Ward2017-07-192-20/+20
| | | | | | | | | | | | The Vaadin OSGi integration component uses Declarative Services, but it does some odd things: * It uses the whiteboard service's own bundle context to get hold of the service instance * It has an asymmetric get/release for the whiteboard service, which could leak instances over time * It releases service instances that it is still actively using This change tidies up the service lifecycle by delegating the get/release to the Service Component Runtime managing the container (specifically by injecting the service instance). Using this injection also ensures that the Vaadin whiteboard service is obtained using this component's bundle context. This change also simplifies the code a little by using the reference as the key to track the registrations. Different references for the same service are required to be equal so there is no issue with doing this. This change does not alter the fact that the whiteboard service's bundle context is used to register the Http Whiteboard servlet, as this may be the intended behaviour. As a result the component should be prepared for an IllegalStateException when unregistering the service whiteboard service, which may already have been unregistered by the OSGi framework if the target bundle is stopping.
* Rename OSGi classes for Java naming conventions (#9320)Henri Sara2017-05-151-3/+3
| | | | | | - Rename OSGi to Osgi in class names. - Rename VaadinOSGiPortlet to OSGiVaadinPortlet for consistency with Spring, CDI etc. add-ons - Add missing javadoc
* Fix parent version in some POMsHenri Sara2017-04-251-1/+1
| | | Use the correct snapshot version of the parent.
* Add missing fields to OSGi manifestsHenri Sara2017-04-251-0/+2
| | | | Adds RequiredExecutionEnvironment and License fields and renames some bundles (SymbolicName) for backwards compatibility.
* Convenience API for registering themes and widgetsetsMirjan Merruko2017-04-251-3/+24
|
* Add scr component to help registering VaadinServlet configurationsMirjan Merruko2017-04-253-0/+240
This component will detect VaadinServlet configurations, add the static resource configuration property and then register a servlet using the HttpWhiteboard specification. This works with pax-jetty but not pax-http-tomcat. Partly covers #7173
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-24 03:26:34 +0000