[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [bpel-dev] DOM nodes order
|
That is indeed necessary.
The writer has had that encoded in the structure of the code. You must
do the same in the DOM synchronizer too. Something must tell it what's
the order of insertation and you must do insertion in that order.
Remove and replace operations are immune to this issue but insert is not.
-m
Dennis Ushakov wrote:
Hi!
During the work on source tab I've encountered a little problem. I
found out that child nodes order is important for some components. In
example, first child node of <bpws:if> should be <bpws:condition> or
the document fails validation. Currently new child element is simply
added to the end. BPELWriter is creating child nodes in right order,
but when we're creating new DOM element for EMF element EMF element
has no children, so I see no way to use BPELWriter for this.
I'm currently working on this problem, so if you have any ideas or
suggestions I'll be very glad to hear them.
Thanks,
Dennis
_______________________________________________
bpel-dev mailing list
bpel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/bpel-dev
--
Michal Chmielewski, CMTS, Oracle Corp,
W:650-506-5952 / M:408-209-9321
"Manuals ?! What manuals ? Son, it's Unix, you just gotta know."
