[seam-commits] Seam SVN: r11700 - branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR.
seam-commits at lists.jboss.org
seam-commits at lists.jboss.org
Sun Nov 29 18:37:38 EST 2009
Author: essaidetest
Date: 2009-11-29 18:37:38 -0500 (Sun, 29 Nov 2009)
New Revision: 11700
Modified:
branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Jbpm.po
Log:
Modified: branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Jbpm.po
===================================================================
--- branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Jbpm.po 2009-11-29 22:52:50 UTC (rev 11699)
+++ branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Jbpm.po 2009-11-29 23:37:38 UTC (rev 11700)
@@ -6,8 +6,8 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-03-31 09:07+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2009-11-30 00:37+0100\n"
+"Last-Translator: P.J <essaidetest at yahoo.fr>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -17,131 +17,91 @@
#: Jbpm.xml:2
#, no-c-format
msgid "Pageflows and business processes"
-msgstr ""
+msgstr "L'enchainement des pages et les processus métiers"
#. Tag: para
#: Jbpm.xml:4
#, no-c-format
-msgid ""
-"JBoss jBPM is a business process management engine for any Java SE or EE "
-"environment. jBPM lets you represent a business process or user interaction "
-"as a graph of nodes representing wait states, decisions, tasks, web pages, "
-"etc. The graph is defined using a simple, very readable, XML dialect called "
-"jPDL, and may be edited and visualised graphically using an eclipse plugin. "
-"jPDL is an extensible language, and is suitable for a range of problems, "
-"from defining web application page flow, to traditional workflow management, "
-"all the way up to orchestration of services in a SOA environment."
-msgstr ""
+msgid "JBoss jBPM is a business process management engine for any Java SE or EE environment. jBPM lets you represent a business process or user interaction as a graph of nodes representing wait states, decisions, tasks, web pages, etc. The graph is defined using a simple, very readable, XML dialect called jPDL, and may be edited and visualised graphically using an eclipse plugin. jPDL is an extensible language, and is suitable for a range of problems, from defining web application page flow, to traditional workflow management, all the way up to orchestration of services in a SOA environment."
+msgstr "JBoss jBPM est un moteur de gestion du processus métier pour tout environement Java SE ou EE. jBPM vous permet de vous représenter un processus métier ou une intéraction utilisateur comme un graphe de noeud représentant les états d'attente, les décisions, les tâches, les pages web, etc. Le graphe est défini en utilisant un simple et facile à lire dialecte XML appelé jPDL, et peut être édité et visualisé graphiquement en utilisant un plugin d'Eclipse. jPDL est un language extensible et il est adapté pour une grande variété de problème, depuis la définition de l'enchainement de page d'une application web jusqu'à la gestion des traditionnels enchainement de tâches, tout cela dans un esprit d'orchestration des services dans un environnement SOA. "
#. Tag: para
#: Jbpm.xml:16
#, no-c-format
msgid "Seam applications use jBPM for two different problems:"
-msgstr ""
+msgstr "Les applications Seam utilise jBPM pour deux types de problèmes différents: "
#. Tag: para
#: Jbpm.xml:22
#, no-c-format
-msgid ""
-"Defining the pageflow involved in complex user interactions. A jPDL process "
-"definition defines the page flow for a single conversation. A Seam "
-"conversation is considered to be a relatively short-running interaction with "
-"a single user."
-msgstr ""
+msgid "Defining the pageflow involved in complex user interactions. A jPDL process definition defines the page flow for a single conversation. A Seam conversation is considered to be a relatively short-running interaction with a single user."
+msgstr "Définition d'un enchainement de page inclus dans de complexes intéractions de l'utilisateur. Une définition de processus jPDL définie l'enchainement de page pour une seule conversation. Une conversation Seam est considérée pour être une intérraction à relativement courte exécution avec un seul utilisateur. "
#. Tag: para
#: Jbpm.xml:30
#, no-c-format
-msgid ""
-"Defining the overarching business process. The business process may span "
-"multiple conversations with multiple users. Its state is persistent in the "
-"jBPM database, so it is considered long-running. Coordination of the "
-"activities of multiple users is a much more complex problem than scripting "
-"an interaction with a single user, so jBPM offers sophisticated facilities "
-"for task management and dealing with multiple concurrent paths of execution."
-msgstr ""
+msgid "Defining the overarching business process. The business process may span multiple conversations with multiple users. Its state is persistent in the jBPM database, so it is considered long-running. Coordination of the activities of multiple users is a much more complex problem than scripting an interaction with a single user, so jBPM offers sophisticated facilities for task management and dealing with multiple concurrent paths of execution."
+msgstr "Définition d'un processus métier hypercintré. Le processus métier peu s'étendre sur de multiples conversations avec de multiples utilisateurs. Son état est persistant dans la base de données jBPM, donc il est considéré comme à longue exécution. La coordination des activités de multiples utilisateurs est un problème beaucoup plus complexe que l'écriture d'une intéraction avec un seul utilisateur, donc jBPM offre des fonctionnalités sophistiquées pour la gestion des tâches et la considération de multiples chemins d'éxécutions concurents. "
#. Tag: para
#: Jbpm.xml:42
#, no-c-format
-msgid ""
-"Don't get these two things confused! They operate at very different levels "
-"or granularity. <emphasis>Pageflow</emphasis>, <emphasis>conversation</"
-"emphasis> and <emphasis>task</emphasis> all refer to a single interaction "
-"with a single user. A business process spans many tasks. Futhermore, the two "
-"applications of jBPM are totally orthogonal. You can use them together or "
-"independently or not at all."
-msgstr ""
+msgid "Don't get these two things confused! They operate at very different levels or granularity. <emphasis>Pageflow</emphasis>, <emphasis>conversation</emphasis> and <emphasis>task</emphasis> all refer to a single interaction with a single user. A business process spans many tasks. Futhermore, the two applications of jBPM are totally orthogonal. You can use them together or independently or not at all."
+msgstr "Ne vous laisser pas embrouillés par ces deux choses ! Elle fonctionne à des niveaux ou de granularité très différents. <emphasis>L'enchainement de page /emphasis>, <emphasis>de conversation</emphasis> et des <emphasis>tâches</emphasis> toutes ce réfèrent à une seule intéraction avec un seul utilisateur. Un processus métier s'étends sur plusieurs tâches. En outre, les deux applications de jBPM sont totalement ortogonales. Vous pouvez les utiliser ensemble ou indépendamment ou pas du tout. "
#. Tag: para
#: Jbpm.xml:51
#, no-c-format
-msgid ""
-"You don't have to know jDPL to use Seam. If you're perfectly happy defining "
-"pageflow using JSF or Seam navigation rules, and if your application is more "
-"data-driven that process-driven, you probably don't need jBPM. But we're "
-"finding that thinking of user interaction in terms of a well-defined "
-"graphical representation is helping us build more robust applications."
-msgstr ""
+msgid "You don't have to know jDPL to use Seam. If you're perfectly happy defining pageflow using JSF or Seam navigation rules, and if your application is more data-driven that process-driven, you probably don't need jBPM. But we're finding that thinking of user interaction in terms of a well-defined graphical representation is helping us build more robust applications."
+msgstr "Vous n'avez pas besoin de connaitre jDPL pour utiliser Seam. Si vous êtes parfaitement heureux de définir l'enchainement de page en utilisant JSF ou les règles de navigation de Seam, et si votre application est plus à connatation données qu'à connotation processus, vous n'avez probablement pas besoin de jBPM. Mais nous allons trouver que penser l'interaction utilisateur en terme de représentation graphique bien définie nous aide à construire des applications plus robustes. "
#. Tag: title
#: Jbpm.xml:60
#, no-c-format
msgid "Pageflow in Seam"
-msgstr ""
+msgstr "L'enchainement de page dans Seam"
#. Tag: para
#: Jbpm.xml:61
#, no-c-format
msgid "There are two ways to define pageflow in Seam:"
-msgstr ""
+msgstr "Il y a deux façon de définir un enchainement de page dans Seam: "
#. Tag: para
#: Jbpm.xml:67
#, no-c-format
-msgid ""
-"Using JSF or Seam navigation rules - the <emphasis>stateless navigation "
-"model</emphasis>"
-msgstr ""
+msgid "Using JSF or Seam navigation rules - the <emphasis>stateless navigation model</emphasis>"
+msgstr "Utiliser les règles de navigation de JSF ou de Seam - le <emphasis>modèle de navigation sans état</emphasis>"
#. Tag: para
#: Jbpm.xml:73
#, no-c-format
msgid "Using jPDL - the <emphasis>stateful navigation model</emphasis>"
-msgstr ""
+msgstr "Utiliser le jPDL - le <emphasis>modèle de navigation avec état</emphasis>"
#. Tag: para
#: Jbpm.xml:79
#, no-c-format
-msgid ""
-"Very simple applications will only need the stateless navigation model. Very "
-"complex applications will use both models in different places. Each model "
-"has its strengths and weaknesses!"
-msgstr ""
+msgid "Very simple applications will only need the stateless navigation model. Very complex applications will use both models in different places. Each model has its strengths and weaknesses!"
+msgstr "De très simple applications n'ont seulement besoin que du modèle de navigation sans état. Des applications très complexes auront besoins des deux modèles à des endroits différents. Chaque modèle a ses forces et ses faiblesses! "
#. Tag: title
#: Jbpm.xml:86
#, no-c-format
msgid "The two navigation models"
-msgstr ""
+msgstr "Les deux modèles de navigation"
#. Tag: para
#: Jbpm.xml:88
#, no-c-format
-msgid ""
-"The stateless model defines a mapping from a set of named, logical outcomes "
-"of an event directly to the resulting page of the view. The navigation rules "
-"are entirely oblivious to any state held by the application other than what "
-"page was the source of the event. This means that your action listener "
-"methods must sometimes make decisions about the page flow, since only they "
-"have access to the current state of the application."
-msgstr ""
+msgid "The stateless model defines a mapping from a set of named, logical outcomes of an event directly to the resulting page of the view. The navigation rules are entirely oblivious to any state held by the application other than what page was the source of the event. This means that your action listener methods must sometimes make decisions about the page flow, since only they have access to the current state of the application."
+msgstr "Le modèle sans état défini une relation depuis un groupe de résultat nomé et la logique d'un évènement directement dans la page résultat de la vue. Les règles de navigation sont entièrement inconnues des autres états inclus dans l'application à part de la page qui a été la source de l'évènement. Cela signifie que les méthodes d'écoute de l'action doivent parfois prendre la décicsion à propos de l'enchainement de page, alors qu'elles n'ont accès qu'à l'état courrant de l'application. "
#. Tag: para
#: Jbpm.xml:98
#, no-c-format
msgid "Here is an example page flow definition using JSF navigation rules:"
-msgstr ""
+msgstr "Voici un exemple de définition d'un enchainement de page en utilisant les règles de navigation de JSF: "
#. Tag: programlisting
#: Jbpm.xml:103
@@ -170,13 +130,34 @@
"\n"
"</navigation-rule>]]>"
msgstr ""
+"<![CDATA[<navigation-rule>\n"
+" <from-view-id>/numberGuess.jsp</from-view-id>\n"
+" \n"
+" <navigation-case>\n"
+" <from-outcome>guess</from-outcome>\n"
+" <to-view-id>/numberGuess.jsp</to-view-id>\n"
+" <redirect/>\n"
+" </navigation-case>\n"
+"\n"
+" <navigation-case>\n"
+" <from-outcome>win</from-outcome>\n"
+" <to-view-id>/win.jsp</to-view-id>\n"
+" <redirect/>\n"
+" </navigation-case>\n"
+" \n"
+" <navigation-case>\n"
+" <from-outcome>lose</from-outcome>\n"
+" <to-view-id>/lose.jsp</to-view-id>\n"
+" <redirect/>\n"
+" </navigation-case>\n"
+"\n"
+"</navigation-rule>]]>"
#. Tag: para
#: Jbpm.xml:105
#, no-c-format
-msgid ""
-"Here is the same example page flow definition using Seam navigation rules:"
-msgstr ""
+msgid "Here is the same example page flow definition using Seam navigation rules:"
+msgstr "Voici un exemple de définition d'un enchainement de page en utilisant les règles de navigation de Seam: "
#. Tag: programlisting
#: Jbpm.xml:110
@@ -198,14 +179,27 @@
"\n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page view-id=\"/numberGuess.jsp\">\n"
+" \n"
+" <navigation>\n"
+" <rule if-outcome=\"guess\">\n"
+" <redirect view-id=\"/numberGuess.jsp\"/>\n"
+" </rule>\n"
+" <rule if-outcome=\"win\">\n"
+" <redirect view-id=\"/win.jsp\"/>\n"
+" </rule>\n"
+" <rule if-outcome=\"lose\">\n"
+" <redirect view-id=\"/lose.jsp\"/>\n"
+" </rule>\n"
+" </navigation>\n"
+"\n"
+"</page>]]>"
#. Tag: para
#: Jbpm.xml:112
#, no-c-format
-msgid ""
-"If you find navigation rules overly verbose, you can return view ids "
-"directly from your action listener methods:"
-msgstr ""
+msgid "If you find navigation rules overly verbose, you can return view ids directly from your action listener methods:"
+msgstr "Si vous trouvez que les règles de navigation beaucoup trop verbeuses, vous pouvez retourner l'identifiant de la vue directement depuis la méthode d'écouteur d'action: "
#. Tag: programlisting
#: Jbpm.xml:117
@@ -217,41 +211,41 @@
" return null;\n"
"}]]>"
msgstr ""
+"<![CDATA[public String guess() {\n"
+" if (guess==randomNumber) return \"/win.jsp\";\n"
+" if (++guessCount==maxGuesses) return \"/lose.jsp\";\n"
+" return null;\n"
+"}]]>"
#. Tag: para
#: Jbpm.xml:119
#, no-c-format
-msgid ""
-"Note that this results in a redirect. You can even specify parameters to be "
-"used in the redirect:"
-msgstr ""
+msgid "Note that this results in a redirect. You can even specify parameters to be used in the redirect:"
+msgstr "Notez que cela résulte dans une redirection. Vous pouvez même spécifier les paramètres à utiliser pour la redirection: "
#. Tag: programlisting
#: Jbpm.xml:124
#, no-c-format
msgid ""
"<![CDATA[public String search() {\n"
-" return \"/searchResults.jsp?searchPattern=#{searchAction.searchPattern}"
-"\";\n"
+" return \"/searchResults.jsp?searchPattern=#{searchAction.searchPattern}\";\n"
"}]]>"
msgstr ""
+"<![CDATA[public String search() {\n"
+" return \"/searchResults.jsp?searchPattern=#{searchAction.searchPattern}\";\n"
+"}]]>"
#. Tag: para
#: Jbpm.xml:126
#, no-c-format
-msgid ""
-"The stateful model defines a set of transitions between a set of named, "
-"logical application states. In this model, it is possible to express the "
-"flow of any user interaction entirely in the jPDL pageflow definition, and "
-"write action listener methods that are completely unaware of the flow of the "
-"interaction."
-msgstr ""
+msgid "The stateful model defines a set of transitions between a set of named, logical application states. In this model, it is possible to express the flow of any user interaction entirely in the jPDL pageflow definition, and write action listener methods that are completely unaware of the flow of the interaction."
+msgstr "Le modèle avec état défini un groupe de transition entre un groupe d'état de l'application logique et nomé. Dans ce modèle, il est possible d'exprimer l'enchainement des interactions utilisateur entièrement dans une définition d'enchainement de page en jPDL et écrire les méthode d'écouteur d'action qui sont complètement ignare du flot d'interaction. "
#. Tag: para
#: Jbpm.xml:134
#, no-c-format
msgid "Here is an example page flow definition using jPDL:"
-msgstr ""
+msgstr "Voici un exemple de définition du flot de page en utilisant jPDL: "
#. Tag: programlisting
#: Jbpm.xml:138
@@ -266,14 +260,12 @@
" </transition>\n"
" </start-page>\n"
" \n"
-" <decision name=\"evaluateGuess\" expression=\"#{numberGuess.correctGuess}"
-"\">\n"
+" <decision name=\"evaluateGuess\" expression=\"#{numberGuess.correctGuess}\">\n"
" <transition name=\"true\" to=\"win\"/>\n"
" <transition name=\"false\" to=\"evaluateRemainingGuesses\"/>\n"
" </decision>\n"
" \n"
-" <decision name=\"evaluateRemainingGuesses\" expression=\"#{numberGuess."
-"lastGuess}\">\n"
+" <decision name=\"evaluateRemainingGuesses\" expression=\"#{numberGuess.lastGuess}\">\n"
" <transition name=\"true\" to=\"lose\"/>\n"
" <transition name=\"false\" to=\"displayGuess\"/>\n"
" </decision>\n"
@@ -290,98 +282,90 @@
" \n"
"</pageflow-definition>]]>"
msgstr ""
+"<![CDATA[<pageflow-definition name=\"numberGuess\">\n"
+" \n"
+" <start-page name=\"displayGuess\" view-id=\"/numberGuess.jsp\">\n"
+" <redirect/>\n"
+" <transition name=\"guess\" to=\"evaluateGuess\">\n"
+" <action expression=\"#{numberGuess.guess}\" />\n"
+" </transition>\n"
+" </start-page>\n"
+" \n"
+" <decision name=\"evaluateGuess\" expression=\"#{numberGuess.correctGuess}\">\n"
+" <transition name=\"true\" to=\"win\"/>\n"
+" <transition name=\"false\" to=\"evaluateRemainingGuesses\"/>\n"
+" </decision>\n"
+" \n"
+" <decision name=\"evaluateRemainingGuesses\" expression=\"#{numberGuess.lastGuess}\">\n"
+" <transition name=\"true\" to=\"lose\"/>\n"
+" <transition name=\"false\" to=\"displayGuess\"/>\n"
+" </decision>\n"
+" \n"
+" <page name=\"win\" view-id=\"/win.jsp\">\n"
+" <redirect/>\n"
+" <end-conversation />\n"
+" </page>\n"
+" \n"
+" <page name=\"lose\" view-id=\"/lose.jsp\">\n"
+" <redirect/>\n"
+" <end-conversation />\n"
+" </page>\n"
+" \n"
+"</pageflow-definition>]]>"
#. Tag: para
#: Jbpm.xml:149
#, no-c-format
msgid "There are two things we notice immediately here:"
-msgstr ""
+msgstr "Il y a deux choses que nous pouvons noter immédiatement ici: "
#. Tag: para
#: Jbpm.xml:155
#, no-c-format
-msgid ""
-"The JSF/Seam navigation rules are <emphasis>much</emphasis> simpler. "
-"(However, this obscures the fact that the underlying Java code is more "
-"complex.)"
-msgstr ""
+msgid "The JSF/Seam navigation rules are <emphasis>much</emphasis> simpler. (However, this obscures the fact that the underlying Java code is more complex.)"
+msgstr "Les règles de navigation JSF/Seam sont beaucoup <emphasis>plus</emphasis> simples. (Néanmoins, cela masque le fait que le code Java sous-entendu est plus complexe.) "
#. Tag: para
#: Jbpm.xml:162
#, no-c-format
-msgid ""
-"The jPDL makes the user interaction immediately understandable, without us "
-"needing to even look at the JSP or Java code."
-msgstr ""
+msgid "The jPDL makes the user interaction immediately understandable, without us needing to even look at the JSP or Java code."
+msgstr "Le jPDL rend les interactions utilisateurs immédiatement compréhensible, sans qu'il soit même nécéssaire de lire le code JSP ou Java. "
#. Tag: para
#: Jbpm.xml:169
#, no-c-format
-msgid ""
-"In addition, the stateful model is more <emphasis>constrained</emphasis>. "
-"For each logical state (each step in the page flow), there are a constrained "
-"set of possible transitions to other states. The stateless model is an "
-"<emphasis>ad hoc</emphasis> model which is suitable to relatively "
-"unconstrained, freeform navigation where the user decides where he/she wants "
-"to go next, not the application."
-msgstr ""
+msgid "In addition, the stateful model is more <emphasis>constrained</emphasis>. For each logical state (each step in the page flow), there are a constrained set of possible transitions to other states. The stateless model is an <emphasis>ad hoc</emphasis> model which is suitable to relatively unconstrained, freeform navigation where the user decides where he/she wants to go next, not the application."
+msgstr "En plus, le modèle à état est plus <emphasis>constraint</emphasis>. Pour chaque état logique (chaque étape dans l'enchainement de page), il y a un contrainte sur un groupe de transition possible vers les autres états. Le modèle sans état est un modèle <emphasis>ad hoc</emphasis> qui est efficace pour la navigation relativement sans contrainte, libre de formulaire quand l'utilisateur décide là ou il/elle veux aller ensuite, pas l'application. "
#. Tag: para
#: Jbpm.xml:178
#, no-c-format
-msgid ""
-"The stateful/stateless navigation distinction is quite similar to the "
-"traditional view of modal/modeless interaction. Now, Seam applications are "
-"not usually modal in the simple sense of the word - indeed, avoiding "
-"application modal behavior is one of the main reasons for having "
-"conversations! However, Seam applications can be, and often are, modal at "
-"the level of a particular conversation. It is well-known that modal behavior "
-"is something to avoid as much as possible; it is very difficult to predict "
-"the order in which your users are going to want to do things! However, there "
-"is no doubt that the stateful model has its place."
-msgstr ""
+msgid "The stateful/stateless navigation distinction is quite similar to the traditional view of modal/modeless interaction. Now, Seam applications are not usually modal in the simple sense of the word - indeed, avoiding application modal behavior is one of the main reasons for having conversations! However, Seam applications can be, and often are, modal at the level of a particular conversation. It is well-known that modal behavior is something to avoid as much as possible; it is very difficult to predict the order in which your users are going to want to do things! However, there is no doubt that the stateful model has its place."
+msgstr "La distinction entre navigation avec/sans état est assez similaire à la traditionnel vue de l'intération avec/sans modèle. Maintenant, les applications de Seam ne sont pas en général modale au sens strict de ce mot - en fait, éviter la fonctionnalité modal de l'application est une des raisons principale pour avoir les conversations! Malgré tout, les applications Seam peuvent être, et souvent le sont, modale au niveau de conversation particulière. Il est bien connu que la fonctionnalité modale est quelquechose à éviter autant que possible; il est très difficile de prédire dans quel ordre vos utilisateurs vont vouloir faire les choses! Ainsi, il n'y a pas de doutes que le modèle avec état a sa place. "
#. Tag: para
#: Jbpm.xml:191
#, no-c-format
-msgid ""
-"The biggest contrast between the two models is the back-button behavior."
-msgstr ""
+msgid "The biggest contrast between the two models is the back-button behavior."
+msgstr "Le plus grand contraste entre les deux modèles est la fonction du bouton-précédent. "
#. Tag: title
#: Jbpm.xml:199
#, no-c-format
msgid "Seam and the back button"
-msgstr ""
+msgstr "Seam et le bouton précédent"
#. Tag: para
#: Jbpm.xml:201
#, no-c-format
-msgid ""
-"When JSF or Seam navigation rules are used, Seam lets the user freely "
-"navigate via the back, forward and refresh buttons. It is the responsibility "
-"of the application to ensure that conversational state remains internally "
-"consistent when this occurs. Experience with the combination of web "
-"application frameworks like Struts or WebWork - that do not support a "
-"conversational model - and stateless component models like EJB stateless "
-"session beans or the Spring framework has taught many developers that this "
-"is close to impossible to do! However, our experience is that in the context "
-"of Seam, where there is a well-defined conversational model, backed by "
-"stateful session beans, it is actually quite straightforward. Usually it is "
-"as simple as combining the use of <literal>no-conversation-view-id</literal> "
-"with null checks at the beginning of action listener methods. We consider "
-"support for freeform navigation to be almost always desirable."
-msgstr ""
+msgid "When JSF or Seam navigation rules are used, Seam lets the user freely navigate via the back, forward and refresh buttons. It is the responsibility of the application to ensure that conversational state remains internally consistent when this occurs. Experience with the combination of web application frameworks like Struts or WebWork - that do not support a conversational model - and stateless component models like EJB stateless session beans or the Spring framework has taught many developers that this is close to impossible to do! However, our experience is that in the context of Seam, where there is a well-defined conversational model, backed by stateful session beans, it is actually quite straightforward. Usually it is as simple as combining the use of <literal>no-conversation-view-id</literal> with null checks at the beginning of action listener methods. We consider support for freeform navigation to be almost always desirable."
+msgstr "Quand les règles de navigation JSF et Seam sont utilisées, Seam laisse l'utilisateur naviger librement avec les boutons précédent, suivant et rafraichir. Il est de la responsabilité de l'application de s'assurer que l'état conversationnel reste en interne consistant quand cela arrive. L'experience avec la combinaisond'application web comme Struts ou WebWork - qui ne supporte pas le modèle conversationnel - et les modèles de composants sans état comme les beans de session sans état EJB ou le serveur d'application Spring a appris à beaucoup de développers qu'il est presque impossible de le faire! Ainsi, notre expérience est que c'est dans le contexte de Seam qu'il y a un modèle conversaionnel bien définie, soutenu par les beans de de sessions avec état, il est actuellement presque prêt. Habituellement, il est presque aussi simple de combiner l'utilisation <literal>no-conversation-view-id</literal> avec la vérification de null au démarrage des métho!
des d'écouteur d'action. Nous considerons le support de la navigation libre de formulaire presque aussi souhaitable. "
#. Tag: para
#: Jbpm.xml:219
#, no-c-format
-msgid ""
-"In this case, the <literal>no-conversation-view-id</literal> declaration "
-"goes in <literal>pages.xml</literal>. It tells Seam to redirect to a "
-"different page if a request originates from a page rendered during a "
-"conversation, and that conversation no longer exists:"
-msgstr ""
+msgid "In this case, the <literal>no-conversation-view-id</literal> declaration goes in <literal>pages.xml</literal>. It tells Seam to redirect to a different page if a request originates from a page rendered during a conversation, and that conversation no longer exists:"
+msgstr "Dans ce cas, la déclaration de <literal>no-conversation-view-id</literal> va dans <literal>pages.xml</literal>. Il indique a Seam de rediriger vers une page différente si une requête originaire d'une page rendue pendant une conversation et que cette conversation n'existe plus: "
#. Tag: programlisting
#: Jbpm.xml:227
@@ -390,23 +374,14 @@
"<![CDATA[<page view-id=\"/checkout.xhtml\" \n"
" no-conversation-view-id=\"/main.xhtml\"/>]]>"
msgstr ""
+"<![CDATA[<page view-id=\"/checkout.xhtml\" \n"
+" no-conversation-view-id=\"/main.xhtml\"/>]]>"
#. Tag: para
#: Jbpm.xml:229
#, no-c-format
-msgid ""
-"On the other hand, in the stateful model, using the back button is "
-"interpreted as an undefined transition back to a previous state. Since the "
-"stateful model enforces a defined set of transitions from the current state, "
-"the back button is not permitted by default in the stateful model! Seam "
-"transparently detects the use of the back button, and blocks any attempt to "
-"perform an action from a previous, \"stale\" page, and simply redirects the "
-"user to the \"current\" page (and displays a faces message). Whether you "
-"consider this a feature or a limitation of the stateful model depends upon "
-"your point of view: as an application developer, it is a feature; as a user, "
-"it might be frustrating! You can enable backbutton navigation from a "
-"particular page node by setting <literal>back=\"enabled\"</literal>."
-msgstr ""
+msgid "On the other hand, in the stateful model, using the back button is interpreted as an undefined transition back to a previous state. Since the stateful model enforces a defined set of transitions from the current state, the back button is not permitted by default in the stateful model! Seam transparently detects the use of the back button, and blocks any attempt to perform an action from a previous, \"stale\" page, and simply redirects the user to the \"current\" page (and displays a faces message). Whether you consider this a feature or a limitation of the stateful model depends upon your point of view: as an application developer, it is a feature; as a user, it might be frustrating! You can enable backbutton navigation from a particular page node by setting <literal>back=\"enabled\"</literal>."
+msgstr "D'un autre côté, dans le modèle avec état, le bouton \"précédent\" est interprété comme un retour de transition non-définie vers l'état précédent. Depuis que le modèle avec état se renforce comme un groupe définie de transition depuis l'état courrant, le bouton \"précédent\" est par défaut interdit dans le modèle avec état! Seam de manière transparent détecte l'utilisation du bouton précédent et bloque toute tentative de réaliser une action depuis une page précédente \"périmée\" et redirige simplement l'utilisateur vers la page \"courante\" (et affiche un message faces). Que vous considériez comme une fonctionnalité ou une limitation le modèle sans état cela dépend de votre point de vue: comme un développeur d'application, c'est une fonctionnalité, comme un utilisateur, cela peut être frustrant. Vous pouvez activer la navigation avec le bouton \"précédent\" depuis un noeud de page particulier en indiquant <literal>back=\"enab!
led\"</literal>."
#. Tag: programlisting
#: Jbpm.xml:245
@@ -420,36 +395,31 @@
" <transition name=\"complete\" to=\"complete\"/>\n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page name=\"checkout\" \n"
+" view-id=\"/checkout.xhtml\" \n"
+" back=\"enabled\">\n"
+" <redirect/>\n"
+" <transition to=\"checkout\"/>\n"
+" <transition name=\"complete\" to=\"complete\"/>\n"
+"</page>]]>"
#. Tag: para
#: Jbpm.xml:247
#, no-c-format
-msgid ""
-"This allows navigation via the back button <emphasis>from</emphasis> the "
-"<literal>checkout</literal> state to <emphasis>any previous state!</emphasis>"
-msgstr ""
+msgid "This allows navigation via the back button <emphasis>from</emphasis> the <literal>checkout</literal> state to <emphasis>any previous state!</emphasis>"
+msgstr "Cela autorise le bouton \"précédent\" <emphasis>depuis</emphasis> l'état checkout vers <emphasis>tout état précédent!</emphasis>"
#. Tag: note
#: Jbpm.xml:253
#, no-c-format
-msgid ""
-"If a page is set to redirect after a transition, it is not possible to use "
-"the back button to return to that page even when back is enabled on a page "
-"later in the flow. The reason is because Seam stores information about the "
-"pageflow in the page scope and the back button must result in a POST for "
-"that information to be restored (i.e., a Faces request). A redirect severs "
-"this linkage."
-msgstr ""
+msgid "If a page is set to redirect after a transition, it is not possible to use the back button to return to that page even when back is enabled on a page later in the flow. The reason is because Seam stores information about the pageflow in the page scope and the back button must result in a POST for that information to be restored (i.e., a Faces request). A redirect severs this linkage."
+msgstr "Si une page est définie pour rediriger après une transition, il n'est pas possible d'utiliser le bouton précédent pour retourner à la page même quand le bouton précédent est sur une page plus tard dans l'enchainement. La raison est que parce que Seam stocke les informations à propos de l'enchainement de page dans l'étendue page donc le bouton précédent doit résulter dans une requête POST pour que l'information soit restorée (autrement dit, une requête Faces). Une redirection fournie ce type de liaison."
#. Tag: para
#: Jbpm.xml:262
#, no-c-format
-msgid ""
-"Of course, we still need to define what happens if a request originates from "
-"a page rendered during a pageflow, and the conversation with the pageflow no "
-"longer exists. In this case, the <literal>no-conversation-view-id</literal> "
-"declaration goes into the pageflow definition:"
-msgstr ""
+msgid "Of course, we still need to define what happens if a request originates from a page rendered during a pageflow, and the conversation with the pageflow no longer exists. In this case, the <literal>no-conversation-view-id</literal> declaration goes into the pageflow definition:"
+msgstr "Bien sûr, nous avons toujours besoin de définir ce qu'il arrive si une requête originiaire d'une page rendue pendant l'enchainement de page, et la conversation ave l'enchainement de page n'existe plus. Dans ce cas, la déclaration <literal>no-conversation-view-id</literal> va dans la définition d'enchainement de page: "
#. Tag: programlisting
#: Jbpm.xml:270
@@ -464,50 +434,50 @@
" <transition name=\"complete\" to=\"complete\"/>\n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page name=\"checkout\" \n"
+" view-id=\"/checkout.xhtml\" \n"
+" back=\"enabled\" \n"
+" no-conversation-view-id=\"/main.xhtml\">\n"
+" <redirect/>\n"
+" <transition to=\"checkout\"/>\n"
+" <transition name=\"complete\" to=\"complete\"/>\n"
+"</page>]]>"
#. Tag: para
#: Jbpm.xml:273
#, no-c-format
-msgid ""
-"In practice, both navigation models have their place, and you'll quickly "
-"learn to recognize when to prefer one model over the other."
-msgstr ""
+msgid "In practice, both navigation models have their place, and you'll quickly learn to recognize when to prefer one model over the other."
+msgstr "En pratique, les deux modèles de navigation ont leur spécificité et vous allez rapidement apprendre à les reconnaitre quand vous préférerez un modèle plutôt que l'autre."
#. Tag: title
#: Jbpm.xml:282
#, no-c-format
msgid "Using jPDL pageflows"
-msgstr ""
+msgstr "Utilisation des enchainements de page jPDL"
#. Tag: title
#: Jbpm.xml:285
#, no-c-format
msgid "Installing pageflows"
-msgstr ""
+msgstr "Installation des enchainements de page"
#. Tag: para
#: Jbpm.xml:287
#, no-c-format
-msgid ""
-"We need to install the Seam jBPM-related components, and place the pageflow "
-"definitions (using the standard <literal>.jpdl.xml</literal> extension) "
-"inside a Seam archive (an archive which contains a <literal>seam.properties</"
-"literal> file):"
-msgstr ""
+msgid "We need to install the Seam jBPM-related components, and place the pageflow definitions (using the standard <literal>.jpdl.xml</literal> extension) inside a Seam archive (an archive which contains a <literal>seam.properties</literal> file):"
+msgstr "Nous avons besoin d'installer les composants jBPM-style de Seam et leurs dirent où ils vont trouver la définition de l'enchainement de page. Nous pouvons spécifier cette configuration de Seam dans components.xml. "
#. Tag: programlisting
#: Jbpm.xml:294
#, no-c-format
msgid "<![CDATA[<bpm:jbpm />]]>"
-msgstr ""
+msgstr "<![CDATA[<bpm:jbpm />]]>"
#. Tag: para
#: Jbpm.xml:296
#, no-c-format
-msgid ""
-"We can also explicitly tell Seam where to find our pageflow definition. We "
-"specify this in <literal>components.xml</literal>:"
-msgstr ""
+msgid "We can also explicitly tell Seam where to find our pageflow definition. We specify this in <literal>components.xml</literal>:"
+msgstr "Vous pouvez aussi explicitement indiquer à Seam où trouver la définition d'enchainement de page. Nous spécifions ceci dans <literal>components.xml</literal>:"
#. Tag: programlisting
#: Jbpm.xml:301
@@ -519,21 +489,23 @@
" </bpm:pageflow-definitions>\n"
"</bpm:jbpm>]]>"
msgstr ""
+"<![CDATA[<bpm:jbpm>\n"
+" <bpm:pageflow-definitions>\n"
+" <value>pageflow.jpdl.xml</value>\n"
+" </bpm:pageflow-definitions>\n"
+"</bpm:jbpm>]]>"
#. Tag: title
#: Jbpm.xml:306
#, no-c-format
msgid "Starting pageflows"
-msgstr ""
+msgstr "Démarrage des enchainements de pages"
#. Tag: para
#: Jbpm.xml:308
#, no-c-format
-msgid ""
-"We \"start\" a jPDL-based pageflow by specifying the name of the process "
-"definition using a <literal>@Begin</literal>, <literal>@BeginTask</literal> "
-"or <literal>@StartTask</literal> annotation:"
-msgstr ""
+msgid "We \"start\" a jPDL-based pageflow by specifying the name of the process definition using a <literal>@Begin</literal>, <literal>@BeginTask</literal> or <literal>@StartTask</literal> annotation:"
+msgstr "Nous \"démarrons\" un enchainement de pages jPDL-style en indiquant le nom de la définition du processus en utilisation une annotation <literal>@Begin</literal>, <literal>@BeginTask</literal> ou <literal>@StartTask</literal>:"
#. Tag: programlisting
#: Jbpm.xml:315
@@ -542,12 +514,14 @@
"<![CDATA[@Begin(pageflow=\"numberguess\")\n"
"public void begin() { ... }]]>"
msgstr ""
+"<![CDATA[@Begin(pageflow=\"numberguess\")\n"
+"public void begin() { ... }]]>"
#. Tag: para
#: Jbpm.xml:317
#, no-c-format
msgid "Alternatively we can start a pageflow using pages.xml:"
-msgstr ""
+msgstr "De manière alternative, nous pouvons démarrer un enchainement de page en utilisant pages.xml:"
#. Tag: programlisting
#: Jbpm.xml:319
@@ -557,29 +531,21 @@
" <begin-conversation pageflow=\"numberguess\"/>\n"
" </page>]]>"
msgstr ""
+"<![CDATA[<page>\n"
+" <begin-conversation pageflow=\"numberguess\"/>\n"
+" </page>]]>"
#. Tag: para
#: Jbpm.xml:321
#, no-c-format
-msgid ""
-"If we are beginning the pageflow during the <literal>RENDER_RESPONSE</"
-"literal> phase — during a <literal>@Factory</literal> or "
-"<literal>@Create</literal> method, for example — we consider ourselves "
-"to be already at the page being rendered, and use a <literal><start-"
-"page></literal> node as the first node in the pageflow, as in the example "
-"above."
-msgstr ""
+msgid "If we are beginning the pageflow during the <literal>RENDER_RESPONSE</literal> phase — during a <literal>@Factory</literal> or <literal>@Create</literal> method, for example — we consider ourselves to be already at the page being rendered, and use a <literal><start-page></literal> node as the first node in the pageflow, as in the example above."
+msgstr "Si nous commençons un enchainement de page pendant la phase R<literal>RENDER_RESPONSE</literal> — pendant qu'une méthode literal>@Factory</literal> ou <literal>@Create</literal>, par exemple — nous considerons nous même être à la page qui doit être rendue, et utilisons un noeud <literal><start-page></literal> comme premier noeud dans l'enchainement de page, comme le montre l'exemple ci dessous. "
#. Tag: para
#: Jbpm.xml:329
#, no-c-format
-msgid ""
-"But if the pageflow is begun as the result of an action listener invocation, "
-"the outcome of the action listener determines which is the first page to be "
-"rendered. In this case, we use a <literal><start-state></literal> as "
-"the first node in the pageflow, and declare a transition for each possible "
-"outcome:"
-msgstr ""
+msgid "But if the pageflow is begun as the result of an action listener invocation, the outcome of the action listener determines which is the first page to be rendered. In this case, we use a <literal><start-state></literal> as the first node in the pageflow, and declare a transition for each possible outcome:"
+msgstr "Mais si l'enchainement de page a commencé comme le resulteat de l'invocation d'un écouteur d'action, le retour de lécouteur d'action détermine quel est la première page à être rendue. Dans ca cas, nous utilisons un <literal><start-state></literal> comme premier noeud de l'enchainement de page et déclarons une transition pour chaque sortie possible: "
#. Tag: programlisting
#: Jbpm.xml:337
@@ -605,20 +571,37 @@
" \n"
"</pageflow-definition>]]>"
msgstr ""
+"<![CDATA[<pageflow-definition name=\"viewEditDocument\">\n"
+"\n"
+" <start-state name=\"start\">\n"
+" <transition name=\"documentFound\" to=\"displayDocument\"/>\n"
+" <transition name=\"documentNotFound\" to=\"notFound\"/>\n"
+" </start-state>\n"
+" \n"
+" <page name=\"displayDocument\" view-id=\"/document.jsp\">\n"
+" <transition name=\"edit\" to=\"editDocument\"/>\n"
+" <transition name=\"done\" to=\"main\"/>\n"
+" </page>\n"
+" \n"
+" ...\n"
+" \n"
+" <page name=\"notFound\" view-id=\"/404.jsp\">\n"
+" <end-conversation/>\n"
+" </page>\n"
+" \n"
+"</pageflow-definition>]]>"
#. Tag: title
#: Jbpm.xml:342
#, no-c-format
msgid "Page nodes and transitions"
-msgstr ""
+msgstr "Les noeuds de page et transitions"
#. Tag: para
#: Jbpm.xml:344
#, no-c-format
-msgid ""
-"Each <literal><page></literal> node represents a state where the "
-"system is waiting for user input:"
-msgstr ""
+msgid "Each <literal><page></literal> node represents a state where the system is waiting for user input:"
+msgstr "Chaque noeud <literal><page></literal> représente un état où le système est en train d'attendre une saisie de l'utilisateur: "
#. Tag: programlisting
#: Jbpm.xml:349
@@ -631,71 +614,54 @@
" </transition>\n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page name=\"displayGuess\" view-id=\"/numberGuess.jsp\">\n"
+" <redirect/>\n"
+" <transition name=\"guess\" to=\"evaluateGuess\">\n"
+" <action expression=\"#{numberGuess.guess}\" />\n"
+" </transition>\n"
+"</page>]]>"
#. Tag: para
#: Jbpm.xml:351
#, no-c-format
-msgid ""
-"The <literal>view-id</literal> is the JSF view id. The <literal><redirect/"
-"></literal> element has the same effect as <literal><redirect/></"
-"literal> in a JSF navigation rule: namely, a post-then-redirect behavior, to "
-"overcome problems with the browser's refresh button. (Note that Seam "
-"propagates conversation contexts over these browser redirects. So there is "
-"no need for a Ruby on Rails style \"flash\" construct in Seam!)"
-msgstr ""
+msgid "The <literal>view-id</literal> is the JSF view id. The <literal><redirect/></literal> element has the same effect as <literal><redirect/></literal> in a JSF navigation rule: namely, a post-then-redirect behavior, to overcome problems with the browser's refresh button. (Note that Seam propagates conversation contexts over these browser redirects. So there is no need for a Ruby on Rails style \"flash\" construct in Seam!)"
+msgstr "Le <literal>view-id</literal> est l'identifiant de la vue JSF. L'élément <literal><redirect/></literal> a le même effet que <literal><redirect/></literal> dans une règle de navigation : à savoir, une fonctionnalité poster-puis-rediriger, pour contourner les problème avec le bouton rafraichir du navigateur. (Notez que Seam propage les contextes de conversation au travers de ces redirection de navigateur. Il n'y a donc pas besoin d'un fabrique de style Ruby on Rails \"flash\" dans Seam!) "
#. Tag: para
#: Jbpm.xml:360
#, no-c-format
-msgid ""
-"The transition name is the name of a JSF outcome triggered by clicking a "
-"command button or command link in <literal>numberGuess.jsp</literal>."
-msgstr ""
+msgid "The transition name is the name of a JSF outcome triggered by clicking a command button or command link in <literal>numberGuess.jsp</literal>."
+msgstr "Le nom de transition est le nom de la sortie JSF déclenché en cliquant sur le bouton de commande ou le lien de commande dans <literal>numberGuess.jsp</literal>."
#. Tag: programlisting
#: Jbpm.xml:365
#, no-c-format
-msgid ""
-"<![CDATA[<h:commandButton type=\"submit\" value=\"Guess\" action=\"guess\"/"
-">]]>"
-msgstr ""
+msgid "<![CDATA[<h:commandButton type=\"submit\" value=\"Guess\" action=\"guess\"/>]]>"
+msgstr "<![CDATA[<h:commandButton type=\"submit\" value=\"Guess\" action=\"guess\"/>]]>"
#. Tag: para
#: Jbpm.xml:367
#, no-c-format
-msgid ""
-"When the transition is triggered by clicking this button, jBPM will activate "
-"the transition action by calling the <literal>guess()</literal> method of "
-"the <literal>numberGuess</literal> component. Notice that the syntax used "
-"for specifying actions in the jPDL is just a familiar JSF EL expression, and "
-"that the transition action handler is just a method of a Seam component in "
-"the current Seam contexts. So we have exactly the same event model for jBPM "
-"events that we already have for JSF events! (The <emphasis>One Kind of "
-"Stuff</emphasis> principle.)"
-msgstr ""
+msgid "When the transition is triggered by clicking this button, jBPM will activate the transition action by calling the <literal>guess()</literal> method of the <literal>numberGuess</literal> component. Notice that the syntax used for specifying actions in the jPDL is just a familiar JSF EL expression, and that the transition action handler is just a method of a Seam component in the current Seam contexts. So we have exactly the same event model for jBPM events that we already have for JSF events! (The <emphasis>One Kind of Stuff</emphasis> principle.)"
+msgstr "Quand la transition est déclenchée par le clic sur le bouton, jBPM ira activer l'action de transition en appelant la méthode <emphasis>guess()</emphasis> du composant <emphasis>numberGuess</emphasis>. Notez que la syntaxe utilisée pour spécifier les actions dans le jPDL est juste une expression familière JSF EL, et que l'action de transation est juste une méthode d'une composant Seam dans le contexte courrant de Seam. Donc, nous avons exactement le même modèle d'évènement pour jBPM que nous avons déjà pour les évènements JSF! (Le principe <emphasis>d'Un Seul Genre de Truc.</emphasis>) "
#. Tag: para
#: Jbpm.xml:378
#, no-c-format
-msgid ""
-"In the case of a null outcome (for example, a command button with no "
-"<literal>action</literal> defined), Seam will signal the transition with no "
-"name if one exists, or else simply redisplay the page if all transitions "
-"have names. So we could slightly simplify our example pageflow and this "
-"button:"
-msgstr ""
+msgid "In the case of a null outcome (for example, a command button with no <literal>action</literal> defined), Seam will signal the transition with no name if one exists, or else simply redisplay the page if all transitions have names. So we could slightly simplify our example pageflow and this button:"
+msgstr "Dans le cas d'un résultat null (par exemple, un bouton de command sans aucune action définie), Seam ira signaler la transition sans aucun nom si une existe, ou sinon simplement réaffiche la page si toutes les transition ont un nom. Donc nous pourrions légèrement simplifier notre exemple d'enchainement de page et ce bouton: "
#. Tag: programlisting
#: Jbpm.xml:385
#, no-c-format
msgid "<![CDATA[<h:commandButton type=\"submit\" value=\"Guess\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<h:commandButton type=\"submit\" value=\"Guess\"/>]]>"
#. Tag: para
#: Jbpm.xml:387
#, no-c-format
msgid "Would fire the following un-named transition:"
-msgstr ""
+msgstr "Qui va déclencher la transition sans-nom suivante: "
#. Tag: programlisting
#: Jbpm.xml:391
@@ -708,22 +674,24 @@
" </transition>\n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page name=\"displayGuess\" view-id=\"/numberGuess.jsp\">\n"
+" <redirect/>\n"
+" <transition to=\"evaluateGuess\">\n"
+" <action expression=\"#{numberGuess.guess}\" />\n"
+" </transition>\n"
+"</page>]]>"
#. Tag: para
#: Jbpm.xml:393
#, no-c-format
-msgid ""
-"It is even possible to have the button call an action method, in which case "
-"the action outcome will determine the transition to be taken:"
-msgstr ""
+msgid "It is even possible to have the button call an action method, in which case the action outcome will determine the transition to be taken:"
+msgstr "Il est même possible d'avoir un bouton qui appele une méthode d'action, dans ce cas le résultat de l'action va déterminer la tranistion qui doit être prise: "
#. Tag: programlisting
#: Jbpm.xml:398
#, no-c-format
-msgid ""
-"<![CDATA[<h:commandButton type=\"submit\" value=\"Guess\" action=\"#"
-"{numberGuess.guess}\"/>]]>"
-msgstr ""
+msgid "<![CDATA[<h:commandButton type=\"submit\" value=\"Guess\" action=\"#{numberGuess.guess}\"/>]]>"
+msgstr "<![CDATA[<h:commandButton type=\"submit\" value=\"Guess\" action=\"#{numberGuess.guess}\"/>]]>"
#. Tag: programlisting
#: Jbpm.xml:400
@@ -734,63 +702,60 @@
" <transition name=\"incorrectGuess\" to=\"evaluateGuess\"/>\n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page name=\"displayGuess\" view-id=\"/numberGuess.jsp\">\n"
+" <transition name=\"correctGuess\" to=\"win\"/>\n"
+" <transition name=\"incorrectGuess\" to=\"evaluateGuess\"/>\n"
+"</page>]]>"
#. Tag: para
#: Jbpm.xml:402
#, no-c-format
-msgid ""
-"However, this is considered an inferior style, since it moves responsibility "
-"for controlling the flow out of the pageflow definition and back into the "
-"other components. It is much better to centralize this concern in the "
-"pageflow itself."
-msgstr ""
+msgid "However, this is considered an inferior style, since it moves responsibility for controlling the flow out of the pageflow definition and back into the other components. It is much better to centralize this concern in the pageflow itself."
+msgstr "Malgré cela, il est est à considérer comme un style inférieur, car il déplace la responsabilité du contrôl du flot à l'extérieur de la définition de l'enchainement de page et le place dans un autre composants. Il est franchement meilleur de centraliser ce qui s'y rapporte dans l'enchainement de pages lui même. "
#. Tag: title
#: Jbpm.xml:411
#, no-c-format
msgid "Controlling the flow"
-msgstr ""
+msgstr "Controler le flot"
#. Tag: para
#: Jbpm.xml:413
#, no-c-format
-msgid ""
-"Usually, we don't need the more powerful features of jPDL when defining "
-"pageflows. We do need the <literal><decision></literal> node, however:"
-msgstr ""
+msgid "Usually, we don't need the more powerful features of jPDL when defining pageflows. We do need the <literal><decision></literal> node, however:"
+msgstr "Habituellement, nous n'avons pas besoin des fonctionnalités les plus puissantes de jPDL pendant la définition des enchainements de pages. Nous avons besoin du noeud <literal><decision></literal>, malgré tout: "
#. Tag: programlisting
#: Jbpm.xml:418
#, no-c-format
msgid ""
-"<![CDATA[<decision name=\"evaluateGuess\" expression=\"#{numberGuess."
-"correctGuess}\">\n"
+"<![CDATA[<decision name=\"evaluateGuess\" expression=\"#{numberGuess.correctGuess}\">\n"
" <transition name=\"true\" to=\"win\"/>\n"
" <transition name=\"false\" to=\"evaluateRemainingGuesses\"/>\n"
"</decision>]]>"
msgstr ""
+"<![CDATA[<decision name=\"evaluateGuess\" expression=\"#{numberGuess.correctGuess}\">\n"
+" <transition name=\"true\" to=\"win\"/>\n"
+" <transition name=\"false\" to=\"evaluateRemainingGuesses\"/>\n"
+"</decision>]]>"
#. Tag: para
#: Jbpm.xml:420
#, no-c-format
-msgid ""
-"A decision is made by evaluating a JSF EL expression in the Seam contexts."
-msgstr ""
+msgid "A decision is made by evaluating a JSF EL expression in the Seam contexts."
+msgstr "Une décision est faite en évaluant une expression JSF EL dans les contextes de Seam. "
#. Tag: title
#: Jbpm.xml:427
#, no-c-format
msgid "Ending the flow"
-msgstr ""
+msgstr "Terminer le flot"
#. Tag: para
#: Jbpm.xml:429
#, no-c-format
-msgid ""
-"We end the conversation using <literal><end-conversation></literal> or "
-"<literal>@End</literal>. (In fact, for readability, use of <emphasis>both</"
-"emphasis> is encouraged.)"
-msgstr ""
+msgid "We end the conversation using <literal><end-conversation></literal> or <literal>@End</literal>. (In fact, for readability, use of <emphasis>both</emphasis> is encouraged.)"
+msgstr "Nous finissons la conversation en utilisant <literal><end-conversation></literal> ou <literal>@End</literal>. (Dans les faits, pour la lisibilité, l'utilisation des deux est encouragé.) "
#. Tag: programlisting
#: Jbpm.xml:435
@@ -801,15 +766,16 @@
" <end-conversation/>\n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page name=\"win\" view-id=\"/win.jsp\">\n"
+" <redirect/>\n"
+" <end-conversation/>\n"
+"</page>]]>"
#. Tag: para
#: Jbpm.xml:437
#, no-c-format
-msgid ""
-"Optionally, we can end a task, specify a jBPM <literal>transition</literal> "
-"name. In this case, Seam will signal the end of the current task in the "
-"overarching business process."
-msgstr ""
+msgid "Optionally, we can end a task, specify a jBPM <literal>transition</literal> name. In this case, Seam will signal the end of the current task in the overarching business process."
+msgstr "De manière optionnel, nous pouvons finir une tâche, spécifiant un nom de <literal>transition</literal> jBPM. Dans ce cas, Seam va signaler la fin de la tâche courrante dans le processus métier hypercintré. "
#. Tag: programlisting
#: Jbpm.xml:443
@@ -820,21 +786,22 @@
" <end-task transition=\"success\"/>\n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page name=\"win\" view-id=\"/win.jsp\">\n"
+" <redirect/>\n"
+" <end-task transition=\"success\"/>\n"
+"</page>]]>"
#. Tag: title
#: Jbpm.xml:448
#, no-c-format
msgid "Pageflow composition"
-msgstr ""
+msgstr "La composition de l'enchainement de page"
#. Tag: para
#: Jbpm.xml:449
#, no-c-format
-msgid ""
-"It is possible to compose pageflows and have one pageflow pause pause while "
-"another pageflow executes. The <literal><process-state></literal> node "
-"pauses the outer pageflow, and begins execution of a named pageflow:"
-msgstr ""
+msgid "It is possible to compose pageflows and have one pageflow pause pause while another pageflow executes. The <literal><process-state></literal> node pauses the outer pageflow, and begins execution of a named pageflow:"
+msgstr "Il ets possible de composer des enchainements de page et d'avoir une pause dans l'enchainement de page alors qu'un autre enchainement s'exécute. Le noeud <literal><process-state></literal> met en pausse l'enchainement de page indiqué et comme l'exécution de l'enchainement de page appelé:"
#. Tag: programlisting
#: Jbpm.xml:456
@@ -845,48 +812,34 @@
" <transition to=\"displayGuess\"/>\n"
"</process-state>]]>"
msgstr ""
+"<![CDATA[<process-state name=\"cheat\">\n"
+" <sub-process name=\"cheat\"/>\n"
+" <transition to=\"displayGuess\"/>\n"
+"</process-state>]]>"
#. Tag: para
#: Jbpm.xml:458
#, no-c-format
-msgid ""
-"The inner flow begins executing at a <literal><start-state></literal> "
-"node. When it reaches an <literal><end-state></literal> node, "
-"execution of the inner flow ends, and execution of the outer flow resumes "
-"with the transition defined by the <literal><process-state></literal> "
-"element."
-msgstr ""
+msgid "The inner flow begins executing at a <literal><start-state></literal> node. When it reaches an <literal><end-state></literal> node, execution of the inner flow ends, and execution of the outer flow resumes with the transition defined by the <literal><process-state></literal> element."
+msgstr "Le flot inclus commence en exécutant un noeud <literal><start-state></literal>. Quand il atteind un noeud <literal><end-state></literal>, l'exécution du flot inclus s'arrête et l'exécution du flot englobant recommence avec la transition définie dans l'élement <literal><process-state></literal>."
#. Tag: title
#: Jbpm.xml:471
#, no-c-format
msgid "Business process management in Seam"
-msgstr ""
+msgstr "La gestion des processus métier dans Seam"
#. Tag: para
#: Jbpm.xml:472
#, no-c-format
-msgid ""
-"A business process is a well-defined set of tasks that must be performed by "
-"users or software systems according to well-defined rules about "
-"<emphasis>who</emphasis> can perform a task, and <emphasis>when</emphasis> "
-"it should be performed. Seam's jBPM integration makes it easy to display "
-"lists of tasks to users and let them manage their tasks. Seam also lets the "
-"application store state associated with the business process in the "
-"<literal>BUSINESS_PROCESS</literal> context, and have that state made "
-"persistent via jBPM variables."
-msgstr ""
+msgid "A business process is a well-defined set of tasks that must be performed by users or software systems according to well-defined rules about <emphasis>who</emphasis> can perform a task, and <emphasis>when</emphasis> it should be performed. Seam's jBPM integration makes it easy to display lists of tasks to users and let them manage their tasks. Seam also lets the application store state associated with the business process in the <literal>BUSINESS_PROCESS</literal> context, and have that state made persistent via jBPM variables."
+msgstr "Un processus métier est un groupe de tâche bien définis qui doivent être réaliser par des utilisateurs ou des systèmes logiciels en accord avec des règles bien définies à propos de <emphasis>qui</emphasis> peut réaliser une tâche, et <emphasis>quand</emphasis> elle devrait être réalisée. L'intégration de JBPM dans Seam rend facile d'afficher la liste des tâches des utilisateurs et les laisser gérer leurs tâches. Seam permet aussi à l'application stocker l'état associé avec le processus métier dans le contexte <literal>BUSINESS_PROCESS</literal> et avoir cet état qui soit persistant via les variables du jBPM. "
#. Tag: para
#: Jbpm.xml:484
#, no-c-format
-msgid ""
-"A simple business process definition looks much the same as a page flow "
-"definition (<emphasis>One Kind of Stuff</emphasis>), except that instead of "
-"<literal><page></literal> nodes, we have <literal><task-node></"
-"literal> nodes. In a long-running business process, the wait states are "
-"where the system is waiting for some user to log in and perform a task."
-msgstr ""
+msgid "A simple business process definition looks much the same as a page flow definition (<emphasis>One Kind of Stuff</emphasis>), except that instead of <literal><page></literal> nodes, we have <literal><task-node></literal> nodes. In a long-running business process, the wait states are where the system is waiting for some user to log in and perform a task."
+msgstr "Une simple définition de processus métier ressemble assez à la définition de l'enchainement de page (<emphasis>Un Seul Genre de Truc</emphasis>), exception sauf qu'au lieu d'un noeud <literal><page></literal> , nous avons des noeuds <literal><task-node></literal>. Dans un procéssus métier à exécution longue, les état d'atente sont là où le système est en attente qu'un utilisateur se connecte pour réaliser une tâche. "
#. Tag: programlisting
#: Jbpm.xml:493
@@ -909,37 +862,46 @@
" \n"
"</process-definition>]]>"
msgstr ""
+"<![CDATA[<process-definition name=\"todo\">\n"
+" \n"
+" <start-state name=\"start\">\n"
+" <transition to=\"todo\"/>\n"
+" </start-state>\n"
+" \n"
+" <task-node name=\"todo\">\n"
+" <task name=\"todo\" description=\"#{todoList.description}\">\n"
+" <assignment actor-id=\"#{actor.id}\"/>\n"
+" </task>\n"
+" <transition to=\"done\"/>\n"
+" </task-node>\n"
+" \n"
+" <end-state name=\"done\"/>\n"
+" \n"
+"</process-definition>]]>"
#. Tag: para
#: Jbpm.xml:505
#, no-c-format
-msgid ""
-"It is perfectly possible that we might have both jPDL business process "
-"definitions and jPDL pageflow definitions in the same project. If so, the "
-"relationship between the two is that a single <literal><task></"
-"literal> in a business process corresponds to a whole pageflow <literal><"
-"pageflow-definition></literal>"
-msgstr ""
+msgid "It is perfectly possible that we might have both jPDL business process definitions and jPDL pageflow definitions in the same project. If so, the relationship between the two is that a single <literal><task></literal> in a business process corresponds to a whole pageflow <literal><pageflow-definition></literal>"
+msgstr "Il est parfaitement possible que nous ayons à la fois des définition de processus métier en jPDL et des définitions d'enchainements de pages en jPDL dans le même projet. Et donc, la relation entre les deux est qu'un seul <literal><task></literal> dans un processus métier correspond à l'ensemble d'un enchainement de page <literal><pageflow-definition></literal>"
#. Tag: title
#: Jbpm.xml:516
#, no-c-format
msgid "Using jPDL business process definitions"
-msgstr ""
+msgstr "Utilisation des définitions de processus métier jPDL"
#. Tag: title
#: Jbpm.xml:519
#, no-c-format
msgid "Installing process definitions"
-msgstr ""
+msgstr "Installation des définition de processus"
#. Tag: para
#: Jbpm.xml:521
#, no-c-format
-msgid ""
-"We need to install jBPM, and tell it where to find the business process "
-"definitions:"
-msgstr ""
+msgid "We need to install jBPM, and tell it where to find the business process definitions:"
+msgstr "Nous avons besoin d'installer un jBPM, et de lui dire où trouver les définition de processus métier : "
#. Tag: programlisting
#: Jbpm.xml:526
@@ -951,34 +913,29 @@
" </bpm:process-definitions>\n"
"</bpm:jbpm>]]>"
msgstr ""
+"<![CDATA[<bpm:jbpm>\n"
+" <bpm:process-definitions>\n"
+" <value>todo.jpdl.xml</value>\n"
+" </bpm:process-definitions>\n"
+"</bpm:jbpm>]]>"
#. Tag: para
#: Jbpm.xml:528
#, no-c-format
-msgid ""
-"As jBPM processes are persistent across application restarts, when using "
-"Seam in a production environment you won't want to install the process "
-"definition every time the application starts. Therefore, in a production "
-"environment, you'll need to deploy the process to jBPM outside of Seam. In "
-"other words, only install process definitions from <literal>components.xml</"
-"literal> when developing your application."
-msgstr ""
+msgid "As jBPM processes are persistent across application restarts, when using Seam in a production environment you won't want to install the process definition every time the application starts. Therefore, in a production environment, you'll need to deploy the process to jBPM outside of Seam. In other words, only install process definitions from <literal>components.xml</literal> when developing your application."
+msgstr "Les processus jBPM sont persistant au travers du redémarrage de l'application, avec l'utilisation de Seam dans un environement de production vous ne voudriez pas avoir à installer la définition de processus à chaque fois que l'application démarre. Cependant, dans un environement de production vous allez avoir besoin de détruire le processus jBPM à l'extérieur de Seam. En d'autres termes, installez seulement le processus de définitions dans <literal>components.xml</literal> pendant le développement de votre application."
#. Tag: title
#: Jbpm.xml:541
#, no-c-format
msgid "Initializing actor ids"
-msgstr ""
+msgstr "Initialisation des identifiants des acteurs"
#. Tag: para
#: Jbpm.xml:543
#, no-c-format
-msgid ""
-"We always need to know what user is currently logged in. jBPM \"knows\" "
-"users by their <emphasis>actor id</emphasis> and <emphasis>group actor ids</"
-"emphasis>. We specify the current actor ids using the built in Seam "
-"component named <literal>actor</literal>:"
-msgstr ""
+msgid "We always need to know what user is currently logged in. jBPM \"knows\" users by their <emphasis>actor id</emphasis> and <emphasis>group actor ids</emphasis>. We specify the current actor ids using the built in Seam component named <literal>actor</literal>:"
+msgstr "Nous avons toujours besoin de connaitre quel utilisateur est actuellement connecté. jBPM \"connait\" les utilisateur par <emphasis>leur identifiant d'acteur</emphasis> et par <emphasis>leurs identifiants de groupe d'acteur</emphasis>. Nous spécifions les identifiant d'acteur courrant en utilisant le composant livré dans Seam nommé <literal>actor</literal>: "
#. Tag: programlisting
#: Jbpm.xml:551
@@ -993,20 +950,26 @@
" ...\n"
"}]]>"
msgstr ""
+"<![CDATA[@In Actor actor;\n"
+"\n"
+"public String login() {\n"
+" ...\n"
+" actor.setId( user.getUserName() );\n"
+" actor.getGroupActorIds().addAll( user.getGroupNames() );\n"
+" ...\n"
+"}]]>"
#. Tag: title
#: Jbpm.xml:556
#, no-c-format
msgid "Initiating a business process"
-msgstr ""
+msgstr "Initialisation d'un processus métier"
#. Tag: para
#: Jbpm.xml:558
#, no-c-format
-msgid ""
-"To initiate a business process instance, we use the <literal>@CreateProcess</"
-"literal> annotation:"
-msgstr ""
+msgid "To initiate a business process instance, we use the <literal>@CreateProcess</literal> annotation:"
+msgstr "Pour initialiser une instance d'un processus métier, nous utilisons l'annotation literal>@CreateProcess</literal>: "
#. Tag: programlisting
#: Jbpm.xml:563
@@ -1015,12 +978,14 @@
"<![CDATA[@CreateProcess(definition=\"todo\")\n"
"public void createTodo() { ... }]]>"
msgstr ""
+"<![CDATA[@CreateProcess(definition=\"todo\")\n"
+"public void createTodo() { ... }]]>"
#. Tag: para
#: Jbpm.xml:565
#, no-c-format
msgid "Alternatively we can initiate a business process using pages.xml:"
-msgstr ""
+msgstr "Autre alternative, nous pouvons initialiser un processus métier en utilisant pages.xml:"
#. Tag: programlisting
#: Jbpm.xml:567
@@ -1030,21 +995,21 @@
" <create-process definition=\"todo\" />\n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page>\n"
+" <create-process definition=\"todo\" />\n"
+"</page>]]>"
#. Tag: title
#: Jbpm.xml:572
#, no-c-format
msgid "Task assignment"
-msgstr ""
+msgstr "Assigner une tâche"
#. Tag: para
#: Jbpm.xml:574
#, no-c-format
-msgid ""
-"When a process reaches a task node, task instances are created. These must "
-"be assigned to users or user groups. We can either hardcode our actor ids, "
-"or delegate to a Seam component:"
-msgstr ""
+msgid "When a process reaches a task node, task instances are created. These must be assigned to users or user groups. We can either hardcode our actor ids, or delegate to a Seam component:"
+msgstr "Quand un processus démarre, les instances de tâches sont créés. Ils doivent être assignés aux utilisateurs et aux groupes d'utilisateurs. Nous pouvons coder en durs les idenfiants d'acteur ou le déléguer à un composant de Seam: "
#. Tag: programlisting
#: Jbpm.xml:580
@@ -1054,14 +1019,15 @@
" <assignment actor-id=\"#{actor.id}\"/>\n"
"</task>]]>"
msgstr ""
+"<![CDATA[<task name=\"todo\" description=\"#{todoList.description}\">\n"
+" <assignment actor-id=\"#{actor.id}\"/>\n"
+"</task>]]>"
#. Tag: para
#: Jbpm.xml:582
#, no-c-format
-msgid ""
-"In this case, we have simply assigned the task to the current user. We can "
-"also assign tasks to a pool:"
-msgstr ""
+msgid "In this case, we have simply assigned the task to the current user. We can also assign tasks to a pool:"
+msgstr "Dans ce cas, nous avons simplement assigné la tâche à l'utilisateur courrant. Nous pouvons aussi assigné les tâches à un groupement: "
#. Tag: programlisting
#: Jbpm.xml:587
@@ -1071,21 +1037,21 @@
" <assignment pooled-actors=\"employees\"/>\n"
"</task>]]>"
msgstr ""
+"<![CDATA[<task name=\"todo\" description=\"#{todoList.description}\">\n"
+" <assignment pooled-actors=\"employees\"/>\n"
+"</task>]]>"
#. Tag: title
#: Jbpm.xml:592
#, no-c-format
msgid "Task lists"
-msgstr ""
+msgstr "Liste des tâches"
#. Tag: para
#: Jbpm.xml:594
#, no-c-format
-msgid ""
-"Several built-in Seam components make it easy to display task lists. The "
-"<literal>pooledTaskInstanceList</literal> is a list of pooled tasks that "
-"users may assign to themselves:"
-msgstr ""
+msgid "Several built-in Seam components make it easy to display task lists. The <literal>pooledTaskInstanceList</literal> is a list of pooled tasks that users may assign to themselves:"
+msgstr "Plusieurs composant livrés dans Seam rendent facile l'affichage de listes de tâches. Le <literal>pooledTaskInstanceList</literal> est une liste de tâches en groupement que les utilisateurs peuvent assigner à eux-même: "
#. Tag: programlisting
#: Jbpm.xml:600
@@ -1097,19 +1063,25 @@
" <h:outputText value=\"#{task.description}\"/>\n"
" </h:column>\n"
" <h:column>\n"
-" <s:link action=\"#{pooledTask.assignToCurrentActor}\" value=\"Assign"
-"\" taskInstance=\"#{task}\"/>\n"
+" <s:link action=\"#{pooledTask.assignToCurrentActor}\" value=\"Assign\" taskInstance=\"#{task}\"/>\n"
" </h:column> \n"
"</h:dataTable>]]>"
msgstr ""
+"<![CDATA[<h:dataTable value=\"#{pooledTaskInstanceList}\" var=\"task\">\n"
+" <h:column>\n"
+" <f:facet name=\"header\">Description</f:facet>\n"
+" <h:outputText value=\"#{task.description}\"/>\n"
+" </h:column>\n"
+" <h:column>\n"
+" <s:link action=\"#{pooledTask.assignToCurrentActor}\" value=\"Assign\" taskInstance=\"#{task}\"/>\n"
+" </h:column> \n"
+"</h:dataTable>]]>"
#. Tag: para
#: Jbpm.xml:602
#, no-c-format
-msgid ""
-"Note that instead of <literal><s:link></literal> we could have used a "
-"plain JSF <literal><h:commandLink></literal>:"
-msgstr ""
+msgid "Note that instead of <literal><s:link></literal> we could have used a plain JSF <literal><h:commandLink></literal>:"
+msgstr "Notez qu'au lieu de <literal><s:link></literal> nous pouvons utiliser un <literal><h:commandLink></literal> en pur JSF : "
#. Tag: programlisting
#: Jbpm.xml:607
@@ -1119,53 +1091,57 @@
" <f:param name=\"taskId\" value=\"#{task.id}\"/>\n"
"</h:commandLink>]]>"
msgstr ""
+"<![CDATA[<h:commandLink action=\"#{pooledTask.assignToCurrentActor}\"> \n"
+" <f:param name=\"taskId\" value=\"#{task.id}\"/>\n"
+"</h:commandLink>]]>"
#. Tag: para
#: Jbpm.xml:609
#, no-c-format
-msgid ""
-"The <literal>pooledTask</literal> component is a built-in component that "
-"simply assigns the task to the current user."
-msgstr ""
+msgid "The <literal>pooledTask</literal> component is a built-in component that simply assigns the task to the current user."
+msgstr "Le composant <literal>pooledTask</literal> est un composant livré qui assigne simplement la tâche à l'utilisateur courrant. "
#. Tag: para
#: Jbpm.xml:614
#, no-c-format
-msgid ""
-"The <literal>taskInstanceListForType</literal> component includes tasks of a "
-"particular type that are assigned to the current user:"
-msgstr ""
+msgid "The <literal>taskInstanceListForType</literal> component includes tasks of a particular type that are assigned to the current user:"
+msgstr "Le composant <literal>taskInstanceListForType</literal> inclus les tâches d'un type particulier qui sont assigné à l'utilisateur courrant: "
#. Tag: programlisting
#: Jbpm.xml:619
#, no-c-format
msgid ""
-"<![CDATA[<h:dataTable value=\"#{taskInstanceListForType['todo']}\" var=\"task"
-"\">\n"
+"<![CDATA[<h:dataTable value=\"#{taskInstanceListForType['todo']}\" var=\"task\">\n"
" <h:column>\n"
" <f:facet name=\"header\">Description</f:facet>\n"
" <h:outputText value=\"#{task.description}\"/>\n"
" </h:column>\n"
" <h:column>\n"
-" <s:link action=\"#{todoList.start}\" value=\"Start Work\" "
-"taskInstance=\"#{task}\"/>\n"
+" <s:link action=\"#{todoList.start}\" value=\"Start Work\" taskInstance=\"#{task}\"/>\n"
" </h:column> \n"
"</h:dataTable>]]>"
msgstr ""
+"<![CDATA[<h:dataTable value=\"#{taskInstanceListForType['todo']}\" var=\"task\">\n"
+" <h:column>\n"
+" <f:facet name=\"header\">Description</f:facet>\n"
+" <h:outputText value=\"#{task.description}\"/>\n"
+" </h:column>\n"
+" <h:column>\n"
+" <s:link action=\"#{todoList.start}\" value=\"Start Work\" taskInstance=\"#{task}\"/>\n"
+" </h:column> \n"
+"</h:dataTable>]]>"
#. Tag: title
#: Jbpm.xml:624
#, no-c-format
msgid "Performing a task"
-msgstr ""
+msgstr "Réalisation d'une tâche"
#. Tag: para
#: Jbpm.xml:626
#, no-c-format
-msgid ""
-"To begin work on a task, we use either <literal>@StartTask</literal> or "
-"<literal>@BeginTask</literal> on the listener method:"
-msgstr ""
+msgid "To begin work on a task, we use either <literal>@StartTask</literal> or <literal>@BeginTask</literal> on the listener method:"
+msgstr "Pour commencer le travail sur une tâche, nous utilisons aussi bien <literal>@StartTask</literal> ou <literal>@BeginTask</literal> sur la méthode d'écoute: "
#. Tag: programlisting
#: Jbpm.xml:631
@@ -1174,12 +1150,14 @@
"<![CDATA[@StartTask\n"
"public String start() { ... }]]>"
msgstr ""
+"<![CDATA[@StartTask\n"
+"public String start() { ... }]]>"
#. Tag: para
#: Jbpm.xml:633
#, no-c-format
msgid "Alternatively we can begin work on a task using pages.xml:"
-msgstr ""
+msgstr "Autre alternative, nous pouvons commencer le travail sur une tâche en utilisant pages.xml:"
#. Tag: programlisting
#: Jbpm.xml:635
@@ -1189,23 +1167,21 @@
" <start-task />\n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page>\n"
+" <start-task />\n"
+"</page>]]>"
#. Tag: para
#: Jbpm.xml:637
#, no-c-format
-msgid ""
-"These annotations begin a special kind of conversation that has significance "
-"in terms of the overarching business process. Work done by this conversation "
-"has access to state held in the business process context."
-msgstr ""
+msgid "These annotations begin a special kind of conversation that has significance in terms of the overarching business process. Work done by this conversation has access to state held in the business process context."
+msgstr "Ces annotations commencent une type spécial de conversation qui ont de l'importance en terme de processus métier hypercintré. Le travail fait par cette conversation à accès à l'état contenue dans le processus métier dans le contexte de processus métier. "
#. Tag: para
#: Jbpm.xml:644
#, no-c-format
-msgid ""
-"If we end the conversation using <literal>@EndTask</literal>, Seam will "
-"signal the completion of the task:"
-msgstr ""
+msgid "If we end the conversation using <literal>@EndTask</literal>, Seam will signal the completion of the task:"
+msgstr "Si nous finisons la conversation en utilisant <literal>@EndTask</literal>, Seam va signaler la réalisation de la tâche: "
#. Tag: programlisting
#: Jbpm.xml:649
@@ -1214,12 +1190,14 @@
"<![CDATA[@EndTask(transition=\"completed\")\n"
"public String completed() { ... }]]>"
msgstr ""
+"<![CDATA[@EndTask(transition=\"completed\")\n"
+"public String completed() { ... }]]>"
#. Tag: para
#: Jbpm.xml:651
#, no-c-format
msgid "Alternatively we can use pages.xml:"
-msgstr ""
+msgstr "Autre alternative, nous pouvons utiliser pages.xml:"
#. Tag: programlisting
#: Jbpm.xml:653
@@ -1229,27 +1207,25 @@
" <end-task transition=\"completed\" />\n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page>\n"
+" <end-task transition=\"completed\" />\n"
+"</page>]]>"
#. Tag: para
#: Jbpm.xml:655
#, no-c-format
msgid "You can also use EL to specify the transition in pages.xml."
-msgstr ""
+msgstr "Vous pouvez aussi utiliser une EL pour spécifier la transition dans pages.xml."
#. Tag: para
#: Jbpm.xml:659
#, no-c-format
-msgid ""
-"At this point, jBPM takes over and continues executing the business process "
-"definition. (In more complex processes, several tasks might need to be "
-"completed before process execution can resume.)"
-msgstr ""
+msgid "At this point, jBPM takes over and continues executing the business process definition. (In more complex processes, several tasks might need to be completed before process execution can resume.)"
+msgstr "A ce moment, jBPM prends le contrôle et continue l'exécution de la définition du processus métier. (Dans des processus plus complexes, plusieurs tâches peuvent avoir besoin d'être réalisés avant que l'exécution du processus ne puisse reprendre.) "
#. Tag: para
#: Jbpm.xml:665
#, no-c-format
-msgid ""
-"Please refer to the jBPM documentation for a more thorough overview of the "
-"sophisticated features that jBPM provides for managing complex business "
-"processes."
-msgstr ""
+msgid "Please refer to the jBPM documentation for a more thorough overview of the sophisticated features that jBPM provides for managing complex business processes."
+msgstr "Merci de vous référer à la document de jBPM pour un apperçu plus détaillé des fonctionnalités sophistiquées que le jBPM fournir pour la gestion des processus métier complexes. "
+
More information about the seam-commits
mailing list