Using xpath expressions in Document-Builder

Hi all
we have re-designed our (existing) DDX-templates with the Document Builder in LC Workbench. The DDX templates are used to assemble PDFs with LC Assembler-Service.
Now my question: Is it still possible to use XPath-expression in the DDX template? Please find our example below:
The XPath expression works only if we copy&paste the DDX source code directly to the Assembler-Service property view (picture below). But referring the DDX-template doens't interpret the xpath path at run time (2nd picture below). Any help on that will be appreciated!
Works (using DDX source code directly):
Doesn't work (using DDX template):

Hi,
>
I tried to get a portion of an XML by using XPath Expressions as follows:
String xPathExpression =
"declare namespace xq='http://inti.notariado.org/indices' " +
"$this/xq:RULES/xq:RULE[@disabled]";
I think any XPath expressions which use [] are not supported in stand alone
version, but as this is not documented I could be wrong.
Regards
Arek

Similar Messages

XPath Expression in document definition

I am trying to use "XPath Expression1" for 894 in the document definition under XPath in order to retrieve invoice number so that, it would be used in BAM but I am not getting successful in putting exact XPath expression for invoice number. I am using as below
/Transaction-894/Segment-G82/Element-861
Pls suggest is there any wrong in the XPath?
Regards,
Suneel Jakka

Here is the XSD for which I am trying XPath for the "Element-861" under "Segment-G82"..
Pls suggest me..
<?xml version="1.0" encoding="UTF-8"?>

