SOAPException: faultCode=SOAP-ENV:Client; msg=No Deserializer found to...

hi all,
i am using tomcat5 and when i run a command
java org.apache.soap.server.ServiceManagerClient http://localhost:8080/soap/servlet/rpcrouter list
the following error is coming. even after i deploy when i run this command also the same
java org.apache.soap.server.ServiceManagerClient http://localhost:8080/soap/servlet/rpcrouter query "urn:helloworldservice"
[SOAPException: faultCode=SOAP-ENV:Client; msg=No Deserializer found to deserialize a 'http://schemas.xmlsoap.org/soap/envelope/:Parameter' using encoding style 'null'.; targetException=java.lang.IllegalArgumentException: No Deserializer found to deserialize a 'http://schemas.xmlsoap.org/soap/envelope/:Parameter' using encoding style 'null'.]
can any one help me the problem is what and how to rectify it

I'm having the same problem, did you resolve this?

Similar Messages

SOAPException: faultCode=SOAP-ENV:Protocol; msg=Missing content type

I have a WSDL file for which I have created a Web Service stub/skeleton through jdeveloper(version 10.1.2.3.0). Below is the complete code which has been generated by developer. Now whenever i try to run this file in jdeveloper I get the following exception. Please let me know how to resolve this issue.
Also error message is received at the following line of code:
*msg.send(endpointURL, ""<<some URL>>", requestEnv);*
{code}
*Exception Message*
{code}
[SOAPException: faultCode=SOAP-ENV:Protocol; msg=Missing content type.]
at org.apache.soap.transport.TransportMessage.read(TransportMessage.java:249)
at oracle.soap.transport.http.OracleSOAPHTTPConnection.post(OracleSOAPHTTPConnection.java:973)
at oracle.soap.transport.http.OracleSOAPHTTPConnection.send(OracleSOAPHTTPConnection.java:722)
at org.apache.soap.messaging.Message.send(Message.java:125)
at mypackage.NPVNSDLStub.PANDetails(NPVNSDLStub.java:88)
at mypackage.NPVNSDLStub.main(NPVNSDLStub.java:41)
{code}
*Code generated by Jdeveloper*
{code}
package mypackage;
import oracle.soap.transport.http.OracleSOAPHTTPConnection;
import org.apache.soap.encoding.SOAPMappingRegistry;
import org.w3c.dom.Element;
import java.util.Vector;
import oracle.jdeveloper.webservices.runtime.WrappedDocLiteralStub;
import java.net.URL;
import org.apache.soap.Envelope;
import org.apache.soap.Body;
import org.apache.soap.messaging.Message;
import java.util.Properties;
* Generated by the Oracle JDeveloper 10g Web Services Stub/Skeleton Generator.
* Date Created: Wed Feb 29 18:39:33 IST 2012
* WSDL URL: file:/C:/WS/sample.wsdl
public class NPVNSDLStub extends WrappedDocLiteralStub
public NPVNSDLStub()
m_httpConnection = new OracleSOAPHTTPConnection();
public static void main(String[] args)
try
NPVNSDLStub stub = new NPVNSDLStub();
stub.PANDetails("aaaaa8888a");
catch(Exception ex)
ex.printStackTrace();
private String _endpoint = "<<some URL>>";
public String getEndpoint()
return _endpoint;
public void setEndpoint(String endpoint)
_endpoint = endpoint;
private OracleSOAPHTTPConnection m_httpConnection = null;
private SOAPMappingRegistry m_smr = null;
public String PANDetails(String Request) throws Exception
URL endpointURL = new URL(_endpoint);
Envelope requestEnv = new Envelope();
Body requestBody = new Body();
Vector requestBodyEntries = new Vector();
String wrappingName = "PANValidationRequest";
String targetNamespace = "<<namespace url>>";
Vector requestData = new Vector();
requestData.add(new Object[] {"Request", Request});
requestBodyEntries.addElement(toElement(wrappingName, targetNamespace, requestData, false));
requestBody.setBodyEntries(requestBodyEntries);
requestEnv.setBody(requestBody);
Message msg = new Message();
msg.setSOAPTransport(m_httpConnection);
*msg.send(endpointURL, "<<some URL>>", requestEnv);*
Envelope responseEnv = msg.receiveEnvelope();
Body responseBody = responseEnv.getBody();
Vector responseData = responseBody.getBodyEntries();
return (String)fromElement((Element)responseData.elementAt(0), java.lang.String.class);
{code}
Edited by: EJP on 2/03/2012 17:22: added code tags, but your indentation needs fixing

Kishore,
See the links referenced in these threads.
Web Services and R12
Re: Web Services and R12
Integrated SOA Gateway
Re: Integrated SOA Gateway
Regards,
Hussein

SOAP-ENV:IOException; msg=SSL handshake failed: SSLProtocolErr

Getting following error while invoking webservice over ssl.
"SOAP-ENV:IOException; msg=SSL handshake failed: SSLProtocolErr"
We generated webservice java stub using JDeveloper based on wsdl provided to us from 3rd party. We are able to test this webservice successfully without ssl . Once ssl is enabled by the 3rd party webservice provider we faced
"java.lang.UnsatisfiedLinkError: no njssl9 in java.library.path" error in JDeveloper.
In JDeveloper we were able to resolve this by following details provided at
Lehmann's web log on "Securing a Web Service - Client SSL" (http://radio.weblogs.com/0132036/2004/02/13.html ).
We then run the same java stub from oracle application server 9iAS 1.0.2.2.2. This is when we get error
"SOAP-ENV:IOException; msg=SSL handshake failed: SSLProtocolErr"
Debugging further we see that in 9iAS we have following in our class path.
..iAS/jlib/jssl-1_1.jar:..iAS/jlib/javax-ssl-1_1.jar:..iAS/soap/webapps/soap/WEB-INF/lib/soap.jar
we took the same files and added to libraries in JDeveloper and are able to reproduce the same error in JDeveloper. We turned on Debug on oracle.jssl.debug and with that we see following details
instantiate the hashtable
SocketTable write Enter fdin 1
SocketTable write offset 0 length 72
SocketTable write: 72 bytes
SocketTable read Enter
SocketTable read: 1 bytes
SocketTable read Enter
SocketTable read: 2 bytes
SSLSocketImpl close Thread:main
In close removing fd 1Thread main
[SOAPException: faultCode=SOAP-ENV:IOException; msg=SSL handshake failed: SSLProtocolErr...
Any suggestions on how to resolve this error in oracle application server 9iAS ?
Note: We run Oracle E-Business Suite on this same 9iAS so any change we make should not impact the oracle applications running on this server.

hi,
thi sis very simple soloution for this. open the wsdl into the internet explorer. when wsdl file open save this wsdl with the .xml extension. when u want to make dat contorl or web sekelton or proxy dont use the hhtps:// ????????/ url give the path there for the .xml file which u save for this. i am sure u will invoke all the services which is provoider by the web service.
have nice day
best regards

SOAP:ENV Error: Resource..not found on this server

I created a simple java class with a method that returns org.w3c.dom.Element type.
Created web service for this class and method in Jdeveloper.
Deployed this web service in OC4J locally (as explained by other web services examples).
Then I created a Client Stub for this web service (.wsdl file).
When testing this client stub ( I followed the same steps as mentioned in OTN DEPT/EMP Web Service), I get the following exception:
D:\JDEVELOPER\jdk\bin\javaw.exe -ojvm -classpath D:\JDEVELOPER\jdev\mywork\MyWorkspace\MyProject2\classes;D:\JDEVELOPER\jdev\lib\jdev-rt.jar;D:\JDEVELOPER\jdbc\lib\classes12.jar;D:\JDEVELOPER\jdbc\lib\nls_charset12.jar;D:\JDEVELOPER\jdev\lib\jdev-rt.jar;D:\JDEVELOPER\soap\lib\soap.jar;D:\JDEVELOPER\lib\xmlparserv2.jar;D:\JDEVELOPER\jlib\javax-ssl-1_2.jar;D:\JDEVELOPER\jlib\jssl-1_2.jar;D:\JDEVELOPER\j2ee\home\lib\activation.jar;D:\JDEVELOPER\j2ee\home\lib\mail.jar;D:\JDEVELOPER\j2ee\home\lib\http_client.jar;D:\JDEVELOPER\lib\xmlparserv2.jar;D:\JDEVELOPER\lib\xmlcomp.jar;D:\JDEVELOPER\rdbms\jlib\xsu12.jar GetProductsClient
[SOAPException: faultCode=SOAP-ENV:Protocol; msg=Unsupported response content type "text/html", must be: "text/xml". Response was:
<HTML><HEAD><TITLE>404 Not Found</TITLE></HEAD><BODY><H1>404 Not Found</H1>Resource /MyWorkspace-MyProject2-context-root/GetProducts not found on this server</BODY></HTML>
The SOAP response is as bellow:
HTTP/1.1 404 Not Found
Date: Wed, 27 Nov 2002 15:36:27 GMT
Server: Oracle9iAS (9.0.3.0.0) Containers for J2EE
Content-Length: 171
Connection: Close
Content-Type: text/html
<HTML><HEAD><TITLE>404 Not Found</TITLE></HEAD><BODY><H1>404 Not Found</H1>Resource /MyWorkspace-MyProject2-context-root/GetProducts not found on this server</BODY></HTML>
The Debug shows, the Method getProductsXM() in the client stub is failing at
Response response = call.invoke(endpointURL, "");
This appears to be generating fault and the code is throughing exception which is not casted in to a Element type.
Not sure what is causing this to fail. And I have not toucjed/ changed the URI for this webservice myself at all. Whatever URIs or Name spaces are there, they are all generarted by JDeveloper.
I was trying to create a web service that display/return Resultset.
Any feedback/suggestions ? I would appreciate if you can point me to some sample code that does this ( returning Resultset as XML -<ROWSET> Element)
Thanks,
Madhu

Does this do the trick?
Server side class:
import org.w3c.dom.*;
import oracle.xml.parser.v2.*;
public class Employee
public Employee ()
public Element getEmployeeElement(){
Document doc = new XMLDocument();
Element elAdd = doc.createElement( "employee");
Element elA = doc.createElement( "name");
elA.appendChild(doc.createTextNode("Mike"));
elAdd.appendChild(elA);
doc.appendChild(elAdd);
return doc.getDocumentElement();
Generated Interface from JDev:
* Generated by the Oracle9i JDeveloper Web Services Interface Generator
* Date Created: Wed Nov 27 11:42:37 PST 2002
* This interface lists the subset of public methods that you
* selected for inclusion in your web service's public interface.
* It is referenced in the web.xml deployment descriptor for this service.
* This file should not be edited.
public interface IEmployee
public org.w3c.dom.Element getEmployeeElement();
Generated client with a print method to output the result (using WSDL generated by JDeveloper):
import oracle.soap.transport.http.OracleSOAPHTTPConnection;
import org.apache.soap.encoding.soapenc.BeanSerializer;
import org.apache.soap.encoding.SOAPMappingRegistry;
import org.apache.soap.util.xml.QName;
import java.net.URL;
import org.apache.soap.Constants;
import org.apache.soap.Fault;
import org.apache.soap.SOAPException;
import org.apache.soap.rpc.Call;
import org.apache.soap.rpc.Parameter;
import org.apache.soap.rpc.Response;
import org.w3c.dom.Element;
import java.util.Vector;
import java.util.Properties;
import oracle.xml.parser.v2.*;
* Generated by the Oracle9i JDeveloper Web Services Stub/Skeleton Generator.
* Date Created: Wed Nov 27 11:39:29 PST 2002
* WSDL URL: file:/D:/demo/Workspace5/Project1/src/Employee.wsdl
public class EmployeeStub
public EmployeeStub()
m_httpConnection = new OracleSOAPHTTPConnection();
m_smr = new SOAPMappingRegistry();
public static void main(String[] args)
try
EmployeeStub stub = new EmployeeStub();
// Add your own code here.
Element e = stub.getEmployeeElement();
((XMLElement)e).print(System.out);
catch(Exception ex)
ex.printStackTrace();
public String endpoint = "http://127.0.0.1:8888/Workspace5-Project1-context-root/Employee";
private OracleSOAPHTTPConnection m_httpConnection = null;
private SOAPMappingRegistry m_smr = null;
public Element getEmployeeElement() throws Exception
Element returnVal = null;
URL endpointURL = new URL(endpoint);
Call call = new Call();
call.setSOAPTransport(m_httpConnection);
call.setTargetObjectURI("Employee");
call.setMethodName("getEmployeeElement");
call.setEncodingStyleURI(Constants.NS_URI_LITERAL_XML);
Vector params = new Vector();
call.setParams(params);
call.setSOAPMappingRegistry(m_smr);
Response response = call.invoke(endpointURL, "");
if (!response.generatedFault())
Parameter result = response.getReturnValue();
returnVal = (Element)result.getValue();
else
Fault fault = response.getFault();
throw new SOAPException(fault.getFaultCode(), fault.getFaultString());
return returnVal;
public void setMaintainSession(boolean maintainSession)
m_httpConnection.setMaintainSession(maintainSession);
public boolean getMaintainSession()
return m_httpConnection.getMaintainSession();
public void setTransportProperties(Properties props)
m_httpConnection.setProperties(props);
public Properties getTransportProperties()
return m_httpConnection.getProperties();
Mike.

Soap client No Deserializer found to deserialize ...

Hello,
I am trying to call a .net service from my java code and i as soon as i get the result an exception occurs as no deserializer is found for my result.
I tried everything, i tried regestering deserializers, using the default but nothing seems to work.
the exception as well as my code are provided below.
Can anyone help me?
the exception
[SOAPException: faultCode=SOAP-ENV:Client; msg=No Deserializer found to deserialize a 'http://tempuri.org/:methodnameResult' using encoding style 'null'.; targetException=java.lang.IllegalArgumentException: No Deserializer found to deserialize a 'http://tempuri.org/:methodnameResult' using encoding style 'null'.]
import java.io.*;
import java.net.*;
import java.util.*;
import org.apache.soap.util.xml.*;
import org.apache.soap.*;
import org.apache.soap.rpc.*;
import org.apache.soap.encoding.*;
import org.apache.soap.encoding.soapenc.*;
import org.apache.soap.encoding.soapenc.ArraySerializer;
public class LoginClient
public String void main(string args[]) throws Exception{
System.err.println("SOAP call testing");
String str1 = "the first string";
String str2 = "the second string";
LoginClient smc = new LoginClient();
String returnValue = smc.doRequest(str1,str2);
System.err.println(returnValue);
public String doRequest(String str1,String str2) throws Exception {
Call call = new Call ();
call.setTargetObjectURI ("http://host");
call.setMethodName ("methodname");
SOAPMappingRegistry soapMappingRegistry = new SOAPMappingRegistry();
BeanSerializer beanSer = new BeanSerializer();
soapMappingRegistry.mapTypes(Constants.NS_URI_SOAP_ENC, new QName("http://host", "methodname"), java.util.List.class, beanSer, beanSer);
call.setSOAPMappingRegistry(soapMappingRegistry);
Vector params = new Vector ();
call.setEncodingStyleURI("http://schemas.xmlsoap.org/soap/encoding/");
params.addElement (new Parameter("parameter", String.class, new String (str1), "http://schemas.xmlsoap.org/soap/encoding/"));
params.addElement (new Parameter("ticket", String.class, new String (str2), "http://schemas.xmlsoap.org/soap/encoding/"));
call.setParams (params);
Response resp = call.invoke (new URL("http://host/DataService.asmx"),"http://tempuri.org/methodname");
if (resp.generatedFault ()) {
Fault fault = resp.getFault ();
System.out.println ("the call failed: ");
System.out.println (" Fault Code = " + fault.getFaultCode ());
System.out.println (" Fault String = " + fault.getFaultString ());
return fault.getFaultCode ()+fault.getFaultString ();
else {
Parameter result = resp.getReturnValue ();
return ((String)result.getValue());
}

I had a similar problem to this when trying to connect a Java Client to a C-Sharp Server. Apparently M$ has issues with allowing anyone other than their products to connect to their server. I had to modify their server to list the namespace for each component of soap document. By default, the body of M$ looks like this....
<soap:Body>
<types:HelloWorld xsi:type="types:HelloWorld">
<name xsi:type="xsd:string">string</name>
</types:HelloWorld>
</soap:Body>
Wheras... with Java, you need to the namespace listed for each element... so the body would look like this:
<soap:Body soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<types:HelloWorld xsi:type="types:HelloWorld">
<name xsi:type="xsd:string">string</name>
</types:HelloWorld>
</soap:Body>
This may or may not help you, but it took me a while to discover it, so maybe it is something wrong with the server, not your code.
Kevin Bryan

BPEL process times out when SOAP-ENV:Fault is received from service.

Hi - I have a BPEL process identical to one in 10.1.2.0.2. If I execute the same test, the BPEL console displays the following on the console for version 10.1.2.0.2.
<Response>Clientwhen invoking endpointAddress 'http://galileo.wlgore.com:5555/soap/default', [ISS.0088.9134] Exception occurred while processing the body of the messageAxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client faultSubcode: faultString: [ISS.0088.9134] Exception occurred while processing the body of the message faultActor: http://galileo.wlgore.com:5555/soap/default faultNode: faultDetail: {http://www.webMethods.com/2001/10/soap/encoding}exception: <className>com.wm.pkg.art.error.DetailedServiceException</className>
     <message lang="">[ART.117.4002] Adapter Runtime (Adapter Service): Unable to invoke adapter service GORE_DSI_Services.AdaptorService:WorkOrderCompletion. BSFN error code: 2 Number of error: 1 Error item 1 ErrorLevel : 1 ErrorID : 0 DDItem : 0115 lineNumber : 5371 fileName : nd3n1114.c subText : alphaDescription : Error: Work Order Number Invalid glossaryText : CAUSE . . . . The Work Order Number entered does not exist in the Work Order Master file (F4801). RESOLUTION. . Either enter the correct Work Order Number or create a new Work Order for the number on the display. javax.resource.ResourceException: BSFN error code: 2 Number of error: 1 Error item 1 ErrorLevel : 1 ErrorID : 0 DDItem : 0115 lineNumber : 5371 fileName : nd3n1114.c subText : alphaDescription : Error: Work Order Number Invalid glossaryText : CAUSE . . . . The Work Order Number entered does not exist in the Work Order Master file (F4801). RESOLUTION. . Either enter the correct Work Order Number or create a new Work Order for the number on the display. at com.psft.xpi.adapter.erp.service.BSFNExecuteTemplateImpl.execute(BSFNExecuteTemplateImpl.java:306) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.psft.xpi.adapter.erp.service.BSFNExecuteTemplate.execute(BSFNExecuteTemplate.java:134) at com.wm.adk.cci.interaction.WmInteraction.execute(WmInteraction.java:70) at com.wm.pkg.art.ns.AdapterServiceNode.invokeService(AdapterServiceNode.java:596) at com.wm.pkg.art.ns.ARTNSService.baseInvoke(ARTNSService.java:47) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:155) at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:324) at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:580) at com.wm.lang.flow.FlowState.step(FlowState.java:438) at com.wm.lang.flow.FlowState.invoke(FlowState.java:403) at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1749) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:113) at com.wm.app.b2b.server.Service.doInvoke(Service.java:607) at com.wm.app.b2b.server.Service.doInvoke(Service.java:556) at wm.server.soap.envelope(soap.java:98) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:287) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:128) at com.wm.app.b2b.server.HTTPSOAPHandler._process(HTTPSOAPHandler.java:457) at com.wm.app.b2b.server.HTTPSOAPHandler.process(HTTPSOAPHandler.java:111) at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:298) at com.wm.util.pool.PooledThread.run(PooledThread.java:105) at java.lang.Thread.run(Thread.java:534) </message>
