Hi,
I question if we need to keep partnerLinkType alive?
If we want to have a 1:1 relation of simBPEL to BPEL, then we really need to
keep it.
We think, it is good to have a more easy language, but this should be the
second step. First, there should be a bijective mapping between simBPEL and
Hi,
We have thought about the syntax of links. As we understand, join and signal
belong to the previous element.
Assume following example:
parallel {
a;
b;
signal(b-to-X);
} and {
join(b-to-X);
c;
d;
} and {
e;
signal(e-to-f);
f;
join(e-to-f);
}
The link b-to-X connects b
Hi Alex,
However, when I read your explanation, you're interpreting
everything in terms of links, sourcing and targeting. What we have
here aren't links, we have a signal construct and a join construct.
Is it fair to say that signal() is like a BPEL empty with a target,
and join() is like an
Hi Matthieu,
I'm not sure I'm completely following so please forgive me if I'm off
base and feel free to correct me. My understanding of what you're
saying is that the way one could understand the snippet above is not
the way it actually is.
Yes, true.
Hence it should be fixed because it's
Hi Assaf,
--cut: http://ode.apache.org/bpel-simplified-syntax-simbpel.html---
The signal and join instructions are here to model links,
--end--
Signal says when something is done, join says when we should hold
until something is done.
This is a semantics different from BPEL!
So if I just
Hi Matthieu,
Ok, let's see with an example that I hope will be better than the last
one:
parrallel {
a;
if (...) {
signal(first);
} else {
signal(second);
}
} and {
c;
join(first);
d;
} and {
join(second);
e;
} and {
join(first, second, $first or
Hi Denis,
These days I'm developing a WS-BPEL status tracking tool which
generate an SVG flow diagram based on the BPEL code,
How does your code relate to
http://blogs.sun.com/toxophily/entry/open_esb_tip_generating_svg
?
and view the
instance variable values and the activity details of the
Hi,
In the context of our usage, we rely on BPEL extension activity
support within ODE for enabling the invocation of REST APIs through a
corresponding extension bundle. We therefore ported the extension
activity support from the 2.0-alpha branch (already some years ago and
therefore not up to
Hi,
We are going to use Apache ODE in a project with involvement of
industry partners. There, we are obliged to proof all (transitive)
dependencies ODE uses, in order to guarantee that all of them apply to
the Apache License Version 2.0. Unfortunately, we were not able to
(automatically)
Hi Sathwik,
Thank you for your answer.
> As of Apache ODE source code distribution, we don't ship any third-party
> dependent source along with it nor do we take their source and compile it
> ourself. We only use third-party library in it's binary form and it's
> binary license will be shipped
Hi,
2018-02-01 18:45 GMT+01:00 Sathwik B P :
> I dont have a timeline as of yet. The trunk has lot of changes. We need to
> release the new JACOB implementation. Revisit the clustering implementation
> based on hazelcast. We need to test migrations from 1.3.x versions from
rent state is
possible without much effort from your side? O:-)
Cheers,
Oliver
2018-02-21 13:40 GMT+01:00 Oliver Kopp <kopp@gmail.com>:
> Hi,
>
> I think, it's a chiggen-egg problem.
>
> Why not establish a more modern release-early-release-often cycle to show
&g
t;
> We would definitely like to see fresh blood coming into the community.
>
> regards,
> sathwik
>
> On Feb 2, 2018 20:27, "Oliver Kopp" <kopp@gmail.com> wrote:
>
> Hi,
>
>
> 2018-02-01 18:45 GMT+01:00 Sathwik B P <sathwik...@gmail.com>:
>
Hi,
would an etherpad instance (maybe created using https://pad.riseup.net/)
help to coordinate? Do you have other means "inbetween" issue tracker and
mailinglists in place in the context of Apache ODE?
Cheers,
Oliver
2018-02-23 12:32 GMT+01:00 Sathwik B P :
> Hi
ed. We also probably need to see if there
> >> are any security concerns with respect to JSON serialization used in the
> >> new Serialization mechanism, I vaguely remember as there was a flag
> raised
> >> on it sometime ago on a different project.
> >> We can pr
Oliver Kopp created ODE-1005:
Summary: Wrong link in Creating a Process
Key: ODE-1005
URL: https://issues.apache.org/jira/browse/ODE-1005
Project: ODE
Issue Type: Improvement
16 matches
Mail list logo