Details
-
Bug
-
Status: Resolved
-
Resolution: Won't Do
-
None
-
None
-
None
-
Operating System: Linux
Platform: PC
-
778
Description
How to reproduce:
1. Create simple bundle extended from org.opendaylight.controller.sal.binding.api.AbstractBindingAwareConsumer
2. Use some class in Activator declaration which doesn't exist in ODL and mark it as resolution:=optional in MANIFEST.MF . For example, I made 'Activator implements SomeInterface' from other bundle which haven't been loaded in ODL. In MANIFEST.MF it was mentioned as 'Import-Package: some.package.SomeInterface;resolution:=optional'
3. Run without some.package.SomeInterface loaded into the ODL.
Expected:
1. BundleException with stack trace identifying the issue
2. BundleException with stack trace recorded into opendaylight.log
Got:
1. stdout: 'BundleException: The activator is invalid'
2. no stack trace
3. no corresponding log record in opendaylight.log
Workaround:
Connect with a debugger, read stack trace.
Version:
org.opendaylight.controller.version = 0.1
org.opendaylight.controller.build.scm.version = b43cbaf25e664bff8b211d13018d7487e5235a90
org.opendaylight.controller.build.user = jenkins-controller
org.opendaylight.controller.build.workspace = **********
org.opendaylight.controller.build.timestamp = 1397752540201
org.opendaylight.controller.build.machine = **********