</Response>
With this version, however, we either receive "java.lang.IllegalStateException: "Cannot call setRollbackOnly() current thread is NOT associated with a transaction" or a timeout error.
I captured the return message from both servers and it is identical (shown below):
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema">
     <SOAP-ENV:Body>
          <SOAP-ENV:Fault>
               <faultcode>SOAP-ENV:Client</faultcode>
               <faultstring>[ISS.0088.9134] Exception occurred while processing the body of the message</faultstring>
               <faultactor>http://galileo.wlgore.com:5555/soap/default </faultactor>
               <detail xmlns:webM="http://www.webMethods.com/2001/10/soap/encoding">
                    <webM:exception>
                         <webM:className>com.wm.pkg.art.error.DetailedServiceException</webM:className>
                         <webM:message xml:lang="">="">[ART.117.4002] Adapter Runtime (Adapter Service): Unable to invoke adapter service GORE_DSI_Services.AdaptorService:WorkOrderCompletion. BSFN error code: 2 Number of error: 1 Error item 1 ErrorLevel : 1 ErrorID : 0 DDItem : 0115 lineNumber : 5371 fileName : nd3n1114.c subText : alphaDescription : Error: Work Order Number Invalid glossaryText : CAUSE . . . . The Work Order Number entered does not exist in the Work Order Master file (F4801). RESOLUTION. . Either enter the correct Work Order Number or create a new Work Order for the number on the display. javax.resource.ResourceException: BSFN error code: 2 Number of error: 1 Error item 1 ErrorLevel : 1 ErrorID : 0 DDItem : 0115 lineNumber : 5371 fileName : nd3n1114.c subText : alphaDescription : Error: Work Order Number Invalid glossaryText : CAUSE . . . . The Work Order Number entered does not exist in the Work Order Master file (F4801). RESOLUTION. . Either enter the correct Work Order Number or create a new Work Order for the number on the display. at com.psft.xpi.adapter.erp.service.BSFNExecuteTemplateImpl.execute(BSFNExecuteTemplateImpl.java:306) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.psft.xpi.adapter.erp.service.BSFNExecuteTemplate.execute(BSFNExecuteTemplate.java:134) at com.wm.adk.cci.interaction.WmInteraction.execute(WmInteraction.java:70) at com.wm.pkg.art.ns.AdapterServiceNode.invokeService(AdapterServiceNode.java:596) at com.wm.pkg.art.ns.ARTNSService.baseInvoke(ARTNSService.java:47) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:155) at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:324) at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:580) at com.wm.lang.flow.FlowState.step(FlowState.java:438) at com.wm.lang.flow.FlowState.invoke(FlowState.java:403) at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1749) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:113) at com.wm.app.b2b.server.Service.doInvoke(Service.java:607) at com.wm.app.b2b.server.Service.doInvoke(Service.java:556) at wm.server.soap.envelope(soap.java:98) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:287) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:128) at com.wm.app.b2b.server.HTTPSOAPHandler._process(HTTPSOAPHandler.java:457) at com.wm.app.b2b.server.HTTPSOAPHandler.process(HTTPSOAPHandler.java:111) at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:298) at com.wm.util.pool.PooledThread.run(PooledThread.java:105) at java.lang.Thread.run(Thread.java:534)</webM:message>
                    </webM:exception>
               </detail>
          </SOAP-ENV:Fault>
     </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Thanks,
