a)JSR 114 ( Rowsets Implementation )
The Rowsets specification was designed for disconnected data access. All the while JDBC had just connected data access. The disconnected data access was crucial for the technology and RowSets defined that along with synchronization mechanisms for synchronizing the data back to the backend.
Tools / Languages used:Java, ant ( for build scripts and developer testing)
OS: Linux, Solaris, Windows
-I was a part of the two member team that implementedthe entire RowSet specification. This specification was driven under the rules and stipulations laid out by the Java Community Process ( JCP ). The RowSets implementation was filed as JSR – 114 and driven by Jonathan Bruce, the then JDBC Specification Lead.
-As a part of my RowSet implementation I implemented a feature for paging data from memory and database, which got a lot of traction from developers both internally and externally.
-Along with the JDBC Specification Lead and the technical writer I co –authored a tutorial that developers who were new to RowSets could use to get a feeling for the technology and demonstrating scenarios where they could use RowSets.
b)JDBC 4.0 Implementation
JDBC 4.0 is being driven through the JCP as JSR 221. The main essence of JDBC 4.0 is Ease of Development. There are annotations that were released as a part ofJSR 175 and through the Java SE 5 release. This feature was leveraged by JDBC 4.0 to reduce the developer code that needed to be written to get things done.
Tools / Languages used:Java, ant ( for build scripts and developer tests )
OS: Solaris, Linux, Windows
-I was responsible for the initialprototyping work that needed to be carried to figure thebest way to attack this Ease of Development. I did this all by myself.
-I was also responsible for the design of the Reference Implementation for the JSR 221 specification.
-I gave valuable inputs to the specification on the Ease of Development area and also participated in Expert group meetings.
-I was given the reponsibility of handling the integration of JDBC 4.0 into Java SE 6, this access is given to very few engineers world wide in Sun ( about 25 -30 engineers)
c)Open ESB Integration
OpenESB isSun's implementaion of the Java Business Integration specificiation which is JSR 208. Integrating this into the Application Server is crucial for the product as anything that was deployed earlier can be exposed as a Web Service.
Team Size: 2
Tools / Languages used: Java
OS: Linux, Solaris
-I had been given the charter to figure out the bottle necks in the exisiting code and improve performance on which I am currently working.
-I had to later own a module in this and drive it all by myslefgoing ahead.