Reg: Generating Proxy for a Schema exposed as a WCF sevice

Hello All,
I have worked on number of project and I never come across such problem. Lemme explain the situation:
1) Exposed Schema as a WCF service (https:// endpoint)
2) I am able to browse the service and also view the metadata.
3) When I try to do add service reference in my .Net project, am getting the following error:
The document at the url "" was
not recognized as a known document type.
The error message from each known type may help you fix the problem:
- Report from 'XML Schema' is 'The document format is not recognized (the
content type is 'text/html; charset=UTF-8').'.
- Report from ''My EndPoint''
is 'The document format is not recognized (the content type is 'text/html;
charset=UTF-8').'.
- Report from 'DISCO Document' is 'There was an error downloading ''My EndPoint''.'.
  - The underlying connection was closed: An unexpected error
occurred on a send.
  - Unable to read data from the transport connection: An existing
connection was forcibly closed by the remote host.
  - An existing connection was forcibly closed by the remote host
- Report from 'WSDL Document' is 'The document format is not recognized (the
content type is 'text/html; charset=UTF-8').'.
Metadata contains a reference that cannot be resolved: 'My EndPoint'.
The HTTP request was forbidden with client authentication scheme 'Anonymous'.
The remote server returned an error: (403) Forbidden.
If the service is defined in the current solution, try building the solution
and adding the service reference again.
In the receive location, I am using transport and client certificate as windows.
At the IIS level, I have the certificate assigned for the site SSL and in the web.config I have authentication mode as Windows.
Am not sure what am I missing.
Thanks, SKGuru

It didn't work for me. Actually I am using the host name. There is no problem with the service as I can browse and see the WSDL. The only problem is I am not able to generate proxy out of it using svcutil.exe.
Thanks, SKGuru

Similar Messages

Reg : Generating Bills for an Account

Dear All,
I'm new to OUCCB.
I want to generate bills for person/account.
Could someone share the list of setups required to perform this?
Any detailed step by step documentation available would help..
Thanks,
Shyam

Hi,
After you have created the person and account you need to install a meter at the premise after installing the meter you need to add a meter read after the meter read you can create the bill.

Creation of client proxy for a WSDL with 2 port types??

Hi,
I am trying to consume an external web service from SAP - ECC6.0. The WSDL file has 2 porttype definitions - one for i/p and one for o/p
When I proceed with SE80 to create a client proxy, it asks me to select any one port type to generate the client proxy. If I select only the input port, it generates proxy for the input port alone.
In this scenario, how do I create proxies and configure logical ports, and call it from a single program to invoke the whole web servie with both i/p and o/p?
TIA,
Regards
Deepthi

Hi,
i. Import your message schemas from external definitions, or RFCs or IDocs from SAP systems. These definitions already contain data types.
ii. Create a message interface and reference the messages of the external definition, or the RFC or IDoc message.
Check this, it may help you
http://help.sap.com/saphelp_nw04/helpdata/en/3f/01623c4f69b712e10000000a114084/content.htm
REgards
Seshagiri

Generating proxy from wsdl ends in error

Our sap installation is 'SAP ECC 6.0' and I'm trying to generate proxy (for testing purposes) from se80 by using url: http://cheeso.members.winisp.net/books/books.asmx?WSDL
Proxy generationg is cancelled by the system and I get message in se80 saying:
'Exception occurred in library handler
Not implemented'
This was working earlier on our system (older sap release) and I also tested this on other sap (SAP ERP Central Component 5.0) and it works.
Does anyone have an idea, what is wrong?

I am facing the same problem.
Take a look at
https://websmp130.sap-ag.de/sap(bD1lcyZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=748781
https://websmp130.sap-ag.de/sap(bD1lcyZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=809792
They correspond to : note 748781 and 809792 in SAP Service Marketplace
The XML format for proxy generation : note 944029
I hope it helps you.

Supressing the JAXB code for Extended Schemas using JWSDP

