Agreed - just need to use a reference that remains stable across
compilations, but still uniquely identifies the relevant node in the
DAG.
Regards
Gary
On Tue, Mar 22, 2011 at 3:43 PM, Shivaraj Tenginakai
wrote:
> Way I have seen this implemented is that we need to distinguish
> between user sta
Way I have seen this implemented is that we need to distinguish
between user state and ode state. ODE state represents the structure
of the DAG while the user state represents the value of the variables
and the position in the DAG .
If we can achieve a clean separation between ODE state and user s
Oh well - back to the drawing board :)
On Tue, Mar 22, 2011 at 3:12 PM, Tammo van Lessen wrote:
> Hi Shivaraj, hi Gary,
>
> yes and no: first, when compiling the process model, each OModel node
> contains a unique ID and this is currently a GUID. Thus, even if the
> BPEL code is unchanged, the O
Hi Shivaraj, hi Gary,
yes and no: first, when compiling the process model, each OModel node
contains a unique ID and this is currently a GUID. Thus, even if the
BPEL code is unchanged, the OModel nodes will have different IDs after
compilation. Second, these IDs are used when serializing the runti
Hi Shivaraj
As far as I am aware this issue is not related to state - only the
static representation of the business process. The OModel simply
represents a binary compiled version of the BPEL process definition.
So all I am suggesting is rather than store the binary version, we
store the xml vers
Gary,
Would it be possible to distinguish between execution optimization and
state? As long as state information can be derived from one version to
another, it should be fine to recompile (to achieve execution
optimization).
Thanks,
Shivaraj
On Tue, Mar 22, 2011 at 3:40 PM, Gary Brown wrote:
On Tue, Mar 22, 2011 at 11:27 PM, Tammo van Lessen wrote:
> Hi guys,
>
> - JPA Refactoring
> - Status (Jeff): needs some final polishing, some tests need to be
> fixed in mvn build, then it can be committed to trunk. It supports both,
> Hibernate and OpenJPA via JPA 2.0
>
small correction here
Hi guys,
thanks for attending today's ODE skype call. AFAIK it was the first ODE
call of this kind, I think it was interesting and helpful. Lets continue
the discussion on the dev list.
Here are my notes:
Attendees: Anurag Aggarwal, Gary Brown, Jeff Yu, Shivaraj Tenginakai,
Sunil Kalva, Milinda
As discussed on the call today, we need a way to overcome the
constraints of the serialized OModel which is produced when compiling
the BPEL process.
Although a more flexible serialization mechanism may provide a
solution, as was also discussed, there will be cases where additional
logic would be