<xsd:schema xmlns="http://www.edifecs.com/xdata/200" targetNamespace="http://www.edifecs.com/xdata/200" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.0" elementFormDefault="qualified">
 <xsd:annotation>
 <xsd:appinfo>
 <FileName>C:\Documents and Settings\jakkasun\Desktop\11g\X12_5010_894.ecs</FileName>
 <InternalID>{0840BE5F-3518-463D-A128-D73D96D4A5D2}</InternalID>
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:element name="Transaction-894" type="Transaction-894"/>
 <xsd:complexType name="Transaction-894">
 <xsd:annotation>
 <xsd:documentation>This X12 Transaction Set contains the format and establishes the data contents of the Delivery/Return Base Record Transaction Set (894) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to enable a Direct Store Delivery (DSD) vendor to communicate the details of a DSD delivery and is to be used during the check-in procedure. </xsd:documentation>
 <xsd:appinfo>
 <UNMKey>Full|CodeList|-<Parent Node ID>.<Index>|Composite|-<Node ID>|Element|-<Node ID>|Loop|-<Node ID>|Segment|-<Node ID>|Transaction|-<Node ID>|ReplacementCharacter|_|InternalSeparator|-</UNMKey>
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="Internal-Properties" type="Internal-Properties" minOccurs="0"/>
 <xsd:element name="Segment-ST" type="Segment-ST"/>
 <xsd:element name="Segment-G82" type="Segment-G82"/>
 <xsd:element name="Segment-N9" type="Segment-N9" minOccurs="0" maxOccurs="unbounded" nillable="true"/>
 <xsd:element name="Loop-LS" type="Loop-LS" minOccurs="0" nillable="true"/>
 <xsd:element name="Segment-G72" type="Segment-G72" minOccurs="0" maxOccurs="20" nillable="true"/>
 <xsd:element name="Segment-G23" type="Segment-G23" minOccurs="0" maxOccurs="20" nillable="true"/>
 <xsd:element name="Segment-G84" type="Segment-G84"/>
 <xsd:element name="Segment-G86" type="Segment-G86"/>
 <xsd:element name="Segment-G85" type="Segment-G85"/>
 <xsd:element name="Segment-SE" type="Segment-SE"/>
 </xsd:sequence>
 <xsd:attribute name="Type" default="Transaction" type="xsd:string"/>
 <xsd:attribute name="ID" default="894" type="xsd:string"/>
 <xsd:attribute name="Name" default="Delivery/Return Base Record" type="xsd:string"/>
 <xsd:attribute name="XDataVersion" fixed="2.0" type="xsd:string"/>
 <xsd:attribute name="Standard" fixed="X12" use="required" type="xsd:string"/>
 <xsd:attribute name="Version" default="V5010" type="xsd:string"/>
 <xsd:attribute name="GUID" type="GUID"/>
 <xsd:attribute name="CreatedBy" type="xsd:string"/>
 <xsd:attribute name="CreatedDate" type="xsd:dateTime"/>
 </xsd:complexType>
 <xsd:simpleType name="GUID">
 <xsd:restriction base="xsd:string">
 <xsd:pattern value="\{[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12}\}"/>
 </xsd:restriction>
 </xsd:simpleType>
 <xsd:complexType name="EDI-Element-String-Type">
 <xsd:simpleContent>
 <xsd:extension base="xsd:string">
 <xsd:attribute name="Type" default="Element" type="xsd:string"/>
 <xsd:attribute name="EDIDataType" type="xsd:string"/>
 <xsd:attribute name="Macro" type="xsd:string" use="optional"/>
 <xsd:attribute name="ApplicationInfo" type="xsd:string"/>
 <xsd:attribute name="ID" type="xsd:string"/>
 <xsd:attribute name="Name" type="xsd:string"/>
 </xsd:extension>
 </xsd:simpleContent>
 </xsd:complexType>
 <xsd:complexType name="EDI-Element-Integer-Type">
 <xsd:simpleContent>
 <xsd:extension base="xsd:integer">
 <xsd:attribute name="Type" default="Element" type="xsd:string"/>
 <xsd:attribute name="EDIDataType" type="xsd:string"/>
 <xsd:attribute name="Macro" type="xsd:string" use="optional"/>
 <xsd:attribute name="ApplicationInfo" type="xsd:string"/>
 <xsd:attribute name="ID" type="xsd:string"/>
 <xsd:attribute name="Name" type="xsd:string"/>
 </xsd:extension>
 </xsd:simpleContent>
 </xsd:complexType>
 <xsd:complexType name="EDI-Element-Decimal-Type">
 <xsd:simpleContent>
 <xsd:extension base="xsd:decimal">
 <xsd:attribute name="Type" default="Element" type="xsd:string"/>
 <xsd:attribute name="EDIDataType" type="xsd:string"/>
 <xsd:attribute name="Macro" type="xsd:string" use="optional"/>
 <xsd:attribute name="ApplicationInfo" type="xsd:string"/>
 <xsd:attribute name="ID" type="xsd:string"/>
 <xsd:attribute name="Name" type="xsd:string"/>
 </xsd:extension>
 </xsd:simpleContent>
 </xsd:complexType>
 <xsd:complexType name="EDI-Element-hexBinary-Type">
 <xsd:simpleContent>
 <xsd:extension base="xsd:hexBinary">
 <xsd:attribute name="Type" default="Element" type="xsd:string"/>
 <xsd:attribute name="EDIDataType" type="xsd:string"/>
 <xsd:attribute name="Macro" type="xsd:string" use="optional"/>
 <xsd:attribute name="ApplicationInfo" type="xsd:string"/>
 <xsd:attribute name="ID" type="xsd:string"/>
 <xsd:attribute name="Name" type="xsd:string"/>
 </xsd:extension>
 </xsd:simpleContent>
 </xsd:complexType>
 <xsd:complexType name="EDI-Element-base64Binary-Type">
 <xsd:simpleContent>
 <xsd:extension base="xsd:base64Binary">
 <xsd:attribute name="Type" default="Element" type="xsd:string"/>
 <xsd:attribute name="EDIDataType" type="xsd:string"/>
 <xsd:attribute name="Macro" type="xsd:string" use="optional"/>
 <xsd:attribute name="ApplicationInfo" type="xsd:string"/>
 <xsd:attribute name="ID" type="xsd:string"/>
 <xsd:attribute name="Name" type="xsd:string"/>
 </xsd:extension>
 </xsd:simpleContent>
 </xsd:complexType>
 <xsd:complexType name="EDI-Element-Any-Type">
 <xsd:simpleContent>
 <xsd:extension base="xsd:string">
 <xsd:attribute name="Type" default="Element" type="xsd:string"/>
 <xsd:attribute name="EDIDataType" type="xsd:string"/>
 <xsd:attribute name="Macro" type="xsd:string" use="optional"/>
 <xsd:attribute name="ApplicationInfo" type="xsd:string"/>
 <xsd:attribute name="ID" type="xsd:string"/>
 <xsd:attribute name="Name" type="xsd:string"/>
 </xsd:extension>
 </xsd:simpleContent>
 </xsd:complexType>
 <xsd:complexType name="Internal-Properties">
 <xsd:sequence>
 <xsd:element name="Data-Structure" type="Data-Structure" minOccurs="0" maxOccurs="unbounded"/>
 </xsd:sequence>
 </xsd:complexType>
 <xsd:complexType name="Data-Structure">
 <xsd:sequence>
 <xsd:element name="Lookup" type="Lookup" minOccurs="0" maxOccurs="unbounded"/>
 <xsd:element name="Property" type="Property" minOccurs="0" maxOccurs="unbounded"/>
 <xsd:element name="Data-Structure" type="Data-Structure" minOccurs="0" maxOccurs="unbounded"/>
 </xsd:sequence>
 <xsd:attribute name="Name" type="xsd:string"/>
 <xsd:attribute name="GUID" type="GUID"/>
 </xsd:complexType>
 <xsd:complexType name="Lookup">
 <xsd:simpleContent>
 <xsd:extension base="xsd:string">
 <xsd:attribute name="Name" type="xsd:string"/>
 </xsd:extension>
 </xsd:simpleContent>
 </xsd:complexType>
 <xsd:complexType name="Property">
 <xsd:simpleContent>
 <xsd:extension base="xsd:string">
 <xsd:attribute name="Name" type="xsd:string"/>
 </xsd:extension>
 </xsd:simpleContent>
 </xsd:complexType>
 <xsd:complexType name="Segment-ST">
 <xsd:annotation>
 <xsd:documentation>To indicate the start of a transaction set and to assign a control number</xsd:documentation>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="Element-143" type="Element-143"/>
 <xsd:element name="Element-329" type="Element-329"/>
 <xsd:element name="Element-1705" type="Element-1705" minOccurs="0" nillable="true"/>
 </xsd:sequence>
 <xsd:attribute name="Type" default="Segment" type="xsd:string"/>
 <xsd:attribute name="ID" default="ST" type="xsd:string"/>
 <xsd:attribute name="Name" default="Transaction Set Header" type="xsd:string"/>
 </xsd:complexType>
 <xsd:complexType name="Element-143">
 <xsd:annotation>
 <xsd:documentation>Code uniquely identifying a Transaction Set </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleContent>
 <xsd:restriction base="EDI-Element-String-Type">
 <xsd:enumeration value="100"/>
 <xsd:enumeration value="101"/>
 <xsd:enumeration value="102"/>
 <xsd:enumeration value="103"/>
 <xsd:enumeration value="104"/>
 <xsd:enumeration value="105"/>
 <xsd:enumeration value="106"/>
 <xsd:enumeration value="107"/>
 <xsd:enumeration value="108"/>
 <xsd:enumeration value="109"/>
 <xsd:enumeration value="110"/>
 <xsd:enumeration value="111"/>
 <xsd:enumeration value="112"/>
 <xsd:enumeration value="113"/>
 <xsd:enumeration value="120"/>
 <xsd:enumeration value="121"/>
 <xsd:enumeration value="124"/>
 <xsd:enumeration value="125"/>
 <xsd:enumeration value="126"/>
 <xsd:enumeration value="127"/>
 <xsd:enumeration value="128"/>
 <xsd:enumeration value="129"/>
 <xsd:enumeration value="130"/>
 <xsd:enumeration value="131"/>
 <xsd:enumeration value="132"/>
 <xsd:enumeration value="133"/>
 <xsd:enumeration value="135"/>
 <xsd:enumeration value="138"/>
 <xsd:enumeration value="139"/>
 <xsd:enumeration value="140"/>
 <xsd:enumeration value="141"/>
 <xsd:enumeration value="142"/>
 <xsd:enumeration value="143"/>
 <xsd:enumeration value="144"/>
 <xsd:enumeration value="146"/>
 <xsd:enumeration value="147"/>
 <xsd:enumeration value="148"/>
 <xsd:enumeration value="149"/>
 <xsd:enumeration value="150"/>
 <xsd:enumeration value="151"/>
 <xsd:enumeration value="152"/>
 <xsd:enumeration value="153"/>
 <xsd:enumeration value="154"/>
 <xsd:enumeration value="155"/>
 <xsd:enumeration value="157"/>
 <xsd:enumeration value="158"/>
 <xsd:enumeration value="159"/>
 <xsd:enumeration value="160"/>
 <xsd:enumeration value="161"/>
 <xsd:enumeration value="163"/>
 <xsd:enumeration value="170"/>
 <xsd:enumeration value="175"/>
 <xsd:enumeration value="176"/>
 <xsd:enumeration value="179"/>
 <xsd:enumeration value="180"/>
 <xsd:enumeration value="185"/>
 <xsd:enumeration value="186"/>
 <xsd:enumeration value="187"/>
 <xsd:enumeration value="188"/>
 <xsd:enumeration value="189"/>
 <xsd:enumeration value="190"/>
 <xsd:enumeration value="191"/>
 <xsd:enumeration value="194"/>
 <xsd:enumeration value="195"/>
 <xsd:enumeration value="196"/>
 <xsd:enumeration value="197"/>
 <xsd:enumeration value="198"/>
 <xsd:enumeration value="199"/>
 <xsd:enumeration value="200"/>
 <xsd:enumeration value="201"/>
 <xsd:enumeration value="202"/>
 <xsd:enumeration value="203"/>
 <xsd:enumeration value="204"/>
 <xsd:enumeration value="205"/>
 <xsd:enumeration value="206"/>
 <xsd:enumeration value="210"/>
 <xsd:enumeration value="211"/>
 <xsd:enumeration value="212"/>
 <xsd:enumeration value="213"/>
 <xsd:enumeration value="214"/>
 <xsd:enumeration value="215"/>
 <xsd:enumeration value="216"/>
 <xsd:enumeration value="217"/>
 <xsd:enumeration value="219"/>
 <xsd:enumeration value="220"/>
 <xsd:enumeration value="222"/>
 <xsd:enumeration value="223"/>
 <xsd:enumeration value="224"/>
 <xsd:enumeration value="225"/>
 <xsd:enumeration value="227"/>
 <xsd:enumeration value="228"/>
 <xsd:enumeration value="240"/>
 <xsd:enumeration value="242"/>
 <xsd:enumeration value="244"/>
 <xsd:enumeration value="245"/>
 <xsd:enumeration value="248"/>
 <xsd:enumeration value="249"/>
 <xsd:enumeration value="250"/>
 <xsd:enumeration value="251"/>
 <xsd:enumeration value="252"/>
 <xsd:enumeration value="255"/>
 <xsd:enumeration value="256"/>
 <xsd:enumeration value="259"/>
 <xsd:enumeration value="260"/>
 <xsd:enumeration value="261"/>
 <xsd:enumeration value="262"/>
 <xsd:enumeration value="263"/>
 <xsd:enumeration value="264"/>
 <xsd:enumeration value="265"/>
 <xsd:enumeration value="266"/>
 <xsd:enumeration value="267"/>
 <xsd:enumeration value="268"/>
 <xsd:enumeration value="269"/>
 <xsd:enumeration value="270"/>
 <xsd:enumeration value="271"/>
 <xsd:enumeration value="272"/>
 <xsd:enumeration value="273"/>
 <xsd:enumeration value="274"/>
 <xsd:enumeration value="275"/>
 <xsd:enumeration value="276"/>
 <xsd:enumeration value="277"/>
 <xsd:enumeration value="278"/>
 <xsd:enumeration value="280"/>
 <xsd:enumeration value="283"/>
 <xsd:enumeration value="284"/>
 <xsd:enumeration value="285"/>
 <xsd:enumeration value="286"/>
 <xsd:enumeration value="288"/>
 <xsd:enumeration value="290"/>
 <xsd:enumeration value="300"/>
 <xsd:enumeration value="301"/>
 <xsd:enumeration value="303"/>
 <xsd:enumeration value="304"/>
 <xsd:enumeration value="309"/>
 <xsd:enumeration value="310"/>
 <xsd:enumeration value="311"/>
 <xsd:enumeration value="312"/>
 <xsd:enumeration value="313"/>
 <xsd:enumeration value="315"/>
 <xsd:enumeration value="317"/>
 <xsd:enumeration value="319"/>
 <xsd:enumeration value="322"/>
 <xsd:enumeration value="323"/>
 <xsd:enumeration value="324"/>
 <xsd:enumeration value="325"/>
 <xsd:enumeration value="326"/>
 <xsd:enumeration value="350"/>
 <xsd:enumeration value="352"/>
 <xsd:enumeration value="353"/>
 <xsd:enumeration value="354"/>
 <xsd:enumeration value="355"/>
 <xsd:enumeration value="356"/>
 <xsd:enumeration value="357"/>
 <xsd:enumeration value="358"/>
 <xsd:enumeration value="361"/>
 <xsd:enumeration value="362"/>
 <xsd:enumeration value="404"/>
 <xsd:enumeration value="410"/>
 <xsd:enumeration value="412"/>
 <xsd:enumeration value="414"/>
 <xsd:enumeration value="417"/>
 <xsd:enumeration value="418"/>
 <xsd:enumeration value="419"/>
 <xsd:enumeration value="420"/>
 <xsd:enumeration value="421"/>
 <xsd:enumeration value="422"/>
 <xsd:enumeration value="423"/>
 <xsd:enumeration value="424"/>
 <xsd:enumeration value="425"/>
 <xsd:enumeration value="426"/>
 <xsd:enumeration value="429"/>
 <xsd:enumeration value="431"/>
 <xsd:enumeration value="432"/>
 <xsd:enumeration value="433"/>
 <xsd:enumeration value="434"/>
 <xsd:enumeration value="435"/>
 <xsd:enumeration value="436"/>
 <xsd:enumeration value="437"/>
 <xsd:enumeration value="440"/>
 <xsd:enumeration value="451"/>
 <xsd:enumeration value="452"/>
 <xsd:enumeration value="453"/>
 <xsd:enumeration value="455"/>
 <xsd:enumeration value="456"/>
 <xsd:enumeration value="460"/>
 <xsd:enumeration value="463"/>
 <xsd:enumeration value="466"/>
 <xsd:enumeration value="468"/>
 <xsd:enumeration value="470"/>
 <xsd:enumeration value="475"/>
 <xsd:enumeration value="485"/>
 <xsd:enumeration value="486"/>
 <xsd:enumeration value="490"/>
 <xsd:enumeration value="492"/>
 <xsd:enumeration value="494"/>
 <xsd:enumeration value="500"/>
 <xsd:enumeration value="501"/>
 <xsd:enumeration value="503"/>
 <xsd:enumeration value="504"/>
 <xsd:enumeration value="511"/>
 <xsd:enumeration value="517"/>
 <xsd:enumeration value="521"/>
 <xsd:enumeration value="527"/>
 <xsd:enumeration value="536"/>
 <xsd:enumeration value="540"/>
 <xsd:enumeration value="561"/>
 <xsd:enumeration value="567"/>
 <xsd:enumeration value="568"/>
 <xsd:enumeration value="601"/>
 <xsd:enumeration value="602"/>
 <xsd:enumeration value="620"/>
 <xsd:enumeration value="625"/>
 <xsd:enumeration value="650"/>
 <xsd:enumeration value="715"/>
 <xsd:enumeration value="753"/>
 <xsd:enumeration value="754"/>
 <xsd:enumeration value="805"/>
 <xsd:enumeration value="806"/>
 <xsd:enumeration value="810"/>
 <xsd:enumeration value="811"/>
 <xsd:enumeration value="812"/>
 <xsd:enumeration value="813"/>
 <xsd:enumeration value="814"/>
 <xsd:enumeration value="815"/>
 <xsd:enumeration value="816"/>
 <xsd:enumeration value="818"/>
 <xsd:enumeration value="819"/>
 <xsd:enumeration value="820"/>
 <xsd:enumeration value="821"/>
 <xsd:enumeration value="822"/>
 <xsd:enumeration value="823"/>
 <xsd:enumeration value="824"/>
 <xsd:enumeration value="826"/>
 <xsd:enumeration value="827"/>
 <xsd:enumeration value="828"/>
 <xsd:enumeration value="829"/>
 <xsd:enumeration value="830"/>
 <xsd:enumeration value="831"/>
 <xsd:enumeration value="832"/>
 <xsd:enumeration value="833"/>
 <xsd:enumeration value="834"/>
 <xsd:enumeration value="835"/>
 <xsd:enumeration value="836"/>
 <xsd:enumeration value="837"/>
 <xsd:enumeration value="838"/>
 <xsd:enumeration value="839"/>
 <xsd:enumeration value="840"/>
 <xsd:enumeration value="841"/>
 <xsd:enumeration value="842"/>
 <xsd:enumeration value="843"/>
 <xsd:enumeration value="844"/>
 <xsd:enumeration value="845"/>
 <xsd:enumeration value="846"/>
 <xsd:enumeration value="847"/>
 <xsd:enumeration value="848"/>
 <xsd:enumeration value="849"/>
 <xsd:enumeration value="850"/>
 <xsd:enumeration value="851"/>
 <xsd:enumeration value="852"/>
 <xsd:enumeration value="853"/>
 <xsd:enumeration value="854"/>
 <xsd:enumeration value="855"/>
 <xsd:enumeration value="856"/>
 <xsd:enumeration value="857"/>
 <xsd:enumeration value="858"/>
 <xsd:enumeration value="859"/>
 <xsd:enumeration value="860"/>
 <xsd:enumeration value="861"/>
 <xsd:enumeration value="862"/>
 <xsd:enumeration value="863"/>
 <xsd:enumeration value="864"/>
 <xsd:enumeration value="865"/>
 <xsd:enumeration value="866"/>
 <xsd:enumeration value="867"/>
 <xsd:enumeration value="868"/>
 <xsd:enumeration value="869"/>
 <xsd:enumeration value="870"/>
 <xsd:enumeration value="871"/>
 <xsd:enumeration value="872"/>
 <xsd:enumeration value="873"/>
 <xsd:enumeration value="874"/>
 <xsd:enumeration value="875"/>
 <xsd:enumeration value="876"/>
 <xsd:enumeration value="877"/>
 <xsd:enumeration value="878"/>
 <xsd:enumeration value="879"/>
 <xsd:enumeration value="880"/>
 <xsd:enumeration value="881"/>
 <xsd:enumeration value="882"/>
 <xsd:enumeration value="883"/>
 <xsd:enumeration value="884"/>
 <xsd:enumeration value="885"/>
 <xsd:enumeration value="886"/>
 <xsd:enumeration value="887"/>
 <xsd:enumeration value="888"/>
 <xsd:enumeration value="889"/>
 <xsd:enumeration value="891"/>
 <xsd:enumeration value="893"/>
 <xsd:enumeration value="894"/>
 <xsd:enumeration value="895"/>
 <xsd:enumeration value="896"/>
 <xsd:enumeration value="920"/>
 <xsd:enumeration value="924"/>
 <xsd:enumeration value="925"/>
 <xsd:enumeration value="926"/>
 <xsd:enumeration value="928"/>
 <xsd:enumeration value="940"/>
 <xsd:enumeration value="943"/>
 <xsd:enumeration value="944"/>
 <xsd:enumeration value="945"/>
 <xsd:enumeration value="947"/>
 <xsd:enumeration value="980"/>
 <xsd:enumeration value="990"/>
 <xsd:enumeration value="993"/>
 <xsd:enumeration value="996"/>
 <xsd:enumeration value="997"/>
 <xsd:enumeration value="998"/>
 <xsd:enumeration value="999"/>
 <xsd:attribute name="EDIDataType" fixed="ID" type="xsd:string"/>
 <xsd:attribute name="ID" fixed="143" type="xsd:string"/>
 <xsd:attribute name="Name" fixed="Transaction Set Identifier Code" type="xsd:string"/>
 </xsd:restriction>
 </xsd:simpleContent>
 </xsd:complexType>
 <xsd:complexType name="Element-329">
 <xsd:annotation>
 <xsd:documentation>Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleContent>
 <xsd:restriction base="EDI-Element-String-Type">
 <xsd:minLength value="4"/>
 <xsd:maxLength value="9"/>
 <xsd:attribute name="EDIDataType" fixed="AN" type="xsd:string"/>
 <xsd:attribute name="ID" fixed="329" type="xsd:string"/>
 <xsd:attribute name="Name" fixed="Transaction Set Control Number" type="xsd:string"/>
 </xsd:restriction>
 </xsd:simpleContent>
 </xsd:complexType>
 <xsd:complexType name="Element-1705">
 <xsd:annotation>
 <xsd:documentation>Reference assigned to identify Implementation Convention </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleContent>
 <xsd:restriction base="EDI-Element-String-Type">
 <xsd:minLength value="1"/>
 <xsd:maxLength value="35"/>
 <xsd:attribute name="EDIDataType" fixed="AN" type="xsd:string"/>
 <xsd:attribute name="ID" fixed="1705" type="xsd:string"/>
 <xsd:attribute name="Name" fixed="Implementation Convention Reference" type="xsd:string"/>
 </xsd:restriction>
 </xsd:simpleContent>
 </xsd:complexType>
 <xsd:complexType name="Segment-G82">
 <xsd:annotation>
 <xsd:documentation>To transmit identifying numbers, dates, and other basic data relating to the transaction set</xsd:documentation>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="Element-478" type="Element-478"/>
 <xsd:element name="Element-861" type="Element-861"/>
 <xsd:element name="Element-860" type="Element-860"/>
