The goal of this document is to investigate about removal of deprecated code such as CamelTable of Contents maxLevel 3
Instruction
To be able to remove the legacy deprecated code the first rule is to isolate it, and after the successfull isolation is to go to the chopping board and do the hard code removal.
Camel
Camel utilizes two types of XML configurations, one such as REST endpoints and the other is the Routes.
- The Rest endpoints configuration accepts a specific url such as getUser and getToscaTemplate. As you can see that the getUser redirects the request to the AuthorizationController, and the getToscaTemplate redirects the request to an actual URL Rest endpoint by using a to uri tag direct:get-service-template
- Then the receiving routes XML configuration which each router has a unique id get-service-template which nested inside of the tag has a from uri direct:-get-service-template, header configurations as the paramater names and finally it redirects it to a specific REST endpoint url onap/policy/clamp/acm/v2/commission/toscaservicetemplate
...
Distributed Network
| Inc drawio | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
|