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
Similar Messages
-
How to deploy web service/client on websphere
Hi,
I have developed a web service client on Jdeveloper 10.1.3.1.0 and I deployed it on the embeded OC4J and OAS and it worked fine. BUT when I packaged it as EAR file and deployed it on websphere 6.0 {the production enviroment at the client side} It gave me NoClassForService00.
And in websphere application server it didn't recognize it as Web service client.
Any one faced this problem b4. PLZ advice.
ThnxHi Amol,
Thank you very much for replying my question. The contents in my application.xml are:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN" "http://java.sun.com/dtd/application_1_3.dtd">
<application>
<display-name>testwsapp</display-name>
<description>J2EE Application testwsapp</description>
<module>
<web>
<web-uri>testws_War.war</web-uri>
<context-root>testws</context-root>
</web>
<alt-dd>testws_War.xml</alt-dd>
</module>
</application>
The contents in jaxrpc-ri-runtime.xml are:
<?xml version="1.0" encoding="UTF-8"?>
<endpoints xmlns='http://java.sun.com/xml/ns/jax-rpc/ri/runtime' version='1.0'>
<endpoint
name='testws'
interface='contactws.testwsGenServer.testwsRPC'
implementation='contactws.testwsGenServer.testwsRPCBean'
tie='contactws.testwsGenServer.testwsRPC_Tie'
model='null'
wsdl='/WEB-INF/testws.wsdl'
service='{urn:testws/wsdl}Testws'
port='{urn:testws/wsdl}testwsRPCPort'
urlpattern='/testws'
</endpoint></endpoints>
I tried to access and check the web service using:
http://servername:port/testws/testws
The first testws is contextroot named and the second testws is url pattern, which was exactly like what you mentioned but I got "404 Not Found" error.
By the way, using the same ear to deploy to Windows Sun ONE App. Server 7 env. and then using the same url, I can access the web service. I am wondering if there is any special for deploying Web Service on Unix Sun ONE app. Server 7 env. or I missed something?
I hope I can hear from you soon.
Thank you again,
Jackie -
Web Service client deployment in JBoss 4.0.4 GA
I need to write a web service client which would be deployed in a WAR file JBoss 4.0.4 GA container.
The web service is written using JSR 181 and deployed in jbossws-1.0.2.GA .
I would like to know which would be the best web service stack to use to write the client in the above mentioned scenario?
TIA...Enable TCP/IP protocol. Select Microsoft SQL Server 2005>Configuration Tools>SQL Server Configuration Manager. In the SQL Server Configuration Manager select the node SQL Server 2005 Network Configuration>Protocols for SQLEXPRESS. Right-click on the TCP/IP node and select Enable. Restart the SQL Server (SQLEXPRESS) service. Right-click on the SQL Server (SQLEXPRESS) service in Services and select Restart.
-
WSDL Web Services Client and EAR deploy problem
Hi!
I have allready posted this on "Web AS General", with no result.
So I hope this forum is a better choise.
Environment:
SAP EP / SAP NW04 / SPS14
NW DevStudio
I just deployed an ear file (first time ...) with SDM.
The ear file represents an auto generated web services client on basis of a WSDL file.
(done from web services perspective in NWDS choosing "New Deployable Proxy Project")
When running a test I get the following error:
"Could not find portal application Unknown provider of external application: J2EE::sap.com/NWTPINWSClient"
.. where NWTPINWSClient is the name of the EAR - file
The test code contains this:
The portalapp.xml has the following tag:
<application-config>
<property name="SharingReference" value="J2EE::sap.com/NWTPINWSClient">
</property>
</application-config>
I'm new to this, so please feel free to consider newbie misstakes.
BRGRDS
Peter MCan you/anybody post solution. I have the same problem.
Thanks
Srinivas -
Application Server 8.2 + Axis Web Service Client +Win Server 2003 Issue
Hi everyone,
I'm facing a weird problem the last couples of days and I'm getting bored of banging my head against the logs/screen, so please if you could help I'd really appreciate it.
I'm working on a Sun Application Server 8.2 project that includes an axis web service client. I am using Netbeans 5 to do the writing plus I am on a Win XP platform.
The developers of the web service I intend to absorb were kind enough to package the client into a jar so all I have to do is to import the client and the axis related jar files (axis, axis-ant etc.) in my project and my classpath.
Everything is working perfect on my pc but when I deploy the project on my actual server the web service client is running forever, leaving my end users with a blank browser window that is also loading forever.
The server OS is Win Server 2003 and is directly connected to a gateway - no proxies. Also my development pc and my server are running the same jre and have the exact server police settings; but Sun's Application Server is running on port 8080 on my pc whereas on my server it's running on port 80.
Here's my server's log:
[#|2008-04-14T21:50:01.795+0300|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=14;|StandardWrapperValve[obos]: Servlet.service() for servlet obos threw exception
AxisFault
faultCode: {http://xml.apache.org/axis/}HTTP
faultSubcode:
faultString: (0)null
faultActor:
faultNode:
faultDetail:
{}:return code: 0
{http://xml.apache.org/axis/}HttpErrorCode:0
(0)null
at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:744)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at uk.ac.ebi.ook.web.services.OntologyQuerySoapBindingStub.getOntologyNames(OntologyQuerySoapBindingStub.java:509)
at org.dude.ols.client.obos.processRequest(obos.java:30)
at org.dude.ols.client.obos.doGet(obos.java:64)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:747)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
at sun.reflect.GeneratedMethodAccessor99.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:257)
at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:161)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:225)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:132)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:933)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:189)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.doProcess(ProcessorTask.java:604)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:475)
at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:371)
at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:264)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:281)
at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:83)
|#]
Any ideas?Hi Paz,
Thanks for taking the time :)
To answer your questions:
1. Has this WebServices ever worked or is this the first time?
The web service is working perfectly fine on my working station, the problem appears only when I deploy it on my actual server, which means that the web service is working.
2. What Apache Axis Version are you using?
1.4
3. What JRE version are you using?
Both my development pc and my server run jre 1.5.0_14
4. In the actual server environment, can you confirm all information are exactly same as DEV environment...
Oh yes! Absolutely.
My recent assumption is that some windows service might be needed to run the web service client and obviously I have no clue which one it might be.
Just to make sure; is the security policy of my Application Server set correctly?
permission java.lang.RuntimePermission "getClassLoader";
permission java.lang.RuntimePermission "createClassLoader";
permission java.lang.RuntimePermission "loadLibrary.*";
permission java.lang.RuntimePermission "queuePrintJob";
permission java.net.SocketPermission "*", "connect,accept,resolve";
permission java.io.FilePermission "<<ALL FILES>>", "read,write,delete";
// work-around for pointbase bug 4864405
permission java.io.FilePermission "${com.sun.aas.instanceRoot}${/}lib${/}databases${/}-", "delete";
permission java.io.FilePermission "${java.io.tmpdir}${/}-", "delete";
permission java.util.PropertyPermission "*", "read,write";
permission java.lang.RuntimePermission "modifyThreadGroup";
Again thanks for taking the time :) -
Standalone Web Service clients in NetBeans with WSIT security
I'm having a problem create a secure app with NetBeans, any help would be appreciated, here's what I did:
Following the WSIT tutorial (http://java.sun.com/webservices/reference/tutorials/wsit/doc/index.html) I was able to create a Web Service with (for example) Username Authentication with Symmetric Key. I select the keystore as being the either the default development settings (I installed V3 certificates previously) or what I imagine are the same as them: keystore from domain1, alias xws-server and a username and password that I've created in the glassfish admin console. All good so far.
I then create a new web app servlet client, configuring the Web Service client with the corresponding cacerts keystore, alias xws-security-server from domain1 and the correct username and password. Deploy that and bingo, it works.
Try that again with a standalone Java client configuring the client reference in exactly the same way and using:
try { // Call Web Service Operation
uk.ac.ox.sddag.glassfish.server.SecureWSService service = new uk.ac.ox.sddag.glassfish.server.SecureWSService();
uk.ac.ox.sddag.glassfish.server.SecureWS port = service.getSecureWSPort();
int x = 1200;
int y = 36;
int result = port.add(x, y);
System.out.println("Result = "+result);
} catch (Exception ex) {
System.out.println("Exception:");
ex.printStackTrace();
}but this time, it doesn't work:
Exception:
javax.xml.ws.soap.SOAPFaultException: ERROR: No security header found in the message
at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:188)
at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:130)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118)
at $Proxy29.add(Unknown Source)
at securestandaloneclient.Main.main(Main.java:26)
Caused by: javax.xml.ws.soap.SOAPFaultException: ERROR: No security header found in the message
at com.sun.xml.ws.security.opt.impl.util.SOAPUtil.getSOAPFaultException(SOAPUtil.java:171)
at com.sun.xml.wss.provider.wsit.WSITServerAuthContext.validateRequest(WSITServerAuthContext.java:277)
at com.sun.xml.wss.provider.wsit.WSITServerAuthContext.validateRequest(WSITServerAuthContext.java:179)
at com.sun.enterprise.webservice.CommonServerSecurityPipe.processRequest(CommonServerSecurityPipe.java:168)
at com.sun.enterprise.webservice.CommonServerSecurityPipe.process(CommonServerSecurityPipe.java:129)
at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135)
at com.sun.enterprise.webservice.JAXWSServlet.doPost(JAXWSServlet.java:176)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:290)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:272)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:263)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:214)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)I'm assuming that it's something to do with the WSDL being used to create the request, here's what the source view for the web service reference says:
<?xml version="1.0" encoding="UTF-8"?><!-- Published by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.3.1-hudson-417-SNAPSHOT. --><!-- Generated by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.3.1-hudson-417-SNAPSHOT. --><definitions xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://server.glassfish.sddag.ox.ac.uk/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://server.glassfish.sddag.ox.ac.uk/" name="SecureWSService">
<ns1:Policy xmlns:ns1="http://schemas.xmlsoap.org/ws/2004/09/policy" wsu:Id="SecureWSPortBindingPolicy">
<ns1:ExactlyOne>
<ns1:All>
<ns4:SignedSupportingTokens xmlns:ns4="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<ns1:Policy>
<ns1:ExactlyOne>
<ns1:All>
<ns4:UsernameToken ns4:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient">
<ns1:Policy>
<ns1:ExactlyOne>
<ns1:All>
<ns4:WssUsernameToken10></ns4:WssUsernameToken10>
</ns1:All>
</ns1:ExactlyOne>
</ns1:Policy>
</ns4:UsernameToken>
</ns1:All>
</ns1:ExactlyOne>
</ns1:Policy>
</ns4:SignedSupportingTokens>
<ns5:SymmetricBinding xmlns:ns5="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<ns1:Policy>
<ns1:ExactlyOne>
<ns1:All>
<ns5:AlgorithmSuite>
<ns1:Policy>
<ns1:ExactlyOne>
<ns1:All>
<ns5:Basic128></ns5:Basic128>
</ns1:All>
</ns1:ExactlyOne>
</ns1:Policy>
</ns5:AlgorithmSuite>
<ns5:IncludeTimestamp></ns5:IncludeTimestamp>
<ns5:Layout>
<ns1:Policy>
<ns1:ExactlyOne>
<ns1:All>
<ns5:Strict></ns5:Strict>
</ns1:All>
</ns1:ExactlyOne>
</ns1:Policy>
</ns5:Layout>
<ns5:OnlySignEntireHeadersAndBody></ns5:OnlySignEntireHeadersAndBody>
<ns5:ProtectionToken>
<ns1:Policy>
<ns1:ExactlyOne>
<ns1:All>
<ns5:X509Token ns5:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/Never">
<ns1:Policy>
<ns1:ExactlyOne>
<ns1:All>
<ns5:RequireIssuerSerialReference></ns5:RequireIssuerSerialReference>
<ns5:WssX509V3Token10></ns5:WssX509V3Token10>
</ns1:All>
</ns1:ExactlyOne>
</ns1:Policy>
</ns5:X509Token>
</ns1:All>
</ns1:ExactlyOne>
</ns1:Policy>
</ns5:ProtectionToken>
</ns1:All>
</ns1:ExactlyOne>
</ns1:Policy>
</ns5:SymmetricBinding>
<ns6:Wss11 xmlns:ns6="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<ns1:Policy>
<ns1:ExactlyOne>
<ns1:All>
<ns6:MustSupportRefEncryptedKey></ns6:MustSupportRefEncryptedKey>
<ns6:MustSupportRefIssuerSerial></ns6:MustSupportRefIssuerSerial>
<ns6:MustSupportRefThumbprint></ns6:MustSupportRefThumbprint>
</ns1:All>
</ns1:ExactlyOne>
</ns1:Policy>
</ns6:Wss11>
<ns7:UsingAddressing xmlns:ns7="http://www.w3.org/2006/05/addressing/wsdl" ns1:Optional="true"></ns7:UsingAddressing>
</ns1:All>
</ns1:ExactlyOne>
</ns1:Policy>
<ns8:Policy xmlns:ns8="http://schemas.xmlsoap.org/ws/2004/09/policy" wsu:Id="SecureWSPortBinding_add_Input_Policy">
<ns8:ExactlyOne>
<ns8:All>
<ns9:EncryptedParts xmlns:ns9="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<ns9:Body></ns9:Body>
</ns9:EncryptedParts>
<ns10:SignedParts xmlns:ns10="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<ns10:Body></ns10:Body>
<ns10:Header Name="ReplyTo" Namespace="http://www.w3.org/2005/08/addressing"></ns10:Header>
<ns10:Header Namespace="http://www.w3.org/2005/08/addressing" Name="To"></ns10:Header>
<ns10:Header Name="From" Namespace="http://www.w3.org/2005/08/addressing"></ns10:Header>
<ns10:Header Name="MessageID" Namespace="http://www.w3.org/2005/08/addressing"></ns10:Header>
<ns10:Header Name="FaultTo" Namespace="http://www.w3.org/2005/08/addressing"></ns10:Header>
<ns10:Header Name="Action" Namespace="http://www.w3.org/2005/08/addressing"></ns10:Header>
<ns10:Header Name="RelatesTo" Namespace="http://www.w3.org/2005/08/addressing"></ns10:Header>
<ns10:Header Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" Name="AckRequested"></ns10:Header>
<ns10:Header Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" Name="CreateSequence"></ns10:Header>
<ns10:Header Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" Name="Sequence"></ns10:Header>
<ns10:Header Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" Name="SequenceAcknowledgement"></ns10:Header>
</ns10:SignedParts>
</ns8:All>
</ns8:ExactlyOne>
</ns8:Policy>
<ns11:Policy xmlns:ns11="http://schemas.xmlsoap.org/ws/2004/09/policy" wsu:Id="SecureWSPortBinding_add_Output_Policy">
<ns11:ExactlyOne>
<ns11:All>
<ns12:EncryptedParts xmlns:ns12="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<ns12:Body></ns12:Body>
</ns12:EncryptedParts>
<ns13:SignedParts xmlns:ns13="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<ns13:Body></ns13:Body>
<ns13:Header Name="ReplyTo" Namespace="http://www.w3.org/2005/08/addressing"></ns13:Header>
<ns13:Header Namespace="http://www.w3.org/2005/08/addressing" Name="To"></ns13:Header>
<ns13:Header Name="From" Namespace="http://www.w3.org/2005/08/addressing"></ns13:Header>
<ns13:Header Name="MessageID" Namespace="http://www.w3.org/2005/08/addressing"></ns13:Header>
<ns13:Header Name="FaultTo" Namespace="http://www.w3.org/2005/08/addressing"></ns13:Header>
<ns13:Header Name="Action" Namespace="http://www.w3.org/2005/08/addressing"></ns13:Header>
<ns13:Header Name="RelatesTo" Namespace="http://www.w3.org/2005/08/addressing"></ns13:Header>
<ns13:Header Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" Name="AckRequested"></ns13:Header>
<ns13:Header Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" Name="CreateSequence"></ns13:Header>
<ns13:Header Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" Name="Sequence"></ns13:Header>
<ns13:Header Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" Name="SequenceAcknowledgement"></ns13:Header>
</ns13:SignedParts>
</ns11:All>
</ns11:ExactlyOne>
</ns11:Policy>
<types>
<xsd:schema>
<xsd:import namespace="http://server.glassfish.sddag.ox.ac.uk/" schemaLocation="http://localhost:8080/SecureApplication/SecureWSService?xsd=1"></xsd:import>
</xsd:schema>
</types>
<message name="add">
<part name="parameters" element="tns:add"></part>
</message>
<message name="addResponse">
<part name="parameters" element="tns:addResponse"></part>
</message>
<portType name="SecureWS">
<operation name="add">
<input message="tns:add"></input>
<output message="tns:addResponse"></output>
</operation>
</portType>
<binding name="SecureWSPortBinding" type="tns:SecureWS">
<ns14:PolicyReference xmlns:ns14="http://schemas.xmlsoap.org/ws/2004/09/policy" URI="#SecureWSPortBindingPolicy"></ns14:PolicyReference>
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"></soap:binding>
<operation name="add">
<soap:operation soapAction="add"></soap:operation>
<input>
<ns15:PolicyReference xmlns:ns15="http://schemas.xmlsoap.org/ws/2004/09/policy" URI="#SecureWSPortBinding_add_Input_Policy"></ns15:PolicyReference>
<soap:body use="literal"></soap:body>
</input>
<output>
<ns16:PolicyReference xmlns:ns16="http://schemas.xmlsoap.org/ws/2004/09/policy" URI="#SecureWSPortBinding_add_Output_Policy"></ns16:PolicyReference>
<soap:body use="literal"></soap:body>
</output>
</operation>
</binding>
<service name="SecureWSService">
<port name="SecureWSPort" binding="tns:SecureWSPortBinding">
<soap:address location="http://localhost:8080/SecureApplication/SecureWSService"></soap:address>
</port>
</service>
</definitions>The contents of META-INF (The WSDL):
<?xml version="1.0" encoding="UTF-8"?><!-- Published by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.3.1-hudson-417-SNAPSHOT. --><!-- Generated by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.3.1-hudson-417-SNAPSHOT. --><definitions xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://server.glassfish.sddag.ox.ac.uk/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://server.glassfish.sddag.ox.ac.uk/" name="SecureWSService" xmlns:wsp="http://www.w3.org/ns/ws-policy" xmlns:sc="http://schemas.sun.com/2006/03/wss/client" xmlns:wspp="http://java.sun.com/xml/ns/wsit/policy">
<types>
<xsd:schema>
<xsd:import namespace="http://server.glassfish.sddag.ox.ac.uk/" schemaLocation="http://localhost:8080/SecureApplication/SecureWSService?xsd=1"></xsd:import>
</xsd:schema>
</types>
<message name="add">
<part name="parameters" element="tns:add"></part>
</message>
<message name="addResponse">
<part name="parameters" element="tns:addResponse"></part>
</message>
<portType name="SecureWS">
<operation name="add">
<input message="tns:add"></input>
<output message="tns:addResponse"></output>
</operation>
</portType>
<binding name="SecureWSPortBinding" type="tns:SecureWS">
<wsp:PolicyReference URI="#SecureWSPortBindingPolicy"/>
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"></soap:binding>
<operation name="add">
<soap:operation soapAction="add"></soap:operation>
<input>
<soap:body use="literal"></soap:body>
</input>
<output>
<soap:body use="literal"></soap:body>
</output>
</operation>
</binding>
<service name="SecureWSService">
<port name="SecureWSPort" binding="tns:SecureWSPortBinding">
<soap:address location="http://localhost:8080/SecureApplication/SecureWSService"></soap:address>
</port>
</service>
<wsp:Policy wsu:Id="SecureWSPortBindingPolicy">
<wsp:ExactlyOne>
<wsp:All>
<sc:CallbackHandlerConfiguration wspp:visibility="private">
<sc:CallbackHandler default="example1" name="usernameHandler"/>
<sc:CallbackHandler default="password1" name="passwordHandler"/>
</sc:CallbackHandlerConfiguration>
<sc:TrustStore wspp:visibility="private" type="JKS" storepass="changeit" location="/Applications/NetBeans/glassfish-v2ur2/domains/domain1/config/cacerts.jks" peeralias="xws-security-server"/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
</definitions>The wsit-client:
<?xml version="1.0" encoding="UTF-8"?>
<definitions
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" name="mainclientconfig"
>
<import location="SecureWSService.xml" namespace="http://server.glassfish.sddag.ox.ac.uk/"/>
</definitions>This bug still isn't fixed.
Thank you, adding Glassfish's webservices-rt.jar does fix it. -
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,
KaceeCan 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,
SandeepHi,
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 -
Problems - WLS 10.0 web service client
I'm having a few issues with WLS 10.0 web service client.
I generated a service control from the WSDL. The service is provided by a 3rd party (non-WLS) at another company. I generated the control within my web project and it's deployed as part of the web application. I experience the following problems with the service control API:
1) The methods setKeyStore(), setTrustStore(), setClientCert() all seem to be ignored - the server always uses the values set in the server's environment definition. Note - the setEndpointAddress() seems to work.
2) The client request does not set the 'Content-Type' HTTP header correctly (it's set to text/html) - I have no way to override this via the service control API (that I can see).
3) I don't see any way/place to turn on more detailed tracing of what's going on internally with the service control invocation - is there a way to enable a detailed trace log of what is happening within the service control?
Note: I'm able to call the web service via the test client (after importing the 3rd party server cert into my local cacerts).
Thanks,
[email protected]Thank you for the reply..
But im still geting the same error. I have tried to include all the libraries in JWSDP pack but still.. I have managed to narrow down the place where the error occures.. It actually happens when I try to get the WebService Client Servant which is located in the package LSC:
---> LSC.LWServiceGenClient.LWS_Impl service = new LSC.LWServiceGenClient.LWS_Impl();
LSC.LWServiceGenClient.LWSServantInterface lagerServiceServant = LSC.LWServiceGenClient.LWSServantInterface_Stub)service.getLWSServantInterfacePort();
return lagerServiceServant;
Could something be wrong with the way I package the Jar? I'm using Sun One Studio and have tried including the 5 packages the application consists of; I have tried including just the files; moving the main class to <root>.. Still same problem..
Or could there be some different fundemental thingy I have forgotten ??
thanks
Aqoi -
OC4J web service client and Spring
Hello!
I'm trying to use the Web Service client mechanism of Spring 1.2.6 in conjunction with OC4J by subclassing org.springframework.remoting.jaxrpc.JaxRpcPortProxyFactoryBean and using generated classes from soap-ui.
Problem is that I keep getting errors like this when starting the (embedded) OC4J:
org.springframework.beans.FatalBeanException: Could not instantiate class [at.sozvers.bva.shared.util.CommaSeparatedClassPathContext]; constructor threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'zpvPartnerAdresseWebService' defined in class path resource [onlineContext.xml]: Initialization of bean failed; nested exception is oracle.j2ee.ws.client.ServiceExceptionImpl: service: {http://oasdev1.bva.sozvers.at:8192/zpvPartnerAdresse/}PartnerAdresse does not contain port: {http://oasdev1.bva.sozvers.at:8192/zpvPartnerAdresse/}PartnerAdresse
The WSDL:
<?xml version="1.0" encoding="UTF-8"?><wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:ns1="http://service.zpv.esb.bva.sozvers.at" xmlns:ns2="http://error.shared.bva.sozvers.at" xmlns:ns3="http://dto.zpv.esb.bva.sozvers.at" xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope" xmlns:soapenc11="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soapenc12="http://www.w3.org/2003/05/soap-encoding" xmlns:tns="http://service.zpv.esb.bva.sozvers.at/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://service.zpv.esb.bva.sozvers.at/">
<wsdl:types>
<xsd:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://service.zpv.esb.bva.sozvers.at/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="lesen">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="1" name="in0" nillable="true" type="ns1:PartnerAdresseServiceRequest"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="lesenResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="1" name="out" nillable="true" type="ns3:ZPVPartnerAdresseDTO"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="schreiben">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="1" name="in0" nillable="true" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="in1" nillable="true" type="ns1:PartnerAdresseServiceRequest"/>
<xsd:element maxOccurs="1" minOccurs="1" name="in2" nillable="true" type="ns3:ArrayOfZPVAdresseDTO"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="schreibenResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="1" name="out" nillable="true" type="ns3:ZPVResponseDTO"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
<xsd:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://service.zpv.esb.bva.sozvers.at" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType name="PartnerAdresseServiceRequest">
<xsd:sequence>
<xsd:element minOccurs="0" name="bisDat" type="xsd:dateTime"/>
<xsd:element minOccurs="0" name="bkFachschluessel" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="bkInput" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="vonDat" type="xsd:dateTime"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
<xsd:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://dto.zpv.esb.bva.sozvers.at" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType name="ZPVPartnerAdresseDTO">
<xsd:sequence>
<xsd:element minOccurs="0" name="exceptionDTO" nillable="true" type="ns2:ExceptionDTO"/>
<xsd:element minOccurs="0" name="responseDto" nillable="true" type="ns3:ZPVResponseDTO"/>
<xsd:element minOccurs="0" name="zpvAdresseDTOs" nillable="true" type="ns3:ArrayOfZPVAdresseDTO"/>
<xsd:element minOccurs="0" name="zpvPartnerStammdatenDTO" nillable="true" type="ns3:ZPVPartnerStammdatenDTO"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ZPVResponseDTO">
<xsd:sequence>
<xsd:element minOccurs="0" name="exceptionDTO" nillable="true" type="ns2:ExceptionDTO"/>
<xsd:element minOccurs="0" name="fehlerJN" nillable="true" type="xsd:boolean"/>
<xsd:element minOccurs="0" name="zpvFehlerId" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="zpvMeldungstext" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ArrayOfZPVAdresseDTO">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="ZPVAdresseDTO" nillable="true" type="ns3:ZPVAdresseDTO"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ZPVAdresseDTO">
<xsd:sequence>
<xsd:element minOccurs="0" name="abgabestelle" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="adresstyp" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="anschriftzusatz" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="beginn" type="xsd:dateTime"/>
<xsd:element minOccurs="0" name="beharrungsadresse" nillable="true" type="xsd:boolean"/>
<xsd:element minOccurs="0" name="bundeslandKennzeichen" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="ende" type="xsd:dateTime"/>
<xsd:element minOccurs="0" name="exceptionDTO" nillable="true" type="ns2:ExceptionDTO"/>
<xsd:element minOccurs="0" name="gebrauchKurz" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="hausnummer" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="ort" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="plz" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="postfach" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="staatkennzeichen" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="staatname" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="stocktuernummer" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="strasse" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="updatecount" nillable="true" type="xsd:int"/>
<xsd:element minOccurs="0" name="verwendungsartKurz" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="zpvAevnummer" nillable="true" type="xsd:long"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ZPVPartnerStammdatenDTO">
<xsd:sequence>
<xsd:element minOccurs="0" name="angehoeriger" type="xsd:boolean"/>
<xsd:element minOccurs="0" name="bkFachschluesselAngabe" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="exceptionDTO" nillable="true" type="ns2:ExceptionDTO"/>
<xsd:element minOccurs="0" name="familienname" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="familiennameDiakritisch" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="geburtsDAT" type="xsd:dateTime"/>
<xsd:element minOccurs="0" name="geschlechtKZ" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="isoa3Staatsbuergerschaft" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="landesstellenKennzeichen" nillable="true" type="xsd:int"/>
<xsd:element minOccurs="0" name="namensergaenzung" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="namenskorrektur" type="xsd:boolean"/>
<xsd:element minOccurs="0" name="staatsbuergerschaftSonderformKZ" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="stornoJN" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="titelHintenKurz" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="titelVorneKurz" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="todesDAT" type="xsd:dateTime"/>
<xsd:element minOccurs="0" name="updatecount" nillable="true" type="xsd:int"/>
<xsd:element minOccurs="0" name="versicherter" type="xsd:boolean"/>
<xsd:element minOccurs="0" name="vorname" nillable="true" type="xsd:string"/>
<xsd:element minOccurs="0" name="vornameDiakritisch" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
<xsd:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://error.shared.bva.sozvers.at" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType name="ExceptionDTO"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="schreibenResponse">
<wsdl:part element="tns:schreibenResponse" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:message name="lesenRequest">
<wsdl:part element="tns:lesen" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:message name="lesenResponse">
<wsdl:part element="tns:lesenResponse" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:message name="schreibenRequest">
<wsdl:part element="tns:schreiben" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:portType name="PartnerAdresseServicePortType">
<wsdl:operation name="lesen">
<wsdl:input message="tns:lesenRequest" name="lesenRequest">
</wsdl:input>
<wsdl:output message="tns:lesenResponse" name="lesenResponse">
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="schreiben">
<wsdl:input message="tns:schreibenRequest" name="schreibenRequest">
</wsdl:input>
<wsdl:output message="tns:schreibenResponse" name="schreibenResponse">
</wsdl:output>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="zpvPartnerAdresseBinding" type="tns:PartnerAdresseServicePortType">
<wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="lesen">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="lesenRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="lesenResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="schreiben">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="schreibenRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="schreibenResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="PartnerAdresse">
<wsdl:port binding="tns:zpvPartnerAdresseBinding" name="zpvPartnerAdresse">
<wsdlsoap:address location="http://0.0.0.0:8192/zpvPartnerAdresse/"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
The Spring configuration of the WS- bean:
<bean id="zpvPartnerAdresseWebService" class="at.sozvers.bva.panda.m02.service.PartnerAdresseProxyFactoryBean">
<property name="serviceInterface">
<value>at.sozvers.bva.panda.m02.service.RemotePartnerAdresseBean</value>
</property>
<property name="wsdlDocumentUrl">
<value>http://oasdev1.bva.sozvers.at:8192/zpvPartnerAdresse/main.wsdl</value>
</property>
<property name="namespaceUri">
<value>http://oasdev1.bva.sozvers.at:8192/zpvPartnerAdresse/</value>
</property>
<property name="serviceName">
<value>PartnerAdresse</value>
</property>
<property name="portName">
<value>PartnerAdresse</value>
</property>
</bean>
Does anyone have ideas or experience using Spring 1.2.6 for web service clients with oc4j 10.1.3 ?
Thank you in advance
StefanI also tried to use "zpvPartnerAdresse" as portName, but this didn't change anything.
Stefan -
WLDL files exported from XI 2.0 not valid for Web Service Clients
Hi there,
Im struggling for almost a week with a <b>BAPI WSDL file</b> exported from the XI repository. My scenario is very simple; A BAPI in R/3 exposed as web service through XI using the SOAP adapter.
The intention was to generate a Web Service Client based on this WSDL file, unfortunately I get all kind of errors when trying to generate the client. (using tools like, SOAPScope, XML Spy and WebSphere Developer Studio none of this tools can validate the generated WSDL file obtained from XI)
Can someone <b>Please explain</b> me how/what exaclty do I have to do in order to expose my BAPI as Web Service in XI 2.0? Or Please tell me if this is just impossible in this version of XI.
Thanks a lot!
Rob.Hi Rob,
It seems that when exporting to a WSDL file from the Repository, <service> and <binding> are missing from the structure.
A way to work this out is to either add them maually, or to create the WSDL from the Directory, using the Create End Point as Webservice in the Tools menu.
When you do that, consider a couple of things:
1. The message interface, by which you create the wsdl should be inbound. The message interface in the scenario should be outbound.
2. In the binding section, the produced url is of the intergration server, and you need to change it to that defined in the SOAP adapter configuration.
Hope this helps.
Avihai -
Web Service client running on Tomcat behind Apache-ModJk
Hi all.
I've realized a web service, which have been deployed on a Tomcat 5.5 instance running behind a firewall.
The Web Service is published through an Apache 2.0 Web Server, which is in the DMZ and which is connected to Tomcat via modjk.
Everything is working fine (as apache forwards to tomcat clients' calls), except from one thing: one of the web-methods needs to connect to a remote server to validate some data... that is, this web-method implements a "web service client" piece of code, by which a remote validating method must be called.
So, the problem is that this remote method must be accessed from something running behind the firewall...
One way could be to open a hole in the firewall, allowing only calls to that remote address, but I'd rather avoid this.
Do someone have other suggestions?
Is there perhaps any way to use mod_jk also for "exiting" and not only for "entering"?
Any help will be very appreciated!!Could you not use a proxy server. The web service client would go through the proxy server to the internet
-
Web Service Client: Project Additional Classpath contributor not working?
I've created a simple web service client/proxy and it works when debugging and running in JDeveloper 10.1.3.3
I created a deployment profile that includes "Project Additional Classpath". The preview does not show any of the jar dependencies being included and the client application does not run because it is missing the dependencies.
Am I missing something simple here? I've searched forever on this with no luck (it's now 2am!)
Help is much appreciatedFrank,
Thank you for your reply. The funny thing is that I had known how to do this in the past.
I have to say. The layout of that screen just is not intuitive.
First, if you select file groups\project output\Contributors and select "Project Additional Path" you would think that you'd either get to select the class libraries there or at least in the filters screen.
Second, the new button on the lower left, beneath the tree control when selecting the File Groups node is an arrangement I havn't seen used in any other application. Usually when you select a tree node, the right side window would have a tool bar over an arrangement of the sub-nodes/folders and you would click new on that tool bar. The new button goes completely unnoticed where it is. I'm sure it's nothng once you get used to it but for a noob like me, it wasn't apparent
I took a brief look at 11g and it seems they're changing some of the screens so perhaps this stuff will become more intuitive.
Thank you for your help.
Maybe you are looking for
-
we have 2 itouchs, we a separate itunes account for each one. We have one home computer to use them both on for sync and icloud, the icloud will not accept the 2 accounts?
-
Keep getting Kernel panics on Snow leopard 10.6.3
I recently messed up my leopard install... long story. When restoring the system I decided to go with Snow leopard, thought why not, would like to become more familiar with it. Ever since I got it I have been getting Kernel Panics out the wazoo. I ha
-
Hi all: I need some inputs form you all. I have some doubts in Vendor Otif in MM-Purchasing. 1.What are all the infocoube,ods,infosource,datasource required to use for vendor otif?.I expect in technical wise. 2.Do u have any document how vendor otif
-
Exporting column and table comments
I need to be able to create an external "data dictionary" to show to database users. I am currently exporting to a reporting schema, and then writing SQL against the reporting schema to get table, column, datatype, etc... information. I also need to
-
Hello friends I want to use some functions which are in Java Servlet Specification 2.3. I found that I have to use Tomcat for this. Any one who know about it please help, to find where I will get Its setup and required information to run the servlet