[seam-commits] Seam SVN: r11616 - branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR.

[seam-commits at lists.jboss.org]

Author: essaidetest
Date: 2009-10-24 16:25:57 -0400 (Sat, 24 Oct 2009)
New Revision: 11616

Modified:
   branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Preface.po
Log:


Modified: branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Preface.po
===================================================================
--- branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Preface.po	2009-10-23 15:47:38 UTC (rev 11615)
+++ branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Preface.po	2009-10-24 20:25:57 UTC (rev 11616)
@@ -6,8 +6,8 @@
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: http://bugs.kde.org\n"
 "POT-Creation-Date: 2009-01-18 15:00+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2009-10-24 22:25+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,414 +17,245 @@
 #: Preface.xml:7
 #, no-c-format
 msgid "Introduction to JBoss Seam"
-msgstr ""
+msgstr "Introduction à JBoss Seam"
 
 #. Tag: para
 #: Preface.xml:9
 #, no-c-format
-msgid ""
-"Seam is an application framework for Enterprise Java. It is inspired by the "
-"following principles:"
-msgstr ""
+msgid "Seam is an application framework for Enterprise Java. It is inspired by the following principles:"
+msgstr "Seam est un serveur d'application pour Java EE5. Il a été inspiré par les principes suivants:"
 
 #. Tag: emphasis
 #: Preface.xml:16
 #, no-c-format
 msgid "One kind of \"stuff\""
-msgstr ""
+msgstr "Une seule sorte de \"truc\""
 
 #. Tag: para
 #: Preface.xml:18
 #, no-c-format
-msgid ""
-"Seam defines a uniform component model for all business logic in your "
-"application. A Seam component may be stateful, with the state associated "
-"with any one of several well-defined contexts, including the long-running, "
-"persistent, <emphasis>business process context</emphasis> and the "
-"<emphasis>conversation context</emphasis>, which is preserved across "
-"multiple web requests in a user interaction."
-msgstr ""
+msgid "Seam defines a uniform component model for all business logic in your application. A Seam component may be stateful, with the state associated with any one of several well-defined contexts, including the long-running, persistent, <emphasis>business process context</emphasis> and the <emphasis>conversation context</emphasis>, which is preserved across multiple web requests in a user interaction."
+msgstr "Seam défini un modèle de composant uniforme pour toute la logique métier de votre application. Un composant Seam peut être avec état, avec état associé avec au choix un des contextes bien définie, ce qui inclus <emphasis>le contexte de processus métier</emphasis> à exécution longue et <emphasis>le contexte conversationnel</emphasis> qui est préservé au travers de plusieurs requêtes web dans les intéractions utilisateur."
 
 #. Tag: para
 #: Preface.xml:25
 #, no-c-format
-msgid ""
-"There is no distinction between presentation tier components and business "
-"logic components in Seam. You can layer your application according to "
-"whatever architecture you devise, rather than being forced to shoehorn your "
-"application logic into an unnatural layering scheme forced upon you by "
-"whatever combination of stovepipe frameworks you're using today."
-msgstr ""
+msgid "There is no distinction between presentation tier components and business logic components in Seam. You can layer your application according to whatever architecture you devise, rather than being forced to shoehorn your application logic into an unnatural layering scheme forced upon you by whatever combination of stovepipe frameworks you're using today."
+msgstr "Il n'y a pas de distinction entre les composants tierces de présentations et les composants de logique métier dans Seam. Vous pouvez mettre en plusieurs couches votre application en accord avec l'architecture de votre choix, au lieu d'être forcé de tordre votre logique d'application dans un schéma avec des couches anormales en étant forcé par une combinaisons de tuyaux des serveurs d'applications que vous utilisez aujourd'hui."
 
 #. Tag: para
 #: Preface.xml:32
 #, no-c-format
-msgid ""
-"Unlike plain Java EE or J2EE components, Seam components may "
-"<emphasis>simultaneously</emphasis> access state associated with the web "
-"request and state held in transactional resources (without the need to "
-"propagate web request state manually via method parameters). You might "
-"object that the application layering imposed upon you by the old J2EE "
-"platform was a Good Thing. Well, nothing stops you creating an equivalent "
-"layered architecture using Seam &#8212; the difference is that "
-"<emphasis>you</emphasis> get to architect your own application and decide "
-"what the layers are and how they work together."
-msgstr ""
+msgid "Unlike plain Java EE or J2EE components, Seam components may <emphasis>simultaneously</emphasis> access state associated with the web request and state held in transactional resources (without the need to propagate web request state manually via method parameters). You might object that the application layering imposed upon you by the old J2EE platform was a Good Thing. Well, nothing stops you creating an equivalent layered architecture using Seam &#8212; the difference is that <emphasis>you</emphasis> get to architect your own application and decide what the layers are and how they work together."
+msgstr "A la différence des composants pur Java EE ou J2EE, les composants Seam peuvent accèder <emphasis>simultanément</emphasis> aux états associés avec la requête web et avec l'état conservé dans les ressources transactionnelles (sans avoir besoin de propager l'état de la requête web avec des paramètres de la méthode). Vous pouvez objecter que la conception en couche de l'application qui vous est imposée par la vieille plateforme J2EE est une Bonne Chose. Et bien, rien ne vous empêche de ne pas créer une architecture en couche équivalent en utilisant Seam  &#8212; la différence est que <emphasis>vous</emphasis> pouvez convevoir votre application et décider quel mis en couche vous avez et comment elles vont fonctionner ensemble."
 
 #. Tag: emphasis
 #: Preface.xml:45
 #, no-c-format
 msgid "Integrate JSF with EJB 3.0"
