Could somebody explain how Espo routes calls to custom Entry Point classes when they are in a different namespace than Espo\Custom ?
So far I have noticed that as long as an Entry Point class name is unique, Espo checks Espo\Modules and Espo\Custom namespaces for the class without a problem, so I can call for the Entry Point from a front end script like this:
var url = '?entryPoint=sqlDataDispatcher';
regardless of where is the SqlDataDispatcher entry point class located, because its name is unique, but how can I address an Entry Point class that has a name that is not unique and is located at a specific namespace ?
for example: assume that I have two different SqlDataDispatcher entry point classes, one located at Espo\Modules\Module1 and the other one located at Espo\Modules\Module2, how could I define var url in my script for entry point "SqlDataDispatcher" that is located at the Espo\Modules\Module2 namespace ?
Thanks in advance for your help
So far I have noticed that as long as an Entry Point class name is unique, Espo checks Espo\Modules and Espo\Custom namespaces for the class without a problem, so I can call for the Entry Point from a front end script like this:
var url = '?entryPoint=sqlDataDispatcher';
regardless of where is the SqlDataDispatcher entry point class located, because its name is unique, but how can I address an Entry Point class that has a name that is not unique and is located at a specific namespace ?
for example: assume that I have two different SqlDataDispatcher entry point classes, one located at Espo\Modules\Module1 and the other one located at Espo\Modules\Module2, how could I define var url in my script for entry point "SqlDataDispatcher" that is located at the Espo\Modules\Module2 namespace ?
Thanks in advance for your help
Comment