IBM Support

PM94514: SCA PROJECT VALIDATION THROWS NOCLASSDEFFOUNDERROR.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • NoClasDefFoundError in Rational Application Developer for
    validating SCA soap over jms binding.
    

Local fix

  • Candidate to be fixed in next release.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: NoClasDefFoundError in Rational         *
    *                      Application Developer when validating   *
    *                      SCA Web Service SOAP over JMS binding.  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    NoClasDefFoundError in Rational Application Developer tool
    when validating SCA Web Service soap over jms binding.
    Stacktrace:
    java.lang.NoClassDefFoundError:
    com.ibm.ws.webservices.engine.transport.jms.JMSURLParser
    at
    org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProcessor
    .getDestinationName(WebServiceBindingProcessor.java:372)
    at
    org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProcessor
    .read(WebServiceBindingProcessor.java:290)
    at
    org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProcessor
    .read(WebServiceBindingProcessor.java:107)
    at
    org.apache.tuscany.sca.contribution.processor.DefaultStAXArtifac
    tProcessorExtensionPoint$LazyStAXArtifactProcessor.read(DefaultS
    tAXArtifactProcessorExtensionPoint.java:387)
    at
    org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArti
    factProcessor.read(ExtensibleStAXArtifactProcessor.java:152)
    at
    org.apache.tuscany.sca.assembly.xml.CompositeProcessor.read(Comp
    ositeProcessor.java:463)
    at
    org.apache.tuscany.sca.assembly.xml.CompositeProcessor.read(Comp
    ositeProcessor.java:90)
    at
    org.apache.tuscany.sca.contribution.processor.DefaultStAXArtifac
    tProcessorExtensionPoint$LazyStAXArtifactProcessor.read(DefaultS
    tAXArtifactProcessorExtensionPoint.java:387)
    at
    org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArti
    factProcessor.read(ExtensibleStAXArtifactProcessor.java:152)
    at
    org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.r
    ead(CompositeDocumentProcessor.java:186)
    at
    org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.r
    ead(CompositeDocumentProcessor.java:137)
    at
    org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.r
    ead(CompositeDocumentProcessor.java:59)
    at
    org.apache.tuscany.sca.contribution.processor.DefaultURLArtifact
    ProcessorExtensionPoint$LazyURLArtifactProcessor.read(DefaultURL
    ArtifactProcessorExtensionPoint.java:222)
    at
    org.apache.tuscany.sca.contribution.processor.ExtensibleURLArtif
    actProcessor.read(ExtensibleURLArtifactProcessor.java:96)
    at
    com.ibm.ccl.sca.tuscany.TuscanyModelHelper.processReadPhase(Tusc
    anyModelHelper.java:242)
    at
    com.ibm.ccl.sca.tuscany.TuscanyModelHelper.loadArtifact(TuscanyM
    odelHelper.java:398)
    ....
    SCA Web Service binding parser code depends on JMSURLParser
    class from com.ibm.ws.runtime plugin which is not included in
    Rational Application Developer. This problem occurs only in
    Rational Application Developer when user validates Web service
    SOAP over JMS binding. This is not an issue when SCA Web
    Service SOAP over JMS binding is deployed and validated in
    WebSphere Application Server.
    

Problem conclusion

  • SCA Web Service SOAP over JMS binding code is re-factored to
    move JMSURLParser class dependency from binding's parser
    class to binding's service provider class which is not invoked
    from Rational Application Developer during validation.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.8 and 8.5.5.1.  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

    PM94514

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-08-05

  • Closed date

    2013-08-09

  • Last modified date

    2013-08-09

  • 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

  • R700 PSY

       UP

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
11 January 2022