-msgstr ""
+msgstr "Intégrer JSF avec EJB3.0"
 
 #. Tag: para
 #: Preface.xml:47
 #, no-c-format
-msgid ""
-"JSF and EJB 3.0 are two of the best new features of Java EE 5. EJB3 is a "
-"brand new component model for server side business and persistence logic. "
-"Meanwhile, JSF is a great component model for the presentation tier. "
-"Unfortunately, neither component model is able to solve all problems in "
-"computing by itself. Indeed, JSF and EJB3 work best used together. But the "
-"Java EE 5 specification provides no standard way to integrate the two "
-"component models. Fortunately, the creators of both models foresaw this "
-"situation and provided standard extension points to allow extension and "
-"integration with other frameworks."
-msgstr ""
+msgid "JSF and EJB 3.0 are two of the best new features of Java EE 5. EJB3 is a brand new component model for server side business and persistence logic. Meanwhile, JSF is a great component model for the presentation tier. Unfortunately, neither component model is able to solve all problems in computing by itself. Indeed, JSF and EJB3 work best used together. But the Java EE 5 specification provides no standard way to integrate the two component models. Fortunately, the creators of both models foresaw this situation and provided standard extension points to allow extension and integration with other frameworks."
+msgstr "JSF et EJB 3.0 sont deux des meilleures fonctionnalités récentes de Java EE5. EJB3 est un modèle de composant tout nouveau pour l’applicatif métier côté serveur et la logique de persistance. Principalement, JSF est un bon modèle par composants pour la partie présentation. Malheureusement, le modèle de composant n’est pas capable de résoudre tous les problèmes dans la programmation elle-même. En fait, JSF et EJB3 fonctionnent bien ensemble. Mais les spécifications Java EE 5 ne fournissent pas un moyen standard pour intégrer les 2 modèles de composants. Heureusement, les créateurs de ces 2 modèles ont prévu cette situation et fournissent des points d’extensions standard  pour permettre l’extension et l’intégration d’autres serveurs d'applications."
 
 #. Tag: para
 #: Preface.xml:57
 #, no-c-format
-msgid ""
-"Seam unifies the component models of JSF and EJB3, eliminating glue code, "
-"and letting the developer think about the business problem."
-msgstr ""
+msgid "Seam unifies the component models of JSF and EJB3, eliminating glue code, and letting the developer think about the business problem."
+msgstr "Seam unifie les modèles de composants de JSF et d’EJB3, élimant le code glue, et laissant le développeur se concentrer sur les problèmes du métier. "
 
 #. Tag: para
 #: Preface.xml:61
 #, no-c-format
-msgid ""
-"It is possible to write Seam applications where \"everything\" is an EJB. "
-"This may come as a surprise if you're used to thinking of EJBs as coarse-"
-"grained, so-called \"heavyweight\" objects. However, version 3.0 has "
-"completely changed the nature of EJB from the point of view of the "
-"developer. An EJB is a fine-grained object &#8212; nothing more complex than "
-"an annotated JavaBean. Seam even encourages you to use session beans as JSF "
-"action listeners!"
-msgstr ""
+msgid "It is possible to write Seam applications where \"everything\" is an EJB. This may come as a surprise if you're used to thinking of EJBs as coarse-grained, so-called \"heavyweight\" objects. However, version 3.0 has completely changed the nature of EJB from the point of view of the developer. An EJB is a fine-grained object &#8212; nothing more complex than an annotated JavaBean. Seam even encourages you to use session beans as JSF action listeners!"
+msgstr "Il est possible d'écrire des applications Seam avec \"tout\" est un EJB. Cela peut être une grosse surprise si vous avez l'habitude de pensez aux EJBs comme des gros grains, des objets \"super-lourd\". Cependant, la version 3.0 a complètement changé la nature de l'EJB depuis le point de vu du développeur. Un EJB est un objet bien dimensionné  &#8212; rien de bien complexe qu'un JavaBean annoté. Seam vous encourage même à utiliser les beans de sessions comme des écouteurs d'actions JSF!"
 
 #. Tag: para
 #: Preface.xml:69
 #, no-c-format
