Defining Complex Condition in choiceCondition

Native Format Builder Wizard 6-45 Native Schema: 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 Translated XML Using Native Schema: LookAhead xmlns=http:xmlns.oracle.compcbpelnxsdsmoketest Record1Name1Record1 Record2Name2Record2 LookAhead

6.2.2.17 Defining dataLines

If the requirement is to translate only a portion of the data and not the entire data, then you can specify the number of lines to be ignored from the beginning of the file and the number of lines to be translated from that point onwards by using the dataLines construct. Native Data Format to Be Translated: Fred,addr,20-08-1954,0161-499-1718 Tam,addr,20-08-1954,0161-499-1718 Albert,addr,20-08-1954,0161-499-1718 Bill,addr,20-08-1954,0161-499-1718 Phil,addr,20-08-1954,0161-499-1718 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:headerLines=1 nxsd:dataLines=1 element name=terminated complexType sequence maxOccurs=unbounded element name=PersonName type=string nxsd:style=terminated nxsd:terminatedBy=, element name=Address type=string nxsd:style=terminated nxsd:terminatedBy=, 6-46 Oracle Fusion Middleware Users Guide for Technology Adapters element name=DOB type=string nxsd:style=terminated nxsd:terminatedBy=, element name=Telephone type=string nxsd:style=terminated nxsd:terminatedBy={eol} sequence complexType element schema Translated XML Using Native Schema: terminated xmlns=http:xmlns.oracle.compcbpelnxsdsmoketest PersonNameTamPersonName AddressaddrAddress DOB20-08-1954DOB Telephone0161-499-1718Telephone terminated

6.2.2.18 Defining Date Formats with Time Zone

In the translator, the date or time must be associated with a time zone. The translator supports the date formats with time zone for both, the date in native data and for the date in XML. There are two parts when translating a datetime string. First, the format of the date in the native data dateformat, second is the time zone to use when parsing that date timeZone or useTimeZone. The translator uses these details while parsing the datetime string. After the parsing, by default, the date string is converted to the ISO-8601 format in an XML. You can override the defaults by using XMLDateFormat and XMLTimeZone, or useTimeZone. Native Data Format to Be Translated: 111602241102 11-20-2002 23112002 01022003 01:02 01022003 03:04:05 Thu, 26 May 2005 15:50:11 India Standard Time Do, 26 Mai 2005 15:43:10 Indische Normalzeit 20063202 111602 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 element name=dateformat complexType