Eclipse Community Forums: ServerTools (WTP) » WSDL 1.1 Binding Extensions for SOAP 1.2

Help

Home

Home » Language IDEs » ServerTools (WTP) » WSDL 1.1 Binding Extensions for SOAP 1.2

Show: Today's Messages :: Show Polls :: Message Navigator

WSDL 1.1 Binding Extensions for SOAP 1.2 [message #178208]

Tue, 29 August 2006 21:28

Eclipse User

Originally posted by: jdoyleoss.gmail.com

I've looked at the 1.5 release info and the 2.0 project plan, and can't
find any mention of the WSDL 1.1 Binding Extensions for SOAP 1.2. Is it in
the plan to support this specification draft?

thanks

jd

Report message to a moderator

Re: WSDL 1.1 Binding Extensions for SOAP 1.2 [message #178290 is a reply to message #178208]

Wed, 30 August 2006 15:15

Eclipse User

Originally posted by: jdoyleoss.gmail.com

I think I may have figured out a fix for my problem, but would
appreciate if someone in the know would validate the approach.

The binding extensions I mentioned are declared in a namespace, that
unlike most of the standard schemas, does not correspond to a URL.
Because if this the standard WSDL validation fails. From looking
through the validation code I think the right approach is to implement
my own IExtensibleURIResolver that will recognize this namespace and
provide the correct location.

Is this a good approach?

thanks

jd wrote:
> I've looked at the 1.5 release info and the 2.0 project plan, and can't
> find any mention of the WSDL 1.1 Binding Extensions for SOAP 1.2. Is it
> in the plan to support this specification draft?
>
> thanks
>
> jd
>

Report message to a moderator

Re: WSDL 1.1 Binding Extensions for SOAP 1.2 [message #179378 is a reply to message #178290]

Tue, 19 September 2006 05:44

Craig Salter

Messages: 169
Registered: July 2009

Senior Member

John Doyle wrote:

> I think I may have figured out a fix for my problem, but would
> appreciate if someone in the know would validate the approach.

> The binding extensions I mentioned are declared in a namespace, that
> unlike most of the standard schemas, does not correspond to a URL.
> Because if this the standard WSDL validation fails. From looking
> through the validation code I think the right approach is to implement
> my own IExtensibleURIResolver that will recognize this namespace and
> provide the correct location.

> Is this a good approach?

The WSDL Validator has an extension mechanism to allow exensibility
elements to be validated. You'll also want to register a schema for SOAP
1.2 in the XML Catalog (there's extension points available to do this
programmatically). Between these two extension points you should be able
to implement the validation support your after.

Report message to a moderator

Previous Topic:	using XML Editor in RCP App
Next Topic:	Debug Setup in WST 1.0.3

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 18:31:19 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter