Prototype for both raml and canonical validation checked in. Have to check the pros and cons of both the methods.

Canonical validation: canonical transformation currently happens in the next flow after ACK sent to 3ps. Had to alter the flow in case if we decided to go with this approach.
The errors are canonical related and might not make any sense that this field (canonical field) is required etc., to the client.

Raml schema validation: Will fail when the 1'st validation fails. Will not give all the errors in 1 shot. Having this schema gives a clear picture of what's expected in a language neutral way for the client.
Setup Complete Service Integration. Haven't tested though. Will test it tomorrow.
raml schema validation (basic). This will be enhanced once we have the latest json.
Setup Complete. Have to wait for other services to work before testing it. For now the call to it is short circuited.
Division Service fixed.
Merge branch 'master' into exception-strategy

resolved following Conflicts manually:
	src/main/app/3ps-dax-integration-layer.xml
	src/main/java/com/bhnetwork/integration/pppstodax/canonical/PartnerProfile.java
	src/main/resources/3ps-dax-int.properties
vendor and customerStore services fully functional - here and there a few mappings to clarify with team and at QA time. Demo ready for steps 6 & 7 in cascade.