I have one with a separate Activator class, same behaviour.
As I mentioned, with Apache Servicemix this kind of update works (same jar
files).
package de.ag.cas.eib.mapping.smx;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
import org.osgi.framework.BundleActivator;
import org.osgi.framework.BundleContext;
public class Activator implements BundleActivator {
private static final transient Log log =
LogFactory.getLog(Activator.class
.getName());
public void start(BundleContext context) throws Exception {
log.info("EIBMappingService started");
}
public void stop(BundleContext context) throws Exception {
log.info("EIBMappingService stopped");
}
}
> Jean-Baptiste Onofre <[email protected]> hat am 21.08.2020 14:43 geschrieben:
>
>
> Hi Gerald,
>
> Do you have to wrap ? I guess it works with "regular" bundle, right ?
>
> Regards
> JB
>
> > Le 21 août 2020 à 14:36, Gerald Kallas <[email protected]> a écrit :
> >
> > Dear all,
> >
> > I've a jar file that can be deployed with copying to the deploy folder. The
> > log shows
> >
> > 2020-08-21T08:51:19,931 | INFO |
> > fileinstall-/opt/apache-karaf-4.2.9/deploy | fileinstall
> > | 10 - org.apache.felix.fileinstall - 3.6.6 | Installing bundle
> > sfo-account-mapping / 0.0.1.SNAPSHOT
> > 2020-08-21T08:51:20,105 | INFO |
> > fileinstall-/opt/apache-karaf-4.2.9/deploy | fileinstall
> > | 10 - org.apache.felix.fileinstall - 3.6.6 | Started bundle:
> > wrap:file:/opt/apache-karaf-4.2.9/deploy/sfo-account-mapping-0.0.1-SNAPSHOT.jar$Bundle-SymbolicName=sfo-account-mapping&Bundle-Version=0.0.1.SNAPSHOT
> >
> > When I'm going to copy a new version of this jar the bundle is not being
> > updated.
> >
> > I know this from Servicemix that even a new copy updates the bundle. Do I
> > need to configure anything special in Karaf?
> >
> > Best
> > Gerald
