WebService Namespace

[Techno_Dex]

Is there a way to configure a WebService Namespace in a config file that can
be set (i.e. [WebService(Namespace = "http://tempuri.org/")] to
[WebService(Namespace = Properties.Settings.WebServiceNamespace)])? I have
a webservice that I might need to configure/move on multiple different
servers but from what I can tell, the Namespace must be compiled into the
assembly or use the default http://tempuri.org/. This seams very limiting
from a load balancing standpoint. If this is possible, is what needs to be
done on the client side also????

[John Saunders]

"Techno_Dex" <no**********@osi-corp.comwrote in message
news:O9**************@TK2MSFTNGP06.phx.gbl...

Is there a way to configure a WebService Namespace in a config file that
can be set (i.e. [WebService(Namespace = "http://tempuri.org/")] to
[WebService(Namespace = Properties.Settings.WebServiceNamespace)])? I
have a webservice that I might need to configure/move on multiple
different servers but from what I can tell, the Namespace must be compiled
into the assembly or use the default http://tempuri.org/. This seams
very limiting from a load balancing standpoint. If this is possible, is
what needs to be done on the client side also????

The namespace is just that - a space containing names. It has nothing to do
with a URL. You could as easily use urn:org.tempuri.

You don't need to change the namespace when you change the server your
service is deployed on.

For the future, consider: if it was necessary to change the namespace, then
everyone would have to do it, and there'd be an easier way!

John

[Techno_Dex]

This is exactly the reason for my question, as I did change the namespace to
something other than tempuri.org and deployed both the webservice and the
client which uses it, but I was receiving errors. As soon as I changed it
back and redeployed, Problem gone..... Any other suggestions?

"John Saunders" <john.saunders at trizetto.comwrote in message
news:uP**************@TK2MSFTNGP03.phx.gbl...

"Techno_Dex" <no**********@osi-corp.comwrote in message
news:O9**************@TK2MSFTNGP06.phx.gbl...

>Is there a way to configure a WebService Namespace in a config file that
can be set (i.e. [WebService(Namespace = "http://tempuri.org/")] to
[WebService(Namespace = Properties.Settings.WebServiceNamespace)])? I
have a webservice that I might need to configure/move on multiple
different servers but from what I can tell, the Namespace must be
compiled into the assembly or use the default http://tempuri.org/. This
seams very limiting from a load balancing standpoint. If this is
possible, is what needs to be done on the client side also????

The namespace is just that - a space containing names. It has nothing to
do with a URL. You could as easily use urn:org.tempuri.

You don't need to change the namespace when you change the server your
service is deployed on.

For the future, consider: if it was necessary to change the namespace,
then everyone would have to do it, and there'd be an easier way!

John

[John Saunders]

"Techno_Dex" <no**********@osi-corp.comwrote in message
news:Ow**************@TK2MSFTNGP05.phx.gbl...

This is exactly the reason for my question, as I did change the namespace
to something other than tempuri.org and deployed both the webservice and
the client which uses it, but I was receiving errors. As soon as I
changed it back and redeployed, Problem gone..... Any other suggestions?

If you'll include the error messages, perhaps someone can help you. But it
has nothing to do with the match between namespace and hosting URL.

John

"John Saunders" <john.saunders at trizetto.comwrote in message
news:uP**************@TK2MSFTNGP03.phx.gbl...

>"Techno_Dex" <no**********@osi-corp.comwrote in message
news:O9**************@TK2MSFTNGP06.phx.gbl...

>>Is there a way to configure a WebService Namespace in a config file that
can be set (i.e. [WebService(Namespace = "http://tempuri.org/")] to
[WebService(Namespace = Properties.Settings.WebServiceNamespace)])? I
have a webservice that I might need to configure/move on multiple
different servers but from what I can tell, the Namespace must be
compiled into the assembly or use the default http://tempuri.org/.
This seams very limiting from a load balancing standpoint. If this is
possible, is what needs to be done on the client side also????

The namespace is just that - a space containing names. It has nothing to
do with a URL. You could as easily use urn:org.tempuri.

You don't need to change the namespace when you change the server your
service is deployed on.

For the future, consider: if it was necessary to change the namespace,
then everyone would have to do it, and there'd be an easier way!

John

[Techno_Dex]

Server did not recognize the value of HTTP Header SOAPAction.

"John Saunders" <john.saunders at trizetto.comwrote in message
news:%2****************@TK2MSFTNGP03.phx.gbl...

