Page Comparison

The goal of this document is to investigate about removal of deprecated code such as Camel

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

...

server
	ssl
		key-store: classpath:/clds/aaf/org.onap.clamp.p12
		key-store-password: enc:WWCxchk4WGBNSvuzLq3MLjMs5ObRybJtts5AI0XD1Vc
		key-password: enc:WWCxchk4WGBNSvuzLq3MLjMs5ObRybJtts5AI0XD1Vc
		key-store-type: PKCS12
		key-alias: clamptest
		
		client-auth: want
		trust-store: classpath:/clds/aaf/truststoreONAPall.jks
		trust-store-password: enc:iDnPBBLq_EMidXlMa1FEuBR8TZzYxrCg66vq_XfLHdJ

|

Login Screen

Inc drawio
diagramName Login UI includedDiagram 1 width

...

pageId 138871171

Distributed Network

Inc drawio
diagramName ClientServer includedDiagram 1 width 851 pageId 138871171