When creating an Apache Wink REST service client in WebSphere Commerce v7.0 it is possible to use a custom entity provider with your REST service client allowing you to map a Java object to the service request and response.
For those who have worked with WebSphere Commerce v7.0, developer toolkit installations do not contain or provide a copy of the DBClean utility. If you want to leverage, test, or develop for the DBClean utility you need to enable the utility to run within your toolkit environment.
I was recently asked by a team member how to go about deleting records from a table based on an arbitrary composite key that was determined by the results of separate query that leveraged one or more tables, and I figured I’d post this solution for everyone.
The WebSphere Commerce Information Center has plenty of documentation on how to create a inbound REST service; however, when trying to create an outbound REST service client, you are left to own research and devices as to an implementation strategy. Knowing that WebSphere Commerce v7.0 includes the Apache Wink framework; we can leverage this to create a REST service client that is also based upon Apache Wink, and leverages a framework pattern rather than just pieces of code put together to execute HTTP calls and retrieve the responses.
Working on a recent project, I had a task that required me to number the rows of result set; however, I needed to reset the numbering based on the distinct value of a field, or group of fields. I accomplished my task by leveraging ROW_NUMBER() and PARTITION BY.
