sorry, I didn't see the code tag, just posting the code snippet and the soap message again.
that is the bpel syntax I have
<copy> <from><literal>test</literal></from> <to>$CreateItemIn.createItem/arg0/@transactionId</to> </copy>
<copy> <from><literal>transaction</literal></from> <to variable="CreateItemIn" part="createItem">arg0/@transactionId</to> </copy>
the soap message look like this
Looks like an ODE problem. Interesting point is if the same behaviour occurs in RiftSaw M1 and M2, then the same issue exists in ODE2.0 aswell as ODE1.3.3.
If you could create a jira and attach your example we will take a look.
google found another possible explanation...
with openesb the variables doesn't need to be initiated completely, as soon $CreateItemIn.createItem/arg0/@transactionId is used in a BPEL, the data structures are created down to the attribute (@transactionId)..
ODE seems to be a bit more picky, the variables must be initialized completely (see http://email@example.comfirstname.lastname@example.org/msg02659.html for more information)
alternate way seems to be to work with extensions (e.g. insert-as-last-into()).