Validating Web Services

Hi,
I wanted to know what was the best mechanism to add validation to Web Service testing through ETest.
For example, record and playback is quite easily done through ETest. But how can one determine if the response SOAP was the correct one. What type of test needs to be added to the script to make it check the response.
Please suggest, as I need to make my script check Web Services in detail.
Thanks
Shankar

Solved Error

Similar Messages

VAT Validation web service from EU VIES

Hello Experts,
We are using external webservice from VIES for VAT validation.It was working fine for some time but from past few weeks we are not getting response from webservice.We are using WSDL http://ec.europa.eu/taxation_customs/vies/checkVatService.wsdl.Please let me know,if any one is aware of this issue.
Thanks in Advance.
Ankur

Hi
Is this working now ?
I would like to use the VIES webservice but I am not able to set it up ...do you have the same issue ?
How to set up the VIES webservice (consumption)?http://scn.sap.com/thread/3648197
Cheers
Stephane

Not able to create Web Service Model in Visual Composer

Hi All,
I am trying to create a Web Service model in VC but I am not able to do so.
When I am clicking on Create button its saying Invalid URL.I have tried a lot of web service URL.
Can any one provide me some valid web service URLs or can anyone tell me what could be the problem.
Sometimes it gives "Bad or missing XML"
Please help
Regards
Roshni
Edited by: Roshni Verma on Jan 15, 2010 3:09 PM

Hi Roshni,
Check the below wiki for web services.
http://wiki.sdn.sap.com/wiki/display/VC/WebservicesforVisual+Composer
Use the web services from www.webservicex.net
Kind Regards
Basheer

Consume Web Service In Coldfusion Error

I'm having a problem using cfinvoke or adding this web service url in the coldfusion admin.
<cfinvoke returnvariable="returndata" webservice="http://www.fortedata.com:8080/axis2/services/FdsWebService?wsdl" refreshwsdl="yes" method="PostData">
I get the error for cfinvoke
"Cannot generate stub objects for web service invocation. "
"Name:
http://www.fortedata.com:8080/axis2/services/FdsWebService?wsdl. WSDL:
http://www.fortedata.com:8080/axis2/services/FdsWebService?wsdl. java.io.IOException: ERROR: Missing element inFault "SQLException" in operation "SQLException", in binding GetRates It is recommended that you use a web browser to retrieve and examine the requested WSDL document to ensure it is correct. If the requested WSDL document cannot be retrieved or is dynamically generated, it is likely that the target web service has programming errors. "
and in the administrator
""Error creating web service. Please ensure that you have entered a correct Web Service name or URL.""
The url is
http://www.fortedata.com:8080/axis2/services/FdsWebService?wsdl
page loads fine in a browser...
I do see an issue being brought up here in the wsdl, but I have no idea why...this isnt my wsdl btw..
<wsdl:operation name="GetRates">
<wsdl:input message="ns:GetRatesRequest" wsaw:Action="urn:GetRates"/>
<wsdl:output message="ns:GetRatesResponse" wsaw:Action="urn:GetRatesResponse"/>
<wsdl:fault message="ns:SQLException" name="SQLException" wsaw:Action="urn:GetRatesSQLException"/>
</wsdl:operation>
line 3
any ideas?
Thanks for any help...

Sorry didnt post everything for the sake of space
I just ended up using .NET to deal with the service..CF just didnt even recognize the url as a valid web service let alone care if I was passing arguments to it.
On a side note, CF admin doesnt recognize the url as a web service and dreamweaver doesnt recognize the url as a web service either.
<cfinvoke method="PostLead" returnvariable="returndata" webservice="http://www.fortedata.com:8080/axis2/services/FdsWebService?wsdl" refreshwsdl="yes">
<cfinvokeargument name="SpecVersion" value="0">
<cfinvokeargument name="ForteId" value="TESTID">
<cfinvokeargument name="AuthKey" value="guestauthenticationkey">
<cfinvokeargument name="LastName" value="0">
<cfinvokeargument name="FirstName" value="0">
<cfinvokeargument name="Address" value="0">
<cfinvokeargument name="city" value="0">
<cfinvokeargument name="state" value="0">
<cfinvokeargument name="zip" value="0">
<cfinvokeargument name="year" value="0">
<cfinvokeargument name="vin" value="0">
<cfinvokeargument name="make" value="0">
<cfinvokeargument name="model" value="0">
<cfinvokeargument name="phone" value="0">
<cfinvokeargument name="crdate" value="0">
<cfinvokeargument name="listcode" value="0">
<cfinvokeargument name="odometer" value="0">
<cfinvokeargument name="dually" value="0">
<cfinvokeargument name="commercial" value="0">
<cfinvokeargument name="convvan" value="0">
<cfinvokeargument name="coverage" value="0">
<cfinvokeargument name="term" value="0">
<cfinvokeargument name="deduct" value="0">
<cfinvokeargument name="av" value="0">
<cfinvokeargument name="gps" value="0">
<cfinvokeargument name="wt" value="0">
<cfinvokeargument name="sg" value="0">
<cfinvokeargument name="emis" value="0">
<cfinvokeargument name="fintype" value="0">
<cfinvokeargument name="finterm" value="0">
<cfinvokeargument name="downpay" value="0">
<cfinvokeargument name="cuscost" value="0">
<cfinvokeargument name="paymeth" value="0">
<cfinvokeargument name="cc" value="0">
<cfinvokeargument name="expdt" value="0">
<cfinvokeargument name="ccid" value="0">
<cfinvokeargument name="routing" value="0">
<cfinvokeargument name="banacct" value="0">
<cfinvokeargument name="checking" value="0">
<cfinvokeargument name="fbdt" value="0">
<cfinvokeargument name="promo" value="0">
<cfinvokeargument name="timeofday" value="0">
<cfinvokeargument name="prefmeth" value="0">
<cfinvokeargument name="email" value="0">
</cfinvoke>

Weblogic app server wsdl web service call with SSL Validation error = 16

Weblogic app server wsdl web service call with SSL Validation error = 16
I need to make wsdl web service call in my weblogic app server. The web service is provided by a 3rd party vendor. I keep getting error
Cannot complete the certificate chain: No trusted cert found
Certificate chain received from ws-eq.demo.xxx.com - xx.xxx.xxx.156 was not trusted causing SSL handshake failure
Validation error = 16
From the SSL debug log, I can see 3 verisign hierarchy certs are correctly loaded (see 3 lines in the log message starting with “adding as trusted cert”). But somehow after first handshake, I got error “Cannot complete the certificate chain: No trusted cert found”.
Here is how I load trustStore and keyStore in my java program:
     System.setProperty("javax.net.ssl.trustStore",”cacerts”);
     System.setProperty("javax.net.ssl.trustStorePassword", trustKeyPasswd);
     System.setProperty("javax.net.ssl.trustStoreType","JKS");
System.setProperty("javax.net.ssl.keyStoreType","JKS");
System.setProperty("javax.net.ssl.keyStore", keyStoreName);
     System.setProperty("javax.net.ssl.keyStorePassword",clientCertPwd);      System.setProperty("com.sun.xml.ws.transport.http.client.HttpTransportPipe.dump","true");
Here is how I create cacerts using verisign hierarchy certs (in this order)
1.6.0_29/jre/bin/keytool -import -trustcacerts -keystore cacerts -storepass changeit -file VerisignClass3G5PCA3Root.txt -alias "Verisign Class3 G5P CA3 Root"
1.6.0_29/jre/bin/keytool -import -trustcacerts -keystore cacerts -storepass changeit -file VerisignC3G5IntermediatePrimary.txt -alias "Verisign C3 G5 Intermediate Primary"
1.6.0_29/jre/bin/keytool -import -trustcacerts -keystore cacerts -storepass changeit -file VerisignC3G5IntermediateSecondary.txt -alias "Verisign C3 G5 Intermediate Secondary"
Because my program is a weblogic app server, when I start the program, I have java command line options set as:
-Dweblogic.security.SSL.trustedCAKeyStore=SSLTrust.jks
-Dweblogic.security.SSL.ignoreHostnameVerification=true
-Dweblogic.security.SSL.enforceConstraints=strong
That SSLTrust.jks is the trust certificate from our web server which sits on a different box. In our config.xml file, we also refer to the SSLTrust.jks file when we bring up the weblogic app server.
In addition, we have working logic to use some other wsdl web services from the same vendor on the same SOAP server. In the working web service call flows, we use clientgen to create client stub, and use SSLContext and WLSSLAdapter to load trustStore and keyStore, and then bind the SSLContext and WLSSLAdapter objects to the webSerive client object and make the webservie call. For the new wsdl file, I am told to use wsimport to create client stub. In the client code created, I don’t see any way that I can bind SSLContext and WLSSLAdapter objects to the client object, so I have to load certs by settting system pramaters. Here I attached the the wsdl file.
I have read many articles. It seems as long as I can install the verisign certs correctly to web logic server, I should have fixed the problem. Now the questions are:
1.     Do I create “cacerts” the correct order with right keeltool options?
2.     Since command line option “-Dweblogic.security.SSL.trustedCAKeyStore” is used for web server jks certificate, will that cause any problem for me?
3.     Is it possible to use wsimport to generate client stub that I can bind SSLContext and WLSSLAdapter objects to it?
4.     Do I need to put the “cacerts” to some specific weblogic directory?
---------------------------------wsdl file
<wsdl:definitions name="TokenServices" targetNamespace="http://tempuri.org/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:tns="http://tempuri.org/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:wsa10="http://www.w3.org/2005/08/addressing" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata">
     <wsp:Policy wsu:Id="TokenServices_policy">
          <wsp:ExactlyOne>
               <wsp:All>
                    <sp:TransportBinding xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
                         <wsp:Policy>
                              <sp:TransportToken>
                                   <wsp:Policy>
                                        <sp:HttpsToken RequireClientCertificate="true"/>
                                   </wsp:Policy>
                              </sp:TransportToken>
                              <sp:AlgorithmSuite>
                                   <wsp:Policy>
                                        <sp:Basic256/>
                                   </wsp:Policy>
                              </sp:AlgorithmSuite>
                              <sp:Layout>
                                   <wsp:Policy>
                                        <sp:Strict/>
                                   </wsp:Policy>
                              </sp:Layout>
                         </wsp:Policy>
                    </sp:TransportBinding>
                    <wsaw:UsingAddressing/>
               </wsp:All>
          </wsp:ExactlyOne>
     </wsp:Policy>
     <wsdl:types>
          <xsd:schema targetNamespace="http://tempuri.org/Imports">
               <xsd:import schemaLocation="xsd0.xsd" namespace="http://tempuri.org/"/>
               <xsd:import schemaLocation="xsd1.xsd" namespace="http://schemas.microsoft.com/2003/10/Serialization/"/>
          </xsd:schema>
     </wsdl:types>
     <wsdl:message name="ITokenServices_GetUserToken_InputMessage">
          <wsdl:part name="parameters" element="tns:GetUserToken"/>
     </wsdl:message>
     <wsdl:message name="ITokenServices_GetUserToken_OutputMessage">
          <wsdl:part name="parameters" element="tns:GetUserTokenResponse"/>
     </wsdl:message>
     <wsdl:message name="ITokenServices_GetSSOUserToken_InputMessage">
          <wsdl:part name="parameters" element="tns:GetSSOUserToken"/>
     </wsdl:message>
     <wsdl:message name="ITokenServices_GetSSOUserToken_OutputMessage">
          <wsdl:part name="parameters" element="tns:GetSSOUserTokenResponse"/>
     </wsdl:message>
     <wsdl:portType name="ITokenServices">
          <wsdl:operation name="GetUserToken">
               <wsdl:input wsaw:Action="http://tempuri.org/ITokenServices/GetUserToken" message="tns:ITokenServices_GetUserToken_InputMessage"/>
               <wsdl:output wsaw:Action="http://tempuri.org/ITokenServices/GetUserTokenResponse" message="tns:ITokenServices_GetUserToken_OutputMessage"/>
          </wsdl:operation>
          <wsdl:operation name="GetSSOUserToken">
               <wsdl:input wsaw:Action="http://tempuri.org/ITokenServices/GetSSOUserToken" message="tns:ITokenServices_GetSSOUserToken_InputMessage"/>
               <wsdl:output wsaw:Action="http://tempuri.org/ITokenServices/GetSSOUserTokenResponse" message="tns:ITokenServices_GetSSOUserToken_OutputMessage"/>
          </wsdl:operation>
     </wsdl:portType>
     <wsdl:binding name="TokenServices" type="tns:ITokenServices">
          <wsp:PolicyReference URI="#TokenServices_policy"/>
          <soap12:binding transport="http://schemas.xmlsoap.org/soap/http"/>
          <wsdl:operation name="GetUserToken">
               <soap12:operation soapAction="http://tempuri.org/ITokenServices/GetUserToken" style="document"/>
               <wsdl:input>
                    <soap12:body use="literal"/>
               </wsdl:input>
               <wsdl:output>
                    <soap12:body use="literal"/>
               </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="GetSSOUserToken">
               <soap12:operation soapAction="http://tempuri.org/ITokenServices/GetSSOUserToken" style="document"/>
               <wsdl:input>
                    <soap12:body use="literal"/>
               </wsdl:input>
               <wsdl:output>
                    <soap12:body use="literal"/>
               </wsdl:output>
          </wsdl:operation>
     </wsdl:binding>
     <wsdl:service name="TokenServices">
          <wsdl:port name="TokenServices" binding="tns:TokenServices">
               <soap12:address location="https://ws-eq.demo.i-deal.com/PhxEquity/TokenServices.svc"/>
               <wsa10:EndpointReference>
                    <wsa10:Address>https://ws-eq.demo.xxx.com/PhxEquity/TokenServices.svc</wsa10:Address>
               </wsa10:EndpointReference>
          </wsdl:port>
     </wsdl:service>
