PM80036: Testing an Enterprise JavaBean v3 with the Universal Test Client might produce an error: Could not get node class

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Abstract:
    
    Attempts to test a v3 Enterprise JavaBean (EJB) with the
    Universal Test Client (UTC) supplied by IBM Rational Application
    Developer 8.0.4.1 or IBM Integration Designer 8.0.1 on IBM
    Business Process Manager v8 might result in the error UTC: Could
    not get node class
    
    Problem:
    
    This issue only occurs when testing on IBM Business Process
    Manager v8 or higher, it does not occur when testing on
    corresponding versions of IBM WebSphere Application Server.
    
    These steps reproduce the issue:
    
    0. Start the server with the Universal Test Client
    1. Develop an EJB 3 project with a Local Interface such
    com.MyInterfaceLocal
    2. Deploy the EJB 3 project to the server
    4. Attempt to test the EJB 3 with the Universal Test Client
    
    If the UTC is set to Debug mode, you will see output like the
    following in the console:
    
    [2012.11.20. 11:37:24:135 CET] 0000005c SystemOut     O   UTC:
    Adding node: ejblocal: ejblocal:
    com.ibm.xmlns.prod.websphere.business_process.services._7_0.bind
    ing.BFMJAXWSPortType
    com.ibm.xmlns.prod.websphere.business_process.services._7_0.bind
    ing.BFMJAXWSPortType
    null
    [2012.11.20. 11:37:24:135 CET] 0000005c SystemOut     O   UTC:
    Node is unknown
    [2012.11.20. 11:37:24:136 CET] 0000005c SystemOut     O   UTC:
    NCP: com.MyInterfaceLocal, com.MyInterfaceLocal
    [2012.11.20. 11:37:24:138 CET] 0000005c SystemOut     O   UTC:
    Could not get node class
    [2012.11.20. 11:37:24:138 CET] 0000005c SystemErr     R
    java.lang.ClassNotFoundException: com.MyInterfaceLocal
    [2012.11.20. 11:37:24:138 CET] 0000005c SystemErr     R       at
    java.lang.Class.forNameImpl(Native Method)
    [2012.11.20. 11:37:24:138 CET] 0000005c SystemErr     R       at
    java.lang.Class.forName(Class.java:170)
    
    Local fix:
    
    There is no known workaround at this time.
    

Local fix

Problem summary

  • A NullPointerException lead to a XML node value not being
    properly parsed.
    

Problem conclusion

  • Added a null check.
    
    The fix for this APAR is included in Rational Application
    Developer v8.0.4.3.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM80036

  • Reported component name

    RATL APP DEV WI

  • Reported component ID

    5724J1901

  • Reported release

    804

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-07

  • Closed date

    2013-10-28

  • Last modified date

    2013-10-28

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

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

    JR45860

Fix information

  • Fixed component name

    RATL APP DEV WI

  • Fixed component ID

    5724J1901

Applicable component levels

  • R804 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Rational Application Developer for WebSphere Software

Software version:

8.0.4

Reference #:

PM80036

Modified date:

2013-10-28

Translate my page

Machine Translation

Content navigation