Dilip comments on TexMex and makes a couple of requests:
I'd love to see support for configuration based metadata as opposed to it being attribute based. The idea being, I'd rather not modify my services if I dont have to! * I'd like to see it reuse some of the service metadata that comes from the asmx model... i.e. http://uri/HelloWorld.asmx?wsdl
The first one shouldn't be too bad -- I'll see what I can do. I figure I will use an XmlSerializationSectionHandler-style implementation. (Then I will need to get Christian Weyer to let me integrate with WsContractFirst, so that the configuration is automatically generated :).
The second one is actually supported in the sense that you could add a MetadataLocation attribute referencing the ?WSDL doc url.
[MetadataLocation(Dialects.Wsdl11, "http://idontexist.com/my.asmx?wsdl", "urn:my-identifier")]
public class MyService
{
// impl
}
It is unfortunate that the url currently has to be hard-coded, which of course makes it difficult to use the same codebase in multiple environments - dev vs. prod. I may rework it to accept relative uris.
Additionally, I have been thinking about integrating ServiceDescriptionReflector - i.e. when initializing the MetadataService from the attributes, provide the service type so that the MetadataReference can reflect the description and/or schemas. I could also make it default to support that, I can check to see if documentation is turned on, and if so, auto-generate the wsdl. I would rather build the tool to encourage Contract-First, but it seems like a reasonable marriage of the default asp.net model and TexMex.
I have another cut of TexMex (1.5) coming out this afternoon that fleshes out the client and DTOs a bit. I will look into the latter request for 1.6 and the former for 1.7. Thanks for the feedback, Dilip!
Comments