Hitachi Vantara Pentaho Community Forums
Results 1 to 3 of 3

Thread: Web services lookup step and VIES web service

  1. #1
    Join Date
    Jun 2013
    Posts
    2

    Exclamation Web services lookup step and VIES web service

    Hi.

    I'm trying to use the Web services lookup step with the VIES VAT number validation webservice provided by the European Comission (http://ec.europa.eu/taxation_customs...atService.wsdl), and I always get the followin error:

    Code:
    2013/06/05 18:13:51 - Web services lookup.0 - Using SOAP Action string ["urn:ec.europa.eu:taxud:vies:services:checkVat/checkVatApprox"] in the request header.
    2013/06/05 18:13:51 - Web services lookup.0 - ERROR (version 4.4.0-stable, build 17588 from 2012-11-21 16.02.21 by buildguy) : Unexpected error
    2013/06/05 18:13:51 - Web services lookup.0 - ERROR (version 4.4.0-stable, build 17588 from 2012-11-21 16.02.21 by buildguy) : org.pentaho.di.core.exception.KettleStepException: 
    2013/06/05 18:13:51 - Web services lookup.0 - ERROR (version 4.4.0-stable, build 17588 from 2012-11-21 16.02.21 by buildguy) : Internal server error while calling the web service. Service URL=http://ec.europa.eu/taxation_customs/vies/services/checkVatService, Response code = 500.
    2013/06/05 18:13:51 - Web services lookup.0 - ERROR (version 4.4.0-stable, build 17588 from 2012-11-21 16.02.21 by buildguy) : Response body: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><soap:Fault><faultcode>soap:Client</faultcode><faultstring>Unexpected wrapper element {urn:ec.europa.eu:taxud:vies:services:checkVat}checkVatApprox found.   Expected {urn:ec.europa.eu:taxud:vies:services:checkVat:types}checkVatApprox.</faultstring></soap:Fault></soap:Body></soap:Envelope>

    Looks like the SOAP Action string is not what the webservice expects.
    Where do I change this string?

    Thanks!

  2. #2
    Join Date
    Jun 2012
    Posts
    5,534

    Default

    Could be a bug ...

    A workaround for VIES could be to use a slightly modified wsdl file: I changed the wsdl targetnamespace and xmlns:impl to "urn:...:checkVat:types" and served it from my own host.
    So long, and thanks for all the fish.

  3. #3
    Join Date
    Jun 2013
    Posts
    2

    Default

    Quote Originally Posted by marabu View Post
    A workaround for VIES could be to use a slightly modified wsdl file: I changed the wsdl targetnamespace and xmlns:impl to "urn:...:checkVat:types" and served it from my own host.
    It's not the prettiest solution but, for now, it may solve my problem...
    Thank you.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Privacy Policy | Legal Notices | Safe Harbor Privacy Policy

Copyright © 2005 - 2019 Hitachi Vantara Corporation. All Rights Reserved.