Regards,
Suneel Jakka

Using XPath to create Document node

Hi, could anyone suggest how to create Document nodes using xpaths with the help of some api (dom4j, JAXP, etc)?
For example:
With xpath="//A/B", I need to produce:
<A>
.. 
</A>
XPath is usually used for querying XML document, but now I need to do the reverse.
Thanks.

DrClap, thanks for your reply.
Yes, the topic title is a bit misleading. I shouldn't call it "Document" node.
"And you have an XPath expression of a very restricted form which is supposed to describe the structure of that document."
Not really, what I have is a bunch of xpath expressions, each of them describe a element in a xml.
With these xpath expressions, in the end of the day I need to create a xml document with these elements.
For example, if I have
//A/B
//A/C
//A/D
I need to create a xml like this:
<A>
 ...
<C>....</C>
<D>.....</D>
</A>
While I could do this in a manual way (creating each element from the root and adding children one by one....), I'm sure dom4j (or other packages) can do this but I couldn't find how.

Help Page Error: Using XPath expressions as list indexes and map keys

The help page says for maps to use the XPath expression
/process_data/mapvar[@id='/process_data/@stringvar']
But in reality for things to work you have to omit the quotations.

thanks a lot for your help..
there are total 162 records in the v$open_cursor for that user.
among that the open cursor is only 4 and open-recursive cursor is only 6 for that user.
in my session i am executing only the renaming of the constraints and nothing more.
When i have queried the v$open_cursor for cursor_type='OPEN' for all the users, then i got that it has exceeded the value of open_cursors parameter.
So how can i resolve that....

