vaadin-framework

19188 Commits

Branch: master

Author	SHA1	Message	Date
Anna Koskinen	cb232f2bff	Update copyright year range (#12507)	2 years ago
Anna Koskinen	32764eca80	Update copyright year range. (#12215) * Update copyright year range.	3 years ago
S.W	583920f327	OSGi: Removed static VaadinResourceService access in liferay-integration, osgi-integration (#11335) * Made VaadinResourceService a OSGi component, removed static access of OsgiVaadinResources	4 years ago
Ilia Motornyi	6541b7bad2	Update copyright year (#10761)	6 years ago
Ilia Motornyi	ece60ca12e	Change log level for "VaadinServlet Registration" message from WARNING to INFO (#10613)	6 years ago
Tim Ward	a108a7e8da	Tidy up the Vaadin OSGi whiteboard component (#9648) 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.	6 years ago
Henri Sara	e788fa906b	Rename OSGi classes for Java naming conventions (#9320) - Rename OSGi to Osgi in class names. - Rename VaadinOSGiPortlet to OSGiVaadinPortlet for consistency with Spring, CDI etc. add-ons - Add missing javadoc	7 years ago
Mirjan Merruko	5308eb76f4	Convenience API for registering themes and widgetsets	7 years ago
Mirjan Merruko	de7a16aee8	Add scr component to help registering VaadinServlet configurations 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	7 years ago

9 Commits (master)