APAR status
Closed as fixed if next.
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
Testing an Enterprise JavaBean v3
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
JR45860
Reported component name
INTEGRATION DES
Reported component ID
5725C9702
Reported release
801
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-02-26
Closed date
2015-02-06
Last modified date
2015-02-06
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
R801 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTLXK","label":"IBM Integration Designer"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
06 February 2015