<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Inline XSD in WSDL with WCF</title>
	<atom:link href="http://winterdom.com/2006/10/inlinexsdinwsdlwithwcf/feed" rel="self" type="application/rss+xml" />
	<link>http://winterdom.com/2006/10/inlinexsdinwsdlwithwcf</link>
	<description>by dæmons be driven</description>
	<lastBuildDate>Wed, 10 Mar 2010 01:45:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: terry</title>
		<link>http://winterdom.com/2006/10/inlinexsdinwsdlwithwcf/comment-page-1#comment-1269</link>
		<dc:creator>terry</dc:creator>
		<pubDate>Wed, 27 Jan 2010 12:20:34 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2006/10/inlinexsdinwsdlwithwcf#comment-1269</guid>
		<description>ok, i worked it out, i needed to implement the BehaviorExtensionElement abstract class thus;

    public class InlineXsdInWsdlBehavior
       : BehaviorExtensionElement,  IWsdlExportExtension, IEndpointBehavior
    

then  implementation is thus;

     public override Type BehaviorType
        {
            get 
            { 
                return typeof(InlineXsdInWsdlBehavior); 
            }

        }

        protected override object CreateBehavior()
        {
            return new InlineXsdInWsdlBehavior();
        }

Job done. works like a charm... other than now im just trying to work out how to get the WSDL to stop importing the xsd types...

Which still results in the following line in the WSDL



Gerrr!</description>
		<content:encoded><![CDATA[<p>ok, i worked it out, i needed to implement the BehaviorExtensionElement abstract class thus;</p>
<p>    public class InlineXsdInWsdlBehavior<br />
       : BehaviorExtensionElement,  IWsdlExportExtension, IEndpointBehavior</p>
<p>then  implementation is thus;</p>
<p>     public override Type BehaviorType<br />
        {<br />
            get<br />
            {<br />
                return typeof(InlineXsdInWsdlBehavior);<br />
            }</p>
<p>        }</p>
<p>        protected override object CreateBehavior()<br />
        {<br />
            return new InlineXsdInWsdlBehavior();<br />
        }</p>
<p>Job done. works like a charm&#8230; other than now im just trying to work out how to get the WSDL to stop importing the xsd types&#8230;</p>
<p>Which still results in the following line in the WSDL</p>
<p>Gerrr!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: terry</title>
		<link>http://winterdom.com/2006/10/inlinexsdinwsdlwithwcf/comment-page-1#comment-1268</link>
		<dc:creator>terry</dc:creator>
		<pubDate>Wed, 27 Jan 2010 11:34:51 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2006/10/inlinexsdinwsdlwithwcf#comment-1268</guid>
		<description>how do you use this in a web service project ??
I see all i need to do is somehow modify the web.config.
I tried using the WCF configuration editor however when selecting 
- advanced/extensions/behaviour element extensions/new
It could not see the type in the assembly which I have placed the class InlineXsdInWsdlBehavior.cs</description>
		<content:encoded><![CDATA[<p>how do you use this in a web service project ??<br />
I see all i need to do is somehow modify the web.config.<br />
I tried using the WCF configuration editor however when selecting<br />
- advanced/extensions/behaviour element extensions/new<br />
It could not see the type in the assembly which I have placed the class InlineXsdInWsdlBehavior.cs</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: terry</title>
		<link>http://winterdom.com/2006/10/inlinexsdinwsdlwithwcf/comment-page-1#comment-1267</link>
		<dc:creator>terry</dc:creator>
		<pubDate>Wed, 27 Jan 2010 11:30:46 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2006/10/inlinexsdinwsdlwithwcf#comment-1267</guid>
		<description>how do you use this in ??</description>
		<content:encoded><![CDATA[<p>how do you use this in ??</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WCF Interoperability: flat WSDL - Jos van Dixhoorn - blog community</title>
		<link>http://winterdom.com/2006/10/inlinexsdinwsdlwithwcf/comment-page-1#comment-1263</link>
		<dc:creator>WCF Interoperability: flat WSDL - Jos van Dixhoorn - blog community</dc:creator>
		<pubDate>Mon, 11 Jan 2010 19:27:14 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2006/10/inlinexsdinwsdlwithwcf#comment-1263</guid>
		<description>[...] This&#160;popular&#160;blogpost&#160;provides a very simple&#160;endpoint behavior to flatten your WSDL and it works like a charm! Note that the WsdlExporter has a property GeneratedWsdlDocuments which returns a ServiceDescriptionCollection. The catch here is that this is a collection&#160;System.Web.Services.ServiceDescription instead of System.ServiceModel.Description.ServiceDescription. It took me a while to figure that out. [...]</description>
		<content:encoded><![CDATA[<p>[...] This&nbsp;popular&nbsp;blogpost&nbsp;provides a very simple&nbsp;endpoint behavior to flatten your WSDL and it works like a charm! Note that the WsdlExporter has a property GeneratedWsdlDocuments which returns a ServiceDescriptionCollection. The catch here is that this is a collection&nbsp;System.Web.Services.ServiceDescription instead of System.ServiceModel.Description.ServiceDescription. It took me a while to figure that out. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wenning Qiu</title>
		<link>http://winterdom.com/2006/10/inlinexsdinwsdlwithwcf/comment-page-1#comment-1013</link>
		<dc:creator>Wenning Qiu</dc:creator>
		<pubDate>Thu, 02 Jul 2009 21:07:45 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2006/10/inlinexsdinwsdlwithwcf#comment-1013</guid>
		<description>I don&#039;t think XSD imports should be removed. 

With XSD imports removed, if related data contracts(container DC and member DC) use different namespaces. WsdlImporter won&#039;t be able to import data contracts back using DataContractSerializer.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think XSD imports should be removed. </p>
<p>With XSD imports removed, if related data contracts(container DC and member DC) use different namespaces. WsdlImporter won&#8217;t be able to import data contracts back using DataContractSerializer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://winterdom.com/2006/10/inlinexsdinwsdlwithwcf/comment-page-1#comment-929</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Fri, 19 Jun 2009 14:56:32 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2006/10/inlinexsdinwsdlwithwcf#comment-929</guid>
		<description>I know this is an old article but the WSDL generated isn&#039;t correct when you check the flat WSDL the types are not declared the same.

Here is the flat version


 
   
   
   
   
   
   
  
  

Here is the WCF normal version


 
   
   
   
   
   
   
  


I think this is what is causing problems in my client with guids been treated as strings but though I would post.  Will give more feedback if I find out the reason behind this.</description>
		<content:encoded><![CDATA[<p>I know this is an old article but the WSDL generated isn&#8217;t correct when you check the flat WSDL the types are not declared the same.</p>
<p>Here is the flat version</p>
<p>Here is the WCF normal version</p>
<p>I think this is what is causing problems in my client with guids been treated as strings but though I would post.  Will give more feedback if I find out the reason behind this.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
