Announcement Announcement Module
Collapse
No announcement yet.
PayloadValidatingInterc error too strict? Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • PayloadValidatingInterc error too strict?

    Hi,

    i'm thinking the org.springframework.ws.endpoint.interceptor.Payloa dValidatingInterceptor is too strict.

    In my case, i have a method call without a parameter. JAX-WS/.Net is creating this valid code.
    <ns1:getAvailableObjectNames xmlns:ns1="..." />

    Now i generated a Python client (to show interoperability) and Python produces this xml code:
    <ns1:getAvailableObjectNames xmlns:ns1="..."></<ns1:getAvailableObjectNames>

    Now i get the following error at my PayloadValidationInterceptor:
    Code:
    <spring-ws:ValidationError xmlns:spring-ws="http://springframework.org/spring-ws">cvc-complex-type.2.1: Element 'ns1:getAvailableObjectNames' must have no character or element information item [children], because the type's content type is empty.</spring-ws:ValidationError>
    In terms of interoperability i think this two messages are both valid.

    Maybe i have to say that i'm using a different XMLSchemaFactory
    -Djavax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema=org...LSchemaFactory

    Cheers,

    Ingo
    Last edited by res1st; Nov 17th, 2006, 05:52 AM.

  • #2
    The PayloadValidator just delegates to the underlying JAXP parsing API's. In effect, it just parses the XML with the given schema's, and records any parsing exceptions.

    So there is really no way around this behaviour, I'm afraid.

    Comment

    Working...
    X