"Techno_Dex" <no**********@osi-corp.comwrote in message
news:Ow**************@TK2MSFTNGP05.phx.gbl...

>This is exactly the reason for my question, as I did change the namespace
to something other than tempuri.org and deployed both the webservice and
the client which uses it, but I was receiving errors. As soon as I
changed it back and redeployed, Problem gone..... Any other suggestions?

If you'll include the error messages, perhaps someone can help you. But it
has nothing to do with the match between namespace and hosting URL.

John

>"John Saunders" <john.saunders at trizetto.comwrote in message
news:uP**************@TK2MSFTNGP03.phx.gbl...

>>"Techno_Dex" <no**********@osi-corp.comwrote in message
news:O9**************@TK2MSFTNGP06.phx.gbl...
Is there a way to configure a WebService Namespace in a config file
that can be set (i.e. [WebService(Namespace = "http://tempuri.org/")]
to [WebService(Namespace = Properties.Settings.WebServiceNamespace)])?
I have a webservice that I might need to configure/move on multiple
different servers but from what I can tell, the Namespace must be
compiled into the assembly or use the default http://tempuri.org/. This
seams very limiting from a load balancing standpoint. If this is
possible, is what needs to be done on the client side also????

The namespace is just that - a space containing names. It has nothing to
do with a URL. You could as easily use urn:org.tempuri.

You don't need to change the namespace when you change the server your
service is deployed on.

For the future, consider: if it was necessary to change the namespace,
then everyone would have to do it, and there'd be an easier way!

John

[John Saunders]

"Techno_Dex" <no**********@osi-corp.comwrote in message
news:uS****************@TK2MSFTNGP03.phx.gbl...

Server did not recognize the value of HTTP Header SOAPAction.

Try putting quotes around the SOAPAction. Also, try doing without it by
using:

[SoapDocumentService(
SoapBindingUse.Literal,
SoapParameterStyle.Bare,
RoutingStyle = SoapServiceRoutingStyle.RequestElement) // ws-i Basic Profile
1.1 Requirement R1109
]

>John Saunders" <john.saunders at trizetto.comwrote in message
news:%2****************@TK2MSFTNGP03.phx.gbl...

>"Techno_Dex" <no**********@osi-corp.comwrote in message
news:Ow**************@TK2MSFTNGP05.phx.gbl...

>>This is exactly the reason for my question, as I did change the
namespace to something other than tempuri.org and deployed both the
webservice and the client which uses it, but I was receiving errors. As
soon as I changed it back and redeployed, Problem gone..... Any other
suggestions?

If you'll include the error messages, perhaps someone can help you. But
it has nothing to do with the match between namespace and hosting URL.

John

>>"John Saunders" <john.saunders at trizetto.comwrote in message
news:uP**************@TK2MSFTNGP03.phx.gbl...
"Techno_Dex" <no**********@osi-corp.comwrote in message
news:O9**************@TK2MSFTNGP06.phx.gbl...
Is there a way to configure a WebService Namespace in a config file
that can be set (i.e. [WebService(Namespace = "http://tempuri.org/")]
to [WebService(Namespace = Properties.Settings.WebServiceNamespace)])?
I have a webservice that I might need to configure/move on multiple
different servers but from what I can tell, the Namespace must be
compiled into the assembly or use the default http://tempuri.org/.
This seams very limiting from a load balancing standpoint. If this is
possible, is what needs to be done on the client side also????

The namespace is just that - a space containing names. It has nothing
to do with a URL. You could as easily use urn:org.tempuri.

You don't need to change the namespace when you change the server your
service is deployed on.

For the future, consider: if it was necessary to change the namespace,
then everyone would have to do it, and there'd be an easier way!

John

[Techno_Dex]

Again, I'm not explicitly setting the SOAPAction anywhere, the only think I
changed was the WebNamespace which broke the service, so I changed it back
and the problem was resolved.... Next idea?

"John Saunders" <john.saunders at trizetto.comwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...

"Techno_Dex" <no**********@osi-corp.comwrote in message
news:uS****************@TK2MSFTNGP03.phx.gbl...

>Server did not recognize the value of HTTP Header SOAPAction.

Try putting quotes around the SOAPAction. Also, try doing without it by
using:

[SoapDocumentService(
SoapBindingUse.Literal,
SoapParameterStyle.Bare,
RoutingStyle = SoapServiceRoutingStyle.RequestElement) // ws-i Basic
Profile 1.1 Requirement R1109
]

>>John Saunders" <john.saunders at trizetto.comwrote in message
news:%2****************@TK2MSFTNGP03.phx.gbl.. .

