Defining LookAhead Using Native Schema Constructs

Native Format Builder Wizard 6-41 Native Data Format to Be Translated: Name1,2 Old Street, Old Town,Manchester,20-08-1954,0161-499-1718, YES Name2,2 Old Street, Old Town,Manchester,20-08-1954,0161-499-1718, NO Name3,2 Old Street, Old Town,Manchester,20-08-1954,0161-499-1718, NO Name4,2 Old Street, Old Town,Manchester,20-08-1954,0161-499-1718, YES Native Schema: ?xml version=1.0 encoding=US-ASCII? schema xmlns=http:www.w3.org2001XMLSchema xmlns:nxsd=http:xmlns.oracle.compcbpelnxsd targetNamespace=http:xmlns.oracle.compcbpelnxsdsmoketest elementFormDefault=qualified attributeFormDefault=unqualified nxsd:stream=chars nxsd:version=NXSD -- nxsd:lookAhead=70 nxsd:scan=3 -- element name=LookAhead complexType choice maxOccurs=unbounded nxsd:choiceCondition={x} nxsd:lookAhead=70 nxsd:scanLength=3 nxsd:assignTo={x} element name=Record1 type=string nxsd:conditionValue=YES nxsd:style=terminated nxsd:terminatedBy=, nxsd:skipMode=after nxsd:skipUntil={eol} element name=Record2 type=string nxsd:conditionValue=NO nxsd:style=terminated nxsd:terminatedBy=, nxsd:skipMode=after nxsd:skipUntil={eol} choice complexType element schema Translated XML Using Native Schema: LookAhead xmlns=http:xmlns.oracle.compcbpelnxsdsmoketest Record1Name1Record1 Record2Name2Record2 Record2Name3Record2 Record1Name4Record1 LookAhead

6.2.2.14 Defining outboundHeader

The actual content of outboundHeader can use variables, specifically {eol}. When headerLines and outboundHeader both are available, outboundHeader takes precedence in the outbound. Note: In the inbound direction, the Skipping Headers feature is supported. Only predefined variables can be used in a header because other variables might either not be accessible or would have only literals. 6-42 Oracle Fusion Middleware Users Guide for Technology Adapters Input XML: terminated xmlns=http:xmlns.oracle.compcbpelnxsdsmoketest PersonNameFredPersonName Address2 Old Street, Old Town,ManchesterAddress DOB20-08-1954DOB Telephone0161-499-1718Telephone terminated Native Schema: ?xml version=1.0 encoding=US-ASCII? schema xmlns=http:www.w3.org2001XMLSchema xmlns:nxsd=http:xmlns.oracle.compcbpelnxsd targetNamespace=http:xmlns.oracle.compcbpelnxsdsmoketest elementFormDefault=qualified attributeFormDefault=unqualified nxsd:stream=chars nxsd:version=NXSD nxsd:hasHeader=true nxsd:outboundHeader=This is a header {eol} element name=terminated complexType sequence element name=PersonName type=string nxsd:style=terminated nxsd:terminatedBy=, nxsd:quotedBy=quot; element name=Address type=string nxsd:style=terminated nxsd:terminatedBy=, nxsd:quotedBy=quot; element name=DOB type=string nxsd:style=terminated nxsd:terminatedBy=, nxsd:quotedBy= element name=Telephone type=string nxsd:style=terminated nxsd:terminatedBy={eol} nxsd:quotedBy= sequence complexType element schema Translated Data: This is a header Fred,2 Old Street, Old Town,Manchester,20-08-1954,0161-499-1718

6.2.2.15 Defining Complex Condition in conditionValue

When you use the conditionValue construct along with the choiceCondition construct, you can specify match criteria such as equals == and not equals =, along with the Boolean operators AND and OR, for comparison between the value read and the value specified in the conditionValue construct. Native Data Format to Be Translated: Order, ID41678, 20May2000 Item1, GigaWidget, 60, 75 Item2, MegaBucket, 48, 125 Cust1, Hopkins Associates, ID26490 Order, ID41680, 20May2000 Item3, Rt.Clopper, 40, 100