Error on Client WebService generation

Dear all,
I am trying to generate a client webservice for Microsoft Exchange Server from the exchange.wsdl.
While generation I get the following error.
+Incorrect value: XSD-Namensraum http://schemas.microsoft.com/exchange/services/2006/types nicht verfügbar
Exception of class CX_SIDL+
Does anybody knows what this means and how I can fix this to generate the client proxy from the WSDL.
Best regards
Roman

Hi,
Thanks for sharing the doc.
I had followed the steps as mentioned in the doc.
After specifying default mappings(Package name and Root Package Type) , I continued with the creation of Proxy.
When I click on the Finish button I am getting the mentioned error.
I can create proxy if I don't mention the default mappings.
Thakns

Similar Messages

Error in client proxy generation

Hi experts,
                I am trying to consume a web-service from an ABAP progam, to do this I create an Enterprise Service Client Proxy. But creation of the proxy fails with the error message
"Incorrect value: Unknown Namespace http://schemas.xmlsoap.org/soap/encoding/ .
      For client confidentiality issues I cannot put the wsdl file or its content on the thread but I can provide certain details of the code which you might wish to see.
Also my wsdl contains messages with miltiple parts.Is this also a trouble while generating the proxies in ABAP ?
Are these two problems related?
Can I find a link precisely which can provide a kind of checklist to see that these steps have to be followed or these conditions have to be met by wsdl for generation of client proxies in ABAP?
Any pointers will be useful.
Thanks and Regds
Abhishek

Hi Anton,
              I will provide you some piece of the file which might help you in analysing the problem....
<wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:tns="http://www.abc.com"
xmlns:s1="http://www.abc.com/AbstractTypes"
xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
targetNamespace="http://www.abc.com"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    <s:schema targetNamespace="http://www.abc.com/AbstractTypes">
      <s:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
      <s:complexType name="StringArray">
        <s:complexContent mixed="false">
          <s:restriction base="soapenc:Array">
            <s:sequence>
              <s:element minOccurs="0" maxOccurs="unbounded" name="String" type="s:string" />
            </s:sequence>
          </s:restriction>
        </s:complexContent>
      </s:complexType>
    </s:schema>
Similarly the WSDL has messages with multiple parts like:
<wsdl:message name="GetReleasedGenericDrawing2DHttpGetIn">
    <wsdl:part name="DocumentNo" type="s:string" />
    <wsdl:part name="SheetNo" type="s:string" />
    <wsdl:part name="ClassName" type="s:string" />
</wsdl:message>
If you need some ther details from the file please let me know. I have cross checked that it is using a Document/literal style so it should not be a problem.
I have gone through the SAP note (944029) for the list some forbidden keywords which were a problem prior to release of SP 16 .We dont have even that problem.
This thing is very new to me ....please let me know if you wnat some other detail for analysis.
Regads
Abhishek

Client Proxy Generation Error

