Additionally Regarding your question to choose between Java and Groovy: That
depends on your personal preferences. You can choose whatever you want.
> Tomek hat am 16.04.2021 14:48 geschrieben:
>
>
> Hi,
>
> I'am browsing the code of OFBiz and I see that the services are written
> in
Hi,
you can define the engine of your service in the engine attribute or your
service definition:
https://cwiki.apache.org/confluence/display/OFBIZ/Service+Engine+Guide#ServiceEngineGuide-ServiceDefinitionserviceDefinition
You can choose between engine definitions configured in your
Hello everyone,
I have a question regarding the following promotion:
User Entered: Y
Show To Customer: Y
Require Code: Y
Use Limit Per Order: (null)
Use Limit Per Customer: (null)
Use Limit Per Promotion: (null)
with only 1 rule without conditions but the following action:
Product Promo Action
earch the codebase for the service name
> to see where it is referenced.
>
> In most cases, an eeca or seca is the cause for unexpected high
> frequency service calls.
>
> Best regards,
>
> Michael Brohl
>
> ecomify GmbH - www.ecomify.de
>
>
> Am 05.02.
lls.
>
> if an error raise, we haven't information on any java stack trace, so
> you idea to implement a possibility to display a service call trace is a
> nice idea.
>
> Don't hesitate to open an issue if you have an idea to implement this.
>
> Cheers
>
> Nicolas
etting called from.
>
> This is of course an ugly solution but works especially if you're in the
> development phase. That said, it would be a nice feature to have the
> DispatchContext have information about current execution context.
>
> Best Regards,
> Girish
>
>
&
ben:
>
>
> Hi Danny Trunk,
>
> Could you please share the use case why you need a service call stack?
>
> If you share the use case it may be possible you will get a better answer.
>
> Kind Regards,
> Deepak Dixit
> DIRECTOR OF PRODUCT ENGINEERING
> mobile: +91 982
Hello,
let's imagine Service A is calling Service B directly through
dispatcher.runSync and Service C is running as an SECA action of Service B. The
call stack would be: Service A -> Service B -> Service C (through SECA)
Or let's imagine Service D is running as an EECA action of entity
