OpenEdge Development: Working with XML - Product ...

More documents

Recommendations

Info

Preface Purpose Audience Organization Preface–2 This book provides a central programming guide for OpenEdge® developers who need their ABL (Advanced Business Language) procedures to work with XML documents. This book is intended for ABL programmers working with XML documents in their ABL procedures. The book assumes that you have a basic working knowledge of XML. For advanced features, a basic working knowledge of XML Schema is also required. Chapter 1, “Developing with XML in OpenEdge” Provides an overview of the role of XML and the ABL features available for developing ABL applications that work with XML documents. Chapter 2, “Reading and Writing XML with the Document Object Model (DOM)” Describes ABL support for XML documents with DOM, including the receipt and processing of XML documents and the creation and transmission of XML documents. Chapter 3, “Reading XML Documents with the Simple API for XML (SAX)” Describes ABL support for reading documents with SAX and includes provides a reference for SAX callback procedures. Chapter 4, “Writing XML Documents with the Simple API for XML (SAX)” Describes ABL support for reading documents with SAX. Chapter 5, “Reading and Writing XML Data from Temp-Tables and ProDataSets” Describes how temp-tables and ProDataSets can serialize their data to an XML document and serialize their definitions to XML Schema documents. This chapter also describes how you can read or read and load XML data and schema into a temp-table or ProDataSet. Appendix A, “XML Schema and ABL Data Type Mappings,” Lists data type mappings needed to support ABL applications that interoperate with XML. Appendix B, “ABL to IANA Code Page Mappings,” Lists code page mappings needed to support ABL applications that interoperate with XML. Appendix C, “Command and Utility Reference” Describes the bproxsdto4gl utility.
Using this manual Preface OpenEdge provides a special purpose programming language for building business applications. In the documentation, the formal name for this language is ABL (Advanced Business Language). With few exceptions, all keywords of the language appear in all UPPERCASE, using a font that is appropriate to the context. All other alphabetic language content appears in mixed case. For the latest documentation updates see the OpenEdge Product Documentation Overview page on PSDN: http://communities.progress.com/pcom/docs/DOC-16074. References to ABL compiler and run-time features ABL is both a compiled and an interpreted language that executes in a run-time engine. The documentation refers to this run-time engine as the ABL Virtual Machine (AVM). When the documentation refers to ABL source code compilation, it specifies ABL or the compiler as the actor that manages compile-time features of the language. When the documentation refers to run-time behavior in an executing ABL program, it specifies the AVM as the actor that manages the specified run-time behavior in the program. For example, these sentences refer to the ABL compiler’s allowance for parameter passing and the AVM’s possible response to that parameter passing at run time: “ABL allows you to pass a dynamic temp-table handle as a static temp-table parameter of a method. However, if at run time the passed dynamic temp-table schema does not match the schema of the static temp-table parameter, the AVM raises an error.” The following sentence refers to run-time actions that the AVM can perform using a particular ABL feature: “The ABL socket object handle allows the AVM to connect with other ABL and non-ABL sessions using TCP/IP sockets.” References to ABL data types ABL provides built-in data types, built-in class data types, and user-defined class data types. References to built-in data types follow these rules: • Like most other keywords, references to specific built-in data types appear in all UPPERCASE, using a font that is appropriate to the context. No uppercase reference ever includes or implies any data type other than itself. • Wherever integer appears, this is a reference to the INTEGER or INT64 data type. • Wherever character appears, this is a reference to the CHARACTER, LONGCHAR, or CLOB data type. • Wherever decimal appears, this is a reference to the DECIMAL data type. • Wherever numeric appears, this is a reference to the INTEGER, INT64, or DECIMAL data type. References to built-in class data types appear in mixed case with initial caps, for example, Progress.Lang.Object. References to user-defined class data types appear in mixed case, as specified for a given application example. Preface–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: Preface This Preface contains the f
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 and 22: Developing with XML in OpenEdge 1 T
Page 23 and 24: About XML The W3C has also defined
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?