Using xpath-expressions inside Task Instructions

Hi all,
I have a process where I would like to build up the task Instructions in a string variable. However I cannot seem to resolve xpath values when I am putting my string as the task instruction.
How can I do this?
Thanks in advance
Sincerely
Kim Christensen

Hi again Marcel - thanks for your quick reply
However I am not sure I und erstand your answer correctly.
I have a string variable (str_Inctructions) that I want to set as my Task Instruction.
So at a point in my process I create a set value with an expression like this:
str_Instructions = 'Here are some instructions for {$/process_data/myOtherVar$} please follow them.'
I then set str_Instructions as the Task Instructions (an xpath-expression). When I get the Task in Workspace I see the {$/process_data/myOthervariable$} instead of the value of myOtherVar.
So how can I get the value of myOtherVar?

OWSM - Signing element using XPATH Expression

Hi,
We have a requirement to sign an element within outgoing body of xml message. We are trying to use the policy pipeline to sign.
Signed Content: XPATH
sign XPATH Expression: referencing the element required to be signed.
We get the error: WS-Security process failure:There are no parts of the message to sign
The error message indicates that the XPATH query is not correct. Does anyone know of a source of documentation for this where we can get examples. Tried google, forums...etc with no success. Any help would be really appreciated.
Thanks

Hi,
Managed to sort it, found the following link.
http://download-uk.oracle.com/docs/cd/B31017_01/integrate.1013/b31008/toc.htm
Thanks

