Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[alf-dev] ALF Event Manager code contribution is checked into CVS

Dear ALF community,

I am pleased to announce that the source code for the version of the ALF
Event Manager to be used for the ALF Proof-of-Concept (POC) is now
available in the ALF CVS repository.

Details and notes:
1. The process followed the Eclipse procedure for code contributions
that were not "developed in the Eclipse CVS". First, I submitted an
Eclipse code Contribution Questionnaire for the ALF Event Manager on
January 23rd.  After interacting with Janet Campbell, Manager of
Intellectual Property for the Eclipse Foundation, the code was reviewed
for IP and accepted by Eclipse for check-in to CVS.  I then checked the
code into CVS late today (Feb 1st).

2. The code is in the Eclipse repository with the following properties:
     Connection type: extssh
     Host: dev.eclipse.org
     Repository path: /home/technology
     Archive location: HEAD / org.eclipse.alf
     Component: eventmgr
     Sub component (i.e. package): org.eclipse.alf.eventManager

3. The corresponding IP log is in the same repository, under Component:
releaseReviews, Sub component: Feb2006

4. An excerpt from the code contribution questionnaire (with personal
info elided)is shown below:
Submitter:
Name:  Brian Carroll
Organisation: Serena
Address: 3445 NW 211th Terrace, Hillsboro OR 97124
Phone: (503) 617-2436 or (503) 318-2017
E-mail: bcarroll@xxxxxxxxxx

Committer
Name:  same

PMC
PMC Name: Bjorn Freeman-Benson

Contribution
Project: Technology
Subproject: Application Lifecycle Framework
Component: Event Manager

Name: ALF EventManager (POC Version)
Version: POC  (Proof of Concept) version
Size: 1800
Description: The ALF Event Manager is the component of the Eclipse
Application Lifecycle Framework project that receives events from
participating tools and applications, examines those events, and
dispatches
the appropriate ALF ServiceFlow (i.e. BPEL-defined process) to handle
the
event.
All communication uses Web Services, including the raising of the Events
and
the dispatching of the SeviceFlow

Pre-existing Packages: Yes. The intention is for users to download those
packages themselves.  [Those 3rd party packages are not part of the
contribution.]

I coordinated and personally conducted the reviews of the code for
quality,
origin of the code, and intellectual property rights prior to
authorizing
this contribution, and have approved these 15 modules of the ALF
EventManager (POC version) for contribution to Eclipse.

Contributor
Name: Manny Panis
Organization: Serena Software

Contribution Percentage: 100
Other Contributors: Manny Panis wrote 100% of the code, using as a guide
the
design specified in the ALF Architecture document published on the
Eclipse
ALF website.  
Brian Carroll (Serena, bcarroll@xxxxxxxxxx) and Tim Buss
(Serena, tbuss@xxxxxxxxxx wrote that Architecture document
and consulted with Manny while he was writing the code.

Cryptography:  Not applicable.

4. Special note about the code: The EventManager code is a Java Servlet.
The initial version is intended to be compiled using the Servlet 2.3
libraries as it uses the SingleThreadModel which has been deprecated in
Servlet 2.4 libraries.  Visual code inspections suggests the ALF Event
Manager is multithreaded, but conservatively we have used the
SingleThreadModel marker interface until sufficient load testing
indicates it is multithreaded, at which time we will remove that marker.
The code that is checked in is the same as is used in the ALF POC
integration work that Tim Buss is conducting with the ALF partner
community.

Please download and review the code.

Regards,
Brian


**********************************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.



Back to the top