Web Service Client Wizard

I seem to have some problems generating the stub using the wizard in JDeveloper. I point to the wsdl file, the wizard shows me the classes that will be generated..the generation starts..but stops..without giving any further information as to why it stopped..Anybody has any clue at to what is happening?

11.1.1.5.0
The strange thing is that if I create a general project and try to create a web service proxy, I have that option but in this particular project that option doesn't appear. I think there's something bounded to this particular project that disables that feature. I just can't figure out wht it is!!!
thanks,
Manuel Leiria

Similar Messages

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

  • 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

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

  • RPC style web service client

    hi,
    i am new to web service technology. i want to create dynamic web service client for a "rpc" style web service in Netbeans.
    please, can anybody guide me for this?
    thanks in advance.

    Hi,
    To avoid creating new topic I will put my question here.
    I try to create new web service (rpc-style) client in netbeans. I have rpc plugin installed. In ejb module node I right click > new > web service client >
    I fill all filds, chose rpc-style and > after clicking finish - error occur:java.lang.LinkageError: com/sun/xml/rpc/processor/generator/Names
         at org.netbeans.modules.websvc.registry.util.Util.getParameterType(Util.java:856)
         at org.netbeans.modules.websvc.registry.jaxrpc.WrapperClientWriter.printOperations(WrapperClientWriter.java:275)
         at org.netbeans.modules.websvc.registry.jaxrpc.WrapperClientWriter.writeClass(WrapperClientWriter.java:219)
         at org.netbeans.modules.websvc.registry.jaxrpc.Wsdl2Java.createWrapperClients(Wsdl2Java.java:305)
         at org.netbeans.modules.websvc.registry.jaxrpc.Wsdl2Java.execute(Wsdl2Java.java:229)
         at org.netbeans.modules.websvc.registry.util.Util.createWSJar(Util.java:493)
         at org.netbeans.modules.websvc.registry.RegistryViewImpl.registerService(RegistryViewImpl.java:221)
         at org.netbeans.modules.websvc.registry.RegistryViewImpl.registerService(RegistryViewImpl.java:159)
         at org.netbeans.modules.websvc.registry.netbeans.RegisterViewImplNetBeansSide.registerService(RegisterViewImplNetBeansSide.java:91)
         at org.netbeans.modules.websvc.jaxrpc.client.wizard.ClientBuilder.generate(ClientBuilder.java:330)
         at org.netbeans.modules.websvc.jaxrpc.client.wizard.JaxRpcClientCreator$2.run(JaxRpcClientCreator.java:319)
         at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:572)
    [catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:997)
    I use netbeans 6.5. In my project I choose java ee 5 as in 1.4 there is no web service client option
    Any ideas?
    I found some rpc tutorils for netbeans 4.0 but I wonder why it couldn't be done in netbean 6.5
    Regards,
    Lech

  • Problem creating J2ME web service client

    Hi,
    I am using netbeans (5 and 5.5 beta 2). I have created a web service which works fine. I also created a regular web service client as a standalone application which also works fine and connects to my web service with no problem.
    BUT, when I want to create a J2ME web service client (under a J2ME application) I have to locate my WSDL file. but the wizard shows me the error "WSDL file does not contain port information".
    By looking at the WSDL file I can see that port is created - or maybe I'm wrong.
    piece from WSDL file:
    <service name="myServiceName">
    <port name="myServiceSPort" binding="tns:TranslatorWSPortBinding">
    <soap:address location="myURLLocation"/>
    </port>
    </service>
    Please note that I have replaced the actual values in above piece
    I tried to use wsgen manually but it didn't help.
    Can anyone help me in generating the correct WSDL format as J2ME web service client expects?
    Thanks a lot,
    S.

    well stubs are generated separately using WTK 2.5 stub generator but the problem is with the WSDL at this point.
    S.

  • Creating web service client with WSDL in NetBeans

    NetBeans: 5.5
    Java: 1.6
    WSDL: http://jira.atlassian.com/rpc/soap/jirasoapservice-v2?wsdl
    Using netbeans, I can't seem to successfully generate the stubs for a client based on the WSDL file above.
    SoapUI ( www.soapui.org ) has no problems receiving and creating the client stubs using the same WSDL file.
    The error I'm getting in the dialog is "Illegal attempt to exit early".
    Further details from the output window reads as follows:
    -=-
    warning: src-resolve: Cannot resolve the name 'impl:ArrayOf_tns2_RemoteEntity' to a(n) 'type definition' component.
    line 0 of file:/C:/Documents%20and%20Settings/Alexander%20Trauzzi/JavaApplication2/xml-resources/web-service-references/jirasoapservice-v2/wsdl/jira.atlassian.com/rpc/soap/jirasoapservice-v2.wsdl#types?schema2
    warning: src-resolve: Cannot resolve the name 'soapenc:Array' to a(n) 'type definition' component.
    line 0 of file:/C:/Documents%20and%20Settings/Alexander%20Trauzzi/JavaApplication2/xml-resources/web-service-references/jirasoapservice-v2/wsdl/jira.atlassian.com/rpc/soap/jirasoapservice-v2.wsdl#types?schema3
    error: undefined simple or complex type 'soapenc:Array'
    line 0 of file:/C:/Documents%20and%20Settings/Alexander%20Trauzzi/JavaApplication2/xml-resources/web-service-references/jirasoapservice-v2/wsdl/jira.atlassian.com/rpc/soap/jirasoapservice-v2.wsdl#types?schema3
    -=-
    And on and on...
    What is going on? Why can't I generate my web service client? Any help is greatly appreciated!

    There is a bug in the processLauncher for deploytool. The workaround is to edit the processLauncher.xml located under <AS_INSTALL>/lib/processLauncher.xml and add
    add xalan.jar and mail.jar to the classpath includes of the s1as-deploytool process:
    includes="appserv-assemblytool.jar,activation.jar,appserv-admin.jar,appserv-cmp.jar,appserv-rt.jar,j2ee.jar,jaxrpc-impl.jar,appserv-ext.jar,deployhelp.jar,admin-cli.jar,dom.jar,xercesImpl.jar, xalan.jar, mail.jar"
    The web service wizard should now work.

  • Creating web service client with deploytool

    J2EE 1.4 SDK 2005Q1 Release Candidate
    Windows XP Professional SP1
    I cannot create a web service client from a WSDL file any longer.
    deploytool
    - new
    - web service
    - web service client
    - next (provide the wsdl file): package name is not filled in automatically
    - next: there is no way to continue - next and finish button are both grey
    There are no problems with J2EE 1.4 SDK 2004Q4 Beta

    There is a bug in the processLauncher for deploytool. The workaround is to edit the processLauncher.xml located under <AS_INSTALL>/lib/processLauncher.xml and add
    add xalan.jar and mail.jar to the classpath includes of the s1as-deploytool process:
    includes="appserv-assemblytool.jar,activation.jar,appserv-admin.jar,appserv-cmp.jar,appserv-rt.jar,j2ee.jar,jaxrpc-impl.jar,appserv-ext.jar,deployhelp.jar,admin-cli.jar,dom.jar,xercesImpl.jar, xalan.jar, mail.jar"
    The web service wizard should now work.

  • Creating Web Service Client to cater for autentication

    Hello everyone,
    I wonder if you can help me...
    I'm trying to connect a web service client; I have done so in the past with no issues.
    I use the wizard of Eclipse to create the clients, loading in the WSDL file and letting it generate all the classes for me.
    However, this time the WSDL I'm trying to access requires a username and password before you can actually view it in a web browser (it isn't a requirement of calling the methods of the web service, it's literally to access the web service).
    I've loaded the WSDL in okay to create the web service client, but when I try to call any of its methods, I get 401: Unauthorised error message.
    The closest I came to solving it was using this:
              Authenticator.setDefault(new MyAuthenticator(username, password));
    which does allow me to view the actual WSDL and write out the lines of the web page (the HTML), which previously wouldn't work. When I then try to call one of the web service's methods, I get the 401: Unauthorised message again.
    Can anyone give me any pointers? I'm really stuck, and just don't know where to turn. I've looked everywhere online, and just can't find any help.
    Thanks very much in advance.
    Robin

    the web service is the specification for whatever functionality you wish to provide
    there are a few artifacts you can auto-generate using the WSDL, but you still need to create a client and server application
    the web service is simply exposing the application remotely and the WSDL is the contract
    http://java.sun.com/webservices/docs/1.6/tutorial/doc/index.html

  • IndexOutOfBoundsException When Creating Web Service Client

    Hello,
    I am getting the following error when I try to create a Web Service Client in JDeveloper 10.1.3. Any ideas why this occurs?
    Thanks,
    Kevin Scott
    java.lang.IndexOutOfBoundsException: Index: 0, Size: 0     
         at java.util.ArrayList.RangeCheck(ArrayList.java:507)     
         at java.util.ArrayList.get(ArrayList.java:324)     
         at oracle.jdeveloper.webservices.model.proxy.ProxyGenerator.updateNavigatorImpl(ProxyGenerator.java:574)
         at oracle.jdeveloper.webservices.model.proxy.ProxyGenerator.access$1000071(ProxyGenerator.java:71)
         at oracle.jdeveloper.webservices.model.proxy.ProxyGenerator$2.run(ProxyGenerator.java:525)
         at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:171)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:141)
         at java.awt.Dialog$1.run(Dialog.java:540)
         at java.awt.Dialog.show(Dialog.java:561)
         at java.awt.Component.show(Component.java:1133)
         at java.awt.Component.setVisible(Component.java:1088)
         at oracle.bali.ewt.dialog.JEWTDialog.runDialog(Unknown Source)
         at oracle.ide.dialogs.ProgressBar.start(ProgressBar.java:275)
         at oracle.jdeveloper.webservices.model.GeneratorUI.start(GeneratorUI.java:189)
         at oracle.jdeveloper.webservices.model.proxy.ProxyGenerator.generate(ProxyGenerator.java:195)
         at oracle.jdeveloper.webservices.model.proxy.WebServiceProxy.saveEdit(WebServiceProxy.java:1066)
         at oracle.jdevimpl.webservices.wizard.jaxrpc.ProxyWizard.runWizard(ProxyWizard.java:263)
         at oracle.jdevimpl.webservices.wizard.jaxrpc.ProxyGalleryWizard.invoke(ProxyGalleryWizard.java:84)
         at oracle.ide.WizardManager.invokeWizard(WizardManager.java:488)
         at oracle.ide.WizardManager$1.run(WizardManager.java:542)
         at oracle.ide.util.IdeUtil.invokeAfterRepaint(IdeUtil.java:1143)
         at oracle.ide.WizardManager$2.run(WizardManager.java:550)
         at oracle.ide.util.IdeUtil$4.run(IdeUtil.java:1123)
         at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)

    the web service is the specification for whatever functionality you wish to provide
    there are a few artifacts you can auto-generate using the WSDL, but you still need to create a client and server application
    the web service is simply exposing the application remotely and the WSDL is the contract
    http://java.sun.com/webservices/docs/1.6/tutorial/doc/index.html

  • HTTP Analyzer help for web service client in 11g

    I am using jDev 11.1.1.3.0 to build a web service client (proxy) to a potential vendor's web service. I've used the Http Analyzer before but I'm having trouble configuring it for a WS proxy. I just want to see the SOAP stream between my client and the web service. I used the Web Service Proxy wizard to create the Java code, but the web service provider has kept some of the contract in the WSDL private so that I had to manually generate the meat and potatoes of the Java code. I need to be able to see the SOAP my Java code is sending.
    I have tried to configure the Http Analyzer to listen on it's own localhost and port with a forward rule to forward the request to the real WS, but I cannot figure out how to get the client to send it's requests to localhost instead of the actual WS.
    Actually, I did figure it out, but then the request fails as it apparently tries to connect to the real WSDL before actually sending the request and cannot find a WSDL at the localhost URL. Here's the error:
    Exception in thread "main" javax.xml.ws.WebServiceException: {http://localhost:8099}CatalogRequest is not a valid service. Valid services are: {http://[actual URL here]}CatalogRequest
         at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:249)
    I have also tried to configure the Http Analyzer to somehow 'sniff' the actual URL by listening on the actual URL and port, but either I cannot get the Analyzer to see the request or it fails because the Analyzer is using the same port the request is trying to use.
    Can someone explain how to configure the Http Analyzer to see the SOAP stream for a Web Client Proxy?

    Hi, I'm just using the default setup for HTTP Analyzer and having no problem using it.
    Just make sure to run the HTTP Analyzer first before running or starting your app server (Integrated weblogic Server).

  • Change the end point in a web service client???

    Hello,
    With the Web Service Proxy Wizard of JDeveloper 10g R3, I created a web service proxy that connects to a (web service) end point like this: http://carina.bicevida.cl/OidServices/OidBasicWebServiceSoapHttpPort
    My three related questions are:
    1.- How can I change the end point registered in the (client) web service proxy ?
    2.- How can I do this without need to rebuild the client application?
    3.- How can I do this once my client application have been deployed in the application server?
    Please help.

    Hi,
    these are your options
    - Edit the endpoint meta data stored in the .proxy xml file (e.g. \src\project\myservice.proxy)
    - Use WS proxy wrapper and call setEndpoint on the proxy
    - Recreate the proxy in JDeveloper based on the new endpoint. This may require merging any business logic if it was inserted directly in the proxy (as opposed to a wrappering class)
    where I think option 1 and 2 is what you would look for. I don't know how exactly JDeveloper 11 is different, but I got the info from development that there will be simplifications.
    Frank

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

  • How to prevent downloading wsdl in weblogic web service client

    Hi,
    I get a problem regarding weblogic web service client. My working environment:
    weblogic server 8.1
    Windows XP SP2
    JDK 1.4
    I use the weblogic tool to generate the client jar file from the wsdl file.
         <target name="generate-client">
              <clientgen wsdl="ACCESS.wsdl"
                   packageName="xxxxxx.client"
                   clientJar="${client}/${AccessClient_jar_file}"
                   keepGenerated="true"
                   saveWSDL="true"
              />
              <javac srcdir="${source}"
              destdir="${client}"
              includes="**/AccessClient.java">
              <classpath>
              <pathelement path="${client}/${AccessClient_jar_file}"/>
              </classpath>
              </javac>
         </target>
    After that, I create a client java file to invoke the service deploy in the server.
    public static void main(String[] argv)
    throws Exception
         int transactionId = 100;
         int id = 1000;
    // Setup the global JAXM message factory
    System.setProperty("javax.xml.soap.MessageFactory", "weblogic.webservice.core.soap.MessageFactoryImpl");
    // Setup the global JAX-RPC service factory
    System.setProperty( "javax.xml.rpc.ServiceFactory", "weblogic.webservice.core.rpc.ServiceFactoryImpl");
    AccessServicePorts ws = new AccessServicePorts_Impl(argv[0]);
    AccessService port = ws.getAccessService();
    // Resource - create
    Resource resource = new Resource();
    resource.setRES_CD("Create ResCo");
    resource.setCODE_CODE("code_cod");
    resource.setRES_TYPE("Resource typ");
    resource.setCOMMON_FIELD(common);
    AccessDefaultResult resultItems = port.createResource(resource);
    System.out.println("createResource : " + resultItems);
    I find that this web service client always issue 2 http requests to invoke an web service method deployed in server.
    1st http reqeust:
    GET /AccessEpol/EpolServiceSoap?WSDL HTTP/1.1
    User-Agent: Java/1.4.2_08
    Host: 127.0.0.1:8001
    Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
    Connection: keep-alive
    the return result is the wsdl downloaded from the server.
    2nd http request is the real web service request.
    The question is how could I eliminate the 1st http request because it's really unnecessary. I use other web service client like Axis 1.x, Axis client never has the http request to download the wsdl from the server.
    I read through weblogic web service document. It do mentions that put saveWSDL="true" in the clientgen ant task. the default value for saveWSDL is true already. I did try saveWSDL="false" also. None of them can eliminate the 1st http request.
    appreciate for any answer my question?

    Hi David,
    thanks for the reply.
    More or less I agree some points you mentioned above.
    I did use Axis 1.x to test the inter-operability. The web service was developed in Weblogic 8.1 and is a part of an existing web application. It will be merged to existing application deployed in weblogic 8.1.
    I also program the web service client to test the web service.
    The implementation of the server and client will be handed over the project team and training for supporting or continuous development have to be conducted by me. So I don't like to use two types of technologies which will make thing complex.
    I found this issue when I tried to protected the web service endpoint, eg http://localhost:7001/epol/service, using the web application Basic mechanism. The wsdl URL http://localhost:7001/epol/service?WSDL is also protected in this case. Unfortunately the username/password pair is not sent to the server when the weblogic client download the WSDL from the server. In this case, the client failed and throw exception.

  • Oracle Database Web Service Client using UTL_DBWS :: ORA-29532 Error

    Hi,
    I have the Oracle Database 10.2.0.1.0 :-
    SQL> select * from v$version;
    BANNER
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
    PL/SQL Release 10.2.0.1.0 - Production
    CORE    10.2.0.1.0      Production
    TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
    NLSRTL Version 10.2.0.1.0 - ProductionI have written a simple Web Services Client using the classes gfrom the UTL_DBWS package. I loaded the JAR file dbwsclient.jar in the SYS Schema and I am trying to use it in the USF Schema.
    However, I have hit this error & I ma unable to proceed :-
    SQL>  select get_stock_price from dual;
    select get_stock_price from dual
    ERROR at line 1:
    ORA-29532: Java call terminated by uncaught Java exception:
    java.lang.IllegalAccessException: javax.xml.rpc.ServiceException:
    java.security.AccessControlException: the Permission
    (java.lang.RuntimePermission getClassLoader) has not been granted to USF. The
    PL/SQL to grant this is dbms_java.grant_permission( 'USF',
    'SYS:java.lang.RuntimePermission', 'getClassLoader', '' )
    ORA-06512: at "USF.UTL_DBWS", line 193
    ORA-06512: at "USF.UTL_DBWS", line 190
    ORA-06512: at "USF.GET_STOCK_PRICE", line 17Can you please help me with this ?
    Regards,
    Sandeep

    Hi,
    The error message said
    the Permission(java.lang.RuntimePermission getClassLoader) has not been granted to USF.
    I'd follow the suggestion
    The PL/SQL to grant this is dbms_java.grant_permission( 'USF','SYS:java.lang.RuntimePermission', 'getClassLoader', '' )
    In case you have not done so, consult the Callout Users Guide @
    http://www.oracle.com/technology/sample_code/tech/java/jsp/callout_users_guide.htm
    Kuassi http://db360.blogspot.com

