I pretty much agree with most of this, but I like the general pattern of
having the simplest of samples to show a particular technology or some
aspect of a technology and then something that brings it all together
which was for M1 BigBank. You may have a point that this is too much
for one sample, but generally these three technologies look in the minds
of people to be sort of separate and I still like the idea of a sample
that shows them all coming together.
Jim Marino wrote:
On Jun 21, 2006, at 4:48 AM, cr22rc wrote:
I'd like to help out on this and also the SPI analysis work you spoke
of. Per the samples I had some thoughts that instead of just jumping
straight to them is to add some more for "baby steps" in bring up.
For example I'd like to see as starters in a J2SE environment the
very simplest of composite with a Java component being loaded with
the minimal amount of any wiring. I was wondering if I could use the
initeager to somehow just have it instantiate a single instance that
would you guessed it display "hello world" to console.
I can take a look at doing this over the next few days in core2.
Not sure if that is possible still learning some of this code. If we
could get that to work first it would be great for all to use in a
debugger to see the system boot strap it self. From there move on to
converting the other samples. I think with bigbank we'll need to
maybe think (brain storm) some on how to best exhibit the new
recursive model.
BigBank I think needs a re-write. When we originally wrote it in the
spec group, the intention was to show the benefits and ease-of-use for
SCA. Since then, it's kind of evolved into a petstore-type application
that pulls in SDO and DAS. While I like those technologies, I'd like
to see BigBank put on a diet so that there is a version people just
interested in SCA can reference. Also, I'd like it to show more of the
value-add around SCA as opposed to just invoking a web service since
people outside of the SCA collaboration and Tuscany project have
questioned me as to why Tuscany is needed if there are things like:
http://seam.demo.jboss.com/home.seam. For me, the value in SCA is
around assembly, policies and conversations, so "showcase" features
could be:
- dynamic re-wiring
- switching transport protocols
- conversations and non-blocking/async behavior
- introduction of policy
I think we'll want to show both composites being used as components
and using composites through inclusion (aka fragments). I also think
we need to eventually start showing some more examples with some
interesting complex properties being set.
Jean-Sebastien Delfino wrote:
The last few weeks we've been talking about composites and recursive
composition so much... and today I looked for a sample showing the
new recursive composition model in our whole code base, including
the head and our various sandboxes... and couldn't find any. I think
it'll help all of us get our heads around this new model if we can
see a few samples. Could somebody point me to a recursive
composition sample if we have any and I missed it?
Is anybody curious and interested in trying to port a few of our
existing samples to the new recursive model? I guess the update of
the SCA spec describing the recursive composition is not public yet,
but the materials presented at JavaOne are public as far as I know,
and should be sufficient to develop samples leveraging the new
recursive composition model.
If anybody is interested in developing sample scenarios that
demonstrate the value of the recursive composition, please let me
know, we can work together on this. I'd like to start this activity
in parallel with the SPI analysis work that I'm currently doing.
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
