-
Improvement
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
-
Empty show more show less
-
Saigon 126, Saigon 127, Saigon 128, Saigon 129, Saigon 130, Saigon 131, Saigon 132, Saigon 133, Saigon 134, Saigon 135, Saigon 136
-
5
After discussed, we agreed new approach as bellow:
- Create simple expander by using Decorator/Wrapper to resolve item to canonical format: [provider]:[workspace]:[uuid] (see DEV-649 for more details). Then resolve that id in NodeWriter.
- Register the ComponentProvider to RestDispatchServlet, then inject it by @Context in NodeWriter, then get resolver by provider in resolving canonical format.
Once this is done, if reference expansion becomes automatic (for the new canonical format for example), then we will have to think about how to enable/disable reference expansion per endpoint. But we don't have to think about this for now, since all expansions have to be configured.
Acceptance criteria
- depends upon
-
MGNLREST-119 Research solution for resolving result of a list of reference nodes
- Closed
- is depended upon by
-
MGNLREST-107 Resolve references as links
- Closed
- is related to
-
MGNLREST-174 Duplicated UUIDs should be resolved correctly
- Closed