org.osgi.framework.BundleException

The bundle could not be resolved. Reason: Missing Constraint: Import-Package: javax.servlet.jsp; version="0.0.0"

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web6412

  • via Google Groups by Gregg, 6 months ago
    The bundle could not be resolved. Reason: Missing Constraint: Import-Package: javax.servlet.jsp; version="0.0.0"
  • The bundle "com.subgraph.vega.scanner_1.0.0.201410142137 [12]" could not be resolved. Reason: Missing Constraint: Import-Package: com.subgraph.vega.sslprobe; version="0.0.0"
  • via Google Groups by Stu Beans, 1 year ago
    The bundle "com.subgraph.vega.scanner_1.0.0.201410142137 [12]" could not be resolved. Reason: Missing Constraint: Import-Package: com.subgraph.vega.sslprobe; version="0.0.0"
  • Stack trace

    • org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Import-Package: javax.servlet.jsp; version="0.0.0" at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1313) at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1297) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:309) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:280) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:272) at org.openanzo.osgi.dirwatcher.DirectoryWatcher.startBundles(DirectoryWatcher.java:160) at org.openanzo.osgi.dirwatcher.DirwatcherActivator.start(DirwatcherActivator.java:75) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:782) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:773) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:754) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:352) at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:370) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1068) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:557) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:464) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:248) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:445) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    6 times, 1 year ago
    2 times, 1 week ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    1 more bugmates