I insert a custom java object into the pipeline but when I look at the pipeline in the Developer it shows the objects value as ‘null’. I build another service, which uses the object from the pipeline and this is working ok. So the object is actually in the pipeline even though the Developer does not show. I suspect that this is because the Developer does not know the class (not in Developers classpath).
My problem starts when I try to call the service, which returns the custom java object, as a WebService (via automatic webMethods WSDL generation). The WebService call does not involve the developer (done via XML-Spy) but it does not return a value for the object even though I am sure that the object exists in the pipeline.
My hope was that the IntegrationServer takes the custom java object and serializes it into the SOAP WebService message but it does not seem to be that easy…
#Integration-Server-and-ESB#Flow-and-Java-services#webMethods