I've made it all the way through the ref guide with revisions that reflect that changes to the RI and spec names and the latest nomenclature and semantics from the spec. It's now ready for a technical review and proofreading (in trunk) https://svn.jboss.org/repos/weld/doc/trunk/reference http://anonsvn.jboss.org/repos/weld/doc/trunk/reference Since there was so much to change, I'm sure there are places where the semantics didn't get properly updated or an explanation is still out of date. Also, there were some areas of the ref guide that were thin, and I didn't have time to fill it all in. If you feel comfortable explaining a topic, please don't be shy to revise or suggest revisions. Here are some notes to consider: - Java SE sections need review for accuracy, relevance - Extending CDI (extend.xml) is extremely thin, to the point of being marginally useful compared to the spec - Weld extensions (extensions.xml) is underwhelming; do we have more to say than just about logging? - The chapter on producer fields (producerfields.xml) is missing, though producer fields are explained in intro.xml - The Weld SPI needs to be reviewed for accuracy, relevance (ri-spi.xml); this was a *long* chapter and I just don't know the Weld SPI yet I did add a lot of content while revising, but the ref guide can always be improved. -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 _______________________________________________ weld-dev mailing list weld-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-dev

Great idea Gavin ;) I should have picked up on your cue of attaching drafts to e-mails. -Dan p.s. Keep the following in mind, which I wrote in the "notes" section before the first chapter: Note that this reference guide was started while changes were still being made to the specification. We've done our best to update it for accuracy. If you discover a conflict between what is written in this guide and the specification, the specification is the authority--assume it is correct. If you believe you have found an error in the specification, please report it to the JSR-299 EG. On Sun, Nov 1, 2009 at 11:40 PM, Gavin King <gavin.king(a)gmail.com&gt; wrote: > Dan, that's really great! > > Could you mail us a PDF, so I can read it on the plane tomorrow? Thanks! > > On Sun, Nov 1, 2009 at 11:33 PM, Dan Allen <dan.j.allen(a)gmail.com&gt; wrote: > > I've made it all the way through the ref guide with revisions that > reflect > > that changes to the RI and spec names and the latest nomenclature and > > semantics from the spec. It's now ready for a technical review and > > proofreading (in trunk) > > > > https://svn.jboss.org/repos/weld/doc/trunk/reference > > http://anonsvn.jboss.org/repos/weld/doc/trunk/reference > > > > Since there was so much to change, I'm sure there are places where the > > semantics didn't get properly updated or an explanation is still out of > > date. Also, there were some areas of the ref guide that were thin, and I > > didn't have time to fill it all in. If you feel comfortable explaining a > > topic, please don't be shy to revise or suggest revisions. > > > > Here are some notes to consider: > > > > - Java SE sections need review for accuracy, relevance > > - Extending CDI (extend.xml) is extremely thin, to the point of being > > marginally useful compared to the spec > > - Weld extensions (extensions.xml) is underwhelming; do we have more to > say > > than just about logging? > > - The chapter on producer fields (producerfields.xml) is missing, though > > producer fields are explained in intro.xml > > - The Weld SPI needs to be reviewed for accuracy, relevance > (ri-spi.xml); > > this was a *long* chapter and I just don't know the Weld SPI yet > > > > I did add a lot of content while revising, but the ref guide can always > be > > improved. > > > > -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 > > > > _______________________________________________ > > weld-dev mailing list > > weld-dev(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/weld-dev > > > > > > -- > Gavin King > gavin.king(a)gmail.com > http://in.relation.to/Bloggers/Gavin > http://hibernate.org > http://seamframework.org > -- 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

Could only manage a quick look over the weekend and - the general SE section is accurate but could use some padding, particularly the introductory paragraphs - the numberguess Swing example uses out-of-date annotations and requires updating.

I'll try to do both of these by Thursday, that OK?

OK I'm done with this. Let me know what you think. On 02/11/2009, at 3:14 PM, Dan Allen wrote: > Could only manage a quick look over the weekend and > > - the general SE section is accurate but could use some padding, > particularly the introductory paragraphs > - the numberguess Swing example uses out-of-date annotations and > requires updating. > There may be some more updates now. But yes, it could use some padding. > > I'll try to do both of these by Thursday, that OK? > Yep, fine with me. Thanks for taking the time to look at it. -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

On Sun, Nov 1, 2009 at 21:33, Dan Allen <dan.j.allen(a)gmail.com&gt; wrote: > I've made it all the way through the ref guide with revisions that reflect > that changes to the RI and spec names and the latest nomenclature and > semantics from the spec. It's now ready for a technical review and > proofreading (in trunk) > > https://svn.jboss.org/repos/weld/doc/trunk/reference > http://anonsvn.jboss.org/repos/weld/doc/trunk/reference > > Since there was so much to change, I'm sure there are places where the > semantics didn't get properly updated or an explanation is still out of > date. Also, there were some areas of the ref guide that were thin, and I > didn't have time to fill it all in. If you feel comfortable explaining a > topic, please don't be shy to revise or suggest revisions. > > Here are some notes to consider: > > - Java SE sections need review for accuracy, relevance > - Extending CDI (extend.xml) is extremely thin, to the point of being > marginally useful compared to the spec > - Weld extensions (extensions.xml) is underwhelming; do we have more to say > than just about logging? > - The chapter on producer fields (producerfields.xml) is missing, though > producer fields are explained in intro.xml > - The Weld SPI needs to be reviewed for accuracy, relevance (ri-spi.xml); > this was a *long* chapter and I just don't know the Weld SPI yet > > I did add a lot of content while revising, but the ref guide can always be > improved. > > -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 > > _______________________________________________ > weld-dev mailing list > weld-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/weld-dev > I'd love to take a look through it (currently reading the spec), but I'd rather not read the XML files. Is there a simple way to generate the PDF or the HTML files, or do I need to check everything out and build from there? -- Jason Porter Real Programmers think better when playing Adventure or Rogue. PGP key id: 926CCFF5 PGP fingerprint: 64C2 C078 13A9 5B23 7738 F7E5 1046 C39B 926C CFF5 PGP key available at: keyserver.net, pgp.mit.edu

Jason, Simply check out that branch of the SVN tree and type: mvn Then, you can choose from either a PDF or HTML. The PDF ends up in the current directory, the HTML in target/docbook/publish/en-US/html -Dan p.s. I tried to attach the PDF to the mailinglist, but it got moderated because of its size p.p.s. Probably not a bad tip to point in either the ref guide or the wiki. On Mon, Nov 2, 2009 at 11:47 AM, Jason Porter <lightguard.jp(a)gmail.com&gt; wrote: On Sun, Nov 1, 2009 at 21:33, Dan Allen <dan.j.allen(a)gmail.com&gt; wrote: > I've made it all the way through the ref guide with revisions that reflect > that changes to the RI and spec names and the latest nomenclature and > semantics from the spec. It's now ready for a technical review and > proofreading (in trunk) > > https://svn.jboss.org/repos/weld/doc/trunk/reference > http://anonsvn.jboss.org/repos/weld/doc/trunk/reference > > Since there was so much to change, I'm sure there are places where the > semantics didn't get properly updated or an explanation is still out of > date. Also, there were some areas of the ref guide that were thin, and I > didn't have time to fill it all in. If you feel comfortable explaining a > topic, please don't be shy to revise or suggest revisions. > > Here are some notes to consider: > > - Java SE sections need review for accuracy, relevance > - Extending CDI (extend.xml) is extremely thin, to the point of being > marginally useful compared to the spec > - Weld extensions (extensions.xml) is underwhelming; do we have more to say > than just about logging? > - The chapter on producer fields (producerfields.xml) is missing, though > producer fields are explained in intro.xml > - The Weld SPI needs to be reviewed for accuracy, relevance (ri- spi.xml); > this was a *long* chapter and I just don't know the Weld SPI yet > > I did add a lot of content while revising, but the ref guide can always be > improved. > > -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 > > _______________________________________________ > weld-dev mailing list > weld-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/weld-dev > I'd love to take a look through it (currently reading the spec), but I'd rather not read the XML files. Is there a simple way to generate the PDF or the HTML files, or do I need to check everything out and build from there? -- Jason Porter Real Programmers think better when playing Adventure or Rogue. PGP key id: 926CCFF5 PGP fingerprint: 64C2 C078 13A9 5B23 7738 F7E5 1046 C39B 926C CFF5 PGP key available at: keyserver.net, pgp.mit.edu -- 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 _______________________________________________ weld-dev mailing list weld-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-dev

On Mon, Nov 2, 2009 at 10:52, Emmanuel Bernard <emmanuel(a)hibernate.org&gt; wrote: > You mean for example taking NumberGuess and enhance it? That's what Pete > proposed as well. > On 2 nov. 09, at 18:09, Dan Allen wrote: > > Jason, > > Simply check out that branch of the SVN tree and type: > > mvn > > Then, you can choose from either a PDF or HTML. The PDF ends up in the > current directory, the HTML in target/docbook/publish/en-US/html > > -Dan > > p.s. I tried to attach the PDF to the mailinglist, but it got moderated > because of its size > > p.p.s. Probably not a bad tip to point in either the ref guide or the wiki. > > On Mon, Nov 2, 2009 at 11:47 AM, Jason Porter <lightguard.jp(a)gmail.com&gt; > wrote: >> >> On Sun, Nov 1, 2009 at 21:33, Dan Allen <dan.j.allen(a)gmail.com&gt; wrote: >> > I've made it all the way through the ref guide with revisions that >> > reflect >> > that changes to the RI and spec names and the latest nomenclature and >> > semantics from the spec. It's now ready for a technical review and >> > proofreading (in trunk) >> > >> > https://svn.jboss.org/repos/weld/doc/trunk/reference >> > http://anonsvn.jboss.org/repos/weld/doc/trunk/reference >> > >> > Since there was so much to change, I'm sure there are places where the >> > semantics didn't get properly updated or an explanation is still out of >> > date. Also, there were some areas of the ref guide that were thin, and I >> > didn't have time to fill it all in. If you feel comfortable explaining a >> > topic, please don't be shy to revise or suggest revisions. >> > >> > Here are some notes to consider: >> > >> > - Java SE sections need review for accuracy, relevance >> > - Extending CDI (extend.xml) is extremely thin, to the point of being >> > marginally useful compared to the spec >> > - Weld extensions (extensions.xml) is underwhelming; do we have more to >> > say >> > than just about logging? >> > - The chapter on producer fields (producerfields.xml) is missing, though >> > producer fields are explained in intro.xml >> > - The Weld SPI needs to be reviewed for accuracy, relevance >> > (ri-spi.xml); >> > this was a *long* chapter and I just don't know the Weld SPI yet >> > >> > I did add a lot of content while revising, but the ref guide can always >> > be >> > improved. >> > >> > -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 >> > >> > _______________________________________________ >> > weld-dev mailing list >> > weld-dev(a)lists.jboss.org >> > https://lists.jboss.org/mailman/listinfo/weld-dev >> > >> >> I'd love to take a look through it (currently reading the spec), but >> I'd rather not read the XML files. Is there a simple way to generate >> the PDF or the HTML files, or do I need to check everything out and >> build from there? >> >> -- >> Jason Porter >> Real Programmers think better when playing Adventure or Rogue. >> >> PGP key id: 926CCFF5 >> PGP fingerprint: 64C2 C078 13A9 5B23 7738 F7E5 1046 C39B 926C CFF5 >> PGP key available at: keyserver.net, pgp.mit.edu > > > > -- > 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 > _______________________________________________ > weld-dev mailing list > weld-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/weld-dev > Yeah, though I just want the docs. I'm currently downloading everything at http://anonsvn.jboss.org/repos/weld/ and we'll see what happens :) I also upgraded maven to 2.2, am I going to have issues? -- Jason Porter Real Programmers think better when playing Adventure or Rogue. PGP key id: 926CCFF5 PGP fingerprint: 64C2 C078 13A9 5B23 7738 F7E5 1046 C39B 926C CFF5 PGP key available at: keyserver.net, pgp.mit.edu

On Mon, Nov 2, 2009 at 11:16, Dan Allen <dan.j.allen(a)gmail.com&gt; wrote: > Ah, one more small detail. When you checkout reference trunk, simply open > pom.xml and remove the "-SNAPSHOT" from the version. Then you should get all > the dependencies from the release repository. > > But yes, you can just check out everything too. Might as well. That way, you > can help out with bugs ;) > > -Dan > From which module, or all of them? [snip] -- Jason Porter Real Programmers think better when playing Adventure or Rogue. PGP key id: 926CCFF5 PGP fingerprint: 64C2 C078 13A9 5B23 7738 F7E5 1046 C39B 926C CFF5 PGP key available at: keyserver.net, pgp.mit.edu

On Mon, Nov 2, 2009 at 12:28, Dan Allen <dan.j.allen(a)gmail.com&gt; wrote: > Just to refresh/restate. > > 1. svn co http://anonsvn.jboss.org/repos/weld/doc/trunk/reference > weld-reference > 2. cd weld-reference > 3. edit pom.xml; remove -SNAPSHOT from <version> element > 4. mvn > > If you use OpenJDK (IcedTea) JVM on Debian (perhaps others) you > will get a > NullPointerException. Reference to bug report in README.txt > > -Dan Well, that's much easier than what I did. Still no workie: Reason: Cannot find parent: org.jboss.weld:weld-parent for project: org.jboss.weld.reference-guide:weld-reference-guide:jdocbook:1.0.0 for project org.jboss.weld.reference

You mean for example taking NumberGuess and enhance it? That's what Pete proposed as well. On 2 nov. 09, at 18:09, Dan Allen wrote: > Jason, > > Simply check out that branch of the SVN tree and type: > > mvn > > Then, you can choose from either a PDF or HTML. The PDF ends up in > the current directory, the HTML in target/docbook/publish/en-US/html > > -Dan > > p.s. I tried to attach the PDF to the mailinglist, but it got > moderated because of its size > > p.p.s. Probably not a bad tip to point in either the ref guide or > the wiki. > > On Mon, Nov 2, 2009 at 11:47 AM, Jason Porter <lightguard.jp(a)gmail.com > > wrote: > On Sun, Nov 1, 2009 at 21:33, Dan Allen <dan.j.allen(a)gmail.com&gt; > wrote: > > I've made it all the way through the ref guide with revisions > that reflect > > that changes to the RI and spec names and the latest nomenclature > and > > semantics from the spec. It's now ready for a technical review and > > proofreading (in trunk) > > > > https://svn.jboss.org/repos/weld/doc/trunk/reference > > http://anonsvn.jboss.org/repos/weld/doc/trunk/reference > > > > Since there was so much to change, I'm sure there are places > where the > > semantics didn't get properly updated or an explanation is still > out of > > date. Also, there were some areas of the ref guide that were > thin, and I > > didn't have time to fill it all in. If you feel comfortable > explaining a > > topic, please don't be shy to revise or suggest revisions. > > > > Here are some notes to consider: > > > > - Java SE sections need review for accuracy, relevance > > - Extending CDI (extend.xml) is extremely thin, to the point of > being > > marginally useful compared to the spec > > - Weld extensions (extensions.xml) is underwhelming; do we have > more to say > > than just about logging? > > - The chapter on producer fields (producerfields.xml) is missing, > though > > producer fields are explained in intro.xml > > - The Weld SPI needs to be reviewed for accuracy, relevance (ri- > spi.xml); > > this was a *long* chapter and I just don't know the Weld SPI yet > > > > I did add a lot of content while revising, but the ref guide can > always be > > improved. > > > > -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 > > > > _______________________________________________ > > weld-dev mailing list > > weld-dev(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/weld-dev > > > > I'd love to take a look through it (currently reading the spec), but > I'd rather not read the XML files. Is there a simple way to generate > the PDF or the HTML files, or do I need to check everything out and > build from there? > > -- > Jason Porter > Real Programmers think better when playing Adventure or Rogue. > > PGP key id: 926CCFF5 > PGP fingerprint: 64C2 C078 13A9 5B23 7738 F7E5 1046 C39B 926C CFF5 > PGP key available at: keyserver.net, pgp.mit.edu > > > > -- > 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 > _______________________________________________ > weld-dev mailing list > weld-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/weld-dev _______________________________________________ weld-dev mailing list weld-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-dev

I've made it all the way through the ref guide with revisions that reflect that changes to the RI and spec names and the latest nomenclature and semantics from the spec. It's now ready for a technical review and proofreading (in trunk)

https://svn.jboss.org/repos/weld/doc/trunk/reference http://anonsvn.jboss.org/repos/weld/doc/trunk/reference Since there was so much to change, I'm sure there are places where the semantics didn't get properly updated or an explanation is still out of date. Also, there were some areas of the ref guide that were thin, and I didn't have time to fill it all in. If you feel comfortable explaining a topic, please don't be shy to revise or suggest revisions. Here are some notes to consider: - Java SE sections need review for accuracy, relevance - Extending CDI (extend.xml) is extremely thin, to the point of being marginally useful compared to the spec

- Weld extensions (extensions.xml) is underwhelming; do we have more to say than just about logging?

- The chapter on producer fields (producerfields.xml) is missing, though producer fields are explained in intro.xml - The Weld SPI needs to be reviewed for accuracy, relevance (ri- spi.xml); this was a *long* chapter and I just don't know the Weld SPI yet

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.