RM

We have tested this same scenario for several services and are experiencing the same result... timing out instead of returning the fault. This is a critical issue for us and would prevent us from implementing this software.

PL/SQL Web Service Error: IllegalArgumentException : No Deserializer found

I deployed a pl/sql web service on a stand-alone OC4J, when I test this I am getting error "IllegalArgumentException : No Deserializer found to deserialize". Find below the detailed response:
<?xml version="1.0" encoding="UTF-8" ?>
- <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- <SOAP-ENV:Body>
- <SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server.Exception:</faultcode>
<faultstring>java.lang.IllegalArgumentException: No Deserializer found to deserialize a 'http://cmem.oracle.apps.cs.ws/ICmem_cs_ws_pkg.xsd:cmem_oracle_apps_cs_ws_CmemServiceRequestParamObj' using encoding style 'http://schemas.xmlsoap.org/soap/encoding/'.</faultstring>
<faultactor>/cmemws/CmemServiceRequests</faultactor>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
I was using a complex parameter as well as response. Below is the WSDL. If anyone has any idea what could be the issue, let me know.
<?xml version="1.0" encoding="UTF-8" ?>
- 
- 
- <definitions name="CmemServiceRequests" targetNamespace="http://cmem/oracle/apps/cs/ws/CmemServiceRequests.wsdl" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://cmem/oracle/apps/cs/ws/CmemServiceRequests.wsdl" xmlns:ns1="http://cmem.oracle.apps.cs.ws/CmemServiceRequests.xsd">
- <types>
- <schema targetNamespace="http://cmem.oracle.apps.cs.ws/CmemServiceRequests.xsd" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns="http://www.w3.org/2001/XMLSchema">
- <complexType name="cmem_oracle_apps_cs_ws_CmemServiceRequestParamObjUser" jdev:packageName="cmem.oracle.apps.cs.ws" xmlns:jdev="http://xmlns.oracle.com/jdeveloper/webservices">
- <all>
<element name="srId" type="decimal" nillable="true" minOccurs="0" />
<element name="srNumber" type="string" nillable="true" minOccurs="0" />
<element name="srGroupOwner" type="string" nillable="true" minOccurs="0" />
<element name="srOwner" type="string" nillable="true" minOccurs="0" />
<element name="srDateFrom" type="dateTime" nillable="true" minOccurs="0" />
<element name="srDateTo" type="dateTime" nillable="true" minOccurs="0" />
<element name="caller" type="string" nillable="true" minOccurs="0" />
<element name="inspector" type="string" nillable="true" minOccurs="0" />
<element name="problemCode" type="string" nillable="true" minOccurs="0" />
</all>
</complexType>
- <complexType name="cmem_oracle_apps_cs_ws_CmemServiceRequestObjUser" jdev:packageName="cmem.oracle.apps.cs.ws" xmlns:jdev="http://xmlns.oracle.com/jdeveloper/webservices">
- <all>
<element name="srId" type="decimal" />
<element name="srNumber" type="string" />
<element name="srGroupOwner" type="string" />
<element name="srOwner" type="string" />
<element name="srType" type="string" />
<element name="srDate" type="dateTime" />
<element name="statusCode" type="string" />
<element name="srParty" type="string" />
<element name="caller" type="string" />
<element name="srSummary" type="string" />
<element name="problemCode" type="string" />
<element name="problemDescription" type="string" />
<element name="resolutionCode" type="string" />
<element name="resolutionDesc" type="string" />
<element name="resolutionSummary" type="string" />
<element name="srAddress" type="string" />
<element name="srCity" type="string" />
<element name="srZipCode" type="string" />
<element name="srState" type="string" />
</all>
</complexType>
</schema>
</types>
- <message name="getSrDetails0Request">
<part name="pSeletionConditions" type="ns1:cmem_oracle_apps_cs_ws_CmemServiceRequestParamObjUser" />
</message>
- <message name="getSrDetails0Response">
<part name="return" type="ns1:cmem_oracle_apps_cs_ws_CmemServiceRequestObjUser" />
</message>
- <portType name="CmemServiceRequestsPortType">
- <operation name="getSrDetails">
<input name="getSrDetails0Request" message="tns:getSrDetails0Request" />
<output name="getSrDetails0Response" message="tns:getSrDetails0Response" />
</operation>
</portType>
- <binding name="CmemServiceRequestsBinding" type="tns:CmemServiceRequestsPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
- <operation name="getSrDetails">
<soap:operation soapAction="" style="rpc" />
- <input name="getSrDetails0Request">
<soap:body use="encoded" namespace="CmemServiceRequests" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</input>
- <output name="getSrDetails0Response">
<soap:body use="encoded" namespace="CmemServiceRequests" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</output>
</operation>
</binding>
- <service name="CmemServiceRequests">
- <port name="CmemServiceRequestsPort" binding="tns:CmemServiceRequestsBinding">
<soap:address location="http://isd104364:8888/cmemws/CmemServiceRequests" />
</port>
</service>
</definitions>
Appreciate any help. Thanks.
Binish

