Subject: Re: [bpel-dev] Re:GSOC project ideas
Sent by:
bpel-dev-bounces@xxxxxxxxxxx
Hi Simon,
Thanks for the quick response. Looking forward to your suggestions.
Regards,
Chamith Buddhika
On Wed, Feb 25, 2009 at 5:31 PM, Simon D Moser <
SMOSER@xxxxxxxxxx> wrote:
Hi Buddhika,
I am currently preparing a set of options ... pls. give me another day or
two
Mit freundlichen Grüßen / Kind regards
Simon Daniel Moser
Team Lead BPEL Editor - Websphere Integration Developer (WID)
IBM Software Group, Application and Integration Middleware Software
Business Process Solutions Development 1
Phone: +49-7031-16-4304 IBM Deutschland
(Embedded
image moved
to file:
pic11157.gif)
Fax: +49-7031-16-4890 Schoenaicher Str. 220
E-Mail:
smoser@xxxxxxxxxx 71032 Boeblingen
Germany
IBM Deutschland
Research &
Development
GmbH /
Vorsitzender des
Aufsichtsrats:
Martin Jetter
Geschäftsführung:
Erich Baier
Sitz der
Gesellschaft:
Böblingen /
Registergericht:
Amtsgericht
Stuttgart, HRB
243294
From: buddhika chamith <
chamibuddhika@xxxxxxxxx>
To: "BPEL Designer project developer discussions." <
bpel-dev@xxxxxxxxxxx>
Date: 25.02.2009 11:32
Subject: Re: [bpel-dev] Re:GSOC project ideas
Sent by:
bpel-dev-bounces@xxxxxxxxxxx
Hi all,
I would like to have any follow on suggestions on Saminda's idea so that
I
can get started on it or any other ideas that are relevant to extending
Eclipse-Bpel project for GSOC 2009. Any suggestions are greatly
appreciated.
Regards,
Chamith Buddhika.
On Fri, Feb 20, 2009 at 2:06 PM, buddhika chamith <
chamibuddhika@xxxxxxxxx>
wrote:
Hi Saminda,
Thanks for the idea. It seems a good idea to me. I think what you meant
was providing some functionality similar to JUnit for testing BPEL
processes. This requires the designer of the BPEL process to be aware of
the expected outputs from the process for specific test cases. So this
requires on the part of the test case designer, some degree of
understanding about the responses returned from partner web services for
a particular test case as well, if I'm not mistaken.
A little issue that came up to me was, supposing that we only have WSDLs
of respective partner web services, determining the nature of the
partner
web service reponse for a specific test case scenario can be tricky
since
we may not know internal logic provided by the service. So for that I
think we should have a set of responses collected from the respective
partner web service for the expected outmessage to be sent by the
process
for the provided process test input, beforehand. Then we base our
assertions on actual returned web service reponse with pre-collected web
service response.
I don't know whether I made myself clear enough on this. But I'm
eargerly
looking forward to hear about any suggestions, enhancements on this idea
or other interesting project ideas.
Best Regards,
Chamith Buddhika
On Thu, Feb 19, 2009 at 12:05 PM, Saminda Wijeratne <
samindaw@xxxxxxxx>
wrote:
tough luck Buddhika. Since Nandika has already been working on the
idea,
I suggest you think of other aspects of a bpel processes. One idea came
to me was to automate test cases. Testing manually a bpel process for
many scenarios each time there are some modifications to the bpel file
is a time consuming and inefficient process. If we could get the plugin
to create test cases for bpel process and allow the users to
run/automate the test cases using the ode engine it would benefit the
developer greatly. Only drawback is that once a bpel is created,
normally the process is never changed. So after that there will be no
more use for the created test cases. May be we can extend the idea.
Best Regards,
Saminda
buddhika chamith wrote:
Hi all,
Thanks for the idea. But since Nandika seems to be already working on
developing debugging support for BPEL designer (he privately informed
me of this after the idea came up on the list as well) I think I will
have to rule out the possibility of doing this as my GSOC project,
though I would have liked to proceed. So any more ideas on areas that
can be improved, are greatly appreciated.
Best Regards,
Chamith Buddhika.
------------------------------------------------------------------------
_______________________________________________
bpel-dev mailing list
bpel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/bpel-dev
_______________________________________________
bpel-dev mailing list
bpel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/bpel-dev
_______________________________________________
bpel-dev mailing list
bpel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/bpel-dev
_______________________________________________
bpel-dev mailing list
bpel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/bpel-dev
_______________________________________________
bpel-dev mailing list
bpel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/bpel-dev
