You should read the XML Namespaces spec.
xmlns:tns1="http://DefaultNamespace"; means "In the scope of this element, that is,
the element, its descendants and contained attributes, unless overridden somewhere in that scope,
the prefix tns1 used in an element or attribute name refers to the namespa
Jeff -
Ok, then can you please tell me how can I get this http://DefaultNamespace";> instead of
Also, I dont understand why you say that http://DefaultNamespace";> does not make sense. Can you
please clarify since I can use such element generated by AXIS Client
using my AXIS Server.
- Kumar.
: "babloosony" <[EMAIL PROTECTED]>
To: "Jeff Greif" <[EMAIL PROTECTED]>
Cc:
Sent: Monday, April 04, 2005 8:38 AM
Subject: Re: No namespace for elements in soap message from .NET
| Hi Jeff,
|
| Thank you for the response. But what else can I configure in my W
Hi Jeff,
Thank you for the response. But what else can I configure in my WSDL
so that .NET adds this xmlns:tns1="http://DefaultNamespace"; to in01
element
that is I want this http://DefaultNamespace";> instead of
Please suggest ...
- Kumar.
specified by xmlns="..." in the containing element.
Jeff
- Original Message -
From: "babloosony" <[EMAIL PROTECTED]>
To: ;
Sent: Monday, April 04, 2005 2:54 AM
Subject: No namespace for elements in soap message from .NET
| Hi All,
|
| Can anyone please tell me
Hi All,
Can anyone please tell me why .NET does not include any namespace for
'in0' in below soap message. Is there anything else I can do in my
WSDL posted here so that .NET includes namespace for the element
'in0'. Please suggest ...
SOAP Message from AXIS 1.2 RC2
-
