Hi Ray, I read the app note but I need some clarification. Couple of questions:
1. In Liferay, we hot deploy bundles to the deploy folder in
Wildfly/Jboss container or appserver using the gradle build script provided by
liferay. I thought we could do the same on the liberty server since
On Sun, Dec 10, 2017 at 11:45 AM, Konrad Windszus wrote:
> Hi Ray,
> thanks for confirming. So the relation between bundle life cycle and
> component lifecycle is clear now.
> The only remaining question is now:
>
> Is it valid to assume that once a DS component is registered,
Hi Ray,
thanks for confirming. So the relation between bundle life cycle and component
lifecycle is clear now.
The only remaining question is now:
> Is it valid to assume that once a DS component is registered, the services
> which are implemented by this component are registered as well or
Compendium Section 112.5.1 states:
> A component must first be enabled before it can be used. A component
cannot be enabled unless the
> component's bundle is started. See Starting Bundles in OSGi Core Release
6. All components in a bun-
> dle become disabled when the bundle is stopped.
Core
And one more related question:
Is it valid to assume that once a DS component is registered, the services
which are implemented by this component are registered as well or does it
happen only afterwards?
> On 10. Dec 2017, at 11:52, Konrad Windszus via osgi-dev
>
Hi,
I have a question about the component life cycle of DS components and the
relation to the containing bundle's life cycle.
According to OSGi Comp R6, 112.5.1 "the life cycle of a component is contained
within the life cycle of its bundle". But is it a valid assumption that all
enabled