Skip to main content
Understanding the service layers clarifies where to add validation, change behavior, or trace a bug. Darpan backend calls use Moqui JSON-RPC through /rpc/json. The method name is a Moqui service name, for example:

Layering

Facade services

Facade services are the app integration point. The active facade files include:
  • service/facade/AuthFacadeServices.xml
  • service/facade/SettingsFacadeServices.xml
  • service/facade/JsonSchemaFacadeServices.xml
  • service/facade/ReconciliationFacadeServices.xml
  • service/facade/SearchFacadeServices.xml
The full verified facade method inventory is in the service catalog.

Core reconciliation services

Core reconciliation services live under service/reconciliation/**.

XML-first rule

XML services own validation, authorization, entity mutation, service calls, and response shaping. Groovy and Java helpers handle processing-heavy code such as Spark preparation, rule execution, JSON normalization, and schema inference.

API shape

Darpan APIs are exposed through verified facade service names and the Moqui JSON-RPC envelope. Service references document required parameters, auth expectations, side effects, and response fields for those facade contracts.