Beyond PSD2 for a Better Open Banking Expereince

PSD2 is acting as a catalyst in the digital transformation happening in the Banking industry. While meeting the compliance requirements of PSD2, financial institutes are excited to make use of the new business models and opportunities opened by this laid foundation. More the customers and partners we can reach, more the business activities and more the revenue. Making the banking functions more accessible and reactive will be a key enabler to provide a seamless experience to these parties, including internal banking staff whom directly affects the business efficiency.
IAM plays a critical role in improving business accessibility without compromising the system boundaries. PSD2 mandates strong customer authentication(SCA), setting the bar high for user authenticity, while keeping few exemptions, not to bother payment services user(PSU) with SCA for every little transactions. While adhering to this policy will make an institute PSD2 complaint, if they can react fast to the fraud rates…

Documentation-patch submission for Apache issues

Submitting a patch for a documentation issue is same as submitting a patch for a code issue. Only thing to be noticed is where the source code for sites resides. Here I am sharing the steps in a very basic level as helpful for a beginner, from identifying an issue to the submission of patch.

Note:The sample commands I am using here are for linux and for other environments the relevant commands should be applied for same functionality.
  • After identifying the issue from Apache issue navigator, check out the relevant files directory from apache SVN. 
  • Navigate to the relevant .xml files and do the improvements or corrections needed and make sure the xml validation is done and the document is presented as it is intended to be. 
  • Lets see how the changes are applying. In the top level directory that includes all the changes and improvements enter the following command. 

eg : svn co http://svn.apache.org/repos/asf/axis/axis2/java/core/trunk/src/site/xdoc/

eg: svn diff -x-p

You will see something as follows,



- lines preceded with - are to be deleted

- lines preceded with + are to be added

Make sure those are the intended changes and then create the patch with the following command:
Now submit the patch at the jira issue page as follows and add any meaningful comments.

svn diff ><the preferred name for patch file>

eg: svn diff >AXIS2-4655.patch




Keep in touch for updates on the patch submitted. Keep contributing.

Comments

  1. Thank you for providing this resource to the web.
    Review my web site - Belleville Washers

    ReplyDelete
  2. Thanks! This article was very helpful and saved me many hours of digging and experimentation.

    ReplyDelete

Post a Comment

Popular posts from this blog

Signing SOAP Messages - Generation of Enveloped XML Signatures

How to send an HTML email in Java (Using Google SMTP Server)

How to convert WSDL to Java