Hello community,
We are building Enterprise Web Services in our application running on Netweaver 7.40 and have built several service definitions through the Enterprise Service Builder tool. Ultimately the WSDL file that the builder creates is mapped to Java skeleton classes which define the API for the service endpoints thanks to Netweaver Developer Studios' 'Generate Java Bean Skeleton' functionality. What we noticed was that during the processing of requests, the application was ignoring all validation imposed/defined in the WSDL definition.
We're assuming that this type of validation is part of an operating Web Service implementation on any J2EE Application Container - including Netweaver - and the Container would be responsible for early validation stages of request processing, utilizing the Service definitions.
Is it not part of the JSR-921 specification that compliant applications include a SOAP Processor that parses and validates a SOAP request that is submitted? Where It is part of the responsibility of the SOAP processor upon receiving a Service request to validate and THEN relay the request to the appropriate Service method?
We could potentially validate our own but we have 100's of objects to manually validate against which becomes a very tedious and hard to maintain exercise. It seems redundant and common behavior that should be handled at the Service layer by the SOAP processor within the Container should it not?
Validation capabilities seem to be provided by other vendor products such as Oracle AS and WebSphere. Does anyone know if Netweaver offers this and if so how would we go about implementing it through configuration or otherwise?
Thank you!
Hanif