OpenJPA
  1. OpenJPA
  2. OPENJPA-1478

OpenJPA is no longer available as an OSGi bundle

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.0-M3
    • Fix Version/s: 1.3.0, 2.0.0-beta
    • Component/s: integration
    • Labels:
      None
    • Environment:
      OSGi

      Description

      The Apache Aries project is building an OSGi based application container that includes container JPA integration.

      OpenJPA 2.0.0-M3 was available as an OSGi bundle, but is using an old version of the JPA 2.0 API (ValidationMode is in the wrong package), and so throws NoSuchMethodError on calls to createContainerEntityManagerFactory. Unfortunately, the latest build snapshots of 2.0.0 are no longer OSGi bundles, which means that OpenJPA can no longer be used with Aries.

      I have two questions:

      Why is OpenJPA no longer available as an OSGi bundle?

      Will OpenJPA be available as an OSGi bundle in future, or should the Aries project re-package OpenJPA for use in the Aries container?

      For use with Aries it would also be ideal if the OpenJPA bundle registered the OpenJPA PersistenceProviderImpl as a service in the OSGi service registry, adding the implementation class name as a service property with the key "javax.persistence.provider".

      I would be happy to provide any assistance I can in re-enabling this functionality.

        Activity

        Hide
        Rick McGuire added a comment -

        Geronimo has a similar requirement for its 3.0 release. We can repackage this if necessary, but a better solution would be to have the bundle manifest entries directly enabled in openjpa.

        Show
        Rick McGuire added a comment - Geronimo has a similar requirement for its 3.0 release. We can repackage this if necessary, but a better solution would be to have the bundle manifest entries directly enabled in openjpa.
        Hide
        Donald Woods added a comment -

        The plan was to create a openjpa-osgi artifact that includes the OSGi metadata and RFC 143 code, so we have a competitive offering to Eclipselink.... I'll try to get the openjpa artifact updated today before I cut the Beta branch, but long-term, we need a better solution than creating a jar that is not OSGi complete.

        Show
        Donald Woods added a comment - The plan was to create a openjpa-osgi artifact that includes the OSGi metadata and RFC 143 code, so we have a competitive offering to Eclipselink.... I'll try to get the openjpa artifact updated today before I cut the Beta branch, but long-term, we need a better solution than creating a jar that is not OSGi complete.
        Hide
        Donald Woods added a comment -

        fixed in trunk for beta as r902169
        fixed in 1.3.x branch as r902170

        Show
        Donald Woods added a comment - fixed in trunk for beta as r902169 fixed in 1.3.x branch as r902170

          People

          • Assignee:
            Donald Woods
            Reporter:
            Timothy Ward
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development