Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-16088

NoSuchMethodError handling SOAP request

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • 26.0.1.Final
    • Web Services
    • None
    • Hide

      These is within a large enterprise application and there is no easy way to create a reproducible test case. 

      Show
      These is within a large enterprise application and there is no easy way to create a reproducible test case. 

    Description

      Calling a SOAP method ultimately causes a NoSuchMethodError. The stack trace is entirely within WildFly, CXF and JAXB (all included with WildFly).

      Caused by: java.lang.NoSuchMethodError: 'void jakarta.xml.bind.JAXBElement.<init>(java.lang.Object, java.lang.Object, java.lang.Object, java.lang.Object)'
          at jakarta.xml.bind.JAXBElementFactory.createJAXBElement(JAXBElementFactory.java)

      It does manage to successfully call two SOAP handlers that we provide (LogHandler and AuthHandler), but goes on to fail in the CXF DocLiteralInInterceptor when trying to unmarshall something.

      The actual error doesn't make a lot of sense for these reasons:

      1. The class JAXBElementFactory doesn't seem to exist anywhere (is this generated bytecode?)
      2. The method it can't find actually does exist (except it's a constructor, and the type arguments are more specific).

       

      Attachments

        Activity

          People

            rhn-engineering-ema Jim Ma
            alexslackx3 Alex Slack (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: