org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Mi ssing Constraint: Require-Bundle: org.eclipse.wst.xml.core; bundle-version="0.0. 0"

Hibernate JIRA | Timur Shakirov | 9 years ago
  1. 0

    I tried to use Hibernate-Tools with the Eclipse 3.3.1. I downloaded the current release of Eclipse 3.3.1.1 and installed Hibernate-Tools 3.2.0.GA. After starting Eclipse I noticed that no Eclipse-Views of Hibernate-Tools are available, but the Hibernate plugin is visible under the 'Product Configuration' window. This is exactly the same problem as it was reported in the issue HBX-960 (and even reported as closed in 3.2beta10). The only difference is that I use now EclipseTools version 3.2.0 GA from JBossTools 2.0.0.GA (2007-12-10 23:33) and Eclipse 3.3.1.1 This is the output of the osgi console: -----------------8<---------------------------- osgi> start org.hibernate.eclipse.mapper org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Mi ssing Constraint: Require-Bundle: org.eclipse.wst.xml.core; bundle-version="0.0. 0" at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(Bundl eHost.java:305) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac tBundle.java:260) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac tBundle.java:252) at org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._st art(FrameworkCommandProvider.java:260) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter. execute(FrameworkCommandInterpreter.java:150) at org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(F rameworkConsole.java:291) at org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(Fra meworkConsole.java:276) at org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(Framewo rkConsole.java:218) at java.lang.Thread.run(Unknown Source) osgi> -----------------8<---------------------------- Should I still have WTP package installed to use HibernateTools on Eclipse?

    Hibernate JIRA | 9 years ago | Timur Shakirov
    org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Mi ssing Constraint: Require-Bundle: org.eclipse.wst.xml.core; bundle-version="0.0. 0"
  2. 0

    I tried to use Hibernate-Tools with the Eclipse 3.3.1. I downloaded the current release of Eclipse 3.3.1.1 and installed Hibernate-Tools 3.2.0.GA. After starting Eclipse I noticed that no Eclipse-Views of Hibernate-Tools are available, but the Hibernate plugin is visible under the 'Product Configuration' window. This is exactly the same problem as it was reported in the issue HBX-960 (and even reported as closed in 3.2beta10). The only difference is that I use now EclipseTools version 3.2.0 GA from JBossTools 2.0.0.GA (2007-12-10 23:33) and Eclipse 3.3.1.1 This is the output of the osgi console: -----------------8<---------------------------- osgi> start org.hibernate.eclipse.mapper org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Mi ssing Constraint: Require-Bundle: org.eclipse.wst.xml.core; bundle-version="0.0. 0" at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(Bundl eHost.java:305) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac tBundle.java:260) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac tBundle.java:252) at org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._st art(FrameworkCommandProvider.java:260) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter. execute(FrameworkCommandInterpreter.java:150) at org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(F rameworkConsole.java:291) at org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(Fra meworkConsole.java:276) at org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(Framewo rkConsole.java:218) at java.lang.Thread.run(Unknown Source) osgi> -----------------8<---------------------------- Should I still have WTP package installed to use HibernateTools on Eclipse?

    Hibernate JIRA | 9 years ago | Timur Shakirov
    org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Mi ssing Constraint: Require-Bundle: org.eclipse.wst.xml.core; bundle-version="0.0. 0"
  3. 0

    Using slf4j with jdk1.4

    Google Groups | 9 years ago | amacg
    org.osgi.framework.BundleException: The activator org.springframework.osgi.extender.internal.ContextLoaderListener for bundle org.springframework.osgi.bundle.extender is invalid
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Spring 2.5 + OSGi, stuck at apache-commons, Help!

    Google Groups | 9 years ago | Hendy Irawan
    org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Import-Package: org.apache.commons.logging; version="0.0.0"
  6. 0

    Spring and OSGi Classloader issue... java.lang.ClassCastException: help :)

    Google Groups | 9 years ago | Hendy Irawan
    org.osgi.framework.BundleException: Exception in com.x.client.swing.App.start() of bundle com.x.client.swing.

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. org.osgi.framework.BundleException

      The bundle could not be resolved. Reason: Mi ssing Constraint: Require-Bundle: org.eclipse.wst.xml.core; bundle-version="0.0. 0"

      at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker()
    2. Eclipse OSGi
      FrameworkCommandProvider._start
      1. org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:305)
      2. org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:260)
      3. org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:252)
      4. org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._start(FrameworkCommandProvider.java:260)
      4 frames
    3. Java RT
      Method.invoke
      1. sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      2. sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
      3. sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      4. java.lang.reflect.Method.invoke(Unknown Source)
      4 frames
    4. Eclipse OSGi
      FrameworkConsole.run
      1. org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.execute(FrameworkCommandInterpreter.java:150)
      2. org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(FrameworkConsole.java:291)
      3. org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(FrameworkConsole.java:276)
      4. org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(FrameworkConsole.java:218)
      4 frames
    5. Java RT
      Thread.run
      1. java.lang.Thread.run(Unknown Source)
      1 frame