"The advantage of this approach is that you can write an XML schema
that prevents spelling errors in your XML document. It's even possible
for a tool to generate the XML schema automatically from the compiled
Java code. Or, an integrated development environment could perform the
same validation without the need for the explicit intermediate
1) the RI will have a code->xsd generator for web-beans.xml; could maybe be used for validation....but requires that all classes can compile
2) we should have xml completions following the naming standard layed out by webbeans spec
Update: webbeans.xml is no longer part of the spec but it will be important for extensions to jsr-299 to somehow tell the tooling which annotations/beans they will be adding into the jsr-299 runtime. Seam 3 will most likely use this suggestion for the spec.