Studio Creator and Web Service Clients

Can somebody please explain to me or point me to some actual documentation on how this junk works?
I have a web service client that was generated from a wsdl file being used by my studio creator project... the web service has changed and now i need to update/replace the client with a new one. It seems like no matter what I do it wants to tag a '3' onto the end of the name of the web service port and also build it into the package names - requirign me to go to all the places in my code that use this client and fix it to have a stupid 3 in it....
Just replacing web service clients appears to be a huge ordeal involving removing the client libraries from the library folder, and even going into the build-impl.xml to remove references to the old client jars...
I can't find any options to specify the web service client jar which would allow me to just overwrite the old ones instead of creating these new ones with archaic numbers (e.g. 1384793814) on the end of them...
Is there an easy way to wipe clean or update a web service from an entire project without leaving these ridiculous references everywhere? When I try to replace the name personService3 with personService in the web service client generator tool it tells me the name is already in use but I can't for the life of me find it...
can somebody shed some light on this for me? please help before i yank all my hair out...
Thanks....
Message was edited by:
kregan77

Please see the article I wrote called, "Web Service Consumption Security" at http://devservices.sun.com/premium/jscreator/standard/reference/tips/ws_consumption_security.html
This will give you an idea of what is supported for the current version of Creator. Also, if you want some other feature supported, please submit a detailed use case to this forum.
Thanks!
-David

Similar Messages

Web-Service Proxy and Web-Service Client access in a Bean (EJB 3.0)

Hello Community,
i want to access the SAP Knowledge-Management via the Webservice "RepositoryFrameworkWS", which resides on our Portal-System, from my Java-Application, which runs on a NW CE 7.11 Ehp1 Java Server.
I choosed to create a WS-Client as a deployable client. So i created an Bean Project, imported the WSDL and created a WS-Proxy in that project. Additionaly i added some beans to that Bean-Project which use the WS-Proxy to access the KM.
So far so good.
But the WSDL also creates a Service-Endpoint, which already has an url for the WS-Target and Authentication-Information (in my case it seems that no Authentication is active) in its body.
Because my client shell run on different systems in the future i searched for a way to easiliy deploy my application and adapt target-information elsewhere. I found in the documentation, that after deploying the deployable WS-Proxy/Client this can be done in the NW-Administrator under SOA-Management->Application and Scenario Communication->Single Service Administration.
To my surprise i found my deployed WS there. And the entry for the there listed Port was configurable. But unfortunatly this customization is ignored by the application. For example i changed authentication to a HTTP-Authentication with a specific user and also changed to Target-URL. But with no success.
What's wrong here?
i accessed the WS in my bean in the following way:
    public Class xyz
     @WebServiceRef (name="RepositoryFrameworkWS")
     RepositoryFrameworkWS service;
      RepositoryFrameworkWSViDocument vi = service.getPort(RepositoryFrameworkWSViDocument.class);
     vi.findResources(rid,....)
regards
Matthias Hayk
Edited by: Matthias Hayk on Sep 15, 2009 10:13 AM

Hi Matthias
In Single Service Administration there are two views: Webservices and WS Clients configurations. First of all you should enable BASIC HTTP authentication in WS configuration. Then go to WS Client configuration and enter user/password in HTTP BASIC authentication settings.
Hope this help.
BR, Siarhei

Web service client invoke problem

