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

Thanks for the reply Leo. Oddly, our partner is using bts2004 and I'm using
bts2006. I would've thought they could ignore the namespaces but they either
don't know how or are unwilling to do so. My envelope/document schemas
follow a couple of the examples in the bts2006 documentation in which you
create the schemas with a wizard and by modifying the return results to
create the envelope (I believe using the xmldata parameter on the sql). You
then use the same target namespace for both schemas and so to differentiate
between them bts prepends the namespace schema "version" they belong to (NS0
or NS1). I am not too surprised or bothered that the inbound xml is
constructed like this but I'm very disturbed the outbound schema is modified
in the same manner after mapping and I don't really understand why. I don't
believe I'm doing anything that numerous developers would like to do so I'm
surprised that I'm having problems. I have also experimented using the
qualified and unqualified form defaults but that either doesn't alter the
output or causes the map to effectively return a blank. But perhaps my
problem is really with my partner? It may very well be. If you know how to
get bts to accept the namespace in parsing the xml please let me know so I
can pass that along to my partner in this. In the end though if a trading
partner is using an xml parser that is more generic I think we still should
be able to generate appropriate xml for them...
--
Thanks again, NWOP.


"Leo Gan" wrote:

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: Word 2003 XML
    ... In essence the parser determines whether the XML provided to it, ... have much info. about the schemas associated with an XML document. ... (which is what namespaces are all about). ...
    (microsoft.public.mac.office.word)
  • Namespaces on Schemas
    ... I need to build an XML file structure so a client can import data to ... I learned about Namespaces and ... Schemas to tell more about what kind of data are allowed on each ...
    (comp.text.xml)
  • 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: 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)
  • Re: namespace?
    ... confusion of using URL's as namespace names. ... Honestly I think if the standard for web service namespaces ... It is an XML standard per the World Wide Web Consortium. ... reason for needing namespaces in XML is because the very nature of XML ...
    (microsoft.public.dotnet.framework.webservices)
Quantcast