IBM Support

PM67019: REQUIREMENT TO INCLUDE 3RD PARTY JAR FILES WHEN DEPLOYING AXIS2 WEBSERVICES

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When deplying an Axis2 web service there is a requirement to
    reference an external jar file from repository/servicejars/lib
    
    The service cannot find the external jar and fails with a
    marshalling exception.
    

Local fix

  • Deploy the application in a single jar file.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS Users                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: When CICS V4.2 runs Axis2 Web Service,  *
    *                      the service cannot find the external    *
    *                      jars in repository/servicejars/lib      *
    *                      and fails with a marshalling            *
    *                      exception.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When deploying Axis2 web service, user places third party
    libraries into repository/servicejars/lib folder. But the
    libraries are not loaded from repository/servicejars/lib for
    jaxws services. When Axis2 web service is issued and tries
    to return an object of a third party class, it cannot find
    the external jars and fails with a marshalling exception.
    Keyword:JIRA 5011
    

Problem conclusion

  • Axis2 jars have been changed. JAXWSDeployer will check whether
    there's a 'lib' folder inside the provided folder and adds all
    the lib URLs into the provided URL list during jaxws deployment.
    PackageBuilderSet is also changed to allow that package names
    are used in the Jax-WS classess.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PM67019

  • Reported component name

    CICS TS Z/OS V4

  • Reported component ID

    5655S9700

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-06-18

  • Closed date

    2012-09-28

  • Last modified date

    2012-11-01

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UK82260

Modules/Macros

  •    DFJ@H294 DFJ@H295 DFJ@H296 DFJ@H297 DFJ@H298
    DFJ@H299 DFJ@H300 DFJ@H301 DFJ@H302 DFJ@H303 DFJ@H304 DFJ@H305
    DFJ@H306 DFJ@H307 DFJ@H308 DFJ@H309 DFJ@H310 DFJ@H311 DFJ@H312
    DFJ@H313 DFJ@H314 DFJ@H315
    

Fix information

  • Fixed component name

    CICS TS Z/OS V4

  • Fixed component ID

    5655S9700

Applicable component levels

  • R70D PSY UK82260

       UP12/10/08 P F210

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.2","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 November 2012