Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-10152

IronJacamar isn't compatible with picketbox version used in WildFly

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.1.0.DR18
    • 7.1.0.DR15, 7.1.0.DR17
    • Build System, JCA
    • None

    Description

      Ironjacamar is compiled with Picketbox 4.0.19.Final and WildFly comes with 5.0.1.Final. These versions are not binary compatible, I'm getting

      Caused by: java.lang.NoSuchMethodError: org.jboss.security.identity.RoleGroup.getRoles()Ljava/util/List;
        at org.jboss.jca.core.security.picketbox.PicketBoxSecurityContext.getRoles(PicketBoxSecurityContext.java:76)
        at org.jboss.as.test.integration.jca.security.WildFlyActivationRaWithSecurityDomainWorkManagerSecurityDomainTestCase$MyWork.run(WildFlyActivationRaWithSecurityDomainWorkManagerSecurityDomainTestCase.java:304)
        at org.jboss.jca.core.workmanager.WorkWrapper.run(WorkWrapper.java:223)
        ... 6 more

      signature changed in this case from List<Role> getRoles() to Collection<Role> getRoles()

      I tried to compile IJ with 5.0.1 and my test then works.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBJCA-1346 IronJacamar isn't compatible with picketbox version used in WildFly

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is related to

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-10418 IronJacamar to 1.4.4 from 1.4.3

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

              psakar@redhat.com Petr Sakar (Inactive)
              msimka@redhat.com Martin Simka
              Martin Simka Martin Simka
              Martin Simka Martin Simka
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: