Results 1 to 4 of 4

Thread: faultString cannot be empty

  1. #1

    Default faultString cannot be empty

    i got my first service up and going with little trouble. i'm trying to port over a xfire service now. i'm not sure what i've missing. the WSDL generates fine but when i call the service i'm getting.

    2007-08-24 11:39:03,875 ERROR [localhost].[/oracle].[spring-ws] - Servlet.service() for
    servlet spring-ws threw exception
    java.lang.IllegalArgumentException: faultString cannot be empty

  2. #2

    Default

    i found my problem. i had some old xfire code in there.

    the question i have now is there a way to pass a generic server fault to the client when this happens?

  3. #3
    Join Date
    Jul 2005
    Location
    Rotterdam, the Netherlands
    Posts
    1,562

    Default

    You can define an EndpointExceptionResolver, see http://static.springframework.org/sp...ption-resolver
    Arjen Poutsma

    Spring Web Services Dev Lead
    Please read the FAQ

  4. #4

    Default

    it doesn't seem like this will deal with run-time exceptions.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •