Problem in  creating a forward proxy

I want to create a forward proxy .
And the requirement is that whenever browser hits a URL then that request should first go to that proxy, I want to add a header to this request then the modified request should go back to browser through which it will reach the remote server.
I tried to implement this through running a port on which I will read the request coming from browser .But I do not know how will I send the modified request back to the browser.
I have written the following code:
Java Code:
import java.io.*;
import java.net.*;
public class ProxyApp {
    public static void main(String a[]) throws IOException , Exception
        ServerSocket proxySocket = new ServerSocket(7456);
        System.out.println("Socket created at port number.....7456.");
        System.out.println("waiting for browser to connect......");
        Socket browserSocket    = proxySocket.accept();
        System.out.println("request received from browser......");
        OutputStream browserOutputStream    = browserSocket.getOutputStream();
        InputStream browserInputStream      = browserSocket.getInputStream();
        byte[]       b = new byte[1];
        StringBuffer buf = new StringBuffer();
        String       s ;
        for ( ; ; ) {
            int len ;
            len = browserInputStream.read(b, 0, 1);
            if ( len == -1 ) {
                break ;
            s = new String( b );
            buf.append( s );
            if ( b[0] != '\n' ) {
                continue ;
            break ;
        String bufferedData = buf.toString();
        System.out.println("browser requested......"+bufferedData);
        int  start, end ;
        start = bufferedData.indexOf( ' ' ) + 1;
        while ( bufferedData.charAt(start) == ' ' ) {
            start++ ;
        end   = bufferedData.indexOf( ' ', start );
        String urlString = bufferedData.substring( start, end );
        System.out.println("browser requested..urlString...."+urlString);
         /*******************reading from server********************************/
        URL url = new URL(urlString);
        URLConnection connection = url.openConnection();
        connection.setDoOutput(true);
        OutputStream remoteOutputStream =  connection.getOutputStream();
        System.out.println("sent to remote......"+bufferedData);
        remoteOutputStream.write(bufferedData.getBytes());
        remoteOutputStream.flush();
        remoteOutputStream.close();
        System.out.println("Data written to remote server...");
        InputStream remoteInputStream   = connection.getInputStream();
        byte[]       b1 = new byte[1];
        StringBuffer buf1 = new StringBuffer();
        String       s1 ;
        for ( ; ; ) {
            int len ;
            len = remoteInputStream.read(b1, 0, 1);
            if ( len == -1 ) {
                break ;
            s1 = new String( b1 );
            buf1.append( s1 );
            if ( b1[0] != '\n' ) {
                continue ;
            break ;
        String bufferedData1 = buf1.toString();
        System.out.println("Data read from remote server...bufferedData1..."+bufferedData1);
        browserOutputStream.write(bufferedData1.getBytes());
        browserOutputStream.flush();
        browserOutputStream.close();
        System.out.println("Data written to browser...");
        System.out.println("**************END********************");
}But while getting the input stream from url connection I get Socket Exception.
Please tell me what is wrong...
Please help me out!
Edited by: 967629 on Oct 25, 2012 4:48 AM

I want to create a forward proxy .
And the requirement is that whenever browser hits a URL then that request should first go to that proxy, I want to add a header to this request then the modified request should go back to browser through which it will reach the remote server.
I tried to implement this through running a port on which I will read the request coming from browser .But I do not know how will I send the modified request back to the browser.
I have written the following code:
Java Code:
import java.io.*;
import java.net.*;
public class ProxyApp {
    public static void main(String a[]) throws IOException , Exception
        ServerSocket proxySocket = new ServerSocket(7456);
        System.out.println("Socket created at port number.....7456.");
        System.out.println("waiting for browser to connect......");
        Socket browserSocket    = proxySocket.accept();
        System.out.println("request received from browser......");
        OutputStream browserOutputStream    = browserSocket.getOutputStream();
        InputStream browserInputStream      = browserSocket.getInputStream();
        byte[]       b = new byte[1];
        StringBuffer buf = new StringBuffer();
        String       s ;
        for ( ; ; ) {
            int len ;
            len = browserInputStream.read(b, 0, 1);
            if ( len == -1 ) {
                break ;
            s = new String( b );
            buf.append( s );
            if ( b[0] != '\n' ) {
                continue ;
            break ;
        String bufferedData = buf.toString();
        System.out.println("browser requested......"+bufferedData);
        int  start, end ;
        start = bufferedData.indexOf( ' ' ) + 1;
        while ( bufferedData.charAt(start) == ' ' ) {
            start++ ;
        end   = bufferedData.indexOf( ' ', start );
        String urlString = bufferedData.substring( start, end );
        System.out.println("browser requested..urlString...."+urlString);
         /*******************reading from server********************************/
        URL url = new URL(urlString);
        URLConnection connection = url.openConnection();
        connection.setDoOutput(true);
        OutputStream remoteOutputStream =  connection.getOutputStream();
        System.out.println("sent to remote......"+bufferedData);
        remoteOutputStream.write(bufferedData.getBytes());
        remoteOutputStream.flush();
        remoteOutputStream.close();
        System.out.println("Data written to remote server...");
        InputStream remoteInputStream   = connection.getInputStream();
        byte[]       b1 = new byte[1];
        StringBuffer buf1 = new StringBuffer();
        String       s1 ;
        for ( ; ; ) {
            int len ;
            len = remoteInputStream.read(b1, 0, 1);
            if ( len == -1 ) {
                break ;
            s1 = new String( b1 );
            buf1.append( s1 );
            if ( b1[0] != '\n' ) {
                continue ;
            break ;
        String bufferedData1 = buf1.toString();
        System.out.println("Data read from remote server...bufferedData1..."+bufferedData1);
        browserOutputStream.write(bufferedData1.getBytes());
        browserOutputStream.flush();
        browserOutputStream.close();
        System.out.println("Data written to browser...");
        System.out.println("**************END********************");
}But while getting the input stream from url connection I get Socket Exception.
Please tell me what is wrong...
Please help me out!
Edited by: 967629 on Oct 25, 2012 4:48 AM

Similar Messages

  • 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.

  • Problem in creating web serivce proxy

    Please let me know how to create web serivce proxy? web service has the parameter of ArrayList<Attachment> . The Attachment is custom class. when i creating proxy it creates Arraylist of XML type
    @XmlAccessorType(XmlAccessType.FIELD)
    @XmlType(name = "abstractList")
    @XmlSeeAlso({
    ArrayList.class
    public abstract class AbstractList
    extends AbstractCollection
    in this Arralist i could not able to cast java.util.ArrayList.
    Thank You.

    Hi Mithu,
    Thanks for your reply, I dose the sam but still I m getting this problem.
    it happens when I click on finish and tha it asks for adding proxy files to the and than to activity.When I click on add. the editor goes to Not Responding state.
    RAM in the server is 8 GB.and in my system its 1 GB.
    Waiting for your reply
    Regards,
    Yajush

  • Problem while creating web service proxy in Jdeveloper 10.1.3

    I am using Jdeveloper 10.1.3 to create a web service proxy so that I can track my request/response in HTTP Analyzer.
    I am following the steps as mentioned in the follwoing uRL:
    http://www.oracle.com/technology/obe/obe1013jdev/ws/wsandascontrol.htm
    But I get the following warning while creating the web servcice proxy:
    Generating proxy
    WARNING: value type package prefix is ignored for the types defined in the schema that has same target namespace as the target namespace of wsdl: <my web service namepsace>
    Proxy generation finished
    After adding my code in the main methoad of proxy, I get the following error while compiling:
    WARNING: Unable to connect to URL: <my web service proxy URL> due to java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Connection refused: connect
    java.rmi.RemoteException: ; nested exception is:
    HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Connection refused: connect
    Please help as how to solve this.
    Edited by: user11258855 on 02-Jul-2009 03:38

    I am using Jdeveloper 10.1.3 to create a web service proxy so that I can track my request/response in HTTP Analyzer.
    I am following the steps as mentioned in the follwoing uRL:
    http://www.oracle.com/technology/obe/obe1013jdev/ws/wsandascontrol.htm
    But I get the following warning while creating the web servcice proxy:
    Generating proxy
    WARNING: value type package prefix is ignored for the types defined in the schema that has same target namespace as the target namespace of wsdl: <my web service namepsace>
    Proxy generation finished
    After adding my code in the main methoad of proxy, I get the following error while compiling:
    WARNING: Unable to connect to URL: <my web service proxy URL> due to java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Connection refused: connect
    java.rmi.RemoteException: ; nested exception is:
    HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Connection refused: connect
    Please help as how to solve this.
    Edited by: user11258855 on 02-Jul-2009 03:38

  • Problems creating a client proxy for a WS

    I've tried creating a client proxy from a wsdl but I've had no luck getting it to work.
    First of all I created the client proxy in se80 with instructions from a teched lecture. The proxy seems to be generated as intended. When I create the default logical port for the proxy in lpconfig, it doesn't get any URL at all by default in the Call Parameters tab. Atleast in the teched demo the logical port got the default URL straight away.
    Therefore I opened the wsdl file with notepad and put the address that was specified in the soap:address element as the location attribute. After saving and activating both the logical port and the client proxy I tried testing the proxy. All the methods give the same following error message:
    Sap Fault Code 1:
    Found 0 operation definitions using keys...
    The WS works fine from the WS Navigator test page though. If I change the logical port URL I get an "Unsupported xstream found" error message. Thus I assume the URL that I took from the wsdl should be correct. Can I assume the wsdl is somehow broken? As I look closer at the wsdl, it seems to consist of several wsdl's that are imported to the main wsdl.

    Hi Evan,
    I don't think the wsdl is broken. I assume your webservice is deployed on WAS. Typically the SAP wsdl consist of 3 files, main wsdl file and 2 other files for binding and porttypes.
    When all three files are appropriately available then only the proxy gets generated.
    Since in your case the proxy is generated and you could activate it, means there is no problem in the wsdl.
    Are there any further details in your error?
    Does your service methods require any input and you are providing the input appropriately?
    Regards,
    Vandana.

  • ABAP PROXY CLIENT PROBLEM TO CREATE

    Hi,
    I am trying to create an ABAP PROXY of the type OUTBOUND SYNCH in my R/3. We already made the configuration according to the manual of the page 26. When I select my interface and I click in the button to create proxy, a screen appears for me to choose the package. I select the package $TMP and a screen appears of registering object. 
    I am trying to create an ABAP PROXY for the interface Z_MI_TESTE_XI_ABAP_PROXY_OU but when I will create the proxy for the transaction sproxy the screen it appears of registering the object "CO_Z_MI_TESTE_XI_ABAP_PROXY_OU." I already researched some documents in that the proxy begins with the letter "Z." How do I do for in the generation of my abap proxy the same nominated "ZBLOGCO_Z_MI_TESTE_XI_ABAP_PROXY_OU comes? 
    How do I do to register the object above? 
    Which are the steps to create an abap proxy?

    Hi,
    Thanks for all the response.
    I followed step by step the document http://weblogs.sdn.sap.com/pub/wlg/1387. [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] I created the proxy and the program abap. When I execute the same for the transaction SE38, it doesn't appear anything. No message is passed for SAP XI and it doesn't also happen any mistake. Is it necessary more some configuration type? Does creating only the proxy the same take charge of doing the communication with SAP XI? In the moment of the creation of the proxy how do I associate my R/3 to the XI? It follows the code used abap below:
    *& Report  ZCO_TESTE_XI_ABAP_PROXY_OUT
    REPORT  zco_teste_xi_abap_proxy_out.
    DATA prxy TYPE REF TO zco_mi_teste_xi_proxy_out.
    CREATE OBJECT prxy.
    DATA it TYPE  zzmt_teste_xi_proxy.
    TRY.
        it-z_mt_teste_xi_abap_proxy-empname = 'Sravya'.
        it-z_mt_teste_xi_abap_proxy-empno = '80101'.
        it-z_mt_teste_xi_abap_proxy-departmentname = 'NetWeaver'.
        CALL METHOD prxy->execute_synchronous
          EXPORTING
            output = it.
         commit work
      CATCH cx_ai_system_fault .
        DATA fault TYPE REF TO cx_ai_system_fault .
        CREATE OBJECT fault.
        WRITE :/ fault->errortext.
    ENDTRY.

  • Push Forward Proxy info within DHCP

    Hello,
    Is it possible to "push" Forward proxy info to clients using DHCP (with some option)?
    Regards
    Kostas

    Kostas B wrote:
    Hello,
    Is it possible to "push" Forward proxy info to clients using DHCP (with some option)?
    Regards
    Kostas
    It is possible to use my DHCP Option Code Utility to create the required DHCP option codes for advertising a proxy server. See http://en.wikipedia.org/wiki/WebProxy_AutodiscoveryProtocol
    As per the above article, there are two methods for a client to 'discover' a proxy server, one is via a DHCP option code, as per your query, the other is via a standard URL formed based on the clients domain name, e.g. http://wpad.example.com/wpad.dat
    Unfortunately, it is my impression that while it is possible to set a Mac OS X Server to provide both the DHCP option code, and to host a suitable file at the address specified via the DNS method, I don't believe any version of Mac OS X as a client will use either of these methods.
    You can manually configure a Mac OS X client to look for the DNS address and then the wpad file in System Preferences -> Network -> Advanced… -> Proxies -> Automatic Proxy Configuration , you could in theory use Managed Preferences via Workgroup Manager as well. However both these methods cause problems for laptops since when out of the office they are unlikely to be able to access your proxy server, or want to.
    So, these two methods on a Mac OS X Server may work with Windows clients (if Windows still supports these methods), but as far as I am aware are useless for Mac OS X clients.
    For the benefit of others, a typical reason for using a proxy server, is to monitor network traffic especially web-browsing. An alternate approach that should work for Macs, would be to have a device in-between the LAN and the Internet so all web-browsing has to go through it regardless. This should therefore not need the Macs to be specifically configured.
    As we all know, historically Apple has not addressed the needs of the Enterprise market and this could be considered an example of that.
    For the benefit of everyone, here is an example DHCP option code as you would add it to your bootpd.plist file at /etc/bootpd.plist
    <code><key>dhcpoption252</key>
    <data>
    aHR0cDovL3dwYWQuZXhhbXBsZS5jb20vd3BhZC5kYXQ=
    </data>
    The above uses the example, URL of http://wpad.example.com/wpad.dat obviously you need to use my utility to create a value that matches your domain and to have a web-server on your LAN that can host that file. The file then tells the client how to access the proxy server, again see the above wiki article and also this one http://en.wikipedia.org/wiki/Proxy_auto-config which tells you how to write the wpad.dat (aka. proxy.pac) file.
    Update: I notice Mac OS X 10.6 now has a "Auto Proxy Discover" option, as Apple do not provide any real documentation for this level of detail, only they know for sure what this does. However it does sound like it might implement the DHCP and DNS methods of auto-discovery. This option was not present in Mac OS X 10.5. If this is what it does you do not need to turn on and fill in the "Automatic Proxy Configuration" option.

  • 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!

  • Cannot create/reply/forward email on FireFox 15.0.1

    I was able to create/reply/forward email on AOL with FireFox 14 but with FireFox 15.0 the reply/forward feature only copied the email to the compose page on the first attempt - I had to end/restart FireFox each time I wanted to reply/forward. With the 15.0.1 upgrade I have lost the ability to create/reply/forward - the compose page works except I cannot issue the send or save commands (thank goodness for autosave). Switching to IE solves the problem but my browser of preferance is FireFox.
    This problem only exists for AOL webpage email - yahoo and gmail work perfectly.

    Is the problem with Send and Save that the buttons are missing or that they don't do anything?
    I don't have an AOL account to test, so I can only offer general advice.
    When you have a problem with one particular site, a good "first thing to try" is clearing your Firefox cache and deleting your saved cookies for the site.
    (1) Bypass Firefox's Cache
    Use Ctrl+Shift+r to reload the page fresh from the server.
    (You also can clear Firefox's cache completely using:
    orange Firefox button ''or'' Tools menu > Options > Advanced
    On the Network mini-tab > Cached Web Content : "Clear Now")
    (2) Remove your aol.com cookies (save any pending work first) using either of these:
    * While viewing a page on the site, right-click and choose View Page Info > Security > "View Cookies"
    * Alt+t (open the classic Tools menu) > Page Info > Security > "View Cookies"
    Then try reloading the page. Does that help?
    A standard diagnostic to bypass interference by extensions (and some custom settings) is to try Firefox's Safe Mode.
    First, I recommend backing up your Firefox settings in case something goes wrong. See [[Backing up your information]]. (You can copy your entire Firefox profile folder somewhere outside of the Mozilla folder.)
    Next, restart Firefox in Firefox's Safe Mode ([[Safe Mode]]) using
    Help > Restart with Add-ons Disabled
    In the dialog, click "Start in Safe Mode."
    If the site works correctly, this points to one of your extensions or custom settings as the problem.
    Any change?

  • ALSB 3.0: Problem with Nested Policies in Proxy Service WSDL

    Hello,
    I'm trying to implement client applications that consume Web Services.
    In ALSB, i imported the WSDLs of the services, created business and proxy Services.
    Creating web references in .NET and Netbeans is working well, as long as there is no security policy attached to the WSDLs of the proxy services.
    When attaching a policy, ALSB nests it inside the WSDL:
    <s0:Policy s1:Id="signMessage">
    <wssp:Integrity SignToken="false">
    <wssp:SignatureAlgorithm URI="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
    <wssp:CanonicalizationAlgorithm URI="http://www.w3.org/2001/10/xml-exc-c14n#"/>
    <wssp:Target>
    and references it, where i want it to have. in this case it's in the request of the service:
    <s2:input>
    <s4:body use="literal"/>
    <wsp:Policy>
    <wsp:PolicyReference URI="#signMessage"/>
    </wsp:Policy>
    </s2:input>
    The problem is, that neither .Net (C#) nor Netbeans (Java) correctly import and handle these policies. .Net even mentions in the generated code that the "Policy" element was not handled. So when running my applications, i logically get exceptions that no credentials/tokens or else were delivered from the client side. In general the mentioned IDEs that i'm using support the configuration of those security issues. But when not correctly parsing the WSDL from the Service Bus, they don't work.
    I tried many ways to dodge this problem, but without success.
    Manually writing policy Statements into the WSDL files is not what i'm searching for as a solution. I want it dynamically.
    I hope i could describe my problem clear enough and to get a possible solution.
    Thanks

    Sorry, found the answer but forgot to update this thread.
    The ?WSDL mechanism fails if Enforce WS-I Interoperability is true for the Proxy Service.
    While BEA support (and the docs relating to this flag) say this is by design (Only POST not GET is supported by WS-I) personally it seems to me that this rule should apply to operation invocation not a metadata inquiry but there you go...

  • Mac OS X Server Forward Proxy(Web Caching)...setup a website for the proxy???

    My office is a Mac environment with a couple of windows pcs. To save on bandwidth i would like to setup a Mac OS X Snow leopard server with a web caching proxy, forward proxy. I read this link from apple
    Server Admin 10.6 Help: Configuring Web Service Proxy Settings
    i understand that to set this up i must enable it on my Mac Server and also on the clients(end user) web browser. What i don't understand is this part:
    "When setting up a forward proxy, make sure you create and enable a  website for the proxy. You might want to disable logging                      on the proxy site or configure the site to record  its access log in a separate file from your other sites’ access logs.  The                      site does not need to be on port 80 but setting up  web clients is easier if its browsers use port 80 by default."
    Create and enable a website for the proxy??? I don't understand, why do i need a website for web caching? Shouldn't the settings in the web browser direct the http requests to the mac server and it does the rest, what has a website got to do with it and what type of website?How?
    Please help, thank you in advance

    SL Server

  • Create a Client Proxy for consume wsdl via https URL return a 110 HTTP code

    Dear all.
    I has new in this forum, and i have a problem when trie to create a client proxy from external WSDL, using https URL, system returns me a 110 http code. For others externs WSDL called via http don´t have any problem, and create client proxy perfect
    Someone can help please.
    best regards in advance.

    Dear Anton I download de WSDL definition in a local file, but when I trie to use, the error persist.
    If I test de URL via WebService navigation option, this work correctly, but if I put this URL thats begins with https, in se80--> create client proxy -->insert URL and then system returns the message HTTP error (return code 110, message "") 
    What it´s happen?.
    Best regards in advance.
    Juliá

  • Problem while creating logical port using soamanager

    Hi all,
    I have created a client proxy for web service from a 3rd party system.
    When i am creating a logical port for the same consumer proxy i get a error as follows:
    RABAX_STATE -e: UNCAUGHT_EXCEPTION
    and a dump saying
    "  The exception 'CX_SXMLP' was raised, but it was not caught anywhere along the call hierarchy.
         Since exceptions represent error situations and this error was not adequately responded to, the running ABAP program
          'CL_SXMLP_FRAGMENT=============CP' has to be terminated.                  
    Please suggest what can be done or what can be the problem.
    Thanks in advance.
    Komal

    Pls go to txn SM59 and check if the RFC destination for webservice is working in the test connection.
    Then go to txn LPCONFIG and create the logical port using the RFC dest.  Pls mention the path suffix appropriately.
    Next in your code while instantiating the client proxy pass the logical port name in the constructor (if the LP is not maintained as default).
    Pls reward points if the tips are helpful.

  • Problems while creating Web Services in development server

    Hello,
    We are facing problems while creating Web services . The transaction like WSADMIN, WSCONFIG are not there in development server. Its gives message u2018This transaction is obsoleteu2019.
    Due to this while creating Webservice, there is and error message . Kindly guide me whats needs to be done.
    We have also tried the transaction WSADMIN2 as suggested by SAP, but didnu2019t know wat needs to be done.
    Regards,
    Rachel
    Edited by: Rachel on Feb 3, 2009 9:15 AM

    Hi,
    With your help, we were configuring WEB Service through soamanger.Due to some problem, we couldn't proceed further.Kindly guide us with the further steps.
    *steps followed *
    Step 1 : Entered Service Registry Parameters in WSPARAM .
    Step 2 : In transaction SOAMANAGER->Technical Configuration -->System Global settings
    Step3 : From u2018SE80u2019 transaction, selected the package ZHR and then right clicked to create the enterprise service -> Client Proxy (Service Producer)
    We have followed steps in se80.Don't know how to proceed further.
    We are unable to find the service in soamanger .How to find the service name in soamanager?
    Regards,
    Rachel
    Edited by: Rachel on Feb 3, 2009 12:38 PM
    Edited by: Rachel on Feb 3, 2009 12:48 PM

  • Problem in Creating HTTP Destination

    Hello all,
    I am trying to consume a web service from ABAP and for this very reason I am creating a Client proxy and now I need to create a HTTP destination(Type G).
    I have created the Destination and when I test the connection I was facing with a error 'Service unavailable'.
    Please help me in how to resolve such an error and also let me know if there are any pre requisites before creating a HTTP Destination.
    Thanks in advance,
    Regards,
    Suman.

    Hi,
    I have raised this issue to the basis team and they are trying to figuring it out regarding the ICM/ICF paramters.
    In the mean time when I am creating the client proxy for a webservice which is internaI,I faced a error similar to which Igor has faced.
    In the WSDL document, the object
    "<complex/simpleType name="ArrayOfAnyType"> <ele..."
    from the namespace
    "http://NJNWKDEV119.enterprise.pseg.com/"
    links to the object
    from the namespace
    This webservice is from .net framework and I have asked them to check MSDN as mentioned by Anton with regards to problem faced by Igor.
    I am pasting my wsdl so that you guys can help me in finding out what exactly the error is. Thank you in advance.
    <?xml version="1.0" encoding="utf-8" ?>
    - <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://NJNWKDEV119.enterprise.pseg.com/" 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://NJNWKDEV119.enterprise.pseg.com/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    - <wsdl:types>
    - <s:schema elementFormDefault="qualified" targetNamespace="http://NJNWKDEV119.enterprise.pseg.com/">
    - <s:element name="ValidatePointAddress">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="streetAddress" type="s:string" />
      </s:sequence>
      </s:complexType>
      </s:element>
    - <s:element name="ValidatePointAddressResponse">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="ValidatePointAddressResult" type="tns:ArrayOfAnyType" />
      </s:sequence>
      </s:complexType>
      </s:element>
    - <s:complexType name="ArrayOfAnyType">
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="unbounded" name="anyType" nillable="true" />
      </s:sequence>
      </s:complexType>
    - <s:element name="ValidateLineAddress">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="streetAddress" type="s:string" />
      </s:sequence>
      </s:complexType>
      </s:element>
    - <s:element name="ValidateLineAddressResponse">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="ValidateLineAddressResult" type="tns:ArrayOfAnyType" />
      </s:sequence>
      </s:complexType>
      </s:element>
    - <s:element name="GetCrossStreetforPointAddress">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="streetAddress" type="s:string" />
      </s:sequence>
      </s:complexType>
      </s:element>
    - <s:element name="GetCrossStreetforPointAddressResponse">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="GetCrossStreetforPointAddressResult" type="tns:ArrayOfAnyType" />
      </s:sequence>
      </s:complexType>
      </s:element>
      </s:schema>
      </wsdl:types>
    - <wsdl:message name="ValidatePointAddressSoapIn">
      <wsdl:part name="parameters" element="tns:ValidatePointAddress" />
      </wsdl:message>
    - <wsdl:message name="ValidatePointAddressSoapOut">
      <wsdl:part name="parameters" element="tns:ValidatePointAddressResponse" />
      </wsdl:message>
    - <wsdl:message name="ValidateLineAddressSoapIn">
      <wsdl:part name="parameters" element="tns:ValidateLineAddress" />
      </wsdl:message>
    - <wsdl:message name="ValidateLineAddressSoapOut">
      <wsdl:part name="parameters" element="tns:ValidateLineAddressResponse" />
      </wsdl:message>
    - <wsdl:message name="GetCrossStreetforPointAddressSoapIn">
      <wsdl:part name="parameters" element="tns:GetCrossStreetforPointAddress" />
      </wsdl:message>
    - <wsdl:message name="GetCrossStreetforPointAddressSoapOut">
      <wsdl:part name="parameters" element="tns:GetCrossStreetforPointAddressResponse" />
      </wsdl:message>
    - <wsdl:portType name="AddValidationSoap">
    - <wsdl:operation name="ValidatePointAddress">
      <wsdl:input message="tns:ValidatePointAddressSoapIn" />
      <wsdl:output message="tns:ValidatePointAddressSoapOut" />
      </wsdl:operation>
    - <wsdl:operation name="ValidateLineAddress">
      <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">ValidatelineAddress -Public web method to validate the line address for the first call from SAP Address Validation screen</wsdl:documentation>
      <wsdl:input message="tns:ValidateLineAddressSoapIn" />
      <wsdl:output message="tns:ValidateLineAddressSoapOut" />
      </wsdl:operation>
    - <wsdl:operation name="GetCrossStreetforPointAddress">
      <wsdl:input message="tns:GetCrossStreetforPointAddressSoapIn" />
      <wsdl:output message="tns:GetCrossStreetforPointAddressSoapOut" />
      </wsdl:operation>
      </wsdl:portType>
    - <wsdl:binding name="AddValidationSoap" type="tns:AddValidationSoap">
      <soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
    - <wsdl:operation name="ValidatePointAddress">
      <soap:operation soapAction="http://NJNWKDEV119.enterprise.pseg.com/ValidatePointAddress" style="document" />
    - <wsdl:input>
      <soap:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
    - <wsdl:operation name="ValidateLineAddress">
      <soap:operation soapAction="http://NJNWKDEV119.enterprise.pseg.com/ValidateLineAddress" style="document" />
    - <wsdl:input>
      <soap:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
    - <wsdl:operation name="GetCrossStreetforPointAddress">
      <soap:operation soapAction="http://NJNWKDEV119.enterprise.pseg.com/GetCrossStreetforPointAddress" style="document" />
    - <wsdl:input>
      <soap:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:binding name="AddValidationSoap12" type="tns:AddValidationSoap">
      <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
    - <wsdl:operation name="ValidatePointAddress">
      <soap12:operation soapAction="http://NJNWKDEV119.enterprise.pseg.com/ValidatePointAddress" style="document" />
    - <wsdl:input>
      <soap12:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap12:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
    - <wsdl:operation name="ValidateLineAddress">
      <soap12:operation soapAction="http://NJNWKDEV119.enterprise.pseg.com/ValidateLineAddress" style="document" />
    - <wsdl:input>
      <soap12:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap12:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
    - <wsdl:operation name="GetCrossStreetforPointAddress">
      <soap12:operation soapAction="http://NJNWKDEV119.enterprise.pseg.com/GetCrossStreetforPointAddress" style="document" />
    - <wsdl:input>
      <soap12:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap12:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:service name="AddValidation">
    - <wsdl:port name="AddValidationSoap" binding="tns:AddValidationSoap">
      <soap:address location="http://njnwkdev119/PSEGAV/AddValidation.asmx" />
      </wsdl:port>
    - <wsdl:port name="AddValidationSoap12" binding="tns:AddValidationSoap12">
      <soap12:address location="http://njnwkdev119/PSEGAV/AddValidation.asmx" />
      </wsdl:port>
      </wsdl:service>
      </wsdl:definitions>
    Regards,
    Suman.

Maybe you are looking for

  • When trying to open pages 08 file with pages 09

    I am trying to open an old pages08 document using pages 09 however is not letting me do so.  A message saying " to open it save it as pages09 first" is coming up however I cannot even open the file, how can I save it as pages 09 then? Very frustratin

  • Windows 7 home premium 64 bit disc won't boot up on Lenovo B575

    My hard drive died on me. I never burned copies of the One Key Recovery disks. I replaced the Hard Drive with a toshiba SATA. I have burned several copies of windows 7 64 bit, and even bought an installation disc from Ebay, because I didn't want to p

  • Migrated Acrobat XI Pro over to new iMac, but now it says serial number is invalid.

    After the migration to a new iMac, it told me that it did not install correctly and I needed to reinstall Adobe Acrobat XI Pro.  So I did, and now when I enter the serial number for activation, it says it is invalid.  Anyone know what the problem mig

  • Remove Task card in Workspace and Terminate a process

    Hi all, We have a long-lived process that goes through an orchestration of approvers. When I try to terminate the process through the Admin UI console the process just remains in TERMINATING status and never gets terminated. The task card also remain

  • MRP: Planning horizon & opening period

    hi MM Experts, please, explain what is "MRP planning horizon" and what is the impact on MD03 ? please expalin elso "the MRP Opening  period" and what's his utility ? both of them are in the OMI8 tcode. thanx in advance. SDA