|
YOUR FEEDBACK
Did you read today's front page stories & breaking news?
SYS-CON.TV |
TODAY'S TOP SOA & WEBSERVICES LINKS Product Review Product Review: Altova Enterprise Suite 2005
XML development is a term that can mean many things to many different people
By: Brian Barbash
Aug. 19, 2005 03:45 AM
XML development is a term that can mean many things to many different people. For some, it is the modeling and creation of XML Schemas and instance documents used to exchange data. Others see it as a part of the larger effort of developing Web services. Still others view it as a means to transform and integrate systems whose data structures and definitions are proprietary. All of these types of development require various skills and tools.
XMLSpy The first things developers will notice in this iteration of XMLSpy are the simple but effective updates to the UI. For example, the text mode of the application is now collapsible by element in order to more easily manage large documents. Another nice change is the addition of an auto-hide capability to the Project, Info, Elements, Attributes, and Entities panels, providing a more efficient use of screen real estate.
The Details panel in Figure 1 provides access to the lower-level properties of the selected node such as type, cardinality, and reference information, among other characteristics. Once the XML Schema is modeled, the document may be validated against the latest W3C XML Schema specification simply by clicking the validate button on the toolbar. Documents are also validated when saved. If any errors exist, they are presented to the developer to correct. XML instance documents are modified in the Text and Grid views. The Text view is the standard text editor within XMLSpy, providing text folding capabilities, autocomplete, and syntax highlighting. The Grid view is useful for working with documents that contain repeating elements, such as the Properties node in the example above. In this view, XML is rendered in a table format that allows developers to view documents in rows and columns. Instance documents are similar to XML Schemas and may be validated if a schema is defined in the schemaLocation attribute of the root element, or if the DTD is defined in the DOCTYPE node. Developers may then validate the document either by clicking the validate button in the toolbar or saving the instance document. Any errors are presented on screen. XMLSpy and Web Services Modeling Web services, as with schemas, is mainly done in a graphical editor. The editor is logically broken into the main components of a WSDL document: Operations, PortTypes, Bindings, and Services. Each component allows a developer to graphically define and update the relevant properties. For example, adding input, output, and fault messages to an operation is as simple as selecting from a context menu and defining the message parts. XMLSpy may also serve as both a SOAP client and debugger. To act as a client, the WSDL of the service to be called is simply identified and a SOAP document is generated. Once the parameters of the call are set, the document may be sent to the service and the results are displayed. This capability is extremely useful for testing and debugging Web service applications. When acting as a SOAP debugger, XMLSpy becomes a proxy between the Web service client and the Web service itself. It provides the capability of establishing breakpoints within a SOAP document based on function calls or XPath query statements. Intercepted documents may be inspected and modified before they are forwarded to the service. Service results are then passed back to XMLSpy for inspection and/or modification before reaching the client. MapForce YOUR FEEDBACK
XML JOURNAL LATEST STORIES . . .
SUBSCRIBE TO THE WORLD'S MOST POWERFUL NEWSLETTERS SUBSCRIBE TO OUR RSS FEEDS & GET YOUR SYS-CON NEWS LIVE!
|
SYS-CON FEATURED WHITEPAPERS MOST READ THIS WEEK BREAKING XML NEWS
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||