You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by kodeninja <ko...@gmail.com> on 2009/10/08 11:33:34 UTC
Trying to understand the "failureHandling" ode extension
Howdy,
In a <failureHandling> element, do retryFor and retryDelay values apply only
to failures? If the invoked operation throws a fault, will the retry still
happen?
Taking a hypothetical example:
<invoke operation="getStockQuote" partnerLink="stockPL" portType="stockPort"
inputVariable="stockSymbol" outputVariable="stockQuote">
<failureHandling>
<faultOnFailure>true</faultOnFailure>
<retryFor>5</retryFor>
<retryDelay>30</retryDelay>
</failureHandling>
<catchAll>
... <!-- Do something -->
</catchAll>
</invoke>
So, in the above example, if the operation throws a fault, the catchAll
would be executed. After that, would the operation still be retried? Or is
that retries happen only for failures, and not faults?
-Kodeninja
--
View this message in context: http://www.nabble.com/Trying-to-understand-the-%22failureHandling%22-ode-extension-tp25801007p25801007.html
Sent from the Apache Ode User mailing list archive at Nabble.com.
Re: Trying to understand the "failureHandling" ode extension
Posted by Alex Boisvert <bo...@intalio.com>.
No, because the extension only deals with failures.
alex
On Thu, Oct 8, 2009 at 10:09 PM, kodeninja <ko...@gmail.com> wrote:
>
> Alex, I understand what failures and faults are in ODE. What I want to find
> out is that if a fault occurs during an invoke call, does it also get
> retried the way failures do, when using the <retryFor> ode extension?
>
> -Kodeninja
>
>
> Alex Boisvert-3 wrote:
> >
> > A failure here is described as anything going wrong (network timeout,
> > service unavailable, server error...) other than faults described in the
> > service description (WSDL).
> >
> > alex
> >
>
> --
> View this message in context:
> http://www.nabble.com/Trying-to-understand-the-%22failureHandling%22-ode-extension-tp25801007p25815571.html
> Sent from the Apache Ode User mailing list archive at Nabble.com.
>
>
Re: Trying to understand the "failureHandling" ode extension
Posted by kodeninja <ko...@gmail.com>.
Alex, I understand what failures and faults are in ODE. What I want to find
out is that if a fault occurs during an invoke call, does it also get
retried the way failures do, when using the <retryFor> ode extension?
-Kodeninja
Alex Boisvert-3 wrote:
>
> A failure here is described as anything going wrong (network timeout,
> service unavailable, server error...) other than faults described in the
> service description (WSDL).
>
> alex
>
--
View this message in context: http://www.nabble.com/Trying-to-understand-the-%22failureHandling%22-ode-extension-tp25801007p25815571.html
Sent from the Apache Ode User mailing list archive at Nabble.com.
Re: Trying to understand the "failureHandling" ode extension
Posted by Alex Boisvert <bo...@intalio.com>.
A failure here is described as anything going wrong (network timeout,
service unavailable, server error...) other than faults described in the
service description (WSDL).
alex
On Thu, Oct 8, 2009 at 2:33 AM, kodeninja <ko...@gmail.com> wrote:
>
> Howdy,
>
> In a <failureHandling> element, do retryFor and retryDelay values apply
> only
> to failures? If the invoked operation throws a fault, will the retry still
> happen?
>
> Taking a hypothetical example:
>
> <invoke operation="getStockQuote" partnerLink="stockPL"
> portType="stockPort"
> inputVariable="stockSymbol" outputVariable="stockQuote">
>
> <failureHandling>
> <faultOnFailure>true</faultOnFailure>
> <retryFor>5</retryFor>
> <retryDelay>30</retryDelay>
> </failureHandling>
>
> <catchAll>
> ... <!-- Do something -->
> </catchAll>
>
> </invoke>
>
> So, in the above example, if the operation throws a fault, the catchAll
> would be executed. After that, would the operation still be retried? Or is
> that retries happen only for failures, and not faults?
>
> -Kodeninja
> --
> View this message in context:
> http://www.nabble.com/Trying-to-understand-the-%22failureHandling%22-ode-extension-tp25801007p25801007.html
> Sent from the Apache Ode User mailing list archive at Nabble.com.
>
>
Re: How to use org.apache.axiom.om within the project
ode-bpel-runtime
Posted by Pascal Aho <P....@gmx.net>.
Hi Milinda,
Thank you for your Answer. It works fine.
Cheers,
Pascal.
-------- Original-Nachricht --------
> Datum: Tue, 13 Oct 2009 22:51:33 +0530
> Von: Milinda Pathirage <mi...@gmail.com>
> An: user@ode.apache.org
> Betreff: Re: How to use org.apache.axiom.om within the project ode-bpel-runtime
> You need to modify build script(Rakefile ) to get build working. You need
> to
> AXIOM dependency to ode-bpel-runtime modules compile.with projects
> section.
>
> Before adding AXIOM:
>
> desc "ODE Runtime Engine"
> define "bpel-runtime" do
> compile.from apt
> compile.with projects("bpel-api", "bpel-compiler", "bpel-dao",
> "bpel-epr", "bpel-obj", "bpel-schemas",
> "bpel-store", "jacob", "jacob-ap", "utils", "agents"),
> COMMONS.logging, COMMONS.collections, COMMONS.httpclient, JAXEN,
> JAVAX.persistence, JAVAX.stream, SAXON, WSDL4J, XMLBEANS
>
> test.with projects("scheduler-simple", "dao-jpa", "dao-hibernate",
> "bpel-epr"),
> BACKPORT, COMMONS.pool, COMMONS.lang, DERBY, JAVAX.connector,
> JAVAX.transaction,
> GERONIMO.transaction, GERONIMO.kernel, GERONIMO.connector, TRANQL,
> HSQLDB, JAVAX.ejb,
> LOG4J, XERCES, Buildr::OpenJPA::REQUIRES, XALAN
>
> package :jar
> end
>
>
>
> After Adding AXIOM:
>
> desc "ODE Runtime Engine"
> define "bpel-runtime" do
> compile.from apt
> compile.with projects("bpel-api", "bpel-compiler", "bpel-dao",
> "bpel-epr", "bpel-obj", "bpel-schemas",
> "bpel-store", "jacob", "jacob-ap", "utils", "agents"),
> COMMONS.logging, COMMONS.collections, COMMONS.httpclient, AXIOM,
> JAXEN, JAVAX.persistence, JAVAX.stream, SAXON, WSDL4J, XMLBEANS
>
> test.with projects("scheduler-simple", "dao-jpa", "dao-hibernate",
> "bpel-epr"),
> BACKPORT, COMMONS.pool, COMMONS.lang, DERBY, JAVAX.connector,
> JAVAX.transaction,
> GERONIMO.transaction, GERONIMO.kernel, GERONIMO.connector, TRANQL,
> HSQLDB, JAVAX.ejb,
> LOG4J, XERCES, Buildr::OpenJPA::REQUIRES, XALAN
>
> package :jar
> end
>
>
>
>
> On Tue, Oct 13, 2009 at 2:22 AM, Pascal Aho <P....@gmx.net> wrote:
>
> >
> > Hi all,
> >
> > I would like to use the following library
> > org.apache.axiom.om.OMElement;
> > org.apache.axiom.om.impl.builder.StAXOMBuilder;
> >
> > within the project ode-bpel-runtime (I use ODE 1.3.2).
> >
> > I add the axiom-api-1.2.5.jar to the project. But when I build the
> project
> > I get several errors but in eclipse I don't get any error. It can not
> > locate the packages
> > org.apache.axiom.om and org.apache.axiom.om.impl
> >
> > I add the jar file like this:
> > 1. Right click the project name and navigate to Build Path.
> > 2. Select Configure Build Path... and the project properties window
> will
> > appear showing your build path configurations.
> > 3. Select the Libraries tab.
> > 4. Click Add External JARs...
> > 5. Locate and select the JARs you want and click Open. The JARs will
> now
> > appear in the list of libraries in the build path.
> >
> > I saw it doesn't look like the other libraries.
> >
> > Why it doesn't work?
> >
> > Thanks
> >
> > Pascal
> >
> > --
> > Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox
> 3.5
> > -
> > sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser
> >
>
>
>
> --
> Milinda Pathirage
> Senior Software Engineer & Product Manager WSO2 BPS; http://wso2.org/bps
> WSO2 Inc.; http://wso2.com
> E-mail: milinda@wso2.com, milinda.pathirage@gmail.com
> Web: http://mpathirage.com
> Blog: http://blog.mpathirage.com
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
Re: How to use org.apache.axiom.om within the project
ode-bpel-runtime
Posted by Milinda Pathirage <mi...@gmail.com>.
You need to modify build script(Rakefile ) to get build working. You need to
AXIOM dependency to ode-bpel-runtime modules compile.with projects section.
Before adding AXIOM:
desc "ODE Runtime Engine"
define "bpel-runtime" do
compile.from apt
compile.with projects("bpel-api", "bpel-compiler", "bpel-dao",
"bpel-epr", "bpel-obj", "bpel-schemas",
"bpel-store", "jacob", "jacob-ap", "utils", "agents"),
COMMONS.logging, COMMONS.collections, COMMONS.httpclient, JAXEN,
JAVAX.persistence, JAVAX.stream, SAXON, WSDL4J, XMLBEANS
test.with projects("scheduler-simple", "dao-jpa", "dao-hibernate",
"bpel-epr"),
BACKPORT, COMMONS.pool, COMMONS.lang, DERBY, JAVAX.connector,
JAVAX.transaction,
GERONIMO.transaction, GERONIMO.kernel, GERONIMO.connector, TRANQL,
HSQLDB, JAVAX.ejb,
LOG4J, XERCES, Buildr::OpenJPA::REQUIRES, XALAN
package :jar
end
After Adding AXIOM:
desc "ODE Runtime Engine"
define "bpel-runtime" do
compile.from apt
compile.with projects("bpel-api", "bpel-compiler", "bpel-dao",
"bpel-epr", "bpel-obj", "bpel-schemas",
"bpel-store", "jacob", "jacob-ap", "utils", "agents"),
COMMONS.logging, COMMONS.collections, COMMONS.httpclient, AXIOM,
JAXEN, JAVAX.persistence, JAVAX.stream, SAXON, WSDL4J, XMLBEANS
test.with projects("scheduler-simple", "dao-jpa", "dao-hibernate",
"bpel-epr"),
BACKPORT, COMMONS.pool, COMMONS.lang, DERBY, JAVAX.connector,
JAVAX.transaction,
GERONIMO.transaction, GERONIMO.kernel, GERONIMO.connector, TRANQL,
HSQLDB, JAVAX.ejb,
LOG4J, XERCES, Buildr::OpenJPA::REQUIRES, XALAN
package :jar
end
On Tue, Oct 13, 2009 at 2:22 AM, Pascal Aho <P....@gmx.net> wrote:
>
> Hi all,
>
> I would like to use the following library
> org.apache.axiom.om.OMElement;
> org.apache.axiom.om.impl.builder.StAXOMBuilder;
>
> within the project ode-bpel-runtime (I use ODE 1.3.2).
>
> I add the axiom-api-1.2.5.jar to the project. But when I build the project
> I get several errors but in eclipse I don't get any error. It can not
> locate the packages
> org.apache.axiom.om and org.apache.axiom.om.impl
>
> I add the jar file like this:
> 1. Right click the project name and navigate to Build Path.
> 2. Select Configure Build Path... and the project properties window will
> appear showing your build path configurations.
> 3. Select the Libraries tab.
> 4. Click Add External JARs...
> 5. Locate and select the JARs you want and click Open. The JARs will now
> appear in the list of libraries in the build path.
>
> I saw it doesn't look like the other libraries.
>
> Why it doesn't work?
>
> Thanks
>
> Pascal
>
> --
> Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5
> -
> sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser
>
--
Milinda Pathirage
Senior Software Engineer & Product Manager WSO2 BPS; http://wso2.org/bps
WSO2 Inc.; http://wso2.com
E-mail: milinda@wso2.com, milinda.pathirage@gmail.com
Web: http://mpathirage.com
Blog: http://blog.mpathirage.com
How to use org.apache.axiom.om within the project ode-bpel-runtime
Posted by Pascal Aho <P....@gmx.net>.
Hi all,
I would like to use the following library
org.apache.axiom.om.OMElement;
org.apache.axiom.om.impl.builder.StAXOMBuilder;
within the project ode-bpel-runtime (I use ODE 1.3.2).
I add the axiom-api-1.2.5.jar to the project. But when I build the project
I get several errors but in eclipse I don't get any error. It can not
locate the packages
org.apache.axiom.om and org.apache.axiom.om.impl
I add the jar file like this:
1. Right click the project name and navigate to Build Path.
2. Select Configure Build Path... and the project properties window will
appear showing your build path configurations.
3. Select the Libraries tab.
4. Click Add External JARs...
5. Locate and select the JARs you want and click Open. The JARs will now
appear in the list of libraries in the build path.
I saw it doesn't look like the other libraries.
Why it doesn't work?
Thanks
Pascal
--
Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 -
sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser
Re: How works ODE?
Posted by Pascal Aho <P....@gmx.net>.
Hi Daniel,
Thank you for your Reply. I already got the answer. As you said I had to modify the buildfile which name is Rakefile with my ODE version.
It works fine now.
Cheers,
Pascal.
-------- Original-Nachricht --------
> Datum: Thu, 15 Oct 2009 19:34:16 +0200
> Von: Daniel Schleicher <sc...@googlemail.com>
> An: user@ode.apache.org
> Betreff: Re: How works ODE?
> Hi Pascal,
> I think your problem arises because you have to build ODE with buildr to
> get
> it running. Eclipse by default also builds the ODE projects in your
> workspace. This happens for example when you add new jars to the classpath
> of an eclipse project. BUT: This classpath of the eclipse project is not
> used when you build ODE with buildr. So, what you have to do to get you
> new
> jars bound into ODE, you have to read the buildfile comming with ODE. It
> is
> located in the root directory of the source distribution of ODE. The
> buildfile is called "Buildfile"
>
> Hope that helps.
>
> Best,
>
> Daniel
>
> On Mon, Oct 12, 2009 at 10:49 PM, Pascal Aho <P....@gmx.net> wrote:
>
> > Hi all,
> >
> > I would like to use the following library
> > org.apache.axiom.om.OMElement;
> > org.apache.axiom.om.impl.builder.StAXOMBuilder;
> >
> > within the project ode-bpel-runtime (I use ODE 1.3.2).
> >
> > I add the axiom-api-1.2.5.jar to the project. But when I build the
> project
> > I get several errors but in eclipse I don't get any error. It can not
> locate
> > the packages
> > org.apache.axiom.om and org.apache.axiom.om.impl
> >
> > I add the jar file like this:
> > 1. Right click the project name and navigate to Build Path.
> > 2. Select Configure Build Path... and the project properties window will
> > appear showing your build path configurations.
> > 3. Select the Libraries tab.
> > 4. Click Add External JARs...
> > 5. Locate and select the JARs you want and click Open. The JARs will now
> > appear in the list of libraries in the build path.
> >
> > I saw it doesn't look like the other libraries.
> >
> > Why it doesn't work?
> >
> > Thanks
> >
> > Pascal
> > --
> > GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
> > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
> >
--
Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 -
sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser
Re: How works ODE?
Posted by Daniel Schleicher <sc...@googlemail.com>.
Hi Pascal,
I think your problem arises because you have to build ODE with buildr to get
it running. Eclipse by default also builds the ODE projects in your
workspace. This happens for example when you add new jars to the classpath
of an eclipse project. BUT: This classpath of the eclipse project is not
used when you build ODE with buildr. So, what you have to do to get you new
jars bound into ODE, you have to read the buildfile comming with ODE. It is
located in the root directory of the source distribution of ODE. The
buildfile is called "Buildfile"
Hope that helps.
Best,
Daniel
On Mon, Oct 12, 2009 at 10:49 PM, Pascal Aho <P....@gmx.net> wrote:
> Hi all,
>
> I would like to use the following library
> org.apache.axiom.om.OMElement;
> org.apache.axiom.om.impl.builder.StAXOMBuilder;
>
> within the project ode-bpel-runtime (I use ODE 1.3.2).
>
> I add the axiom-api-1.2.5.jar to the project. But when I build the project
> I get several errors but in eclipse I don't get any error. It can not locate
> the packages
> org.apache.axiom.om and org.apache.axiom.om.impl
>
> I add the jar file like this:
> 1. Right click the project name and navigate to Build Path.
> 2. Select Configure Build Path... and the project properties window will
> appear showing your build path configurations.
> 3. Select the Libraries tab.
> 4. Click Add External JARs...
> 5. Locate and select the JARs you want and click Open. The JARs will now
> appear in the list of libraries in the build path.
>
> I saw it doesn't look like the other libraries.
>
> Why it doesn't work?
>
> Thanks
>
> Pascal
> --
> GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
> Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
>
Re: How works ODE?
Posted by Pascal Aho <P....@gmx.net>.
Hi all,
I would like to use the following library
org.apache.axiom.om.OMElement;
org.apache.axiom.om.impl.builder.StAXOMBuilder;
within the project ode-bpel-runtime (I use ODE 1.3.2).
I add the axiom-api-1.2.5.jar to the project. But when I build the project I get several errors but in eclipse I don't get any error. It can not locate the packages
org.apache.axiom.om and org.apache.axiom.om.impl
I add the jar file like this:
1. Right click the project name and navigate to Build Path.
2. Select Configure Build Path... and the project properties window will appear showing your build path configurations.
3. Select the Libraries tab.
4. Click Add External JARs...
5. Locate and select the JARs you want and click Open. The JARs will now appear in the list of libraries in the build path.
I saw it doesn't look like the other libraries.
Why it doesn't work?
Thanks
Pascal
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
Re: How works ODE?
Posted by Pascal Aho <P....@gmx.net>.
Hi Daniel,
Thank you for your reply. It was very helpfull.
Cheers,
Pascal.
-------- Original-Nachricht --------
> Datum: Sun, 11 Oct 2009 20:38:02 +0200
> Von: Daniel Schleicher <sc...@googlemail.com>
> An: user@ode.apache.org
> Betreff: Re: How works ODE?
> Hi Pascal,
> first of all a BPEL process ist always started with a SOAP message send to
> the endpoint the process is deployed. You can send SOAP messages to ode
> for
> example via http://www.soapui.org/.
>
> To see what happens when a SOAP message for a deployed BPEL process is
> received by ODE, please look into the class
> org.apache.ode.axis2.ODEService.
> In the method onAxisMessageExchange every incomming message is processed.
> Within this method the method invoke of the
> class org.apache.ode.bpel.engine.MyRoleMessageExchangeImpl is invoked.
> Debug
> here to see what happens further.
>
> Cheers,
>
> Daniel
>
> On Thu, Oct 8, 2009 at 12:47 PM, Pascal Aho <P....@gmx.net> wrote:
>
> > Hi all,
> >
> > I would like to extend the future of ODE. I use ODE 1.3.2. First of all
> I
> > try to understand how ODE now works. I have already read the
> > documentation(ODE - Architectural Overview, the JACOB Framework etc)but
> I
> > still have some points which are not clear for me.
> >
> > When I look through the code I don't see any relationship between the
> > deploy() method implemented in the class ProcessStoreImpl and the others
> > methods(OnScheduleJob, handleWorkEvent, createRuntimeContext which
> execute
> > instance.execute(), vpu.inject(process), etc) which lead to the
> execution of
> > a process.
> >
> > It is clear a process will be get executed only it has been compiled
> > succesfully and the .cbp is created. The compilation is done within the
> > deploy() method of ProcessStoreImpl.
> >
> >
> > I would like to see the point in the code where a order to execute a
> > process is issued.
> >
> > When the process beginns with a receive activity and the container
> receives
> > a message which targets a process the process will be executed.
> >
> > What happens in the case when the process starts with an invoke
> activity?
> >
> > Hopefully you understand my problem and could help me. It is very
> important
> > for me.
> >
> > Thank in advance.
> >
> > Pascal.
> >
> > --
> > GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
> > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
> >
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
Re: How works ODE?
Posted by Daniel Schleicher <sc...@googlemail.com>.
Hi Pascal,
first of all a BPEL process ist always started with a SOAP message send to
the endpoint the process is deployed. You can send SOAP messages to ode for
example via http://www.soapui.org/.
To see what happens when a SOAP message for a deployed BPEL process is
received by ODE, please look into the class org.apache.ode.axis2.ODEService.
In the method onAxisMessageExchange every incomming message is processed.
Within this method the method invoke of the
class org.apache.ode.bpel.engine.MyRoleMessageExchangeImpl is invoked. Debug
here to see what happens further.
Cheers,
Daniel
On Thu, Oct 8, 2009 at 12:47 PM, Pascal Aho <P....@gmx.net> wrote:
> Hi all,
>
> I would like to extend the future of ODE. I use ODE 1.3.2. First of all I
> try to understand how ODE now works. I have already read the
> documentation(ODE - Architectural Overview, the JACOB Framework etc)but I
> still have some points which are not clear for me.
>
> When I look through the code I don't see any relationship between the
> deploy() method implemented in the class ProcessStoreImpl and the others
> methods(OnScheduleJob, handleWorkEvent, createRuntimeContext which execute
> instance.execute(), vpu.inject(process), etc) which lead to the execution of
> a process.
>
> It is clear a process will be get executed only it has been compiled
> succesfully and the .cbp is created. The compilation is done within the
> deploy() method of ProcessStoreImpl.
>
>
> I would like to see the point in the code where a order to execute a
> process is issued.
>
> When the process beginns with a receive activity and the container receives
> a message which targets a process the process will be executed.
>
> What happens in the case when the process starts with an invoke activity?
>
> Hopefully you understand my problem and could help me. It is very important
> for me.
>
> Thank in advance.
>
> Pascal.
>
> --
> GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
> Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
>
How works ODE?
Posted by Pascal Aho <P....@gmx.net>.
Hi all,
I would like to extend the future of ODE. I use ODE 1.3.2. First of all I try to understand how ODE now works. I have already read the documentation(ODE - Architectural Overview, the JACOB Framework etc)but I still have some points which are not clear for me.
When I look through the code I don't see any relationship between the deploy() method implemented in the class ProcessStoreImpl and the others methods(OnScheduleJob, handleWorkEvent, createRuntimeContext which execute instance.execute(), vpu.inject(process), etc) which lead to the execution of a process.
It is clear a process will be get executed only it has been compiled succesfully and the .cbp is created. The compilation is done within the deploy() method of ProcessStoreImpl.
I would like to see the point in the code where a order to execute a process is issued.
When the process beginns with a receive activity and the container receives a message which targets a process the process will be executed.
What happens in the case when the process starts with an invoke activity?
Hopefully you understand my problem and could help me. It is very important for me.
Thank in advance.
Pascal.
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01