-msgid ""
-"On the other hand, if you prefer not to adopt EJB 3.0 at this time, you "
-"don't have to. Virtually any Java class may be a Seam component, and Seam "
-"provides all the functionality that you expect from a \"lightweight\" "
-"container, and more, for any component, EJB or otherwise."
-msgstr ""
+msgid "On the other hand, if you prefer not to adopt EJB 3.0 at this time, you don't have to. Virtually any Java class may be a Seam component, and Seam provides all the functionality that you expect from a \"lightweight\" container, and more, for any component, EJB or otherwise."
+msgstr "D'un autre côté, si vous préférez ne pas adopter EJB 3.0 pour l'instant, vous n'avez pas à le faire. Virtuellement toute classe Java peut être un composant de Seam et Seam fourni toute les fonctionnalité que vous attendez pour un container \"poid-mouche\" et bien plus, pour chaque composant, EJB ou autre."
 
 #. Tag: emphasis
 #: Preface.xml:79
 #, no-c-format
 msgid "Integrated AJAX"
-msgstr ""
+msgstr "Integration AJAX"
 
 #. Tag: para
 #: Preface.xml:81
 #, no-c-format
-msgid ""
-"Seam supports the best open source JSF-based AJAX solutions: JBoss RichFaces "
-"and ICEfaces. These solutions let you add AJAX capability to your user "
-"interface without the need to write any JavaScript code."
-msgstr ""
+msgid "Seam supports the best open source JSF-based AJAX solutions: JBoss RichFaces and ICEfaces. These solutions let you add AJAX capability to your user interface without the need to write any JavaScript code."
+msgstr "Seam utilise deux excelents solutions open source AJAX basé sur JSF: JBoss RichFace et ICEfaces. Ces solutions permettent d’ajouter les capacités d’AJAX à vos interfaces utilisateur sans avoir besoin d’écrire du code Javascript. "
 
 #. Tag: para
 #: Preface.xml:86
 #, no-c-format
-msgid ""
-"Alternatively, Seam provides a built-in JavaScript remoting layer that lets "
-"you call components asynchronously from client-side JavaScript without the "
-"need for an intermediate action layer. You can even subscribe to server-side "
-"JMS topics and receive messages via AJAX push."
-msgstr ""
+msgid "Alternatively, Seam provides a built-in JavaScript remoting layer that lets you call components asynchronously from client-side JavaScript without the need for an intermediate action layer. You can even subscribe to server-side JMS topics and receive messages via AJAX push."
+msgstr "Autrement, Seam fourni aussi un couche distante développée en Javascript vous permettant d'appeler les composants de manière assynchrone depuis le côté client JavaScript sans avoir besoin d'une couche d'action intermédiaire. Vous pouvez même sousrire à des sujets JMS côté serveur et recevoir les messages via un push AJAX."
 
 #. Tag: para
 #: Preface.xml:92
 #, no-c-format
-msgid ""
-"Neither of these approaches would work well, were it not for Seam's built-in "
-"concurrency and state management, which ensures that many concurrent fine-"
-"grained, asynchronous AJAX requests are handled safely and efficiently on "
-"the server side."
-msgstr ""
+msgid "Neither of these approaches would work well, were it not for Seam's built-in concurrency and state management, which ensures that many concurrent fine-grained, asynchronous AJAX requests are handled safely and efficiently on the server side."
+msgstr "Aucune de ces approches ne fonctionnerai bien si il n'y a pas la concurence livrée par Seam et un gestionnaire d'état qui assure que toute les requêtes concurentes assynchrones et à fines granularités  ne sont pas gérées de amnière sure et éfficace du côté serveur."
 
 #. Tag: emphasis
 #: Preface.xml:101
 #, no-c-format
 msgid "Business process as a first class construct"
-msgstr ""
+msgstr "Processus métier intégré comme un premier constructeur de classe"
 
 #. Tag: para
 #: Preface.xml:103
 #, no-c-format
-msgid ""
-"Optionally, Seam provides transparent business process management via jBPM. "
-"You won't believe how easy it is to implement complex workflows, "
-"collaboration and and task management using jBPM and Seam."
-msgstr ""
+msgid "Optionally, Seam provides transparent business process management via jBPM. You won't believe how easy it is to implement complex workflows, collaboration and and task management using jBPM and Seam."
+msgstr "Optionnellement, Seam intègre la gestion des processus métier de façon transparent via jBPM. Vous n’allez pas y croire qu' il est vraiment facile d’implémenter des enchaînements de taches complexes en utilisant jBPM et Seam. "
 
 #. Tag: para
 #: Preface.xml:108
 #, no-c-format
-msgid ""
-"Seam even allows you to define presentation tier pageflow using the same "
-"language (jPDL) that jBPM uses for business process definition."
-msgstr ""
+msgid "Seam even allows you to define presentation tier pageflow using the same language (jPDL) that jBPM uses for business process definition."
+msgstr "Seam permet même de définir des enchainements de pages tierces de présentation en utilisant le même langage (jPDL) que jBPM utilise pour la définition de processus métier."
 
 #. Tag: para
 #: Preface.xml:112
 #, no-c-format
