I like the timing - about a month, 6 weeks at the most is a good
window between releases in early stages like we are.
I agree federation is the big delta between now and then - we should
have by then
* federated classloading (with multi-classloader support)
* federated scope
* the changes done for separating controller and physical runtime
* contribution store and artifact redistribution
It would be good to increase the spec coverage e.g.
* support for casting between proxies and service references
* support the new Conversation API
* clean up around complex properties - specifically being able to use
an external file to configure the server runtime
* some more integration tests
Also, user support such as:
* the composite plugin (i.e. pick an archive type)
* JUnit4/TestNG support in the itest plugin
* contribution tool (command line and plugin?)
* a start on some form of console
* some more samples
* doco for all the above
The Guice idea is intriguing - support for their PM and annotations
would be good. I also would like to take a look at using their EDSL
for assembly - perhaps for hooking up the runtime as an alternative
to SCDL.
--
Jeremy
On Mar 15, 2007, at 2:38 AM, Meeraj Kunnumpurath wrote:
+1
We should get the federation story implemented for the next kernel
release. I think the development for federation is looking in good
shape, and we should most probably have an end to end story, for the
TSSS demo with couple of transports. In terms of extensions we also
need
to look at porting some of the existing extensions to the new model in
addition to adding new ones like Hessian. Also, we need to to look at
the management side of things. I started on it a while ago, it
currently
supports only read-only props on components. We need to start thinking
about how to take it further forward. Some of the other things we can
look at (maybe not in this release) is support for non-XML wiring,
maybe
start looking at things like Guice?
Ta
Meeraj
-----Original Message-----
From: Jim Marino [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 13, 2007 8:54 PM
To: [email protected]
Subject: Kernel Alpha2 Release
I would like to start thinking about the next release of kernel.
Based on the work being done around federation, it seems that
multi- VM
support is the key feature we should look to enable. This will
allow us
to demonstrate the high-value areas of SCA, particularly around
distributed assembly. In addition, we should have a simplified
extension
model and classloader isolation in place.
In terms of timing, I thought sometime around the first or second week
in April would be ideal, as a few of us will be demonstrating these
features at the ServerSide Symposium next week.
I think we may also be able to get some bindings and extensions out
around the same time or shortly after. I was thinking: Spring, Groovy,
JPA, and Hessian to start.
Thoughts?
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This message has been checked for all email viruses by MessageLabs.
*****************************************************
You can find us at www.voca.com
*****************************************************
This communication is confidential and intended for
the exclusive use of the addressee only. You should
not disclose its contents to any other person.
If you are not the intended recipient please notify
the sender named above immediately.
Registered in England, No 1023742,
Registered Office: Voca Limited
Drake House, Three Rivers Court,
Homestead Road, Rickmansworth,
Hertfordshire, WD3 1FX. United Kingdom
VAT No. 226 6112 87
This message has been checked for all email viruses by MessageLabs.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
