Java Proxy Exception

Hi all,
We are implementing a Inbound syncronous java proxy in our scenario. We were able to create and deploy the EJB successfully in the J2EE engine. The adpater configuration is also working fine. When we fire the message we are getting an exception in RWB saying
<b>Delivery of the message to the application using connection JPR failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Exception in method onMessage.: com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method onMessage.. Setting message to status failed.</b>
I'm unable to understand the error. Can somebody tell me what this exception means?
Regards
Arvind

Satish,
Thanks for the reply. My biggest confusion here is if the control is actually going to the proxy class.
>>>Delivery of the message to the application using connection JPR failed>>>
When it says delivery of message failed what does it mean , is the message not reaching the proxy class or is it becuase the proxy class is not able to send the message to atrget URL which is the logic which I have implemented in the class.
regards
Arvind

Similar Messages

JAVA Proxy :: Exception in ejb-jar.xml in NWDS

Hi All
I am getting exception while Importing (Inbound) JAVA Proxy ZIP file in NWDS, ejb-jar.xml shows the red cross & when I double click on it got following error -->
The content of element type "ejb-jar" is incomplete, it must match "(description?,display-name?,small-icon?,large-icon?,enterprise-beans,relationships?,assembly-descriptor?,ejb-client-jar?)".
I already add the following JAR files in class-path -->
aii_proxy_xirt.jar
aii_msg_runtime.jar
aii_utilxi_misc.jar
guidgenerator.jar
One different thing I also notice is that after adding these JAR files in classpath I am not getting my Inbound Interface BEAN under EJB candidates.
Also nothing is visible under ejbModule usually it shows 4 JAVA files & one template file.
As a solution I tried searching in google & forum for above exception, most threads suggest to add the Beans to xml files but I am not getting my interface Bean under EJB candidates.
I also tried reloading all the external JAR files again from System but still same issue.
Also within the same NWDS one another version of EJB is working fine but I worked on it 6months back, I tried copy its contents to ejb-jar.xml source code but then also nothing happens.
I am using NWDS Version: 7.0.10
Can you pls. suggest & let me know what further information I can provide from my side which can help you to investigate it.
Regards
Lalit

hi,
Your are using server java proxy.
You can use some other jar files apart from what you are using,.
ejb20.jar
exception.jar
sapj2eeclient.jar
and after importing your zip file (create a ejb project first ,then add the zar files and then click on the ejbModule and then import your zip file ) close and open your project.
Do not directly click on ejb-jar.xml.Click on ejbModule and import the .zip file.
then save your .template file in ejbModule as a .java project.
then there should not be any error.
you can refer
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d06315a6-e66e-2910-039c-ba8bbbd23702
regards,
ujjwal kumar

Getting Inbound Java Proxy Exception in method "onMessage"

I have built an Inbound Java proxy, deployed the EJB, viewed it in the J2EE admin tool, registered the JPR settings (also listAll, reviewed results, looks OK), configure the XI scenario. When I run the XI scenario using the Runtime workbench I get the following error in the BPM Synchronous Send step (calling the Java Proxy)
"com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method onMessage".
Does anyone have any suggestions?
What causes an "onMessage" Exception?

Thanks Sudhir Here is the process I am following to deploy my Proxy, would you please validate it. Created EJB Project in NWDS, unziped XI gened proxies into ejbModule folder, renamed *PortTypeImpl.template to *PortTypeImpl.java (will add real code later), compiled all code (no errors), edited ejb_jar.xml to match your suggested format, can view EJB Candidates (and see my Proxy Bean), built EJB.JAR file (via Wizard), created new Enterprise Application Project and pointed build path to my EJB Project, within the Enterprise Application Project I built an EAR file (which includes the "EJB Project JAR File", Deployed Enterprise Application Project to the XI J2EE Engine. I can log into XI J2EE Admin and see my EJB Project and the Proxy Bean I am trying to execute. Is this the process you used to deploy the proxy bean?
Also you you turn on JPR Tracing to see what parameters are passed into the JPR engine?

Java Proxy error: Exception in method methodExists

Hello all!
We are doing the following synchronous scenario: CRM->XI->JavaProxy--->Third party....
Here is the process we are following to deploy our Proxy:
1.Created EJB Module Project in NWDS
2.Import the files generated by XI into ejbModule folder from ZIP file.
3.Renamed *PortTypeImpl.template to *PortTypeImpl.java
4.Compiled all code (no errors)
5.Added all the references to the SAP libraries required (taken from our XI server):
com.sap.aii.proxy.xiruntime
com.sap.xi.util.misc
com.sap.aii.messaging.runtime
com.sap.guid
6.Codified Java Proxy codified the method <interfacename> in the <intefacename>_PortTypeImpl class.
7.Edited ejb_jar.xml to add EJBs.
8.Provided a JNDI name in the file ejb-j2ee-engine.xml.
9.Built EJB archive (no errors).
10.Created a new Enterprise Application Project and pointed build path to our EJB Project.
11.Added our EJB to the Enterprise Application project.
12.Created the references to the SAP libraries in the Enterprise Application Project in the application-j2ee-engine.xml file:
com.sap.aii.proxy.xiruntime
com.sap.xi.util.misc
com.sap.aii.messaging.runtime
com.sap.guid
13.Within the Enterprise Application Project we built an EAR file.
14.We deployed our .ear file to the J2EE Engine via Visual Admin (no errors).
15.We registered our Java Proxy on the ProxyServer, using
/register?ns=<interface_namespace>&interface=<XI_Interface_Name>&bean=<EJB_JNDI_name> &method=<name of the method implemented by you on the _PortTypeImpl>
Actually, we did the following:
url for registering the EJB:
http://ithpsrq0:50200/ProxyServer/register?ns=http://banco.popular.com.pr/xi/crm&interface=mi_AccountInfo_is&bean=popularinc.com/MiAccountInfoIs_Default&method=miAccountInfoIs
Message displayed when listing interfaces (http://ithpsrq0:50200/ProxyServer/listAll)
http://banco.popular.com.pr/xi/crm#mi_AccountInfo_is = popularinc.com/MiAccountInfoIs_Default:miAccountInfoIs
1 interfaces found
When running the interface we get the following error:
com.sap.aii.af.ra.ms.api.DeliveryException: Error checking method name miAccountInfoIs of remote inbound proxy bean $Proxy250: Exception in method methodExists.: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Error checking method name miAccountInfoIs of remote inbound proxy bean $Proxy250: Exception in method methodExists.
Does anyone have any suggestions?
What causes a "methodExists" Exception?
Please help us,
Thanks a lot!!!

Hi,
Is this a runtime of "com.sap.aii.proxy.xiruntime.core"
please check the jars used, adding this jars will solve this i guess.
aii_utilxi_misc.jar
ejb20.jar
exception.jar
jARM.jar
sapj2eeclient.jar
sapxmltoolkit.jar
aii_msg_runtime.jar
aii_proxy_xirt.jar
Also check, application-j2ee-engine.xml and see if,
com.sap.aii.proxy.xiruntime
com.sap.aii.messaging.runtime
com.sap.xi.util.misc
com.sap.guid
You wil get the jars in XI servers, you can ftp and get the jars, but you may need to search them.
Anotherthing, always take the jars from the xi servers to be sure you are compatible with the upgrades .
Hope this solves your problem.
Anirban.

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 while running java proxy in PI 7.1

Hi All,
I had created a java proxy using nwds 7.1. This java proxy is called by XI channel and its synchronous.
WHen i run my scenario in PI i am getting a error "Error while sending message: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing inbound message. Exception: No remote bean found for reference of class $Proxy2919
Kindly help me finding what can be the issue.
Regards,
Rajesh

Go to the JNDI Browser (Nwa -> Problem Management), and check if the proxy was deployed correctly with the exact name "Proxy2919".
Also, check the OSS note below.
#1292633 - JPR: Throwing "No remote bean found for reference of class"

Help - how to create java proxy (sender) in NWDS 7.1

Hi,
I am trying to develop a java proxy as sender to send message from WAS to PI.
I am using NWDS 7.1. Let me explain what I have done so far,
1. Received proxy classes from PI
2. Created a EJB Project, imported the proxy classes into EJB project
3. created a EJB bean, local interface in the EJB project and exposed as webservice
4. added the ejb to an ear
5. added reference to the following jar files (external library)
tcaiiproxy_rt_api.jar
com.sap.aii.af.sdk.jar
com.sap.aii.utilxi.server.jar
com.sap.aii.utilxi.core.jar
com.sap.aii.proxy.svc_api.jar
6. able to build and deploy the application
7. able to open the webservice in wsnavigator
Error encountered:
"Server Exception: javax.ejb.EJBException: nested exception is: java.lang.RuntimeException: java.lang.NoClassDefFoundError: com/sap/aii/proxy/xiruntime/core/AbstractType "
Questions:
1. Which method I should execute / call among all the proxy classes from local bean class to send message to PI?
2. Is it mandatory to add refernces to the application.xml, ejb-jar.xml and other xmls ?
3. How can I test / monitor the message being sent to PI interface?
Thanks and best regards,
Arun prabhu S

plz cross chk the references under application-j2eeengine.xml and ejb-jar.xml
http://wiki.sdn.sap.com/wiki/display/Java/JavaProxyChangesinPI7.1fromPI7.0
u can chk tis article also:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/508bb504-87cf-2c10-2aaf-f3a5df75e651?quicklink=index&overridelayout=true

Including helper classes in java proxy jar file

I must not be using the right header search criteria because I'm sure this question
has been asked before. In a Web Service File (.jws) I've imported a couple of
helper classes that function as data transfer objects. I did this to maintain
consistency with other portions of the application. The Java Proxy jar file generated
by Workshop does not include these files. Is there a way of including these dependencies
or do I need to distribute another jar file with my helper classes?

Hi Naichen,
I was able to successfully run both the autotype and clientgen Ant task, on the
WSDL you provided. The code behind those Ant tasks are pretty much what the WebLogic
Web Services test page run. Are you using WLS 8.1 SP2? If not, you might want
to try with that version.
Regards,
Mike Wooten
"Naichen Liu" <[email protected]> wrote:
>
>
>
Hi,
I am having a warning message when trying to generate java proxy jar
file on weblogic8.1
webservice test web app, the message is as follows:
"Warning Failed to generate client proxy from WSDL definition for this
service.
Prescription Please verify the <types> section of the WSDL."
in the mean time, on weblogic starting terminal, I saw the following
exceptions,
C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
t\schema\modifypnr\AlphaLength4Deserializer.java:36: cannot resolve symbol
symbol : class FacetUtils
location: package binding
weblogic.xml.schema.binding.FacetUtils.checkLengthFacet(__typed_obj,4L);
^
C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
t\schema\modifypnr\OSIFieldAnonTypeDeserializer.java:36: cannot resolve
symbol
symbol : class FacetUtils
location: package binding
weblogic.xml.schema.binding.FacetUtils.checkMaxLengthFacet(__typed_obj,69L);
^
C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
t\schema\modifypnr\AlphaLength2Deserializer.java:36: cannot resolve symbol
symbol : class FacetUtils
location: package binding
weblogic.xml.schema.binding.FacetUtils.checkLengthFacet(__typed_obj,2L);
^
C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
t\schema\modifypnr\FreeFormAnonTypeDeserializer.java:36: cannot resolve
symbol
symbol : class FacetUtils"
Can anybody help me about this issue? I attached WSDL file, also United
Airlines
got an enterprise weblogic license deal with BEA, any help will be highly
appreciated.
Thanks!!!
Naichen

Java Proxy error

Hi,
I have generated and deployed Java server proxy successfully in PI 7.1.
The problem is I am getting a error as follows
com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing inbound message. Exception: Cannot locate proxy bean sap.com/HTTPEAR/DeliveryInImp
I have regiered the bean using the URL already.
Should i add any jar references to my EAR explicitly and redeploy.
Regards,
Sudharshan N A

Hello,
You need to add the references of the proxy libraries (jars) in application-j2ee-engine.xml. Once you build the .ear file, you need to delete the libraries by unziping the .ear. Because, the proxy libraries (jar) should not be deployed as there are already existed in J2EE engine. Refer the following blog
/people/thorsten.nordholmsbirk/blog/2006/08/06/use-a-java-proxy-instead-of-a-jca-adapter
Regards,
Prasanna

ADAPTER.JAVA_EXCEPTION - java.lang.Exception: no valid message format obje

Hi experts,
we have a problem when we call a web service PI (release 7.01 , SP 10), from legacy system : the PI system return this message : ADAPTER.JAVA_EXCEPTION ; - java.lang.Exception: no valid message format object found
For to test this scenario we use soapUI tool.
I tried the URL (... /XISOAPAdapter/HelperServlet?action=FindChannel ...) in IE and got the following response :
<?xml version="1.0"; ?>
- <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
<channelID>11ccbb96a7f3349c895a005c9bc09cb7</channelID>
<name>CC_Soap_Sender_TestWS</name>
<type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
<direction>INBOUND</direction>
<party />
<service>BS_..........IDB_DEV</service>
</s:ChannelInfo>
so I think that this service is OK .
Thanks in advance for your help,
Alberto

Hi,
1) Check the URL once again- check for the extra spaces at the end of the link.
2) please refer below blog i hope it will help you
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4?QuickLink=index&overridelayout=true
Did you check the page no 14 of the document which has the same problem - in problem analysis it has mentioned that check the URL as well as proxy setting of internet browser.
3) Try to create the ID objects manually (Sender Channel and Sender Agreement).....when we use the wizard a * gets introduced in the unfilled (unused) fields (party etc) ....however when manually created the unused fields are left blank.
4) Check if all the ID objects are available in SXI_CACHE.
regards,
ganesh.

Got error when trying to generate Java proxy jar file for webservice

Hi,
I am having a warning message when trying to generate java proxy jar file on weblogic8.1
webservice test web app, the message is as follows:
"Warning Failed to generate client proxy from WSDL definition for this service.
Prescription Please verify the <types> section of the WSDL."
in the mean time, on weblogic starting terminal, I saw the following exceptions,
C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
t\schema\modifypnr\AlphaLength4Deserializer.java:36: cannot resolve symbol
symbol : class FacetUtils
location: package binding
weblogic.xml.schema.binding.FacetUtils.checkLengthFacet(__typed_obj,4L);
^
C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
t\schema\modifypnr\OSIFieldAnonTypeDeserializer.java:36: cannot resolve symbol
symbol : class FacetUtils
location: package binding
weblogic.xml.schema.binding.FacetUtils.checkMaxLengthFacet(__typed_obj,69L);
^
C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
t\schema\modifypnr\AlphaLength2Deserializer.java:36: cannot resolve symbol
symbol : class FacetUtils
location: package binding
weblogic.xml.schema.binding.FacetUtils.checkLengthFacet(__typed_obj,2L);
^
C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
t\schema\modifypnr\FreeFormAnonTypeDeserializer.java:36: cannot resolve symbol
symbol : class FacetUtils"
Can anybody help me about this issue? I attached WSDL file, also United Airlines
got an enterprise weblogic license deal with BEA, any help will be highly appreciated.
Thanks!!!
Naichen
[ModifyPNRWSContract.wsdl]

Hi Naichen,
I was able to successfully run both the autotype and clientgen Ant task, on the
WSDL you provided. The code behind those Ant tasks are pretty much what the WebLogic
Web Services test page run. Are you using WLS 8.1 SP2? If not, you might want
to try with that version.
Regards,
Mike Wooten
"Naichen Liu" <[email protected]> wrote:
>
>
>
Hi,
I am having a warning message when trying to generate java proxy jar
file on weblogic8.1
webservice test web app, the message is as follows:
"Warning Failed to generate client proxy from WSDL definition for this
service.
Prescription Please verify the <types> section of the WSDL."
in the mean time, on weblogic starting terminal, I saw the following
exceptions,
C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
t\schema\modifypnr\AlphaLength4Deserializer.java:36: cannot resolve symbol
symbol : class FacetUtils
location: package binding
weblogic.xml.schema.binding.FacetUtils.checkLengthFacet(__typed_obj,4L);
^
C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
t\schema\modifypnr\OSIFieldAnonTypeDeserializer.java:36: cannot resolve
symbol
symbol : class FacetUtils
location: package binding
weblogic.xml.schema.binding.FacetUtils.checkMaxLengthFacet(__typed_obj,69L);
^
C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
t\schema\modifypnr\AlphaLength2Deserializer.java:36: cannot resolve symbol
symbol : class FacetUtils
location: package binding
weblogic.xml.schema.binding.FacetUtils.checkLengthFacet(__typed_obj,2L);
^
C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
t\schema\modifypnr\FreeFormAnonTypeDeserializer.java:36: cannot resolve
symbol
symbol : class FacetUtils"
Can anybody help me about this issue? I attached WSDL file, also United
Airlines
got an enterprise weblogic license deal with BEA, any help will be highly
appreciated.
Thanks!!!
Naichen

Error in scenario for client Java Proxy