-msgid ""
-"JSF provides an incredibly rich event model for the presentation tier. Seam "
-"enhances this model by exposing jBPM's business process related events via "
-"exactly the same event handling mechanism, providing a uniform event model "
-"for Seam's uniform component model."
-msgstr ""
+msgid "JSF provides an incredibly rich event model for the presentation tier. Seam enhances this model by exposing jBPM's business process related events via exactly the same event handling mechanism, providing a uniform event model for Seam's uniform component model."
+msgstr "JSF fourni un modèle incroyablement riche d’évènement pour la couche présentation tierce. Seam améliore ce modèle en exposant les processus métier jBPM liant les évènement par un mécanisme de gestion de ces même évènements, fournissant un modèle d'évènement uniforme pour le modèle uniforme de composant de Seam."
 
 #. Tag: emphasis
 #: Preface.xml:121
 #, no-c-format
 msgid "Declarative state management"
-msgstr ""
+msgstr "Gestionnaire d'état déclaratif"
 
 #. Tag: para
 #: Preface.xml:123
 #, no-c-format
-msgid ""
-"We're all used to the concept of declarative transaction management and "
-"declarative security from the early days of EJB. EJB 3.0 even introduces "
-"declarative persistence context management. These are three examples of a "
-"broader problem of managing state that is associated with a particular "
-"<emphasis>context</emphasis>, while ensuring that all needed cleanup occurs "
-"when the context ends. Seam takes the concept of declarative state "
-"management much further and applies it to <emphasis>application state</"
-"emphasis>. Traditionally, J2EE applications implement state management "
-"manually, by getting and setting servlet session and request attributes. "
-"This approach to state management is the source of many bugs and memory "
-"leaks when applications fail to clean up session attributes, or when session "
-"data associated with different workflows collides in a multi-window "
-"application. Seam has the potential to almost entirely eliminate this class "
-"of bugs."
-msgstr ""
+msgid "We're all used to the concept of declarative transaction management and declarative security from the early days of EJB. EJB 3.0 even introduces declarative persistence context management. These are three examples of a broader problem of managing state that is associated with a particular <emphasis>context</emphasis>, while ensuring that all needed cleanup occurs when the context ends. Seam takes the concept of declarative state management much further and applies it to <emphasis>application state</emphasis>. Traditionally, J2EE applications implement state management manually, by getting and setting servlet session and request attributes. This approach to state management is the source of many bugs and memory leaks when applications fail to clean up session attributes, or when session data associated with different workflows collides in a multi-window application. Seam has the potential to almost entirely eliminate this class of bugs."
+msgstr "Nous somme habitué au concept de gestionnaire de transaction déclaratif et à la sécurité déclarative depuis les tout premier jours des EJB. EJB 3.0 introduit même un gestionnaire de persistance contextuelle déclarative. Ceci sont les trois exemples du grand problème du gestionnaire d’état qui est associé avec un <emphasis>contexte </emphasis> particulie, tout tant s’assurant que tout les besoins en nettoyage interviennent quand le contexte s’arrête. Seam rends le concept de gestionnaire d’état déclaratif bien meilleur et l’applique à <emphasis>l’état applicatif</emphasis>. Traditionnellement, les applications J2EE doivent presque toujours implémenter manuellement un gestionnaire d’état, en affectant et en récupérant les attributs de requête et de session de servlet. Cette approche du gestionnaire d’état est la source de nombreux bugs et de fuite de mémoire quand les applications n’arrivent pas à nettoyer les attributs de la !
 session, ou quand les données de session associées avec différentes enchaînements de tâches cohabitent dans une application multi fenêtrée. Seam dispose du potentiel pour éliminer presque complètement ce genre de bugs. "
 
 #. Tag: para
 #: Preface.xml:136
 #, no-c-format
-msgid ""
-"Declarative application state management is made possible by the richness of "
-"the <emphasis>context model</emphasis> defined by Seam. Seam extends the "
-"context model defined by the servlet spec &#8212; request, session, "
-"application &#8212; with two new contexts &#8212; conversation and business "
-"process &#8212; that are more meaningful from the point of view of the "
-"business logic."
-msgstr ""
+msgid "Declarative application state management is made possible by the richness of the <emphasis>context model</emphasis> defined by Seam. Seam extends the context model defined by the servlet spec &#8212; request, session, application &#8212; with two new contexts &#8212; conversation and business process &#8212; that are more meaningful from the point of view of the business logic."
+msgstr "Une application gestionnaire d’état déclaratif est devenue possible par la richesse du <emphasis>modèle contextuel</emphasis> définis par Seam. Seam étends le modèle de contexte définie par les spécifications servlet c &#8212;  request, session, application c &#8212;  avec deux nouveaux contextes : conversation et processus métier c &#8212;  ces derniers prennent tous leur sens du points de vue de la logique métier. "
 
 #. Tag: para
 #: Preface.xml:143
 #, no-c-format
