[jira] Created: (ODE-351) new listInstancesWithVariables method in InstanceMenager
new listInstancesWithVariables method in InstanceMenager Key: ODE-351 URL: https://issues.apache.org/jira/browse/ODE-351 Project: ODE Issue Type: New Feature Components: Management Reporter: Pawel Stawicki Priority: Minor it would be nice to have a method like listInstancesWithVariables in InstanceMenager. the method should list instances with a list of some variables. It would be simpler to ask for instances, and get some root-scope variables indicating the state of the instance. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-351) new listInstancesWithVariables method in InstanceMenager
[ https://issues.apache.org/jira/browse/ODE-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pawel Stawicki updated ODE-351: --- Attachment: listInstancesWithVariables.diff a proposition diff for the listInstancesWithVariables method. > new listInstancesWithVariables method in InstanceMenager > > > Key: ODE-351 > URL: https://issues.apache.org/jira/browse/ODE-351 > Project: ODE > Issue Type: New Feature > Components: Management >Reporter: Pawel Stawicki >Priority: Minor > Attachments: listInstancesWithVariables.diff > > > it would be nice to have a method like listInstancesWithVariables in > InstanceMenager. > the method should list instances with a list of some variables. > It would be simpler to ask for instances, and get some root-scope variables > indicating the state of the instance. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ODE-352) Type attribute replaces xsi-type attribute value
Type attribute replaces xsi-type attribute value Key: ODE-352 URL: https://issues.apache.org/jira/browse/ODE-352 Project: ODE Issue Type: Bug Affects Versions: 1.3 Reporter: Colin Fix For: 1.3 This is related to ODE-343, see for context. The xsi:type attribute goes missing when you define a type attribute. Example: http://www.w3.org/2001/XMLSchema-instance"; xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:myns="myns"> Test message fooo -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Quick Question - Reg timeout.
Hi All, Can I catch a timeout exception in a tag or a tag so that in case of such a scenario I could do necessary actions for that particular request before it dies off. e.g. Say my request has lifecycle with the following conditional stages (Stage1,Stage2,Stage3,FAIL). If the request(in Stage2) is waiting for a response from another webservice but it gets timed-out. In such scenario I want to update the particular request's status in my DB as 'Fail' before the BPEL instance dies off. Please do suggest if there is some workaround for this problem. Thank you, Vineesh. -- View this message in context: http://www.nabble.com/Quick-Question---Reg-timeout.-tp18756434p18756434.html Sent from the Apache Ode Dev mailing list archive at Nabble.com.
Re: Quick Question - Reg timeout.
On Thu, Jul 31, 2008 at 7:56 AM, Vineesh Thomas <[EMAIL PROTECTED]> wrote: > > Hi All, > > Can I catch a timeout exception in a tag or a tag so > that > in case of such a scenario I could do necessary actions for that particular > request before it dies off. > > e.g. > > Say my request has lifecycle with the following conditional stages > (Stage1,Stage2,Stage3,FAIL). > If the request(in Stage2) is waiting for a response from another webservice > but it gets timed-out. In such scenario I want to update the particular > request's status in my DB as 'Fail' before the BPEL instance dies off. > > > Please do suggest if there is some workaround for this problem. > A timeout is normally a failure, not a fault. But we've implemented a mechanism to deal with failures in different ways (one of of them being throwing a fault instead of failing). You can learn more here: http://ode.apache.org/activity-failure-and-recovery.html Matthieu > > Thank you, > > Vineesh. > -- > View this message in context: > http://www.nabble.com/Quick-Question---Reg-timeout.-tp18756434p18756434.html > Sent from the Apache Ode Dev mailing list archive at Nabble.com. > >
[jira] Updated: (ODE-293) AJAX based Monitoring and Management Console for ODE(Axis2 Integration)
[ https://issues.apache.org/jira/browse/ODE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milinda Lakmal Pathirage updated ODE-293: - Attachment: mmc_v4.tar.gz This version of management Console have cross browser compatibility. I tested it with Firefox 3 and IE 6. This version contains Landing Page, Process page, Instance Page and Deployment. Deployment of process directly through management console is still under development because Axis2 1.3 release has bugs (https://issues.apache.org/jira/browse/AXIS2-3394). It was fixed in 1.4 release. I am still working on adding custom multi part message builder to Axis2 used in ODE by making required modifications according to the patches provided in above JIRA. And also I am extending the capability provided by ODE 1_x branch doGet servelet method to support getting bundle imformation directly by giving process name. Currently it is using some kind of hierarchy of html pages to view deployment bundle content. After finishing this REST style API, I'll add them to management console and you can view it by clicking details button on each process. Please feel free to comment on this. > AJAX based Monitoring and Management Console for ODE(Axis2 Integration) > --- > > Key: ODE-293 > URL: https://issues.apache.org/jira/browse/ODE-293 > Project: ODE > Issue Type: New Feature >Reporter: Milinda Lakmal Pathirage > Attachments: mmc.zip, mmc_v2.zip, mmc_v3.zip, mmc_v4.tar.gz > > > AJAX based Monitoring & Management Console for Apache ODE is a project aimed > at implementing Ajax based web application that expose monitoring and > management capabilities support by Apache ODE BPEL engine and integrate it > with ODE's Axis2 deployment. > This will enable users to gain full advantage of the ODE, by making deploying > BPEL deployment bundles easier, allowing them to monitor running process > models, instances, engine status, and providing easy to use interface to > suspend/resume and start/retire process instances and models. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
