OpenEdge Development: Working with XML - Product ...

More documents

Recommendations

Info

Developing with XML in OpenEdge About XML 1–2 The Extensible Markup Language (XML) is a data format used for exchanging structured data. The body of an XML document contains data and markup which encodes a description of the document’s logical structure. XML is hardware and software independent and is the most widely used markup language today. It is also the preferred standard for data exchange between heterogeneous applications. This section provides a quick overview of some essential XML information and concludes with some recommendations for getting more in-depth information about XML: • Role of XML • Benefits of XML • Benefits of ABL XML development in OpenEdge • Benefits of SOA XML development in OpenEdge • Recommended resources for learning XML basics Role of XML A great many of today's application developers must address interoperability between applications not initially designed to communicate with each other. Small and large enterprises both tackle the problem of coaxing multiple applications to work together to keep up with ever-evolving business processes. Interoperability challenges can require tying together different: • Hardware platforms • Operating systems • Data protocols • Commercial software applications • Local custom software applications So how can a developer create business processes that leverage the functionality distributed on different corporate computing assets and make them interoperate? Assuming the networking infrastructure is in place to access the required assets, the last essential task needed to achieve interoperability is data exchange. Data exchange requires communicating the values that represent business knowledge and the schema that describes those values. Both are needed to drive the business processes built by linking distributed software applications. Fortunately, the rise of the Internet has provided a universal, standards-driven platform to achieve interoperability between heterogeneous application assets within an enterprise or even among a larger circle of an enterprise and its business partners. The development of the Internet is being guided by many groups that all promote interoperability. For example, the World Wide Web Consortium (W3C) develops interoperability technologies for the web. To that end, this consortium approved a data exchange standard called the Extensible Markup Language or XML. A markup language is a data description standard that includes both data and markup in a single document. (In XML, you can think of the markup and data as being analogous to field name and field value pairs presented in a logical structure.)
About XML The W3C has also defined a companion standard to XML to provide rich schema definition for the elements of an XML document. This standard is known as XML Schema and it defines the means for defining the structure, content, and semantics of XML documents with much more detail. The language of XML Schema is known as the XML Schema Definition language (XSD). The combination of XML and XML Schema provides an easy, standards-based vehicle for tackling a very wide array of data exchange challenges. Since its introduction, XML has quickly grown to be the most widely-used markup language. XML makes it easy to describe data that must be used by more than one application. Its ease of use makes it a popular tool for data exchange in many scenarios, not just Internet applications. Any two applications that are XML-enabled can share data and schema. Benefits of XML Besides the fact that XML is a widely accepted standard, several other attributes of XML contribute to its rapid acceptance and growing popularity: • Most importantly, XML is extensible. An XML document can grow to include and describe more data, yet each application that uses the document need only be concerned with the XML content that matters to it. • XML is self-describing. The markup and hierarchical structure of the XML document can in some cases be interpreted by applications that do not know ahead of time what to expect from the document. • XML is simple text. This fact makes it suitable and safe for transferring across platforms and operating systems that do not readily share more complex document types. As text, XML can also be readily displayed and edited in simple editors. • XML is robust. It can describe any kind of data with the help of its associated schema-description languages. • XML is easy to learn, easy to read, and easy to understand. Benefits of ABL XML development in OpenEdge Some of the most immediately noticeable ways OpenEdge supports your XML development work include: • The standard installation of OpenEdge includes built in parsers for reading and writing XML. • The Procedure Editor automatically applies hierarchical whitespace formatting and color to make reading and scanning XML documents easy. • XML parser functionality is accessed using the familiar concepts of ABL objects, methods, and attributes. • ABL XML-enablement features are simple enough to quickly implement basic use cases and rich enough to support the implementation of more complex use cases. 1–3
Page 1 and 2: PROGRESS® PROGRESS® PROGRESS® 10
Page 3 and 4: Contents Preface . . . . . . . . .
Page 5 and 6: Contents 5. Reading and Writing XML
Page 7 and 8: Preface This Preface contains the f
Page 9 and 10: Using this manual Preface OpenEdge
Page 11 and 12: | ... Examples of syntax descriptio
Page 13 and 14: In this example, ASSIGN requires ei
Page 15 and 16: Third party acknowledgements OpenEd
Page 17 and 18: Preface OpenEdge includes http pack
Page 19 and 20: Preface OpenEdge includes Sonic sof
Page 21: Developing with XML in OpenEdge 1 T
Page 25 and 26: Recommended resources for learning
Page 27 and 28: ABL support ABL implements DOM with
Page 29 and 30: Developing XML-enabled ABL applicat
Page 31 and 32: Use cases Serializing ABL temp-tabl
Page 33 and 34: Reading and Writing XML with the Do
Page 35 and 36: DTDs and XML Schema documents XML t
Page 37 and 38: XML empty elements XML terminology
Page 39 and 40: The ABL DOM interface If you are an
Page 41 and 42: The ABL DOM interface Table 2-1 sho
Page 43 and 44: Setting node attributes and values
Page 45 and 46: Writing an XML file to a MEMPTR, a
Page 47 and 48: Loading an XML file from a MEMPTR R
Page 49 and 50: Reading XML input into ABL i-clone.
Page 51 and 52: Namespaces Namespaces When you have
Page 53 and 54: Internationalization Internationali
Page 55 and 56: Validation Validation You can valid
Page 57 and 58: Method and attribute summary Table
Page 59 and 60: Reading XML Documents with the Simp
Page 61 and 62: SAX-reader object Understanding ABL
Page 63 and 64: Understanding ABL SAX The following
Page 65 and 66: Understanding ABL SAX Table 3-3: SA
Page 67 and 68: Creating a SAX-attributes object Un
Page 69 and 70: Understanding ABL SAX A DTD might b
Page 71 and 72: Table 3-7 describes the effect of n
Page 73 and 74:
• A callback raises an error by u
Page 75 and 76:
Developing ABL SAX applications Mos
Page 77 and 78:
Developing ABL SAX applications i-s
Page 79 and 80:
Developing ABL SAX applications Tra
Page 81 and 82:
Page 83 and 84:
i-sax2.xml Developing ABL SAX appli
Page 85 and 86:
Page 87 and 88:
ABL SAX and WebSpeed i-saxe3s.p (2
Page 89 and 90:
ABL SAX and WebSpeed Note: If you m
Page 91 and 92:
SAX API reference This reference co
Page 93 and 94:
EndDocument Invoked when the XML pa
Page 95 and 96:
SAX API reference If validation is
Page 97 and 98:
memPointer SAX API reference Option
Page 99 and 100:
UnparsedEntityDecl SAX API referenc
Page 101 and 102:
Writing XML Documents with the Simp
Page 103 and 104:
SAX-writer overview Table 4-1: SAX-
Page 105 and 106:
Configuring a SAX-writer Configurin
Page 107 and 108:
Examples This section shows example
Page 109 and 110:
Envelope information example Exampl
Page 111 and 112:
Concurrently reading and writing XM
Page 113 and 114:
Examples sax-readwrite.p (2 of 2) /
Page 115 and 116:
Examples sax-readwrite2.p (2 of 2)
Page 117 and 118:
START-ELEMENT("name", "namespaceUri
Page 119 and 120:
DECLARE-NAMESPACE("namespaceUri", "
Page 121 and 122:
Handling errors Handling errors The
Page 123 and 124:
Handling errors Table 4-3: Common e
Page 125 and 126:
Handling errors Example of changing
Page 127 and 128:
Reading and Writing XML Data from T
Page 129 and 130:
Use cases Introduction The XML read
Page 131 and 132:
SERIALIZE-NAME 3 (Readable and writ
Page 133 and 134:
Methods and attributes • If NAMES
Page 135 and 136:
Reading XML Schema into a temp-tabl
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
ead-mode Reading XML into a temp-ta
Page 147 and 148:
verify-schema-mode Reading XML into
Page 149 and 150:
Reading XML into a temp-table, temp
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Here is a snippet of the XML file:
Page 157 and 158:
Page 159 and 160:
The following is the output for thi
Page 161 and 162:
Writing XML Schema from a temp-tabl
Page 163 and 164:
omit-initial-values Writing XML Sch
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
longchar Writing XML from a temp-ta
Page 171 and 172:
Writing XML from a temp-table, temp
Page 173 and 174:
Writing XML from a temp-table, temp
Page 175 and 176:
Minimizing XML document size Minimi
Page 177 and 178:
Minimizing XML document size A non-
Page 179 and 180:
Sample ProDataSet to XML round-trip
Page 181 and 182:
Sample ProDataSet to XML round-trip
Page 183 and 184:
Using XML Schema In the following e
Page 185 and 186:
Using XML Schema Using READ-XML( )
Page 187 and 188:
Representing temp-tables in XML Sch
Page 189 and 190:
Representing indexes in XML Schema
Page 191 and 192:
XML Schema and ABL Data Type Mappin
Page 193 and 194:
Default mappings from other XML Sch
Page 195 and 196:
ABL to IANA Code Page Mappings This
Page 197 and 198:
ABL to IANA code page mappings Tabl
Page 199 and 200:
Command and Utility Reference This
Page 201 and 202:
-fieldtypemapping { field-mapping-f
Page 203 and 204:
Index A ABL benefits of XML develop
Page 205 and 206:
NODE-VALUE-TO-LONGCHAR method 2-26
show all

OpenEdge Development: Working with XML - Product ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?