Friday, July 23, 2010

OGSA-DAI ~Presenting in CXF~ (4)

Build Scripts - Release Builds
Build files and CXF web.xml for the release build of OGSA-DAI/CXF/JAX-WS are committed in the revision 1273. 1281 adds Spring aop (Aspect Oriented Programming) as a dependency for cxf/server module.

OGSA-DAI/CXF deployed in Tomcat

More modifications in the release script, towards deploying in Tomcat (currently testing with Apache Tomcat 6.0.24) are done in the revisions 1282 and 1283. Listing all the 6 OGSA-DAI (SOAP) Services in http://localhost:8080/dai/services. The functionality provided by the package will be handled more for CXF layers here.
OGSA-DAI SOAP Services along with the operations are tabulated here (in DOC format  and PDF format). These tables are drawn from the service listing of OGSA-DAI deployed in Tomcat (refer to the images).
1274 - ReSTful Presentation Layer code development based on JAX-RS/CXF. Committed the folder.

1277 is a minor fix that adds log4j as a dependency in the cxf/server module build, which fixed the odd java fork failure in the test framework, due to the Logger class not found exception [1],[2].
Fixes to Base64 Tests will follow.
Details of CXF based layer to be added here.

[1] Test Results (Currently) [2] Test Framework

Sunday, July 11, 2010

Mid evaluations with the cute hexapus!

Mid evaluation is on the way today evening, while we have done the initial design of ReSTful presentation layer, and towards the completion of the SOAP based layer. Web Application Description Language (WADL), which is said to be the ReST equivalent to WSDL of SOAP, paired with JAX-RS supported by CXF will serve us in this. WADL2Java tool for the stub generation is worth mentioning here. Service Oriented Architecture (SOA) and Resource Oriented Architecture (ROA) all sound good. Again feeling the need for a wsdl2wadl tool [1] (and a wadl2wsdl ;)).

WADL is becoming the standard (if not already) for REST as WSDL for SOAP, though REST with WSDL2.0 too is possible. "CXF JAX-RS now supports the auto-generation of WADL for JAX-RS endpoints. [2]" I was initially planning to write WADL on my own, by referring to the respective WSDL (and then use wadl2java for the stub generation). Finally felt auto-generation from JAX-RS is a smarter option, where we start from Java to WADL and after fine tuning the WADL that is auto-generated from the JAX-RS endpoints, going back to the java code using wadl2java (as thought initially).

[1] "Modelling Web-Oriented Architectures", by G.Thies and G.Vossen
[4] SOAPUI - Working with REST Services. 
[5] #rest on
[6] wadl2java  
[7] MYEclipse - Developing REST Web Services Tutorial
[8] Chapter 13. How requests (workflows) are executed
[9] OGSA-DAI 4.0 Axis Documentation
[10] The Client Toolkit Tutorial
[11] JAX-RS (JSR-311)

 * Hexapus refers to the logo of ogsa-dai.

Saturday, July 3, 2010

OGSA-DAI ~Presenting in CXF~ (3)

Resource Oriented Architecture
While focusing on the SOAP based layer implementation, we also had the first formal discussion on the design of ReSTful presentation layer, this week. I was able to join the discussion via skype, and took down notes, which were also summarized to the committer list by my mentor Ally Hume.

More development
When considering the implementation and the commits, commit 1232 is CXFServer, which is the access point of OGSA-DAI service/resource proxies for OGSA-DAI CXF services. client/toolkit/presentation/cxf/ - A place for the client side resources, is committed in 1244, which is still being modified. CXF implementation of DataRequestExecutionResource, CXFDataSinkResource, and CXFDataSourceResource are committed in the revisions 1245, 1247, and 1248 respectively.

1250 is literally an insignificant. But I couldn't resist committing this, as I am 'worried' to see the cxf/client module being broken at the test server. So let it build happily till the complete fix is committed, which makes all sub-modules of the module presentation being built without any issue. During this period, I also refactored the code to have column width of 80, to fit the ogsa-dai coding standard. My usual column width was 120. 1261 becomes the first commit towards the cxf binary release, by including the ogsa-dai/cxf release script. Building the distribution is fine. Deploying to Tomcat from the that is built, still need to be fixed, obviously. Commit 1263 uncomments the cxf/server module from the trunk's build, as it is not failing anymore.

CS4010 Professional Practice and Fun

We enjoy our lectures a lot, and this is just a sample.. :D

Friday, July 2, 2010

Facebook Permanent Deletion - An option that is hidden..

"Do you know that you can permanently delete your account, as well as deactivate the account?"
"Confusing, isn't it? 
Mostly the deactivating option has been misinterpreted as the delete option, while it is just a mere hide. You can log-in to your account at any time, and start 'facebooking' as usual, though restoring the groups and notes may take a few hours. But there *is* also a permanent deletion option, which is hardly known/used.

You can give it a *try*. 

The funny part is, permanent deletion dialogs are not user-friendly and mechanical, while the deactivating option has a nice interface with super-friendly messages, "oh.. why are you leaving.. your pal Llovizna will miss you.. "

Once you requested the permanent deletion of the account, you will be given a fortnight. You can reactivate your account within that period, if you feel so. After the fortnight your account will be gone forever! :)

Delete my account
If you do not think you will use Facebook again and would like your account deleted, we can take care of this for you. Keep in mind that you will not be able to reactivate your account or retrieve any of the content or information you have added. If you would like your account deleted, then click "Submit".

(No one is going to miss you in this case! Poor you!!)

Permanently delete account
Your account has been deactivated from the site and will be permanently deleted within 14 days. If you log into your account within the next 14 days, you will have the option to cancel your request.

Pradeeban feels it could have been done better.

Thursday, July 1, 2010


OGSA-DAI, by nature can be exposed as resources, and it fits the ReSTful design pretty well, and the initiatives to an alternative ReSTful layer was taken a few months ago. Since the inclusion of the ReSTful layer as a goal of a GSoC project of OGSA-DAI, the design discussions started accelerating.

The first formal discussion on the design was held on 1st of July at Edinburgh Parallel Computing Centre (EPCC), by the senior architects Ally and Bartek. The discussion was targeted towards a high level description of the ReSTful layer design.