</wsdl:definitions>
----------------------------------application log
adding as trusted cert:
Subject: CN=VeriSign Class 3 International Server CA - G3, OU=Terms of use at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
Issuer: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
Algorithm: RSA; Serial number: 0x641be820ce020813f32d4d2d95d67e67
Valid from Sun Feb 07 19:00:00 EST 2010 until Fri Feb 07 18:59:59 EST 2020
adding as trusted cert:
Subject: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
Issuer: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
Algorithm: RSA; Serial number: 0x3c9131cb1ff6d01b0e9ab8d044bf12be
Valid from Sun Jan 28 19:00:00 EST 1996 until Wed Aug 02 19:59:59 EDT 2028
adding as trusted cert:
Subject: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
Issuer: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
Algorithm: RSA; Serial number: 0x250ce8e030612e9f2b89f7054d7cf8fd
Valid from Tue Nov 07 19:00:00 EST 2006 until Sun Nov 07 18:59:59 EST 2021
<Mar 7, 2013 6:59:21 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Ignoring not supported JCE Cipher: SunPKCS11-Solaris version 1.6 for algorithm DESede/CBC/NoPadding>
<Mar 7, 2013 6:59:21 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Will use default Cipher for algorithm DESede>
<Mar 7, 2013 6:59:21 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Using JCE Cipher: SunJCE version 1.6 for algorithm RSA/ECB/NoPadding>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLSetup: loading trusted CA certificates>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Filtering JSSE SSLSocket>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.addContext(ctx): 28395435>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLSocket will be Muxing>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write HANDSHAKE, offset = 0, length = 115>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <25779276 SSL3/TLS MAC>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <25779276 received HANDSHAKE>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: ServerHello>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: Certificate>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Cannot complete the certificate chain: No trusted cert found>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 0 in the chain: Serial number: 2400410601231772600606506698552332774
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
Not Valid Before:Tue Dec 18 19:00:00 EST 2012
Not Valid After:Wed Jan 07 18:59:59 EST 2015
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 1 in the chain: Serial number: 133067699711757643302127248541276864103
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Not Valid Before:Sun Feb 07 19:00:00 EST 2010
Not Valid After:Fri Feb 07 18:59:59 EST 2020
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <validationCallback: validateErr = 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[0] = Serial number: 2400410601231772600606506698552332774
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
Not Valid Before:Tue Dec 18 19:00:00 EST 2012
Not Valid After:Wed Jan 07 18:59:59 EST 2015
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[1] = Serial number: 133067699711757643302127248541276864103
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Not Valid Before:Sun Feb 07 19:00:00 EST 2010
Not Valid After:Fri Feb 07 18:59:59 EST 2020
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <weblogic user specified trustmanager validation status 16>
<Mar 7, 2013 6:59:22 PM EST> <Warning> <Security> <BEA-090477> <Certificate chain received from ws-eq.demo.xxx.com - xx.xxx.xxx.156 was not trusted causing SSL handshake failure.>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validation error = 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Certificate chain is untrusted>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLTrustValidator returns: 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Trust status (16): CERT_CHAIN_UNTRUSTED>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <NEW ALERT with Severity: FATAL, Type: 42
java.lang.Exception: New alert stack
     at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
     at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
     at com.certicom.tls.record.handshake.ClientStateReceivedServerHello.handle(Unknown Source)
     at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown Source)
     at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown Source)
     at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
     at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
     at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
     at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
     at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
     at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
     at com.certicom.tls.record.WriteHandler.write(Unknown Source)
     at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
     at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
     at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
     at java.io.FilterOutputStream.flush(FilterOutputStream.java:123)
     at weblogic.net.http.HttpURLConnection.writeRequests(HttpURLConnection.java:154)
     at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:358)
     at weblogic.net.http.SOAPHttpsURLConnection.getInputStream(SOAPHttpsURLConnection.java:37)
     at weblogic.wsee.util.is.InputSourceUtil.loadURL(InputSourceUtil.java:100)
     at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:118)
     at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)
     at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)
     at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:305)
     at weblogic.wsee.jaxws.spi.WLSProvider.readWSDL(WLSProvider.java:296)
     at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:77)
     at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:62)
     at javax.xml.ws.Service.<init>(Service.java:56)
     at ideal.ws2j.eqtoken.TokenServices.<init>(TokenServices.java:64)
     at com.citi.ilrouter.util.IpreoEQSSOClient.invokeRpcPortalToken(IpreoEQSSOClient.java:165)
     at com.citi.ilrouter.servlets.T3LinkServlet.doPost(T3LinkServlet.java:168)
     at com.citi.ilrouter.servlets.T3LinkServlet.doGet(T3LinkServlet.java:206)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(Unknown Source)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(Unknown Source)
     at weblogic.servlet.internal.WebAppServletContext.execute(Unknown Source)
     at weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write ALERT, offset = 0, length = 2>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <close(): 6457753>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <close(): 6457753>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.removeContext(ctx): 22803607>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Filtering JSSE SSLSocket>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.addContext(ctx): 14640403>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLSocket will be Muxing>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write HANDSHAKE, offset = 0, length = 115>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <23376797 SSL3/TLS MAC>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <23376797 received HANDSHAKE>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: ServerHello>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: Certificate>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Cannot complete the certificate chain: No trusted cert found>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 0 in the chain: Serial number: 2400410601231772600606506698552332774
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
Not Valid Before:Tue Dec 18 19:00:00 EST 2012
Not Valid After:Wed Jan 07 18:59:59 EST 2015
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 1 in the chain: Serial number: 133067699711757643302127248541276864103
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Not Valid Before:Sun Feb 07 19:00:00 EST 2010
Not Valid After:Fri Feb 07 18:59:59 EST 2020
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <validationCallback: validateErr = 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[0] = Serial number: 2400410601231772600606506698552332774
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
Not Valid Before:Tue Dec 18 19:00:00 EST 2012
Not Valid After:Wed Jan 07 18:59:59 EST 2015
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[1] = Serial number: 133067699711757643302127248541276864103
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Not Valid Before:Sun Feb 07 19:00:00 EST 2010
Not Valid After:Fri Feb 07 18:59:59 EST 2020
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <weblogic user specified trustmanager validation status 16>
<Mar 7, 2013 6:59:22 PM EST> <Warning> <Security> <BEA-090477> <Certificate chain received from ws-eq.demo.xxx.com - 12.29.210.156 was not trusted causing SSL handshake failure.>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validation error = 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Certificate chain is untrusted>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLTrustValidator returns: 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Trust status (16): CERT_CHAIN_UNTRUSTED>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <NEW ALERT with Severity: FATAL, Type: 42
java.lang.Exception: New alert stack
     at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
     at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
     at com.certicom.tls.record.handshake.ClientStateReceivedServerHello.handle(Unknown Source)
     at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown Source)
     at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown Source)
     at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
     at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
     at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
     at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
     at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
     at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
     at com.certicom.tls.record.WriteHandler.write(Unknown Source)
     at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
     at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
     at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
     at java.io.FilterOutputStream.flush(FilterOutputStream.java:123)
     at weblogic.net.http.HttpURLConnection.writeRequests(HttpURLConnection.java:154)
     at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:358)
     at weblogic.net.http.SOAPHttpsURLConnection.getInputStream(SOAPHttpsURLConnection.java:37)
     at weblogic.wsee.util.is.InputSourceUtil.loadURL(InputSourceUtil.java:100)
     at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:118)
     at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)
     at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)
     at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:305)
     at weblogic.wsee.jaxws.spi.WLSProvider.readWSDL(WLSProvider.java:296)
     at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:77)
     at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:62)
     at javax.xml.ws.Service.<init>(Service.java:56)
     at ideal.ws2j.eqtoken.TokenServices.<init>(TokenServices.java:64)
     at com.citi.ilrouter.util.IpreoEQSSOClient.invokeRpcPortalToken(IpreoEQSSOClient.java:165)
     at com.citi.ilrouter.servlets.T3LinkServlet.doPost(T3LinkServlet.java:168)
     at com.citi.ilrouter.servlets.T3LinkServlet.doGet(T3LinkServlet.java:206)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(Unknown Source)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(Unknown Source)
     at weblogic.servlet.internal.WebAppServletContext.execute(Unknown Source)
     at weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write ALERT, offset = 0, length = 2>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <close(): 16189141>

