Uploaded image for project: 'Wise'
  1. Wise
  2. WISE-202

Wrong Bus usage when relying on jbossws-cxf stack

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 2.0.2
    • 2.0, 2.0.1
    • core
    • None

      Currently Wise does not directly deal with Apache CXF Bus setup when invoking the jbossws-cxf tooling and when performing the actual jaxws client invocation. This has the side effect of letting the the wsconsume tooling code rely on the cxf default bus, which is both a scalability issue (every wsdl model piles up in the default bus, consuming more and more memory that is never released) and a logic problem (when different wsdl with the same url are consumed, perhaps because the corresponding endpoint has been updated).
      We need to create a new Bus instance when building the WSDynamicClient and associate it to the current thread during tool invocations; finally cleanup it when the client is destroyed.

            rhn-support-asoldano Alessio Soldano
            rhn-support-asoldano Alessio Soldano
            Archiver:
            rhn-support-adandapa Aitik Dandapat

              Created:
              Updated:
              Resolved:
              Archived: