[webbeans-commits] Webbeans SVN: r1879 - in doc/tags: webbeans-reference-guide-1.0.0.BETA1 and 2 other directories.

Author: pete.muir(a)jboss.org Date: 2009-03-09 11:10:55 -0400 (Mon, 09 Mar 2009) New Revision: 1879 Added: doc/tags/webbeans-reference-guide-1.0.0.BETA1/ doc/tags/webbeans-reference-guide-1.0.0.BETA1/de-DE/part3.po doc/tags/webbeans-reference-guide-1.0.0.BETA1/en-US/master.xml doc/tags/webbeans-reference-guide-1.0.0.BETA1/en-US/ri.xml doc/tags/webbeans-reference-guide-1.0.0.BETA1/pom.xml Removed: doc/tags/webbeans-reference-guide-1.0.0.BETA1/de-DE/part3.po doc/tags/webbeans-reference-guide-1.0.0.BETA1/en-US/master.xml doc/tags/webbeans-reference-guide-1.0.0.BETA1/en-US/ri.xml doc/tags/webbeans-reference-guide-1.0.0.BETA1/pom.xml Log: [maven-release-plugin] copy for tag webbeans-reference-guide-1.0.0.BETA1 Copied: doc/tags/webbeans-reference-guide-1.0.0.BETA1 (from rev 1870, doc/trunk/reference) Deleted: doc/tags/webbeans-reference-guide-1.0.0.BETA1/de-DE/part3.po =================================================================== --- doc/trunk/reference/de-DE/part3.po 2009-03-09 12:43:54 UTC (rev 1870) +++ doc/tags/webbeans-reference-guide-1.0.0.BETA1/de-DE/part3.po 2009-03-09 15:10:55 UTC (rev 1879) @@ -1,161 +0,0 @@ -# translation of part3.po to -# Language de-DE translations for Introduction_to_Web_Beans package. -# Automatically generated, 2009. -# -msgid "" -msgstr "" -"Project-Id-Version: part3\n" -"Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-01-10 14:18+0000\n" -"PO-Revision-Date: 2009-02-07 15:34+1100\n" -"Last-Translator: \n" -"Language-Team: <en(a)li.org&gt;\n&quot; -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"X-Generator: KBabel 1.11.4\n" - -#. Tag: para -#: part3.xml:5 -#, no-c-format -msgid "" -"The second major theme of Web Beans is <emphasis>strong typing</emphasis>. " -"The information about the dependencies, interceptors and decorators of a Web " -"Bean, and the information about event consumers for an event producer, is " -"contained in typesafe Java constructs that may be validated by the compiler." -msgstr "" -"Das zweite wichtige Thema von Web Beans ist <emphasis>starke Typisierung</emphasis> (sog. \"strong Typing\"). " -"Die Informationen zu Abhängigkeiten, Interzeptoren und Dekoratoren eines Web " -"Beans und die Informationen zu Ereigniskonsumenten (Event Consumers) für einen Ereignis-Producer sind in typensicheren Java-Konstrukten enthalten, die vom Kompilierer (Compiler) validiert werden können." - -#. Tag: para -#: part3.xml:10 -#, no-c-format -msgid "" -"You don't see string-based identifiers in Web Beans code, not because the " -"framework is hiding them from you using clever defaulting rules &#151; so-" -"called \"configuration by convention\" &#151; but because there are simply no " -"strings there to begin with!" -msgstr "Sie sehen keine String-basierten Bezeichner in Web Beans Code; dies ist nicht der Fall weil das Framework diese unter Verwendung irgendwelcher Defaulting-Regeln &#151 vor Ihnen verbirgt; sogenannte \"Konfiguration nach Konvention\" &#151; sondern weil einfach keine Strings existieren!" - -#. Tag: para -#: part3.xml:15 -#, no-c-format -msgid "" -"The obvious benefit of this approach is that <emphasis>any</emphasis> IDE " -"can provide autocompletion, validation and refactoring without the need for " -"special tooling. But there is a second, less-immediately-obvious, benefit. " -"It turns out that when you start thinking of identifying objects, events or " -"interceptors via annotations instead of names, you have an opportunity to " -"lift the semantic level of your code." -msgstr "" -"Der offensichtliche Vorteil dieser Vorgehensweise ist, dass <emphasis>jede</emphasis> IDE " -"Auto-Completion, Validierung und Refaktorierung ohne die Notwendigkeit spezieller Tools bereitstellen kann. Es existiert jedoch noch ein weiterer, nicht sofort ersichtlicher Vorteil. " -"Es stellt sich nämlich heraus, dass Sie - wenn Sie über die Identifizierung von Objekten, Ereignissen oder Interzeptoren via Annotationen statt Namen nachdenken - Sie Gelegenheit haben, die semantische Ebene Ihres Code anzuheben." - -#. Tag: para -#: part3.xml:21 -#, no-c-format -msgid "" -"Web Beans encourages you develop annotations that model concepts, for " -"example," -msgstr "Web Beans soll dazu ermutigen Annotationen zu entwickeln, die Konzepte formen, etwa " - -#. Tag: para -#: part3.xml:26 -#, no-c-format -msgid "<literal>@Asynchronous</literal>," -msgstr "<literal>@Asynchronous</literal>," - -#. Tag: para -#: part3.xml:29 -#, no-c-format -msgid "<literal>@Mock</literal>," -msgstr "<literal>@Mock</literal>," - -#. Tag: para -#: part3.xml:32 -#, no-c-format -msgid "<literal>@Secure</literal> or" -msgstr "<literal>@Secure</literal> oder" - -#. Tag: para -#: part3.xml:35 -#, no-c-format -msgid "<literal>@Updated</literal>," -msgstr "<literal>@Updated</literal>," - -#. Tag: para -#: part3.xml:39 -#, no-c-format -msgid "instead of using compound names like" -msgstr "statt Namen wie Assoziationsbegriffe wie " - -#. Tag: para -#: part3.xml:43 -#, no-c-format -msgid "<literal>asyncPaymentProcessor</literal>," -msgstr "<literal>asyncPaymentProcessor</literal>," - -#. Tag: para -#: part3.xml:46 -#, no-c-format -msgid "<literal>mockPaymentProcessor</literal>," -msgstr "<literal>mockPaymentProcessor</literal>," - -#. Tag: para -#: part3.xml:49 -#, no-c-format -msgid "<literal>SecurityInterceptor</literal> or" -msgstr "<literal>SecurityInterceptor</literal> oder" - -#. Tag: para -#: part3.xml:52 -#, no-c-format -msgid "<literal>DocumentUpdatedEvent</literal>." -msgstr "<literal>DocumentUpdatedEvent</literal> zu verwenden." - -#. Tag: para -#: part3.xml:56 -#, no-c-format -msgid "" -"The annotations are reusable. They help describe common qualities of " -"disparate parts of the system. They help us categorize and understand our " -"code. They help us deal with common concerns in a common way. They make our " -"code more literate and more understandable." -msgstr "Die Annotationen sind wiederverwendbar. Sie helfen bei der Beschreibung gängiger Eigenschaften verschiedener Teile des Systems. Sie helfen uns bei der Kategorisierung und dem Verständnis unseres Codes. Sie helfen uns dabei auf gängige Weise mit gängigen Problemen umzugehen. Sie machen unseren Code leichter lesbar und einfacher zu verstehen." - -#. Tag: para -#: part3.xml:61 -#, no-c-format -msgid "" -"Web Beans <emphasis>stereotypes</emphasis> take this idea a step further. A " -"stereotype models a common <emphasis>role</emphasis> in your application " -"architecture. It encapsulates various properties of the role, including " -"scope, interceptor bindings, deployment type, etc, into a single reusable " -"package." -msgstr "Web Beans <emphasis>Stereotypen</emphasis> erweitern diese Idee um einen Schritt. Ein Stereotyp formt eine gängige <emphasis>Rolle</emphasis> in Ihrer Anwendungsarchitektur. Es enthält verschiedene Eigenschaften der Rolle, einschließlich deren Geltungsbereich, Interzeptorbindungen, Deployment-Typ usw. in einem einzelnen, wiederverwendbaren Paket." - -#. Tag: para -#: part3.xml:66 -#, no-c-format -msgid "" -"Even Web Beans XML metadata is strongly typed! There's no compiler for XML, " -"so Web Beans takes advantage of XML schemas to validate the Java types and " -"attributes that appear in XML. This approach turns out to make the XML more " -"literate, just like annotations made our Java code more literate." -msgstr "" -"Sogar Web Beans XML Metadaten sind stark typisiert! Es gibt keinen Kompilierer für XML, " -"daher nutzen Web Beans XML-Schemas zur Validierung der in XML vorkommenden Java-Typen und Attribute. Diese Vorgehensweise führt zur besseren Lesbarkeit der XML, ebenso wie Annotationen unseren Java Code einfacher lesbar machten." - -#. Tag: para -#: part3.xml:71 -#, no-c-format -msgid "" -"We're now ready to meet some more advanced features of Web Beans. Bear in " -"mind that these features exist to make our code both easier to validate and " -"more understandable. Most of the time you don't ever really <emphasis>need</" -"emphasis> to use these features, but if you use them wisely, you'll come to " -"appreciate their power." -msgstr "Wir können jetzt einige fortgeschrittenere Features von Web Beans kennenlernen. Vergessen Sie nicht, dass diese Features unseren Code sowohl einfacher zu validieren als auch leserlicher machen sollen. Meist werden Sie diese Features nicht verwenden <emphasis>müssen</emphasis>, wenn Sie dies aber auf kluge Weise tun, so werden Sie deren Vorteile schnell zu schätzen wissen." - Copied: doc/tags/webbeans-reference-guide-1.0.0.BETA1/de-DE/part3.po (from rev 1878, doc/trunk/reference/de-DE/part3.po) =================================================================== --- doc/tags/webbeans-reference-guide-1.0.0.BETA1/de-DE/part3.po (rev 0) +++ doc/tags/webbeans-reference-guide-1.0.0.BETA1/de-DE/part3.po 2009-03-09 15:10:55 UTC (rev 1879) @@ -0,0 +1,161 @@ +# translation of part3.po to +# Language de-DE translations for Introduction_to_Web_Beans package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: part3\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-01-10 14:18+0000\n" +"PO-Revision-Date: 2009-02-07 15:34+1100\n" +"Last-Translator: \n" +"Language-Team: <en(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: para +#: part3.xml:5 +#, no-c-format +msgid "" +"The second major theme of Web Beans is <emphasis>strong typing</emphasis>. " +"The information about the dependencies, interceptors and decorators of a Web " +"Bean, and the information about event consumers for an event producer, is " +"contained in typesafe Java constructs that may be validated by the compiler." +msgstr "" +"Das zweite wichtige Thema von Web Beans ist <emphasis>starke Typisierung</emphasis> (sog. \"strong Typing\"). " +"Die Informationen zu Abhängigkeiten, Interzeptoren und Dekoratoren eines Web " +"Beans und die Informationen zu Ereigniskonsumenten (Event Consumers) für einen Ereignis-Producer sind in typensicheren Java-Konstrukten enthalten, die vom Kompilierer (Compiler) validiert werden können." + +#. Tag: para +#: part3.xml:10 +#, no-c-format +msgid "" +"You don't see string-based identifiers in Web Beans code, not because the " +"framework is hiding them from you using clever defaulting rules &#151; so-" +"called \"configuration by convention\" &#151; but because there are simply no " +"strings there to begin with!" +msgstr "Sie sehen keine String-basierten Bezeichner in Web Beans Code; dies ist nicht der Fall weil das Framework diese unter Verwendung irgendwelcher Defaulting-Regeln &#151; vor Ihnen verbirgt; sogenannte \"Konfiguration nach Konvention\" &#151; sondern weil einfach keine Strings existieren!" + +#. Tag: para +#: part3.xml:15 +#, no-c-format +msgid "" +"The obvious benefit of this approach is that <emphasis>any</emphasis> IDE " +"can provide autocompletion, validation and refactoring without the need for " +"special tooling. But there is a second, less-immediately-obvious, benefit. " +"It turns out that when you start thinking of identifying objects, events or " +"interceptors via annotations instead of names, you have an opportunity to " +"lift the semantic level of your code." +msgstr "" +"Der offensichtliche Vorteil dieser Vorgehensweise ist, dass <emphasis>jede</emphasis> IDE " +"Auto-Completion, Validierung und Refaktorierung ohne die Notwendigkeit spezieller Tools bereitstellen kann. Es existiert jedoch noch ein weiterer, nicht sofort ersichtlicher Vorteil. " +"Es stellt sich nämlich heraus, dass Sie - wenn Sie über die Identifizierung von Objekten, Ereignissen oder Interzeptoren via Annotationen statt Namen nachdenken - Sie Gelegenheit haben, die semantische Ebene Ihres Code anzuheben." + +#. Tag: para +#: part3.xml:21 +#, no-c-format +msgid "" +"Web Beans encourages you develop annotations that model concepts, for " +"example," +msgstr "Web Beans soll dazu ermutigen Annotationen zu entwickeln, die Konzepte formen, etwa " + +#. Tag: para +#: part3.xml:26 +#, no-c-format +msgid "<literal>@Asynchronous</literal>," +msgstr "<literal>@Asynchronous</literal>," + +#. Tag: para +#: part3.xml:29 +#, no-c-format +msgid "<literal>@Mock</literal>," +msgstr "<literal>@Mock</literal>," + +#. Tag: para +#: part3.xml:32 +#, no-c-format +msgid "<literal>@Secure</literal> or" +msgstr "<literal>@Secure</literal> oder" + +#. Tag: para +#: part3.xml:35 +#, no-c-format +msgid "<literal>@Updated</literal>," +msgstr "<literal>@Updated</literal>," + +#. Tag: para +#: part3.xml:39 +#, no-c-format +msgid "instead of using compound names like" +msgstr "statt Namen wie Assoziationsbegriffe wie " + +#. Tag: para +#: part3.xml:43 +#, no-c-format +msgid "<literal>asyncPaymentProcessor</literal>," +msgstr "<literal>asyncPaymentProcessor</literal>," + +#. Tag: para +#: part3.xml:46 +#, no-c-format +msgid "<literal>mockPaymentProcessor</literal>," +msgstr "<literal>mockPaymentProcessor</literal>," + +#. Tag: para +#: part3.xml:49 +#, no-c-format +msgid "<literal>SecurityInterceptor</literal> or" +msgstr "<literal>SecurityInterceptor</literal> oder" + +#. Tag: para +#: part3.xml:52 +#, no-c-format +msgid "<literal>DocumentUpdatedEvent</literal>." +msgstr "<literal>DocumentUpdatedEvent</literal> zu verwenden." + +#. Tag: para +#: part3.xml:56 +#, no-c-format +msgid "" +"The annotations are reusable. They help describe common qualities of " +"disparate parts of the system. They help us categorize and understand our " +"code. They help us deal with common concerns in a common way. They make our " +"code more literate and more understandable." +msgstr "Die Annotationen sind wiederverwendbar. Sie helfen bei der Beschreibung gängiger Eigenschaften verschiedener Teile des Systems. Sie helfen uns bei der Kategorisierung und dem Verständnis unseres Codes. Sie helfen uns dabei auf gängige Weise mit gängigen Problemen umzugehen. Sie machen unseren Code leichter lesbar und einfacher zu verstehen." + +#. Tag: para +#: part3.xml:61 +#, no-c-format +msgid "" +"Web Beans <emphasis>stereotypes</emphasis> take this idea a step further. A " +"stereotype models a common <emphasis>role</emphasis> in your application " +"architecture. It encapsulates various properties of the role, including " +"scope, interceptor bindings, deployment type, etc, into a single reusable " +"package." +msgstr "Web Beans <emphasis>Stereotypen</emphasis> erweitern diese Idee um einen Schritt. Ein Stereotyp formt eine gängige <emphasis>Rolle</emphasis> in Ihrer Anwendungsarchitektur. Es enthält verschiedene Eigenschaften der Rolle, einschließlich deren Geltungsbereich, Interzeptorbindungen, Deployment-Typ usw. in einem einzelnen, wiederverwendbaren Paket." + +#. Tag: para +#: part3.xml:66 +#, no-c-format +msgid "" +"Even Web Beans XML metadata is strongly typed! There's no compiler for XML, " +"so Web Beans takes advantage of XML schemas to validate the Java types and " +"attributes that appear in XML. This approach turns out to make the XML more " +"literate, just like annotations made our Java code more literate." +msgstr "" +"Sogar Web Beans XML Metadaten sind stark typisiert! Es gibt keinen Kompilierer für XML, " +"daher nutzen Web Beans XML-Schemas zur Validierung der in XML vorkommenden Java-Typen und Attribute. Diese Vorgehensweise führt zur besseren Lesbarkeit der XML, ebenso wie Annotationen unseren Java Code einfacher lesbar machten." + +#. Tag: para +#: part3.xml:71 +#, no-c-format +msgid "" +"We're now ready to meet some more advanced features of Web Beans. Bear in " +"mind that these features exist to make our code both easier to validate and " +"more understandable. Most of the time you don't ever really <emphasis>need</" +"emphasis> to use these features, but if you use them wisely, you'll come to " +"appreciate their power." +msgstr "Wir können jetzt einige fortgeschrittenere Features von Web Beans kennenlernen. Vergessen Sie nicht, dass diese Features unseren Code sowohl einfacher zu validieren als auch leserlicher machen sollen. Meist werden Sie diese Features nicht verwenden <emphasis>müssen</emphasis>, wenn Sie dies aber auf kluge Weise tun, so werden Sie deren Vorteile schnell zu schätzen wissen." + Deleted: doc/tags/webbeans-reference-guide-1.0.0.BETA1/en-US/master.xml =================================================================== --- doc/trunk/reference/en-US/master.xml 2009-03-09 12:43:54 UTC (rev 1870) +++ doc/tags/webbeans-reference-guide-1.0.0.BETA1/en-US/master.xml 2009-03-09 15:10:55 UTC (rev 1879) @@ -1,71 +0,0 @@ -<?xml version='1.0' encoding="iso-8859-1"?> - -<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [ ]> - -<book lang="en"> - - <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - <preface> - <title>Note</title> - <para> - JSR-299 has recently changed its name from "Web Beans" to "Java - Contexts and Dependency Injection". The reference guide still refers - to JSR-299 as "Web Beans" and the JSR-299 Reference Implementation as - the "Web Beans RI". Other documentation, blogs, forum posts etc. may - use the new nomenclature, including the new name for the JSR-299 - Reference Implementation - "Web Beans". - </para> - </preface> - - <toc/> - - <part> - <title>Using contextual objects</title> - - <xi:include href="part1.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="intro.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="example.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="ri.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="injection.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="scopescontexts.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="producermethods.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - </part> - - <part> - <title>Developing loosely-coupled code</title> - - <xi:include href="part2.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="interceptors.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="decorators.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="events.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - </part> - - <part> - <title>Making the most of strong typing</title> - - <xi:include href="part3.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - <xi:include href="stereotypes.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="specialization.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="xml.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - </part> - - <part> - <title>Web Beans and the Java EE ecosystem</title> - - <xi:include href="part4.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - <xi:include href="ee.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="extend.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - </part> - - <xi:include href="next.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="ri-spi.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - -</book> - Copied: doc/tags/webbeans-reference-guide-1.0.0.BETA1/en-US/master.xml (from rev 1872, doc/trunk/reference/en-US/master.xml) =================================================================== --- doc/tags/webbeans-reference-guide-1.0.0.BETA1/en-US/master.xml (rev 0) +++ doc/tags/webbeans-reference-guide-1.0.0.BETA1/en-US/master.xml 2009-03-09 15:10:55 UTC (rev 1879) @@ -0,0 +1,77 @@ +<?xml version='1.0' encoding="iso-8859-1"?> + +<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [ ]> + +<book lang="en"> + + <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + + <preface> + <title>Note</title> + <para> + JSR-299 has recently changed its name from "Web Beans" to "Java + Contexts and Dependency Injection". The reference guide still refers + to JSR-299 as "Web Beans" and the JSR-299 Reference Implementation as + the "Web Beans RI". Other documentation, blogs, forum posts etc. may + use the new nomenclature, including the new name for the JSR-299 + Reference Implementation - "Web Beans". + </para> + + <para> + You'll also find that some of the more recent functionality to be + specified is missing (such as producer fields, realization, + asynchronous events, XML mapping of EE resources). + </para> + </preface> + + <toc/> + + <part> + <title>Using contextual objects</title> + + <xi:include href="part1.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="intro.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="example.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="ri.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="injection.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="scopescontexts.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="producermethods.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + + </part> + + <part> + <title>Developing loosely-coupled code</title> + + <xi:include href="part2.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="interceptors.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="decorators.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="events.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + + </part> + + <part> + <title>Making the most of strong typing</title> + + <xi:include href="part3.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + + <xi:include href="stereotypes.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="specialization.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="xml.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + + </part> + + <part> + <title>Web Beans and the Java EE ecosystem</title> + + <xi:include href="part4.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + + <xi:include href="ee.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="extend.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + + </part> + + <xi:include href="next.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="ri-spi.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + +</book> + Deleted: doc/tags/webbeans-reference-guide-1.0.0.BETA1/en-US/ri.xml =================================================================== --- doc/trunk/reference/en-US/ri.xml 2009-03-09 12:43:54 UTC (rev 1870) +++ doc/tags/webbeans-reference-guide-1.0.0.BETA1/en-US/ri.xml 2009-03-09 15:10:55 UTC (rev 1879) @@ -1,756 +0,0 @@ -<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [ ]> - -<chapter id="ri"> - <title>The Web Beans Reference Implementation</title> - - <para> - The Web Beans Reference Implementation is being developed at - <ulink url="http://seamframework.org/WebBeans">the Seam project</ulink>. - You can download the latest developer release of Web Beans from the - <ulink url="http://seamframework.org/Download">the downloads page</ulink>. - </para> - - <para> - The Web Beans RI comes with a two deployable example applications: - <literal>webbeans-numberguess</literal>, a war example, containing only - simple beans, and <literal>webbeans-translator</literal> an ear example, - containing enterprise beans. To run the examples you'll need the following: - </para> - - <itemizedlist> - <listitem> - <para>the latest release of the Web Beans RI,</para> - </listitem> - <listitem> - <para>JBoss AS 5.0.0.GA, and</para> - </listitem> - <listitem> - <para>Ant 1.7.0.</para> - </listitem> - </itemizedlist> - - <para> - Currently, the Web Beans RI only runs on JBoss Application Server 5. - You'll need to download JBoss AS 5.0.0.GA from - <ulink url="http://www.jboss.org/jbossas/downloads/">jboss.org</...;, - and unzip it. For example: - </para> - - <programlisting><![CDATA[$ cd /Applications -$ unzip ~/jboss-5.0.0.GA.zip]]></programlisting> - - <para> - Next, download the Web Beans RI from - <ulink url="http://seamframework.org/Download">seamframework.org<...;, - and unzip it. For example - </para> - - <programlisting><![CDATA[$ cd ~/ -$ unzip ~/webbeans-$VERSION.zip]]></programlisting> - - - <para> - Next, we need to tell Web Beans where JBoss is located. Edit - <literal>jboss-as/build.properties</literal> and set the - <literal>jboss.home</literal> property. For example: - </para> - - <programlisting>jboss.home=/Applications/jboss-5.0.0.GA</programlisting> - - <para> - As Web Beans is a new piece of software, you need to update JBoss AS to - run the Web Beans RI. Future versions of JBoss AS will include these - updates, and this step won't be necessary. - </para> - - <note> - <para> - Currently, two updates are needed. Firstly, a new deployer, - <literal>webbeans.deployer</literal> is added. This adds supports for - Web Bean archives to JBoss AS, and allows the Web Beans RI to query the - EJB3 container and discover which EJBs are installed in your - application. Secondly, an update to JBoss EJB3 is needed. - </para> - </note> - - <para> - To install the update, you'll need Ant 1.7.0 installed, and the - <literal>ANT_HOME</literal> environment variable set. For example: - </para> - - <programlisting>$ unzip apache-ant-1.7.0.zip -$ export ANT_HOME=~/apache-ant-1.7.0</programlisting> - - <para> - Then, you can install the update. The update script will use Maven to - download the Web Beans and EJB3 automatically. - </para> - - <programlisting>$ cd webbeans-$VERSION/jboss-as -$ ant update</programlisting> - - <para> - Now, you're ready to deploy your first example! - </para> - - <tip> - <para> - The build scripts for the examples offer a number of targets, these - are: - </para> - <itemizedlist> - <listitem> - <para> - <literal>ant restart</literal> - deploy the example in exploded - format - </para> - </listitem> - <listitem> - <para> - <literal>ant explode</literal> - update an exploded example, without - restarting the deployment - </para> - </listitem> - <listitem> - <para> - <literal>ant deploy</literal> - deploy the example in compressed jar format - </para> - </listitem> - <listitem> - <para> - <literal>ant undeploy</literal> - remove the example from the server - </para> - </listitem> - <listitem> - <para> - <literal>ant clean</literal> - clean the example - </para> - </listitem> - </itemizedlist> - </tip> - - <para> - To deploy the numberguess example: - </para> - - <programlisting>$ cd examples/numberguess -ant deploy</programlisting> - - <para> - Start JBoss AS: - </para> - - <programlisting>$ /Application/jboss-5.0.0.GA/bin/run.sh</programlisting> - - <tip> - <para> - If you use Windows, use the <literal>run.bat</literal>script. - </para> - </tip> - - <para> - Wait for the application to deploy, and enjoy hours of fun at - <ulink url="http://localhost:8080/webbeans-numberguess" />! - </para> - - <para> - The Web Beans RI includes a second simple example that will translate your text - into Latin. The numberguess example is a war example, and uses only simple - beans; the translator example is an ear example, and includes enterprise - beans, packaged in an EJB module. To try it out: - </para> - - <programlisting>$ cd examples/translator -ant deploy</programlisting> - - <para> - Wait for the application to deploy, and visit - <ulink url="http://localhost:8080/webbeans-translator" />! - </para> - - <section> - <title>The numberguess example</title> - - <para> - In the numberguess application you get given 10 attempts to guess a - number between 1 and 100. After each attempt, you will be told whether - you are too high, or too low. - </para> - - <para> - The numberguess example is comprised of a number of Web Beans, - configuration files, and Facelet JSF pages, packaged as a war. Let's - start with the configuration files. - </para> - - <para> - All the configuration files for this example are located in - <literal>WEB-INF/</literal>, which is stored in - <literal>WebContent</literal> in the source tree. First, we have - <literal>faces-config.xml</literal>, in which we tell JSF to use - Facelets: - </para> - - <programlisting role="XML"><![CDATA[<?xml version='1.0' encoding='UTF-8'?> -<faces-config version="1.2" - xmlns="http://java.sun.com/xml/ns/javaee" - xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" - xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd"> - - <application> - <view-handler>com.sun.facelets.FaceletViewHandler</view-handler> - </application> - -</faces-config>]]></programlisting> - - <para> - There is an empty <literal>web-beans.xml</literal> file, which marks - this application as a Web Beans application. - </para> - - <para> - Finally there is <literal>web.xml</literal>: - </para> - - <programlistingco> - <areaspec> - <area id="faces.servlet" coords="12" /> - <area id="faces.servlet.mapping" coords="18" /> - <area id="faces.default.suffix" coords="23" /> - <area id="session.timeout" coords="28" /> - <area id="webbeans.listener" coords="32" /> - </areaspec> - <programlisting><![CDATA[<?xml version="1.0" encoding="UTF-8"?> - -<web-app version="2.5" - xmlns="http://java.sun.com/xml/ns/javaee" - xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" - xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"> - - <display-name>Web Beans Numbergues example</display-name> - - <!-- JSF --> - - <servlet> - <servlet-name>Faces Servlet</servlet-name> - <servlet-class>javax.faces.webapp.FacesServlet</servlet-class> - <load-on-startup>1</load-on-startup> - </servlet> - - <servlet-mapping> - <servlet-name>Faces Servlet</servlet-name> - <url-pattern>*.jsf</url-pattern> - </servlet-mapping> - - <context-param> - <param-name>javax.faces.DEFAULT_SUFFIX</param-name> - <param-value>.xhtml</param-value> - </context-param> - - <session-config> - <session-timeout>10</session-timeout> - </session-config> - -</web-app>]]></programlisting> - <calloutlist> - <callout arearefs="faces.servlet"> - <para> - Enable and load the JSF servlet - </para> - </callout> - <callout arearefs="faces.servlet.mapping"> - <para> - Configure requests to <literal>.jsf</literal> pages to be - handled by JSF - </para> - </callout> - <callout arearefs="faces.default.suffix"> - <para> - Tell JSF that we will be giving our source files (facelets) an - extension of <literal>.jsf</literal> - </para> - </callout> - <callout arearefs="session.timeout"> - <para> - Configure a session timeout of 10 minutes - </para> - </callout> - </calloutlist> - </programlistingco> - - <note> - <para> - Whilst this demo is a JSF demo, you can use the Web Beans RI with - any Servlet based web framework. - </para> - </note> - - <para> - Let's take a look at the Facelet view: - </para> - - <programlistingco> - <areaspec> - <area id="template" coords="8" /> - <area id="messages" coords="12" /> - <area id="instructions" coords="19" /> - <area id="guess" coords="25" /> - <area id="validator" coords="30" /> - <area id="submit" coords="33" /> - </areaspec> - <programlisting><![CDATA[<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html xmlns="http://www.w3.org/1999/xhtml" - xmlns:ui="http://java.sun.com/jsf/facelets" - xmlns:h="http://java.sun.com/jsf/html" - xmlns:f="http://java.sun.com/jsf/core" - xmlns:s="http://jboss.com/products/seam/taglib"> - - <ui:composition template="template.xhtml"> - <ui:define name="content"> - <h1>Guess a number...</h1> - <h:form id="NumberGuessMain"> - <div style="color: red"> - <h:messages id="messages" globalOnly="false"/> - <h:outputText id="Higher" value="Higher!" rendered="#{game.number gt game.guess and game.guess ne 0}"/> - <h:outputText id="Lower" value="Lower!" rendered="#{game.number lt game.guess and game.guess ne 0}"/> - </div> - - <div> - I'm thinking of a number between #{game.smallest} and #{game.biggest}. - You have #{game.remainingGuesses} guesses. - </div> - - <div> - Your guess: - <h:inputText id="inputGuess" - value="#{game.guess}" - required="true" - size="3" - disabled="#{game.number eq game.guess}"> - <f:validateLongRange maximum="#{game.biggest}" - minimum="#{game.smallest}"/> - </h:inputText> - <h:commandButton id="GuessButton" - value="Guess" - action="#{game.check}" - disabled="#{game.number eq game.guess}"/> - </div> - <div> - <h:commandButton id="RestartButton" value="Reset" action="#{game.reset}" immediate="true" /> - </div> - </h:form> - </ui:define> - </ui:composition> -</html>]]></programlisting> - <calloutlist> - <callout arearefs="template"> - <para> - Facelets is a templating language for JSF, here we are - wrapping our page in a template which defines the header. - </para> - </callout> - <callout arearefs="messages"> - <para> - There are a number of messages which can be sent to the user, - "Higher!", "Lower!" and "Correct!" - </para> - </callout> - <callout arearefs="instructions"> - <para> - As the user guesses, the range of numbers they can guess gets - smaller - this sentance changes to make sure they know what - range to guess in. - </para> - </callout> - <callout arearefs="guess"> - <para> - This input field is bound to a Web Bean, using the value - expression. - </para> - </callout> - <callout arearefs="validator"> - <para> - A range validator is used to make sure the user doesn't - accidentally input a number outside of the range in which they - can guess - if the validator wasn't here, the user might use - up a guess on an out of range number. - </para> - </callout> - <callout arearefs="submit"> - <para> - And, of course, there must be a way for the user to send their - guess to the server. Here we bind to an action method on the - Web Bean. - </para> - </callout> - </calloutlist> - </programlistingco> - - <para> - The example exists of 4 classes, the first two of which are binding - types. First, there is the <literal>@Random</literal> binding type, - used for injecting a random number: - </para> - - <programlisting role="JAVA"><![CDATA[@Target( { TYPE, METHOD, PARAMETER, FIELD }) -@Retention(RUNTIME) -@Documented -@BindingType -public @interface Random {}]]></programlisting> - - <para> - There is also the <literal>@MaxNumber</literal> binding type, used for - injecting the maximum number that can be injected: - </para> - - <programlisting role="JAVA"><![CDATA[@Target( { TYPE, METHOD, PARAMETER, FIELD }) -@Retention(RUNTIME) -@Documented -@BindingType -public @interface MaxNumber {} -]]></programlisting> - - <para> - The <literal>Generator</literal> class is responsible for creating the - random number, via a producer method. It also exposes the maximum - possible number via a producer method: - </para> - - <programlisting role="JAVA"><![CDATA[@ApplicationScoped -public class Generator { - - private java.util.Random random = new java.util.Random( System.currentTimeMillis() ); - - private int maxNumber = 100; - - java.util.Random getRandom() - { - return random; - } - - @Produces @Random int next() { - return getRandom().nextInt(maxNumber); - } - - @Produces @MaxNumber int getMaxNumber() - { - return maxNumber; - } - -}]]></programlisting> - - <para> - You'll notice that the <literal>Generator</literal> is application - scoped; therefore we don't get a different random each time. - </para> - - <para> - The final Web Bean in the application is the session scoped - <literal>Game</literal>. - </para> - - <para> - You'll note that we've used the <literal>@Named</literal> - annotation, so that we can use the bean through EL in the JSF page. - Finally, we've used constructor injection to initialize the game with - a random number. And of course, we need to tell the player when they've - won, so we give feedback with a <literal>FacesMessage</literal>. - </para> - - <programlisting role="JAVA"><![CDATA[package org.jboss.webbeans.examples.numberguess; - - -import javax.annotation.PostConstruct; -import javax.faces.application.FacesMessage; -import javax.faces.context.FacesContext; -import javax.webbeans.AnnotationLiteral; -import javax.webbeans.Current; -import javax.webbeans.Initializer; -import javax.webbeans.Named; -import javax.webbeans.SessionScoped; -import javax.webbeans.manager.Manager; - -@Named -@SessionScoped -public class Game -{ - private int number; - - private int guess; - private int smallest; - private int biggest; - private int remainingGuesses; - - @Current Manager manager; - - public Game() - { - } - - @Initializer - Game(@MaxNumber int maxNumber) - { - this.biggest = maxNumber; - } - - public int getNumber() - { - return number; - } - - public int getGuess() - { - return guess; - } - - public void setGuess(int guess) - { - this.guess = guess; - } - - public int getSmallest() - { - return smallest; - } - - public int getBiggest() - { - return biggest; - } - - public int getRemainingGuesses() - { - return remainingGuesses; - } - - public String check() - { - if (guess>number) - { - biggest = guess - 1; - } - if (guess<number) - { - smallest = guess + 1; - } - if (guess == number) - { - FacesContext.getCurrentInstance().addMessage(null, new FacesMessage("Correct!")); - } - remainingGuesses--; - return null; - } - - @PostConstruct - public void reset() - { - this.smallest = 0; - this.guess = 0; - this.remainingGuesses = 10; - this.number = manager.getInstanceByType(Integer.class, new AnnotationLiteral<Random>(){}); - } - -}]]></programlisting> - </section> - - <section> - <title>The translator example</title> - - <para> - The translator example will take any sentences you enter, and translate - them to Latin. - </para> - - <para> - The translator example is built as an ear, and contains EJBs. As a result, it's structure is more complex than - the numberguess example. - </para> - - <note> - <para> - EJB 3.1 and Jave EE 6 allow you to package EJBs in a war, which will - make this structure much simpler! - </para> - </note> - - <para> - First, let's take a look at the ear aggregator, which is located in - <literal>webbeans-translator-ear</literal> module. Maven automatically - generates the <literal>application.xml</literal> for us: - </para> - - <programlisting role="XML"><![CDATA[<plugin> - <groupId>org.apache.maven.plugins</groupId> - <artifactId>maven-ear-plugin</artifactId> - <configuration> - <modules> - <webModule> - <groupId>org.jboss.webbeans.examples.translator</groupId> - <artifactId>webbeans-translator-war</artifactId> - <contextRoot>/webbeans-translator</contextRoot> - </webModule> - </modules> - </configuration> -</plugin>]]></programlisting> - - <para> - Here we set the context path, which gives us a nice url - (<ulink url="http://localhost:8080/webbeans-translator">http://localhost:8080/webbeans-translator</ulink>). - </para> - - <tip> - <para> - If you aren't using Maven to generate these files, you would need - <literal>META-INF/application.xml</literal>: - </para> - - <programlisting role="XML"><![CDATA[<?xml version="1.0" encoding="UTF-8"?> -<application xmlns="http://java.sun.com/xml/ns/javaee" - xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" - xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd" - version="5"> - <display-name>webbeans-translator-ear</display-name> - <description>Ear Example for the reference implementation of JSR 299: Web Beans</description> - - <module> - <web> - <web-uri>webbeans-translator.war</web-uri> - <context-root>/webbeans-translator</context-root> - </web> - </module> - <module> - <ejb>webbeans-translator.jar</ejb> - </module> -</application>]]></programlisting> - </tip> - - <para> - Next, lets look at the war. Just as in the numberguess example, we have - a <literal>faces-config.xml</literal> (to enabled Facelets) and a - <literal>web.xml</literal> (to enable JSF) in - <literal>WebContent/WEB-INF</literal>. - </para> - - <para> - More intersting is the facelet used to translate text. Just as in - the numberguess example we have a template, which surrounds the form - (ommitted here for brevity): - </para> - - <programlisting role="XML"><![CDATA[<h:form id="NumberGuessMain"> - - <table> - <tr align="center" style="font-weight: bold" > - <td> - Your text - </td> - <td> - Translation - </td> - </tr> - <tr> - <td> - <h:inputTextarea id="text" value="#{translator.text}" required="true" rows="5" cols="80" /> - </td> - <td> - <h:outputText value="#{translator.translatedText}" /> - </td> - </tr> - </table> - <div> - <h:commandButton id="button" value="Translate" action="#{translator.translate}"/> - </div> - -</h:form>]]></programlisting> - - <para> - The user can enter some text in the lefthand textarea, and hit the - translate button to see the result to the right. - </para> - - <para> - Finally, let's look at the ejb module, - <literal>webbeans-translator-ejb</literal>. - In <literal>src/main/resources/META-INF</literal> there is just an - empty <literal>web-beans.xml</literal>, used to mark the archive as - containing Web Beans. - </para> - - <para> - We've saved the most interesting bit to last, the code! The project has - two simple beans, <literal>SentenceParser</literal> and - <literal>TextTranslator</literal> and two enterprise beans, - <literal>TranslatorControllerBean</literal> and - <literal>SentenceTranslator</literal>. You should be getting quite - familiar with what a Web Bean looks like by now, so we'll just - highlight the most interesting bits here. - </para> - - <para> - Both <literal>SentenceParser</literal> and - <literal>TextTranslator</literal> are dependent beans, and - <literal>TextTranslator</literal> uses constructor initialization: - </para> - - <programlisting role="JAVA"><![CDATA[public class TextTranslator { - private SentenceParser sentenceParser; - private Translator sentenceTranslator; - - @Initializer - TextTranslator(SentenceParser sentenceParser, Translator sentenceTranslator) - { - this.sentenceParser = sentenceParser; - this.sentenceTranslator = sentenceTranslator;]]></programlisting> - - <para> - <literal>TextTranslator</literal> is a stateless bean (with a local - business interface), where the magic happens - of course, we couldn't - develop a full translator, but we gave it a good go! - </para> - - <para> - Finally, there is UI orientated controller, that collects the text from - the user, and dispatches it to the translator. This is a request - scoped, named, stateful session bean, which injects the translator. - </para> - - <programlisting role="JAVA"><![CDATA[@Stateful -@RequestScoped -@Named("translator") -public class TranslatorControllerBean implements TranslatorController -{ - - @Current TextTranslator translator;]]></programlisting> - - <para> - The bean also has getters and setters for all the fields on the page. - </para> - - <para> - As this is a stateful session bean, we have to have a remove method: - </para> - - <programlisting role="JAVA"><![CDATA[ @Remove - public void remove() - { - - }]]></programlisting> - - <para> - The Web Beans manager will call the remove method for you when the bean - is destroyed; in this case at the end of the request. - </para> - </section> - - <para> - That concludes our short tour of the Web Beans RI examples. For more on - the RI, or to help out, please visit - <ulink url="http://www.seamframework.org/WebBeans/Development">http...;. - </para> - - <para> - We need help in all areas - bug fixing, writing new features, writing - examples and translating this reference guide. - </para> - -</chapter> \ No newline at end of file Copied: doc/tags/webbeans-reference-guide-1.0.0.BETA1/en-US/ri.xml (from rev 1872, doc/trunk/reference/en-US/ri.xml) =================================================================== --- doc/tags/webbeans-reference-guide-1.0.0.BETA1/en-US/ri.xml (rev 0) +++ doc/tags/webbeans-reference-guide-1.0.0.BETA1/en-US/ri.xml 2009-03-09 15:10:55 UTC (rev 1879) @@ -0,0 +1,754 @@ +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [ ]> + +<chapter id="ri"> + <title>The Web Beans Reference Implementation</title> + + <para> + The Web Beans Reference Implementation is being developed at + <ulink url="http://seamframework.org/WebBeans">the Seam project</ulink>. + You can download the latest developer release of Web Beans from the + <ulink url="http://seamframework.org/Download">the downloads page</ulink>. + </para> + + <para> + The Web Beans RI comes with a two deployable example applications: + <literal>webbeans-numberguess</literal>, a war example, containing only + simple beans, and <literal>webbeans-translator</literal> an ear example, + containing enterprise beans. To run the examples you'll need the following: + </para> + + <itemizedlist> + <listitem> + <para>the latest release of the Web Beans RI,</para> + </listitem> + <listitem> + <para>JBoss AS 5.0.0.GA, and</para> + </listitem> + <listitem> + <para>Ant 1.7.0.</para> + </listitem> + </itemizedlist> + + <para> + Currently, the Web Beans RI only runs on JBoss Application Server 5. + You'll need to download JBoss AS 5.0.1.GA from + <ulink url="http://www.jboss.org/jbossas/downloads/">jboss.org</...;, + and unzip it. For example: + </para> + + <programlisting><![CDATA[$ cd /Applications +$ unzip ~/jboss-5.0.1.GA.zip]]></programlisting> + + <para> + Next, download the Web Beans RI from + <ulink url="http://seamframework.org/Download">seamframework.org<...;, + and unzip it. For example + </para> + + <programlisting><![CDATA[$ cd ~/ +$ unzip ~/webbeans-$VERSION.zip]]></programlisting> + + + <para> + Next, we need to tell Web Beans where JBoss is located. Edit + <literal>jboss-as/build.properties</literal> and set the + <literal>jboss.home</literal> property. For example: + </para> + + <programlisting>jboss.home=/Applications/jboss-5.0.1.GA</programlisting> + + <note> + <para> + A new deployer, + <literal>webbeans.deployer</literal> is added to JBoss AS. This adds supports for + Web Bean archives to JBoss AS, and allows the Web Beans RI to query the + EJB3 container and discover which EJBs are installed in your + application. + </para> + + <para> + Web Beans is bundled with JBoss AS 5.1 and above. + </para> + </note> + + <para> + To install Web Beans, you'll need Ant 1.7.0 installed, and the + <literal>ANT_HOME</literal> environment variable set. For example: + </para> + + <programlisting>$ unzip apache-ant-1.7.0.zip +$ export ANT_HOME=~/apache-ant-1.7.0</programlisting> + + <para> + Then, you can install the update. The update script will use Maven to + download Web Beans automatically. + </para> + + <programlisting>$ cd webbeans-$VERSION/jboss-as +$ ant update</programlisting> + + <para> + Now, you're ready to deploy your first example! + </para> + + <tip> + <para> + The build scripts for the examples offer a number of targets, these + are: + </para> + <itemizedlist> + <listitem> + <para> + <literal>ant restart</literal> - deploy the example in exploded + format + </para> + </listitem> + <listitem> + <para> + <literal>ant explode</literal> - update an exploded example, without + restarting the deployment + </para> + </listitem> + <listitem> + <para> + <literal>ant deploy</literal> - deploy the example in compressed jar format + </para> + </listitem> + <listitem> + <para> + <literal>ant undeploy</literal> - remove the example from the server + </para> + </listitem> + <listitem> + <para> + <literal>ant clean</literal> - clean the example + </para> + </listitem> + </itemizedlist> + </tip> + + <para> + To deploy the numberguess example: + </para> + + <programlisting>$ cd examples/numberguess +ant deploy</programlisting> + + <para> + Start JBoss AS: + </para> + + <programlisting>$ /Application/jboss-5.0.0.GA/bin/run.sh</programlisting> + + <tip> + <para> + If you use Windows, use the <literal>run.bat</literal>script. + </para> + </tip> + + <para> + Wait for the application to deploy, and enjoy hours of fun at + <ulink url="http://localhost:8080/webbeans-numberguess" />! + </para> + + <para> + The Web Beans RI includes a second simple example that will translate your text + into Latin. The numberguess example is a war example, and uses only simple + beans; the translator example is an ear example, and includes enterprise + beans, packaged in an EJB module. To try it out: + </para> + + <programlisting>$ cd examples/translator +ant deploy</programlisting> + + <para> + Wait for the application to deploy, and visit + <ulink url="http://localhost:8080/webbeans-translator" />! + </para> + + <section> + <title>The numberguess example</title> + + <para> + In the numberguess application you get given 10 attempts to guess a + number between 1 and 100. After each attempt, you will be told whether + you are too high, or too low. + </para> + + <para> + The numberguess example is comprised of a number of Web Beans, + configuration files, and Facelet JSF pages, packaged as a war. Let's + start with the configuration files. + </para> + + <para> + All the configuration files for this example are located in + <literal>WEB-INF/</literal>, which is stored in + <literal>WebContent</literal> in the source tree. First, we have + <literal>faces-config.xml</literal>, in which we tell JSF to use + Facelets: + </para> + + <programlisting role="XML"><![CDATA[<?xml version='1.0' encoding='UTF-8'?> +<faces-config version="1.2" + xmlns="http://java.sun.com/xml/ns/javaee" + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" + xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd"> + + <application> + <view-handler>com.sun.facelets.FaceletViewHandler</view-handler> + </application> + +</faces-config>]]></programlisting> + + <para> + There is an empty <literal>web-beans.xml</literal> file, which marks + this application as a Web Beans application. + </para> + + <para> + Finally there is <literal>web.xml</literal>: + </para> + + <programlistingco> + <areaspec> + <area id="faces.servlet" coords="12" /> + <area id="faces.servlet.mapping" coords="18" /> + <area id="faces.default.suffix" coords="23" /> + <area id="session.timeout" coords="28" /> + <area id="webbeans.listener" coords="32" /> + </areaspec> + <programlisting><![CDATA[<?xml version="1.0" encoding="UTF-8"?> + +<web-app version="2.5" + xmlns="http://java.sun.com/xml/ns/javaee" + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" + xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"> + + <display-name>Web Beans Numbergues example</display-name> + + <!-- JSF --> + + <servlet> + <servlet-name>Faces Servlet</servlet-name> + <servlet-class>javax.faces.webapp.FacesServlet</servlet-class> + <load-on-startup>1</load-on-startup> + </servlet> + + <servlet-mapping> + <servlet-name>Faces Servlet</servlet-name> + <url-pattern>*.jsf</url-pattern> + </servlet-mapping> + + <context-param> + <param-name>javax.faces.DEFAULT_SUFFIX</param-name> + <param-value>.xhtml</param-value> + </context-param> + + <session-config> + <session-timeout>10</session-timeout> + </session-config> + +</web-app>]]></programlisting> + <calloutlist> + <callout arearefs="faces.servlet"> + <para> + Enable and load the JSF servlet + </para> + </callout> + <callout arearefs="faces.servlet.mapping"> + <para> + Configure requests to <literal>.jsf</literal> pages to be + handled by JSF + </para> + </callout> + <callout arearefs="faces.default.suffix"> + <para> + Tell JSF that we will be giving our source files (facelets) an + extension of <literal>.jsf</literal> + </para> + </callout> + <callout arearefs="session.timeout"> + <para> + Configure a session timeout of 10 minutes + </para> + </callout> + </calloutlist> + </programlistingco> + + <note> + <para> + Whilst this demo is a JSF demo, you can use the Web Beans RI with + any Servlet based web framework. + </para> + </note> + + <para> + Let's take a look at the Facelet view: + </para> + + <programlistingco> + <areaspec> + <area id="template" coords="8" /> + <area id="messages" coords="12" /> + <area id="instructions" coords="19" /> + <area id="guess" coords="25" /> + <area id="validator" coords="30" /> + <area id="submit" coords="33" /> + </areaspec> + <programlisting><![CDATA[<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" + xmlns:ui="http://java.sun.com/jsf/facelets" + xmlns:h="http://java.sun.com/jsf/html" + xmlns:f="http://java.sun.com/jsf/core" + xmlns:s="http://jboss.com/products/seam/taglib"> + + <ui:composition template="template.xhtml"> + <ui:define name="content"> + <h1>Guess a number...</h1> + <h:form id="NumberGuessMain"> + <div style="color: red"> + <h:messages id="messages" globalOnly="false"/> + <h:outputText id="Higher" value="Higher!" rendered="#{game.number gt game.guess and game.guess ne 0}"/> + <h:outputText id="Lower" value="Lower!" rendered="#{game.number lt game.guess and game.guess ne 0}"/> + </div> + + <div> + I'm thinking of a number between #{game.smallest} and #{game.biggest}. + You have #{game.remainingGuesses} guesses. + </div> + + <div> + Your guess: + <h:inputText id="inputGuess" + value="#{game.guess}" + required="true" + size="3" + disabled="#{game.number eq game.guess}"> + <f:validateLongRange maximum="#{game.biggest}" + minimum="#{game.smallest}"/> + </h:inputText> + <h:commandButton id="GuessButton" + value="Guess" + action="#{game.check}" + disabled="#{game.number eq game.guess}"/> + </div> + <div> + <h:commandButton id="RestartButton" value="Reset" action="#{game.reset}" immediate="true" /> + </div> + </h:form> + </ui:define> + </ui:composition> +</html>]]></programlisting> + <calloutlist> + <callout arearefs="template"> + <para> + Facelets is a templating language for JSF, here we are + wrapping our page in a template which defines the header. + </para> + </callout> + <callout arearefs="messages"> + <para> + There are a number of messages which can be sent to the user, + "Higher!", "Lower!" and "Correct!" + </para> + </callout> + <callout arearefs="instructions"> + <para> + As the user guesses, the range of numbers they can guess gets + smaller - this sentance changes to make sure they know what + range to guess in. + </para> + </callout> + <callout arearefs="guess"> + <para> + This input field is bound to a Web Bean, using the value + expression. + </para> + </callout> + <callout arearefs="validator"> + <para> + A range validator is used to make sure the user doesn't + accidentally input a number outside of the range in which they + can guess - if the validator wasn't here, the user might use + up a guess on an out of range number. + </para> + </callout> + <callout arearefs="submit"> + <para> + And, of course, there must be a way for the user to send their + guess to the server. Here we bind to an action method on the + Web Bean. + </para> + </callout> + </calloutlist> + </programlistingco> + + <para> + The example exists of 4 classes, the first two of which are binding + types. First, there is the <literal>@Random</literal> binding type, + used for injecting a random number: + </para> + + <programlisting role="JAVA"><![CDATA[@Target( { TYPE, METHOD, PARAMETER, FIELD }) +@Retention(RUNTIME) +@Documented +@BindingType +public @interface Random {}]]></programlisting> + + <para> + There is also the <literal>@MaxNumber</literal> binding type, used for + injecting the maximum number that can be injected: + </para> + + <programlisting role="JAVA"><![CDATA[@Target( { TYPE, METHOD, PARAMETER, FIELD }) +@Retention(RUNTIME) +@Documented +@BindingType +public @interface MaxNumber {} +]]></programlisting> + + <para> + The <literal>Generator</literal> class is responsible for creating the + random number, via a producer method. It also exposes the maximum + possible number via a producer method: + </para> + + <programlisting role="JAVA"><![CDATA[@ApplicationScoped +public class Generator { + + private java.util.Random random = new java.util.Random( System.currentTimeMillis() ); + + private int maxNumber = 100; + + java.util.Random getRandom() + { + return random; + } + + @Produces @Random int next() { + return getRandom().nextInt(maxNumber); + } + + @Produces @MaxNumber int getMaxNumber() + { + return maxNumber; + } + +}]]></programlisting> + + <para> + You'll notice that the <literal>Generator</literal> is application + scoped; therefore we don't get a different random each time. + </para> + + <para> + The final Web Bean in the application is the session scoped + <literal>Game</literal>. + </para> + + <para> + You'll note that we've used the <literal>@Named</literal> + annotation, so that we can use the bean through EL in the JSF page. + Finally, we've used constructor injection to initialize the game with + a random number. And of course, we need to tell the player when they've + won, so we give feedback with a <literal>FacesMessage</literal>. + </para> + + <programlisting role="JAVA"><![CDATA[package org.jboss.webbeans.examples.numberguess; + + +import javax.annotation.PostConstruct; +import javax.faces.application.FacesMessage; +import javax.faces.context.FacesContext; +import javax.webbeans.AnnotationLiteral; +import javax.webbeans.Current; +import javax.webbeans.Initializer; +import javax.webbeans.Named; +import javax.webbeans.SessionScoped; +import javax.webbeans.manager.Manager; + +@Named +@SessionScoped +public class Game +{ + private int number; + + private int guess; + private int smallest; + private int biggest; + private int remainingGuesses; + + @Current Manager manager; + + public Game() + { + } + + @Initializer + Game(@MaxNumber int maxNumber) + { + this.biggest = maxNumber; + } + + public int getNumber() + { + return number; + } + + public int getGuess() + { + return guess; + } + + public void setGuess(int guess) + { + this.guess = guess; + } + + public int getSmallest() + { + return smallest; + } + + public int getBiggest() + { + return biggest; + } + + public int getRemainingGuesses() + { + return remainingGuesses; + } + + public String check() + { + if (guess>number) + { + biggest = guess - 1; + } + if (guess<number) + { + smallest = guess + 1; + } + if (guess == number) + { + FacesContext.getCurrentInstance().addMessage(null, new FacesMessage("Correct!")); + } + remainingGuesses--; + return null; + } + + @PostConstruct + public void reset() + { + this.smallest = 0; + this.guess = 0; + this.remainingGuesses = 10; + this.number = manager.getInstanceByType(Integer.class, new AnnotationLiteral<Random>(){}); + } + +}]]></programlisting> + </section> + + <section> + <title>The translator example</title> + + <para> + The translator example will take any sentences you enter, and translate + them to Latin. + </para> + + <para> + The translator example is built as an ear, and contains EJBs. As a result, it's structure is more complex than + the numberguess example. + </para> + + <note> + <para> + EJB 3.1 and Jave EE 6 allow you to package EJBs in a war, which will + make this structure much simpler! + </para> + </note> + + <para> + First, let's take a look at the ear aggregator, which is located in + <literal>webbeans-translator-ear</literal> module. Maven automatically + generates the <literal>application.xml</literal> for us: + </para> + + <programlisting role="XML"><![CDATA[<plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-ear-plugin</artifactId> + <configuration> + <modules> + <webModule> + <groupId>org.jboss.webbeans.examples.translator</groupId> + <artifactId>webbeans-translator-war</artifactId> + <contextRoot>/webbeans-translator</contextRoot> + </webModule> + </modules> + </configuration> +</plugin>]]></programlisting> + + <para> + Here we set the context path, which gives us a nice url + (<ulink url="http://localhost:8080/webbeans-translator">http://localhost:8080/webbeans-translator</ulink>). + </para> + + <tip> + <para> + If you aren't using Maven to generate these files, you would need + <literal>META-INF/application.xml</literal>: + </para> + + <programlisting role="XML"><![CDATA[<?xml version="1.0" encoding="UTF-8"?> +<application xmlns="http://java.sun.com/xml/ns/javaee" + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" + xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd" + version="5"> + <display-name>webbeans-translator-ear</display-name> + <description>Ear Example for the reference implementation of JSR 299: Web Beans</description> + + <module> + <web> + <web-uri>webbeans-translator.war</web-uri> + <context-root>/webbeans-translator</context-root> + </web> + </module> + <module> + <ejb>webbeans-translator.jar</ejb> + </module> +</application>]]></programlisting> + </tip> + + <para> + Next, lets look at the war. Just as in the numberguess example, we have + a <literal>faces-config.xml</literal> (to enable Facelets) and a + <literal>web.xml</literal> (to enable JSF) in + <literal>WebContent/WEB-INF</literal>. + </para> + + <para> + More intersting is the facelet used to translate text. Just as in + the numberguess example we have a template, which surrounds the form + (ommitted here for brevity): + </para> + + <programlisting role="XML"><![CDATA[<h:form id="NumberGuessMain"> + + <table> + <tr align="center" style="font-weight: bold" > + <td> + Your text + </td> + <td> + Translation + </td> + </tr> + <tr> + <td> + <h:inputTextarea id="text" value="#{translator.text}" required="true" rows="5" cols="80" /> + </td> + <td> + <h:outputText value="#{translator.translatedText}" /> + </td> + </tr> + </table> + <div> + <h:commandButton id="button" value="Translate" action="#{translator.translate}"/> + </div> + +</h:form>]]></programlisting> + + <para> + The user can enter some text in the lefthand textarea, and hit the + translate button to see the result to the right. + </para> + + <para> + Finally, let's look at the ejb module, + <literal>webbeans-translator-ejb</literal>. + In <literal>src/main/resources/META-INF</literal> there is just an + empty <literal>web-beans.xml</literal>, used to mark the archive as + containing Web Beans. + </para> + + <para> + We've saved the most interesting bit to last, the code! The project has + two simple beans, <literal>SentenceParser</literal> and + <literal>TextTranslator</literal> and two enterprise beans, + <literal>TranslatorControllerBean</literal> and + <literal>SentenceTranslator</literal>. You should be getting quite + familiar with what a Web Bean looks like by now, so we'll just + highlight the most interesting bits here. + </para> + + <para> + Both <literal>SentenceParser</literal> and + <literal>TextTranslator</literal> are dependent beans, and + <literal>TextTranslator</literal> uses constructor initialization: + </para> + + <programlisting role="JAVA"><![CDATA[public class TextTranslator { + private SentenceParser sentenceParser; + private Translator sentenceTranslator; + + @Initializer + TextTranslator(SentenceParser sentenceParser, Translator sentenceTranslator) + { + this.sentenceParser = sentenceParser; + this.sentenceTranslator = sentenceTranslator;]]></programlisting> + + <para> + <literal>TextTranslator</literal> is a stateless bean (with a local + business interface), where the magic happens - of course, we couldn't + develop a full translator, but we gave it a good go! + </para> + + <para> + Finally, there is UI orientated controller, that collects the text from + the user, and dispatches it to the translator. This is a request + scoped, named, stateful session bean, which injects the translator. + </para> + + <programlisting role="JAVA"><![CDATA[@Stateful +@RequestScoped +@Named("translator") +public class TranslatorControllerBean implements TranslatorController +{ + + @Current TextTranslator translator;]]></programlisting> + + <para> + The bean also has getters and setters for all the fields on the page. + </para> + + <para> + As this is a stateful session bean, we have to have a remove method: + </para> + + <programlisting role="JAVA"><![CDATA[ @Remove + public void remove() + { + + }]]></programlisting> + + <para> + The Web Beans manager will call the remove method for you when the bean + is destroyed; in this case at the end of the request. + </para> + </section> + + <para> + That concludes our short tour of the Web Beans examples. For more on Web + Beans , or to help out, please visit + <ulink url="http://www.seamframework.org/WebBeans/Development">http...;. + </para> + + <para> + We need help in all areas - bug fixing, writing new features, writing + examples and translating this reference guide. + </para> + +</chapter> \ No newline at end of file Deleted: doc/tags/webbeans-reference-guide-1.0.0.BETA1/pom.xml =================================================================== --- doc/trunk/reference/pom.xml 2009-03-09 12:43:54 UTC (rev 1870) +++ doc/tags/webbeans-reference-guide-1.0.0.BETA1/pom.xml 2009-03-09 15:10:55 UTC (rev 1879) @@ -1,307 +0,0 @@ -<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> - - <modelVersion>4.0.0</modelVersion> - - <groupId>org.jboss.webbeans.reference-guide</groupId> - <artifactId>webbeans-reference-guide</artifactId> - <version>1.0.0-SNAPSHOT</version> - <packaging>jdocbook</packaging> - <name>Web Beans Reference Guide</name> - - <pluginRepositories> - <pluginRepository> - <id>repository.jboss.org</id> - <name>JBoss Repository</name> - <url>http://repository.jboss.org/maven2</url> - </pluginRepository> - </pluginRepositories> - <repositories> - <repository> - <id>repository.jboss.org</id> - <name>JBoss Repository</name> - <url>http://repository.jboss.org/maven2</url> - </repository> - </repositories> - - <properties> - <mpjdocbook.version>2.1.1</mpjdocbook.version> - </properties> - - <build> - <defaultGoal>process-classes</defaultGoal> - <plugins> - <plugin> - <groupId>org.jboss.maven.plugins</groupId> - <artifactId>maven-jdocbook-plugin</artifactId> - <version>${mpjdocbook.version}</version> - <extensions>true</extensions> - <dependencies> - <dependency> - <groupId>org.jboss.webbeans</groupId> - <artifactId>webbeans-docbook-xslt</artifactId> - <version>1.1.1.BETA2</version> - <exclusions> - <exclusion> - <groupId>org.eclipse.wst.css</groupId> - <artifactId>core</artifactId> - </exclusion> - <exclusion> - <groupId>org.eclipse.wst.sse</groupId> - <artifactId>core</artifactId> - </exclusion> - </exclusions> - </dependency> - <dependency> - <groupId>org.jboss.seam</groupId> - <artifactId>seam-jdocbook-style</artifactId> - <version>1.1.0.GA</version> - <type>jdocbook-style</type> - </dependency> - <dependency> - <groupId>org.jboss</groupId> - <artifactId>jbossorg-jdocbook-style</artifactId> - <version>1.1.0</version> - <type>jdocbook-style</type> - </dependency> - </dependencies> - <configuration> - <sourceDirectory>${pom.basedir}</sourceDirectory> - <sourceDocumentName>master.xml</sourceDocumentName> - <masterTranslation>en-US</masterTranslation> - <translations> - <translation>it-IT</translation> - <translation>zh-CN</translation> - <translation>zh-TW</translation> - <translation>es-ES</translation> - <translation>ko-KR</translation> - </translations> - <imageResource> - <directory>${pom.basedir}/en-US</directory> - <includes> - <include>images/*.png</include> - </includes> - </imageResource> - <formats> - <format> - <formatName>pdf</formatName> - <stylesheetResource> - classpath:/xslt/org/jboss/webbeans/pdf.xsl - </stylesheetResource> - <finalName>webbeans_reference.pdf</finalName> - </format> - <format> - <formatName>html</formatName> - <stylesheetResource> - classpath:/xslt/org/jboss/webbeans/xhtml.xsl - </stylesheetResource> - <finalName>index.html</finalName> - </format> - <format> - <formatName>html_single</formatName> - <stylesheetResource> - classpath:/xslt/org/jboss/webbeans/xhtml-single.xsl - </stylesheetResource> - <finalName>index.html</finalName> - </format> - </formats> - <options> - <xincludeSupported>true</xincludeSupported> - <xmlTransformerType>saxon</xmlTransformerType> - <!-- needed for uri-resolvers; can be ommitted if using 'current' uri scheme --> - <!-- could also locate the docbook dependency and inspect its version... --> - <docbookVersion>1.72.0</docbookVersion> - <localeSeparator>-</localeSeparator> - </options> - </configuration> - </plugin> - <plugin> - <artifactId>maven-antrun-plugin</artifactId> - <executions> - <execution> - <phase>process-classes</phase> - <configuration> - <tasks> - <copy file="${basedir}/target/docbook/publish/en-US/pdf/webbeans_reference.pdf" todir="${basedir}" /> - </tasks> - </configuration> - <goals> - <goal>run</goal> - </goals> - </execution> - </executions> - </plugin> - <plugin> - <groupId>org.apache.maven.plugins</groupId> - <artifactId>maven-enforcer-plugin</artifactId> - </plugin> - </plugins> - <pluginManagement> - <plugins> - <plugin> - <groupId>org.apache.maven.plugins</groupId> - <artifactId>maven-dependency-plugin</artifactId> - <version>2.0</version> - </plugin> - <plugin> - <groupId>org.jboss.maven.plugins</groupId> - <artifactId>maven-jdocbook-plugin</artifactId> - <version>${mpjdocbook.version}</version> - </plugin> - <plugin> - <groupId>org.apache.maven.plugins</groupId> - <artifactId>maven-jar-plugin</artifactId> - <configuration> - <archive> - <manifest> - <addDefaultImplementationEntries> - true - </addDefaultImplementationEntries> - <addDefaultSpecificationEntries> - true - </addDefaultSpecificationEntries> - </manifest> - </archive> - </configuration> - </plugin> - <plugin> - <groupId>org.apache.maven.plugins</groupId> - <artifactId>maven-surefire-report-plugin</artifactId> - <version>2.4.3</version> - </plugin> - <plugin> - <groupId>org.apache.maven.plugins</groupId> - <artifactId>maven-surefire-plugin</artifactId> - <version>2.4.3</version> - </plugin> - <plugin> - <groupId>org.apache.maven.plugins</groupId> - <artifactId>maven-clean-plugin</artifactId> - <version>2.2</version> - </plugin> - <plugin> - <groupId>org.apache.maven.plugins</groupId> - <artifactId>maven-deploy-plugin</artifactId> - <version>2.4</version> - </plugin> - <plugin> - <groupId>org.apache.maven.plugins</groupId> - <artifactId>maven-install-plugin</artifactId> - <version>2.2</version> - </plugin> - <plugin> - <groupId>org.apache.maven.plugins</groupId> - <artifactId>maven-site-plugin</artifactId> - <version>2.0-beta-6</version> - </plugin> - <plugin> - <groupId>org.apache.maven.plugins</groupId> - <artifactId>maven-source-plugin</artifactId> - <version>2.0.4</version> - </plugin> - <plugin> - <groupId>org.apache.maven.plugins</groupId> - <artifactId>maven-jar-plugin</artifactId> - <version>2.2</version> - </plugin> - <plugin> - <groupId>org.apache.maven.plugins</groupId> - <artifactId>maven-antrun-plugin</artifactId> - <version>1.1</version> - </plugin> - <plugin> - <groupId>org.apache.maven.plugins</groupId> - <artifactId>maven-enforcer-plugin</artifactId> - <version>1.0-alpha-4</version> - <executions> - <execution> - <id>enforce</id> - <goals> - <goal>enforce</goal> - </goals> - <configuration> - <rules> - <requireMavenVersion> - <version>2.0.9</version> - </requireMavenVersion> - <requirePluginVersions> - <unCheckedPlugins> - <unCheckedPlugin>org.apache.maven.plugins:maven-eclipse-plugin</unCheckedPlugin> - </unCheckedPlugins> - </requirePluginVersions> - </rules> - </configuration> - </execution> - </executions> - </plugin> - </plugins> - </pluginManagement> - <extensions> - <extension> - <groupId>org.apache.maven.wagon</groupId> - <artifactId>wagon-webdav</artifactId> - <version>1.0-beta-2</version> - </extension> - </extensions> - </build> - - <profiles> - <profile> - <activation> - <property> - <name>build.translations</name> - </property> - </activation> - <build> - <plugins> - <plugin> - <groupId>org.jboss.maven.plugins</groupId> - <artifactId>maven-jdocbook-plugin</artifactId> - <executions> - <execution> - <phase>process-resources</phase> - <goals> - <goal>translate</goal> - </goals> - </execution> - </executions> - </plugin> - </plugins> - </build> - </profile> - </profiles> - - <ciManagement> - <system>Hudson</system> - <url /> - - </ciManagement> - - <issueManagement> - <system>JIRA</system> - <url>http://jira.jboss.org/browse/WBRI</url> - </issueManagement> - - <inceptionYear>2008</inceptionYear> - - <scm> - - <connection>scm:svn:http://anonsvn.jboss.org/repos/webbeans/doc</con... - <developerConnection>scm:svn:https://svn.jboss.org/repos/webbeans/doc&l... - <url>http://fisheye.jboss.org/browse/WebBeans/doc</url> - </scm> - - <distributionManagement> - <repository> - <!-- Copy the dist to the local checkout of the JBoss maven2 repo ${maven.repository.root} --> - <!-- It is anticipated that ${maven.repository.root} be set in user's settings.xml --> - <!-- todo : replace this with direct svn access once the svnkit providers are available --> - <id>repository.jboss.org</id> - <url>file://${maven.repository.root}</url> - </repository> - <snapshotRepository> - <id>snapshots.jboss.org</id> - <name>JBoss Snapshot Repository</name> - <url>dav:https://snapshots.jboss.org/maven2</url> - </snapshotRepository> - </distributionManagement> -</project> \ No newline at end of file Copied: doc/tags/webbeans-reference-guide-1.0.0.BETA1/pom.xml (from rev 1877, doc/trunk/reference/pom.xml) =================================================================== --- doc/tags/webbeans-reference-guide-1.0.0.BETA1/pom.xml (rev 0) +++ doc/tags/webbeans-reference-guide-1.0.0.BETA1/pom.xml 2009-03-09 15:10:55 UTC (rev 1879) @@ -0,0 +1,321 @@ +<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> + + <modelVersion>4.0.0</modelVersion> + + <groupId>org.jboss.webbeans.reference-guide</groupId> + <artifactId>webbeans-reference-guide</artifactId> + <version>1.0.0-SNAPSHOT</version> + <packaging>jdocbook</packaging> + <name>Web Beans Reference Guide</name> + + <pluginRepositories> + <pluginRepository> + <id>repository.jboss.org</id> + <name>JBoss Repository</name> + <url>http://repository.jboss.org/maven2</url> + </pluginRepository> + </pluginRepositories> + <repositories> + <repository> + <id>repository.jboss.org</id> + <name>JBoss Repository</name> + <url>http://repository.jboss.org/maven2</url> + </repository> + </repositories> + + <properties> + <mpjdocbook.version>2.1.1</mpjdocbook.version> + </properties> + + <build> + <defaultGoal>process-classes</defaultGoal> + <plugins> + <plugin> + <groupId>org.jboss.maven.plugins</groupId> + <artifactId>maven-jdocbook-plugin</artifactId> + <version>${mpjdocbook.version}</version> + <extensions>true</extensions> + <dependencies> + <dependency> + <groupId>org.jboss.webbeans</groupId> + <artifactId>webbeans-docbook-xslt</artifactId> + <version>1.1.1.BETA2</version> + <exclusions> + <exclusion> + <groupId>org.eclipse.wst.css</groupId> + <artifactId>core</artifactId> + </exclusion> + <exclusion> + <groupId>org.eclipse.wst.sse</groupId> + <artifactId>core</artifactId> + </exclusion> + </exclusions> + </dependency> + <dependency> + <groupId>org.jboss.seam</groupId> + <artifactId>seam-jdocbook-style</artifactId> + <version>1.1.0.GA</version> + <type>jdocbook-style</type> + </dependency> + <dependency> + <groupId>org.jboss</groupId> + <artifactId>jbossorg-jdocbook-style</artifactId> + <version>1.1.0</version> + <type>jdocbook-style</type> + </dependency> + </dependencies> + <configuration> + <sourceDirectory>${pom.basedir}</sourceDirectory> + <sourceDocumentName>master.xml</sourceDocumentName> + <masterTranslation>en-US</masterTranslation> + <translations> + <translation>it-IT</translation> + <translation>zh-CN</translation> + <translation>zh-TW</translation> + <translation>es-ES</translation> + <translation>ko-KR</translation> + <translation>de-DE</translation> + <translation>pt-BR</translation> + </translations> + <imageResource> + <directory>${pom.basedir}/en-US</directory> + <includes> + <include>images/*.png</include> + </includes> + </imageResource> + <formats> + <format> + <formatName>pdf</formatName> + <stylesheetResource> + classpath:/xslt/org/jboss/webbeans/pdf.xsl + </stylesheetResource> + <finalName>webbeans_reference.pdf</finalName> + </format> + <format> + <formatName>html</formatName> + <stylesheetResource> + classpath:/xslt/org/jboss/webbeans/xhtml.xsl + </stylesheetResource> + <finalName>index.html</finalName> + </format> + <format> + <formatName>html_single</formatName> + <stylesheetResource> + classpath:/xslt/org/jboss/webbeans/xhtml-single.xsl + </stylesheetResource> + <finalName>index.html</finalName> + </format> + </formats> + <options> + <xincludeSupported>true</xincludeSupported> + <xmlTransformerType>saxon</xmlTransformerType> + <!-- needed for uri-resolvers; can be ommitted if using 'current' uri scheme --> + <!-- could also locate the docbook dependency and inspect its version... --> + <docbookVersion>1.72.0</docbookVersion> + <localeSeparator>-</localeSeparator> + </options> + </configuration> + </plugin> + <plugin> + <artifactId>maven-antrun-plugin</artifactId> + <executions> + <execution> + <phase>process-classes</phase> + <configuration> + <tasks> + <copy file="${basedir}/target/docbook/publish/en-US/pdf/webbeans_reference.pdf" todir="${basedir}" /> + </tasks> + </configuration> + <goals> + <goal>run</goal> + </goals> + </execution> + </executions> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-enforcer-plugin</artifactId> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-release-plugin</artifactId> + <configuration> + <arguments>-Dbuild.translations</arguments> + </configuration> + </plugin> + </plugins> + <pluginManagement> + <plugins> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-dependency-plugin</artifactId> + <version>2.0</version> + </plugin> + <plugin> + <groupId>org.jboss.maven.plugins</groupId> + <artifactId>maven-jdocbook-plugin</artifactId> + <version>${mpjdocbook.version}</version> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-jar-plugin</artifactId> + <configuration> + <archive> + <manifest> + <addDefaultImplementationEntries> + true + </addDefaultImplementationEntries> + <addDefaultSpecificationEntries> + true + </addDefaultSpecificationEntries> + </manifest> + </archive> + </configuration> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-surefire-report-plugin</artifactId> + <version>2.4.3</version> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-surefire-plugin</artifactId> + <version>2.4.3</version> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-clean-plugin</artifactId> + <version>2.2</version> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-deploy-plugin</artifactId> + <version>2.4</version> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-install-plugin</artifactId> + <version>2.2</version> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-site-plugin</artifactId> + <version>2.0-beta-6</version> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-source-plugin</artifactId> + <version>2.0.4</version> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-jar-plugin</artifactId> + <version>2.2</version> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-antrun-plugin</artifactId> + <version>1.1</version> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-release-plugin</artifactId> + <version>2.0-beta-7</version> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-enforcer-plugin</artifactId> + <version>1.0-alpha-4</version> + <executions> + <execution> + <id>enforce</id> + <goals> + <goal>enforce</goal> + </goals> + <configuration> + <rules> + <requireMavenVersion> + <version>2.0.9</version> + </requireMavenVersion> + <requirePluginVersions> + <unCheckedPlugins> + <unCheckedPlugin>org.apache.maven.plugins:maven-eclipse-plugin</unCheckedPlugin> + </unCheckedPlugins> + </requirePluginVersions> + </rules> + </configuration> + </execution> + </executions> + </plugin> + </plugins> + </pluginManagement> + <extensions> + <extension> + <groupId>org.apache.maven.wagon</groupId> + <artifactId>wagon-webdav</artifactId> + <version>1.0-beta-2</version> + </extension> + </extensions> + </build> + + <profiles> + <profile> + <activation> + <property> + <name>build.translations</name> + </property> + </activation> + <build> + <plugins> + <plugin> + <groupId>org.jboss.maven.plugins</groupId> + <artifactId>maven-jdocbook-plugin</artifactId> + <executions> + <execution> + <phase>process-resources</phase> + <goals> + <goal>translate</goal> + </goals> + </execution> + </executions> + </plugin> + </plugins> + </build> + </profile> + </profiles> + + <ciManagement> + <system>Hudson</system> + <url /> + + </ciManagement> + + <issueManagement> + <system>JIRA</system> + <url>http://jira.jboss.org/browse/WBRI</url> + </issueManagement> + + <inceptionYear>2008</inceptionYear> + + <scm> + + <connection>scm:svn:http://anonsvn.jboss.org/repos/webbeans/doc</con... + <developerConnection>scm:svn:https://svn.jboss.org/repos/webbeans/doc&l... + <url>http://fisheye.jboss.org/browse/WebBeans/doc</url> + </scm> + + <distributionManagement> + <repository> + <!-- Copy the dist to the local checkout of the JBoss maven2 repo ${maven.repository.root} --> + <!-- It is anticipated that ${maven.repository.root} be set in user's settings.xml --> + <!-- todo : replace this with direct svn access once the svnkit providers are available --> + <id>repository.jboss.org</id> + <url>file://${maven.repository.root}</url> + </repository> + <snapshotRepository> + <id>snapshots.jboss.org</id> + <name>JBoss Snapshot Repository</name> + <url>dav:https://snapshots.jboss.org/maven2</url> + </snapshotRepository> + </distributionManagement> +</project> \ No newline at end of file