Hi all,
This e-mail is being sent to both Apache Ode and Tuscany development mailing
lists.
The objective is to see which possible collaboration could happen between
our 2 projects and how we could integrate them. Alex, Cory and myself (we're
all Ode contributors) met with Jean-Sebastien
think?
Matthieu
[1]
http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200610.mbox/[EMAIL
PROTECTED]
On 10/25/06, ant elder [EMAIL PROTECTED] wrote:
On 10/25/06, Matthieu Riou [EMAIL PROTECTED] wrote:
Hi all,
This e-mail is being sent to both Apache Ode and Tuscany development
mailing
Hi,
Nice volunteering indeed!
So on the Ode side, I'd go with implementing a specific integration layer
for Tuscany instead of reusing the Axis2 one. That would allow in-VM SCA /
BPEL interactions and a greater integration between the two.
Ode provides an integration API that you have to
zone but can be pretty flexible about scheduling it. How about 9:30am BST
next Tuesday?
..ant
On 10/26/06, Matthieu Riou [EMAIL PROTECTED] wrote:
Hi,
So what about an IRC session to get started? Everybody interested could
come to ask questions and we would discuss in more details how
It's simply sending an e-mail to the infrastructure mailing-list, giving
them the mailing-list name and your Apache id and they'll add you as a
moderator.
Matthieu
On 11/2/06, ant elder [EMAIL PROTECTED] wrote:
On 7/28/06, Jeremy Boynes [EMAIL PROTECTED] wrote:
On Jul 27, 2006, at 9:02 AM,
Thanks ant!
On 11/3/06, ant elder [EMAIL PROTECTED] wrote:
As discussed, I've created an empty skeleton container for this at:
https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/services/containers/container.bpel/
There's a JIRA for attaching patches to at:
Hi,
I have a better and better idea on how Apache Ode could be used as a Tuscany
container. However I'm still wondering how I can get hold on some resources
in Tuscany. To run Ode's BPEL engine we need basic services like a
transaction manager, a datasource or a thread scheduler (
Hi,
I just wanted to let you know that I had a small compilation failure when
building Tuscany from the sources (latest trunk) with a test case that
didn't compile:
/home/dusty/Dev/Projects/tuscany/sca/tools/src/test/java/org/example/creditscore/doclit/DoclitPackage.java:[23,41]
cannot find
for me, how about you Sam?
...ant
On 10/27/06, Matthieu Riou [EMAIL PROTECTED] wrote:
Actually most Ode committers (including myself) are in California.
Also
we're going to be a bit busy early next week. So would 4pm BST (8am
PST) on
Thursday work for you?
On 10/27
Hi Sam,
I'll have a deeper look at this today or tomorrow. I'll certainly have a
look at what you've contributed so far. My understanding is that Tuscany's
SPIs have significantly changed so we may be better off starting from
scratch from the skeleton Luciano has created and import (understand
Hi guys,
I'm starting on the lifecycle part of the Tuscany/ODE integration to get an
engine started with all its necessary resources (transaction, persistence,
...). I can go with in-memory mode and light configuration for now but we'll
want a fully working server sooner or later. So I have a
processes that are implementations of different
components
in a deployment. Is the ODE server something that we should implement
on
lines with the 'hosts' that we have have ? Thoughts ?
- Venkat
On 6/21/07, Matthieu Riou [EMAIL PROTECTED] wrote:
Hi guys,
I'm starting
Hi Sam,
I've submitted a patch yesterday to apply on the skeleton that Luciano
provided (see [1]). It's a first step to get something up and running. I'm
also discussing with the Tuscany guys how to handle the ODE configuration
(see [2]). As for process deployment, we wouldn't have a deployment
Hi Simon,
Please see my answers in line:
On 6/22/07, Simon Laws [EMAIL PROTECTED] wrote:
Can I just check that I understood what you have said. I.e. that there
will be only one ODE server instance on which processes will
be deployed. Does this mean,
1 ODE server instance per Tuscany runtime
Hi,
See my answers in line:
On 6/24/07, Luciano Resende [EMAIL PROTECTED] wrote:
I have committed your initial patch for Tuscany-1365, and also
provided a summary of the necessary steps to build ODE [1] for the
ones interested on playing with the implementation at the moment.
Perfect,
with the contribution.
Cheers,
Matthieu
Thanks,
Raymond
- Original Message -
From: Matthieu Riou [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Monday, July 02, 2007 9:27 AM
Subject: Resolving files, getting the component interface
Hi guys,
I'm continuing on the ODE / Tuscany
Hi guys,
I've done a few additional stuff on the BPEL implementation allowing a BPEL
file to be compiled by ODE upon deployment. The implementation is therefore
created and initialized with most of what would be needed by the runtime.
However there's still a couple of problems with resolution
Sure, no problem. And thanks :-)
On 7/5/07, Luciano Resende [EMAIL PROTECTED] wrote:
Thanks Matthieu
I'm little overbooked these days, but let me see if I could try to
look into the resolution thing over the weekend. Is that OK ?
On 7/5/07, Matthieu Riou [EMAIL PROTECTED] wrote:
Hi guys
-
From: Matthieu Riou [EMAIL PROTECTED]
To: Luciano Resende [EMAIL PROTECTED]
Cc: tuscany-dev@ws.apache.org
Sent: Thursday, July 05, 2007 5:08 PM
Subject: Re: BPEL implementation: WSDL and BPEL resolving
Sure, no problem. And thanks :-)
On 7/5/07, Luciano Resende [EMAIL PROTECTED
On 9/11/07, ant elder [EMAIL PROTECTED] wrote:
An update on some changes to the Tuscany incubation mentors:
- Dims has stepped down as mentor. Many many thanks for all the help and
guidance during our incubation, its been invaluable.
- Paul Fremantle and Matthieu Riou have signed up as new
of this new component type, I'll also look into
references as well.
I'd also like to Thank all the help from the ODE community, especially
Matthieu Riou.
[1] http://osoa.org/display/Main/SCA+BPEL+White+Paper
[2]
http://osoa.org/download/attachments/35/SCA_ClientAndImplementationModelforBPEL_V100.pdf
On 9/15/07, ant elder [EMAIL PROTECTED] wrote:
The implementation-bpel brings in nearly 30Meg of new dependency jars, i'm
guessing a lot of these aren't really necessary and we could exclude them,
but the list is so long it will take a while to work out, could any of
the
bpel/Ode experts
Everything looks good but it seems that a few copyright notices are missing
in the NOTICE file. Is it generated by Maven? I could spot at least
XmlBeans, Xalan, Xerces and Derby.
As that's the only problem I can find, I think you can just patch the
release archives without the necessity of
On 9/20/07, Matthieu Riou [EMAIL PROTECTED] wrote:
Everything looks good but it seems that a few copyright notices are
missing in the NOTICE file. Is it generated by Maven? I could spot at least
XmlBeans, Xalan, Xerces and Derby.
Replying to myself :) Actually I don't see a reason
There are a couple of copyright notices that you should add in your NOTICE
file, mostly derby, stax and woodstox (as described in [1]). Also JSTL is
listed in your LICENSE file although I don't think it's part of the release
(at least not in the binary package). Everything else looks fine to me as
/graduation#checklist
On 9/13/07, Matthieu Riou [EMAIL PROTECTED] wrote:
Guys,
I'm definitely +1 for both graduation and ant as the chair. For the
tasks,
as ant mentioned the graduation guide [1] is definitely a good read. A
few
additional details:
* In your resolution, one
On 9/26/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Matthieu Riou wrote:
Guys,
I'm definitely +1 for both graduation and ant as the chair. For the
tasks,
as ant mentioned the graduation guide [1] is definitely a good read. A
few
additional details:
* In your resolution
On 9/27/07, Simon Laws [EMAIL PROTECTED] wrote:
On 9/27/07, ant elder [EMAIL PROTECTED] wrote:
On 9/27/07, Mike Edwards [EMAIL PROTECTED] wrote:
Folks,
Simon Laws wrote:
On 9/27/07, ant elder [EMAIL PROTECTED] wrote:
On 9/27/07, Matthieu Riou [EMAIL PROTECTED] wrote
On 10/2/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
[snip]
Simon Laws wrote:
How about we put a check list up on the wiki so
we all get a view of what's going on and what needs to be done by when.
I've
started one here by copying the checklist from the graduation guide (
On 10/9/07, ant elder [EMAIL PROTECTED] wrote:
Looks like we've closed all the discussions around this so we can now vote
on it. We've an Incubator discussion thread on our graduation but I don't
see why we can't let that run in parallel, so ...
Please vote on graduating Tuscany as a top
Looks good to me, thanks for correcting the problems mentioned by Sebastian.
+1
Matthieu
On Jan 28, 2008 9:31 AM, Simon Laws [EMAIL PROTECTED] wrote:
Hi,
The previous VOTE thread here for SCA Java 1.1-incubating identified some
issues.
http://www.mail-archive.com/[EMAIL
I'm happy to see this discussion going and I think most of the points listed
make a lot of sense.
A small detail to add to the list that I think could have some importance:
your -dev list is flooded by Jira issues. Newcomers interested in Tuscany's
development are very likely to get overwhelmed
On Thu, Apr 24, 2008 at 10:41 AM, Luciano Resende [EMAIL PROTECTED]
wrote:
On Thu, Apr 24, 2008 at 8:53 AM, ant elder [EMAIL PROTECTED] wrote:
On Thu, Apr 24, 2008 at 4:37 PM, Luciano Resende [EMAIL PROTECTED]
wrote:
Now that we are making more progress with the SCA BPEL
On Thu, Apr 24, 2008 at 8:37 AM, Luciano Resende [EMAIL PROTECTED]
wrote:
Now that we are making more progress with the SCA BPEL integration
and have figured out how to make References to work, let's discuss
what could be the next steps on this area. Below are couple examples
of what we
I think Alex didn't mean it's there already, just pointed out a way to add
this :)
We already have something similar in bpel-store [1]. You can configure
OpenJPA to create the schema for you if it can't find it. So what you would
do is basically:
1. Create a derby instance.
2. Point OpenJPA to
* Matthieu Riou mriou at apache dot org
* Mike Edwards edwardsmj at apache dot org
* Paul Fremantle pzf at apache dot org
* Pete Robbins robbinspg at apache dot org
* Raymond Feng rfeng at apache dot org
* Simon Laws slaws at apache dot org
* Simon Nash nash at apache dot org
On Mon, May 19, 2008 at 9:11 AM, Mike Edwards
[EMAIL PROTECTED] wrote:
Folks,
I am interested in getting rid of the need to have a physical deploy.xml
file in the directory with a BPEL process file.
Can I supply the same information to the ODE runtime through some other
means, such as
On Tue, May 20, 2008 at 2:12 PM, Mike Edwards
[EMAIL PROTECTED] wrote:
Luciano Resende wrote:
So, in the case where we replace the ODE Process Store module with one
implemented by Tuscany, is this new module going to be responsible for
handling all the versioning and matching a running
Special order 7B, Establish the Apache Tuscany Project, was approved by
Unanimous Vote of the directors present.
Congratulations guys!
Matthieu
On Thu, May 22, 2008 at 3:55 AM, ant elder [EMAIL PROTECTED] wrote:
Now that we have graduated we have some work to do to migrate to a TLP, the
Incubator has information about this if anyone is interested in helping
out,
for example a good start is
On Fri, May 23, 2008 at 9:03 AM, Mike Edwards
[EMAIL PROTECTED] wrote:
Matthieu Riou wrote:
What mike says. I should just add that picking the right process version
depending on what's already executing is handled by the runtime. The only
thing that it will need is to know what
On Tue, May 27, 2008 at 10:35 AM, Jean-Sebastien Delfino
[EMAIL PROTECTED] wrote:
Mike Edwards wrote:
Jean-Sebastien Delfino wrote:
Jean-Sebastien Delfino wrote:
The following files:
sca/modules/core/pom.xml
sca/modules/binding-jms/pom.xml
sca/modules/policy-transaction/pom.xml
Actually the process runtime also needs a transaction when you deploy a
process. It persists some data structures needed to optimize message routing
and correlation extraction (basically which receives we can route to).
Cheers,
Matthieu
On Tue, May 27, 2008 at 4:08 PM, Luciano Resende [EMAIL
On Thu, May 29, 2008 at 11:41 AM, Mike Edwards
[EMAIL PROTECTED] wrote:
Folks,
I've run into problems with the SCA BPEL implementation and the way it
interacts with the ODE engine - and I need help from some ODE experts,
please.
OK, the SCA code is using the ODE engine in an embedded mode
)
The message looks fine to me, any idea what this could be? I've committed my
fixes so you should be able to reproduce it.
Cheers,
Matthieu
On Fri, May 30, 2008 at 11:39 PM, Matthieu Riou [EMAIL PROTECTED]
wrote:
I've started looking at the DbError issue and reproduced it. Digging deeper
to get
your fixes for the DB problem?
Matthieu Riou wrote:
Okay, this took a while because it was actually far trickier than I
expected. Here were the two problems (the first being the serious one):
* When OpenJPA first connects to the DB it initializes its sequence table
and does it using
I guess that would be me as the fix I did outlined another issue (as
described in the thread Luciano pointed at). So you guys expect to always
have all the tests passing on trunk all the time?
Cheers,
Matthieu
On Thu, Jun 5, 2008 at 12:57 PM, Mike Edwards
[EMAIL PROTECTED] wrote:
Folks,
[ http://issues.apache.org/jira/browse/TUSCANY-897?page=all ]
Matthieu Riou updated TUSCANY-897:
--
Attachment: BpelServerLoader.java
Simple loader than can be used to initialize Ode.
BPEL container based on Apache Ode
: Java SCA BPEL Implementation Extension
Reporter: Matthieu Riou
Attachments: ode-init.patch
I'm attaching a patch and a zip (for new files) containing the necessary code
to bootstrap the ODE BPEL server. It actually doesn't give you much as it's
just initializing all
[
https://issues.apache.org/jira/browse/TUSCANY-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthieu Riou updated TUSCANY-1365:
---
Attachment: ode-init.patch
Patch file to apply in implementation-bpel
Bootstrap the ODE
[
https://issues.apache.org/jira/browse/TUSCANY-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthieu Riou updated TUSCANY-1365:
---
Attachment: ode-init.zip
Zip file to unzip in implementation-bpel
Bootstrap the ODE
Components: Java SCA BEPL Implementation Extension
Reporter: Matthieu Riou
Attachments: patch.txt, patch.zip
The attached path corrects 2 things so that the module can compile and have
passing tests without any tweaking:
- The ODE derby database gets downloaded as a regular
[
https://issues.apache.org/jira/browse/TUSCANY-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthieu Riou updated TUSCANY-1394:
---
Attachment: patch.txt
Patch to apply to implementation-bpel.
Database import for tests
[
https://issues.apache.org/jira/browse/TUSCANY-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthieu Riou updated TUSCANY-1394:
---
Attachment: patch.zip
Unzip in implementation-bpel.
Database import for tests, using ODE
[
https://issues.apache.org/jira/browse/TUSCANY-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthieu Riou updated TUSCANY-1413:
---
Attachment: patch.txt
WSDL and BPEL resolving
Reporter: Matthieu Riou
Priority: Minor
I've done a few additional stuff on the BPEL implementation allowing a BPEL
file to be compiled by ODE upon deployment. The implementation is therefore
created and initialized with most of what would be needed by the runtime.
However there's still
56 matches
Mail list logo
