Seam SVN: r11607 - branches/community/Seam_2_2/src/test/ftest/seamgen.
by seam-commits＠lists.jboss.org
Author: kpiwko(a)redhat.com
Date: 2009-10-21 06:12:32 -0400 (Wed, 21 Oct 2009)
New Revision: 11607
Modified:
branches/community/Seam_2_2/src/test/ftest/seamgen/build.xml
Log:
Repaired invocation of icefaces deployed testsuite
Modified: branches/community/Seam_2_2/src/test/ftest/seamgen/build.xml
===================================================================
--- branches/community/Seam_2_2/src/test/ftest/seamgen/build.xml 2009-10-20 06:59:52 UTC (rev 11606)
+++ branches/community/Seam_2_2/src/test/ftest/seamgen/build.xml 2009-10-21 10:12:32 UTC (rev 11607)
@@ -113,7 +113,7 @@
<run.selenium.test suite="icefaces-exploded" />
</target>
<target name="seam-gen.icefaces.testsuite.deployed" depends="build">
- <run.selenium.test suite="icefaces-deploy" />
+ <run.selenium.test suite="icefaces-deployed" />
</target>
<target name="seam-gen.smoke.testsuite" depends="build" description="Run smoke testsuite">
15 years, 1 month
- 1
- 0
Seam SVN: r11606 - in branches/enterprise/JBPAPP_5_0/src/test/ftest: seamgen and 2 other directories.
by seam-commits＠lists.jboss.org
Author: oskutka(a)redhat.com
Date: 2009-10-20 02:59:52 -0400 (Tue, 20 Oct 2009)
New Revision: 11606
Modified:
branches/enterprise/JBPAPP_5_0/src/test/ftest/ftest.properties
branches/enterprise/JBPAPP_5_0/src/test/ftest/seamgen/build.xml
branches/enterprise/JBPAPP_5_0/src/test/ftest/seamgen/src/main/org/jboss/seam/test/functional/seamgen/SeamGenTest.java
branches/enterprise/JBPAPP_5_0/src/test/ftest/seamgen/src/main/org/jboss/seam/test/functional/seamgen/utils/SeamGenAdapter.java
Log:
Backporting JBSEAM-4445
Modified: branches/enterprise/JBPAPP_5_0/src/test/ftest/ftest.properties
===================================================================
--- branches/enterprise/JBPAPP_5_0/src/test/ftest/ftest.properties 2009-10-18 20:47:42 UTC (rev 11605)
+++ branches/enterprise/JBPAPP_5_0/src/test/ftest/ftest.properties 2009-10-20 06:59:52 UTC (rev 11606)
@@ -85,3 +85,4 @@
test.package=com.example.test
richfaces.skin=classic
jboss.domain=default
+# ant.exec=/usr/bin/ant
Modified: branches/enterprise/JBPAPP_5_0/src/test/ftest/seamgen/build.xml
===================================================================
--- branches/enterprise/JBPAPP_5_0/src/test/ftest/seamgen/build.xml 2009-10-18 20:47:42 UTC (rev 11605)
+++ branches/enterprise/JBPAPP_5_0/src/test/ftest/seamgen/build.xml 2009-10-20 06:59:52 UTC (rev 11606)
@@ -46,7 +46,6 @@
<path id="classpath.build">
<fileset dir="${root.lib.dir}">
<include name="testng-jdk15.jar"/>
- <include name="gen/ant.jar"/>
</fileset>
<fileset dir="${ftest.lib.dir}" includes="**/*.jar" />
</path>
@@ -93,8 +92,10 @@
</target>
<target name="seam-gen.richfaces.testsuite" description="Run Richfaces testsuite">
- <antcall target="seam-gen.richfaces.testsuite.exploded" />
- <antcall target="seam-gen.richfaces.testsuite.deployed" />
+ <antcall target="seam-gen.richfaces.testsuite.exploded.war" />
+ <antcall target="seam-gen.richfaces.testsuite.exploded.ear" />
+ <antcall target="seam-gen.richfaces.testsuite.deployed.war" />
+ <antcall target="seam-gen.richfaces.testsuite.deployed.ear" />
</target>
<target name="seam-gen.richfaces.testsuite.exploded.ear" depends="build">
Modified: branches/enterprise/JBPAPP_5_0/src/test/ftest/seamgen/src/main/org/jboss/seam/test/functional/seamgen/SeamGenTest.java
===================================================================
--- branches/enterprise/JBPAPP_5_0/src/test/ftest/seamgen/src/main/org/jboss/seam/test/functional/seamgen/SeamGenTest.java 2009-10-18 20:47:42 UTC (rev 11605)
+++ branches/enterprise/JBPAPP_5_0/src/test/ftest/seamgen/src/main/org/jboss/seam/test/functional/seamgen/SeamGenTest.java 2009-10-20 06:59:52 UTC (rev 11606)
@@ -54,6 +54,7 @@
protected static String SEAMGEN_BUILDFILE;
protected static String SEAMGEN_PROPERTIES_FILE;
protected static String WORKSPACE;
+ protected static String ANT_EXECUTABLE;
// container specific properties
protected static String CONTAINER;
@@ -128,7 +129,7 @@
setSeamGenProperties();
- seamGen = new SeamGenAdapter(SEAMGEN_BUILDFILE);
+ seamGen = new SeamGenAdapter(ANT_EXECUTABLE, SEAMGEN_BUILDFILE);
seamGen.setExplode(explode);
}
@@ -152,6 +153,7 @@
ftestProperties.load(new FileInputStream(SEAM_FTEST_PROPERTIES_FILE));
WORKSPACE = ftestProperties.getProperty("workspace.home");
+ ANT_EXECUTABLE = ftestProperties.getProperty("ant.exec", "ant");
// container specific
CONTAINER = ftestProperties.getProperty("container", "jboss5");
Modified: branches/enterprise/JBPAPP_5_0/src/test/ftest/seamgen/src/main/org/jboss/seam/test/functional/seamgen/utils/SeamGenAdapter.java
===================================================================
--- branches/enterprise/JBPAPP_5_0/src/test/ftest/seamgen/src/main/org/jboss/seam/test/functional/seamgen/utils/SeamGenAdapter.java 2009-10-18 20:47:42 UTC (rev 11605)
+++ branches/enterprise/JBPAPP_5_0/src/test/ftest/seamgen/src/main/org/jboss/seam/test/functional/seamgen/utils/SeamGenAdapter.java 2009-10-20 06:59:52 UTC (rev 11606)
@@ -21,15 +21,13 @@
*/
package org.jboss.seam.test.functional.seamgen.utils;
-import java.io.File;
+import java.io.BufferedReader;
+import java.io.InputStream;
+import java.io.InputStreamReader;
+import java.io.OutputStream;
import java.io.PrintStream;
-import org.apache.tools.ant.BuildException;
-import org.apache.tools.ant.DefaultLogger;
-import org.apache.tools.ant.Project;
-import org.apache.tools.ant.ProjectHelper;
-import org.apache.tools.ant.input.InputHandler;
-import org.apache.tools.ant.input.InputRequest;
+import org.jboss.seam.test.functional.seamgen.SeamGenTest;
/**
* This class wraps seam-gen ant script in order to be easily usable from Java.
@@ -43,60 +41,84 @@
public class SeamGenAdapter
{
- private String buildfile;
- private DefaultLogger log;
- private boolean explode = true;
+ protected String buildfile;
+ protected boolean explode = true;
+ protected PrintStream out, err;
+ protected String antExecutable;
- public SeamGenAdapter(String buildfile)
+ public SeamGenAdapter(String antExecutable, String buildfile)
{
- this(buildfile, System.out, System.err);
+ this(antExecutable, buildfile, System.out, System.err);
}
- public SeamGenAdapter(String buildfile, PrintStream out, PrintStream err)
+ public SeamGenAdapter(String antExecutable, String buildfile, PrintStream out, PrintStream err)
{
+ this.antExecutable = antExecutable;
this.buildfile = buildfile;
- log = new DefaultLogger();
- log.setOutputPrintStream(out);
- log.setErrorPrintStream(err);
- log.setMessageOutputLevel(Project.MSG_INFO);
+ this.err = err;
+ this.out = out;
}
- public Project getAntCall()
+ private String getAntCommand(String task)
{
- Project ant = new Project();
- ant.init();
- ProjectHelper.configureProject(ant, new File(buildfile));
- ant.addBuildListener(log);
- return ant;
+ return antExecutable + " -f " + buildfile + " " + task;
}
+ protected void executeAntTarget(String task)
+ {
+ executeAntTarget(task, null);
+ }
+
+ protected void executeAntTarget(String task, String[] properties)
+ {
+ try
+ {
+ OutputStreamFeeder feeder = null;
+ String antCommand = getAntCommand(task);
+ out.print(antCommand);
+ Process process = Runtime.getRuntime().exec((antCommand));
+ if (properties != null && properties.length > 0)
+ {
+ feeder = new OutputStreamFeeder(process.getOutputStream(), out, properties);
+ feeder.start();
+ }
+ // Associate the stdout InputStreamEater with the properties feeder to
+ // have the feeder type in a line from the properties whenever the eater
+ // encounters an input challenge.
+ (new InputStreamEater(process.getInputStream(), out, feeder)).start();
+ (new InputStreamEater(process.getErrorStream(), err, null)).start();
+ process.waitFor();
+ }
+ catch (Exception e)
+ {
+ e.printStackTrace();
+ throw new RuntimeException(e.toString());
+ }
+ }
+
public void createProject()
{
- getAntCall().executeTarget("create-project");
+ executeAntTarget("create-project");
}
public void deleteProject()
{
- getAntCall().executeTarget("delete-project");
+ executeAntTarget("delete-project");
}
public void newAction(String[] properties)
{
- Project project = getAntCall();
- project.setInputHandler(getInputHandler(properties));
- project.executeTarget("new-action");
+ executeAntTarget("new-action", properties);
}
public void newForm(String[] properties)
{
- Project project = getAntCall();
- project.setInputHandler(getInputHandler(properties));
- project.executeTarget("new-form");
+ executeAntTarget("new-form", properties);
}
public void generateEntities()
{
- getAntCall().executeTarget("generate");
+ executeAntTarget("generate");
}
/**
@@ -107,11 +129,11 @@
{
if (explode)
{
- getAntCall().executeTarget("explode");
+ executeAntTarget("explode");
}
else
{
- getAntCall().executeTarget("deploy");
+ executeAntTarget("deploy");
}
}
@@ -123,11 +145,11 @@
{
if (explode)
{
- getAntCall().executeTarget("unexplode");
+ executeAntTarget("unexplode");
}
else
{
- getAntCall().executeTarget("undeploy");
+ executeAntTarget("undeploy");
}
}
@@ -135,7 +157,7 @@
{
if (explode)
{
- getAntCall().executeTarget("explode");
+ executeAntTarget("explode");
}
else
{
@@ -145,48 +167,14 @@
public void restart()
{
- getAntCall().executeTarget("restart");
+ executeAntTarget("restart");
}
public void addIdentityManagement()
{
- getAntCall().executeTarget("add-identity-management");
+ executeAntTarget("add-identity-management");
}
- private InputHandler getInputHandler(final String[] properties)
- {
- return new InputHandler()
- {
- public void handleInput(InputRequest request) throws BuildException
- {
- if (request.getPrompt().contains("Enter the Seam component name"))
- {
- request.setInput(properties[0]);
- }
- else if (request.getPrompt().contains("Enter the local interface name"))
- {
- request.setInput(properties[1]);
- }
- else if (request.getPrompt().contains("Enter the bean class name"))
- {
- request.setInput(properties[2]);
- }
- else if (request.getPrompt().contains("Enter the action method name"))
- {
- request.setInput(properties[3]);
- }
- else if (request.getPrompt().contains("Enter the page name"))
- {
- request.setInput(properties[4]);
- }
- else
- {
- throw new RuntimeException("Unexpected prompt " + request.getPrompt());
- }
- }
- };
- }
-
public boolean isExplode()
{
return explode;
@@ -201,4 +189,95 @@
this.explode = explode;
}
+ /**
+ * EatInputStreamData class is used for handling InputStream (stdout, stderr)
+ * of an ant sub-process. When it encounters an input challenge, it notifies
+ * the associated {@link OutputStreamFeeder} to provide the input.
+ *
+ */
+ class InputStreamEater extends Thread
+ {
+ private static final String INPUT_CHALLENGE = "[input]";
+ private BufferedReader stream;
+ private OutputStreamFeeder feederToNotify;
+ private PrintStream out;
+
+ public InputStreamEater(InputStream stream, PrintStream out, OutputStreamFeeder feederToNotify)
+ {
+ this.stream = new BufferedReader(new InputStreamReader(stream));
+ this.out = out;
+ this.feederToNotify = feederToNotify;
+ setDaemon(true);
+ }
+
+ @Override
+ public void run()
+ {
+ try
+ {
+ String line;
+ while ((line = stream.readLine()) != null)
+ {
+ out.println(line);
+ if (feederToNotify != null && line.contains(INPUT_CHALLENGE))
+ {
+ // notify OutputStreamFeeder to send an input
+ feederToNotify.feed();
+ }
+ }
+ }
+ catch (Exception e)
+ {
+ e.printStackTrace();
+ }
+ }
+
+ }
+
+ /**
+ * OutputStreamFeeder class is used for feeding OutputStream (stdin) of an
+ * ant sub-process with appropriate inputs. It waits for a notification from
+ * the associated {@link InputStreamEater} object.
+ *
+ */
+ class OutputStreamFeeder extends Thread
+ {
+
+ PrintStream stream, out;
+ String[] food;
+
+ public OutputStreamFeeder(OutputStream stream, PrintStream out, String[] food)
+ {
+ this.stream = new PrintStream(stream);
+ this.food = food;
+ this.out = out;
+ setDaemon(true);
+ }
+
+ @Override
+ public synchronized void run()
+ {
+ try
+ {
+ for (int i = 0; i < food.length; i++)
+ {
+ // wait for a notification from EatInputStreamData
+ wait();
+ stream.println(food[i]);
+ stream.flush();
+ out.println("Typed: " + food[i]);
+ }
+ }
+ catch (Exception e)
+ {
+ e.printStackTrace();
+ }
+ }
+
+ public synchronized void feed()
+ {
+ this.notify();
+ }
+
+ }
}
15 years, 1 month
- 1
- 0
Seam SVN: r11605 - branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR.
by seam-commits＠lists.jboss.org
Author: essaidetest
Date: 2009-10-18 16:47:42 -0400 (Sun, 18 Oct 2009)
New Revision: 11605
Modified:
branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/I18n.po
Log:
Modified: branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/I18n.po
===================================================================
--- branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/I18n.po 2009-10-18 16:47:04 UTC (rev 11604)
+++ branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/I18n.po 2009-10-18 20:47:42 UTC (rev 11605)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-06-25 15:02+0000\n"
-"PO-Revision-Date: 2009-10-18 18:46+0100\n"
+"PO-Revision-Date: 2009-10-18 22:47+0100\n"
"Last-Translator: P.J <essaidetest(a)yahoo.fr>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -95,7 +95,7 @@
#: I18n.xml:73
#, no-c-format
msgid "You can write your translation of labels (<xref linkend=\"labels\"/>) to your messages resource bundle in the native encoding and then convert the content of the file into the escaped format through the tool <literal>native2ascii</literal> provided in the JDK. This tool will convert a file written in your native encoding to one that represents non-ASCII characters as Unicode escape sequences."
-msgstr ""
+msgstr "Vous pouvez écrire votre traductions des labels (<xref linkend=\"labels\"/>) dans vos fichiers de ressource dans l'encodage natif et ensuite la conversation du fichier dans le format déspécialisé avec l'outil <literal>native2ascii</literal> fourni dans le JDK. Cet outil va convertir un fichier écrit dans votre encodage natif dans un nouveau où la représentation des caractères non-ASCII sera en séquence déspécialisé Unicode."
#. Tag: para
#: I18n.xml:83
@@ -119,19 +119,19 @@
#: I18n.xml:98
#, no-c-format
msgid "We need to make sure that the view displays your localized data and messages using the correct character set and also any data submitted uses the correct encoding."
-msgstr ""
+msgstr "Soyez sur que les vues affichant vos informations localisées et les message utilisent le bon groupe de caractères et aussi que toute donnée soumise utilise le bon encodage."
#. Tag: para
#: I18n.xml:104
#, no-c-format
msgid "To set the display character encoding, you need to use the <literal><f:view locale=\"cs_CZ\"/></literal> tag (here we tell JSF to use the Czech locale). You may want to change the encoding of the xml document itself if you want to embed localized strings in the xml. To do this alter the encoding attribute in xml declaration <literal><?xml version=\"1.0\" encoding=\"UTF-8\"?></literal> as required."
-msgstr ""
+msgstr "Pour définir l'encodage de caractère à afficher, vous devez utiliser la balise <literal><f:view locale=\"cs_CZ\"/></literal> (ici pour dire à JSF d'utiliser la langue Tchèque). Vous pouvez vouloir modifier l'encodage du document xml lui-même si vous voulez embarqué des chaines de caractères localisées en xml. Pour faire cela, modifiez l'attriut d'encodage dans la déclaration xml <literal><?xml version=\"1.0\" encoding=\"UTF-8\"?></literal> selon le besoin."
#. Tag: para
#: I18n.xml:114
#, no-c-format
msgid "Also JSF/Facelets should submit any requests using the specified character encoding, but to make sure any requests that don't specify an encoding you can force the request encoding using a servlet filter. Configure this in <literal>components.xml</literal>:"
-msgstr ""
+msgstr "De plus JSF/Facelets devrait soumettre toutes les requêtes en utilisant l'encodage de caractères spécifié, mais pour êtrer sur que toutes les requêtes ne vont pas indiquer un encodage vous pouvez obliger l'encodage de la requête en utilisant un filtre servlet. Vous configurez cela dans <literal>components.xml</literal>:"
#. Tag: programlisting
#: I18n.xml:121
@@ -155,19 +155,19 @@
#: I18n.xml:128
#, no-c-format
msgid "Each user login session has an associated instance of <literal>java.util.Locale</literal> (available to the application as a component named <literal>locale</literal>). Under normal circumstances, you won't need to do any special configuration to set the locale. Seam just delegates to JSF to determine the active locale:"
-msgstr ""
+msgstr "Chaque session de connection de l'utilisateur est associé avec une instance de <literal>java.util.Locale</literal> (disponible dans l'application comme un composant appelé <literal>locale</literal>). Dans les circonstances normales, vous n'avez pas besoin de définir la locale. Seam va simplement déléguer à JSF le fait de déterminer la locale active:"
#. Tag: para
#: I18n.xml:136
#, no-c-format
msgid "If there is a locale associated with the HTTP request (the browser locale), and that locale is in the list of supported locales from <literal>faces-config.xml</literal>, use that locale for the rest of the session."
-msgstr ""
+msgstr "S'il ya une langague associée avec la requête HTTP (la langue du navigateur), et que la langue est dans la liste des langues supportées dans le <literal>faces-config.xml</literal>, utilisez cette langue pour le reste de la session."
#. Tag: para
#: I18n.xml:143
#, no-c-format
msgid "Otherwise, if a default locale was specified in the <literal>faces-config.xml</literal>, use that locale for the rest of the session."
-msgstr ""
+msgstr "Cependant, si la langue a été spécifiée dans le <literal>faces-config.xml</literal>, alors utilise cette langue pour le reste de la session."
#. Tag: para
#: I18n.xml:149
@@ -179,13 +179,13 @@
#: I18n.xml:153
#, no-c-format
msgid "It is <emphasis>possible</emphasis> to set the locale manually via the Seam configuration properties <literal> org.jboss.seam.international.localeSelector.language</literal>, <literal> org.jboss.seam.international.localeSelector.country</literal> and <literal> org.jboss.seam.international.localeSelector.variant</literal>, but we can't think of any good reason to ever do this."
-msgstr ""
+msgstr "C'est <emphasis>possible</emphasis> de définir la langue manuellement via les propriétés de configuration de Seam <literal> org.jboss.seam.international.localeSelector.language</literal>, <literal> org.jboss.seam.international.localeSelector.country</literal> et <literal> org.jboss.seam.international.localeSelector.variant</literal>, mais nous n'avons pas trouver de bonne raison d'avoir à faire cela."
#. Tag: para
#: I18n.xml:160
#, no-c-format
msgid "It is, however, useful to allow the user to set the locale manually via the application user interface. Seam provides built-in functionality for overriding the locale determined by the algorithm above. All you have to do is add the following fragment to a form in your JSP or Facelets page:"
-msgstr ""
+msgstr "C'est, cependant, utile de permettre à l'utilisateur de définir sa langue manuellement via un interface utilisateur de l'application. Seam fourni une fonctionnalité livrée pour remplacer la langue déterminée par l'algorithme ci-dessus. Tout ce que vous avez à faire est d'ajouter le fragment suivant dans un formulaire de votre page JSP ou Facelets:"
#. Tag: programlisting
#: I18n.xml:166
@@ -199,12 +199,19 @@
"<h:commandButton action=\"#{localeSelector.select}\"\n"
" value=\"#{messages['ChangeLanguage']}\"/>"
msgstr ""
+"<h:selectOneMenu value=\"#{localeSelector.language}\">\n"
+" <f:selectItem itemLabel=\"English\" itemValue=\"en\"/>\n"
+" <f:selectItem itemLabel=\"Deutsch\" itemValue=\"de\"/>\n"
+" <f:selectItem itemLabel=\"Francais\" itemValue=\"fr\"/>\n"
+"</h:selectOneMenu>\n"
+"<h:commandButton action=\"#{localeSelector.select}\"\n"
+" value=\"#{messages['ChangeLanguage']}\"/>"
#. Tag: para
#: I18n.xml:168
#, no-c-format
msgid "Or, if you want a list of all supported locales from <literal> faces-config.xml</literal>, just use:"
-msgstr ""
+msgstr "Ou si vous voulez une liste de toutes les langues supportées depuis <literal> faces-config.xml</literal>, utilisez simplement :"
#. Tag: programlisting
#: I18n.xml:171
@@ -216,30 +223,35 @@
"<h:commandButton action=\"#{localeSelector.select}\"\n"
" value=\"#{messages['ChangeLanguage']}\"/>"
msgstr ""
+"<h:selectOneMenu value=\"#{localeSelector.localeString}\">\n"
+" <f:selectItems value=\"#{localeSelector.supportedLocales}\"/>\n"
+"</h:selectOneMenu>\n"
+"<h:commandButton action=\"#{localeSelector.select}\"\n"
+" value=\"#{messages['ChangeLanguage']}\"/>"
#. Tag: para
#: I18n.xml:173
#, no-c-format
msgid "When the user selects an item from the drop-down, then clicks the command button, the Seam and JSF locales will be overridden for the rest of the session."
-msgstr ""
+msgstr "Quand l'utilisateur sélectionne un élément depuis cette liste, ensuite il clique sur le bouton de commande, alors les lagues de Seam et de JSF vont être remplacées pour le reste de la session."
#. Tag: para
#: I18n.xml:177
#, no-c-format
msgid "The brings us to the question of where the supported locales are defined. Typically, you provide a list of locales for which you have matching resource bundles in the <literal><locale-config></literal> element of the JSF configuration file (/META-INF/faces-config.xml). However, you have learned to appreciate that Seam's component configuration mechanism is more powerful than what is provided in Java EE. For that reason, you can configure the supported locales, and the default locale of the server, using the built-in component named <literal>org.jboss.seam.international.localeConfig</literal>. To use it, you first declare an XML namespace for Seam's international package in the Seam component descriptor. You then define the default locale and supported locales as follows:"
-msgstr ""
+msgstr "Pour répondre à la question à quel endroit les langues sont-elle définies. Typiquement, vous fournissez une liste de langues pour lesquelles vous avez un fichiers de ressources correspondant dans l'élément <literal><locale-config></literal> de fichier de configuration JSF (/META-INF/faces-config.xml). Cependant, vous avez appris à apprécier le mechanisme de configuration des composants de Seam qui est plus psuissant que celui fourni dans Java EE. Pour cette raison, vous pouvez configurer les langues supportées, et une langue par défaut sur le serveur, en utilisant le composant livré dénommé <literal>org.jboss.seam.international.localeConfig</literal>. Pour l'utiliser, vous déclarer en premier un espace de nommage XML pour le paquet international de Seam dans le descripteur du composant de Seam. Vous définissez ensuite une langue par défaut et les langues supportées comme ci-dessous:"
#. Tag: programlisting
#: I18n.xml:190
#, no-c-format
msgid "<international:locale-config default-locale=\"fr_CA\" supported-locales=\"en fr_CA fr_FR\"/>"
-msgstr ""
+msgstr "<international:locale-config default-locale=\"fr_CA\" supported-locales=\"en fr_CA fr_FR\"/>"
#. Tag: para
#: I18n.xml:192
#, no-c-format
msgid "Naturally, if you pronounce that you support a locale, you better provide a resource bundle to match it! Up next, you'll learn how to define the language-specific labels."
-msgstr ""
+msgstr "Naturellement, si vous déclarrez que vous supporté une langue, vous devriez fournir un fichier de ressource qui lui correspond! Ensuite, vous allez apprendre comment définir des labels spécifiques aux langues."
#. Tag: title
#: I18n.xml:198
@@ -251,7 +263,7 @@
#: I18n.xml:200
#, no-c-format
msgid "JSF supports internationalization of user interface labels and descriptive text via the use of <literal><f:loadBundle /></literal>. You can use this approach in Seam applications. Alternatively, you can take advantage of the Seam <literal> messages</literal> component to display templated labels with embedded EL expressions."
-msgstr ""
+msgstr "JSF permet une internationnalisation des labels des interfaces utilisateurs et des texte descriptif via l'utilisation de <literal><f:loadBundle /></literal>. Vous pouvez utilisez cette approche dans les application Seam. Au alternative, vous pouvez profiter du composant <literal> messages</literal> de Seam pour afficher les labels modèles avec les expressions EL embarquées."
#. Tag: title
#: I18n.xml:207
@@ -263,7 +275,7 @@
#: I18n.xml:209
#, no-c-format
msgid "Seam provides a <literal>java.util.ResourceBundle</literal> (available to the application as a <literal> org.jboss.seam.core.resourceBundle</literal>). You'll need to make your internationalized labels available via this special resource bundle. By default, the resource bundle used by Seam is named <literal>messages</literal> and so you'll need to define your labels in files named <literal> messages.properties</literal>, <literal> messages_en.properties</literal>, <literal> messages_en_AU.properties</literal>, etc. These files usually belong in the <literal>WEB-INF/classes</literal> directory."
-msgstr ""
+msgstr "Seam fourni un<literal>java.util.ResourceBundle</literal> (disponible pour l'application comme un <literal> org.jboss.seam.core.resourceBundle</literal>). Vous allez avoir besoin de rendre les labels à internationnaliser disponible via ce fichier de ressource spécial. Par défaut, le fichier de ressource utilisé par Seam est appelé <literal>messages</literal> et donc vous allez avoir besoin de définir vos labels dans des fichiers appelés <literal> messages.properties</literal>, <literal> messages_en.properties</literal>, <literal> messages_en_AU.properties</literal>, etc. Ces fichiers vont habituellement dans le dossier <literal>WEB-INF/classes</literal>."
#. Tag: para
#: I18n.xml:220
@@ -293,7 +305,7 @@
#: I18n.xml:228
#, no-c-format
msgid "You can select a different name for the resource bundle by setting the Seam configuration property named <literal> org.jboss.seam.core.resourceLoader.bundleNames</literal>. You can even specify a list of resource bundle names to be searched (depth first) for messages."
-msgstr ""
+msgstr "Vous pouvez sélectionner un nom différent pour le fichier de ressource en définissant dans la propriété de configuration de Seam dénommée <literal> org.jboss.seam.core.resourceLoader.bundleNames</literal>. Vous pouvez même spécifie une liste de fichier de ressources à chercher (premier trouvé, premier servi) pour les messages."
#. Tag: programlisting
#: I18n.xml:234
@@ -306,18 +318,24 @@
" </core:bundle-names>\n"
"</core:resource-loader>"
msgstr ""
+"<core:resource-loader>\n"
+" <core:bundle-names>\n"
+" <value>mycompany_messages</value>\n"
+" <value>standard_messages</value> \n"
+" </core:bundle-names>\n"
+"</core:resource-loader>"
#. Tag: para
#: I18n.xml:236
#, no-c-format
msgid "If you want to define a message just for a particular page, you can specify it in a resource bundle with the same name as the JSF view id, with the leading <literal>/</literal> and trailing file extension removed. So we could put our message in <literal> welcome/hello_en.properties</literal> if we only needed to display the message on <literal> /welcome/hello.jsp</literal>."
-msgstr ""
+msgstr "Si vous voulez définir un message juste pour une page particulière, vous pouvez le spécifier dans le fichier de ressource avec le m^me nom que l'identifiant de la vue JSF, avec un <literal>/</literal> devant et en enlevant l'extension du nom de fichier. Ainsi vous pouvez mettre notre message dans <literal> welcome/hello_en.properties</literal> si vous avez seulement besoin d'afficher le message sur <literal> /welcome/hello.jsp</literal>."
#. Tag: para
#: I18n.xml:243
#, no-c-format
msgid "You can even specify an explicit bundle name in <literal> pages.xml</literal>:"
-msgstr ""
+msgstr "Vous pouvez même spécifier un nom de fichier explicite dans <literal> pages.xml</literal>:"
#. Tag: programlisting
#: I18n.xml:246
@@ -329,7 +347,7 @@
#: I18n.xml:248
#, no-c-format
msgid "Then we could use messages defined in <literal> HelloMessages.properties</literal> on <literal> /welcome/hello.jsp</literal>."
-msgstr ""
+msgstr "Ensuite, nous pourions utiliser les messages définie dans <literal> HelloMessages.properties</literal> avec <literal> /welcome/hello.jsp</literal>."
#. Tag: title
#: I18n.xml:254
@@ -341,7 +359,7 @@
#: I18n.xml:256
#, no-c-format
msgid "If you define your labels using the Seam resource bundle, you'll be able to use them without having to type <literal> <f:loadBundle ... /></literal> on every page. Instead, you can simply type:"
-msgstr ""
+msgstr "Si vous définissez vos labels en utilisant le fichier de ressource de Seam, vous allez être capable de les utiliser sans avoir à indiquer <literal> <f:loadBundle ... /></literal> sur chaque page. Au lieu de cela, vous pouvez simplement indiquer:"
#. Tag: programlisting
#: I18n.xml:260
@@ -365,7 +383,7 @@
#: I18n.xml:266
#, no-c-format
msgid "Even better, the messages themselves may contain EL expressions:"
-msgstr ""
+msgstr "Même mieux, les mesages eux-même peuvent contenir des expressions EL:"
#. Tag: programlisting
#: I18n.xml:269
@@ -407,7 +425,7 @@
#: I18n.xml:283
#, no-c-format
msgid "The <literal>facesMessages</literal> component is a super-convenient way to display success or failure messages to the user. The functionality we just described also works for faces messages:"
-msgstr ""
+msgstr "Le composant <literal>facesMessages</literal> est une façon super-simplifiée d'afficher un message de réussite ou d'echec à l'utilisateur. La fonctionnalité que nous avons juste à l'instant décrit fonctionne aussi avec les messages faces:"
#. Tag: programlisting
#: I18n.xml:288
@@ -449,19 +467,19 @@
#: I18n.xml:299
#, no-c-format
msgid "There is also a session-scoped instance of <literal> java.util.Timezone</literal>, named <literal> org.jboss.seam.international.timezone</literal>, and a Seam component for changing the timezone named <literal> org.jboss.seam.international.timezoneSelector</literal>. By default, the timezone is the default timezone of the server. Unfortunately, the JSF specification says that all dates and times should be assumed to be UTC, and displayed as UTC, unless a timezone is explicitly specified using <literal> <f:convertDateTime></literal>. This is an extremely inconvenient default behavior."
-msgstr ""
+msgstr "Il y aussi une instance d'étendue de session dénommé <literal> java.util.Timezone</literal>, dénommée <literal> org.jboss.seam.international.timezone</literal>, et un composant de Seam pour la modificaiton du fuseau horaire dénommé <literal> org.jboss.seam.international.timezoneSelector</literal>. Par défaut, le fuseau horaire est le fuseau horaire par défaut du serveur. Malheureusement, la spécification JSF indique que toute les dates et les heures devraient être en UTC, et affichées en UTC, à moins que le fuseau horaire ne soit spécifié en utilisant <literal> <f:convertDateTime></literal>. Ceci est un inconvénient majeur pour une fonctionnalité par défaut."
#. Tag: para
#: I18n.xml:310
#, no-c-format
msgid "Seam overrides this behavior, and defaults all dates and times to the Seam timezone. In addition, Seam provides the <literal> <s:convertDateTime></literal> tag which always performs conversions in the Seam timezone."
-msgstr ""
+msgstr "Seam remplace cette fonctionnalité et par défaut, toutes les dates et les heures sont du fuseau horaire de Seam. De plus, Seam fourni une balise <literal> <s:convertDateTime></literal> qui réalise toujours une conversation dans le fuseau horaire de Seam."
#. Tag: para
#: I18n.xml:315
#, no-c-format
msgid "Seam also provides a default date converter to convert a string value to a date. This saves you from having to specify a converter on input fields that are simply capturing a date. The pattern is selected according the the user's locale and the time zone is selected as described above."
-msgstr ""
+msgstr "Seam fourni aussi un convertisseur de date par défaut convertissant une valeur de chaine de caractères vers une date. Ceci vous préserve d'avoir à indiquer un convertisseur pour les champs de saisies qui sont simplement capturé comme des dates. Le patron est sélectionné en accord avec la langue de l'utilisateur et son fuseau horaire est sélectionné comme décrit ci-dessous."
#. Tag: title
#: I18n.xml:322
@@ -473,7 +491,7 @@
#: I18n.xml:324
#, no-c-format
msgid "Seam applications are also very easily skinnable. The theme API is very similar to the localization API, but of course these two concerns are orthogonal, and some applications support both localization and themes."
-msgstr ""
+msgstr "Les applications de Seam sont aussi très facilement personnalisable. L'API des thèmes est vraiment similaire à l'API de localisation, mais bien sur ces deux concernes de sujets orthogonaux et quelques application ont à la fois la localisation et les thèmes."
#. Tag: para
#: I18n.xml:329
@@ -493,6 +511,13 @@
" </theme:available-themes>\n"
"</theme:theme-selector>"
msgstr ""
+"<theme:theme-selector cookie-enabled=\"true\">\n"
+" <theme:available-themes>\n"
+" <value>default</value>\n"
+" <value>accessible</value>\n"
+" <value>printable</value>\n"
+" </theme:available-themes>\n"
+"</theme:theme-selector>"
#. Tag: para
#: I18n.xml:333
@@ -504,7 +529,7 @@
#: I18n.xml:335
#, no-c-format
msgid "Themes are defined in a properties file with the same name as the theme. For example, the <literal>default</literal> theme is defined as a set of entries in <literal> default.properties</literal>. For example, <literal> default.properties</literal> might define:"
-msgstr ""
+msgstr "Les thèmes sont définies dans un fichier de propriétés avec le même nom que le thème. par exemple, le thème <literal>default</literal> est définie comme un groupe d'entréees dans <literal> default.properties</literal>. Par exemple, <literal> default.properties</literal> devrait définir:"
#. Tag: programlisting
#: I18n.xml:340
@@ -520,13 +545,13 @@
#: I18n.xml:342
#, no-c-format
msgid "Usually the entries in a theme resource bundle will be paths to CSS styles or images and names of facelets templates (unlike localization resource bundles which are usually text)."
-msgstr ""
+msgstr "Habituellement, un fichier de ressource de thème aura des chemins vers des fichiers de styles CSS ou des images ou des noms de pattron de facelets (à la différence des fichiers de resource de la localisation qui sont habituellement des fichiers textes)."
#. Tag: para
#: I18n.xml:346
#, no-c-format
msgid "Now we can use these entries in our JSP or facelets pages. For example, to theme the stylesheet in a facelets page:"
-msgstr ""
+msgstr "Maintenant, nous pouvons utiliser ces entrées dans nos pages JSP ou facelets. par exemple, pour personnaliser la feuille de style dans une page facelets:"
#. Tag: programlisting
#: I18n.xml:349
@@ -538,7 +563,7 @@
#: I18n.xml:351
#, no-c-format
msgid "Or, when the page definition resides in a subdirectory:"
-msgstr ""
+msgstr "Ou, quand la définition de la page réside dans un sous-dossier:"
#. Tag: programlisting
#: I18n.xml:353
@@ -554,7 +579,7 @@
#: I18n.xml:355
#, no-c-format
msgid "Most powerfully, facelets lets us theme the template used by a <literal><ui:composition></literal>:"
-msgstr ""
+msgstr "Plus impressionnant, les facelets nous permette de personnaisée le pattron utilisé avec un <literal><ui:composition></literal>:"
#. Tag: programlisting
#: I18n.xml:358
@@ -576,7 +601,7 @@
#: I18n.xml:360
#, no-c-format
msgid "Just like the locale selector, there is a built-in theme selector to allow the user to freely switch themes:"
-msgstr ""
+msgstr "Toute comme le sélectioneur de langue, il y a un sélectionneur de thème livré qui permet à l'utilisateur de librement basculer entre les thèmes:"
#. Tag: programlisting
#: I18n.xml:363
@@ -596,13 +621,13 @@
#: I18n.xml:367
#, no-c-format
msgid "Persisting locale and theme preferences via cookies"
-msgstr ""
+msgstr "La préservation des préférences de langue et de thème via des cookies"
#. Tag: para
#: I18n.xml:369
#, no-c-format
msgid "The locale selector, theme selector and timezone selector all support persistence of locale and theme preference to a cookie. Simply set the <literal>cookie-enabled</literal> property in <literal>components.xml</literal>:"
-msgstr ""
+msgstr "Le sélectionneur de langue, le sélectionneur de thème et le sélectionneur de fuseau horaire supportent tous la persistance de la rpéférence vers un cookie. En simplement définissant la propriété <literal>cookie-enabled</literal> dans <literal>components.xml</literal>:"
#. Tag: programlisting
#: I18n.xml:374
15 years, 1 month
- 1
- 0
Seam SVN: r11604 - branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR.
by seam-commits＠lists.jboss.org
Author: essaidetest
Date: 2009-10-18 12:47:04 -0400 (Sun, 18 Oct 2009)
New Revision: 11604
Modified:
branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Hsearch.po
branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/I18n.po
Log:
Modified: branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Hsearch.po
===================================================================
--- branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Hsearch.po 2009-10-18 09:24:03 UTC (rev 11603)
+++ branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Hsearch.po 2009-10-18 16:47:04 UTC (rev 11604)
@@ -6,8 +6,8 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-06-11 18:45+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2009-10-18 18:46+0100\n"
+"Last-Translator: P.J <essaidetest(a)yahoo.fr>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -17,69 +17,49 @@
#: Hsearch.xml:5
#, no-c-format
msgid "Hibernate Search"
-msgstr ""
+msgstr "Hibernate Search"
#. Tag: title
#: Hsearch.xml:8
#, no-c-format
msgid "Introduction"
-msgstr ""
+msgstr "Introduction"
#. Tag: para
#: Hsearch.xml:10
#, no-c-format
-msgid ""
-"Full text search engines like Apache Lucene™ are a very powerful technology "
-"that bring full text and efficient queries to applications. Hibernate "
-"Search, which uses Apache Lucene under the covers, indexes your domain model "
-"with the addition of a few annotations, takes care of the database / index "
-"synchronization and returns regular managed objects that are matched by full "
-"text queries. Keep in mind, thought, that there are mismatches that arise "
-"when dealing with an object domain model over a text index (keeping the "
-"index up to date, mismatch between the index structure and the domain model, "
-"and querying mismatch). But the benefits of speed and efficiency far "
-"outweigh these limitations."
-msgstr ""
+msgid "Full text search engines like Apache Lucene™ are a very powerful technology that bring full text and efficient queries to applications. Hibernate Search, which uses Apache Lucene under the covers, indexes your domain model with the addition of a few annotations, takes care of the database / index synchronization and returns regular managed objects that are matched by full text queries. Keep in mind, thought, that there are mismatches that arise when dealing with an object domain model over a text index (keeping the index up to date, mismatch between the index structure and the domain model, and querying mismatch). But the benefits of speed and efficiency far outweigh these limitations."
+msgstr "Les moteurs de recherches plein texte comme Apache Lucene™ sont une technologie très puissante qui apporte la recherche plain texte et l'efficacité des requêtes dans les applications. Hibernate Search qui utilise Apache Lucene soujacent indexe votre modèle du domaine avec quelques annotations additionnelles, prends garde à la synchronisation base de données / indexes et retourne des objets opérationnels qui correspondent aux requêtes de recherche plain texte. Gardez à l'esprit qu'il peut avoir des erreurs qui apparaisssent avec un modèle de domaine objet par dessus un index de textes (conserver l'index à jours, erreur entre la structure de l'index et le modèle du domaine, et erreurs dans les requêtes). Mais les avantages de la vitesse et de l'efficacité va au delà de ces limitations."
#. Tag: para
#: Hsearch.xml:21
#, no-c-format
-msgid ""
-"Hibernate Search has been designed to integrate nicely and as naturally as "
-"possible with JPA and Hibernate. As a natural extension, JBoss Seam provides "
-"an Hibernate Search integration."
-msgstr ""
+msgid "Hibernate Search has been designed to integrate nicely and as naturally as possible with JPA and Hibernate. As a natural extension, JBoss Seam provides an Hibernate Search integration."
+msgstr "Hibernate Search a été conçu pour s'intégrer facilement et naturellement que possible avec JPA et Hibernate. Comme une extension naturelle, JBoss Seam fourni une intégration avec Hibernate Search."
#. Tag: para
#: Hsearch.xml:25
#, no-c-format
-msgid ""
-"Please refer to the <ulink url=\"http://www.hibernate.org/hib_docs/search/"
-"reference/en/html_single/\">Hibernate Search documentation</ulink> for "
-"information specific to the Hibernate Search project."
-msgstr ""
+msgid "Please refer to the <ulink url=\"http://www.hibernate.org/hib_docs/search/reference/en/html_single/\">Hibernate Search documentation</ulink> for information specific to the Hibernate Search project."
+msgstr "Merci de vous référer à <ulink url=\"http://www.hibernate.org/hib_docs/search/reference/en/html_single/\">Hibernate Search documentation</ulink> pour plus d'information spécifique sur le projet Hibernate Search."
#. Tag: title
#: Hsearch.xml:33
#, no-c-format
msgid "Configuration"
-msgstr ""
+msgstr "La configuration"
#. Tag: para
#: Hsearch.xml:35
#, no-c-format
-msgid ""
-"Hibernate Search is configured either in the <filename>META-INF/persistence."
-"xml</filename> or <filename>hibernate.cfg.xml</filename> file."
-msgstr ""
+msgid "Hibernate Search is configured either in the <filename>META-INF/persistence.xml</filename> or <filename>hibernate.cfg.xml</filename> file."
+msgstr "Hibernate Search est configuré aussi bien dans le fichier <filename>META-INF/persistence.xml</filename> que dans le fichier <filename>hibernate.cfg.xml</filename>."
#. Tag: para
#: Hsearch.xml:39
#, no-c-format
-msgid ""
-"Hibernate Search configuration has sensible defaults for most configuration "
-"parameters. Here is a minimal persistence unit configuration to get started."
-msgstr ""
+msgid "Hibernate Search configuration has sensible defaults for most configuration parameters. Here is a minimal persistence unit configuration to get started."
+msgstr "La configuration d'Hibernate Search configuration est par défaut judicieuse pour la plus part des paramètre de configuration. Ici n configuration d'une unité de persistance minimale pour démarrer."
#. Tag: programlisting
#: Hsearch.xml:43
@@ -98,15 +78,24 @@
" </properties>\n"
"</persistence-unit>]]>"
msgstr ""
+"<![CDATA[<persistence-unit name=\"sample\">\n"
+" <jta-data-source>java:/DefaultDS</jta-data-source>\n"
+" <properties>\n"
+" [...]\n"
+" <!-- use a file system based index -->\n"
+" <property name=\"hibernate.search.default.directory_provider\" \n"
+" value=\"org.hibernate.search.store.FSDirectoryProvider\"/>\n"
+" <!-- directory where the indexes will be stored -->\n"
+" <property name=\"hibernate.search.default.indexBase\" \n"
+" value=\"/Users/prod/apps/dvdstore/dvdindexes\"/>\n"
+" </properties>\n"
+"</persistence-unit>]]>"
#. Tag: para
#: Hsearch.xml:45
#, no-c-format
-msgid ""
-"If you plan to target Hibernate Annotations or EntityManager 3.2.x (embedded "
-"into JBoss AS 4.2.x and later), you also need to configure the appropriate "
-"event listeners."
-msgstr ""
+msgid "If you plan to target Hibernate Annotations or EntityManager 3.2.x (embedded into JBoss AS 4.2.x and later), you also need to configure the appropriate event listeners."
+msgstr "Si vous plannifier de cibler Hibernate Annotations ou EntityManager 3.2.x (embarqué dans JBoss AS 4.2.x et suppérieur), vous allez avoir besoin de configurer les écouteurs d'évènement appropriés."
#. Tag: programlisting
#: Hsearch.xml:49
@@ -124,97 +113,95 @@
" value=\"/Users/prod/apps/dvdstore/dvdindexes\"/>\n"
"\n"
" <property name=\"hibernate.ejb.event.post-insert\" \n"
-" value=\"org.hibernate.search.event.FullTextIndexEventListener"
-"\"/>\n"
+" value=\"org.hibernate.search.event.FullTextIndexEventListener\"/>\n"
" <property name=\"hibernate.ejb.event.post-update\" \n"
-" value=\"org.hibernate.search.event.FullTextIndexEventListener"
-"\"/>\n"
+" value=\"org.hibernate.search.event.FullTextIndexEventListener\"/>\n"
" <property name=\"hibernate.ejb.event.post-delete\" \n"
-" value=\"org.hibernate.search.event.FullTextIndexEventListener"
-"\"/>\n"
+" value=\"org.hibernate.search.event.FullTextIndexEventListener\"/>\n"
" \n"
" </properties>\n"
"</persistence-unit>]]>"
msgstr ""
+"<![CDATA[<persistence-unit name=\"sample\">\n"
+" <jta-data-source>java:/DefaultDS</jta-data-source>\n"
+" <properties>\n"
+" [...]\n"
+" <!-- use a file system based index -->\n"
+" <property name=\"hibernate.search.default.directory_provider\" \n"
+" value=\"org.hibernate.search.store.FSDirectoryProvider\"/>\n"
+" <!-- directory where the indexes will be stored -->\n"
+" <property name=\"hibernate.search.default.indexBase\" \n"
+" value=\"/Users/prod/apps/dvdstore/dvdindexes\"/>\n"
+"\n"
+" <property name=\"hibernate.ejb.event.post-insert\" \n"
+" value=\"org.hibernate.search.event.FullTextIndexEventListener\"/>\n"
+" <property name=\"hibernate.ejb.event.post-update\" \n"
+" value=\"org.hibernate.search.event.FullTextIndexEventListener\"/>\n"
+" <property name=\"hibernate.ejb.event.post-delete\" \n"
+" value=\"org.hibernate.search.event.FullTextIndexEventListener\"/>\n"
+" \n"
+" </properties>\n"
+"</persistence-unit>]]>"
#. Tag: para
#: Hsearch.xml:52
#, no-c-format
-msgid ""
-"It is not longer necessary the register the event listeners if Hibernate "
-"Annotations or EntityManager 3.3.x are used. When using Hibernate Search 3.1."
-"x more eventlisteners are needed, but these are registered automatically by "
-"Hibernate Annotations; refer to the Hibernate Search reference for "
-"configuring it without EntityManager and Annotations."
-msgstr ""
+msgid "It is not longer necessary the register the event listeners if Hibernate Annotations or EntityManager 3.3.x are used. When using Hibernate Search 3.1.x more eventlisteners are needed, but these are registered automatically by Hibernate Annotations; refer to the Hibernate Search reference for configuring it without EntityManager and Annotations."
+msgstr "Il n'est plus nécéssaire d'enregistrer les écouteurs d'évènements si Hibernate Annotations ou EntityManager 3.3.x sont utilisés. Quand on utilise Hibernate Search 3.1.x quelques écouteurs d'évènements sont nécéssaire, mais ils sont automatiquement enregistrés par Hibernate Annotations; référeez vous au guide d'Hibernate Search pour sa configuration sans EntityManager et les Annotations."
#. Tag: para
#: Hsearch.xml:60
#, no-c-format
-msgid ""
-"In addition to the configuration file, the following jars have to be "
-"deployed:"
-msgstr ""
+msgid "In addition to the configuration file, the following jars have to be deployed:"
+msgstr "En plus du fichier de configuration, les jars suivants doivent être déployés:"
#. Tag: para
#: Hsearch.xml:65
#, no-c-format
msgid "hibernate-search.jar"
-msgstr ""
+msgstr "hibernate-search.jar"
#. Tag: para
#: Hsearch.xml:69
#, no-c-format
msgid "hibernate-commons-annotations.jar"
-msgstr ""
+msgstr "hibernate-commons-annotations.jar"
#. Tag: para
#: Hsearch.xml:73
#, no-c-format
msgid "lucene-core.jar"
-msgstr ""
+msgstr "lucene-core.jar"
#. Tag: para
#: Hsearch.xml:78
#, no-c-format
-msgid ""
-"If you deploy those in a EAR, don't forget to update <filename>application."
-"xml</filename>"
-msgstr ""
+msgid "If you deploy those in a EAR, don't forget to update <filename>application.xml</filename>"
+msgstr "Si vous déployez ceux là dans un EAR, n'oubliez pas de mettre à jours <filename>application.xml</filename>"
#. Tag: title
#: Hsearch.xml:84
#, no-c-format
msgid "Usage"
-msgstr ""
+msgstr "Utilisation"
#. Tag: para
#: Hsearch.xml:86
#, no-c-format
-msgid ""
-"Hibernate Search uses annotations to map entities to a Lucene index, check "
-"the <ulink url=\"http://www.hibernate.org/hib_docs/search/reference/en/"
-"html_single/\">reference documentation</ulink> for more informations."
-msgstr ""
+msgid "Hibernate Search uses annotations to map entities to a Lucene index, check the <ulink url=\"http://www.hibernate.org/hib_docs/search/reference/en/html_single/\">reference documentation</ulink> for more informations."
+msgstr "Hibernate Search utlise les annotations pour faire correspondre les entités à l'index de Lucene, vérifiez <ulink url=\"http://www.hibernate.org/hib_docs/search/reference/en/html_single/\">la documentation de référence </ulink> pour plus d'informations."
#. Tag: para
#: Hsearch.xml:91
#, no-c-format
-msgid ""
-"Hibernate Search is fully integrated with the API and semantic of JPA / "
-"Hibernate. Switching from a HQL or Criteria based query requires just a few "
-"lines of code. The main API the application interacts with is the "
-"<classname>FullTextSession</classname> API (subclass of Hibernate's "
-"<classname>Session</classname>)."
-msgstr ""
+msgid "Hibernate Search is fully integrated with the API and semantic of JPA / Hibernate. Switching from a HQL or Criteria based query requires just a few lines of code. The main API the application interacts with is the <classname>FullTextSession</classname> API (subclass of Hibernate's <classname>Session</classname>)."
+msgstr "Hibernate Search est pleinement intégré avec les API et la sémentique JPA / Hibernate. Le basculement des requêtes HQL ou Criteria nécéssite juste quelques lignes de codes. L'API principale à intéragir avec est l'API <classname>FullTextSession</classname> (sousclasse de <classname>Session</classname> d'Hibernate )."
#. Tag: para
#: Hsearch.xml:97
#, no-c-format
-msgid ""
-"When Hibernate Search is present, JBoss Seam injects a "
-"<classname>FullTextSession</classname>."
-msgstr ""
+msgid "When Hibernate Search is present, JBoss Seam injects a <classname>FullTextSession</classname>."
+msgstr "Quand Hibernate Search est présent, JBoss Seam injecte un <classname>FullTextSession</classname>."
#. Tag: programlisting
#: Hsearch.xml:100
@@ -228,8 +215,7 @@
"\n"
" public void search(String searchString) {\n"
" org.apache.lucene.search.Query luceneQuery = getLuceneQuery();\n"
-" org.hibernate.Query query session.createFullTextQuery(luceneQuery, "
-"Product.class);\n"
+" org.hibernate.Query query session.createFullTextQuery(luceneQuery, Product.class);\n"
" searchResults = query\n"
" .setMaxResults(pageSize + 1)\n"
" .setFirstResult(pageSize * currentPage)\n"
@@ -238,21 +224,34 @@
" [...]\n"
"}]]>"
msgstr ""
+"<![CDATA[@Stateful\n"
+"@Name(\"search\")\n"
+"public class FullTextSearchAction implements FullTextSearch, Serializable {\n"
+"\n"
+" @In FullTextSession session;\n"
+"\n"
+" public void search(String searchString) {\n"
+" org.apache.lucene.search.Query luceneQuery = getLuceneQuery();\n"
+" org.hibernate.Query query session.createFullTextQuery(luceneQuery, Product.class);\n"
+" searchResults = query\n"
+" .setMaxResults(pageSize + 1)\n"
+" .setFirstResult(pageSize * currentPage)\n"
+" .list();\n"
+" }\n"
+" [...]\n"
+"}]]>"
#. Tag: para
#: Hsearch.xml:103
#, no-c-format
-msgid ""
-"<classname>FullTextSession</classname> extends <classname>org.hibernate."
-"Session</classname> so that it can be used as a regular Hibernate Session"
-msgstr ""
+msgid "<classname>FullTextSession</classname> extends <classname>org.hibernate.Session</classname> so that it can be used as a regular Hibernate Session"
+msgstr "<classname>FullTextSession</classname> étend <classname>org.hibernate.Session</classname> ainsi il peut être utilisé avec une Hibernate Session habituelle"
#. Tag: para
#: Hsearch.xml:108
#, no-c-format
-msgid ""
-"If the Java Persistence API is used, a smoother integration is proposed."
-msgstr ""
+msgid "If the Java Persistence API is used, a smoother integration is proposed."
+msgstr "Si l'API de Persistence de Java est utilisée, une intégration en douceur est proposée."
#. Tag: programlisting
#: Hsearch.xml:111
@@ -266,8 +265,7 @@
"\n"
" public void search(String searchString) {\n"
" org.apache.lucene.search.Query luceneQuery = getLuceneQuery();\n"
-" javax.persistence.Query query = em.createFullTextQuery(luceneQuery, "
-"Product.class);\n"
+" javax.persistence.Query query = em.createFullTextQuery(luceneQuery, Product.class);\n"
" searchResults = query\n"
" .setMaxResults(pageSize + 1)\n"
" .setFirstResult(pageSize * currentPage)\n"
@@ -276,30 +274,34 @@
" [...]\n"
"}]]>"
msgstr ""
+"<![CDATA[@Stateful\n"
+"@Name(\"search\")\n"
+"public class FullTextSearchAction implements FullTextSearch, Serializable {\n"
+" \n"
+" @In FullTextEntityManager em;\n"
+"\n"
+" public void search(String searchString) {\n"
+" org.apache.lucene.search.Query luceneQuery = getLuceneQuery();\n"
+" javax.persistence.Query query = em.createFullTextQuery(luceneQuery, Product.class);\n"
+" searchResults = query\n"
+" .setMaxResults(pageSize + 1)\n"
+" .setFirstResult(pageSize * currentPage)\n"
+" .getResultList();\n"
+" }\n"
+" [...]\n"
+"}]]>"
#. Tag: para
#: Hsearch.xml:113
#, no-c-format
-msgid ""
-"When Hibernate Search is present, a <classname>FulltextEntityManager</"
-"classname> is injected. <classname>FullTextEntityManager</classname> extends "
-"<classname>EntityManager</classname> with search specific methods, the same "
-"way <classname>FullTextSession</classname> extends <classname>Session</"
-"classname>."
-msgstr ""
+msgid "When Hibernate Search is present, a <classname>FulltextEntityManager</classname> is injected. <classname>FullTextEntityManager</classname> extends <classname>EntityManager</classname> with search specific methods, the same way <classname>FullTextSession</classname> extends <classname>Session</classname>."
+msgstr "Quand Hibernate Search est présent, un <classname>FulltextEntityManager</classname> est injecté. <classname>FullTextEntityManager</classname> étends <classname>EntityManager</classname> avec des méthodes de recherche spécifique, de la même façon que <classname>FullTextSession</classname> étends <classname>Session</classname>."
#. Tag: para
#: Hsearch.xml:120
#, no-c-format
-msgid ""
-"When an EJB 3.0 Session or Message Driven Bean injection is used (i.e. via "
-"the @PersistenceContext annotation), it is not possible to replace the "
-"<classname>EntityManager</classname> interface by the "
-"<classname>FullTextEntityManager</classname> interface in the declaration "
-"statement. However, the implementation injected will be a "
-"<classname>FullTextEntityManager</classname> implementation: downcasting is "
-"then possible."
-msgstr ""
+msgid "When an EJB 3.0 Session or Message Driven Bean injection is used (i.e. via the @PersistenceContext annotation), it is not possible to replace the <classname>EntityManager</classname> interface by the <classname>FullTextEntityManager</classname> interface in the declaration statement. However, the implementation injected will be a <classname>FullTextEntityManager</classname> implementation: downcasting is then possible."
+msgstr "Quand une Session EJB3.0 ou une injection de Message Driven Bean est utilisé (par exemple via l'annotation @PersistenceContext), il ets possible de remplacer l'interface de <classname>EntityManager</classname> par l'interface de <classname>FullTextEntityManager</classname> dans la partie déclaration. Cependant, l'implémentation injectée sera une implémentation de <classname>FullTextEntityManager</classname>: la conversion est ensuite possible."
#. Tag: programlisting
#: Hsearch.xml:128
@@ -314,8 +316,7 @@
" public void search(String searchString) {\n"
" org.apache.lucene.search.Query luceneQuery = getLuceneQuery();\n"
" FullTextEntityManager ftEm = (FullTextEntityManager) em;\n"
-" javax.persistence.Query query = ftEm.createFullTextQuery(luceneQuery, "
-"Product.class);\n"
+" javax.persistence.Query query = ftEm.createFullTextQuery(luceneQuery, Product.class);\n"
" searchResults = query\n"
" .setMaxResults(pageSize + 1)\n"
" .setFirstResult(pageSize * currentPage)\n"
@@ -324,19 +325,33 @@
" [...]\n"
"}]]>"
msgstr ""
+"<![CDATA[@Stateful\n"
+"@Name(\"search\")\n"
+"public class FullTextSearchAction implements FullTextSearch, Serializable {\n"
+" \n"
+" @PersistenceContext EntityManager em;\n"
+"\n"
+" public void search(String searchString) {\n"
+" org.apache.lucene.search.Query luceneQuery = getLuceneQuery();\n"
+" FullTextEntityManager ftEm = (FullTextEntityManager) em;\n"
+" javax.persistence.Query query = ftEm.createFullTextQuery(luceneQuery, Product.class);\n"
+" searchResults = query\n"
+" .setMaxResults(pageSize + 1)\n"
+" .setFirstResult(pageSize * currentPage)\n"
+" .getResultList();\n"
+" }\n"
+" [...]\n"
+"}]]>"
#. Tag: para
#: Hsearch.xml:133
#, no-c-format
-msgid ""
-"For people accustomed to Hibernate Search out of Seam, note that using "
-"<methodname>Search.getFullTextSession</methodname> is not necessary."
-msgstr ""
+msgid "For people accustomed to Hibernate Search out of Seam, note that using <methodname>Search.getFullTextSession</methodname> is not necessary."
+msgstr "Pour les personnes abituées à Hibernate Search sans Seam, notez que l'utilisation de <methodname>Search.getFullTextSession</methodname> n'est pas nécéssaire."
#. Tag: para
#: Hsearch.xml:138
#, no-c-format
-msgid ""
-"Check the DVDStore or the blog examples of the JBoss Seam distribution for a "
-"concrete use of Hibernate Search."
-msgstr ""
+msgid "Check the DVDStore or the blog examples of the JBoss Seam distribution for a concrete use of Hibernate Search."
+msgstr "Voyez le DVDStore dans les exemples de blog de la distribution de JBoss Seam pour une utilisation concrète de Hibernate Search."
+
Modified: branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/I18n.po
===================================================================
--- branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/I18n.po 2009-10-18 09:24:03 UTC (rev 11603)
+++ branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/I18n.po 2009-10-18 16:47:04 UTC (rev 11604)
@@ -6,8 +6,8 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-06-25 15:02+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2009-10-18 18:46+0100\n"
+"Last-Translator: P.J <essaidetest(a)yahoo.fr>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -17,173 +17,120 @@
#: I18n.xml:5
#, no-c-format
msgid "Internationalization, localization and themes"
-msgstr ""
+msgstr "Internationnalisation, les langues locales et les thèmes"
#. Tag: para
#: I18n.xml:7
#, no-c-format
-msgid ""
-"Seam makes it easy to build internationalized applications. First, let's "
-"walk through all the stages needed to internationalize and localize your "
-"app. Then we'll take a look at the components Seam bundles."
-msgstr ""
+msgid "Seam makes it easy to build internationalized applications. First, let's walk through all the stages needed to internationalize and localize your app. Then we'll take a look at the components Seam bundles."
+msgstr "Seam rend facile la construction d'applications internationnalisées? En premier, regardons toutes les étapes nécéssaires pour internationnaliser et rendre avec une langue locale votre application. Ensuite nous allons regarde les composants livrés dans Seam."
#. Tag: title
#: I18n.xml:14
#, no-c-format
msgid "Internationalizing your app"
-msgstr ""
+msgstr "Internationnalisation de votre application."
#. Tag: para
#: I18n.xml:16
#, no-c-format
-msgid ""
-"A JEE application consists of many components and all of them must be "
-"configured properly for your application to be localized."
-msgstr ""
+msgid "A JEE application consists of many components and all of them must be configured properly for your application to be localized."
+msgstr "Une application JEE consisten en plusieurs composants et tous doivent être configurés de manière appropriés pour que votre application soit traduisible."
#. Tag: para
#: I18n.xml:21
#, no-c-format
-msgid ""
-"Starting at the bottom, the first step is to ensure that your database "
-"server and client is using the correct character encoding for your locale. "
-"Normally you'll want to use UTF-8. How to do this is outside the scope of "
-"this tutorial."
-msgstr ""
+msgid "Starting at the bottom, the first step is to ensure that your database server and client is using the correct character encoding for your locale. Normally you'll want to use UTF-8. How to do this is outside the scope of this tutorial."
+msgstr "En partant du bas, la première étape est de s'assrer que le serveur de base de données et le client utilise le bon encodage de caractères pour votre langue. Normallement, vous devriez vouloir utiliser UTF-8. Comment faire cela est hors de porté de ce tutorial."
#. Tag: title
#: I18n.xml:29
#, no-c-format
msgid "Application server configuration"
-msgstr ""
+msgstr "La configuration du serveur d'application"
#. Tag: para
#: I18n.xml:31
#, no-c-format
-msgid ""
-"To ensure that the application server receives the request parameters in the "
-"correct encoding from client requests you have to configure the tomcat "
-"connector. If you use Tomcat or JBoss AS, add the <literal>URIEncoding=\"UTF-"
-"8\"</literal> attribute to the connector configuration. For JBoss AS 4.2 "
-"change <literal>${JBOSS_HOME}/server/(default)/deploy/jboss-web.deployer/"
-"server.xml</literal>:"
-msgstr ""
+msgid "To ensure that the application server receives the request parameters in the correct encoding from client requests you have to configure the tomcat connector. If you use Tomcat or JBoss AS, add the <literal>URIEncoding=\"UTF-8\"</literal> attribute to the connector configuration. For JBoss AS 4.2 change <literal>${JBOSS_HOME}/server/(default)/deploy/jboss-web.deployer/server.xml</literal>:"
+msgstr "Pour s'assurer que le serveur d'application reçoit les paramètres dans l'encodage correct depuis les requêtes client, vous devez configurer le connecteur de tomcat. Si vous utilisez Tomcat ou JBoss AS, ajoutez l'attribut <literal>URIEncoding=\"UTF-8\"</literal> à la configuration du connecteur. Pour JBoss AS 4.2, modifiez <literal>${JBOSS_HOME}/server/(default)/deploy/jboss-web.deployer/server.xml</literal>:"
#. Tag: programlisting
#: I18n.xml:40
#, no-c-format
msgid "<Connector port=\"8080\" URIEncoding=\"UTF-8\"/>"
-msgstr ""
+msgstr "<Connector port=\"8080\" URIEncoding=\"UTF-8\"/>"
#. Tag: para
#: I18n.xml:42
#, no-c-format
-msgid ""
-"There is alternative which is probably better. You can tell JBoss AS that "
-"the encoding for the request parameters will be taken from the request:"
-msgstr ""
+msgid "There is alternative which is probably better. You can tell JBoss AS that the encoding for the request parameters will be taken from the request:"
+msgstr "Il ya une alternative qui est probablement meilleure. Vous pouvez dire à JBoss AS que l'encodage des paramètres des requeêtes sera prit depuis la requête:"
#. Tag: programlisting
#: I18n.xml:48
#, no-c-format
msgid "<Connector port=\"8080\" useBodyEncodingForURI=\"true\"/>"
-msgstr ""
+msgstr "<Connector port=\"8080\" useBodyEncodingForURI=\"true\"/>"
#. Tag: title
#: I18n.xml:52
#, no-c-format
msgid "Translated application strings"
-msgstr ""
+msgstr "Les chaines de caractères de l'application traduites"
#. Tag: para
#: I18n.xml:54
#, no-c-format
-msgid ""
-"You'll also need localized strings for all the <emphasis>messages</emphasis> "
-"in your application (for example field labels on your views). First you need "
-"to ensure that your resource bundle is encoded using the desired character "
-"encoding. By default ASCII is used. Although ASCII is enough for many "
-"languages, it doesn't provide characters for all languages."
-msgstr ""
+msgid "You'll also need localized strings for all the <emphasis>messages</emphasis> in your application (for example field labels on your views). First you need to ensure that your resource bundle is encoded using the desired character encoding. By default ASCII is used. Although ASCII is enough for many languages, it doesn't provide characters for all languages."
+msgstr "Vous allez avoir besoin des chaines de caractères traduites pour tous les <emphasis>messages</emphasis> de votre applicatin (par exemple les labels des champsd e vos vues). En premier, vous alleza avoir besoin de vous assurer que vos fiches de ressources sont encodés avec l'encodage désiré. Par défaut, l'ASCII est utilisé. Mais l'ASCII n'est pas suffisant pour beaucoups de langues, il ne fourni pas toutes les lettres de tous les langages."
#. Tag: para
#: I18n.xml:63
#, no-c-format
-msgid ""
-"Resource bundles must be created in ASCII, or use Unicode escape codes to "
-"represent Unicode characters. Since you don't compile a property file to "
-"byte code, there is no way to tell the JVM which character set to use. So "
-"you must use either ASCII characters or escape characters not in the ASCII "
-"character set. You can represent a Unicode character in any Java file using "
-"\\uXXXX, where XXXX is the hexidecimal representation of the character."
-msgstr ""
+msgid "Resource bundles must be created in ASCII, or use Unicode escape codes to represent Unicode characters. Since you don't compile a property file to byte code, there is no way to tell the JVM which character set to use. So you must use either ASCII characters or escape characters not in the ASCII character set. You can represent a Unicode character in any Java file using \\uXXXX, where XXXX is the hexidecimal representation of the character."
+msgstr "Les fichiers de ressource doivent être créés en ASCII ou utiliser le code déspécialisé Unicode pour représenter les lettres Unicode. Sinon vous ne pourez pas compiler le fichier de propriété dans le byte-code, il n'y a pas de moyen pour indiquer à la JVM quel groupe de caractères utiliser. Donc vous devez utiliser soit les caractères ASCII soi des caractères déspécialisés qui ne sont pas dans le groupe des caractères de l'ASCII. Vous pouvez représenter un caractère Unicode dans le fichier en Java en utilisant \\uXXX, où XXX est la représentation hexadécimale de ce caractère."
#. Tag: para
#: I18n.xml:73
#, no-c-format
-msgid ""
-"You can write your translation of labels (<xref linkend=\"labels\"/>) to "
-"your messages resource bundle in the native encoding and then convert the "
-"content of the file into the escaped format through the tool "
-"<literal>native2ascii</literal> provided in the JDK. This tool will convert "
-"a file written in your native encoding to one that represents non-ASCII "
-"characters as Unicode escape sequences."
+msgid "You can write your translation of labels (<xref linkend=\"labels\"/>) to your messages resource bundle in the native encoding and then convert the content of the file into the escaped format through the tool <literal>native2ascii</literal> provided in the JDK. This tool will convert a file written in your native encoding to one that represents non-ASCII characters as Unicode escape sequences."
msgstr ""
#. Tag: para
#: I18n.xml:83
#, no-c-format
-msgid ""
-"Usage of this tool is described <ulink url=\"http://java.sun.com/j2se/1.5.0/"
-"docs/tooldocs/index.html#intl\">here for Java 5</ulink> or <ulink url="
-"\"http://java.sun.com/javase/6/docs/technotes/tools/#intl\">here for Java 6</"
-"ulink>. For example, to convert a file from UTF-8:"
-msgstr ""
+msgid "Usage of this tool is described <ulink url=\"http://java.sun.com/j2se/1.5.0/docs/tooldocs/index.html#intl\">here for Java 5</ulink> or <ulink url=\"http://java.sun.com/javase/6/docs/technotes/tools/#intl\">here for Java 6</ulink>. For example, to convert a file from UTF-8:"
+msgstr "L'utilisation de cet outil est décrit dans <ulink url=\"http://java.sun.com/j2se/1.5.0/docs/tooldocs/index.html#intl\">ici pour Java 5</ulink> ou <ulink url=\"http://java.sun.com/javase/6/docs/technotes/tools/#intl\">ici pour Java 6</ulink>. Par exemple, pour convertir un fichier depuis UTF-8:"
#. Tag: programlisting
#: I18n.xml:91
#, no-c-format
-msgid ""
-"<prompt>$ native2ascii -encoding UTF-8 messages_cs.properties > "
-"messages_cs_escaped.properties</prompt>"
-msgstr ""
+msgid "<prompt>$ native2ascii -encoding UTF-8 messages_cs.properties > messages_cs_escaped.properties</prompt>"
+msgstr "<prompt>$ native2ascii -encoding UTF-8 messages_cs.properties > messages_cs_escaped.properties</prompt>"
#. Tag: title
#: I18n.xml:96
#, no-c-format
msgid "Other encoding settings"
-msgstr ""
+msgstr "D'autres réglages pour l'encodage"
#. Tag: para
#: I18n.xml:98
#, no-c-format
-msgid ""
-"We need to make sure that the view displays your localized data and messages "
-"using the correct character set and also any data submitted uses the correct "
-"encoding."
+msgid "We need to make sure that the view displays your localized data and messages using the correct character set and also any data submitted uses the correct encoding."
msgstr ""
#. Tag: para
#: I18n.xml:104
#, no-c-format
-msgid ""
-"To set the display character encoding, you need to use the <literal><f:"
-"view locale=\"cs_CZ\"/></literal> tag (here we tell JSF to use the Czech "
-"locale). You may want to change the encoding of the xml document itself if "
-"you want to embed localized strings in the xml. To do this alter the "
-"encoding attribute in xml declaration <literal><?xml version=\"1.0\" "
-"encoding=\"UTF-8\"?></literal> as required."
+msgid "To set the display character encoding, you need to use the <literal><f:view locale=\"cs_CZ\"/></literal> tag (here we tell JSF to use the Czech locale). You may want to change the encoding of the xml document itself if you want to embed localized strings in the xml. To do this alter the encoding attribute in xml declaration <literal><?xml version=\"1.0\" encoding=\"UTF-8\"?></literal> as required."
msgstr ""
#. Tag: para
#: I18n.xml:114
#, no-c-format
-msgid ""
-"Also JSF/Facelets should submit any requests using the specified character "
-"encoding, but to make sure any requests that don't specify an encoding you "
-"can force the request encoding using a servlet filter. Configure this in "
-"<literal>components.xml</literal>:"
+msgid "Also JSF/Facelets should submit any requests using the specified character encoding, but to make sure any requests that don't specify an encoding you can force the request encoding using a servlet filter. Configure this in <literal>components.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -194,67 +141,50 @@
" override-client=\"true\" \n"
" url-pattern=\"*.seam\" />]]>"
msgstr ""
+"<![CDATA[<web:character-encoding-filter encoding=\"UTF-8\" \n"
+" override-client=\"true\" \n"
+" url-pattern=\"*.seam\" />]]>"
#. Tag: title
#: I18n.xml:126
#, no-c-format
msgid "Locales"
-msgstr ""
+msgstr "Les locales"
#. Tag: para
#: I18n.xml:128
#, no-c-format
-msgid ""
-"Each user login session has an associated instance of <literal>java.util."
-"Locale</literal> (available to the application as a component named "
-"<literal>locale</literal>). Under normal circumstances, you won't need to do "
-"any special configuration to set the locale. Seam just delegates to JSF to "
-"determine the active locale:"
+msgid "Each user login session has an associated instance of <literal>java.util.Locale</literal> (available to the application as a component named <literal>locale</literal>). Under normal circumstances, you won't need to do any special configuration to set the locale. Seam just delegates to JSF to determine the active locale:"
msgstr ""
#. Tag: para
#: I18n.xml:136
#, no-c-format
-msgid ""
-"If there is a locale associated with the HTTP request (the browser locale), "
-"and that locale is in the list of supported locales from <literal>faces-"
-"config.xml</literal>, use that locale for the rest of the session."
+msgid "If there is a locale associated with the HTTP request (the browser locale), and that locale is in the list of supported locales from <literal>faces-config.xml</literal>, use that locale for the rest of the session."
msgstr ""
#. Tag: para
#: I18n.xml:143
#, no-c-format
-msgid ""
-"Otherwise, if a default locale was specified in the <literal>faces-config."
-"xml</literal>, use that locale for the rest of the session."
+msgid "Otherwise, if a default locale was specified in the <literal>faces-config.xml</literal>, use that locale for the rest of the session."
msgstr ""
#. Tag: para
#: I18n.xml:149
#, no-c-format
msgid "Otherwise, use the default locale of the server."
-msgstr ""
+msgstr "Sinon, utilise la locale par défaut du serveur."
#. Tag: para
#: I18n.xml:153
#, no-c-format
-msgid ""
-"It is <emphasis>possible</emphasis> to set the locale manually via the Seam "
-"configuration properties <literal> org.jboss.seam.international."
-"localeSelector.language</literal>, <literal> org.jboss.seam.international."
-"localeSelector.country</literal> and <literal> org.jboss.seam.international."
-"localeSelector.variant</literal>, but we can't think of any good reason to "
-"ever do this."
+msgid "It is <emphasis>possible</emphasis> to set the locale manually via the Seam configuration properties <literal> org.jboss.seam.international.localeSelector.language</literal>, <literal> org.jboss.seam.international.localeSelector.country</literal> and <literal> org.jboss.seam.international.localeSelector.variant</literal>, but we can't think of any good reason to ever do this."
msgstr ""
#. Tag: para
#: I18n.xml:160
#, no-c-format
-msgid ""
-"It is, however, useful to allow the user to set the locale manually via the "
-"application user interface. Seam provides built-in functionality for "
-"overriding the locale determined by the algorithm above. All you have to do "
-"is add the following fragment to a form in your JSP or Facelets page:"
+msgid "It is, however, useful to allow the user to set the locale manually via the application user interface. Seam provides built-in functionality for overriding the locale determined by the algorithm above. All you have to do is add the following fragment to a form in your JSP or Facelets page:"
msgstr ""
#. Tag: programlisting
@@ -273,9 +203,7 @@
#. Tag: para
#: I18n.xml:168
#, no-c-format
-msgid ""
-"Or, if you want a list of all supported locales from <literal> faces-config."
-"xml</literal>, just use:"
+msgid "Or, if you want a list of all supported locales from <literal> faces-config.xml</literal>, just use:"
msgstr ""
#. Tag: programlisting
@@ -292,116 +220,79 @@
#. Tag: para
#: I18n.xml:173
#, no-c-format
-msgid ""
-"When the user selects an item from the drop-down, then clicks the command "
-"button, the Seam and JSF locales will be overridden for the rest of the "
-"session."
+msgid "When the user selects an item from the drop-down, then clicks the command button, the Seam and JSF locales will be overridden for the rest of the session."
msgstr ""
#. Tag: para
#: I18n.xml:177
#, no-c-format
-msgid ""
-"The brings us to the question of where the supported locales are defined. "
-"Typically, you provide a list of locales for which you have matching "
-"resource bundles in the <literal><locale-config></literal> element of "
-"the JSF configuration file (/META-INF/faces-config.xml). However, you have "
-"learned to appreciate that Seam's component configuration mechanism is more "
-"powerful than what is provided in Java EE. For that reason, you can "
-"configure the supported locales, and the default locale of the server, using "
-"the built-in component named <literal>org.jboss.seam.international."
-"localeConfig</literal>. To use it, you first declare an XML namespace for "
-"Seam's international package in the Seam component descriptor. You then "
-"define the default locale and supported locales as follows:"
+msgid "The brings us to the question of where the supported locales are defined. Typically, you provide a list of locales for which you have matching resource bundles in the <literal><locale-config></literal> element of the JSF configuration file (/META-INF/faces-config.xml). However, you have learned to appreciate that Seam's component configuration mechanism is more powerful than what is provided in Java EE. For that reason, you can configure the supported locales, and the default locale of the server, using the built-in component named <literal>org.jboss.seam.international.localeConfig</literal>. To use it, you first declare an XML namespace for Seam's international package in the Seam component descriptor. You then define the default locale and supported locales as follows:"
msgstr ""
#. Tag: programlisting
#: I18n.xml:190
#, no-c-format
-msgid ""
-"<international:locale-config default-locale=\"fr_CA\" supported-locales="
-"\"en fr_CA fr_FR\"/>"
+msgid "<international:locale-config default-locale=\"fr_CA\" supported-locales=\"en fr_CA fr_FR\"/>"
msgstr ""
#. Tag: para
#: I18n.xml:192
#, no-c-format
-msgid ""
-"Naturally, if you pronounce that you support a locale, you better provide a "
-"resource bundle to match it! Up next, you'll learn how to define the "
-"language-specific labels."
+msgid "Naturally, if you pronounce that you support a locale, you better provide a resource bundle to match it! Up next, you'll learn how to define the language-specific labels."
msgstr ""
#. Tag: title
#: I18n.xml:198
#, no-c-format
msgid "Labels"
-msgstr ""
+msgstr "Les labels"
#. Tag: para
#: I18n.xml:200
#, no-c-format
-msgid ""
-"JSF supports internationalization of user interface labels and descriptive "
-"text via the use of <literal><f:loadBundle /></literal>. You can use "
-"this approach in Seam applications. Alternatively, you can take advantage of "
-"the Seam <literal> messages</literal> component to display templated labels "
-"with embedded EL expressions."
+msgid "JSF supports internationalization of user interface labels and descriptive text via the use of <literal><f:loadBundle /></literal>. You can use this approach in Seam applications. Alternatively, you can take advantage of the Seam <literal> messages</literal> component to display templated labels with embedded EL expressions."
msgstr ""
#. Tag: title
#: I18n.xml:207
#, no-c-format
msgid "Defining labels"
-msgstr ""
+msgstr "La définition des labels"
#. Tag: para
#: I18n.xml:209
#, no-c-format
-msgid ""
-"Seam provides a <literal>java.util.ResourceBundle</literal> (available to "
-"the application as a <literal> org.jboss.seam.core.resourceBundle</"
-"literal>). You'll need to make your internationalized labels available via "
-"this special resource bundle. By default, the resource bundle used by Seam "
-"is named <literal>messages</literal> and so you'll need to define your "
-"labels in files named <literal> messages.properties</literal>, <literal> "
-"messages_en.properties</literal>, <literal> messages_en_AU.properties</"
-"literal>, etc. These files usually belong in the <literal>WEB-INF/classes</"
-"literal> directory."
+msgid "Seam provides a <literal>java.util.ResourceBundle</literal> (available to the application as a <literal> org.jboss.seam.core.resourceBundle</literal>). You'll need to make your internationalized labels available via this special resource bundle. By default, the resource bundle used by Seam is named <literal>messages</literal> and so you'll need to define your labels in files named <literal> messages.properties</literal>, <literal> messages_en.properties</literal>, <literal> messages_en_AU.properties</literal>, etc. These files usually belong in the <literal>WEB-INF/classes</literal> directory."
msgstr ""
#. Tag: para
#: I18n.xml:220
#, no-c-format
msgid "So, in <literal>messages_en.properties</literal>:"
-msgstr ""
+msgstr "Ainsi, dans <literal>messages_en.properties</literal>:"
#. Tag: programlisting
#: I18n.xml:222
#, no-c-format
msgid "Hello=Hello"
-msgstr ""
+msgstr "Hello=Hello"
#. Tag: para
#: I18n.xml:224
#, no-c-format
msgid "And in <literal>messages_en_AU.properties</literal>:"
-msgstr ""
+msgstr "Et dans <literal>messages_en_AU.properties</literal>:"
#. Tag: programlisting
#: I18n.xml:226
#, no-c-format
msgid "Hello=G'day"
-msgstr ""
+msgstr "Hello=G'day"
#. Tag: para
#: I18n.xml:228
#, no-c-format
-msgid ""
-"You can select a different name for the resource bundle by setting the Seam "
-"configuration property named <literal> org.jboss.seam.core.resourceLoader."
-"bundleNames</literal>. You can even specify a list of resource bundle names "
-"to be searched (depth first) for messages."
+msgid "You can select a different name for the resource bundle by setting the Seam configuration property named <literal> org.jboss.seam.core.resourceLoader.bundleNames</literal>. You can even specify a list of resource bundle names to be searched (depth first) for messages."
msgstr ""
#. Tag: programlisting
@@ -419,69 +310,56 @@
#. Tag: para
#: I18n.xml:236
#, no-c-format
-msgid ""
-"If you want to define a message just for a particular page, you can specify "
-"it in a resource bundle with the same name as the JSF view id, with the "
-"leading <literal>/</literal> and trailing file extension removed. So we "
-"could put our message in <literal> welcome/hello_en.properties</literal> if "
-"we only needed to display the message on <literal> /welcome/hello.jsp</"
-"literal>."
+msgid "If you want to define a message just for a particular page, you can specify it in a resource bundle with the same name as the JSF view id, with the leading <literal>/</literal> and trailing file extension removed. So we could put our message in <literal> welcome/hello_en.properties</literal> if we only needed to display the message on <literal> /welcome/hello.jsp</literal>."
msgstr ""
#. Tag: para
#: I18n.xml:243
#, no-c-format
-msgid ""
-"You can even specify an explicit bundle name in <literal> pages.xml</"
-"literal>:"
+msgid "You can even specify an explicit bundle name in <literal> pages.xml</literal>:"
msgstr ""
#. Tag: programlisting
#: I18n.xml:246
#, no-c-format
msgid "<page view-id=\"/welcome/hello.jsp\" bundle=\"HelloMessages\"/>"
-msgstr ""
+msgstr "<page view-id=\"/welcome/hello.jsp\" bundle=\"HelloMessages\"/>"
#. Tag: para
#: I18n.xml:248
#, no-c-format
-msgid ""
-"Then we could use messages defined in <literal> HelloMessages.properties</"
-"literal> on <literal> /welcome/hello.jsp</literal>."
+msgid "Then we could use messages defined in <literal> HelloMessages.properties</literal> on <literal> /welcome/hello.jsp</literal>."
msgstr ""
#. Tag: title
#: I18n.xml:254
#, no-c-format
msgid "Displaying labels"
-msgstr ""
+msgstr "L'affichage des labels"
#. Tag: para
#: I18n.xml:256
#, no-c-format
-msgid ""
-"If you define your labels using the Seam resource bundle, you'll be able to "
-"use them without having to type <literal> <f:loadBundle ... /></"
-"literal> on every page. Instead, you can simply type:"
+msgid "If you define your labels using the Seam resource bundle, you'll be able to use them without having to type <literal> <f:loadBundle ... /></literal> on every page. Instead, you can simply type:"
msgstr ""
#. Tag: programlisting
#: I18n.xml:260
#, no-c-format
msgid "<h:outputText value=\"#{messages['Hello']}\"/>"
-msgstr ""
+msgstr "<h:outputText value=\"#{messages['Hello']}\"/>"
#. Tag: para
#: I18n.xml:262
#, no-c-format
msgid "<para>or:</para>"
-msgstr ""
+msgstr "<para>ou:</para>"
#. Tag: programlisting
#: I18n.xml:264
#, no-c-format
msgid "<h:outputText value=\"#{messages.Hello}\"/>"
-msgstr ""
+msgstr "<h:outputText value=\"#{messages.Hello}\"/>"
#. Tag: para
#: I18n.xml:266
@@ -493,45 +371,42 @@
#: I18n.xml:269
#, no-c-format
msgid "Hello=Hello, #{user.firstName} #{user.lastName}"
-msgstr ""
+msgstr "Hello=Hello, #{user.firstName} #{user.lastName}"
#. Tag: programlisting
#: I18n.xml:271
#, no-c-format
msgid "Hello=G'day, #{user.firstName}"
-msgstr ""
+msgstr "Hello=G'day, #{user.firstName}"
#. Tag: para
#: I18n.xml:273
#, no-c-format
msgid "You can even use the messages in your code:"
-msgstr ""
+msgstr "Vous pouvez même utiliser les messages dans votre code:"
#. Tag: programlisting
#: I18n.xml:275
#, no-c-format
msgid "@In private Map<String, String> messages;"
-msgstr ""
+msgstr "@In private Map<String, String> messages;"
#. Tag: programlisting
#: I18n.xml:277
#, no-c-format
msgid "@In(\"#{messages['Hello']}\") private String helloMessage;"
-msgstr ""
+msgstr "@In(\"#{messages['Hello']}\") private String helloMessage;"
#. Tag: title
#: I18n.xml:281
#, no-c-format
msgid "Faces messages"
-msgstr ""
+msgstr "Les messages Faces"
#. Tag: para
#: I18n.xml:283
#, no-c-format
-msgid ""
-"The <literal>facesMessages</literal> component is a super-convenient way to "
-"display success or failure messages to the user. The functionality we just "
-"described also works for faces messages:"
+msgid "The <literal>facesMessages</literal> component is a super-convenient way to display success or failure messages to the user. The functionality we just described also works for faces messages:"
msgstr ""
#. Tag: programlisting
@@ -548,75 +423,63 @@
" }\n"
"}"
msgstr ""
+"@Name(\"hello\")\n"
+"@Stateless\n"
+"public class HelloBean implements Hello {\n"
+" @In FacesMessages facesMessages;\n"
+" \n"
+" public String sayIt() {\n"
+" facesMessages.addFromResourceBundle(\"Hello\");\n"
+" }\n"
+"}"
#. Tag: para
#: I18n.xml:290
#, no-c-format
-msgid ""
-"This will display <literal>Hello, Gavin King</literal> or <literal>G'day, "
-"Gavin</literal>, depending upon the user's locale."
-msgstr ""
+msgid "This will display <literal>Hello, Gavin King</literal> or <literal>G'day, Gavin</literal>, depending upon the user's locale."
+msgstr "Cela va afficher <literal>Hello, Gavin King</literal> ou <literal>G'day, Gavin</literal>, selon la locale de l'utilisateur."
#. Tag: title
#: I18n.xml:297
#, no-c-format
msgid "Timezones"
-msgstr ""
+msgstr "Les fuseaux horaires"
#. Tag: para
#: I18n.xml:299
#, no-c-format
-msgid ""
-"There is also a session-scoped instance of <literal> java.util.Timezone</"
-"literal>, named <literal> org.jboss.seam.international.timezone</literal>, "
-"and a Seam component for changing the timezone named <literal> org.jboss."
-"seam.international.timezoneSelector</literal>. By default, the timezone is "
-"the default timezone of the server. Unfortunately, the JSF specification "
-"says that all dates and times should be assumed to be UTC, and displayed as "
-"UTC, unless a timezone is explicitly specified using <literal> <f:"
-"convertDateTime></literal>. This is an extremely inconvenient default "
-"behavior."
+msgid "There is also a session-scoped instance of <literal> java.util.Timezone</literal>, named <literal> org.jboss.seam.international.timezone</literal>, and a Seam component for changing the timezone named <literal> org.jboss.seam.international.timezoneSelector</literal>. By default, the timezone is the default timezone of the server. Unfortunately, the JSF specification says that all dates and times should be assumed to be UTC, and displayed as UTC, unless a timezone is explicitly specified using <literal> <f:convertDateTime></literal>. This is an extremely inconvenient default behavior."
msgstr ""
#. Tag: para
#: I18n.xml:310
#, no-c-format
-msgid ""
-"Seam overrides this behavior, and defaults all dates and times to the Seam "
-"timezone. In addition, Seam provides the <literal> <s:convertDateTime>"
-"</literal> tag which always performs conversions in the Seam timezone."
+msgid "Seam overrides this behavior, and defaults all dates and times to the Seam timezone. In addition, Seam provides the <literal> <s:convertDateTime></literal> tag which always performs conversions in the Seam timezone."
msgstr ""
#. Tag: para
#: I18n.xml:315
#, no-c-format
-msgid ""
-"Seam also provides a default date converter to convert a string value to a "
-"date. This saves you from having to specify a converter on input fields that "
-"are simply capturing a date. The pattern is selected according the the "
-"user's locale and the time zone is selected as described above."
+msgid "Seam also provides a default date converter to convert a string value to a date. This saves you from having to specify a converter on input fields that are simply capturing a date. The pattern is selected according the the user's locale and the time zone is selected as described above."
msgstr ""
#. Tag: title
#: I18n.xml:322
#, no-c-format
msgid "Themes"
-msgstr ""
+msgstr "Les thèmes"
#. Tag: para
#: I18n.xml:324
#, no-c-format
-msgid ""
-"Seam applications are also very easily skinnable. The theme API is very "
-"similar to the localization API, but of course these two concerns are "
-"orthogonal, and some applications support both localization and themes."
+msgid "Seam applications are also very easily skinnable. The theme API is very similar to the localization API, but of course these two concerns are orthogonal, and some applications support both localization and themes."
msgstr ""
#. Tag: para
#: I18n.xml:329
#, no-c-format
msgid "First, configure the set of supported themes:"
-msgstr ""
+msgstr "En permier, configurez le groupe de thème disponibles:"
#. Tag: programlisting
#: I18n.xml:331
@@ -635,16 +498,12 @@
#: I18n.xml:333
#, no-c-format
msgid "Note that the first theme listed is the default theme."
-msgstr ""
+msgstr "Notez que le premier thème listé est le thème par défaut."
#. Tag: para
#: I18n.xml:335
#, no-c-format
-msgid ""
-"Themes are defined in a properties file with the same name as the theme. For "
-"example, the <literal>default</literal> theme is defined as a set of entries "
-"in <literal> default.properties</literal>. For example, <literal> default."
-"properties</literal> might define:"
+msgid "Themes are defined in a properties file with the same name as the theme. For example, the <literal>default</literal> theme is defined as a set of entries in <literal> default.properties</literal>. For example, <literal> default.properties</literal> might define:"
msgstr ""
#. Tag: programlisting
@@ -654,30 +513,26 @@
"css ../screen.css\n"
"template /template.xhtml"
msgstr ""
+"css ../screen.css\n"
+"template /template.xhtml"
#. Tag: para
#: I18n.xml:342
#, no-c-format
-msgid ""
-"Usually the entries in a theme resource bundle will be paths to CSS styles "
-"or images and names of facelets templates (unlike localization resource "
-"bundles which are usually text)."
+msgid "Usually the entries in a theme resource bundle will be paths to CSS styles or images and names of facelets templates (unlike localization resource bundles which are usually text)."
msgstr ""
#. Tag: para
#: I18n.xml:346
#, no-c-format
-msgid ""
-"Now we can use these entries in our JSP or facelets pages. For example, to "
-"theme the stylesheet in a facelets page:"
+msgid "Now we can use these entries in our JSP or facelets pages. For example, to theme the stylesheet in a facelets page:"
msgstr ""
#. Tag: programlisting
#: I18n.xml:349
#, no-c-format
-msgid ""
-"<link href=\"#{theme.css}\" rel=\"stylesheet\" type=\"text/css\" />"
-msgstr ""
+msgid "<link href=\"#{theme.css}\" rel=\"stylesheet\" type=\"text/css\" />"
+msgstr "<link href=\"#{theme.css}\" rel=\"stylesheet\" type=\"text/css\" />"
#. Tag: para
#: I18n.xml:351
@@ -689,17 +544,16 @@
#: I18n.xml:353
#, no-c-format
msgid ""
-"<link href=\"#{facesContext.externalContext.requestContextPath}#{theme."
-"css}\" \n"
+"<link href=\"#{facesContext.externalContext.requestContextPath}#{theme.css}\" \n"
" rel=\"stylesheet\" type=\"text/css\" />"
msgstr ""
+"<link href=\"#{facesContext.externalContext.requestContextPath}#{theme.css}\" \n"
+" rel=\"stylesheet\" type=\"text/css\" />"
#. Tag: para
#: I18n.xml:355
#, no-c-format
-msgid ""
-"Most powerfully, facelets lets us theme the template used by a <literal><"
-"ui:composition></literal>:"
+msgid "Most powerfully, facelets lets us theme the template used by a <literal><ui:composition></literal>:"
msgstr ""
#. Tag: programlisting
@@ -712,13 +566,16 @@
" xmlns:f=\"http://java.sun.com/jsf/core\"\n"
" template=\"#{theme.template}\">"
msgstr ""
+"<ui:composition xmlns=\"http://www.w3.org/1999/xhtml\"\n"
+" xmlns:ui=\"http://java.sun.com/jsf/facelets\"\n"
+" xmlns:h=\"http://java.sun.com/jsf/html\"\n"
+" xmlns:f=\"http://java.sun.com/jsf/core\"\n"
+" template=\"#{theme.template}\">"
#. Tag: para
#: I18n.xml:360
#, no-c-format
-msgid ""
-"Just like the locale selector, there is a built-in theme selector to allow "
-"the user to freely switch themes:"
+msgid "Just like the locale selector, there is a built-in theme selector to allow the user to freely switch themes:"
msgstr ""
#. Tag: programlisting
@@ -728,9 +585,12 @@
"<h:selectOneMenu value=\"#{themeSelector.theme}\">\n"
" <f:selectItems value=\"#{themeSelector.themes}\"/>\n"
"</h:selectOneMenu>\n"
-"<h:commandButton action=\"#{themeSelector.select}\" value=\"Select Theme"
-"\"/>"
+"<h:commandButton action=\"#{themeSelector.select}\" value=\"Select Theme\"/>"
msgstr ""
+"<h:selectOneMenu value=\"#{themeSelector.theme}\">\n"
+" <f:selectItems value=\"#{themeSelector.themes}\"/>\n"
+"</h:selectOneMenu>\n"
+"<h:commandButton action=\"#{themeSelector.select}\" value=\"Select Theme\"/>"
#. Tag: title
#: I18n.xml:367
@@ -741,11 +601,7 @@
#. Tag: para
#: I18n.xml:369
#, no-c-format
-msgid ""
-"The locale selector, theme selector and timezone selector all support "
-"persistence of locale and theme preference to a cookie. Simply set the "
-"<literal>cookie-enabled</literal> property in <literal>components.xml</"
-"literal>:"
+msgid "The locale selector, theme selector and timezone selector all support persistence of locale and theme preference to a cookie. Simply set the <literal>cookie-enabled</literal> property in <literal>components.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -762,3 +618,13 @@
"\n"
"<international:locale-selector cookie-enabled=\"true\"/>"
msgstr ""
+"<theme:theme-selector cookie-enabled=\"true\">\n"
+" <theme:available-themes>\n"
+" <value>default</value>\n"
+" <value>accessible</value>\n"
+" <value>printable</value>\n"
+" </theme:available-themes>\n"
+"</theme:theme-selector>\n"
+"\n"
+"<international:locale-selector cookie-enabled=\"true\"/>"
+
15 years, 1 month
- 1
- 0
Seam SVN: r11603 - branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR.
by seam-commits＠lists.jboss.org
Author: essaidetest
Date: 2009-10-18 05:24:03 -0400 (Sun, 18 Oct 2009)
New Revision: 11603
Modified:
branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Guice.po
branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Gwt.po
Log:
Modified: branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Guice.po
===================================================================
--- branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Guice.po 2009-10-17 22:23:14 UTC (rev 11602)
+++ branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Guice.po 2009-10-18 09:24:03 UTC (rev 11603)
@@ -3,8 +3,8 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-07-15 11:43+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"PO-Revision-Date: 2009-10-18 11:01+0100\n"
+"Last-Translator: P.J <essaidetest(a)yahoo.fr>\n"
"Language-Team: LANGUAGE <LL(a)li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -14,46 +14,31 @@
#: Guice.xml:6
#, no-c-format
msgid "Guice integration"
-msgstr ""
+msgstr "L'intégration Guice"
#. Tag: para
#: Guice.xml:8
#, no-c-format
-msgid ""
-"Google Guice is a library that provides lightweight dependency injection "
-"through type-safe resolution. The Guice integration (part of the Seam IoC "
-"module) allows use of Guice injection for all Seam components annotated with "
-"the <literal>@Guice</literal> annotation. In addition to the regular "
-"bijection that Seam performs (which becomes optional), Seam also delegates "
-"to known Guice injectors to satisfy the dependencies of the component. Guice "
-"may be useful to tie non-Seam parts of large or legacy applications together "
-"with Seam."
-msgstr ""
+msgid "Google Guice is a library that provides lightweight dependency injection through type-safe resolution. The Guice integration (part of the Seam IoC module) allows use of Guice injection for all Seam components annotated with the <literal>@Guice</literal> annotation. In addition to the regular bijection that Seam performs (which becomes optional), Seam also delegates to known Guice injectors to satisfy the dependencies of the component. Guice may be useful to tie non-Seam parts of large or legacy applications together with Seam."
+msgstr "Google Guice est une bibliothèque qui fornie une injection de dépendance légère au travers d'une résolution de type en mode sûr. L'intégration de Guice (la partie du module IoC de Seam ) permet l'utilisation de tous les composants de Seam annoté avec l'annotation <literal>@Guice</literal>. En plus de la bijection classique que Seam réalise (qui devient optionnelle), Seam délègue aussi pour savoir si les injecteurs de Guice satisfons les dependances du composant. Guice peut êtrre utile pour inclure des parties non-Seam de grande applications validées en accord avec Seam."
#. Tag: note
#: Guice.xml:17
#, no-c-format
-msgid ""
-"The Guice integration is bundled in the jboss-seam-ioc library. This "
-"dependency is required for all integration techniques covered in this "
-"chapter. You will also need the Guice JAR file on the classpath."
-msgstr ""
+msgid "The Guice integration is bundled in the jboss-seam-ioc library. This dependency is required for all integration techniques covered in this chapter. You will also need the Guice JAR file on the classpath."
+msgstr "L'intégration de Guice est livré dans la bibliothèque jboss-seam-ioc. Cette dépendance est nécéssaire pour toutes les techniques d'intégration couverte dans ce chapitre. Vous allez aussi avoir besoin du fichier JAR de Guice dans le classpath."
#. Tag: title
#: Guice.xml:24
#, no-c-format
msgid "Creating a hybrid Seam-Guice component"
-msgstr ""
+msgstr "La création d'un composant hybride Seam-Guice"
#. Tag: para
#: Guice.xml:26
#, no-c-format
-msgid ""
-"The goal is to create a hybrid Seam-Guice component. The rule for how to do "
-"this is very simple. If you want to use Guice injection in your Seam "
-"component, annotate it with the <literal>@Guice</literal> annotation (after "
-"importing the type <literal>org.jboss.seam.ioc.guice.Guice</literal>)."
-msgstr ""
+msgid "The goal is to create a hybrid Seam-Guice component. The rule for how to do this is very simple. If you want to use Guice injection in your Seam component, annotate it with the <literal>@Guice</literal> annotation (after importing the type <literal>org.jboss.seam.ioc.guice.Guice</literal>)."
+msgstr "Le but est de créer un composant hybride Seam-Guice. La règle pour faire cela est vraiment très simple. Si vous voulez utiliser l'injection de Guice dans votre composant Seam, annoté le avec l'annotation de <literal>@Guice</literal> (après l'imporation du type <literal>org.jboss.seam.ioc.guice.Guice</literal>)."
#. Tag: programlisting
#: Guice.xml:33
@@ -67,17 +52,19 @@
" ...\n"
"}"
msgstr ""
+"@Name(\"myGuicyComponent\")\n"
+"@Guice public class MyGuicyComponent\n"
+"{\n"
+" @Inject MyObject myObject;\n"
+" @Inject @Special MyObject mySpecialObject;\n"
+" ...\n"
+"}"
#. Tag: para
#: Guice.xml:35
#, no-c-format
-msgid ""
-"This Guice injection will happen on every method call, just like with "
-"bijection. Guice injects based on type and binding. To satisfy the "
-"dependencies in the previous example, you might have bound the following "
-"implementations in a Guice module, where <literal>@Special</literal> is an "
-"annotation you define in your application."
-msgstr ""
+msgid "This Guice injection will happen on every method call, just like with bijection. Guice injects based on type and binding. To satisfy the dependencies in the previous example, you might have bound the following implementations in a Guice module, where <literal>@Special</literal> is an annotation you define in your application."
+msgstr "L'injection de Guice intervient sur chaque appel de méthode tout comme avec la bijection. Guice injecte en se bassant sur le type et la correspondance. Pour satisfaire les dépencandes dans notre exemple précédent, vous devriez avoir lié ces implémentations suivante dans le module Guice, avec <literal>@Special</literal> comme annotation que vous défininissez dans votre application."
#. Tag: programlisting
#: Guice.xml:42
@@ -95,29 +82,35 @@
" }\n"
"}"
msgstr ""
+"public class MyGuicyModule implements Module\n"
+"{\n"
+" public void configure(Binder binder)\n"
+" {\n"
+" binder.bind(MyObject.class)\n"
+" .toInstance(new MyObject(\"regular\"));\n"
+"\n"
+" binder.bind(MyObject.class).annotatedWith(Special.class)\n"
+" .toInstance(new MyObject(\"special\"));\n"
+" }\n"
+"}"
#. Tag: para
#: Guice.xml:44
#, no-c-format
-msgid ""
-"Great, but which Guice injector will be used to inject the dependencies? "
-"Well, you need to perform some setup first."
-msgstr ""
+msgid "Great, but which Guice injector will be used to inject the dependencies? Well, you need to perform some setup first."
+msgstr "Génial, mais avec l'injection de Guice qui va être utilisé pour injecter les dépendances? Et bien, vous avez besoin de réaliser quelques configurations en premier lieu."
#. Tag: title
#: Guice.xml:53
#, no-c-format
msgid "Configuring an injector"
-msgstr ""
+msgstr "La configuration d'une injection"
#. Tag: para
#: Guice.xml:55
#, no-c-format
-msgid ""
-"You tell Seam which Guice injector to use by hooking it into the injection "
-"property of the Guice initialization component in the Seam component "
-"descriptor (components.xml):"
-msgstr ""
+msgid "You tell Seam which Guice injector to use by hooking it into the injection property of the Guice initialization component in the Seam component descriptor (components.xml):"
+msgstr "Vous pouvez dire à Seam quel injecteur de Guice à utiliser quand il intercepte la propriété injectée du composant d'initialisation de Guice dans le descripteur de composant de Seam (components.xml):"
#. Tag: programlisting
#: Guice.xml:60
@@ -136,25 +129,30 @@
"\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xmlns:guice=\"http://jboss.com/products/seam/guice\"\n"
+" xsi:schemaLocation=\"\n"
+" http://jboss.com/products/seam/guice\n"
+" http://jboss.com/products/seam/guice-2.2.xsd\n"
+" http://jboss.com/products/seam/components\n"
+" http://jboss.com/products/seam/components-2.2.xsd\">\n"
+"\n"
+" <guice:init injector=\"#{myGuiceInjector}\"/>\n"
+"\n"
+"</components>]]>"
#. Tag: para
#: Guice.xml:62
#, no-c-format
-msgid ""
-"<literal>myGuiceInjector</literal> must resolve to a Seam component that "
-"implements the Guice <literal>Injector</literal> interface."
-msgstr ""
+msgid "<literal>myGuiceInjector</literal> must resolve to a Seam component that implements the Guice <literal>Injector</literal> interface."
+msgstr "<literal>myGuiceInjector</literal> doit être résolue vers un composant de Seam qui implémente l'interface <literal>Injector</literal> de Guice."
#. Tag: para
#: Guice.xml:67
#, no-c-format
-msgid ""
-"Having to create an injector is boiler-plate code, though. What you really "
-"want to be able to do is simply hook up Seam to your Guice modules. "
-"Fortunately, there is a built-in Seam component that implements the "
-"<literal>Injector</literal> interface to do exactly that. You can configure "
-"it in the Seam component descriptor with this additional stanza."
-msgstr ""
+msgid "Having to create an injector is boiler-plate code, though. What you really want to be able to do is simply hook up Seam to your Guice modules. Fortunately, there is a built-in Seam component that implements the <literal>Injector</literal> interface to do exactly that. You can configure it in the Seam component descriptor with this additional stanza."
+msgstr "Avoir à créer un injecteur est un code de type copier/coller. Quand vous voulez réellement être capable de simplement intercepter Seam vers vos modules Guice. Heureusement, il ya un composant livré de Seam qui implémente l'interface <literal>Injector</literal> pour faire exactement tout cela. Vous pouvez le configurer dans le descripteur de composant de Seam avec cette strophe additionnelle."
#. Tag: programlisting
#: Guice.xml:74
@@ -167,17 +165,18 @@
" </guice:modules> \n"
"</guice:injector>]]>"
msgstr ""
+"<![CDATA[<guice:injector name=\"myGuiceInjector\">\n"
+" <guice:modules> \n"
+" <value>com.example.guice.GuiceModule1</value> \n"
+" <value>com.example.guice.GuiceModule2</value> \n"
+" </guice:modules> \n"
+"</guice:injector>]]>"
#. Tag: para
#: Guice.xml:76
#, no-c-format
-msgid ""
-"Of course you can also use an injector that is already used in other, "
-"possibly non-Seam part of you application. That's one of the main "
-"motivations for creating this integration. Since the injector is defined "
-"with EL expression, you can obtain it in whatever way you like. For "
-"instance, you may use the Seam factory component pattern to provide injector."
-msgstr ""
+msgid "Of course you can also use an injector that is already used in other, possibly non-Seam part of you application. That's one of the main motivations for creating this integration. Since the injector is defined with EL expression, you can obtain it in whatever way you like. For instance, you may use the Seam factory component pattern to provide injector."
+msgstr "Bien sur vous pouvez aussi utiliser un injecteur qui est déjà utilisé dans d'autres, particulièrement des parties non-Seam de votre application. Ceci est une des principales motivation de la création de cette intégration. Quand l'injecteur est définie avec une expression EL, vous pouvez obtenir par ce biais ce que vous voulez. Par exemple, vous pouvez utiliser le patron composant de fabrique de Seam pour fournir votre injecteur."
#. Tag: programlisting
#: Guice.xml:83
@@ -193,22 +192,27 @@
" }\n"
"}"
msgstr ""
+"@Name(\"myGuiceInjectorFactory\")\n"
+"public InjectorFactory\n"
+"{\n"
+" @Factory(name = \"myGuiceInjector\", scope = APPLICATION, create = true)\n"
+" public Injector getInjector()\n"
+" {\n"
+" // Your code that returns injector \n"
+" }\n"
+"}"
#. Tag: title
#: Guice.xml:88
#, no-c-format
msgid "Using multiple injectors"
-msgstr ""
+msgstr "L'utilisation de multiples injecteurs"
#. Tag: para
#: Guice.xml:90
#, no-c-format
-msgid ""
-"By default, an injector configured in the Seam component descriptor is used. "
-"If you really need to use multiple injectors (AFAIK, you should use multiple "
-"modules instead), you can specify different injector for every Seam "
-"component in the <literal>@Guice</literal> annotation."
-msgstr ""
+msgid "By default, an injector configured in the Seam component descriptor is used. If you really need to use multiple injectors (AFAIK, you should use multiple modules instead), you can specify different injector for every Seam component in the <literal>@Guice</literal> annotation."
+msgstr "Par défaut, un injecteur configuré dans le descripteur de composant de Seam est utilisé. Si vous avez réllement besoin d'utiliser plusieurs injecteurs (A ma connaissance vous devriez plutôt utiliser plusieurs modules), vous pouvez spécifier différents injecteurs pour chaque composant de Seam dans l'annotation <literal>@Guice</literal>."
#. Tag: programlisting
#: Guice.xml:97
@@ -222,11 +226,17 @@
" ...\n"
"}"
msgstr ""
+"@Name(\"myGuicyComponent\")\n"
+"@Guice(\"myGuiceInjector\")\n"
+"public class MyGuicyComponent\n"
+"{\n"
+" @Inject MyObject myObject;\n"
+" ...\n"
+"}"
#. Tag: para
#: Guice.xml:101
#, no-c-format
-msgid ""
-"That's all there is to it! Check out the guice example in the Seam "
-"distribution to see the Seam Guice integration in action!"
-msgstr ""
+msgid "That's all there is to it! Check out the guice example in the Seam distribution to see the Seam Guice integration in action!"
+msgstr "C'est tout ce qu'il y a à faire! Consultez l'exemple guice dans la distribution de Seam pour voir l'intégration de Guice de Seam en action!"
+
Modified: branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Gwt.po
===================================================================
--- branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Gwt.po 2009-10-17 22:23:14 UTC (rev 11602)
+++ branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Gwt.po 2009-10-18 09:24:03 UTC (rev 11603)
@@ -6,8 +6,8 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-12-04 00:58+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2009-10-18 11:23+0100\n"
+"Last-Translator: P.J <essaidetest(a)yahoo.fr>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -17,57 +17,43 @@
#: Gwt.xml:5
#, no-c-format
msgid "Seam and the Google Web Toolkit"
-msgstr ""
+msgstr "Seam et le Google Web Toolkit"
#. Tag: para
#: Gwt.xml:7
#, no-c-format
-msgid ""
-"For those that prefer to use the Google Web Toolkit (GWT) to develop dynamic "
-"AJAX applications, Seam provides an integration layer that allows GWT "
-"widgets to interact directly with Seam components."
-msgstr ""
+msgid "For those that prefer to use the Google Web Toolkit (GWT) to develop dynamic AJAX applications, Seam provides an integration layer that allows GWT widgets to interact directly with Seam components."
+msgstr "Pour ceux qui p^réfère utiliser le Google Web Toolkit (GWT) pour développer des applications AJAX dynamique, Seam fourni une couche d'intégration qui permet aux widgets GWT d'interagir directement avecc les composants de Seam."
#. Tag: para
#: Gwt.xml:12
#, no-c-format
-msgid ""
-"To use GWT, we assume that you are already familiar with the GWT tools - "
-"more information can be found at <ulink url=\"http://code.google.com/"
-"webtoolkit/\">http://code.google.com/webtoolkit/</ulink>. This chapter does "
-"not attempt to explain how GWT works or how to use it."
-msgstr ""
+msgid "To use GWT, we assume that you are already familiar with the GWT tools - more information can be found at <ulink url=\"http://code.google.com/webtoolkit/\">http://code.google.com/webtoolkit/</ulink>. This chapter does not attempt to explain how GWT works or how to use it."
+msgstr "Pour utiliser GWT, nous allons postuler que vous êtes déjà familier avec les outils GWT - plus d'informations peut ête trouvée sur <ulink url=\"http://code.google.com/webtoolkit/\">http://code.google.com/webtoolkit/</ulink>. Ce chapitre n'essaye pas d'expliquer comment GWT fonctionne et comment l'utiliser."
#. Tag: title
#: Gwt.xml:19
#, no-c-format
msgid "Configuration"
-msgstr ""
+msgstr "La configuration"
#. Tag: para
#: Gwt.xml:21
#, no-c-format
-msgid ""
-"There is no special configuration required to use GWT in a Seam application, "
-"however the Seam resource servlet must be installed. See <xref linkend="
-"\"configuration\"/> for details."
-msgstr ""
+msgid "There is no special configuration required to use GWT in a Seam application, however the Seam resource servlet must be installed. See <xref linkend=\"configuration\"/> for details."
+msgstr "Il n'y a pas de configuration spécialé nécéssaire pour utiliser GWT dans une application Seam, cependant le servlet de ressource de Seam doit être installé. Voir <xref linkend=\"configuration\"/> pour les détails."
#. Tag: title
#: Gwt.xml:29
#, no-c-format
msgid "Preparing your component"
-msgstr ""
+msgstr "La préparation de votre composant"
#. Tag: para
#: Gwt.xml:31
#, no-c-format
-msgid ""
-"The first step in preparing a Seam component to be called via GWT, is to "
-"create both synchronous and asynchronous service interfaces for the methods "
-"you wish to call. Both of these interfaces should extend the GWT interface "
-"<literal>com.google.gwt.user.client.rpc.RemoteService</literal>:"
-msgstr ""
+msgid "The first step in preparing a Seam component to be called via GWT, is to create both synchronous and asynchronous service interfaces for the methods you wish to call. Both of these interfaces should extend the GWT interface <literal>com.google.gwt.user.client.rpc.RemoteService</literal>:"
+msgstr "La première étape dans la préparation du composant dfe Seam est d'être appelé via GWT, cela créer deux interfaces de service synchrone et assynchrone pour les méthode que vous souhaitez appeler. Ces deux interfaces devraient étendre l'interface GWT <literal>com.google.gwt.user.client.rpc.RemoteService</literal>:"
#. Tag: programlisting
#: Gwt.xml:37
@@ -77,15 +63,15 @@
" public String askIt(String question); \n"
" }]]>"
msgstr ""
+"<![CDATA[public interface MyService extends RemoteService {\n"
+" public String askIt(String question); \n"
+" }]]>"
#. Tag: para
#: Gwt.xml:39
#, no-c-format
-msgid ""
-"The asynchronous interface should be identical, except that it also contains "
-"an additional <literal>AsyncCallback</literal> parameter for each of the "
-"methods it declares:"
-msgstr ""
+msgid "The asynchronous interface should be identical, except that it also contains an additional <literal>AsyncCallback</literal> parameter for each of the methods it declares:"
+msgstr "L'interface asynchrone devrait être identique, à la différence qu'il doit contenir un paramètre additionnel <literal>AsyncCallback</literal> pour chaque méthode qu'il déclare:"
#. Tag: programlisting
#: Gwt.xml:44
@@ -95,23 +81,21 @@
" public void askIt(String question, AsyncCallback callback);\n"
"}]]>"
msgstr ""
+"<![CDATA[public interface MyServiceAsync extends RemoteService {\n"
+" public void askIt(String question, AsyncCallback callback);\n"
+"}]]>"
#. Tag: para
#: Gwt.xml:46
#, no-c-format
-msgid ""
-"The asynchronous interface, in this example <literal>MyServiceAsync</"
-"literal>, will be implemented by GWT and should never be implemented "
-"directly."
-msgstr ""
+msgid "The asynchronous interface, in this example <literal>MyServiceAsync</literal>, will be implemented by GWT and should never be implemented directly."
+msgstr "L'interface assynchrone, dans cet exemple <literal>MyServiceAsync</literal>, sera implémenté par GWT et ne devrait pas être implémenté directement."
#. Tag: para
#: Gwt.xml:51
#, no-c-format
-msgid ""
-"The next step, is to create a Seam component that implements the synchronous "
-"interface:"
-msgstr ""
+msgid "The next step, is to create a Seam component that implements the synchronous interface:"
+msgstr "L'étape suivante, est de créer un composant de Seam qui implémente l'interface synchrone:"
#. Tag: programlisting
#: Gwt.xml:55
@@ -124,8 +108,7 @@
" public String askIt(String question) {\n"
" \n"
" if (!validate(question)) {\n"
-" throw new IllegalStateException(\"Hey, this shouldn't happen, I "
-"checked on the client, \" +\n"
+" throw new IllegalStateException(\"Hey, this shouldn't happen, I checked on the client, \" +\n"
" \"but its always good to double check.\");\n"
" }\n"
" return \"42. Its the real question that you seek now.\";\n"
@@ -137,56 +120,68 @@
" }\n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"org.jboss.seam.example.remoting.gwt.client.MyService\")\n"
+"public class ServiceImpl implements MyService {\n"
+"\n"
+" @WebRemote\n"
+" public String askIt(String question) {\n"
+" \n"
+" if (!validate(question)) {\n"
+" throw new IllegalStateException(\"Hey, this shouldn't happen, I checked on the client, \" +\n"
+" \"but its always good to double check.\");\n"
+" }\n"
+" return \"42. Its the real question that you seek now.\";\n"
+" }\n"
+" \n"
+" public boolean validate(String q) {\n"
+" ValidationUtility util = new ValidationUtility();\n"
+" return util.isValid(q);\n"
+" }\n"
+"}]]>"
#. Tag: para
#: Gwt.xml:57
#, no-c-format
-msgid ""
-"The name of the seam component <emphasis>must</emphasis> match the fully "
-"qualified name of the GWT client interface (as shown), or the seam resource "
-"servlet will not be able to find it when a client makes a GWT call. The "
-"methods that are to be made accessible via GWT also need to be annotated "
-"with the <literal>@WebRemote</literal> annotation."
-msgstr ""
+msgid "The name of the seam component <emphasis>must</emphasis> match the fully qualified name of the GWT client interface (as shown), or the seam resource servlet will not be able to find it when a client makes a GWT call. The methods that are to be made accessible via GWT also need to be annotated with the <literal>@WebRemote</literal> annotation."
+msgstr "Le nom du composant seam <emphasis>doit</emphasis> correspondre au nom pleinement qualifié de l'interface client GWT (comme montré), ou ne servlet de ressource de seam ne sera pas capable de le trouver quand un client fait un appel GWT. Les méthodes qui sont accéssible via GWT doivent aussi être annotées avec l'annotation <literal>@WebRemote</literal>."
#. Tag: title
#: Gwt.xml:67
#, no-c-format
msgid "Hooking up a GWT widget to the Seam component"
-msgstr ""
+msgstr "Interception deu widget GWT vers un composant de Seam"
#. Tag: para
#: Gwt.xml:69
#, no-c-format
-msgid ""
-"The next step, is to write a method that returns the asynchronous interface "
-"to the component. This method can be located inside the widget class, and "
-"will be used by the widget to obtain a reference to the asynchronous client "
-"stub:"
-msgstr ""
+msgid "The next step, is to write a method that returns the asynchronous interface to the component. This method can be located inside the widget class, and will be used by the widget to obtain a reference to the asynchronous client stub:"
+msgstr "La prochaine étape est d'écrire une méthode qui retourne un itnerface assynchrone vers le composant. Cette méthode est localisée dans la classe widget, et sera utilisé avec le widget pour obtenir une référence vers un squelette de client assynchrone:"
#. Tag: programlisting
#: Gwt.xml:75
#, no-c-format
msgid ""
"<![CDATA[private MyServiceAsync getService() { \n"
-" String endpointURL = GWT.getModuleBaseURL() + \"seam/resource/gwt"
-"\"; \n"
+" String endpointURL = GWT.getModuleBaseURL() + \"seam/resource/gwt\"; \n"
" \n"
" MyServiceAsync svc = (MyServiceAsync) GWT.create(MyService.class);\n"
" ((ServiceDefTarget) svc).setServiceEntryPoint(endpointURL);\n"
" return svc; \n"
"}]]>"
msgstr ""
+"<![CDATA[private MyServiceAsync getService() { \n"
+" String endpointURL = GWT.getModuleBaseURL() + \"seam/resource/gwt\"; \n"
+" \n"
+" MyServiceAsync svc = (MyServiceAsync) GWT.create(MyService.class);\n"
+" ((ServiceDefTarget) svc).setServiceEntryPoint(endpointURL);\n"
+" return svc; \n"
+"}]]>"
#. Tag: para
#: Gwt.xml:77
#, no-c-format
-msgid ""
-"The final step is to write the widget code that invokes the method on the "
-"client stub. The following example creates a simple user interface with a "
-"label, text input and a button:"
-msgstr ""
+msgid "The final step is to write the widget code that invokes the method on the client stub. The following example creates a simple user interface with a label, text input and a button:"
+msgstr "La dernière étape est d'écrire le code du widget qui invoque la méthode sur le squelette du client. L'exemple suivant créer un interface utilisateur simple avec un label, une zone de saisie et un bouton:"
#. Tag: programlisting
#: Gwt.xml:82
@@ -232,50 +227,75 @@
" \n"
" ...]]>"
msgstr ""
+"<![CDATA[\n"
+"public class AskQuestionWidget extends Composite {\n"
+" private AbsolutePanel panel = new AbsolutePanel();\n"
+" \n"
+" public AskQuestionWidget() { \n"
+" Label lbl = new Label(\"OK, what do you want to know?\");\n"
+" panel.add(lbl);\n"
+" final TextBox box = new TextBox();\n"
+" box.setText(\"What is the meaning of life?\");\n"
+" panel.add(box);\n"
+" Button ok = new Button(\"Ask\");\n"
+" ok.addClickListener(new ClickListener() {\n"
+" public void onClick(Widget w) {\n"
+" ValidationUtility valid = new ValidationUtility();\n"
+" if (!valid.isValid(box.getText())) {\n"
+" Window.alert(\"A question has to end with a '?'\");\n"
+" } else {\n"
+" askServer(box.getText());\n"
+" } \n"
+" }\n"
+" });\n"
+" panel.add(ok);\n"
+" \n"
+" initWidget(panel);\n"
+" }\n"
+"\n"
+" private void askServer(String text) {\n"
+" getService().askIt(text, new AsyncCallback() {\n"
+" public void onFailure(Throwable t) {\n"
+" Window.alert(t.getMessage());\n"
+" }\n"
+"\n"
+" public void onSuccess(Object data) {\n"
+" Window.alert((String) data);\n"
+" } \n"
+" }); \n"
+" }\n"
+" \n"
+" ...]]>"
#. Tag: para
#: Gwt.xml:85
#, no-c-format
-msgid ""
-"When clicked, the button invokes the <literal>askServer()</literal> method "
-"passing the contents of the input text (in this example, validation is also "
-"performed to ensure that the input is a valid question). The "
-"<literal>askServer()</literal> method acquires a reference to the "
-"asynchronous client stub (returned by the <literal>getService()</literal> "
-"method) and invokes the <literal>askIt()</literal> method. The result (or "
-"error message if the call fails) is shown in an alert window."
-msgstr ""
+msgid "When clicked, the button invokes the <literal>askServer()</literal> method passing the contents of the input text (in this example, validation is also performed to ensure that the input is a valid question). The <literal>askServer()</literal> method acquires a reference to the asynchronous client stub (returned by the <literal>getService()</literal> method) and invokes the <literal>askIt()</literal> method. The result (or error message if the call fails) is shown in an alert window."
+msgstr " Quand on clique, le bouton appelle la méthode <literal>askServer()</literal> en passant le contenu de la zone de saisie (dans cet exemple, la validation est aussi réalisé pour s'assurer que la zone de saiie contient une question valide). La méthode <literal>askServer()</literal> obtient une référencer vers un squelette de client assynchrone (retournée par la méthode <literal>getService()</literal>) et invoque la méthode <literal>askIt()</literal>. Le résultat (ou le message d'erreursi l'appel échoue) est affiché dans une fenètre d'alerte."
#. Tag: para
#: Gwt.xml:102
#, no-c-format
-msgid ""
-"The complete code for this example can be found in the Seam distribution in "
-"the <literal>examples/remoting/gwt</literal> directory."
-msgstr ""
+msgid "The complete code for this example can be found in the Seam distribution in the <literal>examples/remoting/gwt</literal> directory."
+msgstr "Le code complet pour cet exemple peut être trouvé dans la distribution de Seam dans le dossier <literal>examples/remoting/gwt</literal>."
#. Tag: title
#: Gwt.xml:109
#, no-c-format
msgid "GWT Ant Targets"
-msgstr ""
+msgstr "Les cibles Ant GWT"
#. Tag: para
#: Gwt.xml:111
#, no-c-format
-msgid ""
-"For deployment of GWT apps, there is a compile-to-Javascript step (which "
-"compacts and obfuscates the code). There is an ant utility which can be used "
-"instead of the command line or GUI utility that GWT provides. To use this, "
-"you will need to have the ant task jar in your ant classpath, as well as GWT "
-"downloaded (which you will need for hosted mode anyway)."
-msgstr ""
+msgid "For deployment of GWT apps, there is a compile-to-Javascript step (which compacts and obfuscates the code). There is an ant utility which can be used instead of the command line or GUI utility that GWT provides. To use this, you will need to have the ant task jar in your ant classpath, as well as GWT downloaded (which you will need for hosted mode anyway)."
+msgstr "Pour le déploiement des applications GWT, il ya une étape de compilation vers Javascript (avec compactage et cryptage du code). Il y a un utilitaire de ant qui peut être utilisé au lieu de la ligne de commande ou de l'utilitaire GUI que GWT fourni. Pour l'utiliser, vous allez avoir besoin d'avoit le jar de tâche ant dans votre classpath, tout comme le GWT téléchargé (avec ce que vous avez besoin pour votre mode hébergement)."
#. Tag: para
#: Gwt.xml:117
#, no-c-format
msgid "Then, in your ant file, place (near the top of your ant file):"
-msgstr ""
+msgstr "Ensuite, dans votre fichier ant, mettez (presque en haut de votre fichier ant):"
#. Tag: programlisting
#: Gwt.xml:121
@@ -287,40 +307,39 @@
" \n"
" <property file=\"build.properties\"/>]]>"
msgstr ""
+"<![CDATA[<taskdef uri=\"antlib:de.samaflost.gwttasks\"\n"
+" resource=\"de/samaflost/gwttasks/antlib.xml\"\n"
+" classpath=\"./lib/gwttasks.jar\"/>\n"
+" \n"
+" <property file=\"build.properties\"/>]]>"
#. Tag: para
#: Gwt.xml:123
#, no-c-format
-msgid ""
-"Create a <literal>build.properties</literal> file, which has the contents:"
-msgstr ""
+msgid "Create a <literal>build.properties</literal> file, which has the contents:"
+msgstr "Créez un fichier <literal>build.properties</literal>, qui va avoir ce contenu:"
#. Tag: programlisting
#: Gwt.xml:127
#, no-c-format
msgid "<![CDATA[gwt.home=/gwt_home_dir]]>"
-msgstr ""
+msgstr "<![CDATA[gwt.home=/gwt_home_dir]]>"
#. Tag: para
#: Gwt.xml:129
#, no-c-format
-msgid ""
-"This of course should point to the directory where GWT is installed. Then to "
-"use it, create a target:"
-msgstr ""
+msgid "This of course should point to the directory where GWT is installed. Then to use it, create a target:"
+msgstr "Ceci devrait bien sûr pointer vers le dossier où GWT doit être installé. Ensuite, utilisez le pour créer une cible:"
#. Tag: programlisting
#: Gwt.xml:133
#, no-c-format
msgid ""
-"<![CDATA[<!-- the following are are handy utilities for doing GWT "
-"development.\n"
+"<![CDATA[<!-- the following are are handy utilities for doing GWT development.\n"
" To use GWT, you will of course need to download GWT seperately -->\n"
" <target name=\"gwt-compile\">\n"
-" <!-- in this case, we are \"re homing\" the gwt generated stuff, so in "
-"this case\n"
-" we can only have one GWT module - we are doing this deliberately to "
-"keep the URL short -->\n"
+" <!-- in this case, we are \"re homing\" the gwt generated stuff, so in this case\n"
+" we can only have one GWT module - we are doing this deliberately to keep the URL short -->\n"
" <delete>\n"
" <fileset dir=\"view\"/>\n"
" </delete>\n"
@@ -333,25 +352,32 @@
" </copy>\n"
" </target>]]>"
msgstr ""
+"<![CDATA[<!-- the following are are handy utilities for doing GWT development.\n"
+" To use GWT, you will of course need to download GWT seperately -->\n"
+" <target name=\"gwt-compile\">\n"
+" <!-- in this case, we are \"re homing\" the gwt generated stuff, so in this case\n"
+" we can only have one GWT module - we are doing this deliberately to keep the URL short -->\n"
+" <delete>\n"
+" <fileset dir=\"view\"/>\n"
+" </delete>\n"
+" <gwt:compile outDir=\"build/gwt\"\n"
+" gwtHome=\"${gwt.home}\"\n"
+" classBase=\"${gwt.module.name}\"\n"
+" sourceclasspath=\"src\"/>\n"
+" <copy todir=\"view\">\n"
+" <fileset dir=\"build/gwt/${gwt.module.name}\"/>\n"
+" </copy>\n"
+" </target>]]>"
#. Tag: para
#: Gwt.xml:135
#, no-c-format
-msgid ""
-"This target when called will compile the GWT application, and copy it to the "
-"specified directory (which would be in the <literal>webapp</literal> part of "
-"your war - remember GWT generates HTML and Javascript artifacts). You never "
-"edit the resulting code that <literal>gwt-compile</literal> generates - you "
-"always edit in the GWT source directory."
-msgstr ""
+msgid "This target when called will compile the GWT application, and copy it to the specified directory (which would be in the <literal>webapp</literal> part of your war - remember GWT generates HTML and Javascript artifacts). You never edit the resulting code that <literal>gwt-compile</literal> generates - you always edit in the GWT source directory."
+msgstr "La cible quand appelée va compiler l'application GWT et la copier dans le dossier spécifiée (ce qui devrait être dans le coin <literal>webapp</literal> de votre war - n'oubliez pas GWT génère des artefactes HTML et javascript). Vous n'éditez jamais le code résultant que <literal>gwt-compile</literal> génère - vous devez toujours éditer le source dans le dossier GWT."
#. Tag: para
#: Gwt.xml:142
#, no-c-format
-msgid ""
-"Remember that GWT comes with a hosted mode browser - you should be using "
-"that if you are developing with GWT. If you aren't using that, and are just "
-"compiling it each time, you aren't getting the most out of the toolkit (in "
-"fact, if you can't or won't use the hosted mode browser, I would go far as "
-"to say you should NOT be using GWT at all - it's that valuable!)."
-msgstr ""
+msgid "Remember that GWT comes with a hosted mode browser - you should be using that if you are developing with GWT. If you aren't using that, and are just compiling it each time, you aren't getting the most out of the toolkit (in fact, if you can't or won't use the hosted mode browser, I would go far as to say you should NOT be using GWT at all - it's that valuable!)."
+msgstr "N'oubliez pas que GWT vient avec un mode navigable hébergé - vous devriez l'utiliser pendant que vous développez avec GWT. Si vous ne le faite pas, et compilez à chaque fois, vous n'allez pas avoir le meilleurs de ce kit de développement (dans les fait, si vous ne voulez ou ne pouvez utiliser le mode navigable hébergé, je vous déconseille FORTEMENT d'utiliser GWT - est ce bien clair!)."
+
15 years, 1 month
- 1
- 0
Seam SVN: r11602 - branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR.
by seam-commits＠lists.jboss.org
Author: essaidetest
Date: 2009-10-17 18:23:14 -0400 (Sat, 17 Oct 2009)
New Revision: 11602
Modified:
branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Glassfish.po
Log:
Modified: branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Glassfish.po
===================================================================
--- branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Glassfish.po 2009-10-17 20:12:38 UTC (rev 11601)
+++ branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Glassfish.po 2009-10-17 22:23:14 UTC (rev 11602)
@@ -3,11 +3,11 @@
#
msgid ""
msgstr ""
-"Project-Id-Version: Seam_Reference_Guide \n"
+"Project-Id-Version: Seam_Reference_Guide\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-12-27 11:29+0000\n"
-"PO-Revision-Date: 2008-10-14 11:38+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2009-10-18 00:22+0100\n"
+"Last-Translator: P.J <essaidetest(a)yahoo.fr>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -17,438 +17,363 @@
#: Glassfish.xml:3
#, no-c-format
msgid "Seam on GlassFish application server"
-msgstr ""
+msgstr "Seam avec le serveur d'application GlassFish"
#. Tag: para
#: Glassfish.xml:5
#, no-c-format
-msgid ""
-"GlassFish is an open source application server which fully implements Java "
-"EE 5. The latest stable release is v2 UR2."
-msgstr ""
+msgid "GlassFish is an open source application server which fully implements Java EE 5. The latest stable release is v2 UR2."
+msgstr "GlassFish est un serveur d'application open source qui implément complètement Java EE 5. La dernière version stable est v2 UR2."
#. Tag: para
#: Glassfish.xml:10
#, no-c-format
-msgid ""
-"First, we'll discuss the GlassFish environment. Then we will go over the how "
-"you deploy the jee5 example. Next, we will deploy the JPA example "
-"application. Finally we show how to get a seam-gen's generated application "
-"running on GlassFish."
-msgstr ""
+msgid "First, we'll discuss the GlassFish environment. Then we will go over the how you deploy the jee5 example. Next, we will deploy the JPA example application. Finally we show how to get a seam-gen's generated application running on GlassFish."
+msgstr "En premier, nous allons parler de l'environement FlassFish. Ensuite nous allons passer sur comment vous allez déployer l'exemple JEE5. Enfin, nous allons déployer l'application d'exemple JPA. Au final, nous allons vor comment obtenir une application générée par seam-gen pour une exécution sur GlassFish."
#. Tag: title
#: Glassfish.xml:18
#, no-c-format
msgid "GlassFish environment and deployment information"
-msgstr ""
+msgstr "L'environement GlassFish et les informations de déploiement"
#. Tag: title
#: Glassfish.xml:21
#, no-c-format
msgid "Installation"
-msgstr ""
+msgstr "Installation"
#. Tag: para
#: Glassfish.xml:23
#, no-c-format
-msgid ""
-"All of the examples and information in this chapter are based on the the "
-"latest version of GlassFish at the time of this writing."
-msgstr ""
+msgid "All of the examples and information in this chapter are based on the the latest version of GlassFish at the time of this writing."
+msgstr "Tous les exemples et les informations de ce chapitre sont basés sur la dernière version de GlassFish au moment de son écriture."
#. Tag: ulink
#: Glassfish.xml:30
#, no-c-format
msgid "GlassFish v2 UR2 - download page"
-msgstr ""
+msgstr "GlassFish v2 UR2 - page de téléchagement "
#. Tag: para
#: Glassfish.xml:37
#, no-c-format
msgid "After downloading GlassFish, install it:"
-msgstr ""
+msgstr "Après le téléchargement de GlassFish, installez le:"
#. Tag: programlisting
#: Glassfish.xml:41
#, no-c-format
msgid "$ java -Xmx256m -jar glassfish-installer-v2ur2-b04-linux.jar"
-msgstr ""
+msgstr "$ java -Xmx256m -jar glassfish-installer-v2ur2-b04-linux.jar"
#. Tag: para
#: Glassfish.xml:43
#, no-c-format
msgid "After installing, setup GlassFish:"
-msgstr ""
+msgstr "Après l'installation, configurez GlassFish:"
#. Tag: programlisting
#: Glassfish.xml:47
#, no-c-format
msgid "$ cd glassfish; ant -f setup.xml"
-msgstr ""
+msgstr "$ cd glassfish; ant -f setup.xml"
#. Tag: para
#: Glassfish.xml:49
#, no-c-format
msgid "The created domain's name is <literal>domain1</literal>."
-msgstr ""
+msgstr "Le nom de domaine créé est <literal>domain1</literal>."
#. Tag: para
#: Glassfish.xml:53
#, no-c-format
msgid "Next, we start the embedded JavaDB server:"
-msgstr ""
+msgstr "Ensuite, nous démarrons le serveur JavaDB embarqué:"
#. Tag: programlisting
#: Glassfish.xml:57
#, no-c-format
msgid "$ bin/asadmin start-database"
-msgstr ""
+msgstr "$ bin/asadmin start-database"
#. Tag: para
#: Glassfish.xml:60
#, no-c-format
-msgid ""
-"JavaDB is an embedded database that is included with GlassFish, just as "
-"HSQLDB is included in JBoss AS."
-msgstr ""
+msgid "JavaDB is an embedded database that is included with GlassFish, just as HSQLDB is included in JBoss AS."
+msgstr "JavaDB est une base de données embarqué qui est inclue dans dans GlassFish, tout comme HSQLDB est inclue dans JBoss AS."
#. Tag: para
#: Glassfish.xml:66
#, no-c-format
msgid "Now, start the GlassFish server:"
-msgstr ""
+msgstr "Maintenant, démarrez le serveur GlassFish:"
#. Tag: programlisting
#: Glassfish.xml:70
#, no-c-format
msgid "$ bin/asadmin start-domain domain1"
-msgstr ""
+msgstr "$ bin/asadmin start-domain domain1"
#. Tag: para
#: Glassfish.xml:72
#, no-c-format
-msgid ""
-"The web administration console is available at <literal>http://"
-"localhost:4848/</literal>. You can access the web admin console with the "
-"default username (<literal>admin</literal>) and password "
-"(<literal>adminadmin</literal>). We will be using the the admin console to "
-"deploy our examples. You can also copy EAR/WAR files to the "
-"<literal>glassfish/domains/domain1/autodeploy</literal> directory to deploy "
-"them, although we are not going to cover that."
-msgstr ""
+msgid "The web administration console is available at <literal>http://localhost:4848/</literal>. You can access the web admin console with the default username (<literal>admin</literal>) and password (<literal>adminadmin</literal>). We will be using the the admin console to deploy our examples. You can also copy EAR/WAR files to the <literal>glassfish/domains/domain1/autodeploy</literal> directory to deploy them, although we are not going to cover that."
+msgstr "La console web d'administration est disponible à l'adresse <literal>http://localhost:4848/</literal>. Vous pouvez accéder à la console web d'administration avec le nom d'utilisateur par défaut (<literal>admin</literal>) et le mot de passe (<literal>adminadmin</literal>). Nous allons utiliser la console d'administration pour déployer nos exemples. Vous pouvez aussi copier les fichiers EAR/WAR dans le dossier <literal>glassfish/domains/domain1/autodeploy</literal> pour les déployer, mais nous n'allons pas parler de cela."
#. Tag: para
#: Glassfish.xml:82
#, no-c-format
msgid "You can stop the server and database using:"
-msgstr ""
+msgstr "Vous pouvez arrêter le serveur et la base de données en utilisant:"
#. Tag: programlisting
#: Glassfish.xml:86
#, no-c-format
msgid "$ bin/asadmin stop-domain domain1; bin/asadmin stop-database"
-msgstr ""
+msgstr "$ bin/asadmin stop-domain domain1; bin/asadmin stop-database"
#. Tag: title
#: Glassfish.xml:91
#, no-c-format
msgid "The <literal>jee5/booking</literal> example"
-msgstr ""
+msgstr "L'exemple <literal>jee5/booking</literal>"
#. Tag: para
#: Glassfish.xml:93
#, no-c-format
-msgid ""
-"The <literal>jee5/booking</literal> example is based on the Hotel Booking "
-"example (which runs on JBoss AS). Out of the box it is also designed to run "
-"on GlassFish. It is located in <literal>$SEAM_DIST/examples/jee5/booking</"
-"literal>."
-msgstr ""
+msgid "The <literal>jee5/booking</literal> example is based on the Hotel Booking example (which runs on JBoss AS). Out of the box it is also designed to run on GlassFish. It is located in <literal>$SEAM_DIST/examples/jee5/booking</literal>."
+msgstr "L'exemple <literal>jee5/booking</literal> est basé sur l'exemple de réservation d'hotel (qui s'exécute sur JBoss AS). Par défaut, il est aussi prévu de fonctionner sur GlassFish. Il ets localisé dans <literal>$SEAM_DIST/examples/jee5/booking</literal>."
#. Tag: title
#: Glassfish.xml:101
#, no-c-format
msgid "Building the <literal>jee5/booking</literal> example"
-msgstr ""
+msgstr "Compilation de l'exemple <literal>jee5/booking</literal>"
#. Tag: para
#: Glassfish.xml:103
#, no-c-format
-msgid ""
-"To build the example, simply execute the default <literal>ant</literal> "
-"target:"
-msgstr ""
+msgid "To build the example, simply execute the default <literal>ant</literal> target:"
+msgstr "Pour construire l'exemple, exécuter simplement la cible par défaut <literal>ant</literal>:"
#. Tag: programlisting
#: Glassfish.xml:108
#, no-c-format
msgid "$ ant"
-msgstr ""
+msgstr "$ ant"
#. Tag: para
#: Glassfish.xml:110
#, no-c-format
-msgid ""
-"in the <literal>examples/jee5/booking</literal> directory. This will create "
-"the <literal>dist</literal> and <literal>exploded-archives</literal> "
-"directories."
-msgstr ""
+msgid "in the <literal>examples/jee5/booking</literal> directory. This will create the <literal>dist</literal> and <literal>exploded-archives</literal> directories."
+msgstr "dans le dossier <literal>examples/jee5/booking</literal>. Ceci va créer les dossiers <literal>dist</literal> et <literal>exploded-archives</literal>."
#. Tag: title
#: Glassfish.xml:117
#, no-c-format
msgid "Deploying the application to GlassFish"
-msgstr ""
+msgstr "Le déploiement de l'application dans GlassFish"
#. Tag: para
#: Glassfish.xml:119
#, no-c-format
-msgid ""
-"We will deploy the application on GlassFish using the GlassFish admin "
-"console."
-msgstr ""
+msgid "We will deploy the application on GlassFish using the GlassFish admin console."
+msgstr "Nous allons déployer l'application dans GlassFish en utilisant la console d'administration de GlassFish."
#. Tag: para
#: Glassfish.xml:126
#, no-c-format
msgid "Log in to the admin console at <literal>http://localhost:4848</literal>"
-msgstr ""
+msgstr "Connectez vous sur la console d'administration à l'adresse <literal>http://localhost:4848</literal>"
#. Tag: para
#: Glassfish.xml:131
#, no-c-format
-msgid ""
-"Access the <literal>Enterprise Applications</literal> in the menu option "
-"under the <literal>Applications</literal> left side menu."
-msgstr ""
+msgid "Access the <literal>Enterprise Applications</literal> in the menu option under the <literal>Applications</literal> left side menu."
+msgstr "Accédez à <literal>Enterprise Applications</literal> dans le menu option sous <literal>Applications</literal> dans le menu à gauche."
#. Tag: para
#: Glassfish.xml:138
#, no-c-format
-msgid ""
-"At the top of the <literal>Enterprise Application</literal> table select "
-"<literal>Deploy</literal>. Follow through the wizard, using these hints:"
-msgstr ""
+msgid "At the top of the <literal>Enterprise Application</literal> table select <literal>Deploy</literal>. Follow through the wizard, using these hints:"
+msgstr "En haut, le tableau <literal>Enterprise Application</literal> sélectionnez <literal>Deploy</literal>. Suivez l'assistant, en utilisant ces indications:"
#. Tag: literal
-#: Glassfish.xml:146 Glassfish.xml:227
+#: Glassfish.xml:146
+#: Glassfish.xml:227
#, no-c-format
msgid "Preparing for the application installation"
-msgstr ""
+msgstr "La préparation de l'installation de l'application"
#. Tag: para
#: Glassfish.xml:150
#, no-c-format
-msgid ""
-"Browse to <literal>examples/jee5/booking/dist/jboss-seam-jee5.ear</literal>."
-msgstr ""
+msgid "Browse to <literal>examples/jee5/booking/dist/jboss-seam-jee5.ear</literal>."
+msgstr "Navigers vers <literal>examples/jee5/booking/dist/jboss-seam-jee5.ear</literal>."
#. Tag: para
-#: Glassfish.xml:155 Glassfish.xml:238
+#: Glassfish.xml:155
+#: Glassfish.xml:238
#, no-c-format
msgid "Select the <literal>OK</literal> button."
-msgstr ""
+msgstr "Sélectionnez le bouton <literal>OK</literal>."
#. Tag: para
#: Glassfish.xml:164
#, no-c-format
-msgid ""
-"You can now access the application at <literal>http://localhost:8081/seam-"
-"jee5/</literal>."
-msgstr ""
+msgid "You can now access the application at <literal>http://localhost:8081/seam-jee5/</literal>."
+msgstr "Vous pouvez maintenant accéder à l'application sur <literal>http://localhost:8081/seam-jee5/</literal>."
#. Tag: title
#: Glassfish.xml:174
#, no-c-format
msgid "The <literal>jpa</literal> booking example"
-msgstr ""
+msgstr "L'exemple de réservation <literal>jpa</literal>"
#. Tag: para
#: Glassfish.xml:176
#, no-c-format
-msgid ""
-"This is the Hotel Booking example implemented in Seam POJOs and using "
-"Hibernate JPA with JPA transactions. It does not require EJB3 support to run "
-"on application server."
-msgstr ""
+msgid "This is the Hotel Booking example implemented in Seam POJOs and using Hibernate JPA with JPA transactions. It does not require EJB3 support to run on application server."
+msgstr "Ceci est l'exemple de la réservation d'hotel en implémenté en POJOs de Seam et utilisant les transactions JPA avec d'Hibernate JPA. Il ne nécéssite par le support de EJB3 pour s'exécuter sur le serveur d'application."
#. Tag: para
#: Glassfish.xml:182
#, no-c-format
-msgid ""
-"The example already has a break-out of configurations and build scripts for "
-"many of the common containers including GlassFish."
-msgstr ""
+msgid "The example already has a break-out of configurations and build scripts for many of the common containers including GlassFish."
+msgstr "Cet exemple à déjà à disposition les configurations et les scripts de compilation pour la plus part des containeurs y compris GlassFish."
#. Tag: title
#: Glassfish.xml:188
#, no-c-format
msgid "Building the <literal>jpa</literal> example"
-msgstr ""
+msgstr "La construction de l'exemple <literal>jpa</literal>"
#. Tag: para
#: Glassfish.xml:190
#, no-c-format
msgid "To build the example, use the <literal>glassfish</literal> target:"
-msgstr ""
+msgstr "Pour compiler l'exemple, utilisez la cible <literal>glassfish</literal>:"
#. Tag: programlisting
#: Glassfish.xml:194
#, no-c-format
msgid "$ ant glassfish"
-msgstr ""
+msgstr "$ ant glassfish"
#. Tag: para
#: Glassfish.xml:196
#, no-c-format
-msgid ""
-"This will create the container specific <literal>dist-glassfish</literal> "
-"and <literal>exploded-archives-glasfish</literal> directories."
-msgstr ""
+msgid "This will create the container specific <literal>dist-glassfish</literal> and <literal>exploded-archives-glasfish</literal> directories."
+msgstr "Ceci va construire pour le containeur spécifique les dossiers <literal>dist-glassfish</literal> and <literal>exploded-archives-glasfish</literal> "
#. Tag: title
#: Glassfish.xml:203
#, no-c-format
msgid "Deploying the <literal>jpa</literal> example"
-msgstr ""
+msgstr "Le déploiement de l'exemple <literal>jpa</literal>"
#. Tag: para
#: Glassfish.xml:205
#, no-c-format
-msgid ""
-"This is very similar to the <literal>jee5</literal> example at <xref linkend="
-"\"jee5-glassfish-deploy\"/> except that this is a <literal>war</literal> and "
-"not an <literal>ear</literal>."
-msgstr ""
+msgid "This is very similar to the <literal>jee5</literal> example at <xref linkend=\"jee5-glassfish-deploy\"/> except that this is a <literal>war</literal> and not an <literal>ear</literal>."
+msgstr "Ceci est très similaire à l'exemple <literal>jee5</literal> à voir <xref linkend=\"jee5-glassfish-deploy\"/> exception faire que c'est un <literal>war</literal> et non un <literal>ear</literal>."
#. Tag: para
#: Glassfish.xml:213
#, no-c-format
msgid "Log in to the administration console:"
-msgstr ""
+msgstr "Connectez vous à la console d'administraiton:"
#. Tag: programlisting
#: Glassfish.xml:216
#, no-c-format
msgid "http://localhost:4848"
-msgstr ""
+msgstr "http://localhost:4848"
#. Tag: para
#: Glassfish.xml:219
#, no-c-format
-msgid ""
-"Access the <literal>Web Applications</literal> in the menu option under the "
-"<literal>Applications</literal> left side menu."
-msgstr ""
+msgid "Access the <literal>Web Applications</literal> in the menu option under the <literal>Applications</literal> left side menu."
+msgstr "Accédez au <literal>Web Applications</literal> dans le menu d'option sous <literal>Applications</literal> dans le menu de gauche."
#. Tag: para
#: Glassfish.xml:233
#, no-c-format
-msgid ""
-"Browse to <literal>examples/jpa/dist-glassfish/jboss-seam-jpa.war</literal>."
-msgstr ""
+msgid "Browse to <literal>examples/jpa/dist-glassfish/jboss-seam-jpa.war</literal>."
+msgstr "Navigez vers <literal>examples/jpa/dist-glassfish/jboss-seam-jpa.war</literal>."
#. Tag: para
#: Glassfish.xml:245
#, no-c-format
-msgid ""
-"You can now access the application at <literal>http://localhost:8081/jboss-"
-"seam-jpa/</literal>."
-msgstr ""
+msgid "You can now access the application at <literal>http://localhost:8081/jboss-seam-jpa/</literal>."
+msgstr "Vous pouvez maintenant accéder à l'application sur <literal>http://localhost:8081/jboss-seam-jpa/</literal>."
#. Tag: title
#: Glassfish.xml:255
#, no-c-format
msgid "Using Derby instead of Hypersonic SQL DB"
-msgstr ""
+msgstr "En utilisant Derby au lieur d'Hypersonic SQL DB"
#. Tag: note
#: Glassfish.xml:255
#, no-c-format
-msgid ""
-"In order for the app to work out of the box with GlassFish, we have used the "
-"Derby (aka JavaDB) database in GlassFish. However, we strongly recommend "
-"that you use another database (e.g. HSQL). <literal>examples/jpa/resources-"
-"glassfish/WEB-INF/classes/GlassfishDerbyDialect.class</literal> is a hack to "
-"get around a Derby bug in GlassFish server. You must use it as your "
-"Hibernate dialect if you use Derby with GlassFish."
-msgstr ""
+msgid "In order for the app to work out of the box with GlassFish, we have used the Derby (aka JavaDB) database in GlassFish. However, we strongly recommend that you use another database (e.g. HSQL). <literal>examples/jpa/resources-glassfish/WEB-INF/classes/GlassfishDerbyDialect.class</literal> is a hack to get around a Derby bug in GlassFish server. You must use it as your Hibernate dialect if you use Derby with GlassFish."
+msgstr "Pour que l'application fonctionne immédiatement avec GlassFish, nous avons utilisé la base de données Derby (aussi connu JavaDB) dans GlassFish. Cependant, nous recommandons particulièrement d'utiliser une autre base de données (par exemple HSQL). <literal>examples/jpa/resources-glassfish/WEB-INF/classes/GlassfishDerbyDialect.class</literal> est un truc pour contourner un bug de Derby dans le serveur GlassFish. Vous devez l'utiliser comme dialecte Hibernate, si vous utilisez Derby avec GlassFish."
#. Tag: title
#: Glassfish.xml:267
#, no-c-format
msgid "What's different for GlassFish v2 UR2"
-msgstr ""
+msgstr "Ce qui est différent pour GlassFish v2 UR2"
#. Tag: para
#: Glassfish.xml:271
#, no-c-format
msgid "<para>Configuration file changes</para>"
-msgstr ""
+msgstr "<para>Configuration file changes</para>"
#. Tag: para
#: Glassfish.xml:276
#, no-c-format
-msgid ""
-"<literal>META-INF/persistence.xml</literal> — the main changes needed are "
-"the datasource JNDI, switching to the GlassFish transaction manager lookup "
-"class, and changing the hibernate dialect to be "
-"<literal>GlassfishDerbyDialect</literal>."
-msgstr ""
+msgid "<literal>META-INF/persistence.xml</literal> — the main changes needed are the datasource JNDI, switching to the GlassFish transaction manager lookup class, and changing the hibernate dialect to be <literal>GlassfishDerbyDialect</literal>."
+msgstr "<literal>META-INF/persistence.xml</literal> — le principal changement nécéssaire est le datasource JNDI, le basculement vers la classe de scrutation du gestionnaire de transaction de GlassFish , et en changeant le dialecte d'hibernate pour <literal>GlassfishDerbyDialect</literal>."
#. Tag: para
#: Glassfish.xml:285
#, no-c-format
-msgid ""
-"<literal>WEB-INF/classes/GlassfishDerbyDialect.class</literal> — this class "
-"is needed for the Hibernate dialect change to "
-"<literal>GlassfishDerbyDialect</literal>"
-msgstr ""
+msgid "<literal>WEB-INF/classes/GlassfishDerbyDialect.class</literal> — this class is needed for the Hibernate dialect change to <literal>GlassfishDerbyDialect</literal>"
+msgstr "<literal>WEB-INF/classes/GlassfishDerbyDialect.class</literal> — cette classe est nécesssaire pour que le dialecte d'Hibernate soit changé en <literal>GlassfishDerbyDialect</literal>"
#. Tag: para
#: Glassfish.xml:292
#, no-c-format
-msgid ""
-"<literal>import.sql</literal> — either for the dialect or Derby DB the "
-"<literal>ID</literal> column can not be populated by this file and was "
-"removed."
-msgstr ""
+msgid "<literal>import.sql</literal> — either for the dialect or Derby DB the <literal>ID</literal> column can not be populated by this file and was removed."
+msgstr "<literal>import.sql</literal> — tout comme pour le dialecte la colonne <literal>ID</literal> de Derby DB ne peut être remplie par ce fichier et a été retiré."
#. Tag: title
#: Glassfish.xml:305
#, no-c-format
-msgid ""
-"Deploying an application generated by <literal>seam-gen</literal> on "
-"GlassFish v2 UR2"
-msgstr ""
+msgid "Deploying an application generated by <literal>seam-gen</literal> on GlassFish v2 UR2"
+msgstr "Le déploiement d'une application générée par <literal>seam-gen</literal> sur GlassFish v2 UR2"
#. Tag: para
#: Glassfish.xml:307
#, no-c-format
-msgid ""
-"<literal>seam-gen</literal> is a very useful tool for developers to quickly "
-"get an application up and running, and provides a foundation to add your own "
-"functionality. Out of box <literal>seam-gen</literal> will produce "
-"applications configured to run on JBoss AS. These instructions will show the "
-"steps needed to get it to run on GlassFish."
-msgstr ""
+msgid "<literal>seam-gen</literal> is a very useful tool for developers to quickly get an application up and running, and provides a foundation to add your own functionality. Out of box <literal>seam-gen</literal> will produce applications configured to run on JBoss AS. These instructions will show the steps needed to get it to run on GlassFish."
+msgstr "<literal>seam-gen</literal> est un outil très utile pour les développeurs qui rapidement ont une application opérationnelle et s'exécutant et fourni des fondations pour ajouter vos fonctionnalités. Par défaut<literal>seam-gen</literal> va poduire des applications configurés pour s'exécuter sur JBoss AS. Ces instructions vont montrer les étapes nécéssaire poiyr les avoir pour GlassFish."
#. Tag: title
#: Glassfish.xml:316
#, no-c-format
msgid "Running <literal>seam-gen</literal> Setup"
-msgstr ""
+msgstr "Exécution du configurateur <literal>seam-gen</literal>"
#. Tag: para
#: Glassfish.xml:318
#, no-c-format
-msgid ""
-"The first step is setting up <literal>seam-gen</literal> to construct the "
-"base project. There are several choices made below, specifically the "
-"datasource and hibernate values that we will adjust once the project is "
-"created."
-msgstr ""
+msgid "The first step is setting up <literal>seam-gen</literal> to construct the base project. There are several choices made below, specifically the datasource and hibernate values that we will adjust once the project is created."
+msgstr "La première étape est de configurer <literal>seam-gen</literal> pour construire le projet de base. Ils ya plusieurs choix à faire plus bas, particulièrement poiyr le datasource et les valeurs d'hibernate que nous allons modifier une fois que le projet a été créé."
#. Tag: programlisting
#: Glassfish.xml:325
@@ -533,181 +458,235 @@
"BUILD SUCCESSFUL\n"
"Total time: 4 minutes 5 seconds]]>"
msgstr ""
+"<![CDATA[$ ./seam setup\n"
+"Buildfile: build.xml\n"
+"\n"
+"init:\n"
+"\n"
+"setup:\n"
+"[echo] Welcome to seam-gen :-)\n"
+"[input] Enter your Java project workspace (the directory that contains your\n"
+"Seam projects) [C:/Projects] [C:/Projects]\n"
+"/projects\n"
+"[input] Enter your JBoss home directory [C:/Program Files/jboss-4.2.3.GA]\n"
+"[C:/Program Files/jboss-4.2.3.GA]\n"
+"\n"
+"[input] Enter the project name [myproject] [myproject]\n"
+"seamgen_example\n"
+"[echo] Accepted project name as: seamgen_example\n"
+"[input] Do you want to use ICEfaces instead of RichFaces [n] (y, [n])\n"
+"\n"
+"[input] skipping input as property icefaces.home.new has already\n"
+"been set.\n"
+"[input] Select a RichFaces skin [blueSky] ([blueSky], classic, ruby, wine,\n"
+"deepMarine, emeraldTown, japanCherry, DEFAULT)\n"
+"\n"
+"[input] Is this project deployed as an EAR (with EJB components) or a WAR\n"
+"(with no EJB support) [ear] ([ear], war)\n"
+"\n"
+"[input] Enter the Java package name for your session beans\n"
+"[com.mydomain.seamgen_example] [com.mydomain.seamgen_example]\n"
+"org.jboss.seam.tutorial.glassfish.action\n"
+"[input] Enter the Java package name for your entity beans\n"
+"[org.jboss.seam.tutorial.glassfish.action]\n"
+"[org.jboss.seam.tutorial.glassfish.action]\n"
+"org.jboss.seam.tutorial.glassfish.model\n"
+"[input] Enter the Java package name for your test cases\n"
+"[org.jboss.seam.tutorial.glassfish.action.test]\n"
+"[org.jboss.seam.tutorial.glassfish.action.test]\n"
+"org.jboss.seam.tutorial.glassfish.test\n"
+"[input] What kind of database are you using? [hsql] ([hsql], mysql, oracle,\n"
+"postgres, mssql, db2, sybase, enterprisedb, h2)\n"
+"\n"
+"[input] Enter the Hibernate dialect for your database\n"
+"[org.hibernate.dialect.HSQLDialect]\n"
+"[org.hibernate.dialect.HSQLDialect]\n"
+"\n"
+"[input] Enter the filesystem path to the JDBC driver jar\n"
+"[/tmp/seam/lib/hsqldb.jar] [/tmp/seam/lib/hsqldb.jar]\n"
+"\n"
+"[input] Enter JDBC driver class for your database [org.hsqldb.jdbcDriver]\n"
+"[org.hsqldb.jdbcDriver]\n"
+"\n"
+"[input] Enter the JDBC URL for your database [jdbc:hsqldb:.]\n"
+"[jdbc:hsqldb:.]\n"
+"\n"
+"[input] Enter database username [sa] [sa]\n"
+"\n"
+"[input] Enter database password [] []\n"
+"\n"
+"[input] Enter the database schema name (it is OK to leave this blank) [] []\n"
+"\n"
+"[input] Enter the database catalog name (it is OK to leave this\n"
+"blank) [] []\n"
+"\n"
+"[input] Are you working with tables that already exist in the database? [n]\n"
+"(y, [n])\n"
+"\n"
+"[input] Do you want to drop and recreate the database tables and data in\n"
+"import.sql each time you deploy? [n] (y, [n])\n"
+"\n"
+"[propertyfile] Creating new property file:\n"
+"/home/mnovotny/workspaces/jboss/jboss-seam/seam-gen/build.properties\n"
+"[echo] Installing JDBC driver jar to JBoss server\n"
+"[copy] Copying 1 file to\n"
+"/home/mnovotny/workspaces/jboss/jboss-seam/seam-gen/C:/Program\n"
+"Files/jboss-4.2.3.GA/server/default/lib\n"
+"[echo] Type 'seam create-project' to create the new project\n"
+"\n"
+"BUILD SUCCESSFUL\n"
+"Total time: 4 minutes 5 seconds]]>"
#. Tag: para
#: Glassfish.xml:327
#, no-c-format
-msgid ""
-"Type <literal>$ ./seam new-project</literal> to create your project and then "
-"<literal>cd /projects/seamgen_example</literal> to the newly created "
-"structure."
-msgstr ""
+msgid "Type <literal>$ ./seam new-project</literal> to create your project and then <literal>cd /projects/seamgen_example</literal> to the newly created structure."
+msgstr "Entrez <literal>$ ./seam new-project</literal> pour créer votre projet et ensuite <literal>cd /projects/seamgen_example</literal> pour aller dans la structure nouvellement créée."
#. Tag: title
#: Glassfish.xml:335
#, no-c-format
msgid "Changes needed for deployment to GlassFish"
-msgstr ""
+msgstr "Les modifications nécéssaires pour le déploiement dans GlassFish"
#. Tag: para
#: Glassfish.xml:337
#, no-c-format
msgid "We now need to make some changes to the generated project."
-msgstr ""
+msgstr "Nous allons maintenant faire quelques modificaitions dans le projet généré."
#. Tag: title
#: Glassfish.xml:342
#, no-c-format
msgid "<title>Configuration file changes</title>"
-msgstr ""
+msgstr "<title>Configuration file changes</title>"
#. Tag: literal
#: Glassfish.xml:347
#, no-c-format
msgid "resources/META-INF/persistence-dev.xml"
-msgstr ""
+msgstr "resources/META-INF/persistence-dev.xml"
#. Tag: para
#: Glassfish.xml:353
#, no-c-format
-msgid ""
-"Alter the <literal>jta-data-source</literal> to be <literal>jdbc/__default</"
-"literal>. We are going to be using the integrated GlassFish Derby DB."
-msgstr ""
+msgid "Alter the <literal>jta-data-source</literal> to be <literal>jdbc/__default</literal>. We are going to be using the integrated GlassFish Derby DB."
+msgstr "Modifiez le <literal>jta-data-source</literal> pour le mettre à <literal>jdbc/__default</literal>. Nous allons utiliser Derby DB intégré dans GlassFish."
#. Tag: para
#: Glassfish.xml:360
#, no-c-format
-msgid ""
-"Replace all of the properties with the following. The key differences are "
-"briefly described in <xref linkend=\"glassfish_jpa_diff\"/>:"
-msgstr ""
+msgid "Replace all of the properties with the following. The key differences are briefly described in <xref linkend=\"glassfish_jpa_diff\"/>:"
+msgstr "Modifiez les propriétés avec les suivantes. Les différences clefs sont brièvements décrites dans <xref linkend=\"glassfish_jpa_diff\"/>:"
#. Tag: programlisting
#: Glassfish.xml:365
#, no-c-format
msgid ""
-"<![CDATA[<property name=\"hibernate.dialect\" value=\"GlassfishDerbyDialect"
-"\"/>\n"
+"<![CDATA[<property name=\"hibernate.dialect\" value=\"GlassfishDerbyDialect\"/>\n"
"<property name=\"hibernate.hbm2ddl.auto\" value=\"update\"/>\n"
"<property name=\"hibernate.show_sql\" value=\"true\"/>\n"
"<property name=\"hibernate.format_sql\" value=\"true\"/>\n"
-"<property name=\"hibernate.cache.provider_class\" value=\"org.hibernate."
-"cache.HashtableCacheProvider\"/>\n"
-"<property name=\"hibernate.transaction.manager_lookup_class\" value=\"org."
-"hibernate.transaction.SunONETransactionManagerLookup\"/>]]>"
+"<property name=\"hibernate.cache.provider_class\" value=\"org.hibernate.cache.HashtableCacheProvider\"/>\n"
+"<property name=\"hibernate.transaction.manager_lookup_class\" value=\"org.hibernate.transaction.SunONETransactionManagerLookup\"/>]]>"
msgstr ""
+"<![CDATA[<property name=\"hibernate.dialect\" value=\"GlassfishDerbyDialect\"/>\n"
+"<property name=\"hibernate.hbm2ddl.auto\" value=\"update\"/>\n"
+"<property name=\"hibernate.show_sql\" value=\"true\"/>\n"
+"<property name=\"hibernate.format_sql\" value=\"true\"/>\n"
+"<property name=\"hibernate.cache.provider_class\" value=\"org.hibernate.cache.HashtableCacheProvider\"/>\n"
+"<property name=\"hibernate.transaction.manager_lookup_class\" value=\"org.hibernate.transaction.SunONETransactionManagerLookup\"/>]]>"
#. Tag: para
#: Glassfish.xml:368
#, no-c-format
-msgid ""
-"You'll need to alter <literal>persistence-prod.xml</literal> as well if you "
-"want to deploy to GlassFish using the prod profile."
-msgstr ""
+msgid "You'll need to alter <literal>persistence-prod.xml</literal> as well if you want to deploy to GlassFish using the prod profile."
+msgstr "Nous allons avoir besoin de modifier <literal>persistence-prod.xml</literal> aussi si vous voulez deployer dans GlassFish en utilisant le profile de prod."
#. Tag: literal
#: Glassfish.xml:380
#, no-c-format
msgid "resources/GlassfishDerbyDialect.class"
-msgstr ""
+msgstr "resources/GlassfishDerbyDialect.class"
#. Tag: para
#: Glassfish.xml:383
#, no-c-format
-msgid ""
-"As with other examples we need to include this class for DB support. It can "
-"be copied from the <literal>jpa</literal> example into the "
-"<literal>seamgen_example/resources</literal> directory."
-msgstr ""
+msgid "As with other examples we need to include this class for DB support. It can be copied from the <literal>jpa</literal> example into the <literal>seamgen_example/resources</literal> directory."
+msgstr "Tout comme les autres exemples, nous allons avoir besoin d'inclure cette classe pour le support de la BD. Il peut être copie depuis l'exemple <literal>jpa</literal> dans le dossier <literal>seamgen_example/resources</literal>."
#. Tag: programlisting
#: Glassfish.xml:389
#, no-c-format
msgid ""
"$ cp \\ \n"
-"$SEAM_DIST/examples/jpa/resources-glassfish/WEB-INF/classes/"
-"GlassfishDerbyDialect.class \\ \n"
+"$SEAM_DIST/examples/jpa/resources-glassfish/WEB-INF/classes/GlassfishDerbyDialect.class \\ \n"
"./resources"
msgstr ""
+"$ cp \\ \n"
+"$SEAM_DIST/examples/jpa/resources-glassfish/WEB-INF/classes/GlassfishDerbyDialect.class \\ \n"
+"./resources"
#. Tag: literal
#: Glassfish.xml:394
#, no-c-format
msgid "resources/META-INF/jboss-app.xml"
-msgstr ""
+msgstr "resources/META-INF/jboss-app.xml"
#. Tag: para
#: Glassfish.xml:397
#, no-c-format
-msgid ""
-"You can delete this file as we aren't deploying to JBoss AS (<literal>jboss-"
-"app.xml</literal> is used to enable classloading isolation in JBoss AS)"
-msgstr ""
+msgid "You can delete this file as we aren't deploying to JBoss AS (<literal>jboss-app.xml</literal> is used to enable classloading isolation in JBoss AS)"
+msgstr "Vous pouvez effacer ce fichier car nous n'allons pas déployer vers JBoss AS (<literal>jboss-app.xml</literal>est utilisé pour activer l'isolation du chargement des classes dans JBoss AS)"
#. Tag: literal
#: Glassfish.xml:406
#, no-c-format
msgid "resources/*-ds.xml"
-msgstr ""
+msgstr "resources/*-ds.xml"
#. Tag: para
#: Glassfish.xml:409
#, no-c-format
-msgid ""
-"You can delete these file as we aren't deploying to JBoss AS (these files "
-"define data sources in JBoss AS, we are using GlassFish's default data "
-"source)"
-msgstr ""
+msgid "You can delete these file as we aren't deploying to JBoss AS (these files define data sources in JBoss AS, we are using GlassFish's default data source)"
+msgstr "Vous pouvez effacer ces fichiers nous n'allons pas déployer vers JBoss AS (ces fichiers définissent des sources de données dans JBoss AS, nous allons utiliser la source de données par défaut de GlassFish)"
#. Tag: literal
#: Glassfish.xml:418
#, no-c-format
msgid "resources/WEB-INF/components.xml"
-msgstr ""
+msgstr "resources/WEB-INF/components.xml"
#. Tag: para
#: Glassfish.xml:423
#, no-c-format
-msgid ""
-"Enable container managed transaction integration - add the <literal><![CDATA"
-"[<transaction:ejb-transaction/>]]></literal> component, and it's namespace "
-"declaration <literal>xmlns:transaction=\"http://jboss.com/products/seam/"
-"transaction\"</literal>"
-msgstr ""
+msgid "Enable container managed transaction integration - add the <literal><![CDATA[<transaction:ejb-transaction/>]]></literal> component, and it's namespace declaration <literal>xmlns:transaction=\"http://jboss.com/products/seam/transaction\"</literal>"
+msgstr "Active l'intégration des transactions du containeur géré - ajoutez le composant <literal><![CDATA[<transaction:ejb-transaction/>]]></literal> et sa déclaration d'espace de nom <literal>xmlns:transaction=\"http://jboss.com/products/seam/transaction\"</literal>"
#. Tag: para
#: Glassfish.xml:431
#, no-c-format
-msgid ""
-"Alter the <literal>jndi-pattern</literal> to <literal>java:comp/env/"
-"seamgen_example/#{ejbName}</literal>"
-msgstr ""
+msgid "Alter the <literal>jndi-pattern</literal> to <literal>java:comp/env/seamgen_example/#{ejbName}</literal>"
+msgstr "Modifiez le <literal>jndi-pattern</literal> à <literal>java:comp/env/seamgen_example/#{ejbName}</literal>"
#. Tag: literal
#: Glassfish.xml:441
#, no-c-format
msgid "resources/WEB-INF/web.xml"
-msgstr ""
+msgstr "resources/WEB-INF/web.xml"
#. Tag: para
#: Glassfish.xml:444
#, no-c-format
-msgid ""
-"As with the <literal>jee5/booking</literal> example, we need to add EJB "
-"references to web.xml. Technically, the reference type is not required, but "
-"we add it here for good measure. Note that these references require the "
-"presence of an empty <literal>local-home</literal> element to retain "
-"compatibility with a JBoss AS 4.x deployment."
-msgstr ""
+msgid "As with the <literal>jee5/booking</literal> example, we need to add EJB references to web.xml. Technically, the reference type is not required, but we add it here for good measure. Note that these references require the presence of an empty <literal>local-home</literal> element to retain compatibility with a JBoss AS 4.x deployment."
+msgstr "Avez l'exemple <literal>jee5/booking</literal>, nous allons avoir besoin d'ajouter les références EJB references à web.xml. Techniquement, le type de référence n'est pas requi, mais nous l'ajoutons ici pour faire bonne figure. Notez que ces références nécéssitent la présence d'un élément vide <literal>local-home</literal> pour conserver la compatibilité avec un déploiement JBoss AS 4.x."
#. Tag: programlisting
#: Glassfish.xml:453
#, no-c-format
msgid ""
"<![CDATA[<ejb-local-ref> \n"
-" <ejb-ref-name>seamgen_example/AuthenticatorAction</ejb-ref-"
-"name> \n"
+" <ejb-ref-name>seamgen_example/AuthenticatorAction</ejb-ref-name> \n"
" <ejb-ref-type>Session</ejb-ref-type> \n"
" <local-home/>\n"
" <local>org.jboss.seam.tutorial.glassfish.action.Authenticator</local> \n"
@@ -720,26 +699,32 @@
" <local>org.jboss.seam.transaction.LocalEjbSynchronizations</local>\n"
" </ejb-local-ref>]]>"
msgstr ""
+"<![CDATA[<ejb-local-ref> \n"
+" <ejb-ref-name>seamgen_example/AuthenticatorAction</ejb-ref-name> \n"
+" <ejb-ref-type>Session</ejb-ref-type> \n"
+" <local-home/>\n"
+" <local>org.jboss.seam.tutorial.glassfish.action.Authenticator</local> \n"
+" </ejb-local-ref>\n"
+" \n"
+" <ejb-local-ref>\n"
+" <ejb-ref-name>seamgen_example/EjbSynchronizations</ejb-ref-name> \n"
+" <ejb-ref-type>Session</ejb-ref-type>\n"
+" <local-home/>\n"
+" <local>org.jboss.seam.transaction.LocalEjbSynchronizations</local>\n"
+" </ejb-local-ref>]]>"
#. Tag: para
#: Glassfish.xml:454
#, no-c-format
-msgid ""
-"Keep in mind that if you are deploying to JBoss AS 4.x, and have defined the "
-"EJB references shown above in your web.xml, you will need to also define "
-"local JNDI names for each of them in jboss-web.xml, as shown below. This "
-"step is not required when deploying to GlassFish, but it's mentioned here in "
-"case you are also deploying the application to JBoss AS 4.x (not required "
-"for JBoss AS 5)."
-msgstr ""
+msgid "Keep in mind that if you are deploying to JBoss AS 4.x, and have defined the EJB references shown above in your web.xml, you will need to also define local JNDI names for each of them in jboss-web.xml, as shown below. This step is not required when deploying to GlassFish, but it's mentioned here in case you are also deploying the application to JBoss AS 4.x (not required for JBoss AS 5)."
+msgstr "Gardez à l'esprit que si vous déployer dans JBoss AS 4.x, et que vous avez défini les références EJB comme montrées ci-dessus dans votre web.xml, vous allez avoir aussi besoin de définir les noms JNDI locaux de chacun d'entre eux dans jboss-web.xml, comme montré ci-dessous. Cette étape n'est pas nécéssaire avec le déploiement dans GlassFish, mais elle est mentionnée ici dans le cas où vous voudriez aussi déployer lapplication dans JBoss AS 4.x (pas nécéssaire pour JBoss AS 5)."
#. Tag: programlisting
#: Glassfish.xml:463
#, no-c-format
msgid ""
"<![CDATA[<ejb-local-ref> \n"
-" <ejb-ref-name>seamgen_example/AuthenticatorAction</ejb-ref-"
-"name> \n"
+" <ejb-ref-name>seamgen_example/AuthenticatorAction</ejb-ref-name> \n"
" <local-jndi-name>AuthenticatorAction</local-jndi-name> \n"
" </ejb-local-ref>\n"
" \n"
@@ -748,46 +733,45 @@
" <local-jndi-name>EjbSynchronizations</local-jndi-name>\n"
" </ejb-local-ref>]]>"
msgstr ""
+"<![CDATA[<ejb-local-ref> \n"
+" <ejb-ref-name>seamgen_example/AuthenticatorAction</ejb-ref-name> \n"
+" <local-jndi-name>AuthenticatorAction</local-jndi-name> \n"
+" </ejb-local-ref>\n"
+" \n"
+" <ejb-local-ref>\n"
+" <ejb-ref-name>seamgen_example/EjbSynchronizations</ejb-ref-name> \n"
+" <local-jndi-name>EjbSynchronizations</local-jndi-name>\n"
+" </ejb-local-ref>]]>"
#. Tag: title
#: Glassfish.xml:470
#, no-c-format
msgid "Creating the <literal>AuthenticatorAction</literal> EJB"
-msgstr ""
+msgstr "La création de l'EJB <literal>AuthenticatorAction</literal>"
#. Tag: para
#: Glassfish.xml:472
#, no-c-format
-msgid ""
-"We want to take the existing <literal>Authenticator</literal> Seam POJO "
-"component and create an EJB3 out of it."
-msgstr ""
+msgid "We want to take the existing <literal>Authenticator</literal> Seam POJO component and create an EJB3 out of it."
+msgstr "Nous voulons prendre le composant POJO de Seam existant <literal>Authenticator</literal> et créer un EJB à l'extérieur de lui."
#. Tag: para
#: Glassfish.xml:481
#, no-c-format
msgid "Rename the class to <literal>AuthenticatorAction</literal>"
-msgstr ""
+msgstr "Renommer la classe en <literal>AuthenticatorAction</literal>"
#. Tag: para
#: Glassfish.xml:488
#, no-c-format
-msgid ""
-"Add the <literal>@Stateless</literal> annotation to the new "
-"<literal>AuthenticatorAction</literal> class."
-msgstr ""
+msgid "Add the <literal>@Stateless</literal> annotation to the new <literal>AuthenticatorAction</literal> class."
+msgstr "Ajoutez l'annotation <literal>@Stateless</literal> à la nouvelle classe <literal>AuthenticatorAction</literal>."
#. Tag: para
#: Glassfish.xml:495
#, no-c-format
-msgid ""
-"Create an interface called <literal>Authenticator</literal> which "
-"<literal>AuthenticatorAction</literal> implements (EJB3 requires session "
-"beans to have a local interface). Annotate the interface with "
-"<literal>@Local</literal>, and add a single method with same signature as "
-"the <literal>authenticate</literal> in <literal>AuthenticatorAction</"
-"literal>."
-msgstr ""
+msgid "Create an interface called <literal>Authenticator</literal> which <literal>AuthenticatorAction</literal> implements (EJB3 requires session beans to have a local interface). Annotate the interface with <literal>@Local</literal>, and add a single method with same signature as the <literal>authenticate</literal> in <literal>AuthenticatorAction</literal>."
+msgstr "Créer un interface appelé <literal>Authenticator</literal> qui implémente <literal>AuthenticatorAction</literal> (EJB3 nécéssite pour les beans de session d'avoir un interface local). Annotez l'interface avec <literal>@Local</literal>, et ajoutez une seule méthode avec la même signature que <literal>authenticate</literal> dans <literal>AuthenticatorAction</literal>."
#. Tag: programlisting
#: Glassfish.xml:508
@@ -797,6 +781,9 @@
"@Stateless\n"
"public class AuthenticatorAction implements Authenticator {]]>"
msgstr ""
+"<![CDATA[@Name(\"authenticator\") \n"
+"@Stateless\n"
+"public class AuthenticatorAction implements Authenticator {]]>"
#. Tag: programlisting
#: Glassfish.xml:510
@@ -808,61 +795,53 @@
" public boolean authenticate(); \n"
"}]]>"
msgstr ""
+"<![CDATA[@Local\n"
+"public interface Authenticator { \n"
+"\n"
+" public boolean authenticate(); \n"
+"}]]>"
#. Tag: para
#: Glassfish.xml:514
#, no-c-format
-msgid ""
-"We've already added its reference to the <literal>web.xml</literal> file so "
-"we are good to go."
-msgstr ""
+msgid "We've already added its reference to the <literal>web.xml</literal> file so we are good to go."
+msgstr "Vous avons déjà ajouté sa référence au fichier <literal>web.xml</literal> donc nous pouvons continuer."
#. Tag: title
#: Glassfish.xml:523
#, no-c-format
-msgid ""
-"Extra jar dependencies and other changes to the <literal>build.xml</literal>"
-msgstr ""
+msgid "Extra jar dependencies and other changes to the <literal>build.xml</literal>"
+msgstr "Les dépendances jar additionnelles et les autres modification au <literal>build.xml</literal>"
#. Tag: para
#: Glassfish.xml:528
#, no-c-format
-msgid ""
-"This application has similar requirements as the <literal>jee5/booking</"
-"literal> example."
-msgstr ""
+msgid "This application has similar requirements as the <literal>jee5/booking</literal> example."
+msgstr "Cette application a des besoins similaires à l'exemple <literal>jee5/booking</literal>."
#. Tag: para
#: Glassfish.xml:534
#, no-c-format
-msgid ""
-"Change the default target to <literal>archive</literal> (we aren't going to "
-"cover automatic deployment to GlassFish)."
-msgstr ""
+msgid "Change the default target to <literal>archive</literal> (we aren't going to cover automatic deployment to GlassFish)."
+msgstr "Modifiez la cible par défaut à <literal>archive</literal> (nous n'allons pas couvrir le déploiement automatique vers GlassFish)."
#. Tag: programlisting
#: Glassfish.xml:539
#, no-c-format
-msgid ""
-"<![CDATA[<project name=\"seamgen_example\" default=\"archive\" basedir=\"."
-"\">]]>"
-msgstr ""
+msgid "<![CDATA[<project name=\"seamgen_example\" default=\"archive\" basedir=\".\">]]>"
+msgstr "<![CDATA[<project name=\"seamgen_example\" default=\"archive\" basedir=\".\">]]>"
#. Tag: para
#: Glassfish.xml:542
#, no-c-format
-msgid ""
-"We need to get the <literal>GlassfishDerbyDialect.class</literal> into our "
-"application jar. To do that find the <literal>jar</literal> task and add the "
-"<literal>GlassfishDerbyDialect.class</literal> line as shown below:"
-msgstr ""
+msgid "We need to get the <literal>GlassfishDerbyDialect.class</literal> into our application jar. To do that find the <literal>jar</literal> task and add the <literal>GlassfishDerbyDialect.class</literal> line as shown below:"
+msgstr "Nous alllons avoir besoin de <literal>GlassfishDerbyDialect.class</literal> dans notre jar d'application. Pour faire cela, trouvez la tâche <literal>jar</literal> et ajoutez la ligne <literal>GlassfishDerbyDialect.class</literal> comme montré ci-dessous:"
#. Tag: programlisting
#: Glassfish.xml:549
#, no-c-format
msgid ""
-"<![CDATA[<target name=\"jar\" depends=\"compile,copyclasses\" description="
-"\"Build the distribution .jar file\">\n"
+"<![CDATA[<target name=\"jar\" depends=\"compile,copyclasses\" description=\"Build the distribution .jar file\">\n"
" <copy todir=\"${jar.dir}\">\n"
" <fileset dir=\"${basedir}/resources\">\n"
" <include name=\"seam.properties\" />\n"
@@ -872,22 +851,27 @@
" </copy>\n"
" ...]]>"
msgstr ""
+"<![CDATA[<target name=\"jar\" depends=\"compile,copyclasses\" description=\"Build the distribution .jar file\">\n"
+" <copy todir=\"${jar.dir}\">\n"
+" <fileset dir=\"${basedir}/resources\">\n"
+" <include name=\"seam.properties\" />\n"
+" <include name=\"*.drl\" />\n"
+" <include name=\"GlassfishDerbyDialect.class\" />\n"
+" </fileset> \n"
+" </copy>\n"
+" ...]]>"
#. Tag: para
#: Glassfish.xml:552
#, no-c-format
-msgid ""
-"Now we need to get extra jars into the <literal>ear</literal> file. Look for "
-"the <literal><![CDATA[<copy todir=\"${ear.dir}/lib\">]]></literal> section "
-"of the <literal>ear</literal> target. Add the following to the child "
-"<literal><![CDATA[<fileset dir=\"${lib.dir}\">]]></literal> element."
-msgstr ""
+msgid "Now we need to get extra jars into the <literal>ear</literal> file. Look for the <literal><![CDATA[<copy todir=\"${ear.dir}/lib\">]]></literal> section of the <literal>ear</literal> target. Add the following to the child <literal><![CDATA[<fileset dir=\"${lib.dir}\">]]></literal> element."
+msgstr "Maintenant nous allons avoir besoin d'ajouter les jars additionnel dans le fichier <literal>ear</literal>. Regarez dans la section <literal><![CDATA[<copy todir=\"${ear.dir}/lib\">]]></literal> de la cible <literal>ear</literal>. Ajoutez ce qui suit à l'enfant de l'élément <literal><![CDATA[<fileset dir=\"${lib.dir}\">]]></literal>."
#. Tag: para
#: Glassfish.xml:565
#, no-c-format
msgid "Add Hibernate dependencies"
-msgstr ""
+msgstr "Ajoutez les dépendances Hibernate"
#. Tag: programlisting
#: Glassfish.xml:566
@@ -901,12 +885,19 @@
"<include name=\"hibernate-validator.jar\"/>\n"
"<include name=\"jboss-common-core.jar\"/>]]>"
msgstr ""
+"<![CDATA[<!-- Hibernate and deps --> \n"
+"<include name=\"hibernate.jar\"/>\n"
+"<include name=\"hibernate-commons-annotations.jar\"/>\n"
+"<include name=\"hibernate-annotations.jar\"/>\n"
+"<include name=\"hibernate-entitymanager.jar\"/>\n"
+"<include name=\"hibernate-validator.jar\"/>\n"
+"<include name=\"jboss-common-core.jar\"/>]]>"
#. Tag: para
#: Glassfish.xml:569
#, no-c-format
msgid "Add third party dependencies."
-msgstr ""
+msgstr "Ajoutez les dépendances des tierces parties."
#. Tag: programlisting
#: Glassfish.xml:570
@@ -922,12 +913,21 @@
"<include name=\"commons-logging.jar\" />\n"
"<include name=\"commons-collections.jar\" />]]>"
msgstr ""
+"<![CDATA[<!-- 3rd party and supporting jars -->\n"
+"<include name=\"javassist.jar\"/>\n"
+"<include name=\"dom4j.jar\"/> \n"
+"<include name=\"concurrent.jar\" />\n"
+"<include name=\"cglib.jar\"/>\n"
+"<include name=\"asm.jar\"/>\n"
+"<include name=\"antlr.jar\" />\n"
+"<include name=\"commons-logging.jar\" />\n"
+"<include name=\"commons-collections.jar\" />]]>"
#. Tag: para
#: Glassfish.xml:574
#, no-c-format
msgid "You should end up with something like:"
-msgstr ""
+msgstr "Vous pourrions finir avec quelquechose comme:"
#. Tag: programlisting
#: Glassfish.xml:576
@@ -955,35 +955,49 @@
" <include name=\"commons-collections.jar\" />\n"
"</fileset>]]>"
msgstr ""
+"<![CDATA[<fileset dir=\"${lib.dir}\">\n"
+" <includesfile name=\"deployed-jars-ear.list\" />\n"
+" \n"
+" <!-- Hibernate and deps -->\n"
+" <include name=\"hibernate.jar\"/>\n"
+" <include name=\"hibernate-commons-annotations.jar\"/>\n"
+" <include name=\"hibernate-annotations.jar\"/>\n"
+" <include name=\"hibernate-entitymanager.jar\"/>\n"
+" <include name=\"hibernate-validator.jar\"/>\n"
+" <include name=\"jboss-common-core.jar\" />\n"
+" \n"
+" <!-- 3rd party and supporting jars -->\n"
+" <include name=\"javassist.jar\" />\n"
+" <include name=\"dom4j.jar\" />\n"
+" <include name=\"concurrent.jar\" />\n"
+" <include name=\"cglib.jar\" />\n"
+" <include name=\"asm.jar\" />\n"
+" <include name=\"antlr.jar\" />\n"
+" <include name=\"commons-logging.jar\" />\n"
+" <include name=\"commons-collections.jar\" />\n"
+"</fileset>]]>"
#. Tag: title
#: Glassfish.xml:582
#, no-c-format
msgid "Building and deploying the seam-gen'd application to GlassFish"
-msgstr ""
+msgstr "Compilez et déployez l'application en seam-gen vers GlassFish"
#. Tag: para
#: Glassfish.xml:586
#, no-c-format
-msgid ""
-"Build your application by calling <literal>ant</literal> in the base "
-"directory of your project (for example <literal>/projects/seamgen-example</"
-"literal>). The target of the build will be <literal>dist/seamgen-example."
-"ear</literal>."
-msgstr ""
+msgid "Build your application by calling <literal>ant</literal> in the base directory of your project (for example <literal>/projects/seamgen-example</literal>). The target of the build will be <literal>dist/seamgen-example.ear</literal>."
+msgstr "Compilez votre application en appelant <literal>ant</literal> dans le dossier de base de votre projet (par exemple <literal>/projects/seamgen-example</literal>). La cible de cette compilation sera <literal>dist/seamgen-example.ear</literal>."
#. Tag: para
#: Glassfish.xml:595
#, no-c-format
-msgid ""
-"To deploy the application follow the instructions here <xref linkend=\"jee5-"
-"glassfish-deploy\"/> but use references to this project <literal>seamgen-"
-"example</literal> instead of <literal>jboss-seam-jee5</literal>."
-msgstr ""
+msgid "To deploy the application follow the instructions here <xref linkend=\"jee5-glassfish-deploy\"/> but use references to this project <literal>seamgen-example</literal> instead of <literal>jboss-seam-jee5</literal>."
+msgstr "Pour déployer l'application suivre les instructions ici <xref linkend=\"jee5-glassfish-deploy\"/> mais utiliser les références pour ce projet <literal>seamgen-example</literal> au lieu de <literal>jboss-seam-jee5</literal>."
#. Tag: para
#: Glassfish.xml:604
#, no-c-format
-msgid ""
-"Checkout the app at <literal>http://localhost:8081/seamgen_example/</literal>"
-msgstr ""
+msgid "Checkout the app at <literal>http://localhost:8081/seamgen_example/</literal>"
+msgstr "Vérifiez l'application sur <literal>http://localhost:8081/seamgen_example/</literal>"
+
15 years, 1 month
- 1
- 0
Seam SVN: r11601 - branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR.
by seam-commits＠lists.jboss.org
Author: essaidetest
Date: 2009-10-17 16:12:38 -0400 (Sat, 17 Oct 2009)
New Revision: 11601
Modified:
branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Getting_Started_With_JBoss_Tools.po
branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Gettingstarted.po
Log:
Modified: branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Getting_Started_With_JBoss_Tools.po
===================================================================
--- branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Getting_Started_With_JBoss_Tools.po 2009-10-16 19:41:50 UTC (rev 11600)
+++ branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Getting_Started_With_JBoss_Tools.po 2009-10-17 20:12:38 UTC (rev 11601)
@@ -6,8 +6,8 @@
"Project-Id-Version: seam 2_0\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-04-15 13:51+0000\n"
-"PO-Revision-Date: 2008-05-03 11:34+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2009-10-17 21:43+0100\n"
+"Last-Translator: P.J <essaidetest(a)yahoo.fr>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -17,559 +17,420 @@
#: Getting_Started_With_JBoss_Tools.xml:5
#, no-c-format
msgid "Getting started with Seam, using JBoss Tools"
-msgstr ""
+msgstr "Démarrer avec Seam en utilisant JBoss Tools"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:7
#, no-c-format
-msgid ""
-"JBoss Tools is a collection of Eclipse plugins. JBoss Tools a project "
-"creation wizard for Seam, Content Assist for the Unified Expression Language "
-"(EL) in both facelets and Java code, a graphical editor for jPDL, a "
-"graphical editor for Seam configuration files, support for running Seam "
-"integration tests from within Eclipse, and much more."
-msgstr ""
+msgid "JBoss Tools is a collection of Eclipse plugins. JBoss Tools a project creation wizard for Seam, Content Assist for the Unified Expression Language (EL) in both facelets and Java code, a graphical editor for jPDL, a graphical editor for Seam configuration files, support for running Seam integration tests from within Eclipse, and much more."
+msgstr " JBoss Toolsest une collection de plugins Eclipse. JBoss Tools est un projet de d'assistant de création de Seam, Content Assist pour Unified Expression Language (EL) à la fois en facelets et en code Java, un editeur graphique pour le jPDL, un editeur graphique pour les fichiers de configuration de Seam, le support pour l'exécution des tests d'intégration de Seam depuis Eclipse, et bien plus."
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:15
#, no-c-format
msgid "In short, if you are an Eclipse user, then you'll want JBoss Tools!"
-msgstr ""
+msgstr "Pour faire simple, si vous ête un utilisateur d'Eclipse, alors vous allez vouloirs JBoss Tools!"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:19
#, no-c-format
-msgid ""
-"JBoss Tools, as with seam-gen, works best with JBoss AS, but it's possible "
-"with a few tweaks to get your app running on other application servers. The "
-"changes are much like those described for seam-gen later in this reference "
-"manual."
-msgstr ""
+msgid "JBoss Tools, as with seam-gen, works best with JBoss AS, but it's possible with a few tweaks to get your app running on other application servers. The changes are much like those described for seam-gen later in this reference manual."
+msgstr "JBoss Tools, avec seam-gen, fonctionne mieux avec le JBoss AS, mais si c'est pas possible avec quelques trucs d'avoir votre application qui s'exécute sur les autres seveurs d'applications. Le changement est surtout pour ce qui est décrit plus loin pour seam-gen dans ce manueld e référence."
#. Tag: title
#: Getting_Started_With_JBoss_Tools.xml:27
#, no-c-format
msgid "Before you start"
-msgstr ""
+msgstr "Avant de commencer"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:29
#, no-c-format
-msgid ""
-"Make sure you have JDK 5, JBoss AS 4.2 or 5.0, Eclipse 3.3, the JBoss Tools "
-"plugins (at least Seam Tools, the Visual Page Editor, jBPM Tools and JBoss "
-"AS Tools) and the TestNG plugin for Eclipse correctly installed before "
-"starting."
-msgstr ""
+msgid "Make sure you have JDK 5, JBoss AS 4.2 or 5.0, Eclipse 3.3, the JBoss Tools plugins (at least Seam Tools, the Visual Page Editor, jBPM Tools and JBoss AS Tools) and the TestNG plugin for Eclipse correctly installed before starting."
+msgstr "Vérifiez que vous avez JDK 5, JBoss AS 4.2 ou 5.0, Eclipse 3.3, le JBoss Tools plugins (à minima Seam Tools, le Visual Page Editor, jBPM Tools et JBoss AS Tools) et le plugin TestNG pour Eclipse correctement installé avant de commencer."
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:36
#, no-c-format
-msgid ""
-"Please see the official <ulink url=\"http://www.jboss.org/tools/download/"
-"installation\">JBoss Tools installation</ulink> page for the quickest way to "
-"get JBoss Tools setup in Eclipse. You can also check out the <ulink url="
-"\"http://www.jboss.org/community/wiki/InstallingJBossTools\">Installing "
-"JBoss Tools</ulink> page on the JBoss community wiki for the gory details "
-"and a set of alternative installation approaches."
-msgstr ""
+msgid "Please see the official <ulink url=\"http://www.jboss.org/tools/download/installation\">JBoss Tools installation</ulink> page for the quickest way to get JBoss Tools setup in Eclipse. You can also check out the <ulink url=\"http://www.jboss.org/community/wiki/InstallingJBossTools\">Installing JBoss Tools</ulink> page on the JBoss community wiki for the gory details and a set of alternative installation approaches."
+msgstr "Merci de consulter la page officielle <ulink url=\"http://www.jboss.org/tools/download/installation\">JBoss Tools installation</ulink> pour la plus rapide façon d'avoir l'installation de JBoss Tools dans Eclipse. Vous pouvez aussi consulter la page <ulink url=\"http://www.jboss.org/community/wiki/InstallingJBossTools\">Installing JBoss Tools</ulink> sur le wiki de la communauté JBoss pour les détails les plus extrèmes et une suite d'approches alternatives."
#. Tag: title
#: Getting_Started_With_JBoss_Tools.xml:49
#, no-c-format
msgid "Setting up a new Seam project"
-msgstr ""
+msgstr "Configuration d'un nouveau projet Seam"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:51
#, no-c-format
msgid "Start up Eclipse and select the <emphasis>Seam</emphasis> perspective."
-msgstr ""
+msgstr "Démarrez Eclipse et sélectionnez la perspective <emphasis>Seam</emphasis>."
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:55
#, no-c-format
-msgid ""
-"Go to <emphasis>File</emphasis> -> <emphasis>New</emphasis> -> "
-"<emphasis>Seam Web Project</emphasis>."
-msgstr ""
+msgid "Go to <emphasis>File</emphasis> -> <emphasis>New</emphasis> -> <emphasis>Seam Web Project</emphasis>."
+msgstr "Allez dans <emphasis>File</emphasis> -> <emphasis>New</emphasis> -> <emphasis>Seam Web Project</emphasis>."
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:71
#, no-c-format
-msgid ""
-"First, enter a name for your new project. For this tutorial, we're going to "
-"use <literal>helloworld</literal> ."
-msgstr ""
+msgid "First, enter a name for your new project. For this tutorial, we're going to use <literal>helloworld</literal> ."
+msgstr "En premier lieu, entrez un nom pour votre nouveau projet. Pour ce tutoriel, nous allons utiliser<literal>helloworld</literal> ."
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:79
#, no-c-format
-msgid ""
-"Now, we need to tell JBoss Tools about JBoss AS. In this example we are "
-"using JBoss AS 4.2, though you can certainly use JBoss AS 5.0 as well. "
-"Selecting JBoss AS is a two step process. First we need to define a runtime. "
-"Again, we'll choose JBoss AS 4.2 in this case:"
-msgstr ""
+msgid "Now, we need to tell JBoss Tools about JBoss AS. In this example we are using JBoss AS 4.2, though you can certainly use JBoss AS 5.0 as well. Selecting JBoss AS is a two step process. First we need to define a runtime. Again, we'll choose JBoss AS 4.2 in this case:"
+msgstr "Maintenant, vous devez indiquer à JBoss Tools où est JBoss AS. Dans cet exemple, nous utilisons JBoss AS, pensez que vous pouvez certainement utiliser JBoss AS 5.0 tout aussi bien. La sélection de JBoss AS est un processus en deux étapes. En premier vous avez besoin de le définir à l'exécution. Ensuite, vous allez choisir JBoss AS, dasn ce cas:"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:97
#, no-c-format
msgid "Enter a name for the runtime, and locate it on your hard drive:"
-msgstr ""
+msgstr "Entrez le nom à l'exécution, et localisez le sur votre disque dur:"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:112
#, no-c-format
-msgid ""
-"Next, we need to define a server JBoss Tools can deploy the project to. Make "
-"sure to again select JBoss AS 4.2, and also the runtime you just defined:"
-msgstr ""
+msgid "Next, we need to define a server JBoss Tools can deploy the project to. Make sure to again select JBoss AS 4.2, and also the runtime you just defined:"
+msgstr "Ensuite, vous devez définir un serveur pour que JBoss Tools puisse y déployer le projet. Soyez sur de sélectionner encore une fois JBoss AS et aussi à l'exéuction vous devez juste définir:"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:127
#, no-c-format
-msgid ""
-"On the next screen give the server a name, and hit <emphasis>Finish</"
-"emphasis>:"
-msgstr ""
+msgid "On the next screen give the server a name, and hit <emphasis>Finish</emphasis>:"
+msgstr "Sur l'écran suivant donnez au serveur un nom, et appuyez sur <emphasis>Finish</emphasis>:"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:143
#, no-c-format
-msgid ""
-"Make sure the runtime and server you just created are selected, select "
-"<emphasis>Dynamic Web Project with Seam 2.0 (technology preview)</emphasis> "
-"and hit <emphasis>Next</emphasis>:"
-msgstr ""
+msgid "Make sure the runtime and server you just created are selected, select <emphasis>Dynamic Web Project with Seam 2.0 (technology preview)</emphasis> and hit <emphasis>Next</emphasis>:"
+msgstr "Soyez sur qu'à l'exécution et que le server que vous avez juste créez sont sélectionné, sélectionnez <emphasis>Dynamic Web Project with Seam 2.0 (technology preview)</emphasis> et appuyez sur <emphasis>Next</emphasis>:"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:160
#, no-c-format
-msgid ""
-"The next 3 screens allow you to further customize your new project, but for "
-"us the defaults are fine. So just hit <emphasis>Next</emphasis> until you "
-"reach the final screen."
-msgstr ""
+msgid "The next 3 screens allow you to further customize your new project, but for us the defaults are fine. So just hit <emphasis>Next</emphasis> until you reach the final screen."
+msgstr "Les 3 écrans suivants vous permettent de personnalisé votre nouveau projet, mais pour nous les réglages par défaut seront très bien. Donc appuyez juste sur <emphasis>Next</emphasis> tant que vous n'avez pas atteind l'écran final."
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:166
#, no-c-format
-msgid ""
-"The first step here is to tell JBoss Tools about the Seam download you want "
-"to use. <emphasis>Add</emphasis> a new <emphasis>Seam Runtime</emphasis> - "
-"make sure to give it a name, and select <emphasis>2.0</emphasis> as the "
-"version:"
-msgstr ""
+msgid "The first step here is to tell JBoss Tools about the Seam download you want to use. <emphasis>Add</emphasis> a new <emphasis>Seam Runtime</emphasis> - make sure to give it a name, and select <emphasis>2.0</emphasis> as the version:"
+msgstr "La première étape ici est de dire à JBoss Tools où se trouve le Seam téléchargé que vous voulez utiliser. <emphasis>Add</emphasis> un nouveau <emphasis>Seam Runtime</emphasis> - soyez sur d'indiquer le nom , et sélectionez <emphasis>2.0</emphasis> comme version:"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:184
#, no-c-format
-msgid ""
-"The most important choice you need to make is between EAR deployment and WAR "
-"deployment of your project. EAR projects support EJB 3.0 and require Java EE "
-"5. WAR projects do not support EJB 3.0, but may be deployed to a J2EE "
-"environment. The packaging of a WAR is also simpler to understand. If you "
-"installed an EJB3-ready application server like JBoss, choose <emphasis>EAR</"
-"emphasis>. Otherwise, choose <emphasis>WAR</emphasis>. We'll assume that "
-"you've chosen a WAR deployment for the rest of the tutorial, but you can "
-"follow exactly the same steps for a EAR deployment."
-msgstr ""
+msgid "The most important choice you need to make is between EAR deployment and WAR deployment of your project. EAR projects support EJB 3.0 and require Java EE 5. WAR projects do not support EJB 3.0, but may be deployed to a J2EE environment. The packaging of a WAR is also simpler to understand. If you installed an EJB3-ready application server like JBoss, choose <emphasis>EAR</emphasis>. Otherwise, choose <emphasis>WAR</emphasis>. We'll assume that you've chosen a WAR deployment for the rest of the tutorial, but you can follow exactly the same steps for a EAR deployment."
+msgstr "La choix le plus important que vous devez faire est entre un déploiement EAR ou un déploiement WAR de votre projet. Les projets EAR supportent les EJB 3.0 et nécéssitent Java EE5. Les projets WAR ne supportent pas les EJB3.0 mais peuvent être déployés dans un environement J2EE. L'empaquetage d'un WAR est aussi plus simple à comprendre. Si vous installez un serveur d'application prêt pour EJB3, choissisez <emphasis>EAR</emphasis>. Sinon choississez <emphasis>WAR</emphasis>. Nous allons supposez que vous avez choisi un déploiement WAR pour le reste du tutoriel, mais vous pouvez suivre exactement les mêmes étapes pour un déploiement de EAR."
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:196
#, no-c-format
-msgid ""
-"Next, select your database type. We'll assume you have MySQL installed, with "
-"an existing schema. You'll need to tell JBoss Tools about the database, "
-"select <emphasis>MySQL</emphasis> as the database, and create a new "
-"connection profile. Select <emphasis>Generic JDBC Connection</emphasis>:"
-msgstr ""
+msgid "Next, select your database type. We'll assume you have MySQL installed, with an existing schema. You'll need to tell JBoss Tools about the database, select <emphasis>MySQL</emphasis> as the database, and create a new connection profile. Select <emphasis>Generic JDBC Connection</emphasis>:"
+msgstr "Ensuite, sélectionnez votre type de base de données. Nous allons supposé que vous installé MySQL avec un schéma de base de données existant Vous allez devir indiquer à JBoss Tools où est la base de données, selectionnez <emphasis>MySQL</emphasis> comme base de données, et créez un nouveau profil de connection. Sélectionnez <emphasis>Generic JDBC Connection</emphasis>:"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:215
#, no-c-format
msgid "Give it a name:"
-msgstr ""
+msgstr "Indiquez lui un nom:"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:230
#, no-c-format
-msgid ""
-"JBoss Tools doesn't come with drivers for any databases, so you need to tell "
-"JBoss Tools where the MySQL JDBC driver is. Tell it about the driver by "
-"clicking <emphasis>...</emphasis>."
-msgstr ""
+msgid "JBoss Tools doesn't come with drivers for any databases, so you need to tell JBoss Tools where the MySQL JDBC driver is. Tell it about the driver by clicking <emphasis>...</emphasis>."
+msgstr "JBoss Tolls n'est pas fourni avec des pilotes pour les bases de données, vous devez dire à JBoss Tools où se trouve le pilote MySQL JDBC. Indiquez lui où se trouve le pilote en cliquant sur <emphasis>...</emphasis>."
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:236
#, no-c-format
msgid "Locate MySQL 5, and hit <emphasis>Add...</emphasis>:"
-msgstr ""
+msgstr "Localisez le MySQL 5, et appuyez sur<emphasis>Add...</emphasis>:"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:251
#, no-c-format
msgid "Choose the <emphasis>MySQL JDBC Driver</emphasis> template:"
-msgstr ""
+msgstr "Choississez le modèle de <emphasis>MySQL JDBC Driver</emphasis>:"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:266
#, no-c-format
-msgid ""
-"Locate the jar on your computer by choosing <emphasis>Edit Jar/Zip</"
-"emphasis>:"
-msgstr ""
+msgid "Locate the jar on your computer by choosing <emphasis>Edit Jar/Zip</emphasis>:"
+msgstr "Localisez le jar sur votre ordinateur en choissisant <emphasis>Edit Jar/Zip</emphasis>:"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:282
#, no-c-format
-msgid ""
-"Review the username and password used to connect, and if correct, hit "
-"<emphasis>Ok</emphasis>."
-msgstr ""
+msgid "Review the username and password used to connect, and if correct, hit <emphasis>Ok</emphasis>."
+msgstr "Indiquez votre nom d'utilisateur et votre mode passe à utiliser pour se connecter, et si c'est correcte, appuyez sur <emphasis>Ok</emphasis>."
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:287
#, no-c-format
msgid "Finally, choose the newly created driver:"
-msgstr ""
+msgstr "AU final, choississez le pilote nouvellement créer:"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:302
#, no-c-format
-msgid ""
-"If you are working with an existing data model, make sure you tell JBoss "
-"Tools that the tables already exist in the database."
-msgstr ""
+msgid "If you are working with an existing data model, make sure you tell JBoss Tools that the tables already exist in the database."
+msgstr "Si vous travaillez avec un modèle de données existant, soyez sur de dire à JBoss Tools que des tables existent déjà dans la base de données."
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:307
#, no-c-format
-msgid ""
-"Review the username and password used to connect, test the connection using "
-"the <emphasis>Test Connection</emphasis> button, and if it works, hit "
-"<emphasis>Finish</emphasis>:"
-msgstr ""
+msgid "Review the username and password used to connect, test the connection using the <emphasis>Test Connection</emphasis> button, and if it works, hit <emphasis>Finish</emphasis>:"
+msgstr "Indiquez le nom d'utilisateur et le mot de passe utilisé pour se connecter, testez la connection en utilisant le bouton <emphasis>Test Connection</emphasis> , et si cela fonctionne, appuyez sur <emphasis>Finish</emphasis>:"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:313
#, no-c-format
-msgid ""
-"Finally, review the package names for your generated beans, and if you are "
-"happy, click <emphasis>Finish</emphasis>:"
-msgstr ""
+msgid "Finally, review the package names for your generated beans, and if you are happy, click <emphasis>Finish</emphasis>:"
+msgstr "Au final, vérifiez les noms des paquet de vos beans générés et si vous en êtes content, cliquez sur <emphasis>Finish</emphasis>:"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:329
#, no-c-format
-msgid ""
-"JBoss has sophisticated support for hot re-deployment of WARs and EARs. "
-"Unfortunately, due to bugs in the JVM, repeated redeployment of an EAR—which "
-"is common during development—eventually causes the JVM to run out of perm "
-"gen space. For this reason, we recommend running JBoss in a JVM with a large "
-"perm gen space at development time. We suggest the following values:"
-msgstr ""
+msgid "JBoss has sophisticated support for hot re-deployment of WARs and EARs. Unfortunately, due to bugs in the JVM, repeated redeployment of an EAR—which is common during development—eventually causes the JVM to run out of perm gen space. For this reason, we recommend running JBoss in a JVM with a large perm gen space at development time. We suggest the following values:"
+msgstr "JBoss dispose d'un support sophistiqué pour le re-déploiement à chaud des EARs et des WARs. Malheureusement, à cause de bugs dans la JVM, le redéploiement d'un EAR—ce qui est common pendant le développement—peut éventuellement déclencher un épuisement de l'espace perm gen. Pour cette raison, nous recommendons d'exécuter JBoss dans une JVM avec un espace perm gen important pendant la phase de développement. Nous sudgerons les valeurs suivantes:"
#. Tag: programlisting
#: Getting_Started_With_JBoss_Tools.xml:338
#, no-c-format
msgid "-Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512"
-msgstr ""
+msgstr "-Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:340
#, no-c-format
-msgid ""
-"If you don't have so much memory available, the following is our minimum "
-"recommendation:"
-msgstr ""
+msgid "If you don't have so much memory available, the following is our minimum recommendation:"
+msgstr "Si vous navez pas autant de mémoire disponible, les valeurs suivantes sont notre recommendation minimale:"
#. Tag: programlisting
#: Getting_Started_With_JBoss_Tools.xml:345
#, no-c-format
msgid "-Xms256m -Xmx512m -XX:PermSize=128m -XX:MaxPermSize=256"
-msgstr ""
+msgstr "-Xms256m -Xmx512m -XX:PermSize=128m -XX:MaxPermSize=256"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:347
#, no-c-format
-msgid ""
-"Locate the server in the <emphasis>JBoss Server View</emphasis>, right click "
-"on the server and select <emphasis>Edit Launch Configuration</emphasis>:"
-msgstr ""
+msgid "Locate the server in the <emphasis>JBoss Server View</emphasis>, right click on the server and select <emphasis>Edit Launch Configuration</emphasis>:"
+msgstr "Localisez le serveur dans le <emphasis>JBoss Server View</emphasis>, clic droit sur le server et selectionnez <emphasis>Edit Launch Configuration</emphasis>:"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:364
#, no-c-format
msgid "Then, alter the VM arguements:"
-msgstr ""
+msgstr "Ensuite, modifier les arguments de la VM:"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:379
#, no-c-format
-msgid ""
-"If you don't want to bother with this stuff now, you don't have to—come back "
-"to it later, when you get your first <literal>OutOfMemoryException</literal>."
-msgstr ""
+msgid "If you don't want to bother with this stuff now, you don't have to—come back to it later, when you get your first <literal>OutOfMemoryException</literal>."
+msgstr "SI vous ne voulez pas vous inquietes avec tout ce bidule maintenant, vous n'avez pas à le faire—revennez plus tard, quand vous aurez votre premier <literal>OutOfMemoryException</literal>."
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:385
#, no-c-format
-msgid ""
-"To start JBoss, and deploy the project, just right click on the server you "
-"created, and click <emphasis>Start</emphasis>, (or <emphasis>Debug</"
-"emphasis> to start in debug mode):"
-msgstr ""
+msgid "To start JBoss, and deploy the project, just right click on the server you created, and click <emphasis>Start</emphasis>, (or <emphasis>Debug</emphasis> to start in debug mode):"
+msgstr "Pour démarrer JBoss, et deployez votre projet, clic droit sipplement sur le server que vous avez créés et clic sur <emphasis>Start</emphasis>, (ou sur <emphasis>Debug</emphasis> pour démarrer en mode debogage):"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:402
#, no-c-format
-msgid ""
-"Don't get scared by the XML configuration documents that were generated into "
-"the project directory. They are mostly standard Java EE stuff, the stuff you "
-"need to create once and then never look at again, and they are 90% the same "
-"between all Seam projects."
-msgstr ""
+msgid "Don't get scared by the XML configuration documents that were generated into the project directory. They are mostly standard Java EE stuff, the stuff you need to create once and then never look at again, and they are 90% the same between all Seam projects."
+msgstr "Ne soyez pas appeuré par les documents de configuration en XML qui sont générés dans le dossier du projet. Ils sont pour la plus par des trucs de Java EE standards, le genre de truc que vous avez besoin de créer une fois et ensuite de ne jamais plus le regarder, et ils sont dans 90% des cas les même entre tous les projets Seam."
#. Tag: title
#: Getting_Started_With_JBoss_Tools.xml:412
#, no-c-format
msgid "Creating a new action"
-msgstr ""
+msgstr "Création d'une nouvelle action"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:414
#, no-c-format
-msgid ""
-"If you're used to traditional action-style web frameworks, you're probably "
-"wondering how you can create a simple web page with a stateless action "
-"method in Java."
-msgstr ""
+msgid "If you're used to traditional action-style web frameworks, you're probably wondering how you can create a simple web page with a stateless action method in Java."
+msgstr "SI vous utilisez un serveur d'application web de style action traditionnel, vous vous inquiétez surement de comment créer une simple page web avec des méthode d'action sans état en Java."
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:420
#, no-c-format
-msgid ""
-"First, select <emphasis>New</emphasis> -> <emphasis>Seam Action</emphasis>:"
-msgstr ""
+msgid "First, select <emphasis>New</emphasis> -> <emphasis>Seam Action</emphasis>:"
+msgstr "En premier, sélectonnez <emphasis>New</emphasis> -> <emphasis>Seam Action</emphasis>:"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:435
#: Getting_Started_With_JBoss_Tools.xml:501
#, no-c-format
-msgid ""
-"Now, enter the name of the Seam component. JBoss Tools selects sensible "
-"defaults for other fields:"
-msgstr ""
+msgid "Now, enter the name of the Seam component. JBoss Tools selects sensible defaults for other fields:"
+msgstr "Maintenant, entrez le nom du composant de Seam. JBoss Tools sélectionne des valeurs par défauts judicieuses pour les autres champs:"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:451
#, no-c-format
msgid "Finally, hit <emphasis>Finish</emphasis>."
-msgstr ""
+msgstr "Au final, appuyez sur <emphasis>Finish</emphasis>."
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:455
#, no-c-format
-msgid ""
-"Now go to <literal>http://localhost:8080/helloworld/ping.seam</literal> and "
-"click the button. You can see the code behind this action by looking in the "
-"project <literal>src</literal> directory. Put a breakpoint in the "
-"<literal>ping()</literal> method, and click the button again."
-msgstr ""
+msgid "Now go to <literal>http://localhost:8080/helloworld/ping.seam</literal> and click the button. You can see the code behind this action by looking in the project <literal>src</literal> directory. Put a breakpoint in the <literal>ping()</literal> method, and click the button again."
+msgstr "Maintenant allez sur <literal>http://localhost:8080/helloworld/ping.seam</literal> et cliquez sur le bouton. Vous pouvez voir le code derrière cette action en regardant dans le dossier <literal>src</literal> du projet. Metez un point d'arrêt dans la méthode <literal>ping()</literal> et cliquez de nouveau sur le bouton."
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:463
#, no-c-format
-msgid ""
-"Finally, open the <literal>helloworld-test</literal> project, locate "
-"<literal>PingTest</literal> class, right click on it, and choose "
-"<emphasis>Run As</emphasis> -> <emphasis>TestNG Test</emphasis>:"
-msgstr ""
+msgid "Finally, open the <literal>helloworld-test</literal> project, locate <literal>PingTest</literal> class, right click on it, and choose <emphasis>Run As</emphasis> -> <emphasis>TestNG Test</emphasis>:"
+msgstr "Au final, ouvrez le projet <literal>helloworld-test</literal>, localisez la classe <literal>PingTest</literal>, clic droit sur elle et choisissez <emphasis>Run As</emphasis> -> <emphasis>TestNG Test</emphasis>:"
#. Tag: title
#: Getting_Started_With_JBoss_Tools.xml:483
#, no-c-format
msgid "Creating a form with an action"
-msgstr ""
+msgstr "La création d'un formulaire avec une action"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:485
#, no-c-format
-msgid ""
-"The first step is to create a form. Select <emphasis>New</emphasis> -> "
-"<emphasis>Seam Form</emphasis>:"
-msgstr ""
+msgid "The first step is to create a form. Select <emphasis>New</emphasis> -> <emphasis>Seam Form</emphasis>:"
+msgstr "La première étape pour créer un formulaire. Sélectionnez <emphasis>New</emphasis> -> <emphasis>Seam Form</emphasis>:"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:517
#, no-c-format
-msgid ""
-"Go to <literal>http://localhost:8080/helloworld/hello.seam</literal>. Then "
-"take a look at the generated code. Run the test. Try adding some new fields "
-"to the form and Seam component (note, you don't need to restart the app "
-"server each time you change the code in <literal>src/action</literal> as "
-"Seam hot reloads the component for you <xref linkend="
-"\"gettingstartedwithjbosstools.hotdeployment\"/>)."
-msgstr ""
+msgid "Go to <literal>http://localhost:8080/helloworld/hello.seam</literal>. Then take a look at the generated code. Run the test. Try adding some new fields to the form and Seam component (note, you don't need to restart the app server each time you change the code in <literal>src/action</literal> as Seam hot reloads the component for you <xref linkend=\"gettingstartedwithjbosstools.hotdeployment\"/>)."
+msgstr "Allez sur <literal>http://localhost:8080/helloworld/hello.seam</literal>. Ensuite, regardez comment est le code généré. Exécutez le test. Essayez d'ajouter de nouveaux champs au formulaire et au composant de Seam (notez, vous n'avez pas à redémarrer le serveur d'application à chaque fois que vous modifier le code dans <literal>src/action</literal> car Seam recharge à chaud le composant pour vous <xref linkend=\"gettingstartedwithjbosstools.hotdeployment\"/>)."
#. Tag: title
#: Getting_Started_With_JBoss_Tools.xml:528
#, no-c-format
msgid "Generating an application from an existing database"
-msgstr ""
+msgstr "La génération d'une application depuis une base de données existante"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:530
#, no-c-format
-msgid ""
-"Manually create some tables in your database. (If you need to switch to a "
-"different database, create a new project, and select the correct database). "
-"Then, select <emphasis>New</emphasis> -> <emphasis>Seam Generate Entities</"
-"emphasis>:"
-msgstr ""
+msgid "Manually create some tables in your database. (If you need to switch to a different database, create a new project, and select the correct database). Then, select <emphasis>New</emphasis> -> <emphasis>Seam Generate Entities</emphasis>:"
+msgstr "Manuellement, créez quelques tables dans votre base de données. (Si vous avez besoin de basculer vers une base de données différente, créez une nouveau projet et sélectionnez la base de données correcte. Ensuite, sélectionnez <emphasis>New</emphasis> -> <emphasis>Seam Generate Entities</emphasis>:"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:548
#, no-c-format
-msgid ""
-"JBoss Tools gives you the option to either reverse engineer entities, "
-"components and views from a database schema or to reverse engineer "
-"components and views from existing JPA entities. We're going to do "
-"<emphasis>Reverse engieneer from database</emphasis>."
-msgstr ""
+msgid "JBoss Tools gives you the option to either reverse engineer entities, components and views from a database schema or to reverse engineer components and views from existing JPA entities. We're going to do <emphasis>Reverse engieneer from database</emphasis>."
+msgstr "JBoss Tools vous offre aussi l'option de réaliser une ingénieurie inverse des entitées, composants et des vues depuis votre schéma de base de données ou depuis les composants et les vues des entitées JPA existantes. Nous allonrs réaliser <emphasis>une ingénieurie inverse depuis une abase de données</emphasis>."
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:555
#, no-c-format
msgid "Restart the deployment:"
-msgstr ""
+msgstr "Redémarrer le déploiement:"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:570
#, no-c-format
-msgid ""
-"Then go to <literal>http://localhost:8080/helloworld</literal>. You can "
-"browse the database, edit existing objects, and create new objects. If you "
-"look at the generated code, you'll probably be amazed how simple it is! Seam "
-"was designed so that data access code is easy to write by hand, even for "
-"people who don't want to cheat by using reverse engineering."
-msgstr ""
+msgid "Then go to <literal>http://localhost:8080/helloworld</literal>. You can browse the database, edit existing objects, and create new objects. If you look at the generated code, you'll probably be amazed how simple it is! Seam was designed so that data access code is easy to write by hand, even for people who don't want to cheat by using reverse engineering."
+msgstr "Ensuite, allez vers <literal>http://localhost:8080/helloworld</literal>. Vous pouvez naviguer dans la base de données, editer des objets existants, et créez de nouveaux objets. Si vous regardez dans le code généré, vous allez probablement être impréssionné par sa simplicité! Seam a été conçu pour que le code d'accès aux données soit simple à écrire à la main, même par des gens qui ne veulent pas tricher en utilisant l'ingénieurie inverse."
#. Tag: title
#: Getting_Started_With_JBoss_Tools.xml:581
#, no-c-format
msgid "Seam and incremental hot deployment with JBoss Tools"
-msgstr ""
+msgstr "Seam et le déploiement incrémental à chaud avec JBoss Tools"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:583
#, no-c-format
msgid "JBoss Tools supports incremental hot deployment of:"
-msgstr ""
+msgstr "JBoss Tools permet le déploiement incrémental à chaud de :"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:589
#, no-c-format
msgid "any facelets page"
-msgstr ""
+msgstr "toute page facelets"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:593
#, no-c-format
msgid "any <literal>pages.xml</literal> file"
-msgstr ""
+msgstr "tout fichier <literal>pages.xml</literal>"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:599
#, no-c-format
msgid "out of the box."
-msgstr ""
+msgstr "au déballage de la boite."
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:603
#, no-c-format
-msgid ""
-"But if we want to change any Java code, we still need to do a full restart "
-"of the application by doing a <emphasis>Full Publish</emphasis>."
-msgstr ""
+msgid "But if we want to change any Java code, we still need to do a full restart of the application by doing a <emphasis>Full Publish</emphasis>."
+msgstr "Mais si nous voulons modifier n'importe quel code Java, nous avons toujours besoin de faire un redémarrage complet de l'application en faisant un <emphasis>Full Publish</emphasis>."
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:609
#, no-c-format
-msgid ""
-"But if you really want a fast edit/compile/test cycle, Seam supports "
-"incremental redeployment of JavaBean components. To make use of this "
-"functionality, you must deploy the JavaBean components into the <literal>WEB-"
-"INF/dev</literal> directory, so that they will be loaded by a special Seam "
-"classloader, instead of by the WAR or EAR classloader."
-msgstr ""
+msgid "But if you really want a fast edit/compile/test cycle, Seam supports incremental redeployment of JavaBean components. To make use of this functionality, you must deploy the JavaBean components into the <literal>WEB-INF/dev</literal> directory, so that they will be loaded by a special Seam classloader, instead of by the WAR or EAR classloader."
+msgstr "Mais si vous voulez un cycle rapide d'édition/compilation/test, Seam permet de redéploiement incrémental des composants JavaBean. Pour vous permetre d'utilisez cette fonctionnalité, vous devez déploiyer les composants JavaBean dans le dossier<literal>WEB-INF/dev</literal> , ainsi ils sont recharger par le classloader spécial de Seam, au lieu du classloader WAR ou EAR."
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:618
#, no-c-format
msgid "You need to be aware of the following limitations:"
-msgstr ""
+msgstr "Vous devez être au courrant des limitations suivantes:"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:622
#, no-c-format
-msgid ""
-"the components must be JavaBean components, they cannot be EJB3 beans (we "
-"are working on fixing this limitation)"
-msgstr ""
+msgid "the components must be JavaBean components, they cannot be EJB3 beans (we are working on fixing this limitation)"
+msgstr "les composants doivent être des composants JavaBean, il ne peuvent pas être des beans EJB3 (nous travaillons pour corriger cette limitation)"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:629
#, no-c-format
msgid "entities can never be hot-deloyed"
-msgstr ""
+msgstr "les entités ne peuvent jamais être déploiyées à chaud."
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:635
#, no-c-format
-msgid ""
-"components deployed via <literal>components.xml</literal> may not be hot-"
-"deployed"
-msgstr ""
+msgid "components deployed via <literal>components.xml</literal> may not be hot-deployed"
+msgstr "les composants déployés via <literal>components.xml</literal> ne peuvent pas être rechargés à chaud."
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:642
#, no-c-format
-msgid ""
-"the hot-deployable components will not be visible to any classes deployed "
-"outside of <literal>WEB-INF/dev</literal>"
-msgstr ""
+msgid "the hot-deployable components will not be visible to any classes deployed outside of <literal>WEB-INF/dev</literal>"
+msgstr "les composants rechargés à chaud ne seront pas visible pour toute les classes déployés à l'extérieur de <literal>WEB-INF/dev</literal>"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:649
#, no-c-format
-msgid ""
-"Seam debug mode must be enabled and <literal>jboss-seam-debug.jar</literal> "
-"must be in <literal>WEB-INF/lib</literal>"
-msgstr ""
+msgid "Seam debug mode must be enabled and <literal>jboss-seam-debug.jar</literal> must be in <literal>WEB-INF/lib</literal>"
+msgstr "Le mode de débogage de Seam doit être actif et <literal>jboss-seam-debug.jar</literal> doit être dans <literal>WEB-INF/lib</literal>"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:657
#, no-c-format
msgid "You must have the Seam filter installed in web.xml"
-msgstr ""
+msgstr "Vous devez avoir le filtre Seam installé dans web.xml"
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:663
#, no-c-format
-msgid ""
-"You may see errors if the system is placed under any load and debug is "
-"enabled."
-msgstr ""
+msgid "You may see errors if the system is placed under any load and debug is enabled."
+msgstr "Vous pouvez voir des erreurs si le système est situé pendant le chargement ou le débogage est activé."
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:671
#, no-c-format
-msgid ""
-"If you create a WAR project using JBoss Tools, incremental hot deployment is "
-"available out of the box for classes in the <literal>src/action</literal> "
-"source directory. However, JBoss Tools does not support incremental hot "
-"deployment for EAR projects."
-msgstr ""
+msgid "If you create a WAR project using JBoss Tools, incremental hot deployment is available out of the box for classes in the <literal>src/action</literal> source directory. However, JBoss Tools does not support incremental hot deployment for EAR projects."
+msgstr "Si vous créez un projet WAR en utilisant JBoss Tools, le déploiement incrémental à chaud est disponible immédiatement pour les classes se trouvant dans le dossier des sources <literal>src/action</literal>. Cependant, JBoss Tools ne fourni pas de déploiement incrémental à chaud pour les projets EAR."
+
Modified: branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Gettingstarted.po
===================================================================
--- branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Gettingstarted.po 2009-10-16 19:41:50 UTC (rev 11600)
+++ branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Gettingstarted.po 2009-10-17 20:12:38 UTC (rev 11601)
@@ -6,8 +6,8 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-06-25 15:02+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2009-10-17 22:12+0100\n"
+"Last-Translator: P.J <essaidetest(a)yahoo.fr>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -17,137 +17,97 @@
#: Gettingstarted.xml:5
#, no-c-format
msgid "Getting started with Seam, using seam-gen"
-msgstr ""
+msgstr "Démarrage avec Seam en utilisant seam-gen"
#. Tag: para
#: Gettingstarted.xml:7
#, no-c-format
-msgid ""
-"The Seam distribution includes a command line utility that makes it really "
-"easy to set up an Eclipse project, generate some simple Seam skeleton code, "
-"and reverse engineer an application from a preexisting database."
-msgstr ""
+msgid "The Seam distribution includes a command line utility that makes it really easy to set up an Eclipse project, generate some simple Seam skeleton code, and reverse engineer an application from a preexisting database."
+msgstr "La distribution Seam inclus un utilitaire en ligne de commande qui permet facilement de configurer un projet Eclipse, de générer un squelette de code simple Seam et de réaliser une ingénierie inverse sur une base de données pré existante."
#. Tag: para
#: Gettingstarted.xml:10
#, no-c-format
-msgid ""
-"This is the easy way to get your feet wet with Seam, and gives you some "
-"ammunition for next time you find yourself trapped in an elevator with one "
-"of those tedious Ruby guys ranting about how great and wonderful his new toy "
-"is for building totally trivial applications that put things in databases."
-msgstr ""
+msgid "This is the easy way to get your feet wet with Seam, and gives you some ammunition for next time you find yourself trapped in an elevator with one of those tedious Ruby guys ranting about how great and wonderful his new toy is for building totally trivial applications that put things in databases."
+msgstr "C’est une façon simple de garder les pieds au sec avec Seam, et de vous donnez des munitions pour la prochaine fois que vous vous trouverez enfermer dans un ascenseur avec un de ces gars tordus de Ruby vous taquinant sur le fait que leur jouet est génial et merveilleux pour construire des applications triviales qui mettent des choses dans les base de données."
#. Tag: para
#: Gettingstarted.xml:14
#, no-c-format
-msgid ""
-"In this release, seam-gen works best for people with JBoss AS. You can use "
-"the generated project with other J2EE or Java EE 5 application servers by "
-"making a few manual changes to the project configuration."
-msgstr ""
+msgid "In this release, seam-gen works best for people with JBoss AS. You can use the generated project with other J2EE or Java EE 5 application servers by making a few manual changes to the project configuration."
+msgstr "Dans cette version, seam-gen fonctionne mieux pour tous avec JBoss AS. Vous pouvez utiliser le projet généré avec d’autre serveurs d’application J2EE ou Java EE5. en réalisant plusieurs modifications à la main à la configuration du projet."
#. Tag: para
#: Gettingstarted.xml:17
#, no-c-format
-msgid ""
-"You <emphasis>can</emphasis> use seam-gen without Eclipse, but in this "
-"tutorial, we want to show you how to use it in conjunction with Eclipse for "
-"debugging and integration testing. If you don't want to install Eclipse, you "
-"can still follow along with this tutorial—all steps can be performed from "
-"the command line."
-msgstr ""
+msgid "You <emphasis>can</emphasis> use seam-gen without Eclipse, but in this tutorial, we want to show you how to use it in conjunction with Eclipse for debugging and integration testing. If you don't want to install Eclipse, you can still follow along with this tutorial—all steps can be performed from the command line."
+msgstr "Vous <emphasis>pouvez</emphasis> utiliser seam-gen sans Eclipse, mais dans ce tutoriel, nous voulons vous montrer comment l’utiliser en conjonction avec Eclipse pour le débogage ou l’intégration des test. Si vous ne voulez pas installer Eclipse vous pouvez quand même suivre ce tutoriel—toutes les étapes peuvent être réalisées depuis la ligne de commande."
#. Tag: para
#: Gettingstarted.xml:21
#, no-c-format
-msgid ""
-"seam-gen is basically just an intricate Ant script wrapped around Hibernate "
-"Tools, together with some templates. That makes it easy to customize if you "
-"need to."
-msgstr ""
+msgid "seam-gen is basically just an intricate Ant script wrapped around Hibernate Tools, together with some templates. That makes it easy to customize if you need to."
+msgstr "Seam-gen est simplement un gros script Ant bien déguelasse utilisant des outils Hibernate, liant ensemble des patrons. Ce qui rends facile la personnalisation cela vos besoins."
#. Tag: title
#: Gettingstarted.xml:25
#, no-c-format
msgid "Before you start"
-msgstr ""
+msgstr "Avant de démarrer"
#. Tag: para
#: Gettingstarted.xml:27
#, no-c-format
-msgid ""
-"Make sure you have JDK 5 or JDK 6 (see <xref linkend=\"jdk_dependencies\"/> "
-"for details), JBoss AS 4.2 or 5.0 and Ant 1.7.0, along with recent versions "
-"of Eclipse, the JBoss IDE plugin for Eclipse and the TestNG plugin for "
-"Eclipse correctly installed before starting. Add your JBoss installation to "
-"the JBoss Server View in Eclipse. Start JBoss in debug mode. Finally, start "
-"a command prompt in the directory where you unzipped the Seam distribution."
-msgstr ""
+msgid "Make sure you have JDK 5 or JDK 6 (see <xref linkend=\"jdk_dependencies\"/> for details), JBoss AS 4.2 or 5.0 and Ant 1.7.0, along with recent versions of Eclipse, the JBoss IDE plugin for Eclipse and the TestNG plugin for Eclipse correctly installed before starting. Add your JBoss installation to the JBoss Server View in Eclipse. Start JBoss in debug mode. Finally, start a command prompt in the directory where you unzipped the Seam distribution."
+msgstr "Soyez sur d’avoir JDK5 ou JDK6 (voir <xref linkend=\"jdk_dependencies\"/> pour les détails), JBoss AS 4.2 ou 5.0 et Ant 1.7.0, avec des versions récentes d’Eclipse, de Jboss IDE plugin pour Eclipse et de TestNG plugin pour Eclipse correctement installés avant le démarrage. Ajoutez votre installation JBoss a la vue Server JBoss dans Eclipse. Démarrer JBoss en mode debug. Enfin, démarrez un interpréteur de commande dans le dossier où vous avez dézipper la distribution de Seam."
#. Tag: para
#: Gettingstarted.xml:33
#, no-c-format
-msgid ""
-"JBoss has sophisticated support for hot re-deployment of WARs and EARs. "
-"Unfortunately, due to bugs in the JVM, repeated redeployment of an EAR—which "
-"is common during development—eventually causes the JVM to run out of perm "
-"gen space. For this reason, we recommend running JBoss in a JVM with a large "
-"perm gen space at development time. If you're running JBoss from JBoss IDE, "
-"you can configure this in the server launch configuration, under \"VM "
-"arguments\". We suggest the following values:"
-msgstr ""
+msgid "JBoss has sophisticated support for hot re-deployment of WARs and EARs. Unfortunately, due to bugs in the JVM, repeated redeployment of an EAR—which is common during development—eventually causes the JVM to run out of perm gen space. For this reason, we recommend running JBoss in a JVM with a large perm gen space at development time. If you're running JBoss from JBoss IDE, you can configure this in the server launch configuration, under \"VM arguments\". We suggest the following values:"
+msgstr "Jboss dispose d’un support sophistiquer pour le redéploiement à chaud des WARs et des EARs. Malheureusement, à cause de bugs dans la JVM, le redéploiement répété de EAR—ce qui est habituel dans la phase de développement—peut éventuellement entrainer la JVM a être à cours d’espace perm gen. Pour cette raison, nous recommandons d’exécuter JBoss dans une JVM avec un large espace perm gen pendant la période de développement. Si vous exécuter Jboss depuis JBoss IDE, vous pouvez configurer cela dans la configuration de lancement du serveur, dans \"VM arguments\". Nous vous conseillons les valeurs suivantes :"
#. Tag: programlisting
#: Gettingstarted.xml:39
#, no-c-format
msgid "-Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512m"
-msgstr ""
+msgstr "-Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512m"
#. Tag: para
#: Gettingstarted.xml:41
#, no-c-format
-msgid ""
-"If you don't have so much memory available, the following is our minimum "
-"recommendation:"
-msgstr ""
+msgid "If you don't have so much memory available, the following is our minimum recommendation:"
+msgstr "Si vous ne disposez pas d’assez de mémoire, ce qui suit est notre recommandation minimale :"
#. Tag: programlisting
#: Gettingstarted.xml:43
#, no-c-format
msgid "-Xms256m -Xmx512m -XX:PermSize=128m -XX:MaxPermSize=256m"
-msgstr ""
+msgstr "-Xms256m -Xmx512m -XX:PermSize=128m -XX:MaxPermSize=256m"
#. Tag: para
#: Gettingstarted.xml:45
#, no-c-format
-msgid ""
-"If you're running JBoss from the command line, you can configure the JVM "
-"options in <literal>bin/run.conf</literal>."
-msgstr ""
+msgid "If you're running JBoss from the command line, you can configure the JVM options in <literal>bin/run.conf</literal>."
+msgstr "vous exécuter JBoss depuis la ligne de commande, vous pouvez configurer les options de la JVM dans <literal>bin/run.conf</literal>."
#. Tag: para
#: Gettingstarted.xml:48
#, no-c-format
-msgid ""
-"If you don't want to bother with this stuff now, you don't have to—come back "
-"to it later, when you get your first <literal>OutOfMemoryException</literal>."
-msgstr ""
+msgid "If you don't want to bother with this stuff now, you don't have to—come back to it later, when you get your first <literal>OutOfMemoryException</literal>."
+msgstr "Si vous ne voulez pas vous inquiéter de ce truc pour l’instant, nous n’êtes pas obligé, revenez y plus tard quand vous rencontrer votre premier <literal>OutOfMemoryException</literal>.."
#. Tag: title
#: Gettingstarted.xml:53
#, no-c-format
msgid "Setting up a new project"
-msgstr ""
+msgstr "Configurer un nouveau projet Eclipse"
#. Tag: para
#: Gettingstarted.xml:55
#, no-c-format
-msgid ""
-"The first thing we need to do is configure seam-gen for your environment: "
-"JBoss AS installation directory, project workspace, and database connection. "
-"It's easy, just type:"
-msgstr ""
+msgid "The first thing we need to do is configure seam-gen for your environment: JBoss AS installation directory, project workspace, and database connection. It's easy, just type:"
+msgstr "La première chose que vous avez besoin de faire est de configurer seam-gen pour votre environnement : le dossier d’installation de JBoss AS, l'espace de travail d’Eclipse et connexion à la base de données. C'est simple, entrez juste :"
#. Tag: programlisting
#: Gettingstarted.xml:58
@@ -156,12 +116,14 @@
"cd jboss-seam-2.2.x\n"
"seam setup"
msgstr ""
+"cd jboss-seam-2.2.x\n"
+"seam setup"
#. Tag: para
#: Gettingstarted.xml:60
#, no-c-format
msgid "And you will be prompted for the needed information:"
-msgstr ""
+msgstr "Et vous allez être interrogé pour un complément d’information :"
#. Tag: programlisting
#: Gettingstarted.xml:62
@@ -174,66 +136,47 @@
"\n"
"setup:\n"
" [echo] Welcome to seam-gen :-)\n"
-" [input] Enter your project workspace (the directory that contains your "
-"Seam projects) [C:/Projects] [C:/Projects]\n"
+" [input] Enter your project workspace (the directory that contains your Seam projects) [C:/Projects] [C:/Projects]\n"
"/Users/pmuir/workspace\n"
-" [input] Enter your JBoss home directory [C:/Program Files/jboss-4.2.3."
-"GA] [C:/Program Files/jboss-4.2.3.GA]\n"
+" [input] Enter your JBoss home directory [C:/Program Files/jboss-4.2.3.GA] [C:/Program Files/jboss-4.2.3.GA]\n"
"/Applications/jboss-4.2.3.GA\n"
" [input] Enter the project name [myproject] [myproject]\n"
"helloworld\n"
" [echo] Accepted project name as: helloworld\n"
-" [input] Select a RichFaces skin (not applicable if using ICEFaces) "
-"[blueSky] ([blueSky], classic, ruby, wine, deepMarine, emeraldTown, sakura, "
-"DEFAULT)\n"
+" [input] Select a RichFaces skin (not applicable if using ICEFaces) [blueSky] ([blueSky], classic, ruby, wine, deepMarine, emeraldTown, sakura, DEFAULT)\n"
"\n"
-" [input] Is this project deployed as an EAR (with EJB components) or a "
-"WAR (with no EJB support) [ear] ([ear], war, )\n"
+" [input] Is this project deployed as an EAR (with EJB components) or a WAR (with no EJB support) [ear] ([ear], war, )\n"
"\n"
-" [input] Enter the Java package name for your session beans [com.mydomain."
-"helloworld] [com.mydomain.helloworld]\n"
+" [input] Enter the Java package name for your session beans [com.mydomain.helloworld] [com.mydomain.helloworld]\n"
"org.jboss.helloworld\n"
-" [input] Enter the Java package name for your entity beans [org.jboss."
-"helloworld] [org.jboss.helloworld]\n"
+" [input] Enter the Java package name for your entity beans [org.jboss.helloworld] [org.jboss.helloworld]\n"
"\n"
-" [input] Enter the Java package name for your test cases [org.jboss."
-"helloworld.test] [org.jboss.helloworld.test]\n"
+" [input] Enter the Java package name for your test cases [org.jboss.helloworld.test] [org.jboss.helloworld.test]\n"
"\n"
-" [input] What kind of database are you using? [hsql] ([hsql], mysql, "
-"oracle, postgres, mssql, db2, sybase, enterprisedb, h2)\n"
+" [input] What kind of database are you using? [hsql] ([hsql], mysql, oracle, postgres, mssql, db2, sybase, enterprisedb, h2)\n"
"mysql\n"
-" [input] Enter the Hibernate dialect for your database [org.hibernate."
-"dialect.MySQLDialect] [org.hibernate.dialect.MySQLDialect]\n"
+" [input] Enter the Hibernate dialect for your database [org.hibernate.dialect.MySQLDialect] [org.hibernate.dialect.MySQLDialect]\n"
"\n"
-" [input] Enter the filesystem path to the JDBC driver jar [lib/hsqldb."
-"jar] [lib/hsqldb.jar]\n"
+" [input] Enter the filesystem path to the JDBC driver jar [lib/hsqldb.jar] [lib/hsqldb.jar]\n"
"/Users/pmuir/java/mysql.jar\n"
-" [input] Enter JDBC driver class for your database [com.mysql.jdbc."
-"Driver] [com.mysql.jdbc.Driver]\n"
+" [input] Enter JDBC driver class for your database [com.mysql.jdbc.Driver] [com.mysql.jdbc.Driver]\n"
"\n"
-" [input] Enter the JDBC URL for your database [jdbc:mysql:///test] [jdbc:"
-"mysql:///test]\n"
+" [input] Enter the JDBC URL for your database [jdbc:mysql:///test] [jdbc:mysql:///test]\n"
"jdbc:mysql:///helloworld\n"
" [input] Enter database username [sa] [sa]\n"
"pmuir\n"
" [input] Enter database password [] []\n"
"\n"
-" [input] skipping input as property hibernate.default_schema.new has "
-"already been set.\n"
-" [input] Enter the database catalog name (it is OK to leave this blank) "
-"[] []\n"
+" [input] skipping input as property hibernate.default_schema.new has already been set.\n"
+" [input] Enter the database catalog name (it is OK to leave this blank) [] []\n"
"\n"
-" [input] Are you working with tables that already exist in the database? "
-"[n] (y, [n], )\n"
+" [input] Are you working with tables that already exist in the database? [n] (y, [n], )\n"
"y\n"
-" [input] Do you want to drop and recreate the database tables and data in "
-"import.sql each time you deploy? [n] (y, [n], )\n"
+" [input] Do you want to drop and recreate the database tables and data in import.sql each time you deploy? [n] (y, [n], )\n"
"n\n"
-" [input] Enter your ICEfaces home directory (leave blank to omit "
-"ICEfaces) [] []\n"
+" [input] Enter your ICEfaces home directory (leave blank to omit ICEfaces) [] []\n"
"\n"
-"[propertyfile] Creating new property file: /Users/pmuir/workspace/jboss-seam/"
-"seam-gen/build.properties\n"
+"[propertyfile] Creating new property file: /Users/pmuir/workspace/jboss-seam/seam-gen/build.properties\n"
" [echo] Installing JDBC driver jar to JBoss server\n"
" [echo] Type 'seam create-project' to create the new project\n"
"\n"
@@ -241,59 +184,96 @@
"Total time: 1 minute 32 seconds\n"
"~/workspace/jboss-seam $"
msgstr ""
+"~/workspace/jboss-seam$ ./seam setup\n"
+"Buildfile: build.xml\n"
+"\n"
+"init:\n"
+"\n"
+"setup:\n"
+" [echo] Welcome to seam-gen :-)\n"
+" [input] Enter your project workspace (the directory that contains your Seam projects) [C:/Projects] [C:/Projects]\n"
+"/Users/pmuir/workspace\n"
+" [input] Enter your JBoss home directory [C:/Program Files/jboss-4.2.3.GA] [C:/Program Files/jboss-4.2.3.GA]\n"
+"/Applications/jboss-4.2.3.GA\n"
+" [input] Enter the project name [myproject] [myproject]\n"
+"helloworld\n"
+" [echo] Accepted project name as: helloworld\n"
+" [input] Select a RichFaces skin (not applicable if using ICEFaces) [blueSky] ([blueSky], classic, ruby, wine, deepMarine, emeraldTown, sakura, DEFAULT)\n"
+"\n"
+" [input] Is this project deployed as an EAR (with EJB components) or a WAR (with no EJB support) [ear] ([ear], war, )\n"
+"\n"
+" [input] Enter the Java package name for your session beans [com.mydomain.helloworld] [com.mydomain.helloworld]\n"
+"org.jboss.helloworld\n"
+" [input] Enter the Java package name for your entity beans [org.jboss.helloworld] [org.jboss.helloworld]\n"
+"\n"
+" [input] Enter the Java package name for your test cases [org.jboss.helloworld.test] [org.jboss.helloworld.test]\n"
+"\n"
+" [input] What kind of database are you using? [hsql] ([hsql], mysql, oracle, postgres, mssql, db2, sybase, enterprisedb, h2)\n"
+"mysql\n"
+" [input] Enter the Hibernate dialect for your database [org.hibernate.dialect.MySQLDialect] [org.hibernate.dialect.MySQLDialect]\n"
+"\n"
+" [input] Enter the filesystem path to the JDBC driver jar [lib/hsqldb.jar] [lib/hsqldb.jar]\n"
+"/Users/pmuir/java/mysql.jar\n"
+" [input] Enter JDBC driver class for your database [com.mysql.jdbc.Driver] [com.mysql.jdbc.Driver]\n"
+"\n"
+" [input] Enter the JDBC URL for your database [jdbc:mysql:///test] [jdbc:mysql:///test]\n"
+"jdbc:mysql:///helloworld\n"
+" [input] Enter database username [sa] [sa]\n"
+"pmuir\n"
+" [input] Enter database password [] []\n"
+"\n"
+" [input] skipping input as property hibernate.default_schema.new has already been set.\n"
+" [input] Enter the database catalog name (it is OK to leave this blank) [] []\n"
+"\n"
+" [input] Are you working with tables that already exist in the database? [n] (y, [n], )\n"
+"y\n"
+" [input] Do you want to drop and recreate the database tables and data in import.sql each time you deploy? [n] (y, [n], )\n"
+"n\n"
+" [input] Enter your ICEfaces home directory (leave blank to omit ICEfaces) [] []\n"
+"\n"
+"[propertyfile] Creating new property file: /Users/pmuir/workspace/jboss-seam/seam-gen/build.properties\n"
+" [echo] Installing JDBC driver jar to JBoss server\n"
+" [echo] Type 'seam create-project' to create the new project\n"
+"\n"
+"BUILD SUCCESSFUL\n"
+"Total time: 1 minute 32 seconds\n"
+"~/workspace/jboss-seam $"
#. Tag: para
#: Gettingstarted.xml:64
#, no-c-format
-msgid ""
-"The tool provides sensible defaults, which you can accept by just pressing "
-"enter at the prompt."
-msgstr ""
+msgid "The tool provides sensible defaults, which you can accept by just pressing enter at the prompt."
+msgstr "Cet outil fourni des valeurs par défaut judicieuses que vous pouvez accepter juste en appuyant sur la couche enter à la demande."
#. Tag: para
#: Gettingstarted.xml:66
#, no-c-format
-msgid ""
-"The most important choice you need to make is between EAR deployment and WAR "
-"deployment of your project. EAR projects support EJB 3.0 and require Java EE "
-"5. WAR projects do not support EJB 3.0, but may be deployed to a J2EE "
-"environment. The packaging of a WAR is also simpler to understand. If you "
-"installed an EJB3-ready application server like JBoss, choose <literal>ear</"
-"literal>. Otherwise, choose <literal>war</literal>. We'll assume that you've "
-"chosen an EAR deployment for the rest of the tutorial, but you can follow "
-"exactly the same steps for a WAR deployment."
-msgstr ""
+msgid "The most important choice you need to make is between EAR deployment and WAR deployment of your project. EAR projects support EJB 3.0 and require Java EE 5. WAR projects do not support EJB 3.0, but may be deployed to a J2EE environment. The packaging of a WAR is also simpler to understand. If you installed an EJB3-ready application server like JBoss, choose <literal>ear</literal>. Otherwise, choose <literal>war</literal>. We'll assume that you've chosen an EAR deployment for the rest of the tutorial, but you can follow exactly the same steps for a WAR deployment."
+msgstr "Le choix le plus important que vous devez faire est entre un déploiement EAR et un déploiement WAR pour votre projet. Les projets EAR supportent EJB 3.0 et nécessite Java EE5. Les projets WAR ne supportent pas EJB 3.0 mais peuvent être déployés dans un environnement J2EE. Le conditionnement en WAR est aussi plus simple à comprendre. Si vous avez installé un server d’application opérationnel EJB3 comme JBoss, choisissez <literal>ear</literal>. Sinon, choississez <literal>war</literal>. Nous allons partir du principe que vous avez choisi un déploiement EAR pour le reste du tutoriel, mais vous pouvez suivre exactement les même étapes pour un déploiement WAR."
#. Tag: para
#: Gettingstarted.xml:73
#, no-c-format
-msgid ""
-"If you are working with an existing data model, make sure you tell seam-gen "
-"that the tables already exist in the database."
-msgstr ""
+msgid "If you are working with an existing data model, make sure you tell seam-gen that the tables already exist in the database."
+msgstr "Si vous travaillez avec un modèle de données déjà existant, soyez sur d’indiquer à seam-gen que des tables existent déjà dans la base de données."
#. Tag: para
#: Gettingstarted.xml:76
#, no-c-format
-msgid ""
-"The settings are stored in <literal>seam-gen/build.properties</literal>, but "
-"you can also modify them simply by running <literal>seam setup</literal> a "
-"second time."
-msgstr ""
+msgid "The settings are stored in <literal>seam-gen/build.properties</literal>, but you can also modify them simply by running <literal>seam setup</literal> a second time."
+msgstr "Les régleages sont stockés dans <literal>seam-gen/build.properties</literal>, mais vous pouvez aussi les modifier simplement en relançant <literal>seam setup</literal> une seconde fois."
#. Tag: para
#: Gettingstarted.xml:79
#, no-c-format
-msgid ""
-"Now we can create a new project in our Eclipse workspace directory, by "
-"typing:"
-msgstr ""
+msgid "Now we can create a new project in our Eclipse workspace directory, by typing:"
+msgstr "Maintenant vous pouvez créer un nouveau projet dans le dossier de votre espace de travail d’Eclipse, en entrant :"
#. Tag: programlisting
#: Gettingstarted.xml:81
#, no-c-format
msgid "seam new-project"
-msgstr ""
+msgstr "seam new-project"
#. Tag: programlisting
#: Gettingstarted.xml:83
@@ -305,120 +285,89 @@
"...\n"
"\n"
"new-project:\n"
-" [echo] A new Seam project named 'helloworld' was created in the C:"
-"\\Projects directory\n"
+" [echo] A new Seam project named 'helloworld' was created in the C:\\Projects directory\n"
" [echo] Type 'seam explode' and go to http://localhost:8080/helloworld\n"
-" [echo] Eclipse Users: Add the project into Eclipse using File > New "
-"> Project and select General > Project (not Java Project)\n"
+" [echo] Eclipse Users: Add the project into Eclipse using File > New > Project and select General > Project (not Java Project)\n"
" [echo] NetBeans Users: Open the project in NetBeans\n"
"\n"
"BUILD SUCCESSFUL\n"
"Total time: 7 seconds\n"
"C:\\Projects\\jboss-seam>"
msgstr ""
+"C:\\Projects\\jboss-seam>seam new-project\n"
+"Buildfile: build.xml\n"
+"\n"
+"...\n"
+"\n"
+"new-project:\n"
+" [echo] A new Seam project named 'helloworld' was created in the C:\\Projects directory\n"
+" [echo] Type 'seam explode' and go to http://localhost:8080/helloworld\n"
+" [echo] Eclipse Users: Add the project into Eclipse using File > New > Project and select General > Project (not Java Project)\n"
+" [echo] NetBeans Users: Open the project in NetBeans\n"
+"\n"
+"BUILD SUCCESSFUL\n"
+"Total time: 7 seconds\n"
+"C:\\Projects\\jboss-seam>"
#. Tag: para
#: Gettingstarted.xml:85
#, no-c-format
-msgid ""
-"This copies the Seam jars, dependent jars and the JDBC driver jar to a new "
-"Eclipse project, and generates all needed resources and configuration files, "
-"a facelets template file and stylesheet, along with Eclipse metadata and an "
-"Ant build script. The Eclipse project will be automatically deployed to an "
-"exploded directory structure in JBoss AS as soon as you add the project "
-"using <literal>New -> Project... -> General -> Project -> Next</"
-"literal>, typing the <literal>Project name</literal> (<literal>helloworld</"
-"literal> in this case), and then clicking <literal>Finish</literal>. Do not "
-"select <literal>Java Project</literal> from the New Project wizard."
-msgstr ""
+msgid "This copies the Seam jars, dependent jars and the JDBC driver jar to a new Eclipse project, and generates all needed resources and configuration files, a facelets template file and stylesheet, along with Eclipse metadata and an Ant build script. The Eclipse project will be automatically deployed to an exploded directory structure in JBoss AS as soon as you add the project using <literal>New -> Project... -> General -> Project -> Next</literal>, typing the <literal>Project name</literal> (<literal>helloworld</literal> in this case), and then clicking <literal>Finish</literal>. Do not select <literal>Java Project</literal> from the New Project wizard."
+msgstr "Cela recopie les jars de Seam, les jars nécéssaires et le jar du pilote JDBC dans un nouveau projet Eclipse et génère tout les fichiers de configuration et les ressources requises, le fichier modèle facelets et la feuille de style, ainsi que les metadata Eclipse et le script de construction Ant. Le projet Eclipse va être automatiquement déployé dans une structure de dossiers transférer dans JBoss AS dès que vous ajouterez le projet en utilisant <literal>New -> Project... -> General -> Project -> Next</literal>, entrez le <literal>Project name</literal> ( <literal>helloworld</literal> dans notre cas), et alors cliquez sur <literal>Finish</literal>. Ne sélectionnez pas <literal>Java Project<literal> dans l'assistant de Nouveau Projet."
#. Tag: para
#: Gettingstarted.xml:93
#, no-c-format
-msgid ""
-"If your default JDK in Eclipse is not a Java SE 5 or Java SE 6 JDK, you will "
-"need to select a Java SE 5 compliant JDK using <literal>Project -> "
-"Properties -> Java Compiler</literal>."
-msgstr ""
+msgid "If your default JDK in Eclipse is not a Java SE 5 or Java SE 6 JDK, you will need to select a Java SE 5 compliant JDK using <literal>Project -> Properties -> Java Compiler</literal>."
+msgstr "Si votre JDK par défaut dans Eclipse n’est pas un SDK Java SE 5 ou Java SE 6, vous allez devoir sélectionner un JDK compatible Java SE 5 en faisant <literal>Project -> Properties -> Java Compiler</literal>."
#. Tag: para
#: Gettingstarted.xml:96
#, no-c-format
-msgid ""
-"Alternatively, you can deploy the project from outside Eclipse by typing "
-"<literal>seam explode</literal>."
-msgstr ""
+msgid "Alternatively, you can deploy the project from outside Eclipse by typing <literal>seam explode</literal>."
+msgstr "utre alternative, vous pouvez déployer le projet hors d’Eclipse en entrant <literal>seam explode</literal>."
#. Tag: para
#: Gettingstarted.xml:98
#, no-c-format
-msgid ""
-"Go to <literal>http://localhost:8080/helloworld</literal> to see a welcome "
-"page. This is a facelets page, <literal>view/home.xhtml</literal>, using the "
-"template <literal>view/layout/template.xhtml</literal>. You can edit this "
-"page, or the template, in Eclipse, and see the results "
-"<emphasis>immediately</emphasis>, by clicking refresh in your browser."
-msgstr ""
+msgid "Go to <literal>http://localhost:8080/helloworld</literal> to see a welcome page. This is a facelets page, <literal>view/home.xhtml</literal>, using the template <literal>view/layout/template.xhtml</literal>. You can edit this page, or the template, in Eclipse, and see the results <emphasis>immediately</emphasis>, by clicking refresh in your browser."
+msgstr "Allez sur <literal>http://localhost:8080/helloworld</literal> pour voir la page d’accueil. C’est une page facelets, <literal>view/home.xhtml</literal>, l, en utilisant le modèle <literal>view/layout/template.xhtml</literal>. Vous pouvez éditer cette page, ou le modèle dans Eclipse et voir le résultat <emphasis>immediately</emphasis>, en appuyant sur le bouton actualiser de votre navigateur."
#. Tag: para
#: Gettingstarted.xml:103
#, no-c-format
-msgid ""
-"Don't get scared by the XML configuration documents that were generated into "
-"the project directory. They are mostly standard Java EE stuff, the stuff you "
-"need to create once and then never look at again, and they are 90% the same "
-"between all Seam projects. (They are so easy to write that even seam-gen can "
-"do it.)"
-msgstr ""
+msgid "Don't get scared by the XML configuration documents that were generated into the project directory. They are mostly standard Java EE stuff, the stuff you need to create once and then never look at again, and they are 90% the same between all Seam projects. (They are so easy to write that even seam-gen can do it.)"
+msgstr "Ne soyez pas effrayé par les documents de configuration XML qui ont été généré dans le dossier du projet. Ils sont pour la plus part des trucs standards Java EE, un truc créé une fois et plus jamais consulté ensuite et ceci est le cas dans 90% des projets Seam. ( ils sont si facile à écrire que même seam-gen peut le faire.)"
#. Tag: para
#: Gettingstarted.xml:107
#, no-c-format
-msgid ""
-"The generated project includes three database and persistence "
-"configurations. The <literal>persistence-test.xml</literal> and "
-"<literal>import-test.sql</literal> files are used when running the TestNG "
-"unit tests against HSQLDB. The database schema and the test data in "
-"<literal>import-test.sql</literal> is always exported to the database before "
-"running tests. The <literal>myproject-dev-ds.xml</literal>, "
-"<literal>persistence-dev.xml</literal>and <literal>import-dev.sql</literal> "
-"files are for use when deploying the application to your development "
-"database. The schema might be exported automatically at deployment, "
-"depending upon whether you told seam-gen that you are working with an "
-"existing database. The <literal>myproject-prod-ds.xml</literal>, "
-"<literal>persistence-prod.xml</literal>and <literal>import-prod.sql</"
-"literal> files are for use when deploying the application to your production "
-"database. The schema is not exported automatically at deployment."
-msgstr ""
+msgid "The generated project includes three database and persistence configurations. The <literal>persistence-test.xml</literal> and <literal>import-test.sql</literal> files are used when running the TestNG unit tests against HSQLDB. The database schema and the test data in <literal>import-test.sql</literal> is always exported to the database before running tests. The <literal>myproject-dev-ds.xml</literal>, <literal>persistence-dev.xml</literal>and <literal>import-dev.sql</literal> files are for use when deploying the application to your development database. The schema might be exported automatically at deployment, depending upon whether you told seam-gen that you are working with an existing database. The <literal>myproject-prod-ds.xml</literal>, <literal>persistence-prod.xml</literal>and <literal>import-prod.sql</literal> files are for use when deploying the application to your production database. The schema is not exported automatically at deployment."
+msgstr "Le projet généré inclu trois bases de données et des configurations de persistance. Les fichiers <literal>persistence-test.xml</literal>, persistence-test.xml et <literal>import-test.sql</literal> sont utilisés quand vous exécutez les tests unitaires testNG avec HSQLDB. Le schéma de base de données et les données de test dans <literal>import-test.sql</literal> sont toujours exportés vers la base de données avant l’exécution des tests. Les fichiers <literal>myproject-dev-ds.xml</literal>, <literal>persistence-dev.xml</literal> et <literal>import-dev.sql</literal> ont utilisés pendant le déploiement de l’application vers la base de données de développement. Le schéma peut être exporté automatiquement pendant le déploiement, cela dépend si vous avez indiqué à seam-gen que vous travaillez avec une base de données déjà existante. Les fichiers <literal>myproject-prod-ds.xml</literal>, <literal>persistence-prod.xml</literal> et <literal>import!
-prod.sql</literal> sont utilisés pendant le déploiement de l’application vers la base de données de production. Le schema n’est pas exporté automatiquement pendant le déploiement."
#. Tag: title
#: Gettingstarted.xml:121
#, no-c-format
msgid "Creating a new action"
-msgstr ""
+msgstr "Création d'une nouvelle action"
#. Tag: para
#: Gettingstarted.xml:123
#, no-c-format
-msgid ""
-"If you're used to traditional action-style web frameworks, you're probably "
-"wondering how you can create a simple web page with a stateless action "
-"method in Java. If you type:"
-msgstr ""
+msgid "If you're used to traditional action-style web frameworks, you're probably wondering how you can create a simple web page with a stateless action method in Java. If you type:"
+msgstr "Si vous avez l’habitude de serveur d’application web de style action traditionnel, vous vous demandez comment créer une simple page web avec un méthode d’action sans état en Java. Si vous entrez :"
#. Tag: programlisting
#: Gettingstarted.xml:126
#, no-c-format
msgid "seam new-action"
-msgstr ""
+msgstr "seam new-action"
#. Tag: para
#: Gettingstarted.xml:128
#, no-c-format
-msgid ""
-"Seam will prompt for some information, and generate a new facelets page and "
-"Seam component for your project."
-msgstr ""
+msgid "Seam will prompt for some information, and generate a new facelets page and Seam component for your project."
+msgstr "Seam va vous demander des informations, et génèrer une nouvelle page facelets ainsi qu’un composant Seam pour votre projet."
#. Tag: programlisting
#: Gettingstarted.xml:131
@@ -446,75 +395,87 @@
"setup-filters:\n"
"\n"
"new-action:\n"
-" [echo] Creating a new stateless session bean component with an action "
-"method\n"
-" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss"
-"\\helloworld\n"
-" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss"
-"\\helloworld\n"
-" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss"
-"\\helloworld\\test\n"
-" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss"
-"\\helloworld\\test\n"
+" [echo] Creating a new stateless session bean component with an action method\n"
+" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss\\helloworld\n"
+" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss\\helloworld\n"
+" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss\\helloworld\\test\n"
+" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss\\helloworld\\test\n"
" [copy] Copying 1 file to C:\\Projects\\helloworld\\view\n"
-" [echo] Type 'seam restart' and go to http://localhost:8080/helloworld/"
-"ping.seam\n"
+" [echo] Type 'seam restart' and go to http://localhost:8080/helloworld/ping.seam\n"
"\n"
"BUILD SUCCESSFUL\n"
"Total time: 13 seconds\n"
"C:\\Projects\\jboss-seam>"
msgstr ""
+"C:\\Projects\\jboss-seam>seam new-action\n"
+"Buildfile: build.xml\n"
+"\n"
+"validate-workspace:\n"
+"\n"
+"validate-project:\n"
+"\n"
+"action-input:\n"
+" [input] Enter the Seam component name\n"
+"ping\n"
+" [input] Enter the local interface name [Ping]\n"
+"\n"
+" [input] Enter the bean class name [PingBean]\n"
+"\n"
+" [input] Enter the action method name [ping]\n"
+"\n"
+" [input] Enter the page name [ping]\n"
+"\n"
+"\n"
+"setup-filters:\n"
+"\n"
+"new-action:\n"
+" [echo] Creating a new stateless session bean component with an action method\n"
+" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss\\helloworld\n"
+" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss\\helloworld\n"
+" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss\\helloworld\\test\n"
+" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss\\helloworld\\test\n"
+" [copy] Copying 1 file to C:\\Projects\\helloworld\\view\n"
+" [echo] Type 'seam restart' and go to http://localhost:8080/helloworld/ping.seam\n"
+"\n"
+"BUILD SUCCESSFUL\n"
+"Total time: 13 seconds\n"
+"C:\\Projects\\jboss-seam>"
#. Tag: para
#: Gettingstarted.xml:133
#, no-c-format
-msgid ""
-"Because we've added a new Seam component, we need to restart the exploded "
-"directory deployment. You can do this by typing <literal>seam restart</"
-"literal>, or by running the <literal>restart</literal> target in the "
-"generated project <literal>build.xml</literal> file from inside Eclipse. "
-"Another way to force a restart is to edit the file <literal>resources/META-"
-"INF/application.xml</literal> in Eclipse. <emphasis>Note that you do not "
-"need to restart JBoss each time you change the application.</emphasis>"
-msgstr ""
+msgid "Because we've added a new Seam component, we need to restart the exploded directory deployment. You can do this by typing <literal>seam restart</literal>, or by running the <literal>restart</literal> target in the generated project <literal>build.xml</literal> file from inside Eclipse. Another way to force a restart is to edit the file <literal>resources/META-INF/application.xml</literal> in Eclipse. <emphasis>Note that you do not need to restart JBoss each time you change the application.</emphasis>"
+msgstr "Vue que nous avons ajouté un nouveau composant Seam, nous devons redémarrer le déploiement de la structure du dossier. Vous pouvez faire cela en entrant <literal>seam restart</literal>, en en execution la cible <literal>restart</literal> qui se trouve dans le fichier <literal>build.xml</literal> avec Eclipse. Une autre façon de forcer un redémarrage est d’éditer le fichier <literal>resources/META-INF/application.xml</literal> dans Eclipse. <emphasis>Notez que vous navez pas à redémarrer JBoss à chaque vois que vous modifier votre application</emphasis>."
#. Tag: para
#: Gettingstarted.xml:139
#, no-c-format
-msgid ""
-"Now go to <literal>http://localhost:8080/helloworld/ping.seam</literal> and "
-"click the button. You can see the code behind this action by looking in the "
-"project <literal>src</literal> directory. Put a breakpoint in the "
-"<literal>ping()</literal> method, and click the button again."
-msgstr ""
+msgid "Now go to <literal>http://localhost:8080/helloworld/ping.seam</literal> and click the button. You can see the code behind this action by looking in the project <literal>src</literal> directory. Put a breakpoint in the <literal>ping()</literal> method, and click the button again."
+msgstr "Maintenant allez à <literal>http://localhost:8080/helloworld/ping.seam</literal> et cliquez sur le bouton. Vous pouvez voir le code ci-dessous en action en regardant dans le dossier <literal>src</literal>. Placez un point d’arrêt dans la méthode <literal>ping()</literal> et cliquez sur le bouton de nouveau."
#. Tag: para
#: Gettingstarted.xml:143
#, no-c-format
-msgid ""
-"Finally, locate the <literal>PingTest.xml</literal> file in the test package "
-"and run the integration tests using the TestNG plugin for Eclipse. "
-"Alternatively, run the tests using <literal>seam test</literal> or the "
-"<literal>test</literal> target of the generated build."
-msgstr ""
+msgid "Finally, locate the <literal>PingTest.xml</literal> file in the test package and run the integration tests using the TestNG plugin for Eclipse. Alternatively, run the tests using <literal>seam test</literal> or the <literal>test</literal> target of the generated build."
+msgstr "Finalement, localisez le fichier <literal>PingTest.xml</literal> dans le package de test et lancez les tests d’intégration en utilisant le plugin testNG pour Eclipse. Autre alternative, lancez les tests en utilisant <literal>seam test</literal> ou via la cible du fichier généré <literal>test</literal>."
#. Tag: title
#: Gettingstarted.xml:149
#, no-c-format
msgid "Creating a form with an action"
-msgstr ""
+msgstr "Création d'un formulaire avec une action"
#. Tag: para
#: Gettingstarted.xml:151
#, no-c-format
msgid "The next step is to create a form. Type:"
-msgstr ""
+msgstr "L’étape suivante est de créer un formulaire Entrez :"
#. Tag: programlisting
#: Gettingstarted.xml:153
#, no-c-format
msgid "seam new-form"
-msgstr ""
+msgstr "seam new-form"
#. Tag: programlisting
#: Gettingstarted.xml:155
@@ -542,331 +503,277 @@
"setup-filters:\n"
"\n"
"new-form:\n"
-" [echo] Creating a new stateful session bean component with an action "
-"method\n"
+" [echo] Creating a new stateful session bean component with an action method\n"
" [copy] Copying 1 file to C:\\Projects\\hello\\src\\hot\\com\\hello\n"
" [copy] Copying 1 file to C:\\Projects\\hello\\src\\hot\\com\\hello\n"
-" [copy] Copying 1 file to C:\\Projects\\hello\\src\\hot\\com\\hello"
-"\\test\n"
+" [copy] Copying 1 file to C:\\Projects\\hello\\src\\hot\\com\\hello\\test\n"
" [copy] Copying 1 file to C:\\Projects\\hello\\view\n"
-" [copy] Copying 1 file to C:\\Projects\\hello\\src\\hot\\com\\hello"
-"\\test\n"
-" [echo] Type 'seam restart' and go to http://localhost:8080/hello/hello."
-"seam\n"
+" [copy] Copying 1 file to C:\\Projects\\hello\\src\\hot\\com\\hello\\test\n"
+" [echo] Type 'seam restart' and go to http://localhost:8080/hello/hello.seam\n"
"\n"
"BUILD SUCCESSFUL\n"
"Total time: 5 seconds\n"
"C:\\Projects\\jboss-seam>"
msgstr ""
+"C:\\Projects\\jboss-seam>seam new-form\n"
+"Buildfile: C:\\Projects\\jboss-seam\\seam-gen\\build.xml\n"
+"\n"
+"validate-workspace:\n"
+"\n"
+"validate-project:\n"
+"\n"
+"action-input:\n"
+" [input] Enter the Seam component name\n"
+"hello\n"
+" [input] Enter the local interface name [Hello]\n"
+"\n"
+" [input] Enter the bean class name [HelloBean]\n"
+"\n"
+" [input] Enter the action method name [hello]\n"
+"\n"
+" [input] Enter the page name [hello]\n"
+"\n"
+"\n"
+"setup-filters:\n"
+"\n"
+"new-form:\n"
+" [echo] Creating a new stateful session bean component with an action method\n"
+" [copy] Copying 1 file to C:\\Projects\\hello\\src\\hot\\com\\hello\n"
+" [copy] Copying 1 file to C:\\Projects\\hello\\src\\hot\\com\\hello\n"
+" [copy] Copying 1 file to C:\\Projects\\hello\\src\\hot\\com\\hello\\test\n"
+" [copy] Copying 1 file to C:\\Projects\\hello\\view\n"
+" [copy] Copying 1 file to C:\\Projects\\hello\\src\\hot\\com\\hello\\test\n"
+" [echo] Type 'seam restart' and go to http://localhost:8080/hello/hello.seam\n"
+"\n"
+"BUILD SUCCESSFUL\n"
+"Total time: 5 seconds\n"
+"C:\\Projects\\jboss-seam>"
#. Tag: para
#: Gettingstarted.xml:157
#, no-c-format
-msgid ""
-"Restart the application again, and go to <literal>http://localhost:8080/"
-"helloworld/hello.seam</literal>. Then take a look at the generated code. Run "
-"the test. Try adding some new fields to the form and Seam component "
-"(remember to restart the deployment each time you change the Java code)."
-msgstr ""
+msgid "Restart the application again, and go to <literal>http://localhost:8080/helloworld/hello.seam</literal>. Then take a look at the generated code. Run the test. Try adding some new fields to the form and Seam component (remember to restart the deployment each time you change the Java code)."
+msgstr "Relancer l’application encore et allez sur <literal>http://localhost:8080/helloworld/hello.seam</literal>. Ensuite, jetez un coup d’œil sur le code généré. Lancez le test. Essayez d’ajouter de nouveau champs dans le formulaire et dans le composant Seam (rappelez vous de redémarrer le deploiement chaque fois que vous modifiez le code Java)."
#. Tag: title
#: Gettingstarted.xml:163
#, no-c-format
msgid "Generating an application from an existing database"
-msgstr ""
+msgstr "Generation d'une application depuis une base de données existante"
#. Tag: para
#: Gettingstarted.xml:165
#, no-c-format
-msgid ""
-"Manually create some tables in your database. (If you need to switch to a "
-"different database, just run <literal>seam setup</literal> again.) Now type:"
-msgstr ""
+msgid "Manually create some tables in your database. (If you need to switch to a different database, just run <literal>seam setup</literal> again.) Now type:"
+msgstr "Manuellement créez plusieurs tables dans votre base de données. (Si vous devez basculer vers une autre base de données, relancez juste encore une fois <literal>seam setup</literal>.) Maintenant entrez :"
#. Tag: programlisting
#: Gettingstarted.xml:168
#, no-c-format
msgid "seam generate-entities"
-msgstr ""
+msgstr "seam generate-entities"
#. Tag: para
#: Gettingstarted.xml:170
#, no-c-format
-msgid ""
-"Restart the deployment, and go to <literal>http://localhost:8080/helloworld</"
-"literal>. You can browse the database, edit existing objects, and create new "
-"objects. If you look at the generated code, you'll probably be amazed how "
-"simple it is! Seam was designed so that data access code is easy to write by "
-"hand, even for people who don't want to cheat by using seam-gen."
-msgstr ""
+msgid "Restart the deployment, and go to <literal>http://localhost:8080/helloworld</literal>. You can browse the database, edit existing objects, and create new objects. If you look at the generated code, you'll probably be amazed how simple it is! Seam was designed so that data access code is easy to write by hand, even for people who don't want to cheat by using seam-gen."
+msgstr "Relancez le déploiement et allez sur <literal>http://localhost:8080/helloworld</literal>. Vous pouvez naviguer dans la base de données, éditer les objets existants et créez de nouveaux objets. Si vous allez jeter un coup d’œil au code généré, vous être probablement émerveillé par sa simplicité ! Seam a été prévu pour que le code d’accès aux données soit simple à écrire à la main, même pour les gens qui ne veulent pas tricher en utilisant seam-gen."
#. Tag: title
#: Gettingstarted.xml:177
#, no-c-format
msgid "Generating an application from existing JPA/EJB3 entities"
-msgstr ""
+msgstr "Génération d'une application depuis des entitées JPA/EJB3 existantes"
#. Tag: para
#: Gettingstarted.xml:179
#, no-c-format
-msgid ""
-"Place your existing, valid entity classes inside the <literal>src/main</"
-"literal>. Now type"
-msgstr ""
+msgid "Place your existing, valid entity classes inside the <literal>src/main</literal>. Now type"
+msgstr "Placez votre existant, les classes entitées valides dans <literal>src/main</literal>. Ensuite entrez"
#. Tag: programlisting
#: Gettingstarted.xml:181
#, no-c-format
msgid "seam generate-ui"
-msgstr ""
+msgstr "seam generate-ui"
#. Tag: para
#: Gettingstarted.xml:183
#, no-c-format
-msgid ""
-"Restart the deployment, and go to <literal>http://localhost:8080/helloworld</"
-"literal>."
-msgstr ""
+msgid "Restart the deployment, and go to <literal>http://localhost:8080/helloworld</literal>."
+msgstr "Redémarrez le déploiement, et allez sur <literal>http://localhost:8080/helloworld</literal>."
#. Tag: title
#: Gettingstarted.xml:187
#, no-c-format
msgid "Deploying the application as an EAR"
-msgstr ""
+msgstr "Déploiement d'une application avec un EAR"
#. Tag: para
#: Gettingstarted.xml:189
#, no-c-format
-msgid ""
-"Finally, we want to be able to deploy the application using standard Java EE "
-"5 packaging. First, we need to remove the exploded directory by running "
-"<literal>seam unexplode</literal>. To deploy the EAR, we can type "
-"<literal>seam deploy</literal> at the command prompt, or run the "
-"<literal>deploy</literal> target of the generated project build script. You "
-"can undeploy using <literal>seam undeploy</literal> or the "
-"<literal>undeploy</literal> target."
-msgstr ""
+msgid "Finally, we want to be able to deploy the application using standard Java EE 5 packaging. First, we need to remove the exploded directory by running <literal>seam unexplode</literal>. To deploy the EAR, we can type <literal>seam deploy</literal> at the command prompt, or run the <literal>deploy</literal> target of the generated project build script. You can undeploy using <literal>seam undeploy</literal> or the <literal>undeploy</literal> target."
+msgstr "Au final, nous voulons être capable de déployer l'application en utilisant l'empaquetage standard de Java EE. En premier, vous avons besoin de retirer le dossier fabriqué en exécutant <literal>seam unexplode</literal>. Pour déployer le EAR, nous pouvons entrer <literal>seam deploy</literal> à l'invite de commande, ou exécuter la cible <literal>deploy</literal> du script généré de construction du projet. Vous pouvez le désinstaller en utilisant <literal>seam undeploy</literal> ou la cible <literal>undeploy</literal>."
#. Tag: para
#: Gettingstarted.xml:195
#, no-c-format
-msgid ""
-"By default, the application will be deployed with the <emphasis>dev profile</"
-"emphasis>. The EAR will include the <literal>persistence-dev.xml</literal> "
-"and <literal>import-dev.sql</literal> files, and the <literal>myproject-dev-"
-"ds.xml</literal> file will be deployed. You can change the profile, and use "
-"the <emphasis>prod profile</emphasis>, by typing"
-msgstr ""
+msgid "By default, the application will be deployed with the <emphasis>dev profile</emphasis>. The EAR will include the <literal>persistence-dev.xml</literal> and <literal>import-dev.sql</literal> files, and the <literal>myproject-dev-ds.xml</literal> file will be deployed. You can change the profile, and use the <emphasis>prod profile</emphasis>, by typing"
+msgstr "Par défaut, l'application sera déployée avec le <emphasis>dev profile</emphasis>. Le EAR inclura les fichiers <literal>persistence-dev.xml</literal> et <literal>import-dev.sql</literal>, et le fichier <literal>myproject-dev-ds.xml</literal> sera déployé. Vous pouvez modifier le profil et utilisez le <emphasis>prod profile</emphasis>, en entrant"
#. Tag: programlisting
#: Gettingstarted.xml:200
#, no-c-format
msgid "seam -Dprofile=prod deploy"
-msgstr ""
+msgstr "seam -Dprofile=prod deploy"
#. Tag: para
#: Gettingstarted.xml:202
#, no-c-format
-msgid ""
-"You can even define new deployment profiles for your application. Just add "
-"appropriately named files to your project—for example, <literal>persistence-"
-"staging.xml</literal>, <literal>import-staging.sql</literal> and "
-"<literal>myproject-staging-ds.xml</literal>—and select the name of the "
-"profile using <literal>-Dprofile=staging</literal>."
-msgstr ""
+msgid "You can even define new deployment profiles for your application. Just add appropriately named files to your project—for example, <literal>persistence-staging.xml</literal>, <literal>import-staging.sql</literal> and <literal>myproject-staging-ds.xml</literal>—and select the name of the profile using <literal>-Dprofile=staging</literal>."
+msgstr "Vous pouvez même définir de nouveaux profils de déploiement pour votre application. Ajoutez juste les fichier dénommés de manière appropriés à votre projet —par exemple, <literal>persistence-staging.xml</literal>, <literal>import-staging.sql</literal> et <literal>myproject-staging-ds.xml</literal>—et sélectionnez le nom du profil en utilisant <literal>-Dprofile=staging</literal>."
#. Tag: title
#: Gettingstarted.xml:209
#, no-c-format
msgid "Seam and incremental hot deployment"
-msgstr ""
+msgstr "Seam et le déploiement incrémental à chaud"
#. Tag: para
#: Gettingstarted.xml:211
#, no-c-format
-msgid ""
-"When you deploy your Seam application as an exploded directory, you'll get "
-"some support for incremental hot deployment at development time. You need to "
-"enable debug mode in both Seam and Facelets, by adding this line to "
-"<literal>components.xml</literal>:"
-msgstr ""
+msgid "When you deploy your Seam application as an exploded directory, you'll get some support for incremental hot deployment at development time. You need to enable debug mode in both Seam and Facelets, by adding this line to <literal>components.xml</literal>:"
+msgstr "Quand vous déployez votre application Seam dans un dossier complet, vous allez avoir un peu d'indications pour le déploiement incrémental à chaud au moment du développement. Vous avez besoin d'activer le mode debug à la fois dans Seam et Facelets, en ajoutant cette ligne à <literal>components.xml</literal>:"
#. Tag: programlisting
#: Gettingstarted.xml:215
#, no-c-format
msgid "<![CDATA[<core:init debug=\"true\">]]>"
-msgstr ""
+msgstr "<![CDATA[<core:init debug=\"true\">]]>"
#. Tag: para
#: Gettingstarted.xml:217
#, no-c-format
-msgid ""
-"Now, the following files may be redeployed without requiring a full restart "
-"of the web application:"
-msgstr ""
+msgid "Now, the following files may be redeployed without requiring a full restart of the web application:"
+msgstr "Maintenant, les fichiers suivants devraient être redéployés sans nécéssiter un rédémarrage complet de l'application web:"
#. Tag: para
#: Gettingstarted.xml:221
#, no-c-format
msgid "any facelets page"
-msgstr ""
+msgstr "toutes les pages facelets"
#. Tag: para
#: Gettingstarted.xml:225
#, no-c-format
msgid "any <literal>pages.xml</literal> file"
-msgstr ""
+msgstr "et tout fichier <literal>pages.xml</literal>"
#. Tag: para
#: Gettingstarted.xml:229
#, no-c-format
-msgid ""
-"But if we want to change any Java code, we still need to do a full restart "
-"of the application. (In JBoss this may be accomplished by touching the top "
-"level deployment descriptor: <literal>application.xml</literal> for an EAR "
-"deployment, or <literal>web.xml</literal> for a WAR deployment.)"
-msgstr ""
+msgid "But if we want to change any Java code, we still need to do a full restart of the application. (In JBoss this may be accomplished by touching the top level deployment descriptor: <literal>application.xml</literal> for an EAR deployment, or <literal>web.xml</literal> for a WAR deployment.)"
+msgstr "Mais si nous voulons changer le code Java, nous continuons à avoir besoin de réaliser un redémarrage complet de l’application.( Dans JBoss, cela peut être accompli en changeant le descripteur de déploiement de plus haut niveau <literal>application.xml</literal> pour un déploiement d'un EAR ou <literal>web.xml</literal> pour un déploiement d'un WAR.) "
#. Tag: para
#: Gettingstarted.xml:233
#, no-c-format
-msgid ""
-"But if you really want a fast edit/compile/test cycle, Seam supports "
-"incremental redeployment of JavaBean components. To make use of this "
-"functionality, you must deploy the JavaBean components into the <literal>WEB-"
-"INF/dev</literal> directory, so that they will be loaded by a special Seam "
-"classloader, instead of by the WAR or EAR classloader."
-msgstr ""
+msgid "But if you really want a fast edit/compile/test cycle, Seam supports incremental redeployment of JavaBean components. To make use of this functionality, you must deploy the JavaBean components into the <literal>WEB-INF/dev</literal> directory, so that they will be loaded by a special Seam classloader, instead of by the WAR or EAR classloader."
+msgstr "Mais si vous voulez réellement un cycle rapide d'édition/compilation/test, Seam supporte un redéploiement incrémental des composants JavaBeans. Pour utiliser cette fonctionnalité, vous devez déployer les composants JavaBeans dans le dossier <literal>WEB-INF/dev</literal>, donc il vont être rechargé par un chargeur de classes spécialisé de Seam au lieu du chargeur de classes WAR ou EAR."
#. Tag: para
#: Gettingstarted.xml:238
#, no-c-format
msgid "You need to be aware of the following limitations:"
-msgstr ""
+msgstr "Vous devez être au courrant sur les limitations suivantes:"
#. Tag: para
#: Gettingstarted.xml:242
#, no-c-format
-msgid ""
-"the components must be JavaBean components, they cannot be EJB3 beans (we "
-"are working on fixing this limitation)"
-msgstr ""
+msgid "the components must be JavaBean components, they cannot be EJB3 beans (we are working on fixing this limitation)"
+msgstr "les composants doivent être des composants JavaBeans, ils ne peuvent pas être des beans EJB3 (nous travaillons pour régler cette limitation)"
#. Tag: para
#: Gettingstarted.xml:247
#, no-c-format
msgid "entities can never be hot-deployed"
-msgstr ""
+msgstr "les entités ne peuvent pas être déployées à chaud"
#. Tag: para
#: Gettingstarted.xml:251
#, no-c-format
-msgid ""
-"components deployed via <literal>components.xml</literal> may not be hot-"
-"deployed"
-msgstr ""
+msgid "components deployed via <literal>components.xml</literal> may not be hot-deployed"
+msgstr "les composants déployés via <literal>components.xml</literal> ne devraient pas être déployées à chaud"
#. Tag: para
#: Gettingstarted.xml:255
#, no-c-format
-msgid ""
-"the hot-deployable components will not be visible to any classes deployed "
-"outside of <literal>WEB-INF/dev</literal>"
-msgstr ""
+msgid "the hot-deployable components will not be visible to any classes deployed outside of <literal>WEB-INF/dev</literal>"
+msgstr "les composants déployables à chaud ne seront pas visibles dans les classes déployées hors de <literal>WEB-INF/dev</literal>"
#. Tag: para
#: Gettingstarted.xml:260
#, no-c-format
-msgid ""
-"Seam debug mode must be enabled and <literal>jboss-seam-debug.jar</literal> "
-"must be in <literal>WEB-INF/lib</literal>"
-msgstr ""
+msgid "Seam debug mode must be enabled and <literal>jboss-seam-debug.jar</literal> must be in <literal>WEB-INF/lib</literal>"
+msgstr "e mode de debug de Seam doit être activé et <literal>jboss-seam-debug.jar</literal> doit être dans <literal>WEB-INF/lib</literal>"
#. Tag: para
#: Gettingstarted.xml:265
#, no-c-format
msgid "You must have the Seam filter installed in web.xml"
-msgstr ""
+msgstr "Vous devez avoir le filtre de Seam installé dans web.xml"
#. Tag: para
#: Gettingstarted.xml:269
#, no-c-format
-msgid ""
-"You may see errors if the system is placed under any load and debug is "
-"enabled."
-msgstr ""
+msgid "You may see errors if the system is placed under any load and debug is enabled."
+msgstr "Vous pouvez avoir des erreurs si le systèm est placé en chargement et débogage est actif."
#. Tag: para
#: Gettingstarted.xml:274
#, no-c-format
-msgid ""
-"If you create a WAR project using seam-gen, incremental hot deployment is "
-"available out of the box for classes in the <literal>src/hot</literal> "
-"source directory. However, seam-gen does not support incremental hot "
-"deployment for EAR projects."
-msgstr ""
+msgid "If you create a WAR project using seam-gen, incremental hot deployment is available out of the box for classes in the <literal>src/hot</literal> source directory. However, seam-gen does not support incremental hot deployment for EAR projects."
+msgstr "Si vous créé un projet WAR en utilisant seam-gen, le déploiement incrémental à chaud est disponible automatiquement pour les classes placées dans le dossier source <literal>src/hot</literal>. Mais, sean-gen ne permet le support du déploiement incrémental à chaud pour les projets EAR."
#. Tag: title
#: Gettingstarted.xml:280
#, no-c-format
msgid "Using Seam with JBoss 4.0"
-msgstr ""
+msgstr "Utilisation de Seam avec JBoss 4.0"
#. Tag: para
#: Gettingstarted.xml:282
#, no-c-format
-msgid ""
-"Seam 2 was developed for JavaServer Faces 1.2. When using JBoss AS, we "
-"recommend using JBoss 4.2 or JBoss 5.0, both of which bundle the JSF 1.2 "
-"reference implementation. However, it is still possible to use Seam 2 on the "
-"JBoss 4.0 platform. There are two basic steps required to do this: install "
-"an EJB3-enabled version of JBoss 4.0 and replace MyFaces with the JSF 1.2 "
-"reference implementation. Once you complete these steps, Seam 2 applications "
-"can be deployed to JBoss 4.0."
-msgstr ""
+msgid "Seam 2 was developed for JavaServer Faces 1.2. When using JBoss AS, we recommend using JBoss 4.2 or JBoss 5.0, both of which bundle the JSF 1.2 reference implementation. However, it is still possible to use Seam 2 on the JBoss 4.0 platform. There are two basic steps required to do this: install an EJB3-enabled version of JBoss 4.0 and replace MyFaces with the JSF 1.2 reference implementation. Once you complete these steps, Seam 2 applications can be deployed to JBoss 4.0."
+msgstr "Seam 2 a été développé pour JavaServer Faces 1.2. Avec l’utilisation de JBoss AS, nous vous recommandons d’utiliser JBoss 4.2 ou JBoss 5.0 les deux sont liés avec l'implémentation de référence JSF 1.2. Malgré tout, il est toujours possible d’utiliser Seam 2 sur une plateforme JBoss 4.0. il y a deux étapes de bases pour faire cela : installer une version de JBoss 4.0 avec EJB3 activé et remplacer MyFaces par l’implémentation de référence JSF 1.2. Une fois que ces étapes sont faites, l’application Seam 2 peut être déployé sur JBoss 4.0."
#. Tag: title
#: Gettingstarted.xml:289
#, no-c-format
msgid "Install JBoss 4.0"
-msgstr ""
+msgstr "Installation de JBoss 4.0"
#. Tag: para
#: Gettingstarted.xml:290
#, no-c-format
-msgid ""
-"JBoss 4.0 does not ship a default configuration compatible with Seam. To run "
-"Seam, you must install JBoss 4.0.5 using the JEMS 1.2 installer with the "
-"ejb3 profile selected. Seam will not run with an installation that doesn't "
-"include EJB3 support. The JEMS installer can be downloaded from <ulink url="
-"\"http://labs.jboss.com/jemsinstaller/downloads\">http://labs.jboss.com/"
-"jemsinstaller/downloads</ulink>."
-msgstr ""
+msgid "JBoss 4.0 does not ship a default configuration compatible with Seam. To run Seam, you must install JBoss 4.0.5 using the JEMS 1.2 installer with the ejb3 profile selected. Seam will not run with an installation that doesn't include EJB3 support. The JEMS installer can be downloaded from <ulink url=\"http://labs.jboss.com/jemsinstaller/downloads\">http://labs.jboss.com/jemsinstaller/downloads</ulink>."
+msgstr "JBoss 4.0 ne propose pas une configuration par défaut compatible avec Seam. Pour exécuter Seam, vous devez installer JBoss 4.0.5 en utilisant l’installateur JEMS 1.2 avec le profil ejv3 sélectionné. Seam ne va pas s’exécuter avec une installation qui n’inclu pas le support EJB3. L’installateur JEMS peut être téléchargé depuis <ulink url=\"http://labs.jboss.com/jemsinstaller/downloads\">http://labs.jboss.com/jemsinstaller/downloads</ulink>."
#. Tag: title
#: Gettingstarted.xml:297
#, no-c-format
msgid "Install the JSF 1.2 RI"
-msgstr ""
+msgstr "Installation de JSF 1.2 RI"
#. Tag: para
#: Gettingstarted.xml:299
#, no-c-format
-msgid ""
-"The web configuration for JBoss 4.0 can be found in the <literal>server/"
-"default/deploy/jbossweb-tomcat55.sar</literal>. You'll need to delete "
-"<literal>myfaces-api.jar</literal> any <literal>myfaces-impl.jar</literal> "
-"from the <literal>jsf-libs </literal>directory. Then, you'll need to copy "
-"<literal>jsf-api.jar</literal>, <literal>jsf-impl.jar</literal>, <literal>el-"
-"api.jar</literal>, and <literal>el-ri.jar</literal> to that directory. The "
-"JSF JARs can be found in the Seam <literal>lib</literal> directory. The el "
-"JARs can be obtained from the Seam 1.2 release."
-msgstr ""
+msgid "The web configuration for JBoss 4.0 can be found in the <literal>server/default/deploy/jbossweb-tomcat55.sar</literal>. You'll need to delete <literal>myfaces-api.jar</literal> any <literal>myfaces-impl.jar</literal> from the <literal>jsf-libs </literal>directory. Then, you'll need to copy <literal>jsf-api.jar</literal>, <literal>jsf-impl.jar</literal>, <literal>el-api.jar</literal>, and <literal>el-ri.jar</literal> to that directory. The JSF JARs can be found in the Seam <literal>lib</literal> directory. The el JARs can be obtained from the Seam 1.2 release."
+msgstr "La configuration de JBoss 4.0 peut être trouvée dans <literal>server/default/deploy/jbossweb-tomcat55.sar</literal>. Vous allez avoir besoin d'effacer <literal>myfaces-api.jar</literal> et <literal>myfaces-impl.jar</literal> du dossier <literal>jsf-libs</literal>. Ensuite, vous allez devoir copier <literal>jsf-api.jar</literal>, <literal>jsf-impl.jar</literal>, <literal>el-api.jar</literal>, et <literal>el-ri.jar</literal> dans ce même dossier. Les JARs de JSF peuvent être trouvés dans le dossier <literal>lib</literal> de Seam. Les JARs EL peuvent être obtenue depuis la version 1.2 de Seam. "
#. Tag: para
#: Gettingstarted.xml:307
#, no-c-format
-msgid ""
-"You'll also need to edit the <literal>conf/web.xml</literal>, replacing "
-"<literal>myfaces-impl.jar</literal> with <literal>jsf-impl.jar</literal>."
-msgstr ""
+msgid "You'll also need to edit the <literal>conf/web.xml</literal>, replacing <literal>myfaces-impl.jar</literal> with <literal>jsf-impl.jar</literal>."
+msgstr "Vous allez aussi devoir éditer le fichier <literal>conf/web.xml</literal>, en remplaçant<literal>myfaces-impl.jar</literal> par <literal>jsf-impl.jar</literal>."
+
15 years, 1 month
- 1
- 0
Seam SVN: r11600 - tags/JBPAPP_5_0-CR5/build.
by seam-commits＠lists.jboss.org
Author: manaRH
Date: 2009-10-16 15:41:50 -0400 (Fri, 16 Oct 2009)
New Revision: 11600
Modified:
tags/JBPAPP_5_0-CR5/build/root.pom.xml
Log:
upgraded jboss-vfs
Modified: tags/JBPAPP_5_0-CR5/build/root.pom.xml
===================================================================
--- tags/JBPAPP_5_0-CR5/build/root.pom.xml 2009-10-16 18:55:53 UTC (rev 11599)
+++ tags/JBPAPP_5_0-CR5/build/root.pom.xml 2009-10-16 19:41:50 UTC (rev 11600)
@@ -878,7 +878,7 @@
<dependency>
<groupId>org.jboss</groupId>
<artifactId>jboss-vfs</artifactId>
- <version>2.1.2.GA</version>
+ <version>2.1.3.SP1</version>
</dependency>
<dependency>
15 years, 1 month
- 1
- 0
Seam SVN: r11599 - branches/enterprise/JBPAPP_5_0/build.
by seam-commits＠lists.jboss.org
Author: manaRH
Date: 2009-10-16 14:55:53 -0400 (Fri, 16 Oct 2009)
New Revision: 11599
Modified:
branches/enterprise/JBPAPP_5_0/build/root.pom.xml
Log:
upgraded jboss-vfs
Modified: branches/enterprise/JBPAPP_5_0/build/root.pom.xml
===================================================================
--- branches/enterprise/JBPAPP_5_0/build/root.pom.xml 2009-10-16 17:24:54 UTC (rev 11598)
+++ branches/enterprise/JBPAPP_5_0/build/root.pom.xml 2009-10-16 18:55:53 UTC (rev 11599)
@@ -878,7 +878,7 @@
<dependency>
<groupId>org.jboss</groupId>
<artifactId>jboss-vfs</artifactId>
- <version>2.1.2.GA</version>
+ <version>2.1.3.SP1</version>
</dependency>
<dependency>
15 years, 1 month
- 1
- 0
Seam SVN: r11598 - tags.
by seam-commits＠lists.jboss.org
Author: manaRH
Date: 2009-10-16 13:24:54 -0400 (Fri, 16 Oct 2009)
New Revision: 11598
Added:
tags/JBPAPP_5_0-CR5/
Log:
tagged Seam EAP5 CR5
Copied: tags/JBPAPP_5_0-CR5 (from rev 11597, branches/enterprise/JBPAPP_5_0)
15 years, 1 month
- 1
- 0