-
Bug
-
Resolution: Done
-
Neutral
-
5.6
-
None
-
-
Empty show more show less
-
Saigon 122, Saigon 123, Saigon 124, Saigon 125, Saigon 126
-
3
In a nutshell, I have two YAML files.
light-modules/rest-test/restEndpoints/rest1.yaml
class: info.magnolia.rest.delivery.jcr.v1.JcrDeliveryEndpointDefinition params: pages: workspace: website bypassWorkspaceAcls: true includeSystemProperties: false nodeTypes: 0: mgnl:page
and
light-modules/add-features-1/decorations/rest-test/restEndpoints/rest1.yaml
params: pages: nodeTypes: 0: mgnl:page 1: mgnl:component
Although decoration shows error of parsing YAML, new provider is still sent in event. This is causing further processing which messes up the current config.
Stack trace: stackTrace
Light module to reproduce the issue: light-modules.zip
This is a related issue. Firstly, the endpoint worked with list syntax ( - ).
light-modules+2.zip
After deleting the decoration module, the endpoint stopped working.
info.magnolia.objectfactory.MgnlInstantiationException: Unable to resolve parameters for constructor public info.magnolia.rest.delivery.jcr.v1.JcrDeliveryEndpoint(info.magnolia.rest.delivery.jcr.v1.JcrDeliveryEndpointDefinition,javax.inject.Provider). Unresolved parameter(s) are: 1st parameter which is of type info.magnolia.rest.delivery.jcr.v1.JcrDeliveryEndpointDefinition
Modifying the main YAML file made it work again.
- clones
-
MAGNOLIA-7193 Number keys are not supported in definition decoration
- Closed
- relates to
-
MGNLREST-138 Cannot decorate the delivery endpoint
- Closed
-
MGNLREST-156 SwaggerRestDispatcherServlet (re)register endpoint without provider validation.
- Closed