Hi All,
I have a java web-service deployed in Enterprise Portal which I need to consume in a BSP.
Unfortunately, I'm getting an error on client proxy generation:
Proxy generation terminated: Message must have exactly one part
Is anyone familiar with this? The WSDL file says it has been generated by SAP PORTAL ECLIPSE PLUGINS.
Here is the WSDL file:
<?xml version="1.0" encoding="UTF-8" ?>
- 
- 
- <wsdl:definitions name="xCDRServices" targetNamespace="prt:service:com.sap.xcdr.xCDRServices" xmlns:intf="prt:service:com.sap.xcdr.xCDRServices" xmlns:xsd_doc="prt:service:com.sap.xcdr.xCDRServices/DocumentTypes" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime" xmlns:http="http://schemas.xmlsoap.org/soap/http" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tns0="http://prt.java.soap/schemas" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns2="http://lang.java" xmlns:tns1="http://api.security.sap.com">
- <types>
- <schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="prt:service:com.sap.xcdr.xCDRServices/DocumentTypes" elementFormDefault="qualified">
<element name="checkUserExists_1_param2" nillable="true" type="xsd:string" />
<element name="response_checkUserExists_1" type="xsd:int" />
<element name="getUserRoles_1_param3" nillable="true" type="xsd:string" />
<element name="response_getUserRoles_2" nillable="true" type="xsd:string" />
<element name="getAllRolesInNameSpace_1_param4" nillable="true" type="xsd:string" />
<element name="response_getAllRolesInNameSpace_3" nillable="true" type="xsd:string" />
<element name="assignRoles_2_param5" nillable="true" type="xsd:string" />
<element name="assignRoles_2_param6" nillable="true" type="xsd:string" />
<element name="response_assignRoles_4" nillable="true" type="xsd:string" />
</schema>
- <schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://prt.java.soap/schemas" elementFormDefault="qualified">
- <complexType name="PortalSOAPFault">
- <sequence>
<element name="stackTrace" minOccurs="0" maxOccurs="1" type="xsd:string" />
</sequence>
</complexType>
- <complexType name="UMException">
- <complexContent>
- <extension base="tns0:PortalSOAPFault">
- <sequence>
<element name="LocalizedMessage" nillable="true" type="xsd:string" />
<element name="Message" nillable="true" type="xsd:string" />
<element name="NestedException" type="tns0:Throwable" />
</sequence>
</extension>
</complexContent>
</complexType>
- <complexType name="Throwable">
- <complexContent>
- <extension base="tns0:PortalSOAPFault">
<sequence />
</extension>
</complexContent>
</complexType>
<element name="error_UMException" type="tns0:UMException" />
</schema>
</types>
- <wsdl:message name="assignRolesResponse">
<wsdl:part name="response_assignRoles_4" element="xsd_doc:response_assignRoles_4" />
</wsdl:message>
- <wsdl:message name="checkUserExistsRequest">
<wsdl:part name="checkUserExists_1_param2" element="xsd_doc:checkUserExists_1_param2" />
</wsdl:message>
- <wsdl:message name="checkUserExistsResponse">
<wsdl:part name="response_checkUserExists_1" element="xsd_doc:response_checkUserExists_1" />
</wsdl:message>
- <wsdl:message name="getAllRolesInNameSpaceResponse">
<wsdl:part name="response_getAllRolesInNameSpace_3" element="xsd_doc:response_getAllRolesInNameSpace_3" />
</wsdl:message>
- <wsdl:message name="getAllRolesInNameSpaceRequest">
<wsdl:part name="getAllRolesInNameSpace_1_param4" element="xsd_doc:getAllRolesInNameSpace_1_param4" />
</wsdl:message>
- <wsdl:message name="UMException">
<wsdl:part name="error_UMException" element="tns0:error_UMException" />
</wsdl:message>
- <wsdl:message name="getUserRolesRequest">
<wsdl:part name="getUserRoles_1_param3" element="xsd_doc:getUserRoles_1_param3" />
</wsdl:message>
- <wsdl:message name="assignRolesRequest">
<wsdl:part name="assignRoles_2_param5" element="xsd_doc:assignRoles_2_param5" />
<wsdl:part name="assignRoles_2_param6" element="xsd_doc:assignRoles_2_param6" />
</wsdl:message>
- <wsdl:message name="getUserRolesResponse">
<wsdl:part name="response_getUserRoles_2" element="xsd_doc:response_getUserRoles_2" />
</wsdl:message>
- <wsdl:portType name="xCDRServices">
- <wsdl:operation name="checkUserExists" parameterOrder="checkUserExists_1_param2">
<wsdl:input name="checkUserExists_input0" message="intf:checkUserExistsRequest" />
<wsdl:output name="checkUserExists_output0" message="intf:checkUserExistsResponse" />
</wsdl:operation>
- <wsdl:operation name="getUserRoles" parameterOrder="getUserRoles_1_param3">
<wsdl:input name="getUserRoles_input0" message="intf:getUserRolesRequest" />
<wsdl:output name="getUserRoles_output0" message="intf:getUserRolesResponse" />
<wsdl:fault name="com.sap.security.api.UMException" message="intf:UMException" />
</wsdl:operation>
- <wsdl:operation name="getAllRolesInNameSpace" parameterOrder="getAllRolesInNameSpace_1_param4">
<wsdl:input name="getAllRolesInNameSpace_input0" message="intf:getAllRolesInNameSpaceRequest" />
<wsdl:output name="getAllRolesInNameSpace_output0" message="intf:getAllRolesInNameSpaceResponse" />
<wsdl:fault name="com.sap.security.api.UMException" message="intf:UMException" />
</wsdl:operation>
- <wsdl:operation name="assignRoles" parameterOrder="assignRoles_2_param5 assignRoles_2_param6">
<wsdl:input name="assignRoles_input0" message="intf:assignRolesRequest" />
<wsdl:output name="assignRoles_output0" message="intf:assignRolesResponse" />
<wsdl:fault name="com.sap.security.api.UMException" message="intf:UMException" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="com.sap.portal.prt.soap.xCDRServicesBinding" type="intf:xCDRServices">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="checkUserExists">
<soap:operation soapAction="prt:service:com.sap.xcdr.xCDRServices.xCDRServices/checkUserExists0" />
- <wsdl:input name="checkUserExists_input0">
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output name="checkUserExists_output0">
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
- <wsdl:operation name="getUserRoles">
<soap:operation soapAction="prt:service:com.sap.xcdr.xCDRServices.xCDRServices/getUserRoles0" />
- <wsdl:input name="getUserRoles_input0">
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output name="getUserRoles_output0">
<soap:body use="literal" />
</wsdl:output>
- <wsdl:fault name="com.sap.security.api.UMException">
<soap:fault name="com.sap.security.api.UMException" use="literal" />
</wsdl:fault>
</wsdl:operation>
- <wsdl:operation name="getAllRolesInNameSpace">
<soap:operation soapAction="prt:service:com.sap.xcdr.xCDRServices.xCDRServices/getAllRolesInNameSpace0" />
- <wsdl:input name="getAllRolesInNameSpace_input0">
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output name="getAllRolesInNameSpace_output0">
<soap:body use="literal" />
</wsdl:output>
- <wsdl:fault name="com.sap.security.api.UMException">
<soap:fault name="com.sap.security.api.UMException" use="literal" />
</wsdl:fault>
</wsdl:operation>
- <wsdl:operation name="assignRoles">
<soap:operation soapAction="prt:service:com.sap.xcdr.xCDRServices.xCDRServices/assignRoles0" />
- <wsdl:input name="assignRoles_input0">
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output name="assignRoles_output0">
<soap:body use="literal" />
</wsdl:output>
- <wsdl:fault name="com.sap.security.api.UMException">
<soap:fault name="com.sap.security.api.UMException" use="literal" />
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="xCDRServicesService">
- <wsdl:port name="com.sap.portal.prt.soap.xCDRServices" binding="intf:com.sap.portal.prt.soap.xCDRServicesBinding">
<soap:address location="http://idesportaluss1.phl.sap.corp:1080/irj/servlet/prt/soap/com.sap.portal.prt.soap.xcdrservices?style=doc_lit" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Thanks very much in advance!
Regards,
Roman

By the way, I read a few post about this on SDN, but they didn't offer any solutions, and were from almost a year ago, so I was wondering if there's been any progress.

Error while invoking webservice throu https

Error while invoking webservice throu https://
can any one help me on this topic please:
CODE:
SOAPConnection con = null;
          try{
               String endpoint = "https://wks3089639:4565/Service.serviceagent/PortTypeEndpoint1";
               //String endpoint = "http://wks3101999:5539/Service.serviceagent/PortTypeEndpoint1";
               //String endpoint      = args[0];
               //String soapAction      = args[1];
               System.out.println("javax.net.ssl.keyStore-->"+System.getProperty("javax.net.ssl.trustStore"));
               System.setProperty("javax.net.ssl.trustStore","C:/Documents and Settings/1067555/Desktop/certificates/cer.jks");
               System.setProperty("javax.net.ssl.keyStore","C:/Documents and Settings/1067555/Desktop/certificates/server.keystore");
               System.setProperty("javax.net.ssl.trustStorePassword","password");
               System.setProperty("javax.net.ssl.keyStorePassword","password");
               // use Sun's reference implementation of a URL handler for the     "https" URL protocol type.
               //System.setProperty("java.protocol.handler.pkgs","com.sun.net.ssl.internal.www.protocol");
               // dynamically register sun's ssl provider
               System.setProperty("security.provider","com.sun.net.ssl.internal.ssl.Provider");
               //Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
               System.out.println("javax.net.ssl.trustStore-->"+System.getProperty("javax.net.ssl.trustStore"));
               System.setProperty("javax.net.debug","ssl,handshake");
               SOAPConnectionFactory connectionFactory = SOAPConnectionFactory.newInstance();
               con = connectionFactory.createConnection();
               MessageFactory messageFactory      = MessageFactory.newInstance();
               SOAPMessage message                = messageFactory.createMessage();
               SOAPPart soapPart                     = message.getSOAPPart();
     SOAPEnvelope envelope                = soapPart.getEnvelope();
     SOAPBody body                          = envelope.getBody();
//     MimeHeaders headers = message.getMimeHeaders();
//     headers.addHeader("SOAPAction", soapAction);
//     headers.addHeader("SOAPAction", "/Service.serviceagent/PortTypeEndpoint1/Operation");
//     headers.addHeader("Content-Type","text/xml");
//     headers.addHeader("charset","utf-8");
     MimeHeaders headers = message.getMimeHeaders();
     headers.addHeader("SOAPAction", "/Service.serviceagent/PortTypeEndpoint1/sampleOperation");
     headers.addHeader("Content-Type","text/xml");
     headers.addHeader("charset","utf-8");
     StreamSource inputmsg = new StreamSource(new FileInputStream("client.wsdl"));
     soapPart.setContent(inputmsg);
     System.out.println("REQUEST:\n");
     message.writeTo(System.out);
     System.out.println();
     message.saveChanges();
     SOAPMessage reply = con.call(message, new URL(endpoint));
     System.out.println("RESPONSE:\n"+reply.toString());
     System.out.println("Header:::"+reply.getSOAPHeader());
     System.out.println("Body:::"+reply.getSOAPBody());
     System.out.println("RESPONSE:\n");
     TransformerFactory transformerFactory      = TransformerFactory.newInstance();
     Transformer transformer                     = transformerFactory.newTransformer();
     //Extract the content of the reply
     Source responseContent                          = reply.getSOAPPart().getContent();
     //Set the output for the transformation
     StreamResult result = new StreamResult(System.out);
     transformer.transform(responseContent, result);
     System.out.println();
          }catch(Exception e){
               e.printStackTrace();
          finally{
               con.close();
Exception:
10-Nov-2008 11:55:04 com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection post
SEVERE: SAAJ0009: Message send failed
com.sun.xml.messaging.saaj.SOAPExceptionImpl: java.security.PrivilegedActionException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
     at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:127)
     at com.Sample.main(Sample.java:91)
Caused by: java.security.PrivilegedActionException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:121)
     ... 1 more
Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
     at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:325)
     at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:150)
     ... 3 more