Hi,
Im trying to generate the JAXB code for the XML Schema using JWSDP using ANT build tool.
Q : My schema(eg., Schema01.xsd) extends other two schemas(Schema02.xsd, Schema03.xsd).Here using JWSDP package using ANT Build tool, i want to Generate the JAXB java classes only for Schema01.xsd not for other two schemas.
Can somebody help in this regard.
Note : By default using JWSDP, Ant build tool, in "Build.xml" it expects schema name(eg. Schema01.xsd"). when i generate the java code, it generates code for the Schema and as well as its all exetended schemas.
Q : how can supress generating the java code for the extended schemas.
Regards
Madhu

Hi, no I didn't notice this, tried it now and got
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><metadata xmlns="http://musicbrainz.org/ns/mmd-1.0#"><artist-list offset="0" count="1"><artist type="Group" id="ccd4879c-5e88-4385-b131-bf65296bf245" ext:score="100" xmlns:ext="http://musicbrainz.org/ns/ext#"><name>Echo & The Bunnymen</name><sort-name>Echo & The Bunnymen</sort-name><life-span begin="1978"/></artist></artist-list></metadata>is this right, its different to what I was originally trying to get

Best Practice for WSDL Generate Proxy Class for Web Service with Two Versions

Dear All
Thank you in advance for you help.
I would like to generate proxy classes for same function but with two versions.
Old version web service (v23.2) is used for stable modules in a project which is not going to modify.
However, enhancement is added in new version web service (v24) and is going to use in any future modules.
For example,
wsdl.exe -o="TestProxy.cs" -l:CS -n:Test -sharetypes https://community.workday.com/custom/developer/API/Notification/v23.2/Notification.wsdl https://community.workday.com/custom/developer/API/Notification/v24.0/Notification.wsdl
It generates similar classes with an '1' added at the end of the class name.
ublic partial class Event_TargetObjectType {
private Event_TargetObjectIDType[] idField;
public partial class Event_TargetObjectType1 {
private Event_TargetObjectIDType1[] idField; ...}
Since the function inside some class is the same, is it possible for WSDL.exe to generate proxy classes automatically that if the class is the same, then generate one class only (sameFunction()) but if it detects the class is different, then add '1'
to the end of class name (differentFunction() and differentFunction1())
i.e.
public class sameFunction()
public class differentFunction()
private int a;}
public class differentFunction1()
{ private int b;
Best Regards
mintssoul

Hi mintssoul,
As per this case, I have shared corresponding details below :
1.As far as I know, WCF doesn’t support method overloading directly
2.Because WSDL doesn’t support method overloading (not OOPs).
3.WCF generates WSDL which specifies the location of the service and the operation or methods the service exposes.
4.WCF use Document/Literal WSDL Style : Microsoft proposed this standard where the soap body element will contain the web method name.
5.By default all the WCF services conform to the document literal standard where the soap body should include the method name.
6.but you can differ the method in the same manually by using Name attribute like below
For example:
    [OperationContract(Name="Integers")]
    int Display(int a,int b)
    [OperationContract(Name="Doubles")]
double Display(double a,double b)
7. Or I suggest you that can use svcutil to map multiple namespaces for generating wcf service proxies .
    for more information about this, refer here :
http://stackoverflow.com/questions/1103686/use-svcutil-to-map-multiple-namespaces-for-generating-wcf-service-proxies

Compilation Error for import classes not found in generated Proxy Class

Hi,
We are generating java classes for the COM dll using JCOM com2java compiler.
We are getting a compilation error for import class not found when compiling the
generated Proxy java source code. It can't find the com.bea.jcom.Dispatch class that
the generated Proxy java source code extends. It also can't find com.bea.jcom.Variant
or com.bea.jcom.Param. These are interfaces or data types or classes used by COM
library.
I added weblogic.jar to my class path and the only Dispatch class i found inside
the weblogic.jar is com.linar.jintegra.Dispatch;
We have com objects for which we want to develop an EJB client to interface with
the COM object using JCOM with Native Mode disabled.
Any help on the compilation error..I tried changing the extends for Dispatch to com.linar.jintegra.Dispatch
but the other errors are still there.
To begin with, I think the generated code should not refer to any of the COM data
types.
Any help please.
Thank you in advance,
Regards,
Rahul Srivastava
[email protected]

Hi,
I resolved the other errors by changing all references from com.bea.jcom.Variant
etc to com.linar.jintegra.class name..all were present under the com.linar.jintegra
package.
Thank you all anyways,
Regards,
rahul
"Rahul Srivastava" <[email protected]> wrote:
>
Hi,
We are generating java classes for the COM dll using JCOM com2java compiler.
We are getting a compilation error for import class not found when compiling
the
generated Proxy java source code. It can't find the com.bea.jcom.Dispatch
class that
the generated Proxy java source code extends. It also can't find com.bea.jcom.Variant
or com.bea.jcom.Param. These are interfaces or data types or classes used
by COM
library.
I added weblogic.jar to my class path and the only Dispatch class i found
inside
the weblogic.jar is com.linar.jintegra.Dispatch;
We have com objects for which we want to develop an EJB client to interface
with
the COM object using JCOM with Native Mode disabled.
Any help on the compilation error..I tried changing the extends for Dispatch
to com.linar.jintegra.Dispatch
but the other errors are still there.
To begin with, I think the generated code should not refer to any of the
COM data
types.
Any help please.
Thank you in advance,
Regards,
Rahul Srivastava
[email protected]

Generating consumer proxy for a webservice generated from a BAPI

Hello gurus,
I'm having some kind of troubles when I try to generate a a consumer proxy for a service that I have created from an existing BAPI.
First of all, I have activated the service in tx SICF, I've assigned an endpoint from the Tx SOAMANAGER, and I can check the
correct work of the webservice from the wsnavigator, but the developerst still can't use it from the visual studio.
I was browsing help.sap.com and I found that I need to generate a consumer proxy and this must be linked with a logical port.
So I was trying to generate the consumer proxy, but I can't do it because I can't find the service in the Tx SE80.
How can I generate the consumer proxy?
Best regards.
Juanfra.

Sorry, but I was confused because what I had to do was generate a consumer proxy fro the user that will use the webservice.
Best regards
Juanfra

Namespace Error when generating Client Proxy for Java Web Service

Hi.Experts:
    When I want to generating a Client Proxy for my WSDL file created by JAVA,it seems that some namespace errors occur.
    The error like this:
    "Incorrect value: Unknown Namespace http://sql.java
    Exception of class CX_SLIB "
   I checked all the SOAP runtime,it seems no error.So do I need to create the objects in the Integration Repository??If it is the truth,then how can I do it.
Best Regards
Martin Xie

Hi Martin
I didn't find this options in SAP GUI Create -->Enterprise Service ->Consumer Service ->url/http
Maybe my version is different.
You say that you can select the file ou url.
Did you select the file or url?
If was file, open this file, find the tag that you have the wrong namespace and eliminate this tag.
If was url, access this url, copy the xml and same in one file, then select this file in the step above.
I don't know if works, its only a suggestion.
regards
Marcos

How to generate XSD file for XML schema adobe form

Hi,
I want to generate XSD file for XML schema interfaces adobe forms. How can I do it. Where I can do it..or who will provide this file..
Thanks
Ram
Edited by: Ramesh ram on Feb 23, 2010 6:33 PM

Aaaaah, my mistake, sorry for that. Of course you should use the XML interface and I forgot it is not described in this tutorial. You can easily find another one where the XML based interface is used. But... you won´t need any tutorial. just create a WD context. Place a Interactive form element on your WD app screen, in the attributes you need to maintain the form template name. If you write a name suitable for you which no existing forms uses, the system will offer you to generate a XML based interface and right after that it will "send" you to the SFP transaction. That means you can like skipi the step defining the interface because it it is generated automatically and you only draw the layout for this generated interface.
You should use XMl based interface for your WD app, because when using the ABAP dic based, some features are not available (I am not sure, but ABAP based works only for print form or something).
Hope it is all clear now,
have a nice day,
Otto

Error while creating a deployable proxy for a URL in NWDS

Hi ,
There is a requirement for calling a webservice in the .NET platform from JAVA using NWDS. The webservice of the server is pinged using the URL of the webservice. when the URL is passed in the WS navigator of CRD ( that is Development Server) , the response is retreived successfully . The version of NWDS is 7.0.23.
we are facing problem when we are trying to create a Deployable proxy in NWDS by using the following steps :
1) Create a Development Component
2) Select the Deployable Proxy
3) Create the Client Proxy Defintion of the created DC
At step 3 , when we giving the url or WSDL link like "http:// www3.authoring.syngenta/newswebservice.asmx?WSDL" (this is just for example) , it is showing as "Invalid wsdl or wsdl not found " . so that we are not able to procees further.
When we are trying to create proxy the for the WSDL link like " http:// www.authoring.syngenta/newswebservice.asmx?WSDL" , we are able to create successfully.
can anyone suggest why we are able to create the proxy for the URL "http:// www.authoring.syngenta/newswebservice.asmx?WSDL" and not for the other URL.
Any pointers or suggestions are very helpful.
Thanks and Regards,
Sreedevi

