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
On Thu, Jun 5, 2008 at 12:38 PM, Mike Edwards
[EMAIL PROTECTED] wrote:
Matthieu,
First - many thanks for your hard work on this.
I take no pleasure in saying this, but I am glad that the DB problem was
ODE's problem rather than Tuscany's - it looks like you are far more
experienced in
Hi guys,
I'm hoping to get some time tomorrow to cut a release. That would be a 1.2,
built from the 1.1 branch and not the trunk yet (although I'm hoping that
will come very soon). Just wanted to check with everybody if the timing was
right. Just to share the warm fuzzy feeling of working tests.
On Thu, Jun 5, 2008 at 5:12 PM, Matthieu Riou [EMAIL PROTECTED]
wrote:
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
[
https://issues.apache.org/jira/browse/ODE-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexis Midon reopened ODE-295:
--
After discussion about this, we agreed on the following:
* EPRs implementation knowledge belongs to the
[
https://issues.apache.org/jira/browse/ODE-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexis Midon updated ODE-295:
-
Summary: EPR configuration (was: Integration-Layer configuration)
EPR configuration
-
