Re: ** IMPLEMENTATION.BPEL USERS ** - updated implementation-bpel code in trunk - affects your BPEL applications
I am cc'ing tunscay-users since this seems to be interesting to users and
they may not be on the dev list.
Thanks Mike.
On 5/17/08, Mike Edwards <[EMAIL PROTECTED]> wrote:
>
> Folks,
>
> I've just committed some changes to the implementation-bpel and
> implementatio-bpel-ode code in trunk which fix some issues relating to
> exposing BPEL processes using Web services (and other remote protocols).
>
> These changes have an impact on the content of the deploy.xml file that is
> associated with your BPEL applications. In order to work correctly, you
> will need to ensure that your deploy.xml file corresponds to the following
> pattern:
>
>
> http://www.apache.org/ode/schemas/dd/2007/03";
>xmlns:tns="http://helloworld";
>xmlns:helloworld="http://helloworld";
>xmlns:greetings="http://greetings";
>xmlns:tus="http://tuscany.apache.org";>
>
>
>
>true
>
> port="HelloWorld"/>
>
>
> port="Greetings"/>
>
>
>
>
>
> You must ensure:
>
> a) Each partner link in your BPEL process is declared using either a
> (for a service) or using a for a reference.
>
> b) Each and must use the partnerLink name, as declared
> in your BPEL process.
>
> c) The and elements each have a single child
> element. The elements have name and port attributes.
> The NAME attribute MUST be set to the same name as the partnerLink and MUST
> be prefixed by a prefix which references the namespace "
> http://tuscany.apache.org"; ("tus" in the example above). The port
> attribute can be set to any name (it must be present but it is not actually
> used for anything significant).
>
>
> Sorry for forcing this change on you all, but the previous version of the
> code had a mixup over the name of the services and references as used by the
> ODE BPEL engine - this change fixes that problem.
>
>
> In the next week, we shall aim to remove the need for the deploy.xml file
> entirely. All the information in the file is already known to the Tuscany
> code - either we shall generate the file dynamically, or - ODE willing - we
> shall pass the information to ODE in-memory, avoiding the need for a file at
> all.
>
>
> You will find that the BPEL Sample applications and the BPEL iTests have
> been adjusted to use this new format for the deploy.xml file.
>
>
> Yours, Mike.
>
** IMPLEMENTATION.BPEL USERS ** - updated implementation-bpel code in trunk - affects your BPEL applications
Folks,
I've just committed some changes to the implementation-bpel and implementatio-bpel-ode code in trunk
which fix some issues relating to exposing BPEL processes using Web services (and other remote
protocols).
These changes have an impact on the content of the deploy.xml file that is associated with your BPEL
applications. In order to work correctly, you will need to ensure that your deploy.xml file
corresponds to the following pattern:
http://www.apache.org/ode/schemas/dd/2007/03";
xmlns:tns="http://helloworld";
xmlns:helloworld="http://helloworld";
xmlns:greetings="http://greetings";
xmlns:tus="http://tuscany.apache.org";>
true
You must ensure:
a) Each partner link in your BPEL process is declared using either a (for a service)
or using a for a reference.
b) Each and must use the partnerLink name, as declared in
your BPEL process.
c) The and elements each have a single child element. The
elements have name and port attributes. The NAME attribute MUST be set to the same name
as the partnerLink and MUST be prefixed by a prefix which references the namespace
"http://tuscany.apache.org"; ("tus" in the example above). The port attribute can be set to any name
(it must be present but it is not actually used for anything significant).
Sorry for forcing this change on you all, but the previous version of the code had a mixup over the
name of the services and references as used by the ODE BPEL engine - this change fixes that problem.
In the next week, we shall aim to remove the need for the deploy.xml file entirely. All the
information in the file is already known to the Tuscany code - either we shall generate the file
dynamically, or - ODE willing - we shall pass the information to ODE in-memory, avoiding the need
for a file at all.
You will find that the BPEL Sample applications and the BPEL iTests have been adjusted to use this
new format for the deploy.xml file.
Yours, Mike.
[jira] Resolved: (TUSCANY-1716) implementation.bpel build issue
[ https://issues.apache.org/jira/browse/TUSCANY-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luciano Resende resolved TUSCANY-1716. -- Resolution: Fixed Assignee: Luciano Resende This issue is now solved on new surefire releases and trunk is working as expected now. > implementation.bpel build issue > --- > > Key: TUSCANY-1716 > URL: https://issues.apache.org/jira/browse/TUSCANY-1716 > Project: Tuscany > Issue Type: Bug > Components: Java SCA BPEL Implementation Extension >Affects Versions: Java-SCA-Next >Reporter: Luciano Resende >Assignee: Luciano Resende > Fix For: Java-SCA-Next > > > See threads for more information : > http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg23507.html > and > http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg23439.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-1716) implementation.bpel build issue
[ https://issues.apache.org/jira/browse/TUSCANY-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luciano Resende updated TUSCANY-1716: - Priority: Major (was: Blocker) Affects Version/s: (was: Java-SCA-1.0) Java-SCA-Next Fix Version/s: (was: Java-SCA-1.0) Java-SCA-Next Moving to SCA next, as we are ok by disabling the tests for 1.0 > implementation.bpel build issue > --- > > Key: TUSCANY-1716 > URL: https://issues.apache.org/jira/browse/TUSCANY-1716 > Project: Tuscany > Issue Type: Bug > Components: Java SCA BPEL Implementation Extension >Affects Versions: Java-SCA-Next >Reporter: Luciano Resende > Fix For: Java-SCA-Next > > > See threads for more information : > http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg23507.html > and > http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg23439.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Created: (TUSCANY-1716) implementation.bpel build issue
Hi, I'm OK either way. Just want to point out that the scope of the SNAPSHOT reference will be only for that module and it will be used for the build time. There are usually SNAPSHOT versions of plugins involved in maven build especially when the "mvn :" command is used. Thanks, Raymond - Original Message - From: "Jean-Sebastien Delfino" <[EMAIL PROTECTED]> To: Sent: Sunday, September 16, 2007 7:02 PM Subject: Re: [jira] Created: (TUSCANY-1716) implementation.bpel build issue Jean-Sebastien Delfino wrote: Luciano Resende wrote: Could you apply to trunk at least ? Then we could verify we are not seeing the issue anymore, as it looks like your stackTrace and the one from Ant and myself are different. On 9/16/07, Raymond Feng <[EMAIL PROTECTED]> wrote: Hi, I found a fix for this problem: using surefire plugin version 2.3.1-SNAPSHOT which fixes http://jira.codehaus.org/browse/SUREFIRE-322. It's not perfect to reference SNAPSHOT versions but I think it's OK as a workaround to run the test case. I'll check in the fix if there is no objections. Thanks, Raymond I'm not sure that we should reference a SNAPSHOT in a release... How about turning that particular test case off for now in the branch as we know that everything works OK on our side with the fixed surefire plugin? I reviewed SUREFIRE-322, it looks like a Windows only problem, perhaps the simplest is to disable the test case on Windows only? It builds OK for me on both Linux RHEL5 and Ubuntu. -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Created: (TUSCANY-1716) implementation.bpel build issue
Jean-Sebastien Delfino wrote: Luciano Resende wrote: Could you apply to trunk at least ? Then we could verify we are not seeing the issue anymore, as it looks like your stackTrace and the one from Ant and myself are different. On 9/16/07, Raymond Feng <[EMAIL PROTECTED]> wrote: Hi, I found a fix for this problem: using surefire plugin version 2.3.1-SNAPSHOT which fixes http://jira.codehaus.org/browse/SUREFIRE-322. It's not perfect to reference SNAPSHOT versions but I think it's OK as a workaround to run the test case. I'll check in the fix if there is no objections. Thanks, Raymond I'm not sure that we should reference a SNAPSHOT in a release... How about turning that particular test case off for now in the branch as we know that everything works OK on our side with the fixed surefire plugin? I reviewed SUREFIRE-322, it looks like a Windows only problem, perhaps the simplest is to disable the test case on Windows only? It builds OK for me on both Linux RHEL5 and Ubuntu. -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Created: (TUSCANY-1716) implementation.bpel build issue
Luciano Resende wrote: Could you apply to trunk at least ? Then we could verify we are not seeing the issue anymore, as it looks like your stackTrace and the one from Ant and myself are different. On 9/16/07, Raymond Feng <[EMAIL PROTECTED]> wrote: Hi, I found a fix for this problem: using surefire plugin version 2.3.1-SNAPSHOT which fixes http://jira.codehaus.org/browse/SUREFIRE-322. It's not perfect to reference SNAPSHOT versions but I think it's OK as a workaround to run the test case. I'll check in the fix if there is no objections. Thanks, Raymond I'm not sure that we should reference a SNAPSHOT in a release... How about turning that particular test case off for now in the branch as we know that everything works OK on our side with the fixed surefire plugin? -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Created: (TUSCANY-1716) implementation.bpel build issue
Could you apply to trunk at least ? Then we could verify we are not seeing the issue anymore, as it looks like your stackTrace and the one from Ant and myself are different. On 9/16/07, Raymond Feng <[EMAIL PROTECTED]> wrote: > Hi, > > I found a fix for this problem: using surefire plugin version 2.3.1-SNAPSHOT > which fixes http://jira.codehaus.org/browse/SUREFIRE-322. It's not perfect > to reference SNAPSHOT versions but I think it's OK as a workaround to run > the test case. > > I'll check in the fix if there is no objections. > > Thanks, > Raymond > > - Original Message - > From: "ant elder" <[EMAIL PROTECTED]> > To: "tuscany-dev" > Sent: Sunday, September 16, 2007 4:32 PM > Subject: Fwd: [jira] Created: (TUSCANY-1716) implementation.bpel build issue > > > > This is raised as a blocker so whats peoples feelings on it? I'd like bpel > > to get in 1.0 as well but what should i do tomorrow morning if this is > > still > > unresolved? Defer the JIRA or hold the RC vote till tomorrow evening in > > the > > hope that will be time to find a resolution? > > > > ...ant > > > > -- Forwarded message -- > > From: Luciano Resende (JIRA) > > Date: Sep 17, 2007 12:13 AM > > Subject: [jira] Created: (TUSCANY-1716) implementation.bpel build issue > > To: tuscany-dev@ws.apache.org > > > > implementation.bpel build issue > > --- > > > > Key: TUSCANY-1716 > > URL: https://issues.apache.org/jira/browse/TUSCANY-1716 > > Project: Tuscany > > Issue Type: Bug > > Components: Java SCA BPEL Implementation Extension > >Affects Versions: Java-SCA-1.0 > >Reporter: Luciano Resende > >Priority: Blocker > > Fix For: Java-SCA-1.0 > > > > > > See threads for more information : > > > > http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg23507.html > > and > > http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg23439.html > > > > -- > > This message is automatically generated by JIRA. > > - > > You can reply to this email to add a comment to the issue online. > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Created: (TUSCANY-1716) implementation.bpel build issue
Hi, I found a fix for this problem: using surefire plugin version 2.3.1-SNAPSHOT which fixes http://jira.codehaus.org/browse/SUREFIRE-322. It's not perfect to reference SNAPSHOT versions but I think it's OK as a workaround to run the test case. I'll check in the fix if there is no objections. Thanks, Raymond - Original Message - From: "ant elder" <[EMAIL PROTECTED]> To: "tuscany-dev" Sent: Sunday, September 16, 2007 4:32 PM Subject: Fwd: [jira] Created: (TUSCANY-1716) implementation.bpel build issue This is raised as a blocker so whats peoples feelings on it? I'd like bpel to get in 1.0 as well but what should i do tomorrow morning if this is still unresolved? Defer the JIRA or hold the RC vote till tomorrow evening in the hope that will be time to find a resolution? ...ant -- Forwarded message -- From: Luciano Resende (JIRA) Date: Sep 17, 2007 12:13 AM Subject: [jira] Created: (TUSCANY-1716) implementation.bpel build issue To: tuscany-dev@ws.apache.org implementation.bpel build issue --- Key: TUSCANY-1716 URL: https://issues.apache.org/jira/browse/TUSCANY-1716 Project: Tuscany Issue Type: Bug Components: Java SCA BPEL Implementation Extension Affects Versions: Java-SCA-1.0 Reporter: Luciano Resende Priority: Blocker Fix For: Java-SCA-1.0 See threads for more information : http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg23507.html and http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg23439.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fwd: [jira] Created: (TUSCANY-1716) implementation.bpel build issue
This is raised as a blocker so whats peoples feelings on it? I'd like bpel to get in 1.0 as well but what should i do tomorrow morning if this is still unresolved? Defer the JIRA or hold the RC vote till tomorrow evening in the hope that will be time to find a resolution? ...ant -- Forwarded message -- From: Luciano Resende (JIRA) Date: Sep 17, 2007 12:13 AM Subject: [jira] Created: (TUSCANY-1716) implementation.bpel build issue To: tuscany-dev@ws.apache.org implementation.bpel build issue --- Key: TUSCANY-1716 URL: https://issues.apache.org/jira/browse/TUSCANY-1716 Project: Tuscany Issue Type: Bug Components: Java SCA BPEL Implementation Extension Affects Versions: Java-SCA-1.0 Reporter: Luciano Resende Priority: Blocker Fix For: Java-SCA-1.0 See threads for more information : http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg23507.html and http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg23439.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-1716) implementation.bpel build issue
implementation.bpel build issue --- Key: TUSCANY-1716 URL: https://issues.apache.org/jira/browse/TUSCANY-1716 Project: Tuscany Issue Type: Bug Components: Java SCA BPEL Implementation Extension Affects Versions: Java-SCA-1.0 Reporter: Luciano Resende Priority: Blocker Fix For: Java-SCA-1.0 See threads for more information : http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg23507.html and http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg23439.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Implementation.bpel
Just to add Luciano in order to get a feel of deploying a simple Bpel Process in ODE, do check this module [1] bpel-test It contains various examples (like HelloWorld etc..) where in required .bpel / .wsdl / deploy.xml are put in a directory [2] and the entire directory is deployed. The request / response expected from the bpel process are available in test.properties . This [3] will give a broad idea of when/how ode runtime is initialized , made to run , deployed and finally invoked. [1] - http://svn.apache.org/repos/asf/incubator/ode/trunk/bpel-test/ [2] - http://svn.apache.org/repos/asf/incubator/ode/trunk/bpel-test/src/test/resources/bpel/2.0/HelloWorld2/ [3] - http://svn.apache.org/repos/asf/incubator/ode/trunk/bpel-test/src/main/java/org/apache/ode/test/BPELTestAbstract.java ~~ Sam... _ On 6/25/07, Luciano Resende <[EMAIL PROTECTED]> wrote: Hi Matthieu 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. One thing I noticed is that some required databases (ode-work/jpadb) is not being created (if not present)... is this a configuration issue as we were discussing on [2] or something that we need to investigate further ? [1] http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+implementation.bpel [2] http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg19068.html -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --
Re: Implementation.bpel
As for the databases, if it helps, I have some places that I uploaded the derby db into src/test/resources [1]. This might be a workaround to have things working for the time being [1] https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/modules/implementation-das/src/test/resources/ On 6/25/07, Matthieu Riou <[EMAIL PROTECTED]> wrote: 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, thanks! One thing I noticed is that some required databases > (ode-work/jpadb) is not being created (if not present)... is this a > configuration issue as we were discussing on [2] or something that we > need to investigate further ? Actually that's something I indicated in the bug report. The database is required if we want meaningful tests and for now it must be copied manually. I'll try to make Maven2 download it and unzip it somewhere, I just have to pay the time toll that goes with any non-trivial Maven2 task :) I'll try to have another patch ready today or tomorrow. Cheers, Matthieu [1] > http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+implementation.bpel > [2] http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg19068.html > > -- > Luciano Resende > Apache Tuscany Committer > http://people.apache.org/~lresende > http://lresende.blogspot.com/ > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Implementation.bpel
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, thanks! One thing I noticed is that some required databases (ode-work/jpadb) is not being created (if not present)... is this a configuration issue as we were discussing on [2] or something that we need to investigate further ? Actually that's something I indicated in the bug report. The database is required if we want meaningful tests and for now it must be copied manually. I'll try to make Maven2 download it and unzip it somewhere, I just have to pay the time toll that goes with any non-trivial Maven2 task :) I'll try to have another patch ready today or tomorrow. Cheers, Matthieu [1] http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+implementation.bpel [2] http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg19068.html -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Implementation.bpel
Hi Matthieu 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. One thing I noticed is that some required databases (ode-work/jpadb) is not being created (if not present)... is this a configuration issue as we were discussing on [2] or something that we need to investigate further ? [1] http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+implementation.bpel [2] http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg19068.html -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