Hi all,I want to in sap studio to develop web service client to invoke a .net webservice,this webservice need authen ,so I develop a standandalone proxy to write a consle to invoke my code.
The follwoing is my invoke code
public class WebServiceTest {
     public static void main(String[] args) throws Exception {
          GetScaVersion parameter = new GetScaVersion();
          ManagementSoap port = new ManagementImpl().getLogicalPort();
                    port._setProperty(port.USERNAME_PROPERTY,"administrator");
                    port._setProperty(port.PASSWORD_PROPERTY,"administrator");
          GetUserList list=new GetUserList();
          GetScaVersionResponse response= port.getScaVersion(parameter);
          System.out.println(response.getGetScaVersionResult());
          System.out.println(response.getAErrorMsg());
But final I got the following errors,
Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
Error Message is :com/sap/guid/GUIDGeneratorFactory
null
Invalid UserName and Password
so I just want to ask ,if the webservice is need to authen,does the following tow senteces works for authenciation ?
port._setProperty(port.USERNAME_PROPERTY,"administrator");
port._setProperty(port.PASSWORD_PROPERTY,"administrator");

Hi,
You need to set the credentials of the .net user.
Also, which type of proxy have you created? Are you able to open the wsdl in the browser?.
Thanks,
Vasu

Web service client and SSL Certificate

Hello, everyone,
I have a problem that has really stumped me.
I've written a web service client for a web service that has a digital certificate. This comes in the form of a .pfx file.
When I try send a request to the web service, I get the following:
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
faultActor:
faultNode:
faultDetail:
     {http://xml.apache.org/axis/}stackTrace:javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
     at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Unknown Source)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(Unknown Source)
     at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Unknown Source)
     at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Unknown Source)
     at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(Unknown Source)
     at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(Unknown Source)
     at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Unknown Source)
     at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Unknown Source)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source)
     at org.apache.axis.components.net.JSSESocketFactory.create(JSSESocketFactory.java:186)
     at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:191)
     at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:404)
     at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
     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 org.tempuri.BasicHttpBinding_IExternalServiceStub.submitAchievementBatchJob(BasicHttpBinding_IExternalServiceStub.java:531)
     at uk.gov.qcf.lrs.api.services.IExternalServiceProxy.submitAchievementBatchJob(IExternalServiceProxy.java:56)
     at uk.org.aqa.main.Main.main(Main.java:111)
Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
     at sun.security.validator.PKIXValidator.doBuild(Unknown Source)
     at sun.security.validator.PKIXValidator.engineValidate(Unknown Source)
     at sun.security.validator.Validator.validate(Unknown Source)
     at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.validate(Unknown Source)
     at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown Source)
     at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown Source)
     ... 24 more
Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
     at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(Unknown Source)
     at java.security.cert.CertPathBuilder.build(Unknown Source)
     ... 30 more
     {http://xml.apache.org/axis/}hostname:WM8-319
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
     at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
     at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:154)
     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 org.tempuri.BasicHttpBinding_IExternalServiceStub.submitAchievementBatchJob(BasicHttpBinding_IExternalServiceStub.java:531)
     at uk.gov.qcf.lrs.api.services.IExternalServiceProxy.submitAchievementBatchJob(IExternalServiceProxy.java:56)
     at uk.org.aqa.main.Main.main(Main.java:111)
Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
     at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Unknown Source)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(Unknown Source)
     at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Unknown Source)
     at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Unknown Source)
     at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(Unknown Source)
     at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(Unknown Source)
     at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Unknown Source)
     at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Unknown Source)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source)
     at org.apache.axis.components.net.JSSESocketFactory.create(JSSESocketFactory.java:186)
     at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:191)
     at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:404)
     at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
     ... 12 more
Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
     at sun.security.validator.PKIXValidator.doBuild(Unknown Source)
     at sun.security.validator.PKIXValidator.engineValidate(Unknown Source)
     at sun.security.validator.Validator.validate(Unknown Source)
     at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.validate(Unknown Source)
     at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown Source)
     at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown Source)
     ... 24 more
Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
     at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(Unknown Source)
     at java.security.cert.CertPathBuilder.build(Unknown Source)
     ... 30 moreI've looked onliine to try to solve this issue, and it seemed that the answer was the add the certificate to the keystore. I had a lot of issues doing this, due to the certificate being a .pfx file. However, using the following, I was able to do it:
