On 6/26/06, Matthieu Riou <[EMAIL PROTECTED]> wrote:
Hi Cory,
I've been looking at the bpel-content project and had few questions:
* What would the "atomic" implementation used for?
This would be opaque data. The atomic interaction allows the engine
to persist non serializable objects by using xstream. You can also
assign from atomic(toString) into a DOM.
* Do you plan to have other implementations than the DOM/jaxen one?
We have wraped some proprietary data objects with an Interaction
implementation. These proprietry Interaction implementations work
with he the Jaxen Query implementation, so we haven't implemented any
other Query types. Are there any other Query and Interaction
implementations we would want to support by default?
I should have mentioned this in the first email. I was thinking in
the iapi Content would change to DescribedContent and the engine would
expose some setters for Query and Interaction implementations.
Also, something else I didn't mention, these apis are just for the
BPEL query language, not the BPEL expression language. I was thinking
the expression language apis would be part of the engine's process
context project, although it would have to work in concert with the
Interaction/Query stuff. What do you think?
Thanks!
Matthieu.
On 6/21/06, cory <[EMAIL PROTECTED]> wrote:
>
> Hello All,
>
> I've imported a bpel-content project into scratch/ode. This is a
> cleaned up version of what was in the BPE. There is also a default
> impl and a few unit tests. Comments please...
>
> -cory
>
