Choreography component meeting agenda (7th Feb):

1. Discuss volunteers to join Oasis.org BPEL Technical Committee on behalf of TPTP choreography component

2. Discuss choreography plugin refactoring and recent UI changes / dependency refactoring
	- removal of choreography testsuite UI
	- addition of launch configuration
	- removal of trace.ui dependency
	- general approach to expansion of choreography dependant features

3. Discuss the design of enhancement 50076 in so far as it relates to the choreography component



Attending:
	Antony Miguel (Scapa)
	Joe Toomey (IBM)
	Koustubh Parwar (CA)
	George Din (Fokus)
	Diana Vega (Fokus)	

Absent:	
	Harm Sluiman (IBM)
	Serge Lucio (IBM)
	Jim Saliba (CA)
	Kent Siefkes (IBM)



Point 1 discussion:

Koustubh has spoken to Jim about joining the BPEL TC but has not yet received a response.



Point 2 discussion:

George Din had problems compiling the code in TPTP 4.0 CVS (HEAD), he will forward the compile errors to Antony by email.

Koustubh is able to compile the TPTP CVS code without errors and is able to run the provided examples.

Koustubh would like to see some more complex example BPEL processes such as testing specific examples.  There have been example files for e.g. HTTP testing in the past but these proved difficult to maintain given the changes to the BPEL specification and the development of the engine.  Antony will try to dig out some of the old example BPEL scripts to send to Koustubh.

In the light of the recent separation of the Java engine implementation from the Java engine interfaces, will the BPEL, XSD and WSDL translator classes be separated out into interfaces?  The translator classes generate Java which specifically uses the (TPTP) proprietary Java engine interfaces so it is unlikely that there will be any 3rd party translators to replace these.  A more likely scenario is that a vendor wishes to use an entire 3rd party BPEL engine to run their process.  We should provide for this in our APIs if necessary.



Point 3 discussion:

The URL of the design document for enhancement 50076 is:

	http://dev.eclipse.org/viewcvs/indextools.cgi/~checkout~/hyades-home/docs/unapproveddrafts/project%20info/plans/3+/features/hf_50076.html

There are two main issues remaining in the document but only one of these requires significant work to resolve it.  This is the second problem as described in the design document.

Harm on the previous models call had expected that the SUT model would contain binding information as this is required for the behaviour to be complete and runnable but this may or may not be feasible.

If we were to drop the possiblity of having binding information in our SUT model then we could reference binding files as external SUTs.

If we did wish to have binding information in our SUT model but the problem was too big to solve as part of this enhancement request for 4.0 we could go ahead with the current SUT plans and create an enhancement request for 4.x to deal with the problem of native binding information.  It would be nice to get these enhancement requests finished though.

Joe will talk to some contacts in IBM about UML to BPEL mapping to ascertain if the work required for mapping binding information into the SUT model will be significant.



Other discussion:

Koustubh is compiling a list of questions based on his observations of the choreography source code.  He will send this to Antony in time to be added to the meeting agenda next week.

This will probably be the last meeting on a monday at 2pm.  Kent Siefkes has been unable to attend the past choreography meetings because of a recurring conflict.  The meeting time has been and will be discussed on TPTP-platform-dev mailing list and hopefully everyone can agree on a time in plenty of time for next week's meeting.



Actions:

- George will forward his TPTP compile errors to Antony
- Joe will talk to some contacts in IBM about the SUT model binding issue
- Antony will send some example testing BPEL processes to Koustubh (or TPTP-dev mailing list)
- Koustubh will forward his questions to Antony in time for the next meeting agenda