Namespace prefix change

[jb]

I have discovered that when the WSDL is auto-generated in .NET (i.e.
http://.../MyService.asmx?WSDL):

* Prior to SP1, it generated xmlns:s0="http://mynamespace/" in
<wsdl:definitio ns>, and then output my web methods as "s0:MyWebMethod " in
<wsdl:message > sections

* At SP1, it generates xmlns:tns="http ://mynamespace/" in
<wsdl:definitio ns>, and then output my web methods as "tns:MyWebMetho d" in
<wsdl:message > sections

So the namespace is the same, but the namespace *prefix* has changed from
"s0" to "tns".

This is causing problems with external integrations (InfoPath, as it happens).

Is there anything I can do about this, e.g. get it now to use "s0" again if
that's what I want? And/or, why the change?

[Drew Marsh]

jb wrote:

I have discovered that when the WSDL is auto-generated in .NET (i.e.
http://.../MyService.asmx?WSDL):

* Prior to SP1, it generated xmlns:s0="http://mynamespace/" in
<wsdl:definitio ns>, and then output my web methods as "s0:MyWebMethod "
in <wsdl:message > sections

* At SP1, it generates xmlns:tns="http ://mynamespace/" in
<wsdl:definitio ns>, and then output my web methods as
"tns:MyWebMetho d" in <wsdl:message > sections

So the namespace is the same, but the namespace *prefix* has changed
from "s0" to "tns".

This is causing problems with external integrations (InfoPath, as it
happens).

Is there anything I can do about this, e.g. get it now to use "s0"
again if that's what I want? And/or, why the change?

While I realize you obviously have a problem and I'm sympathetic to that,
the changing of a prefix really shouldn't matter in terms of XML. The prefix
is just an alias within the scope of declaration in the instance document.
You can technically have infinite prefixes in an instance document that point
to the same namespace URI.

That said, I don't know exactly what the InfoPath side is doing, but I know
InfoPath is aware of namespaces. Can you give more detail on what the error
is? Also, I don't know of any way to change the prefix that the WSDL generator
uses since, from it's perspective (which is correct), the prefix used really
doesn't matter.

Cheers,
Dre

[Dan Rogers]

What is the infopath issue?
--------------------
Thread-Topic: Namespace prefix change
thread-index: AcTkY35JG1qSfwb 1T8qg68tMZlp5YA ==
X-WBNR-Posting-Host: 82.152.32.104
From: "=?Utf-8?B?amI=?=" <jb@discussions .microsoft.com>
Subject: Namespace prefix change
Date: Fri, 17 Dec 2004 10:09:04 -0800
Lines: 20
Message-ID: <FD************ *************** *******@microso ft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups:
microsoft.publi c.dotnet.framew ork.webservices ,microsoft.publ ic.infopath
NNTP-Posting-Host: TK2MSFTNGXA03.p hx.gbl 10.40.1.29
Path: cpmsftngxa10.ph x.gbl!TK2MSFTNG XA03.phx.gbl
Xref: cpmsftngxa10.ph x.gbl microsoft.publi c.infopath:1497 3
microsoft.publi c.dotnet.framew ork.webservices :8177
X-Tomcat-NG: microsoft.publi c.dotnet.framew ork.webservices

I have discovered that when the WSDL is auto-generated in .NET (i.e.
http://.../MyService.asmx?WSDL):

* Prior to SP1, it generated xmlns:s0="http://mynamespace/" in
<wsdl:definitio ns>, and then output my web methods as "s0:MyWebMethod " in
<wsdl:message > sections

* At SP1, it generates xmlns:tns="http ://mynamespace/" in
<wsdl:definitio ns>, and then output my web methods as "tns:MyWebMetho d" in
<wsdl:message > sections

So the namespace is the same, but the namespace *prefix* has changed from
"s0" to "tns".

This is causing problems with external integrations (InfoPath, as it
happens).

Is there anything I can do about this, e.g. get it now to use "s0" again if
that's what I want? And/or, why the change?

[jb]

Thanks, Drew.

Yes, you'd think the prefixes wouldn't matter, but they do in practice for
InfoPath stuff (as explained a bit more in my other reply below).

I've come to the same conclusion as you say: I don't see how to influence
them. Given which, I have decided I have no option but to say my InfoPath
solution will require .NET SP1.

"Drew Marsh" wrote:

jb wrote:

I have discovered that when the WSDL is auto-generated in .NET (i.e.
http://.../MyService.asmx?WSDL):

* Prior to SP1, it generated xmlns:s0="http://mynamespace/" in
<wsdl:definitio ns>, and then output my web methods as "s0:MyWebMethod "
in <wsdl:message > sections

* At SP1, it generates xmlns:tns="http ://mynamespace/" in
<wsdl:definitio ns>, and then output my web methods as
"tns:MyWebMetho d" in <wsdl:message > sections

So the namespace is the same, but the namespace *prefix* has changed
from "s0" to "tns".

This is causing problems with external integrations (InfoPath, as it
happens).

Is there anything I can do about this, e.g. get it now to use "s0"
again if that's what I want? And/or, why the change?

While I realize you obviously have a problem and I'm sympathetic to that,
the changing of a prefix really shouldn't matter in terms of XML. The prefix
is just an alias within the scope of declaration in the instance document.
You can technically have infinite prefixes in an instance document that point
to the same namespace URI.

That said, I don't know exactly what the InfoPath side is doing, but I know
InfoPath is aware of namespaces. Can you give more detail on what the error
is? Also, I don't know of any way to change the prefix that the WSDL generator
uses since, from it's perspective (which is correct), the prefix used really
doesn't matter.

Cheers,
Drew

[jb]

The InfoPath are so numerous I can't type it all in; in fact, I can't even
track them all down.

One example: IP saves the text of a condition you type in. If the namespace
prefix gets changed later, it can no longer match up the condition against
the "tree" it maintains of the source's data fields. There are plenty other
cases that go wrong. I'm most worried about the ones that only show up after
a while of testing.

Since I can't seem to influence the WSDL generation, I seem to have little
choice but to require that users of my InfoPath solution must have .NET SP1,
and that's that. So I'm changing all my sources to use the new "tns" prefix
instead of the old "s0".

"Dan Rogers" wrote:

What is the infopath issue?
--------------------
Thread-Topic: Namespace prefix change
thread-index: AcTkY35JG1qSfwb 1T8qg68tMZlp5YA ==
X-WBNR-Posting-Host: 82.152.32.104
From: "=?Utf-8?B?amI=?=" <jb@discussions .microsoft.com>
Subject: Namespace prefix change
Date: Fri, 17 Dec 2004 10:09:04 -0800
Lines: 20
Message-ID: <FD************ *************** *******@microso ft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups:
microsoft.publi c.dotnet.framew ork.webservices ,microsoft.publ ic.infopath
NNTP-Posting-Host: TK2MSFTNGXA03.p hx.gbl 10.40.1.29
Path: cpmsftngxa10.ph x.gbl!TK2MSFTNG XA03.phx.gbl
Xref: cpmsftngxa10.ph x.gbl microsoft.publi c.infopath:1497 3
microsoft.publi c.dotnet.framew ork.webservices :8177
X-Tomcat-NG: microsoft.publi c.dotnet.framew ork.webservices

I have discovered that when the WSDL is auto-generated in .NET (i.e.
http://.../MyService.asmx?WSDL):

* Prior to SP1, it generated xmlns:s0="http://mynamespace/" in
<wsdl:definitio ns>, and then output my web methods as "s0:MyWebMethod " in
<wsdl:message > sections

* At SP1, it generates xmlns:tns="http ://mynamespace/" in
<wsdl:definitio ns>, and then output my web methods as "tns:MyWebMetho d" in
<wsdl:message > sections

So the namespace is the same, but the namespace *prefix* has changed from
"s0" to "tns".

This is causing problems with external integrations (InfoPath, as it
happens).

Is there anything I can do about this, e.g. get it now to use "s0" again if
that's what I want? And/or, why the change?