Late response I know, but I have solved a similar problem recently and thought I would share.
Firstly, the problem is not with the namespace. The "Namespace ..." part is just stating the namespace the "Incorrect Value" has. So this error is complaining about the value "Unknown" - which isn't very helpful.
It appears the SAP SE80 importer does not like elements like the following because it can't understand <s:element ref="s:schema" />. It appears this is a common thing to be included in .NET generated WSDLs.
<s:element minOccurs="0" maxOccurs="1" name="GetCursDynamicResult">      <s:complexType>          <s:sequence>               <s:element ref="s:schema" />               <s:any />          </s:sequence>     </s:complexType></s:element>
SAP will also not like this example as it does not support mixed content (see: http://www.w3schools.com/schema/schema_complex_mixed.asp)
<s:element minOccurs="0" maxOccurs="1" name="SaldoXMLResult">
     <s:complexType mixed="true">
          <s:sequence>
               <s:any />
          </s:sequence>
     </s:complexType>
</s:element>
You can "Fix" the problem in both cases by removing the offending text in a local copy of the WSDL file so remove line 4 in the first example and change line 2 in the second to <s:complexType> the proxy can then be generated. No idea if the resulting service will be fully operational though!

Unable to locate Spring NamespaceHandler for XML schema namespace

I am not sure if this is the best practice approach but this is the problem I am ruining into. Below, I explain what I am doing:
1) What I am doing:
=============
Based on the oracle incubator example (http://coherence.oracle.com/display/INCUBATOR/Processing+Pattern+Examples); I am running a server and submitting tasks through a proxy application that submits them to ProcessingPatternConfigurator; let's call my task processReport.
a) my processReport is using spring and ibatis together, I created a utility static class to obtain a spring context and retrieves beans using the following lines ( see exhibit "A1 and A2" below).
b) when my task calls the context and that spring loads, it is failing with the error show in exhibit "B".
I suspect I am missing a lib? I googled the error and searched you site but could find a meaningful discussion on it. I guess my question is if this is not the best approach, how do I integrated with spring initializing beans and setting up ibatis framwork, providing beans and database access through Ibatis for each task ruining on the grid (processReport).
thanks
A1) processReport (submitted in the grid) uses this line
AbstractXmlApplicationContext ctx = (AbstractXmlApplicationContext) AmrContextUtil.getInstance();
          System.out.println("Classpath loaded. Executing Report...");
          ReportProcessor repProcessor = (ReportProcessor) ctx.getBean("reportProcessor");
A2) Here is the AmrContextUtil:
import org.springframework.context.support.AbstractApplicationContext;
import org.springframework.context.support.ClassPathXmlApplicationContext;
public final class AmrContextUtil {
     private static AbstractApplicationContext ctx = null;
     public AmrContextUtil() {
          super();
     public final static synchronized AbstractApplicationContext getInstance(){
          if (ctx == null){
               ctx = new ClassPathXmlApplicationContext("classpath:config/applicationContext.xml");
               setCtx(ctx);
          return ctx;
     public final static synchronized AbstractApplicationContext getCtx() {
          return ctx;
     public final static synchronized void setCtx(AbstractApplicationContext ctx) {
          AmrContextUtil.ctx = ctx;
B) Here is the error reported by the server:
2010-02-10 15:42:28.312/57.986 Oracle Coherence GE 3.5.2/463 <Warning> (thread=GridExecutor:Thread-2
, member=1): TaskRunner - Failed to process 0x00000126B99E5524AC1F007AAB1587BBCFEC5E6637E1DED6CCB984
03D6AADF4D due to:org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Failed to import bean definitions from URL location [classpath:config/reports-application.xml] Offending resource: class path resource [config/applicationContext.xml]; nested exception is org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Unexpected failure during bean definition parsing
Offending resource: class path resource [config/reports-application.xml] Bean 'reportSqlMapConfig'; nested exception is org.springframework.beans.factory.parsing.BeanDefinitionParsingException: *Configuration problem: Unable to locate Spring NamespaceHandler for XML schema namespace [http://www.springframework.org/schema/util]*
*Offending resource: class path resource [config/reports-application.xml] Bean 'reportSqlMapConfig'*
-> Property 'resourceMap'
c)Here is my application-context.xml offending line:
<bean id="reportSqlMapConfig"
class="com.xx.report.generator.ReportSqlMapConfig">
<property name="resourceMap">
<map>
<entry>
<key>
<util:constant static-field="com.xx.report.domain.ReportType.FPA"/>
</key>
<value>classpath:config/diehardReportSqlMapConfig.xml</value>
</entry>
<entry>
<key>
<util:constant static-field="com.xx.report.domain.ReportType.FCN"/>
</key>
<value>classpath:config/falconReportSqlMapConfig.xml</value>
</entry>
<entry>
<key>
<util:constant static-field="com.xx.report.domain.ReportType.ODS"/>
</key>
<value>classpath:config/odsReportSqlMapConfig.xml</value>
</entry>
</map>
</property>
</bean>

My guess is that something is broken in the configuration of the cacheServer and its not finding
all of the dependencies that your process pattern application needs. Probably the best way
to debug this stuff is to define a static main in your runnable task which will make the call
to the run() method and invoke it as the main class using the identical settings (classpath,
run directory) that you are using to launch the Coherence cache server.
Regards,
Bob

Problem in creating a java proxy for PHP web service

This is a problem in generating a java proxy for a PHP webservice.
I have a PHP service running on Wamp Server and also a PHP client which is able to call the service.
The WSDL for the PHP web service is also generated .
I am trying to create a java proxy using the jdev (10.1.3.0.3) from the wsdl file.
The wsdl generated by the php program is
<?xml version="1.0" encoding="ISO-8859-1" ?>
<definitions xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:si="http://soapinterop.org/xsd" xmlns:tns="urn:hellowsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="urn:hellowsdl">
<types>
<xsd:schema targetNamespace="urn:hellowsdl">
<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
<xsd:import namespace="http://schemas.xmlsoap.org/wsdl/" />
</xsd:schema>
</types>
<message name="helloRequest">
<part name="name" type="xsd:string" />
</message>
<message name="helloResponse">
<part name="return" type="xsd:string" />
</message>
<portType name="hellowsdlPortType">
<operation name="hello">
<documentation>Says hello to the caller</documentation>
<input message="tns:helloRequest" />
<output message="tns:helloResponse" />
</operation>
</portType>
<binding name="hellowsdlBinding" type="tns:hellowsdlPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
<operation name="hello">
<soap:operation soapAction="urn:hellowsdl#hello" style="rpc" />
<input>
<soap:body use="encoded" namespace="urn:hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</input>
<output>
<soap:body use="encoded" namespace="urn:hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</output>
</operation>
</binding>
<service name="hellowsdl">
<port name="hellowsdlPort" binding="tns:hellowsdlBinding">
<soap:address location="http://localhost/mywork/myphp.php" />
</port>
</service>
</definitions>After making following changes to the wsdl program, I tried to generate java proxy.
<definitions name="hellowsdl"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:si="http://soapinterop.org/xsd" xmlns:tns="http://localhost/mywork/hellowsdl.wsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://localhost/mywork/myphpwsdl.wsdll">
<types>
<xsd:schema targetNamespace="http://localhost/mywork/hellowsdl.wsdl">
<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
<xsd:import namespace="http://schemas.xmlsoap.org/wsdl/" />
</xsd:schema>
</types>
<message name="helloRequest">
<part name="name" type="xsd:string" />
</message>
<message name="helloResponse">
<part name="return" type="xsd:string" />
</message>
<portType name="hellowsdlPortType">
<operation name="hello">
<documentation>Says hello to the caller</documentation>
<input message="tns:helloRequest" />
<output message="tns:helloResponse" />
</operation>
</portType>
<binding name="hellowsdlBinding" type="tns:hellowsdlPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
<operation name="hello">
<soap:operation soapAction="" style="rpc" />
<input>
<soap:body use="encoded" namespace="http://localhost/mywork/hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</input>
<output>
<soap:body use="encoded" namespace="http://localhost/mywork/hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</output>
</operation>
</binding>
<service name="hellowsdl">
<port name="hellowsdlPort" binding="tns:hellowsdlBinding">
<soap:address location="http://localhost/mywork/myphp.php" />
</port>
</service>
</definitions>This is how the java stub file looks like:
public class HellowsdlBinding_Stub
    extends oracle.j2ee.ws.client.StubBase
    implements demo.mypackage.HellowsdlPortType {
     * public constructor
    public HellowsdlBinding_Stub(HandlerChain handlerChain) {
        super(handlerChain);
        _setProperty(ENDPOINT_ADDRESS_PROPERTY, "http://localhost/mywork/hellowsdl.php");
        setSoapVersion(SOAPVersion.SOAP_11);
        setServiceName( new QName("http://localhost/mywork/hellowsdl","hellowsdl"));
        setPortName( new QName("http://localhost/mywork/hellowsdl","hellowsdlPort"));
     * implementation of hello
    public java.lang.String hello(java.lang.String name)
        throws java.rmi.RemoteException {
        StreamingSenderState _state = null;
        try {
            _state = _start(_handlerChain);
            if (_getProperty(ClientConstants.DIME_ENCODE_MESSAGES_WITH_ATTACHMENTS) != null) {
                _state.getMessageContext().getMessage().setProperty("DimeEncode",_getProperty(ClientConstants.DIME_ENCODE_MESSAGES_WITH_ATTACHMENTS));
            InternalSOAPMessage _request = _state.getRequest();
            _request.setOperationCode(hello_OPCODE);
            _state.getMessageContext().setProperty("oracle.j2ee.ws.mgmt.interceptor.operation-qname",new QName("","hello"));
            demo.mypackage.runtime.HellowsdlBinding_hello_ReqS _myHellowsdlBinding_hello_ReqS = new demo.mypackage.runtime.HellowsdlBinding_hello_ReqS();
        _myHellowsdlBinding_hello_ReqS.setName(name);
        SOAPBlockInfo _bodyBlock = new SOAPBlockInfo(ns1_hello_hello_QNAME);
        _bodyBlock.setValue(_myHellowsdlBinding_hello_ReqS);
        _bodyBlock.setSerializer(myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer);
        _request.setBody(_bodyBlock);
        _state.getMessageContext().setProperty("http.soap.action", "http://localhost/mywork/hellowsdl");
        _send((String) _getProperty(ENDPOINT_ADDRESS_PROPERTY), _state);
        demo.mypackage.runtime.HellowsdlBinding_hello_RespS _myHellowsdlBinding_hello_RespS = null;
        Object _responseObj = _state.getResponse().getBody().getValue();
        if (_responseObj instanceof SOAPDeserializationState) {
            _myHellowsdlBinding_hello_RespS =
                (demo.mypackage.runtime.HellowsdlBinding_hello_RespS)((SOAPDeserializationState)_responseObj).getInstance();
        } else {
            _myHellowsdlBinding_hello_RespS =
                (demo.mypackage.runtime.HellowsdlBinding_hello_RespS)_responseObj;
        return _myHellowsdlBinding_hello_RespS.get_return();
    } catch (RemoteException e) {
        // let this one through unchanged
        throw e;
    } catch (JAXRPCException e) {
        throw new RemoteException(e.getMessage(), e);
    } catch (Exception e) {
        if (e instanceof RuntimeException) {
            throw (RuntimeException)e;
        } else {
            throw new RemoteException(e.getMessage(), e);
* this method deserializes the request/response structure in the body
protected void _readFirstBodyElement(XMLReader bodyReader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
    int opcode = state.getRequest().getOperationCode();
    switch (opcode) {
        case hello_OPCODE:
            _deserialize_hello(bodyReader, deserializationContext, state);
            break;
        default:
            throw new SenderException("sender.response.unrecognizedOperation", Integer.toString(opcode));
* This method deserializes the body of the hello operation.
private void _deserialize_hello(XMLReader bodyReader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
    try {
        Object myHellowsdlBinding_hello_RespSObj =
            myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer.deserialize(ns1_hello_helloResponse_QNAME,
                bodyReader, deserializationContext);
        SOAPBlockInfo bodyBlock = new SOAPBlockInfo(ns1_hello_helloResponse_QNAME);
        bodyBlock.setValue(myHellowsdlBinding_hello_RespSObj);
        state.getResponse().setBody(bodyBlock);
    } catch (DeserializationException e) {
        if (e.getSoapFaultSubCodeType() == JAXRPCExceptionBase.FAULT_CODE_NONE && e.getSoapFaultCodeType() != JAXRPCExceptionBase.FAULT_CODE_DATA_ENCODING_UNKNOWN) {
            e.setSoapFaultSubCodeType(JAXRPCExceptionBase.FAULT_CODE_BAD_ARGUMENTS);
        throw e;
public String _getEncodingStyle() {
    return SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding();
public void _setEncodingStyle(String encodingStyle) {
    throw new UnsupportedOperationException("cannot set encoding style");
public ClientTransport getClientTransport() {
    return super._getTransport();
* This method returns an array containing (prefix, nsURI) pairs.
protected String[] _getNamespaceDeclarations() {
    return myNamespace_declarations;
* This method returns an array containing the names of the headers we understand.
public QName[] _getUnderstoodHeaders() {
    return understoodHeaderNames;
* This method handles the case of an empty SOAP body.
protected void _handleEmptyBody(XMLReader reader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
public void _initialize(InternalTypeMappingRegistry registry) throws Exception {
    super._initialize(registry);
    myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer = (CombinedSerializer)registry.getSerializer(SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding(), demo.mypackage.runtime.HellowsdlBinding_hello_ReqS.class, ns1_hello_TYPE_QNAME);
    myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer = (CombinedSerializer)registry.getSerializer(SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding(), demo.mypackage.runtime.HellowsdlBinding_hello_RespS.class, ns1_helloResponse_TYPE_QNAME);
private static final QName _portName = new QName("http://localhost/mywork/hellowsdl", "hellowsdlPort");
private static final int hello_OPCODE = 0;
private static final QName ns1_hello_hello_QNAME = new QName("http://localhost/mywork/hellowsdl", "hello");
private static final QName ns1_hello_TYPE_QNAME = new QName("http://localhost/mywork/hellowsdl", "hello");
private CombinedSerializer myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer;
private static final QName ns1_hello_helloResponse_QNAME = new QName("http://localhost/mywork/hellowsdl", "helloResponse");
private static final QName ns1_helloResponse_TYPE_QNAME = new QName("http://localhost/mywork/hellowsdl", "helloResponse");
private CombinedSerializer myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer;
private static final String[] myNamespace_declarations =
                                    new String[] {
                                        "ns0", "http://localhost/mywork/hellowsdl"
private static final QName[] understoodHeaderNames = new QName[] { };
}The errors that are produced are-
java.rmi.RemoteException: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 404 Not Found; nested exception is:
     HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 404 Not Found
Kindly help to resolve this.
Thanks.

This is a problem in generating a java proxy for a PHP webservice.
I have a PHP service running on Wamp Server and also a PHP client which is able to call the service.
The WSDL for the PHP web service is also generated .
I am trying to create a java proxy using the jdev (10.1.3.0.3) from the wsdl file.
The wsdl generated by the php program is
<?xml version="1.0" encoding="ISO-8859-1" ?>
<definitions xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:si="http://soapinterop.org/xsd" xmlns:tns="urn:hellowsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="urn:hellowsdl">
<types>
<xsd:schema targetNamespace="urn:hellowsdl">
<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
<xsd:import namespace="http://schemas.xmlsoap.org/wsdl/" />
</xsd:schema>
</types>
<message name="helloRequest">
<part name="name" type="xsd:string" />
</message>
<message name="helloResponse">
<part name="return" type="xsd:string" />
</message>
<portType name="hellowsdlPortType">
<operation name="hello">
<documentation>Says hello to the caller</documentation>
<input message="tns:helloRequest" />
<output message="tns:helloResponse" />
</operation>
</portType>
<binding name="hellowsdlBinding" type="tns:hellowsdlPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
<operation name="hello">
<soap:operation soapAction="urn:hellowsdl#hello" style="rpc" />
<input>
<soap:body use="encoded" namespace="urn:hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</input>
<output>
<soap:body use="encoded" namespace="urn:hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</output>
</operation>
</binding>
<service name="hellowsdl">
<port name="hellowsdlPort" binding="tns:hellowsdlBinding">
<soap:address location="http://localhost/mywork/myphp.php" />
</port>
</service>
</definitions>After making following changes to the wsdl program, I tried to generate java proxy.
<definitions name="hellowsdl"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:si="http://soapinterop.org/xsd" xmlns:tns="http://localhost/mywork/hellowsdl.wsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://localhost/mywork/myphpwsdl.wsdll">
<types>
<xsd:schema targetNamespace="http://localhost/mywork/hellowsdl.wsdl">
<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
<xsd:import namespace="http://schemas.xmlsoap.org/wsdl/" />
</xsd:schema>
</types>
<message name="helloRequest">
<part name="name" type="xsd:string" />
</message>
<message name="helloResponse">
<part name="return" type="xsd:string" />
</message>
<portType name="hellowsdlPortType">
<operation name="hello">
<documentation>Says hello to the caller</documentation>
<input message="tns:helloRequest" />
<output message="tns:helloResponse" />
</operation>
</portType>
<binding name="hellowsdlBinding" type="tns:hellowsdlPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
<operation name="hello">
<soap:operation soapAction="" style="rpc" />
<input>
<soap:body use="encoded" namespace="http://localhost/mywork/hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</input>
<output>
<soap:body use="encoded" namespace="http://localhost/mywork/hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</output>
</operation>
</binding>
<service name="hellowsdl">
<port name="hellowsdlPort" binding="tns:hellowsdlBinding">
<soap:address location="http://localhost/mywork/myphp.php" />
</port>
</service>
</definitions>This is how the java stub file looks like:
public class HellowsdlBinding_Stub
    extends oracle.j2ee.ws.client.StubBase
    implements demo.mypackage.HellowsdlPortType {
     * public constructor
    public HellowsdlBinding_Stub(HandlerChain handlerChain) {
        super(handlerChain);
        _setProperty(ENDPOINT_ADDRESS_PROPERTY, "http://localhost/mywork/hellowsdl.php");
        setSoapVersion(SOAPVersion.SOAP_11);
        setServiceName( new QName("http://localhost/mywork/hellowsdl","hellowsdl"));
        setPortName( new QName("http://localhost/mywork/hellowsdl","hellowsdlPort"));
     * implementation of hello
    public java.lang.String hello(java.lang.String name)
        throws java.rmi.RemoteException {
        StreamingSenderState _state = null;
        try {
            _state = _start(_handlerChain);
            if (_getProperty(ClientConstants.DIME_ENCODE_MESSAGES_WITH_ATTACHMENTS) != null) {
                _state.getMessageContext().getMessage().setProperty("DimeEncode",_getProperty(ClientConstants.DIME_ENCODE_MESSAGES_WITH_ATTACHMENTS));
            InternalSOAPMessage _request = _state.getRequest();
            _request.setOperationCode(hello_OPCODE);
            _state.getMessageContext().setProperty("oracle.j2ee.ws.mgmt.interceptor.operation-qname",new QName("","hello"));
            demo.mypackage.runtime.HellowsdlBinding_hello_ReqS _myHellowsdlBinding_hello_ReqS = new demo.mypackage.runtime.HellowsdlBinding_hello_ReqS();
        _myHellowsdlBinding_hello_ReqS.setName(name);
        SOAPBlockInfo _bodyBlock = new SOAPBlockInfo(ns1_hello_hello_QNAME);
        _bodyBlock.setValue(_myHellowsdlBinding_hello_ReqS);
        _bodyBlock.setSerializer(myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer);
        _request.setBody(_bodyBlock);
        _state.getMessageContext().setProperty("http.soap.action", "http://localhost/mywork/hellowsdl");
        _send((String) _getProperty(ENDPOINT_ADDRESS_PROPERTY), _state);
        demo.mypackage.runtime.HellowsdlBinding_hello_RespS _myHellowsdlBinding_hello_RespS = null;
        Object _responseObj = _state.getResponse().getBody().getValue();
        if (_responseObj instanceof SOAPDeserializationState) {
            _myHellowsdlBinding_hello_RespS =
                (demo.mypackage.runtime.HellowsdlBinding_hello_RespS)((SOAPDeserializationState)_responseObj).getInstance();
        } else {
            _myHellowsdlBinding_hello_RespS =
                (demo.mypackage.runtime.HellowsdlBinding_hello_RespS)_responseObj;
        return _myHellowsdlBinding_hello_RespS.get_return();
    } catch (RemoteException e) {
        // let this one through unchanged
        throw e;
    } catch (JAXRPCException e) {
        throw new RemoteException(e.getMessage(), e);
    } catch (Exception e) {
        if (e instanceof RuntimeException) {
            throw (RuntimeException)e;
        } else {
            throw new RemoteException(e.getMessage(), e);
* this method deserializes the request/response structure in the body
protected void _readFirstBodyElement(XMLReader bodyReader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
    int opcode = state.getRequest().getOperationCode();
    switch (opcode) {
        case hello_OPCODE:
            _deserialize_hello(bodyReader, deserializationContext, state);
            break;
        default:
            throw new SenderException("sender.response.unrecognizedOperation", Integer.toString(opcode));
* This method deserializes the body of the hello operation.
private void _deserialize_hello(XMLReader bodyReader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
    try {
        Object myHellowsdlBinding_hello_RespSObj =
            myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer.deserialize(ns1_hello_helloResponse_QNAME,
                bodyReader, deserializationContext);
        SOAPBlockInfo bodyBlock = new SOAPBlockInfo(ns1_hello_helloResponse_QNAME);
        bodyBlock.setValue(myHellowsdlBinding_hello_RespSObj);
        state.getResponse().setBody(bodyBlock);
    } catch (DeserializationException e) {
        if (e.getSoapFaultSubCodeType() == JAXRPCExceptionBase.FAULT_CODE_NONE && e.getSoapFaultCodeType() != JAXRPCExceptionBase.FAULT_CODE_DATA_ENCODING_UNKNOWN) {
            e.setSoapFaultSubCodeType(JAXRPCExceptionBase.FAULT_CODE_BAD_ARGUMENTS);
        throw e;
public String _getEncodingStyle() {
    return SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding();
public void _setEncodingStyle(String encodingStyle) {
    throw new UnsupportedOperationException("cannot set encoding style");
public ClientTransport getClientTransport() {
    return super._getTransport();
* This method returns an array containing (prefix, nsURI) pairs.
protected String[] _getNamespaceDeclarations() {
    return myNamespace_declarations;
* This method returns an array containing the names of the headers we understand.
public QName[] _getUnderstoodHeaders() {
    return understoodHeaderNames;
* This method handles the case of an empty SOAP body.
protected void _handleEmptyBody(XMLReader reader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
public void _initialize(InternalTypeMappingRegistry registry) throws Exception {
    super._initialize(registry);
    myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer = (CombinedSerializer)registry.getSerializer(SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding(), demo.mypackage.runtime.HellowsdlBinding_hello_ReqS.class, ns1_hello_TYPE_QNAME);
    myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer = (CombinedSerializer)registry.getSerializer(SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding(), demo.mypackage.runtime.HellowsdlBinding_hello_RespS.class, ns1_helloResponse_TYPE_QNAME);
private static final QName _portName = new QName("http://localhost/mywork/hellowsdl", "hellowsdlPort");
private static final int hello_OPCODE = 0;
private static final QName ns1_hello_hello_QNAME = new QName("http://localhost/mywork/hellowsdl", "hello");
private static final QName ns1_hello_TYPE_QNAME = new QName("http://localhost/mywork/hellowsdl", "hello");
private CombinedSerializer myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer;
private static final QName ns1_hello_helloResponse_QNAME = new QName("http://localhost/mywork/hellowsdl", "helloResponse");
private static final QName ns1_helloResponse_TYPE_QNAME = new QName("http://localhost/mywork/hellowsdl", "helloResponse");
private CombinedSerializer myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer;
private static final String[] myNamespace_declarations =
                                    new String[] {
                                        "ns0", "http://localhost/mywork/hellowsdl"
private static final QName[] understoodHeaderNames = new QName[] { };
}The errors that are produced are-
java.rmi.RemoteException: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 404 Not Found; nested exception is:
     HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 404 Not Found
Kindly help to resolve this.
Thanks.

Creation of Server Proxy for Message interface with External Defination

Dear All,
I am getting a problem while generating a server proxy for the inbound interface . The request message used in the inbound interface is a external definition which is uploaded using a XSD file. The XSD file was supplied by a third party which is having very high complex strucuture and used lot of abstract data types in the design. When i tried to generate the proxy in the R/3 system (Transaction SPROXY) for the inbound interface i am getting following error.
Interface uses external and internal message definitions
Message no. SPRX122 *
Diagnosis
In a message interface you can use messages from different sources:
Message types and fault message types edited in the Enterprise Services Repository
Messages imported into the Enterprise Services Repository (external definitions, RFC, IDoc)
In the current message interface, message types from different sources have been used. Since messages from these different sources must be handled differently during proxy generation, such a mixture of messages within a message interface is not possible.
System Response
The interface cannot be generated.
Procedure
Change the interface definition accordingly in the Enterprise Services Repository.
Please guide me, how to generate the proxy for the interface with external defination message. I could nt geneate manullay, because it is having very high complexity and its a big structure.
Is there is any way to generate the proxy for interface with external definition
Regards
Vijayanand

Hi,
i. Import your message schemas from external definitions, or RFCs or IDocs from SAP systems. These definitions already contain data types.
ii. Create a message interface and reference the messages of the external definition, or the RFC or IDoc message.
Check this, it may help you
http://help.sap.com/saphelp_nw04/helpdata/en/3f/01623c4f69b712e10000000a114084/content.htm
REgards
Seshagiri

Use BizTalk 2006 as a proxy for an external Web Service

Hi
We have a solution that is going to work just as a proxy for an external Web Service.
It works like this:
1. We have a Request-Response receive port that receives the calls for the WS.
2. Different Static Solicit-Response ports that have filters for each method in the WS receive the requests and then send them to the external WS.
3. The response from the external WS is then sendt back to the caller via the Request-Response port in point 1.
This generally works like it should. The only problem i have is when the external WS returns a Fault message. I get this fault from the external WS:
<s:Fault xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>s:Client</faultcode><faultstring xml:lang="nb-NO">Some error message the caller should see.</faultstring><detail><GenericFault
xmlns="http://register.test.com/Common" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"><ErrorCode>SomthingWentWrong</ErrorCode><Message>Some error message the caller should see.</Message></GenericFault></detail></s:Fault>
This message then failes on BizTalk and BizTalk returns this Fault message to the caller:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP:Body><SOAP:Fault><faultcode>Microsoft BizTalk Server Negative Acknowledgment
</faultcode><faultstring>An error occurred while processing the message, refer to the details section for more information </faultstring><faultactor>/Hemit.BizTalk.NHN.Position.ws/IPositionService.asmx</faultactor><detail><ns0:NACK
Type="NACK" xmlns:ns0="http://schema.microsoft.com/BizTalk/2003/NACKMessage.xsd"><NAckID>{7AC314FE-2CA3-44AE-8208-180495500481}</NAckID><ErrorCode>0xc0c016b7</ErrorCode><ErrorCategory>0</ErrorCategory><ErrorDescription>There
is an error in XML document (1, 2).</ErrorDescription><ErrorDetail><Fault xmlns='http://schemas.xmlsoap.org/soap/envelope/'> was not expected.</ErrorDetail></ns0:NACK></detail></SOAP:Fault></SOAP:Body></SOAP:Envelope>
So the problem seems to be that the Request-Response port in point one will ONLY accept the real response that is specified in the response schema for that particular method, and not a Fault. And when it receives a fault, it generates its own Fault saying
a Fault message was not expected.
Does anyone know how i can be able to send the actual fault from the external WS all the way back to the caller on the inside?
I know how to do it with an orchestration, but can not figure out how to get it done just with the ports.
Kind regars
John Viggo

Hi John,
Enable Propagate fault message
on the WCF solict –response port.
For the two-way send port, you can choose whether to forward
SOAP fault messages on to the original caller over a solicit-response send port by selecting
Propagate fault message. If this option is not selected, BizTalk Server will generate a NACK. What you see is the NACK.
If it is selected, BizTalk Server will treat the message as a valid WCF response message from the external service and the response message will not be suspended because it is propagated.
Then you need to map the fault message to the actual response in the map. Set this Fault-Message to Caller-Response map in the outbound map of the Requeust-Response port.
In this case of messaging-only scenario, this method shall help in handling the fault message and passing fault details back to the caller. Refer the following articles for more details.
Synchronous web services calls and Faults
BizTalk and
SOAPFault
version issues
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful.

Reg: Generating Proxy for a Schema exposed as a WCF sevice

Similar Messages

Maybe you are looking for