-msgid ""
-"You'll be amazed at how many things become easier once you start using "
-"conversations. Have you ever suffered pain dealing with lazy association "
-"fetching in an ORM solution like Hibernate or JPA? Seam's conversation-"
-"scoped persistence contexts mean you'll rarely have to see a "
-"<literal>LazyInitializationException</literal>. Have you ever had problems "
-"with the refresh button? The back button? With duplicate form submission? "
-"With propagating messages across a post-then-redirect? Seam's conversation "
-"management solves these problems without you even needing to really think "
-"about them. They're all symptoms of the broken state management architecture "
-"that has been prevalent since the earliest days of the web."
-msgstr ""
+msgid "You'll be amazed at how many things become easier once you start using conversations. Have you ever suffered pain dealing with lazy association fetching in an ORM solution like Hibernate or JPA? Seam's conversation-scoped persistence contexts mean you'll rarely have to see a <literal>LazyInitializationException</literal>. Have you ever had problems with the refresh button? The back button? With duplicate form submission? With propagating messages across a post-then-redirect? Seam's conversation management solves these problems without you even needing to really think about them. They're all symptoms of the broken state management architecture that has been prevalent since the earliest days of the web."
+msgstr "Vous allez être impréssionné comment les choses deviennent plus simple une fois que vous commencerez à utiliser les conversations. Avez vous déjà connu la douleur dans la gestion de correspondance d'association chargées à la demande avec une solution ORM comme Hibernate ou JPA? Les contextes de persistance d'étendue conversationnelle de Seam font que vous allez rarement voir une <literal>LazyInitializationException</literal>. Avez-vous déjà eu des problèmes avec le bouton rafraichir ? Le bouton précédent? Avec une soumission de formulaire dupliquée ? Avec des messages propagées au travers d'un post-ensuite-redirection? Le gestionnaire de conversation de Seam résoud tous ces problèmes sans que vous n'aillez besoin de réellement y penser. Ils sont tous des symptomes d'une architecture de gestions d'état morcelée qui a prévalue depuis les premiers temps du web."
 
 #. Tag: emphasis
 #: Preface.xml:158
 #, no-c-format
 msgid "Bijection"
-msgstr ""
+msgstr "La bijection"
 
 #. Tag: para
 #: Preface.xml:160
 #, no-c-format
-msgid ""
-"The notion of <emphasis>Inversion of Control</emphasis> or "
-"<emphasis>dependency injection</emphasis> exists in both JSF and EJB3, as "
-"well as in numerous so-called \"lightweight containers\". Most of these "
-"containers emphasize injection of components that implement "
-"<emphasis>stateless services</emphasis>. Even when injection of stateful "
-"components is supported (such as in JSF), it is virtually useless for "
-"handling application state because the scope of the stateful component "
-"cannot be defined with sufficient flexibility, and because components "
-"belonging to wider scopes may not be injected into components belonging to "
-"narrower scopes."
-msgstr ""
+msgid "The notion of <emphasis>Inversion of Control</emphasis> or <emphasis>dependency injection</emphasis> exists in both JSF and EJB3, as well as in numerous so-called \"lightweight containers\". Most of these containers emphasize injection of components that implement <emphasis>stateless services</emphasis>. Even when injection of stateful components is supported (such as in JSF), it is virtually useless for handling application state because the scope of the stateful component cannot be defined with sufficient flexibility, and because components belonging to wider scopes may not be injected into components belonging to narrower scopes."
+msgstr "  La notion d'<emphasis>Inversion de contrôle</emphasis> ou <emphasis>d’injection dépendante</emphasis> existe à la fois dans JSF et dans EJB3, tout autant que \"les containeurs légers\" aux multiples dénominations. La plus part de ces containers parlent d’injection de composants en implémentant <emphasis>des services sans état</emphasis>. Même quand l’injection de composants avec état est disponible (comme dans JSF), il est virtuellement inutile pour la gestion de l’état de l’application car la durée de vie du composants avec état ne peut être définie avec suffisamment de flexibilité et parce que l'appartenance des composants à une étendue plus grande ne peuvent pas être injecté dans des composants appartenant à des étendues plus réduites."
 
 #. Tag: para
 #: Preface.xml:169
 #, no-c-format
-msgid ""
-"<emphasis>Bijection</emphasis> differs from IoC in that it is "
-"<emphasis>dynamic</emphasis>, <emphasis>contextual</emphasis>, and "
-"<emphasis>bidirectional</emphasis>. You can think of it as a mechanism for "
-"aliasing contextual variables (names in the various contexts bound to the "
-"current thread) to attributes of the component. Bijection allows auto-"
-"assembly of stateful components by the container. It even allows a component "
-"to safely and easily manipulate the value of a context variable, just by "
-"assigning it to an attribute of the component."
-msgstr ""
+msgid "<emphasis>Bijection</emphasis> differs from IoC in that it is <emphasis>dynamic</emphasis>, <emphasis>contextual</emphasis>, and <emphasis>bidirectional</emphasis>. You can think of it as a mechanism for aliasing contextual variables (names in the various contexts bound to the current thread) to attributes of the component. Bijection allows auto-assembly of stateful components by the container. It even allows a component to safely and easily manipulate the value of a context variable, just by assigning it to an attribute of the component."
+msgstr "La <emphasis>Bijection</emphasis>diffère de l’inversion de contrôle (IoC) dans le fait qu’il est <emphasis>dynamique</emphasis>, <emphasis>contextuel</emphasis> et <emphasis>bidirectionnel</emphasis>. Vous pouvez penser à ce mécanisme comme des variables de contextes avec alias (les noms dans les différents contextes correspondant au thread courrant) pour des attributs de composants. La bijection autorise un assemblage automatisé de composants avec état par le containeur. Il autorise le composant de manière sécurisante et facile de manipuler les valeurs des variables de contexte, juste par assignation d’un attribut d’un composant. "
 
 #. Tag: emphasis
 #: Preface.xml:181
 #, no-c-format
 msgid "Workspace management and multi-window browsing"
-msgstr ""
+msgstr "Gestionnaire d'espace de travail et navigation multi-fenétrée"
 
 #. Tag: para
 #: Preface.xml:183
 #, no-c-format
-msgid ""
-"Seam applications let the user freely switch between multiple browser tabs, "
-"each associated with a different, safely isolated, conversation. "
-"Applications may even take advantage of <emphasis>workspace management</"
-"emphasis>, allowing the user to switch between conversations (workspaces) in "
-"a single browser tab. Seam provides not only correct multi-window operation, "
-"but also multi-window-like operation in a single window!"
-msgstr ""
+msgid "Seam applications let the user freely switch between multiple browser tabs, each associated with a different, safely isolated, conversation. Applications may even take advantage of <emphasis>workspace management</emphasis>, allowing the user to switch between conversations (workspaces) in a single browser tab. Seam provides not only correct multi-window operation, but also multi-window-like operation in a single window!"
+msgstr "Les applications de Seam permettent à l'utilisateur de librement basculer entre les multiples onglets du navigateur, chacun associé avec une conversation différentes, isolé de manière sécurisée. Les applications peuvent même profiter du <emphasis>gestionnaire d'espace de travail</emphasis> autorisant l'utilisateur à basculer entre des conversations (les espaces de travail) dans un seul onglet du navigateur. Seam ne fournit pas seulement des opération correcte multi-fenétrée mais aussi des opération simulant le multi-fenetré dans une seule fenètre!"
 
 #. Tag: emphasis
 #: Preface.xml:194
 #, no-c-format
 msgid "Prefer annotations to XML"
-msgstr ""
+msgstr "Préfère les annotations au XML"
 
 #. Tag: para
 #: Preface.xml:196
 #, no-c-format
-msgid ""
-"Traditionally, the Java community has been in a state of deep confusion "
-"about precisely what kinds of meta-information counts as configuration. J2EE "
-"and popular \"lightweight\" containers have provided XML-based deployment "
-"descriptors both for things which are truly configurable between different "
-"deployments of the system, and for any other kinds or declaration which can "
-"not easily be expressed in Java. Java 5 annotations changed all this."
-msgstr ""
+msgid "Traditionally, the Java community has been in a state of deep confusion about precisely what kinds of meta-information counts as configuration. J2EE and popular \"lightweight\" containers have provided XML-based deployment descriptors both for things which are truly configurable between different deployments of the system, and for any other kinds or declaration which can not easily be expressed in Java. Java 5 annotations changed all this."
+msgstr "Traditionnellement, la communauté Java a été dans un état de grande confusion à propos de ce qui précisément compte comme méta-information dans une configuration. J2EE et les containeurs \"légers\" ont fourni des descripteurs de déploiement basé sur XML à la fois pour les choses qui sont clairement configurable entre les différents déploiement du système et pour tout autre chose comme déclaration qui ne peut pas être facilement exprimé en Java. Les annotations de Java 5 ont changé tout cela."
 
 #. Tag: para
 #: Preface.xml:204
 #, no-c-format
-msgid ""
-"EJB 3.0 embraces annotations and \"configuration by exception\" as the "
-"easiest way to provide information to the container in a declarative form. "
-"Unfortunately, JSF is still heavily dependent on verbose XML configuration "
-"files. Seam extends the annotations provided by EJB 3.0 with a set of "
-"annotations for declarative state management and declarative context "
-"demarcation. This lets you eliminate the noisy JSF managed bean declarations "
-"and reduce the required XML to just that information which truly belongs in "
-"XML (the JSF navigation rules)."
-msgstr ""
+msgid "EJB 3.0 embraces annotations and \"configuration by exception\" as the easiest way to provide information to the container in a declarative form. Unfortunately, JSF is still heavily dependent on verbose XML configuration files. Seam extends the annotations provided by EJB 3.0 with a set of annotations for declarative state management and declarative context demarcation. This lets you eliminate the noisy JSF managed bean declarations and reduce the required XML to just that information which truly belongs in XML (the JSF navigation rules)."
+msgstr "EJB 3.0 utilise les annotations et la \"configuration par exception\" est la façon la plus facile de fournir de l'informations au containeur dans une forme déclarative. Malheureusement, JSF est encore lourdement dépendant de fichiers de configuration XML verbeux. Seam étend les annotations fournies par EJB3.0 avec un groupe de d'annotations pour le gestionnaire d'état déclaratif et une démarcation du contexte déclarative. Ceci vous permet d'éliminer les complexes déclaration de gestion des beans de JSF et de reduire le XML nécéssaire à ce qui est du ressort réellement du XML (les règles de navigation de JSF)."
 
 #. Tag: emphasis
 #: Preface.xml:217
 #, no-c-format
 msgid "Integration testing is easy"