Displaying XML using XPath expressions

Hi. I have a XML file which looks something like this:
<?xml version="1.0"?>
<SAQ>
<question id="1">
What does UML stand for?
<answer id="1" correct="yes">
Unified Modelling Language
<explanation>
Explanation
</explanation>
</answer>
<answer id="2" correct="no">
United Modelling Language
<explanation>
Wrong
</explanation>
</answer>
</question>
I want to just display the Question, not the child Answer and Explantion nodes under it, but when I use:
<c:set var="temp" value="1" />
<x:out select="$doc//SAQ//question[@id = $temp]" />
it displays:
What does UML stand for? Unified Modelling Language Explanation United Modelling Language Wrong
How do I just display the parent question node and not its child answer and explanation nodes?
Thanks!

use the text() xpath function it should work:
<x:out select="$doc//SAQ//question[@id = $temp]/text()" />

Using XPath expressions

Hi,
Currently, the support for queries in the standalone version of XmlBeans is
somewhat limited. However, is there a sensible way to query the XML
directly and then map the results back to XmlObjects? Presumably this is
what happens at some level anyway. For example, a DOM node could easily be
obtained from the relevant XmlObject and passed to the selectNodeList()
method of the org.apache.xpath.XPathAPI class. This would return a
org.w3c.dom.NodeList object. The question would then be how to map the DOM
nodes in the NodeList back to the corresponding XmlObjects in the object
model. Presumably, there wouldn't be any equivalence between the Nodes in
the NodeList and the Nodes returned by the newDomNode() method in XmlObject?
Would this also be possible by querying an XmlCursor?
Steve

