-
Bug
-
Resolution: Done
-
Major
-
fuse-7.6-GA, fuse-7.8-GA
-
None
-
False
-
False
-
%
-
-
+
-
Automated
-
undefined
-
camel-fhir bundles going to installed state after karaf restart
when the karaf is started and feature is installed for the first time, all bundles go to 'Resolved' state as below :
272 | Active | 50 | 3.5.0 | HAPI FHIR - Core Library, Fragments: 273
273 | Resolved | 50 | 3.5.0 | HAPI FHIR - Client Framework, Hosts: 272
274 | Resolved | 50 | 3.5.0 | HAPI FHIR Structures - DSTU2 (FHIR v1.0.0)
275 | Resolved | 50 | 3.5.0 | HAPI FHIR Structures - DSTU3
276 | Active | 50 | 3.5.0 | HAPI FHIR - Utilities
277 | Active | 50 | 2.8.2 | Gson
278 | Active | 50 | 25.0.0.jre | Guava: Google Core Libraries for Java
279 | Active | 50 | 2.21.0.fuse-760027-redhat-00001 | camel-fhir
280 | Active | 50 | 2.21.0.fuse-760027-redhat-00001 | camel-fhir-api
when the karaf is restarted, it again goes in 'Installed' state
273 | Resolved | 50 | 3.5.0 | HAPI FHIR - Client Framework, Hosts: 272
274 | Installed | 50 | 3.5.0 | HAPI FHIR Structures - DSTU2 (FHIR v1.0.0)
275 | Installed | 50 | 3.5.0 | HAPI FHIR Structures - DSTU3
276 | Active | 50 | 3.5.0 | HAPI FHIR - Utilities
277 | Active | 50 | 2.8.2 | Gson
278 | Active | 50 | 25.0.0.jre | Guava: Google Core Libraries for Java
279 | Active | 50 | 2.21.0.fuse-760027-redhat-00001 | camel-fhir
280 | Active | 50 | 2.21.0.fuse-760027-redhat-00001 | camel-fhir-api
- is related to
-
ENTESB-16766 Installing feature causes "Resolved" bundles to activate unexpectedly
-
- Closed
-