>>"Techno_Dex" <no**********@osi-corp.comwrote in message
news:Ow**************@TK2MSFTNGP05.phx.gbl...
This is exactly the reason for my question, as I did change the
namespace to something other than tempuri.org and deployed both the
webservice and the client which uses it, but I was receiving errors.
As soon as I changed it back and redeployed, Problem gone..... Any
other suggestions?

If you'll include the error messages, perhaps someone can help you. But
it has nothing to do with the match between namespace and hosting URL.

John
"John Saunders" <john.saunders at trizetto.comwrote in message
news:uP**************@TK2MSFTNGP03.phx.gbl...
"Techno_Dex" <no**********@osi-corp.comwrote in message
news:O9**************@TK2MSFTNGP06.phx.gbl.. .
>Is there a way to configure a WebService Namespace in a config file
>that can be set (i.e. [WebService(Namespace = "http://tempuri.org/")]
>to [WebService(Namespace =
>Properties.Settings.WebServiceNamespace)])? I have a webservice that
>I might need to configure/move on multiple different servers but from
>what I can tell, the Namespace must be compiled into the assembly or
>use the default http://tempuri.org/. This seams very limiting from a
>load balancing standpoint. If this is possible, is what needs to be
>done on the client side also????
>
The namespace is just that - a space containing names. It has nothing
to do with a URL. You could as easily use urn:org.tempuri.
>
You don't need to change the namespace when you change the server your
service is deployed on.
>
For the future, consider: if it was necessary to change the namespace,
then everyone would have to do it, and there'd be an easier way!
>
John
>
>

[John Saunders]

"Techno_Dex" <no**********@osi-corp.comwrote in message
news:%2****************@TK2MSFTNGP06.phx.gbl...

Again, I'm not explicitly setting the SOAPAction anywhere, the only think
I changed was the WebNamespace which broke the service, so I changed it
back and the problem was resolved.... Next idea?

You must have a mismatch between which namespace is being sent and which is
being received.

Also, although you may not be explicitly sending the SOAPaction, _something_
appears to be sending it, and you might want to find out what's going out on
the wire.

John

>
"John Saunders" <john.saunders at trizetto.comwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...

>"Techno_Dex" <no**********@osi-corp.comwrote in message
news:uS****************@TK2MSFTNGP03.phx.gbl...

>>Server did not recognize the value of HTTP Header SOAPAction.

Try putting quotes around the SOAPAction. Also, try doing without it by
using:

[SoapDocumentService(
SoapBindingUse.Literal,
SoapParameterStyle.Bare,
RoutingStyle = SoapServiceRoutingStyle.RequestElement) // ws-i Basic
Profile 1.1 Requirement R1109
]

>>>John Saunders" <john.saunders at trizetto.comwrote in message
news:%2****************@TK2MSFTNGP03.phx.gbl. ..
"Techno_Dex" <no**********@osi-corp.comwrote in message
news:Ow**************@TK2MSFTNGP05.phx.gbl...
This is exactly the reason for my question, as I did change the
namespace to something other than tempuri.org and deployed both the
webservice and the client which uses it, but I was receiving errors.
As soon as I changed it back and redeployed, Problem gone..... Any
other suggestions?

If you'll include the error messages, perhaps someone can help you. But
it has nothing to do with the match between namespace and hosting URL.

John
"John Saunders" <john.saunders at trizetto.comwrote in message
news:uP**************@TK2MSFTNGP03.phx.gbl.. .
>"Techno_Dex" <no**********@osi-corp.comwrote in message
>news:O9**************@TK2MSFTNGP06.phx.gbl. ..
>>Is there a way to configure a WebService Namespace in a config file
>>that can be set (i.e. [WebService(Namespace =
>>"http://tempuri.org/")] to [WebService(Namespace =
>>Properties.Settings.WebServiceNamespace)])? I have a webservice that
>>I might need to configure/move on multiple different servers but
>>from what I can tell, the Namespace must be compiled into the
>>assembly or use the default http://tempuri.org/. This seams very
>>limiting from a load balancing standpoint. If this is possible, is
>>what needs to be done on the client side also????
>>
>The namespace is just that - a space containing names. It has nothing
>to do with a URL. You could as easily use urn:org.tempuri.
>>
>You don't need to change the namespace when you change the server
>your service is deployed on.
>>
>For the future, consider: if it was necessary to change the
>namespace, then everyone would have to do it, and there'd be an
>easier way!
>>
>John
>>
>>
>
>