I received a workaround by an internal message.
The how to guide is :
-Download the wsdl file (with bindings, not the one from ESR)
-Correct it in order that the schema corresponds to the answer (remove minOccurs or other things like this)
-Deploy the wsdl file on you a server (java web project for exemple). you can deploy on your local
-Create a new logicial destination that point to the wsdl file modified
-Change the metadata destination in your web dynpro project for the corresponding model and keep the execution desitnation as before.
Then the received data is check by the metadata logical destination but the data is retrieved from the correct server.

Infopath 2013 SOAP Web Service Data Connection - Error: The file is not a valid XML file

Here are the steps to replicate the issue I’m having when adding lists.asmx or any other SharePoint web service in InfoPath 2013. This web service opens fine in the browser from my desktop. My account is a farm administrator and is added to the
web application’s User Policy. I can use these services just fine using Nintex 2013 Workflow.
Open InfoPath Designer 2013.
Select Blank Form and click Design Form button.
Click “Data” tab.
Click “From Web Service” and select “From SOAP Web Service”
Enter https://mysiteurl.com/_vti_bin/lists.asmx?WSDL for the web service definition.
Click Next.
Windows Security window pops up.
Enter a credential. I tried both my account and the farm account. My account is a farm admin and is added to the web application’s User Policy with Full Control.
Click OK. It prompts for credential multiple times.
I get below this error messages:
Sorry, we couldn't open https://mysiteurl.com/_vti_bin/lists.asmx?WSDL
InfoPath cannot find or cannot access the specified Web Service description.
The file is not a valid XML file.
Not enough storage is available to process this command.
We have a project that is in need of these services using InfoPath so any help is greatly appreciated.

Hi Brian_TX,
For your issue, try to the following methods:
Change your service binding in web.config to:binding="basicHttpBinding". It seems in VS it defaults to wsHttpBinding.
Replace all instances of "parameters" from the web service wsdl with the name "parameter"
There are some similar articles about the issue, you can have a look at them:
http://www.infopathdev.com/forums/t/23239.aspx
https://social.msdn.microsoft.com/Forums/office/en-US/621929c3-0335-40af-8332-5a0b430901ab/problems-with-infopath-web-service-connection?forum=sharepointcustomizationprevious
https://social.msdn.microsoft.com/Forums/en-US/5fa5eca8-f8d7-4a2e-81ba-a3b4bdcfe5af/infopath-cannot-find-or-cannot-access-the-specified-web-service-description?forum=sharepointcustomizationlegacy
Best Regards
Lisa Chen
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]

Validation error while creating Web Service Proxy.

Hi,
I'm trying to create Web Service Proxy. But I'm stuck with a Validation error
model error: type
+"{http://xmlns.oracle.com/2001/XMLSchema/DOM}+
+org.w3c.dom.Document" not found.+
I'm using "Create Web Service Proxy" wizard. There are 6 steps in creating proxy through JDev. wizard.
First step itself displaying the above validation error when I click on "Next" button.
Few points
We have created web service using "oracle.j2ee.ws.StatelessJavaRpcWebService" servlet
Thanks in advance.
-Sukumar

