Hi,

This is probably a dull question but I'm quite new to namespaces etc. and a 
bit stuck!

I currently have an orchestration exposed as a web service and I've been try
ing without success to get front page to recognise the WSDL.  None of the pa
rameters show up in the data source wizard, though, and I was wondering whet
her this was a namespace is
sue caused by the extra blank namespaces that Biztalk inserts into my child 
nodes.  Basically when I generate the web service the following SOAP structu
re is generated for inbound messages:

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:x
sd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org
/soap/envelope/">
<soap:Body>
<GetQuote xmlns="http://www.landg.com">
<TermQuoteRequest xmlns="http://Direct.TermQuoteRequest">
<Life xmlns="">
<title>string</title>
<forename>string</forename>
<surname>string</surname>
<sex>string</sex>
<dob>date</dob>
<smoker>Yes or No</smoker>
<mail>Yes or No</mail>
</Life>
<QuoteBasis xmlns="">
<sumAssured>string</sumAssured>
<premium>string</premium>
<term>string</term>
<frequency>Monthly or Annually</frequency>
<waiver>Yes or No</waiver>
<cic>Yes or No</cic>
<product>Level Term or Mortgage Term or Mortgage Decreasing Term</product>
</QuoteBasis>
</TermQuoteRequest>
</GetQuote>
</soap:Body>
</soap:Envelope>

Do the blank namespaces i.e. xmlns="" in the child elements take these eleme
nts outside of the overall namespace of the document root element?  Could th
is be why the fp wizard finds the Port and Operations but thinks that there 
are no parameters?

Thanks in advance for any advice!

Ian

[ Post a follow-up to this message ]

Not sure.  But I would recommend that you cross post to the Frongpage
newsgroup.  They will need to confirm if the blank namespace is causing the
problem.

Hope this helps.

Sincerely,


Everett Yang
DSI - Microsoft BizTalk Server

This posting is provided “AS IS” with no warranties, and confers no rights.
Subscribe at
http://support.microsoft.com/defaul...msdn/nospam.asp
&SD=msdn

[ Post a follow-up to this message ]