Generate automatically batch infrastructure

• Type: Story
• Status: Closed
• Priority: Major
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: 7.0.X, 7.1.X, 7.2.10 DXP FP17, 7.2.10.6 DXP SP6, 7.2.X
• Component/s: Headless Delivery API
• Labels:
  • 7110-sp-pending
  • 7210-sp-pending
  • fc_20_02
  • liferay-dxp-72-sp6
  • liferay-fixpack-dxp-17-7210
  • poshi_test_not_needed
• Branch Version/s:
  7.2.x, 7.1.x, 7.0.x
• Backported to Branch:
  Committed
• Epic/Theme:
  • API_Content_Management
• Epic Link: headless-batch-operations
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/85073

(v1.0/import/DTO_CLASSNAME/VERSION/)

We need a way of informing batch framework of the:

• DTO className
• version
• operation (delete, get...)

Options:

1 - Annotations manually
1.1 - trying to avoid passing the full dto classname and version (version latest, trying to use simple dto class name). Behaviour won't be consistent between versions.
2 - Explicit endpoint /batch ^ -> Drew -> /organizations (long[] id) <> /organizations (page...)

3 - Global configuration
4 - Interface that you implement in resourceImpl (generator with 2 generation passes)

5 - Add a flag in the model and generate or not the path

Things that we want:

• A method to be optionally overriden for implementing batch