Damon, Could you please log a JIRA bug? with your wsdl and the url construct?
thanks, dims On 11/6/06, Damon Lanphear <[EMAIL PROTECTED]> wrote:
Greetings, I've been working on getting REST support working using HTTP GET for a service specified using the contract-first idiom, and code generated using WSDL2Java. The data binding is Axis Data Binding (adb). It appears that there are mismatches between the expectations of the generated adb code and the output of the URL to SOAPEnvelope transcoder: SchemaUtil.handleMediaTypeURLEncoded() 1) SchemaUtil.handleMediaTypeURLEncoded() appears to strip off the namespace information when constructing an OMElement for the SOAP message body. The ADB data binding assumes that the namespace information is present when unmarshalling SOAP message input. 2) SchemaUtil.handleMediaTypeURLEncoded() assumes that complex XML data types are specified as <sequence> as opposed to <all>. Attempts to use complex types specified with <all> will silently fail. I'm not sure if this is a reasonable enough assumption for a silent failure. It seems that the fix is straightforward enough: Have SchemaUtil.handleMediaTypeURLEncoded() not drop namespace information, and have it be robust to complex types specified with <all>. But perhaps there are sound reasons for such a fix not being correct. Can someone please clarify this for me? Thanks, Damon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
