Chapter 14 - Creating WSDL Extensions
Our native language is like a second skin, so much a part of us we resist the idea that it is constantly changing, constantly being renewed.
Many languages are not static. They evolve and grow over time. For example, natural languages, such as English, continue to evolve and grow as new constructs, such as words, terms, and sentence structure, are added to the language or take on new meaning. Although all are written in English, Shakespeare's work is noticeably different from that of John Grisham or Margaret Atwood.
Just as natural languages may evolve, so too may computer languages. In the XML family of languages, the content of each element may be defined by a grammar, typically specified by a DTD or XML Schema (XSD). If the grammar limits the content to a fixed set of elements and attributes, the language is said to have a closed content model. For example, XSD itself has a closed content model. To add new content to XSD, you must put in it annotation elements.
In contrast, an XML language that allows new elements and attributes to be added is said to have an open content model. Web Service Description Language (WSDL) has an open content model. Elements and attributes may be added to the language at almost any level [WSDL11] (see Example 14.1).
Other Sections in This Chapter
- Creating the WSDL Extension Plug-in
- Extending the WSDL Editor
- Customizing the Look of Extensibility Elements in the Editor's Design View
- Adding Extensibility Elements to the Editor
- Adding Custom Actions to the WSDL Editor Design View
- Extending WSDL Validation
- Contributing to WSDL 1.1 Validation
- Contributing Custom Validation Rules