New way generating of Java Proxy to support parallel processing

Hi All!!
To the Java Proxy Server supports the processing of several executions in parallel way, a new way or generation has been released. On the Integration Directory, when you select an Inbound Message Interface and go to Java Proxy Generation, 2 .zip archives are generated, one for the execution in sequential way (XXX.ZIP) and other for the execution in parallel way (XXX_PARARELL.ZIP).
I have tried to generate the Java Proxy only with XXX_PARARELL.ZIP and I think is not possible, because no EJB Candidate is generated.
Somebody knows how I can generate the Java Proxy?
Thanks and regards,
Manuel Míguez.

a bit of light reading for you
http://onesearch.sun.com/search/developers/index.jsp?and=java.lang.ClassFormatError+Bad+magic+number&nh=10&Search.x=26&Search.y=11&phr=&qt=&not=&field=&since=&col=devforums&rf=0

Similar Messages

Error in generating the Java Proxy

Hi all,
While generating a Java Proxy, I am getting an error :
Unable to generate proxies
Construct not supported
Can anybody please suggest the possible reason and solution for the same.
Thanks and best regards,
Kulwant

In the Integration Repository documentation for External Definitions you find a hint where you can find a document describing restrictions on the handling of XSD.
In that document you can see, that references to global elements are not supported by the java proxy generation.
Therefore, you have to edit your document accordingly.
regards
chandra

Any news or ETA on Java 1.7 support for Coherence 3.7?

