Dims--
Some people are probably aware of Tuscany -- I'm listed as an
initial committer, so that would follow in my case. :)
In SCA's Java binding, Controls and SCA do overlap some
syntactically. Here, annotations are used for things like:
- declaratively injecting contextual information -- @Context
- declaratively injecting dependent objects (Java 5 metadata driven
DI) -- @Reference
- basic lifecycle support -- @Init + @Destroy
- general DI -- @Property
But, these annotations do very different things than the annotations
in Beehive's Controls framework. Controls are a richer, all-around
component model that supports meta-metadata, annotation validation,
eventing, contextually available services, inheritance, and a very
cool extensibility model that is configured simply via metadata on a
Java interface. This model is general enough to be used in building
things that scale from abstracting JDBC / EJB / JMS all the way into
building services. For example, take a look at this thread from TSS
two weeks ago:
http://www.theserverside.com/news/thread.tss?thread_id=37685#192002
which discussed some of the meta-metadata, validation, and custom
annotation checking features available in Controls. This is different
in purpose than the conceptual vision for services put forth in the
SCA client / impl spec.
The SCA assembly spec then allows SCA service implementations to be
bound into an SCA module and used in some service infrastructure.
Here, Controls could naturally plug into the assembly architecture.
What I'd potentially like to see (without having spent tons of time
thinking about this so far...), is the ability to "mix" the annotation
sets such that Beehive Controls could be exposed as SCA services by
using their Java 5 metadata. Then, we could deliver the richness of
our component model in a way that could integrate into the SCA
assembly service model and assembly architecture.
Ultimately, I agree with your point -- at first glance, they are
similar things in concept. But, in digging deeper, I think we'll find
that they're complimentary.
Thoughts? Will you be at ApacheCon and available to talk about some of this?
Eddie
On 12/3/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> Hmmm...Did you guys see the Tuscany proposal?
> (http://marc.theaimsgroup.com/?t=113337453000005&r=1&w=2) Seems like a
> bit of overlap with Beehive Controls (SCA stuff). That would leave
> WSM, which would be a great addition to WS stack if we can port it to
> Axis2.
>
> -- dims
>
> On 12/3/05, Rich Feit <[EMAIL PROTECTED]> wrote:
> > Hi all,
> >
> > This mail involves a potentially big question about the future of
> > Beehive; I'll try to keep it short, but if you're impatient, skip to the
> > middle. :)
> >
> > Ted Husted and Don Brown of Struts have proposed merging WebWork into
> > Struts:
> >
> > http://www.mail-archive.com/dev%40struts.apache.org/msg13815.html
> >
> > This is a big deal; see
> > http://www.theserverside.com/news/thread.tss?thread_id=37794#192216 for
> > starters.
> >
> > Following from the prototyping work that we did with "Struts Ti",
> > they've included Beehive Page Flow as part of a Phase 2:
> >
> > > * Ti phase 1 = WebWork 2.2 + Struts 1.x compatibility library and
> > migration tools
> > > * Ti phase 2 = phase 1 + Commons Chain integration + Beehive's Page
> > Flow + simplified annotations + quick development mode
> >
> > ** What this means is that most of the NetUI piece of Beehive would move
> > into the Struts project -- refactored or rewritten to run on the core
> > action framework that's being developed in Phase 1. ** The question
> > for our community is, do we want to sign onto this?
> >
> > For my part, I am all for it. I think it would be good for Beehive
> > (joining forces with our "big sibling") and it would be good for Struts
> > (bringing in our toolability, annotation-based programming model,
> > etc.). We're both Apache projects, and it seems like a natural move to
> > make.
> >
> > What are your thoughts? Eddie and I will both be at ApacheCon along
> > with several of the Struts committers, so any
> > support/objections/questions/concerns you have before that will help us
> > understand where the Beehive community stands on this.
> >
> > Thanks,
> > Rich
> >
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
