In XSLT, make XPath expression to retrieve attribute nodes
I have a problem fetching attribute nodes in an Xpath expression.
SOAP Request:
<Create ID=5/>
<Name>Per</Name>
I want to fetch the value of ID and put it into another variable with an XPath expression in a XSLT transformation.
If you look at http://www.w3schools.com/xpath/xpath_syntax.asp
You should be able to do this with "//Create[@ID]" according to the examples, but this is not working at all in JDev.
Any thoughts?
/Per
Thanks, that worked!
Just thought about it. How do you do the other way around.
<Create>
<ID>7</ID>
to
<Create ID=7>
.
Similar Messages
-
XPATH expression to get Array node
Hi
I have a problem with an XPATH expression in BPEL. I want to get to a particular node in the following result set ..
<return xmlns:ns2="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns3="http://com.quion.taken.services/ITakenService.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns2:Array" ns2:arrayType="ns3:com_quion_dto_taken_BouwnotaVoorraadDTO[2]">
<item xsi:type="ns3:com_quion_dto_taken_BouwnotaVoorraadDTO">
<begunstigde xsi:type="xsd:string">Sjoerd</begunstigde>
<datum xsi:type="xsd:dateTime">2005-10-31T23:00:00.000Z</datum>
<bedrag xsi:type="xsd:string">1000.0</bedrag>
<geldLeningId xsi:type="xsd:string">4.0</geldLeningId>
<rekeningnummer xsi:type="xsd:string">1234</rekeningnummer>
<notaId xsi:type="xsd:string">1.0</notaId>
</item>
<item xsi:type="ns3:com_quion_dto_taken_BouwnotaVoorraadDTO">
<begunstigde xsi:type="xsd:string">Laszlo</begunstigde>
<datum xsi:type="xsd:dateTime">2005-10-31T23:00:00.000Z</datum>
<bedrag xsi:type="xsd:string">1.0</bedrag>
<geldLeningId xsi:type="xsd:string">4.0</geldLeningId>
<rekeningnummer xsi:type="xsd:string">5678</rekeningnummer>
<notaId xsi:type="xsd:string">2.0</notaId>
</item>
</return>
The first thing is that my variable in BPEL does not show the ïtem"level", it shows for example 'return/notaId'.
However I can get to the second node by keying in
EXPRESSION 1:
bpws:getVariableData('invokeGetBouwnotaVoorraadVoorLening_getBouwnotaVoorraadVoorLening_OutputVariable','return','/return/item[1]/notaId')
No I want to dynamically determine the particular node instance. I do this as follows [copied from the Array sample]:
EXPRESSION 2:
bpws:getVariableData('invokeGetBouwnotaVoorraadVoorLening_getBouwnotaVoorraadVoorLening_OutputVariable','return','/return/item[', bpws:getVariableData('i'),']/notaId')
BPEL throws the following error
assignNotaId (faulted)
[2005/11/09 09:49:36] Updated variable "invokeTaskManager_initiateTask_InputVariable" More...
<invokeTaskManager_initiateTask_InputVariable>
<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="payload">
<task xmlns="http://services.oracle.com/bpel/task">
<taskId />
<title />
<creationDate />
<creator />
<modifyDate />
<modifier />
<assignee>jstein</assignee>
<status />
<expired />
<expirationDate />
<duration />
<priority />
<template />
<customKey />
<conclusion />
<attachment />
</task>
</part>
</invokeTaskManager_initiateTask_InputVariable>
[2005/11/09 09:49:36] Error in evaluate <from> expression at line "172". The result is empty for the XPath expression : "bpws:getVariableData('invokeGetBouwnotaVoorraadVoorLening_getBouwnotaVoorraadVoorLening_OutputVariable','return','/return/item[', bpws:getVariableData('i'),']/notaId')".
[2005/11/09 09:49:36] "{http://schemas.xmlsoap.org/ws/2003/03/business-process/}selectionFailure" has been thrown. less
<selectionFailure xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/">
<part name="summary">
<summary>empty variable/expression result. xpath variable/expression expression "bpws:getVariableData('invokeGetBouwnotaVoorraadVoorLening_getBouwnotaVoorraadVoorLening_OutputVariable','return','/return/item[', bpws:getVariableData('i'),']/notaId')" is empty at line 172, when attempting reading/copying it. Please make sure the variable/expression result "bpws:getVariableData('invokeGetBouwnotaVoorraadVoorLening_getBouwnotaVoorraadVoorLening_OutputVariable','return','/return/item[', bpws:getVariableData('i'),']/notaId')" is not empty.</summary>
What is wrong with my expression 2?
Thanks
Jan WillemThis Example works fine for arrays that are part of a WSDL message.
But in 10.1.3.1 this does not work with a array that is part of an XSD declaration
for Example XSD snippet
<xsd:element name="itemList">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="1" ref="tns:Item" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
using the following in assign statement
<copy>
<from expression="concat('/ns9:itemList/ns9:Item[',string(bpws:getVariableData('index')),']')"/>
<to variable="idxXpath"/>
</copy>
<copy>
<from expression="bpws:getVariableData('OutputItemList',bpws:getVariableData('idxXpath'))"/>
<to variable="idx_item"/>
</copy>
gives a compiler error that is
Error(176):
[Error ORABPEL-10085]: invalid argument
[Description]: in line 176 of "D:\OnlineShopping_1\bpel\OnlineShopping.bpel", the second argument "bpws:getVariableData("idxXpath")" for getVariableData is not a literal expression.
[Potential fix]: Please correct the second argument, you might need to escape using single quote or " to make it literal.
Can anyone site the reason for the same or a possible solution?
Message was edited by:
user607972 -
Generate xpath expression from xslt
How can I generate an xpath expression for a selected node within xslt? I've found ways to get the node name, it's number and so on, but there doesn't seem to be a simple way to just print out the nodes xpath ( besides writing some type of recursive template )
The application is to set an HTML <input/> fields name attribute to the XPATH. That way, from within my app I can catch the update values and apply using XPATH.Typically you will be using the XSLT functions like position(), for the actual position of the node and of course other XSLT axis specifiers like ancestor, sibling, descendant, etc. For more info go to http://www.mulberrytech.com and http://www.zvon.org for tutorials.
Hope this helps -
Xpath expression in condition editor
Hi Expert Forum !
I have an xml structure like this :
<aaa>
<bbb>
<ccc>
</ccc>
</bbb>
</aaa>
In my condition editor (receiver determination) I want to refer to an element which is a child of node <ccc>. However, node ccc is not defined in my data type.
I can without any problems type my xpath expression manually but it doesn't seem to work though. As if it doesn't recognize node ccc if it's not in the data type. I know for 100% sure that node ccc will be in my inbound message.
Is it possible to reference an element in the condition editor - knowing that it will be present in the inbound message - even though it's not defined in the underlying data type ??
So why not just change the data type if I know <ccc> will be there? Well, data type is an external definition and I don't wanna edit it only to support an xpath expression in my rec. determination. If I can avoid it...
Message was edited by:
Hans Hougaard
Message was edited by:
Hans HougaardManaged to make xpath expression work. It is possible to reference an element which is not defined in the data type. My problem turned out to be a namespace issue..
-
XPath expression for fetching element names & attributes
Hi out there!
I�m trying to get a result set out of a xml schema, using XPath. The problem is, that any expression gets just a whole node set back, as it seems. The result I�d like to get would be the following. Imagine I got a schema like this:
<schema xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:r="http://recipes.org"
targetNamespace="http://recipes.org"
elementFormDefault="qualified">
<element name="recipe">
<complexType>
<sequence>
<element name="title" type="string"/>
<element ref="r:ingredient" minOccurs="0" maxOccurs="unbounded"/>
<element ref="r:preparation"/>
<element name="comment" minOccurs="0" type="string"/>
<element name="nutrition">
<complexType>
<attribute name="protein" type="r:nonNegativeDecimal" use="required"/>
<attribute name="carbohydrates" type="r:nonNegativeDecimal" use="required"/>
<attribute name="fat" type="r:nonNegativeDecimal" use="required"/>
<attribute name="calories" type="r:nonNegativeDecimal" use="required"/>
<attribute name="alcohol" type="r:nonNegativeDecimal" use="optional"/>
</complexType>
</element>
</sequence>
</complexType>
</element>
</schema>
Now, when I`m refering to the element <attribute name="protein" type="r:nonNegativeDecimal" use="required"/>, I would like to get all ancestors of it, which is not a big issue at all, but i`d just like to get their names and attributes, if they have some. So the result should be something like:
<element name="recipe">
<complexType>
<sequence>
<element name="nutrition">
<complexType>
</complexType>
</element>
</sequence>
</complexType>
</element>
Any ideas anybody?
Thanks in advance, JensWell, I would use the org.apache.xpath.XPathAPI class and parse the input XML into a DOM document., and then utilize the single xpath expression //attribute[@name=protein]/ancestor::* to recover all ancestors (in a directal-tree-traversal order) of any node called "attribute" and with attr "name=protein" .
Could it be? -
1 Unable to retrieve the form values entered by the user from the xpath expression(with or without s
1.1 Description of the Workflow
We have designed a Workflow, which has an init form HighLevelQuestionnaire.
1. The user attempts to start the workflow by submitting this form, which has an XML schema embedded.
2. When user submits the data, we set workflow variables to fetch data from the init-form and all the values entered by the user are stored in the database.
3. Based on the values, value of Risk Level is calculated to be either High or Medium, and user is routed to one of the two routes.
4. The user QPAC is used to show the next form to the user.
Another form has been designed called AssessRisk in which user is asked to confirm the Risk Level.
5. At this point, we use Script QPAC to print the values in the log.
1.2 Problem description
1. In the Point No. 6 of the workflow, the values are not printed in the log. A blank space is printed instead.
2. Initially, we embedded the schema in the form. But when values were not printed, we removed the schema. Even then it didnt work.
1.2.1 User QPAC Specifications
Properties of user QPAC used in Step 4 of the workflow
Mappings Tab: -
Input Variable --- No variable
Template URL ----- Form11.xdp
Output Variable ---- myform
Myform is a form-variable, which has template URL as Form11.xdp
1.2.2 Script QPAC
1.2.2.1 With XML Schema embedded
import com.adobe.workflow.pat.service.*;
System.out.println("----------- High Level Questions -----------");
System.out.println("--1- the RiskLevel is: " + patExecContext.getProcessDataStringValue("/process_data/myform/form-data/data/xdp/dataset s/data/RiskLevel/general/Risk_Level") + " @@@@@");
Note:- Here RiskLevel is the schema root of myform and Risk_Level is the schema variable mapped with textfield on the form
1.2.2.2 Without XML Schema embedded
System.out.println("--1.1- the RiskLevel is: " + patExecContext.getProcessDataStringValue("/process_data/myform/form-data/data/xdp/dataset s/data/fields/Risk_Level") + " @@@@@");
1.2.2.3 Conclusion
In both the cases, a blank value is printed. In both the cases, we get some output which is when we use
System.out.println("--1.1- the RiskLevel is: " + patExecContext.getProcessDataStringValue("/process_data/myform/form-data/data/xdp/dataset s/data ") + " @@@@@");
In this case all the values are printed with space in between.
This is the basic feature which has to be used while developing workflows.Hi
You might want to try using VariableLogger, at:
http://www.avoka.com/avoka/qpac_library.shtml
It's a little more reliable than the script QPAC, especially if one of your xpath expressions is wrong.
Please note that embedding the schema makes no difference in how the data from the form is stored. What makes the difference is whether your fields are bound to specify schema elements, or whether they use the "normal" binding.
Howard -
Xpath Expression/Functions in XSLT Mapper
Manual says I can use the orcl functions as well as Xpath Expressions, but when I try to execute it does not work? am I missing something her?
Trying to get a variable data into the target schema , the var is not in the source data schema?
Any suggestions?Can you explain a bit more what you want to do. It's very vague right now. Probably will be able to help you out.
Thanks -
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 JakkaHere 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"?>
<!-- Automatically generated by EDIFECS SpecBuilder (http://www.edifecs.com) -->
<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 -
We are using the OAGis schema and a client is sending us data in an expression instead of in the actual schema location using the <Get> portion of the schema.
<Get uniqueIndicator="true">
<Expression expressionLanguage="XPath">//Credit/FirstName[.="John"]</Expression>
<Expression expressionLanguage="XPath">//Credit/LastName[.="Smith"]</Expression>
</Get>What is the best way in BPEL to evaluate this xpath expression to set the FirstName to John and LastName to Smith? We are currently using a transform to parse each expression using XSLT into our database schema. It's not very elegant because it uses an if statement to check the path then has to parse out between the quotes then passes the value to the new var/schema.
It seems like there should be a way to evaluate the XPath and set the path to the noted string.
Thanks,This Example works fine for arrays that are part of a WSDL message.
But in 10.1.3.1 this does not work with a array that is part of an XSD declaration
for Example XSD snippet
<xsd:element name="itemList">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="1" ref="tns:Item" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
using the following in assign statement
<copy>
<from expression="concat('/ns9:itemList/ns9:Item[',string(bpws:getVariableData('index')),']')"/>
<to variable="idxXpath"/>
</copy>
<copy>
<from expression="bpws:getVariableData('OutputItemList',bpws:getVariableData('idxXpath'))"/>
<to variable="idx_item"/>
</copy>
gives a compiler error that is
Error(176):
[Error ORABPEL-10085]: invalid argument
[Description]: in line 176 of "D:\OnlineShopping_1\bpel\OnlineShopping.bpel", the second argument "bpws:getVariableData("idxXpath")" for getVariableData is not a literal expression.
[Potential fix]: Please correct the second argument, you might need to escape using single quote or " to make it literal.
Can anyone site the reason for the same or a possible solution?
Message was edited by:
user607972 -
[Error ORABPEL-10039]: invalid xpath expression - array processing
hi,
I am trying to process multiple xml elements
<assign name="setinsideattributes">
<copy>
<from expression="ora:getElement('Receive_1_Read_InputVariable','BILL','/ns2:BILL/ns2:CMS1500['bpws:getVariableData('iterator')']/ns2:HEADER/ns2:SSN')"/>
<to variable="ssn"/>
</copy>
</assign>
where iterator is a index variable .
I am getting into this error .
Error(48):
[Error ORABPEL-10039]: invalid xpath expression
[Description]: in line 48 of "D:\OraBPELPM_1\integration\jdev\jdev\mywork\may10-workspace\multixm-catch\multixm-catch.bpel", xpath expression "ora:getElement('Receive_1_Read_InputVariable','BILL','/ns2:BILL/ns2:CMS1500['bpws:getVariableData('iterator')']/ns2:HEADER/ns2:SSN')" specified in <from> is not valid, because XPath query syntax error.
Syntax error while parsing xpath expression "ora:getElement('Receive_1_Read_InputVariable','BILL','/ns2:BILL/ns2:CMS1500['bpws:getVariableData('iterator')']/ns2:HEADER/ns2:SSN')", at position "77" the exception is Expected: ).
Please verify the xpath query "ora:getElement('Receive_1_Read_InputVariable','BILL','/ns2:BILL/ns2:CMS1500['bpws:getVariableData('iterator')']/ns2:HEADER/ns2:SSN')" which is defined in BPEL process.
[Potential fix]: Please make sure the expression is valid.
any information on how to fix this .
thanks in advancecheck out this note here
http://clemensblog.blogspot.com/2006/03/bpel-looping-over-arrays-collections.html
hth clemens -
Hello to all,
I'm trying to create a ABAP based mapping without xslt, as xslt-mapping is running in a timeout.
Is there a way to execute XPATH expressions on a document?
The method "get_elements_by_name" isn't helpfull, as I need to specify a certain path within the xml-document.
Thanks for your suggestions.
Best regards,
ChristianI dont think it will be possible untill you include XSLT mapping in to ABAP mapping as you would need a compiler for XPATH expressions.
-
Xslt error: the expression does not evaluate to a node-set
hi guys - i'm really down because i cannot find / understand my xsl error and i have to finish my work very very soon
the error message (by using xalan to create from the xml file my html output) is the following:
xslt error: the expression does not evaluate to a node-set
and the code fragement is:
<xsl:template name="getNext">
<xsl:param name="currentKnoten" />
<xsl:for-each select="$currentKnoten"> //error is in this line
</xsl:for-each>
</xsl:template>please... help me....ok thanks!!! this saved me some time ;-)
now i go back to the origin problem... my main idea is the following xsl code... may u can see here the problem with the node site.. but i think u need the xml file or?
however this is my relevant xsl code:
<xsl:template match="DATA">
<xsl:element name="process">
<xsl:attribute name="name">
<xsl:value-of select="@name" />
</xsl:attribute>
<xsl:apply-templates select="INSTANCE"/>
</xsl:element>
</xsl:template>
<xsl:template match="INSTANCE[@class='Data']">
<xsl:element name="node">
<xsl:attribute name="name">
<xsl:value-of select="@name" />
</xsl:attribute>
<xsl:attribute name="class">
<xsl:value-of select="@class" />
</xsl:attribute>
<xsl:call-template name="copyAttributes" />
<xsl:variable name="nextNodes">
<xsl:value-of select="key('keyGetData', key('keyFrom', @name)/../TO/@instance)" />
</xsl:variable>
<xsl:call-template name="getNext">
<xsl:with-param name="currentNode" select="$nextNodes" />
</xsl:call-template>
</xsl:element>
</xsl:template>
<xsl:template name="getNext">
<xsl:param name="currentNode"/>
<xsl:for-each select="$currentNode">
<xsl:element name="node">
<xsl:attribute name="name"><xsl:value-of select="@name"/></xsl:attribute>
<xsl:attribute name="class"><xsl:value-of select="@class"/></xsl:attribute>
<xsl:variable name="nextNodes">
<xsl:value-of select="key('keyGetData', key('keyFrom', @name)/../TO/@instance)"/>
</xsl:variable>
<xsl:call-template name="copyAttributes"/>
<xsl:call-template name="getNext">
<xsl:with-param name="currentNode" select="$nextNodes"/>
</xsl:call-template>
</xsl:element>
</xsl:for-each>
</xsl:template>
<xsl:template name="copyAttributes">
<xsl:for-each select="descendant::*">
<xsl:copy>
<xsl:copy-of select="@*|node()"/>
</xsl:copy>
</xsl:for-each>
</xsl:template>
<xsl:template match="@*|node()">
<xsl:apply-templates/>
</xsl:template> -
The result is empty for the XPath expression
Hi friends
Please, could anyone help-me with this issue? My BPEL process was working yesterday and stoped today...
I think I´m facing a namespace problem.
If I start my process using BPEL Console, filling the "HTML form" option, all works ok.
If my process is started by a call from another bpel process, my XPath query gives me an error, but the 2 received messages are "almost" egual:
Using BPEL Console:
<RejectionMessage>
<part name="message" >
<RejectedMessage ns1:BatchId="" ns1:PrimaryKey="" ns1:RejectionId="invalid_msg_processName_token1_token2_token3" ns1:BatchInfo="" >
<MessageHeader/>
<MessagePayload/>
<RejectionReason/>
</RejectedMessage>
</part>
</RejectionMessage>
Started by another BPEL Process:
<RejectionMessage>
<part name="message" >
<RejectedMessage RejectionId="INVALID_MSG_BatchTest_Read_20060418_101233_0463" BatchId="" BatchInfo="" PrimaryKey="" >
<MessageHeader/>
<MessagePayload> AgICAgICAgICAgICAgICAgIE1aIEpBSVJPUyAg MDYwMzA4MTAwMQ0K </MessagePayload>
<RejectionReason> ORABPEL-11008</RejectionReason>
</RejectedMessage>
</part>
</RejectionMessage>
XPath Query:
bpws:getVariableData('RejectionMessage','message','/ns2:RejectedMessage/@ns2:RejectionId')
In the first case, it works.
In the second case, it raises a "The result is empty for the XPath expression" error.
As you can see, this process is used as a "Rejection Handler" process: It implements the interface defined in RejectionMessage.wsdl
Could you help me?
Thanks in advanceHi All
I find a workaround to the problem. I´m almost sure it is a bug in BPEL.
As you can see on my previous post, the diferences between the two messages is that the attributes have qualified names on one message and unqualified names on the other: ns1:BatchId, ns1:PrimaryKey...
The schema definition for this message (JCAErrorHandling.xsd) define that attribute names MUST be qualified (attributeFormDefault="qualified"). The problem is that the File Adapter sends the message with unqualified attribute names!!
So I edited JCAErrorHandling.xsd (<ORACLE_HOME>\integration\orabpel\system\xmllib\jca) file, changing it to attributeFormDefault="unqualified".
The correct solution is to fix File Adapter to send the message with qualified names, so I´m opening a Service Request at Oracle Metalink.
Thanks. -
How to evaluate dynamic XPath expression in BPEL?
I have an xml file where I keep many settings for my BPEL process. At runtime, I read the file and I want to select values from it based on values in the process payload.
For example, imagine that the process payload is an order:
<order>
<header>
<id/>
<customer_id/>
<team_id/>
</header>
<items>
<item>
<id/>
<sku/>
<price/>
<quantity/>
</item>
</items>
</order>
Now, in my xml settings file, I have a section where I keep a mapping of "team_id" and "assignment_group", so that for each team id, I can select the appropriate group to whom a task should be assigned. The relevant section of the settings file will look something like this:
<assignment_groups>
<group team_id='0923230'>invoice_approvers</group>
<group team_id='3094303'>order_approvers</group>
<group team_id='3434355'>shipping_approvers</group>
</assignment_groups>
So, imagine I get an order input to my process where the team_id is '3094303'. Now I have to lookup the correct assignment group in my settings file.
So, I construct the dynamic XPath expression
/settings/assignment_groups/group[@team_id=3094303]
I know that this would evaluate to "order_approvers". However, even though I have the XPath expression in a BPEL variable, and I have my settings file as a BPEL variable also, I don't know how to execute the XPath expression against the settings BPEL variable to retrieve the correct value.
Any ideas appreciated.
Thanks,
JackJames:
Thank you for the response. Incidentally, this is the very same document and section that I have been looking at for guidance. Specifically, the section titled "Dynamically indexing by Constructing an XPath at Run Time" on page 12-13.
I tried to do something similar to the example at the top of page 13:
<variable name="iterator" type="xsd:integer"/>
<assign>
<copy>
<from expression="concat('/invoice/line-item[',bpws:getVariableData('iterator'), ']/line-total')"/>
<to variable="xpath"/>
</copy>
<copy>
<from expression="bpws:getVariableData('input', 'payload',bpws:getVariableData('xpath')) + ..."/>
</copy>
</assign>
I am able to achieve the first copy operation to get my dynamic XPath into a BPEL variable and that's fairly straightforward. But I am unable to get the second copy to work. Specifically, I am not sure what to put in the second argument of the bpws:getVariableData function. I have tried many different combinations, but when I try to compile my program, I get the following compilation error:
Error:
[Error ORABPEL-10902]: compilation failed
[Description]: in "C:\code\TrainingWS\SampleGetSettings\bpel\SampleGetSettings.bpel", XML parsing failed because "org.collaxa.thirdparty.jaxen.expr.DefaultFunctionCallExpr".
[Potential fix]: n/a.
Thanks,
Jack -
Using a xpath expression stored in a variable
Hi All,
I have an xpath expression which is stored in the database which I need to use against the request XML. I am able to retrieve this Xpath expression from the database, but not able to use it against the request XML.
Xpath expression got from the database is: /request/param//name.
I have tried $body/$XpathVariable, this does not work. I can not hard code this expression during my design time, so the details of the expression has to be fetched at run time.
Any ideas to get the value would helpful.
Thankstry to assign this value to a temp variable and then in the XqueryExpression try to retrieve it starting with "//"
Maybe you are looking for
-
Help using multiple Time Capsules
I'm new to the Time Capsule and it's features, but my sister had one, then two and now three - all purchased to be dedicated to three different computers. She had to purchase more then one because she needed more capacity than one would hold. She i
-
Hello. So I built my computer at the end of last year, and my SSD was shipped FIRST, and by mistake, I installed that first, before my secondary drive, which is a 3Tb drive. Fast forward to today. I am running out of space, and I come up with an idea
-
Placed .eps files w/ spot white don't appear in PDF
This happens on and off and I am completely flummoxed. Any suggestions would be most welcome!
-
Move photos, music, time machine
I would like to move my iphoto library, itunes library and time machine off of my current i-mac. What is my best solution? I love that my ipad and iphone sync with my computer when i walk in the door, if I move the libraries to an external drive wo
-
Having trouble logging in to Adobe.com to download Audition CS6 (academic version). I got an email wth the serial number and a link to get things started which started off by having me log-in to my adobe account. I attempted a login and the page jus