Web service client stubs generation

Hi,
I try to generated model for WebDynpro application based on Web service (deprecated). WSDL file is valid. Stub classes generation is completed with compilation error. I found that the generator builds strange method for CMapLayerField complex type. There is setter with java.util.List param for MapLayer field but no one exists for Metafields field. Why for? Metafields field has the same cardinality as MapLayer one. Please, take me advance. I don't understand generation mechanism. I tried Axis2 and no problem was. How to fix this problem? How can I use Axis2 WSDL2Java generator instead of SAP Schema to Java generator?
The problem is below described in details. Compilation failed due to type cast error. The error message is:
The method setMapLayer(CMapLayer) in the type CMapLayerField is not applicable for the arguments (CMapLayer[])
Below I give some scrap from WSDL and generated Java class.
WSDL
==============
      <s:complexType name="CMapLayerField">
        <s:complexContent mixed="false">
          <s:extension base="tns:CTable">
            <s:sequence>
              <s:element minOccurs="0" maxOccurs="1" name="Metafields" type="tns:CMetafields" />
              <s:element minOccurs="0" maxOccurs="1" name="MapLayer" type="tns:CMapLayer" />
              <s:element minOccurs="1" maxOccurs="1" name="MapLayerFieldIsName" type="s:int" />
            </s:sequence>
          </s:extension>
        </s:complexContent>
      </s:complexType>
Generated API class for CMapLayerField type
==============================
package com.test.model;
public class ComplexType_CMapLayerField
private com.test.model.proxies.types.CMapLayerField originalBean;
//skipped
private com.test.model.ComplexType_CMetafields metafields;
/** sets the JavaWrapper in the relationship**/
public void setMetafields(com.test.model.ComplexType_CMetafields arg)
     this.metafields = arg;           
sets the original bean in the relationship
  public void setMetafields(com.test.model.proxies.types.CMetafields origBean)
     if(this.metafields == null)
          this.metafields = new com.test.model.ComplexType_CMetafields ();
     this.metafields.setOriginalBean(origBean);           
private java.util.List _mapLayer = null;
public void setMapLayer (java.util.List list)
     com.test.model.proxies.types.CMapLayer[] array = new com.test.model.proxies.types.CMapLayer[list.size()];
     for(int i=0;i<list.size();i++)
          com.test.model.ComplexType_CMapLayer item = (com.test.model.ComplexType_CMapLayer)list.get(i);
           array<i> = item.getOriginalBean();
     getOriginalBean().setMapLayer(array);
     this._mapLayer = list;
public void setMapLayer (com.test.model.proxies.types.CMapLayer[] args)
     if(_mapLayer == null) _mapLayer = new java.util.ArrayList();
     if (args == null ) return ;
     for(int i=0;i<args.length;i++)
          com.test.model.ComplexType_CMapLayer wrapper = new com.test.model.ComplexType_CMapLayer ();
          wrapper.setOriginalBean(args<i>);
          _mapLayer.add(wrapper);     
//skipped
Generated stub class for CMapLayerField type
===================================
package com.test.model.proxies.types;
public  class CMapLayerField extends com.test.model.proxies.types.CTable {
  //some line were skipped
  private com.test.model.proxies.types.CMetafields fMetafields;
  public void setMetafields(com.test.model.proxies.types.CMetafields _Metafields) {
    this._f_Metafields = _Metafields;
    this._f_hasMetafields = true;
  private com.test.model.proxies.types.CMapLayer fMapLayer;
  private boolean fhasMapLayer;
  public void setMapLayer(com.test.model.proxies.types.CMapLayer _MapLayer) {
    this._f_MapLayer = _MapLayer;
    this._f_hasMapLayer = true;

Obsolete

Similar Messages

  • ABAP Web Service client proxy - generation problems

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

    Resolved through SAP Help. Refer SAP note# 0001403271.

  • Web service client stub had exception

    Hi there,
    I'm new to Oracle AS(10.1.2). I used JDeveloper 10.1.3 created web service, and client stub. When I called the web service from client stub, I got the following error:
    [SOAPException: faultCode=SOAP-ENV:Server; msg=java.math.BigDecimal.&lt;init&gt;(I)V [java.lang.NoSuchMethodError]]
    I didn't find any problem with my parameters passing from client to the WS.
    Anybody can help?
    Thanks,
    Helen

    Hi there,
    I'm new to Oracle AS(10.1.2). I used JDeveloper 10.1.3 created web service, and client stub. When I called the web service from client stub, I got the following error:
    [SOAPException: faultCode=SOAP-ENV:Server; msg=java.math.BigDecimal.&lt;init&gt;(I)V [java.lang.NoSuchMethodError]]
    I didn't find any problem with my parameters passing from client to the WS.
    Anybody can help?
    Thanks,
    Helen

  • Web Service and Stub-generation with WTK

    Hi there,
    I hope someone can help me.
    I just deployed a webservice using Axis.
    WSDL: http://www.freewebs.com/sirpreis/CustomerWS.xml
    WSDD (for deployment): http://www.freewebs.com/sirpreis/customerWS-WSDD.xml
    The WS deploys fine, but now I want to generate stubs using the WTK stub generator. Unfortunately I get the following warnings:
    warning: R2716 WSI-BasicProfile ver. 1.0, namespace attribute not allowed in doc/lit for soapbind:body: "getAccountBalance"
    warning: R2716 WSI-BasicProfile ver. 1.0, namespace attribute not allowed in doc/lit for soapbind:body: "getAccountBalance"
    I don't know if that will become a problem...
    Well now, three classes + src are generated
    AuthSet.java/.class
    CustomerWS.java/.class
    CustomerWS_Stub.java/.class
    In my webservice, the method "getAccountBalance" gets an "AuthSet" (which is set up of a String pwd and an int userID) as argument
    (public int getAccountBalance(AuthSet auth) throws RemoteException {).
    In the CustomerWS_Stub.java now there is a method "getAccountBalance", but it gets the following:
    public int getAccountBalance(java.lang.String pwd, int userID) throws java.rmi.RemoteException {
    Can anyone help me with that? I don't know what to do :(

    Hi,
    I think its a problem of your wsdl-File. If you post it, it would be easier to find the problem. The wsdl-file don't provide the WS-I specifications.
    Steve

  • Web Service - Client Proxy generation error

    Hi All,
    I tried creating a client proxy using an URL provided to me and followed the steps using the wizard. I end up in getting the following error messages. Could anyone throw some light on resolving this? I do not have any idea about what WSDL is. Any help is highly appreciated. Not able to attach the WSDL code here.
    Below is the error message upon client proxy creation:
    Proxy-Generierung: Fehler aufgetreten
    Exception occurred in library handler
    Not implemented
    Thanks
    Srini
    Edited by: Srinivasan Karunakaran on Oct 22, 2010 11:11 PM

    Resolved through SAP Help. Refer SAP note# 0001403271.

  • Web Service Client Generation on 7.10 SP3 - No WSDL URL is specified....

    We have a mysterious problem here.
    In out ABAP system we had a WebService created. With "New - Web Service Client" we created a web service client on the java side for that one and we were able to invoke it.
    We had to recreate this Web service due to wrong naming conventions. And now the problem starts.
    In the Main service class we had before something generated by NWDS:
    private static java.net.URL SERVICES_SERVICE_WSDL_LOCATION = null;
    static {
        java.net.URL url = null;
        try {
              java.net.URL tmpUrl = Thread.currentThread().getContextClassLoader().getResource("wsdl/com/sap/document/sap/soap/functions/mc_style/sap/bc/srt/wsdl/bndg_001279D063121DECA58AC5F7200DC55D/wsdl11/allinone/ws_policy/document/rootwsdl_SERVICES.wsdl");
              url = new java.net.URL(tmpUrl.getProtocol(), tmpUrl.getHost(), tmpUrl.getPort(), tmpUrl.getFile());
        } catch (java.net.MalformedURLException e) {
          e.printStackTrace();
        SERVICES_SERVICE_WSDL_LOCATION = url;
    After the new creation with the new Web Service this static initializer is gone an we see:
    private final static java.net.URL SERVICE_WSDL_LOCATION = null;
    This code is ridiculous, to make something static final and set it to Null. And as expected at runtime it results in WebServioceException telling us:
    No WSDL URL is specified for service [class com.sap.document.sap.soap.functions.mc_style.Service] on service creation.
    Anyone knows what is going wrong here??
    Best regards,
    Frank

    Same problem here.
    From Netweaver dev studio, I'm generating a deployable proxy for a Session Bean that is supposed to access a webservice but I keep getting the exception:
    "Caused by: javax.xml.ws.WebServiceException: No WSDL URL is specified for service [class eu.socrades.sap.ServiceMonitorBeanTESTService] on service creation.
    at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.<init>(SAPServiceDelegate.java:108)
    at com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider.createDelegate(CTSProvider.java:170)
    at com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider.createServiceDelegate(CTSProvider.java:151)
    at javax.xml.ws.Service.<init>(Service.java:57)
    at eu.socrades.sap.ServiceMonitorBeanTESTService.<init>(ServiceMonitorBeanTESTService.java:14)"
    I'm injecting the reference to the service with:
    @WebServiceRef(wsdlLocation = "rootwsdl_ServiceMonitorBeanTESTService.wsdl")
    private ServiceMonitorBeanTESTService service;
    I tried changing the location to a URL (where the wsdl can be downloaded from) or to "META-INF/wsdl/eu/socrades/sap/rootwsdl_ServiceMonitorBeanTESTService/rootwsdl_ServiceMonitorBeanTESTService.wsdl" but that did not help.
    Any clue?
    Thanks a lot,
    Dom

  • Web Service Client Generation.

    <b>Hi
    I have deployed an EJB as a web service, now am trying to create a client using the web service client wizard in NWDS to test the web service. I pass the wsdl url to the wizard for the service definition, move the slider for Test client and change the web service runtime to SAP Netweaver and say Next. Then the wizard asks for the Output Folder and i use the default folder and say Next. Now at this point an error comes which says,</b>
    Publishing failed
      Error during deployment:
          com.sap.ide.eclipse.sdm.deploy.DeploymentException: DeploymentException.
          Reason: An error occurred while deploying the deployment item 'sap.com_SummitOrder_140207ClientEAR'.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: sap.com_SummitOrder_140207ClientEAR
          sdu file path: C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear
          version status: NEW
          deployment status: Admitted
          description:
          1. Error:
          Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
          Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
          No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
          The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
          Possible reasons :
          1.An AS Java service, which is providing a container, is stopped or not deployed.
          2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
          . Cannot deploy it.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.deploy.server.utils.DSRemoteException: Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
          Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
          No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
          The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
          Possible reasons :
          1.An AS Java service, which is providing a container, is stopped or not deployed.
          2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
          at com.sap.ide.eclipse.sdm.threading.DCDeployThread.run(DCDeployThread.java:145)
    Nested exception -
          com.sap.engine.services.dc.api.deploy.DeployException: DeploymentException.
          Reason: An error occurred while deploying the deployment item 'sap.com_SummitOrder_140207ClientEAR'.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: sap.com_SummitOrder_140207ClientEAR
          sdu file path: C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear
          version status: NEW
          deployment status: Admitted
          description:
          1. Error:
          Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
          Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
          No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
          The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
          Possible reasons :
          1.An AS Java service, which is providing a container, is stopped or not deployed.
          2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
          . Cannot deploy it.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.deploy.server.utils.DSRemoteException: Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
          Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
          No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
          The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
          Possible reasons :
          1.An AS Java service, which is providing a container, is stopped or not deployed.
          2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
          at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:734)
          at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:220)
          at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:111)
          at com.sap.ide.eclipse.sdm.threading.DCDeployThread.run(DCDeployThread.java:119)
          Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: An error occurred while deploying the deployment item 'sap.com_SummitOrder_140207ClientEAR'.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: sap.com_SummitOrder_140207ClientEAR
          sdu file path: C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear
          version status: NEW
          deployment status: Admitted
          description:
          1. Error:
          Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
          Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
          No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
          The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
          Possible reasons :
          1.An AS Java service, which is providing a container, is stopped or not deployed.
          2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
          . Cannot deploy it.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.deploy.server.utils.DSRemoteException: Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
          Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
          No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
          The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
          Possible reasons :
          1.An AS Java service, which is providing a container, is stopped or not deployed.
          2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
          at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:186)
          at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:47)
          at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:177)
          at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
          at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:76)
          at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:624)
          at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:483)
          at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:206)
          at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:153)
          at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:807)
          at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:253)
          at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:109)
          at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:841)
          at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:125)
          at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:59)
          at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
          at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:168)
          Caused by: java.rmi.RemoteException:  class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: sap.com_SummitOrder_140207ClientEAR
          sdu file path: C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear
          version status: NEW
          deployment status: Admitted
          description:
          1. Error:
          Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
          Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
          No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
          The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
          Possible reasons :
          1.An AS Java service, which is providing a container, is stopped or not deployed.
          2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
          . Cannot deploy it.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.deploy.server.utils.DSRemoteException: Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
          Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
          No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
          The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
          Possible reasons :
          1.An AS Java service, which is providing a container, is stopped or not deployed.
          2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
          at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.performDeployment(ApplicationDeployer.java:162)
          at com.sap.engine.services.dc.gd.impl.GenericDeliveryImpl.deploy(GenericDeliveryImpl.java:54)
          at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:157)
          ... 16 more
          Caused by: java.rmi.RemoteException:  class com.sap.engine.services.deploy.server.utils.DSRemoteException: Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
          Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
          No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
          The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
          Possible reasons :
          1.An AS Java service, which is providing a container, is stopped or not deployed.
          2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
          at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:302)
          at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.performDeployment(ApplicationDeployer.java:150)
          ... 18 more
    <b>Now what can be the reason for this failure, is there any configuration issues with the server which i have to take care of.
    Also is there any other way of testing a web service in NWDS. I tried using soap sonar as was specified in one article on SDN, but either you have to but that product or use a trial version, which expires after some days.
    Please help me on this.
    Thanks & Regards
    Bhupesh...</b>

    I tried with the project <i>type</i> as 'SAP Application Client Project', then this error comes,
    Publishing failed
      Error during deployment:
          com.sap.ide.eclipse.sdm.deploy.DeploymentException: DeploymentException.
          Reason: An error occurred while deploying the deployment item 'sap.com_DummyClientEAR'.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: sap.com_DummyClientEAR
          sdu file path: C:\SAP\DevStudio\eclipse\workspace\DummyClientEAR\DummyClientEAR.ear
          version status: NEW
          deployment status: Admitted
          description:
          1. Error:
          Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
          Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.deploy.server.utils.DSRemoteException: Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
          Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
          java.rmi.RemoteException:  com.sap.engine.services.library_container.deploy.LCDeploymentException: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.
          at com.sap.ide.eclipse.sdm.threading.DCDeployThread.run(DCDeployThread.java:145)
    Nested exception -
          com.sap.engine.services.dc.api.deploy.DeployException: DeploymentException.
          Reason: An error occurred while deploying the deployment item 'sap.com_DummyClientEAR'.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: sap.com_DummyClientEAR
          sdu file path: C:\SAP\DevStudio\eclipse\workspace\DummyClientEAR\DummyClientEAR.ear
          version status: NEW
          deployment status: Admitted
          description:
          1. Error:
          Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
          Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.deploy.server.utils.DSRemoteException: Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
          Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
          java.rmi.RemoteException:  com.sap.engine.services.library_container.deploy.LCDeploymentException: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.
          at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:734)
          at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:220)
          at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:111)
          at com.sap.ide.eclipse.sdm.threading.DCDeployThread.run(DCDeployThread.java:119)
          Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: An error occurred while deploying the deployment item 'sap.com_DummyClientEAR'.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: sap.com_DummyClientEAR
          sdu file path: C:\SAP\DevStudio\eclipse\workspace\DummyClientEAR\DummyClientEAR.ear
          version status: NEW
          deployment status: Admitted
          description:
          1. Error:
          Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
          Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.deploy.server.utils.DSRemoteException: Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
          Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
          java.rmi.RemoteException:  com.sap.engine.services.library_container.deploy.LCDeploymentException: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.
          at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:186)
          at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:47)
          at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:177)
          at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
          at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:76)
          at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:624)
          at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:483)
          at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:206)
          at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:153)
          at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:807)
          at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:253)
          at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:109)
          at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:841)
          at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:125)
          at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:59)
          at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
          at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:168)
          Caused by: java.rmi.RemoteException:  class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: sap.com_DummyClientEAR
          sdu file path: C:\SAP\DevStudio\eclipse\workspace\DummyClientEAR\DummyClientEAR.ear
          version status: NEW
          deployment status: Admitted
          description:
          1. Error:
          Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
          Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.deploy.server.utils.DSRemoteException: Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
          Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
          java.rmi.RemoteException:  com.sap.engine.services.library_container.deploy.LCDeploymentException: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.
          at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.performDeployment(ApplicationDeployer.java:162)
          at com.sap.engine.services.dc.gd.impl.GenericDeliveryImpl.deploy(GenericDeliveryImpl.java:54)
          at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:157)
          ... 16 more
          Caused by: java.rmi.RemoteException:  class com.sap.engine.services.deploy.server.utils.DSRemoteException: Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
          Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
          java.rmi.RemoteException:  com.sap.engine.services.library_container.deploy.LCDeploymentException: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.
          at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:299)
          at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.performDeployment(ApplicationDeployer.java:150)
          ... 18 more
          Caused by: java.rmi.RemoteException:  com.sap.engine.services.library_container.deploy.LCDeploymentException: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.
          at com.sap.engine.services.library_container.deploy.LibraryContainer.addLibsFromClassPathElement(LibraryContainer.java:328)
          at com.sap.engine.services.library_container.deploy.LibraryContainer.addLibsFromClassPathElements(LibraryContainer.java:290)
          at com.sap.engine.services.library_container.deploy.LibraryContainer.getDeployableFiles(LibraryContainer.java:220)
          at com.sap.engine.services.library_container.deploy.LibraryContainer.deploy(LibraryContainer.java:148)
          at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:506)
          at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:248)
          at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:215)
          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:371)
          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:405)
          at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2298)
          at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:286)
          ... 19 more
    <b>What can be the reason for this?</b>

  • XML Parser Error while creating Web service Client using JAX RPC

    hello evryone,
    Im facing XML Parser Error while creating web service client using JAX RPC. Im using Net Beans IDE for development purpose. I have wrote configuration file for client. Now i want to create Client stub. However i dont know how to do this in Net Beans. So i tried to do it from Command promt using command :
    wscompile -gen:client -d build -classpath build config-wsdl.xml
    here im getting Error:
    error parsing configuration file: XML parsing error: com.sun.xml.rpc.sp.ParseException:10: XML declaration may only begin entities
    Please help me out.
    Many thanks in advance,
    Kacee

    Can i use the client generated using jdeveloper 11g to import into the oracle forms 10g, i.e., form builder 10g. Currently this is the version we have in our office.

  • Error creating a web service client from th WSDL document (soamanager)

    Hello everyone,
    we have generate with the wizard a web-service using the function module BAPI_CONTROL_RECIPE_GET_LIST. Then we have generated with SOAMANAGER the end point. As test, we have used a web-service explorer of Eclispe and we can retrieve without problems the data.
    Then we wanted to generate the web-servcie client with Eclipse Galileo (3.5.0) wiith the server GlassFish v2.1 Java EE 5 we first installed the WSIT jars, in order to support WS-RM protocol
    We have started the generation based on the document obtainend within the soamanager under the "Open WSDL document for selected binding" link.
    We have tried it several times and we always got the following error is:
    IWAB0399E Error in generating Java from WSDL: WSDLException (at /wsdl:definitions/wsdl:portType/wsp:Policy):
    faultCode=INVALID_WSDL: Encountered unexpected element 'Policy'.: <br>
        WSDLException (at /wsdl:definitions/wsdl:portType/wsp:Policy): faultCode=INVALID_WSDL: Encountered unexpected element 'Policy'.:
    at com.ibm.wsdl.util.xml.DOMUtils.throwWSDLException(Unknown Source)
    at com.ibm.wsdl.xml.WSDLReaderImpl.parsePortType(Unknown Source)
    at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
    at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
    at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
    at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
    at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:516)
    at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495)
    at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
    at java.lang.Thread.run(Unknown Source)
    Do you know if we took the right document in order to generate the web-service client? Do we need to have some specifics settings in the configurations of th endpoint? (provider security, transport settings, etc...?)
    If needed, or if someone would be nice enough to try to generate it on its side, I can post here the whole wsdl document, but due to its length, I first wait your comments.
    Thanks a lot in advance for your feed-back
    best regards
    Pierre-André
    addtions:
    maybe this should have been better posted within the forum Service-Oriented Architecture than standards?
    I forgot to mention the following threads, which seems to me to be somehow in this direction. But I do not get really how I could use them, or how is is releated.
    Edited by: Pierre-andre Jacquod on Sep 23, 2009 4:02 PM

    Hi,
    I am facing the same issue while generating the client java class from IBM RAD 6.0.
    Here is the error I am getting.
    WSDLException (at /wsdl:definitions/wsdl:portType/wsp:Policy): faultCode=INVALID_WSDL: Encountered unexpected element 'Policy'.:
         [java] at com.ibm.wsdl.util.xml.DOMUtils.throwWSDLException(Unknown Source)
         [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parsePortType(Unknown Source)
         [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
         [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
         [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
         [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
         [java] at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:516)
         [java] at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495)
         [java] at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
         [java] at java.lang.Thread.run(Thread.java:571)
    Please guide me to resolve this issue.
    Thanks & Regards,
    Vijay

  • Deploying Web Service clients to earlier versions of AS

    Hello,
    I'm using JDeveloper to create web service proxy for existing service to use in my Web Service client. For development, I'm using JDeveloper 10.1.3.3, for deployment of client application I'm using Application Server 10.1.3.0.
    The problem is that AS 10.1.3.0 contains other versions of the libraries, for example, wsclient.jar, so, there's an error using Web Service Proxy (stub) as method setSOAPVersion() doesn't exist.
    The question is how can I use generated stub with earlier versions of Application Server.
    I've tried some things, but they didn't work. Maybe I did something wrong and step-by-step guidelines to deploy application are needed - I hope, it could be useful not only for me.
    So, I found JDev 10.1.3 Release Notes (http://www.oracle.com/technology/products/jdev/htdocs/10.1.3.0.3/readme.html) and the following abstract:
    Workaround for URL / WS Data Control Apps When Deploying to Third Party Application Servers or Oracle Application Server 10.1.2 (4931009)
    1. Copy the following JAR files to your target application server along with the rest of the ADF installed JAR files. The following JAR files are available under your JDeveloper's home directory.
    bc4j/jlib/dc-adapters.jar
    bc4j/jlib/adf-connections.jar
    j2ee/home/lib/http_client.jar
    webservices/lib/wsdl.jar
    webservices/lib/orajaxr.jar
    webservices/lib/orawsrm.jar
    webservices/lib/wsclient.jar
    webservices/lib/orasaaj.jar
    webservices/lib/xsdlib.jar
    webservices/lib/mdds.jar
    jlib/osdt_core.jar
    jlib/osdt_cert.jar
    jlib/osdt_xmlsec.jar
    jlib/osdt_wss.jar
    jlib/osdt_saml.jar
    jlib/ojpse.jar
    jlib/oraclepki.jar
    webservices/lib/wssecurity.jar
    webservices/lib/orawsdl.jar
    j2ee/home/jazncore.jar
    2. Shutdown the application server and modify the application server's class path to include all of the JAR files that were extracted from the archive. Please refer to the application server documentation for details on how to modify the class path.
    3. Restart the application server. You are now ready to deploy / run the application successfully.
    So, I've created a new Shared Library with Enterprise Manager, uploaded all this files and, deploying application, checked this library too. This didn't help.
    Thanks in advance, Valeriy

    Hi Valeriy,
    I have exactly the same problem. Have you been able to resolve this yet?
    Thanks
    Stu

  • Web service client type

    Hi,
    I am new to web services. I need to write a web service client that invokes a web service method. The method takes complex types as parameter and returns a complex type.what kind of client(static stub, dynamic proxy or DII) should I use to invoke such kind of method from a standalone java application?
    Thanks in advance.

    yes, you are right. stubs must be regenerated when the service definition changes. But is it possible to write a standalone client using dynamic proxy to invoke a web service method that uses complex types as parameters?.

  • Web service client timeout

    Hi,
    I'm trying to set a timeout on my web service client. But its not working. Your tutorials do not seem to address this.
    I am using weblogic 10.3.2, with Java 1.6.
    ============
    Properties propSys = System.getProperties();
    propSys.put( "weblogic.webservice.UseWebLogicURLStreamHandler", "true" );
    Stub stub = (Stub)portObject;
    BindingInfo bindingInfo = (weblogic.webservice.binding.BindingInfo)stub._getProperty("weblogic.webservice.bindinginfo");
    bindingInfo.setTimeout(1);
    Iterator itr = stub._getPropertyNames();
    while (itr.hasNext()){
    Object element = itr.next();
    log("\n properties that can be set: "+element);
    stub._setProperty("weblogic.webservice.rpc.timeoutsecs","1");
    ===========
    I've also tried setting the transaction-timeout and the remove-client-timeout in the weblogic-ear-jar.xml.
    ===========
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>ExternalEntryEJB</ejb-name>
    <transaction-descriptor>
    <trans-timeout-seconds>1</trans-timeout-seconds>
    </transaction-descriptor>
    <enable-call-by-reference>True</enable-call-by-reference>
    <jndi-name>ExternalEntry</jndi-name>
    <remote-client-timeout>1</remote-client-timeout>
    </weblogic-enterprise-bean>
    <weblogic-enterprise-bean>
    <ejb-name>InternalEJB</ejb-name>
    <local-jndi-name>Internal</local-jndi-name>
    <enable-call-by-reference>True</enable-call-by-reference>
    <remote-client-timeout>1</remote-client-timeout>
    <transaction-descriptor>
    <trans-timeout-seconds>1</trans-timeout-seconds>
    </transaction-descriptor>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    ===========
    in case it matters, I am using weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask as the clientgen task in my build.xml
    ============
    <clientgen autotype="False" ear="${dist}/${app.earname}" warName="${servlet.warname}" packageName="MyPackage.webservices.client"
    keepgenerated="False" useServerTypes="True" clientJar="${dist}/MyAppClient.jar">
    <classpath refid="build.classpath.builddir"/>
    </clientgen>
    ============
    I am testing by putting a Thread.sleep(75000) in the method which is called in the internal EJB. But the method runs to completion and returns the reply object after 90 seconds or so (it normally takes about 12 seconds), but does not timeout.
    I've been told that because it is a web services client, the remote-client-timeout will be ineffective. I've also been told that because the EJBs run in the same JVM, the transaction-timeout will be ineffective. Is this so?
    Thanks,
    Walter

    Can you change the clientgen task to weblogic.wsee.tools.anttasks.ClientGenTask this is for jax-rpc 1.1.
    <taskdef name="clientgen"
    classname="weblogic.wsee.tools.anttasks.ClientGenTask" />
    ((Stub)port)._setProperty(weblogic.wsee.transport.connection.timeout,2);
    ((Stub)port)._setProperty(weblogic.wsee.transport.read.timeoutt,2);
    Hope that helps.

  • Web service Client developing!

    Hi,
    I've developed a web service client with JDeveloper 9i.
    I did it using the WSDL file location and the stub/skeleton generator wizard.
    Once made it, I wrote a client class with a method as follows:
    // code beggining
    public static Integer calculator (Integer a,Integer b) throws Exception {
    Integer result= null;
    if (a==null || b==null){
    a= new Integer(0);
    b= new Integer(0);
    try {
    CalculadoraWSStub calc= new CalculadoraWSStub();
    result= calc.calculator(a,b);
    catch (Exception ex)
    throw new Exception ("\nMy Exception: " + ex.toString());
    return result;
    // code ending
    Ok, now the main point of the problem.
    If we execute this code under JDeveloper, everything goes well, BUT if we execute it as a function under Oracle database appears a Exception telling us something about a internal error because HttpClient/RetryModule constructor is private!
    Can you help us?
    -- we can't solve this problem because it only appears when we are trying to connect to a web service.
    Thanks in advance, people!

    Yes, this is correct. ANM 4.1 does not allow more that 5 logins per account and unfortunately this is not configurable. I suggest the you mention this to your local Cisco Account Team.

  • How to implement web service client timeout

    I'm trying to implement a web service client using JAX-RPC specification and the client is generated by clientgen utility. We are using weblogic8.1(sp5).
    How do I control the connection timeout and data transmission timeout? I have tried:
    BindingInfo.setTimeout() method and stub._setProperty("weblogic.webservice.rpc.timeoutsecs", "1" /* secs */);
    and they don't seem to be working...
    I have searched the web service documentation and didn't found any mentioning on this. Can someone shred some light on this?
    Thanks.
    Ren
    null

    Hi,
    I had a problem too for setting the timeout of a webservice client. but i didn't find any thing on this.
    But there is a work around for this see if it suits you but for this you have to use Apache AXIS webservice api to generate the client in that Api you have the Stub.timeOut() function to over come this problem
    Cheers !!
    Vivek:-)

  • A question regarding Web Service Client

    Hi,
    I read the tutorial "Creating Web Service Clients with JAX-RPC" and I coundn't understand something.
    The code conatins, for example: (Stub) (new MyHelloService_Impl().getHelloIFPort()); Since it's a stand alone client, how it suppose to recognize MyHelloService_Impl()? Should it be added to the project libraries? What did I miss here?
    Thanks, Lior

    The wscompile tool generates class files required by the static stub client. The HelloClient program creates a stub as follows:
    stub = (HelloIF_Stub)
    (new HelloWorldService_Impl().getHelloIFPort());
    The wscompile tool generates the HelloIF_Stub and HelloWorldService_Impl classes and places them in the build/classes/server/ subdirectory. To construct the HelloIF_Stub name, wscompile appends _Stub to the portType name defined in the WSDL file:
    <portType name="HelloIF">
    To create the HelloWorldService_Impl name, wscompile appends _Impl to the service name, which the WSDL file specifies as follows:
    <service name="HelloWorldService">

Maybe you are looking for

  • "Xandros" (linux flavor), shows "TNS 12203" connect with oracle server(win

    I am using oracle developer 6i and from 2000 on operating system "Xandros" (linux flavor),and working properly after instalation. Problem when i am connecting to this Machine with oracle server(windos) it shows "TNS 12203" i want to use xendros at cl

  • How to create .a files for iPhone applications

    Hi guys, I am working on iphone library in Objective-C and I need to create .a files in this library. Please let me know if anybody knows how can I create the .a files from .m files in Objective-C. Thanks in advance, Ishita

  • SYNC of Calendar with Windows Live Mail

    Hi we urgently need a sync for free calendars i.e windows live mail or thunderbird/lightning . Does anybody know how to get?

  • Updated and now can't text, etc

    I apologize if this information is already somewhere on this forum but I've had a look around and was unable to locate the information that I was looking for. If you can point me in the right direction, please do so. So, here is my problem.  I finall

  • Version Management with Requisition

    Hi, We have activated version mangement for requisitions. Some of our requisitions are not routed through approval process. Version management is working with requisitions not related to release strategy. But version management is not triggering requ