Jackrabbit Content Repository
  1. Jackrabbit Content Repository
  2. JCR-3241

Jackrabbit does not deploy on JBoss AS 7.1.0 Final

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.2.10
    • Fix Version/s: None
    • Component/s: jackrabbit-jca
    • Labels:
      None

      Description

      When deploying Jackrabbit JCA rar (resource adapter archive) on JBoss 7.1.0 final we have the following errors:
      Section: 19.4.2
      Description: A ResourceAdapter must implement a "public int hashCode()" method.
      Code: org.apache.jackrabbit.jca.JCAResourceAdapter

      Severity: ERROR
      Section: 19.4.2
      Description: A ResourceAdapter must implement a "public boolean equals(Object)" method.
      Code: org.apache.jackrabbit.jca.JCAResourceAdapter

      JBoss ironjacamar runs a validation sequence on the JCAResourceAdapter which seems to not conform to EE6 specifications.

      I tried with latest jackrabbit version and I have the same result.
      I need to use jackrabbit with JBoss 7.1.0 so this issue is kind of blocking.

        Activity

        Hide
        Marek Slama added a comment -

        FYI: I just tried to patch org.apache.jackrabbit.jca.JCAResourceAdapter to implement those 2 missing methods, delegating them to superclass (Object) and it seems to work fine. As workaround it seems ok. Anyway I have no idea what would be correct implementation of those 2 methods.

        I also had to change jndi name. JBoss 7.1 requires jndi name starts with java:/

        Show
        Marek Slama added a comment - FYI: I just tried to patch org.apache.jackrabbit.jca.JCAResourceAdapter to implement those 2 missing methods, delegating them to superclass (Object) and it seems to work fine. As workaround it seems ok. Anyway I have no idea what would be correct implementation of those 2 methods. I also had to change jndi name. JBoss 7.1 requires jndi name starts with java:/
        Hide
        Alex Parvulescu added a comment -

        If I understand correctly ironjacamar uses the 1.6 spec to validate the archives which is more strict that the 1.5 version.
        So apparently the temporary workaround is to disable archive validation within the JCA subsystem.

        I'll lower the priority as the workaround seems pretty common for other projects who ran into the same issue.

        Can you test Marek's solution and just add hashCode & equals and see if that is enough to get you going?

        Show
        Alex Parvulescu added a comment - If I understand correctly ironjacamar uses the 1.6 spec to validate the archives which is more strict that the 1.5 version. So apparently the temporary workaround is to disable archive validation within the JCA subsystem. I'll lower the priority as the workaround seems pretty common for other projects who ran into the same issue. Can you test Marek's solution and just add hashCode & equals and see if that is enough to get you going?

          People

          • Assignee:
            Unassigned
            Reporter:
            Claudiu Muresan
          • Votes:
            4 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:

              Development