Caused by: java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(Unknown Source)
     at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
     at java.net.PlainSocketImpl.connect(Unknown Source)
     at java.net.Socket.connect(Unknown Source)
     at java.net.Socket.connect(Unknown Source)
     at sun.net.NetworkClient.doConnect(Unknown Source)
     at sun.net.www.http.HttpClient.openServer(Unknown Source)
     at sun.net.www.http.HttpClient.openServer(Unknown Source)
     at sun.net.www.protocol.https.HttpsClient.<init>(Unknown Source)
     at sun.net.www.protocol.https.HttpsClient.New(Unknown Source)
     at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(Unknown Source)
     at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
     at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
     at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
     at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(Unknown Source)
     at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:282)
     ... 4 more
CAUSE:
java.security.PrivilegedActionException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:121)
     at com.Sample.main(Sample.java:91)
Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
     at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:325)
     at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:150)
     ... 3 more
Caused by: java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(Unknown Source)
     at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
     at java.net.PlainSocketImpl.connect(Unknown Source)
     at java.net.Socket.connect(Unknown Source)
     at java.net.Socket.connect(Unknown Source)
     at sun.net.NetworkClient.doConnect(Unknown Source)
     at sun.net.www.http.HttpClient.openServer(Unknown Source)
     at sun.net.www.http.HttpClient.openServer(Unknown Source)
     at sun.net.www.protocol.https.HttpsClient.<init>(Unknown Source)
     at sun.net.www.protocol.https.HttpsClient.New(Unknown Source)
     at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(Unknown Source)
     at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
     at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
     at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
     at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(Unknown Source)
     at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:282)
     ... 4 more
CAUSE:
java.security.PrivilegedActionException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:121)
     at com.Sample.main(Sample.java:91)
Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
     at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:325)
     at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:150)
     ... 3 more
Caused by: java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(Unknown Source)
     at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
     at java.net.PlainSocketImpl.connect(Unknown Source)
     at java.net.Socket.connect(Unknown Source)
     at java.net.Socket.connect(Unknown Source)
     at sun.net.NetworkClient.doConnect(Unknown Source)
     at sun.net.www.http.HttpClient.openServer(Unknown Source)
     at sun.net.www.http.HttpClient.openServer(Unknown Source)
     at sun.net.www.protocol.https.HttpsClient.<init>(Unknown Source)
     at sun.net.www.protocol.https.HttpsClient.New(Unknown Source)
     at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(Unknown Source)
     at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
     at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
     at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
     at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(Unknown Source)
     at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:282)
     ... 4 more
Edited by: javausers07 on Nov 10, 2008 11:58 AM

I hope the sun forum can help for me. Lets see

Error while generating webservices using Date

I am facing the following problem while generating a web service which is having Date as one its members.
I have serialized a class with the following DataStructure
private String rowId1;
private Date created;
private String name;
private String quoteNum;
private String revNum;
private String curcyCd;
private String activeFlg;
private Number discntAmt;
private Number discntPercent;
When i tried to expose this as webservice, If I use the class oracle.jbo.domain.Date for Date type, the webservice is not generated properly. It is not including the method which contains this call. ie) This method is not present in the WSDL file as well as in the proxy.
When I used java.util.Date instead of oracle.jbo.domain.Date, I am able to expose the method and webservice got generated properly. But When i tried to generate the proxy for the WSDL in the consumer, I go the following error.
oracle.jdeveloper.webservices.model.GenerationException: Proxy generation failed for the following reason:
     at oracle.jdeveloper.webservices.model.proxy.ProxyGenerator.doGeneration(ProxyGenerator.java:608)
     at oracle.jdeveloper.webservices.model.proxy.ProxyGenerator.generateImpl(ProxyGenerator.java:365)
     at oracle.jdeveloper.webservices.model.proxy.ProxyGenerator.mav$generateImpl(ProxyGenerator.java:77)
     at oracle.jdeveloper.webservices.model.proxy.ProxyGenerator$1ThrowingRunnable.run(ProxyGenerator.java:206)
     at oracle.jdeveloper.webservices.model.GeneratorUI$GeneratorAction.run(GeneratorUI.java:446)
     at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:551)
     at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.RuntimeException: generator error: no encoder for type "{http://www.w3.org/2001/XMLSchema}dateTime" and Java type "java.lang.String"
     at oracle.j2ee.ws.common.processor.Processor.runActions(Processor.java:105)
     at oracle.j2ee.ws.tools.wsa.AssemblerTool.run(AssemblerTool.java:99)
     at oracle.j2ee.ws.tools.wsa.WsdlToJavaTool.createProxy(WsdlToJavaTool.java:354)
     at oracle.j2ee.ws.tools.wsa.Util.createProxy(Util.java:838)
     at oracle.jdeveloper.webservices.model.proxy.ProxyGenerator.doGeneration(ProxyGenerator.java:549)
     ... 6 more
Caused by: generator error: no encoder for type "{http://www.w3.org/2001/XMLSchema}dateTime" and Java type "java.lang.String"
     at oracle.j2ee.ws.common.processor.generator.GeneratorBase.doGeneration(GeneratorBase.java:181)
     at oracle.j2ee.ws.common.processor.generator.GeneratorBase.perform(GeneratorBase.java:137)
     at oracle.j2ee.ws.common.processor.Processor.runActions(Processor.java:97)
     ... 10 more