Hi,
It might be that the .net service which you have is not WS-I compliant. Can you first run WS-I Analyzer on the wsdl to see it the test passes.
Thanks,
Vishal

Web Dynpro Import Web Service Model - not a valid NCName

Hi people,
We are having a problem while importing a WSDL as an Adaptive Web Service Model in Web Dynpro (CE 7.2 SP03).
The error is the following:
"Definition of qualified base /schema/element[5]/complexType/sequence/element[4] is not correct. The value of property is not a valid NCName."
We tried importing the same WSDL in other tools (XML Spy and SOAP UI). With these tools it could be read without errors and were able to successfully call the service.
The point is, why the import fails in Web Dynpro if the WSDL can be read in other tools ? Can we do something in WD to import the WSDL that is supposed to be "not correct" ?
Thanks in advance for your comments,
Daniel

Hi Pranav,
I was facing this issue sometime back and i figured out that the ABAP proxy namespace in my case had a '/' in it, because of which the internal name of the service had a '/' character too.
And this was unacceptable for the endpoint binding name in my case.
Since it is occuring for you in case of the service name (i figured it out from attribute definations/services@name), check if the proxy name have a special character like '/'.
Regards,
Vivek

How do I create a Username Validator for a web service.

I'm trying to figure out how to create a Username validator. I've followed the WSIT documentation and created their calculator service. The service works when I leave security turned off, so I know I'm good up to this point. I right click on the Web Service in Netbeans, and select Edit Web Services Attributes which pops up the Quality of Service window. I click Secure Service to enable security and select Message Authentication over SSL. I then deselect Use Development Defaults. The Validators button never enables; it stays disabled and greyed out. I've trying picking all different kinds of Security Mechanisms and changing their configuration but I can never get the Validators button to enable. I've also noticed a problem where I select Message Authentication over SSL and deselect Use Development Defaults and then click OK to close the Quality Of Service window. If I then go back to the Quality Of Service window Use Development Defaults is turned back on. The only way I have found around this is to keep turning it off, closing the window and then opening the window again. I sometimes have to screw around with the configuration on the Security Mechanism to be able to keep the Use Development Defaults checkbox unchecked.
My question is if anyone else has had this problem? How do you go about creating a Username Validator on a Web Service? I know WSIT is pretty new and the IDE wizards seem very buggy. I wouldn't mind creating the Validator by hand and mapping it in, I just can not figure out how to do it.

I read the examples you referred to. I currently use this method in my non WSIT code, I was trying to figure out how you do the same thing with WSIT (or the equivalent). I've continued playing around with the code, and I found a few settings changes to get my JAX-WS 2.1 SOAP Server to talk with my .Net 3.5 SOAP client. I'm going to stick with the client I have now until I feel it's necessary to switch to WSIT.

MBAM 2.5 Web Applications installation - "Web service application pool account is not valid"

