[bpel-dev] DOM Facade work

[Michal Chmielewski <michal.chmielewski@xxxxxxxxxx>]

Bruno,

Any news on that ?

Simon,

I've actually taken a look at some of the code that's in there in 
BPELWriter trying to fix an indent problem on save of the process map. 
Turns out there some strange settings in JDK5 on the transformer 
defaults that can only be overwritten via bootclasspath settings ... I 
managed to locate this bug

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5064280

So I replaced the code in there (10 lines or so)  with the xerces 
specific XMLSerializer way of saving things (which is in an eclipse 
plugin, so isolating that from the JDK issue)

Regarding the DOM facade, we derive almost everything from WSDLElement 
ultimately (via ExtensibilityElement) - there were a few EMF objects 
that did not do that (like import for example and a couple of others). I 
had made the change to derive these from WSDLElement too just so that I 
can have the getElement() setElement() capability on all of our model 
objects.

Now I reckon there is already some capability in that layer to reconcile 
changes which are applied to the model to the DOM elements present 
within. I looked at the code down low and it seemed that all the parts 
around moving, attaching,detaching, etc. seem to be there. The only 
thing that remains to be written I think is some way to flush the 
current state of the EMF object to the DOM element it wraps when the EMF 
objects changes. This is not as nice a facade as it could be (since it 
is one directional) ... but it would serve our immediate purpose of 
preserving some of the nodes which are currently destroyed during 
reading/writing.

Thoughts ?

--
Michal Chmielewski, CMTS, Oracle Corp, 
W:650-506-5952 / M:408-209-9321 

"Manuals ?! What manuals ? Son, it's Unix, you just gotta know."