I added it to the misc portion of the faq, because I didn't have a
better idea. I thought of adding it to the service engine page, but I
don't have permissions to edit that one.
Thanks everyone.
Cheers,
Anne.
On 14 September 2011 18:54, Jacques Le Roux
jacques.le.r...@les7arts.com wrote:
It's
Thanks Anne,
I don't see a better place either.
Jacques
From: Anne a...@cohsoft.com.au
I've added a page to the wiki at
https://cwiki.apache.org/confluence/display/OFBIZ/SECAs+and+Error+and+Failure+Management
summarising my findings on secas and error/failure handling.
I couldn't find an
oops this is the one I meant to suggest the link to service engine and FAQ
Jacques Le Roux sent the following on 9/13/2011 10:24 PM:
Thanks Anne,
I don't see a better place either.
Jacques
From: Anne a...@cohsoft.com.au
I've added a page to the wiki at
It's already in FAQ, and there is a link to Service Engine (SECA) in the page
Jacques
From: BJ Freeman bjf...@free-man.net
oops this is the one I meant to suggest the link to service engine and FAQ
Jacques Le Roux sent the following on 9/13/2011 10:24 PM:
Thanks Anne,
I don't see a better
I've added a page to the wiki at
https://cwiki.apache.org/confluence/display/OFBIZ/SECAs+and+Error+and+Failure+Management
summarising my findings on secas and error/failure handling.
I couldn't find an obvious place to link to it from, so as yet there
are no links to it from anywhere else in the
Thanks for you effort Anne.
Anne sent the following on 9/12/2011 7:43 PM:
I've added a page to the wiki at
https://cwiki.apache.org/confluence/display/OFBIZ/SECAs+and+Error+and+Failure+Management
summarising my findings on secas and error/failure handling.
I couldn't find an obvious place
run-on-error=true, run this eca service even when the main service flow
contains an error condition
ignore-error=true, do not allow an error return from this service to cause an
error condition in the main service flow
For example if you have a validate event eca with ignore-error=false that
Thanks Scott. But I now think it's more complicated than that.
After BJ's comment I spent nearly all of today going through the code
(ServiceDispatcher.java and friends) to try to answer my question. I
had hoped to avoid doing that, for what I thought was a simple
question.
It's looking like it
Also if the parameter is not specifically set false, it is evaluated true.
Anne sent the following on 9/6/2011 3:19 AM:
Thanks Scott. But I now think it's more complicated than that.
After BJ's comment I spent nearly all of today going through the code
(ServiceDispatcher.java and friends) to
The main service will never run if an error condition exists, I don't think
that is something I would consider unexpected. I'm not really sure why the
context validation is skipped but I don't think it matters much since the main
service won't be run anyway. But anyway, just consider the main
Does anyone know how run-on-error (eca tag) and ignore-error
(action tag) attributes work for a SECA that is set to run at invoke
time? The documentation's wording suggests to me it is talking about a
commit or return SECA.
Cheers,
Anne.
On 2 September 2011 15:35, Anne a...@cohsoft.com.au wrote:
best docs are in
framework\service\src\org\ofbiz\service\eca\ServiceEcaAction.java
and
framework\service\src\org\ofbiz\service\eca\ServiceEcaRule.java
Anne sent the following on 9/5/2011 4:56 PM:
Does anyone know how run-on-error (eca tag) and ignore-error
(action tag) attributes work for a
Hi
I've successfully added secas many times before, but only on actions
that run after the service, such as return or commit events. I now
need an invoke seca, and it isn't working the way I expected. So I
re-read the documentation, and all that did was confuse me. :-(
Searching the mailing list
13 matches
Mail list logo
