The problem with calling the implementation is the service
implementation could be moved. Also, some services have SECAs attached
to them to provide additional business logic - so you would need to
track those down and invoke them manually.
Bypassing the service engine has no benefit, and it introduces a lot of
problems. I recommend that you don't do it.
-Adrian
On 12/13/2011 7:14 PM, Wai wrote:
Hello All,
Is there an advantage of using dispatch.runSync() to invoke a service as
opposed to calling the underlying service implementation directly.
Is the advantage only with transaction processing?
Could it be that as a service, I would have the option of calling the
service asynchronously (ie with dispatch.runAsync()?
What other reason would I choose to call a service as opposed to calling the
underlying method that implements the service?
TIA
Wai
--
View this message in context:
http://ofbiz.135035.n4.nabble.com/Advantage-of-calling-services-as-opposed-to-calling-underlying-service-implementation-tp4191569p4191569.html
Sent from the OFBiz - User mailing list archive at Nabble.com.
