IBM Support

PI64053: WSWS7054E IS THROWN WHEN DEPLOYING A JAX-WS WEB SERVICE APPLICATION

Fixes are available

9.0.0.1: WebSphere Application Server traditional V9.0 Fix Pack 1
9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
9.0.5.6: WebSphere Application Server traditional Version 9.0.5 Fix Pack 6

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The following NoClassDefFoundError is generated during the
    deployment of the web service application:
    
    [4/4/16 12:36:22:414 JST] 00000087 WSModuleDescr E   WSWS7027E:
    JAX-WS Service Descriptions could not be correctly built
    because of the following error:
    javax.xml.ws.WebServiceException: WSWS7054E: The Web
    Services Description Language (WSDL) file could not be
    generated for the sample.TestService Web service implementation
    class because of the following error:
    java.lang.NoClassDefFoundError: javax.el.ELResolver
    at com.ibm.ws.websvcs.wsdl.WASWSDLGenerator
        .generateWsdl(WASWSDLGen erator.java:267)
    at org.apache.axis2.jaxws.description.impl
         .EndpointDescriptionImpl
        .generateWSDL(EndpointDescriptionImpl.java:2084)
    at org.apache.axis2.jaxws.description.impl
          .EndpointDescriptionImpl
          .<init>(EndpointDescriptionImpl.java:434)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server users of   *
    *                  JAX-WS web service applications             *
    ****************************************************************
    * PROBLEM DESCRIPTION: WSWS7054E was thrown when deploying a   *
    *                      JAX-WS web service application          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When deploying a JAX-WS web service application without a
    WSDL packaged, if the application uses a Java EL API in its
    web service implementation, the following error will be
    reported:
    [4/4/16 12:36:22:414 JST] 00000087 WSModuleDescr E
    WSWS7027E: JAX-WS Service Descriptions could not be correctly
    built because of the following error:
    javax.xml.ws.WebServiceException: WSWS7054E: The Web Services
    Description Language (WSDL) file could not be generated for
    the sample.TestService Web service implementation class
    because of the following error:
    java.lang.NoClassDefFoundError: javax.el.ELResolver
    at
    com.ibm.ws.websvcs.wsdl.WASWSDLGenerator.generateWsdl(WASWSDLGen
    erator.java:267)
    at
    org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.
    generateWSDL(EndpointDescriptionImpl.java:2084)
    at
    org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.
    <init>(EndpointDescriptionImpl.java:434)
    at
    org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.<
    init>(ServiceDescriptionImpl.java:401)
    at
    org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.<
    init>(ServiceDescriptionImpl.java:297)
    at
    org.apache.axis2.jaxws.description.impl.DescriptionFactoryImpl.c
    reateServiceDescriptionFromDBCMap(DescriptionFactoryImpl.java:27
    7)
    at
    org.apache.axis2.jaxws.description.DescriptionFactory.createServ
    iceDescriptionFromDBCMap(DescriptionFactory.java:524)
    at
    com.ibm.ws.websvcs.desc.WSModuleDescriptorImpl.buildJAXWSService
    s(WSModuleDescriptorImpl.java:1389)
    at
    com.ibm.ws.websvcs.desc.WSModuleDescriptorImpl._containsJAXWSWeb
    Services(WSModuleDescriptorImpl.java:550)
    at
    com.ibm.ws.websvcs.desc.WSModuleDescriptorImpl.containsJAXWSWebS
    ervices(WSModuleDescriptorImpl.java:525)
    at
    com.ibm.ws.webservices.admin.utils.ServiceContainmentHelper.<ini
    t>(ServiceContainmentHelper.java:71)
    at
    com.ibm.ws.webservices.admin.utils.CommonUtils.getServiceContian
    mentHelper(CommonUtils.java:690)
    at
    com.ibm.ws.webservices.admin.utils.CommonUtils.hasWebServices(Co
    mmonUtils.java:295)
    at
    com.ibm.ws.webservices.admin.utils.CommonUtils.hasJAXWSWebServic
    es(CommonUtils.java:238)
    at
    com.ibm.ws.webservices.admin.deploy.DeploymentValidation.getWebS
    erviceType(DeploymentValidation.java:309)
    at
    com.ibm.ws.webservices.admin.deploy.DeploymentValidation.validat
    eEarModules(DeploymentValidation.java:381)
    at
    com.ibm.ws.webservices.admin.deploy.DeploymentValidation.validat
    eOperation_Required(DeploymentValidation.java:204)
    at
    com.ibm.ws.management.application.task.ValidateAppTask.performTa
    sk(ValidateAppTask.java:433)
    at
    com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImp
    l.java:315)
    at java.lang.Thread.run(Thread.java:798)
    Caused by: java.lang.NoClassDefFoundError: javax.el.ELResolver
    at java.lang.ClassLoader.defineClassImpl(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:324)
    at
    java.security.SecureClassLoader.defineClass(SecureClassLoader.ja
    va:155)
    at java.net.URLClassLoader.defineClass(URLClassLoader.java:712)
    at java.net.URLClassLoader.access$400(URLClassLoader.java:93)
    at
    java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1164
    )
    at
    java.security.AccessController.doPrivileged(AccessController.jav
    a:456)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:595)
    at java.lang.ClassLoader.loadClassHelper(ClassLoader.java:777)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:750)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:731)
    at
    com.ibm.jtc.jax.tools.ws.wscompile.WsgenOptions.getClass(WsgenOp
    tions.java:305)
    at
    com.ibm.jtc.jax.tools.ws.wscompile.WsgenOptions.validateEndpoint
    Class(WsgenOptions.java:244)
    at
    com.ibm.jtc.jax.tools.ws.wscompile.WsgenOptions.validate(WsgenOp
    tions.java:235)
    at
    com.ibm.jtc.jax.tools.ws.wscompile.WsgenTool.run(WsgenTool.java:
    134)
    at
    com.ibm.jtc.jax.tools.ws.util.WSToolsObjectFactoryImpl.wsgen(WST
    oolsObjectFactoryImpl.java:66)
    at
    com.ibm.jtc.jax.tools.ws.spi.WSToolsObjectFactory.wsgen(WSToolsO
    bjectFactory.java:112)
    at
    com.ibm.ws.websvcs.wsdl.WASWSDLGenerator.wsgen(WASWSDLGenerator.
    java:607)
    at
    com.ibm.ws.websvcs.wsdl.WASWSDLGenerator.generateWsdl(WASWSDLGen
    erator.java:244)
    ... 19 more
    Caused by: java.lang.ClassNotFoundException:
    javax.el.ELResolver
    at java.net.URLClassLoader.findClass(URLClassLoader.java:600)
    at java.lang.ClassLoader.loadClassHelper(ClassLoader.java:777)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:750)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:731)
    ... 38 more
    

Problem conclusion

  • When deploying a JAX-WS web service application which uses
    the Java EL API, the JAX-WS runtime failed to generate the
    WSDL file because there was no Java EL library in the
    classpath.
    
    The JAX-WS runtime is changed to include the necessary Java EL
    library in the classpath while generating a WSDL file for the
    web service application.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack s8.5.5.11 and 9.0.0.2.  Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI64053

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-06-13

  • Closed date

    2016-06-29

  • Last modified date

    2016-09-07

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

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

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R850 PSY

       UP

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
17 October 2021