| Re: [bpel-dev] What makes 2 element type compatible? |
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
Team Lead BPEL Editor - Websphere Integration Developer (WID)
IBM Software Group, Application and Integration Middleware Software
Business Process Solutions Development 1
Phone: +49-7031-16-4304 IBM Deutschland (Embedded
image moved
to file:
pic00610.gif)
Fax: +49-7031-16-4890 Schoenaicher Str. 220
E-Mail: smoser@xxxxxxxxxx 71032 Boeblingen
Germany
IBM Deutschland
Research &
Development
GmbH /
Vorsitzender des
Aufsichtsrats:
Martin Jetter
Geschäftsführung:
Dirk Wittkopp
Sitz der
Gesellschaft:
Böblingen /
Registergericht:
Amtsgericht
Stuttgart, HRB
243294
From: Joni Lee <webcokies@xxxxxxxxx>
To: "BPEL Designer project developer discussions." <bpel-dev@xxxxxxxxxxx>
Date: 09.12.2009 17:48
Subject: Re: [bpel-dev] What makes 2 element type compatible?
Sent by: bpel-dev-bounces@xxxxxxxxxxx
Hi Simon,
AHA! then a message's part from type "data type" can be assigned to a message's part from type "element", if this "element" is
defined as the same XML data type as above?
Thank you
--- On Wed, 12/9/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-dev@xxxxxxxxxxx, bpel-dev-bounces@xxxxxxxxxxx
Date: Wednesday, December 9, 2009, 4:13 PM
Joni,
two elements are compatible if
... a.) their QName (qualifiedName), that is : name and namespace of
the type that is associated with the element are exactly the same
(simpleCheck)
... b.) the assignee is SuperType of the Assigner. Example: have two
types "string" and "myString" (derived from String either by extension or
restriction),
so then I could assign the less general type (myString) to
the more general type (string) . In general, deciding XSD Type
Compatibility is not easy.
From: Joni Lee <webcokies@xxxxxxxxx>
To: bpel-dev@xxxxxxxxxxx
Date: 08.12.2009 18:49
Subject: [bpel-dev] What makes 2 element type compatible?
Sent by: bpel-dev-bounces@xxxxxxxxxxx
Hi Michael,
Thank you for all your help. From my current school project, I need to understand the assignment and type compatibility. I have a
new question.
Example, we have an assigment from a message's part from type element to another message's part from type element. What makes the
2 element
compatible?
1. When they (and their children) must have the same element name.
2. Their name can be different but the data type, which defines the elements is the same. Which means their structures "look" the
same.
3. Two elements are not required to be compatible at all, because the destination element will be replaced by the source element
(replace by element
in 8.4.2). If this is right, then 2 very different elements can be assigned, no matter how they are?
Thank you again and again.
_______________________________________________
bpel-dev mailing list
bpel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/bpel-dev
_______________________________________________
bpel-dev mailing list
bpel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/bpel-dev
_______________________________________________
bpel-dev mailing list
bpel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/bpel-dev
Attachment:
pic00610.gif
Description: GIF image
