ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Denis Weerasiri (JIRA)" <j...@apache.org>
Subject [jira] Updated: (ODE-565) Adding web based BPEL debugging support
Date Thu, 09 Jul 2009 05:46:15 GMT

     [ https://issues.apache.org/jira/browse/ODE-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Denis Weerasiri updated ODE-565:

    Attachment: fromDenis.zip

Here I have attached

   1. oryx-ode-integration-on-BPMNLayouterInformatiCup.patch - contains the modifications.
I used the branch (http://oryx-editor.googlecode.com/svn/branches/BPMNLayouterInformatiCup/)
   2. fromDenis.zip - contains the external javascripts, which are used to manipulate server
side functionality.

Here are the steps to test the patch

   1. Add the patch to the BPMNLayouterInformatiCup branch source
   2. deploy it in tomcat.
   3. Extract, Copy, and paste the directory "fromDenis" to the deployed "oryx" directory.
   4. Call http://localhost:8080/oryx/fromDenis/testMovi/basic.xhtml

In this basic.xhtml , I've commented on important functionalities for your convenience.

When you try this you will see the final output is a oryx editor page which overlapped with
the PNG generarated from MOVI. This is bacause when I create the editor instance in the basic.xhtml,
it renders into DOM. I asked about this in the b3mn mailing list. But I couldn't find a workable
solution. I would be great if you can give me a solution to avoid overlapping of these two.

After this I can delete the files step by step in deployed "oryx" directory and create a working
directory inside ODE with oryx functionalities.
And There are some improvements needed to be done, such as reducing the ping-pong of data
between client and server when the layouting happens.

Best Regards,
Denis Weerasiri.

> Adding web based BPEL debugging support
> ---------------------------------------
>                 Key: ODE-565
>                 URL: https://issues.apache.org/jira/browse/ODE-565
>             Project: ODE
>          Issue Type: New Feature
>          Components: Management API
>            Reporter: Denis Weerasiri
>         Attachments: fromDenis.zip, ODE-565_1.patch, ODE-565_2.patch, ODE-565_3.patch,
> In order to run a business process successfully in ODE, it is a must to verify and debug
its BPEL process model before deploying it in Apache ODE. So exposing the process debugging
functionality as a web services such that a user can remotely debug a process and adding a
graphical monitoring console allows for setting breakpoints and to monitor the run time details
of that process will increase the usability as well as popularity of the work-flow engine
we are concerning. Currently though the debugging functionality is included in Apache ODE,
it's not really been tested for the current Apache ODE and it's not exposed as a web service.
> Web based debugging support for Apache ODE is a project aimed at exposing the debugging
functionality as a web service and adding an AJAX based monitoring console to which consist
of a graphical representation of a particular business process, allows for setting breakpoints
to activities and allows for monitoring that process being debugged.
> This will enable users to gain full advantage of the ODE, by reducing design time and
the testing time during the process development by allowing them to remotely debug a business
process, set breakpoints to process activities, modify variables and to monitor the run rime
variable information.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message