Ok, this sounds like a known bug ( Bug 5908689 ) in 10.1.3.1, but this was specific to non-Windows platforms. Are you on Linux/Solaris or any other platform? It might or might not be the same problem you are hitting but it does seem quite close (can't say for sure without a close investigation, I am afraid!)
In any case, this bug is fixed in the 10.1.3.4 patchset (besides quite a few other fixes and enhancements) - so would recommend you to first apply the 10.1.3.4 patchset and retest. The patchset is available on My Oracle Support (formerly Metalink) under Patch 7272722. Or you could go a step ahead, and apply the 10.1.3.5 patchset (Patch 8626084) instead which is the latest patchset for OracleAS 10.1.3.x.
HTH,
Yogesh

OSB not adding SOAP-ENV:encodingStyle attribute, invoke fails

Hi, I have a WSDL that when inspected by XMLSpy, creates the following payload.
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
     <SOAP-ENV:Body>
          <m:logOut xmlns:m="http://konnex.aarp.org/wsdl/HartfordServicesSecure" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
               <String_1 xsi:type="xsd:string">String</String_1>
          </m:logOut>
     </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
When I try to invoke this via OSB, I get the following message.
<env:Envelope env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="http://konnex.aarp.org/types/HartfordServicesSecure">
     <env:Body>
          <env:Fault>
               <faultcode>env:Client</faultcode>
               <faultstring>JAXRPCTIE01: caught exception while handling request: unexpected encoding style: expected=http://schemas.xmlsoap.org/soap/encoding/, actual=</faultstring>
          </env:Fault>
     </env:Body>
</env:Envelope>
The reason is because OSB is not putting in the *SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/* attribute. I verified this in obtunnel.
I'm currently trying to work around this in OSB using xquery but so far I've had no luck.
Thanks in Advance.

hi,
I have two policies applies on business service :
1. Password digest policy
<wsp:Policy wsu:Id="PasswrdDigest" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wssp="http://www.bea.com/wls90/security/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wssp:Identity>
          <wssp:SupportedTokens>
               <wssp:SecurityToken TokenType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#UsernameToken">
               <wssp:UsePassword Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest"/>
          </wssp:SecurityToken>
          </wssp:SupportedTokens>
          </wssp:Identity>
</wsp:Policy>
2. Message Interval Policy
<wsp:Policy wsu:Id="MessageAge" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy">
<wssp:MessageAge Age="60" xmlns:wssp="http://www.bea.com/wls90/security/policy"/>
</wsp:Policy>
Please share your views.

Changing SOAP-ENV prefix in SAAJ?

I'm using the latest webservices pack from Sun and have hit a roadblock.
We have some external clients that are relying on the SOAP messages we send them to have the prefix namespace <SOAP>. The SAAJ implementation seems to be hardcoding <SOAP-ENV>.
Is there anyway to specify/override the default SOAP namespace prefix?
i.e.
<SOAP-ENV:Envelope> --> <SOAP:Envelope>
Thanks,
- Tim

I managed to change my SOAP-ENV but the problem then is that unless you declare the namespace in every tag it add a xmlns="" to the first non specified tag.
how I changed the SOAP-ENV is as follows
SOAPPart part = msg.getSOAPPart();
//get the envelope
SOAPEnvelope envelope = part.getEnvelope();
//add the soap declaration
envelope.addNamespaceDeclaration("soap","http://schemas.xmlsoap.org/soap/envelope/");
//remove the default SOAP-ENV
envelope.removeNamespaceDeclaration("SOAP-ENV");
//Set the prefix to soap instead of SOAP-ENV
envelope.setPrefix("soap");
Mike

Upgrading from 8.1 to 9.2: non-WL SOAP/websvc client timeout

So, I was using a Weblogic 8.1 'clientgen' generated a SOAP/websvc client, based on a WSDL the svc provider gave me. The generated components were accessing an Axis SOAP svc from a WL 8.1 deployed svc.
To set the conn timeout and SOAP-end-point-URL dynamically, I did this:
System.setProperty("weblogic.webservice.UseWebLogicURLStreamHandler","true");
BindingInfo bindingInfo =(weblogic.webservice.binding.BindingInfo) stub._getProperty("weblogic.webservice.bindinginfo");
bindingInfo.setTimeout(3);
bindingInfo.setAddress("http://someco.com/SOAPEndPoint");
After regenerating using WL 9.2 'clientgen', it turns out BindingInfo is deprecated, but it only says "please migrate to jws for webservices". Not sure what that means, but after some searching, I was able to figure out that I might be able to do this:
stub._setProperty(MyStub.ENDPOINT_ADDRESS_PROPERTY,"http://someco.com/SOAPEndPoint");
stub._setProperty("weblogic.wsee.transport.connection.timeout",3);
Sadly, my env is not ready yet, so I haven't been able to try it out, so I thought I'd check here for comments.
I know I could do this using Axis' wsdl2java generated components, but I want to keep it within weblogic for now.
Also, I'm suspecting that the URL stream handler is no longer needed either.
Any comments?
Karoly

Hi All,
I am also having the same problem.
Some one PLEASE HELP, its very urgent.
Thanks,

XI SOAP-ENV request!!!

Hi all,
I have a problem that is not resolved yet and Im feeling quite worried because I used up all the hypotheses that knew!!! I did a test that it gave a light, where problem are placed, but I dont know how I can fix it. I hope that somebody could help me
Calling the web service directly via an external tool as a web service client using soap sender adapter, the request SOAP-ENV is:
<?xml version="1.0" encoding="UTF-8" ?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema"><SOAP-ENV:Body SOAP-ENV:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'><b><ns1:send xmlns:ns1='prt:service:pt.edp.sync'><send_1_param2 xsi:type='xs:string'>teste</send_1_param2></ns1:send></b></SOAP-ENV:Body></SOAP-ENV:Envelope>
And it works fine!
Using the same external tool also as a web service client, but now trough XI, the SOAP-ENV request is a little bit different: (the tag with send method it lack!!!)
<b>
<ns1:send_1_param2 xmlns:ns1='prt:service:pt.edp.sync'>teste</ns1:send_1_param2>
</b>
It seams that method <b>send</b> is not being invoked, if you look to the previous SOAP-ENV you see the tag with method <b><ns1:send ></b> before tag with input parameter <b><ns1:send_1_param2></b> I think that this tag should come into soap request invoked by XI. For one reason that I dont know, this tag doesnt come... and when I look to the log of web service provider invoked from XI (is a SAP EP) the log gives me this message:
<b>Method with name send_1_param2 is not defined in wsdl file
[EXCEPTION]
java.lang.NoSuchMethodException</b>
It seams that XI wants to invoke a method with a wrong name <b>send_1_param2</b>; the method to be invoked should be <b>send</b> and not <b>send_1_param2</b>!!! Can anybody explain me why this happening? Did I forget something, some configuration steps?
Any help are appreciated.
Regards,
Ricardo.

Hi guys,
Here the answer like I promise!
All I get is a little explanation about web services rpc-styled in SOAP FAQ (note 856597) under question: Q: Can I convert an RPC styled WSDL to a document styled WSDL?
Some RPC styled service implementations have problems with such non conformant SOAP service. Therefore, we also need to adjust the message accordingly.
First we need to find what kind of elements (tags) are missing on the soap request/response and add these elements (adjust the message accordingly).
I fixed my problem using XSLT extension (ABAP Engine). All I did was following the steps provided in the Robert Eijpe weblog /people/r.eijpe/blog/2005/11/04/using-abap-xslt-extensions-for-xi-mapping
But you also could create your own request using graphical mapping and add the missing tags. In my case a just only needed to add <operator> tag to invoke the right method.
I test with both (XSLT and Graphical mapping) and it works
I hope it helps anybody with identical problems.
Cheers,
Ricardo.

Tracing SOAP-ENV:Server.Exception errors

Hi,
I have generated my WebServices from an ADF Application Module using Jdeveloper 10.1.2.1.
After deploying the Web Services to the Application Server I call the web service test screens i.e. http://machine:port/MyWebServicesPath/MyWebService to check that the deployment has been successful.
When I enter the required values into the test screen occasionally I receive a SOAP response that contains error messages that are not being returned from my application code
e.g.
faultcode = FaultSOAP-ENV:Server.Exception
faultstring = oracle.jbo.common.ampool.ApplicationPoolException: JBO-30003: The application pool (package1.MyServiceLocal) failed to checkout an application module due to the following exception:
faultactor = /MyWebServicesPath/MyWebService
Checking the logs written by the web service application code confirms that these errors are thrown before the values reach the application code.
Are there any logs that would give me a clearer picture of what the problem is as tracking down the problem by trial and error often requires multiple time-consuming redeployments.
Thanks in advance
Lisa

Hi Lisa,
From a quick search with google on JBO-30003, it seams to indicate that the most common error condition is a dead connection to the underlying database.
The ADF Application Module that you are exposing as a service is most likely to be the one throwing this error. The SOAP server is then wrapping this runtime error into a SOAP fault with the code,actor and string that you see.
Hope this helps,
Eric

Error: [env:ClienT:caught exception while handling request]

failure when calling to the service Web
1. I INTRODUCE DIRECTION WSDL URL And SOON PULSE TO SHOW METODOS
2. And IT INDICATES The METODOS To ME AVAILABLE FOR THIS SERVICE WEB
3. LATER IT SHOWS THE PARAMETERS TO ME THAT NEEDS TO MAKE THE CALL TO THE PREVIOUS METODO
4. I INTRODUCE THE VALUE OF THE PARAMETER AND WHEN I TEST THE TEST RESULTS IS THE FOLLOWING ERROR:
[env:Client : caught exception while handling request: unexpected encoding style: expected=, actual=http://xml.apache.org/xml-soap/literalxml]

failure when calling to the service Web
1. I INTRODUCE DIRECTION WSDL URL And SOON PULSE TO SHOW METODOS
2. And IT INDICATES The METODOS To ME AVAILABLE FOR THIS SERVICE WEB
3. LATER IT SHOWS THE PARAMETERS TO ME THAT NEEDS TO MAKE THE CALL TO THE PREVIOUS METODO
4. I INTRODUCE THE VALUE OF THE PARAMETER AND WHEN I TEST THE TEST RESULTS IS THE FOLLOWING ERROR:
[env:Client : caught exception while handling request: unexpected encoding style: expected=, actual=http://xml.apache.org/xml-soap/literalxml]

Web-service client in JDeveloper 10.1.3.3.0 -- No Deserializer found...

Hi,
I'm trying to connect to a web-service that has a wsdl on this url:
http://shimmer.oslo.dnmi.no/metdata/MetDataService?WSDL
I can reach this site from a browser.
In the Connection Manager I create a new 'UDDI Registry' connection, and type in the url above as the 'Inquiry endpoint url'. When I try to test the connection I get the folowing error:
Testing connection with no proxy...
Contacting http://shimmer.oslo.dnmi.no/metdata/MetDataService?WSDL...
The inquiry endpoint could not be contacted. Test failed.
No Deserializer found to deserialize a 'urn:uddi-org:api_v2:name' using encoding style 'null'. [java.lang.IllegalArgumentException]
Have I missed something here ? I just want to connect to a public web-service, if someone could point me in the right direction I would be happy...
Regards
Erik
Message was edited by:
Bradski

Hi,
actually this URL is non that points to a UDDI but to a Web Service directly. So you can build a WS client for this WSDL file by providing the URL in teh Web Services field
Frank

Remove SOAP-ENV tags from xml RECEIVER RESPONSE payload (XSL needed?)

Hi
I need to remove some tags from the payload of a RESPONSE message in a SOAP webservice scenarion.
The received payload looks like this:
before -
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns="http://tempuri.org/what.xsd">
<SOAP-ENV:Body>
<ns:crejob-resp>
    <response-data>
      <Result>0</Result>
    </response-data>
</ns:crejob-resp>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
after it should look like this
after -
<?xml version="1.0" encoding="UTF-8"?>
<crejob-resp>
   <response-data>
      <Result>0</Result>
   </response-data>
</crejob-resp>
I was thinking of using XSL as a "pre-burner" step before my mapping program but need help to XSL on this.
Hope somebody can help
Cheers

I am sorry to be such a pain in the a..
But I still get the wrong result (with your first option, 2nd option is not working):
<?xml version="1.0" encoding="UTF-8"?>
<crejob-resp>
<response-data>0<Result>0</Result></response-data>
</crejob-resp>
Hope u can help again
and also my source can look like: (unbounded on response-data)
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns="http://tempuri.org/what.xsd">
<SOAP-ENV:Body>
<ns:crejob-resp>
   <response-data>
      <Result>0</Result>
   </response-data>
   <response-data>
      <Result>1</Result>
   </response-data>
   <response-data>
      <Result>2</Result>
   </response-data>
</ns:crejob-resp>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Edited by: Bowie on Jul 2, 2009 3:08 PM

SOAPException: faultCode=SOAP-ENV:Client; msg=No Deserializer found to...

Similar Messages

Maybe you are looking for