WidgetService 'legacy' method no longer supported, adjust according widgets

[adube]

With r901, the org_geoprisma_service_WidgetService service is no longer supported using the 'legacy' method (see in documentation ​here, under "Service of ‘widget’ type (legacy method)". The according code was put under comments.

This was a mistake at first but I think we should drop the support of this legacy method since it requires building unnecessary objects (datastores, resources, etc.) and by 'drop' I don't mean deprecate, but a complete removal.

affected widgets

The change may have caused some widgets to stop working, such as the split and merge widgets if I recall correctly. They should be updated to support the new way.

[adube]

r905, this ticket is mentioned in the source code directly for developers to at least have some notice to where to look at if they get an error while using the legacy method.

[yvesm]

The split & merge require all logic in the database currently which isn't a good thing so indeed we need to change those widgets. Worse comes to worse, someone in dire need of the split & merge can always use a revision of GP < 901. For now, we could mark the widgets as requiring revision < 901.

[adube]

I agree.

I made the following change : r907. It features a "requires revision 900 or older" notice for both widget in their doc.

Let's keep this ticket open until they fully support the new way.

[adube]

'merge', 'split' and all 'legacy' widgets could become deprecated in 1.0.

[adube]

'merge', 'split' were removed and the 'legacy' widgets (map and mapfishlayertree) are deprecated in 1.0.