Eclipse Community Forums: ServerTools (WTP)

Help

Home

Home » Language IDEs » ServerTools (WTP) » WSDL editor

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

WSDL editor [message #136343]

Fri, 02 September 2005 10:37

John O'Shea

Messages: 43
Registered: July 2009

Member

Hi all,
I've just noticed the WTP WSDL Editor insists on automatically
modifying the values of soapActions attribute on <soap:operation>
(inside binding definitions). It insists on rewriting them in the form:

<soap:operation soapAction="http://www.capeclear.com/cc/getAll"/>

where "http://www.capeclear.com/cc" is the operation namespace and
"getAll" is the wsdl:operation name.

Similarily it also insists on setting the "namespace" and "use"
attributes of wsdl:fault bindings as follows:

<wsdl:fault name="bdiFault">
<soap:fault namespace="http://www.capeclear.com/cc-bdi"
use="literal" name="bdiFault"/>
</wsdl:fault>

The editor silently does this when file is saved - this behavior seems a
bit excessive. Can anyone explain why the editor thinks it knows best
in these scenarios? I can understand if the editor wants to validate
the file's contents to ensure it is suitable for a particular WS stack,
but silently modifying the file's contents seems wrong.

On a slightly related note, has anyone noticed the WSDL editor, on
occasion, embed junk non-UTF-8 encoded characters into WSDL files?
These characters seem to confuse the XML parser quite a lot, causing all
sorts of problems within the editor (highlighting errors that do not
exist etc). This has happened to me once, despite the fact that
- the XML editor should default to encoding WSDL file content as UTF-8
(Prefs->General->Content Types->Text->XML->WSDL Content Type ->
Default=UTF-8)
- the WSDL file itself specified UTF-8 as the encoding type in it's XML
declaration.

If I reproduce, I'll send on more details, I just wanted to check if
this is a known issue already (bugzilla say's zarro bugs found).

cheers for any info,

John.

Report message to a moderator

Re: WSDL editor [message #136363 is a reply to message #136343]

Fri, 02 September 2005 13:41

Lawrence Mandel

Messages: 486
Registered: July 2009

Senior Member

Hi John,

>I've just noticed the WTP WSDL Editor insists on automatically
>modifying the values of soapActions attribute on <soap:operation>
>(inside binding definitions).

I've seen this problem before. Did you try disabling the "Regenerate
Binding on save" option on the Window->Preferences->Web and XML->WSDL
Files page? This solved my problem but if this doesn't solve yours please
open a defect.

>The editor silently does this when file is saved - this behavior seems a
>bit excessive. Can anyone explain why the editor thinks it knows best
>in these scenarios? I can understand if the editor wants to validate
>the file's contents to ensure it is suitable for a particular WS stack,
>but silently modifying the file's contents seems wrong.

Not sure whether or not I'm a fan of this feature but I can see the use
case if you can specify the type of bindings you want (including non
Doc/lit bindings). The editor should probably make it clear that the
bindings are being regenerated. I'd say open a defect for this as well.

>On a slightly related note, has anyone noticed the WSDL editor, on
>occasion, embed junk non-UTF-8 encoded characters into WSDL files?
>These characters seem to confuse the XML parser quite a lot, causing all
>sorts of problems within the editor (highlighting errors that do not
>exist etc). This has happened to me once, despite the fact that
>- the XML editor should default to encoding WSDL file content as UTF-8
>(Prefs->General->Content Types->Text->XML->WSDL Content Type ->
>Default=UTF-8)
>- the WSDL file itself specified UTF-8 as the encoding type in it's XML
>declaration.

Haven't seen this but please open a defect with a reproducible case if you
can create one.

Lawrence

Report message to a moderator

Re: WSDL editor [message #136754 is a reply to message #136363]

Tue, 06 September 2005 13:11

John O'Shea

Messages: 43
Registered: July 2009

Member

Hi Laurence,

lmandel@ca.ibm.com wrote:
>
> I've seen this problem before. Did you try disabling the "Regenerate
> Binding on save" option on the Window->Preferences->Web and XML->WSDL
> Files page? This solved my problem but if this doesn't solve yours please
> open a defect.
> <snip>
> Not sure whether or not I'm a fan of this feature but I can see the use
> case if you can specify the type of bindings you want (including non
> Doc/lit bindings). The editor should probably make it clear that the
> bindings are being regenerated. I'd say open a defect for this as well.

Yes, changing the preference resolved the problem. I'm definately not
convinced this option should be enabled by default as silently changing
namespace info in WSDL bindings that were originally authored with
different values for these attributes will break compatability with
existing client (or server) implementations (depending on what the
module is using the WSDL for). I'll open a enhancement request to
request this change.

>
> Haven't seen this but please open a defect with a reproducible case if you
> can create one.

I havn't managed to reproduce this but will do if it happens again.

j.

Report message to a moderator

Previous Topic:	Publish to server disabled while rebuilding workspace
Next Topic:	XML Editor - "document is empty"

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 14:23:44 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter