On Mon, Nov 2, 2009 at 7:35 PM, Pete Muir
<pmuir@redhat.com> wrote:
On 3 Nov 2009, at 00:31, Dan Allen wrote:
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.
Exactly. Or "Extending CDI: A primer". The key point will be the link to the other guide, and perhaps to let the reader experience a realization as to whether extending is something that interests them, or they just feel nothing. It's like a food sample ;)
-Dan