We're currently in the process of preparing for a rather large upgrade to our existing cluster that is running on older JVMs and an older version of Coherence. One motivating factor is to get on a supported JVM / Coherence version instead of just an "enduring support" version.
As part of this effort, we are going to be doing a lot of regression testing of our applications. From what I understand, Java 1.6 will be EOL in November of 2012 - so it would seem prudent to consider upgrading to Java 1.7 at this same time (although upgrading JVMs in a rolling fashion isn't as big of a deal as upgrading to a major version of coherence since the cluster can have heterogeneous JVM versions but not heterogenous protocol versions)
Is there an ETA for when Coherence will be supported on Java 1.7?

cfelde wrote:
It doesn't support 1.7?
We've run Coherence on 1.7 under various installations for some time with no issues. In fact we've seen significant performance gains.
http://docs.oracle.com/cd/E24290_01/coh.371/e22837/gs_install.htm#CIHDECEA
It says "1.6 update 23 JVM or later", but it doesn't include 1.7? Also given that 7 is binary-compatible with 6 (in a most cases at least: http://www.oracle.com/technetwork/java/javase/compatibility-417013.html#incompatibilities), it didn't look like a big risk up front.
There were a few other reported incompatibilities with other software out there and Java 7 besides those listed in the compatibility list, so I would be a bit careful about it.
Or are you talking about compiling and having a Java 7 compiled coherence jar?I don't think you would see anything like that with 3.7. After all 3.7 still has to run on Java 6 and Java 6 would not be able to load Java 7 compiled class files.
Best regards,
Robert

Java Proxy Generation not working - Support for Parallel Processing

Hi Everyone,
As per SAP Note 1230721 - Java Proxy Generation - Support for Parallel Processing, when we generate a java proxy from an interface we are supposed to get 2 archives (one for serial processing and another suffixed with "PARALLEL" for parallel processing of jaav proxies in JPR).
https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1230721
We are on the correct patch level as per the Note, however when we generate java proxy from the IR for an outbound interface, it genrates only 1 zip archive (whose name we ourselves provide in the craete new archive section). This does not enable the parallel processsing of the messages in JPR.
Could you please help me in this issue, and guide as to how archives can be generated for parallel processing.
Thanks & Regards,
Rosie Sasidharan.

Hi,
Thanks a lot for your reply, Prateek.
I have already checked SAP Note 1142580 - "Java Proxy is not processing messages in parallel" where they ask to modify the ejb-jar.xml. However, on performing the change in ejb-jar.xml and while building the EAR, I get the following error:
Error! The state of the source cache is INCONSISTENT for at least one of the request DCs. The build might produce incorrect results.
Then, on going through the SAP Note 1142580 again, I realised that the SAP Note 1230721 also should be looked onto which will be needed for generating the Java proxy from Message Interfaces in IR for parallel processing.
Kindly help me if any of you have worked on such a scenario.
Thanks in advance,
Regards,
Rosie Sasidharan.

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.

Error in java proxy generation due to xs:choice tag

Hi all,
I'm trying to generate a java proxy in the SAP XI design.
The message interface I'm using is based on an external definition which i imported from an xsd file.
The problem is that XI doesn't allow me to generate the java proxy because in the xsd schema the tag <xs:choice> is present and XI cannot handle it (just in this case, because the external definition works fine).
Does anybody know how to solve the problem or manage to generate the javaproxy anyhow?
Thanks in advance,
Daniele

> Replace <xs:choice> tag with <b><xsd:choice> tag
> </b>
> that should solve the prob.
I tried to change the tag (replacing also other <xs:...> tags in order to obtain a valid xsd) but the problem didnt change.
i'm almost convinced that tag is not supported in java proxy generation (but it is for external definitions...)

Java proxy problem:com.sap.aii.proxy.xiruntime cannot be resolved to a type

hi:
    i am new to Java proxy and new to SAP netweaver developer studio.
    thei PI version is 7.1
    I have generate a java proxy , then create a project in netweaver developer studio and import this java proxy according document "How Tou2026Work with XI 3.0 Java Proxies".
    but i can not find :aii_proxy_xirt.jar aii_msg_runtime.jar on the PI server, only guidgenerator.jaraii_utilxi_misc.jar could be found. then i could not config the build path.
    in the SAP netweaver developer studio, the error shows like :com.sap.aii.proxy.xiruntime cannot be resolved to a type
   then how to resolve this problem
   thank you very much

Hi Cheng,
I am trying to create a java proxy to send message from WebAS to PI using java proxy.
I am using NWDS 7.1. Can you please help with step on how to create a java proxy in NWDS 7.1?
Thanks and best regards,
Arun prabhu S

Java proxy from BAPI

I am new to java development and I want to generate a java proxy for a correspong BAPI. What is the process to do it using NET weaver.
what are the neccessary jars that are required to implement the functions

Hi Chaitanya,
You can use the SAP Enterrpise Connector from NWDS. You can find the doc here: http://help.sap.com/saphelp_nw70/helpdata/en/11/e2bc3d9ecc6b3be10000000a114084/frameset.htm
But you may also consider other options such as external services with CAF.

Java Proxy error .... com.sap.aii.utilxi.misc.api.BaseException

Hello All,
I have generated a java proxy and trying to compile in Developer Studio. I am getting this error while doing so. I have all my jars in classpath.
com.sap.aii.utilxi.misc.api.BaseException
Below are the jars i have in my class path.. Anybosy has idea
aii_msg_runtime.jar
aii_proxy_xirt.jar
aii_utilxi_misc.jar
guidgenerator.jar
ejb20.jar
exception.jar
jARM.jar
sapj2eeclient.jar
sapxmltoolkit.jar
-Srinivas

Hi Srinivasa,
Other than that u can try importing these jars as well:
aii_adapter_xi_svc
aii_af_cci
aii_af_cpa
aii_af_mp
aii_af_ms_api
aii_af_ms_spi
aii_af_service_message_security
aii_msg_runtime
aii_proxy_xirt
aii_utilxi_misc
jperflib
jta
log_api
logging
sapni
It might help.
Thanks and Regards,
Sanjeev.

Synchronous interfaces missing in Java proxy generation

Hi,
In PI 7.1 ESR, in "Java proxy generation" wizard, it only lists the Asynchronous interfaces from the software component version. None of the synchronous interfaces are listed. how can I solve this? I need to generate a java proxy for a syncronous interface.
thanks and regards,
Raghu

Make sure that the inteface pattern is "stateless (XI 3.0 compatible)".

Send JDBC Data with Java Proxy

Hello,
I Have generated a Java Proxy. And the Data Source is a JDBC Table like:
VALUE01--VALUE02--VALUE03
ROW1-Test1----Test1----Test1
ROW2-Test2----Test2----Test2
Now i can set the Datatypes in XI Proxy with
TYPE.setVALUE01("Test1");
TYPE.setVALUE02("Test1");
TYPE.setVALUE03("Test1");
so i can send a XML like
<TYPE>
<VALUE01>Test</VALUE01>
<VALUE02>Test</VALUE02>
<VALUE03>Test</VALUE03>
</TYPE>
My Problem is to send a XML Data like
<TYPE>
<VALUE01>Test1</VALUE01>
<VALUE02>Test1</VALUE02>
<VALUE03>Test1</VALUE03>
</TYPE>
<TYPE>
<VALUE01>Test2</VALUE01>
<VALUE02>Test2</VALUE02>
<VALUE03>Test2</VALUE03>
</TYPE>
How can is send more than one item throw XI Proxi?
Any Idea or Documentation?
Regards,
Robin

Hi Robin,
Hope these links provide good help
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/java proxies and sap xi - the inside story, part 1.pdf
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/java proxies and sap xi - the inside story, part ii.pdf
Regards
Vishnu

XI Java Proxy deploy on JBoss

Hello,
Can I deploy XI java Proxy inside JBoss application server
Appreciate you response.
Thanks

Hi,
<b>Yes</b>
You can deploy your Java Proxy inside JBoss Server (in any Application server). But this will be possible only for Client Java Proxy and not for Server Java Proxy.
I have succesfully completed those scenarios.
After generating Client Java proxy, create EJB application with generated Java classes for proxies and deploy it in JBoss.
Then you can access that EJB to pass inputs either in standalone application or some JSP.
Regards,
Uma

Deploy XI java Proxy inside JBoss application server

Hello,
Can I deploy XI java Proxy inside JBoss application server
Appreciate you response.
Thanks

Hi,
<b>Yes</b>
You can deploy your Java Proxy inside JBoss Server (in any Application server). But this will be possible only for Client Java Proxy and not for Server Java Proxy.
I have succesfully completed those scenarios.
After generating Client Java proxy, create EJB application with generated Java classes for proxies and deploy it in JBoss.
Then you can access that EJB to pass inputs either in standalone application or some JSP.
Regards,
Uma

How to generate java proxy in PI 7.1

Hi All,
How do I generate java proxy in PI 7.1
I am unable to see the "Generate Java Proxy" in the Tools menu in the Integration Builder
Edited by: Piyush Mathur SAP on Apr 15, 2010 11:14 AM
Edited by: Piyush Mathur SAP on Apr 15, 2010 11:14 AM

hi ,
As mentioned in the Question, I am unable to find the "Java Proxy Generattion" link in the Int builder.
Also the help doc says:
Java proxy generation is no longer supported in subsequent releases. For new developments or when making significant changes to a service interface, use Java proxy generation in SAP NetWeaver Studio instead. More information: Creating Outside-In Web Services, SAP NetWeaver Developer Studio.
Does that mean that I can no longer generate java proxy from Int builder?
regards,
Piyush

Generating Java Proxy

I am having some problems generating a particular java proxy... I've developed several
others without trouble...I suspect the issue is in the imported WSDL.
I have imported an existing WSDL into the "External Definitions" section of
Interface Objects in the Integration Builder ...no problems and the
"Messages" tab properly shows one message. I also checked the rendered
WSDL text on the "WSDL" tab and all looks fine. Note that this WSDL comes from a working web service that is running on a JBoss Applicatino server.
Next I create a Message Interface using this imported WSDL to define my
"Input" message - since this is Async, there is no corresponding "Response"
message - all this goes fine.
Finally, I right mouse click on the Message Interface to generate the Proxy
and at the last step after selecting the MI I get the following message from SAP:
Unable to generate proxies Construct <part type ="....">
not supported (path: <portType http://ram.proxy.test:B2B_JAVA_PROXY_GenerateStatements_MI>
<message http://ws.ferg.com/:GenerateStatements_getStatementInfo>)
The raw WSDL from the External Definitions "WSDL" tab is:
<?xml version="1.0" encoding="ISO-8859-1"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://ws.ferg.com/">
<wsdl:types>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap11enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns="http://ws.ferg.com/types" targetNamespace="http://ws.ferg.com/types">
<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
<xsd:complexType name="ArrayOfstring">
<xsd:complexContent>
<xsd:restriction base="soap11enc:Array">
<xsd:attribute ref="soap11enc:arrayType" wsdl:arrayType="string[]" />
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
</xsd:schema>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns2="http://ws.ferg.com/types">
<xsd:complexType name="GenerateStatements_getStatementInfo">
<xsd:sequence>
<xsd:element name="String_1" type="xsd:string" />
<xsd:element name="arrayOfString_2" type="ns2:ArrayOfstring" />
<xsd:element name="arrayOfString_3" type="ns2:ArrayOfstring" />
<xsd:element name="String_4" type="xsd:string" />
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</wsdl:types>
<wsdl:message name="GenerateStatements_getStatementInfoResponse" />
<wsdl:message name="GenerateStatements_getStatementInfo">
<wsdl:part name="GenerateStatements_getStatementInfo" type="GenerateStatements_getStatementInfo" />
</wsdl:message>
</wsdl:definitions>
My runtime environment info is:
Runtime Environment
Java version:
1.6.0_07
Java vendor:
Sun Microsystems Inc.
Version
Service pack:
13
Release:
NW04S_13_REL
Latest change:
34074
Any ideas would be appreciated ! Seems that if SAP was
going to have trouble with this WSDL it should have complained much earlier like when I imported the WSDL in the first place ...very frustrating !
Rod

According to this document
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2089f29b-b10a-2a10-5297-e258df0c1bfc
the syntax
<wsdl:part name="GenerateStatements_getStatementInfo" type="GenerateStatements_getStatementInfo" />
is not supported for java proxies.
Unfortunately, u will have to edit the wsdl for working with java proxy.
Regards,
Prateek

New way generating of Java Proxy to support parallel processing

Similar Messages

Maybe you are looking for