9:04 a.m.
message parts with the atribute element won't be accepted by bpel
-----------------------------------------------------------------
Key: BPEL-277
URL: http://jira.jboss.com/jira/browse/BPEL-277
Project: JBoss jBPM BPEL
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jBPM BPEL 1.1 beta 3
Environment: Running Java sdk 1.5.0_11, Jboss AS 4.0.5 GA and ant 1.7 in SunOs
5.9
Reporter: Felipe
Assigned To: Alejandro Guizar
Wsdl specification allows the use of the attribute element or type to refer to the XSD
definition of the part (Cf. http://www.w3.org/TR/2001/NOTE-wsdl-20010315.html#_messages )
However, when using the following definitions:
<element name="EE">
<complexType>
<sequence>
<element name="usuario" type="xsd:string"/>
<element name="sistema" type="xsd:string"/>
</sequence>
</complexType>
</element>
<wsdl:message name="pruebaE">
<wsdl:part name="entrada" element="tns1:EE"/>
</wsdl:message>
<variable name="entradaPruebaE" messageType="BA:pruebaE"/>
<copy>
<from variable="nombres" />
<to variable="entradaPruebaElectrica" part="entrada"
query="/entrada/usuario"/>
</copy>
It will throw the following exception:
2007-08-28 14:45:28,291 DEBUG [org.jbpm.bpel.graph.scope.FaultActionHandler] handling
fault: org.jbpm.bpel.gra
ph.exe.ScopeInstance@1f8ab0d[name=<null>,token=/,state=performingPrimaryActivity,id=0]
org.jbpm.bpel.graph.exe.BpelFaultException:
org.jbpm.bpel.graph.exe.FaultInstance@4a1535[name={http://schemas.
xmlsoap.org/ws/2004/03/business-process/}selectionFailure,id=0]
at org.jbpm.bpel.sublang.xpath.XPathEvaluator.createNode(XPathEvaluator.java:100)
at
org.jbpm.bpel.sublang.xpath.XPathEvaluator.selectOrCreateNodes(XPathEvaluator.java:79)
In the addressed part of XPathEvaluator, the following can be read:
if (!(node instanceof Element)) {
// cannot create node for a non-element parent
throw new BpelFaultException(BpelConstants.FAULT_SELECTION_FAILURE);
}
This won't happen when using a type especification.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:16 p.m.
New subject: [JBoss JIRA] Commented: (BPEL-277) message parts with the atribute element won't be accepted by bpel
[ http://jira.jboss.com/jira/browse/BPEL-277?page=comments#action_12374285 ]
Alejandro Guizar commented on BPEL-277:
---------------------------------------
The representation of a part P1 defined with a type T is an element with a null namespace
URI and a local name equal to the name of P1.
Conversely, the representation of a part P2 defined with an element E is an element with a
qualified name equal to the qualified name of E.
Your query is written as if part "entrada" was defined with a type, hence the
bpel:selectionFailure fault. Try this:
<copy>
<from variable="nombres" />
<to variable="entradaPruebaElectrica" part="entrada"
query="/tns1:EE/usuario"/>
</copy>
message parts with the atribute element won't be accepted by
bpel
-----------------------------------------------------------------
Key: BPEL-277
URL: http://jira.jboss.com/jira/browse/BPEL-277
Project: JBoss jBPM BPEL
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM BPEL 1.1 beta 3
Environment: Running Java sdk 1.5.0_11, Jboss AS 4.0.5 GA and ant 1.7 in SunOs
5.9
Reporter: Felipe Jensen Casado
Assigned To: Alejandro Guizar
Wsdl specification allows the use of the attribute element or type to refer to the XSD
definition of the part (Cf. http://www.w3.org/TR/2001/NOTE-wsdl-20010315.html#_messages )
However, when using the following definitions:
<element name="EE">
<complexType>
<sequence>
<element name="usuario" type="xsd:string"/>
<element name="sistema" type="xsd:string"/>
</sequence>
</complexType>
</element>
<wsdl:message name="pruebaE">
<wsdl:part name="entrada" element="tns1:EE"/>
</wsdl:message>
<variable name="entradaPruebaE" messageType="BA:pruebaE"/>
<copy>
<from variable="nombres" />
<to variable="entradaPruebaElectrica" part="entrada"
query="/entrada/usuario"/>
</copy>
It will throw the following exception:
2007-08-28 14:45:28,291 DEBUG [org.jbpm.bpel.graph.scope.FaultActionHandler] handling
fault: org.jbpm.bpel.gra
ph.exe.ScopeInstance@1f8ab0d[name=<null>,token=/,state=performingPrimaryActivity,id=0]
org.jbpm.bpel.graph.exe.BpelFaultException:
org.jbpm.bpel.graph.exe.FaultInstance@4a1535[name={http://schemas.
xmlsoap.org/ws/2004/03/business-process/}selectionFailure,id=0]
at
org.jbpm.bpel.sublang.xpath.XPathEvaluator.createNode(XPathEvaluator.java:100)
at
org.jbpm.bpel.sublang.xpath.XPathEvaluator.selectOrCreateNodes(XPathEvaluator.java:79)
In the addressed part of XPathEvaluator, the following can be read:
if (!(node instanceof Element)) {
// cannot create node for a non-element parent
throw new BpelFaultException(BpelConstants.FAULT_SELECTION_FAILURE);
}
This won't happen when using a type especification.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:25 p.m.
New subject: [JBoss JIRA] Commented: (BPEL-277) message parts with the atribute element won't be accepted by bpel
[ http://jira.jboss.com/jira/browse/BPEL-277?page=comments#action_12374287 ]
Alejandro Guizar commented on BPEL-277:
---------------------------------------
Alternatively, if you have a BPEL 2 process, the location path can be relative:
<copy>
<from variable="nombres" />
<to variable="entradaPruebaElectrica" part="entrada"
query="usuario"/>
</copy>
In fact, in jBPM BPEL this works in BPEL 1.1 processes as well, but we do not recommend it
because the specification mandates absolute location paths.
You can find examples of BPEL 2 processes created using the Eclipse BPEL designer in our
CVS repository: http://fisheye.jboss.com/browse/JBPM/jbpm.3/bpel/examples
In each example process, look for subdirectory src/main/bpel2.
message parts with the atribute element won't be accepted by
bpel
-----------------------------------------------------------------
Key: BPEL-277
URL: http://jira.jboss.com/jira/browse/BPEL-277
Project: JBoss jBPM BPEL
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM BPEL 1.1 beta 3
Environment: Running Java sdk 1.5.0_11, Jboss AS 4.0.5 GA and ant 1.7 in SunOs
5.9
Reporter: Felipe Jensen Casado
Assigned To: Alejandro Guizar
Wsdl specification allows the use of the attribute element or type to refer to the XSD
definition of the part (Cf. http://www.w3.org/TR/2001/NOTE-wsdl-20010315.html#_messages )
However, when using the following definitions:
<element name="EE">
<complexType>
<sequence>
<element name="usuario" type="xsd:string"/>
<element name="sistema" type="xsd:string"/>
</sequence>
</complexType>
</element>
<wsdl:message name="pruebaE">
<wsdl:part name="entrada" element="tns1:EE"/>
</wsdl:message>
<variable name="entradaPruebaE" messageType="BA:pruebaE"/>
<copy>
<from variable="nombres" />
<to variable="entradaPruebaElectrica" part="entrada"
query="/entrada/usuario"/>
</copy>
It will throw the following exception:
2007-08-28 14:45:28,291 DEBUG [org.jbpm.bpel.graph.scope.FaultActionHandler] handling
fault: org.jbpm.bpel.gra
ph.exe.ScopeInstance@1f8ab0d[name=<null>,token=/,state=performingPrimaryActivity,id=0]
org.jbpm.bpel.graph.exe.BpelFaultException:
org.jbpm.bpel.graph.exe.FaultInstance@4a1535[name={http://schemas.
xmlsoap.org/ws/2004/03/business-process/}selectionFailure,id=0]
at
org.jbpm.bpel.sublang.xpath.XPathEvaluator.createNode(XPathEvaluator.java:100)
at
org.jbpm.bpel.sublang.xpath.XPathEvaluator.selectOrCreateNodes(XPathEvaluator.java:79)
In the addressed part of XPathEvaluator, the following can be read:
if (!(node instanceof Element)) {
// cannot create node for a non-element parent
throw new BpelFaultException(BpelConstants.FAULT_SELECTION_FAILURE);
}
This won't happen when using a type especification.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:58 a.m.
New subject: [JBoss JIRA] Commented: (BPEL-277) message parts with the atribute element won't be accepted by bpel
[ http://jira.jboss.com/jira/browse/BPEL-277?page=comments#action_12374374 ]
Felipe Jensen Casado commented on BPEL-277:
-------------------------------------------
My process is 1.1 and you are totally right, Alejandro: It works perfectly, sorry. I had
also tried using a qname, but my mistake was writing the name of the part in the query,
instead of the name of the xsd element.
Thanks for the help and so this is closed.
Greetings.
message parts with the atribute element won't be accepted by
bpel
-----------------------------------------------------------------
Key: BPEL-277
URL: http://jira.jboss.com/jira/browse/BPEL-277
Project: JBoss jBPM BPEL
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM BPEL 1.1 beta 3
Environment: Running Java sdk 1.5.0_11, Jboss AS 4.0.5 GA and ant 1.7 in SunOs
5.9
Reporter: Felipe Jensen Casado
Assigned To: Alejandro Guizar
Wsdl specification allows the use of the attribute element or type to refer to the XSD
definition of the part (Cf. http://www.w3.org/TR/2001/NOTE-wsdl-20010315.html#_messages )
However, when using the following definitions:
<element name="EE">
<complexType>
<sequence>
<element name="usuario" type="xsd:string"/>
<element name="sistema" type="xsd:string"/>
</sequence>
</complexType>
</element>
<wsdl:message name="pruebaE">
<wsdl:part name="entrada" element="tns1:EE"/>
</wsdl:message>
<variable name="entradaPruebaE" messageType="BA:pruebaE"/>
<copy>
<from variable="nombres" />
<to variable="entradaPruebaElectrica" part="entrada"
query="/entrada/usuario"/>
</copy>
It will throw the following exception:
2007-08-28 14:45:28,291 DEBUG [org.jbpm.bpel.graph.scope.FaultActionHandler] handling
fault: org.jbpm.bpel.gra
ph.exe.ScopeInstance@1f8ab0d[name=<null>,token=/,state=performingPrimaryActivity,id=0]
org.jbpm.bpel.graph.exe.BpelFaultException:
org.jbpm.bpel.graph.exe.FaultInstance@4a1535[name={http://schemas.
xmlsoap.org/ws/2004/03/business-process/}selectionFailure,id=0]
at
org.jbpm.bpel.sublang.xpath.XPathEvaluator.createNode(XPathEvaluator.java:100)
at
org.jbpm.bpel.sublang.xpath.XPathEvaluator.selectOrCreateNodes(XPathEvaluator.java:79)
In the addressed part of XPathEvaluator, the following can be read:
if (!(node instanceof Element)) {
// cannot create node for a non-element parent
throw new BpelFaultException(BpelConstants.FAULT_SELECTION_FAILURE);
}
This won't happen when using a type especification.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:09 a.m.
New subject: [JBoss JIRA] Commented: (BPEL-277) message parts with the atribute element won't be accepted by bpel
[ http://jira.jboss.com/jira/browse/BPEL-277?page=comments#action_12374375 ]
Felipe Jensen Casado commented on BPEL-277:
-------------------------------------------
And thanks also for the specification of the representation of parts. I haven't found
anything about it in the wsdl nor the bpel 1.1 specifications.
message parts with the atribute element won't be accepted by
bpel
-----------------------------------------------------------------
Key: BPEL-277
URL: http://jira.jboss.com/jira/browse/BPEL-277
Project: JBoss jBPM BPEL
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM BPEL 1.1 beta 3
Environment: Running Java sdk 1.5.0_11, Jboss AS 4.0.5 GA and ant 1.7 in SunOs
5.9
Reporter: Felipe Jensen Casado
Assigned To: Alejandro Guizar
Wsdl specification allows the use of the attribute element or type to refer to the XSD
definition of the part (Cf. http://www.w3.org/TR/2001/NOTE-wsdl-20010315.html#_messages )
However, when using the following definitions:
<element name="EE">
<complexType>
<sequence>
<element name="usuario" type="xsd:string"/>
<element name="sistema" type="xsd:string"/>
</sequence>
</complexType>
</element>
<wsdl:message name="pruebaE">
<wsdl:part name="entrada" element="tns1:EE"/>
</wsdl:message>
<variable name="entradaPruebaE" messageType="BA:pruebaE"/>
<copy>
<from variable="nombres" />
<to variable="entradaPruebaElectrica" part="entrada"
query="/entrada/usuario"/>
</copy>
It will throw the following exception:
2007-08-28 14:45:28,291 DEBUG [org.jbpm.bpel.graph.scope.FaultActionHandler] handling
fault: org.jbpm.bpel.gra
ph.exe.ScopeInstance@1f8ab0d[name=<null>,token=/,state=performingPrimaryActivity,id=0]
org.jbpm.bpel.graph.exe.BpelFaultException:
org.jbpm.bpel.graph.exe.FaultInstance@4a1535[name={http://schemas.
xmlsoap.org/ws/2004/03/business-process/}selectionFailure,id=0]
at
org.jbpm.bpel.sublang.xpath.XPathEvaluator.createNode(XPathEvaluator.java:100)
at
org.jbpm.bpel.sublang.xpath.XPathEvaluator.selectOrCreateNodes(XPathEvaluator.java:79)
In the addressed part of XPathEvaluator, the following can be read:
if (!(node instanceof Element)) {
// cannot create node for a non-element parent
throw new BpelFaultException(BpelConstants.FAULT_SELECTION_FAILURE);
}
This won't happen when using a type especification.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:28 p.m.
New subject: [JBoss JIRA] Resolved: (BPEL-277) message parts with the atribute element won't be accepted by bpel
[ http://jira.jboss.com/jira/browse/BPEL-277?page=all ]
Alejandro Guizar resolved BPEL-277.
-----------------------------------
Resolution: Rejected
Resolving this issue per Felipe's request.
message parts with the atribute element won't be accepted by
bpel
-----------------------------------------------------------------
Key: BPEL-277
URL: http://jira.jboss.com/jira/browse/BPEL-277
Project: JBoss jBPM BPEL
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM BPEL 1.1 beta 3
Environment: Running Java sdk 1.5.0_11, Jboss AS 4.0.5 GA and ant 1.7 in SunOs
5.9
Reporter: Felipe Jensen Casado
Assigned To: Alejandro Guizar
Wsdl specification allows the use of the attribute element or type to refer to the XSD
definition of the part (Cf. http://www.w3.org/TR/2001/NOTE-wsdl-20010315.html#_messages )
However, when using the following definitions:
<element name="EE">
<complexType>
<sequence>
<element name="usuario" type="xsd:string"/>
<element name="sistema" type="xsd:string"/>
</sequence>
</complexType>
</element>
<wsdl:message name="pruebaE">
<wsdl:part name="entrada" element="tns1:EE"/>
</wsdl:message>
<variable name="entradaPruebaE" messageType="BA:pruebaE"/>
<copy>
<from variable="nombres" />
<to variable="entradaPruebaElectrica" part="entrada"
query="/entrada/usuario"/>
</copy>
It will throw the following exception:
2007-08-28 14:45:28,291 DEBUG [org.jbpm.bpel.graph.scope.FaultActionHandler] handling
fault: org.jbpm.bpel.gra
ph.exe.ScopeInstance@1f8ab0d[name=<null>,token=/,state=performingPrimaryActivity,id=0]
org.jbpm.bpel.graph.exe.BpelFaultException:
org.jbpm.bpel.graph.exe.FaultInstance@4a1535[name={http://schemas.
xmlsoap.org/ws/2004/03/business-process/}selectionFailure,id=0]
at
org.jbpm.bpel.sublang.xpath.XPathEvaluator.createNode(XPathEvaluator.java:100)
at
org.jbpm.bpel.sublang.xpath.XPathEvaluator.selectOrCreateNodes(XPathEvaluator.java:79)
In the addressed part of XPathEvaluator, the following can be read:
if (!(node instanceof Element)) {
// cannot create node for a non-element parent
throw new BpelFaultException(BpelConstants.FAULT_SELECTION_FAILURE);
}
This won't happen when using a type especification.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6889
days inactive
6904
days old
5 comments
3 participants
participants (3)
-
Alejandro Guizar (JIRA) -
Felipe (JIRA)
-
Felipe Jensen Casado (JIRA)