-msgstr ""
+msgstr "L'intégration des tests est facile"
 
 #. Tag: para
 #: Preface.xml:219
 #, no-c-format
-msgid ""
-"Seam components, being plain Java classes, are by nature unit testable. But "
-"for complex applications, unit testing alone is insufficient. Integration "
-"testing has traditionally been a messy and difficult task for Java web "
-"applications. Therefore, Seam provides for testability of Seam applications "
-"as a core feature of the framework. You can easily write JUnit or TestNG "
-"tests that reproduce a whole interaction with a user, exercising all "
-"components of the system apart from the view (the JSP or Facelets page). You "
-"can run these tests directly inside your IDE, where Seam will automatically "
-"deploy EJB components using JBoss Embedded."
-msgstr ""
+msgid "Seam components, being plain Java classes, are by nature unit testable. But for complex applications, unit testing alone is insufficient. Integration testing has traditionally been a messy and difficult task for Java web applications. Therefore, Seam provides for testability of Seam applications as a core feature of the framework. You can easily write JUnit or TestNG tests that reproduce a whole interaction with a user, exercising all components of the system apart from the view (the JSP or Facelets page). You can run these tests directly inside your IDE, where Seam will automatically deploy EJB components using JBoss Embedded."
+msgstr "Les composants Seam, en étant de pures classes Java, sont par nature testable unitairement. Mais pour des applications complexes, le fait de tester unitairement n’est pas suffisant. Tester unitairement est traditionnellement une tâche fatigante et complexe pour les applications web Java. Cependant, Seam fourni pour le test des applications Seam un fonctionnalité au coeur du serveur d'applidcation Vous pouvez facilement écrire des tests JUnit ou TestNG pour reproduire une parfaite interaction avec un utilisateur, sollicitant tous les composants du système indépendamment de vues (la page JSP ou Facelets). Vous pouvez exécuter ces tests directement depuis votre IDE, là où Seam va automatiquement déployer les composants EJB en utilisant Jboss Embeddable. "
 
 #. Tag: emphasis
 #: Preface.xml:232
 #, no-c-format
 msgid "The specs ain't perfect"
-msgstr ""
+msgstr "La spécification n'est pas perfaite"
 
 #. Tag: para
 #: Preface.xml:234
 #, no-c-format
-msgid ""
-"We think the latest incarnation of Java EE is great. But we know it's never "
-"going to be perfect. Where there are holes in the specifications (for "
-"example, limitations in the JSF lifecycle for GET requests), Seam fixes "
-"them. And the authors of Seam are working with the JCP expert groups to make "
-"sure those fixes make their way back into the next revision of the standards."
-msgstr ""
+msgid "We think the latest incarnation of Java EE is great. But we know it's never going to be perfect. Where there are holes in the specifications (for example, limitations in the JSF lifecycle for GET requests), Seam fixes them. And the authors of Seam are working with the JCP expert groups to make sure those fixes make their way back into the next revision of the standards."
+msgstr "Vous pensez que la dernière incarnation de Java EE est géniale. Mais nous savons qu'elle n'est pas parfaite. Là où il y a des trous dans la spécification (par exemple les limitations dans le cycle de vie de JSF pour les requêtes GET), Seam les règles lui-même. Et les auteurs de Seam travaille avec le groupe d'experts JCP pour faire en sorte que ces corrections seront conservé dans les prochaines révisions des standards."
 
 #. Tag: emphasis
 #: Preface.xml:245
 #, no-c-format
 msgid "There's more to a web application than serving HTML pages"
-msgstr ""
+msgstr "Il y a bien plus pour une application web que de confectionner des pages HTML"
 
 #. Tag: para
 #: Preface.xml:247
 #, no-c-format
-msgid ""
-"Today's web frameworks think too small. They let you get user input off a "
-"form and into your Java objects. And then they leave you hanging. A truly "
-"complete web application framework should address problems like persistence, "
-"concurrency, asynchronicity, state management, security, email, messaging, "
-"PDF and chart generation, workflow, wikitext rendering, webservices, caching "
-"and more. Once you scratch the surface of Seam, you'll be amazed at how many "
-"problems become simpler..."
-msgstr ""
+msgid "Today's web frameworks think too small. They let you get user input off a form and into your Java objects. And then they leave you hanging. A truly complete web application framework should address problems like persistence, concurrency, asynchronicity, state management, security, email, messaging, PDF and chart generation, workflow, wikitext rendering, webservices, caching and more. Once you scratch the surface of Seam, you'll be amazed at how many problems become simpler..."
+msgstr "Aujourd'huis les serveurs d'applications pensent trop petit. Ils vous permettent d'obtenir les entrées d'un formulaire utilisateur dans vos objets Java. Et ensuite ils vous laissent vous débrouiller. Un serveur d'application web vraiment complet devrait régler les problèmes comme la persistance, la concurence, l'assynchronisme, la gestion d'état, la sécurité, l'email, les messages, le PDF, la génération de diagrame, l'enchainement de tâche, le rendu du formatage wiki, les services web, la mise en cache et bien plus encore. Une fois que vous aurez plogeés sous la surface de Seam, vous allez être impréssionné par comment les problèmes deviennent plus simple...."
 
 #. Tag: para
 #: Preface.xml:255
 #, no-c-format