Hi,
I've created a Server 2012R2 installation to install MBAM 2.5. When installing the Web Applications I keep getting "The web service application pool account is not valid".
The account I am using is a standard domain account with admin rights on the Server and I've also set the SPN (both netbios and FQDN) and Delegation.
This account is also a member of the group that is defined as RW of the SQL databases (which were setup without any problem and are on a separate Server 2008R2, SQL 2008R2 installation.
I am also getting an error with the SSRS URL , stating "SQL Server Reporting Services URL that points to the MBAM reports is not valid", despite being able to browse to the http://[FQDN]/ReportServer_MBAM location.
Thanks.

I got this kind of error when I revert back my virtual machine a lot to my previous checkpoints. I hope this can't be an issue for you.
Make sure the application pool account must have the following login roles on the SQL server and have following rights on the reporting instance:-
Required SQL Server permissions
The user responsible for installing MBAM database and reporting feature must have the local administrator privileges and the following log in permission:-
SQL Server instance login server roles:
dbcreator
processadmin
SQL Server Reporting Services instance rights:
Create Folder
Publish Reports
SQL Server Database Engine Services: SQL Server Database Engine Services must be installed and running during MBAM Server installation.
SQL Server Reporting Services (SSRS): SSRS must be installed and running during the MBAM Server installation. Configure SSRS in "native" mode and not in "SharePoint" mode.
Gaurav Ranjan

Validation Failed. Creation Web Service Proxy

Hi, all
I've got a problem with JDeveloper 10.1.3 when I try to create a web serviceproxy using the wizard.
My service class is next,
package swa;
import java.awt.Graphics;
import java.awt.Image;
import java.awt.Toolkit;
import java.awt.color.ColorSpace;
import java.awt.geom.AffineTransform;
import java.awt.image.AffineTransformOp;
import java.awt.image.BufferedImage;
import java.awt.image.ColorConvertOp;
import java.awt.image.RescaleOp;
import javax.xml.soap.AttachmentPart;
import javax.xml.soap.MessageFactory;
import javax.xml.soap.SOAPException;
import javax.xml.soap.SOAPMessage;
public class ImgToolbox {
public final static int FLIP_VERTICAL = 0;
public final static int FLIP_HORIZONTAL = 1;
public final static int FLIP_VERTICAL_HORIZONTAL = 2;
public AttachmentPart toGray(AttachmentPart imagen){
AttachmentPart apRetorno = null;
try{
Image image = (Image)imagen.getContent();
BufferedImage originalImage = new BufferedImage(image.getWidth(null), image.getHeight(null), BufferedImage.TYPE_INT_RGB);
ColorSpace cs = ColorSpace.getInstance(ColorSpace.CS_GRAY);
ColorConvertOp op = new ColorConvertOp(cs, null);
BufferedImage grayImage = op.filter(originalImage, null);
// Creación del AttachmentPart con la nueva imagen
MessageFactory mf = MessageFactory.newInstance();
SOAPMessage message = mf.createMessage();
apRetorno = message.createAttachmentPart();
apRetorno.setContent(Toolkit.getDefaultToolkit().createImage(grayImage.getSource()),"image/jpeg");
} catch(SOAPException e){
System.out.println("Error, en el mensaje SOAP.");
return apRetorno;
public AttachmentPart flip(AttachmentPart ap, int tipo){
AttachmentPart apRetorno = null;
try{
Image image = (Image)ap.getContent();
BufferedImage originalImage = new BufferedImage(image.getWidth(null), image.getHeight(null), BufferedImage.TYPE_INT_RGB);
AffineTransform tx = null;
AffineTransformOp op = null;
switch(tipo){
case FLIP_VERTICAL : {
tx = AffineTransform.getScaleInstance(1, -1);
tx.translate(0, -image.getHeight(null));
break;
case FLIP_HORIZONTAL : {
tx = AffineTransform.getScaleInstance(-1, 1);
tx.translate(-image.getWidth(null), 0);
break;
case FLIP_VERTICAL_HORIZONTAL : {
tx = AffineTransform.getScaleInstance(-1, -1);
tx.translate(-image.getWidth(null), -image.getHeight(null));
break;
op = new AffineTransformOp(tx, AffineTransformOp.TYPE_NEAREST_NEIGHBOR);
BufferedImage flipImage = op.filter(originalImage, null);
// Creación del AttachmentPart con la nueva imagen
MessageFactory mf = MessageFactory.newInstance();
SOAPMessage message = mf.createMessage();
apRetorno = message.createAttachmentPart();
apRetorno.setContent(Toolkit.getDefaultToolkit().createImage(flipImage.getSource()),"image/jpeg");
} catch (SOAPException e) {
System.out.println("Error, en el mensaje SOAP.");
return apRetorno;
public AttachmentPart resize(AttachmentPart img,float escala){
AttachmentPart apRetorno = null;
try{
Image image = (Image)img.getContent();
BufferedImage originalImage = new BufferedImage(image.getWidth(null), image.getHeight(null), BufferedImage.TYPE_INT_RGB);
// Se rellena la BufferedImage con la imagen original
Graphics g = originalImage.createGraphics();
g.drawImage(image, 0, 0, null);
g.dispose();
// Modificación de la imagen original
RescaleOp op = new RescaleOp(escala, 0, null);
BufferedImage tempImage = op.filter(originalImage, null);
// Creación del AttachmentPart con la nueva imagen
MessageFactory mf = MessageFactory.newInstance();
SOAPMessage message = mf.createMessage();
apRetorno = message.createAttachmentPart();
apRetorno.setContent(Toolkit.getDefaultToolkit().createImage(tempImage.getSource()),"image/jpeg");
} catch (SOAPException e) {
System.out.println("Error, en el mensaje SOAP.");
return apRetorno;
the wizard creates a JAX-RPC web service without problems from this class. However, if I click on "Regenerate Web Service from WSDL..." the method fails and throws a exception. The trace is next :
java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
     at java.util.ArrayList.RangeCheck(ArrayList.java:547)
     at java.util.ArrayList.get(ArrayList.java:322)
     at oracle.jdeveloper.webservices.model.SOAPBinding.<init>(SOAPBinding.java:243)
     at oracle.jdeveloper.webservices.model.Binding.create(Binding.java:668)
     at oracle.jdeveloper.webservices.model.WebService.createServiceFromWSDL(WebService.java:2275)
     at oracle.jdeveloper.webservices.model.WebService.createServiceFromWSDL(WebService.java:2117)
     at oracle.jdeveloper.webservices.model.java.JavaWebService.saveEditTopDown(JavaWebService.java:1704)
     at oracle.jdevimpl.webservices.WebServicesAddin$2.run(WebServicesAddin.java:2261)
     at oracle.jdeveloper.webservices.model.GeneratorUI$GeneratorAction.run(GeneratorUI.java:446)
     at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:551)
     at java.lang.Thread.run(Thread.java:595)
WSDL FILE GENERATED BY THE WIZARD
<definitions
name="ImgToolboxWS"
targetNamespace="http://swa/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://swa/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:tns0="http://swa/types/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns1="http://ws-i.org/profiles/basic/1.1/xsd"
>
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://ws-i.org/profiles/basic/1.1/xsd"
elementFormDefault="qualified" xmlns:tns="http://ws-i.org/profiles/basic/1.1/xsd">
<import namespace="http://swa/types/"/>
<simpleType name="swaRef">
<restriction base="xsd:anyURI"/>
</simpleType>
</schema>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://swa/types/"
elementFormDefault="qualified" xmlns:tns="http://swa/types/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soap12-enc="http://www.w3.org/2003/05/soap-encoding"
xmlns:ns1="http://ws-i.org/profiles/basic/1.1/xsd">
<import namespace="http://ws-i.org/profiles/basic/1.1/xsd"/>
<complexType name="flip">
<sequence>
<element name="ap" type="ns1:swaRef" nillable="true"/>
<element name="tipo" type="int"/>
</sequence>
</complexType>
<complexType name="flipResponse">
<sequence>
<element name="result" type="ns1:swaRef" nillable="true"/>
</sequence>
</complexType>
<complexType name="resize">
<sequence>
<element name="img" type="ns1:swaRef" nillable="true"/>
</sequence>
</complexType>
<complexType name="resizeResponse">
<sequence>
<element name="result" type="ns1:swaRef" nillable="true"/>
</sequence>
</complexType>
<complexType name="toGray">
<sequence>
<element name="imagen" type="ns1:swaRef" nillable="true"/>
</sequence>
</complexType>
<complexType name="toGrayResponse">
<sequence>
<element name="result" type="ns1:swaRef" nillable="true"/>
</sequence>
</complexType>
<element name="flipElement" type="tns:flip"/>
<element name="flipResponseElement" type="tns:flipResponse"/>
<element name="resizeElement" type="tns:resize"/>
<element name="resizeResponseElement" type="tns:resizeResponse"/>
<element name="toGrayElement" type="tns:toGray"/>
<element name="toGrayResponseElement" type="tns:toGrayResponse"/>
</schema>
</types>
<message name="ImgToolboxWS_flip">
<part name="parameters" element="tns0:flipElement"/>
</message>
<message name="ImgToolboxWS_flipResponse">
<part name="parameters" element="tns0:flipResponseElement"/>
</message>
<message name="ImgToolboxWS_resize">
<part name="parameters" element="tns0:resizeElement"/>
</message>
<message name="ImgToolboxWS_resizeResponse">
<part name="parameters" element="tns0:resizeResponseElement"/>
</message>
<message name="ImgToolboxWS_toGray">
<part name="parameters" element="tns0:toGrayElement"/>
</message>
<message name="ImgToolboxWS_toGrayResponse">
<part name="parameters" element="tns0:toGrayResponseElement"/>
</message>
<portType name="ImgToolboxWS">
<operation name="flip">
<input message="tns:ImgToolboxWS_flip"/>
<output message="tns:ImgToolboxWS_flipResponse"/>
</operation>
<operation name="resize">
<input message="tns:ImgToolboxWS_resize"/>
<output message="tns:ImgToolboxWS_resizeResponse"/>
</operation>
<operation name="toGray">
<input message="tns:ImgToolboxWS_toGray"/>
<output message="tns:ImgToolboxWS_toGrayResponse"/>
</operation>
</portType>
<binding name="ImgToolboxWSSoap12Http" type="tns:ImgToolboxWS">
<soap12:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="flip">
<soap12:operation soapAction="http://swa//flip" soapActionRequired="false"/>
<input>
<mime:multipartRelated>
<mime:part>
<soap12:body use="literal" parts="parameters"/>
</mime:part>
</mime:multipartRelated>
</input>
<output>
<mime:multipartRelated>
<mime:part>
<soap12:body use="literal" parts="parameters"/>
</mime:part>
</mime:multipartRelated>
</output>
</operation>
<operation name="resize">
<soap12:operation soapAction="http://swa//resize" soapActionRequired="false"/>
<input>
<mime:multipartRelated>
<mime:part>
<soap12:body use="literal" parts="parameters"/>
</mime:part>
</mime:multipartRelated>
</input>
<output>
<mime:multipartRelated>
<mime:part>
<soap12:body use="literal" parts="parameters"/>
</mime:part>
</mime:multipartRelated>
</output>
</operation>
<operation name="toGray">
<soap12:operation soapAction="http://swa//toGray" soapActionRequired="false"/>
<input>
<mime:multipartRelated>
<mime:part>
<soap12:body use="literal" parts="parameters"/>
</mime:part>
</mime:multipartRelated>
</input>
<output>
<mime:multipartRelated>
<mime:part>
<soap12:body use="literal" parts="parameters"/>
</mime:part>
</mime:multipartRelated>
</output>
</operation>
</binding>
<service name="ImgToolboxWS">
<port name="ImgToolboxWSSoap12HttpPort" binding="tns:ImgToolboxWSSoap12Http">
<soap12:address location="http://192.168.0.6:8888/Capitulo3-SwA-context-root/ImgToolboxWSSoap12HttpPort"/>
</port>
</service>
</definitions>
If I only expose the toGray method as a Web Service all works fine. Any combinatio with other methods won't work. It's very strange.
When I try to create a proxy using the wizard JDeveloper shows me next error message :
Validation Failed
...wsdl file does not contain sufficient information to create a proxy. At least one port type and a binding of the are required.
Any reply will be greatly appreciated.
Best regards.

I am getting this error by generating a web service from pl/sql procedure. Just one package, just one procedure. Error stack:
java.lang.NullPointerException
     at oracle.jdevimpl.webservices.generator.WrapperClassGenerator.generate(WrapperClassGenerator.java:262)
     at oracle.jdevimpl.webservices.generator.SPWebServiceGenerator$1.run(SPWebServiceGenerator.java:285)
     at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:551)
     at java.lang.Thread.run(Thread.java:595)
The pl/sql package header looks like this:
CREATE OR REPLACE package ADMIN.etis_autent as
procedure autent(
     ps_kasutajatunnus in varchar2,
     ps_parool in varchar2,
     ps_isikukood out varchar2,
     ps_eesnimi out varchar2,
     ps_perekonnanimi out varchar2
end etis_autent;
/

Reporting Server Web Service- (FileShare) CreateSubscription: The value of parameter 'ExtensionSettings' is not valid

I've tried to create a subscription by Web Service api calling the method CreateSubscription and I've an error:
> The value of parameter 'ExtensionSettings' is not valid. --->
> Microsoft.ReportingServices.Diagnostics.Utilities.InvalidParameterException:
> The value of parameter 'ExtensionSettings' is not valid.
Below is my code:
ReportingService2010 m_RptManager = new ReportingService2010(); m_RptManager.Url = "<path>/ReportService2010.asmx"; m_RptManager.Credentials = GetCredential(); string filename = Path.GetFileName(m_FileName); string path = Path.GetDirectoryName(m_FileName); ParameterValue[] extensionParams = new ParameterValue[7]; for (int i = 0; i < extensionParams.Length; i++) extensionParams[i] = new ParameterValue(); extensionParams[0].Name = "FILENAME"; extensionParams[0].Value = filename; extensionParams[1].Name = "FILEEXTN"; extensionParams[1].Value = "False"; extensionParams[2].Name = "PATH"; extensionParams[2].Value = path; extensionParams[3].Name = "RENDER_FORMAT"; extensionParams[3].Value = m_Format; extensionParams[4].Name = "WRITEMODE"; extensionParams[4].Value = "Overwrite"; extensionParams[5].Name = "USERNAME"; extensionParams[5].Value = m_UserName; extensionParams[6].Name = "PASSWORD"; extensionParams[6].Value = m_Password; ExtensionSettings extensionSettings = new ExtensionSettings(); extensionSettings.Extension = "Report Server FileShare"; extensionSettings.ParameterValues = extensionParams; MinuteRecurrence pattern = new MinuteRecurrence(); pattern.MinutesInterval = 1; ScheduleDefinition schedule = new ScheduleDefinition(); schedule.StartDateTime = DateTime.Now; schedule.EndDateSpecified = false; schedule.Item = pattern; XmlSerializer serializer = new XmlSerializer(typeof(ScheduleDefinition)); string dateMatch; using (StringWriter sw = new StringWriter()) { serializer.Serialize(sw, schedule); dateMatch = sw.ToString(); } string reportPath = "MyReport"; string eventType = "TimedSubscription"; string description = "description"; m_RptManager.CreateSubscription(reportPath, extensionSettings, description, eventType, matchData, GetReportParameters(reportPath));
Where have I wrong?

Thank for reply, I checked my parameter and I seem that (maybe) is ok below is my parameters, do you see anything of wrong?
<?xml version="1.0" encoding="utf-16"?>
<ExtensionSettings xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Extension xmlns="http://schemas.microsoft.com/sqlserver/reporting/2010/03/01/ReportServer">Report Server FileShare</Extension>
<ParameterValues xmlns="http://schemas.microsoft.com/sqlserver/reporting/2010/03/01/ReportServer">
<ParameterValue>
<Name xmlns="http://schemas.microsoft.com/sqlserver/2005/06/30/reporting/reportingservices">FILENAME</Name>
<Value xmlns="http://schemas.microsoft.com/sqlserver/2005/06/30/reporting/reportingservices">pippo.xls</Value>
</ParameterValue>
<ParameterValue>
<Name xmlns="http://schemas.microsoft.com/sqlserver/2005/06/30/reporting/reportingservices">FILEEXTN</Name>
<Value xmlns="http://schemas.microsoft.com/sqlserver/2005/06/30/reporting/reportingservices">False</Value>
</ParameterValue>
<ParameterValue>
<Name xmlns="http://schemas.microsoft.com/sqlserver/2005/06/30/reporting/reportingservices">PATH</Name>
<Value xmlns="http://schemas.microsoft.com/sqlserver/2005/06/30/reporting/reportingservices">\\10.4.44.253\D$\Data Applications\DBP\Output\DOMAIN\User\14</Value>
</ParameterValue>
<ParameterValue>
<Name xmlns="http://schemas.microsoft.com/sqlserver/2005/06/30/reporting/reportingservices">RENDER_FORMAT</Name>
<Value xmlns="http://schemas.microsoft.com/sqlserver/2005/06/30/reporting/reportingservices">EXCEL</Value>
</ParameterValue>
<ParameterValue>
<Name xmlns="http://schemas.microsoft.com/sqlserver/2005/06/30/reporting/reportingservices">WRITEMODE</Name>
<Value xmlns="http://schemas.microsoft.com/sqlserver/2005/06/30/reporting/reportingservices">Overwrite</Value>
</ParameterValue>
<ParameterValue>
<Name xmlns="http://schemas.microsoft.com/sqlserver/2005/06/30/reporting/reportingservices">USERNAME</Name>
<Value xmlns="http://schemas.microsoft.com/sqlserver/2005/06/30/reporting/reportingservices">domain\user</Value>
</ParameterValue>
<ParameterValue>
<Name xmlns="http://schemas.microsoft.com/sqlserver/2005/06/30/reporting/reportingservices">PASSWORD</Name>
<Value xmlns="http://schemas.microsoft.com/sqlserver/2005/06/30/reporting/reportingservices">xxxxxx</Value>
</ParameterValue>
</ParameterValues>
</ExtensionSettings>

Web Service XML Input Arguments Schema Validation

I'm new to web services, but we are currently implementing a number of Web Services that all take as arguments a single parameter which is an XMLBean, which has been generated by a XML Schema.
What I find surprising is that when I submit a SOAP message to the Web Service (through the http Web Service Tester inside eclipse), I can send any valid XML without getting a SOAP fault. Is there a way on the Web Service that I want the XML submitted to be validated against the XML Schema for that parameter?
Bit surprised I have to implement my own input argument validation, and there doesn't appear to be a standard way to do this. I must be missing soemthing surely? Why else would the Schema be in the WSDL?
Cheers
John

I'm new to web services, but we are currently
implementing a number of Web Services that all take
as arguments a single parameter which is an XMLBean,
which has been generated by a XML Schema.
What I find surprising is that when I submit a SOAP
message to the Web Service (through the http Web
Service Tester inside eclipse), I can send any valid
XML without getting a SOAP fault. Is there a way on
the Web Service that I want the XML submitted to be
validated against the XML Schema for that parameter?
Bit surprised I have to implement my own input
argument validation, and there doesn't appear to be a
standard way to do this. I must be missing soemthing
surely? Why else would the Schema be in the WSDL?
Cheers
JohnHas anyone found an answer to this, we have the same issue?

Web Service in EnterpriseOne: Credentials could not be validated

I am trying to run one of the lab exercises to test the address book web service. While testing this web service; I am getting the following error in the SOAP response XML when nothing is passed in the WS-Security :
<faultstring>Internal Server Error (Caught exception while handling request: java.lang.RuntimeException: Credentials could not be validated from message or from configuration file.)</faultstring>
Whenever I pass in my user/id password; I get the following message in the response XML:
<faultcode>env:MustUnderstand</faultcode>
<faultstring>SOAP must understand error: {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security</faultstring>
I am new to web services and am unsure of what setup is missing in or outside of EnterpriseOne. I will really appreciate if someone could shed some light on this.

It's worth checking that security has been enabled for the web service. I seem to remember that I had to do this when I got the same error a while back.
In OAS, log onto the Enterprise Manager on your OAS server and select the OC4J instance that contains the Business Services Server. Click on the Web Services tab and then select the Web Service that you're trying to test (eg: RI_AddressBookManagerHttpPort). Click on the Administration tab and if the Security feature is not enabled then press the Enable/Disable Features button, move Security across to the Enabled Features pane and press OK.
Back on the Administration tab, select the Edit Configuration icon for the Security Feature, and press the Inbound Policies button. Ensure that the Use Username/Password Authentication checkbox is selected. The Password Type should be Plain Text.
You shouldn't need to bounce the OC4J instance.
I'm not sure about Websphere without doing more research, but I imagine there must be a similar option.
Good luck,
Dave

WSDL Validation Failed (Web Services)

I want to create a Web Service-Based Application in LabVIEW and I'm
trying to go through the steps in the tutorial
http://zone.ni.com/devzone/cda/tut/p/id/4728.
I tried the following web services, but I always get the same error.
http://coeservice.en.kku.ac.th:8080/TemperatureConvertor/TemperatureConvertorService?WSDL
http://www.ecubicle.net/iptocountry.asmx?wsdl
Error:
WSDL Validation Failed.
Validation failed. The URL is not formatted correctly and should be in the folowing form: http://localhost/test/good.asmx?WSDL
I defined a proxy server with authentication. Without doing, that I get another error:
Validation Failed.
Possible Reasons are:
1. The URL does not exist or the WSDL is bad.
2. Authentication is not correct.
3. Proxy information is not correct.
So it seems that the proxy information is ok. But the web service I want to access isn't located on the localhost - I want to access a service in the internet. Can somebody give me a hint? I already tried to change some settings of the LabVIEW webserver. But it didn't help anything.
David
Solved!
Go to Solution.

In my browser I don't need to define a proxy (the proxy is detected automatically). But I still tried to define a proxy for the webservice - I got the informations from our IT department.
I attached 3 screenshots of the webservice wizard with the error message...
Attachments:
ImportWebService1.gif ‏19 KB
ImportWebService2.gif ‏22 KB
ImportWebService3.gif ‏6 KB

Validating Web Services

Similar Messages

Maybe you are looking for