I am referring to "Entity and view objects based on web service " in the following URL
http://radio.weblogs.com/0118231/stories/2004/09/23/notYetDocumentedAdfSampleApplications.html#93
Thanks and Regards,
James

Hi all,
I have applied the consolidated JRI fixes - patch 17191279 .
Then, when generating Jar, received keypass is tampered error.
re-generated the key using $ adjkey -initialize.
Now, its working fine.
Regards,
Krish.

Error while invoking webservice using UTL_HTTP from PL/SQL Block

Hi All,
I am invoking a webservice (SOAP Request) from a PL/SQL block using UTL_HTTP package.
I am able to send the complete request and am getting the required instance on the BPEL Console, but the process is erroring out while getting response back.
and the PL/SQL Block is ending in error mentioned below:
ERROR at line 1:
ORA-29266: end-of-body reached
ORA-06512: at "SYS.UTL_HTTP", line 1321
ORA-06512: at "APPS.CSM_BPEL_TEST_PKG", line 34
ORA-06512: at line 1
Package is completing successfully if i test in local DB and local BPEL.
But giving above error in client's.
Can anyone let me know what is the cause of this.
Thanks in advance

I got it working by making process Synchronous.
But with asynchronous process it is still same error.
Thanks...

ABAP Web Service client proxy - generation problems

Hi!
I tried to create an ABAP web service client proxy for many different web services -
for instance some of that listed at <a href="http://www.xmethods.net/">http://www.xmethods.net/</a> .
Almost on 99% of the WSDLs the client proxy generation failed.
For istance "<extension> not supported", or "<message...> must have at least one part",... .
Could anybody tell me what restrictions are to web services you can create a
ABAP client proxy for ?
In the SAP Web AS Java Stack there is no problem at all to generate a
client proxy for almost all of the xmethod-WebServices !
Is the ABAP Web Service proxy generation for production use ?
Regards
Frank Ruggaber

Resolved through SAP Help. Refer SAP note# 0001403271.

An Error Occurred during CHART Generation in BI Launch Pad 4.0

Hi Guys,
I am creating a report on BI launch Pad, the query result shows fine in the "Table" format but when i "Turn Into" chart it gives me an error " An Error Occurred During chart generation, The chart cannot be displayed".
I created the same report in Rich Client and everything is working fine but on the portal the charts cannot be displayed.
Let me know if anyone has faced this error or has any solution for it.
Thanks in Advance,
Sheikh Hassan Ayub

try the following:
1) We created a new Adaptive Processing server by stopping the existing one.
2) Enabled and Started the new server.
3) And now you were successfully able to Create, Open and Modify any web Intelligence reports in BI Launchpad.
It worked for me.
But the problem is that i had to re create the charts in BI launch pad, the old charts didnt work.
If you have any other solution let me know.
Sheikh Hassan Ayub

Error: C:\jdev10134\webservices\lib\jaxb-impl.jar The system cannot find..

In jdeveloper 10.1.3.4, I created a new synchronous BPEL project, then connected to my db and selected a package and did the right-click, create a web service from it. Now that I compile the project it returns this error:
Error: C:\jdev10134\webservices\lib\jaxb-impl.jar (The system cannot find the file specified)
Do I need to add something to jdeveloper to allow it to compile web services?
Thanks,
Edited by: srollins on Aug 21, 2009 12:42 PM

Creating a WS client in a BPEL project breaks BPEL compilatiopn, that's easy to reproduce.
I dont' know how you can fix this without getting rid of the WS client, but if you want to keep the BPEL and are happy to remove the WS client, then proceed as follows:
- delete the src directory
- remove the "oracle.jdevimpl.config.JProjectLibraries" and "ownerMap" sections in the *.jpr.
- restart JDev
After this you should be able to compile the BPEL again.

Getting Error :Error when instantiating WebService runtime