-msgid ""
-"Seam integrates JPA and Hibernate3 for persistence, the EJB Timer Service "
-"and Quartz for lightweight asychronicity, jBPM for workflow, JBoss Rules for "
-"business rules, Meldware Mail for email, Hibernate Search and Lucene for "
-"full text search, JMS for messaging and JBoss Cache for page fragment "
-"caching. Seam layers an innovative rule-based security framework over JAAS "
-"and JBoss Rules. There's even JSF tag libraries for rendering PDF, outgoing "
-"email, charts and wikitext. Seam components may be called synchronously as a "
-"Web Service, asynchronously from client-side JavaScript or Google Web "
-"Toolkit or, of course, directly from JSF."
-msgstr ""
+msgid "Seam integrates JPA and Hibernate3 for persistence, the EJB Timer Service and Quartz for lightweight asychronicity, jBPM for workflow, JBoss Rules for business rules, Meldware Mail for email, Hibernate Search and Lucene for full text search, JMS for messaging and JBoss Cache for page fragment caching. Seam layers an innovative rule-based security framework over JAAS and JBoss Rules. There's even JSF tag libraries for rendering PDF, outgoing email, charts and wikitext. Seam components may be called synchronously as a Web Service, asynchronously from client-side JavaScript or Google Web Toolkit or, of course, directly from JSF."
+msgstr "Seam intègre JPA et Hibernate3 pour la persistance, le EJB Timer Service et Quartz pour l'assynchronisme version allégée, jBPM pour l'enchainement de tâches, JBoss Rules pour les règles métiers, Meldware Mail pour les emails, Hibernate Search et Lucene pour la recherche plein texte, JMS pour les messages et JBoss Cache pour la mise en cache de fragments. Les couches de Seam son un serveur d'application de sécurité innovant basés sur des règles au desus de JAAS et de JBoss Rules. Il ya aussi des bibliothèques de tag JSF pour le rendu de PDF, l'envoie des emails, les diagrammes et le texte wiki. Les composants de Seam peuvent même être appelés de mmanière synchrones comme des services web, asynchronisme depuis le JavaScript côté client ou avec Google Web Toolkit ou bien sur directement depuis JSF."
 
 #. Tag: emphasis
 #: Preface.xml:268
 #, no-c-format
 msgid "Get started now!"
-msgstr ""
+msgstr "Prêt au départ maintenant!"
 
 #. Tag: para
 #: Preface.xml:270
 #, no-c-format
-msgid ""
-"Seam works in any Java EE application server, and even works in Tomcat. If "
-"your environment supports EJB 3.0, great! If it doesn't, no problem, you can "
-"use Seam's built-in transaction management with JPA or Hibernate3 for "
-"persistence. Or, you can deploy JBoss Embedded in Tomcat, and get full "
-"support for EJB 3.0."
-msgstr ""
+msgid "Seam works in any Java EE application server, and even works in Tomcat. If your environment supports EJB 3.0, great! If it doesn't, no problem, you can use Seam's built-in transaction management with JPA or Hibernate3 for persistence. Or, you can deploy JBoss Embedded in Tomcat, and get full support for EJB 3.0."
+msgstr "Seam fonctionne dans n’importe quel serveur d’application Java EE et fonctionne même dans Tomcat. Si votre environement supporte EJB3.0, génial!Si cen'est pas le cas, pas de problème, vous pouvez utiliser le gestionnaire de transaction livré dans Seam avec JPA ou Hibernate3 pour la persistance. Ou, vous pouvez deployer JBoss Embedded dans Tomcat, et avoir le support plein et entier d'EJB 3.0."
 
 #. Tag: para
 #: Preface.xml:286
 #, no-c-format
-msgid ""
-"It turns out that the combination of Seam, JSF and EJB3 is <emphasis>the</"
-"emphasis> simplest way to write a complex web application in Java. You won't "
-"believe how little code is required!"
-msgstr ""
+msgid "It turns out that the combination of Seam, JSF and EJB3 is <emphasis>the</emphasis> simplest way to write a complex web application in Java. You won't believe how little code is required!"
+msgstr "Il est clair que la combinaison de Seam, JSF et EJB3 est <emphasis>la</emphasis> façon la plus simple d'écrire une application web complexe en Java. Vous ne réalisez pas le peut de code qu'il nécéssite!"
+