Hi,
Currently, the support for queries in the standalone version of XmlBeans is
somewhat limited. However, is there a sensible way to query the XML
directly and then map the results back to XmlObjects? Presumably this is
what happens at some level anyway. For example, a DOM node could easily be
obtained from the relevant XmlObject and passed to the selectNodeList()
method of the org.apache.xpath.XPathAPI class. This would return a
org.w3c.dom.NodeList object. The question would then be how to map the DOM
nodes in the NodeList back to the corresponding XmlObjects in the object
model. Presumably, there wouldn't be any equivalence between the Nodes in
the NodeList and the Nodes returned by the newDomNode() method in XmlObject?
Would this also be possible by querying an XmlCursor?
Steve

How to retrieve value of attribute using xPath ?

Hello experts,
I have a following xml chunk
<image file="/articles/engineering/boxerengine/preview_282x160.jpg">
<tout name="copyright"></tout>
<tout name="license"></tout>
<tout name="photographer"></tout>
<tout name="description"></tout>
</image>
I want to retrieve value of attribute file from absolute node image.
I tried using xpath='/image/@file' It gives output as file="/articles/engineering/boxerengine/preview_282x160.jpg"
I just want value "/articles/engineering/boxerengine/preview_282x160.jpg"
I tried using xpath='/image/@file/text()' . It does not work
Following is the java code. I am using XOM parser.
java code :
Builder parser = new Builder();
Document doc = parser.build(xmlFile);
Nodes titles = doc.query(xPath);
//xpath = ''/image/@file/text()"
for (int i = 0; i < titles.size(); i++) {
strChunk = strChunk.append(titles.get(i).toXML());
return strChunk.toString();
Please help.
Thanks,
Sandeep Parmar

Hi Sandeep,
Using XPath and XPathExpression you can evaluate XPath queries on Document. have a look at code given bellow:
// Building Document from XML File
org.w3c.dom.Document imageDoc = builder.parse(xmlFile);
// getting new instance of XPath
javax.xml.xpath.XPath xpath = javax.xml.xpath.XPathFactory.newInstance().newXPath();
// Building XPathExpression by compiling XPath query
javax.xml.xpath.XPathExpression xPathExp = xpath.compile("/image/@file");
// Evaluting XPath Expression on Document
String imagePath = (String) xPathExp.evaluate(imageDoc, javax.xml.xpath.XPathConstants.STRING);
// Priting image path it will print : "/articles/engineering/boxerengine/preview_282x160.jpg", if you try with data given in your post.
System.out.println(imagePath); Hope this will help.
thanks,
Tejas Purohit

Oracle OES: Possible to use XPath wildcards in OES authorization policies?

Hi,
I have policies to authorize WS-requests using OES through OWSM.
In the OES policies I retrieve attributes from the WS-request using XPath expressions.
When I use namespace in my XPath it all works well:
NAMESPACE tns=http://myns/
myAttr //tns:myVal
But I have several WS-requests that have different namespaces, but that i need to authorize using the same policy, so I would like to use a wildcard for the namespace. But when I try the attribute retriever doesn't find the node value:
myAttr //*:myVal
When i use tools to check the XPath, like SoapUI, I am able to get the node value using the expression above.
Does anyone have experience using XPath wildcards in OES policies?
-T

I understand that the LDAP structure design depends on the business goals and requirements and we are defnitely building the schema in that lines. But the thing we want to make sure is how flexible are the products like OIM, OAM and OES to provide user authentication(if the user is deep down in the tree), authorization (if the user needs to be authorized to services having attributes deep down in the tree), mapping complex relationships and permissions in conjunction with OID.
I think the other way of asking this question would be what we should take into consideration while designing the LDAP structure in OID as the backend LDAP store and what things we should leave whille designing LDAP structure in OID that could be considered while designing the authentication, authorization process in OIM, OAM and OES.
Our goal is to keep the LDAP structure simple and flexible but at the sametime use OAM, OES and OIM at their best capabilities to serve our purpose without lot of customizations required.
Thanks!

XPath expressions in XmlCursor / XmlObjects

Hi all,
I tried to get a portion of an XML by using XPath Expressions as follows:
String xPathExpression =
"declare namespace xq='http://inti.notariado.org/indices' " +
"$this/xq:RULES/xq:RULE[@disabled]";
A simple example of an xml
<rules>
<rule disabled="true">hello</rule>
<rule>hello</rule>
</rules>
It should return one node, but actually it returns nothing. If I use another one:
String xPathExpression =
"declare namespace xq='http://inti.notariado.org/indices' " +
"$this/xq:RULES/xq:RULE";
Then I get two nodes (which is correct). It seems to me a bug or a partial support
for XPath expressions. Or maybe I am using a bad syntax, anyone can help?
Thanks in advance !

Hi,
>
I tried to get a portion of an XML by using XPath Expressions as follows:
String xPathExpression =
"declare namespace xq='http://inti.notariado.org/indices' " +
"$this/xq:RULES/xq:RULE[@disabled]";
I think any XPath expressions which use [] are not supported in stand alone
version, but as this is not documented I could be wrong.
Regards
Arek

How to use XPath in the adapter framework

I am creating a XI adapter to our system.
In the adapter I want to use XPath expression.
I use the classes from javax.xml.xpath.*
This way does not work in the XI application server. (Java 1.4.2)
What is the correct way? Which packages/classes must be used?
Miklos

Hi Miklos,
The package javax.xml.xpath was introduced with Java 5 (1.5), thus it is not available in XI which runs Java 1.4.2. There are (at least) a couple of ways to use XPath in Java 1.4:
1. Use a third-party library that supports XPath, for instance Xalan-J from Apache.
2. Embed your XPath expression in an XSLT transformation, execute the transformation using classes from the javax.xml.tranform... packages (which are part 1.4) and extract the result.
Cheers,
Thorsten

C++ sample code using XPATH

Need to navigate an XML and extract xml nodes using XPATH expressions in C++ Application.
Please send us a C++ code sample using Oracle 9.2.0.3 XPATH API functions to extract an XML using XPATH expression.
Thanks
Shiva

Hi,
Where i can find this path "$XDK_HOME\xdk\demo\c\xslt"
thanks in advance
shashi.

Cannot use bpws:getVariableData in dynamic assignment using xpath

Hello,
I'm trying to use dynamic task assignment using xpath expression. I have a BPEL variable (collection) that holds a list of users.
Under task assignment I set the following expression (data type- by expression):
bpws:getVariableData('Invoke1_get_usersSelect_OutputVariable','TestApprovalCollection','/ns5:TestApprovalCollection/ns5:TestApproval')
But when i run the process i get this error :
Function 'getVariableData' not found
Your help is appreciated.
Regards,

Make sure you have this entry in your bpel.
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"

Using XPath for associatios into BPMN process??

Hello everybody:
I'm using Oracle SOA and BPM Suite 11.1.1.5
I have a BPMN process that have an entry variable of type CBEFF_BIR_Type (the xml declaration is shown below)
<xsd:complexType name="CBEFF_BIR_Type">
 <xsd:sequence>
 <xsd:element name="FormatOwner" type="xsd:positiveInteger" minOccurs="1" maxOccurs="1"/>
 <xsd:element name="FormatType" type="xsd:positiveInteger" minOccurs="1" maxOccurs="1"/>
 <xsd:element name="BIR_Information" minOccurs="0" maxOccurs="1">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="BIR_Info" type="iso-iec19785-3-7:BIRInfoType" minOccurs="0"
 maxOccurs="1"/>
 <xsd:element name="BDB_Info" type="iso-iec19785-3-7:BDBInfoType" minOccurs="0"
 maxOccurs="1"/>
 <xsd:element name="SB_Info" type="iso-iec19785-3-7:SBInfoType" minOccurs="0"
 maxOccurs="1"/>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
 *<xsd:element name="BIR" type="tns:BaseBIRType"/>*
 </xsd:sequence>
 </xsd:complexType>* BaseBIRType xml declaration*
<xsd:complexType name="BaseBIRType"/>According to the business logic that BIR sould contain a node of type URI_BIR or BinaryBIR (xml declaration is shown below), it will never a self BaseBIRType.
<xsd:complexType name="URI_BIR">
 <xsd:complexContent>
 *<xsd:extension base="tns:BaseBIRType">*
 <xsd:sequence>
 <xsd:element name="URI" type="xsd:anyURI"/>
 </xsd:sequence>
 </xsd:extension>
 </xsd:complexContent>
 </xsd:complexType>
<xsd:complexType name="BinaryBIR">
 <xsd:complexContent>
 *<xsd:extension base="tns:BaseBIRType">*
 <xsd:sequence>
 <xsd:element name="Binary" type="xsd:base64Binary"/>
 </xsd:sequence>
 </xsd:extension>
 </xsd:complexContent>
 </xsd:complexType>As you can see, the bolded code in the first block illustrate a node of type BaseBIRType and the bolded code in the second block shows that the complex type URI_BIR and BinaryBIR are an extension of BaseBIRType. So it looks like a inheritance, as I see it.
Inside my process I need to know what kind of node is coming inside de BIR (URI or Binary) to copy it to the correct variable type. I've tryed using the XPath Expessions provided by the IDE (+ora:instanceOf(XpathExpression, QName)+) but I had no results.
Please someone who can guide me?, I'll appreciate any help. I'm new in XPath.
Regards,
isabelbernely

As I see it you should use transformations not associations in such case. Within transformation (xslt) you should use XPath expression to test which of the concrete instance of the base type you are dealing with and proceed accordingly. That's bit ugly (depending on actual subelements to distinguish types) so there are two alternatives:
1. use xsi:type in xml instance - an attribute which will directly indicate the type of the element (many java xml binding frameworks can output such attribute while marshalling types to xml)
2. remodel your xsd to use substitution groups - the construct is similar but due to nature of substitution groups each concrete type will have a separate named element - easy to distinguish later in transformation

Using xpath expressions in Document-Builder

Similar Messages

Maybe you are looking for