Basically if CDI does these....

•Split specification into core and Java EE integration
•Bootstrap support
•Java SE context definition

1, 1.1, and 1.2 need to be rewritten.

The spec CDI 1.0 started out very JSF and EJB centric. CDI is, and is becoming more so, more general. 

Then all of the intro material from 
On Thu, Oct 13, 2011 at 11:23 AM, Peter Muir <> wrote:
I would be more than happy to accept rewrites here.

I think the best way is for you to offer a proposal and then we discuss it here...

On 13 Oct 2011, at 19:16, Rick Hightower <> wrote:

I think CDI has changed its purpose and scope enough that some of the intro material which made total sense when CDI was forming is now missing the mark.

CDI sort of evolved what was possible. The intro is still talking about the CDI you are going to build and the problem it is trying to solve.

CDI 1.1, problem has been solved well, and CDI redefined what was there.

Anyway... the intro material does not match the current scope and where CDI is today.

I think its important because some folks will never get past the intro... :)

Don't want CDI to be pigeon holed into some role it has but it is so much more than that.

It is more general purpose than that.

I want to table this. I can offer some rewrites.. But wanted to throw this out there. 

On Wed, Oct 5, 2011 at 5:21 PM, Pete Muir <> wrote:
cdi-dev mailing list

Rick Hightower
(415) 968-9037

Rick Hightower
(415) 968-9037