Re: getting rid of NS0 (name space) in xml tags

Hi,
Is your partner use a self-made xml parser?
As I know U can ignore the prefixes if U don't want to use the namespaces
(it's quite strange, cose, the namespaces are one of the main part of XMl)
and if U use MS xml-parsers.
It's the parser's job to bother with namespases and prefixes.
BTW BizTalk doesn't work well with xml-messages without namespaces.

I agree that SQL adapter is sort of hard to understanding
(http://geekswithblogs.net/leonidganeline/archive/2006/03/14/72293.aspx)

could U, pleease, give more information about:
I am using a sql adapter with an xml document schema and envelope schema...


--
Regards

Leonid Ganeline
BizTalk Solution Developer
===========================
http://geekswithblogs.com/leonidganeline
================================

"new_world_order_piggies" <newworldorderpiggies@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message news:040A7286-EC0D-4193-9052-9FDB5694B587@xxxxxxxxxxxxxxxx
I am using a sql adapter with an xml document schema and envelope schema.
My
understanding is that I need to use the same name space to put this into
effect for the 2 schemas and allow biztalk to bring back multiple rows
from
SQL Server. Is this correct? The bottom line is that I need to remove
the
NS0: prepended to the output tags or our trading partner can't consume our
xml. Is there any way to get rid of these prepended values? As a general
comment if this is being monitored, I am surprised at the complexity and
difficulty in using the sql adapter for biztalk, especially in terms of
bringing back and interpreting multiple rows. I would've thought this
would
be much easier and further the fact that the schema tags are changed is
outrageous. I'm sure someone can explain it and I'm also sure there are
"good" reasons for it happening but really, to change the schema such that
it
no longer becomes portable really destroys the entire idea of xml being
the
self-describing, all-purpose data format it is supposed to be. In short,
if
there is a way to remove the cursed NS0 I'd love the hear about it.
--
Thanks to any and all, NWOP.


.

Relevant Pages

  • Re: Prefixed namespaces and Xpath
    ... Well you don't need to know the exact prefixes - but you do need to know the ... compliled all of them with no namespaces. ... For some reason in the Xml world people just don't seem to see this as being ... a SelectNode... ...
    (microsoft.public.dotnet.xml)
  • RE: Get all namespace prefix from XmlDocument class
    ... prefixes and URIs in an XmlDocument. ... there are no methods or properties in XmlDocument for us ... to search for all namespaces in an Xml. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: namespace?
    ... I think it's a bit funny that the new MS stuff, I forget the name maybe it was WCF?, was almost back to comma delimited and they talked about cutting down on the data being sent across the net in comparison to XML. ... Honestly I think if the standard for web service namespaces was ACME/employees/HR instead of http://www.ACME.com/employees/HR it would have made more sense to me as it doesn't carry the connotation that it's a web address. ... The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. ...
    (microsoft.public.dotnet.framework.webservices)
  • RE: .NET objects (C#)
    ... and BizTalk Receive and Send handlers treat all message content ... Adapters can pass any content in - it doesn't have to be XML. ... say, the File adapter, and select Pass-through pipelines (pipelines that ... message received by the orchestration, BizTalk will at this stage attempt XML ...
    (microsoft.public.biztalk.general)
  • Re: XmlSerializer: deserialize against xsd generated class
    ... If there are 5 namespaces in the XML do I need to add a namespace for each ... I did find a code snippet that removes the "empty" nodes ... public partial class Request_TypeMessageTypeFieldTag4000 { ...
    (microsoft.public.dotnet.xml)