Eclipse activator for bundle is invalid

Bundle-Activator: com. NewActivator Import-Package: com. BundleActivator; import org. Powered by FUDForum. Page generated in 0. Sign up to our Newsletter A fresh new issue delivered monthly. Eclipse Community Forums. Forum Search:.

BundleException: Activator for bundle is invalid, but everything appears to be in place. Mon, 03 June Erwin Hogeweg Messages: 37 Registered: July I had the same error, in my case I created my own constructor with parameters.

But I didn't provide a default constructor. So after removing my constructor and initialized all within the start method, it worked like charme. I have also run into this isue when 'bundle-izing' plain jar files. If some dependencies are not resolved, or jars depend on a higher JAVA version than the one you're using, the activator will not start, giving the above exception.

The quick way to find out if this is the problem is to remove the jars from the bundle-classpath runtime tab of the manifest and check if the activator will run correctly. In my case there was this Message "Activator.. OK, I hate to be captain obvious here, but I've made this mistake before. This can also happen when you forget to extend BundleActivator.

To deploy a bundle to the remote target device, you will need to connect Eclipse to the OSGi framework running on the device. This is done using mToolkit. See Kura Setup for instructions on installing mToolkit into the Eclipse development environment. The remote target device must have port open in its firewall, in order to allow mToolkit o make a connection to its OSGi framework.

Right-click the framework icon name and select Connect Framework. The list of installed bundles and deployment packages should be retrieved shortly. Use the Disconnect Framework option to disconnect from the remote target framework when finished. In order to allow mToolkit to make a remote connection to the OSGi framework on the target device, the device must allow the incoming port in its firewall.

To set this option, open a Web browser and log into Kura using its current IP address, such as:. Click the Firewall icon and then click the Open Ports tab. If port is not shown in the list of allowed ports, click the New button under Open Ports. Enter the port and select protocol TCP. Then click Submit. Now, click Apply to apply changes to the remote device. Even if I change the name of the Activator class to something else, it's still giving me the exact same error using the old class name.

Apparently eclipse is caching something, but I have no idea what or why. I've tried restarting eclipse, and rebuilding all projects in my workspace, but nothing helps.

As you can see I renamed the activator class, but it's still reporting the error using the class name that I specified previously. I experienced this problem after renaming the package of my Activator class.

MF but not in the plugin. In my case the plugin. Eclipse caches really something! Go to your launch configuration and open the Settings tab. Choose the option Clear the configuration area before launching and try to run again your OSGi application! Is there no chained exception?

One reason is that your bundle does not import org. So the class load of your activator fails since your bundle class loader cannot load org. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams?