Hi, Tom.

Thanks for bringing it to our attention.

Here are a few more items:

1) Core and SPI:

Add the support for multiple bindings of the composite service or reference.
Add interfaces for discovery service

2) Host-API: Add interfaces for deployment and management

BTW, what's the best way to maintain this kind of changelog in automatic way? Tracking the commits? Using wiki? Going through JIRAs?

Thanks,
Raymond

----- Original Message ----- From: "Tom Seelbach" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, January 16, 2007 12:37 PM
Subject: status of sca kernel


I am trying to determine the status of the sca kernel as of the recent
revision 495979
by diffing the source code from M2 with r495979 which changed the spec
CompositeContext.

My goals are:
   1) to write a high level description of the changes since M2
   2) to get an idea what changes are planned in the next few weeks/month
   3) determine if this is a good revision to work with/extend in
terms of customizing bindings, working with samples, etc.
   4) ask the community if this should be a published kernel snapshot
in the spirit of "release early and often".
(maybe it is, i'm pretty sure Jean-Sebastien did publish the snapshot)
     if not, what kernel revision is/will be a good candidate?

At a high level, these are the changes since M2:

Spec:
 bring spec CompositeContext in compliance with the SCA Java C&I 0.95 spec
 renamed methods in kernel CompositeContext
   getCompositeName()
   getCompositeURI();

 added ConversationEndedException
 removed SessionEndedExeception

 added annotations:
   Converstation
   ConversationID
   EagerInit
   EndConversation

 removed annotation:
   Init - removed "eager()"

kernel/api:
TuscanyException.java - new overridden constructors

kernel/spi:

  added more detailed exceptions
  refactoring
  changed "module" to "composite" throughout

  builder changes
  autowire/wiring changes

kernel/core:
 bring core CompositeContext in compliance with the SCA Java C&I 0.95 spec
   renamed methods in kernel CompositeContext
     getCompositeName()
     getCompositeURI();
   lots of refactoring
   ...


Regards,
Tom



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to