I’m working with IS 6.0.1. From a generated service (from the administrator) executes a remote method in the EJB fine (I see on the application server which is BEA Weblogic 5.1 sp12 logs coming from the EJB that indicate a completely successful execution beginning to end). The EJB call ends and I get an exception:

java.lang.ClassCastException: java.lang.Integer
at com.wm.util.coder.IDataBinCoder._decode(IDataBinCoder.java:668)
at com.wm.util.coder.IDataBinCoder._decode(IDataBinCoder.java:671)
at com.wm.util.coder.IDataBinCoder.decode(IDataBinCoder.java:205)
at com.wm.driver.comm.b2b.http.SessionHTTPLink.transportMsg(SessionHTTPLink.java:95)
at com.wm.driver.comm.b2b.http.HTTPLink$HTTPSendReceive.run(HTTPLink.java:446)
at java.lang.Thread.run(Thread.java:484)

The EJB accepts a String as a parameter and returns a custom Java class (a very simple data object which is a few getter/setters). I’m not sure if the below message is related but I get the below from the Developer console:

2003-06-18 15:54:13 EDT [ISC.0076.0005E] BinCoder decode error creating Java serialized object. Excpt:java.lang.ClassNotFoundException: loyalty.accountmanagement.AccountRecord

From what I can tell, the jar file containing the classes are in the right spot. I actually put them everywhere just to eliminate that possibility (in <is>/lib/jar and <is>/lib/system and in the classpath).

You are actually encountering a Java de-serialization error between the Integration Server and the Developer; not between the Integration Server and your application server.

This error occurs when you do not have the Java class on your Develeper classpath.

You have one of two options for verifying proper service execution:
i) ensure that the Java class (and any classes it references/subclasses) also appears on the Developer’s classpath, or
ii) test your service via a browser.

That was exactly the problem. Thanks!