2006-04-28 15:30:49 Success Java proxy runtime (JPR) is transferring the request message to the messaging System
2006-04-28 15:30:49 Success Application attempting to send an XI message synchronously using connection JPR.
2006-04-28 15:30:49 Success Trying to put the message into the call queue.
2006-04-28 15:30:49 Success Message successfully put into the queue.
2006-04-28 15:30:49 Success The message was successfully retrieved from the call queue.
2006-04-28 15:30:49 Success The message status set to DLNG.
2006-04-28 15:30:50 Error Received XI System Error. ErrorCode: NO_RECEIVER_CASE_BE ErrorText: ErrorStack: No receiver could be determined
2006-04-28 15:30:50 Error Returning synchronous error notification to calling application: XIServer:NO_RECEIVER_CASE_BE:.
2006-04-28 15:30:50 Error Transmitting the message using connection http://<SERVER>:<PORT>/sap/xi/engine?type=entry failed, due to: XIServer:NO_RECEIVER_CASE_BE:.
2006-04-28 15:30:50 Error The message status set to FAIL.
2006-04-28 15:30:50 Error Returning to application. Exception: XIServer:NO_RECEIVER_CASE_BE:
2006-04-28 15:30:50 Error JPR failed to transfer the request message to the messaging system. Reason: XIServer:NO_RECEIVER_CASE_BE:
I am getting this in the audit log for a Java Proxy <> XI <> RFC scenario. What could be the problem?
the configuration in integration directory seems to be perfectly fine however the message flow fails giving this error <b>NO_RECEIVER_CASE_BE</b>
Regards,
Amol

HI Amol,
Did you check the Message type/Message Inetrface names in the Java Proxy ?
Also check for Receiever Determinations in the configuration.
I assume that , you have created the Communication Channel under the Business System created as Standalone Java System.. If not check this.
Go to SXI_CACHE and check for the Receiever Determination created in the Configuration...
Hope this helps,
regards,
Moorthy

Error while calling the java proxy with the ValueMapping repl scenario

Hi All
I am trying to upload values in the RWB for vaue mapping using the standard ValueMappingReplication interface . But I can see the following message in the Message Display Tool of the RWB .This scenario was working fine sometime back suddenly after some days we started to see this exception .
JPR could not process the message. Reason: No such method valueMappingReplication (for the asynchronous replication scenario) in proxy bean localejbs/sap.com/com.sap.xi.services/ValueMappingApplication
Delivery of the message to the application using connection JPR failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: No such method valueMappingReplication (for the asynchronous replication scenario) in proxy bean localejbs/sap.com/com.sap.xi.services/ValueMappingApplication: com.sap.aii.proxy.xiruntime.core.XmlInboundException: No such method valueMappingReplication (for the asynchronous replication scenario) in proxy bean localejbs/sap.com/com.sap.xi.services/ValueMappingApplication.
Can anyone please guide me what could be the done to resolve this .
Thanks.

This may happen when the java proxy is not registered. Use the following URL to do so
http://<Server>:<Port>/ProxyServer/register?ns=http://sap.com/xi/XI/System&interface=ValueMappingReplication&bean=localejbs/sap.com/com.sap.xi.services/ValueMappingApplication&method=valueMappingReplication
Regards,
Prateek

Execute Fault Message in Java Proxy

