[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [bpel-dev] What makes 2 element type compatible?
|
basically that's what I am saying, yes. The BPEL standard says that you can
assign an XSD element to an XSD element (of a compatible element), or an
XSD type to an XSD type (of a compatible type) or a WSDL message to a WSDL
message (of a compatible message).
Some engine implementations allow also assignments of an XSD element to an
XSD type (or vice versa) if and only if the XSD type behind the element is
compatible to the XSD type ... but that is an implementation detail and as
far as I know not explicitly specified in the BPEL standard, so I would not
rely on that
[XSD elements have a qualified name, too, and compatibility for an element
means the qnames of both elements are equal, not necessarily that the XSD
types behind the elements are compatible]
From: Joni Lee <webcokies@xxxxxxxxx>
To: "BPEL Designer project developer discussions." <bpel-dev@xxxxxxxxxxx>
Date: 10.12.2009 13:08
Subject: Re: [bpel-dev] What makes 2 element type compatible?
Sent by: bpel-dev-bounces@xxxxxxxxxxx
Hallo Simon,
You mean, it depends on the BPEL Engine? (Active VOS...)
And this kind of assignment is not defined officially by the BPEL specification?
viele Gruesse
--- On Thu, 12/10/09, Simon D Moser <SMOSER@xxxxxxxxxx> wrote:
From: Simon D Moser <SMOSER@xxxxxxxxxx>
Subject: Re: [bpel-dev] What makes 2 element type compatible?
To: "BPEL Designer project developer discussions." <bpel-dev@xxxxxxxxxxx>
Cc: "BPEL Designer project developer discussions." <bpel-dev@xxxxxxxxxxx>,
bpel-dev-bounces@xxxxxxxxxxx
Date: Thursday, December 10, 2009, 5:33 PM
well, that depends on the runtime that you use, since this an
implementation question ... it might well be that runtime A can handle
this, whereas runtime B cannot
Mit freundlichen Grüßen / Kind regards
Simon Daniel Moser
_______________________________________________
bpel-dev mailing list
bpel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/bpel-dev