9

Closed

Include a Web Service DSL

description

This domain specific language should allow the user to define the service interface (operations) as well as the messages (message, data, and fault contracts) for the operations. The model should be able to be driven from WSDL and XSD files.
Closed May 12, 2007 at 6:36 AM by donsmith
Completed

comments

donsmith wrote Apr 25, 2007 at 9:05 PM

The Service Factory team has gotten this feedback a lot. So now you get to tell us why you want it. Do any of these statements represent why?
  • The model represents a logical (technology agnostic) service interface. This let's me:++ design the service and delay the technology (platform, language, ect) decision at the same time++ regenerate the code at anytime without any duplication of design work++ have more flexibility (agility) while designing the service interface, messages, etc.++ reduce coding errors since it is generated from the model+ The graphical representation also acts as enhanced documentation about the service
Are there other reasons why a graphical design surface would be good to have?

hastarin wrote Apr 25, 2007 at 9:05 PM

All of the above except code regeneration, though perhaps I misunderstand the point. A design surface that maps both ways, like the Class Designer, would be ideal.

Many designers/developers are highly visual people and being able to visualize the design can make a big difference to the speed and accuracy of development.