Announcement Announcement Module
Collapse
No announcement yet.
What's the best way to install Libraries on springsource-dm-server-2.0.0.RELEASE Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • What's the best way to install Libraries on springsource-dm-server-2.0.0.RELEASE

    My Bundle MANIFEST.MF has Import-Library element to import "org.hibernate.ejb;version="3.4.0.GA""

    and this library is not available in my DM Server installation.

    What's the best way to install Library on DM Server.

    Is there any documentation on it?

  • #2
    You can download libraries and the bundles they refer to from the Enterprise Bundle Repository (EBR).

    For example, a search for "hibernate" shows the corresponding libraries at various versions. Each of these provides the library definition file, Ivy and Maven build snippets, a manifest header example, and a list of bundles (each with its own page).

    If you find this way of downloading too laborious, you can use one of the STS dm Server tool panels to download artifacts from the EBR.

    Comment


    • #3
      Thanks Glyn. Thanks for the reply.

      I think I am running into more trouble with Libraries.

      1) Through Eclipse Plugin i can configure only version 1 of DM Server and it doesn't support version2.

      to download "hibernate" related library bundles i have installed version 1 of DM Server and configured it through eclipse. but even after downloading the Hibernate Library it won't be listed under the list of installed libraries and there is no error message.

      I went back to version 2.0 of DM Server and downloaded all the dependencies one after the other. Dependencies contain two fragments and they can't be installed into DM Server.

      com.springsource.org.hibernate.annotations-3.4.0.GA
      com.springsource.org.hibernate.ejb-3.4.0.GA

      Error message is

      Unable to satisfy dependencies of bundle "com.springsource.org.hibernate.ejb-3.4.0.GA". The fragment could not be resolved because of a constraint conflict with host.

      and the class org.springframework.orm.jpa.vendor.HibernateJpaVen dorAdapter is within this fragment.

      Any idea how to go ahead?

      Comment


      • #4
        Please would you start a thread on the dm Server tooling forum in relation to the STS/dm Server tools problems you are seeing. It may be that you are not running the latest levels.

        As for the resolution problem: it looks odd. Were there any more diagnostics to indicate what the constraint conflict was? If not, please could you reduce the problem to a small set of bundles and, if you haven't figured out what's wrong during that process, raise a JIRA with steps to reproduce and attach your binary application bundles and list all the dependencies you have placed in the repository so we can look into it.

        Comment


        • #5
          Thanks Glyn.

          I have changed my development environment from Eclipse-jee-galileo to spring source tool suite 2.3.0 RELEASE.

          This allowed me to download Hibernate Libraries and pont to a DM Server version 2.0.0 RELEASE.

          I am still having issues with deploying my Bundle.

          In thus bundle I am registering HibernateJpaVendorAdapter as a service.

          Error I am getting is :

          [2010-02-08 13:33:48.982] http-8080-2 <DE0002E> Installation of bundle 'MyVendorAdapter' version '1.0.0' failed. com.springsource.kernel.osgi.framework.UnableToSat isfyBundleDependenciesException: Unable to satisfy dependencies of bundle 'MyVendorAdapter' at version '1.0.0': Cannot resolve: MyVendorAdapter
          Resolver report:
          Uses violation: <Import-Package: org.springframework.orm.jpa; version="0.0.0"> in bundle <MyVendorAdapter_1.0.0>
          Resolver reported uses conflict for import constrained to bundle <org.springframework.orm> constrained bundle version range "[3.0.0.RELEASE,3.0.0.RELEASE]"

          See the attached file for more info.


          My Manifest File is

          Manifest-Version: 1.0
          Bundle-Version: 1.0.0
          Bundle-Name: MyVendorAdapter
          Bundle-ManifestVersion: 2
          Bundle-SymbolicName: MyVendorAdapter
          Import-Library: org.hibernate.ejb;version="[3.3.2.GA,3.3.2.GA]",
          org.springframework.spring;version="[3.0.0.RELEASE,3.0.0.RELEASE]"

          Configuration Files Are:

          <?xml version="1.0" encoding="UTF-8"?>
          <beans xmlns="http://www.springframework.org/schema/beans"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd">

          <bean id="hibernateJpaVendorAdapter" class="org.springframework.orm.jpa.vendor.Hibernat eJpaVendorAdapter">
          <property name="generateDdl" value="true"/>
          <property name="showSql" value="true"/>
          </bean>

          </beans>


          <?xml version="1.0" encoding="UTF-8"?>
          <beans xmlns="http://www.springframework.org/schema/beans"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xmlns:osgi="http://www.springframework.org/schema/osgi"
          xsi:schemaLocation="http://www.springframework.org/schema/osgi http://www.springframework.org/schem...sgi-2.0-m1.xsd
          http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd">

          <osgi:service ref="hibernateJpaVendorAdapter" interface="org.springframework.orm.jpa.JpaVendorAd apter"/>
          </beans>

          Any thoughts?

          Comment


          • #6
            The easiest way to analyse uses constraint violations is to open up the state dump generated by dm Server in the admin console and then look at the importers and exporters of the relevant package, in this case org.springframework.orm.jpa, to see what uses constraints may be broken. We have posted a few blogs on this topic which should get you going.

            Comment


            • #7
              Tried different approach to solve this.

              Instead of installing all the dependencies of Hibernate Library i installed minimum dependencies needed for my application and this solved the issue.

              Comment

              Working...
              X