This content has been marked as final.
Show 3 replies
-
1. Re: Stop enforcing parameter names?
thomas.diesler Jun 5, 2007 10:54 AM (in response to bcowan)The question is, whether the incomming message conforms to the abstract contract published by the endpoint. If the message is invalid with that respect it simply is invalid
-
2. Re: Stop enforcing parameter names?
bcowan Jun 5, 2007 11:20 AM (in response to bcowan)"thomas.diesler@jboss.com" wrote:
The question is, whether the incomming message conforms to the abstract contract published by the endpoint. If the message is invalid with that respect it simply is invalid
At this point we're much more concerned about consistency. Updating to a newer server version has invalidated several thousand clients because the server has changed the way it validates the messages. Granted that those clients don't conform 100% to the published WSDL, but the tools at the time (including JBoss) ignored parameter names so it has never been an issue. Since the WSDL specifies the type and order of the parameters, validation of the actual name wasn't (and perhaps isn't) required.
We just need the current version of the JBoss web service stack to handle messages in compatible manner with the prior version. Judging by your response, it sounds like there is no such compatibility option.
Regards,
Bruce -
3. Re: Stop enforcing parameter names?
thomas.diesler Jun 5, 2007 11:55 AM (in response to bcowan)You can setup an endpoint that consumes raw XML. Have a look at JAXWS @Provider, also an XML preproccessing phase might do the job for you