keytool -importkeystore -srckeystore "sandpit.pfx" -destkeystore "%JAVA_HOME2%\lib\security\cacerts" -srcstoretype pkcs12 -deststoretype jks -srcstorepass password -deststorepass anotherpassword -vHowever, I am still getting the same error. This may be because this isn't the keystore used, but it is located in the area marked as being used in the build path.
I then looked further, and found that I may need to add:
System.setProperty("javax.net.ssl.trustStore","myKeystore");
System.setProperty("javax.net.ssl.trustStorePassword","myPassword");altering where appropriate. But this didn't work, and I'm thinking that this would involve a lot more code than just those two lines.
I'm just not sure what to do, and am hoping someone can help. I didn't think it would be too big an issue to ensure my program used the certificate, but it seems to be. I thought that once it was added to the keystore, that would be it, but it appears not.
I'm sure this isn't a rare issue, but I just lack the knowledge to make any headway. Please can someone help or point me in the right direction?
Thank you very much in advance.
Robin

Sorry to bother you again with my request but I would appreciate some help with my problems.
Nobody his using some web services who requires protection ?
Thanks a lot.

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
Stefan

I also tried to use "zpvPartnerAdresse" as portName, but this didn't change anything.
Stefan

Setting connect timeout and read timeout on a Web service Client

How can I set timeout values for a SOAP Web service client?
I don't want to set timeout values for the complete JVM, but on a call-by-call basis. I was looking for something like:
SOAPConnection c = ....
c.setTimeout(...);Anyone?

Thanks again fsato4, but i still can not resolve my problem. I must use the java 1.2.2 and i think the package java.nio.charset is not supported. I have read documentation about the use of encodings but i can not understand clearly what is happening in my application. Let me explain what i am thinking and ask you some things.
I send a message from the client in VB using soap toolkit, obviously in UTF-8 format. When the message is received in my Java Web service, Do i need to do something in order to my Java string understands the message?.
What i am doing is to obtain the byte array with the following line:
byte[] utf8Bytes = strXmlFile.getBytes("UTF8");
And then i use the constructor of the string as follows:
String ostr = new String (utf8Bytes,"UTF8"); I think that in this point i have my string in a valid representation for my server (Sun solaris) Rigth?. And finally i use my new string to pass that value to my function which expects a java.lang.String, but the result is that all the special characters are replaced.
Just after of the new String line, i write my string to an Buffered Writer pointed to a FileOutputStream (just for Doublecheck) using the "ISO8859_1" encoding and for my surprise i can read very well that xml in my browser and the special characters are displayed in a correct way. Could you please explain me why?
Thanks for your help.

Dynamic and embeddable web service client

Hello,
I want to write a web service client application that can run on JSE (not requiring JEE5, J2EE 1.4, an enterprise server or anything). This should be no problem with JSE6. However, I would like the client application to run on embedded devices (cell phones, PDA's etc.) as well. So I would like to know if web service clients are supported by the embedded JAVA runtimes in such devices. One additional requirement is that the webservices will only be accessible over SSL. So all clients will need support for SSL as well.
The other problem (and probably the more difficult one) is this: Using the WDSL file, stubs for the client can be generated. However, the WDSL files (at least the ones generated by the SUN enterprise server) contain the IP-address of the server. In the final deployment of the system the IP-address of the server will be different from the one of the development system. Secondly, the same service might be deployed on different servers and needs to be accessible from the same client. So I'm looking for a mechanism to still use stubs generated from the WDSL file, but dynamically configure the IP address of the server to which the client should connect.
Any help here is greathly appreciated.

Hey Rishika,
You don't need tomcat to run a client. A web service client does not need a container and can be run without it.
Karan

OIM 11gR2 Request Validator Plugin and Axis based Web Service Client

Hi,
I am trying call a web service client generated using axis2 from a request validator plugin in OIM 11gR2 and I have all the axis related jar files under the plugin lib folder but it fails due to the axis reference issues.
I tried putting the jar files under different locations like thirdparty folder, server lib etc. But it is giving issues every where. Please let me know if you have some solution.
Thanks in advance,

Haven't worked on this, but have you tried by putting the axis libraries inside the plugin lib folder when you are building up the plugin? Also you need to check asix2 compatibility with weblogic version with R2.
-Bikash

JAX-WS web service client and Windows integrated Security authentication

I am currently developing a JAX-WS web service client running on WebLogic 10.3.2.0. The client is connecting to exchange web service running on IIS.
Everything works well when EWS is configured with Http basic authentication.
The problems started when I changed the autentication method on EWS from Http basic authentication to Windows integrated Security authentication.
The client is then unable to authenticate to the web service. Every request made to EWS returns with the message : Invalid HTTP server response [401] - Unauthorized.
I tried using an authenticator like this one:
static class RetrieveWSDLAuthenticator extends Authenticator
private String username, password;
public RetrieveWSDLAuthenticator(String user, String pass)
username = user;
password = pass;
@Override
protected PasswordAuthentication getPasswordAuthentication()
return new PasswordAuthentication(username, password.toCharArray());
and setting it as the default authenticator :
Authenticator.setDefault(new MyAuthenticator("username", "password"));
but the method getPasswordAuthentication() was not even called.
Is there a way to make a JAX-WS client works with Windows integrated Security ?

WIS is not suppported on WLS JAX-WS. You'll need to use other authentication mechanisms such as http basic (which you tried already), or message-level security such as UNT, or SAML.
Regards,
Pyounguk

SAAJ (Web Service Client) and Integrated windows Authentication

Hello
I have build a web service client using SAAJ, the Web services is deployed on MS IIS. Every thing seems to work fine, The problem appears when I apply directory security on the Web Service Directory. When I apply Basic authentication SAAJ manages to send the user name and password and it goes fine, but when I apply Integrated Windows Authentication, I always get a response Access is Denied.
I know we can authenticate the user credentials from NTLM from JAAS but here I am using a web services client.
My Question is How can we pass the user credentials through a web service client to the IIS when the directory security is Windows Integrated Authentication?
Any work around or the solution will be appreciated.
Thanks :-)
Syed Saulat

Hi Gilles,
Thank you very much for your answer. Actually, I think the problem is a little bit different. The kerberos server is not delivering a "grant" ticket to the client for the service provided by the VIP, because the CSS didn't register to the Active Directory, as a normal W2K web server would. The first thing the client does when he wants to access a web server behind the CSS is to ask the kerberos server for a "gtanting" ticket for that service. So the problem arise before the client sends any packet to the CSS (therefore I think it is more a Microsoft problem rather than a CSS problem).
But for sure, other people have this environment I suppose...
What is your opinion on this ?
Yves

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 M

Can you/anybody post solution. I have the same problem.
Thanks
Srinivas

Web Services Client is not working fine on JBOSS 4.0.4.GA

Dear Team,
we had JBOSS AS 4.0.3 and web services was build on EJB which was working fine. we new have to migrate it to JBOSS 4.0.4.GA Application Server....
we have generated wsdl, webservices.xml and jaxrpc-mapping.xml file from wstools.exe of JBOSS AS 4.0.4.GA and we are able to see the web services wsdl on web browser.... but when we execute the same client which was earlier running for JBOSS 4.0.3 it throws error saying
javax.xml.rpc.ServiceException :modeler error : uniqueness constraint voilation, duplicate member found "type" to javastructureType "userDetails"
rgrds,
~J

Please provide the following information:
- Help > About BEA Workshop studio - build #
- Window > Preferences > Java - Installed JREs - what is your default JRE selection?
- Run > Run... _ J2EE Server > JBoss 4.0 - Have you customized any of the default values. Ex: Arguments, Classpath ...
- What kind of application are you trying to debug Struts/JSF?
- Can you try to reproduce the problem with the bundled samples workshop-struts-tour/bookstore (run the app and modify one of the configuration file).
- Do you see the same behavior with Sun JDK?
- Finally, copy-paste the first line from the "Console View"
Message was edited by:
ram.v

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

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 Generation on 7.10 SP3 - No WSDL URL is specified....

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

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

Studio Creator and Web Service Clients

Similar Messages

Maybe you are looking for