Hello All,
I am a new to Webservices and writing a test program .I am using the ECC 5.0 .I am calling a Webservice from R/3 .I am trying to call this webservice :[http://webservices.daehosting.com/services/isbnservice.wso?WSDL].
I am getting the following exception
{<?xml version="1.0" encoding="utf-8" ?>
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
- <asx:values>
<SYSTEMFAULT href="#o68" />
</asx:values>
- <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">
- <cls:CX_AI_SYSTEM_FAULT id="o68">
- <CX_ROOT>
<TEXTID>F63AFF63DBE4BB4786A7F52CC4167145</TEXTID>
<PREVIOUS href="#o55" />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>191</PROGID>
<CONTID>558</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_STATIC_CHECK />
- <CX_AI_SYSTEM_FAULT>
<CODECONTEXT>Local</CODECONTEXT>
<CODE>ERROR_WEBSERVICE_RUNTIME_INIT</CODE>
<ERRORTEXT>Error when instantiating WebService runtime (Error when initializing SOAP client application )</ERRORTEXT>
<LANGUAGE />
</CX_AI_SYSTEM_FAULT>
</cls:CX_AI_SYSTEM_FAULT>
- <cls:CX_XMS_SYSERR_PROXY id="o55">
- <CX_ROOT>
<TEXTID>3F829CAF9A45633CE10000000A155117</TEXTID>
<PREVIOUS />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>0</PROGID>
<CONTID>0</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_STATIC_CHECK />
- <CX_XMS_SYSTEM_ERROR>
<ID>ERROR_WEBSERVICE_RUNTIME_INIT</ID>
<P1>Error when initializing SOAP client application</P1>
<P2 />
<P3 />
<P4 />
<INFO />
<CATEGORY>XIProxy</CATEGORY>
<AREA>ABAP</AREA>
<RETRY>M</RETRY>
</CX_XMS_SYSTEM_ERROR>
- <CX_XMS_SYSERR_PROXY>
<CO_AREA_ABAP>ABAP</CO_AREA_ABAP>
</CX_XMS_SYSERR_PROXY>
</cls:CX_XMS_SYSERR_PROXY>
</asx:heap>
</asx:abap>}
This is what i have given in LPCONFIG Tcode
LPCONFIG->General setting-> Call parameters->
URL->http://webservices.daehosting.com/services/isbnservice.wso?WSDL
Please help out what I am missing here
Thanks
Krishna

I had the same error, while implementing a new client webservice.
The Error ERROR_WEBSERVICE_RUNTIME_INIT was in my case solved by:
1. regenerating the CL_SOAP_APPLICATION_CLIENT class.
and
2. deleting the LPCONFIG setting and creating a new one.
Edwin.

Error: C:\jdevstudio10133\webservices\lib\jaxr_api.jar

Hi all,
I newly creating asynchronous web service using jdeveloper editor and then bpel process with pl/sql web service but my system given following error
Error: C:\jdevstudio10133\webservices\lib\jaxr_api.jar (The system cannot find the file specified)
any bodies know how solve this problem i need jaxr_api, jaxr_impl jar files how can download this files.

Creating a WS client in a BPEL project breaks BPEL compilatiopn, that's easy to reproduce.
I dont' know how you can fix this without getting rid of the WS client, but if you want to keep the BPEL and are happy to remove the WS client, then proceed as follows:
- delete the src directory
- remove the "oracle.jdevimpl.config.JProjectLibraries" and "ownerMap" sections in the *.jpr.
- restart JDev
After this you should be able to compile the BPEL again.

Migration from 2003 - 2010, OAB errors on client, and OAB virtual directory does not contain any files.

Migration from 2003 - 2010, OAB errors on client, and OAB virtual directory does not contain any files.

Hi,
Please re-create the Outlook profile to have a try. If the issue persists, we can do the further checks in Exchange server.
Please make sure you have changed the OAB generation server to Exchange 2010 and enable Web distribution on the Exchange 2010 Client Access server:
Move-OfflineAddressBook "Default Offline Address List" -Server <MBX2010>
If all configurations are correct, please check whether there is any folder in the following path in Exchange sever 2010:
a. OAB generation in Mailbox:
\\Program Files\Microsoft\Exchange Server\V14\ExchangeOAB
b. OAB distribution in Client Access:
\\Program Files\Microsoft\Exchange Server\V14\ClientAccess\OAB
Thanks,
Winnie Liang
TechNet Community Support

Getting error"Broker Client is no longer connected to the Broker Host"

HI Guruu2019s,
I'm trying to featch Data from SAP using IDOCs in Real Time Job. I have configured Real-time service ,Client Interface and RFC details successfully .also I start my Real-time service, it is showing green symble -" Weating for Idocs "
when start Idoc process from SAP system ,I'm getting below Error-
*"Broker Client is no longer connected to the Broker Host AGLSAPSBXARDDB1:4000"
Pls-2 give me the solution where is the problem -in sap side or BODS side and I hope you should have some solution
I'm doing wait for your response.
Thanks & Regards,
Rajeev kumar
SAP-BODS Developer

Greetings cdewinkel,
It seems your iPad is not staying connected to your computer during syncing. The following article provides a number of troubleshooting steps which may help. This article is intended for devices which are not being detected, but the troubleshooting steps are relevant to your issue:
If you don't see your connected device in iTunes for Mac - Apple Support
Make sure that your device is on
Also make sure that you can get to the Home screen.
Get help if you have one of these issues:
Your iOS device won't respond or turn on.
Your iPod won't turn on.
You forgot your passcode or your device is disabled.
Make sure that your Mac supports your device
See the system requirements for iPhone, iPad, or iPod.Check your USB connections
Unplug other USB devices from your Mac and try again.
Try a different USB port.
Try a different USB cable.
Learn more about using USB cables with your Mac.Make sure that your device trusts the computer
You might get an alert if you haven't connected your iOS device to this computer before. Unlock your device and tap Trust.
Learn more about the Trust This Computer alert.Restart your device
Restart your iOS device or reset your iPod.Restart your Mac
Turn your Mac off and back on.Update your software
Check for software updates on your Mac.
Check for an iTunes update.
Check your security software
If you have security software installed, learn how to resolve issues between iTunes and your security software.
Get more help
If you still don't see your device in iTunes, contact Apple Support.
Thank you for contributing to Apple Support Communities.
Best,
Bobby_D

Errors while invoking webservice

I am getting below error while invoking webservice in jdev:
<env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>Failure in SDOSerializer.deserialize.</faultstring>
</env:Fault>
</env:Body>
</env:Envelope>
I can see only below log in jdev server log :
<oracle.adf.model> <SDOHelper> <findHelperContext> <SDOHelperContext identified by {http://xmlns.oracle.com/apps/projects/projectManagement/common/projectServiceV2/}ProjectService has not been defined yet!>
<oracle.adf.model> <SDOHelper> <findHelperContext> <SDOHelperContext identified by {http://xmlns.oracle.com/apps/projects/projectManagement/common/projectServiceV2/}ProjectService has not been defined yet!>
could anybody help me to understand what gone wrong ?

This thread might help you:
Problems invoke Web Service

InvalidSecurity Error while accessing Webservice

Hi,
I am getting an "*InvalidSecurity*" error while accessing webservice.
Below is the error, which I got while invoking the webservice :
<env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault
xmlns:ns0="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<faultcode>ns0:InvalidSecurity</faultcode>
<faultstring>InvalidSecurity : error in processing the WS-Security security header</faultstring>
<faultactor/>
</env:Fault>
</env:Body>
</env:Envelope>
Thanks
Abheek
Edited by: 1005832 on May 14, 2013 6:16 AM

The error was generated on the endpoint and indicates that the SOAP request message had incorrect WS-Security information in its headers. The SOAP response message you included doesn't contain specific information about what is wrong (we wouldn't want to reveal too much to hackers, of course!).
Without seeing the SOAP request message and the WS-SecurityPolicy that the endpoint requires, it's impossible to tell what's wrong.
Other important information:
- what version of WLS are you running?
- is the endpoint a WLS JAX-WS or a WLS JAX-RPC web service?
- is WS-Security configured using native WLS WS-Security (e.g. @Policy) or using OWSM WS-Security (i.e. @SecurityPolicy)?
- what specific policy is being used to enforce security at the endpoint (the advertised WSDL for the endpoint should contain this)

Error on Client WebService generation

Similar Messages

Maybe you are looking for