Hello,
I Call my Java Inbound Proxy and catch an exception.
How can i send now a Faul Message back to XI ?
} catch (Exception ex4) {
               ExchangeFaultData_Type faultData = new ExchangeFaultData_Type();
               faultData.setFaultText(ex4.getMessage());
               ErrorReturn_Type errorReturn = new ErrorReturn_Type();
               errorReturn.setStandard(faultData);
What should i do ?
Regards,
Robin

Hi Robin:
Without knowing your complete code, I think what your are missing is "gluining" everything together, something like this:
Somewhere in your code, define some variables:
      ExchangeFaultData_Type      faultData                   = null;
      FmJpAviso_Type              fmJpAviso_Type              = null;
      FmJpAviso_Message           fmJpAviso_Message           = null;
      FmJpAviso_Message_Exception fmJpAviso_Message_Exception = null;
      catch( HibernateException ehibernate )
       mensajeError = new StringBuffer();
       mensajeError.append(DataComercial.PED_XI_BDI_DMS_DC_001).append("\n\n")
                            .append(ehibernate.toString());
       catAPPL.fatalT(logger,mensajeError.toString());
          // Default Integration Scenario ExchangeFault Message
       faultData = new ExchangeFaultData_Type();
       faultData.setFaultText(mensajeError.toString());
           // My Fault Message Type for the inbound Message Interface
       fmJpAviso_Type = new FmJpAviso_Type();
       fmJpAviso_Type.setStandard(faultData);
           // My Fault Message
       fmJpAviso_Message = new FmJpAviso_Message();
       fmJpAviso_Message.setFmJpAviso(fmJpAviso_Type);
          // My Fault Message Exception
       fmJpAviso_Message_Exception = new FmJpAviso_Message_Exception();
       fmJpAviso_Message_Exception.setFmJpAviso_Message(fmJpAviso_Message);
       ehibernate = null;
       mensajeError = null;
          // Inform XI about this situation in the Java Proxy
       throw fmJpAviso_Message_Exception;
Hope this helps,
Regards, Pedro

Sender java proxy don't work

Hello!
i configured a test xi scenario: JSP->(JAVA Proxy)-> XI -> file adapter.
Jsp is in the same bean of proxy.
I deploy this j2ee application in the same j2ee of XI.
When I open jsp page with browser and send data, nothing appened.
I check also in adapter engine monitor and xml monitor but i can't see any message.
I think the problem is inside java bean because if i fix the output data, after post action i see data in jsp page.
this is the class for call proxy:
public class InvokeProxy {
     public String getRole(String name, String pwd){
          String role="";
          UsersSyncMI_PortTypeLocalHome queryOutLocalHome=null;
          UsersSyncMI_PortTypeLocal queryOutLocal=null;
          try{ Context ctx = null; Object ref = null; Properties p = new Properties();
          p.put(Context.INITIAL_CONTEXT_FACTORY,"com.sap.engine.services.jndi.InitialContextFactoryImpl");
          p.put(Context.PROVIDER_URL, "server:50004");
          p.put(Context.SECURITY_PRINCIPAL, "user");
          p.put(Context.SECURITY_CREDENTIALS, "pwd");
          ctx = new InitialContext();
          queryOutLocalHome = (UsersSyncMI_PortTypeLocalHome)ctx.lookup("java:comp/env/ejb/UsersSyncMI_PortTypeBean");
          queryOutLocal = queryOutLocalHome.create();
          MessageSpecifier msg = queryOutLocal.$messageSpecifier();
          msg.setSenderService("BS_XID_PROXY");
          queryOutLocal.$messageSpecifier(msg);
          UserDT_Type reqtype = new UserDT_Type();
          reqtype.setUsername(name);
          reqtype.setPassword(pwd);
          UsersDBDTResponse_Type response = new UsersDBDTResponse_Type();
          response = queryOutLocal.usersSyncMI(reqtype);
          role = role + response.getStatementResponse().get_as_listRow().getRow(0).getRole();
           } catch(Exception ex){
               System.out.println(ex.getMessage()); } return role; }
any suggestion
thanks Ale

I haven't J2SE in my scenario. I can't try.
anyway, the code that i'm using now for call proxy is:
try{ Context ctx = null; Object ref = null; Properties p = new Properties();
            ctx = new InitialContext();
          ref = ctx.lookup("java:comp/env/ejb/MIZPROTOTIPOOUT_PortTypeBean");
          queryOutLocalHome = (MIZPROTOTIPOOUT_PortTypeLocalHome)ctx.lookup("java:comp/env/ejb/MIZPROTOTIPOOUT_PortTypeBean");
          queryOutLocal = queryOutLocalHome.create();
          MessageSpecifier msg = queryOutLocal.$messageSpecifier();
          msg.setSenderService("BS_XID_PROXY");
          queryOutLocal.$messageSpecifier(msg);
          DTZPROTOTIPOOUT_Type reqtype = new DTZPROTOTIPOOUT_Type();
          reqtype.setData1(name);
          reqtype.setData1(pwd);
          DTZRETURN_Type response = new DTZRETURN_Type();
          queryOutLocal.mIZPROTOTIPOOUT(reqtype);
          String respons = "work!";
          role = respons;
           } catch(Exception ex){
               System.out.println(ex.getMessage());
               String error = ex.getMessage();
               role = error;
      return role; }

Java Proxy Exception

Similar Messages

Maybe you are looking for