From Fedora Project Wiki

Line 35: Line 35:
Architecturally, everything in the Jboss ESB is a service. These services are ESB services, which can be exposed over variety of transports. ESB services are single method (doWork) services.
Architecturally, everything in the Jboss ESB is a service. These services are ESB services, which can be exposed over variety of transports. ESB services are single method (doWork) services.


Thus integrating such a popular open source application framework that has led to the creation of CDI (Contexts and Dependency Injection) with JBoss ESB and expose it's functionalities will be a great facility for SOA users.  
Thus integrating such a popular open source application framework that has led to the creation of CDI (Contexts and Dependency Injection) with JBoss ESB and expose it's functionalities will be a highly useful for SOA users.  


Technolgies to be used : EJB3, JPA, JMS, Spring, Java 6


Seam is a popular open source application framework that has led to the creation of CDI (Contexts and Dependency Injection)  
   


# What is the timeline for development of your project? The Fedora Summer Coding work period is 11 weeks long, May 24 - August 9; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 5-12); the last steps always take longer than you think, and we will consider canceling projects that are not mostly working by then.
# What is the timeline for development of your project? The Fedora Summer Coding work period is 11 weeks long, May 24 - August 9; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 5-12); the last steps always take longer than you think, and we will consider canceling projects that are not mostly working by then.

Revision as of 14:06, 18 May 2010

For information how to complete this form, refer to Summer Coding 2010 step-by-step for students.

Random list of application requirements

  1. Must include a schedule that was worked out with mentor
  2. Keep on eye on the Talk: page that is associated with the proposal page you create. Click on the discussion link on the top of your proposal page. The Talk: page is where mentors comment on your proposal.
  3. Make sure you have clicked on the watch link on the top of your proposal page(s) and Talk: page(s). Use the link to my preferences at the top of the page to set your Watchlist preferences to email you when changes are made.

About you

  1. What is your name? Harshajith Halgaswatta
  2. What is your email address? harsha.halgaswatta@gmail.com
  3. What is your wiki username? Harshajith
  4. What is your IRC nickname? harsha
  5. What is your primary language? (We have mentors who may speak your preferred languages and can match you with one of them if you request.) Sinhalese and English
  6. Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.) Sri Lanka, UTC+5.30, Generally available between 12UTC-20UTC
  7. Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?

Yes, have participated in various Open Source Projects like Sci-Flex [1][2], Sahana[3], OpenMRS[4], LimeSurvey.

[1]: http://code.google.com/p/sci-flex/

[2]: https://www.ohloh.net/accounts/harsha_halgaswatta

[3]: http://code.google.com/p/google-summer-of-code-2008-sahana/

[4]: http://openmrs.org/wiki/OpenMRS

About your project

  1. What is the name of your project? JBoss_ESB_integration_with_CDI
  2. Does your project come from an idea on the Summer Coding 2010 ideas page? If so, provide a link for reference, as well as a link to any discussions with mentors about your proposal.

Yes, this idea came under Summer Coding 2010 ideas page. The references are listed here.

[1]: http://seamframework.org/Community/StudentProjects

[2]: http://www.infoq.com/articles/jboss-esb-jbpm

[3]: http://www.germanescobar.net/2010/01/from-seam-to-cdi.html

[4]: www.tibco.com/.../journal-jboss-esb-journal-notes_tcm8-9736.pdf


  1. Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?

The intension of this project is to make an enterprise level solution that will yield Seam Framework-CDI work with JBoss ESB. The actual effort is to make and working prototype that will integrate CDI with Jboss ESB 4.Today The Jboss ESB is being most popular in SOA world with its highly valued features.JBoss ESB is an open source implementation of the Enterprise Service bus, based on The RosettaNet ESB and supporting creation, deployment and integration of services.

Architecturally, everything in the Jboss ESB is a service. These services are ESB services, which can be exposed over variety of transports. ESB services are single method (doWork) services.

Thus integrating such a popular open source application framework that has led to the creation of CDI (Contexts and Dependency Injection) with JBoss ESB and expose it's functionalities will be a highly useful for SOA users.

Technolgies to be used : EJB3, JPA, JMS, Spring, Java 6


  1. What is the timeline for development of your project? The Fedora Summer Coding work period is 11 weeks long, May 24 - August 9; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 5-12); the last steps always take longer than you think, and we will consider canceling projects that are not mostly working by then.


    • If your project development progresses differently so there is not 90% functionality by the mid-term, you must be in regular contact with your mentor about this. Your mentor must not be surprised about the state of your project when the mid-term comes.
    • If you are not progressed this far in mid-term, you must have a plan with your mentor to fix the situation.
  1. Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.

You and the community

  1. If your project is successfully completed, what will its impact be on the Fedora community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Fedora community, at least one of whom should be a Fedora Summer Coding mentor. Provide email contact information for non-Summer Coding mentors.

Letting SOA infrastructure around Seam Framework- CDI integrating this with JBOSS ESB will be an added advantage for the users.The intension of this project is to develop a prototype with ESB 4 that will lead some users looking at this, and can teach some lessons about how well CDI can operate with an ESB.


  1. What will you do if you get stuck on your project and your mentor isn't around? I believe and experienced engaging in various Open Source projects the community is there to help under different aspects. Even though the mentor may have some specialization on the particular area where i am working many technological solutions can be achieved through collaborating with the community.
  1. In addition to the required blogging minimum of twice per week, how do you propose to keep the community informed of your progress and any problems or questions you might have over the course of the project? Blogging twice per week would be really better in case informing the community where i am, other than that i can think of mailing to the dev lists at the end of each week letting the community know what sort of work i have completed so far.

Miscellaneous

  1. We want to make sure that you are prepared before the project starts.
    • Can you set up an appropriate development environment?
    • Have you met your proposed mentor and members of the associated community?

I have already finished setting up the environment and running some samples, Yet i am grabbing through the code and now feel really confident to start working on the project. Yes ,i have met the community and the mentor through mails and IRC meetings.

  1. What is your t-shirt size? Large
  2. Describe a great learning experience you had as a child.

While engaging in various Open Source Projects before i used to learn lot of different disciplines while getting Software Engineering skills exposed through various aspects.

  1. Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?

I can assure and confident to make this project success with the past experience i had with Open Source Projects which wrapped through many technologies which are in the path of key technologies of this project.