Hello community, The original schedule proposed to guide the development of my project, whose name is "Integrating Google Services in SCA Compositions", was composed of eight stages:
1) Get familiar with Tuscany binding model, GData protocol, and other related technologies (*Second week April – Fourth week April*) 2) Study the suitability to extend the Atom binding, already existed in the Tuscany binding set, to handle with the GData protocol. (*Fourth week April – First week May*) 3) Define the prior steps after discussions with the mentor and the community (*First week May – Second week May*) 4) First Phase of the development: Integrating GData protocol with Tuscany bindings (*Second week May – First week July*) *5) **Mid-term evaluation *(*14th July 2008*) 6) Second Phase of development: Creating the scenario example (*First week July – Second week August*) 7) Generate some documentation explaining how to use the new features added (*Second week August – First week September*) *8) **Final Evaluation *(*1st September 2008*) As we can observe, the first four steps was programmed to be executed before the mid-term evaluation, and, basically, the end of one indicate the beginning of another. However, in the practice, was common to a phase start before the expected period, or another one finish afterward. The first phase was realized through the study of some documentation exposed in the GData [1] and Tuscany [2] web sites. The document "Extending Tuscany" [3], as well as the analysis of the source code of some already existed binding implementations, like binding-atom, binding-atom-abdera, and binding-feed, was very useful at this phase. At the second phase, a discussion about the better way to implement the GData binding was made at the development list of Tuscany project. Two approaches were suggested: (1) provide an extension to the existing Atom and RSS bindings, and (2) define a completely new binding to handle with GData protocol. My implementation follows the second approach. By the way, there is another GSoC project about integrating Google services with Tuscany bindings, whose implementation follows the first approach. Hence, as soon as the two projects have been finished, could be a good idea confront the two approaches in a practical scenario. The usage of Google code, with the GData Java Client, was discussed in the mailing list as well. Because this is under the apache license 2.0 the usage was permitted The development list was used as the main instrument to consolidate the third phase. The discussions were used to guide the development of patches. The integration of GData protocol with Tuscany binding was done at the fourth phase. However it is not absolutely complete, and has some limitations: - A component that uses a binding.gdata can only access Google services. There is still not a way to a component provide a GData service; - The authentication is done by passing the username and password information through the Service Component Definition Language (SCDL) file – there is still not any data encryption; - The current state of binding.gdata only supports operations done with Google Calendar Service; - Operations to work with media types are not available yet. As can be observed, the binding.gdata still needs some enhancements in order to build a first release version that resolve all the limitations mentioned above. Assure all this improvements perhaps can prejudice the execution of the schedule proposed, since a complete scenario was intend to be implemented in the second development phase. However, I think that improvements are essentials, and I will adopt it as the next steps. Thanks for all that help me in the mailing list, and in special to my mentor Luciano. On Sat, Jul 12, 2008 at 11:33 AM, Thilina Buddhika <[EMAIL PROTECTED]> wrote: > Hi, > > My project is to implement *Tuscany SCA support in the Geronimo Admin > Console*. My mentor is Ant Elder and the following is an effort to brief > the work carried out during the first half of the GSoC. > > As my first step, I spent time to understand what Geronimo ACEs are, and > how to implement them. The main building block of a Geronimo ACE is a > portlet. So my next move was to learn the concepts behind portlets. Then I > did some reading and coding work to get familiarized with portlets. > > Then I worked on implementing a simple Geronimo ACE. So I followed an > article recommended by Ant. After puting some effort, I was able to > implement an ACE which was up and running. Then I explored the possibility > of calling JSPs and Servlets from an ACE. Calling a single JSP was pretty > straight forward. But calling a cascade of JSPs was not straight forward. So > I went throigh the JSR 168 specification and some other resources to figure > out the exact way. > > After doing some reading and test codes, I started working on the actual > ACE. Ant was kind enough to allocate me an area in the sandbox [1], to > commit my work. I started adding contents to a simple ACE. This was done in > an iterative manner to make sure the resulted ACE is perfectly up and > running in the latest Geronimo distribution. I referred to the existing > domain manager app, and added some similar contents to the ACE. I submitted > few patches which contained this workings to the JIRA [2], I have created > earlier.* > > Problems Encountered* > The current Geronimo-Tuscany integration is not working with the latest > Geronimo distribution. So it will be hard to carry on work due to this lack > of functionality. Having an underlying integration will help me to add some > functionality to the ACE. > > *Next Step* > Now it is decided to integrate the available domain manager app with the > ACE. So now I am looking at the possibilities and the required workarounds > for that with the help of my mentor. > > Finally I would like to thank the Tuscany community and especially to my > mentor, Ant for helping and guiding me. I am looking forward to complete > this project successfully and I am doing my best to achieve that goal. > > Thank you. > > best regards, > / thilina > > [1] - > https://svn.apache.org/repos/asf/tuscany/sandbox/thilina/geronimo_ACE > > [2] - https://issues.apache.org/jira/browse/TUSCANY-2391 > > > > > > > On Wed, Jul 9, 2008 at 9:25 AM, Luciano Resende <[EMAIL PROTECTED]> > wrote: > >> To help Mentors with mid-term evaluation, I'd like to suggest students >> to send a mid-term update describing high level >> progress/acomplishments towards the original project proposal. >> >> Mentors : Any thoughts on this ? other suggestions ? >> >> -- >> Luciano Resende >> Apache Tuscany Committer >> http://people.apache.org/~lresende <http://people.apache.org/%7Elresende> >> http://lresende.blogspot.com/ >> > > > > -- > E-Mail : [EMAIL PROTECTED] > I blog here : http://thilinamb.blogspot.com -- Douglas Siqueira Leite Computer Science Master's degree student of University of Campinas (Unicamp), Brazil