Maybe you are looking for

  • My itunes account  had me change my Apple ID to an email address.

    Recently Itunes flagged me for a password reset. When I went to reset the password it told me that I could no longer just use a username that I had to use an email.  So I went through the process, but now I don't see any of my previouse purchased Ite

  • Problem in Posting Goods Receipt , Pl Help .

    Hello All, Kindlt help me as i had created  Purchase Order in the Development System , but when trying to Post the Goods Receipt, i am  getting a System Message as " Purchase Order does not Contain Selectable Items ". Then i had Checked the P.O and f

  • How to add child node in Tree table programmetically

    Jdev Version 11.1.1.4.0. I have created tree table programmetically in bean. I have to add child node to tree table component on button click event on page. Please let me know how to do this in bean. Regards, Kiran

  • How to debug script to know output function ?

    Hi  , How to know the function to output  of this "PPIO_ENTRY"  program? (I want get the structure to show ALV ) Please advise, your help is greatly appreciated. Thanks, Karen Edited by: abaper1712 on Jul 14, 2010 8:54 AM

  • CIN - J1ID TAX RATE MAINTAINED VALIDITY DATE (INDIAN SCENARIO)

    IN INDIA TAX RATES CHANGE DURING EVERY YEARS BUDGET. EXCISE AND CUSTOMS DUTY CHANGE FROM MARCH WHEREAS SALES TAX CHANGES FROM APRIL. THIS TIME DUE TO RECESSION AND ELECTION THE EXCISE DUTY STRUCTURE WAS CHANGED THRICE FROM DEC 2008 TILL DATE. FROM 14