Thanks David,
the name is actually misleading.
About the description: yes, using the one of the service would be ideal,
but there are two aspects we should consider:
1) I don't know if there is an easy way to retrieve it in forms (e.g.
using the <display-*/> element)
2) localization: storing the description in an entity field makes it
easier to translate it in different languages
Maybe we could use the following convention: if the
CustomMethod.description is empty, then retrieve it from the service.
Jacopo
David E Jones wrote:
Thanks for the heads up Jacopo. I've changed that back and added/changed
comments to clarify how this works and note the misleading field name.
As for the general pattern, it may come in useful at some point if we
want to configure additional things related to these service calls or
other methods. For the human description, why not just use the one on
the service def itself?
-David
