We've been having trouble with the sandbox wsdl so as we're close to
going live I figured I'd check that we will, if neccessary, be able to
rebuild our client against the live service wsdl. It appears not. I
tried using both the Axis tool in Eclipse and the underlying wsdl2java
utility in cxf from the command line. Heres the result:
C:\Documents and Settings\haggiscode>wsdl2java -client -d C:\temptest
\googleclient h
ttps://www.google.com/api/adsense/v3/AccountService?wsdl 07-Oct-2009 10:12:55 org.apache.cxf.transport.https.SSLUtils
getCiphersuites
INFO: The cipher suites have not been configured, falling back to
cipher suite f
ilters.
07-Oct-2009 10:12:55 org.apache.cxf.transport.https.SSLUtils
getCiphersuites
INFO: The cipher suite filters have not been configured, falling back
to default
filters.
07-Oct-2009 10:12:55 org.apache.cxf.transport.https.SSLUtils
getCiphersFromList
INFO: The cipher suites have been set to SSL_RSA_WITH_RC4_128_MD5,
SSL_RSA_WITH_
RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA,
TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS
_DHE_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA,
SSL_DHE_RSA_WITH_3
DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA,
SSL_RSA_WITH_DES_CBC_SHA, SS
L_DHE_RSA_WITH_DES_CBC_SHA, SSL_DHE_DSS_WITH_DES_CBC_SHA,
SSL_RSA_EXPORT_WITH_RC
4_40_MD5, SSL_RSA_EXPORT_WITH_DES40_CBC_SHA,
SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_S
HA, SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA, TLS_KRB5_WITH_RC4_128_SHA,
TLS_KRB5_W
ITH_RC4_128_MD5, TLS_KRB5_WITH_3DES_EDE_CBC_SHA,
TLS_KRB5_WITH_3DES_EDE_CBC_MD5,
TLS_KRB5_WITH_DES_CBC_SHA, TLS_KRB5_WITH_DES_CBC_MD5,
TLS_KRB5_EXPORT_WITH_RC4_
40_SHA, TLS_KRB5_EXPORT_WITH_RC4_40_MD5,
TLS_KRB5_EXPORT_WITH_DES_CBC_40_SHA, TL
S_KRB5_EXPORT_WITH_DES_CBC_40_MD5.
WSDLToJava Error: Thrown by JAXB : undefined simple or complex type
'xs:Exceptio
n'
Eclipse winged about a problem with associateAccountFault which I'm
guessing is related - summary output here:
IWAB0399E Error in generating Java from WSDL: java.io.IOException:
ERROR: Missing <soap:fault> element inFault "associateAccountFault" in
operation "associateAccountFault", in binding associateAccount
java.io.IOException: ERROR: Missing <soap:fault> element inFault
"associateAccountFault" in operation "associateAccountFault", in
binding associateAccount
at
Any suggestions how we get round this? or are you replacing the wsdl?
Are you using Axis2's WSDL2Java? There are some interoperability
issues between the two, and since our backend relies on Axis2, we
suggest you use that as well (specifically v1.4). The command to
generate for all ports (binding styles) should be as follows:
To generate for a specific binding style (say, SOAP 1.1), use:
./wsdl2java.sh -p com.google.api.adsense.v3.${SERVICE_NAME} -pn v3/$
{SERVICE_NAME}SOAP11port_https -uri https://google.com/api/adsense/v3/${SERVICE_NAME}?wsdl
Cheers,
Wes
On Oct 7, 2:29 am, HaggisCode <hamishnr...@googlemail.com> wrote:
> We've been having trouble with the sandbox wsdl so as we're close to
> going live I figured I'd check that we will, if neccessary, be able to
> rebuild our client against the live service wsdl. It appears not. I
> tried using both the Axis tool in Eclipse and the underlying wsdl2java
> utility in cxf from the command line. Heres the result:
> C:\Documents and Settings\haggiscode>wsdl2java -client -d C:\temptest
> \googleclient h
> ttps://www.google.com/api/adsense/v3/AccountService?wsdl > 07-Oct-2009 10:12:55 org.apache.cxf.transport.https.SSLUtils
> getCiphersuites
> INFO: The cipher suites have not been configured, falling back to
> cipher suite f
> ilters.
> 07-Oct-2009 10:12:55 org.apache.cxf.transport.https.SSLUtils
> getCiphersuites
> INFO: The cipher suite filters have not been configured, falling back
> to default
> filters.
> 07-Oct-2009 10:12:55 org.apache.cxf.transport.https.SSLUtils
> getCiphersFromList
> INFO: The cipher suites have been set to SSL_RSA_WITH_RC4_128_MD5,
> SSL_RSA_WITH_
> RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA,
> TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS
> _DHE_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA,
> SSL_DHE_RSA_WITH_3
> DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA,
> SSL_RSA_WITH_DES_CBC_SHA, SS
> L_DHE_RSA_WITH_DES_CBC_SHA, SSL_DHE_DSS_WITH_DES_CBC_SHA,
> SSL_RSA_EXPORT_WITH_RC
> 4_40_MD5, SSL_RSA_EXPORT_WITH_DES40_CBC_SHA,
> SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_S
> HA, SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA, TLS_KRB5_WITH_RC4_128_SHA,
> TLS_KRB5_W
> ITH_RC4_128_MD5, TLS_KRB5_WITH_3DES_EDE_CBC_SHA,
> TLS_KRB5_WITH_3DES_EDE_CBC_MD5,
> TLS_KRB5_WITH_DES_CBC_SHA, TLS_KRB5_WITH_DES_CBC_MD5,
> TLS_KRB5_EXPORT_WITH_RC4_
> 40_SHA, TLS_KRB5_EXPORT_WITH_RC4_40_MD5,
> TLS_KRB5_EXPORT_WITH_DES_CBC_40_SHA, TL
> S_KRB5_EXPORT_WITH_DES_CBC_40_MD5.
> WSDLToJava Error: Thrown by JAXB : undefined simple or complex type
> 'xs:Exceptio
> n'
> Eclipse winged about a problem with associateAccountFault which I'm
> guessing is related - summary output here:
> IWAB0399E Error in generating Java from WSDL: java.io.IOException:
> ERROR: Missing <soap:fault> element inFault "associateAccountFault" in
> operation "associateAccountFault", in binding associateAccount
> java.io.IOException: ERROR: Missing <soap:fault> element inFault
> "associateAccountFault" in operation "associateAccountFault", in
> binding associateAccount
> at
> Any suggestions how we get round this? or are you replacing the wsdl?