[weld-dev] ref guide (re)draft ready

[Dan Allen]

>
> I actually wonder if we should make two guides:
>
> * Using CDI - the user guide
> * Extending CDI - the guide for framework developers and integrators.


I was actually thinking the same thing. It's less likely (though not out of
the ordinary) for the same person to be reading how to develop with Weld and
how to extend Weld to create a framework. The extending CDI can be much more
technical and cater to those framework developers. Surely we will learn a
ton when doing Seam 3 and could contribute our experiences in this guide.

With that in mind, we should at least consider that most applications will
tap into the SPI at least once or twice to satisfy some edge case or in
house integration. Thus, we should cover the most common and useful
interfaces and explain how they are used in the user guide.

-Dan

-- 
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/weld-dev/attachments/20091102/7b1138f5/attachment.html