[portal-commits] JBoss Portal SVN: r13759 - in docs/enterprise/trunk/Reference_Guide: ja-JP and 1 other directories.

Author: mospina Date: 2009-08-13 20:54:27 -0400 (Thu, 13 Aug 2009) New Revision: 13759 Added: docs/enterprise/trunk/Reference_Guide/ja-JP/ docs/enterprise/trunk/Reference_Guide/ja-JP/Ajax.po docs/enterprise/trunk/Reference_Guide/ja-JP/Authentication.po docs/enterprise/trunk/Reference_Guide/ja-JP/Author_Group.po docs/enterprise/trunk/Reference_Guide/ja-JP/Book_Info.po docs/enterprise/trunk/Reference_Guide/ja-JP/CMS_Portlet.po docs/enterprise/trunk/Reference_Guide/ja-JP/Clustering.po docs/enterprise/trunk/Reference_Guide/ja-JP/Common_Content/ docs/enterprise/trunk/Reference_Guide/ja-JP/Common_Content/Feedback.po docs/enterprise/trunk/Reference_Guide/ja-JP/Common_Content/Legal_Notice.po docs/enterprise/trunk/Reference_Guide/ja-JP/Common_Content/css/ docs/enterprise/trunk/Reference_Guide/ja-JP/Configuration.po docs/enterprise/trunk/Reference_Guide/ja-JP/Content_Integration.po docs/enterprise/trunk/Reference_Guide/ja-JP/Coordination.po docs/enterprise/trunk/Reference_Guide/ja-JP/Error_Handling.po docs/enterprise/trunk/Reference_Guide/ja-JP/Feedback.po docs/enterprise/trunk/Reference_Guide/ja-JP/Identity.po docs/enterprise/trunk/Reference_Guide/ja-JP/Identity_Portlets.po docs/enterprise/trunk/Reference_Guide/ja-JP/Installation.po docs/enterprise/trunk/Reference_Guide/ja-JP/Jboss_Portlet_DTD.po docs/enterprise/trunk/Reference_Guide/ja-JP/Ldap.po docs/enterprise/trunk/Reference_Guide/ja-JP/Migration.po docs/enterprise/trunk/Reference_Guide/ja-JP/Nav_Tabs.po docs/enterprise/trunk/Reference_Guide/ja-JP/Portal_API.po docs/enterprise/trunk/Reference_Guide/ja-JP/Portal_Objects_DTD.po docs/enterprise/trunk/Reference_Guide/ja-JP/Portlet_Instances_DTD.po docs/enterprise/trunk/Reference_Guide/ja-JP/Portlet_Modes.po docs/enterprise/trunk/Reference_Guide/ja-JP/Preface.po docs/enterprise/trunk/Reference_Guide/ja-JP/Reference_Guide.po docs/enterprise/trunk/Reference_Guide/ja-JP/Revision_History.po docs/enterprise/trunk/Reference_Guide/ja-JP/SSO.po docs/enterprise/trunk/Reference_Guide/ja-JP/Security.po docs/enterprise/trunk/Reference_Guide/ja-JP/Supported.po docs/enterprise/trunk/Reference_Guide/ja-JP/Target.po docs/enterprise/trunk/Reference_Guide/ja-JP/Theme_And_Layouts.po docs/enterprise/trunk/Reference_Guide/ja-JP/Trademarks.po docs/enterprise/trunk/Reference_Guide/ja-JP/Troubleshooting.po docs/enterprise/trunk/Reference_Guide/ja-JP/Tutorials.po docs/enterprise/trunk/Reference_Guide/ja-JP/URLs.po docs/enterprise/trunk/Reference_Guide/ja-JP/WSRP.po docs/enterprise/trunk/Reference_Guide/ja-JP/Widget_Integration.po docs/enterprise/trunk/Reference_Guide/ja-JP/Workflow.po docs/enterprise/trunk/Reference_Guide/ja-JP/XML_Descriptors.po docs/enterprise/trunk/Reference_Guide/ja-JP/extras/ docs/enterprise/trunk/Reference_Guide/ja-JP/src/ Modified: docs/enterprise/trunk/Reference_Guide/Makefile Log: Adding PO files for Japanese Modified: docs/enterprise/trunk/Reference_Guide/Makefile =================================================================== --- docs/enterprise/trunk/Reference_Guide/Makefile 2009-08-14 00:51:13 UTC (rev 13758) +++ docs/enterprise/trunk/Reference_Guide/Makefile 2009-08-14 00:54:27 UTC (rev 13759) @@ -7,6 +7,7 @@ #OTHER_LANGS = as-IN bn-IN de-DE es-ES fr-FR gu-IN hi-IN it-IT ja-JP kn-IN ko-KR ml-IN mr-IN or-IN pa-IN pt-BR ru-RU si-LK ta-IN te-IN zh-CN zh-TW +OTHER_LANGS = ja-JP TRANSLATIONS = $(XML_LANG) $(OTHER_LANGS) COMMON_CONFIG = /usr/share/publican Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Ajax.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Ajax.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Ajax.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,524 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Ajax.xml:11 +#, no-c-format +msgid "Ajax" +msgstr "" + +#. Tag: para +#: Ajax.xml:12 +#, no-c-format +msgid "This section covers the ajax features provided by the portal." +msgstr "" + +#. Tag: title +#: Ajax.xml:14 +#, no-c-format +msgid "Introduction" +msgstr "" + +#. Tag: para +#: Ajax.xml:15 +#, no-c-format +msgid "Todo" +msgstr "" + +#. Tag: title +#: Ajax.xml:18 +#, no-c-format +msgid "Ajaxified markup" +msgstr "" + +#. Tag: title +#: Ajax.xml:20 +#, no-c-format +msgid "Ajaxified layouts" +msgstr "" + +#. Tag: para +#: Ajax.xml:21 +#, no-c-format +msgid "" +"Part of the Ajax capabilities are implemented in the layout framework which " +"provide the structure for generating portal pages. The good news is that the " +"existing layout only requires a few modifications in order to be ajaxified." +msgstr "" + +#. Tag: para +#: Ajax.xml:24 +#, no-c-format +msgid "" +"We will use as example an simplified version of the layout JSP provided in " +"JBoss Portal 2.6 and outline what are the required changes that makes it an " +"ajaxified layout:" +msgstr "" + +#. Tag: programlisting +#: Ajax.xml:26 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<%@ taglib uri=\"/WEB-INF/theme/portal-layout.tld\" prefix=\"p\" %>\n" +"<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n" +"\"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\">\n" +"<html xmlns=\"http://www.w3.org/1999/xhtml\">\n" +"<head>\n" +" <meta http-equiv=\"Content-Type\" content=\"text/html;\"/>\n" +" <!-- inject the theme, default to the Renaissance theme if\n" +" nothing is selected for the portal or the page -->\n" +" <p:theme themeName=\"renaissance\"/>\n" +" <!-- insert header content that was possibly set by portlets on the page " +"-->\n" +" <p:headerContent/>\n" +"</head>\n" +"\n" +"<body id=\"body\">\n" +"<p:region regionName='AJAXScripts' regionID='AJAXScripts'/>\n" +"<div id=\"portal-container\">\n" +" <div id=\"sizer\">\n" +" <div id=\"expander\">\n" +" <div id=\"logoName\"></div>\n" +" <table border=\"0\" cellpadding=\"0\" cellspacing=\"0\" id=\"header-" +"container\">\n" +" <tr>\n" +" <td align=\"center\" valign=\"top\" id=\"header\">\n" +"\n" +" <!-- Utility controls -->\n" +" <p:region regionName='dashboardnav' " +"regionID='dashboardnav'/>\n" +"\n" +" <!-- navigation tabs and such -->\n" +" <p:region regionName='navigation' regionID='navigation'/>\n" +" <div id=\"spacer\"></div>\n" +" </td>\n" +" </tr>\n" +" </table>\n" +" <div id=\"content-container\">\n" +" <!-- insert the content of the 'left' region of the page,\n" +" and assign the css selector id 'regionA' -->\n" +" <p:region regionName='left' regionID='regionA'/>\n" +" <!-- insert the content of the 'center' region of the page,\n" +" and assign the css selector id 'regionB' -->\n" +" <p:region regionName='center' regionID='regionB'/>\n" +" <hr class=\"cleaner\"/>\n" +" </div>\n" +" </div>\n" +" </div>\n" +"</div>\n" +"\n" +"<p:region regionName='AJAXFooter' regionID='AJAXFooter'/>\n" +"\n" +"</body>\n" +"</html>\n" +"]]>" +msgstr "" + +#. Tag: para +#: Ajax.xml:28 +#, no-c-format +msgid "" +"<![CDATA[<p:theme themeName=\"renaissance\"/>]]> should be already present " +"as it exists since 2.4 but is even more necessary as it will inject in the " +"page the reference to the ajax stylesheet." +msgstr "" + +#. Tag: para +#: Ajax.xml:30 +#, no-c-format +msgid "" +"<![CDATA[<p:region regionName='AJAXScripts' regionID='AJAXScripts'/>]]> " +"should be added before any other region in the markup of the layout." +msgstr "" + +#. Tag: para +#: Ajax.xml:32 +#, no-c-format +msgid "" +"<![CDATA[<p:region regionName='AJAXFooter' regionID='AJAXFooter'/>]]> should " +"be added after any other region in the markup of the layout." +msgstr "" + +#. Tag: title +#: Ajax.xml:38 +#, no-c-format +msgid "Ajaxified renderers" +msgstr "" + +#. Tag: para +#: Ajax.xml:39 +#, no-c-format +msgid "" +"At runtime the portal combines the layout and the renderers in order create " +"the markup returned to the web browser. The most used render set is the " +"divRenderer. Renderers only need a modification in the deployment descriptor " +"to indicate that they support ajax. Here is the declaration of the default " +"divRenderer now in 2.6:" +msgstr "" + +#. Tag: programlisting +#: Ajax.xml:42 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<renderSet name=\"divRenderer\">\n" +" <set content-type=\"text/html\">\n" +" <ajax-enabled>true</ajax-enabled>\n" +" <region-renderer>org.jboss.portal.theme.impl.render.div." +"DivRegionRenderer\n" +" </region-renderer>\n" +" <window-renderer>org.jboss.portal.theme.impl.render.div." +"DivWindowRenderer\n" +" </window-renderer>\n" +" <portlet-renderer>org.jboss.portal.theme.impl.render.div." +"DivPortletRenderer\n" +" </portlet-renderer>\n" +" <decoration-renderer>org.jboss.portal.theme.impl.render.div." +"DivDecorationRenderer\n" +" </decoration-renderer>\n" +" </set>\n" +"</renderSet>\n" +"]]>" +msgstr "" + +#. Tag: para +#: Ajax.xml:43 +#, no-c-format +msgid "" +"You should notice the <![CDATA[<ajax-enabled>true</ajax-enabled>]]> which " +"indicates that the render set supports ajaxification." +msgstr "" + +#. Tag: title +#: Ajax.xml:48 +#, no-c-format +msgid "Ajaxified pages" +msgstr "" + +#. Tag: para +#: Ajax.xml:49 +#, no-c-format +msgid "" +"The ajaxification of the portal pages can be configured in a fine grained " +"manner. Thanks to the portal object properties it is possible to control " +"which pages support ajax and which page do not support ajax. The " +"administrator must pay attention to the fact that property values are " +"inherited in the object hierarchy." +msgstr "" + +#. Tag: title +#: Ajax.xml:53 +#, no-c-format +msgid "Drag and Drop" +msgstr "" + +#. Tag: para +#: Ajax.xml:54 +#, no-c-format +msgid "" +"That feature is only effective in dashboards as it requires the offer " +"personalization of the page layout per user. By default the feature is " +"enabled thanks to a property set on the dashboard object. It is possible to " +"turn off that property if the administrator does not want to expose that " +"feature to its user." +msgstr "" + +#. Tag: para +#: Ajax.xml:58 +#, no-c-format +msgid "" +"In the file <emphasis>jboss-portal.sar/conf/data/default-object.xml</" +"emphasis> is declared and configured the creation of the dashboard portal:" +msgstr "" + +#. Tag: programlisting +#: Ajax.xml:60 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<deployment>\n" +" <parent-ref/>\n" +" <if-exists>keep</if-exists>\n" +" <context>\n" +" <context-name>dashboard</context-name>\n" +" <properties>\n" +" ...\n" +" <property>\n" +" <name>theme.dyna.dnd_enabled</name>\n" +" <value>true</value>\n" +" </property>\n" +" ...\n" +" </properties>\n" +" ...\n" +" </context>\n" +"</deployment>\n" +"]]>" +msgstr "" + +#. Tag: para +#: Ajax.xml:61 +#, no-c-format +msgid "" +"The property <emphasis>theme.dyna.dnd_enabled</emphasis> is set to the value " +"<emphasis>true</emphasis> which means that the dashboard object will provide " +"the drag and drop feature." +msgstr "" + +#. Tag: title +#: Ajax.xml:66 +#, no-c-format +msgid "Partial refresh" +msgstr "" + +#. Tag: para +#: Ajax.xml:67 +#, no-c-format +msgid "" +"Partial refresh is a very powerful feature which allows the portal to " +"optimize the refreshing of portlets on a page. When one portlet is invoked, " +"instead of redrawing the full page, the portal is able to detect which " +"portlets needs to be refreshed and will update only these portlets." +msgstr "" + +#. Tag: para +#: Ajax.xml:75 +#, no-c-format +msgid "The portal providing partial refresh." +msgstr "" + +#. Tag: title +#: Ajax.xml:78 +#, no-c-format +msgid "Portal objects configuration" +msgstr "" + +#. Tag: para +#: Ajax.xml:79 +#, no-c-format +msgid "" +"Like with the drag and drop feature, partial page refresh is controlled via " +"properties on portal objects. The name of the property is <emphasis>theme." +"dyna.partial_refresh_enabled</emphasis> and its values can be " +"<emphasis>true</emphasis> or <emphasis>false</emphasis>. When this property " +"is set on an object it is automatically inherited by the sub hierarchy " +"located under that object. By default the drag and drop feature is " +"positioned on the dashboard object and not on the rest of the portal objects." +msgstr "" + +#. Tag: programlisting +#: Ajax.xml:85 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<deployment>\n" +" <parent-ref/>\n" +" <if-exists>keep</if-exists>\n" +" <context>\n" +" <context-name>dashboard</context-name>\n" +" <properties>\n" +" ...\n" +" <property>\n" +" <name>theme.dyna.partial_refresh_enabled</name>\n" +" <value>true</value>\n" +" </property>\n" +" ...\n" +" </properties>\n" +" ...\n" +" </context>\n" +"</deployment>\n" +"]]>" +msgstr "" + +#. Tag: para +#: Ajax.xml:87 +#, no-c-format +msgid "" +"The partial page refresh feature is compatible with the Portal API. The " +"Portal API allows programmatic update of the state of portlets at runtime. " +"For instance it is possible to modify the window state or the mode of " +"several portlets on a given page. When such event occurs, the portal detects " +"the changes which occurred and will update the portlet fragments in the page." +msgstr "" + +#. Tag: para +#: Ajax.xml:92 +#, no-c-format +msgid "" +"It is possible to change that behavior at runtime using the property editor " +"of the management portlet. If you want to enable partial refreshing on the " +"default portal you should set the property to true directly on the portal " +"and all the pages in that portal will automatically inherit those properties." +msgstr "" + +#. Tag: para +#: Ajax.xml:100 +#, no-c-format +msgid "The default portal configured for partial page refresh" +msgstr "" + +#. Tag: title +#: Ajax.xml:104 +#, no-c-format +msgid "Portlet configuration" +msgstr "" + +#. Tag: para +#: Ajax.xml:105 +#, no-c-format +msgid "" +"By default any portlet will support partial refreshing. When does the portal " +"performs partial page refreshing ? By default it is enabled for action and " +"render links with the following exceptions. In those situations, the portal " +"will prefer to perform a full page refresh:" +msgstr "" + +#. Tag: para +#: Ajax.xml:111 +#, no-c-format +msgid "" +"Form GET are not handled, however it should not be an issue as this " +"situation is discouraged by the Portlet specification. It however taken in " +"account, just in case of. Here is an example of a JavaServer Page that would " +"do one:" +msgstr "" + +#. Tag: programlisting +#: Ajax.xml:114 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<form action=\"<%= renderResponse.createActionURL() %>\" method=\"get\">\n" +" ...\n" +"</form>\n" +"]]>" +msgstr "" + +#. Tag: para +#: Ajax.xml:117 +#, no-c-format +msgid "Form uploads are not handled." +msgstr "" + +#. Tag: para +#: Ajax.xml:119 +#, no-c-format +msgid "" +"Having an interaction that deals with the <emphasis>MAXIMIZED</emphasis> " +"window state. When a window is entering a maximized state or leaving a " +"maximized window state, the portal will perform a full page refresh." +msgstr "" + +#. Tag: para +#: Ajax.xml:124 +#, no-c-format +msgid "" +"It can happen that a portlet does not want to support partial refreshing, in " +"those situations the <emphasis>jboss-portlet.xml</emphasis> can be used to " +"control that behavior. Since 2.6 an ajax section has been added in order to " +"configure ajax features related to the portlet." +msgstr "" + +#. Tag: programlisting +#: Ajax.xml:127 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<portlet>\n" +" <portlet-name>MyPortletNoAjax</portlet-name>\n" +" <ajax>\n" +" <partial-refresh>false</partial-refresh>\n" +" </ajax>\n" +"</portlet>\n" +"]]>" +msgstr "" + +#. Tag: para +#: Ajax.xml:128 +#, no-c-format +msgid "" +"The usage of the <emphasis>partial-refresh</emphasis> set to the value false " +"means that the portlet will not be subject of a partial page refresh when it " +"is invoked. However the portlet markup can still be subject to a partial " +"rendering." +msgstr "" + +#. Tag: title +#: Ajax.xml:133 +#, no-c-format +msgid "Limitations" +msgstr "" + +#. Tag: para +#: Ajax.xml:134 +#, no-c-format +msgid "" +"Partial refreshing of portlets has limitations both on the server side " +"(portal) and on the client side (browser)." +msgstr "" + +#. Tag: title +#: Ajax.xml:136 +#, no-c-format +msgid "Application scoped session attributes" +msgstr "" + +#. Tag: para +#: Ajax.xml:137 +#, no-c-format +msgid "" +"When partial refresh is activated, the state of a page can potentially " +"become inconsistent. for example, if some objects are shared in the " +"application scope of the session between portlets. When one portlet update a " +"session object, the other portlet won't be refreshed and will still display " +"content based on the previous value of the object in the session. To avoid " +"that, partial refresh can be deactivated for certain portlets by adding &lt;" +"portlet-refresh&gt;false&lt;portlet-refresh&gt; in the jboss-portlet.xml " +"file." +msgstr "" + +#. Tag: title +#: Ajax.xml:144 +#, no-c-format +msgid "Non ajax interactions" +msgstr "" + +#. Tag: para +#: Ajax.xml:145 +#, no-c-format +msgid "" +"The solution developed by JBoss Portal on the client side is built on top of " +"DOM events emitted by the web browser when the user interacts with the page. " +"If an interaction is done without an emission of an event then JBoss Portal " +"will not be able to transform it into a partial refresh and it will result " +"instead of a full refresh. This can happen with programmatic submission of " +"forms." +msgstr "" + +#. Tag: programlisting +#: Ajax.xml:150 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<form id=\"<%= formId %>\" action=\"<%= renderResponse.createActionURL() %>" +"\" method=\"post\">\n" +" ...\n" +" <select onclick=\"document.getElementById('<%= formId %>').submit()\">\n" +" ...\n" +" </select>\n" +" ...\n" +"</form>\n" +"]]>" +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Authentication.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Authentication.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Authentication.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,534 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Authentication.xml:11 +#, no-c-format +msgid "Authentication and Authorization" +msgstr "" + +#. Tag: para +#: Authentication.xml:12 +#, no-c-format +msgid "This chapter describes the authentication mechanisms in JBoss Portal" +msgstr "" + +#. Tag: title +#: Authentication.xml:14 +#, no-c-format +msgid "Authentication in JBoss Portal" +msgstr "" + +#. Tag: para +#: Authentication.xml:15 +#, no-c-format +msgid "" +"JBoss Portal is heavily standard based so it leverages <emphasis>Java " +"Authentication and Authorization Service (JAAS)</emphasis> in JBoss " +"Application Server. Because of this it can be configured in a very flexible " +"manner and other authentication solutions can be plugged in easily. To " +"better understand authentication mechanisms in JBoss Portal please refer to " +"<xref linkend=\"security.security_authentication\"/>. To learn more about " +"JAAS look for proper documentation on <ulink url=\"http://java.sun.com/" +"javase/6/docs/technotes/guides/security/\">Java Security</ulink> website. To " +"learn more about security in JBoss Application Server please read <ulink url=" +"\"http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossSX\">JBossSX</ulink> " +"documentation." +msgstr "" + +#. Tag: title +#: Authentication.xml:26 +#, no-c-format +msgid "Configuration" +msgstr "" + +#. Tag: para +#: Authentication.xml:27 +#, no-c-format +msgid "" +"You can configure the JAAS authentication stack in <emphasis>jboss-portal." +"sar/conf/login-config.xml</emphasis>. It is important to remember that " +"authorization in portal starts at the JAAS level - configured " +"<emphasis>LoginModule</emphasis>s apply proper <emphasis>Principal</" +"emphasis> objects representing the roles of authenticated user. As you can " +"see in <emphasis>jboss-portal.sar/portal-server.war/WEB-INF/web.xml</" +"emphasis> portal servlet is secured with specified role " +"(\"<emphasis>Authenticated</emphasis>\"). In the default portal " +"configuration this role is dynamically added by " +"<emphasis>IdentityLoginModule</emphasis>. If you reconfigure the default " +"JAAS authentication chain with other <emphasis>LoginModule</emphasis> " +"implementations, you should remember that you must deal with that security " +"constraints in order to be able to access portal. For example if you place " +"only one <emphasis>LoginModule</emphasis> that will authenticate users " +"against LDAP server you may consider adding all users in your LDAP tree to " +"such role." +msgstr "" + +#. Tag: title +#: Authentication.xml:40 +#, no-c-format +msgid "JAAS Login Modules" +msgstr "" + +#. Tag: para +#: Authentication.xml:41 +#, no-c-format +msgid "" +"JBoss Portal comes with a few implementations of JAAS <emphasis>LoginModule</" +"emphasis> interface" +msgstr "" + +#. Tag: title +#: Authentication.xml:43 +#, no-c-format +msgid "org.jboss.portal.identity.auth.IdentityLoginModule" +msgstr "" + +#. Tag: para +#: Authentication.xml:44 +#, no-c-format +msgid "" +"This is the standard portal LoginModule implementation that uses portal " +"identity modules in order to search users and roles. By default it is the " +"only configured LoginModule in the portal authentication stack. Its behavior " +"can be altered with the following options:" +msgstr "" + +#. Tag: para +#: Authentication.xml:47 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">userModuleJNDIName</emphasis> - JNDI name of portal " +"UserModule." +msgstr "" + +#. Tag: para +#: Authentication.xml:50 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">roleModuleJNDIName</emphasis> - JNDI name of portal " +"RoleModule." +msgstr "" + +#. Tag: para +#: Authentication.xml:53 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">membershipModuleJNDIName</emphasis> - JNDI name of " +"portal MembershipModule." +msgstr "" + +#. Tag: para +#: Authentication.xml:56 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">additionalRole</emphasis> - additional user " +"<emphasis>Principal</emphasis> that will be added to user <emphasis>Subject</" +"emphasis>. This is important as in default portal configuration it is the " +"role that portal servlet is secured with." +msgstr "" + +#. Tag: para +#: Authentication.xml:60 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">havingRole</emphasis> - only users belonging to role " +"specified with this option will be authenticated." +msgstr "" + +#. Tag: para +#: Authentication.xml:63 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">unauthenticatedIdentity</emphasis> - the principal " +"to use when a null username and password are seen." +msgstr "" + +#. Tag: title +#: Authentication.xml:67 Authentication.xml:110 Authentication.xml:212 +#, no-c-format +msgid "Note" +msgstr "" + +#. Tag: para +#: Authentication.xml:67 +#, no-c-format +msgid "" +"IdentityLoginModule extends org.jboss.security.auth.spi." +"UsernamePasswordLoginModule so if you are familiar with JBossSX you can " +"apply few other options like \"password-stacking\". Please refer to JBossSX " +"documentation." +msgstr "" + +#. Tag: title +#: Authentication.xml:72 +#, no-c-format +msgid "org.jboss.portal.identity.auth.DBIdentityLoginModule" +msgstr "" + +#. Tag: para +#: Authentication.xml:73 +#, no-c-format +msgid "" +"This <emphasis>LoginModule</emphasis> implementation extends JBossSX " +"<emphasis>org.jboss.security.auth.spi.DatabaseServerLoginModule</emphasis> " +"and can be used to authenticate against Database. The main purpose of this " +"module is to be configured directly against portal database (instead of " +"using portal identity modules like in IdentityLoginModule). So if you are " +"using custom LoginModule implementation you can place this module with " +"\"sufficient\" flag. This can be extremely useful. For example if you " +"authenticate against LDAP server using JBossSX <emphasis>LdapLoginModule</" +"emphasis> you can fallback to users present in portal database and not " +"present in LDAP like \"admin\" user. Please look into <ulink url=\"http://" +"wiki.jboss.org/wiki/Wiki.jsp?page=DatabaseServerLoginModule\">this</ulink> " +"wiki page to learn more about <emphasis>DatabaseServerLoginModule</emphasis> " +"configuration" +msgstr "" + +#. Tag: para +#: Authentication.xml:80 +#, no-c-format +msgid "Options are:" +msgstr "" + +#. Tag: para +#: Authentication.xml:83 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">dsJndiName</emphasis> - The name of the DataSource " +"of the database containing the Principals and Roles tables" +msgstr "" + +#. Tag: para +#: Authentication.xml:86 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">principalsQuery</emphasis> - The prepared statement " +"query, equivalent to: <emphasis>\"select Password from Principals where " +"PrincipalID=?\"</emphasis>" +msgstr "" + +#. Tag: para +#: Authentication.xml:89 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">rolesQuery</emphasis> - The prepared statement " +"query, equivalent to: <emphasis>\"select Role, RoleGroup from Roles where " +"PrincipalID=?\"</emphasis>" +msgstr "" + +#. Tag: para +#: Authentication.xml:92 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">hashAlgorithm</emphasis> - The name of the " +"<emphasis>java.security.MessageDigest</emphasis> algorithm to use to hash " +"the password. There is no default so this option must be specified to enable " +"hashing. When hashAlgorithm is specified, the clear text password obtained " +"from the <emphasis>CallbackHandler</emphasis> is hashed before it is passed " +"to UsernamePasswordLoginModule.validatePassword as the inputPassword " +"argument. The expectedPassword as stored in the users.properties file must " +"be comparably hashed." +msgstr "" + +#. Tag: para +#: Authentication.xml:98 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">hashEncoding</emphasis> - The string format for the " +"hashed pass and st be either \"base64\" or \"hex\". Base64 is the default." +msgstr "" + +#. Tag: para +#: Authentication.xml:101 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">additionalRole</emphasis> - additional user " +"<emphasis>Principal</emphasis> that will be added to user <emphasis>Subject</" +"emphasis>." +msgstr "" + +#. Tag: para +#: Authentication.xml:106 +#, no-c-format +msgid "Configuration using portal database will look like this:" +msgstr "" + +#. Tag: programlisting +#: Authentication.xml:108 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<login-module code = \"org.jboss.portal.identity.auth.DBIdentityLoginModule" +"\"\n" +" flag=\"sufficient\">\n" +" <module-option name=\"dsJndiName\">java:/PortalDS</module-option>\n" +" <module-option name=\"principalsQuery\">\n" +" SELECT jbp_password FROM jbp_users WHERE jbp_uname=?\n" +" </module-option/>\n" +" <module-option name=\"rolesQuery\">\n" +" SELECT jbp_roles.jbp_name, 'Roles' FROM jbp_role_membership INNER " +"JOIN\n" +" jbp_roles ON jbp_role_membership.jbp_rid = jbp_roles.jbp_rid INNER JOIN " +"jbp_users ON\n" +" jbp_role_membership.jbp_uid = jbp_users.jbp_uid WHERE jbp_users." +"jbp_uname=?\n" +" </module-option>\n" +" <module-option name=\"hashAlgorithm\">MD5</module-option>\n" +" <module-option name=\"hashEncoding\">HEX</module-option>\n" +" <module-option name=\"additionalRole\">Authenticated</module-option>\n" +"</login-module>\n" +" ]]>" +msgstr "" + +#. Tag: para +#: Authentication.xml:110 +#, no-c-format +msgid "" +"SQL query should be in single line. This code snipped was formatted like " +"this only to fit documentation page." +msgstr "" + +#. Tag: title +#: Authentication.xml:114 +#, no-c-format +msgid "org.jboss.portal.identity.auth.SynchronizingLdapLoginModule" +msgstr "" + +#. Tag: para +#: Authentication.xml:115 +#, no-c-format +msgid "" +"This module can be used instead of the IdentityLoginModule to bind to LDAP. " +"<emphasis>org.jboss.portal.identity.auth.SynchronizingLDAPLoginModule</" +"emphasis> class is a wrapper around <ulink url=\"http://wiki.jboss.org/wiki/" +"Wiki.jsp?page=LdapLoginModule\">LdapLoginModule</ulink> from JBossSX. It " +"extends it so all configuration that can be applied to " +"<emphasis>LdapExtLoginModule</emphasis> remains valid here. For a user that " +"was authenticated successfully it will try to call the identity modules from " +"portal, then check if such user exists or not, and if does not exist it will " +"try to create it. Then for all roles assigned to this authenticated " +"principal it will try to check and create them using identity modules. This " +"behavior can be altered using following options: <itemizedlist> " +"<listitem><para> <emphasis role=\"bold\">userModuleJNDIName</emphasis> - " +"JNDI name of portal UserModule. This option is <emphasis>obligatory</" +"emphasis> if <emphasis>synchronizeIdentity</emphasis> option is set to " +"<emphasis>true</emphasis></para> </listitem> <listitem><para> <emphasis role=" +"\"bold\">roleModuleJNDIName</emphasis> - JNDI name of portal RoleModule. " +"This option is <emphasis>obligatory</emphasis> if " +"<emphasis>synchronizeIdentity</emphasis> and <emphasis>synchronizeRoles</" +"emphasis> options are set to <emphasis>true</emphasis></para> </listitem> " +"<listitem><para> <emphasis role=\"bold\">membershipModuleJNDIName</emphasis> " +"- JNDI name of portal MembershipModule. This option is <emphasis>obligatory</" +"emphasis> if <emphasis>synchronizeIdentity</emphasis> and " +"<emphasis>synchronizeRoles</emphasis> options are set to <emphasis>true</" +"emphasis></para> </listitem> <listitem><para> <emphasis role=\"bold" +"\">userProfileModuleJNDIName</emphasis> - JNDI name of portal " +"UserProfileModule. This option is <emphasis>obligatory</emphasis> if " +"<emphasis>synchronizeIdentity</emphasis> option is set to <emphasis>true</" +"emphasis></para> </listitem> <listitem><para> <emphasis role=\"bold" +"\">synchronizeIdentity</emphasis> - if set to <emphasis>true</emphasis> " +"module will check if successfully authenticated user exist in portal and if " +"not it will try to create it. If user exists module will update its password " +"to the one that was just validated.</para> </listitem> <listitem><para> " +"<emphasis role=\"bold\">synchronizeRoles</emphasis> - if set to " +"<emphasis>true</emphasis> module will iterate over all roles assigned to " +"authenticated user and for each it will try to check if such role exists in " +"portal and if not it will try to create it. This option is checked only if " +"<emphasis>synchronizeIdentity</emphasis> is set to true;</para> </listitem> " +"<listitem><para> <emphasis role=\"bold\">additionalRole</emphasis> - module " +"will add this role name to the group of principals assigned to the " +"authenticated user.</para> </listitem> <listitem><para> <emphasis role=\"bold" +"\">defaultAssignedRole</emphasis> - if <emphasis>synchronizeIdentity</" +"emphasis> is set to true, module will try to assign portal role with such " +"name to the authenticated user. If such role doesn't exist in portal, module " +"will try to create it. </para> </listitem> </itemizedlist> For obvious " +"reasons this is designed to use with portal identity modules configured with " +"DB and not LDAP" +msgstr "" + +#. Tag: title +#: Authentication.xml:161 +#, no-c-format +msgid "org.jboss.portal.identity.auth.SynchronizingLdapExtLoginModule" +msgstr "" + +#. Tag: para +#: Authentication.xml:162 +#, no-c-format +msgid "" +"All options that apply for <emphasis>SynchronizingLdapLoginModule</emphasis> " +"also apply here. It's the same kind of wrapper made around <ulink url=" +"\"http://wiki.jboss.org/wiki/Wiki.jsp?page=LdapExtLoginModule" +"\">LdapExtLoginModule</ulink> from JBossSX. Sample configuration can look " +"like this:" +msgstr "" + +#. Tag: programlisting +#: Authentication.xml:165 +#, no-c-format +msgid "" +"<![CDATA[\n" +" <login-module code=\"org.jboss.portal.identity.auth." +"SynchronizingLDAPExtLoginModule\"\n" +" flag=\"required\">\n" +" <module-option name=\"synchronizeIdentity\">true</module-option>\n" +" <module-option name=\"synchronizeRoles\">true</module-option>\n" +" <module-option name=\"additionalRole\">Authenticated</module-option>\n" +" <module-option name=\"defaultAssignedRole\">User</module-option>\n" +" <module-option name=\"userModuleJNDIName\">java:/portal/UserModule</" +"module-option>\n" +" <module-option name=\"roleModuleJNDIName\">java:/portal/RoleModule</" +"module-option>\n" +" <module-option name=\"membershipModuleJNDIName\">java:/portal/" +"MembershipModule\n" +" </module-option>\n" +" <module-option name=\"userProfileModuleJNDIName\">java:/portal/" +"UserProfileModule\n" +" </module-option>\n" +" <module-option name=\"java.naming.factory.initial\">com.sun.jndi.ldap." +"LdapCtxFactory\n" +" </module-option>\n" +" <module-option name=\"java.naming.provider.url\">ldap://example." +"com:10389/\n" +" </module-option>\n" +" <module-option name=\"java.naming.security.authentication\">simple</" +"module-option>\n" +" <module-option name=\"bindDN\">cn=Directory Manager</module-option>\n" +" <module-option name=\"bindCredential\">secret</module-option>\n" +" <module-option name=\"baseCtxDN\">ou=People,dc=example,dc=com</module-" +"option>\n" +" <module-option name=\"baseFilter\">(uid={0})</module-option>\n" +" <module-option name=\"rolesCtxDN\">ou=Roles,dc=example,dc=com</module-" +"option>\n" +" <module-option name=\"roleFilter\">(member={1})</module-option>\n" +" <module-option name=\"roleAttributeID\">cn</module-option>\n" +" <module-option name=\"roleRecursion\">-1</module-option>\n" +" <module-option name=\"searchTimeLimit\">10000</module-option>\n" +" <module-option name=\"searchScope\">SUBTREE_SCOPE</module-option>\n" +" <module-option name=\"allowEmptyPasswords\">false</module-option>\n" +"</login-module>]]>" +msgstr "" + +#. Tag: title +#: Authentication.xml:168 +#, no-c-format +msgid "org.jboss.portal.identity.auth.SynchronizingLoginModule" +msgstr "" + +#. Tag: para +#: Authentication.xml:169 +#, no-c-format +msgid "" +"This module is designed to provide synchronization support for any other " +"LoginModule placed in the authentication stack. It leverages the fact that " +"in JAAS authentication process occurs in two phases. In first phase when " +"login() method is invoked it always returns \"true\". Because of this " +"behavior <emphasis>SynchronizingLoginModule</emphasis> should be always used " +"with \"optional\" flag. More over it should be placed after the module we " +"want to leverage as a source for synchronization and that module should have " +"\"required\" flag set. During the second phase when commit() method is " +"invoked it gets user <emphasis>Subject</emphasis> and its " +"<emphasis>Principal</emphasis>s and tries to synchronize them into storage " +"configured for portal identity modules. For this purposes such options are " +"supported:" +msgstr "" + +#. Tag: para +#: Authentication.xml:178 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">userModuleJNDIName</emphasis> - JNDI name of portal " +"UserModule. This option is <emphasis>obligatory</emphasis> if " +"<emphasis>synchronizeIdentity</emphasis> option is set to <emphasis>true</" +"emphasis>" +msgstr "" + +#. Tag: para +#: Authentication.xml:182 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">roleModuleJNDIName</emphasis> - JNDI name of portal " +"RoleModule. This option is <emphasis>obligatory</emphasis> if " +"<emphasis>synchronizeIdentity</emphasis> and <emphasis>synchronizeRoles</" +"emphasis> options are set to <emphasis>true</emphasis>" +msgstr "" + +#. Tag: para +#: Authentication.xml:186 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">membershipModuleJNDIName</emphasis> - JNDI name of " +"portal MembershipModule. This option is <emphasis>obligatory</emphasis> if " +"<emphasis>synchronizeIdentity</emphasis> and <emphasis>synchronizeRoles</" +"emphasis> options are set to <emphasis>true</emphasis>" +msgstr "" + +#. Tag: para +#: Authentication.xml:190 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">userProfileModuleJNDIName</emphasis> - JNDI name of " +"portal UserProfileModule. This option is <emphasis>obligatory</emphasis> if " +"<emphasis>synchronizeIdentity</emphasis> option is set to <emphasis>true</" +"emphasis>" +msgstr "" + +#. Tag: para +#: Authentication.xml:194 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">synchronizeIdentity</emphasis> - if set to " +"<emphasis>true</emphasis> module will check if successfully authenticated " +"user exist in portal and if not it will try to create it. If user exists " +"module will update its password to the one that was just validated." +msgstr "" + +#. Tag: para +#: Authentication.xml:199 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">synchronizeRoles</emphasis> - if set to " +"<emphasis>true</emphasis> module will iterate over all roles assigned to " +"authenticated user and for each it will try to check if such role exists in " +"portal and if not it will try to create it. This option is checked only if " +"<emphasis>synchronizeIdentity</emphasis> is set to true;" +msgstr "" + +#. Tag: para +#: Authentication.xml:204 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">additionalRole</emphasis> - module will add this " +"role name to the group of principals assigned to the authenticated user." +msgstr "" + +#. Tag: para +#: Authentication.xml:207 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">defaultAssignedRole</emphasis> - if " +"<emphasis>synchronizeIdentity</emphasis> is set to true, module will try to " +"assign portal role with such name to the authenticated user. If such role " +"doesn't exist in portal, module will try to create it." +msgstr "" + +#. Tag: para +#: Authentication.xml:212 +#, no-c-format +msgid "" +"Example of usage in LDAP authentication can be found in <xref linkend=\"ldap." +"synchronizing\"/>." +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Author_Group.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Author_Group.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Author_Group.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,20 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: author +#: Author_Group.xml:6 +#, no-c-format +msgid "<firstname>Red Hat</firstname> <surname></surname>" +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Book_Info.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Book_Info.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Book_Info.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,32 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Book_Info.xml:6 +#, no-c-format +msgid "Reference Guide" +msgstr "" + +#. Tag: para +#: Book_Info.xml:16 +#, no-c-format +msgid "This book is the Enterprise Portal Platform Reference Guide." +msgstr "" + +#. Tag: holder +#: Book_Info.xml:28 +#, no-c-format +msgid "&HOLDER;" +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/CMS_Portlet.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/CMS_Portlet.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/CMS_Portlet.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,806 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: CMS_Portlet.xml:15 +#, no-c-format +msgid "CMS Portlet" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:16 +#, no-c-format +msgid "" +"JBoss Portal packages a Web Content Management System capable of serving and " +"allowing administration of web content. This chapter describes the CMS " +"Portlet which is responsible for serving resources requested, the following " +"chapter describes the CMSAdmin Portlet and all administration functionality." +msgstr "" + +#. Tag: title +#: CMS_Portlet.xml:26 +#, no-c-format +msgid "Introduction" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:27 +#, no-c-format +msgid "" +"The CMS Portlet displays content from the file store inside a portlet " +"window, or, in the case of binary content, outside of the portlet window " +"altogether." +msgstr "" + +#. Tag: title +#: CMS_Portlet.xml:31 +#, no-c-format +msgid "Features" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:32 +#, no-c-format +msgid "The CMSPortlet handles all requests for all content types." +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:33 +#, no-c-format +msgid "" +"The methodology of serving content within the CMSPortlet, allows for some " +"beneficial features, like:" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:37 +#, no-c-format +msgid "" +"Search-engine friendly URLs: http://domain/[portal]/content/company.html" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:38 +#, no-c-format +msgid "" +"Serve binaries with simple urls independent of the portal: http://domain/" +"content/products.pdf" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:40 +#, no-c-format +msgid "" +"Deploy several instances of the CMSPortlet on any page and configure them to " +"display different start pages." +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:42 +#, no-c-format +msgid "" +"Localization support: CMSPortlet will display content based on the user " +"request locale, or display content using the default locale setting." +msgstr "" + +#. Tag: title +#: CMS_Portlet.xml:47 +#, no-c-format +msgid "CMS content" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:48 +#, no-c-format +msgid "" +"Since 2.6 displaying CMS content in the portal is done using the new content " +"integration feature. Each window of the portal can be configured to display " +"CMS content directly instead of having to configure the CMS portlet as it " +"used to be." +msgstr "" + +#. Tag: title +#: CMS_Portlet.xml:53 +#, no-c-format +msgid "Configuring a window to display CMS content" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:54 +#, no-c-format +msgid "" +"Showing CMS content in a portal window can be done in the deployment " +"descriptor quite easily <programlisting><![CDATA[<window>\n" +" <window-name>MyCMSWindow</window-name>\n" +" <content>\n" +" <content-type>cms</content-type>\n" +" <content-uri>/default/index.html</content-uri>\n" +" </content>\n" +" <region>center</region>\n" +" <height>1</height>\n" +"</window>\n" +"]]></programlisting> At the first display of the window, the content is " +"initialized with the content uri value. When the user clicks on a link that " +"navigates to another CMS file, the CMS file will be shown in the same window." +msgstr "" + +#. Tag: title +#: CMS_Portlet.xml:63 +#, no-c-format +msgid "CMS Configuration" +msgstr "" + +#. Tag: title +#: CMS_Portlet.xml:65 +#, no-c-format +msgid "Display CMS content" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:66 +#, no-c-format +msgid "" +"Since 2.6 displaying CMS content in the portal is done using the new content " +"integration feature. The portal is also able to map urls content to the CMS " +"through a specific window. The CMS portlet default page is defined as a " +"preference and can be overridden like any other preference up to the user's " +"preference level. The default CMS portlet displayed when you install JBoss " +"Portal for the first time is describe in the following file: <emphasis>jboss-" +"portal.sar/portal-core.war/WEB-INF/portlet.xml</emphasis> ." +msgstr "" + +#. Tag: programlisting +#: CMS_Portlet.xml:77 +#, no-c-format +msgid "" +"<![CDATA[<portlet-preferences>\n" +" <preference>\n" +" <name>indexpage</name>\n" +" <value>/default/index.html</value>\n" +" </preference>\n" +"</portlet-preferences>]]>" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:78 +#, no-c-format +msgid "" +"The preference key is \"indexpage\". To change the default page, just make " +"sure to create an HTML document using the CMS Admin portlet then change the " +"value of \"indexpage\" to the corresponding path." +msgstr "" + +#. Tag: title +#: CMS_Portlet.xml:85 +#, no-c-format +msgid "Service Configuration" +msgstr "" + +#. Tag: title +#: CMS_Portlet.xml:87 +#, no-c-format +msgid "Tuning Apache Jackrabbit" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:88 +#, no-c-format +msgid "" +"JBoss Portal uses Apache Jackrabbit as its Java Content Repository " +"implementation. Configuration of the service descriptor, allows for changing " +"many of the variables associated with the service." +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:91 +#, no-c-format +msgid "" +"Here is the default configuration for the CMS repository found under " +"<literal>portal-cms.sar/META-INF-INF/jboss-service.xml</literal>" +msgstr "" + +#. Tag: programlisting +#: CMS_Portlet.xml:94 +#, no-c-format +msgid "" +"<![CDATA[...\n" +"<attribute name=\"DoChecking\">true</attribute>\n" +"<attribute name=\"DefaultContentLocation\">portal/cms/conf/default-content/" +"default/</attribute>\n" +"<attribute name=\"DefaultLocale\">en</attribute>\n" +"<attribute name=\"RepositoryName\">PortalRepository</attribute>\n" +"<attribute name=\"HomeDir\">${jboss.server.data.dir}${/}portal${/}cms${/}" +"conf</attribute>]]>\n" +"..." +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:95 +#, no-c-format +msgid "" +"Below is a list of items found in the service descriptor and their " +"definitions. Only items commonly changed are covered here and it is " +"recommended you do not change any others unless you are very brave." +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:100 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">DoChecking:</emphasis> Should the portal attempt to " +"check for the existence of the repository configuration files and default " +"content on startup?" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:106 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">DefaultContentLocation:</emphasis> Location of the " +"default content used to pre-populate the repository." +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:111 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">DefaultLocale:</emphasis> Two-letter abbreviation of " +"the default locale the portal should use when fetching content for users. A " +"complete ISO-639 list can be found <ulink url=\"http://ftp.ics.uci.edu/pub/" +"ietf/http/related/iso639.txt\">here</ulink> ." +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:119 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">HomeDir:</emphasis> Location of configuration " +"information for the repository when in 100% FileSystem store mode. " +"Otherwise, its in the database." +msgstr "" + +#. Tag: title +#: CMS_Portlet.xml:127 +#, no-c-format +msgid "Changing the url under which the content should be accessible" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:128 +#, no-c-format +msgid "" +"By default, the content will be accessible to a url like this: http://www." +"example.com/content/[...], if you need or prefer to change \"content\" to " +"something else you will need to edit the following file: <literal>portal-cms." +"sar/META-INF-INF/jboss-service.xml</literal> and change the value of Prefix " +"to something else. Please note that you cannot change it to \"nothing\", you " +"need to provide a value." +msgstr "" + +#. Tag: programlisting +#: CMS_Portlet.xml:135 +#, no-c-format +msgid "" +"<![CDATA[...\n" +"<mbean\n" +" code=\"org.jboss.portal.core.cms.CMSObjectCommandFactory\"\n" +" name=\"portal:commandFactory=CMSObject\"\n" +" xmbean-dd=\"\"\n" +" xmbean-code=\"org.jboss.portal.common.system.JBossServiceModelMBean\">\n" +" <xmbean/>\n" +" <attribute name=\"Prefix\">content</attribute>\n" +" <attribute name=\"TargetWindowRef\">default.default.CMSPortletWindow</" +"attribute>\n" +" <depends optional-attribute-name=\"Factory\" proxy-type=\"attribute\">\n" +" portal:commandFactory=Delegating\n" +" </depends>\n" +" <depends optional-attribute-name=\"CMSService\" proxy-type=\"attribute" +"\">\n" +" portal:service=CMS\n" +" </depends>\n" +"</mbean>\n" +"...]]>" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:138 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">Prefix:</emphasis> This is the context path prefix " +"that will trigger the portal to render content. By default, navigating to a " +"URL such as http://localhost:8080/[portal_context]/content/Test.PDF will " +"trigger the portal to display the PDF isolated from the portal pages. The " +"path following the <emphasis>Prefix</emphasis> has to be absolute when " +"fetching content." +msgstr "" + +#. Tag: title +#: CMS_Portlet.xml:150 +#, no-c-format +msgid "Configuring the Content Store Location" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:151 +#, no-c-format +msgid "" +"By default, the JBoss Portal CMS stores all node properties, references, and " +"binary content in the database, using the portal datasource. The location of " +"some of these items is configurable, and there are 3 options:" +msgstr "" + +#. Tag: title +#: CMS_Portlet.xml:173 +#, no-c-format +msgid "100% Filesystem Storage" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:174 +#, no-c-format +msgid "" +"To enable 100% Filesystem storage, you must edit the file: <emphasis>jboss-" +"portal.sar/portal-cms.sar/META-INF/jboss-service.xml</emphasis> . You will " +"note that the file is set to use the HibernateStore and " +"HibernatePersistenceManager classes, by default. To have the CMS use 100% " +"file system storage, simply comment these blocks. Then, you should uncomment " +"to use the LocalFileSystem and XMLPersistenceManager classes. Follow these " +"steps to activate 100% FS storage:" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:184 +#, no-c-format +msgid "" +"Comment out the following blocks (there are 3 in total): <programlisting><!" +"[CDATA[\n" +"<!-- HibernateStore: uses RDBMS + Hibernate for storage -->\n" +"<FileSystem class=\"org.jboss.portal.cms.hibernate.HibernateStore\">\n" +"...\n" +"</FileSystem>\n" +"]]></programlisting> And uncomment the blocks under them (there are 3 in " +"total):" +msgstr "" + +#. Tag: programlisting +#: CMS_Portlet.xml:188 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!-- LocalFileSystem: uses FileSystem for storage. -->\n" +"<FileSystem class=\"org.apache.jackrabbit.core.fs.local.LocalFileSystem\">\n" +"...\n" +"</FileSystem>]]>" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:192 +#, no-c-format +msgid "" +"Now comment out the following blocks (there are 2 in total): " +"<programlisting><![CDATA[\n" +"<!-- HibernatePersistentManager: uses RDBMS + Hibernate for storage -->\n" +"<PersistenceManager class=\"org.jboss.portal.cms.hibernate.state." +"HibernatePersistenceManager\">\n" +"...\n" +"</PersistenceManager>]]></programlisting> And uncomment the blocks under " +"them (there are 2 in total):" +msgstr "" + +#. Tag: programlisting +#: CMS_Portlet.xml:196 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!-- XMLPersistenceManager: uses FileSystem for storage -->\n" +"<PersistenceManager class=\"org.apache.jackrabbit.core.state.xml." +"XMLPersistenceManager\"/>\n" +"]]>" +msgstr "" + +#. Tag: title +#: CMS_Portlet.xml:202 CMS_Portlet.xml:233 +#, no-c-format +msgid "Caution" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:202 CMS_Portlet.xml:233 +#, no-c-format +msgid "" +"If you do any change at the workspaces configuration you will need to delete " +"the file <emphasis>$JBOSS_HOME/server/xxx/data/portal/cms/conf/workspaces/" +"default/workspace.xml</emphasis> before restarting JBoss or redeploying " +"JBoss Portal. If you forget to do that, the changes won't affect the CMS. " +"For the same reason, you also need to delete that file if you recompile " +"JBoss Portal after changing the name of the datasource. Note that on a " +"cluster environment, you need to remove that file (if it exists) on all the " +"nodes." +msgstr "" + +#. Tag: title +#: CMS_Portlet.xml:214 +#, no-c-format +msgid "100% Database Storage" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:215 +#, no-c-format +msgid "" +"This is the default configuration for the CMS store. Please view the " +"original <emphasis>jboss-portal.sar/portal-cms.sar/META-INF/jboss-service." +"xml</emphasis> , for guidance on how to reset it." +msgstr "" + +#. Tag: title +#: CMS_Portlet.xml:221 +#, no-c-format +msgid "Mixed Storage" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:222 +#, no-c-format +msgid "" +"Mixed storage consists of meta-data being stored in the DB and blobs being " +"stored on the Filesystem. This is the recommended setting for those of you " +"that serve large files or stream media content." +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:224 +#, no-c-format +msgid "" +"Setting the repository this way is simple. Change every instance in the file " +"<emphasis>jboss-portal.sar/portal-cms.sar/META-INF/jboss-service.xml</" +"emphasis> , from: <programlisting><![CDATA[<param name=\"externalBLOBs\" " +"value=\"false\"/>]]></programlisting> to:" +msgstr "" + +#. Tag: programlisting +#: CMS_Portlet.xml:230 +#, no-c-format +msgid "<![CDATA[<param name=\"externalBLOBs\" value=\"true\"/>]]>" +msgstr "" + +#. Tag: title +#: CMS_Portlet.xml:251 +#, no-c-format +msgid "Localization Support" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:252 +#, no-c-format +msgid "" +"The CMS Portlet now serves content based on the user's locale setting. For " +"example: if a user's locale is set to Spanish in his browser, and he " +"requests URL: <emphasis>default/index.html</emphasis> , the CMSPortlet will " +"first try and retrieve the Spanish version of that file. If a Spanish " +"version is not found, it will then try and retrieve the default language " +"version set for the CMSPortlet." +msgstr "" + +#. Tag: title +#: CMS_Portlet.xml:261 +#, no-c-format +msgid "CMS Service" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:262 +#, no-c-format +msgid "" +"The CMS portlet calls a CMS service that can be reused in your own portlets." +msgstr "" + +#. Tag: title +#: CMS_Portlet.xml:266 +#, no-c-format +msgid "CMS Interceptors" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:267 +#, no-c-format +msgid "" +"Since JBoss Portal 2.4 you can add your own interceptor stack to the CMS " +"service. The interceptors are called around each command (Get a file, write " +"a file, create a folder...), this is a very easy way to customize some " +"actions based on your needs." +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:272 +#, no-c-format +msgid "" +"To create your own interceptor you just need to extend the <literal>org." +"jboss.portal.cms.CMSInterceptor</literal> class and provide the content of " +"the <literal>invoke(JCRCommand)</literal> method. Do not forget to make a " +"call to <literal>JCRCommand.invokeNext()</literal> or the command will never " +"be executed." +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:282 +#, no-c-format +msgid "" +"JBoss Portal relies on the interceptor mechanism to integrate its Fine " +"Grained Security Service and the Publish/Approve Workflow Service" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:286 +#, no-c-format +msgid "" +"To add or remove an interceptor, you just need to edit the following file: " +"<literal>portal-cms-sar/META-INF/jboss-service.xml</literal>. It works the " +"same way as the server interceptor, for each interceptor you need to define " +"an MBean then add it to the cms interceptor stack. For example, if you have " +"the 2 default interceptors, you should have the following lines in the jboss-" +"service.xml file: <programlisting><![CDATA[<!-- ACL Security Interceptor --" +">\n" +"<mbean code=\"org.jboss.portal.cms.impl.interceptors.ACLInterceptor\"\n" +" name=\"portal:service=Interceptor,type=Cms,name=ACL\" xmbean-dd=" +"\"\"\n" +" xmbean-code=\"org.jboss.portal.jems.as.system.JBossServiceModelMBean" +"\">\n" +" <xmbean />\n" +" <attribute name=\"JNDIName\">\n" +" java:/portal/cms/ACLInterceptor\n" +" </attribute>\n" +" <attribute name=\"CmsSessionFactory\">\n" +" java:/portal/cms/CMSSessionFactory\n" +" </attribute>\n" +" <attribute name=\"IdentitySessionFactory\">\n" +" java:/portal/IdentitySessionFactory\n" +" </attribute>\n" +" <attribute name=\"DefaultPolicy\">\n" +" <policy>\n" +" <!-- permissions on the root cms node -->\n" +" <criteria name=\"path\" value=\"/\">\n" +" <permission name=\"cms\" action=\"read\">\n" +" <role name=\"Anonymous\" />\n" +" </permission>\n" +" <permission name=\"cms\" action=\"write\">\n" +" <role name=\"User\" />\n" +" </permission>\n" +" <permission name=\"cms\" action=\"manage\">\n" +" <role name=\"Admin\" />\n" +" </permission>\n" +" </criteria>\n" +" <!-- permissions on the default cms node -->\n" +" <criteria name=\"path\" value=\"/default\">\n" +" <permission name=\"cms\" action=\"read\">\n" +" <role name=\"Anonymous\" />\n" +" </permission>\n" +" <permission name=\"cms\" action=\"write\">\n" +" <role name=\"User\" />\n" +" </permission>\n" +" <permission name=\"cms\" action=\"manage\">\n" +" <role name=\"Admin\" />\n" +" </permission>\n" +" </criteria>\n" +" <!-- permissions on the private/protected node -->\n" +" <criteria name=\"path\" value=\"/default/private\">\n" +" <permission name=\"cms\" action=\"manage\">\n" +" <role name=\"Admin\" />\n" +" </permission>\n" +" </criteria>\n" +" </policy>\n" +" </attribute>\n" +" <depends optional-attribute-name=\"AuthorizationManager\"\n" +" proxy-type=\"attribute\">\n" +" portal:service=AuthorizationManager,type=cms\n" +" </depends>\n" +" <depends>portal:service=Hibernate,type=CMS</depends>\n" +" <depends>\n" +" portal:service=Module,type=IdentityServiceController\n" +" </depends>\n" +"</mbean>\n" +"\n" +"<!-- Approval Workflow Interceptor -->\n" +"<mbean\n" +" code=\"org.jboss.portal.cms.impl.interceptors." +"ApprovalWorkflowInterceptor\"\n" +" name=\"portal:service=Interceptor,type=Cms,name=ApprovalWorkflow\"\n" +" xmbean-dd=\"\"\n" +" xmbean-code=\"org.jboss.portal.jems.as.system.JBossServiceModelMBean" +"\">\n" +" <xmbean />\n" +" <attribute name=\"JNDIName\">\n" +" java:/portal/cms/ApprovalWorkflowInterceptor\n" +" </attribute>\n" +" <depends>portal:service=Hibernate,type=CMS</depends>\n" +"</mbean>\n" +"\n" +"<!-- CMS Interceptor Registration -->\n" +"<mbean\n" +" code=\"org.jboss.portal.server.impl.invocation." +"JBossInterceptorStackFactory\"\n" +" name=\"portal:service=InterceptorStackFactory,type=Cms\" xmbean-dd=" +"\"\"\n" +" xmbean-code=\"org.jboss.portal.jems.as.system.JBossServiceModelMBean" +"\">\n" +" <xmbean />\n" +" <depends-list optional-attribute-name=\"InterceptorNames\">\n" +" <depends-list-element>\n" +" portal:service=Interceptor,type=Cms,name=ACL\n" +" </depends-list-element>\n" +" <depends-list-element>\n" +" portal:service=Interceptor,type=Cms," +"name=ApprovalWorkflow\n" +" </depends-list-element>\n" +" </depends-list>\n" +"</mbean>\n" +" ]]>\n" +" </programlisting> The first two MBeans define the interceptors " +"and the third MBean, define which interceptors to add to the CMS service." +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:296 +#, no-c-format +msgid "" +"If you create your own interceptor <literal>org.example.myCMSInterceptor</" +"literal>, the service descriptor file will look like:" +msgstr "" + +#. Tag: programlisting +#: CMS_Portlet.xml:298 +#, no-c-format +msgid "" +"<![CDATA[<mbean code=\"org.example.myCMSInterceptor\"\n" +" name=\"portal:service=Interceptor,type=Cms,name=MyName\" xmbean-dd=" +"\"\"\n" +" xmbean-code=\"org.jboss.portal.common.system.JBossServiceModelMBean" +"\">\n" +" <xmbean />\n" +"</mbean>\n" +"\n" +"<!-- ACL Security Interceptor -->\n" +"<mbean code=\"org.jboss.portal.cms.impl.interceptors.ACLInterceptor\"\n" +" name=\"portal:service=Interceptor,type=Cms,name=ACL\" xmbean-dd=" +"\"\"\n" +" xmbean-code=\"org.jboss.portal.jems.as.system.JBossServiceModelMBean" +"\">\n" +" <xmbean />\n" +" <attribute name=\"JNDIName\">\n" +" java:/portal/cms/ACLInterceptor\n" +" </attribute>\n" +" <attribute name=\"CmsSessionFactory\">\n" +" java:/portal/cms/CMSSessionFactory\n" +" </attribute>\n" +" <attribute name=\"IdentitySessionFactory\">\n" +" java:/portal/IdentitySessionFactory\n" +" </attribute>\n" +" <attribute name=\"DefaultPolicy\">\n" +" <policy>\n" +" <!-- permissions on the root cms node -->\n" +" <criteria name=\"path\" value=\"/\">\n" +" <permission name=\"cms\" action=\"read\">\n" +" <role name=\"Anonymous\" />\n" +" </permission>\n" +" <permission name=\"cms\" action=\"write\">\n" +" <role name=\"User\" />\n" +" </permission>\n" +" <permission name=\"cms\" action=\"manage\">\n" +" <role name=\"Admin\" />\n" +" </permission>\n" +" </criteria>\n" +" <!-- permissions on the default cms node -->\n" +" <criteria name=\"path\" value=\"/default\">\n" +" <permission name=\"cms\" action=\"read\">\n" +" <role name=\"Anonymous\" />\n" +" </permission>\n" +" <permission name=\"cms\" action=\"write\">\n" +" <role name=\"User\" />\n" +" </permission>\n" +" <permission name=\"cms\" action=\"manage\">\n" +" <role name=\"Admin\" />\n" +" </permission>\n" +" </criteria>\n" +" <!-- permissions on the private/protected node -->\n" +" <criteria name=\"path\" value=\"/default/private\">\n" +" <permission name=\"cms\" action=\"manage\">\n" +" <role name=\"Admin\" />\n" +" </permission>\n" +" </criteria>\n" +" </policy>\n" +" </attribute>\n" +" <depends optional-attribute-name=\"AuthorizationManager\"\n" +" proxy-type=\"attribute\">\n" +" portal:service=AuthorizationManager,type=cms\n" +" </depends>\n" +" <depends>portal:service=Hibernate,type=CMS</depends>\n" +" <depends>\n" +" portal:service=Module,type=IdentityServiceController\n" +" </depends>\n" +"</mbean>\n" +"\n" +"<!-- Approval Workflow Interceptor -->\n" +"<mbean\n" +" code=\"org.jboss.portal.cms.impl.interceptors." +"ApprovalWorkflowInterceptor\"\n" +" name=\"portal:service=Interceptor,type=Cms,name=ApprovalWorkflow\"\n" +" xmbean-dd=\"\"\n" +" xmbean-code=\"org.jboss.portal.jems.as.system.JBossServiceModelMBean" +"\">\n" +" <xmbean />\n" +" <attribute name=\"JNDIName\">\n" +" java:/portal/cms/ApprovalWorkflowInterceptor\n" +" </attribute>\n" +" <depends>portal:service=Hibernate,type=CMS</depends>\n" +"</mbean>\n" +"<mbean\n" +" code=\"org.jboss.portal.server.impl.invocation." +"JBossInterceptorStackFactory\"\n" +" name=\"portal:service=InterceptorStackFactory,type=Cms\" xmbean-dd=" +"\"\"\n" +" xmbean-code=\"org.jboss.portal.jems.as.system.JBossServiceModelMBean" +"\">\n" +" <xmbean />\n" +" <depends-list optional-attribute-name=\"InterceptorNames\">\n" +" <depends-list-element>\n" +" portal:service=Interceptor,type=Cms,name=ACL\n" +" </depends-list-element>\n" +" <depends-list-element>\n" +" portal:service=Interceptor,type=Cms," +"name=ApprovalWorkflow\n" +" </depends-list-element>\n" +" </depends-list>\n" +"</mbean>\n" +"\n" +"<!-- CMS Interceptor Registration -->\n" +"<mbean\n" +" code=\"org.jboss.portal.server.impl.invocation.JBossInterceptorStack" +"\"\n" +" name=\"portal:service=InterceptorStack,type=Cms\" xmbean-dd=\"\"\n" +" xmbean-code=\"org.jboss.portal.common.system.JBossServiceModelMBean" +"\">\n" +" <xmbean />\n" +" <depends-list optional-attribute-name=\"InterceptorNames\">\n" +" <depends-list-element>\n" +" portal:service=Interceptor,type=Cms,name=ACL\n" +" </depends-list-element>\n" +" <depends-list-element>\n" +" portal:service=Interceptor,type=Cms," +"name=ApprovalWorkflow\n" +" </depends-list-element>\n" +" <depends-list-element>\n" +" portal:service=Interceptor,type=Cms,name=MyName\n" +" </depends-list-element>\n" +" </depends-list>\n" +"</mbean>\n" +"]]>" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:301 +#, no-c-format +msgid "The interceptor order is important !" +msgstr "" + +#. Tag: para +#: CMS_Portlet.xml:305 +#, no-c-format +msgid "" +"To check that the interceptors have been correctly added, you can check the " +"JMX console, by going to: <literal>http://localhost.localdomain:8080/jmx-" +"console/HtmlAdaptor?action=inspectMBean&amp;name=portal%3Aservice%" +"3DInterceptorStack%2Ctype%3DCms</literal> You should notice all the " +"interceptors in the attribute \"interceptors\"." +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Clustering.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Clustering.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Clustering.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,774 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Clustering.xml:15 +#, no-c-format +msgid "Clustering Configuration" +msgstr "" + +#. Tag: para +#: Clustering.xml:16 +#, no-c-format +msgid "" +"This section covers configuring JBoss Portal for a clustered environment." +msgstr "" + +#. Tag: title +#: Clustering.xml:18 +#, no-c-format +msgid "Introduction" +msgstr "" + +#. Tag: para +#: Clustering.xml:19 +#, no-c-format +msgid "" +"JBoss Portal leverages various clustered services that are found in JBoss " +"Application Server. This section briefly details how each is leveraged:" +msgstr "" + +#. Tag: para +#: Clustering.xml:23 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">JBoss Cache:</emphasis> Used to replicate data among " +"the different hibernate session factories that are deployed in each node of " +"the cluster." +msgstr "" + +#. Tag: emphasis +#: Clustering.xml:31 +#, no-c-format +msgid "JBoss HA Singleton:" +msgstr "" + +#. Tag: para +#: Clustering.xml:33 +#, no-c-format +msgid "" +"Used to make the deployer a singleton on the cluster, in order to avoid " +"concurrency issues when deploying the various *-object.xml files. Without " +"that, each node would try to create the same objects in the database when it " +"deploys an archive containing such descriptors." +msgstr "" + +#. Tag: para +#: Clustering.xml:37 +#, no-c-format +msgid "" +"Used with JCR. The Apache Jackrabbit server is not able to run in a cluster " +"by itself, therefore we make a singleton on the cluster. This provides HA-" +"CMS, which is similar to the current HA JBossMQ provided in JBoss AS." +msgstr "" + +#. Tag: para +#: Clustering.xml:44 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">HA-JNDI:</emphasis> Used to replicate a proxy that " +"will talk to the HA CMS on the cluster." +msgstr "" + +#. Tag: para +#: Clustering.xml:50 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">Http Session Replication:</emphasis> Used to " +"replicate the portal and the portlet sessions." +msgstr "" + +#. Tag: para +#: Clustering.xml:56 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">JBoss SSO:</emphasis> Used to replicate the user " +"identity, an authenticated user does not have to login again when failover " +"occurs." +msgstr "" + +#. Tag: title +#: Clustering.xml:63 +#, no-c-format +msgid "Note" +msgstr "" + +#. Tag: para +#: Clustering.xml:63 +#, no-c-format +msgid "" +"JBoss Clustering details can be found in the <ulink url=\"http://wiki.jboss." +"org/wiki/Wiki.jsp?page=JBossHA\">Wiki</ulink> or the <ulink url=\"http://" +"labs.jboss.com/jbossas/docs/\">clustering documentation</ulink>." +msgstr "" + +#. Tag: title +#: Clustering.xml:74 +#, no-c-format +msgid "Considerations" +msgstr "" + +#. Tag: para +#: Clustering.xml:75 +#, no-c-format +msgid "" +"When you want to run JBoss Portal on a cluster there are a few things to " +"keep in mind:" +msgstr "" + +#. Tag: para +#: Clustering.xml:77 +#, no-c-format +msgid "" +"Deploy the portal under the <emphasis role=\"bold\">all</emphasis> " +"application server configuration as it contains the clustering services that " +"is leveraged by JBoss Portal." +msgstr "" + +#. Tag: para +#: Clustering.xml:78 +#, no-c-format +msgid "" +"All the portal instances have to use the same datasource : the database is " +"used to store the portal persistent state like pages. If you don't use a " +"shared database then you will have consistency problems." +msgstr "" + +#. Tag: title +#: Clustering.xml:84 +#, no-c-format +msgid "JBoss Portal Clustered Services" +msgstr "" + +#. Tag: title +#: Clustering.xml:87 +#, no-c-format +msgid "Portal Session Replication" +msgstr "" + +#. Tag: para +#: Clustering.xml:88 +#, no-c-format +msgid "" +"The portal associates with each user a http session in order to keep " +"specific objects such as: <itemizedlist> <listitem><para>Navigational " +"state : this is mainly the state of different portlet windows that the user " +"will manipulate during its interactions with the portal. For instance a " +"maximized portlet window with specific render parameters.</para></listitem> " +"<listitem><para>WSRP objects : the WSRP protocol can require to provide " +"specific cookies during interactions with a remote portlet.</para></" +"listitem> </itemizedlist> Replicating the portal session ensures that this " +"state will be kept in sync on the cluster, e.g The user will see exactly the " +"same portlet window on every node of the cluster. The activation of the " +"portal session replication is made through the configuration of the web " +"application that is the main entry point of the portal. This setting is " +"available in the file <emphasis>jboss-portal.sar/portal-server.war/WEB-INF/" +"web.xml</emphasis>" +msgstr "" + +#. Tag: programlisting +#: Clustering.xml:100 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<web-app>\n" +" <description>JBoss Portal</description>\n" +" <!-- Comment/Uncomment to enable portal session replication -->\n" +" <distributable/>\n" +" ...\n" +"</web-app>\n" +"]]>" +msgstr "" + +#. Tag: title +#: Clustering.xml:105 +#, no-c-format +msgid "Hibernate clustering" +msgstr "" + +#. Tag: para +#: Clustering.xml:106 +#, no-c-format +msgid "" +"JBoss Portal leverages hibernate for its database access. In order to " +"improve performances it uses the caching features provided by hibernate. On " +"a cluster the cache needs to be replicated in order to avoid state " +"inconsistencies. Hibernate is configured with JBoss Cache which performs " +"that synchronization transparently. Therefore the different hibernate " +"services must be configured to use JBoss Cache. The following hibernate " +"configurations needs to use a replicated JBoss Cache : <itemizedlist> " +"<listitem><para><emphasis>jboss-portal.sar/conf/hibernate/user/hibernate.cfg." +"xml</emphasis></para></listitem> <listitem><para><emphasis>jboss-portal.sar/" +"conf/hibernate/instances/hibernate.cfg.xml</emphasis></para></listitem> " +"<listitem><para><emphasis>jboss-portal.sar/conf/hibernate/portal/hibernate." +"cfg.xml</emphasis></para></listitem> <listitem><para><emphasis>jboss-portal." +"sar/conf/hibernate/portlet/hibernate.cfg.xml</emphasis></para></listitem> </" +"itemizedlist> The cache configuration should look like : <programlisting><!" +"[CDATA[\n" +"<!--\n" +" | Uncomment in clustered mode : use transactional replicated cache\n" +" -->\n" +" <property name=\"cache.provider_class\">org.jboss.portal.core.hibernate." +"JMXTreeCacheProvider\n" +" </property>\n" +" <property name=\"cache.object_name\">portal:service=TreeCacheProvider," +"type=hibernate\n" +" </property>\n" +"\n" +"<!--\n" +" | Comment in clustered mode\n" +" <property name=\"cache.provider_configuration_file_resource_path\">\n" +" conf/hibernate/instance/ehcache.xml</property>\n" +" <property name=\"cache.provider_class\">org.hibernate.cache." +"EhCacheProvider</property>\n" +"-->\n" +"]]></programlisting> Also we need to ensure that the cache is deployed by " +"having in the file <emphasis>jboss-portal.sar/META-INF/jboss-service.xml</" +"emphasis> the cache service uncommented : <programlisting><![CDATA[\n" +"<!--\n" +" | Uncomment in clustered mode : replicated cache for hibernate\n" +" -->\n" +" <mbean\n" +" code=\"org.jboss.cache.TreeCache\"\n" +" name=\"portal:service=TreeCache,type=hibernate\">\n" +" <depends>jboss:service=Naming</depends>\n" +" <depends>jboss:service=TransactionManager</depends>\n" +" <attribute name=\"TransactionManagerLookupClass\">\n" +" org.jboss.cache.JBossTransactionManagerLookup</attribute>\n" +" <attribute name=\"IsolationLevel\">REPEATABLE_READ</attribute>\n" +" <attribute name=\"CacheMode\">REPL_SYNC</attribute>\n" +" <attribute name=\"ClusterName\">portal.hibernate</attribute>\n" +" </mbean>\n" +"\n" +" <mbean\n" +" code=\"org.jboss.portal.core.hibernate.JBossTreeCacheProvider\"\n" +" name=\"portal:service=TreeCacheProvider,type=hibernate\">\n" +" <depends optional-attribute-name=\"CacheName\">portal:service=TreeCache," +"type=hibernate\n" +" </depends>\n" +" </mbean>\n" +"]]></programlisting> More information can be found <ulink url=\"http://wiki." +"jboss.org/wiki/Wiki.jsp?page=JBossCacheHibernate\">here</ulink>." +msgstr "" + +#. Tag: title +#: Clustering.xml:127 +#, no-c-format +msgid "Identity clustering" +msgstr "" + +#. Tag: para +#: Clustering.xml:128 +#, no-c-format +msgid "" +"JBoss Portal leverages the servlet container authentication for its own " +"authentication mechanism. When the user is authenticated on one particular " +"node he will have to reauthenticate again if a different node of the cluster " +"(during a failover for instance) is used. This is valid only for the " +"<emphasis>FORM</emphasis> based authentication which is the default form of " +"authentication that JBoss Portal uses. Fortunately JBoss provides " +"transparent reauthentication of the user called JBoss clustered SSO. Its " +"configuration can be found in <literal>$JBOSS_HOME/server/all/deploy/jboss-" +"web.deployer/server.xml</literal> and you will need to uncomment the " +"following valve: <programlisting><![CDATA[<Valve className=\"org.jboss.web." +"tomcat.service.sso.ClusteredSingleSignOn\" />]]></programlisting> More " +"information can be found <ulink url=\"http://www.jboss.org/wiki/Wiki.jsp?" +"page=SingleSignOn\">here</ulink>." +msgstr "" + +#. Tag: title +#: Clustering.xml:142 +#, no-c-format +msgid "CMS clustering" +msgstr "" + +#. Tag: para +#: Clustering.xml:143 +#, no-c-format +msgid "" +"The CMS backend storage relies on the Apache Jackrabbit project. Jackrabbit " +"does not support clustering out of the box. So the portal run the Jackrabbit " +"service on one node of the cluster using the <ulink url=\"http://www.onjava." +"com/pub/a/onjava/2003/08/20/jboss_clustering.html\">HA-Singleton</ulink> " +"technology. The file <emphasis>jboss-portal.sar/portal-cms.sar/META-INF/" +"jboss-service.xml</emphasis> contains the configuration. We will not " +"reproduce it in this documentation as the changes are quite complex and " +"numerous. Access from all nodes of the cluster is provided by a proxy bound " +"in HA-JNDI. In order to avoid any bottleneck JBoss Cache is leveraged to " +"cache CMS content cluster wide." +msgstr "" + +#. Tag: title +#: Clustering.xml:159 +#, no-c-format +msgid "Setup" +msgstr "" + +#. Tag: para +#: Clustering.xml:160 +#, no-c-format +msgid "" +"We are going to outline how to setup a two node cluster on the same machine " +"in order to test JBoss Portal HA. The only missing part from the full " +"fledged setup is the addition of a load balancer in front of Apache Tomcat. " +"However a lot of documentation exist on the subject. A detailed step by step " +"setup of Apache and mod_jk is available from the <ulink url=\"http://wiki." +"jboss.org/wiki/Wiki.jsp?page=UsingMod_jk1.2WithJBoss\">JBoss Wiki</ulink>." +msgstr "" + +#. Tag: para +#: Clustering.xml:164 +#, no-c-format +msgid "" +"As we need two application servers running at the same time, we must avoid " +"any conflict. For instance we will need Apache Tomcat to bind its socket on " +"two different ports otherwise a network conflict will occur. We will " +"leverage the service binding manager <ulink url=\"http://docs.jboss.org/" +"jbossas/jboss4guide/r3/html/ch10.html\">this chapter</ulink> of the JBoss AS " +"documentation." +msgstr "" + +#. Tag: para +#: Clustering.xml:168 +#, no-c-format +msgid "" +"The first step is to copy the <emphasis>all</emphasis> configuration of " +"JBoss into two separate configurations that we name <emphasis>ports-01</" +"emphasis> and <emphasis>ports-02</emphasis> :" +msgstr "" + +#. Tag: programlisting +#: Clustering.xml:170 +#, no-c-format +msgid "" +"<![CDATA[\n" +">cd $JBOSS_HOME/server\n" +">cp -r all ports-01\n" +">cp -r all ports-02\n" +"]]>" +msgstr "" + +#. Tag: para +#: Clustering.xml:172 +#, no-c-format +msgid "" +"Edit the file <emphasis>$JBOSS_HOME/server/ports-01/conf/jboss-service.xml</" +"emphasis> and uncomment the service binding manager :" +msgstr "" + +#. Tag: programlisting +#: Clustering.xml:174 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<mbean code=\"org.jboss.services.binding.ServiceBindingManager\"\n" +" name=\"jboss.system:service=ServiceBindingManager\">\n" +" <attribute name=\"ServerName\">ports-01</attribute>\n" +" <attribute name=\"StoreURL\">\n" +" ${jboss.home.url}/docs/examples/binding-manager/sample-bindings.xml</" +"attribute>\n" +" <attribute name=\"StoreFactoryClassName\">org.jboss.services.binding." +"XMLServicesStoreFactory</attribute>\n" +"</mbean>\n" +"]]>" +msgstr "" + +#. Tag: para +#: Clustering.xml:176 +#, no-c-format +msgid "" +"Edit the file <emphasis>$JBOSS_HOME/server/ports-02/conf/jboss-service.xml</" +"emphasis>, uncomment the service binding manager and change the value " +"<emphasis>ports-01</emphasis> into <emphasis>ports-02</emphasis>:" +msgstr "" + +#. Tag: programlisting +#: Clustering.xml:178 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<mbean code=\"org.jboss.services.binding.ServiceBindingManager\"\n" +" name=\"jboss.system:service=ServiceBindingManager\">\n" +" <attribute name=\"ServerName\">ports-02</attribute>\n" +" <attribute name=\"StoreURL\">\n" +" ${jboss.home.url}/docs/examples/binding-manager/sample-bindings.xml</" +"attribute>\n" +" <attribute name=\"StoreFactoryClassName\">\n" +" org.jboss.services.binding.XMLServicesStoreFactory</attribute>\n" +"</mbean>]]>" +msgstr "" + +#. Tag: para +#: Clustering.xml:180 +#, no-c-format +msgid "" +"Setup a database that will be shared by the two nodes and obviously we " +"cannot use an embedded database. For instance using postgresql we would need " +"to copy the file <emphasis>portal-postgresql-ds.xml</emphasis> into " +"<emphasis>$JBOSS_HOME/server/ports-01/deploy</emphasis> and <emphasis>" +"$JBOSS_HOME/server/ports-02/deploy</emphasis>." +msgstr "" + +#. Tag: para +#: Clustering.xml:184 +#, no-c-format +msgid "Copy JBoss Portal HA to the deploy directory of the two configurations." +msgstr "" + +#. Tag: title +#: Clustering.xml:188 +#, no-c-format +msgid "JBoss Cache" +msgstr "" + +#. Tag: para +#: Clustering.xml:189 +#, no-c-format +msgid "" +"To improve CMS performance JBoss Cache is leveraged to cache the content " +"cluster wide. We recommend that you use the following version of JBoss Cache " +"for best performance:" +msgstr "" + +#. Tag: emphasis +#: Clustering.xml:196 +#, no-c-format +msgid "JBoss Cache 1.4.0.SP1 and above" +msgstr "" + +#. Tag: emphasis +#: Clustering.xml:199 +#, no-c-format +msgid "JGroups 2.2.7 or 2.2.8" +msgstr "" + +#. Tag: para +#: Clustering.xml:202 +#, no-c-format +msgid "" +"When building from source the following command: <literal>{core}/build.xml " +"deploy-ha</literal> automatically upgrades your JBoss Cache version." +msgstr "" + +#. Tag: para +#: Clustering.xml:206 +#, no-c-format +msgid "" +"<emphasis>Alternative:</emphasis> If upgrading your JBoss Cache version is " +"not an option, the following configuration change is needed in the " +"<literal>jboss-portal-ha.sar/portal-cms.sar/META-INF/jboss-service.xml</" +"literal>. Replace the following configuration in the <emphasis>cms.pm.cache:" +"service=TreeCache</emphasis> Mbean:" +msgstr "" + +#. Tag: programlisting +#: Clustering.xml:215 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!--\n" +" Configuring the PortalCMSCacheLoader\n" +" CacheLoader configuration for 1.4.0\n" +"-->\n" +"<attribute name=\"CacheLoaderConfiguration\">\n" +" <config>\n" +" <passivation>false</passivation>\n" +" <preload></preload>\n" +" <shared>false</shared>\n" +" <cacheloader>\n" +" <class>org.jboss.portal.cms.hibernate.state.PortalCMSCacheLoader</" +"class>\n" +" <properties></properties>\n" +" <async>false</async>\n" +" <fetchPersistentState>false</fetchPersistentState>\n" +" <ignoreModifications>false</ignoreModifications>\n" +" </cacheloader>\n" +" </config>\n" +"</attribute>]]>" +msgstr "" + +#. Tag: para +#: Clustering.xml:216 +#, no-c-format +msgid "with the following configuration:" +msgstr "" + +#. Tag: programlisting +#: Clustering.xml:219 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!--\n" +" Configuring the PortalCMSCacheLoader\n" +" CacheLoader configuratoon for 1.2.4SP2\n" +"-->\n" +"<attribute name=\"CacheLoaderClass\">org.jboss.portal.cms.hibernate.state." +"PortalCMSCacheLoader\n" +"</attribute>\n" +"<attribute name=\"CacheLoaderConfig\" replace=\"false\"></attribute>\n" +"<attribute name=\"CacheLoaderPassivation\">false</attribute>\n" +"<attribute name=\"CacheLoaderPreload\"></attribute>\n" +"<attribute name=\"CacheLoaderShared\">false</attribute>\n" +"<attribute name=\"CacheLoaderFetchTransientState\">false</attribute>\n" +"<attribute name=\"CacheLoaderFetchPersistentState\">false</attribute>\n" +"<attribute name=\"CacheLoaderAsynchronous\">false</attribute>]]>" +msgstr "" + +#. Tag: para +#: Clustering.xml:221 +#, no-c-format +msgid "Finally we can start both servers, open two shells and execute :" +msgstr "" + +#. Tag: programlisting +#: Clustering.xml:222 +#, no-c-format +msgid "" +"<![CDATA[\n" +">cd $JBOSS_HOME/bin\n" +">sh run.sh -c ports-01\n" +"]]>" +msgstr "" + +#. Tag: programlisting +#: Clustering.xml:223 +#, no-c-format +msgid "" +"<![CDATA[\n" +">cd $JBOSS_HOME/bin\n" +">sh run.sh -c ports-02\n" +"]]>" +msgstr "" + +#. Tag: title +#: Clustering.xml:228 +#, no-c-format +msgid "Portlet Session Replication" +msgstr "" + +#. Tag: para +#: Clustering.xml:229 +#, no-c-format +msgid "" +"Web containers offer the capability to replicate sessions of web " +"applications. In the context of a portal using portlets the use case is " +"different. The portal itself is a web application that benefits of web " +"application session replication. We have to make the distinction between " +"local or remote portlets :" +msgstr "" + +#. Tag: para +#: Clustering.xml:232 +#, no-c-format +msgid "" +"Local portlets are web applications deployed in the same virtual machine as " +"the portal web application. At runtime the access to a portlet is done using " +"the mechanism of request dispatching. The portlet session is actually a mere " +"wrapper of the underlying http session of the web application in which the " +"portlet is deployed." +msgstr "" + +#. Tag: para +#: Clustering.xml:236 +#, no-c-format +msgid "" +"Remote portlets are accessed using a web service, we will not cover the " +"replication in this chapter." +msgstr "" + +#. Tag: para +#: Clustering.xml:238 +#, no-c-format +msgid "" +"The servlet specification is very loose on the subject of replication and " +"does not state anything about the replication of sessions during a " +"dispatched request. JBoss Portal offers a portlet session replication " +"mechanism that leverages the usage of the portal session instead which has " +"several advantages" +msgstr "" + +#. Tag: para +#: Clustering.xml:243 +#, no-c-format +msgid "Replicate only the portlet that requires it." +msgstr "" + +#. Tag: para +#: Clustering.xml:244 +#, no-c-format +msgid "" +"Portal session replication is just web application replication and is very " +"standard." +msgstr "" + +#. Tag: para +#: Clustering.xml:246 +#, no-c-format +msgid "" +"There are, however, some limitations. For example, you can only replicate " +"portlet-scoped attributes of a portlet session. This means that any " +"application-scoped attribute are not replicated." +msgstr "" + +#. Tag: title +#: Clustering.xml:249 +#, no-c-format +msgid "JBoss Portal configuration" +msgstr "" + +#. Tag: para +#: Clustering.xml:250 +#, no-c-format +msgid "" +"The mandatory step to make JBoss Portal able to replicate portlet sessions " +"is to configure the portal web application to be distributed as explained in" +msgstr "" + +#. Tag: title +#: Clustering.xml:254 +#, no-c-format +msgid "Portlet configuration" +msgstr "" + +#. Tag: para +#: Clustering.xml:255 +#, no-c-format +msgid "In order to activate portlet session replication you need to:" +msgstr "" + +#. Tag: para +#: Clustering.xml:257 +#, no-c-format +msgid "" +"Add a Portal-specific listener class to the <literal>/WEB-INF/web.xml</" +"literal> file of your portlet web application" +msgstr "" + +#. Tag: para +#: Clustering.xml:258 +#, no-c-format +msgid "" +"Configure your portlet to be distributed in the <literal>/WEB-INF/jboss-" +"portlet.xml</literal> file" +msgstr "" + +#. Tag: programlisting +#: Clustering.xml:261 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<web-app>\n" +" ...\n" +" <listener>\n" +" <listener-class> org.jboss.portal.portlet.session.SessionListener </" +"listener-class>\n" +" </listener>\n" +" ...\n" +"</web-app>\n" +"]]>" +msgstr "" + +#. Tag: para +#: Clustering.xml:263 +#, no-c-format +msgid "Example web.xml" +msgstr "" + +#. Tag: programlisting +#: Clustering.xml:265 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<portlet-app>\n" +" ...\n" +" <portlet>\n" +" <portlet-name>YourPortlet</portlet-name>\n" +" ...\n" +" <session-config>\n" +" <distributed>true</distributed>\n" +" </session-config>\n" +" ...\n" +" </portlet>\n" +" ...\n" +"</portlet-app>\n" +"]]>" +msgstr "" + +#. Tag: para +#: Clustering.xml:267 +#, no-c-format +msgid "Configure YourPortlet to be replicated in jboss-portlet.xml" +msgstr "" + +#. Tag: title +#: Clustering.xml:271 +#, no-c-format +msgid "Limitations" +msgstr "" + +#. Tag: para +#: Clustering.xml:272 +#, no-c-format +msgid "" +"As we noted above there are advantages as well as limitations to the " +"clustering configuration" +msgstr "" + +#. Tag: para +#: Clustering.xml:274 +#, no-c-format +msgid "" +"You can only replicate portlet scoped attributes of a portlet. The main " +"reason of this is to keep consistency with the session state. If accessing a " +"portlet would trigger replication of application scoped attribute during the " +"rendering of a page then another portlet on the same page could use this " +"attribute for generating its markup. Then the state seen by this second " +"portlet would not necessarily be the same depending on the order in which " +"the portlets on this page are rendered." +msgstr "" + +#. Tag: para +#: Clustering.xml:279 +#, no-c-format +msgid "" +"Mutable objects need an explicit call to <emphasis>setAttribute(String name, " +"Object value)</emphasis> on the portlet session object in order to trigger " +"replication by the container." +msgstr "" + +#. Tag: programlisting +#: Clustering.xml:283 +#, no-c-format +msgid "" +"<![CDATA[\n" +"public void processAction(ActionRequest req, ActionResponse resp)\n" +" throws PortletException, IOException\n" +"{\n" +" ...\n" +" if (\"addItem\".equals(action))\n" +" {\n" +" PortletSession session = req.getPortletSession();\n" +" ShoppingCart cart = (PortletSession)session.getAttribute(\"cart\");\n" +" cart.addItem(item);\n" +"\n" +" // Perform an explicit set in order to signal to the container that " +"the object\n" +" // state has changed\n" +" session.setAttribute(\"cart\", cart);\n" +" }\n" +" ...\n" +"}\n" +"]]>" +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Common_Content/Feedback.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Common_Content/Feedback.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Common_Content/Feedback.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,61 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Feedback.xml:6 +#, no-c-format +msgid "We Need Feedback!" +msgstr "" + +#. Tag: primary +#: Feedback.xml:8 +#, no-c-format +msgid "feedback" +msgstr "" + +#. Tag: secondary +#: Feedback.xml:9 +#, no-c-format +msgid "contact information for this manual" +msgstr "" + +#. Tag: para +#: Feedback.xml:11 +#, no-c-format +msgid "" +"If you find a typographical error in this manual, or if you have thought of " +"a way to make this manual better, we would love to hear from you! Please " +"submit a report in Bugzilla: <ulink url=\"http://bugzilla.redhat.com/" +"bugzilla/\">http://bugzilla.redhat.com/bugzilla/</ulink> against the product " +"<application>&PRODUCT;.</application>" +msgstr "" + +#. Tag: para +#: Feedback.xml:14 +#, no-c-format +msgid "" +"When submitting a bug report, be sure to mention the manual&#39;s " +"identifier: <citetitle>&BOOKID;</citetitle>" +msgstr "" + +#. Tag: para +#: Feedback.xml:17 +#, no-c-format +msgid "" +"If you have a suggestion for improving the documentation, try to be as " +"specific as possible when describing it. If you have found an error, please " +"include the section number and some of the surrounding text so we can find " +"it easily." +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Common_Content/Legal_Notice.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Common_Content/Legal_Notice.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Common_Content/Legal_Notice.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,65 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: para +#: Legal_Notice.xml:6 +#, no-c-format +msgid "" +"Copyright <trademark class=\"copyright\"></trademark> &YEAR; &HOLDER;. This " +"material may only be distributed subject to the terms and conditions set " +"forth in the Creative Commons Attribution-Noncommercial-Share Alike 3.0 " +"Unported License (which is presently available at <ulink url=\"http://" +"creativecommons.org/licenses/by-nc-sa/3.0/\">http://creativecommons.org/" +"licenses/by-nc-sa/3.0/</ulink>)." +msgstr "" + +#. Tag: para +#: Legal_Notice.xml:9 +#, no-c-format +msgid "" +"Red Hat and the Red Hat \"Shadow Man\" logo are registered trademarks of Red " +"Hat, Inc. in the United States and other countries." +msgstr "" + +#. Tag: para +#: Legal_Notice.xml:12 +#, no-c-format +msgid "" +"All other trademarks referenced herein are the property of their respective " +"owners." +msgstr "" + +#. Tag: para +#: Legal_Notice.xml:15 +#, no-c-format +msgid "The GPG fingerprint of the security(a)redhat.com key is:" +msgstr "" + +#. Tag: para +#: Legal_Notice.xml:18 +#, no-c-format +msgid "CA 20 86 86 2B D6 9D FC 65 F6 EC C4 21 91 80 CD DB 42 A6 0E" +msgstr "" + +#. Tag: address +#: Legal_Notice.xml:22 +#, no-c-format +msgid "" +"<street>1801 Varsity Drive</street> <city>Raleigh</city>, <state>NC</state> " +"<postcode>27606-2072</postcode><country>USA</country><phone>Phone: +1 919 " +"754 3700</phone> <phone>Phone: 888 733 4281</phone> <fax>Fax: +1 919 754 " +"3701</fax> <pob>PO Box 13588</pob><city>Research Triangle Park</city>, " +"<state>NC</state> <postcode>27709</postcode><country>USA</country>" +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Configuration.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Configuration.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Configuration.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,561 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Configuration.xml:5 +#, no-c-format +msgid "Customizing your Installation" +msgstr "" + +#. Tag: para +#: Configuration.xml:6 +#, no-c-format +msgid "" +"This chapter describes how to customize the default installation. This " +"includes the JBoss EAP listening port, email and proxy settings, and " +"database dialect settings. For further configuration details, refer to <xref " +"linkend=\"portaldescriptors\"/> and <xref linkend=\"troubleshooting\"/>." +msgstr "" + +#. Tag: title +#: Configuration.xml:10 +#, no-c-format +msgid "Choosing server Configuration" +msgstr "" + +#. Tag: para +#: Configuration.xml:13 +#, no-c-format +msgid "" +"In rest of the document, you will see several references of <filename>" +"$JBOSS_HOME/server/production/</filename>. This also applies to <filename>" +"$JBOSS_HOME/server/default/</filename> as well as <filename>$JBOSS_HOME/" +"server/all/</filename>" +msgstr "" + +#. Tag: title +#: Configuration.xml:20 +#, no-c-format +msgid "Changing the Port" +msgstr "" + +#. Tag: para +#: Configuration.xml:21 +#, no-c-format +msgid "" +"It is common for web services to run on port 80. By default, JBoss EAP and " +"JBoss AS use port 8080. If you can not use <ulink url=\"http://wiki.jboss." +"org/wiki/Wiki.jsp?page=UsingPortForwardingWithJBoss\">port forwarding</" +"ulink>, it is recommended to change the port JBoss EAP or JBoss AS listens " +"on. To change the default port, open the <filename>$JBOSS_HOME/server/" +"production/deploy/jboss-web.deployer/server.xml</filename> file, and edit " +"the <computeroutput>Connector port</computeroutput> value for the " +"<computeroutput>jboss.web</computeroutput> service; however, this " +"configuration only applies to Apache Tomcat:" +msgstr "" + +#. Tag: programlisting +#: Configuration.xml:29 +#, no-c-format +msgid "" +"&lt;Service name=\"jboss.web\"&gt;\n" +"&lt;Connector port=\"8088\" address=\"${jboss.bind.address}\"" +msgstr "" + +#. Tag: para +#: Configuration.xml:30 +#, no-c-format +msgid "" +"This example changes the default port to port 8088. The JBoss EAP or JBoss " +"AS server must be restarted before the new port settings take affect." +msgstr "" + +#. Tag: para +#: Configuration.xml:33 +#, no-c-format +msgid "" +"The default SSL port is 8843. To enable HTTPS support, refer to the <ulink " +"url=\"http://docs.jboss.org/jbossas/jboss4guide/r4/html/ch9.chapt." +"html#d0e21962\">JBoss AS Guide</ulink>. For further information, refer to " +"the <ulink url=\"http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html" +"\">Apache Tomcat SSL configuration how-to</ulink>." +msgstr "" + +#. Tag: title +#: Configuration.xml:38 +#, no-c-format +msgid "Changing/Adding a connector" +msgstr "" + +#. Tag: para +#: Configuration.xml:39 +#, no-c-format +msgid "" +"When adding or changing a JBoss Web connector make sure to keep " +"<emphasis>emptySessionPath=\"true\"</emphasis> which is required for the " +"portal to work correctly" +msgstr "" + +#. Tag: para +#: Configuration.xml:42 +#, no-c-format +msgid "" +"Please refer to <xref linkend=\"wsrp-ports\"/> to update the WSRP service " +"after having changed the port." +msgstr "" + +#. Tag: title +#: Configuration.xml:47 +#, no-c-format +msgid "Root User Privileges" +msgstr "" + +#. Tag: para +#: Configuration.xml:48 +#, no-c-format +msgid "" +"Linux operating systems require root user privileges to run a service on a " +"port less than 1024. Starting JBoss EAP on port 80 as a non-privileged user " +"will not work. Running JBoss EAP as the root user could lead to security " +"breaches." +msgstr "" + +#. Tag: title +#: Configuration.xml:55 +#, no-c-format +msgid "Changing the Context Path" +msgstr "" + +#. Tag: para +#: Configuration.xml:56 +#, no-c-format +msgid "" +"By default, the main JBoss Portal page is accessible by navigating to " +"<emphasis>http://localhost:8080/portal/index.html</emphasis>. This can be " +"changed to a different path, for example, <emphasis>http://localhost:8080/" +"index.html</emphasis>. The context path can be changed when using the " +"deployed <filename>jboss-portal.sar/</filename>, or before building from " +"source. To change the context path when using the JBoss Portal binary " +"package:" +msgstr "" + +#. Tag: para +#: Configuration.xml:63 +#, no-c-format +msgid "" +"Open the <emphasis>$JBOSS_HOME/server/default/deploy/jboss-portal.sar/portal-" +"server.war/WEB-INF/jboss-web.xml</emphasis> file. If this file does not " +"exist, copy and save the following example:" +msgstr "" + +#. Tag: programlisting +#: Configuration.xml:65 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<?xml version=\"1.0\"?>\n" +"<jboss-web>\n" +" <security-domain>java:jaas/portal</security-domain>\n" +" <context-root>/portal</context-root>\n" +" <replication-config>\n" +" <replication-trigger>SET</replication-trigger>\n" +" </replication-config>\n" +" <resource-ref>\n" +" <res-ref-name>jdbc/PortalDS</res-ref-name>\n" +" <jndi-name>java:PortalDS</jndi-name>\n" +" </resource-ref>\n" +"</jboss-web>]]>" +msgstr "" + +#. Tag: para +#: Configuration.xml:68 +#, no-c-format +msgid "" +"Edit the <computeroutput>&lt;context-root&gt;</computeroutput> element with " +"the desired context path:" +msgstr "" + +#. Tag: programlisting +#: Configuration.xml:71 +#, no-c-format +msgid "<![CDATA[<context-root>/testing</context-root>]]>" +msgstr "" + +#. Tag: para +#: Configuration.xml:72 Configuration.xml:93 +#, no-c-format +msgid "" +"Using this example, the main JBoss Portal page would be reached by " +"navigating to <emphasis>http://localhost:8080/testing</emphasis>." +msgstr "" + +#. Tag: para +#: Configuration.xml:78 +#, no-c-format +msgid "To change the context path when building from source:" +msgstr "" + +#. Tag: para +#: Configuration.xml:84 +#, no-c-format +msgid "" +"Change into the directory where the <filename>JBoss Portal Source Code</" +"filename> ZIP file was extracted to, or where the source from SVN was " +"checked out to. Copy the <filename>build/etc/local.properties-example</" +"filename> file and save it as <filename>build/local.properties</filename>." +msgstr "" + +#. Tag: para +#: Configuration.xml:89 +#, no-c-format +msgid "" +"Open the <filename>build/local.properties</filename> file and edit the " +"<computeroutput>portal.web.context-root</computeroutput> option with the " +"desired context path:" +msgstr "" + +#. Tag: programlisting +#: Configuration.xml:92 +#, no-c-format +msgid "" +"# Context root for the portal main servlet\n" +"portal.web.context-root=/testing" +msgstr "" + +#. Tag: para +#: Configuration.xml:99 +#, no-c-format +msgid "" +"To clean the project, make sure you are connected to the Internet, and " +"change into the <filename>build/</filename> directory. Run the <command>ant " +"clean</command> command." +msgstr "" + +#. Tag: title +#: Configuration.xml:111 +#, no-c-format +msgid "Changing the context-root" +msgstr "" + +#. Tag: para +#: Configuration.xml:112 +#, no-c-format +msgid "" +"By default, Apache Tomcat holds on to the root context, <emphasis>/</" +"emphasis>. You may need to remove the <filename>$JBOSS_HOME/server/default/" +"deploy/jboss-web.deployer/ROOT.war/</filename> directory, or add a " +"<filename>jboss-web.xml</filename> file, which declares another context-root " +"other than <emphasis>/</emphasis>, under the <filename>$JBOSS_HOME/server/" +"default/deploy/jboss-web.deployer/ROOT.war/WEB-INF/</filename> directory, " +"for the above changes to take affect. The following is an example " +"<filename>jboss-web.xml</filename> file, which changes the Apache Tomcat " +"context path to <computeroutput>/tomcat-root</computeroutput>:" +msgstr "" + +#. Tag: programlisting +#: Configuration.xml:117 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<?xml version=\"1.0\"?>\n" +"<jboss-web>\n" +" <context-root>/tomcat-root</context-root>\n" +"</jboss-web>]]>" +msgstr "" + +#. Tag: title +#: Configuration.xml:121 +#, no-c-format +msgid "Forcing the Database Dialect" +msgstr "" + +#. Tag: para +#: Configuration.xml:122 +#, no-c-format +msgid "" +"This sections describes how to override the Database (DB) dialect settings. " +"Under most circumstances, the auto-detect feature works. If the Hibernate " +"dialect is not working correctly, override the default behavior by following " +"the instructions in this section." +msgstr "" + +#. Tag: title +#: Configuration.xml:126 +#, no-c-format +msgid "Database Dialect Settings for JBoss Portal" +msgstr "" + +#. Tag: para +#: Configuration.xml:127 +#, no-c-format +msgid "" +"All <filename>hibernate.cfg.xml</filename> files in all JBoss Portal modules " +"you intend to use need to be modified. The <filename>hibernate.cfg.xml</" +"filename> files are found in the <filename>jboss-portal.sar/" +"<replaceable>module</replaceable>/conf/hibernate/<replaceable>directory</" +"replaceable>/</filename> directory, where <replaceable>module</replaceable> " +"is the module name, and <replaceable>directory</replaceable> is a directory " +"that, depending on the module, may or may not exist." +msgstr "" + +#. Tag: para +#: Configuration.xml:130 +#, no-c-format +msgid "" +"To modify these files to force the DB dialect, un-comment the following line " +"from each <filename>hibernate.cfg.xml</filename> file in each JBoss Portal " +"module you intend to use, so that it looks like the following:" +msgstr "" + +#. Tag: programlisting +#: Configuration.xml:133 Configuration.xml:154 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!-- Force the dialect instead of using autodetection -->\n" +"<property name=\"dialect\">org.hibernate.dialect.PostgreSQLDialect</" +"property>\n" +"]]>" +msgstr "" + +#. Tag: para +#: Configuration.xml:134 Configuration.xml:159 +#, no-c-format +msgid "" +"Note: this example is for a PostgreSQL database. If you use another " +"database, you need to modify <computeroutput>org.hibernate.dialect." +"PostgreSQLDialect</computeroutput> to reflect the correct database. For a " +"list of supported dialects, refer to the <ulink url=\"http://www.hibernate." +"org/hib_docs/v3/reference/en/html/session-configuration.html#configuration-" +"optional-dialects\">dialects list on the Hibernate website</ulink>." +msgstr "" + +#. Tag: title +#: Configuration.xml:139 +#, no-c-format +msgid "DB Dialect Settings for the CMS Component" +msgstr "" + +#. Tag: para +#: Configuration.xml:140 +#, no-c-format +msgid "To modify the DB dialect setting for the JBoss Portal CMS component:" +msgstr "" + +#. Tag: para +#: Configuration.xml:146 +#, no-c-format +msgid "" +"Open the <filename>jboss-portal.sar/portal-cms.sar/conf/hibernate/cms/" +"hibernate.cfg.xml</filename> file." +msgstr "" + +#. Tag: para +#: Configuration.xml:151 +#, no-c-format +msgid "Un-comment the following line, so that it looks as follows:" +msgstr "" + +#. Tag: title +#: Configuration.xml:165 +#, no-c-format +msgid "Configuring the Email Service" +msgstr "" + +#. Tag: para +#: Configuration.xml:166 +#, no-c-format +msgid "" +"If you have a standard setup and a mail server installed, the email service " +"should work without any extra configuration. Most Linux distributions have a " +"mail server installed by default. The email service, for example, can be " +"used to verify a user's email address when a user subscribes, or for CMS " +"workflow notifications." +msgstr "" + +#. Tag: para +#: Configuration.xml:169 +#, no-c-format +msgid "" +"The email service is configured using the <filename>$JBOSS_HOME/server/" +"default/deploy/jboss-portal.sar/META-INF/jboss-service.xml</filename> file. " +"The following is an example of the section which is used to configure the " +"email service:" +msgstr "" + +#. Tag: programlisting +#: Configuration.xml:172 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<mbean\n" +"code=\"org.jboss.portal.core.impl.mail.MailModuleImpl\"\n" +"name=\"portal:service=Module,type=Mail\"\n" +"xmbean-dd=\"\"\n" +"xmbean-code=\"org.jboss.portal.jems.as.system.JBossServiceModelMBean\">\n" +"<xmbean/>\n" +"<depends>jboss:service=Mail</depends>\n" +"<depends>portal:service=Module,type=IdentityServiceController</depends>\n" +"<attribute name=\"QueueCapacity\">-1</attribute>\n" +"<attribute name=\"Gateway\">localhost</attribute>\n" +"<attribute name=\"SmtpUser\"></attribute>\n" +"<attribute name=\"SmtpPassword\"></attribute>\n" +"<attribute name=\"JavaMailDebugEnabled\">false</attribute>\n" +"<attribute name=\"SMTPConnectionTimeout\">100000</attribute>\n" +"<attribute name=\"SMTPTimeout\">10000</attribute>\n" +"<attribute name=\"JNDIName\">java:portal/MailModule</attribute>\n" +"</mbean>]]>" +msgstr "" + +#. Tag: para +#: Configuration.xml:174 +#, no-c-format +msgid "" +"A different SMTP server (other than localhost) can be configured, along with " +"a SMTP username and an SMTP password. The following is an example " +"configuration that uses the Gmail SMTP server:" +msgstr "" + +#. Tag: programlisting +#: Configuration.xml:177 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<mbean\n" +"code=\"org.jboss.portal.core.impl.mail.MailModuleImpl\"\n" +"name=\"portal:service=Module,type=Mail\"\n" +"xmbean-dd=\"\"\n" +"xmbean-code=\"org.jboss.portal.jems.as.system.JBossServiceModelMBean\">\n" +"<xmbean/>\n" +"<depends>jboss:service=Mail</depends>\n" +"<depends>portal:service=Module,type=IdentityServiceController</depends>\n" +"<attribute name=\"QueueCapacity\">-1</attribute>\n" +"<attribute name=\"Gateway\">smtp.gmail.com</attribute>\n" +"<attribute name=\&quot;SmtpUser\&quot;&gt;username(a)gmail.com&lt;/attribute&gt;\n&quot; +"<attribute name=\"SmtpPassword\">myPassword</attribute>\n" +"<attribute name=\"JavaMailDebugEnabled\">false</attribute>\n" +"<attribute name=\"SMTPConnectionTimeout\">100000</attribute>\n" +"<attribute name=\"SMTPTimeout\">10000</attribute>\n" +"<attribute name=\"JNDIName\">java:portal/MailModule</attribute>\n" +"</mbean>]]>" +msgstr "" + +#. Tag: para +#: Configuration.xml:178 +#, no-c-format +msgid "" +"Using this example, replace <computeroutput&gt;username(a)gmail.com&lt;/&quot; +"computeroutput> and <computeroutput>myPassword</computeroutput> with your " +"correct Gmail username and password." +msgstr "" + +#. Tag: title +#: Configuration.xml:183 +#, no-c-format +msgid "Configuring proxy settings" +msgstr "" + +#. Tag: para +#: Configuration.xml:184 +#, no-c-format +msgid "" +"There are a couple of scenarios where you need your proxy to be correctly " +"defined at the <trademark class=\"trade\">JVM</trademark> level so that you " +"can access documents from Internet. It could be to get the thirdparty " +"libraries if you decided to build JBoss Portal from the sources, to access " +"RSS feeds or weather information in the samples portlet we provide or for " +"your own needs." +msgstr "" + +#. Tag: para +#: Configuration.xml:185 +#, no-c-format +msgid "" +"To configure the proxy settings, you need to know the proxy host and the " +"port to use. Then, add them when starting Java." +msgstr "" + +#. Tag: para +#: Configuration.xml:187 +#, no-c-format +msgid "" +"Usually setting up JAVA_OPTS environment variable to <literal>-Dhttp." +"proxyHost=YOUR_PROXY_HOST -Dhttp.proxyPort=YOUR_PROXY_PORT</literal> is " +"enough." +msgstr "" + +#. Tag: para +#: Configuration.xml:190 +#, no-c-format +msgid "" +"If the proxy requires authentication, it is also possible to pass username " +"and password by specifying those additional parameters: <literal>-Dhttp." +"proxyUser=MYUSERNAME -Dhttp.proxyPassword=MYPASSWORD</literal>" +msgstr "" + +#. Tag: title +#: Configuration.xml:194 +#, no-c-format +msgid "Disabling Dynamic Proxy Un-wrapping" +msgstr "" + +#. Tag: para +#: Configuration.xml:195 +#, no-c-format +msgid "" +"JBoss Portal uses the JBoss Microkernel for the service infrastructure. The " +"JBoss Microkernel provides injection of services into other services, " +"otherwise known as wiring. Due to the Microkernel being <trademark class=" +"\"trade\">JMX</trademark> based, it is only possible to inject dynamic " +"proxies that talk to the MBeanServer. The overhead at runtime is minimal " +"since the Microkernel implementation is highly optimized; however, when it " +"is used with Java 5, a noticeable bottleneck occurs due to the fact that the " +"implementation of the JMX API classes, <emphasis>javax.management.*</" +"emphasis>, provided by the Java Platform, perform synchronization. This does " +"not occur under <trademark class=\"trade\">JDK</trademark> 1.4, since those " +"classes are implemented by JBoss MX." +msgstr "" + +#. Tag: para +#: Configuration.xml:197 +#, no-c-format +msgid "" +"JBoss Portal services use a special kind of Model MBean called " +"<emphasis>JBossServiceModelMBean</emphasis>, which allows the un-wrapping of " +"injected dynamic proxies, and replaces them with Plain Old Java Object " +"(POJO) services. This removes the bottleneck when using Java 5, and also " +"provides a performance boost on JDK 1.4. By default this feature is enabled, " +"but it is possible to disable. To do this on Linux operating systems, change " +"into the <filename>$JBOSS_HOME/bin/</filename> directory and run the " +"following command:" +msgstr "" + +#. Tag: programlisting +#: Configuration.xml:201 +#, no-c-format +msgid "sh run.sh -Dportal.kernel.no_proxies=false" +msgstr "" + +#. Tag: para +#: Configuration.xml:203 +#, no-c-format +msgid "On Windows, run the following command:" +msgstr "" + +#. Tag: programlisting +#: Configuration.xml:207 +#, no-c-format +msgid "run.bat -Dportal.kernel.no_proxies=false" +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Content_Integration.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Content_Integration.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Content_Integration.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,806 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Content_Integration.xml:16 +#, no-c-format +msgid "Content Integration" +msgstr "" + +#. Tag: para +#: Content_Integration.xml:17 +#, no-c-format +msgid "" +"Since JBoss Portal 2.6 it is possible to provide an easy integration of " +"content within the portal. Up to the 2.4 version content integration had to " +"be done by configuring a portlet to show some content from an URI and then " +"place that portlet on a page. The new content integration capabilities " +"allows to directly configure a page window with the content URI by removing " +"the need to configure a portlet for that purpose." +msgstr "" + +#. Tag: title +#: Content_Integration.xml:21 Content_Integration.xml:206 +#, no-c-format +msgid "Note" +msgstr "" + +#. Tag: para +#: Content_Integration.xml:21 +#, no-c-format +msgid "" +"We do not advocate to avoid the usage portlet preferences, we rather " +"advocate that content configuration managed at the portal level simplifies " +"the configuration: it helps to make content a first class citizen of the " +"portal instead of having an intermediary portlet that holds the content for " +"the portal. The portlet preferences can still be used to configure how " +"content is displayed to the user." +msgstr "" + +#. Tag: para +#: Content_Integration.xml:31 +#, no-c-format +msgid "The portal uses portlets to configure content" +msgstr "" + +#. Tag: para +#: Content_Integration.xml:39 +#, no-c-format +msgid "" +"The portal references directly the content and use portlet to interact with " +"content" +msgstr "" + +#. Tag: title +#: Content_Integration.xml:42 +#, no-c-format +msgid "Window content" +msgstr "" + +#. Tag: para +#: Content_Integration.xml:43 +#, no-c-format +msgid "The content of a window is defined by" +msgstr "" + +#. Tag: para +#: Content_Integration.xml:45 +#, no-c-format +msgid "" +"The content URI which is the resource that the window is pointing to. It is " +"an arbitrary string that the portal cannot interpret and is left up to the " +"content provider to interpret." +msgstr "" + +#. Tag: para +#: Content_Integration.xml:47 +#, no-c-format +msgid "" +"The window content type which defines how the portal interpret the window " +"content" +msgstr "" + +#. Tag: para +#: Content_Integration.xml:49 +#, no-c-format +msgid "" +"The default content type is for portlets and has the value " +"<emphasis>portlet</emphasis>. In this case the content URI is the portlet " +"instance id." +msgstr "" + +#. Tag: para +#: Content_Integration.xml:51 +#, no-c-format +msgid "" +"The CMS content type allows to integrate content from the CMS at the page " +"and it has the value <emphasis>cms</emphasis>. For that content type, the " +"content URI is the CMS file path." +msgstr "" + +#. Tag: para +#: Content_Integration.xml:55 +#, no-c-format +msgid "" +"The content parameters which are a set of additional key/value string pairs " +"holding state that is interpreted by the content provider." +msgstr "" + +#. Tag: para +#: Content_Integration.xml:59 +#, no-c-format +msgid "" +"At runtime when the portal needs to render a window it delegates the " +"production of markup to a content provider. The portal comes with a " +"preconfigured set of providers which handles the portlet and the cms content " +"types. The most natural way to plug a content provider in the portal is to " +"use a JSR 286 Portlet. Based on a few carefully chosen conventions it is " +"possible to provide an efficient content integration with the benefit of " +"using standards and without requiring the usage of a proprietary API." +msgstr "" + +#. Tag: title +#: Content_Integration.xml:66 +#, no-c-format +msgid "Content customization" +msgstr "" + +#. Tag: para +#: Content_Integration.xml:67 +#, no-c-format +msgid "" +"Content providers must be able to allow the user or administrator to chose " +"content from the external resource it integrates in the portal in order to " +"properly configure a portal window. A few interactions between the portal, " +"the content provider and the portal user are necessary to achieve that goal. " +"Here again it is possible to provide content customization using a JSR 286 " +"Portlet. For that purpose two special portlet modes called " +"<emphasis>edit_content</emphasis> and <emphasis>select_content</emphasis> " +"has been introduced. It signals to the portlet that it is selecting or " +"editing the content portion of the state of a portlet. " +"<emphasis>select_content</emphasis> is used to select a new content to put " +"in a window while <emphasis>edit_content</emphasis> is used to modify the " +"previously defined content, often the two modes will display the same thing. " +"The traditional edit mode is not used because the edit mode is more targeted " +"to configure how the portlet shows content to the end user rather than what " +"content it shows." +msgstr "" + +#. Tag: para +#: Content_Integration.xml:81 +#, no-c-format +msgid "Example of content customization - CMS Portlet" +msgstr "" + +#. Tag: title +#: Content_Integration.xml:84 +#, no-c-format +msgid "Content Driven Portlet" +msgstr "" + +#. Tag: para +#: Content_Integration.xml:85 +#, no-c-format +msgid "" +"Portlet components are used to integrate content into the portal. It relies " +"on a few conventions which allow the portal and the portlet to communicate." +msgstr "" + +#. Tag: title +#: Content_Integration.xml:89 +#, no-c-format +msgid "Displaying content" +msgstr "" + +#. Tag: para +#: Content_Integration.xml:90 +#, no-c-format +msgid "" +"At runtime the portal will call the portlet with the view mode when it " +"displays content. It will send information about the content to display " +"using the public render parameter <emphasis>urn:jboss:portal:content uri</" +"emphasis> to the portlet. Therefore the portlet has just to read the render " +"parameters and use them to properly display the content in the portlet. The " +"public render parameters values are the key/value pairs that form the " +"content properties and the resource URI of the content to display." +msgstr "" + +#. Tag: title +#: Content_Integration.xml:96 +#, no-c-format +msgid "Configuring content" +msgstr "" + +#. Tag: para +#: Content_Integration.xml:97 +#, no-c-format +msgid "" +"As explained before, the portal will call the portlet using the " +"<emphasis>edit_content</emphasis> mode. In that mode the portlet and the " +"portal will communicate using either action or render parameters. We have " +"two use cases which are:" +msgstr "" + +#. Tag: para +#: Content_Integration.xml:101 +#, no-c-format +msgid "" +"The portal needs to configure a new content item for a new window. In that " +"use case the portal will not send special render parameters to the portlet " +"and the initial set of render parameters will be empty. The portlet can then " +"use render parameters in order to provide navigation in the content " +"repository. For example the portlet can navigate the CMS tree and store the " +"current CMS path in the render parameters. Whenever the portlet has decided " +"to tell the portal that content has been selected by the user it needs to " +"trigger a JSR-286 event with the uri and eventual parameters as payload." +msgstr "" + +#. Tag: para +#: Content_Integration.xml:107 +#, no-c-format +msgid "" +"The second use case happens when the portal needs to edit existing content. " +"In such situation everything works as explained before except that the " +"initial set of render parameters of the portlet will be prepopulated with " +"the content uri URI and parameters." +msgstr "" + +#. Tag: title +#: Content_Integration.xml:114 +#, no-c-format +msgid "Step by step example of a content driven portlet" +msgstr "" + +#. Tag: title +#: Content_Integration.xml:117 +#, no-c-format +msgid "The Portlet skeleton" +msgstr "" + +#. Tag: para +#: Content_Integration.xml:118 +#, no-c-format +msgid "" +"Here is the base skeleton of the content portlet. The FSContentDrivenPortlet " +"shows the files which are in the war file in which the portlet is deployed. " +"The arbitrary name <emphasis>filesystem</emphasis> will be the content type " +"interpreted by the portlet." +msgstr "" + +#. Tag: programlisting +#: Content_Integration.xml:122 +#, no-c-format +msgid "" +"<![CDATA[\n" +"public class FSContentDrivenPortlet extends GenericPortlet\n" +"{\n" +"\n" +" /** The edit_content mode. */\n" +" public static final PortletMode EDIT_CONTENT_MODE = new PortletMode" +"(\"edit_content\");\n" +"\n" +" ...\n" +"\n" +"}\n" +"]]>" +msgstr "" + +#. Tag: title +#: Content_Integration.xml:125 +#, no-c-format +msgid "Overriding the dispatch method" +msgstr "" + +#. Tag: para +#: Content_Integration.xml:126 +#, no-c-format +msgid "" +"First the <emphasis>doDispatch(RenderRequest req, RenderResponse resp)</" +"emphasis> is overridden in order to branch the request flow to a method that " +"will take care of displaying the editor." +msgstr "" + +#. Tag: programlisting +#: Content_Integration.xml:128 +#, no-c-format +msgid "" +"<![CDATA[\n" +"protected void doDispatch(RenderRequest req, RenderResponse resp)\n" +" throws PortletException, PortletSecurityException, " +"IOException\n" +"{\n" +" if (EDIT_CONTENT_MODE.equals(req.getPortletMode()))\n" +" {\n" +" doEditContent(req, resp);\n" +" }\n" +" else\n" +" {\n" +" super.doDispatch(req, resp);\n" +" }\n" +"}\n" +"]]>" +msgstr "" + +#. Tag: title +#: Content_Integration.xml:131 +#, no-c-format +msgid "Utilities methods" +msgstr "" + +#. Tag: para +#: Content_Integration.xml:132 +#, no-c-format +msgid "" +"The portlet also needs a few utilities methods which take care of converting " +"content URI to a file back and forth. There is also an implementation of a " +"file filter that keep only text files and avoid the WEB-INF directory of the " +"war file for security reasons." +msgstr "" + +#. Tag: programlisting +#: Content_Integration.xml:135 +#, no-c-format +msgid "" +"<![CDATA[\n" +"protected File getFile(String contentURI) throws IOException\n" +"{\n" +" String realPath = getPortletContext().getRealPath(contentURI);\n" +" if (realPath == null)\n" +" {\n" +" throw new IOException(\"Cannot access war file content\");\n" +" }\n" +" File file = new File(realPath);\n" +" if (!file.exists())\n" +" {\n" +" throw new IOException(\"File \" + contentURI + \" does not exist\");\n" +" }\n" +" return file;\n" +"}\n" +"]]>" +msgstr "" + +#. Tag: programlisting +#: Content_Integration.xml:136 +#, no-c-format +msgid "" +"<![CDATA[\n" +" protected String getContentURI(File file) throws IOException\n" +" {\n" +" String rootPath = getPortletContext().getRealPath(\"/\");\n" +" if (rootPath == null)\n" +" {\n" +" throw new IOException(\"Cannot access war file content\");\n" +" }\n" +"\n" +" // Make it canonical\n" +" rootPath = new File(rootPath).getCanonicalPath();\n" +"\n" +" // Get the portion of the path that is significant for us\n" +" String filePath = file.getCanonicalPath();\n" +" return filePath.length() >=\n" +" rootPath.length() ? filePath.substring(rootPath.length()) : null;\n" +" }\n" +"]]>" +msgstr "" + +#. Tag: programlisting +#: Content_Integration.xml:137 +#, no-c-format +msgid "" +"<![CDATA[\n" +" private final FileFilter filter = new FileFilter()\n" +" {\n" +" public boolean accept(File file)\n" +" {\n" +" String name = file.getName();\n" +" if (file.isDirectory())\n" +" {\n" +" return !\"WEB-INF\".equals(name);\n" +" }\n" +" else if (file.isFile())\n" +" {\n" +" return name.endsWith(\".txt\");\n" +" }\n" +" else\n" +" {\n" +" return false;\n" +" }\n" +" }\n" +" };\n" +"]]>" +msgstr "" + +#. Tag: title +#: Content_Integration.xml:140 +#, no-c-format +msgid "The editor" +msgstr "" + +#. Tag: para +#: Content_Integration.xml:141 +#, no-c-format +msgid "" +"The editor is probably the longest part of the portlet. It tries to stay " +"simple though and goes directly to the point." +msgstr "" + +#. Tag: para +#: Content_Integration.xml:146 +#, no-c-format +msgid "Content editor of FSContentDrivenPortlet in action" +msgstr "" + +#. Tag: programlisting +#: Content_Integration.xml:147 +#, no-c-format +msgid "" +"<![CDATA[\n" +"protected void doEditContent(RenderRequest req, RenderResponse resp)\n" +" throws PortletException, PortletSecurityException, " +"IOException\n" +"{\n" +" String uri = req.getParameter(\"current_uri\");\n" +" if (uri == null)\n" +" {\n" +" // Get the uri value optionally provided by the portal\n" +" uri = req.getParameter(\"uri\");\n" +" }\n" +"\n" +" // Get the working directory directory\n" +" File workingDir = null;\n" +" String currentFileName = null;\n" +" if (uri != null)\n" +" {\n" +" workingDir = getFile(uri).getParentFile();\n" +" currentFileName = getFile(uri).getName();\n" +" }\n" +" else\n" +" {\n" +" // Otherwise try to get the current directory we are browsing,\n" +" // if no current dir exist we use the root\n" +" String currentDir = req.getParameter(\"current_dir\");\n" +" if (currentDir == null)\n" +" {\n" +" currentDir = \"/\";\n" +" }\n" +" workingDir = getFile(currentDir);\n" +" }\n" +"\n" +" // Get the parent path\n" +" String parentPath = getContentURI(workingDir.getParentFile());\n" +"\n" +" // Get the children of the selected file, we use a filter\n" +" // to retain only text files and avoid WEB-INF dir\n" +" File[] children = workingDir.listFiles(filter);\n" +"\n" +" // Configure the response\n" +" resp.setContentType(\"text/html\");\n" +" PrintWriter writer = resp.getWriter();\n" +"\n" +" //\n" +" writer.print(\"Directories:<br/>\");\n" +" writer.print(\"<ul>\");\n" +" PortletURL choseDirURL = resp.createRenderURL();\n" +" if (parentPath != null)\n" +" {\n" +" choseDirURL.setParameter(\"current_dir\", parentPath);\n" +" writer.print(\"<li><a href=\\\"\" + choseDirURL + \"\\\">..</a></li>" +"\");\n" +" }\n" +" for (int i = 0;i < children.length;i++)\n" +" {\n" +" File child = children[i];\n" +" if (child.isDirectory())\n" +" {\n" +" choseDirURL.setParameter(\"current_dir\", getContentURI(child));\n" +" writer.print(\"<li><a href=\\\"\" + choseDirURL + \"\\\">\" + child." +"getName() +\n" +" \"</a></li>\");\n" +" }\n" +" }\n" +" writer.print(\"</ul><br/>\");\n" +"\n" +" //\n" +" writer.print(\"Files:<br/>\");\n" +" writer.print(\"<ul>\");\n" +" PortletURL selectFileURL = resp.createActionURL();\n" +" selectFileURL.setParameter(\"content.action.select\", \"select\");\n" +" for (int i = 0;i < children.length;i++)\n" +" {\n" +" File child = children[i];\n" +" if (child.isFile())\n" +" {\n" +" selectFileURL.setParameter(\"current_uri\", getContentURI(child));\n" +" if (child.getName().equals(currentFileName))\n" +" {\n" +" writer.print(\"<li><b>\" + child.getName() + \"</b></li>\");\n" +" }\n" +" else\n" +" {\n" +" writer.print(\"<li><a href=\\\"\" + selectFileURL + \"\\\">\" + " +"child.getName() + \"</a></li>\");\n" +" }\n" +" }\n" +" }\n" +" writer.print(\"</ul><br/>\");\n" +"\n" +" //\n" +" writer.close();\n" +"}\n" +"]]>" +msgstr "" + +#. Tag: title +#: Content_Integration.xml:150 +#, no-c-format +msgid "Viewing content at runtime" +msgstr "" + +#. Tag: para +#: Content_Integration.xml:151 +#, no-c-format +msgid "" +"Last but not least the portlet needs to implement the <emphasis>doView" +"(RenderRequest req, RenderResponse resp)</emphasis> method in order to " +"display the file that the portal window wants to show." +msgstr "" + +#. Tag: programlisting +#: Content_Integration.xml:153 +#, no-c-format +msgid "" +"<![CDATA[\n" +"protected void doView(RenderRequest req, RenderResponse resp)\n" +" throws PortletException, PortletSecurityException, " +"IOException\n" +"{\n" +" // Get the URI provided by the portal\n" +" String uri = req.getParameter(\"uri\");\n" +"\n" +" // Configure the response\n" +" resp.setContentType(\"text/html\");\n" +" PrintWriter writer = resp.getWriter();\n" +"\n" +" //\n" +" if (uri == null)\n" +" {\n" +" writer.print(\"No selected file\");\n" +" }\n" +" else\n" +" {\n" +" File file = getFile(uri);\n" +" FileInputStream in = null;\n" +" try\n" +" {\n" +" in = new FileInputStream(file);\n" +" FileChannel channel = in.getChannel();\n" +" byte[] bytes = new byte[(int)channel.size()];\n" +" ByteBuffer buffer = ByteBuffer.wrap(bytes);\n" +" channel.read(buffer);\n" +" writer.write(new String(bytes, 0, bytes.length, \"UTF8\"));\n" +" }\n" +" catch (FileNotFoundException e)\n" +" {\n" +" writer.print(\"No such file \" + uri);\n" +" getPortletContext().log(\"Cannot find file \" + uri, e);\n" +" }\n" +" finally\n" +" {\n" +" if (in != null)\n" +" {\n" +" in.close();\n" +" }\n" +" }\n" +" }\n" +"\n" +" //\n" +" writer.close();\n" +"}\n" +"]]>" +msgstr "" + +#. Tag: title +#: Content_Integration.xml:156 +#, no-c-format +msgid "Hooking the portlet into the portal" +msgstr "" + +#. Tag: para +#: Content_Integration.xml:162 +#, no-c-format +msgid "" +"Management portlet with <emphasis>filesystem</emphasis> content type enabled" +msgstr "" + +#. Tag: para +#: Content_Integration.xml:164 +#, no-c-format +msgid "" +"Finally we need to make the portal aware of the fact that the portlet can " +"edit and interpret content. For that we need a few descriptors. The " +"<emphasis>portlet.xml</emphasis> descriptor will define our portlet, the " +"<emphasis>portlet-instances.xml</emphasis> will create a single instance of " +"our portlet. The <emphasis>web.xml</emphasis> descriptor will contain a " +"servlet context listener that will hook the content type in the portal " +"content type registry." +msgstr "" + +#. Tag: para +#: Content_Integration.xml:169 +#, no-c-format +msgid "" +"First, we need to define the portlet's particular event and render " +"parameters:" +msgstr "" + +#. Tag: programlisting +#: Content_Integration.xml:170 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" +"<portlet-app xmlns=\"http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd" +"\"\n" +" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n" +" xsi:schemaLocation=\"http://java.sun.com/xml/ns/portlet/portlet-" +"app_2_0.xsd http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd\"\n" +" version=\"2.0\">\n" +" \n" +" <portlet>\n" +" <description>File System Content Driven Portlet</description>\n" +" <portlet-name>FSContentDrivenPortlet</portlet-name>\n" +" <display-name>File System Content Driven Portlet</display-name>\n" +" <portlet-class>org.jboss.portal.core.samples.basic." +"FSContentDrivenPortlet</portlet-class>\n" +" <supports>\n" +" <mime-type>text/html</mime-type>\n" +" <portlet-mode>VIEW</portlet-mode>\n" +" <portlet-mode>EDIT_CONTENT</portlet-mode>\n" +" </supports>\n" +" <portlet-info>\n" +" <title>File Portlet</title>\n" +" <keywords>sample,test</keywords>\n" +" </portlet-info>\n" +" <supported-public-render-parameter>uri</supported-public-render-" +"parameter>\n" +" <supported-publishing-event xmlns:x=\"urn:jboss:portal:content\">x:" +"select</supported-publishing-event>\n" +" </portlet>\n" +"\n" +" <public-render-parameter>\n" +" <identifier>uri</identifier>\n" +" <qname xmlns:c=\"urn:jboss:portal:content\">c:uri</qname>\n" +" </public-render-parameter>\n" +"\n" +" <event-definition>\n" +" <qname xmlns:x=\"urn:jboss:portal:content\">x:select</qname>\n" +" <value-type>java.lang.String</value-type>\n" +" </event-definition>\n" +"\n" +"</portlet-app>\n" +"]]>" +msgstr "" + +#. Tag: para +#: Content_Integration.xml:171 +#, no-c-format +msgid "" +"Note that here we need to use a JSR-286 portlet, this portlet will use the " +"event <emphasis>urn:jboss:portal:content select</emphasis> and have a " +"payload of type <emphasis>java.lang.String</emphasis>. This event will be " +"used to tell the portal the URI selected by the user. This same portlet will " +"also be in charge of rendering the content based on that URI, it will then " +"also need to access the public render parameter qualified with the name: " +"<emphasis>urn:jboss:portal:content uri</emphasis>." +msgstr "" + +#. Tag: para +#: Content_Integration.xml:175 +#, no-c-format +msgid "The portlet.xml descriptor" +msgstr "" + +#. Tag: programlisting +#: Content_Integration.xml:176 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<deployments>\n" +" ...\n" +" <deployment>\n" +" <instance>\n" +" <instance-id>FSContentDrivenPortletInstance</instance-id>\n" +" <portlet-ref>FSContentDrivenPortlet</portlet-ref>\n" +" </instance>\n" +" </deployment>\n" +" ...\n" +"</deployments\n" +"]]>" +msgstr "" + +#. Tag: para +#: Content_Integration.xml:177 +#, no-c-format +msgid "The portlet-instances.xml descriptor" +msgstr "" + +#. Tag: programlisting +#: Content_Integration.xml:178 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<web-app>\n" +" ...\n" +" <context-param>\n" +" <param-name>org.jboss.portal.content_type</param-name>\n" +" <param-value>filesystem</param-value>\n" +" </context-param>\n" +" <context-param>\n" +" <param-name>org.jboss.portal.portlet_instance</param-name>\n" +" <param-value>FSContentDrivenPortletInstance</param-value>\n" +" </context-param>\n" +" <listener>\n" +" <listener-class>org.jboss.content.ContentTypeRegistration</listener-" +"class>\n" +" </listener>\n" +" ...\n" +"</web-app>\n" +"]]>" +msgstr "" + +#. Tag: para +#: Content_Integration.xml:179 +#, no-c-format +msgid "The web.xml descriptor" +msgstr "" + +#. Tag: title +#: Content_Integration.xml:180 +#, no-c-format +msgid "Caution" +msgstr "" + +#. Tag: para +#: Content_Integration.xml:180 +#, no-c-format +msgid "" +"You don't need to add the listener class into your war file. As it is " +"provided by the portal it will always be available." +msgstr "" + +#. Tag: title +#: Content_Integration.xml:196 +#, no-c-format +msgid "Configuring window content in deployment descriptor" +msgstr "" + +#. Tag: para +#: Content_Integration.xml:197 +#, no-c-format +msgid "" +"How to create a portlet that will enable configuration of content at runtime " +"has been covered above, however it is also possible to configure content in " +"deployment descriptors. With our previous example it would give the " +"following snippet placed in a <emphasis>*-portal.xml</emphasis> file:" +msgstr "" + +#. Tag: programlisting +#: Content_Integration.xml:201 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<window>\n" +"<window-name>MyWindow</window-name>\n" +"<content>\n" +" <content-type>filesystem</content-type>\n" +" <content-uri>/dir1/foo.txt</content-uri>\n" +"</content>\n" +"<region>center</region>\n" +"<height>1</height>\n" +"</window>\n" +"]]>" +msgstr "" + +#. Tag: para +#: Content_Integration.xml:205 +#, no-c-format +msgid "Final effect - portal window with FSContentDrivenPortlet" +msgstr "" + +#. Tag: para +#: Content_Integration.xml:206 +#, no-c-format +msgid "How to configure CMS file this way is covered in the CMS chapter:" +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Coordination.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Coordination.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Coordination.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,289 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Coordination.xml:12 +#, no-c-format +msgid "JBoss Portal Explicit Coordination" +msgstr "" + +#. Tag: title +#: Coordination.xml:14 +#, no-c-format +msgid "Explicit vs implicit coordination" +msgstr "" + +#. Tag: para +#: Coordination.xml:15 +#, no-c-format +msgid "" +"Portlet 2.0 coordination features are mediated by the portal between several " +"portlet windows, therefore the portal at runtime needs to be able to define " +"relationships between windows. Relationship can be established from an " +"implicit model (i.e a set of predicates applied on some state that will " +"answer TRUE/FALSE to the question are the portlet windows foo and bar in a " +"relationship) or from an explicit model (that states that foo and bar have a " +"relationship). The implicit model is very good for defining default " +"configuration as it does not require much configuration but is not able to " +"cover the exceptional case, that's why we need to combine it with an " +"explicit model that will take precedence over the implicit model, it is the " +"well known principle of convention over configuration." +msgstr "" + +#. Tag: para +#: Coordination.xml:27 +#, no-c-format +msgid "" +"Similar to implicit Coordination, currently all explicit coordination " +"happens only in the scope of the same page." +msgstr "" + +#. Tag: title +#: Coordination.xml:32 +#, no-c-format +msgid "Bindings and wirings" +msgstr "" + +#. Tag: title +#: Coordination.xml:35 +#, no-c-format +msgid "Event wiring" +msgstr "" + +#. Tag: para +#: Coordination.xml:37 +#, no-c-format +msgid "" +"Wires JSR-286 events. With implicit wirings the event producer and the " +"consumer declares the same event namespace and local name to get event " +"delivered in the scope of the same page. With explicit wiring any pairs of " +"Window:Event can be connected." +msgstr "" + +#. Tag: title +#: Coordination.xml:45 +#, no-c-format +msgid "Parameter binding" +msgstr "" + +#. Tag: para +#: Coordination.xml:47 +#, no-c-format +msgid "" +"Binds JSR-286 shared parameters. With implicit binding parameters with the " +"same public name are shared. With explicit binding any public parameters can " +"share values. Windows for which such binding applies are explicitly defined." +msgstr "" + +#. Tag: title +#: Coordination.xml:54 +#, no-c-format +msgid "Alias binding" +msgstr "" + +#. Tag: para +#: Coordination.xml:56 +#, no-c-format +msgid "" +"Explicit alias binding define a name of page scoped parameter that will " +"apply value to specified portlet windows public parameters." +msgstr "" + +#. Tag: programlisting +#: Coordination.xml:61 +#, no-c-format +msgid "" +"<![CDATA[http://localhost:8080/portal/portal/default/Coordination+Samples?" +"aliasBinding1=someValue]]>" +msgstr "" + +#. Tag: title +#: Coordination.xml:65 +#, no-c-format +msgid "Coordination configuration" +msgstr "" + +#. Tag: para +#: Coordination.xml:67 +#, no-c-format +msgid "" +"Configuration takes place in -object.xml file. The &lt;coordination&gt; tag " +"can be used in both &lt;page&gt; and &lt;portal&gt; tags. When used in &lt;" +"portal&gt; tag only &lt;implicit-mode&gt; tag can be defined for wirings and " +"bindings:" +msgstr "" + +#. Tag: programlisting +#: Coordination.xml:74 +#, no-c-format +msgid "" +"<![CDATA[<portal>\n" +"\n" +" ...\n" +"\n" +" <coordination>\n" +" <bindings>\n" +" <implicit-mode>TRUE</implicit-mode>\n" +" </bindings>\n" +" <wirings>\n" +" <implicit-mode>FALSE</implicit-mode>\n" +" </wirings>\n" +" </coordination>\n" +"\n" +"</portal>]]>" +msgstr "" + +#. Tag: para +#: Coordination.xml:75 +#, no-c-format +msgid "" +"When used within the &lt;page&gt; tag coordination event wirings and " +"bindings can be defined:&lt;/page&gt;" +msgstr "" + +#. Tag: programlisting +#: Coordination.xml:79 +#, no-c-format +msgid "" +"<![CDATA[<coordination>\n" +" \n" +" <wirings>\n" +" <implicit-mode>TRUE</implicit-mode>\n" +" <event-wiring>\n" +" <name>eventWiring1</name>\n" +" <sources>\n" +" <window-coordination>\n" +" <window-name>ShoppingCatalogPortletWindow1</window-" +"name>\n" +" <qname>{urn:jboss:portal:samples:event}CartEvent</" +"qname>\n" +" </window-coordination>\n" +" </sources>\n" +" <destinations>\n" +" <window-coordination>\n" +" <window-name>ShoppingCartPortletWindow2</window-name>\n" +" <qname>{urn:jboss:portal:samples:event}CartEvent</" +"qname>\n" +" </window-coordination>\n" +" <window-coordination>\n" +" <window-name>ShoppingCartPortletWindow3</window-name>\n" +" <qname>{urn:jboss:portal:samples:event}CartEvent</" +"qname>\n" +" </window-coordination>\n" +" </destinations>\n" +" </event-wiring>\n" +" <event-wiring>\n" +" <name>eventWiring2</name>\n" +" <sources>\n" +" <window-coordination>\n" +" <window-name>ShoppingCatalogPortletWindow2</window-" +"name>\n" +" <qname>{urn:jboss:portal:samples:event}CartEvent</" +"qname>\n" +" </window-coordination>\n" +" </sources>\n" +" <destinations>\n" +" <window-coordination>\n" +" <window-name>ShoppingCartPortletWindow1</window-name>\n" +" <qname>{urn:jboss:portal:samples:event}CartEvent</" +"qname>\n" +" </window-coordination>\n" +" <window-coordination>\n" +" <window-name>ShoppingCartPortletWindow4</window-name>\n" +" <qname>{urn:jboss:portal:samples:event}CartEvent</" +"qname>\n" +" </window-coordination>\n" +" </destinations>\n" +" </event-wiring>\n" +" </wirings>\n" +" \n" +"\n" +" <bindings> \n" +" <implicit-mode>FALSE</implicit-mode>\n" +" \n" +" <parameter-binding>\n" +" <id>parameterBinding1</id>\n" +" <window-coordination>\n" +" <window-name>SomePortletWindow1</window-name>\n" +" <qname>foo</qname>\n" +" </window-coordination>\n" +" <window-coordination>\n" +" <window-name>SomePortletWindow2</window-name>\n" +" <qname>foo</qname>\n" +" </window-coordination>\n" +" <window-coordination>\n" +" <window-name>SomePortletWindow3</window-name>\n" +" <qname>foo</qname>\n" +" </window-coordination>\n" +" </parameter-binding>\n" +"\n" +" <parameter-binding>\n" +" <id>parameterBinding2</id>\n" +" <window-coordination>\n" +" <window-name>SomePortletWindow1</window-name>\n" +" <qname>bar1</qname>\n" +" </window-coordination>\n" +" <window-coordination>\n" +" <window-name>SomePortletWindow2</window-name>\n" +" <qname>{urn:jboss:portal:samples:daa1}daa1</qname>\n" +" </window-coordination>\n" +" </parameter-binding>\n" +"\n" +" <alias-binding>\n" +" <id>aliasBinding1</id>\n" +" <qname>foo</qname>\n" +" </alias-binding>\n" +"\n" +" <alias-binding>\n" +" <id>aliasBinding2</id>\n" +" <qname>bar1</qname>\n" +" <qname>{urn:jboss:portal:samples:daa2}daa2</qname>\n" +" </alias-binding>\n" +" \n" +" </bindings>\n" +"</coordination>]]>" +msgstr "" + +#. Tag: title +#: Coordination.xml:82 +#, no-c-format +msgid "&lt;implicit-mode&gt;" +msgstr "" + +#. Tag: para +#: Coordination.xml:84 +#, no-c-format +msgid "" +"This tag can be applied for both &lt;bindings&gt; and &lt;wirings&gt; tags. " +"It defines if implicit coordination is enabled or disabled for this given " +"portal object. Value of this setting is cascaded to all children in portal " +"object tree unless overwritten somewhere in the hierarchy. If no &lt;" +"implicit-mode&gt; is defined in portal object tree default value is TRUE." +msgstr "" + +#. Tag: title +#: Coordination.xml:95 +#, no-c-format +msgid "Coordination Samples" +msgstr "" + +#. Tag: para +#: Coordination.xml:96 +#, no-c-format +msgid "" +"JBoss Portal comes with several examples in 'Coordination Samples' page. Its " +"good to follow them looking at the configuration file that can be found in " +"portal-coordination-samples.war/WEB-INF/default-object.xml" +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Error_Handling.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Error_Handling.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Error_Handling.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,745 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Error_Handling.xml:12 +#, no-c-format +msgid "Error Handling Configuration" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:13 +#, no-c-format +msgid "" +"The JBoss Portal request pipeline allows fine-grained, dynamic configuration " +"of how JBoss Portal behaves when errors occur during runtime." +msgstr "" + +#. Tag: title +#: Error_Handling.xml:17 +#, no-c-format +msgid "Error Types" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:18 +#, no-c-format +msgid "There are several types of errors that can occur during a request:" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:21 +#, no-c-format +msgid "" +"<emphasis>Access denied</emphasis>: the user does not have the required " +"permissions to access the resource." +msgstr "" + +#. Tag: para +#: Error_Handling.xml:26 +#, no-c-format +msgid "" +"<emphasis>Error</emphasis>: an anticipated error, such as when a portlet " +"throws an exception." +msgstr "" + +#. Tag: para +#: Error_Handling.xml:31 +#, no-c-format +msgid "<emphasis>Internal error</emphasis>: an unexpected error." +msgstr "" + +#. Tag: para +#: Error_Handling.xml:36 +#, no-c-format +msgid "<emphasis>Resource not found</emphasis>: the resource was not found." +msgstr "" + +#. Tag: para +#: Error_Handling.xml:41 +#, no-c-format +msgid "" +"<emphasis>Resource unavailable</emphasis>: the resource was found, but was " +"not serviceable." +msgstr "" + +#. Tag: title +#: Error_Handling.xml:49 +#, no-c-format +msgid "Control Policies" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:50 +#, no-c-format +msgid "" +"If an error occurs, the request control-flow changes according to the " +"configuration. This configuration is known as the <emphasis>control policy</" +"emphasis>." +msgstr "" + +#. Tag: title +#: Error_Handling.xml:53 +#, no-c-format +msgid "Policy Delegation and Cascading" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:54 +#, no-c-format +msgid "" +"When a control policy is invoked, the response sent by the control flow can " +"be changed. If the control policy ignores the error, the error is handled by " +"the next policy. If the control policy provides a new response, the next " +"policy is not invoked, since the new response is not an error." +msgstr "" + +#. Tag: para +#: Error_Handling.xml:57 +#, no-c-format +msgid "" +"If a portlet in a page produces an exception, the following reactions are " +"possible:" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:63 +#, no-c-format +msgid "the error is displayed in the window." +msgstr "" + +#. Tag: para +#: Error_Handling.xml:68 +#, no-c-format +msgid "the window is removed from the aggregation." +msgstr "" + +#. Tag: para +#: Error_Handling.xml:73 +#, no-c-format +msgid "a portal error page is displayed." +msgstr "" + +#. Tag: para +#: Error_Handling.xml:78 +#, no-c-format +msgid "a HTTP 500 error response is sent to the Web browser." +msgstr "" + +#. Tag: title +#: Error_Handling.xml:86 +#, no-c-format +msgid "Default Policy" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:87 +#, no-c-format +msgid "" +"The default policy applies when errors are not handled by another level. By " +"default, errors are translated into the most appropriate HTTP response:" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:93 +#, no-c-format +msgid "Access denied: <computeroutput>HTTP 403 Forbidden</computeroutput>" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:98 +#, no-c-format +msgid "Error: <computeroutput>HTTP 500 Internal Server Error</computeroutput>" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:103 +#, no-c-format +msgid "" +"Internal error: <computeroutput>HTTP 500 Internal Server Error</" +"computeroutput>" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:108 +#, no-c-format +msgid "Resource not found: <computeroutput>HTTP 404 Not Found</computeroutput>" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:113 +#, no-c-format +msgid "" +"Resource unavailable: <computeroutput>HTTP 404 Not Found</computeroutput>" +msgstr "" + +#. Tag: title +#: Error_Handling.xml:121 +#, no-c-format +msgid "Portal Policy" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:122 +#, no-c-format +msgid "" +"The portal error-policy controls the response sent to the Web browser when " +"an error occurs. A default error policy exists, which can be configured per " +"portal. If an error occurs, the policy can either handle a redirect to a JSP " +"page, or ignore it. If the error is ignored, it is handled by the default " +"policy, otherwise a JSP page is invoked with the appropriate request " +"attributes, allowing page customization." +msgstr "" + +#. Tag: title +#: Error_Handling.xml:127 +#, no-c-format +msgid "Page Policy" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:128 +#, no-c-format +msgid "" +"The window error-policy controls how pages react to aggregation errors. Most " +"of the time pages are an aggregation of several portlet windows, and the " +"action to take when an error occurs differs from other policies. When an " +"error occurs, the policy can either handle it, or ignore it. If the error is " +"ignored, it is handled by the portal policy. Possible actions taken after " +"such errors are:" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:134 +#, no-c-format +msgid "remove the window from the aggregation." +msgstr "" + +#. Tag: para +#: Error_Handling.xml:139 +#, no-c-format +msgid "replace the markup of the window using a redirect to a JSP page." +msgstr "" + +#. Tag: title +#: Error_Handling.xml:148 +#, no-c-format +msgid "Configuration using XML Descriptors" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:149 +#, no-c-format +msgid "" +"Different policies are configured using portal object properties, allowing " +"the error-handling policy for objects to be configured in XML descriptors -- " +"the <filename>*-object.xml</filename> files -- for a portal deployment." +msgstr "" + +#. Tag: title +#: Error_Handling.xml:153 +#, no-c-format +msgid "Portal Policy Properties" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:154 +#, no-c-format +msgid "" +"A set of properties configure the the behavior of the portal policy. These " +"properties are only taken into account for objects that use the " +"<emphasis>portal</emphasis> type. The following table represents possible " +"portal-policy properties:" +msgstr "" + +#. Tag: entry +#: Error_Handling.xml:165 +#, no-c-format +msgid "Property Name" +msgstr "" + +#. Tag: entry +#: Error_Handling.xml:166 Error_Handling.xml:227 +#, no-c-format +msgid "Description" +msgstr "" + +#. Tag: entry +#: Error_Handling.xml:167 +#, no-c-format +msgid "Possible Values" +msgstr "" + +#. Tag: computeroutput +#: Error_Handling.xml:172 +#, no-c-format +msgid "control.portal.access_denied" +msgstr "" + +#. Tag: entry +#: Error_Handling.xml:173 Error_Handling.xml:234 +#, no-c-format +msgid "when access is denied" +msgstr "" + +#. Tag: entry +#: Error_Handling.xml:174 Error_Handling.xml:179 Error_Handling.xml:184 +#: Error_Handling.xml:189 Error_Handling.xml:194 +#, no-c-format +msgid "" +"<computeroutput>ignore</computeroutput> and <computeroutput>jsp</" +"computeroutput>" +msgstr "" + +#. Tag: computeroutput +#: Error_Handling.xml:177 +#, no-c-format +msgid "control.portal.unavailable" +msgstr "" + +#. Tag: entry +#: Error_Handling.xml:178 Error_Handling.xml:239 +#, no-c-format +msgid "when a resource is unavailable" +msgstr "" + +#. Tag: computeroutput +#: Error_Handling.xml:182 +#, no-c-format +msgid "control.portal.not_found" +msgstr "" + +#. Tag: entry +#: Error_Handling.xml:183 Error_Handling.xml:244 +#, no-c-format +msgid "when a resource is not found" +msgstr "" + +#. Tag: computeroutput +#: Error_Handling.xml:187 +#, no-c-format +msgid "control.portal.internal_error" +msgstr "" + +#. Tag: entry +#: Error_Handling.xml:188 Error_Handling.xml:249 +#, no-c-format +msgid "when an unexpected error occurs" +msgstr "" + +#. Tag: computeroutput +#: Error_Handling.xml:192 +#, no-c-format +msgid "control.portal.error" +msgstr "" + +#. Tag: entry +#: Error_Handling.xml:193 Error_Handling.xml:254 +#, no-c-format +msgid "when an expected error occurs" +msgstr "" + +#. Tag: computeroutput +#: Error_Handling.xml:197 +#, no-c-format +msgid "control.portal.resource_uri" +msgstr "" + +#. Tag: entry +#: Error_Handling.xml:198 Error_Handling.xml:259 +#, no-c-format +msgid "the path to the JSP used for redirections" +msgstr "" + +#. Tag: entry +#: Error_Handling.xml:199 +#, no-c-format +msgid "" +"a valid path to a JSP located in the <filename>portal-core.war/</filename> " +"directory" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:206 +#, no-c-format +msgid "" +"The following portal configuration demonstrates the use of portal-policy " +"properties:" +msgstr "" + +#. Tag: programlisting +#: Error_Handling.xml:210 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<portal>\n" +" <portal-name>MyPortal</portal-name>\n" +" ...\n" +" <properties>\n" +" <property>\n" +" <name>control.portal.access_denied</name>\n" +" <value>ignore</value>\n" +" </property>\n" +" <property>\n" +" <name>control.portal.unavailable</name>\n" +" <value>ignore</value>\n" +" </property>\n" +" <property>\n" +" <name>control.portal.not_found</name>\n" +" <value>ignore</value>\n" +" </property>\n" +" <property>\n" +" <name>control.portal.internal_error</name>\n" +" <value>jsp</value>\n" +" </property>\n" +" <property>\n" +" <name>control.portal.error</name>\n" +" <value>jsp</value>\n" +" </property>\n" +" <property>\n" +" <name>control.portal.resource_uri</name>\n" +" <value>/WEB-INF/jsp/error/portal.jsp</value>\n" +" </property>\n" +" ...\n" +" </properties>\n" +" ...\n" +"</portal>\n" +"]]>" +msgstr "" + +#. Tag: title +#: Error_Handling.xml:214 +#, no-c-format +msgid "Page Policy Properties" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:215 +#, no-c-format +msgid "" +"A set of properties configure the behavior of the page policy. These " +"properties are only taken into account for objects that use the " +"<emphasis>portal</emphasis> type. The following table represents possible " +"page-policy properties:" +msgstr "" + +#. Tag: entry +#: Error_Handling.xml:226 +#, no-c-format +msgid "Property name" +msgstr "" + +#. Tag: entry +#: Error_Handling.xml:228 +#, no-c-format +msgid "Possible values" +msgstr "" + +#. Tag: computeroutput +#: Error_Handling.xml:233 +#, no-c-format +msgid "control.page.access_denied" +msgstr "" + +#. Tag: entry +#: Error_Handling.xml:235 Error_Handling.xml:240 Error_Handling.xml:245 +#: Error_Handling.xml:250 Error_Handling.xml:255 Error_Handling.xml:260 +#, no-c-format +msgid "" +"<computeroutput>ignore</computeroutput>, <computeroutput>jsp</" +"computeroutput> and <computeroutput>hide</computeroutput>" +msgstr "" + +#. Tag: computeroutput +#: Error_Handling.xml:238 +#, no-c-format +msgid "control.page.unavailable" +msgstr "" + +#. Tag: computeroutput +#: Error_Handling.xml:243 +#, no-c-format +msgid "control.page.not_found" +msgstr "" + +#. Tag: computeroutput +#: Error_Handling.xml:248 +#, no-c-format +msgid "control.page.internal_error" +msgstr "" + +#. Tag: computeroutput +#: Error_Handling.xml:253 +#, no-c-format +msgid "control.page.error" +msgstr "" + +#. Tag: computeroutput +#: Error_Handling.xml:258 +#, no-c-format +msgid "control.page.resource_uri" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:266 +#, no-c-format +msgid "" +"The following page configuration demonstrates the use of page-policy " +"properties:" +msgstr "" + +#. Tag: programlisting +#: Error_Handling.xml:270 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<page>\n" +" <page-name>MyPortal</page-name>\n" +" ...\n" +" <properties>\n" +" <property>\n" +" <name>control.page.access_denied</name>\n" +" <value>hide</value>\n" +" </property>\n" +" <property>\n" +" <name>control.page.unavailable</name>\n" +" <value>hide</value>\n" +" </property>\n" +" <property>\n" +" <name>control.page.not_found</name>\n" +" <value>hide</value>\n" +" </property>\n" +" <property>\n" +" <name>control.page.internal_error</name>\n" +" <value>jsp</value>\n" +" </property>\n" +" <property>\n" +" <name>control.page.error</name>\n" +" <value>jsp</value>\n" +" </property>\n" +" <property>\n" +" <name>control.page.resource_uri</name>\n" +" <value>/WEB-INF/jsp/error/page.jsp</value>\n" +" </property>\n" +" ...\n" +" </properties>\n" +" ...\n" +"</page>\n" +"]]>" +msgstr "" + +#. Tag: title +#: Error_Handling.xml:274 +#, no-c-format +msgid "Page Property Inheritance for Objects" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:275 +#, no-c-format +msgid "" +"When page properties are configured for objects that use the " +"<emphasis>portal</emphasis> type, the properties are inherited by pages in " +"that portal." +msgstr "" + +#. Tag: title +#: Error_Handling.xml:283 +#, no-c-format +msgid "Using <trademark class=\"trade\">JSP</trademark> to Handle Errors" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:284 +#, no-c-format +msgid "" +"As described in previous sections, error handling can be redirected to a " +"<trademark class=\"trade\">JSP</trademark> page. Two pages can be created to " +"handle errors: one for the portal level, and the other for the page level. " +"Portal level error-handling requires a page that produces a full page, and " +"page-level handling requires a page that produces markup, but only for a " +"window. When the page is invoked, a set of request attributes are passed. " +"The following table represents possible request attributes:" +msgstr "" + +#. Tag: entry +#: Error_Handling.xml:295 +#, no-c-format +msgid "Attribute Name" +msgstr "" + +#. Tag: entry +#: Error_Handling.xml:296 +#, no-c-format +msgid "Attribute Description" +msgstr "" + +#. Tag: entry +#: Error_Handling.xml:297 +#, no-c-format +msgid "Attribute Value" +msgstr "" + +#. Tag: computeroutput +#: Error_Handling.xml:302 +#, no-c-format +msgid "org.jboss.portal.control.ERROR_TYPE" +msgstr "" + +#. Tag: entry +#: Error_Handling.xml:303 +#, no-c-format +msgid "the error type" +msgstr "" + +#. Tag: entry +#: Error_Handling.xml:304 +#, no-c-format +msgid "" +"possible values are <computeroutput>ACCESS_DENIED</computeroutput>, " +"<computeroutput>UNAVAILABLE</computeroutput>, <computeroutput>ERROR</" +"computeroutput>, <computeroutput>INTERNAL_ERROR</computeroutput>, and " +"<computeroutput>NOT_FOUND</computeroutput>" +msgstr "" + +#. Tag: computeroutput +#: Error_Handling.xml:307 +#, no-c-format +msgid "org.jboss.portal.control.CAUSE" +msgstr "" + +#. Tag: entry +#: Error_Handling.xml:308 +#, no-c-format +msgid "a cause which is thrown, that can be null" +msgstr "" + +#. Tag: entry +#: Error_Handling.xml:309 +#, no-c-format +msgid "" +"the object is a subclass of <computeroutput>java.lang.Throwable</" +"computeroutput>" +msgstr "" + +#. Tag: computeroutput +#: Error_Handling.xml:312 +#, no-c-format +msgid "org.jboss.portal.control.MESSAGE" +msgstr "" + +#. Tag: entry +#: Error_Handling.xml:313 +#, no-c-format +msgid "an error message that can be null" +msgstr "" + +#. Tag: entry +#: Error_Handling.xml:314 +#, no-c-format +msgid "text" +msgstr "" + +#. Tag: title +#: Error_Handling.xml:322 +#, no-c-format +msgid "<trademark class=\"trade\">JSP</trademark> Location" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:322 +#, no-c-format +msgid "" +"The JavaServer Pages must be located in the <filename>jboss-portal.sar/" +"portal-core.war/</filename> web application." +msgstr "" + +#. Tag: title +#: Error_Handling.xml:328 +#, no-c-format +msgid "Configuration using the Portal Management Application" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:329 +#, no-c-format +msgid "" +"The error handling policy can be configured via the portal management " +"application. To access the portal management application:" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:335 +#, no-c-format +msgid "" +"Use a Web browser to navigate to <ulink url=\"http://localhost:8080/portal" +"\"></ulink>." +msgstr "" + +#. Tag: para +#: Error_Handling.xml:340 +#, no-c-format +msgid "" +"Click the <guibutton>Login</guibutton> button on the top right-hand of the " +"welcome page, and log in as the <option>admin</option> user." +msgstr "" + +#. Tag: para +#: Error_Handling.xml:345 +#, no-c-format +msgid "" +"Click the <guibutton>Admin</guibutton> tab on the top right-hand of the " +"welcome page. Four tabs will appear on the left-hand side of the page." +msgstr "" + +#. Tag: para +#: Error_Handling.xml:350 +#, no-c-format +msgid "" +"Click the <guibutton>Admin</guibutton> tab to open the portal management " +"application, and then click the <guibutton>Portal Objects</guibutton> tab to " +"display available portals." +msgstr "" + +#. Tag: para +#: Error_Handling.xml:356 +#, no-c-format +msgid "" +"Configuration options are available as part of the properties for each " +"configuration level. You can specify the default error handling policy (at " +"the root of the portal object hierarchy) for each portal, or each page, by " +"clicking on the <guibutton>Properties</guibutton> button for each page or " +"portal:" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:366 +#, no-c-format +msgid "" +"As well, you can specify how dashboards should behave with respect to error " +"handling, by clicking on the <guibutton>Dashboards</guibutton> tab in the " +"portal management application:" +msgstr "" + +#. Tag: para +#: Error_Handling.xml:376 +#, no-c-format +msgid "" +"The page specified with <computeroutput>On error redirect to this resource</" +"computeroutput> is used when the <option>Redirect to the specified resource</" +"option> action is selected for an error type, such as <computeroutput>When " +"access to the page is denied</computeroutput>. After making changes, click " +"the <guibutton>Update</guibutton> button for settings to take effect." +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Feedback.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Feedback.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Feedback.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,47 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Feedback.xml:6 +#, no-c-format +msgid "We Need Feedback!" +msgstr "" + +#. Tag: primary +#: Feedback.xml:8 +#, no-c-format +msgid "feedback" +msgstr "" + +#. Tag: secondary +#: Feedback.xml:9 +#, no-c-format +msgid "contact information for this manual" +msgstr "" + +#. Tag: para +#: Feedback.xml:11 +#, no-c-format +msgid "" +"If you find a typographical error in this manual, or if you have thought of " +"a way to make this manual better, we would love to hear from you! Submit a " +"report in <ulink url=\"http://jira.jboss.com/jira/browse/JBEPP\">JIRA</" +"ulink> against the Version: <emphasis>&JBEPPVERS;</emphasis>, Component: " +"<emphasis>Documentation</emphasis>. When submitting a bug report, be sure to " +"mention the manual's identifier: Portal_User_Guide If you have a suggestion " +"for improving the documentation, try to be as specific as possible when " +"describing it. If you have found an error, please include the section number " +"and some of the surrounding text so we can find it easily." +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Identity.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Identity.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Identity.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,1504 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Identity.xml:12 +#, no-c-format +msgid "JBoss Portal Identity Management" +msgstr "" + +#. Tag: para +#: Identity.xml:13 +#, no-c-format +msgid "This chapter addresses identity management in JBoss Portal 2.6" +msgstr "" + +#. Tag: title +#: Identity.xml:15 +#, no-c-format +msgid "Identity management API" +msgstr "" + +#. Tag: para +#: Identity.xml:16 +#, no-c-format +msgid "" +"Since JBoss Portal 2.6 there are 4 identity services and 2 identity related " +"interfaces. The goal of having such a fine grained API is to enable flexible " +"implementations based on different identity storage like relational " +"databases or LDAP servers. The Membership service takes care of managing the " +"relationship between user objects and role objects. The User Profile service " +"is responsible for managing the profile of a user, it has database and LDAP " +"implementations as well as a mode that combines data from both." +msgstr "" + +#. Tag: para +#: Identity.xml:24 +#, no-c-format +msgid "" +"The <emphasis role=\"bold\">org.jboss.portal.identity.User</emphasis> " +"interface represents a user and exposes the following operations:" +msgstr "" + +#. Tag: programlisting +#: Identity.xml:28 +#, no-c-format +msgid "" +"<![CDATA[\n" +" /** The user identifier. */\n" +" public Object getId();\n" +"\n" +" /** The user name. */\n" +" public String getUserName();\n" +"\n" +" /** Set the password using proper encoding. */\n" +" public void updatePassword(String password);\n" +"\n" +" /** Return true if the password is valid. */\n" +" public boolean validatePassword(String password);\n" +" ]]>" +msgstr "" + +#. Tag: para +#: Identity.xml:30 +#, no-c-format +msgid "Important Note! The proper usage of getId() method is:" +msgstr "" + +#. Tag: programlisting +#: Identity.xml:33 +#, no-c-format +msgid "" +"<![CDATA[\n" +"// Always use it like this:\n" +"user.getId().toString();\n" +"\n" +"// Do not use it like this:\n" +"\n" +"// We would get a Long object if we are using the database implementation\n" +"(Long)user.getId();\n" +"\n" +"// We would get a String with an LDAP server\n" +"(String)user.getId();\n" +"]]>" +msgstr "" + +#. Tag: para +#: Identity.xml:34 +#, no-c-format +msgid "" +"This is because the ID value depends on the User implementation. It'll " +"probably be String object with the LDAP implementation and a Long object " +"with the database implementation but it could be something else if one has " +"chosen to make its own implementation." +msgstr "" + +#. Tag: para +#: Identity.xml:41 +#, no-c-format +msgid "" +"The <emphasis role=\"bold\">org.jboss.portal.identity.Role</emphasis> " +"interface represents a Role and exposes the following operations:" +msgstr "" + +#. Tag: programlisting +#: Identity.xml:45 +#, no-c-format +msgid "" +"<![CDATA[\n" +"/** The role identifier. */\n" +"public Object getId();\n" +"\n" +"/** The role name used in security rules. This name can not be modified */\n" +"public String getName();\n" +"\n" +"/** The role display name used on screens. This name can be modified */\n" +"public String getDisplayName();\n" +"\n" +"/** */\n" +"public void setDisplayName(String name);\n" +"]]>" +msgstr "" + +#. Tag: para +#: Identity.xml:49 +#, no-c-format +msgid "" +"The <emphasis role=\"bold\">org.jboss.portal.identity.UserModule</emphasis> " +"interface exposes operations for users management:" +msgstr "" + +#. Tag: programlisting +#: Identity.xml:53 +#, no-c-format +msgid "" +"<![CDATA[\n" +"/**Retrieve a user by its name.*/\n" +"User findUserByUserName(String userName)\n" +" throws IdentityException, IllegalArgumentException, NoSuchUserException;\n" +"\n" +"/**Retrieve a user by its id.*/\n" +"User findUserById(Object id)\n" +" throws IdentityException, IllegalArgumentException, NoSuchUserException;\n" +"\n" +"/**Retrieve a user by its id.*/\n" +"User findUserById(String id)\n" +" throws IdentityException, IllegalArgumentException, NoSuchUserException;\n" +"\n" +"/** Creates a new user with the specified name.*/\n" +"User createUser(String userName, String password)\n" +" throws IdentityException, IllegalArgumentException;\n" +"\n" +"/** Remove a user.*/\n" +"void removeUser(Object id)\n" +" throws IdentityException, IllegalArgumentException;\n" +"\n" +"/** Get a range of users.*/\n" +"Set findUsers(int offset, int limit)\n" +" throws IdentityException, IllegalArgumentException;\n" +"\n" +"/** Get a range of users.*/\n" +"Set findUsersFilteredByUserName(String filter, int offset, int limit)\n" +" throws IdentityException, IllegalArgumentException;\n" +"\n" +"/**Returns the number of users.*/\n" +"int getUserCount() throws IdentityException, IllegalArgumentException;\n" +"]]>" +msgstr "" + +#. Tag: para +#: Identity.xml:57 +#, no-c-format +msgid "" +"The <emphasis role=\"bold\">org.jboss.portal.identity.RoleModule</emphasis> " +"interface exposes operations for roles management:" +msgstr "" + +#. Tag: programlisting +#: Identity.xml:61 +#, no-c-format +msgid "" +"<![CDATA[\n" +"/** Retrieves a role by its name*/\n" +"Role findRoleByName(String name)\n" +" throws IdentityException, IllegalArgumentException;\n" +"\n" +"/**Retrieve a collection of role from the role names.*/\n" +"Set findRolesByNames(String[] names)\n" +" throws IdentityException, IllegalArgumentException;\n" +"\n" +"/** Retrieves a role by its id.*/\n" +"Role findRoleById(Object id)\n" +" throws IdentityException, IllegalArgumentException;\n" +"\n" +"/** Retrieves a role by its id.*/\n" +"Role findRoleById(String id)\n" +" throws IdentityException, IllegalArgumentException;\n" +"\n" +"/** Create a new role with the specified name.*/\n" +"Role createRole(String name, String displayName)\n" +" throws IdentityException, IllegalArgumentException;\n" +"\n" +"/** Remove a role.*/\n" +"void removeRole(Object id)\n" +" throws IdentityException, IllegalArgumentException;\n" +"\n" +"/** Returns the number of roles. */\n" +"int getRolesCount()\n" +" throws IdentityException;\n" +"\n" +"/** Get all the roles */\n" +"Set findRoles() throws IdentityException;\n" +"]]>" +msgstr "" + +#. Tag: para +#: Identity.xml:65 +#, no-c-format +msgid "" +"The <emphasis role=\"bold\">MembershipModule</emphasis> interface exposes " +"operations for obtaining or managing relationships beetween users and roles. " +"The role of this service is to decouple relationship information from user " +"and roles. Indeed while user role relationship is pretty straightforward " +"with a relational database (using a many to many relationship with an " +"intermediary table), with an LDAP server there a different ways to define " +"relationships between users and roles." +msgstr "" + +#. Tag: programlisting +#: Identity.xml:73 +#, no-c-format +msgid "" +"<![CDATA[\n" +"/** Return the set of role objects that a given user has.*/\n" +"Set getRoles(User user) throws IdentityException, IllegalArgumentException;\n" +"\n" +"Set getUsers(Role role) throws IdentityException, IllegalArgumentException;\n" +"\n" +"/** Creates a relationship beetween a role and set of users. Other roles " +"that have\n" +" assotiontions with those users remain unaffected.*/\n" +"void assignUsers(Role role, Set users) throws IdentityException, " +"IllegalArgumentException;\n" +"\n" +"/** Creates a relationship beetween a user and set of roles. This operation " +"will erase any\n" +" other assotientions beetween the user and roles not specified in the " +"provided set.*/\n" +"void assignRoles(User user, Set roles) throws IdentityException, " +"IllegalArgumentException;\n" +"\n" +"/** Returns role members based on rolename - depreciated method ethod here " +"only\n" +" for compatibility with old RoleModule interface */\n" +"Set findRoleMembers(String roleName, int offset, int limit, String " +"userNameFilter)\n" +" throws IdentityException, IllegalArgumentException;\n" +"]]>" +msgstr "" + +#. Tag: para +#: Identity.xml:77 +#, no-c-format +msgid "" +"The <emphasis role=\"bold\">UserProfileModule</emphasis> interface exposes " +"operations to access and manage informations stored in User profile:" +msgstr "" + +#. Tag: programlisting +#: Identity.xml:81 +#, no-c-format +msgid "" +"<![CDATA[\n" +"public Object getProperty(User user, String propertyName)\n" +" throws IdentityException, IllegalArgumentException;\n" +"\n" +"public void setProperty(User user, String name, Object property)\n" +" throws IdentityException, IllegalArgumentException;\n" +"\n" +"public Map getProperties(User user)\n" +" throws IdentityException, IllegalArgumentException;\n" +"\n" +"public ProfileInfo getProfileInfo()\n" +" throws IdentityException;\n" +"]]>" +msgstr "" + +#. Tag: para +#: Identity.xml:83 +#, no-c-format +msgid "" +"UserProfileModule.getProperty() method returns an Object. In most cases with " +"DB backend it will always be String object. But normally you should check " +"what object will be retrieved using getProfileInfo() method." +msgstr "" + +#. Tag: para +#: Identity.xml:91 +#, no-c-format +msgid "" +"The <emphasis role=\"bold\">ProfileInfo</emphasis> interface can be obtained " +"using the <emphasis role=\"bold\">UserProfileModule</emphasis> and exposes " +"meta information of a profile:" +msgstr "" + +#. Tag: programlisting +#: Identity.xml:97 +#, no-c-format +msgid "" +"<![CDATA[\n" +"/** Returns a Map o PropertyInfo objects describing profile properties */\n" +"public Map getPropertiesInfo();\n" +"\n" +"public PropertyInfo getPropertyInfo(String name);\n" +"]]>" +msgstr "" + +#. Tag: para +#: Identity.xml:101 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">PropertyInfo</emphasis> interface expose methods to " +"obtain information about accessible property in User profile" +msgstr "" + +#. Tag: programlisting +#: Identity.xml:105 +#, no-c-format +msgid "" +"<![CDATA[\n" +"public static final String ACCESS_MODE_READ_ONLY = \"read-only\";\n" +"public static final String ACCESS_MODE_READ_WRITE = \"read-write\";\n" +"public static final String USAGE_MANDATORY = \"mandatory\";\n" +"public static final String USAGE_OPTIONAL = \"optional\";\n" +"public static final String MAPPING_DB_TYPE_COLUMN = \"column\";\n" +"public static final String MAPPING_DB_TYPE_DYNAMIC = \"dynamic\";\n" +"\n" +"public String getName();\n" +"\n" +"public String getType();\n" +"\n" +"public String getAccessMode();\n" +"\n" +"public String getUsage();\n" +"\n" +"public LocalizedString getDisplayName();\n" +"\n" +"public LocalizedString getDescription();\n" +"\n" +"public String getMappingDBType();\n" +"\n" +"public String getMappingLDAPValue();\n" +"\n" +"public String getMappingDBValue();\n" +"\n" +"public boolean isMappedDB();\n" +"\n" +"public boolean isMappedLDAP();\n" +"]]>" +msgstr "" + +#. Tag: title +#: Identity.xml:112 +#, no-c-format +msgid "How to obtain identity modules services ?" +msgstr "" + +#. Tag: para +#: Identity.xml:113 +#, no-c-format +msgid "" +"The advocated way to get a reference to the identity modules is by using " +"JNDI:" +msgstr "" + +#. Tag: programlisting +#: Identity.xml:116 +#, no-c-format +msgid "" +"import org.jboss.portal.identity.UserModule;\n" +"import org.jboss.portal.identity.RoleModule;\n" +"import org.jboss.portal.identity.MembershipModule;\n" +"import org.jboss.portal.identity.UserProfileModule;\n" +"\n" +"[...]\n" +"\n" +"(UserModule)new InitialContext().lookup(\"java:portal/UserModule\");\n" +"(RoleModule)new InitialContext().lookup(\"java:portal/RoleModule\");\n" +"(MembershipModule)new InitialContext().lookup(\"java:portal/MembershipModule" +"\");\n" +"(UserProfileModule)new InitialContext().lookup(\"java:portal/" +"UserProfileModule\");" +msgstr "" + +#. Tag: para +#: Identity.xml:117 +#, no-c-format +msgid "" +"Another way to do this is, if you are fimiliar with JBoss Microkernel " +"architecture is to get the <emphasis role=\"bold" +"\">IdentityServiceController</emphasis> mbean. You may want to inject it " +"into your services like this:" +msgstr "" + +#. Tag: programlisting +#: Identity.xml:122 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<depends optional-attribute-name=\"IdentityServiceController\" proxy-type=" +"\"attribute\">\n" +" portal:service=Module,type=IdentityServiceController\n" +"</depends>]]>" +msgstr "" + +#. Tag: para +#: Identity.xml:123 +#, no-c-format +msgid "" +"or simply obtain in your code by doing a lookup using the <emphasis role=" +"\"bold\">portal:service=Module,type=IdentityServiceController</emphasis> " +"name. Please refer to the JBoss Application Server documentation if you want " +"to learn more about service MBeans. Once you obtained the object you can use " +"it:" +msgstr "" + +#. Tag: programlisting +#: Identity.xml:130 +#, no-c-format +msgid "" +"(UserModule)identityServiceController.getIdentityContext()\n" +" .getObject(IdentityContext.TYPE_USER_MODULE);\n" +"\n" +"(RoleModule)identityServiceController.getIdentityContext()\n" +" .getObject(IdentityContext.TYPE_ROLE_MODULE);\n" +"\n" +"(MembershipModule)identityServiceController.getIdentityContext()\n" +" .getObject(IdentityContext.TYPE_MEMBERSHIP_MODULE);\n" +"\n" +"(UserProfileModule)identityServiceController.getIdentityContext()\n" +" .getObject(IdentityContext.TYPE_USER_PROFILE_MODULE);" +msgstr "" + +#. Tag: title +#: Identity.xml:134 +#, no-c-format +msgid "API changes since 2.4" +msgstr "" + +#. Tag: para +#: Identity.xml:135 +#, no-c-format +msgid "" +"Because in JBoss Portal 2.4 there were only <emphasis role=\"bold" +"\">UserModule</emphasis> , <emphasis role=\"bold\">RoleModule</emphasis> , " +"<emphasis role=\"bold\">User</emphasis> and <emphasis role=\"bold\">Role</" +"emphasis> interfaces some API usages changed. Here are the most important " +"changes you will need to aply to your code while migrating your aplication " +"to 2.6:" +msgstr "" + +#. Tag: para +#: Identity.xml:148 +#, no-c-format +msgid "For the <emphasis role=\"bold\">User</emphasis> interface:" +msgstr "" + +#. Tag: programlisting +#: Identity.xml:151 +#, no-c-format +msgid "" +"<![CDATA[\n" +"// Instead of: user.getEnabled()\n" +"userProfileModule.getProperty(user, User.INFO_USER_ENABLED);\n" +"\n" +"// Instead of: user.setEnabled(value)\n" +"userProfileModule.setProperty(user, User.INFO_USER_ENABLED, value);\n" +"\n" +"// In a similar way you should change rest of methods that are missing in " +"User interface\n" +"// in 2.6 by the call to the UserProfileModule\n" +"\n" +"// Instead of: user.getProperties()\n" +"userProfileModule.getProperties(user);\n" +"\n" +"// Instead of: user.getGivenName()\n" +"userProfileModule.getProperty(user, User.INFO_USER_NAME_GIVEN);\n" +"\n" +"// Instead of: user.getFamilyName()\n" +"userProfileModule.getProperty(user, User.INFO_USER_NAME_FAMILY);\n" +"\n" +"// Instead of: user.getRealEmail()\n" +"userProfileModule.getProperty(user, User.INFO_USER_EMAIL_REAL);\n" +"\n" +"// Instead of: user.getFakeEmail()\n" +"userProfileModule.getProperty(user, User.INFO_USER_EMAIL_FAKE);\n" +"\n" +"// Instead of: user.getRegistrationDate()\n" +"userProfileModule.getProperty(user, User.INFO_USER_REGISTRATION_DATE);\n" +"\n" +"// Instead of: user.getViewRealEmail()\n" +"userProfileModule.getProperty(user, User.INFO_USER_VIEW_EMAIL_VIEW_REAL);\n" +"\n" +"// Instead of: user.getPreferredLocale()\n" +"userProfileModule.getProperty(user, User.INFO_USER_LOCALE);\n" +"\n" +"// Instead of: user.getSignature()\n" +"userProfileModule.getProperty(user, User.INFO_USER_SIGNATURE);\n" +"\n" +"// Instead of: user.getLastVisitDate()\n" +"userProfileModule.getProperty(user, User.INFO_USER_LAST_LOGIN_DATE);]]>" +msgstr "" + +#. Tag: para +#: Identity.xml:155 +#, no-c-format +msgid "The <emphasis role=\"bold\">RoleModule</emphasis> interface:" +msgstr "" + +#. Tag: programlisting +#: Identity.xml:158 +#, no-c-format +msgid "" +"<![CDATA[\n" +"// Instead of\n" +"// RoleModule.findRoleMembers(String roleName, int offset, int limit, String " +"userNameFilter)\n" +"// throws IdentityException;\n" +"membershipModule.findRoleMembers(String roleName, int offset, int limit,\n" +" String userNameFilter)\n" +"\n" +"// Instead of\n" +"// RoleModule.setRoles(User user, Set roles) throws IdentityException;\n" +"membershipModule.assignRoles(User user, Set roles)\n" +"\n" +"// Instead of\n" +"// RoleModule.getRoles(User user) throws IdentityException;\n" +"membershipModule.getRoles(User user)]]>" +msgstr "" + +#. Tag: title +#: Identity.xml:165 +#, no-c-format +msgid "Identity configuration" +msgstr "" + +#. Tag: para +#: Identity.xml:166 +#, no-c-format +msgid "" +"In order to understand identity configuration you need to understand its " +"architecture. Different identity services like UserModule, RoleModule and " +"etc are just plain Java classes that are instantiated and exposed by the " +"portal. So an *example* of UserModule service could be a plain Java bean " +"object that would be:" +msgstr "" + +#. Tag: para +#: Identity.xml:172 +#, no-c-format +msgid "<emphasis role=\"bold\">Instantiated</emphasis> using reflection" +msgstr "" + +#. Tag: para +#: Identity.xml:175 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">Initialized/Started</emphasis> by invoking some " +"methods" +msgstr "" + +#. Tag: para +#: Identity.xml:178 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">Registered/Exposed</emphasis> using JNDI and/or " +"mbeans (JBoss Microkernel) services, so other services of the portal can use " +"it" +msgstr "" + +#. Tag: para +#: Identity.xml:181 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">Managed</emphasis> in the matter of lifecycle - so " +"it'll be stopped and unregistered during portal shutdown" +msgstr "" + +#. Tag: para +#: Identity.xml:184 +#, no-c-format +msgid "" +"As you see from this point of view, configuration just specifies what Java " +"class will be used and how it should be used by portal as a service." +msgstr "" + +#. Tag: title +#: Identity.xml:187 Identity.xml:239 Identity.xml:245 Identity.xml:290 +#: Identity.xml:308 Identity.xml:327 Identity.xml:362 Identity.xml:364 +#: Identity.xml:378 +#, no-c-format +msgid "Note" +msgstr "" + +#. Tag: para +#: Identity.xml:187 +#, no-c-format +msgid "" +"We use JBoss Microcontainer internally to manage the sub system made of " +"those components so if you are interested in implementing custom services - " +"look on the methods that are used by this framework." +msgstr "" + +#. Tag: para +#: Identity.xml:190 +#, no-c-format +msgid "" +"In JBoss Portal we provide a very flexible configuration. It is very easy to " +"rearrange and customize services, provide alternative implementations, " +"extend the existing ones or provide a custom identity model." +msgstr "" + +#. Tag: para +#: Identity.xml:194 +#, no-c-format +msgid "" +"To grasp the full picture of the configuration of identity services let's " +"start from its root component. Whole configuration and setup of identity " +"components is done by the <emphasis role=\"bold\">IdentityServiceController</" +"emphasis> service. It brings to life and registers all other services such " +"as UserModule, RoleModule, MembershipModule and UserProfileModule. <emphasis " +"role=\"bold\">IdentityServiceController</emphasis> is defined in " +"<emphasis>jboss-portal.sar/META-INF/jboss-service.xml</emphasis>" +msgstr "" + +#. Tag: programlisting +#: Identity.xml:202 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<mbean\n" +" code=\"org.jboss.portal.identity.IdentityServiceControllerImpl\"\n" +" name=\"portal:service=Module,type=IdentityServiceController\"\n" +" xmbean-dd=\"\"\n" +" xmbean-code=\"org.jboss.portal.jems.as.system.JBossServiceModelMBean\">\n" +" <xmbean/>\n" +" <depends>portal:service=Hibernate</depends>\n" +" <attribute name=\"JndiName\">java:/portal/IdentityServiceController</" +"attribute>\n" +" <attribute name=\"RegisterMBeans\">true</attribute>\n" +" <attribute name=\"ConfigFile\">conf/identity/identity-config.xml</" +"attribute>\n" +" <attribute name=\"DefaultConfigFile\">conf/identity/standardidentity-" +"config.xml</attribute>\n" +"</mbean>]]>" +msgstr "" + +#. Tag: para +#: Identity.xml:203 +#, no-c-format +msgid "We can specify a few options here:" +msgstr "" + +#. Tag: para +#: Identity.xml:207 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">RegisterMBeans</emphasis> - defines if " +"IdentityServiceController should register components which are instantiated " +"as mbeans" +msgstr "" + +#. Tag: para +#: Identity.xml:213 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">ConfigFile</emphasis> - defines the location of the " +"main identity services configuration file. It describes and configures all " +"the components like UserModule, RoleModule... that need to be instantiated" +msgstr "" + +#. Tag: para +#: Identity.xml:218 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">DefaultConfigFile</emphasis> - defines the location " +"of the configuration file containing the default values. For each component " +"defined in <emphasis role=\"bold\">ConfigFile</emphasis>, the " +"IdentityServiceController will obtain a set of default options from this " +"file. That helps to keep the main main configuration file simple, short and " +"easy to read. Potentially it provides more powerful customizations." +msgstr "" + +#. Tag: title +#: Identity.xml:228 +#, no-c-format +msgid "Main configuration file architecture (identity-config.xml)" +msgstr "" + +#. Tag: para +#: Identity.xml:229 +#, no-c-format +msgid "The file describing portal identity services contains three sections:" +msgstr "" + +#. Tag: programlisting +#: Identity.xml:232 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<identity-configuration>\n" +" <datasources>\n" +" <!-- Datasources section -->\n" +" <datasource> ... </datasource>\n" +" <datasource> ... </datasource>\n" +" ...\n" +" </datasources>\n" +" <modules>\n" +" <!-- Modules section -->\n" +" <module> ... </module>\n" +" <module> ... </module>\n" +" ...\n" +" </modules>\n" +" <options>\n" +" <!-- Options section -->\n" +" <option-group> ... </option-group>\n" +" <option-group> ... </option-group>\n" +" ...\n" +" </options>\n" +"</identity-configuration>]]>" +msgstr "" + +#. Tag: para +#: Identity.xml:233 +#, no-c-format +msgid "" +"By default you can find it in <emphasis>jboss-portal.sar/conf/identity/" +"identity-config.xml</emphasis>" +msgstr "" + +#. Tag: title +#: Identity.xml:235 +#, no-c-format +msgid "Datasources" +msgstr "" + +#. Tag: para +#: Identity.xml:236 +#, no-c-format +msgid "" +"This section defines datasource components. They will be processed and " +"instantiated before components in <emphasis role=\"bold\">Module</emphasis> " +"section, so they will be ready to serve them." +msgstr "" + +#. Tag: para +#: Identity.xml:240 +#, no-c-format +msgid "" +"This section isn't used with Database configuration as in JBoss Portal " +"services exposing Hibernate are defined separately. It is used by LDAP " +"configuration and we will use it as an example" +msgstr "" + +#. Tag: programlisting +#: Identity.xml:243 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<datasource>\n" +" <name>LDAP</name>\n" +" <service-name>portal:service=Module,type=LDAPConnectionContext</service-" +"name>\n" +" <class>org.jboss.portal.identity.ldap.LDAPConnectionContext</class>\n" +" <config>\n" +" <option>\n" +" <name>host</name>\n" +" <value>jboss.com</value>\n" +" </option>\n" +" <option>\n" +" <name>port</name>\n" +" <value>10389</value>\n" +" </option>\n" +" <option>\n" +" <name>adminDN</name>\n" +" <value>cn=Directory Manager</value>\n" +" </option>\n" +" <option>\n" +" <name>adminPassword</name>\n" +" <value>xxxxx</value>\n" +" </option>\n" +"\n" +" <!-- Other options here.... -->\n" +"\n" +" </config>\n" +"</datasource>]]>" +msgstr "" + +#. Tag: para +#: Identity.xml:246 +#, no-c-format +msgid "" +"If you look into JBoss Portal configuration files you will find that <![CDATA" +"[<service-name/> and <class/>]]> are specified in <emphasis role=\"bold" +"\">DefaultConfigFile</emphasis> and not in <emphasis role=\"bold" +"\">ConfigFile</emphasis>. So here is how it works: those two will be picked " +"up from default configuration. The same rule is effective for the options - " +"additional options will be picked up from default configuration. What is " +"linking configuration in those two files is the <emphasis role=\"bold\"><!" +"[CDATA[<name>]]></emphasis> tag." +msgstr "" + +#. Tag: title +#: Identity.xml:254 +#, no-c-format +msgid "Modules" +msgstr "" + +#. Tag: para +#: Identity.xml:255 +#, no-c-format +msgid "" +"Modules are core service components like UserModule, RoleModule and etc." +msgstr "" + +#. Tag: programlisting +#: Identity.xml:256 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<module>\n" +" <!--type used to correctly map in IdentityContext registry-->\n" +" <type>User</type>\n" +" <implementation>DB</implementation>\n" +"\n" +" <!--name of service and class for creating mbean-->\n" +" <service-name>portal:service=Module,type=User</service-name>\n" +" <class>org.jboss.portal.identity.db.HibernateUserModuleImpl</class>\n" +"\n" +" <!--set of options that are in the instantiated object-->\n" +" <config>\n" +" <option>\n" +" <name>sessionFactoryJNDIName</name>\n" +" <value>java:/portal/IdentitySessionFactory</value>\n" +" </option>\n" +" <option>\n" +" <name>jNDIName</name>\n" +" <value>java:/portal/UserModule</value>\n" +" </option>\n" +" </config>\n" +"</module>]]>" +msgstr "" + +#. Tag: para +#: Identity.xml:259 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">implementation</emphasis> - defines the scope under " +"which the configuration for different implementations of modules <emphasis " +"role=\"bold\">type</emphasis>s resides. It enables to define the default " +"options of the configuration of the different implementations of same module " +"types in one configuration file." +msgstr "" + +#. Tag: para +#: Identity.xml:267 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">type</emphasis> - must be unique name across all " +"modules defined in the main configuration file. This is important as module " +"will be stored with such name within IdentityContext registry at runtime. " +"Standard names are used (User, Role, Membership, UserProfile). Together with " +"<emphasis role=\"bold\">implementation</emphasis> will create unique pair " +"within file with default configuration values." +msgstr "" + +#. Tag: para +#: Identity.xml:275 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">service-name</emphasis> - will be used for the name " +"when registered as an MBean." +msgstr "" + +#. Tag: para +#: Identity.xml:280 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">class</emphasis> - Java class that will be use to " +"instantiate the module." +msgstr "" + +#. Tag: para +#: Identity.xml:285 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">config</emphasis> - contains options related to this " +"module" +msgstr "" + +#. Tag: para +#: Identity.xml:290 +#, no-c-format +msgid "" +"Here you can easily see the whole idea about having two config files - main " +"one and the one with default values. The above code snippet with User module " +"comes from <emphasis role=\"bold\">standardidentity-config.xml</emphasis>, " +"so the file that defines default configuration values. Because of this in " +"the main configuration file the definition of User module will be as short " +"as: <programlisting><![CDATA[\n" +"<module>\n" +" <!--type used to correctly map in IdentityContext registry-->\n" +" <type>User</type>\n" +" <implementation>DB</implementation>\n" +" <config/>\n" +"</module>]]></programlisting> As you can see we specify only the type and " +"the implementation - all the other values (service-name, class and set of " +"options) are read from default configuration. But remember that you can " +"still overwrite any of those values in the main config simply by overriding " +"them." +msgstr "" + +#. Tag: title +#: Identity.xml:303 +#, no-c-format +msgid "Options" +msgstr "" + +#. Tag: para +#: Identity.xml:304 +#, no-c-format +msgid "" +"This section provides common options that are accessible by identity " +"modules. We set options here that may need to be shared. They are grouped, " +"and can have many values:" +msgstr "" + +#. Tag: programlisting +#: Identity.xml:306 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<options>\n" +"<!--Common options section-->\n" +"<option-group>\n" +" <group-name>common</group-name>\n" +" <option>\n" +" <name>userCtxDN</name>\n" +" <value>ou=People,dc=example,dc=com</value>\n" +" </option>\n" +" <option>\n" +" <name>uidAttributeID</name>\n" +" <value>uid</value>\n" +" </option>\n" +" <option>\n" +" <name>passwordAttributeID</name>\n" +" <value>userPassword</value>\n" +" </option>\n" +" <option>\n" +" <name>roleCtxDN</name>\n" +" <value>ou=Roles,dc=example,dc=com</value>\n" +" </option>\n" +" <option>\n" +" <name>ridAttributeId</name>\n" +" <value>cn</value>\n" +" </option>\n" +" <option>\n" +" <name>roleDisplayNameAttributeID</name>\n" +" <value>cn</value>\n" +" </option>\n" +" <option>\n" +" <name>membershipAttributeID</name>\n" +" <value>member</value>\n" +" </option>\n" +" <option>\n" +" <name>membershipAttributeIsDN</name>\n" +" <value>true</value>\n" +" </option>\n" +"</option-group>\n" +"<option-group>\n" +" <group-name>userCreateAttibutes</group-name>\n" +" <option>\n" +" <name>objectClass</name>\n" +" <value>top</value>\n" +" <value>uidObject</value>\n" +" <value>person</value>\n" +" <value>inetUser</value>\n" +" </option>\n" +" <!--Schema requires those to have initial value-->\n" +" <option>\n" +" <name>cn</name>\n" +" <value>none</value>\n" +" </option>\n" +" <option>\n" +" <name>sn</name>\n" +" <value>none</value>\n" +" </option>\n" +"</option-group>]]>" +msgstr "" + +#. Tag: para +#: Identity.xml:308 +#, no-c-format +msgid "" +"In this section we use the same inheritance mechanism. When an option is not " +"set, its value will be read from the default config file. But this also " +"means that you may need to overwrite some values that are specific to your " +"LDAP architecture. All the options will be described along with module " +"implementations that use them." +msgstr "" + +#. Tag: title +#: Identity.xml:318 +#, no-c-format +msgid "User profile configuration" +msgstr "" + +#. Tag: para +#: Identity.xml:319 +#, no-c-format +msgid "" +"UserProfileModule has additional configuration file that defines user " +"properties. It is specified in configuration in:" +msgstr "" + +#. Tag: programlisting +#: Identity.xml:320 +#, no-c-format +msgid "" +"<![CDATA[\n" +" <module>\n" +" <type>UserProfile</type>\n" +" <implementation>DELEGATING</implementation>\n" +"\n" +" (...)\n" +"\n" +" <config>\n" +"\n" +" (...)\n" +"\n" +" <option>\n" +" <name>profileConfigFile</name>\n" +" <value>conf/identity/profile-config.xml</value>\n" +" </option>\n" +" </config>\n" +" </module>\n" +" ]]>" +msgstr "" + +#. Tag: para +#: Identity.xml:321 +#, no-c-format +msgid "" +"This means that you can configure user profile in <emphasis>jboss-portal.sar/" +"conf/identity/profile-config.xml</emphasis>" +msgstr "" + +#. Tag: programlisting +#: Identity.xml:323 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<profile>\n" +"\n" +" <property>\n" +" <name>user.name.nickName</name>\n" +" <type>java.lang.String</type>\n" +" <access-mode>read-only</access-mode>\n" +" <usage>mandatory</usage>\n" +" <display-name xml:lang=\"en\">Name</display-name>\n" +" <description xml:lang=\"en\">The user name</description>\n" +" <mapping>\n" +" <database>\n" +" <type>column</type>\n" +" <value>jbp_uname</value>\n" +" </database>\n" +" </mapping>\n" +" </property>\n" +"\n" +" <property>\n" +" <name>user.business-info.online.email</name>\n" +" <type>java.lang.String</type>\n" +" <access-mode>read-write</access-mode>\n" +" <usage>mandatory</usage>\n" +" <display-name xml:lang=\"en\">Email</display-name>\n" +" <description xml:lang=\"en\">The user real email</description>\n" +" <mapping>\n" +" <database>\n" +" <type>column</type>\n" +" <value>jbp_realemail</value>\n" +" </database>\n" +" <ldap>\n" +" <value>mail</value>\n" +" </ldap>\n" +" </mapping>\n" +" </property>\n" +"\n" +" <property>\n" +" <name>portal.user.location</name>\n" +" <type>java.lang.String</type>\n" +" <access-mode>read-write</access-mode>\n" +" <usage>optional</usage>\n" +" <display-name xml:lang=\"en\">Location</display-name>\n" +" <description xml:lang=\"en\">The user location</description>\n" +" <mapping>\n" +" <database>\n" +" <type>dynamic</type>\n" +" <value>portal.user.location</value>\n" +" </database>\n" +" </mapping>\n" +" </property>\n" +"\n" +" (...)\n" +"\n" +"</properties>\n" +" ]]>" +msgstr "" + +#. Tag: para +#: Identity.xml:324 +#, no-c-format +msgid "" +"Configuration file contains properties definition that can be retrieved " +"using the <emphasis role=\"bold\">PropertyInfo</emphasis> interface. Each " +"property used in portal has to be defined here." +msgstr "" + +#. Tag: para +#: Identity.xml:327 +#, no-c-format +msgid "" +"Some information provided here can have a large impact on the behavior of " +"the UserProfileModule. For instance <emphasis>access-mode</emphasis> can be " +"made read-only and the value provided in <emphasis>type</emphasis> will be " +"checked during <emphasis>setProperty()/getProperty()</emphasis> operations. " +"On the other hand tags like <emphasis>usage</emphasis>, " +"<emphasis>description</emphasis> or <emphasis>display-name</emphasis> have " +"mostly informational meaning at the moment and are used by the management " +"tools at runtime." +msgstr "" + +#. Tag: para +#: Identity.xml:334 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">name</emphasis> - property name. This value will be " +"used to refer to the property in <emphasis>UserProfileModule</emphasis>" +msgstr "" + +#. Tag: para +#: Identity.xml:337 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">type</emphasis> - Java type of property. This type " +"will be checked when in <emphasis>UserProfileModule</emphasis> methods " +"invocation." +msgstr "" + +#. Tag: para +#: Identity.xml:341 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">access-mode</emphasis> - possible values are " +"<emphasis>read-write</emphasis> and <emphasis>read-only</emphasis>" +msgstr "" + +#. Tag: para +#: Identity.xml:346 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">usage</emphasis> - property usage can be " +"<emphasis>mandatory</emphasis> or <emphasis>optional</emphasis>." +msgstr "" + +#. Tag: para +#: Identity.xml:350 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">display-name</emphasis> - property display name." +msgstr "" + +#. Tag: para +#: Identity.xml:354 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">description</emphasis> - description of property." +msgstr "" + +#. Tag: para +#: Identity.xml:358 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">mapping</emphasis> - defines how property is mapped " +"in the underlaying storage mechanism. It can be mapped in " +"<emphasis>database</emphasis> either as a <emphasis>column</emphasis> or " +"<emphasis>dynamic</emphasis> value. It can also be mapped as <emphasis>ldap</" +"emphasis> attribute." +msgstr "" + +#. Tag: para +#: Identity.xml:362 +#, no-c-format +msgid "" +"In current implementation <emphasis>column</emphasis> and <emphasis>dynamic</" +"emphasis> mappings have the same effect, as database mappings are defined in " +"hibernate configuration." +msgstr "" + +#. Tag: para +#: Identity.xml:365 +#, no-c-format +msgid "" +"Property can have both <emphasis>ldap</emphasis> and <emphasis>database</" +"emphasis> mappings. In such situation when LDAP support is enabled " +"<emphasis>ldap</emphasis> mapping will take precedense. Also even when using " +"LDAP some properties will be mapped to LDAP and some to database. Its " +"because LDAP schema doesn't support all attributes proper to for portal " +"properties. To solve this we have <emphasis role=\"bold" +"\">DelegatingUserProfileModuleImpl</emphasis> that will delegate method " +"invocation to <emphasis>ldap</emphasis> or <emphasis>database</emphasis> " +"related <emphasis>UserProfile</emphasis> module. When <emphasis>LDAP</" +"emphasis> support is enabled and property need to be stored in database user " +"will be synchronized into database when needed. This behavior can be " +"configured." +msgstr "" + +#. Tag: title +#: Identity.xml:376 +#, no-c-format +msgid "Identity modules implementations" +msgstr "" + +#. Tag: para +#: Identity.xml:378 +#, no-c-format +msgid "" +"Identity modules implementations related to LDAP are described in <xref " +"linkend=\"ldap.ldap_identity_modules\"/>." +msgstr "" + +#. Tag: title +#: Identity.xml:381 +#, no-c-format +msgid "Database modules" +msgstr "" + +#. Tag: para +#: Identity.xml:382 +#, no-c-format +msgid "" +"JBoss portal comes with a set of database related identity modules " +"implementations done using Hibernate - those are configured by default. " +"Those are not very configurable in <emphasis>identity-config.xml</emphasis> " +"file. The reason is that to keep backwards compatibility of database schema " +"with previous portal version, we reused most of hibernate implementation. If " +"you want to tweak the hibernate mappings you should look into files in " +"<emphasis role=\"bold\">jboss-portal.sar/conf/hibernate</emphasis>. Also " +"those modules rely on hibernate <emphasis>SessionFactory</emphasis> " +"components that are created in <emphasis>SessionFactoryBinder</emphasis> " +"mbeans defined in <emphasis>jboss-portal.sar/META-INF/jboss-service.xml</" +"emphasis>" +msgstr "" + +#. Tag: para +#: Identity.xml:388 +#, no-c-format +msgid "Classes implementing identity modules:" +msgstr "" + +#. Tag: para +#: Identity.xml:391 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">org.jboss.portal.identity.db." +"HibernateUserModuleImpl</emphasis> - implementaing <emphasis>UserModule</" +"emphasis> interface" +msgstr "" + +#. Tag: para +#: Identity.xml:394 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">org.jboss.portal.identity.db." +"HibernateRoleModuleImpl</emphasis> - implementaing <emphasis>RoleModule</" +"emphasis> interface" +msgstr "" + +#. Tag: para +#: Identity.xml:397 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">org.jboss.portal.identity.db." +"HibernateMembershipModuleImpl</emphasis> - implementaing " +"<emphasis>MembershipModule</emphasis> interface" +msgstr "" + +#. Tag: para +#: Identity.xml:400 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">org.jboss.portal.identity.db." +"HibernateUserProfileModuleImpl</emphasis> - implementing " +"<emphasis>UserProfileModule</emphasis> interface" +msgstr "" + +#. Tag: para +#: Identity.xml:405 +#, no-c-format +msgid "For each of those modules you can alter two config options:" +msgstr "" + +#. Tag: para +#: Identity.xml:407 +#, no-c-format +msgid "" +"<emphasis>sessionFactoryJNDIName</emphasis> - JNDI name under which " +"hibernate SessionFactory object is registered" +msgstr "" + +#. Tag: para +#: Identity.xml:411 +#, no-c-format +msgid "" +"<emphasis>jNDIName</emphasis> - JNDI name under which this module should be " +"registered" +msgstr "" + +#. Tag: title +#: Identity.xml:417 +#, no-c-format +msgid "Delegating UserProfile module" +msgstr "" + +#. Tag: para +#: Identity.xml:418 +#, no-c-format +msgid "" +"Delegating UserProfileModule implementation has very specific role. When we " +"use a storage mechanism like LDAP we may not be able to map all user " +"properties into LDAP attributes because of schema limitations. To solve this " +"problem we still can use the database to store user properties that do not " +"exist in the LDAP schema. The Delegating user profile module will recognize " +"if a property is mapped as <emphasis role=\"bold\">ldap</emphasis> or " +"<emphasis role=\"bold\">database</emphasis> and delegate " +"<emphasis>setProperty()/getProperty()</emphasis> method invocation to proper " +"module implementation. This is implemented in <emphasis role=\"bold\">org." +"jboss.portal.identity.DelegatingUserProfileModuleImpl</emphasis>. If " +"property is mapped either as <emphasis role=\"bold\">ldap</emphasis> and " +"<emphasis role=\"bold\">database</emphasis> the <emphasis role=\"bold" +"\">ldap</emphasis> mapping will have higher priority." +msgstr "" + +#. Tag: programlisting +#: Identity.xml:428 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<module>\n" +" <!--type used to correctly map in IdentityContext registry-->\n" +" <type>UserProfile</type>\n" +" <implementation>DELEGATING</implementation>\n" +"\n" +" <!--name of service and class for creating mbean-->\n" +" <service-name>portal:service=Module,type=UserProfile</service-name>\n" +" <class>org.jboss.portal.identity.DelegatingUserProfileModuleImpl</class>\n" +" <!--set of options that are set in instantiated object-->\n" +" <config>\n" +" <option>\n" +" <name>jNDIName</name>\n" +" <value>java:/portal/UserProfileModule</value>\n" +" </option>\n" +" <option>\n" +" <name>dbModuleJNDIName</name>\n" +" <value>java:/portal/DBUserProfileModule</value>\n" +" </option>\n" +" <option>\n" +" <name>profileConfigFile</name>\n" +" <value>conf/identity/profile-config.xml</value>\n" +" </option>\n" +" </config>\n" +"</module>]]>" +msgstr "" + +#. Tag: para +#: Identity.xml:429 +#, no-c-format +msgid "Module options are:" +msgstr "" + +#. Tag: para +#: Identity.xml:432 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">dbModuleJNDIName</emphasis> - JNDI name under which " +"database implementation of UserProfileModule is registered." +msgstr "" + +#. Tag: para +#: Identity.xml:435 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">ldapModuleJNDIName</emphasis> - JNDI name under " +"which ldap implementation of UserProfileModule is registered." +msgstr "" + +#. Tag: para +#: Identity.xml:438 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">profileConfigFile</emphasis> - configuration file " +"for user properties." +msgstr "" + +#. Tag: title +#: Identity.xml:445 +#, no-c-format +msgid "Database UserProfile module implementation" +msgstr "" + +#. Tag: para +#: Identity.xml:446 +#, no-c-format +msgid "" +"Because of the behavior described in the previous section, database " +"UserProfileModule requires some special features. If a user is present in " +"LDAP server but a writable property isn't mapped as an LDAP attribute, such " +"property requires to be stored in the database. In order to achieve such " +"result the user need to be synchronized from LDAP into the database first." +msgstr "" + +#. Tag: para +#: Identity.xml:449 +#, no-c-format +msgid "" +"Class <emphasis>org.jboss.portal.identity.db.HibernateUserProfileModuleImpl</" +"emphasis> has additional synchronization features. Here are the options:" +msgstr "" + +#. Tag: para +#: Identity.xml:453 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">synchronizeNonExistingUsers</emphasis> - when set to " +"\"true\" if the user subject to the operation does not exist, then it will " +"created it in database. By default it is \"true\"." +msgstr "" + +#. Tag: para +#: Identity.xml:457 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">acceptOtherImplementations</emphasis> - if set to " +"\"true\" module will accept user objects other than <emphasis>org.jboss." +"portal.identity.db.HibernateUserImpl</emphasis>. This is needed to enable " +"cooperation with UserModule implementations other than <emphasis>org.jboss." +"portal.identity.db.HibernateUserModuleImpl</emphasis>. The default value is " +"set \"true\"." +msgstr "" + +#. Tag: para +#: Identity.xml:463 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">defaultSynchronizePassword</emphasis> - if this " +"option is set, the value will be used as a password for synchronized user." +msgstr "" + +#. Tag: para +#: Identity.xml:466 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">randomSynchronizePassword</emphasis> - if this " +"option is set to \"true\" synchronized user will have random generated " +"password. This is mostly used for the security reasons. Default value is " +"\"false\"." +msgstr "" + +#. Tag: para +#: Identity.xml:469 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">sessionFactoryJNDIName</emphasis> - JNDI name under " +"which this user will be registered." +msgstr "" + +#. Tag: para +#: Identity.xml:472 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">profileConfigFile</emphasis> - file with user " +"profile configuration. If this option is not set, and we use delegating " +"UserProfileModule, profile configuration will be obtained from it." +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Identity_Portlets.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Identity_Portlets.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Identity_Portlets.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,1225 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Identity_Portlets.xml:6 +#, no-c-format +msgid "JBoss Portal Identity Portlets" +msgstr "" + +#. Tag: title +#: Identity_Portlets.xml:8 +#, no-c-format +msgid "Introduction" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:9 +#, no-c-format +msgid "" +"Two Identity Portlets are shipped by default: <itemizedlist> <listitem> " +"<para>The User Portlet</para> </listitem> <listitem> <para>The Identity " +"Management Portlet</para> </listitem> </itemizedlist> As the names indicate " +"- the User Portlet is responsible for actions related to the end user. " +"Whereas the Identity Management Portlet contains all the functionality for " +"managing users and roles." +msgstr "" + +#. Tag: title +#: Identity_Portlets.xml:24 Identity_Portlets.xml:151 +#, no-c-format +msgid "Caution" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:24 +#, no-c-format +msgid "" +"The Identity portlets will evolve over time, therefore usage and " +"configuration might change." +msgstr "" + +#. Tag: title +#: Identity_Portlets.xml:28 +#, no-c-format +msgid "Features" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:29 +#, no-c-format +msgid "The identity portlets provide the following features:" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:33 +#, no-c-format +msgid "" +"Email verification: The users can receive an email with a link on which they " +"must click to confirm the creation of the new account. (Disabled by default," +"see <xref linkend=\"identity_portlet_configuration_jbpm\"/>)" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:37 +#, no-c-format +msgid "" +"Captcha support: The users are prompted to copy letters from a deformed " +"image. (Disabled by default, see <xref linkend=" +"\"identity_portlet_configuration_captcha\"/>)" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:40 +#, no-c-format +msgid "" +"Lost password: The users can receive a new password by email, any user with " +"access to the admin portlet can also reset another user's password and send " +"the new one by email in one click. (Disabled by default, see <xref linkend=" +"\"identity_portlet_configuration_lost_password\"/>)" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:43 +#, no-c-format +msgid "" +"jBPM based user registration: Several business processes are available out " +"of the box (this includes administration approval), this can be extended to " +"custom ones. See <xref linkend=\"identity_portlet_configuration_jbpm\"/>." +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:47 +#, no-c-format +msgid "" +"User and role management: Ability for the administrator to add and edit " +"users as well as adding," +msgstr "" + +#. Tag: title +#: Identity_Portlets.xml:54 +#, no-c-format +msgid "Configuration" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:55 +#, no-c-format +msgid "This section covers the configuration of the Identity Portlets." +msgstr "" + +#. Tag: title +#: Identity_Portlets.xml:60 +#, no-c-format +msgid "Captcha support" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:61 +#, no-c-format +msgid "" +"CAPTCHA is an acronym for <literal>Completely Automated Public Turing test " +"to tell Computers and Humans Apart</literal>. This is providing a mechanism " +"to prevent automated programs from using different services. The User " +"Portlet uses JCaptcha to provide a challenge-response." +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:68 +#, no-c-format +msgid "" +"By default the captcha service needs a XServer to generate the images. For " +"using the captcha service without a XServer make sure you run the JVM with " +"the following option:" +msgstr "" + +#. Tag: programlisting +#: Identity_Portlets.xml:72 +#, no-c-format +msgid "-Djava.awt.headless=true" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:82 +#, no-c-format +msgid "The registration page with captcha." +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:83 +#, no-c-format +msgid "" +"The captcha support can be enabled by changing the portlet preference " +"'captcha' to 'true'. If enabled, captcha will be used for the registration " +"and lost password action." +msgstr "" + +#. Tag: programlisting +#: Identity_Portlets.xml:89 +#, no-c-format +msgid "" +"<![CDATA[...\n" +"<portlet>\n" +"...\n" +" <display-name>User portlet</display-name>\n" +"...\n" +" <portlet-preferences>\n" +" <preference>\n" +" <name>captcha</name>\n" +" <value>true</value>\n" +" </preference>\n" +" </portlet-preferences>\n" +"</portlet>\n" +"...]]>" +msgstr "" + +#. Tag: title +#: Identity_Portlets.xml:92 +#, no-c-format +msgid "Lost password" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:93 +#, no-c-format +msgid "" +"The lost password feature enables the end user to reset his password by " +"entering his username." +msgstr "" + +#. Tag: title +#: Identity_Portlets.xml:98 Identity_Portlets.xml:148 +#: Identity_Portlets.xml:323 Identity_Portlets.xml:380 +#: Identity_Portlets.xml:390 Identity_Portlets.xml:398 +#: Identity_Portlets.xml:407 Identity_Portlets.xml:605 +#, no-c-format +msgid "Note" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:98 +#, no-c-format +msgid "" +"This feature requires a properly configured MailModule. See <xref linkend=" +"\"emailConfiguration\"/>." +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:108 +#, no-c-format +msgid "The lost password page with captcha enabled." +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:111 +#, no-c-format +msgid "" +"The lost password feature can be enabled by changing the portlet preference " +"'lostPassword' to 'true'. If captcha is enabled it will be also used for " +"verifying the lost password action." +msgstr "" + +#. Tag: programlisting +#: Identity_Portlets.xml:117 +#, no-c-format +msgid "" +"<![CDATA[...\n" +"<portlet>\n" +"...\n" +" <display-name>User portlet</display-name>\n" +"...\n" +" <portlet-preferences>\n" +" <preference>\n" +" <name>lostPassword</name>\n" +" <value>true</value>\n" +" </preference>\n" +" </portlet-preferences>\n" +"</portlet>\n" +"...]]>" +msgstr "" + +#. Tag: title +#: Identity_Portlets.xml:120 +#, no-c-format +msgid "Reset password" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:121 +#, no-c-format +msgid "" +"The reset password feature is similar to the lost password feature, but it " +"is used in the User Management Portlet to reset the password of a user. That " +"means changing the password of a user is slightly simplified, because a " +"random password will be generated and sent to the users e-mail address." +msgstr "" + +#. Tag: programlisting +#: Identity_Portlets.xml:129 +#, no-c-format +msgid "" +"<![CDATA[...\n" +"<portlet>\n" +"...\n" +" <display-name>User management portlet</display-name>\n" +"...\n" +" <portlet-preferences>\n" +" <preference>\n" +" <name>resetPassword</name>\n" +" <value>true</value>\n" +" </preference>\n" +" </portlet-preferences>\n" +"</portlet>\n" +"...]]>" +msgstr "" + +#. Tag: title +#: Identity_Portlets.xml:132 +#, no-c-format +msgid "jBPM based user registration" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:133 +#, no-c-format +msgid "JBoss Portal supports three different subscription modes by default:" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:137 +#, no-c-format +msgid "" +"Automatic subscription (no jBPM required), the users can register and " +"directly login." +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:140 +#, no-c-format +msgid "" +"E-Mail validation, the users need to click on a link sent by email before " +"being able to login." +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:143 +#, no-c-format +msgid "" +"E-Mail validation and admin approval, the users need to validate their " +"email, then an admin needs to approve the newly created account." +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:148 +#, no-c-format +msgid "" +"The subscription mode has to be defined in the configuration file as " +"explained here: <xref linkend=\"identity_portlet_configuration_file\"/>." +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:151 +#, no-c-format +msgid "" +"Make sure that the application server is restarted after re-deploying the " +"Identity Portlets. This is required to make sure that the registration and " +"approval process works properly!" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:163 +#, no-c-format +msgid "" +"Approve or reject pending registrations " +"(<emphasis>jbp_identity_validation_approval_workflow</emphasis>)." +msgstr "" + +#. Tag: title +#: Identity_Portlets.xml:168 +#, no-c-format +msgid "The configuration file" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:169 +#, no-c-format +msgid "" +"The Identity Portlets use some metadata which can be easily changed in the " +"main configuration file, which is located at <literal>jboss-portal.sar/" +"portal-identity.sar/conf/identity-ui-configuration.xml</literal> as shown " +"here:" +msgstr "" + +#. Tag: programlisting +#: Identity_Portlets.xml:174 +#, no-c-format +msgid "" +"<![CDATA[<identity-ui-configuration>\n" +"\n" +" <subscription-mode>automatic</subscription-mode>\n" +" <admin-subscription-mode>automatic</admin-subscription-mode>\n" +" <overwrite-workflow>false</overwrite-workflow>\n" +" <email-domain>jboss.org</email-domain>\n" +" <email-from&gt;no-reply(a)jboss.com&lt;/email-from&gt;\n&quot; +" <password-generation-characters>a...Z</password-generation-" +"characters>\n" +" <default-roles>\n" +" <role>User</role>\n" +" </default-roles>\n" +"\n" +" <!-- user interface components -->\n" +" <ui-components>\n" +" <ui-component name=\"givenname\">\n" +" <property-ref>user.name.given</property-ref>\n" +" </ui-component>\n" +" <ui-component name=\"familyname\">\n" +" <property-ref>user.name.family</property-ref>\n" +" </ui-component>\n" +" ...\n" +"</identity-ui-configuration>]]>" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:178 +#, no-c-format +msgid "" +"<emphasis role=\"bold\"> subscription-mode: </emphasis> defines the User " +"Portlet registration process" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:184 Identity_Portlets.xml:206 +#, no-c-format +msgid "<emphasis>automatic:</emphasis> no validation nor approval (default)" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:187 Identity_Portlets.xml:210 +#, no-c-format +msgid "" +"<emphasis>jbp_identity_validation_workflow:</emphasis> e-mail validation, no " +"approval" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:190 Identity_Portlets.xml:214 +#, no-c-format +msgid "" +"<emphasis>jbp_identity_validation_approval_workflow:</emphasis> e-mail " +"validation and approval" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:193 Identity_Portlets.xml:218 +#, no-c-format +msgid "<emphasis>custom:</emphasis> Take a look at Customizing the workflow" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:200 +#, no-c-format +msgid "" +"<emphasis role=\"bold\"> admin-subscription-mode: </emphasis> jBPM process " +"used in the User Management Portlet for creating users" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:227 +#, no-c-format +msgid "" +"<emphasis role=\"bold\"> overwrite-workflow: </emphasis> if set to 'true' " +"the workflow will be overwritten during the next startup (default: false)" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:235 +#, no-c-format +msgid "" +"<emphasis role=\"bold\"> email-domain: </emphasis> e-mail domain used in the " +"validation e-mail by the template (can be anything)" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:243 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">email-from:</emphasis> e-mail fro field used by the " +"validation e-mail" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:249 +#, no-c-format +msgid "" +"<emphasis role=\"bold\"> password-generation-characters: </emphasis> " +"characters to use to generate a random password" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:257 +#, no-c-format +msgid "" +"<emphasis role=\"bold\"> default-roles: </emphasis> one or more default roles" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:263 +#, no-c-format +msgid "available element: <emphasis role=\"bold\">role</emphasis>" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:270 +#, no-c-format +msgid "" +"<emphasis role=\"bold\"> ui-components: </emphasis> Defines the available " +"user interface components. Take a look at the next section for further " +"details." +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:278 +#, no-c-format +msgid "" +"Due to the differentiation between subscription-mode and admin-subscription-" +"mode it is possible to require e-mail validation and approval for new " +"registrations and e-mail validation only when a user is created in the user " +"management portlet." +msgstr "" + +#. Tag: title +#: Identity_Portlets.xml:287 +#, no-c-format +msgid "Customize e-mail templates" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:288 +#, no-c-format +msgid "" +"The email templates can be found in the folder: <emphasis>portal-identity." +"sar/conf/templates/</emphasis>" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:291 +#, no-c-format +msgid "" +"New languages can be added by creating a new file like: " +"<emphasis>emailTemplate_fr.tpl</emphasis>" +msgstr "" + +#. Tag: title +#: Identity_Portlets.xml:297 +#, no-c-format +msgid "User interface customization" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:298 +#, no-c-format +msgid "" +"The following three examples describe common use cases for customizing the " +"User Portlet." +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:302 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">Example 1:</emphasis> Describes how to tag a input " +"field as required and add it to the registration page." +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:309 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">Example 2:</emphasis> Shows how to create a simple " +"dropdown menu." +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:315 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">Example 3:</emphasis> Describes how to add new " +"properties." +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:323 +#, no-c-format +msgid "" +"This is not a JavaServer Faces tutorial. Basic knowledge of this technology " +"is a precondition for customizing the User Portlet Interface." +msgstr "" + +#. Tag: title +#: Identity_Portlets.xml:328 +#, no-c-format +msgid "Example 1: required fields" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:329 +#, no-c-format +msgid "" +"This example explains how to change optional properties to required " +"properties, of course once this is done, we will also need to add the " +"corresponding fields in the registration page. Here are the modifications in " +"<emphasis>portal-identity.sar/conf/identity-ui-configuration.xml</emphasis>, " +"we simply changed the required element to true on our two fields " +"corresponding to the given and family names." +msgstr "" + +#. Tag: programlisting +#: Identity_Portlets.xml:337 +#, no-c-format +msgid "" +"<![CDATA[<identity-ui-configuration>\n" +"...\n" +" <!-- user interface components -->\n" +" ...\n" +" <ui-component name=\"givenname\">\n" +" <property-ref>user.name.given</property-ref>\n" +" <required>true</required>\n" +" </ui-component>\n" +" <ui-component name=\"familyname\">\n" +" <property-ref>user.name.family</property-ref>\n" +" <required>true</required>\n" +" </ui-component>\n" +" ...\n" +"</identity-ui-configuration>]]>" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:338 +#, no-c-format +msgid "" +"Now that we changed those values to \"required\" we need to give a chance to " +"the user to enter those values, here are the changes done in " +"<emphasis>portal-identity.sar/portal-identity.war/WEB-INF/jsf/common/" +"register.xhtml</emphasis>" +msgstr "" + +#. Tag: programlisting +#: Identity_Portlets.xml:342 +#, no-c-format +msgid "" +"<![CDATA[\n" +"...\n" +" <h:outputText value=\"#{bundle.IDENTITY_GIVENNAME}\"/>\n" +" <h:inputText id=\"givenname\" value=\"#{manager.uiUser.attribute." +"givenname}\"\n" +" required=\"#{metadataservice.givenname.required}\"/" +">\n" +" <h:panelGroup />\n" +" <h:message for=\"givenname\" />\n" +"\n" +" <h:outputText value=\"#{bundle.IDENTITY_FAMILYNAME}\"/>\n" +" <h:inputText id=\"lastname\" value=\"#{manager.uiUser.attribute." +"familyname}\"\n" +" required=\"#{metadataservice.familyname.required}" +"\"/>\n" +" <h:panelGroup />\n" +" <h:message for=\"lastname\"/>\n" +"...]]>" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:343 +#, no-c-format +msgid "" +"That's it - from now on the given name and family name will be required on " +"registration. We dynamically obtain the values from the descriptor. Now if i " +"just wanted to make them back to optional, i would change the values only in " +"the descriptor, letting the user enter or not those values." +msgstr "" + +#. Tag: title +#: Identity_Portlets.xml:351 +#, no-c-format +msgid "Example 2: dynamic values (dropdown menu with predefined values)" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:354 +#, no-c-format +msgid "" +"If the data to enter is a choice instead of a free-text value, you can also " +"define those in the descriptor like shown here:" +msgstr "" + +#. Tag: programlisting +#: Identity_Portlets.xml:358 +#, no-c-format +msgid "" +"<![CDATA[<identity-ui-configuration>\n" +"...\n" +" <!-- user interface components -->\n" +" ...\n" +" <ui-component name=\"interests\">\n" +" <property-ref>portal.user.interests</property-ref>\n" +" <values>\n" +" <value key=\"board\">snowboarding</value>\n" +" <value key=\"ski\">skiing</value>\n" +" <value key=\"sledge\">sledging</value>\n" +" </values>\n" +" </ui-component>\n" +" ...\n" +"</identity-ui-configuration>]]>" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:359 +#, no-c-format +msgid "" +"<emphasis> In portal-identity.sar/portal-identity.war/WEB-INF/jsf/common/" +"profile.xhtml </emphasis> - change inputText to a selectOneMenu:" +msgstr "" + +#. Tag: programlisting +#: Identity_Portlets.xml:365 +#, no-c-format +msgid "" +"<![CDATA[\n" +" ...\n" +" <h:outputText value=\"#{bundle.IDENTITY_INTERESTS}\"/>\n" +" <h:selectOneMenu id=\"interests\" value=\"#{manager.uiUser.attribute." +"interests}\"\n" +" required=\"#{metadataservice.interests.required}\">\n" +" <f:selectItems value=\"#{metadataservice.interests.values}\" />\n" +" </h.selectOneMenu>\n" +" <h:panelGroup />\n" +" <h:message for=\"interests\"/>\n" +"...\n" +"]]>" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:366 +#, no-c-format +msgid "" +"For localizing dynamic values it is also possible to use the resource " +"bundle. This can be done by adding the key with a prefix (to i.e. " +"<emphasis>Identity.properties</emphasis>) like in the following listing. The " +"key will be stored in the users property and is used to identify the " +"element. The value of the configuration file will only be used if no " +"localization information is found." +msgstr "" + +#. Tag: programlisting +#: Identity_Portlets.xml:371 +#, no-c-format +msgid "" +"<![CDATA[\n" +"...\n" +"IDENTITY_DYNAMIC_VALUE_BOARD=localized snowboarding\n" +"IDENTITY_DYNAMIC_VALUE_SKI=localized skiing\n" +"IDENTITY_DYNAMIC_VALUE_SLEDGE=localized sledging\n" +"...\n" +"]]>" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:373 +#, no-c-format +msgid "If the value is not required a blank element will be added at the top." +msgstr "" + +#. Tag: title +#: Identity_Portlets.xml:378 +#, no-c-format +msgid "Example 3: adding new properties" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:380 +#, no-c-format +msgid "" +"Please make sure you read at least the section about user profile " +"configuration: <xref linkend=\"user_profile_configuration\"/>, to add a new " +"value on the interface it also has to be defined in your model, as shown on " +"Step 1." +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:384 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">step 1:</emphasis> add a new property to " +"<emphasis>profile-config.xml</emphasis> e.g. a dynamic property called " +"gender:" +msgstr "" + +#. Tag: programlisting +#: Identity_Portlets.xml:388 +#, no-c-format +msgid "" +"<![CDATA[\n" +"...\n" +" <property>\n" +" <name>user.gender</name>\n" +" <type>java.lang.String</type>\n" +" <access-mode>read-write</access-mode>\n" +" <usage>optional</usage>\n" +" <display-name xml:lang=\"en\">Gender</display-name>\n" +" <description xml:lang=\"en\">The gender</description>\n" +" <mapping>\n" +" <database>\n" +" <type>dynamic</type>\n" +" <value>user.gender</value>\n" +" </database>\n" +" </mapping>\n" +" </property>\n" +"...\n" +"]]>" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:390 +#, no-c-format +msgid "" +"It is recommended to use the 'User Information Attribute Names' from the " +"<ulink url=\"http://jcp.org/en/jsr/detail?id=168\">Portlet Specification</" +"ulink> for defining properties." +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:392 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">step 2:</emphasis> add the property to the identity-" +"ui-configuration: (<emphasis>portal-identity.sar/conf/identity-ui-" +"configuration.xml</emphasis>)" +msgstr "" + +#. Tag: programlisting +#: Identity_Portlets.xml:396 +#, no-c-format +msgid "" +"<![CDATA[\n" +"...\n" +" <ui-component name=\"gender\">\n" +" <property-ref>user.gender</property-ref>\n" +" <required>true</required>\n" +" <values>\n" +" <value key=\"male\">Male</value>\n" +" <value key=\"female\">Female</value>\n" +" </values>\n" +" </ui-component>\n" +"...\n" +"]]>" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:398 +#, no-c-format +msgid "" +"The property-ref must match a property from the <emphasis>profile-config." +"xml</emphasis>." +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:401 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">step 3:</emphasis> add your custom ui-component to " +"the profile page: (<emphasis>portal-identity.sar/portal-identity.war/WEB-INF/" +"jsf/profile.xhtml</emphasis>)" +msgstr "" + +#. Tag: programlisting +#: Identity_Portlets.xml:405 +#, no-c-format +msgid "" +"<![CDATA[\n" +"...\n" +" <h:outputText value=\"#{bundle.IDENTITY_GENDER}\"/>\n" +" <h:selectOneMenu id=\"gender\" value=\"#{manager.uiUser.attribute." +"gender}\"\n" +" required=\"#{metadataservice.gender.required}\">\n" +" <f:selectItems value=\"#{metadataservice.gender.values}\" /" +">\n" +" </h.selectOneMenu>\n" +" <h:panelGroup />\n" +" <h:message for=\"gender\"/>\n" +"...\n" +"]]>" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:407 +#, no-c-format +msgid "Don't forget to add the localization elements." +msgstr "" + +#. Tag: title +#: Identity_Portlets.xml:411 +#, no-c-format +msgid "Illustration" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:422 +#, no-c-format +msgid "Illustration of the relationship between the configuration files." +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:426 +#, no-c-format +msgid "The JSF-View in more detail:" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:430 +#, no-c-format +msgid "" +"<emphasis role=\"bold\"> manager.uiUser.attribute:</emphasis> manages and " +"stores the dynamic properties" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:435 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">examples:</emphasis> <emphasis>manager.uiUser." +"attribute.gender</emphasis>, <emphasis>manager.uiUser.attribute.interests</" +"emphasis>" +msgstr "" + +#. Tag: programlisting +#: Identity_Portlets.xml:438 +#, no-c-format +msgid "" +"<![CDATA[<h:inputText id=\"gender\" value=\"#{manager.uiUser.attribute." +"gender}\" />]]>" +msgstr "" + +#. Tag: emphasis +#: Identity_Portlets.xml:446 +#, no-c-format +msgid "metadataservice" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:451 +#, no-c-format +msgid "" +"<emphasis role=\"bold\"> required </emphasis> - references the required " +"attribute from the ui-component example: <emphasis>metadataservice.gender." +"required</emphasis>" +msgstr "" + +#. Tag: programlisting +#: Identity_Portlets.xml:457 +#, no-c-format +msgid "" +"<![CDATA[<h:inputText id=\"gender\" value=\"#{manager.uiUser.attribute." +"gender}\" required=\"#{metadataservice.gender.required}\"/>]]>" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:461 +#, no-c-format +msgid "" +"<emphasis role=\"bold\"> values </emphasis> - references the values list " +"from the ui-component example: <emphasis>metadataservice.gender.values</" +"emphasis>" +msgstr "" + +#. Tag: programlisting +#: Identity_Portlets.xml:467 +#, no-c-format +msgid "" +"<![CDATA[<h:selectOneMenu id=\"interests\" value=\"#{manager.uiUser." +"attribute.interests}\">\n" +" <f:selectItems value=\"#{metadataservice.interests.values}\" />\n" +"</h:selectOneMenu>]]>" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:471 +#, no-c-format +msgid "" +"<emphasis role=\"bold\"> validator </emphasis> - references the name of a " +"registered JSF validator example:<emphasis>metadataservice.gender.validator</" +"emphasis> - the first validator of the validator list example: " +"<emphasis>metadataservice.gender.validators[0]</emphasis> - the validator " +"list with an index" +msgstr "" + +#. Tag: programlisting +#: Identity_Portlets.xml:480 +#, no-c-format +msgid "" +"<![CDATA[<f:validator validatorId=\"#{metadataservice.gender.validator}\"/>]]" +">" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:484 +#, no-c-format +msgid "" +"<emphasis role=\"bold\"> converter </emphasis> - references the name of a " +"registered JSF converter example: <emphasis>metadataservice.gender." +"converter</emphasis>" +msgstr "" + +#. Tag: programlisting +#: Identity_Portlets.xml:490 +#, no-c-format +msgid "" +"<![CDATA[<f:converter converterId=\"#{metadataservice.gender.converter}\"/>]]" +">" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:494 +#, no-c-format +msgid "" +"<emphasis role=\"bold\"> readOnly </emphasis> - references the access-mode " +"of <emphasis>profile-config.xml</emphasis> possible usage i.e. in <emphasis>/" +"WEB-INF/jsf/common/profile.xhtml</emphasis>" +msgstr "" + +#. Tag: programlisting +#: Identity_Portlets.xml:500 +#, no-c-format +msgid "" +"<![CDATA[<h:inputText value=\"#{manager.uiUser.attribute.nickname}\" " +"disabled=\"#{metadataservice.nickname.readOnly}\" />]]>" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:509 +#, no-c-format +msgid "" +"The values of the profile-config.xml have a higher priority than the values " +"in the user portlet configuration. That means if the 'usage' is 'mandatory' " +"in <emphasis>profile-config.xml</emphasis> and 'required' is 'false' it will " +"be overwritten by the value from the profile config!" +msgstr "" + +#. Tag: title +#: Identity_Portlets.xml:518 +#, no-c-format +msgid "Customizing the View Profile page" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:519 +#, no-c-format +msgid "" +"By default not all values of the user profile will be displayed on the " +"<emphasis>View profile</emphasis> page. For customization it is possible to " +"add further properties to the page by editing the file: <emphasis>portal-" +"identity.sar/portal-identity.war/WEB-INF/jsf/profile/viewProfile.xhtml</" +"emphasis>" +msgstr "" + +#. Tag: title +#: Identity_Portlets.xml:526 +#, no-c-format +msgid "Customizing the workflow" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:527 +#, no-c-format +msgid "" +"For more details about jBPM please read the <ulink url=\"http://docs.jboss." +"com/jbpm/v3/userguide/index.html\">jBPM documentation</ulink>" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:528 +#, no-c-format +msgid "" +"The process definitions are located in: <emphasis>portal-identity.sar/conf/" +"processes</emphasis>. To create a custom workflow, you can extend the " +"existing process description file: <emphasis>custom.xml</emphasis>." +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:532 +#, no-c-format +msgid "Available variables in the business process:" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:536 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">name:</emphasis> portalURL <emphasis role=\"bold" +"\">type:</emphasis> <emphasis>java.lang.String</emphasis> <emphasis role=" +"\"bold\">description:</emphasis> represents the full url of the portal e.g. " +"<emphasis> http://localhost:8080/portal </emphasis>" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:552 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">name:</emphasis> locale <emphasis role=\"bold\">type:" +"</emphasis> <emphasis>java.util.Locale</emphasis> <emphasis role=\"bold" +"\">description:</emphasis> the requested locale at registration" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:565 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">name:</emphasis> email <emphasis role=\"bold\">type:" +"</emphasis> <emphasis>java.lang.String</emphasis> <emphasis role=\"bold" +"\">description:</emphasis> the e-mail address of the user in case of " +"registration. In case of changing the e-mail the new e-mail address." +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:578 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">name:</emphasis> user <emphasis role=\"bold\">type:</" +"emphasis> <emphasis> org.jboss.portal.core.identity.services.workflow." +"UserContainer </emphasis> <emphasis role=\"bold\">description:</emphasis> " +"Seralizable Object containing user information through the jBPM process" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:592 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">name:</emphasis> validationHash <emphasis role=\"bold" +"\">type:</emphasis> <emphasis>java.lang.String</emphasis> <emphasis role=" +"\"bold\">description:</emphasis> hash used for the validation part. Only " +"available after executing SendValidationEmailAction" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:605 +#, no-c-format +msgid "" +"Make sure that the filename and the process name match! e.g. <emphasis>conf/" +"processes/custom.xml</emphasis> and process-definition name=\"custom\"." +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:610 +#, no-c-format +msgid "" +"When using a custom workflow it is possible to customize the status message " +"after registering in the locale bundle: ( e.g. <emphasis>portal-identity.sar/" +"conf/bundles/Identity.properties</emphasis>)" +msgstr "" + +#. Tag: programlisting +#: Identity_Portlets.xml:615 +#, no-c-format +msgid "" +"<![CDATA[\n" +"\n" +"IDENTITY_VERIFICATION_STATUS_REGISTER_CUSTOM=Customized message here\n" +"\n" +"]]>" +msgstr "" + +#. Tag: title +#: Identity_Portlets.xml:617 +#, no-c-format +msgid "Duration of process validity" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:618 +#, no-c-format +msgid "" +"By default requests (e.g. e-mail validation and registrations) expire after " +"some time in the validation state. Therefore it is not required to add " +"additional maintenance mechanism to invalidate a request. The default " +"expiration time is 2 days, but is quite easy to change the timing by editing " +"the <emphasis>duedate</emphasis> attribute in the process definition. " +"changes in: <emphasis>portal-identity.sar/conf/processes/*.xml</emphasis>" +msgstr "" + +#. Tag: programlisting +#: Identity_Portlets.xml:624 +#, no-c-format +msgid "" +"<![CDATA[<process-definition>\n" +"...\n" +" <state name=\"validate_email\">\n" +" <timer name=\"time_to_expire\" duedate=\"2 days\" transition=" +"\"timedOut\" />\n" +" </state>\n" +"...\n" +"</process-definition>]]>" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:626 +#, no-c-format +msgid "" +"For further information take a look at the <ulink url=\"http://docs.jboss." +"com/jbpm/v3/userguide/index.html\">jBPM documentation</ulink> on " +"<emphasis>Duration</emphasis>." +msgstr "" + +#. Tag: title +#: Identity_Portlets.xml:632 +#, no-c-format +msgid "Disabling the Identity Portlets" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:633 +#, no-c-format +msgid "" +"Due to the fact that the former user portlets are still included in JBoss " +"Portal 2.6.2 it is possible to activate it in the Portal Admin interface, by " +"using the PortletInstances:" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:638 +#, no-c-format +msgid "<emphasis>UserPortletInstance:</emphasis> The former user portlet" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:641 +#, no-c-format +msgid "" +"<emphasis>RolePortletInstance:</emphasis> The former role managment portlet" +msgstr "" + +#. Tag: title +#: Identity_Portlets.xml:647 +#, no-c-format +msgid "Enabling the Identity Portlets" +msgstr "" + +#. Tag: para +#: Identity_Portlets.xml:648 +#, no-c-format +msgid "" +"When migrating from former versions of JBoss Portal the Identity User " +"Portlets won't be displayed by default, but windows can be created on basis " +"of the existing Portlet Instances which are deployed by default. (The " +"instances names being <literal>IdentityUserPortletInstance</literal> and " +"<literal>IdentityAdminPortletInstance</literal>.)" +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Installation.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Installation.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Installation.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,28 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Installation.xml:6 +#, no-c-format +msgid "Installation" +msgstr "" + +#. Tag: para +#: Installation.xml:7 +#, no-c-format +msgid "" +"Please see the accompanying Installation Guide on how to install Enterprise " +"Portal Platform." +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Jboss_Portlet_DTD.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Jboss_Portlet_DTD.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Jboss_Portlet_DTD.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,370 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Jboss_Portlet_DTD.xml:7 +#, no-c-format +msgid "jboss-portlet.xml DTD" +msgstr "" + +#. Tag: programlisting +#: Jboss_Portlet_DTD.xml:9 +#, no-c-format +msgid "" +"<![CDATA[\n" +"\n" +" <?xml version=\"1.0\" encoding=\"UTF-8\" ?>\n" +"\n" +"<!--" +"~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n" +" ~ JBoss, a division of Red " +"Hat ~\n" +" ~ Copyright 2006, Red Hat Middleware, LLC, and " +"individual ~\n" +" ~ contributors as indicated by the @authors tag. See " +"the ~\n" +" ~ copyright.txt in the distribution for a full listing " +"of ~\n" +" ~ individual " +"contributors. ~\n" +" ~ " +"~\n" +" ~ This is free software; you can redistribute it and/or modify " +"it ~\n" +" ~ under the terms of the GNU Lesser General Public License " +"as ~\n" +" ~ published by the Free Software Foundation; either version 2.1 " +"of ~\n" +" ~ the License, or (at your option) any later " +"version. ~\n" +" ~ " +"~\n" +" ~ This software is distributed in the hope that it will be " +"useful, ~\n" +" ~ but WITHOUT ANY WARRANTY; without even the implied warranty " +"of ~\n" +" ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the " +"GNU ~\n" +" ~ Lesser General Public License for more " +"details. ~\n" +" ~ " +"~\n" +" ~ You should have received a copy of the GNU Lesser General " +"Public ~\n" +" ~ License along with this software; if not, write to the " +"Free ~\n" +" ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, " +"MA ~\n" +" ~ 02110-1301 USA, or see the FSF site: http://www.fsf." +"org. ~\n" +" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~--" +">\n" +"\n" +"<!-- The additional configuration elements of the JBoss portlet container.\n" +"\n" +"<!DOCTYPE portlet-app PUBLIC\n" +" \"-//JBoss Portal//DTD JBoss Portlet 2.6//EN\"\n" +" \"http://www.jboss.org/portal/dtd/jboss-portlet_2_6.dtd\">\n" +"-->\n" +"\n" +"<!--\n" +"The remotable element is used to configure the default behavior of the " +"portlets with\n" +"respect to WSRP exposure.\n" +"\n" +"For each portlet defined in portlet.xml, it is possible to configure " +"specific\n" +"settings of the portlet container.\n" +"\n" +"It is also possible to inject services in the portlet context of the " +"application\n" +"using the service elements.\n" +"-->\n" +"<!ELEMENT portlet-app (remotable?,portlet*,service*)>\n" +"\n" +"<!--\n" +"Additional configuration for a portlet.\n" +"\n" +"The portlet-name defines the name of the portlet. It must match a portlet " +"defined already\n" +"in portlet.xml of the same web application.\n" +"\n" +"The remotable element configures the portlet exposure to WSRP. If no value " +"is present\n" +"then the value considered is either the value defined globally at the " +"portlet\n" +"application level or false.\n" +"\n" +"The trans-attribute value specifies the behavior of the portlet when it is " +"invoked at\n" +"runtime with respect to the transactionnal context. According to how the " +"portlet is\n" +"invoked a transaction may exist or not before the portlet is invoked. " +"Usually in the\n" +"local context the portal transaction could be present. By default the value " +"considered is\n" +" NotSupported which means that the portal transaction will be suspended for " +"the duration\n" +" of the portlet invocation.\n" +"\n" +"Example:\n" +"\n" +"<portlet>\n" +" <portlet-name>MyPortlet</portlet-name>\n" +" <remotable>true</remotable>\n" +" <trans-attribute>Required</trans-attribute>\n" +"</portlet>\n" +"\n" +"-->\n" +"<!ELEMENT portlet (portlet-name,remotable?,ajax?,session-config?," +"transaction?,\n" +" header-content?,portlet-info?)>\n" +"\n" +"<!--\n" +"The portlet name.\n" +"-->\n" +"<!ELEMENT portlet-name (#PCDATA)>\n" +"\n" +"<!--\n" +"The remotable value is used for WSRP exposure. The accepted values are the\n" +"litterals true of false.\n" +"-->\n" +"<!ELEMENT remotable (#PCDATA)>\n" +"\n" +"<!--\n" +"The ajax tag allows to configure the ajax capabilities of the portlet. If\n" +"the portlet is tagged as partial-refresh then the portal may use partial " +"page\n" +"refreshing and render only that portlet. If the portlet partial-refresh " +"value\n" +"is false, then the portal will perform a full page refresh when the portlet " +"is refreshed.\n" +"-->\n" +"<!ELEMENT ajax (partial-refresh)>\n" +"\n" +"<!--\n" +"The authorized values for the partial-refresh element are true or false.\n" +"-->\n" +"<!ELEMENT partial-refresh (#PCDATA)>\n" +"\n" +"<!--\n" +"Additional portlet information\n" +"-->\n" +"<!ELEMENT portlet-info (icon?)>\n" +"\n" +"<!--\n" +"Defines icons for the portlet, they can be used by the administration " +"portlet\n" +"to represent a particular portlet.\n" +"-->\n" +"<!ELEMENT icon (small-icon?, large-icon?)>\n" +"\n" +"<!--\n" +"A small icon image, usually 16x16, gif, jpg and png are usually supported.\n" +"An absolute URL or a URL starting with a '/' in the context of the webapp " +"are accepted:\n" +"eg. http://www.example.com/images/smallIcon.png\n" +"eg. /images/smallIcon.png\n" +"-->\n" +"<!ELEMENT small-icon (#PCDATA)>\n" +"\n" +"<!--\n" +"A large icon image, usually 32x32, gif, jpg and png are usually supported.\n" +"An absolute URL or a URL starting with a '/' in the context of the webapp " +"are accepted:\n" +"eg. http://www.example.com/images/smallIcon.png\n" +"eg. /images/smallIcon.png\n" +"-->\n" +"<!ELEMENT large-icon (#PCDATA)>\n" +"\n" +"<!--\n" +"This element configure the portlet session of the portlet.\n" +"\n" +"The distributed element instructs the container to distribute the session " +"attributes\n" +"using the portal session replication. It applies only to local portlets are " +"not to\n" +"remote portlets. The default value is false.\n" +"\n" +"Example:\n" +"\n" +"<session-config>\n" +" <distributed>true</distributed>\n" +"</session-config>\n" +"\n" +"-->\n" +"<!ELEMENT session-config (distributed)>\n" +"\n" +"<!--\n" +"The authorized values for the distributed element are true or false.\n" +"-->\n" +"<!ELEMENT distributed (#PCDATA)>\n" +"\n" +"<!--\n" +"Defines how the portlet behaves with the transactionnal context. The default " +"value\n" +"is Never.\n" +"\n" +"Example:\n" +"\n" +"<transaction>\n" +" <trans-attribute>Required</transaction>\n" +"<transaction>\n" +"-->\n" +"<!ELEMENT transaction (trans-attribute)>\n" +"\n" +"<!--\n" +"The trans-attribute value defines the transactionnal behavior. The accepted " +"values\n" +"are Required, Mandatory, Never, Supports, NotSupported and RequiresNew.\n" +"-->\n" +"<!ELEMENT trans-attribute (#PCDATA)>\n" +"\n" +"<!--\n" +"Specify content which should be included in the portal aggregated page when " +"the portlet\n" +"is present on that page. This setting only applies when the portlet is used " +"in the local mode.\n" +"-->\n" +"<!ELEMENT header-content (link|script|meta)*>\n" +"\n" +"<!--\n" +"Creates a header markup element for linked resources,\n" +"see http://www.w3.org/TR/html401/struct/links.html#h-12.3\n" +"\n" +"At runtime the href attribute value will be prefixed with the context path\n" +"of the web application.\n" +"\n" +"Example:\n" +"\n" +"<link rel=\"stylesheet\" type=\"text/css\" href=\"/style.css\" media=\"screen" +"\"/>\n" +"\n" +"will produce at runtime the following markup\n" +"\n" +"<link rel=\"stylesheet\" type=\"text/css\" href=\"/my-web-application/style." +"css\" media=\"screen\"/>\n" +"-->\n" +"<!ATTLIST link\n" +" href CDATA #IMPLIED\n" +" rel CDATA #IMPLIED\n" +" type CDATA #IMPLIED\n" +" media CDATA #IMPLIED\n" +" title CDATA #IMPLIED>\n" +"\n" +"<!--\n" +"No content is allowed inside an link element.\n" +"-->\n" +"<!ELEMENT link EMPTY>\n" +"\n" +"<!--\n" +"Creates a header markup for scripting,\n" +"see http://www.w3.org/TR/html401/interact/scripts.html\n" +"\n" +"At runtime the src attribute value will be prefixed with the context path\n" +"of the web application.\n" +"\n" +"Example 1:\n" +"\n" +"<script type=\"text/javascript\" src=\"/myscript.js\"></script>\n" +"\n" +"will produce at runtime the following markup\n" +"\n" +"<script type=\"text/javascript\" src=\"/my-web-application/myscript.js\"></" +"script>\n" +"\n" +"Example 2:\n" +"\n" +"<script type=\"text/javascript\">\n" +" function hello() {\n" +" alert('Hello');\n" +" }\n" +"</script>\n" +"-->\n" +"<!ATTLIST script\n" +" src CDATA #IMPLIED\n" +" type CDATA #IMPLIED\n" +" language CDATA #IMPLIED>\n" +"\n" +"<!--\n" +"The script header element can contain inline script definitions.\n" +"-->\n" +"<!ELEMENT script (#PCDATA)>\n" +"\n" +"<!--\n" +"Creates a header markup for adding meta data to a page,\n" +"see http://www.w3.org/TR/html401/struct/global.html#h-7.4.4\n" +"\n" +"Example:\n" +"\n" +"<meta name=\"keywords\" content=\"jboss, portal, redhat\"/>\n" +"-->\n" +"<!ATTLIST meta\n" +" name CDATA #REQUIRED\n" +" content CDATA #REQUIRED>\n" +"\n" +"<!--\n" +"No content is allowed for meta element.\n" +"-->\n" +"<!ELEMENT meta EMPTY>\n" +"\n" +"<!--\n" +"Declare a service that will be injected by the portlet container as an\n" +"attribute of the portlet context.\n" +"\n" +"Example:\n" +"\n" +"<service>\n" +" <service-name>UserModule</service-name>\n" +" <service-class>org.jboss.portal.identity.UserModule</service-class>\n" +" <service-ref>:service=Module,type=User</service-ref>\n" +"</service>\n" +"\n" +"In the portlet it is then possible to use it by doing a lookup on the " +"service\n" +"name, for example in the init() lifecycle method :\n" +"\n" +"public void init()\n" +"{\n" +" UserModule userModule = (UserModule)getPortletContext().getAttribute" +"(\"UserModule\");\n" +"}\n" +"\n" +"-->\n" +"<!ELEMENT service (service-name,service-class,service-ref)>\n" +"\n" +"<!--\n" +"The service name that will be used to bind the service as a portlet context " +"attribute.\n" +"-->\n" +"<!ELEMENT service-name (#PCDATA)>\n" +"\n" +"<!--\n" +"The full qualified name of the interface that the service implements.\n" +"-->\n" +"<!ELEMENT service-class (#PCDATA)>\n" +"\n" +"<!--\n" +"The reference to the service. In the JMX Microkernel environment it consist " +"of the JMX\n" +"name of the service MBean. For an MBean reference if the domain is left out, " +"then the\n" +"current domain of the portal will be used.\n" +"-->\n" +"<!ELEMENT service-ref (#PCDATA)>\n" +"\n" +" \n" +"]]>" +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Ldap.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Ldap.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Ldap.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,1799 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Ldap.xml:12 +#, no-c-format +msgid "LDAP" +msgstr "" + +#. Tag: para +#: Ldap.xml:13 +#, no-c-format +msgid "This chapter describes how to setup LDAP support in JBoss Portal" +msgstr "" + +#. Tag: title +#: Ldap.xml:14 Ldap.xml:55 Ldap.xml:92 Ldap.xml:110 Ldap.xml:362 Ldap.xml:466 +#, no-c-format +msgid "Note" +msgstr "" + +#. Tag: para +#: Ldap.xml:15 +#, no-c-format +msgid "" +"To be able to fully understand this chapter you should also read <xref " +"linkend=\"identity\"/> and <xref linkend=\"authentication\"/> before." +msgstr "" + +#. Tag: title +#: Ldap.xml:18 +#, no-c-format +msgid "How to enable LDAP usage in JBoss Portal" +msgstr "" + +#. Tag: para +#: Ldap.xml:19 +#, no-c-format +msgid "" +"We'll describe here the simple steps that you will need to perform to enable " +"LDAP support in JBoss Portal. For additional information you need to read " +"more about configuration of identity and specific implementations of " +"identity modules" +msgstr "" + +#. Tag: para +#: Ldap.xml:21 +#, no-c-format +msgid "There are two ways to achieve this:" +msgstr "" + +#. Tag: para +#: Ldap.xml:24 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">jboss-portal.sar/META-INF/jboss-service.xml</" +"emphasis> in section:" +msgstr "" + +#. Tag: programlisting +#: Ldap.xml:28 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<mbean\n" +" code=\"org.jboss.portal.identity.IdentityServiceControllerImpl\"\n" +" name=\"portal:service=Module,type=IdentityServiceController\"\n" +" xmbean-dd=\"\"\n" +" xmbean-code=\"org.jboss.portal.jems.as.system.JBossServiceModelMBean\">\n" +" <xmbean/>\n" +" <depends>portal:service=Hibernate</depends>\n" +" <attribute name=\"JndiName\">java:/portal/IdentityServiceController</" +"attribute>\n" +" <attribute name=\"RegisterMBeans\">true</attribute>\n" +" <attribute name=\"ConfigFile\">conf/identity/identity-config.xml</" +"attribute>\n" +" <attribute name=\"DefaultConfigFile\">conf/identity/standardidentity-" +"config.xml</attribute>\n" +"</mbean>]]>" +msgstr "" + +#. Tag: para +#: Ldap.xml:29 +#, no-c-format +msgid "" +"change <emphasis role=\"bold\">identity-config.xml</emphasis> to <emphasis " +"role=\"bold\">ldap_identity-config.xml</emphasis>" +msgstr "" + +#. Tag: para +#: Ldap.xml:37 +#, no-c-format +msgid "" +"Swap the names or content of files in <emphasis role=\"bold\">jboss-portal." +"sar/conf/identity/identity-config.xml</emphasis> and <emphasis role=\"bold" +"\">jboss-portal.sar/conf/identity/ldap_identity-config.xml</emphasis>" +msgstr "" + +#. Tag: para +#: Ldap.xml:45 +#, no-c-format +msgid "" +"After doing one of the above changes you need to edit configuration file " +"that you choose to use (identity-config.xml or ldap_identity-config.xml) and " +"configure LDAP connection options in section:" +msgstr "" + +#. Tag: programlisting +#: Ldap.xml:49 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<datasource>\n" +" <name>LDAP</name>\n" +" <config>\n" +" <option>\n" +" <name>host</name>\n" +" <value>jboss.com</value>\n" +" </option>\n" +" <option>\n" +" <name>port</name>\n" +" <value>10389</value>\n" +" </option>\n" +" <option>\n" +" <name>adminDN</name>\n" +" <value>cn=Directory Manager</value>\n" +" </option>\n" +" <option>\n" +" <name>adminPassword</name>\n" +" <value>qpq123qpq</value>\n" +" </option>\n" +" </config>\n" +"</datasource>]]>" +msgstr "" + +#. Tag: para +#: Ldap.xml:50 +#, no-c-format +msgid "" +"You also need to specify options for your LDAP tree (described in " +"configuration documentation) like those:" +msgstr "" + +#. Tag: programlisting +#: Ldap.xml:53 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<option-group>\n" +" <group-name>common</group-name>\n" +" <option>\n" +" <name>userCtxDN</name>\n" +" <value>ou=People,dc=portal26,dc=jboss,dc=com</value>\n" +" </option>\n" +" <option>\n" +" <name>roleCtxDN</name>\n" +" <value>ou=Roles,dc=portal26,dc=jboss,dc=com</value>\n" +" </option>\n" +"</option-group>]]>" +msgstr "" + +#. Tag: para +#: Ldap.xml:55 +#, no-c-format +msgid "" +"Under <emphasis role=\"bold\">PORTAL_SOURCES/identity/src/resources/example/" +"</emphasis> you can find a sample ldif that you can use to populate LDAP " +"server and quickly start playing with it." +msgstr "" + +#. Tag: title +#: Ldap.xml:62 +#, no-c-format +msgid "Configuration of LDAP connection" +msgstr "" + +#. Tag: title +#: Ldap.xml:64 +#, no-c-format +msgid "Connection Pooling" +msgstr "" + +#. Tag: para +#: Ldap.xml:65 +#, no-c-format +msgid "" +"JBoss Portal uses <ulink url=\"http://java.sun.com/products/jndi/tutorial/" +"ldap/connect/pool.html\">connection pooling</ulink> provided by <ulink url=" +"\"http://java.sun.com/products/jndi/\">JNDI</ulink>, and is enabled by " +"default. Use the following options to configure connection pooling settings:" +msgstr "" + +#. Tag: programlisting +#: Ldap.xml:66 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<datasource>\n" +" <name>LDAP</name>\n" +" <config>\n" +" ...\n" +" <!-- com.sun.jndi.ldap.connect.pool -->\n" +" <option>\n" +" <name>pooling</name>\n" +" <value>true</value>\n" +" </option>\n" +"\n" +" <!-- com.sun.jndi.ldap.connect.pool.protocol -->\n" +" <option>\n" +" <name>poolingProtocol</name>\n" +" <value>plain ssl</value>\n" +" </option>\n" +"\n" +" <!-- com.sun.jndi.ldap.connect.pool.timeout -->\n" +" <option>\n" +" <name>poolingTimeout</name>\n" +" <value>300000</value>\n" +" </option>\n" +"\n" +" <!-- com.sun.jndi.ldap.connect.pool.debug -->\n" +" <option>\n" +" <name>pooling</name>\n" +" <value> ... </value>\n" +" </option>\n" +"\n" +" <!-- com.sun.jndi.ldap.connect.pool.initsize -->\n" +" <option>\n" +" <name>poolingInitsize</name>\n" +" <value> ... </value>\n" +" </option>\n" +"\n" +" <!-- com.sun.jndi.ldap.connect.pool.maxsize -->\n" +" <option>\n" +" <name>poolingMaxsize</name>\n" +" <value> ... </value>\n" +" </option>\n" +"\n" +" <!-- com.sun.jndi.ldap.connect.pool.prefsize -->\n" +" <option>\n" +" <name>poolingPrefsize</name>\n" +" <value> ... </value>\n" +" </option>\n" +"\n" +" ...\n" +" </config>\n" +"</datasource>]]>" +msgstr "" + +#. Tag: para +#: Ldap.xml:67 +#, no-c-format +msgid "" +"Remember, as it is described in the <ulink url=\"http://java.sun.com/" +"products/jndi/tutorial/ldap/connect/config.html\">JNDI documentation</" +"ulink>, these options are system properties, not environment properties, and " +"as such, they affect all connection pooling requests in the <trademark class=" +"\"trade\">Java runtime environment</trademark>." +msgstr "" + +#. Tag: title +#: Ldap.xml:73 +#, no-c-format +msgid "<title>SSL</title>" +msgstr "" + +#. Tag: para +#: Ldap.xml:74 +#, no-c-format +msgid "" +"The setup is very similar to the one described in LdapLoginModule <ulink url=" +"\"http://www.jboss.org/wiki/Wiki.jsp?page=LdapLoginModule\">wiki page</ulink>" +msgstr "" + +#. Tag: para +#: Ldap.xml:75 +#, no-c-format +msgid "" +"You need to modify your identity configuration file and add \"protocol\"" +msgstr "" + +#. Tag: programlisting +#: Ldap.xml:76 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<datasource>\n" +" <name>LDAP</name>\n" +" <config>\n" +" ...\n" +" <option>\n" +" <name>protocol</name>\n" +" <value>ssl</value>\n" +" </option>\n" +" ...\n" +" </config>\n" +"</datasource>]]>" +msgstr "" + +#. Tag: para +#: Ldap.xml:77 +#, no-c-format +msgid "" +"Then you need to have LDAP server certificate imported into your keystore. " +"You can use following command:" +msgstr "" + +#. Tag: programlisting +#: Ldap.xml:79 +#, no-c-format +msgid "keytool -import -file ldapcert.der -keystore ldap.truststore" +msgstr "" + +#. Tag: para +#: Ldap.xml:81 +#, no-c-format +msgid "" +"Now you need to change the settings to use the alternative truststore. That " +"can be done in the properties-service.xml in deploy directory:" +msgstr "" + +#. Tag: programlisting +#: Ldap.xml:83 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<attribute name=\"Properties\">\n" +" javax.net.ssl.trustStore=../some/path/to/ldap.truststore\n" +" javax.net.ssl.trustStorePassword=somepw\n" +"</attribute>]]>" +msgstr "" + +#. Tag: title +#: Ldap.xml:87 +#, no-c-format +msgid "ExternalContext" +msgstr "" + +#. Tag: para +#: Ldap.xml:88 +#, no-c-format +msgid "" +"Instead of configuring your own connection you can use JNDI context " +"federation mechanism in JBoss Application Server. Configuration of " +"ExternalContext is described in <ulink url=\"http://docs.jboss.com/jbossas/" +"guides/j2eeguide/r2/en/html_single/#d0e6877\">JBoss Application Server " +"documentation</ulink>" +msgstr "" + +#. Tag: para +#: Ldap.xml:90 +#, no-c-format +msgid "" +"When you have ExternalContext configured you can use it in JBoss Portal by " +"providing proper JNDI name in the configuration:" +msgstr "" + +#. Tag: programlisting +#: Ldap.xml:91 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<datasource>\n" +" <name>LDAP</name>\n" +" <config>\n" +" <option>\n" +" <name>externalContextJndiName</name>\n" +" <value>external/ldap/jboss</value>\n" +" </option>\n" +" </config>\n" +"</datasource>]]>" +msgstr "" + +#. Tag: para +#: Ldap.xml:92 +#, no-c-format +msgid "" +"When using \"externalContextJndiName\" you don't need to specify any other " +"option for this datasource" +msgstr "" + +#. Tag: title +#: Ldap.xml:97 +#, no-c-format +msgid "LDAP Identity Modules" +msgstr "" + +#. Tag: para +#: Ldap.xml:98 +#, no-c-format +msgid "" +"JBoss Portal comes with base LDAP implementation of all identity modules." +msgstr "" + +#. Tag: title +#: Ldap.xml:100 +#, no-c-format +msgid "Common settings" +msgstr "" + +#. Tag: para +#: Ldap.xml:101 +#, no-c-format +msgid "For all modules you can set two config options:" +msgstr "" + +#. Tag: para +#: Ldap.xml:103 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">jNDIName</emphasis> - JNDI name under which this " +"module will be registered" +msgstr "" + +#. Tag: para +#: Ldap.xml:107 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">connectionJNDIName</emphasis> - JNDI name under " +"which LDAP datasource is registered" +msgstr "" + +#. Tag: para +#: Ldap.xml:110 +#, no-c-format +msgid "" +"Most configuration of LDAP identity modules is done in <emphasis>options</" +"emphasis> section by adding module specific options in <emphasis>\"common\"</" +"emphasis> option-group or in other module specific groups." +msgstr "" + +#. Tag: title +#: Ldap.xml:115 +#, no-c-format +msgid "<title>UserModule</title>" +msgstr "" + +#. Tag: title +#: Ldap.xml:118 +#, no-c-format +msgid "Comparision of UserModule implementations" +msgstr "" + +#. Tag: entry +#: Ldap.xml:125 Ldap.xml:252 Ldap.xml:381 +#, no-c-format +msgid "Features" +msgstr "" + +#. Tag: entry +#: Ldap.xml:126 Ldap.xml:631 +#, no-c-format +msgid "<entry>UserModule</entry>" +msgstr "" + +#. Tag: entry +#: Ldap.xml:129 Ldap.xml:637 +#, no-c-format +msgid "<entry>LDAPUserModuleImpl</entry>" +msgstr "" + +#. Tag: entry +#: Ldap.xml:130 Ldap.xml:638 +#, no-c-format +msgid "<entry>LDAPExtUserModuleImpl</entry>" +msgstr "" + +#. Tag: entry +#: Ldap.xml:135 +#, no-c-format +msgid "User creation" +msgstr "" + +#. Tag: entry +#: Ldap.xml:136 Ldap.xml:141 Ldap.xml:263 Ldap.xml:268 Ldap.xml:392 +#: Ldap.xml:398 Ldap.xml:402 Ldap.xml:403 +#, no-c-format +msgid "<entry>X</entry>" +msgstr "" + +#. Tag: entry +#: Ldap.xml:137 Ldap.xml:142 Ldap.xml:264 Ldap.xml:269 Ldap.xml:393 +#: Ldap.xml:397 +#, no-c-format +msgid "<entry>-</entry>" +msgstr "" + +#. Tag: entry +#: Ldap.xml:140 +#, no-c-format +msgid "User removal" +msgstr "" + +#. Tag: entry +#: Ldap.xml:145 +#, no-c-format +msgid "User search" +msgstr "" + +#. Tag: entry +#: Ldap.xml:146 Ldap.xml:273 +#, no-c-format +msgid "Flat - one level scope" +msgstr "" + +#. Tag: entry +#: Ldap.xml:147 Ldap.xml:274 +#, no-c-format +msgid "Flexible filter - sub tree scope" +msgstr "" + +#. Tag: title +#: Ldap.xml:154 +#, no-c-format +msgid "<title>LDAPUserModuleImpl</title>" +msgstr "" + +#. Tag: para +#: Ldap.xml:155 +#, no-c-format +msgid "" +"This is the base implementation of LDAP <emphasis>UserModule</emphasis>. It " +"supports user creation, but will retrieve users and create them in strictly " +"specified place in LDAP tree." +msgstr "" + +#. Tag: para +#: Ldap.xml:157 Ldap.xml:199 Ldap.xml:284 Ldap.xml:315 Ldap.xml:412 +#: Ldap.xml:436 Ldap.xml:464 +#, no-c-format +msgid "To enable it in your configuration you should have:" +msgstr "" + +#. Tag: programlisting +#: Ldap.xml:158 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<module>\n" +" <!--type used to correctly map in IdentityContext registry-->\n" +" <type>User</type>\n" +" <implementation>LDAP</implementation>\n" +" <config/>\n" +"</module>]]>" +msgstr "" + +#. Tag: para +#: Ldap.xml:160 Ldap.xml:470 +#, no-c-format +msgid "" +"org.jboss.portal.identity.ldap.LDAPUserModuleImpl configuration option-" +"groups options:" +msgstr "" + +#. Tag: para +#: Ldap.xml:163 Ldap.xml:204 Ldap.xml:289 Ldap.xml:322 Ldap.xml:417 +#: Ldap.xml:441 Ldap.xml:473 +#, no-c-format +msgid "<emphasis role=\"bold\">common</emphasis>:" +msgstr "" + +#. Tag: para +#: Ldap.xml:166 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">userCtxDN</emphasis> - DN that will be used as " +"context for user searches" +msgstr "" + +#. Tag: para +#: Ldap.xml:170 Ldap.xml:215 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">uidAttributeID</emphasis> - attribute name under " +"which user name is specified. Default value is \"uid\"" +msgstr "" + +#. Tag: para +#: Ldap.xml:173 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">passwordAttributeID</emphasis> - attribute name " +"under which user password is specified. Default value is \"userPassword\"" +msgstr "" + +#. Tag: para +#: Ldap.xml:176 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">principalDNPrefix</emphasis> and <emphasis role=" +"\"bold\">principalDNSuffix</emphasis>" +msgstr "" + +#. Tag: para +#: Ldap.xml:179 Ldap.xml:218 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">searchTimeLimit</emphasis> - The timeout in " +"milliseconds for the user searches. Defaults to 10000 (10 seconds)." +msgstr "" + +#. Tag: para +#: Ldap.xml:185 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">userCreateAttibutes</emphasis>: This option-group " +"defines a set of ldap attributes that will be set on user entry creation. " +"Option name will be used as attribute name, and option values as attribute " +"values. This enables to fulfill LDAP schema requirements." +msgstr "" + +#. Tag: para +#: Ldap.xml:190 +#, no-c-format +msgid "Example configuration:" +msgstr "" + +#. Tag: programlisting +#: Ldap.xml:191 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<option-group>\n" +" <group-name>common</group-name>\n" +" <option>\n" +" <name>userCtxDN</name>\n" +" <value>ou=People,o=portal,dc=my-domain,dc=com</value>\n" +" </option>\n" +" <option>\n" +" <name>uidAttributeID</name>\n" +" <value>uid</value>\n" +" </option>\n" +" <option>\n" +" <name>passwordAttributeID</name>\n" +" <value>userPassword</value>\n" +" </option>\n" +"</option-group>\n" +"<option-group>\n" +" <group-name>userCreateAttibutes</group-name>\n" +" <option>\n" +" <name>objectClass</name>\n" +" <!--This objectclasses should work with Red Hat Directory-->\n" +" <value>top</value>\n" +" <value>person</value>\n" +" <value>inetOrgPerson</value>\n" +" </option>\n" +" <!--Schema requires those to have initial value-->\n" +" <option>\n" +" <name>cn</name>\n" +" <value>none</value>\n" +" </option>\n" +" <option>\n" +" <name>sn</name>\n" +" <value>none</value>\n" +" </option>\n" +"</option-group>]]>" +msgstr "" + +#. Tag: title +#: Ldap.xml:196 +#, no-c-format +msgid "<title>LDAPExtUserModuleImpl</title>" +msgstr "" + +#. Tag: para +#: Ldap.xml:197 +#, no-c-format +msgid "" +"Aim of this implementation is to give more flexibility for users retrieval. " +"You can specify LDAP filter that will be used for searches. This module " +"doesn't support user creation and removal" +msgstr "" + +#. Tag: programlisting +#: Ldap.xml:200 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<module>\n" +" <!--type used to correctly map in IdentityContext registry-->\n" +" <type>User</type>\n" +" <implementation>LDAP</implementation>\n" +" <class>org.jboss.portal.identity.ldap.LDAPExtUserModuleImpl</class>\n" +" <config/>\n" +"</module]]>" +msgstr "" + +#. Tag: para +#: Ldap.xml:202 +#, no-c-format +msgid "" +"org.jboss.portal.identity.ldap.LDAPExtUserModuleImpl configuration option-" +"groups options:" +msgstr "" + +#. Tag: para +#: Ldap.xml:208 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">userCtxDN</emphasis> - DN that will be used as " +"context for user searches. More than one value can be specified." +msgstr "" + +#. Tag: para +#: Ldap.xml:211 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">userSearchFilter</emphasis> - ldap filter to search " +"users with. {0} will be substitute with user name. Example filter can look " +"like this: \"(uid={0})\". This substituion behavior comes from the standard " +"<emphasis>DirContext.search(Name, String, Object, SearchControls cons)</" +"emphasis> method" +msgstr "" + +#. Tag: title +#: Ldap.xml:244 +#, no-c-format +msgid "<title>RoleModule</title>" +msgstr "" + +#. Tag: title +#: Ldap.xml:247 +#, no-c-format +msgid "Comparision of RoleModule implementations" +msgstr "" + +#. Tag: entry +#: Ldap.xml:253 Ldap.xml:632 +#, no-c-format +msgid "<entry>RoleModule</entry>" +msgstr "" + +#. Tag: entry +#: Ldap.xml:256 Ldap.xml:639 +#, no-c-format +msgid "<entry>LDAPRoleModuleImpl</entry>" +msgstr "" + +#. Tag: entry +#: Ldap.xml:257 Ldap.xml:640 +#, no-c-format +msgid "<entry>LDAPExtRoleModuleImpl</entry>" +msgstr "" + +#. Tag: entry +#: Ldap.xml:262 +#, no-c-format +msgid "Role creation" +msgstr "" + +#. Tag: entry +#: Ldap.xml:267 +#, no-c-format +msgid "Role removal" +msgstr "" + +#. Tag: entry +#: Ldap.xml:272 +#, no-c-format +msgid "Role search" +msgstr "" + +#. Tag: title +#: Ldap.xml:281 +#, no-c-format +msgid "<title>LDAPRoleModuleImpl</title>" +msgstr "" + +#. Tag: para +#: Ldap.xml:282 +#, no-c-format +msgid "" +"This is the base implementation of LDAP <emphasis>RoleModule</emphasis>. It " +"supports user creation, but will retrieve roles and create them in strictly " +"specified place in LDAP tree." +msgstr "" + +#. Tag: programlisting +#: Ldap.xml:285 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<module>\n" +" <!--type used to correctly map in IdentityContext registry-->\n" +" <type>Role</type>\n" +" <implementation>LDAP</implementation>\n" +" <config/>\n" +"</module>]]>" +msgstr "" + +#. Tag: para +#: Ldap.xml:287 +#, no-c-format +msgid "" +"org.jboss.portal.identity.ldap.LDAPRoleModuleImpl configuration option-" +"groups options:" +msgstr "" + +#. Tag: para +#: Ldap.xml:293 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">roleCtxDN</emphasis> - DN that will be used as " +"context for role searches." +msgstr "" + +#. Tag: para +#: Ldap.xml:296 Ldap.xml:332 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">ridAttributeID</emphasis> - attribute name under " +"which role name is specified. Default value is \"cn\"." +msgstr "" + +#. Tag: para +#: Ldap.xml:299 Ldap.xml:335 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">roleDisplayNameAttributeID</emphasis> - attribute " +"name under which role display name is specified. Default value is \"cn\"." +msgstr "" + +#. Tag: para +#: Ldap.xml:302 Ldap.xml:338 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">searchTimeLimit</emphasis> - The timeout in " +"milliseconds for the roles searches. Defaults to 10000 (10 seconds)." +msgstr "" + +#. Tag: title +#: Ldap.xml:311 +#, no-c-format +msgid "<title>LDAPExtRoleModuleImpl</title>" +msgstr "" + +#. Tag: para +#: Ldap.xml:312 +#, no-c-format +msgid "" +"Aim of this implementation is to give more flexibility for roles retrieval. " +"You can specify LDAP filter that will be used for searches. This module " +"doesn't support role creation and removal." +msgstr "" + +#. Tag: para +#: Ldap.xml:314 +#, no-c-format +msgid "This module doesn't support role creation and removal" +msgstr "" + +#. Tag: programlisting +#: Ldap.xml:316 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<module>\n" +" <!--type used to correctly map in IdentityContext registry-->\n" +" <type>Role</type>\n" +" <implementation>LDAP</implementation>\n" +" <class>org.jboss.portal.identity.ldap.LDAPExtRoleModuleImpl</class>\n" +" <config/>\n" +"</module>]]>" +msgstr "" + +#. Tag: para +#: Ldap.xml:318 +#, no-c-format +msgid "" +"org.jboss.portal.identity.ldap.LDAPExtRoleModuleImpl configuration option-" +"groups options:" +msgstr "" + +#. Tag: para +#: Ldap.xml:325 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">roleCtxDN</emphasis> - DN that will be used as " +"context for role searches. More than one value can be specified." +msgstr "" + +#. Tag: para +#: Ldap.xml:328 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">roleSearchFilter</emphasis> - ldap filter to search " +"roles with. {0} will be substitute with role name. Example filter can look " +"like this: \"(cn={0})\". This substituion behavior comes from the standard " +"<emphasis>DirContext.search(Name, String, Object, SearchControls cons)</" +"emphasis> method." +msgstr "" + +#. Tag: para +#: Ldap.xml:341 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">searchScope</emphasis> - Sets the search scope to " +"one of the strings. The default is SUBTREE_SCOPE." +msgstr "" + +#. Tag: para +#: Ldap.xml:344 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">OBJECT_SCOPE</emphasis> - only search the named " +"roles context." +msgstr "" + +#. Tag: para +#: Ldap.xml:347 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">ONELEVEL_SCOPE</emphasis> - search directly under " +"the named roles context." +msgstr "" + +#. Tag: para +#: Ldap.xml:350 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">SUBTREE_SCOPE</emphasis> - If the roles context is " +"not a <emphasis>DirContext</emphasis>, search only the object. If the roles " +"context is a <emphasis>DirContext</emphasis>, search the subtree rooted at " +"the named object, including the named object itself." +msgstr "" + +#. Tag: para +#: Ldap.xml:362 +#, no-c-format +msgid "" +"In <emphasis>UserModule</emphasis> there are two methods that handle offset/" +"limit (pagination) behavior. <programlisting>\n" +" <![CDATA[\n" +"/** Get a range of users.*/\n" +"Set findUsers(int offset, int limit) throws IdentityException, " +"IllegalArgumentException;\n" +"\n" +"/** Get a range of users.*/\n" +"Set findUsersFilteredByUserName(String filter, int offset, int limit)\n" +" throws IdentityException, IllegalArgumentException;\n" +" ]]>\n" +" </programlisting> Pagination support is not widely implemented " +"in LDAP servers. Because <emphasis>UserModule</emphasis> implementations " +"rely on JNDI and are targetted to be LDAP server agnostic those methods " +"aren't very effecient. As long as you don't rely on portal user management " +"and use dedicated tools for user provisioning it shouldn't bother you. " +"Otherwise you should consider extending the implementation and providing " +"solution dedicated to your LDAP server." +msgstr "" + +#. Tag: title +#: Ldap.xml:373 +#, no-c-format +msgid "<title>MembershipModule</title>" +msgstr "" + +#. Tag: title +#: Ldap.xml:376 +#, no-c-format +msgid "Comparision of MembershipModule implementations" +msgstr "" + +#. Tag: entry +#: Ldap.xml:382 Ldap.xml:633 +#, no-c-format +msgid "<entry>MembershipModule</entry>" +msgstr "" + +#. Tag: entry +#: Ldap.xml:385 Ldap.xml:641 +#, no-c-format +msgid "<entry>LDAPStaticGroupMembershipModuleImpl</entry>" +msgstr "" + +#. Tag: entry +#: Ldap.xml:386 Ldap.xml:642 +#, no-c-format +msgid "<entry>LDAPStaticRoleMembershipModuleImpl</entry>" +msgstr "" + +#. Tag: entry +#: Ldap.xml:391 +#, no-c-format +msgid "Role assignment stored in LDAP role entry" +msgstr "" + +#. Tag: entry +#: Ldap.xml:396 +#, no-c-format +msgid "Role assignment stored in LDAP user entry" +msgstr "" + +#. Tag: entry +#: Ldap.xml:401 +#, no-c-format +msgid "User/Role relationship creation" +msgstr "" + +#. Tag: title +#: Ldap.xml:410 +#, no-c-format +msgid "<title>LDAPStaticGroupMembershipModuleImpl</title>" +msgstr "" + +#. Tag: para +#: Ldap.xml:411 +#, no-c-format +msgid "" +"This module support tree shape where role entries keep information about " +"users that are their members." +msgstr "" + +#. Tag: programlisting +#: Ldap.xml:413 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<module>\n" +" <!--type used to correctly map in IdentityContext registry-->\n" +" <type>Membership</type>\n" +" <implementation>LDAP</implementation>\n" +" <config/>\n" +"</module>]]>" +msgstr "" + +#. Tag: para +#: Ldap.xml:415 +#, no-c-format +msgid "" +"org.jboss.portal.identity.ldap.LDAPStaticGroupMembershipModuleImpl " +"configuration option-groups options:" +msgstr "" + +#. Tag: para +#: Ldap.xml:421 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">membershipAttributeID</emphasis> - LDAP attribute " +"that defines member users ids. This will be used to retrieved users from " +"role entry." +msgstr "" + +#. Tag: para +#: Ldap.xml:424 Ldap.xml:449 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">membershipAttributeIsDN</emphasis> - defines if " +"values of attribute defined in <emphasis>membershipAttributeID</emphasis> " +"are fully qualified LDAP DNs." +msgstr "" + +#. Tag: title +#: Ldap.xml:434 +#, no-c-format +msgid "<title>LDAPStaticRoleMembershipModuleImpl</title>" +msgstr "" + +#. Tag: para +#: Ldap.xml:435 +#, no-c-format +msgid "" +"This module support tree shape where user entries keep information about " +"roles that they belong to." +msgstr "" + +#. Tag: programlisting +#: Ldap.xml:437 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<module>\n" +" <!--type used to correctly map in IdentityContext registry-->\n" +" <type>Membership</type>\n" +" <implementation>LDAP</implementation>\n" +" <class>org.jboss.portal.identity.ldap.LDAPStaticRoleMembershipModuleImpl</" +"class>\n" +" <config/>\n" +"</module>]]>" +msgstr "" + +#. Tag: para +#: Ldap.xml:439 +#, no-c-format +msgid "" +"org.jboss.portal.identity.ldap.LDAPStaticRoleMembershipModuleImpl " +"configuration option-groups options:" +msgstr "" + +#. Tag: para +#: Ldap.xml:444 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">membershipAttributeID</emphasis> - LDAP attribute " +"that defines role ids that user belongs to. This will be used to retrieved " +"roles from user entry." +msgstr "" + +#. Tag: title +#: Ldap.xml:460 +#, no-c-format +msgid "<title>UserProfileModule</title>" +msgstr "" + +#. Tag: title +#: Ldap.xml:462 +#, no-c-format +msgid "<title>LDAPUserProfileModuleImpl</title>" +msgstr "" + +#. Tag: para +#: Ldap.xml:463 +#, no-c-format +msgid "" +"This is standard implementation that enables to retrieve user properties " +"from atributes in LDAP entries." +msgstr "" + +#. Tag: programlisting +#: Ldap.xml:465 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<module>\n" +" <type>UserProfile</type>\n" +" <implementation>DELEGATING</implementation>\n" +" <config>\n" +" <option>\n" +" <name>ldapModuleJNDIName</name>\n" +" <value>java:/portal/LDAPUserProfileModule</value>\n" +" </option>\n" +" </config>\n" +"</module>\n" +"<module>\n" +" <type>DBDelegateUserProfile</type>\n" +" <implementation>DB</implementation>\n" +" <config>\n" +" <option>\n" +" <name>randomSynchronizePassword</name>\n" +" <value>true</value>\n" +" </option>\n" +" </config>\n" +"</module>\n" +"<module>\n" +" <type>LDAPDelegateUserProfile</type>\n" +" <implementation>LDAP</implementation>\n" +" <config/>\n" +"</module>]]>" +msgstr "" + +#. Tag: para +#: Ldap.xml:466 +#, no-c-format +msgid "" +"Using such configuration you will have LDAP MembershipModule along with DB " +"MembershipModule and Delegating MembershipModule. Please read <xref linkend=" +"\"identity.management_api\"/> to see why this is important." +msgstr "" + +#. Tag: para +#: Ldap.xml:476 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">profileConfigFile</emphasis> - file with user " +"profile configuration. If this option is not set, and we use delegating " +"UserProfileModule, profile configuration will be obtained from it." +msgstr "" + +#. Tag: title +#: Ldap.xml:488 +#, no-c-format +msgid "LDAP server tree shapes" +msgstr "" + +#. Tag: para +#: Ldap.xml:489 +#, no-c-format +msgid "" +"JBoss Portal supports full user/role management for simple LDAP tree shapes. " +"Some more flexible trees can be supported by " +"<emphasis>LdapExtUserModuleImpl</emphasis> and " +"<emphasis>LdapExtRoleModuleImpl</emphasis> - but without user/role creation " +"and removal capabilities. However if you have complex LDAP tree you should " +"consider using <xref linkend=\"authentication.synchronizing_login_module\"/> " +"described in <xref linkend=\"authentication\"/> along with dedicated tools " +"for user provisioning provided with LDAP server." +msgstr "" + +#. Tag: para +#: Ldap.xml:496 +#, no-c-format +msgid "" +"In following subsections we will describe two base LDAP tree shapes along " +"with example LDIFs and portal identity modules configurations. Those two " +"examples differ only by using different <emphasis>MembershipModule</" +"emphasis> implementations and describe only tree shapes with supported user/" +"role creation and removal capabilities." +msgstr "" + +#. Tag: title +#: Ldap.xml:502 +#, no-c-format +msgid "Keeping users membership in role entries" +msgstr "" + +#. Tag: para +#: Ldap.xml:503 +#, no-c-format +msgid "" +"In this example, information about users/roles assignment is stored in roles " +"entries using LDAP \"<emphasis>member</emphasis>\". Of course any other " +"attribute that comes with schema can be used for this." +msgstr "" + +#. Tag: para +#: Ldap.xml:505 Ldap.xml:537 +#, no-c-format +msgid "Example tree shape in LDAP browser" +msgstr "" + +#. Tag: title +#: Ldap.xml:520 Ldap.xml:552 +#, no-c-format +msgid "Example LDIF" +msgstr "" + +#. Tag: programlisting +#: Ldap.xml:522 +#, no-c-format +msgid "" +"<![CDATA[\n" +"dn: dc=example,dc=com\n" +"objectclass: top\n" +"objectclass: dcObject\n" +"objectclass: organization\n" +"dc: example\n" +"o: example\n" +"\n" +"dn: ou=People,dc=example,dc=com\n" +"objectclass: top\n" +"objectclass: organizationalUnit\n" +"ou: People\n" +"\n" +"dn: uid=user,ou=People,dc=example,dc=com\n" +"objectclass: top\n" +"objectclass: inetOrgPerson\n" +"objectclass: person\n" +"uid: user\n" +"cn: JBoss Portal user\n" +"sn: user\n" +"userPassword: user\n" +"mail: email(a)email.com\n&quot; +"\n" +"dn: uid=admin,ou=People,dc=example,dc=com\n" +"objectclass: top\n" +"objectclass: inetOrgPerson\n" +"objectclass: person\n" +"uid: admin\n" +"cn: JBoss Portal admin\n" +"sn: admin\n" +"userPassword: admin\n" +"mail: email(a)email.com\n&quot; +"\n" +"dn: ou=Roles,dc=example,dc=com\n" +"objectclass: top\n" +"objectclass: organizationalUnit\n" +"ou: Roles\n" +"\n" +"dn: cn=User,ou=Roles,dc=example,dc=com\n" +"objectClass: top\n" +"objectClass: groupOfNames\n" +"cn: User\n" +"description: the JBoss Portal user group\n" +"member: uid=user,ou=People,dc=example,dc=com\n" +"\n" +"dn: cn=Admin,ou=Roles,dc=example,dc=com\n" +"objectClass: top\n" +"objectClass: groupOfNames\n" +"cn: Echo\n" +"description: the JBoss Portal admin group\n" +"member: uid=admin,ou=People,dc=example,dc=com]]>" +msgstr "" + +#. Tag: title +#: Ldap.xml:526 Ldap.xml:558 +#, no-c-format +msgid "Example identity configuration" +msgstr "" + +#. Tag: programlisting +#: Ldap.xml:528 +#, no-c-format +msgid "" +"<![CDATA[\n" +" <modules>\n" +" <module>\n" +" <!--type used to correctly map in IdentityContext registry-->\n" +" <type>User</type>\n" +" <implementation>LDAP</implementation>\n" +" <config/>\n" +" </module>\n" +" <module>\n" +" <type>Role</type>\n" +" <implementation>LDAP</implementation>\n" +" <config/>\n" +" </module>\n" +" <module>\n" +" <type>Membership</type>\n" +" <implementation>LDAP</implementation>\n" +" <config/>\n" +" </module>\n" +" <module>\n" +" <type>UserProfile</type>\n" +" <implementation>DELEGATING</implementation>\n" +" <config>\n" +" <option>\n" +" <name>ldapModuleJNDIName</name>\n" +" <value>java:/portal/LDAPUserProfileModule</value>\n" +" </option>\n" +" </config>\n" +" </module>\n" +" <module>\n" +" <type>DBDelegateUserProfile</type>\n" +" <implementation>DB</implementation>\n" +" <config>\n" +" <option>\n" +" <name>randomSynchronizePassword</name>\n" +" <value>true</value>\n" +" </option>\n" +" </config>\n" +" </module>\n" +" <module>\n" +" <type>LDAPDelegateUserProfile</type>\n" +" <implementation>LDAP</implementation>\n" +" <config/>\n" +" </module>\n" +"</modules>\n" +"\n" +"<options>\n" +" <option-group>\n" +" <group-name>common</group-name>\n" +" <option>\n" +" <name>userCtxDN</name>\n" +" <value>ou=People,dc=example,dc=com</value>\n" +" </option>\n" +" <option>\n" +" <name>roleCtxDN</name>\n" +" <value>ou=Roles,dc=example,dc=com</value>\n" +" </option>\n" +" </option-group>\n" +" <option-group>\n" +" <group-name>userCreateAttibutes</group-name>\n" +" <option>\n" +" <name>objectClass</name>\n" +" <!--This objectclasses should work with Red Hat Directory-->\n" +" <value>top</value>\n" +" <value>person</value>\n" +" <value>inetOrgPerson</value>\n" +" </option>\n" +" <!--Schema requires those to have initial value-->\n" +" <option>\n" +" <name>cn</name>\n" +" <value>none</value>\n" +" </option>\n" +" <option>\n" +" <name>sn</name>\n" +" <value>none</value>\n" +" </option>\n" +" </option-group>\n" +" <option-group>\n" +" <group-name>roleCreateAttibutes</group-name>\n" +" <!--Schema requires those to have initial value-->\n" +" <option>\n" +" <name>cn</name>\n" +" <value>none</value>\n" +" </option>\n" +" <!--Some directory servers require this attribute to be valid DN-->\n" +" <!--For safety reasons point to the admin user here-->\n" +" <option>\n" +" <name>member</name>\n" +" <value>uid=admin,ou=People,dc=example,dc=com</value>\n" +" </option>\n" +" </option-group>\n" +"</options>]]>" +msgstr "" + +#. Tag: title +#: Ldap.xml:534 +#, no-c-format +msgid "Keeping users membership in user entries" +msgstr "" + +#. Tag: para +#: Ldap.xml:535 +#, no-c-format +msgid "" +"In this example, information about users/roles assignment is stored in user " +"entries using LDAP \"<emphasis>memberOf</emphasis>\". Of course any other " +"attribute that comes with schema can be used for this." +msgstr "" + +#. Tag: programlisting +#: Ldap.xml:554 +#, no-c-format +msgid "" +"<![CDATA[\n" +"dn: dc=example,dc=com\n" +"objectclass: top\n" +"objectclass: dcObject\n" +"objectclass: organization\n" +"dc: example\n" +"o: example\n" +"\n" +"dn: o=example2,dc=example,dc=com\n" +"objectclass: top\n" +"objectclass: organization\n" +"o: example2\n" +"\n" +"dn: ou=People,o=example2,dc=example,dc=com\n" +"objectclass: top\n" +"objectclass: organizationalUnit\n" +"ou: People\n" +"\n" +"dn: uid=admin,ou=People,o=example2,dc=example,dc=com\n" +"objectclass: top\n" +"objectclass: inetOrgPerson\n" +"objectclass: inetUser\n" +"uid: admin\n" +"cn: JBoss Portal admin\n" +"sn: admin\n" +"userPassword: admin\n" +"mail: email(a)email.com\n&quot; +"memberOf: cn=Admin,ou=Roles,o=example2,dc=example,dc=com\n" +"\n" +"dn: uid=user,ou=People,o=example2,dc=example,dc=com\n" +"objectclass: top\n" +"objectclass: inetOrgPerson\n" +"objectclass: inetUser\n" +"uid: user\n" +"cn: JBoss Portal user\n" +"sn: user\n" +"userPassword: user\n" +"mail: email(a)email.com\n&quot; +"memberOf: cn=User,ou=Roles,o=example2,dc=example,dc=com\n" +"\n" +"dn: ou=Roles,o=example2,dc=example,dc=com\n" +"objectclass: top\n" +"objectclass: organizationalUnit\n" +"ou: Roles\n" +"\n" +"dn: cn=User,ou=Roles,o=example2,dc=example,dc=com\n" +"objectClass: top\n" +"objectClass: organizationalRole\n" +"cn: User\n" +"description: the JBoss Portal user group\n" +"\n" +"dn: cn=Admin,ou=Roles,o=example2,dc=example,dc=com\n" +"objectClass: top\n" +"objectClass: organizationalRole\n" +"cn: Echo\n" +"description: the JBoss Portal admin group]]>" +msgstr "" + +#. Tag: programlisting +#: Ldap.xml:560 +#, no-c-format +msgid "" +"<![CDATA[\n" +" <modules>\n" +" <module>\n" +" <!--type used to correctly map in IdentityContext registry-->\n" +" <type>User</type>\n" +" <implementation>LDAP</implementation>\n" +" <config/>\n" +" </module>\n" +" <module>\n" +" <type>Role</type>\n" +" <implementation>LDAP</implementation>\n" +" <config/>\n" +" </module>\n" +" <module>\n" +" <type>Membership</type>\n" +" <implementation>LDAP</implementation>\n" +" <class>org.jboss.portal.identity.ldap." +"LDAPStaticRoleMembershipModuleImpl</class>\n" +" <config/>\n" +" </module>\n" +" <module>\n" +" <type>UserProfile</type>\n" +" <implementation>DELEGATING</implementation>\n" +" <config>\n" +" <option>\n" +" <name>ldapModuleJNDIName</name>\n" +" <value>java:/portal/LDAPUserProfileModule</value>\n" +" </option>\n" +" </config>\n" +" </module>\n" +" <module>\n" +" <type>DBDelegateUserProfile</type>\n" +" <implementation>DB</implementation>\n" +" <config>\n" +" <option>\n" +" <name>randomSynchronizePassword</name>\n" +" <value>true</value>\n" +" </option>\n" +" </config>\n" +" </module>\n" +" <module>\n" +" <type>LDAPDelegateUserProfile</type>\n" +" <implementation>LDAP</implementation>\n" +" <config/>\n" +" </module>\n" +"</modules>\n" +"\n" +"<options>\n" +" <option-group>\n" +" <group-name>common</group-name>\n" +" <option>\n" +" <name>userCtxDN</name>\n" +" <value>ou=People,dc=example,dc=com</value>\n" +" </option>\n" +" <option>\n" +" <name>roleCtxDN</name>\n" +" <value>ou=Roles,dc=example,dc=com</value>\n" +" </option>\n" +" <option>\n" +" <name>membershipAttributeID</name>\n" +" <value>memberOf</value>\n" +" </option>\n" +" </option-group>\n" +" <option-group>\n" +" <group-name>userCreateAttibutes</group-name>\n" +" <option>\n" +" <name>objectClass</name>\n" +" <!--This objectclasses should work with Red Hat Directory-->\n" +" <value>top</value>\n" +" <value>person</value>\n" +" <value>inetOrgPerson</value>\n" +" </option>\n" +" <!--Schema requires those to have initial value-->\n" +" <option>\n" +" <name>cn</name>\n" +" <value>none</value>\n" +" </option>\n" +" <option>\n" +" <name>sn</name>\n" +" <value>none</value>\n" +" </option>\n" +" </option-group>\n" +" <option-group>\n" +" <group-name>roleCreateAttibutes</group-name>\n" +" <!--Schema requires those to have initial value-->\n" +" <option>\n" +" <name>cn</name>\n" +" <value>none</value>\n" +" </option>\n" +" <!--Some directory servers require this attribute to be valid DN-->\n" +" <!--For safety reasons point to the admin user here-->\n" +" <option>\n" +" <name>member</name>\n" +" <value>uid=admin,ou=People,dc=example,dc=com</value>\n" +" </option>\n" +" </option-group>\n" +"</options>]]>" +msgstr "" + +#. Tag: title +#: Ldap.xml:566 +#, no-c-format +msgid "Synchronizing LDAP configuration" +msgstr "" + +#. Tag: para +#: Ldap.xml:567 +#, no-c-format +msgid "" +"Like it was described in previous section, you can meet some limitations in " +"identity modules support for more complex LDAP tree shapes. To workaround " +"this you can use identity synchronization on JAAS level. JBoss Portal comes " +"with <xref linkend=\"authentication.synchronizing_login_module\"/> that can " +"be easily configured with other authentication solutions that support JAAS " +"framework. Here we want to provide a simple example on how it can be " +"integrated with <emphasis><ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?" +"page=LdapExtLoginModule\">LdapExtLoginModule</ulink> from <emphasis>JBossSX</" +"emphasis> framework.</emphasis>" +msgstr "" + +#. Tag: para +#: Ldap.xml:576 +#, no-c-format +msgid "" +"First of all portal identity modules should be configured to work with " +"portal database - default configuration. This is important as we will " +"leverage them, and we want to synchronize users identity into default portal " +"storage mechanism. So lets look at simple configuration that should take " +"place in <emphasis>jboss-portal.sar/conf/login-config.xml</emphasis>" +msgstr "" + +#. Tag: programlisting +#: Ldap.xml:581 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<policy>\n" +" <!-- For the JCR CMS -->\n" +" <application-policy name=\"cms\">\n" +" <authentication>\n" +" <login-module code=\"org.apache.jackrabbit.core.security." +"SimpleLoginModule\"\n" +" flag=\"required\"/>\n" +" </authentication>\n" +" </application-policy>\n" +"\n" +" <application-policy name=\"portal\">\n" +" <authentication>\n" +"\n" +" <login-module code=\"org.jboss.security.auth.spi.LdapExtLoginModule" +"\" flag=\"required\">\n" +" <module-option name=\"java.naming.factory.initial\">com.sun.jndi." +"ldap.LdapCtxFactory\n" +" </module-option>\n" +" <module-option name=\"java.naming.provider.url\">ldap://example." +"com:10389/\n" +" </module-option>\n" +" <module-option name=\"java.naming.security.authentication" +"\">simple</module-option>\n" +" <module-option name=\"bindDN\">cn=Directory Manager</module-" +"option>\n" +" <module-option name=\"bindCredential\">lolo</module-option>\n" +" <module-option name=\"baseCtxDN\">ou=People,dc=example,dc=com</" +"module-option>\n" +" <module-option name=\"baseFilter\">(uid={0})</module-option>\n" +" <module-option name=\"rolesCtxDN\">ou=Roles,dc=example,dc=com</" +"module-option>\n" +" <module-option name=\"roleFilter\">(member={1})</module-option>\n" +" <module-option name=\"roleAttributeID\">cn</module-option>\n" +" <module-option name=\"roleRecursion\">-1</module-option>\n" +" <module-option name=\"searchTimeLimit\">10000</module-option>\n" +" <module-option name=\"searchScope\">SUBTREE_SCOPE</module-" +"option>\n" +" <module-option name=\"allowEmptyPasswords\">false</module-" +"option>\n" +" </login-module>\n" +"\n" +" <login-module code=\"org.jboss.portal.identity.auth." +"SynchronizingLoginModule\"\n" +" flag=\"optional\">\n" +" <module-option name=\"synchronizeIdentity\">true</module-" +"option>\n" +" <module-option name=\"synchronizeRoles\">true</module-option>\n" +" <module-option name=\"additionalRole\">Authenticated</module-" +"option>\n" +" <module-option name=\"defaultAssignedRole\">User</module-" +"option>\n" +" <module-option name=\"userModuleJNDIName\">java:/portal/" +"UserModule</module-option>\n" +" <module-option name=\"roleModuleJNDIName\">java:/portal/" +"RoleModule</module-option>\n" +" <module-option name=\"membershipModuleJNDIName\">java:/portal/" +"MembershipModule\n" +" </module-option>\n" +" <module-option name=\"userProfileModuleJNDIName\">java:/portal/" +"UserProfileModule\n" +" </module-option>\n" +" </login-module>\n" +"\n" +" </authentication>\n" +" </application-policy>\n" +"</policy>]]>" +msgstr "" + +#. Tag: para +#: Ldap.xml:583 +#, no-c-format +msgid "Few things are important in this configuration:" +msgstr "" + +#. Tag: para +#: Ldap.xml:586 +#, no-c-format +msgid "" +"<emphasis>LdapExtLoginModule</emphasis> has <emphasis>flag=\"required\"</" +"emphasis> set which means that if this single <emphasis>LoginModule</" +"emphasis> return <emphasis>fail</emphasis> from authentication request whole " +"process will fail. <emphasis>SynchronizingLoginModule</emphasis> has " +"<emphasis>flag=\"optional\"</emphasis>. Such combination is critical as " +"<emphasis>SynchronizingLoginModule</emphasis> always authenticates user " +"sucessfully no matter what credentials were provided. You always must have " +"at least one <emphasis>LoginModule</emphasis> that you will rely on." +msgstr "" + +#. Tag: para +#: Ldap.xml:595 +#, no-c-format +msgid "" +"<emphasis>SynchronizingLoginModule</emphasis> is always the <emphasis>last</" +"emphasis> one in whole authentication chain. This is because in " +"<emphasis>commit</emphasis> phase it will take users <emphasis>Subject</" +"emphasis> and its <emphasis>Principals</emphasis> (roles) assigned by " +"previous <emphasis>LoginModule</emphasis>s and try to synchronize them. " +"Roles assigned to authenticated user by <emphasis>LoginModule</emphasis>s " +"after it won't be handled." +msgstr "" + +#. Tag: title +#: Ldap.xml:605 +#, no-c-format +msgid "Supported LDAP servers" +msgstr "" + +#. Tag: para +#: Ldap.xml:606 +#, no-c-format +msgid "" +"LDAP servers support depends on few conditions. In most cases they differ in " +"schema support - various objectClass objects are not present by default in " +"server schema. Sometimes it can be workarounded by manually extending schema." +msgstr "" + +#. Tag: para +#: Ldap.xml:609 +#, no-c-format +msgid "Servers can be" +msgstr "" + +#. Tag: emphasis +#: Ldap.xml:612 Ldap.xml:649 Ldap.xml:650 Ldap.xml:651 Ldap.xml:652 +#: Ldap.xml:653 Ldap.xml:654 Ldap.xml:655 Ldap.xml:659 Ldap.xml:660 +#: Ldap.xml:661 Ldap.xml:662 Ldap.xml:663 Ldap.xml:665 Ldap.xml:669 +#: Ldap.xml:670 Ldap.xml:671 Ldap.xml:672 Ldap.xml:673 Ldap.xml:675 +#, no-c-format +msgid "Supported" +msgstr "" + +#. Tag: emphasis +#: Ldap.xml:613 Ldap.xml:664 Ldap.xml:674 +#, no-c-format +msgid "Not Supported" +msgstr "" + +#. Tag: para +#: Ldap.xml:614 +#, no-c-format +msgid "" +"<emphasis>Experimental</emphasis> - implementation can work with such server " +"but it's not well tested so shouldn't be considered for production." +msgstr "" + +#. Tag: title +#: Ldap.xml:618 +#, no-c-format +msgid "Support of identity modules with different LDAP servers" +msgstr "" + +#. Tag: entry +#: Ldap.xml:630 +#, no-c-format +msgid "LDAP Server" +msgstr "" + +#. Tag: entry +#: Ldap.xml:634 +#, no-c-format +msgid "<entry>UserProfileModule</entry>" +msgstr "" + +#. Tag: entry +#: Ldap.xml:643 +#, no-c-format +msgid "<entry>LDAPUserProfileModuleImpl</entry>" +msgstr "" + +#. Tag: entry +#: Ldap.xml:648 +#, no-c-format +msgid "Red Hat Directory Server" +msgstr "" + +#. Tag: entry +#: Ldap.xml:658 +#, no-c-format +msgid "OpenDS" +msgstr "" + +#. Tag: entry +#: Ldap.xml:668 +#, no-c-format +msgid "OpenLDAP" +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Migration.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Migration.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Migration.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,337 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Migration.xml:6 +#, no-c-format +msgid "Upgrading JBoss Portal 2.6 to Enterprise Portal Platform 4.3" +msgstr "" + +#. Tag: para +#: Migration.xml:9 +#, no-c-format +msgid "" +"Before performing any instructions or operations in this chapter, back up " +"your database and the entire JBoss EAP directory!" +msgstr "" + +#. Tag: para +#: Migration.xml:14 +#, no-c-format +msgid "" +"Enterprise Portal Platform 4.3 compatibility with JBoss Portal 2.6 is very " +"high. The main differences are the use of JSR-286 features to replace JBoss " +"Portal specific features. The database schema has slightly changed though." +msgstr "" + +#. Tag: title +#: Migration.xml:20 +#, no-c-format +msgid "Schema update" +msgstr "" + +#. Tag: para +#: Migration.xml:21 +#, no-c-format +msgid "" +"If you haven't used any workflow mechanism in JBoss Portal 2.6 and if the " +"database user has the rights to alter/create tables in the running database, " +"all the following changes will be automatically be done." +msgstr "" + +#. Tag: para +#: Migration.xml:23 +#, no-c-format +msgid "" +"The columns SER_STATE of the table JBP_INSTANCE and SER_STATE of the table " +"JBP_INSTANCE_PER_USER have changed from a length of 50000000 to 16384. You " +"can either alter the tables or modify the hibernate mapping file " +"<literal>portal-core-sar/conf/hibernate/instance/domain.hbm.xml </literal> " +"to set back the length to 50000000 if your database allows it." +msgstr "" + +#. Tag: para +#: Migration.xml:26 +#, no-c-format +msgid "" +"The major changes on the schema are related to JBpm as stated in the JBpm " +"3.2 release note. JBoss Portal 2.6 was using JBpm 3.1 while the Enterprise " +"Portal Platform 4.3 is using JBpm 3.2. Here is the relevant part from the " +"JBpm release note:" +msgstr "" + +#. Tag: title +#: Migration.xml:29 +#, no-c-format +msgid "JBpm 3.2 release note extract" +msgstr "" + +#. Tag: para +#: Migration.xml:30 +#, no-c-format +msgid "" +"jPDL Database Schema Updates from 3.1.x to 3.2.x <programlisting><![CDATA[\n" +"create table JBPM_JOB (\n" +" ID_ bigint generated by default as identity (start with 1), \n" +" CLASS_ char(1) not null, \n" +" VERSION_ integer not null, \n" +" DUEDATE_ timestamp, \n" +" PROCESSINSTANCE_ bigint, \n" +" TOKEN_ bigint, \n" +" TASKINSTANCE_ bigint, \n" +" ISSUSPENDED_ bit, \n" +" ISEXCLUSIVE_ bit, \n" +" LOCKOWNER_ varchar(255), \n" +" LOCKTIME_ timestamp, \n" +" EXCEPTION_ varchar(4000), \n" +" RETRIES_ integer, \n" +" NAME_ varchar(255), \n" +" REPEAT_ varchar(255),\n" +" TRANSITIONNAME_ varchar(255), \n" +" ACTION_ bigint, \n" +" GRAPHELEMENTTYPE_ varchar(255), \n" +" GRAPHELEMENT_ bigint, \n" +" NODE_ bigint, \n" +" primary key (ID_)\n" +")\n" +"\n" +"alter table JBPM_MODULEINSTANCE add column VERSION_ integer\n" +"alter table JBPM_NODE add column DESCRIPTION_ varchar(4000)\n" +"alter table JBPM_NODE add column ISASYNCEXCL_ bit\n" +"alter table JBPM_NODE add column SUBPROCNAME_ varchar(255)\n" +"alter table JBPM_NODE add column SCRIPT_ bigint\n" +"alter table JBPM_POOLEDACTOR add column VERSION_ integer\n" +"alter table JBPM_PROCESSDEFINITION add column CLASS_ char(1)\n" +"alter table JBPM_PROCESSDEFINITION add column DESCRIPTION_ varchar(4000)\n" +"alter table JBPM_PROCESSINSTANCE add column KEY_ varchar(255)\n" +"alter table JBPM_SWIMLANEINSTANCE add column VERSION_ integer\n" +"alter table JBPM_TASK add column CONDITION_ varchar(255)\n" +"alter table JBPM_TASK add column PRIORITY_ integer\n" +"alter table JBPM_TASKINSTANCE add column VERSION_ integer\n" +"alter table JBPM_TASKINSTANCE add column PROCINST_ bigint\n" +"alter table JBPM_TOKEN add column LOCK_ varchar(255)\n" +"alter table JBPM_TOKENVARIABLEMAP add column VERSION_ integer\n" +"alter table JBPM_TRANSITION add column DESCRIPTION_ varchar(4000)\n" +"alter table JBPM_TRANSITION add column CONDITION_ varchar(255)\n" +"alter table JBPM_VARIABLEINSTANCE add column VERSION_ integer\n" +"alter table JBPM_JOB add constraint FK_JOB_TOKEN foreign key (TOKEN_) " +"references JBPM_TOKEN\n" +"alter table JBPM_JOB add constraint FK_JOB_NODE foreign key (NODE_) " +"references JBPM_NODE\n" +"alter table JBPM_JOB add constraint FK_JOB_PRINST foreign key " +"(PROCESSINSTANCE_) references JBPM_PROCESSINSTANCE\n" +"alter table JBPM_JOB add constraint FK_JOB_ACTION foreign key (ACTION_) " +"references JBPM_ACTION\n" +"alter table JBPM_JOB add constraint FK_JOB_TSKINST foreign key " +"(TASKINSTANCE_) references JBPM_TASKINSTANCE\n" +"alter table JBPM_NODE add constraint FK_NODE_SCRIPT foreign key (SCRIPT_) " +"references JBPM_ACTION\n" +"alter table JBPM_PROCESSINSTANCE add constraint FK_PROCIN_SPROCTKN foreign " +"key (SUPERPROCESSTOKEN_) references JBPM_TOKEN\n" +"alter table JBPM_RUNTIMEACTION add constraint FK_RTACTN_PROCINST foreign key " +"(PROCESSINSTANCE_) references JBPM_PROCESSINSTANCE\n" +"alter table JBPM_RUNTIMEACTION add constraint FK_RTACTN_ACTION foreign key " +"(ACTION_) references JBPM_ACTION\n" +"alter table JBPM_SWIMLANE add constraint FK_SWL_ASSDEL foreign key " +"(ASSIGNMENTDELEGATION_) references JBPM_DELEGATION\n" +"alter table JBPM_SWIMLANE add constraint FK_SWL_TSKMGMTDEF foreign key " +"(TASKMGMTDEFINITION_) references JBPM_MODULEDEFINITION\n" +"alter table JBPM_SWIMLANEINSTANCE add constraint FK_SWIMLANEINST_TM foreign " +"key (TASKMGMTINSTANCE_) references JBPM_MODULEINSTANCE\n" +"alter table JBPM_SWIMLANEINSTANCE add constraint FK_SWIMLANEINST_SL foreign " +"key (SWIMLANE_) references JBPM_SWIMLANE\n" +"alter table JBPM_TASK add constraint FK_TSK_TSKCTRL foreign key " +"(TASKCONTROLLER_) references JBPM_TASKCONTROLLER\n" +"alter table JBPM_TASK add constraint FK_TASK_ASSDEL foreign key " +"(ASSIGNMENTDELEGATION_) references JBPM_DELEGATION\n" +"alter table JBPM_TASK add constraint FK_TASK_TASKNODE foreign key " +"(TASKNODE_) references JBPM_NODE\n" +"alter table JBPM_TASK add constraint FK_TASK_PROCDEF foreign key " +"(PROCESSDEFINITION_) references JBPM_PROCESSDEFINITION\n" +"alter table JBPM_TASK add constraint FK_TASK_STARTST foreign key " +"(STARTSTATE_) references JBPM_NODE\n" +"alter table JBPM_TASK add constraint FK_TASK_TASKMGTDEF foreign key " +"(TASKMGMTDEFINITION_) references JBPM_MODULEDEFINITION\n" +"alter table JBPM_TASK add constraint FK_TASK_SWIMLANE foreign key " +"(SWIMLANE_) references JBPM_SWIMLANE\n" +"alter table JBPM_TASKACTORPOOL add constraint FK_TSKACTPOL_PLACT foreign key " +"(POOLEDACTOR_) references JBPM_POOLEDACTOR\n" +"alter table JBPM_TASKACTORPOOL add constraint FK_TASKACTPL_TSKI foreign key " +"(TASKINSTANCE_) references JBPM_TASKINSTANCE\n" +"alter table JBPM_TASKCONTROLLER add constraint FK_TSKCTRL_DELEG foreign key " +"(TASKCONTROLLERDELEGATION_) references JBPM_DELEGATION\n" +"alter table JBPM_TASKINSTANCE add constraint FK_TSKINS_PRCINS foreign key " +"(PROCINST_) references JBPM_PROCESSINSTANCE\n" +"alter table JBPM_TASKINSTANCE add constraint FK_TASKINST_TMINST foreign key " +"(TASKMGMTINSTANCE_) references JBPM_MODULEINSTANCE\n" +"alter table JBPM_TASKINSTANCE add constraint FK_TASKINST_TOKEN foreign key " +"(TOKEN_) references JBPM_TOKEN\n" +"alter table JBPM_TASKINSTANCE add constraint FK_TASKINST_SLINST foreign key " +"(SWIMLANINSTANCE_) references JBPM_SWIMLANEINSTANCE\n" +"alter table JBPM_TASKINSTANCE add constraint FK_TASKINST_TASK foreign key " +"(TASK_) references JBPM_TASK\n" +"alter table JBPM_TOKEN add constraint FK_TOKEN_PARENT foreign key (PARENT_) " +"references JBPM_TOKEN\n" +"alter table JBPM_TOKEN add constraint FK_TOKEN_NODE foreign key (NODE_) " +"references JBPM_NODE\n" +"alter table JBPM_TOKEN add constraint FK_TOKEN_PROCINST foreign key " +"(PROCESSINSTANCE_) references JBPM_PROCESSINSTANCE\n" +"alter table JBPM_TOKEN add constraint FK_TOKEN_SUBPI foreign key " +"(SUBPROCESSINSTANCE_) references JBPM_PROCESSINSTANCE\n" +"alter table JBPM_TOKENVARIABLEMAP add constraint FK_TKVARMAP_CTXT foreign " +"key (CONTEXTINSTANCE_) references JBPM_MODULEINSTANCE\n" +"alter table JBPM_TOKENVARIABLEMAP add constraint FK_TKVARMAP_TOKEN foreign " +"key (TOKEN_) references JBPM_TOKEN\n" +"alter table JBPM_TRANSITION add constraint FK_TRANSITION_TO foreign key " +"(TO_) references JBPM_NODE\n" +"alter table JBPM_TRANSITION add constraint FK_TRANS_PROCDEF foreign key " +"(PROCESSDEFINITION_) references JBPM_PROCESSDEFINITION\n" +"alter table JBPM_TRANSITION add constraint FK_TRANSITION_FROM foreign key " +"(FROM_) references JBPM_NODE\n" +"alter table JBPM_VARIABLEACCESS add constraint FK_VARACC_TSKCTRL foreign key " +"(TASKCONTROLLER_) references JBPM_TASKCONTROLLER\n" +"alter table JBPM_VARIABLEACCESS add constraint FK_VARACC_SCRIPT foreign key " +"(SCRIPT_) references JBPM_ACTION\n" +"alter table JBPM_VARIABLEACCESS add constraint FK_VARACC_PROCST foreign key " +"(PROCESSSTATE_) references JBPM_NODE\n" +"alter table JBPM_VARIABLEINSTANCE add constraint FK_VARINST_TK foreign key " +"(TOKEN_) references JBPM_TOKEN\n" +"alter table JBPM_VARIABLEINSTANCE add constraint FK_VARINST_TKVARMP foreign " +"key (TOKENVARIABLEMAP_) references JBPM_TOKENVARIABLEMAP\n" +"alter table JBPM_VARIABLEINSTANCE add constraint FK_VARINST_PRCINST foreign " +"key (PROCESSINSTANCE_) references JBPM_PROCESSINSTANCE\n" +"alter table JBPM_VARIABLEINSTANCE add constraint FK_VAR_TSKINST foreign key " +"(TASKINSTANCE_) references JBPM_TASKINSTANCE\n" +"alter table JBPM_VARIABLEINSTANCE add constraint FK_BYTEINST_ARRAY foreign " +"key (BYTEARRAYVALUE_) references JBPM_BYTEARRAY\n" +"\n" +"insert into JBPM_JOB\n" +" (ID_,\n" +" CLASS_,\n" +" VERSION_,\n" +" DUEDATE_,\n" +" PROCESSINSTANCE_,\n" +" TOKEN_,\n" +" TASKINSTANCE_,\n" +" ISSUSPENDED_,\n" +" ISEXCLUSIVE_,\n" +" LOCKOWNER_,\n" +" LOCKTIME_,\n" +" EXCEPTION_,\n" +" RETRIES_,\n" +" NAME_,\n" +" REPEAT_,\n" +" TRANSITIONNAME_,\n" +" ACTION_,\n" +" GRAPHELEMENTTYPE_,\n" +" GRAPHELEMENT_)\n" +"select\n" +" ID_,\n" +" 'T',\n" +" 0,\n" +" DUEDATE_,\n" +" PROCESSINSTANCE_,\n" +" TOKEN_,\n" +" TASKINSTANCE_,\n" +" ISSUSPENDED_,\n" +" 0,\n" +" NULL,\n" +" NULL,\n" +" EXCEPTION_,\n" +" 0,\n" +" NAME_,\n" +" REPEAT_,\n" +" TRANSITIONNAME_,\n" +" ACTION_,\n" +" GRAPHELEMENTTYPE_,\n" +" GRAPHELEMENT_\n" +"from JBPM_TIMER;\n" +"\n" +"drop table JBPM_MESSAGE\n" +"]]></programlisting> Since, 3.2, the table JBPM_DECISIONCONDITION is not " +"used any more. But it is still in the default generated schema because of " +"backwards compatibility reasons. Newly deployed processes (even if they have " +"decision conditions) will not use that table any more. So if your old " +"processes don't have decision conditions or if you only deploy new processes " +"to your db, you can safely drop the JBPM_DECISIONCONDITION table. If you do " +"that, don't forget to remove the line that refers to the decision condition " +"class in your hibernate.cfg.xml and also remove the decisionConditions list " +"entry in the org/jbpm/graph/node/Decision.hbm.xml file." +msgstr "" + +#. Tag: title +#: Migration.xml:45 +#, no-c-format +msgid "Usage of JBossActionRequest" +msgstr "" + +#. Tag: para +#: Migration.xml:46 +#, no-c-format +msgid "" +"Usage of JBossActionRequest is not available directly anymore. From now on " +"it is only accessible if the <emphasis>org.jboss.portlet.filter." +"JBossPortletFilter</emphasis> is applied on the portlet. To do so, first you " +"will need to change the <emphasis>portlet.xml</emphasis> descriptor in order " +"to declare the new portlet as a JSR-286 portlet so that the filter can be " +"applied. For a portlet named <emphasis>MyFooPortlet</emphasis> it would now " +"look like this:" +msgstr "" + +#. Tag: programlisting +#: Migration.xml:52 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<portlet-app\n" +" xmlns=\"http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd\"... +" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n" +" xsi:schemaLocation=\"http://java.sun.com/xml/ns/portlet/portlet-app_... +"xsd http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd\"\n" +" version=\"2.0\">\n" +" \n" +" <portlet>\n" +" <description>My foo portlet</description>\n" +" <portlet-name>MyFooPortlet</portlet-name>\n" +" ...\n" +" </portlet>\n" +"\n" +" <filter>\n" +" <filter-name>JBoss Portlet Filter</filter-name>\n" +" <filter-class>org.jboss.portlet.filter.JBossPortletFilter</filter-" +"class>\n" +" <lifecycle>ACTION_PHASE</lifecycle>\n" +" <lifecycle>RENDER_PHASE</lifecycle>\n" +" </filter>\n" +" \n" +" <filter-mapping>\n" +" <filter-name>JBoss Portlet Filter</filter-name>\n" +" <portlet-name>MyFooPortlet</portlet-name>\n" +" </filter-mapping>\n" +" \n" +"</portlet-app>\n" +" \n" +"]]>" +msgstr "" + +#. Tag: para +#: Migration.xml:53 +#, no-c-format +msgid "" +"By not adding this filter on a portlet using JBossActionRequest/" +"JBossActionResponse, an error message such as: <emphasis>The request isn't a " +"JBossRenderRequest, you probably need to activate the JBoss Portlet Filter: " +"org.jboss.portlet.filter.JBossPortletFilter on MyFooPortlet</emphasis>" +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Nav_Tabs.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Nav_Tabs.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Nav_Tabs.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,148 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Nav_Tabs.xml:16 +#, no-c-format +msgid "Navigation Tabs" +msgstr "" + +#. Tag: para +#: Nav_Tabs.xml:17 +#, no-c-format +msgid "" +"The navigation tabs allow users to navigate the portal pages. This section " +"describes some of the functionality available in configuring them." +msgstr "" + +#. Tag: title +#: Nav_Tabs.xml:26 +#, no-c-format +msgid "Explicit ordering of tabs" +msgstr "" + +#. Tag: para +#: Nav_Tabs.xml:27 +#, no-c-format +msgid "" +"Explicit ordering of the tab display, is accomplished via page properties " +"that are defined in your <emphasis>*-object.xml</emphasis> ( <xref linkend=" +"\"desc_objectxml\"/> ). Ordering is accomplished using the <emphasis>order</" +"emphasis> tag at the page level as a page property." +msgstr "" + +#. Tag: programlisting +#: Nav_Tabs.xml:34 +#, no-c-format +msgid "" +"<![CDATA[\r\n" +"<page>\r\n" +" <page-name>default</page-name>\r\n" +" <properties>\r\n" +" <property>\r\n" +" <name>order</name>\r\n" +" <value>1</value>\r\n" +" </property>\r\n" +" </properties>\r\n" +" ...\r\n" +"</page>]]>" +msgstr "" + +#. Tag: title +#: Nav_Tabs.xml:48 +#, no-c-format +msgid "Translating tab labels" +msgstr "" + +#. Tag: para +#: Nav_Tabs.xml:49 +#, no-c-format +msgid "" +"Labels on tabs can be defined in multiple languages. Two different ways can " +"be used, the first one consist at defining several display name for page " +"objects, the second one consists of defining a resource bundle where to find " +"the localized display-name. Both methods have advantages and drawbacks." +msgstr "" + +#. Tag: title +#: Nav_Tabs.xml:53 +#, no-c-format +msgid "Method one: Multiple <literal>display-name</literal>" +msgstr "" + +#. Tag: para +#: Nav_Tabs.xml:54 +#, no-c-format +msgid "" +"In the <filename>*-object.xml</filename> descriptor under the <literal>page</" +"literal> element, it is possible to define a display-name per locale. Here " +"is an example: <programlisting><![CDATA[\r\n" +"<page>\r\n" +" <page-name>News</page-name>\r\n" +" <display-name xml:lang=\"en\">News</display-name>\r\n" +" <display-name xml:lang=\"it\">Novita'</display-name>\r\n" +" <display-name xml:lang=\"es\">Noticias</display-name>\r\n" +" <display-name xml:lang=\"fr\">Actualités</display-name>\r\n" +" ...\r\n" +"</page>\r\n" +" ]]></programlisting> Here we defined a display name for four " +"different languages. The advantage of this method is that it is simple and " +"the display name is kept along the metadata. The drawback of this method is " +"that if you may end up with different places to keep your localized data. If " +"you are using resource bundles for other elements, the second method might " +"be simpler when you add new supported languages." +msgstr "" + +#. Tag: title +#: Nav_Tabs.xml:73 +#, no-c-format +msgid "Defining a resource bundle and supported locales" +msgstr "" + +#. Tag: para +#: Nav_Tabs.xml:74 +#, no-c-format +msgid "" +"If you are already using resource bundles for localization you may prefer to " +"point to those files. To do so you can define the name of your ressource " +"bundle. The files should be in the classloader of the war containing the " +"<filename>*-object.xml</filename> where you define them, meaning in the same " +"war file." +msgstr "" + +#. Tag: para +#: Nav_Tabs.xml:77 +#, no-c-format +msgid "" +"Here is an example: <programlisting><![CDATA[\r\n" +"<page>\r\n" +" <page-name>Weather</page-name>\r\n" +" <supported-locale>fr</supported-locale>\r\n" +" <supported-locale>en</supported-locale>\r\n" +" ...\r\n" +"</page>\r\n" +" ]]></programlisting> With one or the other method, accessing the " +"portal will now display the tab names with the preferred locale if a " +"localized value exists." +msgstr "" + +#. Tag: para +#: Nav_Tabs.xml:89 +#, no-c-format +msgid "" +"If you change the values in the descriptor (method 1) or in the resource " +"bundles (method 2) you need to use the <literal>&lt;if-exists&gt;" +"overwrite&lt;/if-exists&gt;</literal> so that the values are updated" +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Portal_API.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Portal_API.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Portal_API.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,1275 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Portal_API.xml:15 +#, no-c-format +msgid "Portal API" +msgstr "" + +#. Tag: title +#: Portal_API.xml:17 +#, no-c-format +msgid "Introduction" +msgstr "" + +#. Tag: para +#: Portal_API.xml:19 +#, no-c-format +msgid "" +"JBoss Portal provides an Application Programming Interface (API) which " +"allows to write code that interacts with the portal. The life time and " +"validity of the API is tied to the major version which means that no changes " +"should be required when code is written against the API provided by the " +"JBoss Portal 2.x versions and used in a later version of JBoss Portal 2.x." +msgstr "" + +#. Tag: para +#: Portal_API.xml:24 +#, no-c-format +msgid "" +"The Portal API package prefix is <emphasis>org.jboss.portal.api</emphasis>. " +"All of the classes that are part of this API are prefixed with this package " +"name except for the <emphasis>org.jboss.portal.Mode</emphasis> and " +"<emphasis>org.jboss.portal.WindowState</emphasis> classes. These two classes " +"were defined before the official Portal API framework was created and so the " +"names have been maintained for backward compatibility." +msgstr "" + +#. Tag: para +#: Portal_API.xml:28 +#, no-c-format +msgid "" +"The Portlet API defines two classes that represent a portion of the visual " +"state of a Portlet which are <emphasis>javax.portlet.PortletMode</emphasis> " +"and <emphasis>javax.portlet.WindowState</emphasis>. Likewise the Portal API " +"defines similar classes named <emphasis>org.jboss.portal.Mode</emphasis> and " +"<emphasis>org.jboss.portal.WindowState</emphasis> which offer comparable " +"characteristics, the main differences are:" +msgstr "" + +#. Tag: para +#: Portal_API.xml:34 +#, no-c-format +msgid "Usage of factory methods to obtain instances." +msgstr "" + +#. Tag: para +#: Portal_API.xml:35 +#, no-c-format +msgid "" +"Classes implements the <emphasis>java.io.Serializable</emphasis> interface." +msgstr "" + +#. Tag: para +#: Portal_API.xml:42 +#, no-c-format +msgid "The Mode class" +msgstr "" + +#. Tag: para +#: Portal_API.xml:51 +#, no-c-format +msgid "The WindowState class" +msgstr "" + +#. Tag: para +#: Portal_API.xml:53 +#, no-c-format +msgid "" +"In the Portal API, the <emphasis>Mode</emphasis> interface is named like " +"this because it does represent the mode of some visual object. The Portlet " +"API names it <emphasis>PortletMode</emphasis> because it makes the " +"assumption that the underlying object is of type Portlet." +msgstr "" + +#. Tag: title +#: Portal_API.xml:58 +#, no-c-format +msgid "Portlet to Portal communication" +msgstr "" + +#. Tag: para +#: Portal_API.xml:59 +#, no-c-format +msgid "" +"There are times when a portlet needs to signal the portal or share " +"information with it. The portal is the only authority to decide if it will " +"take into account that piece of information or ignore it. In JBoss Portal we " +"use as much as possible the mechanisms offered by the portlet spec to " +"achieve that communication." +msgstr "" + +#. Tag: title +#: Portal_API.xml:63 +#, no-c-format +msgid "Requesting a sign out" +msgstr "" + +#. Tag: para +#: Portal_API.xml:64 +#, no-c-format +msgid "" +"If a portlet desires to sign out the user, it can let the portal know by " +"triggering a JSR-286 portlet event. To do so, simply defines the event " +"\"signOut\" in the namespace \"urn:jboss:portal\" as a publishing event. In " +"the action phase of the portlet, trigger the event, as a payload you can " +"specify a redirection URL. If the payload is null, it will redirect the user " +"to the default page of the default portal. See the following snippet to use " +"in the action phase, it will ask the portal to sign out the user and " +"redirect him to the JBoss Portal blog:" +msgstr "" + +#. Tag: programlisting +#: Portal_API.xml:71 +#, no-c-format +msgid "" +"<![CDATA[QName name = new QName(\"urn:jboss:portal\", \"signOut\");\n" +"response.setEvent(name, \"http://blog.jboss-portal.org\"); ]]>" +msgstr "" + +#. Tag: title +#: Portal_API.xml:75 +#, no-c-format +msgid "Setting up the web browser title" +msgstr "" + +#. Tag: para +#: Portal_API.xml:76 +#, no-c-format +msgid "" +"The JSR-286 specification introduced a new phase for setting up the HTML " +"headers. It is commonly used to add stylesheets and javascript to the page. " +"An extension of it for JBoss Portal lets you define the web browser title. " +"To define the web browser title, a portlet simply needs to define a new " +"header element \"title\". This could be done by a portlet overriding the " +"method <literal>doHeaders(RenderRequest req, RenderResponse resp)</literal> " +"to add such an element." +msgstr "" + +#. Tag: programlisting +#: Portal_API.xml:81 +#, no-c-format +msgid "" +"<![CDATA[public void doHeaders(RenderRequest req, RenderResponse resp)\n" +"{\n" +" Element element = resp.createElement(\"title\");\n" +" element.setTextContent(\"My new web browser title\");\n" +" resp.addProperty(MimeResponse.MARKUP_HEAD_ELEMENT, element);\n" +"}]]>" +msgstr "" + +#. Tag: para +#: Portal_API.xml:82 +#, no-c-format +msgid "" +"It several portlets on a page defines a web browser title, only one of them " +"will be displayed. We can consider that the title to be displayed will be " +"randomly chosen." +msgstr "" + +#. Tag: title +#: Portal_API.xml:88 +#, no-c-format +msgid "Portal URL" +msgstr "" + +#. Tag: para +#: Portal_API.xml:89 +#, no-c-format +msgid "" +"The Portal API defines the <emphasis>org.jboss.portal.api.PortalURL</" +"emphasis> interface to represent URL managed by the portal." +msgstr "" + +#. Tag: para +#: Portal_API.xml:96 +#, no-c-format +msgid "The PortalURL interface" +msgstr "" + +#. Tag: para +#: Portal_API.xml:99 +#, no-c-format +msgid "" +"The <emphasis>setAuthenticated(Boolean wantAuthenticated)</emphasis> methods " +"defines if the URL requires the authentication of the user. If the argument " +"value is true then the user must be authenticated to access the URL, if the " +"argument value is false then the user should not be authenticated. Finally " +"if the argument value is null then it means that the URL authenticated mode " +"should reuse the current mode." +msgstr "" + +#. Tag: para +#: Portal_API.xml:103 +#, no-c-format +msgid "" +"The <emphasis>setSecure(Boolean wantSecure)</emphasis> methods defines the " +"same as above but for the transport guarantee offered by the underlying " +"protocol which means most of the time the secure HTTP protocol (HTTPS)." +msgstr "" + +#. Tag: para +#: Portal_API.xml:105 +#, no-c-format +msgid "" +"The <emphasis>setRelative(boolean relative)</emphasis> defines the output " +"format of the URL and whether the created URL will be an URL relative to the " +"same web server or will be the full URL." +msgstr "" + +#. Tag: para +#: Portal_API.xml:107 +#, no-c-format +msgid "" +"The <emphasis>toString()</emphasis> method will create the URL as a string." +msgstr "" + +#. Tag: title +#: Portal_API.xml:111 +#, no-c-format +msgid "Portal session" +msgstr "" + +#. Tag: para +#: Portal_API.xml:117 +#, no-c-format +msgid "The PortalSession interface" +msgstr "" + +#. Tag: para +#: Portal_API.xml:119 +#, no-c-format +msgid "" +"It is possible to have access to a portion of the portal session to store " +"objects. The <emphasis>org.jboss.portal.api.session.PortalSession</emphasis> " +"interface defines its API and is similar to the <emphasis>javax.servlet.http." +"HttpSession</emphasis> except that it does not offer methods to invalidate " +"the session as the session is managed by the portal." +msgstr "" + +#. Tag: title +#: Portal_API.xml:126 +#, no-c-format +msgid "Portal runtime context" +msgstr "" + +#. Tag: para +#: Portal_API.xml:132 +#, no-c-format +msgid "The PortalRuntimeContext interface" +msgstr "" + +#. Tag: para +#: Portal_API.xml:134 +#, no-c-format +msgid "" +"The <emphasis>org.jboss.portal.api.PortalRuntimeContext</emphasis> gives " +"access to state or operations associated at runtime with the current user of " +"the portal. The <emphasis>String getUserId()</emphasis> retrieve the user id " +"and can return null if no user is associated with the context. It also gives " +"access to the <emphasis>PortalSession</emphasis> instance associated with " +"the current user. Finally it gives access to the " +"<emphasis>NavigationalStateContext</emphasis> associated with the current " +"user." +msgstr "" + +#. Tag: title +#: Portal_API.xml:142 +#, no-c-format +msgid "Portal nodes" +msgstr "" + +#. Tag: para +#: Portal_API.xml:143 +#, no-c-format +msgid "" +"The portal structure is a tree formed by nodes. It is possible to " +"programmatically access the portal tree in order to" +msgstr "" + +#. Tag: para +#: Portal_API.xml:146 +#, no-c-format +msgid "discover the tree structure of the portal" +msgstr "" + +#. Tag: para +#: Portal_API.xml:147 +#, no-c-format +msgid "create URL that will render the different portal nodes" +msgstr "" + +#. Tag: para +#: Portal_API.xml:148 +#, no-c-format +msgid "access the properties of a specific node" +msgstr "" + +#. Tag: para +#: Portal_API.xml:155 +#, no-c-format +msgid "The PortalNode interface" +msgstr "" + +#. Tag: para +#: Portal_API.xml:157 +#, no-c-format +msgid "" +"As usual with tree structures, the main interface to study is the " +"<emphasis>org.jboss.portal.api.node.PortalNode</emphasis>. That interface is " +"intentionally intended for obtaining useful information from the tree. It is " +"not possible to use it to modify the tree shape because it is not intended " +"to be a management interface." +msgstr "" + +#. Tag: programlisting +#: Portal_API.xml:160 +#, no-c-format +msgid "" +"<![CDATA[\n" +"public interface PortalNode\n" +"{\n" +" int getType();\n" +" String getName();\n" +" String getDisplayName(Locale locale);\n" +" Map getProperties();\n" +" PortalNodeURL createURL(PortalRuntimeContext portalRuntimeContext);\n" +" ...\n" +"}\n" +"]]>" +msgstr "" + +#. Tag: para +#: Portal_API.xml:161 +#, no-c-format +msgid "" +"The interface offers methods to retrieve informations for a given node such " +"as the node type, the node name or the properties of the node. The " +"noticeable node types are:" +msgstr "" + +#. Tag: para +#: Portal_API.xml:164 +#, no-c-format +msgid "PortalNode.TYPE_PORTAL : the node represents a portal" +msgstr "" + +#. Tag: para +#: Portal_API.xml:165 +#, no-c-format +msgid "PortalNode.TYPE_PAGE : the node represents a portal page" +msgstr "" + +#. Tag: para +#: Portal_API.xml:166 +#, no-c-format +msgid "PortalNode.TYPE_WINDOW : the node represents a page window" +msgstr "" + +#. Tag: para +#: Portal_API.xml:168 +#, no-c-format +msgid "" +"The <emphasis>org.jboss.portal.api.node.PortalNodeURL</emphasis> is an " +"extension of the <emphasis>PortalURL</emphasis> interface which adds " +"additional methods useful for setting parameters on the URL. There are no " +"guarantees that the portal node will use the parameters. So far portal node " +"URL parameters are only useful for nodes of type <emphasis>PortalNode." +"TYPE_WINDOW</emphasis> and they should be treated as portlet render " +"parameters in the case of the portlet is a local portlet and is not a remote " +"portlet. The method that creates portal node URL requires as parameter an " +"instance of <emphasis>PortalRuntimeContext</emphasis>." +msgstr "" + +#. Tag: para +#: Portal_API.xml:174 +#, no-c-format +msgid "The interface also offers methods to navigate the node hierarchy:" +msgstr "" + +#. Tag: programlisting +#: Portal_API.xml:175 +#, no-c-format +msgid "" +"<![CDATA[\n" +"public interface PortalNode\n" +"{\n" +" ...\n" +" PortalNode getChild(String name);\n" +" Collection getChildren();\n" +" PortalNode getRoot();\n" +" PortalNode getParent();\n" +" ...\n" +"}\n" +"]]>" +msgstr "" + +#. Tag: title +#: Portal_API.xml:178 +#, no-c-format +msgid "Portal navigational state" +msgstr "" + +#. Tag: para +#: Portal_API.xml:179 +#, no-c-format +msgid "" +"The navigational state is a state managed by the portal that associates to " +"each user the state triggered by its navigation. A well known part of the " +"navigational state are the render parameters provided at runtime during the " +"call of the method <emphasis>void render(RenderRequest req, RenderResponse " +"resp)</emphasis>. The portal API offers an interface to query and update the " +"navigational state of the portal. For now the API only exposes mode and " +"window states of portal nodes of type window." +msgstr "" + +#. Tag: para +#: Portal_API.xml:189 +#, no-c-format +msgid "The NavigationalStateContext interface" +msgstr "" + +#. Tag: title +#: Portal_API.xml:193 +#, no-c-format +msgid "Portal events" +msgstr "" + +#. Tag: para +#: Portal_API.xml:194 +#, no-c-format +msgid "" +"Portal events are a powerful mechanism to be aware of what is happening in " +"the portal at runtime. The base package for event is <emphasis>org.jboss." +"portal.api.event</emphasis> and it contains the common event classes and " +"interfaces." +msgstr "" + +#. Tag: para +#: Portal_API.xml:203 +#, no-c-format +msgid "The PortalEvent class" +msgstr "" + +#. Tag: para +#: Portal_API.xml:205 +#, no-c-format +msgid "" +"The <emphasis>org.jboss.portal.api.event.PortalEvent</emphasis> abstract " +"class is the base class for all kind of portal events." +msgstr "" + +#. Tag: para +#: Portal_API.xml:213 +#, no-c-format +msgid "The PortalEventContext interface" +msgstr "" + +#. Tag: para +#: Portal_API.xml:215 +#, no-c-format +msgid "" +"The <emphasis>org.jboss.portal.api.event.PortalEventContext</emphasis> " +"interface defines the context in which an event is created and propagated. " +"It allows retrieval of the <emphasis>PortalRuntimeContext</emphasis> which " +"can in turn be used to obtain the portal context." +msgstr "" + +#. Tag: para +#: Portal_API.xml:225 +#, no-c-format +msgid "The PortalEventListener interface" +msgstr "" + +#. Tag: para +#: Portal_API.xml:227 +#, no-c-format +msgid "" +"The <emphasis>org.jboss.portal.api.event.PortalEventListener</emphasis> " +"interface defines the contract that class can implement in order to receive " +"portal event notifications. It contains the method <emphasis>void onEvent" +"(PortalEvent event)</emphasis> called by the portal framework." +msgstr "" + +#. Tag: para +#: Portal_API.xml:232 +#, no-c-format +msgid "" +"Listeners declaration requires a service to be deployed in JBoss that will " +"instantiate the service implementation and register it with the service " +"registry. We will see how to achieve that in the example section of this " +"chapter." +msgstr "" + +#. Tag: para +#: Portal_API.xml:237 +#, no-c-format +msgid "" +"The event propagation model uses one instance of a listener class to receive " +"all portal events that may be routed to that class when appropriate. " +"Therefore implementors needs to be aware of that model and must provide " +"<emphasis role=\"bold\">thread safe</emphasis> implementations." +msgstr "" + +#. Tag: title +#: Portal_API.xml:242 +#, no-c-format +msgid "Portal node events" +msgstr "" + +#. Tag: para +#: Portal_API.xml:243 +#, no-c-format +msgid "" +"Portal node events extend the abstract portal event framework in order to " +"provide notifications about user interface events happening at runtime. For " +"instance when the portal renders a page or a window, a corresponding event " +"will be fired." +msgstr "" + +#. Tag: para +#: Portal_API.xml:251 +#, no-c-format +msgid "The portal node event class hierarchy" +msgstr "" + +#. Tag: para +#: Portal_API.xml:253 +#, no-c-format +msgid "" +"The <emphasis>org.jboss.portal.api.node.event.PortalNodeEvent</emphasis> " +"class extends the <emphasis>org.jboss.portal.api.node.PortalEvent</emphasis> " +"class and is the base class for all events of portal nodes. It defines a " +"single method <emphasis>PortalNode getNode()</emphasis> which can be used to " +"retrieve the node targetted by the event." +msgstr "" + +#. Tag: para +#: Portal_API.xml:257 +#, no-c-format +msgid "" +"The <emphasis>org.jboss.portal.api.node.event.WindowEvent</emphasis> is an " +"extension for portal nodes of type window. It provides access to the mode " +"and window state of the window. It has 3 subclasses which represent " +"different kind of event that can target windows." +msgstr "" + +#. Tag: para +#: Portal_API.xml:260 +#, no-c-format +msgid "" +"The <emphasis>org.jboss.portal.api.node.event.WindowNavigationEvent</" +"emphasis> is fired when the window navigational state changes. For a portlet " +"it means that the window is targetted by an URL of type render." +msgstr "" + +#. Tag: para +#: Portal_API.xml:263 +#, no-c-format +msgid "" +"The <emphasis>org.jboss.portal.api.node.event.WindowActionEvent</emphasis> " +"is fired when the window is targetted by an action. For a portlet it means " +"that the window is targetted by an URL of type action." +msgstr "" + +#. Tag: para +#: Portal_API.xml:266 +#, no-c-format +msgid "" +"The <emphasis>org.jboss.portal.api.node.event.WindowRenderEvent</emphasis> " +"is fired when the window is going to be rendered by the portal." +msgstr "" + +#. Tag: para +#: Portal_API.xml:268 +#, no-c-format +msgid "" +"The <emphasis>org.jboss.portal.api.node.event.PageEvent</emphasis> is an " +"extension for portal nodes of type page." +msgstr "" + +#. Tag: para +#: Portal_API.xml:270 +#, no-c-format +msgid "" +"The <emphasis>org.jboss.portal.api.node.event.PageRenderEvent</emphasis> is " +"fired when the page is going to be rendered by the portal." +msgstr "" + +#. Tag: title +#: Portal_API.xml:273 +#, no-c-format +msgid "Portal node event propagation model" +msgstr "" + +#. Tag: para +#: Portal_API.xml:274 +#, no-c-format +msgid "" +"A portal node event is fired when an event of interest happens to a portal " +"node of the portal tree. The notification model is comparable to the <ulink " +"url=\"http://en.wikipedia.org/wiki/DOM_Events#Event_flow\">bubbling " +"propagation model </ulink> defined by the DOM specification. When an event " +"is fired, the event is propagated in the hierarchy from the most inner node " +"where the event happens to the root node of the tree." +msgstr "" + +#. Tag: para +#: Portal_API.xml:285 +#, no-c-format +msgid "The portal node event propagation model" +msgstr "" + +#. Tag: title +#: Portal_API.xml:290 +#, no-c-format +msgid "Portal node event listener" +msgstr "" + +#. Tag: para +#: Portal_API.xml:291 +#, no-c-format +msgid "" +"The <emphasis>org.jboss.portal.api.node.event.PortalNodeEventListener</" +"emphasis> interface should be used instead of the too generic <emphasis>org." +"jboss.portal.api.event.PortalEventListener</emphasis> when it comes down of " +"listening portal node events. Actually it does not replace it, the " +"<emphasis>PortalEventListener</emphasis> interface semantic allows only " +"traditional event delivering. The <emphasis>PortalNodeEventListener</" +"emphasis> interface is designed to match the bubbling effect during an event " +"delivery." +msgstr "" + +#. Tag: para +#: Portal_API.xml:296 +#, no-c-format +msgid "" +"The <emphasis>PortalNodeEvent onEvent(PortalNodeEventContext context, " +"PortalNodeEvent event)</emphasis> method declares a " +"<emphasis>PortalNodeEvent</emphasis> as return type. Commonly the method " +"returns null; however, a returned PortalNodeEvent replaces the event in the " +"listeners subsequently called during the event bubbling process." +msgstr "" + +#. Tag: title +#: Portal_API.xml:303 +#, no-c-format +msgid "Portal node event context" +msgstr "" + +#. Tag: para +#: Portal_API.xml:309 +#, no-c-format +msgid "The PortalNodeEventContext interface" +msgstr "" + +#. Tag: para +#: Portal_API.xml:311 +#, no-c-format +msgid "" +"The <emphasis>org.jboss.portal.api.node.event.PortalNodeEventContext</" +"emphasis> interface extends the <emphasis>PortalEventContext</emphasis> " +"interface and plays an important role in the event delivery model explained " +"in the previous section. That interface gives full control over the delivery " +"of the event to ascendant nodes in the hierarchy, even more it gives the " +"possibility to replace the current event being delivered by a new event that " +"will be transformed into the corresponding portal behavior. However there " +"are no guarantees that the portal will turn the returned event into a portal " +"behavior, here the portal provides a best effort policy, indeed sometime it " +"is not possible to achieve the substitution of one event by another." +msgstr "" + +#. Tag: para +#: Portal_API.xml:319 +#, no-c-format +msgid "" +"Here the simplest implementation of a listener that does nothing except than " +"correctly passing the control to a parent event listener if there is one." +msgstr "" + +#. Tag: programlisting +#: Portal_API.xml:321 +#, no-c-format +msgid "" +"<![CDATA[\n" +"public PortalNodeEvent onEvent(PortalNodeEventContext context, " +"PortalNodeEvent event)\n" +"{\n" +" return context.dispatch();\n" +"}\n" +"]]>" +msgstr "" + +#. Tag: para +#: Portal_API.xml:322 +#, no-c-format +msgid "" +"The method <emphasis>PortalNode getNode()</emphasis> returns the current " +"node being selected during the event bubbler dispatching mechanism." +msgstr "" + +#. Tag: title +#: Portal_API.xml:327 +#, no-c-format +msgid "Portal session events" +msgstr "" + +#. Tag: para +#: Portal_API.xml:328 +#, no-c-format +msgid "" +"The life cycle of the session of the portal associated with the user can " +"also raise events. This kind of event is not bound to a portal node since it " +"is triggered whenever a portal session is created or destroyed" +msgstr "" + +#. Tag: para +#: Portal_API.xml:335 +#, no-c-format +msgid "The PortalSessionEvent class" +msgstr "" + +#. Tag: para +#: Portal_API.xml:337 +#, no-c-format +msgid "There are two different types of events:" +msgstr "" + +#. Tag: para +#: Portal_API.xml:339 +#, no-c-format +msgid "" +"org.jboss.portal.api.session.event.PortalSessionEvent.SESSION_CREATED, fired " +"when a new portal session is created" +msgstr "" + +#. Tag: para +#: Portal_API.xml:340 +#, no-c-format +msgid "" +"org.jboss.portal.api.session.event.PortalSessionEvent.SESSION_DESTROYED, " +"fired when a new portal session is destroyed" +msgstr "" + +#. Tag: title +#: Portal_API.xml:345 +#, no-c-format +msgid "Portal user events" +msgstr "" + +#. Tag: para +#: Portal_API.xml:346 +#, no-c-format +msgid "" +"The life cycle of the portal user can also raise events such as its " +"authentication. A subclass of the wider scope UserEvent class is provided " +"and triggers events whenever a user signs in or out. The UserEvent object " +"gives access to the user name of the logged-in user through the method " +"<emphasis>String getId()</emphasis>." +msgstr "" + +#. Tag: para +#: Portal_API.xml:355 +#, no-c-format +msgid "The UserEvent class and UserAuthenticationEvent sub-classes" +msgstr "" + +#. Tag: para +#: Portal_API.xml:357 +#, no-c-format +msgid "The UserAuthenticationEvent triggers two events that can be catched:" +msgstr "" + +#. Tag: para +#: Portal_API.xml:359 +#, no-c-format +msgid "" +"org.jboss.portal.api.session.event.UserAuthenticationEvent.SIGN_IN, fired " +"when a portal user signs in" +msgstr "" + +#. Tag: para +#: Portal_API.xml:360 +#, no-c-format +msgid "" +"org.jboss.portal.api.session.event.UserAuthenticationEvent.SIGN_OUT, fired " +"when a portal user signs out" +msgstr "" + +#. Tag: para +#: Portal_API.xml:363 +#, no-c-format +msgid "" +"Based on the UserEvent class other custom user related events could be added " +"like one that would trigger when a new user is being registered" +msgstr "" + +#. Tag: title +#: Portal_API.xml:368 +#, no-c-format +msgid "Examples" +msgstr "" + +#. Tag: para +#: Portal_API.xml:369 +#, no-c-format +msgid "" +"The events mechanism is quite powerful, in this section of the chapter we " +"will see few simple examples to explain how it works." +msgstr "" + +#. Tag: title +#: Portal_API.xml:372 +#, no-c-format +msgid "UserAuthenticationEvent example" +msgstr "" + +#. Tag: para +#: Portal_API.xml:373 +#, no-c-format +msgid "" +"In this example, we will create a simple counter of the number of logged-in " +"registered users. In order to do that we just need to keep track of Sign-in " +"and Sign-out events." +msgstr "" + +#. Tag: para +#: Portal_API.xml:375 +#, no-c-format +msgid "" +"First, let's write our listener. It just a class that will implement " +"<emphasis>org.jboss.portal.api.event.PortalEventListener</emphasis> and its " +"unique method <emphasis>void onEvent(PortalEventContext eventContext, " +"PortalEvent event)</emphasis>. Here is such an example: <programlisting role=" +"\"java\"><![CDATA[\n" +"package org.jboss.portal.core.portlet.test.event;\n" +"\n" +"import[...]\n" +"\n" +"public class UserCounterListener implements PortalEventListener\n" +"{\n" +" \n" +" /** Thread-safe long */\n" +" private final SynchronizedLong counter = new SynchronizedLong(0);\n" +"\n" +" /** Thread-safe long */\n" +" private final SynchronizedLong counterEver = new SynchronizedLong(0);\n" +" \n" +" public void onEvent(PortalEventContext eventContext, PortalEvent event)\n" +" {\n" +" if (event instanceof UserAuthenticationEvent)\n" +" {\n" +" UserAuthenticationEvent userEvent = (UserAuthenticationEvent)" +"event;\n" +" if (userEvent.getType() == UserAuthenticationEvent.SIGN_IN)\n" +" {\n" +" counter.increment();\n" +" counterEver.increment();\n" +" }\n" +" else if (userEvent.getType() == UserAuthenticationEvent.SIGN_OUT)\n" +" {\n" +" counter.decrement();\n" +" }\n" +" System.out.println(\"Counter : \" + counter.get());\n" +" System.out.println(\"Counter ever: \" + counterEver.get());\n" +" }\n" +" }\n" +"}\n" +" ]]></programlisting> On this method we simply filter down to " +"UserAuthenticationEvent then depending on the type of authentication event " +"we update the counters. <emphasis>counter</emphasis> keeps track of the " +"registered and logged-in users, while counterEver only counts the number of " +"times people logged-in the portal." +msgstr "" + +#. Tag: para +#: Portal_API.xml:381 +#, no-c-format +msgid "" +"Now that the Java class has been written we need to register it so that it " +"can be called when the events are triggered. To do so we need to register it " +"as an MBean. It can be done by editing the sar descriptor file: " +"<emphasis>YourService.sar/META-INF/jboss-service.xml</emphasis> so that it " +"looks like the following: <programlisting><![CDATA[\n" +"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" +"<server> \n" +" <mbean\n" +" code=\"org.jboss.portal.core.event.PortalEventListenerServiceImpl\"\n" +" name=\"portal:service=ListenerService,type=counter_listener\"\n" +" xmbean-dd=\"\"\n" +" xmbean-code=\"org.jboss.portal.jems.as.system.JBossServiceModelMBean" +"\">\n" +" <xmbean/>\n" +" <depends\n" +" optional-attribute-name=\"Registry\"\n" +" proxy-type=\"attribute\">portal:service=ListenerRegistry</depends>\n" +" <attribute name=\"RegistryId\">counter_listener</attribute>\n" +" <attribute name=\"ListenerClassName\">\n" +" org.jboss.portal.core.portlet.test.event.UserCounterListener\n" +" </attribute>\n" +" </mbean>\n" +"</server>\n" +" ]]></programlisting> This snippet can be kept as it is, " +"providing you change the values:" +msgstr "" + +#. Tag: para +#: Portal_API.xml:388 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">name:</emphasis> Must follow the pattern: portal:" +"service=ListenerService,type={{UNIQUENAME}}" +msgstr "" + +#. Tag: para +#: Portal_API.xml:391 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">RegistryId:</emphasis> Must match the type (here: " +"counter_listener)" +msgstr "" + +#. Tag: para +#: Portal_API.xml:394 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">ListenerClassName:</emphasis> Full path to the " +"listener (here: org.jboss.portal.core.portlet.test.event." +"UserCounterListener)." +msgstr "" + +#. Tag: para +#: Portal_API.xml:399 +#, no-c-format +msgid "" +"That's it - we now have a user counter that will display it states each time " +"a user logs-in our logs-out." +msgstr "" + +#. Tag: title +#: Portal_API.xml:402 +#, no-c-format +msgid "Achieving Inter Portlet Communication with the events mechanism" +msgstr "" + +#. Tag: para +#: Portal_API.xml:403 +#, no-c-format +msgid "" +"The first version of the Portlet Specification (JSR 168), regretfully, did " +"not cover interaction between portlets. The side-effect of diverting the " +"issue to the subsequent release of the specification, has forced portal " +"vendors to each craft their own proprietary API to achieve inter portlet " +"communication. Here we will see how we can use the event mechanism to pass " +"parameters from one portlet to the other (and only to the other portlet)." +msgstr "" + +#. Tag: para +#: Portal_API.xml:407 +#, no-c-format +msgid "" +"The overall scenario will be that Portlet B will need to be updated based on " +"some parameter set on Portlet A. To achieve that we will use a portal node " +"event." +msgstr "" + +#. Tag: para +#: Portal_API.xml:409 +#, no-c-format +msgid "" +"Portlet A is a simple Generic portlet that has a form that sends a color " +"name:" +msgstr "" + +#. Tag: programlisting +#: Portal_API.xml:410 +#, no-c-format +msgid "" +"<![CDATA[ \n" +"public class PortletA extends GenericPortlet\n" +"{\n" +" protected void doView(RenderRequest request, RenderResponse response)\n" +" throws PortletException, PortletSecurityException, IOException\n" +" {\n" +" response.setContentType(\"text/html\");\n" +" PrintWriter writer = response.getWriter();\n" +" writer.println(\"<form action=\\\"\" + response.createActionURL() + " +"\"\\\" method=\\\"post\\\">\");\n" +" writer.println(\"<select name=\\\"color\\\">\");\n" +" writer.println(\"<option>blue</option>\");\n" +" writer.println(\"<option>red</option>\");\n" +" writer.println(\"<option>black</option>\");\n" +" writer.println(\"</select>\");\n" +" writer.println(\"<input type=\\\"submit\\\"/>\");\n" +" writer.println(\"</form>\");\n" +" writer.close();\n" +" }\n" +"}\n" +" ]]>" +msgstr "" + +#. Tag: para +#: Portal_API.xml:412 +#, no-c-format +msgid "" +"The other portlet (Portlet B) that will receive parameters from Portlet A is " +"also a simple Generic portlet:" +msgstr "" + +#. Tag: programlisting +#: Portal_API.xml:413 +#, no-c-format +msgid "" +"<![CDATA[ \n" +"public class PortletB extends GenericPortlet\n" +"{\n" +"\n" +" public void processAction(ActionRequest request, ActionResponse " +"response)\n" +" throws PortletException, PortletSecurityException, " +"IOException\n" +" {\n" +" String color = request.getParameter(\"color\");\n" +" if (color != null)\n" +" {\n" +" response.setRenderParameter(\"color\", color);\n" +" }\n" +" }\n" +"\n" +" protected void doView(RenderRequest request, RenderResponse response)\n" +" throws PortletException, PortletSecurityException, IOException\n" +" {\n" +" String color = request.getParameter(\"color\");\n" +" response.setContentType(\"text/html\");\n" +" PrintWriter writer = response.getWriter();\n" +" writer.println(\"<div\" +\n" +" (color == null ? \"\" : \" style=\\\"color:\" + color + \";\\\"\") " +"+\n" +" \">some text in color</div>\");\n" +" writer.close();\n" +" }\n" +" \n" +" // Inner listener explained after\n" +"}\n" +" ]]>" +msgstr "" + +#. Tag: para +#: Portal_API.xml:415 +#, no-c-format +msgid "" +"With those two portlets in hands, we just want to pass parameters from " +"Portlet A to Portlet B (the color in as a request parameter in our case). In " +"order to achieve this goal, we will write an inner Listener in Portlet B " +"that will be triggered on any WindowActionEvent of Portlet A. This listener " +"will create a new WindowActionEvent on the window of Portlet B." +msgstr "" + +#. Tag: programlisting +#: Portal_API.xml:419 +#, no-c-format +msgid "" +"<![CDATA[\n" +"public static class Listener implements PortalNodeEventListener\n" +"{\n" +" public PortalNodeEvent onEvent(PortalNodeEventContext context, " +"PortalNodeEvent event)\n" +" {\n" +" PortalNode node = event.getNode();\n" +" // Get node name\n" +" String nodeName = node.getName();\n" +" // See if we need to create a new event or not\n" +" WindowActionEvent newEvent = null;\n" +" if (nodeName.equals(\"PortletAWindow\") && event instanceof " +"WindowActionEvent)\n" +" {\n" +" // Find window B\n" +" WindowActionEvent wae = (WindowActionEvent)event;\n" +" PortalNode windowB = node.resolve(\"../PortletBWindow\");\n" +" if (windowB != null)\n" +" {\n" +" // We can redirect\n" +" newEvent = new WindowActionEvent(windowB);\n" +" newEvent.setParameters(wae.getParameters());\n" +" \n" +" newEvent.setMode(wae.getMode());\n" +" newEvent.setWindowState(WindowState.MAXIMIZED); \n" +" \n" +" // Redirect to the new event\n" +" return newEvent;\n" +" }\n" +" }\n" +" // Otherwise bubble up\n" +" return context.dispatch();\n" +" }\n" +"}\n" +" ]]>" +msgstr "" + +#. Tag: para +#: Portal_API.xml:421 +#, no-c-format +msgid "" +"It is important to note here some of the important items in this listener " +"class. Logic used to determine if the requesting node was Portlet A.:" +msgstr "" + +#. Tag: programlisting +#: Portal_API.xml:424 +#, no-c-format +msgid "nodeName.equals(\"PortletAWindow\")" +msgstr "" + +#. Tag: para +#: Portal_API.xml:426 +#, no-c-format +msgid "Get the current window object so we can dispatch the event to it:" +msgstr "" + +#. Tag: programlisting +#: Portal_API.xml:428 +#, no-c-format +msgid "PortalNode windowB = node.resolve(\"../PortletBWindow\");" +msgstr "" + +#. Tag: para +#: Portal_API.xml:430 +#, no-c-format +msgid "" +"Set the original parameter from Portlet A, so Portlet B can access them in " +"its processAction():" +msgstr "" + +#. Tag: programlisting +#: Portal_API.xml:432 +#, no-c-format +msgid "newEvent.setParameters(wae.getParameters());" +msgstr "" + +#. Tag: para +#: Portal_API.xml:440 +#, no-c-format +msgid "" +"We still need to register our listener as an mbean: <programlisting role=" +"\"xml\">\n" +"<![CDATA[<mbean\n" +" code=\"org.jboss.portal.core.event.PortalEventListenerServiceImpl\"\n" +" name=\"portal:service=ListenerService,type=test_listener\"\n" +" xmbean-dd=\"\"\n" +" xmbean-code=\"org.jboss.portal.jems.as.system.JBossServiceModelMBean\">\n" +" <xmbean/>\n" +" <depends\n" +" optional-attribute-name=\"Registry\"\n" +" proxy-type=\"attribute\">portal:service=ListenerRegistry</depends>\n" +" <attribute name=\"RegistryId\">test_listener</attribute>\n" +" <attribute name=\"ListenerClassName\">\n" +" org.jboss.portal.core.samples.basic.event.PortletB$Listener\n" +" </attribute>\n" +"</mbean>]]></programlisting> For node events, we also need to declare on " +"which node we want to listen, this is done by modifying the <literal>*-" +"object.xml</literal> that defines your portal nodes. In this example we want " +"to trigger the listener each time the window containing the portlet A is " +"actioned. We can add the <literal>listener</literal> tag to specify that out " +"listener with <literal>RegistryId</literal>=test_listener should be " +"triggered on events on the embedding object. <programlisting>\n" +"<![CDATA[...\n" +" <window>\n" +" <window-name>PortletAWindow</window-name>\n" +" <instance-ref>PortletAInstance</instance-ref>\n" +" <region>center</region>\n" +" <height>0</height>\n" +" <listener>test_listener</listener>\n" +" </window>\n" +"...]]>\n" +" </programlisting> Of course we could have added it at the page " +"level instead of the window level. Note that a unique listener can be " +"specified, the event mechanism is primarily done to let the developer change " +"the navigation state of the portal, this example being a nice side-effect of " +"this feature." +msgstr "" + +#. Tag: para +#: Portal_API.xml:453 +#, no-c-format +msgid "" +"The portlet 2.0 specification (JSR 286) will cover Inter Portlet " +"Communication so that portlets using it can work with different portal " +"vendors." +msgstr "" + +#. Tag: title +#: Portal_API.xml:457 +#, no-c-format +msgid "Link to other pages" +msgstr "" + +#. Tag: para +#: Portal_API.xml:458 +#, no-c-format +msgid "" +"Linking to some other pages or portals is also out of the scope of the " +"portlet specification. As seen previously JBoss Portal offers an API in " +"order to create links to other portal nodes. The JBoss request gives access " +"to the current window node from which we can navigate from." +msgstr "" + +#. Tag: programlisting +#: Portal_API.xml:462 +#, no-c-format +msgid "" +"<![CDATA[\n" +"// Get the ParentNode. Since we are inside a Window, the Parent is the Page\n" +"PortalNode thisNode = req.getPortalNode().getParent();\n" +"\n" +"// Get the Node in the Portal hierarchy tree known as \"../default\"\n" +"PortalNode linkToNode = thisNode.resolve(\"../default\");\n" +"\n" +"// Create a RenderURL to the \"../default\" Page Node\n" +"PortalNodeURL pageURL = resp.createRenderURL(linkToNode);\n" +"\n" +"// Output the Node's name and URL for users\n" +"html.append(\"Page: \" + linkToNode.getName() + \" -> \");\n" +"html.append(\"<a href=\\\"\" + pageURL.toString() + \"\\\">\" + linkToNode." +"getName() + \"</a>\");\n" +" ]]>" +msgstr "" + +#. Tag: para +#: Portal_API.xml:463 +#, no-c-format +msgid "" +"From this, it is easy to create a menu or sitemap, the <emphasis>List " +"getChildren()</emphasis> method will return all the child nodes on which the " +"user has the view right access." +msgstr "" + +#. Tag: title +#: Portal_API.xml:467 +#, no-c-format +msgid "Samples" +msgstr "" + +#. Tag: para +#: Portal_API.xml:468 +#, no-c-format +msgid "" +"Those examples are available in the core-samples package in the sources of " +"JBoss Portal. There are more examples of events usage in the samples " +"delivered with JBoss Portal. One of them shows the usage of a portal node " +"event to only have one window in normal mode at a time in a region. Anytime " +"another window is being put in normal mode, all the other windows of the " +"same regions are automatically minimized." +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Portal_Objects_DTD.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Portal_Objects_DTD.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Portal_Objects_DTD.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,423 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Portal_Objects_DTD.xml:7 +#, no-c-format +msgid "*-object.xml DTD" +msgstr "" + +#. Tag: programlisting +#: Portal_Objects_DTD.xml:9 +#, no-c-format +msgid "" +"<![CDATA[\n" +"\n" +" <?xml version=\"1.0\" encoding=\"UTF-8\" ?>\n" +"\n" +"<!--" +"~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n" +" ~ JBoss, a division of Red " +"Hat ~\n" +" ~ Copyright 2006, Red Hat Middleware, LLC, and " +"individual ~\n" +" ~ contributors as indicated by the @authors tag. See " +"the ~\n" +" ~ copyright.txt in the distribution for a full listing " +"of ~\n" +" ~ individual " +"contributors. ~\n" +" ~ " +"~\n" +" ~ This is free software; you can redistribute it and/or modify " +"it ~\n" +" ~ under the terms of the GNU Lesser General Public License " +"as ~\n" +" ~ published by the Free Software Foundation; either version 2.1 " +"of ~\n" +" ~ the License, or (at your option) any later " +"version. ~\n" +" ~ " +"~\n" +" ~ This software is distributed in the hope that it will be " +"useful, ~\n" +" ~ but WITHOUT ANY WARRANTY; without even the implied warranty " +"of ~\n" +" ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the " +"GNU ~\n" +" ~ Lesser General Public License for more " +"details. ~\n" +" ~ " +"~\n" +" ~ You should have received a copy of the GNU Lesser General " +"Public ~\n" +" ~ License along with this software; if not, write to the " +"Free ~\n" +" ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, " +"MA ~\n" +" ~ 02110-1301 USA, or see the FSF site: http://www.fsf." +"org. ~\n" +" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~--" +">\n" +"\n" +"<!--\n" +"<!DOCTYPE deployments PUBLIC\n" +" \"-//JBoss Portal//DTD Portal Object 2.6//EN\"\n" +" \"http://www.jboss.org/portal/dtd/portal-object_2_6.dtd\">\n" +"-->\n" +"\n" +"<!--\n" +"The deployements element is a generic container for deployment elements.\n" +"-->\n" +"<!ELEMENT deployments (deployment*)>\n" +"\n" +"<!--\n" +"The deployment is a generic container for portal object elements. The parent-" +"ref\n" +"child gives the name of the parent object that the current object will use " +"as parent.\n" +"The optional if-exists element define the behavior when a portal object " +"which\n" +"an identical name is already child of the parent element. The default " +"behavior of\n" +"the if-exist tag is to keep the existing object and not create a new object. " +"The\n" +"last element is the portal object itself.\n" +"\n" +"Example:\n" +"\n" +"<deployment>\n" +" <parent-ref>default</parent-ref>\n" +" <page>\n" +" ...\n" +" </page>\n" +"</deployment>\n" +"\n" +"All portal objects have a common configuration which can be :\n" +"\n" +"1/ a listener : specifies the id of a listener is the listener registry. A " +"listener\n" +"object is able to listen portal events which apply to the portal node " +"hierarchy.\n" +"\n" +"2/ properties : a set of generic properties owned by the portal object. " +"Some\n" +"properties can drive the behavior of the object.\n" +"\n" +"3/ security-constraint : defines security configuration of the portal " +"object.\n" +"\n" +"-->\n" +"<!ELEMENT deployment (parent-ref?,if-exists?,(context|portal|page|window))>\n" +"\n" +"<!--\n" +"Contains a reference to the parent object. The naming convention for naming " +"object\n" +"is to concatenate the names of the path to the object and separate the names " +"by a dot.\n" +"If the path is empty then the empty string must be used.\n" +"\n" +"Example:\n" +"\n" +"<parent-ref/> the root having an empty path\n" +"\n" +"<parent-ref>default</parent-ref> the object with the name default under the " +"root\n" +"having the path (default)\n" +"\n" +"<parent-ref>default.default</parent-ref> the object with the path (default," +"default)\n" +"\n" +"-->\n" +"<!ELEMENT parent-ref (#PCDATA)>\n" +"\n" +"<!--\n" +"The authorized values are overwrite and keep. Overwrite means that the " +"existing\n" +"object will be destroyed and the current declaration will be used. Keep " +"means that\n" +"the existing object will not be destroyed and no creation hence will be " +"done.\n" +"-->\n" +"<!ELEMENT if-exists (#PCDATA)>\n" +"\n" +"<!--\n" +"A portal object of type context. A context type represent a node in the tree " +"which\n" +"does not have a visual representation. It can exist only under the root. A " +"context can\n" +"only have children with the portal type.\n" +"-->\n" +"<!ELEMENT context (context-name,properties?,listener?,security-constraint?," +"portal*,\n" +" (display-name* | (resource-bundle, supported-locale+)))>\n" +"\n" +"<!--\n" +"The context name value.\n" +"-->\n" +"<!ELEMENT context-name (#PCDATA)>\n" +"\n" +"<!--\n" +"A portal object of type portal. A portal type represents a virtual portal " +"and can\n" +"have children of type page. In addition of the common portal object elements " +"it support\n" +"also the declaration of the modes and the window states it supports. If no " +"declaration\n" +"of modes or window states is done then the default value will be " +"respectively\n" +"(view,edit,help) and (normal,minimized,maximized).\n" +"-->\n" +"<!ELEMENT portal (portal-name,supported-modes,supported-window-states?," +"properties?,\n" +" listener?,security-constraint?,page*, \n" +" (display-name* | (resource-bundle, supported-locale+)))>\n" +"\n" +"<!--\n" +"The portal name value.\n" +"-->\n" +"<!ELEMENT portal-name (#PCDATA)>\n" +"\n" +"\n" +"<!--\n" +"The supported modes of a portal.\n" +"\n" +"Example:\n" +"\n" +"<supported-mode>\n" +" <mode>view</mode>\n" +" <mode>edit</mode>\n" +" <mode>help</mode>\n" +"</supported-mode>\n" +"-->\n" +"<!ELEMENT supported-modes (mode*)>\n" +"\n" +"<!--\n" +"A portlet mode value.\n" +"-->\n" +"<!ELEMENT mode (#PCDATA)>\n" +"\n" +"<!--\n" +"The supported window states of a portal.\n" +"\n" +"Example:\n" +"\n" +"<supported-window-states>\n" +" <window-state>normal</window-state>\n" +" <window-state>minimized</window-state>\n" +" <window-state>maximized</window-state>\n" +"</supported-window-states>\n" +"\n" +"-->\n" +"<!ELEMENT supported-window-states (window-state*)>\n" +"\n" +"<!--\n" +"A window state value.\n" +"-->\n" +"<!ELEMENT window-state (#PCDATA)>\n" +"\n" +"<!--\n" +"A portal object of type page. A page type represents a page which can have " +"children of\n" +"type page and window. The children windows are the windows of the page and " +"the children\n" +"pages are the subpages of this page.\n" +"-->\n" +"<!ELEMENT page (page-name,properties?,listener?,security-constraint?,(page|" +"window)*,\n" +" (display-name* | (resource-bundle, supported-locale+)))>\n" +"\n" +"<!ELEMENT display-name (#PCDATA)>\n" +"<!ATTLIST display-name\n" +" xml:lang NMTOKEN #IMPLIED\n" +">\n" +"\n" +"<!ELEMENT resource-bundle (#PCDATA)>\n" +"\n" +"<!ELEMENT supported-locale (#PCDATA)>\n" +"\n" +"<!--\n" +"The page name value.\n" +"-->\n" +"<!ELEMENT page-name (#PCDATA)>\n" +"\n" +"<!--\n" +"A portal object of type window. A window type represents a window. Beside " +"the common\n" +"properties a window has a content and belong to a region on the page.\n" +"\n" +"The instance-ref or content tags are used to define the content of the " +"window. The\n" +"usage of the content tag is generic and can be used to describe any kind of " +"content.\n" +"The instance-ref is a shortcut to define a content type of portlet which " +"points to a\n" +"portlet instance.\n" +"\n" +"The region and height defines how the window is placed in the page.\n" +"-->\n" +"<!ELEMENT window (window-name,(instance-ref|content),region,height,\n" +" initial-window-state?,initial-mode?,properties?,listener?,\n" +" (display-name* | (resource-bundle, supported-locale+)))>\n" +"\n" +"<!--\n" +"The window name value.\n" +"-->\n" +"<!ELEMENT window-name (#PCDATA)>\n" +"\n" +"<!--\n" +"Define the content of the window as a reference to a portlet instance. The " +"value\n" +"is the id of the instance.\n" +"\n" +"Example:\n" +"\n" +"<instance-ref>MyPortletInstance</instance-ref>\n" +"\n" +"-->\n" +"<!ELEMENT instance-ref (#PCDATA)>\n" +"\n" +"<!--\n" +"Define the content of the window in a generic manner. The content is define " +"by\n" +"the type of the content and an URI which acts as an identificator for the " +"content.\n" +"\n" +"Example:\n" +"\n" +"<content>\n" +" <content-type>portlet</content-type>\n" +" <content-uri>MyPortletInstance</content-uri>\n" +"</content>\n" +"\n" +"<content>\n" +" <content-type>cms</content-type>\n" +" <content-uri>/default/index.html</content-uri>\n" +"</content>\n" +"\n" +"-->\n" +"<!ELEMENT content (content-type,content-uri)>\n" +"\n" +"<!--\n" +"The content type of the window.\n" +"-->\n" +"<!ELEMENT content-type (#PCDATA)>\n" +"\n" +"<!--\n" +"The content URI of the window.\n" +"-->\n" +"<!ELEMENT content-uri (#PCDATA)>\n" +"\n" +"<!--\n" +"The region the window belongs to.\n" +"-->\n" +"<!ELEMENT region (#PCDATA)>\n" +"\n" +"<!--\n" +"The window state to use when the window is first accessed\n" +"-->\n" +"<!ELEMENT initial-window-state (#PCDATA)>\n" +"\n" +"<!--\n" +"The mode to use when the window is first accessed\n" +"-->\n" +"<!ELEMENT initial-mode (#PCDATA)>\n" +"\n" +"<!--\n" +"The height of the window in the particular region.\n" +"-->\n" +"<!ELEMENT height (#PCDATA)>\n" +"\n" +"<!--\n" +"Define a listener for a portal object. The value is the id of the listener.\n" +"-->\n" +"<!ELEMENT listener (#PCDATA)>\n" +"\n" +"<!--\n" +"A set of generic properties for the portal object.\n" +"-->\n" +"<!ELEMENT properties (property*)>\n" +"\n" +"<!--\n" +"A generic string property.\n" +"-->\n" +"<!ELEMENT property (name,value)>\n" +"\n" +"<!--\n" +"A name value.\n" +"-->\n" +"<!ELEMENT name (#PCDATA)>\n" +"\n" +"<!--\n" +"A value.\n" +"-->\n" +"<!ELEMENT value (#PCDATA)>\n" +"\n" +"<!--\n" +"The security-constraint element is a container for policy-permission " +"elements\n" +"\n" +"Examples:\n" +"\n" +"<security-constraint>\n" +" <policy-permission>\n" +" <role-name>User</role-name>\n" +" <action-name>view</action-name>\n" +" </policy-permission>\n" +"</security-constraint>\n" +"\n" +"<security-constraint>\n" +" <policy-permission>\n" +" <unchecked/>\n" +" <action-name>view</action-name>\n" +" </policy-permission>\n" +"</security-constraint>\n" +"-->\n" +"<!ELEMENT security-constraint (policy-permission*)>\n" +"\n" +"<!--\n" +"The policy-permission element is used to secure a specific portal page based " +"on a\n" +"user's role.\n" +"-->\n" +"<!ELEMENT policy-permission (action-name*,unchecked?,role-name*)>\n" +"\n" +"<!--\n" +"The role-name element is used to define a role that this security constraint " +"will apply to\n" +"\n" +" * <role-name>SOMEROLE</role-name> Access to this portal page is limited " +"to the defined role.\n" +"-->\n" +"<!ELEMENT action-name (#PCDATA)>\n" +"\n" +"<!--\n" +"The unchecked element is used to define (if present) that anyone can view " +"this portal page\n" +"-->\n" +"<!ELEMENT unchecked EMPTY>\n" +"\n" +"<!--\n" +"The action-name element is used to define the access rights given to the " +"role defined.\n" +"Possible values are:\n" +"\n" +" * view - Users can view the page.\n" +"-->\n" +"<!ELEMENT role-name (#PCDATA)>\n" +"\n" +" \n" +"]]>" +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Portlet_Instances_DTD.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Portlet_Instances_DTD.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Portlet_Instances_DTD.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,246 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Portlet_Instances_DTD.xml:7 +#, no-c-format +msgid "portlet-instances.xml DTD" +msgstr "" + +#. Tag: programlisting +#: Portlet_Instances_DTD.xml:9 +#, no-c-format +msgid "" +"<![CDATA[\n" +"\n" +" <?xml version=\"1.0\" encoding=\"UTF-8\" ?>\n" +"\n" +"<!--" +"~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n" +" ~ JBoss, a division of Red " +"Hat ~\n" +" ~ Copyright 2006, Red Hat Middleware, LLC, and " +"individual ~\n" +" ~ contributors as indicated by the @authors tag. See " +"the ~\n" +" ~ copyright.txt in the distribution for a full listing " +"of ~\n" +" ~ individual " +"contributors. ~\n" +" ~ " +"~\n" +" ~ This is free software; you can redistribute it and/or modify " +"it ~\n" +" ~ under the terms of the GNU Lesser General Public License " +"as ~\n" +" ~ published by the Free Software Foundation; either version 2.1 " +"of ~\n" +" ~ the License, or (at your option) any later " +"version. ~\n" +" ~ " +"~\n" +" ~ This software is distributed in the hope that it will be " +"useful, ~\n" +" ~ but WITHOUT ANY WARRANTY; without even the implied warranty " +"of ~\n" +" ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the " +"GNU ~\n" +" ~ Lesser General Public License for more " +"details. ~\n" +" ~ " +"~\n" +" ~ You should have received a copy of the GNU Lesser General " +"Public ~\n" +" ~ License along with this software; if not, write to the " +"Free ~\n" +" ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, " +"MA ~\n" +" ~ 02110-1301 USA, or see the FSF site: http://www.fsf." +"org. ~\n" +" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~--" +">\n" +"\n" +"<!--\n" +"<!DOCTYPE deployments PUBLIC\n" +" \"-//JBoss Portal//DTD Portlet Instances 2.6//EN\"\n" +" \"http://www.jboss.org/portal/dtd/portlet-instances_2_6.dtd\">\n" +"-->\n" +"\n" +"<!--\n" +"The deployements element is a container for deployment elements.\n" +"-->\n" +"<!ELEMENT deployments (deployment*)>\n" +"\n" +"<!--\n" +"The deployment is a container for an instance element.\n" +"-->\n" +"<!ELEMENT deployment (if-exists?,instance)>\n" +"\n" +"<!--\n" +"The if-exists element is used to define action to take if instance with such " +"name is\n" +"already present. Possible values are overwrite or keep . Overwrite will " +"destroy the\n" +"existing object in the database and create a new one, based on the content " +"of the\n" +"deployment. Keep will maintain the existing object deployment or create a " +"new one if\n" +"it does not yet exist.\n" +"-->\n" +"<!ELEMENT if-exists (#PCDATA)>\n" +"\n" +"<!--\n" +"The instance element is used to create an instance of a portlet from the " +"portlet\n" +"application of the same war file containing the portlet-instances.xml file. " +"The portlet\n" +"will be created and configured only if the portlet is present and an " +"instance with\n" +"such a name does not already exist.\n" +"\n" +"Example :\n" +"\n" +"<instance>\n" +" <instance-id>MyPortletInstance</instance-id>\n" +" <portlet-ref>MyPortlet</portlet-ref>\n" +" <preferences>\n" +" <preference>\n" +" <name>abc</name>\n" +" <value>def</value>\n" +" </preference>\n" +" </preferences>\n" +" <security-constraint>\n" +" <policy-permission>\n" +" <role-name>User</role-name>\n" +" <action-name>view</action-name>\n" +" </policy-permission>\n" +" </security-constraint>\n" +"</instance>\n" +"\n" +"-->\n" +"<!ELEMENT instance (instance-id,portlet-ref,display-name*,preferences?,\n" +" security-constraint?, (display-name* | (resource-bundle, supported-" +"locale+)))>\n" +"\n" +"<!ELEMENT display-name (#PCDATA)>\n" +"<!ATTLIST display-name\n" +" xml:lang NMTOKEN #IMPLIED\n" +">\n" +"\n" +"<!ELEMENT resource-bundle (#PCDATA)>\n" +"\n" +"<!ELEMENT supported-locale (#PCDATA)>\n" +"\n" +"\n" +"<!--\n" +"The identifier of the instance.\n" +"-->\n" +"<!ELEMENT instance-id (#PCDATA)>\n" +"\n" +"<!--\n" +"The reference to the portlet which is its portlet name.\n" +"-->\n" +"<!ELEMENT portlet-ref (#PCDATA)>\n" +"\n" +"<!--\n" +"Display name is the string used to represent this instance\n" +"-->\n" +"<!ELEMENT display-name (#PCDATA)>\n" +"<!ATTLIST display-name\n" +" xml:lang NMTOKEN #IMPLIED\n" +">\n" +"\n" +"<!--\n" +"The preferences element configures the instance with a specific set of " +"preferences.\n" +"-->\n" +"<!ELEMENT preferences (preference+)>\n" +"\n" +"<!--\n" +"The preference configure one preference of a set of preferences.\n" +"-->\n" +"<!ELEMENT preference (name,value)>\n" +"\n" +"<!--\n" +"A name.\n" +"-->\n" +"<!ELEMENT name (#PCDATA)>\n" +"\n" +"<!--\n" +"A string value.\n" +"-->\n" +"<!ELEMENT value (#PCDATA)>\n" +"\n" +"<!--\n" +"The security-constraint element is a container for policy-permission " +"elements\n" +"\n" +"Examples:\n" +"\n" +"<security-constraint>\n" +" <policy-permission>\n" +" <role-name>User</role-name>\n" +" <action-name>view</action-name>\n" +" </policy-permission>\n" +"</security-constraint>\n" +"\n" +"<security-constraint>\n" +" <policy-permission>\n" +" <unchecked/>\n" +" <action-name>view</action-name>\n" +" </policy-permission>\n" +"</security-constraint>\n" +"-->\n" +"<!ELEMENT security-constraint (policy-permission*)>\n" +"\n" +"<!--\n" +"The policy-permission element is used to secure a specific portlet instance " +"based on a\n" +"user's role.\n" +"-->\n" +"<!ELEMENT policy-permission (action-name*,unchecked?,role-name*)>\n" +"\n" +"<!--\n" +"The action-name element is used to define the access rights given to the " +"role defined.\n" +"Possible values are:\n" +"\n" +" * view - Users can view the page.\n" +" * viewrecursive - Users can view the page and child pages.\n" +" * personalize - Users are able to view AND personalize the page.\n" +" * personalizerecursive - Users are able to view AND personalize the page " +"AND its child\n" +" pages.\n" +"-->\n" +"<!ELEMENT action-name (#PCDATA)>\n" +"\n" +"<!--\n" +"The unchecked element is used to define (if present) that anyone can view " +"this instance\n" +"-->\n" +"<!ELEMENT unchecked EMPTY>\n" +"\n" +"<!--\n" +"The role-name element is used to define a role that this security constraint " +"will apply to\n" +"\n" +" * <role-name>SOMEROLE</role-name> Access to this instance is limited to " +"the defined role.\n" +"-->\n" +"<!ELEMENT role-name (#PCDATA)>\n" +"\n" +" \n" +"]]>" +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Portlet_Modes.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Portlet_Modes.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Portlet_Modes.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,146 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Portlet_Modes.xml:12 +#, no-c-format +msgid "Portlet Modes" +msgstr "" + +#. Tag: para +#: Portlet_Modes.xml:13 +#, no-c-format +msgid "" +"JBoss Portal supports the standard portlet modes defined by the JSR-168 " +"specification which are <emphasis>view</emphasis>, <emphasis>edit</emphasis> " +"and <emphasis>help</emphasis>. In addition of that it also supports the " +"<emphasis>admin</emphasis> portlet mode." +msgstr "" + +#. Tag: title +#: Portlet_Modes.xml:18 +#, no-c-format +msgid "Admin Portlet Mode" +msgstr "" + +#. Tag: para +#: Portlet_Modes.xml:19 +#, no-c-format +msgid "" +"The admin mode defines a mode for the portlet which allows the " +"administration of the portlet. Access to this mode is only granted to users " +"having an appropriate role. In order to grant admin access to a portlet, the " +"user must have a role which grants him the <emphasis>admin</emphasis> action " +"permission on the portlet instance. This can be done in the instance " +"deployment descriptor or using the administation portlet of the portal." +msgstr "" + +#. Tag: title +#: Portlet_Modes.xml:24 +#, no-c-format +msgid "Portlet configuration" +msgstr "" + +#. Tag: para +#: Portlet_Modes.xml:25 +#, no-c-format +msgid "" +"In order to be able to use the admin mode, the portlet must declare it in " +"the portlet deployment descriptor." +msgstr "" + +#. Tag: programlisting +#: Portlet_Modes.xml:26 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<portlet-app>\n" +" ...\n" +" <portlet>\n" +" ...\n" +" <supports>\n" +" <mime-type>text/html</mime-type>\n" +" <portlet-mode>admin</portlet-mode>\n" +" </supports>\n" +" ...\n" +" </portlet>\n" +" ...\n" +" <custom-portlet-mode>\n" +" <name>admin</name>\n" +" </custom-portlet-mode>\n" +" ...\n" +"</portlet-app>\n" +"]]>" +msgstr "" + +#. Tag: title +#: Portlet_Modes.xml:29 +#, no-c-format +msgid "Declarative instance security configuration" +msgstr "" + +#. Tag: para +#: Portlet_Modes.xml:30 +#, no-c-format +msgid "" +"The following example shows the configuration of a portlet instance that " +"grants the admin action permission to the <emphasis>Admin</emphasis> " +"security role. It also grants the view action permission to all users." +msgstr "" + +#. Tag: programlisting +#: Portlet_Modes.xml:33 +#, no-c-format +msgid "" +"<![CDATA[\n" +"...\n" +"<instance>\n" +" <instance-id>ModePortletInstance</instance-id>\n" +" <portlet-ref>ModePortlet</portlet-ref>\n" +" <security-constraint>\n" +" <policy-permission>\n" +" <action-name>admin</action-name>\n" +" <role-name>Admin</role-name>\n" +" </policy-permission>\n" +" <policy-permission>\n" +" <action-name>view</action-name>\n" +" <unchecked/>\n" +" </policy-permission>\n" +" </security-constraint>\n" +"</instance>\n" +"...\n" +"]]>" +msgstr "" + +#. Tag: title +#: Portlet_Modes.xml:36 +#, no-c-format +msgid "Instance security configuration with the administration portlet" +msgstr "" + +#. Tag: para +#: Portlet_Modes.xml:37 +#, no-c-format +msgid "" +"At runtime the security configuration section of the administration portlet " +"can be used to grant or revoke the admin access. It can be done by clicking " +"the security action of the portlet instance and then use the security editor." +msgstr "" + +#. Tag: para +#: Portlet_Modes.xml:45 +#, no-c-format +msgid "Edit the security instance configuration" +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Preface.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Preface.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Preface.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,20 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Preface.xml:6 +#, no-c-format +msgid "Preface" +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Reference_Guide.po =================================================================== Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Revision_History.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Revision_History.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Revision_History.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,26 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Revision_History.xml:6 +#, no-c-format +msgid "Revision History" +msgstr "" + +#. Tag: author +#: Revision_History.xml:12 +#, no-c-format +msgid "<firstname></firstname> <surname></surname> <email></email>" +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/SSO.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/SSO.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/SSO.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,968 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: SSO.xml:16 +#, no-c-format +msgid "Single Sign On" +msgstr "" + +#. Tag: para +#: SSO.xml:17 +#, no-c-format +msgid "This chapter describes how to setup SSO in JBoss Portal" +msgstr "" + +#. Tag: title +#: SSO.xml:19 +#, no-c-format +msgid "Overview of SSO in portal" +msgstr "" + +#. Tag: para +#: SSO.xml:20 +#, no-c-format +msgid "" +"Portal as an integration and aggregation platform provides some form of SSO " +"by itself. When you log into the portal you gain access to many systems " +"through portlets using a single identity. Still in many cases you need to " +"integrate the portal infrastructure with other SSO enabled systems. There " +"are many different Identity Management solutions on the market. In most " +"cases each SSO framework provides its own way to plug into Java EE " +"application. For custom configurations you need to have a good understanding " +"of <xref linkend=\"identity\"/> and <xref linkend=\"authentication\"/> " +"authentication mechanisms." +msgstr "" + +#. Tag: title +#: SSO.xml:29 +#, no-c-format +msgid "Using an Apache Tomcat Valve" +msgstr "" + +#. Tag: para +#: SSO.xml:30 +#, no-c-format +msgid "" +"JBoss Application Server embeds Apache Tomcat as the default servlet " +"container. Tomcat provides a builtin SSO support using a valve. The Single " +"Sign On Valve caches credentials on the server side, and then invisibly " +"authenticate users when they reach different web applications. Credentials " +"are stored in a host-wide session which means that SSO will be effective " +"throughout the session." +msgstr "" + +#. Tag: title +#: SSO.xml:35 +#, no-c-format +msgid "Enabling the Apache Tomcat SSO Valve" +msgstr "" + +#. Tag: para +#: SSO.xml:36 +#, no-c-format +msgid "" +"To enable SSO valve in Apache Tomcat you should uncomment the following line " +"<programlisting><![CDATA[<Valve className=’org.apache.catalina.authenticator." +"SingleSignOn’/>]]></programlisting> in the <literal>$JBOSS_HOME/server/" +"default/deploy/jboss-web.deployer/server.xml</literal> file. More " +"information can be found <ulink url=\"http://www.jboss.org/wiki/Wiki.jsp?" +"page=SingleSignOn\">here</ulink>." +msgstr "" + +#. Tag: title +#: SSO.xml:44 +#, no-c-format +msgid "Example of usage" +msgstr "" + +#. Tag: para +#: SSO.xml:45 +#, no-c-format +msgid "" +"Lets look a little bit closer and configure SSO between portal and other web " +"application. As an example we'll use <emphasis>jmx-console</emphasis> web-" +"app that comes with every JBoss Application Server installation. You can " +"find more information on how to secure <emphasis>jmx-console</emphasis> in " +"<ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=SecureTheJmxConsole&q... +"\">JBoss AS wiki</ulink>." +msgstr "" + +#. Tag: para +#: SSO.xml:53 +#, no-c-format +msgid "Take a clean install of <emphasis>JBoss Application Server</emphasis>" +msgstr "" + +#. Tag: para +#: SSO.xml:56 +#, no-c-format +msgid "" +"Edit <emphasis>$JBOSS_HOME/server/default/deploy/jmx-console.war/WEB-INF/web." +"xml</emphasis> file and make sure it contains following content:" +msgstr "" + +#. Tag: programlisting +#: SSO.xml:57 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<security-constraint>\n" +" <web-resource-collection>\n" +" <web-resource-name>HtmlAdaptor</web-resource-name>\n" +" <description>An example security config that only allows users with the\n" +" role JBossAdmin to access the HTML JMX console web application\n" +" </description>\n" +" <url-pattern>/*</url-pattern>\n" +" <http-method>GET</http-method>\n" +" <http-method>POST</http-method>\n" +" </web-resource-collection>\n" +" <auth-constraint>\n" +" <role-name>Admin</role-name>\n" +" </auth-constraint>\n" +"</security-constraint>\n" +"\n" +"<security-constraint>\n" +" <web-resource-collection>\n" +" <web-resource-name>Public</web-resource-name>\n" +" <url-pattern>/public/*</url-pattern>\n" +" <http-method>GET</http-method>\n" +" <http-method>POST</http-method>\n" +" </web-resource-collection>\n" +"</security-constraint>\n" +"\n" +"<login-config>\n" +" <auth-method>BASIC</auth-method>\n" +" <realm-name>jmx-console</realm-name>\n" +"</login-config>\n" +"\n" +"<security-role>\n" +" <role-name>Admin</role-name>\n" +"</security-role>]]>" +msgstr "" + +#. Tag: para +#: SSO.xml:58 +#, no-c-format +msgid "" +"This will secure <emphasis>jmx-console</emphasis> web application using " +"BASIC browser authentication and restrict access for users with " +"<emphasis>Admin</emphasis> role only." +msgstr "" + +#. Tag: para +#: SSO.xml:62 +#, no-c-format +msgid "" +"Edit <emphasis>$JBOSS_HOME/server/default/conf/props/jmx-console-roles." +"properties</emphasis> file and make it contain: <programlisting>\n" +" <![CDATA[\n" +"admin=JBossAdmin,HttpInvoker,Admin]]>\n" +" </programlisting> This file is a simple identity store for " +"this web application authentication. It will make user <emphasis>admin</" +"emphasis> belongs to <emphasis>Admin</emphasis> role." +msgstr "" + +#. Tag: para +#: SSO.xml:71 +#, no-c-format +msgid "Deploy JBoss Portal" +msgstr "" + +#. Tag: para +#: SSO.xml:74 +#, no-c-format +msgid "Run JBoss Application Server" +msgstr "" + +#. Tag: para +#: SSO.xml:77 +#, no-c-format +msgid "" +"Now you can check that when you go to <itemizedlist> <listitem><para> " +"<emphasis>http://localhost:8080/portal</emphasis></para> </listitem> " +"<listitem> <para> <emphasis>http://localhost:8080/jmx-console</emphasis></" +"para> </listitem> </itemizedlist> you need to authenticate separately into " +"each of those web applications." +msgstr "" + +#. Tag: para +#: SSO.xml:90 +#, no-c-format +msgid "Shutdown Application Server" +msgstr "" + +#. Tag: para +#: SSO.xml:93 +#, no-c-format +msgid "" +"Uncomment the following line <programlisting><![CDATA[<Valve className=’org." +"apache.catalina.authenticator.SingleSignOn’/>]]></programlisting> in the " +"<literal>$JBOSS_HOME/server/default/deploy/jboss-web.deployer/server.xml</" +"literal> file. More information can be found <ulink url=\"http://www.jboss." +"org/wiki/Wiki.jsp?page=SingleSignOn\">here</ulink>." +msgstr "" + +#. Tag: para +#: SSO.xml:100 +#, no-c-format +msgid "Run JBoss Application Server." +msgstr "" + +#. Tag: para +#: SSO.xml:105 +#, no-c-format +msgid "" +"Now if you log into portal as user <emphasis>admin</emphasis> with password " +"<emphasis>admin</emphasis>, you won't be asked for credentials when " +"accessing <emphasis>jmx-console</emphasis>. This should work in both " +"directions." +msgstr "" + +#. Tag: title +#: SSO.xml:109 SSO.xml:120 SSO.xml:124 SSO.xml:151 SSO.xml:157 SSO.xml:197 +#: SSO.xml:201 +#, no-c-format +msgid "Note" +msgstr "" + +#. Tag: para +#: SSO.xml:109 +#, no-c-format +msgid "" +"Please note that in this example <emphasis>jmx-console</emphasis> uses " +"<emphasis>BASIC</emphasis> authentication method. This means that user " +"credentials are cached on the client side by browser and passed on each " +"request. Once authenticated to clear authentication cache you may need to " +"restart browser." +msgstr "" + +#. Tag: title +#: SSO.xml:115 +#, no-c-format +msgid "CAS - Central Authentication Service" +msgstr "" + +#. Tag: para +#: SSO.xml:116 +#, no-c-format +msgid "" +"This Single Sign On plugin enables seamless integration between JBoss Portal " +"and the CAS Single Sign On Framework. Details about CAS can be found <ulink " +"url=\"http://www.ja-sig.org/products/cas/\">here</ulink>" +msgstr "" + +#. Tag: title +#: SSO.xml:119 SSO.xml:205 +#, no-c-format +msgid "Integration steps" +msgstr "" + +#. Tag: para +#: SSO.xml:120 +#, no-c-format +msgid "" +"The steps below assume that CAS server and JBoss Portal will be deployed on " +"the same JBoss Application Server instance. CAS will be configured to " +"leverage identity services exposed by JBoss Portal to perform " +"authentication. Procedure may be slightly different for other deployment " +"scenarios. Both JBoss Portal and CAS will need to be configured to " +"authenticate against same database or LDAP server. Please see CAS " +"documentation to learn how to setup it up against proper identity store." +msgstr "" + +#. Tag: para +#: SSO.xml:124 +#, no-c-format +msgid "" +"Configuration below assumes that JBoss Application Server is HTTPS enabled " +"and operates on standard ports: 80 (for HTTP) and 443 (for HTTPS)." +msgstr "" + +#. Tag: para +#: SSO.xml:128 +#, no-c-format +msgid "" +"Install CAS server (v 3.0.7). This should be as simple as deploying single " +"<emphasis>cas.war</emphasis> file." +msgstr "" + +#. Tag: para +#: SSO.xml:131 +#, no-c-format +msgid "" +"Copy <emphasis>portal-identity-lib.jar</emphasis> and <emphasis>portal-" +"identity-sso-lib.jar</emphasis> files from <emphasis>$JBOSS_HOME/server/" +"default/deploy/jboss-portal.sar/lib</emphasis> to <emphasis>$JBOSS_HOME/" +"server/default/deploy/cas.war/WEB-INF/lib</emphasis>." +msgstr "" + +#. Tag: para +#: SSO.xml:136 +#, no-c-format +msgid "" +"Edit <emphasis>$JBOSS_HOME/server/default/deploy/jboss-portal.sar/portal-" +"server.war/WEB-INF/context.xml</emphasis> file and enable proper Apache " +"Tomcat Valve by uncommenting following lines: <programlisting>\n" +" <![CDATA[\n" +"<Valve className=\"org.jboss.portal.identity.sso.cas.CASAuthenticationValve" +"\"\n" +" casLogin=\"https://localhost/cas/login\"\n" +" casValidate=\"https://localhost/cas/serviceValidate\"\n" +" casServerName=\"localhost\"\n" +" authType=\"FORM\"\n" +"/>\n" +" ]]>\n" +" </programlisting> Update valve options as follow:" +msgstr "" + +#. Tag: para +#: SSO.xml:142 +#, no-c-format +msgid "<emphasis>casLogin: </emphasis> URL of your CAS Authentication Server" +msgstr "" + +#. Tag: para +#: SSO.xml:145 +#, no-c-format +msgid "" +"<emphasis>casValidate: </emphasis> URL of your CAS Authentication Server " +"validation service" +msgstr "" + +#. Tag: para +#: SSO.xml:148 +#, no-c-format +msgid "" +"<emphasis>casServerName:</emphasis> the hostname:port combination of your " +"CAS Authentication Server" +msgstr "" + +#. Tag: para +#: SSO.xml:151 +#, no-c-format +msgid "" +"CAS client requires to use SSL connection. To learn how to setup JBoss " +"Application Server to use HTTPS see here" +msgstr "" + +#. Tag: para +#: SSO.xml:155 +#, no-c-format +msgid "" +"Copy <emphasis>casclient.jar</emphasis> into <emphasis>$JBOSS_HOME/server/" +"default/deploy/jboss-portal.sar/lib</emphasis>. You can download this file " +"from CAS homepage or from JBoss repository under <emphasis>http://repository." +"jboss.com/cas/3.0.7/lib/</emphasis>" +msgstr "" + +#. Tag: para +#: SSO.xml:157 +#, no-c-format +msgid "" +"The CAS engine does not accept self-signed SSL certificates. This " +"requirement is fine for production use where a production level SSL " +"certificate is available. However, for testing purposes, this can get a " +"little annoying. Hence, if you are having this issue, you can use " +"<emphasis>casclient-lenient.jar</emphasis> instead." +msgstr "" + +#. Tag: para +#: SSO.xml:163 +#, no-c-format +msgid "" +"Edit <emphasis>$JBOSS_HOME/server/default/deploy/jboss-portal.sar/META-INF/" +"jboss-service.xml</emphasis> file and uncomment following lines: " +"<programlisting>\n" +" <![CDATA[\n" +"<mbean\n" +" code=\"org.jboss.portal.identity.sso.cas.CASAuthenticationService\"\n" +" name=\"portal:service=Module,type=CASAuthenticationService\"\n" +" xmbean-dd=\"\"\n" +" xmbean-code=\"org.jboss.portal.jems.as.system.JBossServiceModelMBean\">\n" +" <xmbean/>\n" +" <depends>portal:service=Module,type=IdentityServiceController</depends>\n" +" <attribute name=\"HavingRole\"></attribute>\n" +"</mbean>\n" +" ]]>\n" +" </programlisting> This will expose special service in JBoss " +"Portal that can be leveraged by CAS AuthenticationHandler if the server is " +"deployed on the same application server instance. This AuthenticationHandler " +"will be enabled in next 2 steps." +msgstr "" + +#. Tag: para +#: SSO.xml:169 +#, no-c-format +msgid "" +"Edit <emphasis>$JBOSS_HOME/server/default/deploy/cas.war/WEB-INF/" +"deployerConfigContext.xml</emphasis> and add following line in the " +"<emphasis>authenticationHandlers</emphasis> section: <programlisting>\n" +" <![CDATA[\n" +"<bean class=\"org.jboss.portal.identity.sso.cas.CASAuthenticationHandler\" /" +">\n" +" ]]>\n" +" </programlisting> This can replace default " +"<emphasis>SimpleTestUsernamePasswordAuthenticationHandler</emphasis> so " +"whole part of this config file can look as follows:" +msgstr "" + +#. Tag: programlisting +#: SSO.xml:175 +#, no-c-format +msgid "" +"<![CDATA[<property name=\"authenticationHandlers\">\n" +" <list>\n" +" <!--\n" +" | This is the authentication handler that authenticates services by " +"means of callback via SSL, thereby validating\n" +" | a server side SSL certificate.\n" +" +-->\n" +" <bean\n" +" class=\"org.jasig.cas.authentication.handler.support." +"HttpBasedServiceCredentialsAuthenticationHandler\">\n" +" <property\n" +" name=\"httpClient\"\n" +" ref=\"httpClient\" />\n" +" </bean>\n" +"\n" +" <!--\n" +" | This is the authentication handler declaration that every CAS " +"deployer will need to change before deploying CAS\n" +" | into production. The default " +"SimpleTestUsernamePasswordAuthenticationHandler authenticates " +"UsernamePasswordCredentials\n" +" | where the username equals the password. You will need to replace " +"this with an AuthenticationHandler that implements your\n" +" | local authentication strategy. You might accomplish this by coding a " +"new such handler and declaring\n" +" | edu.someschool.its.cas.MySpecialHandler here, or you might use one of " +"the handlers provided in the adaptors modules.\n" +" +-->\n" +" <bean class=\"org.jboss.portal.identity.sso.cas.CASAuthenticationHandler" +"\" />\n" +" </list>\n" +"</property>]]>" +msgstr "" + +#. Tag: para +#: SSO.xml:180 SSO.xml:287 +#, no-c-format +msgid "To test the integration:" +msgstr "" + +#. Tag: para +#: SSO.xml:183 SSO.xml:290 +#, no-c-format +msgid "Go to your portal. Typically, http://localhost:8080/portal" +msgstr "" + +#. Tag: para +#: SSO.xml:184 SSO.xml:291 +#, no-c-format +msgid "Click on the \"Login\" link on the main portal page" +msgstr "" + +#. Tag: para +#: SSO.xml:185 +#, no-c-format +msgid "" +"This should bring up the CAS Authentication Server's login screen instead of " +"the default JBoss Portal login screen" +msgstr "" + +#. Tag: para +#: SSO.xml:186 SSO.xml:293 +#, no-c-format +msgid "" +"Input your portal username and password. For built-in portal login try user:" +"user or admin:admin" +msgstr "" + +#. Tag: para +#: SSO.xml:187 SSO.xml:294 +#, no-c-format +msgid "" +"If login is successful, you should be redirected back to the portal with the " +"appropriate user logged in" +msgstr "" + +#. Tag: title +#: SSO.xml:194 +#, no-c-format +msgid "<trademark class=\"trade\">Java</trademark> Open Single Sign-On (JOSSO)" +msgstr "" + +#. Tag: para +#: SSO.xml:195 +#, no-c-format +msgid "" +"JBoss Portal enables seamless integration with JOSSO server version 1.8. " +"More details on JOSSO can be found <ulink url=\"http://www.josso.org/" +"\">here</ulink>" +msgstr "" + +#. Tag: para +#: SSO.xml:197 +#, no-c-format +msgid "" +"The steps below assume that JOSS server and JBoss Portal will be deployed on " +"the same JBoss Application Server instance. JOSSO will be configured to " +"leverage identity services exposed by JBoss Portal to perform " +"authentication. Procedure may be slightly different for other deployment " +"scenarios. Both JBoss Portal and JOSSO will need to be configured to " +"authenticate against same database or LDAP server. Please see JOSSO " +"documentation to learn how to setup it up against proper identity store." +msgstr "" + +#. Tag: para +#: SSO.xml:201 +#, no-c-format +msgid "" +"Configuration below assumes that JOSSO is already installed and deployed in " +"the JBoss Application Server. This involves adding proper jar files into the " +"classpath and altering several configuration files (adding Apache Tomcat " +"Valves, security realm and specific JOSSO configuration files). For JBoss " +"setup please refer to JOSSO <ulink url=\"http://www.josso.org/jboss4-howto." +"html\">documentation</ulink>" +msgstr "" + +#. Tag: para +#: SSO.xml:210 +#, no-c-format +msgid "" +"Copy <emphasis>portal-identity-lib.jar</emphasis> and <emphasis>portal-" +"identity-sso-lib.jar</emphasis> files from <emphasis>$JBOSS_HOME/server/" +"default/deploy/jboss-portal.sar/lib</emphasis> to <emphasis>$JBOSS_HOME/" +"server/default/deploy/josso.ear/josso.war/WEB-INF/lib</emphasis>." +msgstr "" + +#. Tag: para +#: SSO.xml:215 +#, no-c-format +msgid "" +"Edit <emphasis>$JBOSS_HOME/server/default/deploy/jboss-portal.sar/portal-" +"server.war/WEB-INF/context.xml</emphasis> file and enable proper Apache " +"Tomcat Valve by uncommenting following lines:" +msgstr "" + +#. Tag: programlisting +#: SSO.xml:217 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<Valve className=\"org.jboss.portal.identity.sso.josso.JOSSOLogoutValve\"/>\n" +" ]]>" +msgstr "" + +#. Tag: para +#: SSO.xml:220 +#, no-c-format +msgid "" +"Edit <emphasis>$JBOSS_HOME/server/default/config/josso-agent-config.xml</" +"emphasis> and mapping for portal web application: " +"<programlisting> \n" +" <![CDATA[\n" +".........\n" +"<configuration>\n" +" <agent:agent-configuration>\n" +" <agent:partner-apps>\n" +" <agent:partner-app id=\"jboss_portal\" context=\"/portal\"/" +">\n" +" </agent:partner-apps>\n" +" </agent:agent-configuration>\n" +"<configuration>\n" +"...........\n" +" ]]>\n" +" </programlisting> Complete config file can look as follows:" +msgstr "" + +#. Tag: programlisting +#: SSO.xml:223 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<?xml version=\"1.0\" encoding=\"UTF-8\" ?>\n" +"<!--\n" +" ~ JOSSO: Java Open Single Sign-On\n" +" ~\n" +" ~ Copyright 2004-2009, Atricore, Inc.\n" +" ~\n" +" ~ This is free software; you can redistribute it and/or modify it\n" +" ~ under the terms of the GNU Lesser General Public License as\n" +" ~ published by the Free Software Foundation; either version 2.1 of\n" +" ~ the License, or (at your option) any later version.\n" +" ~\n" +" ~ This software is distributed in the hope that it will be useful,\n" +" ~ but WITHOUT ANY WARRANTY; without even the implied warranty of\n" +" ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU\n" +" ~ Lesser General Public License for more details.\n" +" ~\n" +" ~ You should have received a copy of the GNU Lesser General Public\n" +" ~ License along with this software; if not, write to the Free\n" +" ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA\n" +" ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org.\n" +" ~\n" +" -->\n" +"\n" +"<s:beans xmlns:s=\"http://www.springframework.org/schema/beans\"\n" +" xmlns:jb42=\"urn:org:josso:agent:jboss42\"\n" +" xmlns:agent=\"urn:org:josso:agent:core\"\n" +" xmlns:protocol=\"urn:org:josso:protocol:client\"\n" +" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n" +" xsi:schemaLocation=\"http://www.springframework.org/schema/beans " +"http://www.springframework.org/schema/beans/spring-beans-2.5.xsd\n" +" urn:org:josso:agent:jboss42 http://www.josso.org/schema/josso-" +"jboss42-agent.xsd\n" +" urn:org:josso:agent:core http://www.josso.org/schema/josso-agent." +"xsd\n" +" urn:org:josso:protocol:client http://www.josso.org/schema/josso-" +"protocol-client.xsd\">\n" +"\n" +" <jb42:agent name=\"josso-jboss42-agent\" sessionAccessMinInterval=\"1000" +"\" >\n" +"\n" +" <!-- Gateway LOGIN and LOGOUT URLs -->\n" +" <gatewayLoginUrl>http://josso-01:8080/josso/signon/login.do</" +"gatewayLoginUrl>\n" +" <gatewayLogoutUrl>http://josso-01:8080/josso/signon/logout.do</" +"gatewayLogoutUrl>\n" +"\n" +" <!-- Gateway service locator -->\n" +" <gatewayServiceLocator>\n" +" <!-- Other properties for ws-service-locator :\n" +" username, password, servicesWebContext, transportSecurity\n" +" -->\n" +" <protocol:ws-service-locator endpoint=\"josso-01:8080\" />\n" +" </gatewayServiceLocator>\n" +"\n" +" <configuration>\n" +" <agent:agent-configuration>\n" +"\n" +" <!-- " +"============================================================================= " +"-->\n" +" <!-- " +"-->\n" +" <!-- JOSSO Parnter application " +"definicions : -->\n" +" <!-- " +"-->\n" +" <!-- Configure all web applications that should be a josso " +"partner application -->\n" +" <!-- within this " +"server. -->\n" +" <!-- For each partner application you have to define the " +"proper web-context. -->\n" +" <!-- " +"============================================================================= " +"-->\n" +" <agent:partner-apps>\n" +" <agent:partner-app id=\"jboss_portal\" context=\"/portal" +"\"/>\n" +"\n" +" </agent:partner-apps>\n" +" </agent:agent-configuration>\n" +" </configuration>\n" +" <!-- Only useful when configuring multiple security domains -->\n" +" <!-- You can configure your own parameter builder to send parameters " +"to your SecurityDomainMatcher -->\n" +" <!--\n" +" <parametersBuilders>\n" +" <agent:vhost-parameters-builder/>\n" +" <agent:appctx-parameters-builder/>\n" +" </parametersBuilders>\n" +" -->\n" +"\n" +" </jb42:agent>\n" +"\n" +"</s:beans>\n" +" ]]>" +msgstr "" + +#. Tag: para +#: SSO.xml:226 +#, no-c-format +msgid "" +"Edit <emphasis>$JBOSS_HOME/server/default/deploy/jboss-portal.sar/portal-" +"server.war/login.jsp</emphasis> and <emphasis>$JBOSS_HOME/server/default/" +"deploy/jboss-portal.sar/portal-server.war/erros.jsp</emphasis> and uncomment " +"following line: <programlisting>\n" +" <![CDATA[\n" +"<%\n" +" response.sendRedirect(request.getContextPath() + \"/josso_login/\");\n" +"%>\n" +" ]]>\n" +" </programlisting> (make sure to remove java style comment " +"'/* */' - not the xml one)." +msgstr "" + +#. Tag: para +#: SSO.xml:232 +#, no-c-format +msgid "" +"Edit <emphasis>$JBOSS_HOME/server/default/deploy/jboss-portal.sar/META-INF/" +"jboss-service.xml</emphasis> file and uncomment following lines: " +"<programlisting>\n" +" <![CDATA[\n" +"<mbean\n" +" code=\"org.jboss.portal.identity.sso.josso.JOSSOIdentityServiceImpl\"\n" +" name=\"portal:service=Module,type=JOSSOIdentityService\"\n" +" xmbean-dd=\"\"\n" +" xmbean-code=\"org.jboss.portal.jems.as.system.JBossServiceModelMBean\">\n" +" <xmbean/>\n" +" <depends>portal:service=Module,type=IdentityServiceController</depends>\n" +"</mbean>\n" +" ]]>\n" +" </programlisting> This will expose a special service in JBoss " +"Portal that can be leveraged by JOSSO Credential and Identity Stores if the " +"server is deployed on the same application server instance." +msgstr "" + +#. Tag: para +#: SSO.xml:238 +#, no-c-format +msgid "" +"Activate <emphasis>JAAS based Login Module</emphasis> by configuring the " +"following:" +msgstr "" + +#. Tag: emphasis +#: SSO.xml:243 +#, no-c-format +msgid "$JBOSS_HOME/server/default/deploy/conf/login-config.xml" +msgstr "" + +#. Tag: programlisting +#: SSO.xml:244 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<application-policy name=\"josso\"> \n" +" <authentication>\n" +" <login-module code=\"org.jboss.portal.identity.sso.josso." +"JOSSOLoginModule\" flag=\"required\">\n" +" <module-option name=\"debug\">true</module-option>\n" +" </login-module>\n" +" </authentication>\n" +"</application-policy>\n" +" ]]>" +msgstr "" + +#. Tag: emphasis +#: SSO.xml:248 +#, no-c-format +msgid "" +"$JBOSS_HOME/server/default/deploy/jboss-portal.sar/portal-server.war/WEB-INF/" +"jboss-web.xml" +msgstr "" + +#. Tag: programlisting +#: SSO.xml:249 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<jboss-web>\n" +"<security-domain>java:jaas/josso</security-domain>\n" +".........\n" +" ]]>" +msgstr "" + +#. Tag: para +#: SSO.xml:256 +#, no-c-format +msgid "" +"Register the JBoss Portal Identity and Credential Store by configuring the " +"following:" +msgstr "" + +#. Tag: para +#: SSO.xml:259 +#, no-c-format +msgid "" +"Add the file<emphasis>$JBOSS_HOME/server/default/deploy/conf/josso-gateway-" +"portal-stores.xml</emphasis>" +msgstr "" + +#. Tag: programlisting +#: SSO.xml:260 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<s:beans xmlns:s=\"http://www.springframework.org/schema/beans\"\n" +" xmlns:portal-istore=\"urn:org:jboss:portal:josso:identitystore\"\n" +" xmlns:memory-sstore=\"urn:org:josso:memory:sessionstore\"\n" +" xmlns:memory-astore=\"urn:org:josso:memory:assertionstore\"\n" +" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n" +" xsi:schemaLocation=\"\n" +" http://www.springframework.org/schema/beans http://www." +"springframework.org/schema/beans/spring-beans-2.5.xsd \n" +" urn:org:josso:memory:sessionstore http://www.josso.org/schema/josso-" +"memory-sessionstore.xsd\n" +" urn:org:josso:memory:assertionstore http://www.josso.org/schema/" +"josso-memory-assertionstore.xsd\n" +" \">\n" +" <!-- " +"===================================================================== -->\n" +" <!-- JOSSO Identity Store, the id is very important because it " +"is -->\n" +" <!-- referenced by the identity manager, auth schemes and who knows " +"where -->\n" +" <!-- " +"else. -->\n" +" <!-- " +"===================================================================== -->\n" +" <portal-istore:portal-store id=\"josso-identity-store\" s:scope=" +"\"singleton\"/> \n" +"\n" +" <!-- " +"===================================================================== -->\n" +" <!-- JOSSO Session Store, the id is very important because it " +"is -->\n" +" <!-- referenced by the session manager and who knows where " +"else -->\n" +" <!-- " +"===================================================================== -->\n" +" <memory-sstore:memory-store id=\"josso-session-store\"/>\n" +"\n" +" <!-- " +"===================================================================== -->\n" +" <!-- JOSSO Assertion Store, the id is very important because it " +"is -->\n" +" <!-- referenced by the assertion manager and who knows where " +"elese -->\n" +" <!-- " +"===================================================================== -->\n" +" <memory-astore:memory-store id=\"josso-assertion-store\"/>\n" +"</s:beans>\n" +" ]]>" +msgstr "" + +#. Tag: para +#: SSO.xml:263 +#, no-c-format +msgid "" +"Register the Portal Identity Store with the file <emphasis>$JBOSS_HOME/" +"server/default/deploy/conf/josso-gateway-config.xml</emphasis>" +msgstr "" + +#. Tag: programlisting +#: SSO.xml:264 +#, no-c-format +msgid "" +"<![CDATA[\n" +"............ \n" +"<!-- Identity, Session and Assertion Stores configuration -->\n" +" <s:import resource=\"josso-gateway-portal-stores.xml\" /> \n" +" <!--\n" +" <s:import resource=\"josso-gateway-memory-stores.xml\" />\n" +" <s:import resource=\"josso-gateway-db-stores.xml\" />\n" +" <s:import resource=\"josso-gateway-ldap-stores.xml\" />\n" +" -->\n" +"............ \n" +" ]]>" +msgstr "" + +#. Tag: para +#: SSO.xml:271 +#, no-c-format +msgid "Enable BIND Authentication Scheme by configuring the following:" +msgstr "" + +#. Tag: para +#: SSO.xml:274 +#, no-c-format +msgid "" +"Uncomment the BIND Authentication Scheme in <emphasis>$JBOSS_HOME/server/" +"default/deploy/conf/josso-gateway-auth.xml</emphasis>" +msgstr "" + +#. Tag: programlisting +#: SSO.xml:275 +#, no-c-format +msgid "" +"<![CDATA[\n" +"............ \n" +"<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->\n" +" <!-- BIND Authentication Scheme (normally LDAP) -->\n" +" <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->\n" +" <!-- Requires a be a bindalble credential store ! -->\n" +" <!-- name attribute is important and must not be changed -->\n" +" <bind-authscheme:bind-auth-scheme\n" +" id=\"josso-bind-authentication\"\n" +" name=\"basic-authentication\"\n" +" hashAlgorithm=\"MD5\"\n" +" hashEncoding=\"HEX\"\n" +" ignorePasswordCase=\"false\"\n" +" ignoreUserCase=\"false\">\n" +"\n" +" <bind-authscheme:credentialStore>\n" +" <s:ref bean=\"josso-identity-store\"/>\n" +" </bind-authscheme:credentialStore>\n" +"\n" +" <bind-authscheme:credentialStoreKeyAdapter>\n" +" <s:ref bean=\"josso-simple-key-adapter\"/>\n" +" </bind-authscheme:credentialStoreKeyAdapter>\n" +" </bind-authscheme:bind-auth-scheme>\n" +"............ \n" +" ]]>" +msgstr "" + +#. Tag: para +#: SSO.xml:278 +#, no-c-format +msgid "" +"Register BIND Authentication Scheme with the JOSSO Authenticator in " +"<emphasis>$JBOSS_HOME/server/default/deploy/conf/josso-gateway-config.xml</" +"emphasis>" +msgstr "" + +#. Tag: programlisting +#: SSO.xml:279 +#, no-c-format +msgid "" +"<![CDATA[\n" +"............ \n" +"<!-- ===================================================================== --" +">\n" +"<!-- SSO Authenticator, all authentication schemes must be configured here --" +">\n" +"<!-- ===================================================================== --" +">\n" +" <def-auth:authenticator id=\"josso-authenticator\">\n" +" <def-auth:schemes> \n" +" <s:ref bean=\"josso-bind-authentication\"/>\n" +" <!--\n" +" <s:ref bean=\"josso-basic-authentication\"/>\n" +" <s:ref bean=\"josso-strong-authentication\"/>\n" +" <s:ref bean=\"josso-rememberme-authentication\"/>\n" +" -->\n" +" <!-- Others like NTLM and BIND go here -->\n" +" <!--\n" +" <s:ref bean=\"josso-bind-authentication\"/>\n" +" -->\n" +" </def-auth:schemes>\n" +" </def-auth:authenticator>\n" +"............ \n" +" ]]>" +msgstr "" + +#. Tag: para +#: SSO.xml:292 +#, no-c-format +msgid "" +"This should bring up the JOSSO login screen instead of the default JBoss " +"Portal login screen" +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Security.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Security.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Security.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,916 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Security.xml:16 +#, no-c-format +msgid "Security" +msgstr "" + +#. Tag: title +#: Security.xml:18 +#, no-c-format +msgid "Securing Portal Objects" +msgstr "" + +#. Tag: para +#: Security.xml:19 +#, no-c-format +msgid "" +"This section describes how to secure portal objects (portal instances, " +"pages, and portlet instances), using the JBoss Portal *-object.xml " +"descriptor OR portlet-instances.xml descriptor. View the User Guide for " +"information on how to secure objects using the Management Portlet." +msgstr "" + +#. Tag: para +#: Security.xml:26 +#, no-c-format +msgid "" +"Securing portal objects declaratively, is done through the *-object.xml " +"( <xref linkend=\"desc_objectxml\"/> ), for Portal Instances and Pages, or " +"the portlet-instances.xml ( <xref linkend=\"desc_instancesxml\"/> ) for " +"Portlet Instances. The portion you will be adding to each object is denoted " +"by the <emphasis>&lt;security-constraint&gt;</emphasis> tag:" +msgstr "" + +#. Tag: programlisting +#: Security.xml:33 +#, no-c-format +msgid "" +"<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" +"<!DOCTYPE deployments PUBLIC\n" +" \"-//JBoss Portal//DTD Portal Object 2.6//EN\"\n" +" \"http://www.jboss.org/portal/dtd/portal-object_2_6.dtd\">\n" +"<deployments>\n" +" <deployment>\n" +" <parent-ref>default</parent-ref>\n" +" <if-exists>overwrite</if-exists>\n" +" <properties/>\n" +" <page>\n" +" <page-name>MyPage</page-name>\n" +" <window>\n" +" <window-name>HelloWorldPortletPageWindow</window-name>\n" +" <instance-ref>HelloWorldPortletPageInstance</instance-ref>\n" +" <region>center</region>\n" +" <height>0</height>\n" +" </window>\n" +" <security-constraint>\n" +" <policy-permission>\n" +" <action-name>viewrecursive</action-name>\n" +" <unchecked/>\n" +" </policy-permission>\n" +" </security-constraint>\n" +" </page>\n" +" </deployment>\n" +"</deployments>]]>" +msgstr "" + +#. Tag: para +#: Security.xml:35 +#, no-c-format +msgid "" +"The basic principle of the security mechanism is that everything is " +"restricted unless you grant privileges. You grant privilege on a portal node " +"by adding a security constraint as explained here: <programlisting><![CDATA" +"[<security-constraint>\n" +" <policy-permission>\n" +" <unchecked/>\n" +" <action-name>viewrecursive</action-name>\n" +" </policy-permission>\n" +"</security-constraint>]]></programlisting> The example above will grant the " +"view privilege to anyone (unchecked role) to the current object and any " +"child object recursively." +msgstr "" + +#. Tag: para +#: Security.xml:41 +#, no-c-format +msgid "" +"The security contraint portion is worth taking a look at, in an isolated " +"fashion. It allows you to secure a specific window/page/portal-instance " +"based on a user's role." +msgstr "" + +#. Tag: para +#: Security.xml:45 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">Role definition:</emphasis> You must define a role " +"that this security constraint will apply to. Possible values are:" +msgstr "" + +#. Tag: para +#: Security.xml:51 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">&lt;unchecked/&gt;</emphasis> Anyone can view this " +"page." +msgstr "" + +#. Tag: para +#: Security.xml:55 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">&lt;role-name&gt;SOMEROLE&lt;/role-name&gt;</" +"emphasis> Access to this page is limited to the defined role." +msgstr "" + +#. Tag: para +#: Security.xml:59 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">Access Rights:</emphasis> You must define the access " +"rights given to the role defined. Possible values are:" +msgstr "" + +#. Tag: para +#: Security.xml:65 +#, no-c-format +msgid "<emphasis role=\"bold\">view</emphasis> Users can view the page." +msgstr "" + +#. Tag: para +#: Security.xml:69 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">viewrecursive</emphasis> Users can view the page and " +"child pages." +msgstr "" + +#. Tag: para +#: Security.xml:73 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">personalize</emphasis> Users are able to personalize " +"the page's theme." +msgstr "" + +#. Tag: para +#: Security.xml:77 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">personalizerecursive</emphasis> Users are able to " +"personalize the page AND its children's pages themes." +msgstr "" + +#. Tag: title +#: Security.xml:83 +#, no-c-format +msgid "Restricting access" +msgstr "" + +#. Tag: para +#: Security.xml:84 +#, no-c-format +msgid "" +"Out of the box the default portal as a viewrecursive right for all the " +"users, it means that whenever a page is added, this page will be seen by any " +"user. To restrict access to this page, the default portal security " +"constraint must be changed from viewrecursive to view, and viewrecursive " +"security constraints must be added to its children so that they can be " +"viewed except the one you want to restrict access to." +msgstr "" + +#. Tag: para +#: Security.xml:89 +#, no-c-format +msgid "" +"We provide three live samples of this descriptor, here <xref linkend=" +"\"desc_instancesxml\"/> , <xref linkend=\"desc_example_page\"/> ,and" +msgstr "" + +#. Tag: title +#: Security.xml:100 +#, no-c-format +msgid "Securing the Content Management System" +msgstr "" + +#. Tag: para +#: Security.xml:101 +#, no-c-format +msgid "" +"The JBoss Portal CMS system consists of a directory structure of Files " +"organized unto their respective Folders. Both Files and Folders are " +"considered to be CMS resources that can be secured based on portal Roles and/" +"or Users." +msgstr "" + +#. Tag: para +#: Security.xml:105 +#, no-c-format +msgid "" +"The following features are supported by the fine grained security system of " +"Portal CMS:" +msgstr "" + +#. Tag: para +#: Security.xml:108 +#, no-c-format +msgid "" +"You can associate \"Read\", \"Write\", and \"Manage\" Permissions at the CMS " +"node level. (Both Files and Folders are treated as CMS nodes)" +msgstr "" + +#. Tag: para +#: Security.xml:112 +#, no-c-format +msgid "The Permissions are propagated recursively down a folder hierarchy" +msgstr "" + +#. Tag: para +#: Security.xml:115 +#, no-c-format +msgid "" +"Any Permissions specified explicitly on the CMS Node overrides the policy " +"inherited via recursive propagation" +msgstr "" + +#. Tag: para +#: Security.xml:118 +#, no-c-format +msgid "" +"You can manage the Permissions using the CMS Admin GUI tool via the newly " +"added \"Secure Node\" feature" +msgstr "" + +#. Tag: title +#: Security.xml:124 +#, no-c-format +msgid "Portal CMS Permission Matrix:" +msgstr "" + +#. Tag: entry +#: Security.xml:129 +#, no-c-format +msgid "Permissions" +msgstr "" + +#. Tag: entry +#: Security.xml:130 +#, no-c-format +msgid "Allowed Actions" +msgstr "" + +#. Tag: entry +#: Security.xml:131 +#, no-c-format +msgid "Implies" +msgstr "" + +#. Tag: entry +#: Security.xml:136 +#, no-c-format +msgid "Read" +msgstr "" + +#. Tag: entry +#: Security.xml:137 +#, no-c-format +msgid "Read Contents of Folder, File and its versions" +msgstr "" + +#. Tag: entry +#: Security.xml:138 +#, no-c-format +msgid "<entry>N/A</entry>" +msgstr "" + +#. Tag: entry +#: Security.xml:141 +#, no-c-format +msgid "Write" +msgstr "" + +#. Tag: entry +#: Security.xml:142 +#, no-c-format +msgid "Create and Update new Folder and File" +msgstr "" + +#. Tag: entry +#: Security.xml:143 +#, no-c-format +msgid "Read Access" +msgstr "" + +#. Tag: entry +#: Security.xml:146 +#, no-c-format +msgid "Manage" +msgstr "" + +#. Tag: entry +#: Security.xml:147 +#, no-c-format +msgid "Delete/Copy/Move/Rename Folders and Files" +msgstr "" + +#. Tag: entry +#: Security.xml:148 +#, no-c-format +msgid "Read and Write Access" +msgstr "" + +#. Tag: title +#: Security.xml:155 +#, no-c-format +msgid "CMS Security Configuration" +msgstr "" + +#. Tag: para +#: Security.xml:156 +#, no-c-format +msgid "" +"The configuration for the CMS Security service is specified in the " +"<literal>jboss-portal.sar/portal-cms.sar/META-INF/jboss-service.xml</" +"literal> file. The portion of the configuration relevant for securing the " +"CMS service is listed as follows:" +msgstr "" + +#. Tag: programlisting +#: Security.xml:160 +#, no-c-format +msgid "" +"<![CDATA[\n" +" <!-- CMS Authorization Security Service -->\n" +" <mbean\n" +" code=\"org.jboss.portal.cms.security." +"AuthorizationManagerImpl\"\n" +" name=\"portal:service=AuthorizationManager," +"type=cms\"\n" +" xmbean-dd=\"\"\n" +" xmbean-code=\"org.jboss.portal.jems.as.system." +"JBossServiceModelMBean\">\n" +" <xmbean/>\n" +" <attribute name=\"JNDIName\">java:portal/cms/" +"AuthorizationManager</attribute> \n" +" <depends optional-attribute-name=\"Provider\" " +"proxy-type=\"attribute\">\n" +" portal:service=AuthorizationProvider," +"type=cms\n" +" </depends> \n" +" </mbean> \n" +" <mbean\n" +" code=\"org.jboss.portal.cms.security." +"AuthorizationProviderImpl\"\n" +" name=\"portal:service=AuthorizationProvider," +"type=cms\"\n" +" xmbean-dd=\"\"\n" +" xmbean-code=\"org.jboss.portal.jems.as.system." +"JBossServiceModelMBean\">\n" +" <xmbean/> \n" +" <!--\n" +" NOTE: cmsRootUserName denotes a single " +"Portal user that has access to everything in the CMS. Denote this user\n" +" carefully and should be synonymous to the " +"'root' user in UNIX operating systems. By default: this value is the built-" +"in\n" +" 'admin' user account. This can be " +"changed to any other user account registered in your Portal\n" +" -->\n" +" <attribute name=\"CmsRootUserName\">admin</" +"attribute> \n" +" <depends optional-attribute-name=" +"\"IdentityServiceController\" proxy-type=\"attribute\">portal:service=Module," +"type=IdentityServiceController</depends> \n" +" </mbean> \n" +" <!-- ACL Security Interceptor -->\n" +" <mbean\n" +" code=\"org.jboss.portal.cms.impl.interceptors." +"ACLInterceptor\"\n" +" name=\"portal:service=Interceptor,type=Cms," +"name=ACL\"\n" +" xmbean-dd=\"\"\n" +" xmbean-code=\"org.jboss.portal.jems.as.system." +"JBossServiceModelMBean\">\n" +" <xmbean/>\n" +" <attribute name=\"JNDIName\">java:/portal/cms/" +"ACLInterceptor</attribute>\n" +" <attribute name=\"CmsSessionFactory\">java:/" +"portal/cms/CMSSessionFactory</attribute>\n" +" <attribute name=\"IdentitySessionFactory" +"\">java:/portal/IdentitySessionFactory</attribute>\n" +" <attribute name=\"DefaultPolicy\">\n" +" <policy>\n" +" <!-- permissions on " +"the root cms node --> \n" +" <criteria name=\"path" +"\" value=\"/\">\n" +" <permission " +"name=\"cms\" action=\"read\">\n" +" <role " +"name=\"Anonymous\"/>\n" +" </permission>\n" +" <permission " +"name=\"cms\" action=\"write\">\n" +" <role " +"name=\"User\"/>\n" +" </permission>\n" +" <permission " +"name=\"cms\" action=\"manage\">\n" +" <role " +"name=\"Admin\"/>\n" +" </permission>\n" +" </criteria>\n" +" <!-- permissions on " +"the default cms node --> \n" +" <criteria name=\"path" +"\" value=\"/default\">\n" +" <permission " +"name=\"cms\" action=\"read\">\n" +" <role " +"name=\"Anonymous\"/>\n" +" </permission>\n" +" <permission " +"name=\"cms\" action=\"write\">\n" +" <role " +"name=\"User\"/>\n" +" </permission>\n" +" <permission " +"name=\"cms\" action=\"manage\">\n" +" <role " +"name=\"Admin\"/>\n" +" </permission>\n" +" </" +"criteria> \n" +" <!-- permissions on " +"the private/protected node -->\n" +" <criteria name=\"path" +"\" value=\"/default/private\">\n" +" <permission " +"name=\"cms\" action=\"manage\">\n" +" <role " +"name=\"Admin\"/>\n" +" </permission>\n" +" </criteria>\n" +" </policy>\n" +" </attribute>\n" +" <depends optional-attribute-name=" +"\"AuthorizationManager\" proxy-type=\"attribute\">\n" +" portal:service=AuthorizationManager," +"type=cms\n" +" </depends> \n" +" <depends>portal:service=Hibernate,type=CMS</" +"depends>\n" +" <depends>portal:service=Module," +"type=IdentityServiceController</depends> \n" +" </mbean>]]>" +msgstr "" + +#. Tag: title +#: Security.xml:163 +#, no-c-format +msgid "CMS Super User" +msgstr "" + +#. Tag: para +#: Security.xml:164 +#, no-c-format +msgid "" +"A CMS Super User is a designated Portal User Account that has access to all " +"resources/functions in the CMS. It is a concept similar to the super user " +"concept in a Linux and UNIX security systems. This account should be " +"carefully used and properly protected. By default, JBoss Portal designates " +"the built-in 'admin' user account as a CMS Super User. This can be changed " +"by modifying the <emphasis>cmsRootUserName</emphasis> value in the " +"<literal>jboss-portal.sar/portal-cms.sar/META-INF/jboss-service.xml</" +"literal> configuration." +msgstr "" + +#. Tag: programlisting +#: Security.xml:169 +#, no-c-format +msgid "" +"<![CDATA[ \n" +" <mbean\n" +" code=\"org.jboss.portal.cms.security." +"AuthorizationProviderImpl\"\n" +" name=\"portal:service=AuthorizationProvider," +"type=cms\"\n" +" xmbean-dd=\"\"\n" +" xmbean-code=\"org.jboss.portal.jems.as.system." +"JBossServiceModelMBean\">\n" +" <xmbean/> \n" +" <!--\n" +" NOTE: cmsRootUserName denotes a single " +"Portal user that has access to everything in the CMS. Denote this user\n" +" carefully and should be synonymous to the " +"'root' user in UNIX operating systems. By default: this value is the built-" +"in\n" +" 'admin' user account. This can be " +"changed to any other user account registered in your Portal\n" +" -->\n" +" <attribute name=\"CmsRootUserName\">admin</" +"attribute> \n" +" <depends optional-attribute-name=" +"\"IdentityServiceController\" proxy-type=\"attribute\">portal:service=Module," +"type=IdentityServiceController</depends> \n" +" </mbean> \n" +" ]]>" +msgstr "" + +#. Tag: title +#: Security.xml:173 +#, no-c-format +msgid "CMS Security Console" +msgstr "" + +#. Tag: para +#: Security.xml:174 +#, no-c-format +msgid "" +"The CMS Security Console is used to assign proper permissions to all the " +"nodes/content in the CMS. Besides protection on CMS content, this console " +"itself needs to be secured against unauthorized acceess. Currently, the " +"console can be accessed only by Portal users that are members of the " +"specified Role. By default, JBoss Portal uses the built-in <emphasis>Admin</" +"emphasis> role to allow access to this security console. This can be " +"customized by modifying the value of <emphasis>defaultAdminRole</emphasis> " +"option specified in <literal>jboss-portal.sar/conf/identity/standardidentity-" +"config.xml</literal>" +msgstr "" + +#. Tag: title +#: Security.xml:185 +#, no-c-format +msgid "Authentication with JBoss Portal" +msgstr "" + +#. Tag: para +#: Security.xml:186 +#, no-c-format +msgid "" +"JBoss Portal relies on Java Platform, Enterprise Edition (Java EE) for the " +"authentication of users. The Java EE authentication has its advantages and " +"drawbacks. The main motivation for using Java EE security is the integration " +"with the application server and the operational environment in which the " +"portal is deployed. The servlet layer provides already the authentication " +"functionality and obviously it is not a responsibility of the portal. " +"Whenever a user is authenticated by the servlet layer its security identity " +"is propagated throughout the call stack in the different layers of the Java " +"EE stack. The weaknesses are the lack of an explicit logout mechanism and " +"the lack of dynamicity in the mapping of URL as security resources. However " +"JBoss Portal improves that behavior when it is possible to do so." +msgstr "" + +#. Tag: title +#: Security.xml:188 +#, no-c-format +msgid "Authentication configuration" +msgstr "" + +#. Tag: para +#: Security.xml:189 +#, no-c-format +msgid "" +"JBoss Portal can be seen before all as a web application and therefore " +"inherits all the configuration mechanisms related to web applications. The " +"main entry point of the whole portal is the <emphasis>jboss-portal.sar/" +"portal-server.war</emphasis> deployment which is the web application that " +"defines and maps the portal servlet. Here you can configure various things" +msgstr "" + +#. Tag: para +#: Security.xml:193 +#, no-c-format +msgid "" +"In the <emphasis>WEB-INF/web.xml</emphasis> you can change the " +"authentication mode. The default authentication mechanism uses the form " +"based authentication, however you can change it to any of the mechanism " +"provided by the servlet specification." +msgstr "" + +#. Tag: para +#: Security.xml:196 +#, no-c-format +msgid "" +"In the <emphasis>WEB-INF/jboss-web.xml</emphasis> you can change the " +"security domain used by the portal. The default security domain used by the " +"portal is <emphasis>java:/jaas/portal</emphasis>. That setting is specific " +"to the JBoss Application Server and how it binds the Java EE security to the " +"operational environment. A security domain is a scope defined at the " +"Application Server Level and defines usually a JAAS authentication stack. " +"The portal security domain authentication stack is defined in the " +"<emphasis>jboss-portal.sar/conf/login-config.xml</emphasis> and is " +"dynamically deployed with the portal. The JBoss Application Server " +"documentation is certainly the best reference for that topic." +msgstr "" + +#. Tag: para +#: Security.xml:204 +#, no-c-format +msgid "" +"The files <emphasis>login.jsp</emphasis> and <emphasis>error.jsp</emphasis> " +"represent the pages used the form based authentication process. More " +"information can be found in any good servlet documentation." +msgstr "" + +#. Tag: title +#: Security.xml:210 +#, no-c-format +msgid "The portal servlet" +msgstr "" + +#. Tag: para +#: Security.xml:211 +#, no-c-format +msgid "" +"The portal defines a single servlet to take care of all portal requests. The " +"class name of that servlet is <emphasis>org.jboss.portal.server.servlet." +"PortalServlet</emphasis>. That servlet needs to be declared two times with " +"different configurations otherwise the portal would not be able to know " +"about some request details which are importants. <itemizedlist> " +"<listitem><para><emphasis>PortalServletWithPathMapping</emphasis> is used " +"for path mapping mappings.</para></listitem> " +"<listitem><para><emphasis>PortalServletWithDefaultServletMapping</emphasis> " +"is used for the default servlet mapping.</para></listitem> </itemizedlist> " +"The portal servlet is mapped four times with different semantics, the " +"differences between the semantics are related to the transport layer. Each " +"one of those for mappings will have the same request meaning for the portal " +"beside the transport aspect. By default those mappings are <itemizedlist> " +"<listitem><para><emphasis>/*</emphasis> : the default access, does not " +"define any security constraint. This is the default access that everybody " +"uses.</para></listitem> <listitem><para><emphasis>/sec/*</emphasis> : the " +"secured access, requires https usage. It is triggered when a portlet is " +"defined as secure or when a secure portlet link is created. It requires the " +"configuration of the https connector in JBoss Web. The JBoss Application " +"Server documentation provides more information about it.</para></listitem> " +"<listitem><para><emphasis>/auth/*</emphasis> : the authenticated access, " +"requires the user to be authenticated to be used.</para></listitem> " +"<listitem><para><emphasis>/authsec/*</emphasis> : combine the two previous " +"options into a single one.</para></listitem> </itemizedlist> Usually ones " +"should not care much about those mappings as the portal will by itself " +"switch to the most appropriate mapping." +msgstr "" + +#. Tag: title +#: Security.xml:238 +#, no-c-format +msgid "Authorization with JBoss Portal" +msgstr "" + +#. Tag: para +#: Security.xml:239 +#, no-c-format +msgid "" +"JBoss Portal defines a framework for authorization. The default " +"implementation of that framework is based on the Java Authorization Contract " +"for Containers (JACC) which is implemented by <trademark class=\"trade" +"\">J2EE</trademark> 1.4 Application Servers. This section of the " +"documentation focuses on defining the framework and its usage and is not an " +"attempt to define what authorization is or is not because it is out of scope " +"of this context. Instead we will try to straightforwardly describe the " +"framework and how it is used. No specific knowledge is expected about JACC " +"although it is a recommended read." +msgstr "" + +#. Tag: title +#: Security.xml:245 +#, no-c-format +msgid "The portal permission" +msgstr "" + +#. Tag: para +#: Security.xml:246 +#, no-c-format +msgid "" +"The <emphasis>org.jboss.portal.security.PortalPermission</emphasis> object " +"is used to describe a permission for the portal. It extends the " +"<emphasis>java.security.Permission</emphasis> class and any permission " +"checked in the portal should extend the <emphasis>PortalPermission</" +"emphasis> as well. That permission adds two fields to the " +"<emphasis>Permission</emphasis> class" +msgstr "" + +#. Tag: para +#: Security.xml:250 +#, no-c-format +msgid "" +"uri : is a string which represents an URI of the resource described by the " +"permission." +msgstr "" + +#. Tag: para +#: Security.xml:251 +#, no-c-format +msgid "" +"collection : an object of class <emphasis>org.jboss.portal.security." +"PortalPermissionCollection</emphasis> which is used when the permission act " +"as a container for other permissions. If that object exists then the uri " +"field should be null as a portal permission represents an uri or acts as a " +"container in an exclusive manner." +msgstr "" + +#. Tag: title +#: Security.xml:258 +#, no-c-format +msgid "The authorization provider" +msgstr "" + +#. Tag: para +#: Security.xml:259 +#, no-c-format +msgid "" +"The <emphasis>org.jboss.portal.security.spi.provider.AuthorizationDomain</" +"emphasis> is an interface which provides access to several services." +msgstr "" + +#. Tag: programlisting +#: Security.xml:261 +#, no-c-format +msgid "" +"public interface AuthorizationDomain\n" +"{\n" +" String getType();\n" +" DomainConfigurator getConfigurator();\n" +" PermissionRepository getPermissionRepository();\n" +" PermissionFactory getPermissionFactory();\n" +"}" +msgstr "" + +#. Tag: para +#: Security.xml:263 +#, no-c-format +msgid "" +"<emphasis>org.jboss.portal.security.spi.provider.DomainConfigurator</" +"emphasis> provides configuration access to an authorization domain. The " +"authorization schema is very simple as it consists of bindings between URI, " +"roles and permissions." +msgstr "" + +#. Tag: para +#: Security.xml:265 +#, no-c-format +msgid "" +"<emphasis>org.jboss.portal.security.spi.provider.PermissionRepository</" +"emphasis> provides runtime access to the authorization domain. Usually it is " +"used to retrieve the permissions for a specific role and URI. It is used at " +"runtime by the framework to take security decisions." +msgstr "" + +#. Tag: para +#: Security.xml:268 +#, no-c-format +msgid "" +"<emphasis>org.jboss.portal.security.spi.provider.PermissionFactory</" +"emphasis> is a factory to instantiate permissions for the specific domain. " +"It is used at runtime to create permissions objects of the appropriate type " +"by the security framework." +msgstr "" + +#. Tag: title +#: Security.xml:274 +#, no-c-format +msgid "Making a programmatic security check" +msgstr "" + +#. Tag: para +#: Security.xml:275 +#, no-c-format +msgid "" +"Making a security check is an easy thing as it consists in creating a " +"permission of the appropriate type and make a check against the " +"<emphasis>org.jboss.portal.spi.auth.PortalAuthorizationManager</emphasis> " +"service. That service is used by the portal to make security checks. It is " +"connected to the different authorization providers in order to take " +"decisions at runtime based on the type of the permission. Access to that " +"service is done through the <emphasis>org.jboss.portal.spi.auth." +"PortalAuthorizationManagerFactory</emphasis>. The factory is a portal " +"service which is usually injected in other services like that" +msgstr "" + +#. Tag: programlisting +#: Security.xml:281 +#, no-c-format +msgid "" +"<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" +"<server>\n" +" ...\n" +" <mbean\n" +" code='MyService\"\n" +" name=\"portal:service=MyService\">\n" +" <depends\n" +" optional-attribute-name=\"PortalAuthorizationManagerFactory\"\n" +" proxy-type=\"attribute\">portal:" +"service=PortalAuthorizationManagerFactory</depends>\n" +" ...\n" +" </mbean>\n" +" ...\n" +"</server>]]>" +msgstr "" + +#. Tag: para +#: Security.xml:282 +#, no-c-format +msgid "" +"It can be injected in the servlet context of a war file in the file " +"<emphasis>WEB-INF/jboss-portlet.xml</emphasis>" +msgstr "" + +#. Tag: programlisting +#: Security.xml:283 +#, no-c-format +msgid "" +"<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" +"<!DOCTYPE portlet-app PUBLIC\n" +" \"-//JBoss Portal//DTD JBoss Portlet 2.6//EN\"\n" +" \"http://www.jboss.org/portal/dtd/jboss-portlet_2_6.dtd\">\n" +"<portlet-app>\n" +" ...\n" +" <service>\n" +" <service-name>PortalAuthorizationManagerFactory</service-name>\n" +" <service-class>\n" +" org.jboss.portal.security.spi.auth.PortalAuthorizationManagerFactory\n" +" </service-class>\n" +" <service-ref>:service=PortalAuthorizationManagerFactory</service-ref>\n" +" </service>\n" +" ...\n" +"</portlet-app>]]>" +msgstr "" + +#. Tag: para +#: Security.xml:284 +#, no-c-format +msgid "Here is an example of how a security check is made for a specific page" +msgstr "" + +#. Tag: programlisting +#: Security.xml:285 +#, no-c-format +msgid "" +"PortalAuthorizationManager pam = factory.getManager();\n" +"PortalObjectId id = page.getId();\n" +"PortalObjectPermission perm = new PortalObjectPermission(id, " +"PortalObjectPermission.VIEW_MASK);\n" +"if (pam.checkPermission(perm) == false)\n" +"{\n" +" System.out.println(\"Current user is not authorized to view page \" + " +"id);\n" +"}" +msgstr "" + +#. Tag: title +#: Security.xml:288 +#, no-c-format +msgid "Configuring an authorization domain" +msgstr "" + +#. Tag: para +#: Security.xml:289 +#, no-c-format +msgid "" +"Configuring a domain can be done through the <emphasis>DomainConfigurator</" +"emphasis> interface" +msgstr "" + +#. Tag: programlisting +#: Security.xml:290 +#, no-c-format +msgid "" +"public interface DomainConfigurator\n" +"{\n" +" Set getSecurityBindings(String uri);\n" +" void setSecurityBindings(String uri, Set securityBindings)\n" +" throws SecurityConfigurationException;\n" +" void removeSecurityBindings(String uri) throws " +"SecurityConfigurationException;\n" +"}" +msgstr "" + +#. Tag: para +#: Security.xml:291 +#, no-c-format +msgid "" +"The various methods of that interface allows to configure security bindings " +"for a given resource where a resource is naturally identified by an URI. The " +"<emphasis>org.jboss.portal.security.RoleSecurityBinding</emphasis> object is " +"an object which encapsulate a role name and a set of actions bound to this " +"role." +msgstr "" + +#. Tag: programlisting +#: Security.xml:295 +#, no-c-format +msgid "" +"RoleSecurityBinding binding1 = new RoleSecurityBinding(Collections.singleton" +"(\"view\"), \"Admin\");\n" +"RoleSecurityBinding binding2 = new RoleSecurityBinding(Collections.singleton" +"(\"view\"), \"User\");\n" +"Set bindings = new HashSet();\n" +"bindings.add(binding1);\n" +"bindings.add(binding2);\n" +"configurator.setSecurityBinding(pageURI, bindings);" +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Supported.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Supported.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Supported.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,190 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Supported.xml:6 +#, no-c-format +msgid "System Requirements" +msgstr "" + +#. Tag: para +#: Supported.xml:7 +#, no-c-format +msgid "" +"The following chapter details hardware and software versions that are " +"compatible with Enterprise Portal Platform. The hardware and software listed " +"has been tested and is supported." +msgstr "" + +#. Tag: para +#: Supported.xml:11 +#, no-c-format +msgid "" +"If you want to use the Enterprise Portal Platform on other combinations, " +"please let your sale representative know." +msgstr "" + +#. Tag: title +#: Supported.xml:15 +#, no-c-format +msgid "Minimum System Requirements" +msgstr "" + +#. Tag: para +#: Supported.xml:18 +#, no-c-format +msgid "" +"JDK 5 or JDK 6 (requires modification, see the <ulink url=\"http://www." +"redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/4.3.0.cp03/html-" +"single/JDK6_Compatibility_Notes/index.html\">EAP guide</ulink>" +msgstr "" + +#. Tag: para +#: Supported.xml:19 +#, no-c-format +msgid "512 MB RAM" +msgstr "" + +#. Tag: para +#: Supported.xml:20 +#, no-c-format +msgid "100 MB hard disk space" +msgstr "" + +#. Tag: para +#: Supported.xml:21 +#, no-c-format +msgid "400 MHz CPU" +msgstr "" + +#. Tag: title +#: Supported.xml:26 +#, no-c-format +msgid "Supported Operating Systems" +msgstr "" + +#. Tag: para +#: Supported.xml:27 +#, no-c-format +msgid "" +"JBoss Enterprise Portal Platform (EPP) is <trademark class=\"trade\">100% " +"Pure Java</trademark>, and therefore it is interoperable with most operating " +"systems capable of running a Java Virtual Machine (<trademark class=\"trade" +"\">JVM</trademark>), including <trademark class=\"registered\">Linux</" +"trademark>, <trademark class=\"registered\">Windows</trademark>, <trademark " +"class=\"registered\">UNIX</trademark> operating systems, and Mac OS X." +msgstr "" + +#. Tag: title +#: Supported.xml:32 +#, no-c-format +msgid "JBoss Enterprise Application Platform (EAP)" +msgstr "" + +#. Tag: para +#: Supported.xml:33 +#, no-c-format +msgid "" +"Enterprise Portal Platform 4.3 CP02 embeds JBoss EAP 4.3_CP06 and JBoss EAP " +"FP01 4.3_CP05 and supports the same environment unless specified." +msgstr "" + +#. Tag: title +#: Supported.xml:36 +#, no-c-format +msgid "Databases" +msgstr "" + +#. Tag: para +#: Supported.xml:37 +#, no-c-format +msgid "" +"Enterprise Portal Platform is database-agnostic. The following list outlines " +"tested database vendor and version combinations:" +msgstr "" + +#. Tag: para +#: Supported.xml:39 +#, no-c-format +msgid "" +"<trademark class=\"registered\">MySQL</trademark> 4 (use <ulink url=\"http://" +"dev.mysql.com/downloads/connector/j/3.1.html\">Connector/J 3.1</ulink>) and " +"5 (<ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?" +"page=AvoidMySQL5DataTruncationErrors\">known issue</ulink>)" +msgstr "" + +#. Tag: para +#: Supported.xml:40 +#, no-c-format +msgid "PostgreSQL 8.<replaceable>x</replaceable>" +msgstr "" + +#. Tag: para +#: Supported.xml:41 +#, no-c-format +msgid "Hypersonic SQL" +msgstr "" + +#. Tag: para +#: Supported.xml:42 +#, no-c-format +msgid "Apache Derby" +msgstr "" + +#. Tag: para +#: Supported.xml:43 +#, no-c-format +msgid "" +"<trademark class=\"registered\">Oracle</trademark> Database 9 and 10g (use " +"the <ulink url=\"http://www.oracle.com/technology/software/tech/java/" +"sqlj_jdbc/index.html\">latest driver from the Oracle 10 branch</ulink> even " +"if you are running Oracle 9)" +msgstr "" + +#. Tag: para +#: Supported.xml:44 +#, no-c-format +msgid "" +"<trademark class=\"registered\">Microsoft</trademark><trademark class=" +"\"registered\"> SQL Server</trademark>" +msgstr "" + +#. Tag: para +#: Supported.xml:45 +#, no-c-format +msgid "MaxDB" +msgstr "" + +#. Tag: para +#: Supported.xml:47 +#, no-c-format +msgid "" +"Enterprise Portal Platform employs Hibernate as an interface to a Relational " +"Database Management System (RDBMS)." +msgstr "" + +#. Tag: title +#: Supported.xml:50 +#, no-c-format +msgid "Source Building" +msgstr "" + +#. Tag: para +#: Supported.xml:51 +#, no-c-format +msgid "" +"The source building mechanism works on Linux, Windows, Mac OS X, and UNIX " +"operating systems." +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Target.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Target.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Target.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,30 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Target.xml:6 +#, no-c-format +msgid "Target Audience" +msgstr "" + +#. Tag: para +#: Target.xml:7 +#, no-c-format +msgid "" +"This guide is aimed towards portlet developers, portal administrators, and " +"those wishing to implement and extend the Enterprise Portal Platform " +"framework. For end-user documentation, please refer to the Enterprise Portal " +"Platform's User Guide available with the documentation bundle." +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Theme_And_Layouts.po =================================================================== Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Trademarks.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Trademarks.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Trademarks.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,105 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Trademarks.xml:6 +#, no-c-format +msgid "Please Read: Important Trademark Information" +msgstr "" + +#. Tag: para +#: Trademarks.xml:7 +#, no-c-format +msgid "" +"Sun, JavaServer, JSP, Java, JMX, JDK, Java runtime environment, J2EE, JVM, " +"Javadoc, 100% Pure Java, JDBC, and JavaScript are trademarks or registered " +"trademarks of Sun Microsystems, Inc. in the United States and other " +"countries." +msgstr "" + +#. Tag: para +#: Trademarks.xml:10 +#, no-c-format +msgid "" +"JBoss is a registered trademark of Red Hat, Inc. in the U.S. and other " +"countries." +msgstr "" + +#. Tag: para +#: Trademarks.xml:13 +#, no-c-format +msgid "" +"Red Hat is a registered trademark of Red Hat, Inc. in the United States and " +"other countries." +msgstr "" + +#. Tag: para +#: Trademarks.xml:16 +#, no-c-format +msgid "Oracle is a registered trademark of Oracle International Corporation." +msgstr "" + +#. Tag: para +#: Trademarks.xml:19 +#, no-c-format +msgid "" +"Microsoft, Windows, Active Directory, and SQL Server are either registered " +"trademarks or trademarks of Microsoft Corporation in the United States and/" +"or other countries." +msgstr "" + +#. Tag: para +#: Trademarks.xml:22 +#, no-c-format +msgid "" +"Linux® is the registered trademark of Linus Torvalds in the U.S. and other " +"countries." +msgstr "" + +#. Tag: para +#: Trademarks.xml:25 +#, no-c-format +msgid "UNIX is a registered trademark of The Open Group." +msgstr "" + +#. Tag: para +#: Trademarks.xml:28 +#, no-c-format +msgid "" +"MySQL is a trademark or registered trademark of MySQL AB in the U.S. and " +"other countries." +msgstr "" + +#. Tag: para +#: Trademarks.xml:31 +#, no-c-format +msgid "Apache is a trademark of The Apache Software Foundation." +msgstr "" + +#. Tag: para +#: Trademarks.xml:34 +#, no-c-format +msgid "" +"Mac and Mac OS are trademarks of Apple Inc., registered in the U.S. and " +"other countries." +msgstr "" + +#. Tag: para +#: Trademarks.xml:37 +#, no-c-format +msgid "" +"All other trademarks referenced herein are the property of their respective " +"owners." +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Troubleshooting.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Troubleshooting.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Troubleshooting.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,325 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Troubleshooting.xml:13 Troubleshooting.xml:15 +#, no-c-format +msgid "Troubleshooting and FAQ" +msgstr "" + +#. Tag: emphasis +#: Troubleshooting.xml:17 +#, no-c-format +msgid "Installation / Configuration" +msgstr "" + +#. Tag: para +#: Troubleshooting.xml:19 +#, no-c-format +msgid "" +"I am seeing \"ERROR [JDBCExceptionReporter] Table not found in statement\" " +"in the logfile on first boot. What is this?" +msgstr "" + +#. Tag: para +#: Troubleshooting.xml:24 +#, no-c-format +msgid "" +"<para>I want to do a clean install/upgrade over my existing one. What are " +"the steps?</para>" +msgstr "" + +#. Tag: para +#: Troubleshooting.xml:28 +#, no-c-format +msgid "Is my database vendor/version combination supported?" +msgstr "" + +#. Tag: para +#: Troubleshooting.xml:32 +#, no-c-format +msgid "How do I force the Hibernate Dialect used for my database?" +msgstr "" + +#. Tag: para +#: Troubleshooting.xml:35 +#, no-c-format +msgid "" +"How do I change the context-root of the portal to http://localhost:8080/?" +msgstr "" + +#. Tag: emphasis +#: Troubleshooting.xml:40 +#, no-c-format +msgid "<emphasis>CMS</emphasis>" +msgstr "" + +#. Tag: para +#: Troubleshooting.xml:43 +#, no-c-format +msgid ". How do I change the CMS repository configuration?" +msgstr "" + +#. Tag: para +#: Troubleshooting.xml:46 +#, no-c-format +msgid ".On reboot, the CMS is complaining about a locked repository." +msgstr "" + +#. Tag: para +#: Troubleshooting.xml:49 +#, no-c-format +msgid ". I created a file in the CMSAdmin. How do I view it?" +msgstr "" + +#. Tag: emphasis +#: Troubleshooting.xml:54 +#, no-c-format +msgid "Errors" +msgstr "" + +#. Tag: para +#: Troubleshooting.xml:57 +#, no-c-format +msgid "" +". When I access a specific portal-instance or page, I keep seeing \"401 - " +"not authorized\" error in my browser." +msgstr "" + +#. Tag: para +#: Troubleshooting.xml:61 +#, no-c-format +msgid ". How do I disable development-mode errors on the presentation layer?" +msgstr "" + +#. Tag: emphasis +#: Troubleshooting.xml:66 +#, no-c-format +msgid "Miscellaneous" +msgstr "" + +#. Tag: para +#: Troubleshooting.xml:69 +#, no-c-format +msgid "" +"<para>Is there a sample portlet I can look at to learn about portlet " +"development and JBoss Portal deployments?</para>" +msgstr "" + +#. Tag: title +#: Troubleshooting.xml:77 +#, no-c-format +msgid "\"Error [JDBCExceptionReporter] Table not found in statement\"" +msgstr "" + +#. Tag: para +#: Troubleshooting.xml:78 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">I am seeing \"ERROR [JDBCExceptionReporter] Table " +"not found in statement\" in the logfile on first boot. What is this?</" +"emphasis> Ignore this error. It is used by the portal to create the initial " +"database tables. On second boot, you should not see them at all." +msgstr "" + +#. Tag: title +#: Troubleshooting.xml:88 +#, no-c-format +msgid "install/upgrade" +msgstr "" + +#. Tag: emphasis +#: Troubleshooting.xml:90 +#, no-c-format +msgid "" +"<emphasis>I want to do a clean install/upgrade over my existing one. What " +"are the steps?</emphasis>" +msgstr "" + +#. Tag: para +#: Troubleshooting.xml:92 +#, no-c-format +msgid "Shut down JBoss AS" +msgstr "" + +#. Tag: para +#: Troubleshooting.xml:93 +#, no-c-format +msgid "Delete JBOSS_HOME/server/default/data/portal" +msgstr "" + +#. Tag: para +#: Troubleshooting.xml:94 +#, no-c-format +msgid "Delete all JBoss Portal tables from your database" +msgstr "" + +#. Tag: para +#: Troubleshooting.xml:95 +#, no-c-format +msgid "Start JBoss AS." +msgstr "" + +#. Tag: title +#: Troubleshooting.xml:100 +#, no-c-format +msgid "database support" +msgstr "" + +#. Tag: para +#: Troubleshooting.xml:101 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">Is my database vendor/version combination supported?" +"</emphasis> See" +msgstr "" + +#. Tag: title +#: Troubleshooting.xml:108 +#, no-c-format +msgid "Hibernate Dialect" +msgstr "" + +#. Tag: para +#: Troubleshooting.xml:109 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">How do I force the Hibernate Dialect used for my " +"database?</emphasis> See" +msgstr "" + +#. Tag: title +#: Troubleshooting.xml:116 +#, no-c-format +msgid "context-root" +msgstr "" + +#. Tag: para +#: Troubleshooting.xml:117 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">How do I change the context-root of the portal to " +"http://localhost:8080/?</emphasis> See" +msgstr "" + +#. Tag: title +#: Troubleshooting.xml:124 +#, no-c-format +msgid "CMS repository configuration" +msgstr "" + +#. Tag: para +#: Troubleshooting.xml:125 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">How do I change the CMS repository configuration?</" +"emphasis> There are 3 supported modes: 100% DB (default), 100% Filsystem, " +"and Mixed (Blobs on the Filesystem and metadata in the DB). You can see " +"configuration options here:" +msgstr "" + +#. Tag: title +#: Troubleshooting.xml:133 +#, no-c-format +msgid "Locked repository" +msgstr "" + +#. Tag: para +#: Troubleshooting.xml:134 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">On reboot, the CMS is complaining about a locked " +"repository.</emphasis> This occurs when JBoss AS is improperly shutdown or " +"the CMS Service errors on startup. To remove the lock, shutdown JBoss, and " +"then remove the file under JBOSS_HOME/server/default/data/portal/cms/conf/." +"lock." +msgstr "" + +#. Tag: title +#: Troubleshooting.xml:142 +#, no-c-format +msgid "CMSAdmin" +msgstr "" + +#. Tag: para +#: Troubleshooting.xml:143 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">I created a file in the CMSAdmin. How do I view it?</" +"emphasis> Using the default configuration, the path to the file in the " +"browser would be: http://localhost:8080/portal/content/path/to/file.ext. " +"Note that all requests for cms content must be prepended with /content and " +"then followed by the path/to/the/file.gif as it is in your directory " +"structure." +msgstr "" + +#. Tag: title +#: Troubleshooting.xml:153 +#, no-c-format +msgid "\"401 - not authorised\"" +msgstr "" + +#. Tag: para +#: Troubleshooting.xml:154 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">When I access a specific portal-instance or page, I " +"keep seeing \"401 - not authorized\" error in my browser.</emphasis> You are " +"likely not authorized to view the page or portal instance. You can either " +"modify the security using the Management Portlet under the Admin Tab, or " +"secure your portlets via the object descriptor," +msgstr "" + +#. Tag: title +#: Troubleshooting.xml:163 +#, no-c-format +msgid "Development errors" +msgstr "" + +#. Tag: para +#: Troubleshooting.xml:164 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">How do I disable development-mode errors on the " +"presentation layer?</emphasis> See:" +msgstr "" + +#. Tag: title +#: Troubleshooting.xml:170 +#, no-c-format +msgid "Portlet Deployment" +msgstr "" + +#. Tag: emphasis +#: Troubleshooting.xml:172 +#, no-c-format +msgid "" +"<emphasis>Is there a sample portlet I can look at to learn about portlet " +"development and JBoss Portal deployments?</emphasis>" +msgstr "" + +#. Tag: para +#: Troubleshooting.xml:177 +#, no-c-format +msgid "Sample portlets with tutorials can be found here," +msgstr "" + +#. Tag: para +#: Troubleshooting.xml:180 +#, no-c-format +msgid "" +"Additional Portlets can be found at <ulink url=\"http://www.portletswap.com" +"\">PortletSwap.com</ulink> ." +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Tutorials.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Tutorials.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Tutorials.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,1186 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Tutorials.xml:6 +#, no-c-format +msgid "Portlet Primer" +msgstr "" + +#. Tag: title +#: Tutorials.xml:8 +#, no-c-format +msgid "JSR-168 and JSR-286 overview" +msgstr "" + +#. Tag: para +#: Tutorials.xml:9 +#, no-c-format +msgid "" +"The Portlet Specifications aims at defining portlets that can be used by any " +"<ulink url=\"http://www.jcp.org/en/jsr/detail?id=168\"> JSR-168 (Portlet " +"1.0) </ulink> or <ulink url=\"http://www.jcp.org/en/jsr/detail?id=286\"> JSR-" +"286 (Portlet 2.0) </ulink> portlet container. Most Java EE portals include " +"one, it is obviously the case for JBoss Portal which includes the JBoss " +"Portlet container supporting the two versions. This chapter gives a brief " +"overview of the Portlet Specifications but portlet developers are strongly " +"encouraged to read the <ulink url=\"http://www.jcp.org/en/jsr/detail?id=286" +"\"> JSR-286 Portlet Specification </ulink> ." +msgstr "" + +#. Tag: para +#: Tutorials.xml:27 +#, no-c-format +msgid "" +"JBoss Portal is fully JSR-286 compliant, which means any JSR-168 or JSR-286 " +"portlet behaves as it is mandated by the respective specifications inside " +"the portal." +msgstr "" + +#. Tag: title +#: Tutorials.xml:33 +#, no-c-format +msgid "Portal Pages" +msgstr "" + +#. Tag: para +#: Tutorials.xml:34 +#, no-c-format +msgid "" +"A portal can be seen as pages with different areas, and inside areas, " +"different windows, and each window having one portlet:" +msgstr "" + +#. Tag: title +#: Tutorials.xml:48 +#, no-c-format +msgid "Rendering Modes" +msgstr "" + +#. Tag: para +#: Tutorials.xml:49 +#, no-c-format +msgid "" +"A portlet can have different view modes. Three modes are defined by the JSR-" +"286 specification:" +msgstr "" + +#. Tag: para +#: Tutorials.xml:56 +#, no-c-format +msgid "" +"<emphasis>view</emphasis> - generates markup reflecting the current state of " +"the portlet." +msgstr "" + +#. Tag: para +#: Tutorials.xml:62 +#, no-c-format +msgid "" +"<emphasis>edit</emphasis> - allows a user to customize the behavior of the " +"portlet." +msgstr "" + +#. Tag: para +#: Tutorials.xml:68 +#, no-c-format +msgid "" +"<emphasis>help</emphasis> - provides information to the user as to how to " +"use the portlet." +msgstr "" + +#. Tag: title +#: Tutorials.xml:77 +#, no-c-format +msgid "Window States" +msgstr "" + +#. Tag: para +#: Tutorials.xml:78 +#, no-c-format +msgid "" +"Window states are an indicator of how much page real-estate a portlet " +"consumes on any given page. The three states defined by the JSR-168 " +"specification are:" +msgstr "" + +#. Tag: para +#: Tutorials.xml:85 +#, no-c-format +msgid "" +"<emphasis>normal</emphasis> - a portlet shares this page with other portlets." +msgstr "" + +#. Tag: para +#: Tutorials.xml:91 +#, no-c-format +msgid "" +"<emphasis>minimized</emphasis> -a portlet may show very little information, " +"or none at all." +msgstr "" + +#. Tag: para +#: Tutorials.xml:97 +#, no-c-format +msgid "" +"<emphasis>maximized</emphasis> - a portlet may be the only portlet displayed " +"on this page." +msgstr "" + +#. Tag: title +#: Tutorials.xml:107 +#, no-c-format +msgid "Tutorials" +msgstr "" + +#. Tag: para +#: Tutorials.xml:108 +#, no-c-format +msgid "" +"The tutorials contained in this chapter are targeted toward portlet " +"developers. Although they are a good starting and reference point, it is " +"highly recommend that portlet developers read and understand the <ulink url=" +"\"http://www.jcp.org/en/jsr/detail?id=286\"> JSR-286 Portlet Specification </" +"ulink>." +msgstr "" + +#. Tag: title +#: Tutorials.xml:117 +#, no-c-format +msgid "Deploying your first Portlet" +msgstr "" + +#. Tag: title +#: Tutorials.xml:119 Tutorials.xml:620 +#, no-c-format +msgid "Introduction" +msgstr "" + +#. Tag: para +#: Tutorials.xml:120 +#, no-c-format +msgid "" +"This section describes how to deploy a portlet in JBoss Portal. You will " +"find the <emphasis>SimplestHelloWorld</emphasis> portlet in the " +"<literal>jboss-epp-4.3/jboss-as/docs/portal/examples</literal> directory of " +"your distribution." +msgstr "" + +#. Tag: title +#: Tutorials.xml:130 +#, no-c-format +msgid "Compiling" +msgstr "" + +#. Tag: para +#: Tutorials.xml:131 +#, no-c-format +msgid "" +"This example is using Maven to compile and build the web archive. If you " +"don't have Maven already installed, you will find a version for your " +"operating system <ulink url=\"http://maven.apache.org/download.html\">here</" +"ulink>" +msgstr "" + +#. Tag: para +#: Tutorials.xml:137 +#, no-c-format +msgid "" +"To compile and package the application, go to the SimplestHelloWorld " +"directory and type <literal>mvn package</literal> ." +msgstr "" + +#. Tag: para +#: Tutorials.xml:143 +#, no-c-format +msgid "" +"Once successfully packaged, the result should be available in: " +"<literal>SimplestHelloWorld/target/SimplestHelloWorld-0.0.1.war</literal> . " +"Simply copy that file into <literal>JBOSS_HOME/server/default/deploy</" +"literal> , then start JBoss Application Server if it was not already started." +msgstr "" + +#. Tag: para +#: Tutorials.xml:150 +#, no-c-format +msgid "" +"You should now see a new page called <literal>SimplestHelloWorld</literal> , " +"with a window inside containing the portlet instance we have created, as " +"seen below." +msgstr "" + +#. Tag: para +#: Tutorials.xml:160 +#, no-c-format +msgid "SimplestHelloWorldPortlet deployed on a new page." +msgstr "" + +#. Tag: title +#: Tutorials.xml:168 Tutorials.xml:644 +#, no-c-format +msgid "Package Structure" +msgstr "" + +#. Tag: para +#: Tutorials.xml:169 +#, no-c-format +msgid "" +"Now that we have seen how to deploy an existing web application, let's have " +"a look inside." +msgstr "" + +#. Tag: para +#: Tutorials.xml:173 +#, no-c-format +msgid "" +"Like other Java Platform, Enterprise Edition (Java EE) applications, " +"portlets are packaged in WAR files. A typical portlet WAR file can include " +"servlets, resource bundles, images, HTML, <trademark class=\"trade" +"\">JavaServer</trademark> Pages ( <trademark class=\"trade\">JSP</" +"trademark> ), and other static or dynamic files. The following is an example " +"of the directory structure of the HelloWorldPortlet portlet:" +msgstr "" + +#. Tag: programlisting +#: Tutorials.xml:191 +#, no-c-format +msgid "" +"<![CDATA[|-- SimplestHelloWorld-0.0.1.war\n" +"| `-- WEB-INF\n" +"| |-- classes\n" +"| | `-- org\n" +"| | `-- jboss\n" +"| | `-- portal\n" +"| | `-- portlet\n" +"| | `-- samples\n" +"| | `-- SimplestHelloWorldPortlet.class\n" +"| |-- default-object.xml\n" +"| |-- portlet-instances.xml\n" +"| |-- portlet.xml\n" +"| `-- web.xml]]>" +msgstr "" + +#. Tag: para +#: Tutorials.xml:194 +#, no-c-format +msgid "" +"The compiled Java class implementing <emphasis>javax.portlet.Portlet</" +"emphasis> (through <emphasis>javax.portlet.GenericPortlet</emphasis> )" +msgstr "" + +#. Tag: para +#: Tutorials.xml:203 +#, no-c-format +msgid "" +"<emphasis>default-object.xml</emphasis> is an optional file, it is used to " +"define the layout of the portal. It can be used to define the different " +"portals, pages and windows. The same result can be obtained through the " +"administration portal. Note that the definition of the layout is stored in " +"database, this file is then used to populate the database during deployment " +"which can be very useful during development." +msgstr "" + +#. Tag: para +#: Tutorials.xml:215 +#, no-c-format +msgid "" +"<emphasis>portlet-instances.xml</emphasis> is also optional, it allows to " +"create a portlet instance from the SimpleHelloWorld portlet definition. " +"Creating instances can also be done through the administration portal. Note " +"that the definition of instances is stored in database, this file is then " +"used to populate the database during deployment which can be very useful " +"during development. Having portlet-instances.xml and default-object.xml " +"included in this package ensures that the portlet will appear directly on " +"the portal by just deploying the web application." +msgstr "" + +#. Tag: para +#: Tutorials.xml:229 +#, no-c-format +msgid "" +"This is the mandatory descriptor files for portlets. It is used during " +"deployment.." +msgstr "" + +#. Tag: para +#: Tutorials.xml:235 +#, no-c-format +msgid "This is the mandatory descriptor for web applications." +msgstr "" + +#. Tag: title +#: Tutorials.xml:242 Tutorials.xml:657 +#, no-c-format +msgid "Portlet Class" +msgstr "" + +#. Tag: para +#: Tutorials.xml:243 +#, no-c-format +msgid "Let us study the Java class in detail." +msgstr "" + +#. Tag: para +#: Tutorials.xml:244 +#, no-c-format +msgid "" +"The following file is the <filename> SimplestHelloWorldPortlet/src/main/java/" +"org/jboss/portal/portlet/samples/SimplestHelloWorldPortlet.java </filename> " +"Java source." +msgstr "" + +#. Tag: programlisting +#: Tutorials.xml:259 +#, no-c-format +msgid "" +"<![CDATA[package org.jboss.portal.portlet.samples;\n" +"\n" +"import java.io.IOException;\n" +"import java.io.PrintWriter;\n" +"\n" +"import javax.portlet.GenericPortlet;\n" +"import javax.portlet.RenderRequest;\n" +"import javax.portlet.RenderResponse;\n" +"\n" +"public class SimplestHelloWorldPortlet extends GenericPortlet\n" +"{\n" +" public void doView(RenderRequest request, \n" +" RenderResponse response) throws IOException\n" +" {\n" +" PrintWriter writer = response.getWriter();\n" +" writer.write(\"Hello World !\");\n" +" writer.close();\n" +" }\n" +"}]]>" +msgstr "" + +#. Tag: para +#: Tutorials.xml:262 +#, no-c-format +msgid "" +"All portlets must implement the <literal>javax.portlet.Portlet</literal> " +"interface. The portlet API provides a convenient implementation of this " +"interface, in the form of the <literal>javax.portlet.GenericPortlet</" +"literal> class, which among other things, implements the <literal>Portlet " +"render</literal> method to dispatch to abstract mode-specific methods to " +"make it easier to support the standard portlet modes. As well, it provides a " +"default implementation for the <literal>processAction</literal> , " +"<literal>init</literal> and <literal>destroy</literal> methods. It is " +"recommended to extend <literal>GenericPortlet</literal> for most cases." +msgstr "" + +#. Tag: para +#: Tutorials.xml:284 +#, no-c-format +msgid "" +"As we extend from <literal>GenericPortlet</literal> , and are only " +"interested in supporting the <literal>view</literal> mode, only the " +"<literal>doView</literal> method needs to be implemented, and the " +"<literal>GenericPortlet</literal> <literal>render</literal> implemention " +"calls our implementation when the <literal>view</literal> mode is requested." +msgstr "" + +#. Tag: para +#: Tutorials.xml:300 +#, no-c-format +msgid "" +"Use the <emphasis>RenderResponse</emphasis> to obtain a writer to be used to " +"produce content." +msgstr "" + +#. Tag: para +#: Tutorials.xml:307 +#, no-c-format +msgid "Write the markup to display." +msgstr "" + +#. Tag: para +#: Tutorials.xml:310 +#, no-c-format +msgid "Closing the writer." +msgstr "" + +#. Tag: title +#: Tutorials.xml:316 +#, no-c-format +msgid "Markup Fragments" +msgstr "" + +#. Tag: para +#: Tutorials.xml:317 +#, no-c-format +msgid "" +"Portlets are responsible for generating markup fragments, as they are " +"included on a page and are surrounded by other portlets. In particular, this " +"means that a portlet outputting HTML must not output any markup that cannot " +"be found in a <literal>&lt;body&gt;</literal> element." +msgstr "" + +#. Tag: title +#: Tutorials.xml:329 +#, no-c-format +msgid "Application Descriptors" +msgstr "" + +#. Tag: para +#: Tutorials.xml:330 +#, no-c-format +msgid "" +"JBoss Portal requires certain descriptors to be included in a portlet WAR " +"file. Some of these descriptors are defined by the Portlet Specification, " +"and others are specific to JBoss Portal." +msgstr "" + +#. Tag: para +#: Tutorials.xml:335 +#, no-c-format +msgid "" +"The following is an example of the <filename>SimplestHelloWorldPortlet/WEB-" +"INF/portlet.xml</filename> file. This file must adhere to its definition in " +"the JSR-286 Portlet Specification. You may define more than one portlet " +"application in this file:" +msgstr "" + +#. Tag: section +#: Tutorials.xml:341 +#, no-c-format +msgid "" +"<programlistingco> <areaspec> <area id=\"tutorials.simplest.portletname\" " +"coords=\"8\"/> <area id=\"tutorials.simplest.portletclass\" coords=\"9\"/> " +"<area id=\"tutorials.simplest.supports\" coords=\"12\"/> <area id=" +"\"tutorials.simplest.portletinfo\" coords=\"15\"/> </areaspec> " +"<programlisting><![CDATA[\n" +"<portlet-app xmlns=\"http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd" +"\"\n" +" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n" +" xsi:schemaLocation=\"http://java.sun.com/xml/ns/portlet/portlet-app_... +"xsd \n" +" http://java.sun.com/xml/ns/portlet/" +"portlet-app_2_0.xsd\"\n" +" version=\"2.0\">\n" +" <portlet>\n" +" <portlet-name>SimplestHelloWorldPortlet</portlet-name>\n" +" <portlet-class>\n" +" org.jboss.portal.portlet.samples.SimplestHelloWorldPortlet\n" +" </portlet-class>\n" +" <supports>\n" +" <mime-type>text/html</mime-type>\n" +" </supports>\n" +" <portlet-info>\n" +" <title>Simplest Hello World Portlet</title>\n" +" </portlet-info>\n" +" </portlet>\n" +"</portlet-app>]]>\n" +" </programlisting> <calloutlist> <callout arearefs=\"tutorials." +"simplest.portletname\"> <para> Define the portlet name. It does not have to " +"be the class name. </para> </callout> <callout arearefs=\"tutorials.simplest." +"portletclass\"> <para> The Fully Qualified Name (FQN) of your portlet class " +"must be declared here. </para> </callout> <callout arearefs=\"tutorials." +"simplest.supports\"> <para> The <computeroutput>&lt;supports&gt;</" +"computeroutput> element declares all of the markup types that a portlet " +"supports in the <literal>render</literal> method. This is accomplished via " +"the <computeroutput>&lt;mime-type&gt;</computeroutput> element, which is " +"required for every portlet. The declared MIME types must match the " +"capability of the portlet. As well, it allows you to pair which modes and " +"window states are supported for each markup type. All portlets must support " +"the <computeroutput>view</computeroutput> portlet mode, so this does not " +"have to be declared. Use the <computeroutput>&lt;mime-type&gt;</" +"computeroutput> element to define which markup type your portlet supports, " +"which in this example, is <computeroutput>text/html</computeroutput> . This " +"section tells the portal that it only outputs HTML. </para> </callout> " +"<callout arearefs=\"tutorials.simplest.portletinfo\"> <para> When rendered, " +"the portlet's title is displayed as the header in the portlet window, unless " +"it is overridden programmatically. In this example, the title would be " +"<computeroutput>Simplest Hello World Portlet</computeroutput> . </para> </" +"callout> </calloutlist> </programlistingco> <para> The <filename> " +"SimplestHelloWorldPortlet/WEB-INF/portlet-instances.xml </filename> file is " +"a JBoss Portal specific descriptor, that allows you to create instances of " +"portlets. The <computeroutput>&lt;portlet-ref&gt;</computeroutput> value " +"must match the <computeroutput>&lt;portlet-name&gt;</computeroutput> value " +"given in the <filename>SimplestHelloWorldPortlet/WEB-INF/portlet.xml</" +"filename> file. The <computeroutput>&lt;instance-id&gt;</computeroutput> " +"value can be named anything, but it must match the <computeroutput>&lt;" +"instance-ref&gt;</computeroutput> value given in the <filename>*-object.xml</" +"filename> file, which in this example, would be the " +"<filename>SimplestHelloWorldPortlet/WEB-INF/default-object.xml</filename> " +"file. </para> <para> The following is an example of the <filename> " +"SimplestHelloWorldPortlet/WEB-INF/portlet-instances.xml </filename> file: </" +"para> <programlisting role=\"XML\"><![CDATA[<?xml version=\"1.0\" standalone=" +"\"yes\"?>\n" +"<!DOCTYPE deployments PUBLIC\n" +" \"-//JBoss Portal//DTD Portlet Instances 2.6//EN\"\n" +" \"http://www.jboss.org/portlet/dtd/portlet-instances_2_6.dtd\">\n" +"<deployments>\n" +" <deployment>\n" +" <instance>\n" +" <instance-id>SimplestHelloWorldInstance</instance-id>\n" +" <portlet-ref>SimplestHelloWorldPortlet</portlet-ref>\n" +" </instance>\n" +" </deployment>\n" +"</deployments>]]>\n" +" </programlisting> <para> The <filename>*-object.xml</filename> " +"file is a JBoss Portal specific descriptor that allow users to define the " +"structure of their portal instances, and create and configure their windows " +"and pages. In the following example: </para> <para> <itemizedlist> " +"<listitem> <para>a portlet window is created.</para> </listitem> <listitem> " +"<para> specifies that the window displays the markup generated by the " +"<computeroutput>SimplestHelloWorldInstance</computeroutput> portlet " +"instance. </para> </listitem> <listitem> <para> the window is assigned to " +"the page that we are creating and called <computeroutput>SimplestHelloWorld</" +"computeroutput> page. </para> </listitem> <listitem> <para> the " +"<computeroutput>&lt;region&gt;</computeroutput> element specifies where the " +"window appears on the page. </para> </listitem> </itemizedlist> </para> " +"<para> The following is an example <filename>SimplestHelloWorldPortlet/WEB-" +"INF/default-object.xml</filename> file: </para> <programlistingco> " +"<areaspec> <area id=\"tutorials.simplest.parentref\" coords=\"7\"/> <area id=" +"\"tutorials.simplest.ifexists\" coords=\"8\"/> <area id=\"tutorials.simplest." +"pagename\" coords=\"12\"/> <area id=\"tutorials.simplest.windowname\" coords=" +"\"12\"/> <area id=\"tutorials.simplest.instanceref\" coords=\"13\"/> <area " +"id=\"tutorials.simplest.region\" coords=\"14\"/> <area id=\"tutorials." +"simplest.height\" coords=\"15\"/> </areaspec> <programlisting><![CDATA[<?xml " +"version=\"1.0\" encoding=\"UTF-8\"?>\n" +"<!DOCTYPE deployments PUBLIC\n" +" \"-//JBoss Portal//DTD Portal Object 2.6//EN\"\n" +" \"http://www.jboss.org/portal/dtd/portal-object_2_6.dtd\">\n" +"<deployments>\n" +" <deployment>\n" +" <parent-ref>default</parent-ref>\n" +" <if-exists>overwrite</if-exists>\n" +" <page>\n" +" <page-name>SimplestHelloWorld</page-name>\n" +" <window>\n" +" <window-name>SimplestHelloWorldWindow</window-name>\n" +" <instance-ref>SimplestHelloWorldInstance</instance-ref>\n" +" <region>center</region>\n" +" <height>0</height>\n" +" </window>\n" +" </page>\n" +" </deployment>\n" +"</deployments>]]>\n" +" </programlisting> <calloutlist> <callout arearefs=\"tutorials." +"simplest.parentref\"> <para> Tells the portal where this portlet appears. In " +"this case, <computeroutput>default.default</computeroutput> specifies that " +"the portlet appears in the portal instance named <computeroutput>default</" +"computeroutput> , and on the page named <computeroutput>default</" +"computeroutput> . </para> </callout> <callout arearefs=\"tutorials.simplest." +"ifexists\"> <para> Instructs the portal to overwrite or keep this object if " +"it already exists. Accepted values are <computeroutput>overwrite</" +"computeroutput> and <computeroutput>keep</computeroutput> . The " +"<computeroutput>overwrite</computeroutput> option destroys the existing " +"object, and creates a new one based on the content of the deployment. The " +"<computeroutput>keep</computeroutput> option maintains the existing object " +"deployment, or creates a new one if it does not exist. </para> </callout> " +"<callout arearefs=\"tutorials.simplest.pagename\"> <para> Here we are " +"creating a new page to put the new window on. We give that new page a name " +"that will be by default used on the tab of the default theme. </para> </" +"callout> <callout arearefs=\"tutorials.simplest.windowname\"> <para> A " +"<emphasis role=\"bold\">unique name</emphasis> given to the portlet window. " +"This can be named anything. </para> </callout> <callout arearefs=\"tutorials." +"simplest.instanceref\"> <para> The value of <computeroutput>&lt;instance-" +"ref&gt;</computeroutput> must match the value of one of the " +"<computeroutput>&lt;instance-id&gt;</computeroutput> elements found in the " +"<filename> HelloWorldPortlet/WEB-INF/portlet-instances.xml </filename> file. " +"</para> </callout> <callout arearefs=\"tutorials.simplest.region\"> <para> " +"Specifies where the window appears within the page layout. </para> </" +"callout> <callout arearefs=\"tutorials.simplest.height\"> <para> Specifies " +"where the window appears within the page layout. </para> </callout> </" +"calloutlist> </programlistingco>" +msgstr "" + +#. Tag: para +#: Tutorials.xml:543 +#, no-c-format +msgid "" +"The following diagram illustrates the relationship between the " +"<filename>portlet.xml</filename> , <filename>portlet-instances.xml</" +"filename> , and <filename>default-object.xml</filename> descriptors:" +msgstr "" + +#. Tag: para +#: Tutorials.xml:562 +#, no-c-format +msgid "" +"JBoss Portal 2.6 introduced the notion of <emphasis>content-type</" +"emphasis> , which is a generic mechanism to specify what content displayed " +"by a given portlet window. The <computeroutput>window</computeroutput> " +"section of the previous example, <filename>SimplestHelloWorldPortlet/WEB-INF/" +"default-object.xml</filename> , can be re-written to take advantage of the " +"new content framework. The following is an example deployment descriptor " +"that uses the new content framework:" +msgstr "" + +#. Tag: programlisting +#: Tutorials.xml:574 +#, no-c-format +msgid "" +"<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" +"<!DOCTYPE deployments PUBLIC\n" +" \"-//JBoss Portal//DTD Portal Object 2.6//EN\"\n" +" \"http://www.jboss.org/portal/dtd/portal-object_2_6.dtd\">\n" +"<deployments>\n" +" <deployment>\n" +" <parent-ref>default.default</parent-ref>\n" +" <if-exists>overwrite</if-exists>\n" +" <window>\n" +" <window-name>SimplestHelloWorldWindow</window-name>\n" +" <content>\n" +" <content-type>portlet</content-type>\n" +" <content-uri>SimplestHelloWorldInstance</content-uri>\n" +" </content>\n" +" <region>center</region>\n" +" <height>1</height>\n" +" </window>\n" +" </deployment>\n" +"</deployments>]]>" +msgstr "" + +#. Tag: para +#: Tutorials.xml:575 +#, no-c-format +msgid "" +"This declaration is equivalent to the previous " +"<filename>SimplestHelloWorldPortlet/WEB-INF/default-object.xml</filename> " +"example. Use <computeroutput>&lt;content-type&gt;</computeroutput> to " +"specify the content to display. In this example, the content being displayed " +"by the <computeroutput>SimplestHelloWorldWindow</computeroutput> is a " +"<computeroutput>portlet</computeroutput> . The <computeroutput>&lt;content-" +"uri&gt;</computeroutput> element specifies which content to display, which " +"in this example, is the <computeroutput>SimplestHelloWorldInstance</" +"computeroutput> :" +msgstr "" + +#. Tag: programlisting +#: Tutorials.xml:592 +#, no-c-format +msgid "" +"<![CDATA[<content>\n" +" <content-type>portlet</content-type>\n" +" <content-uri>SimplestHelloWorldInstance</content-uri>\n" +"</content>]]>" +msgstr "" + +#. Tag: para +#: Tutorials.xml:593 +#, no-c-format +msgid "" +"To display certain content or a file, use the <computeroutput>cms</" +"computeroutput> content-type, with the <computeroutput>&lt;content-uri&gt;</" +"computeroutput> element being the path to the file in the CMS. This behavior " +"is pluggable: you can plug in almost any type of content." +msgstr "" + +#. Tag: title +#: Tutorials.xml:602 +#, no-c-format +msgid "Beware of context-path change" +msgstr "" + +#. Tag: para +#: Tutorials.xml:603 +#, no-c-format +msgid "" +"If the context-path change the portal may not be able to find a reference on " +"your portlets anymore. For that reason it's recommended to add the following " +"descriptor <filename>WEB-INF/jboss-portlet.xml</filename> which is not " +"mandatory:" +msgstr "" + +#. Tag: programlisting +#: Tutorials.xml:611 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!DOCTYPE portlet-app PUBLIC\n" +" \"-//JBoss Portal//DTD JBoss Portlet 2.6//EN\"\n" +" \"http://www.jboss.org/portal/dtd/jboss-portlet_2_6.dtd\">\n" +"\n" +"<portlet-app>\n" +" <app-id>SimplestHelloWorld</app-id>\n" +"</portlet-app>]]>" +msgstr "" + +#. Tag: title +#: Tutorials.xml:615 +#, no-c-format +msgid "<trademark class=\"trade\">JavaServer</trademark> Pages Portlet Example" +msgstr "" + +#. Tag: para +#: Tutorials.xml:621 +#, no-c-format +msgid "" +"Now we will add more features to the previous example and also use a JSP " +"page to render the markup. We will use the portlet tag library to generate " +"links to our portlet in different ways and use the other standard portlet " +"modes. This example can be found in the directory <literal>jboss-epp-4.3/" +"jboss-as/docs/portal/examples/JSPHelloUser</literal>. Use <literal>mvn " +"package</literal> then copy <filename>JSPHelloUser/target/JSPHelloUser-0.0.1." +"war</filename> in the <literal>deploy</literal> directory of JBoss " +"Application Server. Point your browser to <literal></literal>, you should " +"see the following:" +msgstr "" + +#. Tag: para +#: Tutorials.xml:638 +#, no-c-format +msgid "" +"The <literal>EDIT</literal> button only appears with logged-in users, which " +"is not the case on the screenshot" +msgstr "" + +#. Tag: para +#: Tutorials.xml:645 +#, no-c-format +msgid "" +"The structure doesn't change much at the exception of adding some JSP files " +"detailed later." +msgstr "" + +#. Tag: para +#: Tutorials.xml:649 +#, no-c-format +msgid "" +"The JSPHelloUser portlet contains the traditional portlet and JBoss Portal " +"specific application descriptors. The following is an example of the " +"directory structure of the JSPHelloUser portlet:" +msgstr "" + +#. Tag: programlisting +#: Tutorials.xml:654 +#, no-c-format +msgid "" +"<![CDATA[JSPHelloUser-0.0.1.war\n" +" |-- META-INF\n" +" | |-- MANIFEST.MF\n" +" | `-- maven\n" +" | `-- org.jboss.portal.example\n" +" | `-- JSPHelloUser\n" +" | |-- pom.properties\n" +" | `-- pom.xml\n" +" |-- WEB-INF\n" +" | |-- classes\n" +" | | `-- org\n" +" | | `-- jboss\n" +" | | `-- portal\n" +" | | `-- portlet\n" +" | | `-- samples\n" +" | | `-- JSPHelloUserPortlet.class\n" +" | |-- default-object.xml\n" +" | |-- jboss-portlet.xml\n" +" | |-- portlet-instances.xml\n" +" | |-- portlet.xml\n" +" | `-- web.xml\n" +" `-- jsp\n" +" |-- edit.jsp\n" +" |-- hello.jsp\n" +" |-- help.jsp\n" +" `-- welcome.jsp]]>" +msgstr "" + +#. Tag: para +#: Tutorials.xml:658 +#, no-c-format +msgid "Let's study the Java class in detail." +msgstr "" + +#. Tag: para +#: Tutorials.xml:659 +#, no-c-format +msgid "" +"The following file is the <filename> JSPHelloUser/src/main/java/org/jboss/" +"portal/portlet/samples/JSPHelloUserPortlet.java </filename> Java source. It " +"is split in different pieces." +msgstr "" + +#. Tag: section +#: Tutorials.xml:665 +#, no-c-format +msgid "" +"<programlistingco> <areaspec> <area id=\"tutorials.jsphello.doView\" coords=" +"\"18\"/> <area id=\"tutorials.jsphello.renderParameter\" coords=\"21\"/> " +"<area id=\"tutorials.jsphello.requestDispatcher\" coords=\"25\"/> <area id=" +"\"tutorials.jsphello.include\" coords=\"26\"/> </areaspec> <programlisting " +"role=\"JAVA\"><![CDATA[package org.jboss.portal.portlet.samples;\n" +"package org.jboss.portal.portlet.samples;\n" +"\n" +"import java.io.IOException;\n" +"\n" +"import javax.portlet.ActionRequest;\n" +"import javax.portlet.ActionResponse;\n" +"import javax.portlet.GenericPortlet;\n" +"import javax.portlet.PortletException;\n" +"import javax.portlet.PortletRequestDispatcher;\n" +"import javax.portlet.RenderRequest;\n" +"import javax.portlet.RenderResponse;\n" +"import javax.portlet.UnavailableException;\n" +"\n" +"public class JSPHelloUserPortlet extends GenericPortlet\n" +"{\n" +" \n" +" public void doView(RenderRequest request, RenderResponse response)\n" +" throws PortletException, IOException\n" +" {\n" +" String sYourName = (String) request.getParameter(\"yourname\");\n" +" if (sYourName != null)\n" +" {\n" +" request.setAttribute(\"yourname\", sYourName);\n" +" PortletRequestDispatcher prd = \n" +" getPortletContext().getRequestDispatcher(\"/jsp/hello.jsp\");\n" +" prd.include(request, response);\n" +" }\n" +" else\n" +" {\n" +" PortletRequestDispatcher prd = getPortletContext()." +"getRequestDispatcher(\"/jsp/welcome.jsp\");\n" +" prd.include(request, response);\n" +" }\n" +" }\n" +"...]]></programlisting> <calloutlist> <callout arearefs=\"tutorials.jsphello." +"doView\"> <para> As in the first portlet, we override the <emphasis>doView</" +"emphasis> method. </para> </callout> <callout arearefs=\"tutorials.jsphello." +"renderParameter\"> <para> Here we try to obtain the value of the render " +"parameter names <literal>yourname</literal> . If defined we want to redirect " +"to the <filename>hello.jsp</filename> JSP page, otherwise to the " +"<filename>welcome.jsp</filename> JSP page. </para> </callout> <callout " +"arearefs=\"tutorials.jsphello.requestDispatcher\"> <para> Very similar to " +"the Servlet way, we get a request dispatcher on a file located within the " +"web archive. </para> </callout> <callout arearefs=\"tutorials.jsphello." +"include\"> <para> The last step is to perform the inclusion of the markup " +"obtained from the JSP. </para> </callout> </calloutlist> </programlistingco> " +"<para> We have seen the <literal>VIEW</literal> portlet mode, the spec " +"defines two other modes that can be used called <literal>EDIT</literal> and " +"<literal>HELP</literal> . In order to enable those modes, they will need to " +"be defined in the <filename>portlet.xml</filename> descriptor as we will see " +"later. Having those modes defined will enable the corresponding buttons on " +"the portlet's window. </para> <para> The generic portlet that is inherited " +"dispatches the different views to methods named: <literal>doView</literal> , " +"<literal>doHelp</literal> and <literal>doEdit</literal> . Let's watch the " +"code for those two last portlet modes. </para> <programlisting role=\"JAVA" +"\"><![CDATA[...\n" +" protected void doHelp(RenderRequest rRequest, RenderResponse rResponse) " +"throws PortletException, IOException,\n" +" UnavailableException\n" +" {\n" +" rResponse.setContentType(\"text/html\");\n" +" PortletRequestDispatcher prd = getPortletContext().getRequestDispatcher" +"(\"/jsp/help.jsp\");\n" +" prd.include(rRequest, rResponse);\n" +" }\n" +"\n" +" protected void doEdit(RenderRequest rRequest, RenderResponse rResponse) " +"throws PortletException, IOException,\n" +" UnavailableException\n" +" {\n" +" rResponse.setContentType(\"text/html\");\n" +" PortletRequestDispatcher prd = getPortletContext().getRequestDispatcher" +"(\"/jsp/edit.jsp\");\n" +" prd.include(rRequest, rResponse);\n" +" }\n" +"...]]></programlisting> <para> If you have read the portlet specification " +"carefully you should have notice that portlet calls happen in one or two " +"phases. One when the portlet is just rendered, two when the portlet is " +"actionned then rendered. An action phase is a phase where some state change. " +"The render phase will have access to render parameters that will be passed " +"each time the portlet is refreshed (with the exception of caching " +"capabilities). </para> <para> The code to be executed during an action has " +"to be implemented in the <emphasis>processAction</emphasis> method of the " +"portlet. </para> <programlistingco> <areaspec> <area id=\"tutorials.jsphello." +"processAction\" coords=\"2\"/> <area id=\"tutorials.jsphello." +"getActionParameter\" coords=\"5\"/> <area id=\"tutorials.jsphello." +"setRenderParameter\" coords=\"6\"/> </areaspec> <programlisting role=\"JAVA" +"\"><![CDATA[...\n" +" public void processAction(ActionRequest aRequest, ActionResponse " +"aResponse) throws PortletException, IOException,\n" +" UnavailableException\n" +" {\n" +" String sYourname = (String) aRequest.getParameter(\"yourname\");\n" +" aResponse.setRenderParameter(\"yourname\", sYourname);\n" +" }\n" +"...]]></programlisting> <calloutlist> <callout arearefs=\"tutorials.jsphello." +"processAction\"> <para> <literal>processAction</literal> is the method from " +"GernericPorlet to override for the <emphasis>action</emphasis> phase. </" +"para> </callout> <callout arearefs=\"tutorials.jsphello.getActionParameter" +"\"> <para> Here we retrieve the parameter obtained through an " +"<emphasis>action URL</emphasis> . </para> </callout> <callout arearefs=" +"\"tutorials.jsphello.setRenderParameter\"> <para> Here we need to keep the " +"value of <literal>yourname</literal> to make it available in the rendering " +"phase. With the previous line, we are simply copying an action parameter to " +"a render parameter for the sake of this example. </para> </callout> </" +"calloutlist> </programlistingco>" +msgstr "" + +#. Tag: title +#: Tutorials.xml:780 +#, no-c-format +msgid "" +"<trademark class=\"trade\">JSP</trademark> files and the Portlet Tag Library" +msgstr "" + +#. Tag: para +#: Tutorials.xml:784 +#, no-c-format +msgid "Let's have a look inside the JSP pages." +msgstr "" + +#. Tag: para +#: Tutorials.xml:785 +#, no-c-format +msgid "" +"The <filename>help.jsp</filename> and <filename>edit.jsp</filename> files " +"are very simple, they simply display some text. Note that we used CSS styles " +"as defined in the portlet specification. It ensures that the portlet will " +"look \"good\" within the theme and accross portal vendors." +msgstr "" + +#. Tag: programlisting +#: Tutorials.xml:794 +#, no-c-format +msgid "" +"<![CDATA[<div class=\"portlet-section-header\">Help mode</div>\n" +"<div class=\"portlet-section-body\">This is the help mode, a convenient " +"place to give the user some help information.</div>]]>" +msgstr "" + +#. Tag: programlisting +#: Tutorials.xml:795 +#, no-c-format +msgid "" +"<![CDATA[<div class=\"portlet-section-header\">Edit mode</div>\n" +"<div class=\"portlet-section-body\">This is the edit mode, a convenient " +"place to let the user change his portlet preferences.</div>]]>" +msgstr "" + +#. Tag: para +#: Tutorials.xml:796 +#, no-c-format +msgid "" +"Now let's have a look at the landing page, it contains the links and form to " +"call our portlet:" +msgstr "" + +#. Tag: programlisting +#: Tutorials.xml:810 +#, no-c-format +msgid "" +"<![CDATA[<%@ taglib uri=\"http://java.sun.com/portlet\" prefix=\"portlet\" %" +">\n" +"\n" +"<div class=\"portlet-section-header\">Welcome !</div>\n" +"\n" +"<br/>\n" +"\n" +"<div class=\"portlet-font\">Welcome on the JSP Hello User portlet,\n" +"my name is JBoss Portal. What's yours ?</div>\n" +"\n" +"<br/>\n" +"\n" +"<div class=\"portlet-font\">Method 1: We simply pass the parameter to the " +"render phase:<br/>\n" +"<a href=\"<portlet:renderURL><portlet:param name=\"yourname\" value=\"John " +"Doe\"/>\n" +" </portlet:renderURL>\">John Doe</a></div>\n" +"\n" +"<br/>\n" +"\n" +"<div class=\"portlet-font\">Method 2: We pass the parameter to the render " +"phase, using valid XML:\n" +"Please check the source code to see the difference with Method 1.\n" +"<portlet:renderURL var=\"myRenderURL\">\n" +" <portlet:param name=\"yourname\" value='John Doe'/>\n" +"</portlet:renderURL>\n" +"<br/>\n" +"<a href=\"<%= myRenderURL %>\">John Doe</a></div>\n" +"\n" +"<br/>\n" +"\n" +"<div class=\"portlet-font\">Method 3: We use a form:<br/>\n" +"\n" +"<portlet:actionURL var=\"myActionURL\"/>\n" +"<form action=\"<%= myActionURL %>\" method=\"POST\">\n" +" <span class=\"portlet-form-field-label\">Name:</span>\n" +" <input class=\"portlet-form-input-field\" type=\"text\" name=" +"\"yourname\"/>\n" +" <input class=\"portlet-form-button\" type=\"Submit\"/>\n" +"</form>\n" +"</div>]]>" +msgstr "" + +#. Tag: para +#: Tutorials.xml:813 +#, no-c-format +msgid "Since we will use the portlet taglib, we first need to declare it." +msgstr "" + +#. Tag: para +#: Tutorials.xml:818 +#, no-c-format +msgid "" +"The first method showed here is the simplest one, <literal>portlet:" +"renderURL</literal> will create a URL that will call the render phase of the " +"current portlet and append the result at the place of the markup (Here " +"within a tag...). We also added a parameter directly on the URL." +msgstr "" + +#. Tag: para +#: Tutorials.xml:827 +#, no-c-format +msgid "" +"In this method instead of having a tag within another tag, which is not XML " +"valid, we use the <literal>var</literal> attribute. Instead of printing the " +"url the <literal>portlet:renderURL</literal> tag will store the result in " +"the referenced variable ( <literal>myRenderURL</literal> in our case)." +msgstr "" + +#. Tag: para +#: Tutorials.xml:839 +#, no-c-format +msgid "" +"The variable <literal>myRenderURL</literal> is used like any other JSP " +"variable." +msgstr "" + +#. Tag: para +#: Tutorials.xml:846 +#, no-c-format +msgid "" +"The third method mixes form submission and action request. Like in the " +"second method, we used a temporary variable to put the created URL into." +msgstr "" + +#. Tag: para +#: Tutorials.xml:853 +#, no-c-format +msgid "The action URL is used in the HTML form." +msgstr "" + +#. Tag: para +#: Tutorials.xml:858 +#, no-c-format +msgid "" +"On the third method, first the action phase is triggered then later in the " +"request, the render phase is triggered, which output some content back to " +"the web browser based on the available render parameters." +msgstr "" + +#. Tag: title +#: Tutorials.xml:871 +#, no-c-format +msgid "" +"<trademark class=\"trade\">JSF</trademark> example using the JBoss Portlet " +"Bridge" +msgstr "" + +#. Tag: para +#: Tutorials.xml:875 +#, no-c-format +msgid "" +"In order to write a portlet using JSF we need a piece of software called " +"'bridge' that lets us write a portlet application as if it was a JSF " +"application, the bridge takes care of the interactions between the two " +"layers." +msgstr "" + +#. Tag: para +#: Tutorials.xml:878 +#, no-c-format +msgid "" +"Such an example is available in jboss-epp-4.3/jboss-as/docs/portal/examples/" +"JSFHelloUser, it uses the JBoss Portlet Bridge. The configuration is " +"slightly different from a JSP application, since it is a bit tricky it is " +"usally a good idea to copy an existing application that starting from " +"scratch." +msgstr "" + +#. Tag: para +#: Tutorials.xml:881 +#, no-c-format +msgid "" +"First, as any JSF application, the file <literal>faces-config.xml</literal> " +"is required. It includes the following required information in it: " +"<programlisting role=\"XML\"><![CDATA[<faces-config>\n" +"...\n" +" <application>\n" +" <view-handler>org.jboss.portletbridge.application.PortletViewHandler</" +"view-handler>\n" +" <state-manager>org.jboss.portletbridge.application." +"PortletStateManager</state-manager>\n" +" </application>\n" +"...\n" +"</faces-config> ]]></programlisting> The portlet bridge libraries must be " +"available and are usually bundled with the <literal>WEB-INF/lib</literal> " +"directory of the web archive." +msgstr "" + +#. Tag: para +#: Tutorials.xml:886 +#, no-c-format +msgid "" +"The other difference compare to a regular portlet application, can be found " +"in the portlet descriptor. All details about it can be found in the JSR-301 " +"specification that the JBoss Portlet Bridge implements. <programlistingco> " +"<areaspec> <area id=\"tutorials.jsf.portlet\" coords=\"9\"/> <area id=" +"\"tutorials.jsf.view\" coords=\"21\"/> <area id=\"tutorials.jsf.edit\" " +"coords=\"26\"/> <area id=\"tutorials.jsf.help\" coords=\"31\"/> </areaspec> " +"<programlisting role=\"XML\"><![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8" +"\"?>\n" +"<portlet-app xmlns=\"http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd" +"\"\n" +" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n" +" xsi:schemaLocation=\"http://java.sun.com/xml/ns/portlet/portlet-app_... +"xsd \n" +" http://java.sun.com/xml/ns/portlet/" +"portlet-app_2_0.xsd\"\n" +" version=\"2.0\">\n" +" <portlet>\n" +" <portlet-name>JSFHelloUserPortlet</portlet-name>\n" +" <portlet-class>javax.portlet.faces.GenericFacesPortlet</portlet-" +"class>\n" +" <supports>\n" +" <mime-type>text/html</mime-type>\n" +" <portlet-mode>view</portlet-mode>\n" +" <portlet-mode>edit</portlet-mode>\n" +" <portlet-mode>help</portlet-mode>\n" +" </supports>\n" +" <portlet-info>\n" +" <title>JSF Hello User Portlet</title>\n" +" </portlet-info>\n" +" \n" +" <init-param>\n" +" <name>javax.portlet.faces.defaultViewId.view</name>\n" +" <value>/jsf/welcome.jsp</value>\n" +" </init-param>\n" +"\n" +" <init-param>\n" +" <name>javax.portlet.faces.defaultViewId.edit</name>\n" +" <value>/jsf/edit.jsp</value>\n" +" </init-param>\n" +"\n" +" <init-param>\n" +" <name>javax.portlet.faces.defaultViewId.help</name>\n" +" <value>/jsf/help.jsp</value>\n" +" </init-param>\n" +"\n" +" </portlet>\n" +"</portlet-app>]]></programlisting> <calloutlist> <callout arearefs=" +"\"tutorials.jsf.portlet\"><para>All JSF portlets define <literal>javax." +"portlet.faces.GenericFacesPortlet</literal> as portlet class. This class is " +"part of the JBoss Portlet Bridge</para></callout> <callout arearefs=" +"\"tutorials.jsf.view\"><para>This is a mandatory parameter to define what's " +"the default page to display.</para></callout> <callout arearefs=\"tutorials." +"jsf.edit\"><para>This parameter defines which page to display on the 'edit' " +"mode.</para></callout> <callout arearefs=\"tutorials.jsf.help\"><para>This " +"parameter defines which page to display on the 'help' mode.</para></callout> " +"</calloutlist> </programlistingco>" +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/URLs.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/URLs.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/URLs.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,165 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: URLs.xml:7 +#, no-c-format +msgid "Portal URLs" +msgstr "" + +#. Tag: title +#: URLs.xml:9 +#, no-c-format +msgid "Introduction to Portals" +msgstr "" + +#. Tag: para +#: URLs.xml:10 +#, no-c-format +msgid "" +"Portal URLs are often very complicated; however, it is possible to setup " +"entry points in portals that follow simple patterns." +msgstr "" + +#. Tag: para +#: URLs.xml:13 +#, no-c-format +msgid "" +"Each portal container can contain multiple portals. Within a given portal, " +"windows are organized into pages, with a page being a collection of windows " +"associated to a name:" +msgstr "" + +#. Tag: para +#: URLs.xml:23 +#, no-c-format +msgid "" +"Before reading the following sections, be familiar with how to define pages " +"and portal. Refer to <xref linkend=\"desc_example_page\"/> for details." +msgstr "" + +#. Tag: title +#: URLs.xml:28 +#, no-c-format +msgid "Accessing a Portal" +msgstr "" + +#. Tag: para +#: URLs.xml:29 +#, no-c-format +msgid "" +"The <computeroutput>default</computeroutput> portal is used when no portal " +"is specified. How selection is done:" +msgstr "" + +#. Tag: para +#: URLs.xml:35 +#, no-c-format +msgid "" +"<computeroutput>/portal/</computeroutput> points to the default page of the " +"default portal." +msgstr "" + +#. Tag: para +#: URLs.xml:40 +#, no-c-format +msgid "" +"<computeroutput>/portal/<replaceable>portal-name</replaceable>/</" +"computeroutput> points to the default page of the <replaceable>portal-name</" +"replaceable> portal." +msgstr "" + +#. Tag: para +#: URLs.xml:45 +#, no-c-format +msgid "" +"A default link like http://localhost:8080/portal/portal/foo/bar can be " +"decomposed as hostname:port:/contextPath/'portal'/portalName/pageName. The " +"'portal' part can be modified in: <literal>jboss-portal.sar/portal-core.sar/" +"META-INF/jboss-service.xml</literal> by modifying the attribute " +"<literal>Path</literal> on the two following MBEans: <literal>portal:" +"commandFactory=Delegate,path=portal</literal> and <literal>portal:" +"commandFactory=Delegate,path=portal\"</literal>, however this cannot be " +"changed to '/'." +msgstr "" + +#. Tag: title +#: URLs.xml:51 +#, no-c-format +msgid "Note" +msgstr "" + +#. Tag: para +#: URLs.xml:51 +#, no-c-format +msgid "" +"The default page or portal can be specified either by using the admin " +"portlet or by using the XML descriptors as explained in the <xref linkend=" +"\"xml.default.objectname.property\"/>." +msgstr "" + +#. Tag: title +#: URLs.xml:55 +#, no-c-format +msgid "Accessing a Page" +msgstr "" + +#. Tag: para +#: URLs.xml:56 +#, no-c-format +msgid "" +"Each portal can have multiple pages, with each portal having a default page. " +"When a portal is selected, a page must be used, and all windows in that page " +"are rendered. The page selection mechanism is as follows:" +msgstr "" + +#. Tag: para +#: URLs.xml:59 +#, no-c-format +msgid "" +"<computeroutput>/portal/default/<replaceable>page-name</replaceable></" +"computeroutput> renders the <replaceable>page-name</replaceable> page." +msgstr "" + +#. Tag: title +#: URLs.xml:64 +#, no-c-format +msgid "Accessing CMS Content" +msgstr "" + +#. Tag: para +#: URLs.xml:65 +#, no-c-format +msgid "" +"The <emphasis>CMSPortlet</emphasis> delivers content transparently, without " +"modifying the displayed URL. It is desirable to display binary content, such " +"as GIF, JPEG, PDF, ZIP, and so on, outside of the confines of the portal. " +"For example, <computeroutput>/content/default/images/jboss_logo.gif</" +"computeroutput> displays the <computeroutput>jboss_logo.gif</computeroutput> " +"file outside of the portal." +msgstr "" + +#. Tag: para +#: URLs.xml:68 +#, no-c-format +msgid "" +"To display content outside of the portal, the portal interprets any path " +"beginning with <computeroutput>/content</computeroutput> as a request for " +"CMS content. As long as the <computeroutput>&lt;mime-type&gt;</" +"computeroutput> is not <computeroutput>text/html</computeroutput>, or " +"<computeroutput>text/text</computeroutput>, and the path to the content " +"begins with <computeroutput>/content</computeroutput>, the content is " +"rendered independently, outside of the portal." +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/WSRP.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/WSRP.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/WSRP.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,1345 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: WSRP.xml:6 +#, no-c-format +msgid "Web Services for Remote Portlets (WSRP)" +msgstr "" + +#. Tag: title +#: WSRP.xml:9 +#, no-c-format +msgid "Introduction" +msgstr "" + +#. Tag: para +#: WSRP.xml:10 +#, no-c-format +msgid "" +"The Web Services for Remote Portlets specification defines a web service " +"interface for accessing and interacting with interactive presentation-" +"oriented web services. It has been produced through the efforts of the Web " +"Services for Remote Portlets (WSRP) OASIS Technical Committee. It is based " +"on the requirements gathered and on the concrete proposals made to the " +"committee." +msgstr "" + +#. Tag: para +#: WSRP.xml:16 +#, no-c-format +msgid "Scenarios that motivate WSRP functionality include:" +msgstr "" + +#. Tag: para +#: WSRP.xml:18 +#, no-c-format +msgid "" +"Content hosts, such as portal servers, providing Portlets as presentation-" +"oriented web services that can be used by aggregation engines." +msgstr "" + +#. Tag: para +#: WSRP.xml:21 +#, no-c-format +msgid "" +"Aggregating frameworks, including portal servers, consuming presentation-" +"oriented web services offered by content providers and integrating them into " +"the framework." +msgstr "" + +#. Tag: para +#: WSRP.xml:27 +#, no-c-format +msgid "" +"More information on WSRP can be found on the <ulink url=\"http://www.oasis-" +"open.org/committees/tc_home.php?wg_abbrev=wsrp\">official website for WSRP</" +"ulink>. We suggest reading the <ulink url=\"http://www.oasis-open.org/" +"committees/tc_home.php?wg_abbrev=wsrp\">primer </ulink> for a good, albeit " +"technical, overview of WSRP." +msgstr "" + +#. Tag: title +#: WSRP.xml:35 +#, no-c-format +msgid "Level of support in JBoss Portal" +msgstr "" + +#. Tag: para +#: WSRP.xml:36 +#, no-c-format +msgid "" +"The WSRP Technical Committee defined <ulink url=\"http://www.oasis-open.org/" +"committees/download.php/3073\">WSRP Use Profiles</ulink> to help with WSRP " +"interoperability. We will refer to terms defined in that document in this " +"section." +msgstr "" + +#. Tag: para +#: WSRP.xml:42 +#, no-c-format +msgid "" +"JBoss Portal provides a Simple level of support for our WSRP Producer except " +"that out-of-band registration is not currently handled. We support in-band " +"registration and persistent local state (which are defined at the Complex " +"level)." +msgstr "" + +#. Tag: para +#: WSRP.xml:47 +#, no-c-format +msgid "" +"On the Consumer side, JBoss Portal provides a Medium level of support for " +"WSRP, except that we only handle HTML markup (as Portal itself doesn't " +"handle other markup types). We do support explicit portlet cloning and we " +"fully support the PortletManagement interface." +msgstr "" + +#. Tag: para +#: WSRP.xml:52 +#, no-c-format +msgid "" +"As far as caching goes, we have Level 1 Producer and Consumer. We support " +"Cookie handling properly on the Consumer and our Producer requires " +"initialization of cookies (as we have found that it improved interoperabilty " +"with some consumers). We don't support custom window states or modes, as " +"Portal doesn't either. We do, however, support CSS on both the Producer " +"(though it's more a function of the portlets than inherent Producer " +"capability) and Consumer." +msgstr "" + +#. Tag: para +#: WSRP.xml:59 +#, no-c-format +msgid "" +"While we provide a complete implementation of WSRP 1.0, we do need to go " +"through the <ulink url=\"http://www.oasis-open.org/committees/download." +"php/6018\">Conformance statements</ulink> and perform more interoperability " +"testing (an area that needs to be better supported by the WSRP Technical " +"Committee and Community at large)." +msgstr "" + +#. Tag: title +#: WSRP.xml:67 +#, no-c-format +msgid "Deploying JBoss Portal's WSRP services" +msgstr "" + +#. Tag: para +#: WSRP.xml:68 +#, no-c-format +msgid "" +"JBoss Portal provides a complete support of WSRP 1.0 standard interfaces and " +"offers both consumer and producer services. WSRP support is provided by the " +"<filename>portal-wsrp.sar</filename> service archive, included in the main " +"<filename>jboss-portal.sar</filename> service archive, if you've obtained " +"JBoss Portal from a binary distribution. If you don't intend on using WSRP, " +"we recommend that you remove <filename>portal-wspr.sar</filename> from the " +"main <filename>jboss-portal.sar</filename> service archive." +msgstr "" + +#. Tag: para +#: WSRP.xml:75 +#, no-c-format +msgid "" +"If you've obtained the source distribution of JBoss Portal, you need to " +"build and deploy the WSRP service separately. Please follow the instructions " +"on how to install <ulink url=\"http://docs.jboss.com/jbportal/v2.6/reference-" +"guide/en/html/installation.html#install_source\">JBoss Portal from the " +"sources</ulink>. Once this is done, navigate to " +"<filename>JBOSS_PORTAL_HOME_DIRECTORY/wsrp</filename> and type: " +"<command>build deploy</command> At the end of the build process, " +"<filename>portal-wsrp.sar</filename> is copied to <filename>JBOSS_HOME/" +"server/default/deploy</filename>." +msgstr "" + +#. Tag: title +#: WSRP.xml:85 +#, no-c-format +msgid "" +"Considerations to use WSRP when running Portal on a non-default port or " +"hostname" +msgstr "" + +#. Tag: para +#: WSRP.xml:86 +#, no-c-format +msgid "" +"If you have modified the port number on which Portal runs or bound your " +"Application Server to a specific host name, you will also need <ulink url=" +"\"http://wiki.jboss.org/wiki/Wiki.jsp?page=WSRPChangePorts\">update the port " +"and/or hostname information for WSRP</ulink> as found on <ulink url=\"http://" +"wiki.jboss.org/wiki/Wiki.jsp?page=JBossPortal\">JBoss Portal's wiki</ulink>." +msgstr "" + +#. Tag: title +#: WSRP.xml:95 +#, no-c-format +msgid "Considerations to use WSRP with SSL" +msgstr "" + +#. Tag: para +#: WSRP.xml:96 +#, no-c-format +msgid "" +"It is possible to use WSRP over SSL for secure exchange of data. Please " +"refer to the <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=WSRPUseSSL" +"\">instructions</ulink> on how to do so from <ulink url=\"http://wiki.jboss." +"org/wiki/Wiki.jsp?page=JBossPortal\">JBoss Portal's wiki</ulink>." +msgstr "" + +#. Tag: title +#: WSRP.xml:105 +#, no-c-format +msgid "Making a portlet remotable" +msgstr "" + +#. Tag: para +#: WSRP.xml:106 +#, no-c-format +msgid "" +"JBoss Portal does <emphasis role=\"bold\">NOT</emphasis>, by default, expose " +"local portlets for consumption by remote WSRP consumers. In order to make a " +"portlet remotely available, it must be made \"remotable\" by adding a " +"<literal>remotable</literal> element to the <filename>jboss-portlet.xml</" +"filename> deployment descriptor for that portlet. If a <filename>jboss-" +"portlet.xml</filename> file does not exist, one must be added to the " +"<filename>WEB-INF</filename> folder of the web application containing the " +"portlet." +msgstr "" + +#. Tag: para +#: WSRP.xml:112 +#, no-c-format +msgid "" +"In the following example, the \"BasicPortlet\" portlet is specified as being " +"remotable. The <literal>remotable</literal> element is optional." +msgstr "" + +#. Tag: programlisting +#: WSRP.xml:116 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<?xml version=\"1.0\" standalone=\"yes\"?>\n" +"<!DOCTYPE portlet-app PUBLIC \"-//JBoss Portal//DTD JBoss Portlet 2.6//EN\"\n" +" \"http://www.jboss.org/portal/dtd/jboss-portlet_2_6.dtd\">\n" +"<portlet-app>\n" +" <portlet>\n" +" <portlet-name>BasicPortlet</portlet-name>\n" +" <remotable>true</remotable>\n" +" </portlet>\n" +"</portlet-app>]]>" +msgstr "" + +#. Tag: para +#: WSRP.xml:118 +#, no-c-format +msgid "" +"It is also possible to specify that all the portlets declared within a given " +"<filename>jboss-portlet.xml</filename> file have a specific \"remotable\" " +"status by default. This is done by adding a single <literal>remotable</" +"literal> element to the root <literal>portlet-app</literal> element. " +"Usually, this feature will be used to remotely expose several portlets " +"without having to specify the status for all the declared portlets. Let's " +"look at an example:" +msgstr "" + +#. Tag: programlisting +#: WSRP.xml:125 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<?xml version=\"1.0\" standalone=\"yes\"?>\n" +"<!DOCTYPE portlet-app PUBLIC\n" +" \"-//JBoss Portal//DTD JBoss Portlet 2.6//EN\"\n" +" \"http://www.jboss.org/portal/dtd/jboss-portlet_2_6.dtd\">\n" +"<portlet-app>\n" +" <remotable>true</remotable>\n" +" <portlet>\n" +" <portlet-name>RemotelyExposedPortlet</portlet-name>\n" +" ...\n" +" </portlet>\n" +" <portlet>\n" +" <portlet-name>NotRemotelyExposedPortlet</portlet-name>\n" +" <remotable>false</remotable>\n" +" ...\n" +" </portlet>\n" +"</portlet-app>]]>" +msgstr "" + +#. Tag: para +#: WSRP.xml:128 +#, no-c-format +msgid "" +"In the example above, we defined two portlets with a default \"remotable\" " +"status set to true. This means that all portlets defined in this descriptor " +"are, by default, exposed remotely by JBoss Portal's WSRP producer. Note, " +"however, that it is possible to override the default behavior by adding a " +"<literal>remotable</literal> element to a portlet description. In that case, " +"the \"remotable\" status defined by the portlet takes precedence over the " +"default. In the example above, the <literal>RemotelyExposedPortlet</literal> " +"inherits the \"remotable\" status defined by default since it does not " +"specify a <literal>remotable</literal> element in its description. The " +"<literal>NotRemotelyExposedPortlet</literal>, however, overrides the default " +"behavior and is not remotely exposed. Note that in the absence of a top-" +"level <literal>remotable</literal> element, portlets are NOT remotely " +"exposed." +msgstr "" + +#. Tag: title +#: WSRP.xml:142 +#, no-c-format +msgid "Consuming JBoss Portal's WSRP portlets from a remote Consumer" +msgstr "" + +#. Tag: para +#: WSRP.xml:143 +#, no-c-format +msgid "" +"WSRP Consumers vary a lot as far as how they are configured. Most of them " +"require that you either specify the URL for the Producer's WSDL definition " +"or the URLs for the individual endpoints. Please refer to your Consumer's " +"documentation for specific instructions. For instructions on how to do so in " +"JBoss Portal, please refer to <xref linkend=\"consumer_configuration\"/>." +msgstr "" + +#. Tag: para +#: WSRP.xml:148 +#, no-c-format +msgid "" +"JBoss Portal's Producer is automatically set up when you deploy a portal " +"instance with the WSRP service. You can access the WSDL file at " +"<filename>http://{hostname}:{port}/portal-wsrp/MarkupService?wsdl</" +"filename>. You can access the endpoint URLs at: <itemizedlist> " +"<listitem><para> <filename>http://{hostname}:{port}/portal-wsrp/" +"ServiceDescriptionService</filename></para> </listitem> <listitem><para> " +"<filename>http://{hostname}:{port}/portal-wsrp/MarkupService</filename></" +"para> </listitem> <listitem><para> <filename>http://{hostname}:{port}/portal-" +"wsrp/RegistrationService</filename></para> </listitem> <listitem> " +"<para><filename>http://{hostname}:{port}/portal-wsrp/" +"PortletManagementService</filename></para> </listitem> </itemizedlist> The " +"default hostname is <literal>localhost</literal> and the default port is " +"8080." +msgstr "" + +#. Tag: title +#: WSRP.xml:172 +#, no-c-format +msgid "Consuming remote WSRP portlets in JBoss Portal" +msgstr "" + +#. Tag: title +#: WSRP.xml:174 WSRP.xml:703 +#, no-c-format +msgid "Overview" +msgstr "" + +#. Tag: para +#: WSRP.xml:175 +#, no-c-format +msgid "" +"To be able to consume WSRP portlets exposed by a remote producer, JBoss " +"Portal's WSRP consumer needs to know how to access that remote producer. One " +"can configure access to a remote producer using WSRP Producer descriptors. " +"Alternatively, a portlet is provided to configure remote producers." +msgstr "" + +#. Tag: para +#: WSRP.xml:180 +#, no-c-format +msgid "" +"Once a remote producer has been configured, it can be made available in the " +"list of portlet providers in the Management portlet on the Admin page of " +"JBoss Portal. You can then examine the list of portlets that are exposed by " +"this producer and configure the portlets just like you would for local " +"portlets." +msgstr "" + +#. Tag: para +#: WSRP.xml:186 +#, no-c-format +msgid "" +"JBoss Portal's default configuration exposes some of the sample portlets for " +"remote consumption. As a way to test the WSRP service, a default consumer " +"has been configured to consume these portlets. To make sure that the service " +"indeed works, check that there is a portlet provider with the <literal>self</" +"literal> identifier in the portlet providers list in the Management portlet " +"of the Admin page. All local portlets marked as remotable are exposed as " +"remote portlets via the <literal>self</literal> portlet provider so that you " +"can check that they work as expected with WSRP. The <filename>portal-wsrp." +"sar</filename> file contains a WSRP Producer descriptor (<filename>default-" +"wsrp.xml</filename>) that configures this default producer. This file can be " +"edited or removed if needed." +msgstr "" + +#. Tag: title +#: WSRP.xml:203 +#, no-c-format +msgid "Configuring a remote producer walk-through" +msgstr "" + +#. Tag: para +#: WSRP.xml:204 +#, no-c-format +msgid "" +"Let's work through the steps of defining access to a remote producer so that " +"its portlets can be consumed within JBoss Portal. We will configure access " +"to BEA's public WSRP producer. We will first examine how to do so using the " +"configuration portlet. We will then show how the same result can be " +"accomplish with a producer descriptor." +msgstr "" + +#. Tag: title +#: WSRP.xml:212 +#, no-c-format +msgid "Using the configuration portlet" +msgstr "" + +#. Tag: para +#: WSRP.xml:213 +#, no-c-format +msgid "" +"As of Portal 2.6, a configuration portlet is provided to configure access to " +"remote WSRP Producers grahically. You can access it at <filename>http://" +"{hostname}:{port}/portal/auth/portal/admin/WSRP</filename> or by logging in " +"as a Portal administrator and clicking on the WSRP tab in the Admin portal. " +"If all went well, you should see something similar to this: <mediaobject> " +"<imageobject> <imagedata fileref=\"images/wsrp/config_init.png\" align=" +"\"center\" valign=\"middle\" scalefit=\"1\"/> </imageobject> </mediaobject> " +"This screen presents all the configured producers associated with their " +"status and possible actions on them. A Consumer can be active or inactive. " +"Activating a Consumer means that it is ready to act as a portlet provider. " +"Deactivating it will remove it from the list of available portlet providers. " +"Note also that a Consumer can be marked as requiring refresh meaning that " +"the information held about it might not be up to date and refreshing it from " +"the remote Producer might be a good idea. This can happen for several " +"reasons: the service description for that remote Producer has not been " +"fetched yet, the cached version has expired or modifications have been made " +"to the configuration that could potentially invalidate it, thus requiring re-" +"validation of the information." +msgstr "" + +#. Tag: para +#: WSRP.xml:234 +#, no-c-format +msgid "" +"Next, we create a new Consumer which we will call<literal>bea</literal>. " +"Type \"<literal>bea</literal>\" in the \"Create a consumer named:\" field " +"then click on \"Create consumer\": <mediaobject> <imageobject> <imagedata " +"fileref=\"images/wsrp/config_create.png\" align=\"center\" valign=\"middle\" " +"scalefit=\"1\"/> </imageobject> </mediaobject> You should now see a form " +"allowing you to enter/modify the information about the Consumer. Set the " +"cache expiration value to 300 seconds and enter the WSDL URL for the " +"producer in the text field and press the \"Refresh &amp; Save\" button: " +"<mediaobject> <imageobject> <imagedata fileref=\"images/wsrp/config_usewsdl." +"png\" align=\"center\" valign=\"middle\" scalefit=\"1\"/> </imageobject> </" +"mediaobject> This will retrieve the service description associated with the " +"Producer which WSRP is described by the WSDL file found at the URL you just " +"entered. In our case, querying the service description will allow us to " +"learn that the Producer requires registration and that it expects a value " +"for the registration property named <literal>registration/consumerRole</" +"literal>: <mediaobject> <imageobject> <imagedata fileref=\"images/wsrp/" +"config_refresh.png\" align=\"center\" valign=\"middle\" scalefit=\"1\"/> </" +"imageobject> </mediaobject> <note><title>Note</title><para>At this point, " +"there is no automated way to learn about which possible values (if any) are " +"expected by the remote Producer. In the case of BEA's public producer, the " +"possible values are indicated in the registration property description. This " +"is not always the case... Please refer to the specific Producer's " +"documentation.</para> </note> Enter \"<literal>public</literal>\" as the " +"value for the registration property and press \"Save &amp; Refresh\" once " +"more. You should now see something similar to: <mediaobject> <imageobject> " +"<imagedata fileref=\"images/wsrp/config_end.png\" align=\"center\" valign=" +"\"middle\" scalefit=\"1\"/> </imageobject> </mediaobject> The Consumer for " +"the <literal>bea</literal> Producer should now be available as a portlet " +"provider and is ready to be used." +msgstr "" + +#. Tag: para +#: WSRP.xml:276 +#, no-c-format +msgid "" +"A producer is configured, by default, by retrieving the producer's " +"information via a WSDL URL. There are rare cases, however, where URLs need " +"to be provided for each of the producer's end points. You can do exactly " +"that by unchecking the \"Use WSDL?\" checkbox, as is the case for the " +"<literal>self</literal> producer:" +msgstr "" + +#. Tag: title +#: WSRP.xml:290 +#, no-c-format +msgid "Using a WSRP Producer XML descriptor" +msgstr "" + +#. Tag: para +#: WSRP.xml:292 +#, no-c-format +msgid "" +"We will create a <filename>public-bea-wsrp.xml</filename> descriptor. Note " +"that the actual name does not matter as long as it ends with <filename>-wsrp." +"xml</filename>:" +msgstr "" + +#. Tag: programlisting +#: WSRP.xml:295 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<?xml version='1.0' encoding='UTF-8' ?>\n" +"<!DOCTYPE deployments PUBLIC \"-//JBoss Portal//DTD WSRP Remote Producer " +"Configuration 2.6//EN\"\n" +" \"http://www.jboss.org/portal/dtd/jboss-wsrp-consumer_2_6.dtd\">\n" +"<deployments>\n" +" <deployment>\n" +" <wsrp-producer id=\"bea\" expiration-cache=\"300\">\n" +" <endpoint-wsdl-url>http://wsrp.bea.com:7001/producer/producer?WSDL</" +"endpoint-wsdl-url>\n" +" <registration-data>\n" +" <property>\n" +" <name>registration/consumerRole</name>\n" +" <lang>en</lang>\n" +" <value>public</value>\n" +" </property>\n" +" </registration-data>\n" +" </wsrp-producer>\n" +" </deployment>\n" +"</deployments>]]>" +msgstr "" + +#. Tag: para +#: WSRP.xml:296 +#, no-c-format +msgid "" +"This producer descriptor gives access to BEA's public WSRP producer. We will " +"look at the details of the different elements later. Note for now the " +"<literal>producer-id</literal> element with a \"<literal>bea</literal>\" " +"value. Put this file in the deploy directory and start the server (with " +"JBoss Portal and its WSRP service deployed)." +msgstr "" + +#. Tag: title +#: WSRP.xml:300 WSRP.xml:364 WSRP.xml:421 WSRP.xml:468 WSRP.xml:630 +#: WSRP.xml:782 WSRP.xml:787 WSRP.xml:824 +#, no-c-format +msgid "Note" +msgstr "" + +#. Tag: para +#: WSRP.xml:300 +#, no-c-format +msgid "" +"A DTD and an XML Schema for WSRP Producer XML descriptors are available in " +"<filename>jboss-portal.sar/portal-wsrp.sar/dtd/jboss-wsrp-consumer_2_6.dtd</" +"filename> and <filename>jboss-portal.sar/portal-wsrp.sar/xsd/jboss-wsrp-" +"consumer_2_6.xsd</filename>" +msgstr "" + +#. Tag: title +#: WSRP.xml:308 +#, no-c-format +msgid "Configuring access to a remote portlet" +msgstr "" + +#. Tag: para +#: WSRP.xml:309 +#, no-c-format +msgid "" +"Let's now look at the Admin page and the Management portlet. Click on the " +"\"Portlet definitions\" tab at the top. Once this is done, look at the list " +"of available portlet providers. If all went well, you should see something " +"similar to this:" +msgstr "" + +#. Tag: para +#: WSRP.xml:320 +#, no-c-format +msgid "" +"We have 3 available portlet providers: <literal>local, self</literal> " +"and<literal>bea</literal>. The <literal>local</literal> portlet provider " +"exposes all the portlets deployed in this particular instance of Portal. As " +"explained above, the <literal>self</literal> provider refers to the default " +"WSRP consumer bundled with Portal that consumes the portlets exposed by the " +"default WSRP producer. The <literal>bea</literal> provider corresponds to " +"BEA's public producer we just configured. Select it and click on \"View " +"portlets\". You should now see something similar to:" +msgstr "" + +#. Tag: para +#: WSRP.xml:339 +#, no-c-format +msgid "" +"From there on out, you should be able to configure WSRP portlets just as any " +"other. In particular, you can create an instance of one of the remote " +"portlets offered by BEA's public producer just like you would create an " +"instance of a local portlet and then assign it to a window in a page. If you " +"go to that page, you should see something similar to below for this portlet:" +msgstr "" + +#. Tag: title +#: WSRP.xml:354 +#, no-c-format +msgid "WSRP Producer descriptors" +msgstr "" + +#. Tag: para +#: WSRP.xml:356 +#, no-c-format +msgid "" +"A WSRP Producer descriptor is an XML file which name ends in <filename>-wsrp." +"xml</filename> and which can be dropped in the deploy directory of the JBoss " +"application server or nested in .sar files. It is possible to configure " +"access to several different producers within a single descriptor or use one " +"file per producer, depending on your needs. An XML Schema for the WSRP " +"Producer descriptor format can be found at <filename>jboss-portal.sar/portal-" +"wsrp.sar/xsd/jboss-wsrp-consumer_2_6.xsd</filename>, while a (legacy) DTD " +"can be found at <filename>jboss-portal.sar/portal-wsrp.sar/dtd/jboss-wsrp-" +"consumer_2_6.dtd</filename>." +msgstr "" + +#. Tag: para +#: WSRP.xml:364 +#, no-c-format +msgid "" +"It is important to note how WSRP Producer descriptors are processed. They " +"are read the first time the WSRP service starts and the associated " +"information is then put in the Portal database. Subsequent launch of the " +"WSRP service will use the database-stored information for all producers " +"which identifier is already known to Portal. More specifically, all the " +"descriptors are scanned for producer identifiers. Any identifier that is " +"already known will be bypassed and the configuration associated with this " +"remote producer in the database will be used. If a producer identifier is " +"found that wasn't already in the database, that producer information will be " +"processed and recorded in the database. Therefore, if you wish to delete a " +"producer configuration, you need to delete the associated information in the " +"database (this can be accomplished using the configuration portlet as we saw " +"in <xref linkend=\"consumer_gui\"/>) <emphasis>AND</emphasis> remove the " +"associated information in any WSRP Producer descriptor (if such information " +"exists) as the producer will be re-created the next time the WSRP is " +"launched if that information is not removed." +msgstr "" + +#. Tag: title +#: WSRP.xml:380 +#, no-c-format +msgid "Required configuration information" +msgstr "" + +#. Tag: para +#: WSRP.xml:382 +#, no-c-format +msgid "" +"Let's now look at which information needs to be provided to configure access " +"to a remote producer." +msgstr "" + +#. Tag: para +#: WSRP.xml:385 +#, no-c-format +msgid "" +"First, we need to provide an identifier for the producer we are configuring " +"so that we can refer to it afterwards. This is accomplished via the " +"mandatory <literal>id</literal> attribute of the <literal>&lt;wsrp-" +"producer&gt;</literal> element." +msgstr "" + +#. Tag: para +#: WSRP.xml:393 +#, no-c-format +msgid "" +"JBoss Portal also needs to learn about the remote producer's endpoints to be " +"able to connect to the remote web services and perform WSRP invocations. Two " +"options are currently supported to provide this information:" +msgstr "" + +#. Tag: para +#: WSRP.xml:400 +#, no-c-format +msgid "" +"You can provide the URLs for each of the different WSRP interfaces offered " +"by the remote producer via the <literal>&lt;endpoint-config&gt;</literal> " +"element and its <literal>&lt;service-description-url&gt;</literal>, " +"<literal>&lt;markup-url&gt;</literal>, <literal>&lt;registration-url&gt;</" +"literal> and <literal>&lt;portlet-management-url&gt;</literal> children. " +"These URLs are producer-specific so you will need to refer to your producer " +"documentation or WSDL file to determine the appropriate values." +msgstr "" + +#. Tag: para +#: WSRP.xml:414 +#, no-c-format +msgid "" +"Alternatively, and this is the easiest way to configure your producer, you " +"can provide a URL pointing to the WSDL description of the producer's WSRP " +"services. This is accomplished via the <literal>&lt;endpoint-wsdl-url&gt;</" +"literal> element. JBoss Portal will then heuristically determine, from the " +"information contained in the WSDL file, how to connect appropriately to the " +"remote WSRP services." +msgstr "" + +#. Tag: para +#: WSRP.xml:421 +#, no-c-format +msgid "" +"It is important to note that, when using this method, JBoss Portal will try " +"to match a port name to an interface based solely on the provided name. " +"There are no standard names for these ports so it is possible (though rare) " +"that this matching process fails. In this case, you should look at the WSDL " +"file and provide the endpoint URLs manually, as per the previous method." +msgstr "" + +#. Tag: para +#: WSRP.xml:430 +#, no-c-format +msgid "" +"Both the <literal>id</literal> attribute and either <literal>&lt;endpoint-" +"config&gt;</literal> or <literal>&lt;endpoint-wsdl-url&gt;</literal> " +"elements are required for a functional remote producer configuration." +msgstr "" + +#. Tag: title +#: WSRP.xml:442 +#, no-c-format +msgid "Optional configuration" +msgstr "" + +#. Tag: para +#: WSRP.xml:443 +#, no-c-format +msgid "" +"It is also possible to provide addtional configuration, which, in some " +"cases, might be important to establish a proper connection to the remote " +"producer." +msgstr "" + +#. Tag: para +#: WSRP.xml:447 +#, no-c-format +msgid "" +"One such optional configuration concerns caching. To prevent useless " +"roundtrips between the local consumer and the remote producer, it is " +"possible to cache some of the information sent by the producer (such as the " +"list of offered portlets) for a given duration. The rate at which the " +"information is refreshed is defined by the <literal>expiration-cache</" +"literal> attribute of the <literal>&lt;wsrp-producer&gt;</literal> element " +"which specifies the refreshing period in seconds. For example, providing a " +"value of 120 for expiration-cache means that the producer information will " +"not be refreshed for 2 minutes after it has been somehow accessed. If no " +"value is provided, JBoss Portal will always access the remote producer " +"regardless of whether the remote information has changed or not. Since, in " +"most instances, the information provided by the producer does not change " +"often, we recommend that you use this caching facility to minimize bandwidth " +"usage." +msgstr "" + +#. Tag: para +#: WSRP.xml:464 +#, no-c-format +msgid "" +"Additionally, some producers require consumers to register with them before " +"authorizing them to access their offered portlets. If you know that " +"information beforehand, you can provide the required registration " +"information in the producer configuration so that the Portal consumer can " +"register with the remote producer when required." +msgstr "" + +#. Tag: para +#: WSRP.xml:468 +#, no-c-format +msgid "" +"At this time, though, only simple String properties are supported and it is " +"not possible to configure complex registration data. This should however be " +"sufficient for most cases." +msgstr "" + +#. Tag: para +#: WSRP.xml:473 +#, no-c-format +msgid "" +"Registration configuration is done via the <literal>&lt;registration-data&gt;" +"</literal> element. Since JBoss Portal can generate the mandatory " +"information for you, if the remote producer does not require any " +"registration properties, you only need to provide an empty <literal>&lt;" +"registration-data&gt;</literal> element. Values for the registration " +"properties required by the remote producer can be provided via <literal>&lt;" +"property&gt;</literal> elements. See the example below for more details. " +"Additionally, you can override the default consumer name automatically " +"provided by JBoss Portal via the <literal>&lt;consumer-name&gt;</literal> " +"element. If you choose to provide a consumer name, please remember that this " +"should uniquely identify your consumer." +msgstr "" + +#. Tag: title +#: WSRP.xml:494 +#, no-c-format +msgid "Examples" +msgstr "" + +#. Tag: para +#: WSRP.xml:496 +#, no-c-format +msgid "" +"Here is the configuration of the <literal>self</literal> producer as found " +"in <filename>default-wsrp.xml</filename> with a cache expiring every five " +"minutes:" +msgstr "" + +#. Tag: programlisting +#: WSRP.xml:502 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" +"<!DOCTYPE deployments PUBLIC \"-//JBoss Portal//DTD WSRP Remote Producer " +"Configuration 2.6//EN\"\n" +" \"http://www.jboss.org/portal/dtd/jboss-wsrp-consumer_2_6.dtd\">\n" +"\n" +"<deployments>\n" +" <deployment>\n" +" <wsrp-producer id=\"self\" expiration-cache=\"300\">\n" +" <!--\n" +" we need to use the individual endpoint configuration because the " +"configuration via\n" +" wsdl forces an immediate attempt to access the web service " +"description which is not\n" +" available yet at this point of deployment\n" +" -->\n" +" <endpoint-config>\n" +" <service-description-url>\n" +" http://localhost:8080/portal-wsrp/ServiceDescriptionService\n" +" </service-description-url>\n" +" <markup-url>http://localhost:8080/portal-wsrp/MarkupService</" +"markup-url>\n" +" <registration-url>\n" +" http://localhost:8080/portal-wsrp/RegistrationService\n" +" </registration-url>\n" +" <portlet-management-url>\n" +" http://localhost:8080/portal-wsrp/PortletManagementService\n" +" </portlet-management-url>\n" +" </endpoint-config>\n" +" <registration-data/>\n" +" </wsrp-producer>\n" +" </deployment>\n" +"</deployments>]]>" +msgstr "" + +#. Tag: para +#: WSRP.xml:505 +#, no-c-format +msgid "" +"Here is an example of a WSRP descriptor with a 2 minute caching time and " +"manual definition of the endpoint URLs:" +msgstr "" + +#. Tag: programlisting +#: WSRP.xml:510 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" +"<!DOCTYPE deployments PUBLIC \"-//JBoss Portal//DTD WSRP Remote Producer " +"Configuration 2.6//EN\"\n" +" \"http://www.jboss.org/portal/dtd/jboss-wsrp-consumer_2_6.dtd\">\n" +"\n" +"<deployments>\n" +" <deployment>\n" +" <wsrp-producer id=\"MyProducer\" expiration-cache=\"120\">\n" +" <endpoint-config>\n" +" <service-description-url>\n" +" http://www.someproducer.com/portal-wsrp/" +"ServiceDescriptionService\n" +" </service-description-url>\n" +" <markup-url>\n" +" http://www.someproducer.com/portal-wsrp/MarkupService\n" +" </markup-url>\n" +" <registration-url>\n" +" http://www.someproducer.com/portal-wsrp/RegistrationService\n" +" </registration-url>\n" +" <portlet-management-url>\n" +" http://www.someproducer.com/portal-wsrp/" +"PortletManagementService\n" +" </portlet-management-url>\n" +" </endpoint-config>\n" +" </wsrp-producer>\n" +" </deployment>\n" +"</deployments>]]>" +msgstr "" + +#. Tag: para +#: WSRP.xml:513 +#, no-c-format +msgid "" +"Here is an example of a WSRP descriptor with endpoint definition via remote " +"WSDL file, registration data and cache expiring every minute:" +msgstr "" + +#. Tag: programlisting +#: WSRP.xml:518 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" +"<!DOCTYPE deployments PUBLIC \"-//JBoss Portal//DTD WSRP Remote Producer " +"Configuration 2.6//EN\"\n" +" \"http://www.jboss.org/portal/dtd/jboss-wsrp-consumer_2_6.dtd\">\n" +"\n" +"<deployments>\n" +" <deployment>\n" +" <wsrp-producer id=\"AnotherProducer\" expiration-cache=\"60\">\n" +" <endpoint-wsdl-url>http://example.com/producer/producer?WSDL</" +"endpoint-wsdl-url>\n" +" <registration-data>\n" +" <property>\n" +" <name>property name</name>\n" +" <lang>en</lang>\n" +" <value>property value</value>\n" +" </property>\n" +" </registration-data>\n" +" </wsrp-producer>\n" +" </deployment>\n" +"</deployments>]]>" +msgstr "" + +#. Tag: title +#: WSRP.xml:524 +#, no-c-format +msgid "Consumers maintenance" +msgstr "" + +#. Tag: title +#: WSRP.xml:527 +#, no-c-format +msgid "Modifying a currently held registration" +msgstr "" + +#. Tag: title +#: WSRP.xml:530 +#, no-c-format +msgid "Registration modification for service upgrade" +msgstr "" + +#. Tag: para +#: WSRP.xml:531 +#, no-c-format +msgid "" +"Producers often offer several levels of service depending on consumers' " +"subscription levels (for example). This is implemented at the WSRP level " +"with the registration concept: producers assert which level of service to " +"provide to consumers based on the values of given registration properties." +msgstr "" + +#. Tag: para +#: WSRP.xml:537 +#, no-c-format +msgid "" +"It is therefore sometimes necessary to modify the registration that " +"concretizes the service agreement between a consumer and a producer. An " +"example of easily available producer offering different level of services is " +"BEA's public producer. We configured access to that producer in <xref " +"linkend=\"consumer_gui\"/>. If you recall, the producer was requiring " +"registration and required a value to be provided for the " +"<literal>registration/consumerRole</literal> property. The description of " +"that property indicated that three values were possible: <literal>public</" +"literal>, <literal>partner</literal> or <literal>insider</literal> each " +"corresponding to a different service level. We registered using the " +"<literal>public</literal> service level. This gave us access to three " +"portlets as shown here:" +msgstr "" + +#. Tag: para +#: WSRP.xml:554 +#, no-c-format +msgid "" +"Suppose now that we would like to upgrade our service level to the \"insider" +"\" level. We will need to tell BEA's producer that our registration data has " +"been modified. Let's see how to do this. Assuming you have configured access " +"to the producer as previously described, please go to the configuration " +"screen for the <literal>bea</literal> producer and modify the value of the " +"<literal>registration/consumerRole</literal> to <literal>insider</literal> " +"instead of <literal>public</literal>: <mediaobject> <imageobject> <imagedata " +"fileref=\"images/wsrp/modify_reg_start.png\" align=\"center\" valign=\"middle" +"\" scalefit=\"1\"/> </imageobject> </mediaobject> Now click on \"Update " +"properties\" to save the change. A \"Modify registration\" button should now " +"appear to let you send this new data to the remote producer: <mediaobject> " +"<imageobject> <imagedata fileref=\"images/wsrp/modify_reg_modify.png\" align=" +"\"center\" valign=\"middle\" scalefit=\"1\"/> </imageobject> </mediaobject> " +"Click on this new button and, if everything went well and your updated " +"registration has been accepted by the remote producer, you should see " +"something similar to: <mediaobject> <imageobject> <imagedata fileref=" +"\"images/wsrp/modify_reg_end.png\" align=\"center\" valign=\"middle\" " +"scalefit=\"1\"/> </imageobject> </mediaobject> You can now check the list of " +"available portlets from the <literal>bea</literal> provider and verify that " +"new portlets are now available:" +msgstr "" + +#. Tag: title +#: WSRP.xml:592 +#, no-c-format +msgid "Registration modification on producer error" +msgstr "" + +#. Tag: para +#: WSRP.xml:594 +#, no-c-format +msgid "" +"It can also happen that a producer administrator decided to require more " +"information from registered consumers. In this case, invoking operations on " +"the producer will fail with an <literal>OperationFailedFault</literal>. " +"JBoss Portal will attempt to help you in this situation. Let's walk through " +"an example using the <literal>self</literal> producer. Let's assume that " +"registration is required without any registration properties (as is the case " +"by default). If you go to the configuration screen for this producer, you " +"should see: <mediaobject> <imageobject> <imagedata fileref=\"images/wsrp/" +"config_self.png\" align=\"center\" valign=\"middle\" scalefit=\"1\"/> </" +"imageobject> </mediaobject> Now suppose that the administrator of the " +"producer now requires a value to be provided for an <literal>email</literal> " +"registration property. We will actually see how to do perform this operation " +"in JBoss Portal when we examine how to configure Portal's producer in <xref " +"linkend=\"producer_config\"/>. Operations with this producer will now fail. " +"If you suspect that a registration modification is required, you should go " +"to the configuration screen for this remote producer and refresh the " +"information held by the consumer by pressing \"Refresh &amp; Save\": " +"<mediaobject> <imageobject> <imagedata fileref=\"images/wsrp/modify_reg_self." +"png\" align=\"center\" valign=\"middle\" scalefit=\"1\"/> </imageobject> </" +"mediaobject> As you can see, the configuration screen now shows the " +"currently held registration information and the expected information from " +"the producer. Enter a value for the <literal>email</literal> property and " +"then click on \"Modify registration\". If all went well and the producer " +"accepted your new registration data, you should see something similar to:" +msgstr "" + +#. Tag: para +#: WSRP.xml:630 +#, no-c-format +msgid "" +"As of WSRP 1, it is rather difficult to ascertain for sure what caused an " +"<literal>OperationFailedFault</literal> as it is the generic exception " +"returned by producers if something didn't quite happen as expected during a " +"method invocation. This means that <literal>OperationFailedFault</literal> " +"can be caused by several different reasons, one of them being a request to " +"modify the registration data. Please take a look at the log files to see if " +"you can gather more information as to what happened. WSRP 2 introduces an " +"exception that is specific to a request to modify registrations thus " +"reducing the ambiguity that currently exists." +msgstr "" + +#. Tag: title +#: WSRP.xml:643 +#, no-c-format +msgid "Consumer operations" +msgstr "" + +#. Tag: para +#: WSRP.xml:644 +#, no-c-format +msgid "" +"Several operations are available from the consumer list view of the WSRP " +"configuration portlet:" +msgstr "" + +#. Tag: para +#: WSRP.xml:652 +#, no-c-format +msgid "The available operations are:" +msgstr "" + +#. Tag: para +#: WSRP.xml:655 +#, no-c-format +msgid "Configure: displays the consumer details and allows user to edit them" +msgstr "" + +#. Tag: para +#: WSRP.xml:657 +#, no-c-format +msgid "" +"Refresh: forces the consumer to retrieve the service description from the " +"remote producer to refresh the local information (offered portlets, " +"registration information, etc.)" +msgstr "" + +#. Tag: para +#: WSRP.xml:660 +#, no-c-format +msgid "" +"Activate/Deactivate: activates/deactivates a consumer, governing whether it " +"will be available to provide portlets and receive portlet invocations" +msgstr "" + +#. Tag: para +#: WSRP.xml:664 +#, no-c-format +msgid "" +"Register/Deregister: registers/deregisters a consumer based on whether " +"registration is required and/or acquired" +msgstr "" + +#. Tag: para +#: WSRP.xml:668 +#, no-c-format +msgid "" +"Delete: destroys the consumer, after deregisterting it if it was registered" +msgstr "" + +#. Tag: title +#: WSRP.xml:674 +#, no-c-format +msgid "Erasing local registration data" +msgstr "" + +#. Tag: para +#: WSRP.xml:675 +#, no-c-format +msgid "" +"There are rare cases where it might be required to erase the local " +"information without being able to deregister first. This is the case when a " +"consumer is registered with a producer that has been modified by its " +"administrator to not require registration anymore. If that ever was to " +"happen (most likely, it won't), you can erase the local registration " +"information from the consumer so that it can resume interacting with the " +"remote producer. To do so, click on \"Erase local registration\" button next " +"to the registration context information on the consumer configuration screen:" +msgstr "" + +#. Tag: para +#: WSRP.xml:688 +#, no-c-format +msgid "" +"<emphasis>Warning:</emphasis> This operation is dangerous as it can result " +"in inability to interact with the remote producer if invoked when not " +"required. A warning screen will be displayed to give you a chance to change " +"your mind:" +msgstr "" + +#. Tag: title +#: WSRP.xml:701 +#, no-c-format +msgid "Configuring JBoss Portal's WSRP Producer" +msgstr "" + +#. Tag: para +#: WSRP.xml:704 +#, no-c-format +msgid "" +"You can configure the behavior of Portal's WSRP Producer by using the WSRP " +"administration interface, which is the preferred way, or by editing the " +"<filename>conf/config.xml</filename> file found in <filename>portal-wsrp." +"sar</filename>. Several aspects can be modified with respects to whether " +"registration is required for consumers to access the Producer's services. An " +"XML Schema for the configuration format is available at <filename>jboss-" +"portal.sar/portal-wsrp.sar/xsd/jboss-wsrp-producer_2_6.xsd</filename>, while " +"a (legacy) DTD is available at <filename>jboss-portal.sar/portal-wsrp.sar/" +"dtd/jboss-wsrp-producer_2_6.dtd</filename>" +msgstr "" + +#. Tag: title +#: WSRP.xml:715 +#, no-c-format +msgid "Default configuration" +msgstr "" + +#. Tag: para +#: WSRP.xml:716 +#, no-c-format +msgid "" +"The default producer configuration is to require that consumers register " +"with it before providing access its services but does not require any " +"specific registration properties (apart from what is mandated by the WSRP " +"standard). It does, however, require consumers to be registered before " +"sending them a full service description. This means that our WSRP producer " +"will not provide the list of offered portlets and other capabilities to " +"unregistered consumers. The producer also uses the default " +"<classname>RegistrationPolicy</classname> paired with the default " +"<classname>RegistrationPropertyValidator</classname>. We will look into " +"property validators in greater detail later in <xref linkend=\"registration-" +"configuration\"/>. Suffice to say for now that this allows users to " +"customize how Portal's WSRP Producer decides whether a given registration " +"property is valid or not." +msgstr "" + +#. Tag: para +#: WSRP.xml:728 +#, no-c-format +msgid "" +"JBoss Portal 2.6.3 introduces a web interface to configure the producer's " +"behavior. You can access it by clicking on the \"Producer Configuration\" " +"tab of the \"WSRP\" page of the \"admin\" portal. Here's what you should see " +"with the default configuration: <mediaobject> <imageobject> <imagedata " +"fileref=\"images/wsrp/producer_default.png\" align=\"center\" valign=\"middle" +"\" scalefit=\"1\"/> </imageobject> </mediaobject> As would be expected, you " +"can specify whether or not the producer will send the full service " +"description to unregistered consumers, and, if it requires registration, " +"which <classname>RegistrationPolicy</classname> to use (and, if needed, " +"which <classname>RegistrationPropertyValidator</classname>), along with " +"required registration property description for which consumers must provide " +"acceptable values to successfully register." +msgstr "" + +#. Tag: title +#: WSRP.xml:746 +#, no-c-format +msgid "Registration configuration" +msgstr "" + +#. Tag: para +#: WSRP.xml:747 +#, no-c-format +msgid "" +"In order to require consumers to register with Portal's producer before " +"interacting with it, you need to configure Portal's behavior with respect to " +"registration. Registration is optional, as are registration properties. The " +"producer can require registration without requiring consumers to pass any " +"registration properties as is the case in the default configuration. Let's " +"configure our producer starting with a blank state: <mediaobject> " +"<imageobject> <imagedata fileref=\"images/wsrp/producer_blank.png\" align=" +"\"center\" valign=\"middle\" scalefit=\"1\"/> </imageobject> </mediaobject> " +"We will allow unregistered consumers to see the list of offered portlets so " +"we leave the first checkbox (\"Access to full service description requires " +"consumers to be registered.\") unchecked. We will, however, specify that " +"consumers will need to be registered to be able to interact with our " +"producer. Check the second checkbox (\"Requires registration. Modifying this " +"information will trigger invalidation of consumer registrations.\"). The " +"screen should now refresh and display: <mediaobject> <imageobject> " +"<imagedata fileref=\"images/wsrp/producer_registration.png\" align=\"center" +"\" valign=\"middle\" scalefit=\"1\"/> </imageobject> </mediaobject> You can " +"specify the fully-qualified name for your <classname>RegistrationPolicy</" +"classname> and <classname>RegistrationPropertyValidator</classname> there. " +"We will keep the default value. See <xref linkend=\"custom_registration\"/> " +"for more details. Let's add, however, a registration property called " +"<literal>email</literal>. Click \"Add property\" and enter the appropriate " +"information in the fields, providing a description for the registration " +"property that can be used by consumers to figure out its purpose: " +"<mediaobject> <imageobject> <imagedata fileref=\"images/wsrp/producer_email." +"png\" align=\"center\" valign=\"middle\" scalefit=\"1\"/> </imageobject> </" +"mediaobject> Press \"Save\" to record your modifications." +msgstr "" + +#. Tag: para +#: WSRP.xml:782 +#, no-c-format +msgid "" +"At this time, only String (xsd:string) properties are supported. If your " +"application requires more complex properties, please let us know." +msgstr "" + +#. Tag: para +#: WSRP.xml:787 +#, no-c-format +msgid "" +"If consumers are already registered with the producer, modifying the " +"configuration of required registration information will trigger the " +"invalidation of held registrations, requiring consumers to modify their " +"registration before being able to access the producer again. We saw the " +"consumer side of that process in <xref linkend=\"reg_mod_error\"/>." +msgstr "" + +#. Tag: title +#: WSRP.xml:797 +#, no-c-format +msgid "Customization of Registration handling behavior" +msgstr "" + +#. Tag: para +#: WSRP.xml:798 +#, no-c-format +msgid "" +"Registration handling behavior can be customized by users to suit their " +"Producer needs. This is accomplished by providing an implementation of the " +"<classname>RegistrationPolicy</classname> interface. This interface defines " +"methods that are called by Portal's Registration service so that decisions " +"can be made appropriately. A default registration policy that provides basic " +"behavior is provided and should be enough for most user needs." +msgstr "" + +#. Tag: para +#: WSRP.xml:806 +#, no-c-format +msgid "" +"While the default registration policy provides default behavior for most " +"registration-related aspects, there is still one aspect that requires " +"configuration: whether a given value for a registration property is " +"acceptable by the WSRP Producer. This is accomplished by plugging a " +"<classname>RegistrationPropertyValidator</classname> in the default " +"registration policy. This allows users to define their own validation " +"mechanism." +msgstr "" + +#. Tag: para +#: WSRP.xml:813 +#, no-c-format +msgid "" +"Please refer to the <trademark class=\"trade\">Javadoc</trademark> for " +"<classname>org.jboss.portal.registration.RegistrationPolicy</classname> and " +"<classname>org.jboss.portal.Registration.policies." +"RegistrationPropertyValidator</classname> for more details on what is " +"expected of each method." +msgstr "" + +#. Tag: para +#: WSRP.xml:818 +#, no-c-format +msgid "" +"Defining a registration policy is required for the producer to be correctly " +"configured. This is accomplished by specifying the qualified class name of " +"the registration policy. Since we anticipate that most users will use the " +"default registration policy, it is possible to provide the class name of " +"your custom property validator instead to customize the default registration " +"policy behavior. Note that property validators are only used by the default " +"policy." +msgstr "" + +#. Tag: para +#: WSRP.xml:824 +#, no-c-format +msgid "" +"Since the policy or the validator are defined via their class name and " +"dynamically loaded, it is important that you make sure that the identified " +"class is available to the application server. One way to accomplish that is " +"to deploy your policy implementation as JAR file in your AS instance deploy " +"directory. Note also that, since both policies and validators are " +"dynamically instantiated, they must provide a default, no-argument " +"constructor." +msgstr "" + +#. Tag: title +#: WSRP.xml:834 +#, no-c-format +msgid "WSRP validation mode" +msgstr "" + +#. Tag: para +#: WSRP.xml:835 +#, no-c-format +msgid "" +"The lack of conformance kit and the wording of the WSRP specification leaves " +"room for differing interpretations, resulting in interoperability issues. It " +"is therefore possible to encounter issues when using consumers from " +"different vendors. We have experienced such issues and have introduced a way " +"to relax the validation that our WSRP producer performs on the data provided " +"by consumers to help with interoperability by accepting data that would " +"normally be invalid. Note that we only relax our validation algorithm on " +"aspects of the specification that are deemed harmless such as invalid " +"language codes." +msgstr "" + +#. Tag: para +#: WSRP.xml:842 +#, no-c-format +msgid "" +"By default, the WSRP producer is configured in strict mode. If you " +"experience issues with a given consumer, you might want to try to relax the " +"validation mode. This is accomplished by unchecking the \"Use strict WSRP " +"compliance.\" checkbox on the Producer configuration screen." +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Widget_Integration.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Widget_Integration.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Widget_Integration.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,152 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Widget_Integration.xml:7 +#, no-c-format +msgid "Widget Integration" +msgstr "" + +#. Tag: title +#: Widget_Integration.xml:9 +#, no-c-format +msgid "Introduction" +msgstr "" + +#. Tag: para +#: Widget_Integration.xml:10 +#, no-c-format +msgid "" +"JBoss Portal supports the integration of Google gadgets and Netvibes (<ulink " +"url=\"http://dev.netvibes.com/doc/uwa_specification\">UWA</ulink> " +"compatible) widgets out of the box. This integration allows you to display " +"the content of the widget within a portlet. Both types can be added in the " +"administration interface by editing the 'Page Layout' of a page or in the " +"configuration of the users dashboard when selecting the appropriate 'Content " +"type'." +msgstr "" + +#. Tag: title +#: Widget_Integration.xml:17 +#, no-c-format +msgid "Widget portlet configuration" +msgstr "" + +#. Tag: para +#: Widget_Integration.xml:18 +#, no-c-format +msgid "" +"It is possible to modify certain behavior of caching and fetching widgets by " +"changing the init-param values of the portlet." +msgstr "" + +#. Tag: para +#: Widget_Integration.xml:22 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">connectionTimeout</emphasis>. Connection timeout " +"used for the directory lookup in milliseconds." +msgstr "" + +#. Tag: para +#: Widget_Integration.xml:28 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">widgetExpiration</emphasis>. Time in minutes for " +"which a widget should be cached. After this time the cached widget " +"information will be deleted and fetched again when the information are " +"needed." +msgstr "" + +#. Tag: para +#: Widget_Integration.xml:35 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">queryExpiration</emphasis>. Times in minutes for " +"which a directory query should be cached. After this time the cached query " +"information will be deleted." +msgstr "" + +#. Tag: para +#: Widget_Integration.xml:41 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">fetchWidgetsOnDirectoryLookup</emphasis>. This " +"parameter defines if all widgets from a directory lookup should be fetched " +"at the time of the query or not. The default values is false. This means " +"that widgets are only fetched on demand - when the information is really " +"needed." +msgstr "" + +#. Tag: para +#: Widget_Integration.xml:49 +#, no-c-format +msgid "" +"The parameter for both widget types can be changed identically in either:" +msgstr "" + +#. Tag: para +#: Widget_Integration.xml:52 +#, no-c-format +msgid "" +"<emphasis>jboss-portal.sar/portal-widget.war/WEB-INF/portlet.xml</emphasis> " +"(for google gadgets)" +msgstr "" + +#. Tag: para +#: Widget_Integration.xml:53 +#, no-c-format +msgid "" +"or <emphasis>jboss-portal.sar/portal-widget-netvibes.war/WEB-INF/portlet." +"xml</emphasis> (for netvibes widgets)." +msgstr "" + +#. Tag: programlisting +#: Widget_Integration.xml:57 +#, no-c-format +msgid "" +"<![CDATA[...\n" +" <portlet>\n" +" ...\n" +" <init-param>\n" +" <name>connectionTimeout</name>\n" +" <value>5000</value>\n" +" </init-param>\n" +" <init-param>\n" +" <name>widgetExpiration</name>\n" +" <value>360</value>\n" +" </init-param>\n" +" <init-param>\n" +" <name>queryExpiration</name>\n" +" <value>60</value>\n" +" </init-param>\n" +" <init-param>\n" +" <name>fetchWidgetsOnDirectoryLookup</name>\n" +" <value>false</value>\n" +" </init-param>\n" +" ...\n" +" </portlet>\n" +"...]]>" +msgstr "" + +#. Tag: para +#: Widget_Integration.xml:59 +#, no-c-format +msgid "" +"For Netvibes widgets it is also possible to define a init-param called " +"<emphasis role=\"bold\">defaultHeight</emphasis> to set a specific default " +"height if no height attribute is defined by the widget itself. The default " +"value is 250." +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/Workflow.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/Workflow.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/Workflow.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,209 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Workflow.xml:6 +#, no-c-format +msgid "Portal Workflow" +msgstr "" + +#. Tag: para +#: Workflow.xml:7 +#, no-c-format +msgid "" +"JBoss Portal packages a Workflow Service based on jBPM. This service " +"provides you with the jBPM services that your portal can use to build out " +"the end-user/application workflows that should meet your portal's " +"requirements." +msgstr "" + +#. Tag: title +#: Workflow.xml:12 +#, no-c-format +msgid "jBPM Workflow Engine Integration" +msgstr "" + +#. Tag: para +#: Workflow.xml:13 +#, no-c-format +msgid "" +"The jBPM Workflow service is packaged as an mbean and takes care of all the " +"low-level jBPM related functions. The configuration is found in " +"<filename>portal-workflow.sar/META-INF/jboss-service.xml</filename>." +msgstr "" + +#. Tag: title +#: Workflow.xml:19 +#, no-c-format +msgid "CMS Publish/Approve Workflow Service" +msgstr "" + +#. Tag: para +#: Workflow.xml:20 +#, no-c-format +msgid "" +"The CMS Publish/Approval Workflow feature is turned on by default, so that " +"every file that is created or updated needs to go through an <emphasis role=" +"\"bold\">approval process</emphasis> before it can be published to go live. " +"The current implementation creates a pending queue for managers. The " +"managers can then either approve or reject the publishing of the document in " +"question." +msgstr "" + +#. Tag: title +#: Workflow.xml:27 +#, no-c-format +msgid "How to activate this feature?" +msgstr "" + +#. Tag: para +#: Workflow.xml:28 +#, no-c-format +msgid "" +"The CMS Publish/Approval Workflow feature can be activated by uncommenting " +"the <literal>ApprovePublishWorkflow</literal> attribute of the " +"<literal>portal:service=CMS</literal> mbean in <filename>portal-cms.sar/META-" +"INF/jboss-service.xml</filename>:" +msgstr "" + +#. Tag: programlisting +#: Workflow.xml:32 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<mbean\n" +" code=\&quot;@cms.service.code(a)\&quot;\n&quot; +" name=\"portal:service=CMS\"\n" +" xmbean-dd=\"\"\n" +" xmbean-code=\"org.jboss.portal.jems.as.system.JBossServiceModelMBean" +"\">\n" +" <xmbean/>\n" +"\n" +" ...\n" +"\n" +" <!-- Add this to activate publish/approval workflow integration -->\n" +" <!-- <depends optional-attribute-name=\"ApprovePublishWorkflow\" proxy-" +"type=\"attribute\">portal:service=ApprovePublish,type=Workflow</depends> --" +">\n" +"\n" +" ...\n" +"</mbean>]]>" +msgstr "" + +#. Tag: title +#: Workflow.xml:36 +#, no-c-format +msgid "How to configure this feature?" +msgstr "" + +#. Tag: para +#: Workflow.xml:37 +#, no-c-format +msgid "" +"The workflow service can be configured by editing the <literal>portal:" +"service=ApprovePublish,type=Workflow</literal> mbean found in " +"<filename>portal-cms.sar/META-INF/jboss-service.xml</filename>." +msgstr "" + +#. Tag: programlisting +#: Workflow.xml:40 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!-- ApprovePublish workflow service -->\n" +" <mbean\n" +" code=\"org.jboss.portal.cms.workflow.ApprovePublishImpl\"\n" +" name=\"portal:service=ApprovePublish,type=Workflow\"\n" +" xmbean-dd=\"\"\n" +" xmbean-code=\"org.jboss.portal.jems.as.system.JBossServiceModelMBean" +"\">\n" +" <xmbean/>\n" +" <depends optional-attribute-name=\"WorkflowService\" proxy-type=" +"\"attribute\">\n" +" portal:service=Workflow,type=WorkflowService\n" +" </depends>\n" +" <depends optional-attribute-name=\"IdentityServiceController\" proxy-" +"type=\"attribute\">\n" +" portal:service=Module,type=IdentityServiceController\n" +" </depends>\n" +" <!-- JBPM process definition -->\n" +" <attribute name=\"Process\">\n" +" <!-- cms approval workflow -->\n" +" <process-definition name=\"approval_workflow\">\n" +" <start-state>\n" +" <transition to=\"request_approval\"/>\n" +" </start-state>\n" +" <task-node name=\"request_approval\" signal=\"first\">\n" +" <task name=\"approve_publish\">\n" +" <assignment class=\"org.jboss.portal.cms.workflow." +"PublishAssignmentHandler\"/>\n" +" <event type=\"task-start\">\n" +" <action class=\"org.jboss.portal.cms.workflow." +"FinalizePublish\"/>\n" +" </event>\n" +" <exception-handler>\n" +" <action class=\"org.jboss.portal.cms.workflow." +"TaskExceptionHandler\"/>\n" +" </exception-handler>\n" +" </task>\n" +" <transition name=\"approval\" to=\"end\"/>\n" +" <transition name=\"rejection\" to=\"end\"/>\n" +" </task-node>\n" +" <end-state name=\"end\"/>\n" +" </process-definition>\n" +" </attribute>\n" +" <!--\n" +" overwrite = false creates the process first time if does not exist, " +"for\n" +" subsequent server restarts, this process definition remains in " +"tact\n" +"\n" +" overwrite = true creates the process first time if does not exist,\n" +" for subsequent server restarts, it creates a new version of the " +"process definition\n" +" which will be used for processes created from then onwards. Old " +"processes created\n" +" for an older version of the definition remain in tact and use their " +"corresponding\n" +" process definition.\n" +"\n" +" Typically use overwrite=false and overwrite=true only when a new " +"process definition\n" +" related to this workflow needs to be deployed\n" +" -->\n" +" <attribute name=\"Overwrite\">false</attribute>\n" +" <!--\n" +" A comma separated list of portal roles that are designated\n" +" to act as workflow managers. They are allowed to\n" +" approve/reject content publish requests\n" +" -->\n" +" <attribute name=\"ManagerRoles\">Admin</attribute>\n" +" <attribute name=\"JNDIName\">java:portal/ApprovePublishWorkflow</" +"attribute>\n" +" </mbean>]]>" +msgstr "" + +#. Tag: para +#: Workflow.xml:42 +#, no-c-format +msgid "" +"Of note in this configuration are the <literal>Process</literal> and " +"<literal>ManagerRoles</literal> attributes. The <literal>Process</literal> " +"attribute is used to provide the jBPM process definition to be followed by " +"the workflow service during the approval process. This follows the standard " +"jBPM syntax for process definition. <literal>ManagerRoles</literal>, on the " +"other hand, is a comma-delimited list of user roles that are being marked as " +"\"managers\" who can approve the publication of CMS documents." +msgstr "" Added: docs/enterprise/trunk/Reference_Guide/ja-JP/XML_Descriptors.po =================================================================== --- docs/enterprise/trunk/Reference_Guide/ja-JP/XML_Descriptors.po (rev 0) +++ docs/enterprise/trunk/Reference_Guide/ja-JP/XML_Descriptors.po 2009-08-14 00:54:27 UTC (rev 13759) @@ -0,0 +1,3338 @@ +# Language ja-JP translations for Reference_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Reference_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:52+0000\n" +"PO-Revision-Date: 2009-08-14 00:52+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: XML_Descriptors.xml:6 +#, no-c-format +msgid "XML Descriptors" +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:8 +#, no-c-format +msgid "DTDs" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:9 +#, no-c-format +msgid "" +"To use a DTD, add the following declaration to the start of the desired " +"descriptors:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:12 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" +"<!DOCTYPE deployments PUBLIC\n" +"\"-//JBoss Portal//DTD Portal Object 2.6//EN\"\n" +"\"http://www.jboss.org/portal/dtd/portal-object_2_6.dtd\">]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:13 +#, no-c-format +msgid "" +"If you do not use the DTD declaration, the previous mechanism for XML " +"validation is used. The DTD is more strict, specifically with the order of " +"XML elements. The following is an example from a <filename>*-object.xml</" +"filename> descriptor, which is valid if you are not using the DTD, but is " +"rejected if you are:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:16 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<if-exists>overwrite</if-exists>\n" +"<parent-ref>default.default</parent-ref>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:17 +#, no-c-format +msgid "" +"The correct element order, and one which is valid against the DTD, is as " +"follows:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:20 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<parent-ref>default.default</parent-ref>\n" +"<if-exists>overwrite</if-exists>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:21 +#, no-c-format +msgid "The following DTDs are available:" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:27 +#, no-c-format +msgid "" +"for <filename>-object.xml</filename> descriptors: <userinput>\"-//JBoss " +"Portal//DTD Portal Object 2.6//EN\"</userinput>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:32 +#, no-c-format +msgid "" +"for <filename>jboss-app.xml</filename> descriptors: <userinput>\"-//JBoss " +"Portal//DTD JBoss Web Application 2.6//EN\"</userinput>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:37 +#, no-c-format +msgid "" +"for <filename>jboss-portlet.xml</filename> descriptors: <userinput>\"-//" +"JBoss Portal//DTD JBoss Portlet 2.6//EN\"</userinput>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:42 +#, no-c-format +msgid "" +"for <filename>portlet-instances.xml</filename> descriptors: <userinput>\"-//" +"JBoss Portal//DTD Portlet Instances 2.6//EN\"</userinput>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:48 +#, no-c-format +msgid "" +"The DTDs are located in the <filename>$JBOSS_HOME/server/" +"<replaceable>configuration</replaceable>/deploy/jboss-portal.sar/dtd/</" +"filename> directory." +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:52 +#, no-c-format +msgid "The JBoss Portlet DTD" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:53 +#, no-c-format +msgid "" +"The following items refer to elements found in the JBoss Portlet DTD, " +"<filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/" +"jboss-portal.sar/dtd/jboss-portlet_<replaceable>version_number</replaceable>." +"dtd</filename>:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:56 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT portlet-app (remotable?,portlet*,service*)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:57 +#, no-c-format +msgid "" +"Use the <computeroutput>&lt;remotable&gt;</computeroutput> element to " +"configure the default behavior of portlets with respect to WSRP exposure: if " +"no value is given, the value is either the value globally defined at the " +"portlet application level, or <computeroutput>false</computeroutput>. " +"Accepted values are <computeroutput>true</computeroutput> and " +"<computeroutput>false</computeroutput>." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:60 +#, no-c-format +msgid "" +"You can configure specific settings of the portlet container for each " +"portlet defined in the <filename>WEB-INF/portlet.xml</filename> file. Use " +"the <computeroutput>&lt;service&gt;</computeroutput> element to inject " +"services into the portlet context of applications." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:63 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT portlet (portlet-name,remotable?,ajax?,session-config?," +"transaction?,\n" +"header-content?,portlet-info?)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:64 +#, no-c-format +msgid "" +"Additional configuration of the portlet. The <computeroutput>&lt;portlet-" +"name&gt;</computeroutput> element defines the portlet name. It must match a " +"portlet defined in the <filename>WEB-INF/portlet.xml</filename> file for " +"that application." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:67 +#, no-c-format +msgid "" +"Use the <computeroutput>&lt;remotable&gt;</computeroutput> element to " +"configure the default behavior of portlets with respect to WSRP exposure: if " +"no value is given, the value is either the value globally defined at the " +"portlet application level, or <computeroutput>false</computeroutput>." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:70 +#, no-c-format +msgid "" +"The <computeroutput>&lt;trans-attribute&gt;</computeroutput> element " +"specifies the behavior of the portlet when it is invoked at runtime with " +"respect to the transactional context. Depending on how the portlet is " +"invoked, a transaction may or may not exist before the portlet is invoked. " +"The portal transaction is usually present in the local context. The default " +"value is <computeroutput>NotSupported</computeroutput>, which means that the " +"portal transaction is suspended for the duration of the portlet's " +"invocation. Accepted values are <computeroutput>Required</computeroutput>, " +"<computeroutput>Mandatory</computeroutput>, <computeroutput>Never</" +"computeroutput>, <computeroutput>Supports</computeroutput>, " +"<computeroutput>NotSupported</computeroutput>, and " +"<computeroutput>RequiresNew</computeroutput>." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:74 +#, no-c-format +msgid "" +"The following is an example section from a <filename>WEB-INF/portlet.xml</" +"filename> file, which uses the <computeroutput>&lt;portlet-name&gt;</" +"computeroutput>, <computeroutput>&lt;remotable&gt;</computeroutput>, and " +"<computeroutput>&lt;trans-attribute&gt;</computeroutput> elements:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:77 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<portlet>\n" +" <portlet-name>MyPortlet</portlet-name>\n" +" <remotable>true</remotable>\n" +" <trans-attribute>Required</trans-attribute>\n" +"</portlet>]]>" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:78 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT portlet-name (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:78 +#, no-c-format +msgid "The portlet name." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:81 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT remotable (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:82 +#, no-c-format +msgid "" +"Accepted values are <computeroutput>true</computeroutput> and " +"<computeroutput>false</computeroutput>." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:85 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT ajax (partial-refresh)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:86 +#, no-c-format +msgid "" +"Use the <computeroutput>ajax</computeroutput> element to configure the " +"Asynchronous JavaScript and XML (AJAX) capabilities of the portlet." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:89 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT partial-refresh (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:90 +#, no-c-format +msgid "" +"If a portlet uses the <computeroutput>true</computeroutput> value for the " +"<computeroutput>&lt;partial-refresh&gt;</computeroutput> element, the portal " +"uses partial-page refreshing and only renders that portlet. If the " +"<computeroutput>&lt;partial-refresh&gt;</computeroutput> element uses a " +"<computeroutput>false</computeroutput> value, the portal uses a full-page " +"refresh when the portlet is refreshed." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:93 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT session-config (distributed)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:94 +#, no-c-format +msgid "" +"The <computeroutput>&lt;session-config&gt;</computeroutput> element " +"configures the portlet session for the portlet. The <computeroutput>&lt;" +"distributed&gt;</computeroutput> element instructs the container to " +"distribute the session attributes using portal session replication. This " +"only applies to local portlets, not remote portlets." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:97 +#, no-c-format +msgid "" +"The following is an example of the <computeroutput>&lt;session-config&gt;</" +"computeroutput> and <computeroutput>&lt;distributed&gt;</computeroutput> " +"elements:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:100 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<session-config>\n" +" <distributed>true</distributed>\n" +"</session-config>]]>" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:101 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT distributed (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:102 +#, no-c-format +msgid "" +"Accepted values are <computeroutput>true</computeroutput> and " +"<computeroutput>false</computeroutput>. The default value is " +"<computeroutput>false</computeroutput>." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:105 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT transaction (trans-attribute)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:106 +#, no-c-format +msgid "" +"The <computeroutput>&lt;transaction&gt;</computeroutput> element defines how " +"the portlet behaves with regards to the transactional context. The " +"<computeroutput>&lt;trans-attribute&gt;</computeroutput> element specifies " +"the behavior of the portlet when it is invoked at runtime, with respect to " +"the transactional context. Depending on how the portlet is invoked, a " +"transaction may or may not exist before the portlet is invoked. The portal " +"transaction is usually present in the local context." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:109 +#, no-c-format +msgid "" +"The following is an example of the <computeroutput>&lt;transaction&gt;</" +"computeroutput> and <computeroutput>&lt;trans-attribute&gt;</computeroutput> " +"elements:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:112 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<transaction>\n" +" <trans-attribute>Required</transaction>\n" +"<transaction>]]>" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:113 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT trans-attribute (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:114 +#, no-c-format +msgid "" +"The default value is <computeroutput>NotSupported</computeroutput>, which " +"means that the portal transaction is suspended for the duration of the " +"portlet's invocation. Accepted values are <computeroutput>Required</" +"computeroutput>, <computeroutput>Mandatory</computeroutput>, " +"<computeroutput>Never</computeroutput>, <computeroutput>Supports</" +"computeroutput>, <computeroutput>NotSupported</computeroutput>, and " +"<computeroutput>RequiresNew</computeroutput>." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:117 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT header-content (link|script|meta)*>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:118 +#, no-c-format +msgid "" +"Specify the content to be included in the portal aggregated page when the " +"portlet is present on that page. This setting only applies when the portlet " +"is used in the local mode." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:121 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT link EMPTY>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:122 +#, no-c-format +msgid "No content is allowed inside a link element." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:125 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT script (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:126 +#, no-c-format +msgid "" +"Use the <computeroutput>&lt;script&gt;</computeroutput> element for inline " +"script definitions." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:129 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT meta EMPTY>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:130 +#, no-c-format +msgid "" +"No content is allowed for the <computeroutput>&lt;meta&gt;</computeroutput> " +"element." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:133 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT service (service-name,service-class,service-ref)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:134 +#, no-c-format +msgid "" +"Declare a service that will be injected by the portlet container as an " +"attribute of the portlet context." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:137 +#, no-c-format +msgid "" +"The following is an example of the <computeroutput>&lt;service&gt;</" +"computeroutput> element:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:140 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<service>\n" +" <service-name>UserModule</service-name>\n" +" <service-class>org.jboss.portal.identity.UserModule</service-class>\n" +" <service-ref>:service=Module,type=User</service-ref>\n" +"</service>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:141 +#, no-c-format +msgid "" +"To use an injected service in a portlet, perform a lookup of the " +"<computeroutput>&lt;service-name&gt;</computeroutput>, for example, using " +"the <computeroutput>init()</computeroutput> lifecycle method:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:144 +#, no-c-format +msgid "" +"<![CDATA[\n" +"public void init()\n" +"{\n" +" UserModule userModule = (UserModule)getPortletContext().getAttribute" +"(\"UserModule\");\n" +"}]]>" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:145 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT service-name (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:146 +#, no-c-format +msgid "" +"The <computeroutput>&lt;service-name&gt;</computeroutput> element defines " +"the name that binds the service as a portlet context attribute." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:149 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT service-class (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:150 +#, no-c-format +msgid "" +"The <computeroutput>&lt;service-class&gt;</computeroutput> element defines " +"the fully qualified name of the interface that the service implements." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:153 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT service-ref (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:154 +#, no-c-format +msgid "" +"The <computeroutput>&lt;service-ref&gt;</computeroutput> element defines the " +"reference to the service. In the JMX Microkernel environment, this consist " +"of the JMX name of the service MBean. For an MBean reference, if the domain " +"is left out, the current domain of the portal is used." +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:159 +#, no-c-format +msgid "The JBoss Portlet Instance DTD" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:160 +#, no-c-format +msgid "" +"The following items refer to elements found in the JBoss Portlet Instance " +"DTD, <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/" +"deploy/jboss-portal.sar/dtd/portlet-instances_<replaceable>version_number</" +"replaceable>.dtd</filename>:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:163 XML_Descriptors.xml:259 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT deployments (deployment*)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:164 XML_Descriptors.xml:260 +#, no-c-format +msgid "" +"The <computeroutput>&lt;deployments&gt;</computeroutput> element is a " +"container for <computeroutput>&lt;deployment&gt;</computeroutput> elements." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:167 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT deployment (if-exists?,instance)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:168 +#, no-c-format +msgid "" +"The <computeroutput>&lt;deployment&gt;</computeroutput> element is a " +"container for the <computeroutput>&lt;instance&gt;</computeroutput> element." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:171 XML_Descriptors.xml:309 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT if-exists (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:172 XML_Descriptors.xml:541 +#, no-c-format +msgid "" +"The <computeroutput>&lt;if-exists&gt;</computeroutput> element defines the " +"action to take if an instance with the same name already exists. Accepted " +"values are <computeroutput>overwrite</computeroutput> and " +"<computeroutput>keep</computeroutput>. The <computeroutput>overwrite</" +"computeroutput> option destroys the existing object, and creates a new one " +"based on the content of the deployment. The <computeroutput>keep</" +"computeroutput> option maintains the existing object deployment, or creates " +"a new one if it does not exist." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:175 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT instance (instance-id,portlet-ref,display-name*,preferences?,\n" +"security-constraint?, (display-name* | (resource-bundle, supported-locale+)))" +">]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:176 +#, no-c-format +msgid "" +"The <computeroutput>&lt;instance&gt;</computeroutput> element is used in the " +"<filename>WEB-INF/portlet-instances.xml</filename> file, which creates " +"instances of portlets. The portlet will only be created and configured if " +"the portlet is present, and if an instance with the same name does not " +"already exist." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:179 +#, no-c-format +msgid "" +"The following is an example of the <computeroutput>&lt;instance&gt;</" +"computeroutput> element, which also contains the <computeroutput>&lt;" +"security-constraint&gt;</computeroutput> element. Descriptions of each " +"element follow afterwards:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:182 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<instance>\n" +" <instance-id>MyPortletInstance</instance-id>\n" +" <portlet-ref>MyPortlet</portlet-ref>\n" +" <preferences>\n" +" <preference>\n" +" <name>abc</name>\n" +" <value>def</value>\n" +" </preference>\n" +" </preferences>\n" +" <security-constraint>\n" +" <policy-permission>\n" +" <role-name>User</role-name>\n" +" <action-name>view</action-name>\n" +" </policy-permission>\n" +" </security-constraint>\n" +"</instance>]]>" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:183 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT instance-id (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:184 +#, no-c-format +msgid "" +"The instance identifier. The <computeroutput>&lt;instance-id&gt;</" +"computeroutput> value can be named anything, but it must match the " +"<computeroutput>&lt;instance-ref&gt;</computeroutput>value given in the " +"<filename>*-object.xml</filename> file." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:187 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT portlet-ref (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:188 XML_Descriptors.xml:646 +#, no-c-format +msgid "" +"The <computeroutput>&lt;portlet-ref&gt;</computeroutput> element defines the " +"portlet that an instance represents. The <computeroutput>&lt;portlet-ref&gt;" +"</computeroutput> value must match the <computeroutput>&lt;portlet-name&gt;</" +"computeroutput> given in the <filename>WEB-INF/portlet.xml</filename> file." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:191 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT preferences (preference+)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:192 +#, no-c-format +msgid "" +"The <computeroutput>&lt;preferences&gt;</computeroutput> element configures " +"an instance with a set of preferences." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:195 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT preference (name,value)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:196 XML_Descriptors.xml:660 +#, no-c-format +msgid "" +"The <computeroutput>&lt;preference&gt;</computeroutput> element configures " +"one preference, which is part of a set of preferences. Use the " +"<computeroutput>&lt;preferences&gt;</computeroutput> element to define a set " +"of preferences." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:199 XML_Descriptors.xml:434 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT name (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:200 +#, no-c-format +msgid "A name." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:203 XML_Descriptors.xml:438 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT value (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:204 +#, no-c-format +msgid "A string value." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:207 XML_Descriptors.xml:442 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT security-constraint (policy-permission*)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:208 XML_Descriptors.xml:443 XML_Descriptors.xml:1137 +#, no-c-format +msgid "" +"The <computeroutput>&lt;security-constraint&gt;</computeroutput> element is " +"a container for <computeroutput>&lt;policy-permission&gt;</computeroutput> " +"elements. The following is an example of the <computeroutput>&lt;security-" +"constraint&gt;</computeroutput> and <computeroutput>&lt;policy-permission&gt;" +"</computeroutput> elements:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:211 XML_Descriptors.xml:446 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<security-constraint>\n" +" <policy-permission>\n" +" <role-name>User</role-name>\n" +" <action-name>view</action-name>\n" +" </policy-permission>\n" +"</security-constraint>\n" +"\n" +"<security-constraint>\n" +" <policy-permission>\n" +" <unchecked/>\n" +" <action-name>view</action-name>\n" +" </policy-permission>\n" +"</security-constraint>]]>" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:212 XML_Descriptors.xml:447 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT policy-permission (action-name*,unchecked?,role-name*)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:213 +#, no-c-format +msgid "" +"The <computeroutput>&lt;policy-permission&gt;</computeroutput> element " +"secures a specific portlet instance based on a user's role." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:216 XML_Descriptors.xml:451 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT action-name (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:217 XML_Descriptors.xml:452 XML_Descriptors.xml:671 +#: XML_Descriptors.xml:1146 +#, no-c-format +msgid "" +"The <computeroutput>&lt;action-name&gt;</computeroutput> element defines the " +"access rights given to the role defined. Accepted values are:" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:223 XML_Descriptors.xml:458 XML_Descriptors.xml:677 +#: XML_Descriptors.xml:1152 +#, no-c-format +msgid "<computeroutput>view</computeroutput>: users can view the page." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:228 XML_Descriptors.xml:463 XML_Descriptors.xml:682 +#: XML_Descriptors.xml:1157 +#, no-c-format +msgid "" +"<computeroutput>viewrecursive</computeroutput>: users can view the page and " +"child pages." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:233 XML_Descriptors.xml:468 XML_Descriptors.xml:687 +#: XML_Descriptors.xml:1162 +#, no-c-format +msgid "" +"<computeroutput>personalize</computeroutput>: users are able personalize the " +"page's theme." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:238 XML_Descriptors.xml:473 XML_Descriptors.xml:692 +#: XML_Descriptors.xml:1167 +#, no-c-format +msgid "" +"<computeroutput>personalizerecursive</computeroutput>: users are able " +"personalize the page and child pages themes." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:244 XML_Descriptors.xml:479 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT unchecked EMPTY>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:245 +#, no-c-format +msgid "" +"If present, the <computeroutput>&lt;unchecked&gt;</computeroutput> element " +"defines anyone can view the instance." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:248 XML_Descriptors.xml:483 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT role-name (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:249 XML_Descriptors.xml:1182 +#, no-c-format +msgid "" +"The <computeroutput>&lt;role-name&gt;</computeroutput> element defines a " +"role that the security constraint will apply to. The following example only " +"allows users that are part of the <computeroutput>EXAMPLEROLE</" +"computeroutput> role to access the instance:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:252 XML_Descriptors.xml:487 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<role-name>EXAMPLEROLE</role-name>]]>" +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:255 +#, no-c-format +msgid "The JBoss Portal Object DTD" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:256 +#, no-c-format +msgid "" +"The following items refer to elements found in the JBoss Portal Object DTD, " +"<filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/" +"jboss-portal.sar/dtd/portal-object_<replaceable>version_number</replaceable>." +"dtd</filename>:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:263 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT deployment (parent-ref?,if-exists?,(context|portal|page|window))>]]" +">" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:264 +#, no-c-format +msgid "" +"The <computeroutput>&lt;deployment&gt;</computeroutput> element is a generic " +"container for portal object elements. The <computeroutput>&lt;parent-ref&gt;" +"</computeroutput> child element gives the name of the parent object that the " +"current object will use as parent. The optional <computeroutput>&lt;if-" +"exists&gt;</computeroutput> element defines the action to take if an " +"instance with the same name already exists. The default behavior of the " +"<computeroutput>&lt;if-exists&gt;</computeroutput> element is to keep the " +"existing object, and not to create a new object." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:267 +#, no-c-format +msgid "" +"The following is an example of the <computeroutput>&lt;deployment&gt;</" +"computeroutput> and <computeroutput>&lt;parent-ref&gt;</computeroutput> " +"elements:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:270 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<deployment>\n" +" <parent-ref>default</parent-ref>\n" +" <page>\n" +" ...\n" +" </page>\n" +"</deployment>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:271 +#, no-c-format +msgid "All portal objects have a common configuration which can include:" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:277 +#, no-c-format +msgid "" +"a listener: specifies the ID of a listener in the listener registry. A " +"listener object is able to listen to portal events, which apply to the " +"portal node hierarchy." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:282 +#, no-c-format +msgid "" +"properties: a set of generic properties owned by the portal object. Certain " +"properties drive the behavior of the portal object." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:287 +#, no-c-format +msgid "" +"security-constraint: defines the security configuration for the portal " +"object." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:293 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT parent-ref (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:294 XML_Descriptors.xml:549 XML_Descriptors.xml:1071 +#, no-c-format +msgid "" +"The <computeroutput>&lt;parent-ref&gt;</computeroutput> element contains a " +"reference to the parent object. The naming convention for naming objects is " +"to concatenate the names of the path to the object, and separate the names " +"using a period. If the path is empty, the empty string must be used. The " +"<computeroutput>&lt;parent-ref&gt;</computeroutput> element tells the portal " +"where the portlet appears. The syntax for the <computeroutput>&lt;parent-" +"ref&gt;</computeroutput> element is <computeroutput><replaceable>portal-" +"instance</replaceable>.<replaceable>portal-page</replaceable></" +"computeroutput>." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:297 +#, no-c-format +msgid "The following is an example of the root having an empty path:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:300 +#, no-c-format +msgid "&lt;parent-ref /&gt;" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:301 +#, no-c-format +msgid "" +"The following specifies that the portlet appears in the portal instance " +"named <computeroutput>default</computeroutput>:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:304 +#, no-c-format +msgid "&lt;parent-ref&gt;default&lt;/parent-ref&gt;" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:305 +#, no-c-format +msgid "" +"The following specifies that the portlet appear in the portal instance named " +"<computeroutput>default</computeroutput>, and on the page named " +"<computeroutput>default</computeroutput>:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:308 +#, no-c-format +msgid "&lt;parent-ref&gt;default.default&lt;/parent-ref&gt;" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:310 XML_Descriptors.xml:1065 +#, no-c-format +msgid "" +"The <computeroutput>&lt;if-exists&gt;</computeroutput> element defines the " +"action to take if an instance with the same name already exists. Accepted " +"values are <computeroutput>overwrite</computeroutput> and " +"<computeroutput>keep</computeroutput>. The <computeroutput>overwrite</" +"computeroutput> option destroys the existing object, and creates a new one " +"based on the content of the deployment. The <computeroutput>keep</" +"computeroutput> option matains the existing object deployment, or creates a " +"new one if it does not exist." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:313 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT context (context-name,properties?,listener?,security-constraint?," +"portal*,\n" +"(display-name* | (resource-bundle, supported-locale+)))>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:314 +#, no-c-format +msgid "" +"The context type of the portal object. A context type represent a node in a " +"tree, which does not have a visual representation, and only exists under the " +"root. A context can only have children that use the <emphasis>portal</" +"emphasis> type." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:317 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT context-name (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:318 +#, no-c-format +msgid "The context name." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:321 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT portal (portal-name,supported-modes,supported-window-states?," +"properties?,listener?,\n" +"security-constraint?,page*, (display-name* | (resource-bundle, supported-" +"locale+)))>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:322 +#, no-c-format +msgid "" +"A portal object that uses the <emphasis>portal</emphasis> type. A portal " +"type represents a virtual portal, and can only have children that use the " +"<emphasis>page</emphasis> type. In addition to the common portal object " +"elements, it also allows you to declare modes and window states that are " +"supported." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:325 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT portal-name (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:326 +#, no-c-format +msgid "The portal name." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:329 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT supported-modes (mode*)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:330 +#, no-c-format +msgid "" +"The <computeroutput>&lt;supported-modes&gt;</computeroutput> elements " +"defines the supported modes of the portal. Accepted values are " +"<computeroutput>view</computeroutput>, <computeroutput>edit</" +"computeroutput>, and <computeroutput>help</computeroutput>." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:333 +#, no-c-format +msgid "" +"The following is an example of the <computeroutput>&lt;supported-mode&gt;</" +"computeroutput> and <computeroutput>&lt;mode&gt;</computeroutput> elements:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:336 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<supported-mode>\n" +" <mode>view</mode>\n" +" <mode>edit</mode>\n" +" <mode>help</mode>\n" +"</supported-mode>]]>" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:337 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT mode (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:338 +#, no-c-format +msgid "" +"The portlet mode value. If there are no declarations of modes or window " +"states, the default values are <computeroutput>view</computeroutput>, " +"<computeroutput>edit</computeroutput>, <computeroutput>help</" +"computeroutput>, and <computeroutput>normal</computeroutput>, " +"<computeroutput>minimized</computeroutput>, <computeroutput>maximized</" +"computeroutput>, respectively." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:341 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT supported-window-states (window-state*)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:342 +#, no-c-format +msgid "" +"Use the <computeroutput>&lt;supported-window-states&gt;</computeroutput> " +"element to define the supported window states of the portal. The following " +"is an example of the <computeroutput>&lt;supported-window-states&gt;</" +"computeroutput> and <computeroutput>&lt;window-state&gt;</computeroutput> " +"elements:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:345 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<supported-window-states>\n" +" <window-state>normal</window-state>\n" +" <window-state>minimized</window-state>\n" +" <window-state>maximized</window-state>\n" +"</supported-window-states>]]>" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:346 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT window-state (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:347 +#, no-c-format +msgid "" +"Use the <computeroutput>&lt;window-state&gt;</computeroutput> element to " +"define a window states. Accepted values are <computeroutput>normal</" +"computeroutput>, <computeroutput>minimized</computeroutput>, and " +"<computeroutput>maximized</computeroutput>." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:350 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT page (page-name,properties?,listener?,security-constraint?,(page | " +"window)*,\n" +"(display-name* | (resource-bundle, supported-locale+)))>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:351 +#, no-c-format +msgid "" +"A portal object that uses the <emphasis>page</emphasis> type. A page type " +"represents a page, and can only have children that use the <emphasis>page</" +"emphasis> and <emphasis>window</emphasis> types. The children windows are " +"the windows of the page, and the children pages are the subpages of the page." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:354 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT page-name (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:355 XML_Descriptors.xml:1089 +#, no-c-format +msgid "The page name." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:358 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT window (window-name,(instance-ref|content),region,height,initial-" +"window-state?,\n" +"initial-mode?,properties?,listener?, (display-name* | (resource-bundle, " +"supported-locale+)))>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:359 +#, no-c-format +msgid "" +"A portal object that uses the <emphasis>window</emphasis> type. A window " +"type represents a window. Besides the common properties, a window has " +"content, and belongs to a region on the page." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:362 +#, no-c-format +msgid "" +"The <computeroutput>&lt;instance-ref&gt;</computeroutput> and " +"<computeroutput>&lt;content&gt;</computeroutput> elements, configured in the " +"<filename>WEB-INF/*-object.xml</filename> files, define the content of a " +"window. The <computeroutput>&lt;content&gt;</computeroutput> element is " +"generic, and describes any kind of content. The <computeroutput>&lt;instance-" +"ref&gt;</computeroutput> element is a shortcut to define the content-type of " +"the portlet, which points to a portlet instance. The value of " +"<computeroutput>&lt;instance-ref&gt;</computeroutput> must match the value " +"of one of the <computeroutput>&lt;instance-id&gt;</computeroutput> elements " +"in the <filename>WEB-INF/portlet-instances.xml</filename> file." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:365 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT window-name (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:366 +#, no-c-format +msgid "The window name value." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:369 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT instance-ref (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:370 +#, no-c-format +msgid "" +"Define the content of the window as a reference to a portlet instance. This " +"value is the ID of a portlet instance, and must much the value of one of the " +"<computeroutput>&lt;instance-id&gt;</computeroutput> elements in the " +"<filename>WEB-INF/portlet-instances.xml</filename> file. The following is an " +"example of the <computeroutput>&lt;instance-ref&gt;</computeroutput> element:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:373 +#, no-c-format +msgid "&lt;instance-ref&gt;MyPortletInstance&lt;/instance-ref&gt;" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:374 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT region (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:375 +#, no-c-format +msgid "" +"The region the window belongs to. The <computeroutput>&lt;region&gt;</" +"computeroutput> element specifies where the window appears on the page." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:378 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT height (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:379 +#, no-c-format +msgid "The height of the window in a particular region." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:382 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT listener (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:383 +#, no-c-format +msgid "" +"Define a listener for a portal object. This value is the ID of the listener." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:386 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT content (content-type,content-uri)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:387 +#, no-c-format +msgid "" +"Define the content of a window in a generic manner. The content is defined " +"by the type of content, and a URI, which acts as an identifier for the " +"content. The following is an example of the <computeroutput>&lt;content&gt;</" +"computeroutput> element, which is configured in the <filename>WEB-INF/*-" +"object.xml</filename> files:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:390 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<content>\n" +" <content-type>portlet</content-type>\n" +" <content-uri>MyPortletInstance</content-uri>\n" +"</content>\n" +"\n" +"<content>\n" +" <content-type>cms</content-type>\n" +" <content-uri>/default/index.html</content-uri>\n" +"</content>]]>" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:391 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT content-type (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:392 +#, no-c-format +msgid "" +"The content type of the window. The <computeroutput>&lt;content-type&gt;</" +"computeroutput> element specifies the content to display, for example, a " +"<computeroutput>portlet</computeroutput>." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:395 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT content-uri (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:396 +#, no-c-format +msgid "" +"The content URI of the window. The <computeroutput>&lt;content-uri&gt;</" +"computeroutput> element specifies which content to display, for example, a " +"portlet instance. To display a file from the CMS, use the " +"<computeroutput>&lt;content-uri&gt;</computeroutput> element to define the " +"full path to that file in the CMS." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:399 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT properties (property*)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:400 +#, no-c-format +msgid "" +"A set of generic properties for the portal object. The <computeroutput>&lt;" +"properties&gt;</computeroutput> elements contain definitions specific to a " +"portal object." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:403 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT property (name,value)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:404 +#, no-c-format +msgid "" +"A generic string property. The following table lists accepted values. This " +"table is not exhaustive:" +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:407 +#, no-c-format +msgid "Properties" +msgstr "" + +#. Tag: entry +#: XML_Descriptors.xml:413 +#, no-c-format +msgid "Name" +msgstr "" + +#. Tag: entry +#: XML_Descriptors.xml:414 +#, no-c-format +msgid "Description" +msgstr "" + +#. Tag: computeroutput +#: XML_Descriptors.xml:419 +#, no-c-format +msgid "layout.id" +msgstr "" + +#. Tag: entry +#: XML_Descriptors.xml:420 +#, no-c-format +msgid "" +"Defines the layout to use for the portal object and sub-objects if they do " +"not override the value." +msgstr "" + +#. Tag: computeroutput +#: XML_Descriptors.xml:423 +#, no-c-format +msgid "theme.id" +msgstr "" + +#. Tag: entry +#: XML_Descriptors.xml:424 +#, no-c-format +msgid "" +"Defines the theme used for the portal object and sub-objects if they do not " +"override the value." +msgstr "" + +#. Tag: computeroutput +#: XML_Descriptors.xml:427 +#, no-c-format +msgid "portal.defaultObjectName" +msgstr "" + +#. Tag: entry +#: XML_Descriptors.xml:428 +#, no-c-format +msgid "" +"Defines the default child object. If applied to a <literal>context</" +"literal>, it defines the default portal. If applied to a <literal>portal</" +"literal>, it defines the default portal page." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:435 +#, no-c-format +msgid "A name value." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:439 +#, no-c-format +msgid "A value." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:448 +#, no-c-format +msgid "" +"The <computeroutput>&lt;policy-permission&gt;</computeroutput> element is " +"secures a specific portlet instance based on a user's role." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:480 XML_Descriptors.xml:1176 +#, no-c-format +msgid "" +"If present, the <computeroutput>&lt;unchecked&gt;</computeroutput> element " +"defines that anyone can view the instance." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:484 +#, no-c-format +msgid "" +"The <computeroutput>&lt;role-name&gt;</computeroutput> element defines a " +"role that the security constraint applies to. The following example only " +"allows users that are part of the <computeroutput>EXAMPLEROLE</" +"computeroutput> role to access the instance:" +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:490 +#, no-c-format +msgid "The JBoss Portal App DTD" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:491 +#, no-c-format +msgid "" +"The following items refer to elements found in the JBoss Portal App DTD, " +"<filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/jboss-" +"portal.sar/dtd/jboss-app_<replaceable>version_number</replaceable>.dtd</" +"filename>:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:494 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<Element <![CDATA[<!ELEMENT jboss-app (app-name?)>]]>" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:495 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!DOCTYPE jboss-app PUBLIC\n" +" \"-//JBoss Portal//DTD JBoss Web Application 2.6//EN\"\n" +" \"http://www.jboss.org/portal/dtd/jboss-app_2_6.dtd\">]]>" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:496 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!ELEMENT app-name (#PCDATA)>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:497 +#, no-c-format +msgid "" +"When a web application is deployed, the context path under which it is " +"deployed is taken as the application name. The application name value in the " +"<computeroutput>&lt;app-name&gt;</computeroutput> element overrides it. When " +"a component references a portlet, it needs to reference the application too, " +"and if the portlet application WAR file is renamed, the reference is no " +"longer valid; therefore, the <computeroutput>&lt;app-name&gt;</" +"computeroutput> element is used to have an application name that does not " +"depend upon the context path, under which the application is deployed." +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:505 +#, no-c-format +msgid "Portlet Descriptors" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:506 +#, no-c-format +msgid "" +"The following sections describe the descriptors that define portal objects, " +"such as portals, pages, portlet instances, windows, and portlets. Refer to " +"<xref linkend=\"tutorials_tutorials\"/> and <xref linkend=\"desc_examples\"/" +"> for examples on using these descriptors within a portlet application." +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:510 +#, no-c-format +msgid "<filename>*-object.xml</filename> Descriptors" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:511 +#, no-c-format +msgid "" +"The <filename>*-object.xml</filename> descriptors define portal instances, " +"pages, windows, and the window layout. You can define several files if you " +"want to split them into many files, they just all have to end with '-object." +"xml'. As well, themes and layouts for specific portal instances, pages, and " +"windows, can be defined. The following example defines a portlet window " +"being added to the <computeroutput>default</computeroutput> page, in the " +"<computeroutput>default</computeroutput> portal. For advanced functionality " +"using these descriptors, refer to <xref linkend=\"desc_examples\"/>:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:519 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" +"<!DOCTYPE deployments PUBLIC\n" +" \"-//JBoss Portal//DTD Portal Object 2.6//EN\"\n" +" \"http://www.jboss.org/portal/dtd/portal-object_2_6.dtd\">\n" +"<deployments>\n" +" <deployment>\n" +" <parent-ref>default.default</parent-ref>\n" +" <if-exists>overwrite</if-exists>\n" +" <window>\n" +" <window-name>HelloWorldJSPPortletWindow</window-name>\n" +" <instance-ref>HelloWorldJSPPortletInstance</instance-ref>\n" +" <region>center</region>\n" +" <height>1</height>\n" +" </window>\n" +" </deployment>\n" +"</deployments>]]>" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:523 XML_Descriptors.xml:620 +#, no-c-format +msgid "<![CDATA[<deployments>...</deployments>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:525 XML_Descriptors.xml:622 +#, no-c-format +msgid "" +"The <computeroutput>&lt;deployments&gt;</computeroutput> element " +"encapsulates the entire document, and is a container for <computeroutput>&lt;" +"deployment&gt;</computeroutput> elements. Multiple deployments can be " +"specified within the <computeroutput>&lt;deployments&gt;</computeroutput> " +"element." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:531 +#, no-c-format +msgid "<![CDATA[<deployment>...</deployment>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:533 +#, no-c-format +msgid "" +"The <computeroutput>&lt;deployment&gt;</computeroutput> element specifies " +"object deployments, such as portals, pages, windows, and so on." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:539 +#, no-c-format +msgid "<![CDATA[<if-exists>...</if-exists>]]>" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:547 +#, no-c-format +msgid "<![CDATA[<parent-ref>...</parent-ref>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:552 +#, no-c-format +msgid "" +"In the example above, a window is defined, and assigned to " +"<computeroutput>default.default</computeroutput>. This means the window " +"appears on the <computeroutput>default</computeroutput> page, in the " +"<computeroutput>default</computeroutput> portal." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:558 +#, no-c-format +msgid "<![CDATA[<window>...</window>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:560 XML_Descriptors.xml:1095 +#, no-c-format +msgid "" +"The <computeroutput>&lt;window&gt;</computeroutput> element defines a " +"portlet window. The <computeroutput>&lt;window&gt;</computeroutput> element " +"requires an <computeroutput>&lt;instance-ref&gt;</computeroutput> element, " +"which assigns a portal instance to a window." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:566 +#, no-c-format +msgid "<![CDATA[<window-name>...</window-name>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:568 XML_Descriptors.xml:1101 +#, no-c-format +msgid "" +"The <computeroutput>&lt;window-name&gt;</computeroutput> element defines the " +"<emphasis role=\"bold\">unique name</emphasis> given to a portlet window. " +"This can be named anything." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:574 +#, no-c-format +msgid "<![CDATA[<instance-ref>...</instance-ref>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:576 XML_Descriptors.xml:1107 +#, no-c-format +msgid "" +"The <computeroutput>&lt;instance-ref&gt;</computeroutput> elements define " +"the portlet instances that windows represent. This value is the ID of a " +"portlet instance, and must match the value of one of the <computeroutput>&lt;" +"instance-id&gt;</computeroutput> elements in the <filename>WEB-INF/portlet-" +"instances.xml</filename> file." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:582 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<region>...</region>\n" +"<height>...</height>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:584 XML_Descriptors.xml:1113 +#, no-c-format +msgid "" +"The <computeroutput>&lt;region&gt;</computeroutput> and <computeroutput>&lt;" +"height&gt;</computeroutput> elements define where the window appears within " +"the page layout. The <computeroutput>&lt;region&gt;</computeroutput> element " +"specifies where the window appears on the page. The <computeroutput>&lt;" +"region&gt;</computeroutput> element often depends on other regions defined " +"in the portal layout. The <computeroutput>&lt;height&gt;</computeroutput> " +"element can be assigned a value between one and <replaceable>X</replaceable>." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:589 +#, no-c-format +msgid "" +"The previous <filename>*-object.xml</filename> example makes reference to " +"items found in other descriptor files. The following diagram illustrates the " +"relationship between the <filename>portlet.xml</filename>, <filename>portlet-" +"instances.xml</filename>, and <filename>*-object.xml</filename> descriptors:" +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:601 +#, no-c-format +msgid "Are <filename>*-object.xml</filename> descriptors required?" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:602 +#, no-c-format +msgid "" +"Technically, they are not. The portal object hierarchy, such as creating " +"portals, pages, instances, and organizing them on the page, can be defined " +"using the management portlet, which is accessible to JBoss Portal " +"administrators." +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:609 +#, no-c-format +msgid "The <filename>portlet-instances.xml</filename> Descriptor" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:610 +#, no-c-format +msgid "" +"The <filename>portlet-instances.xml</filename> descriptor is JBoss Portal " +"specific, and allows developers to instantiate one-or-many instances of one-" +"or-many portlets. The benefit of this allows one portlet to be instantiated " +"several times, with different preference parameters. The following example " +"instantiates two separate instances of the <computeroutput>NewsPortlet</" +"computeroutput>, both using different parameters. One instance draws feeds " +"from Red Hat announcements, and the other from McDonalds announcements:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:614 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<?xml version=\"1.0\" standalone=\"yes\"?>\n" +"<!DOCTYPE deployments PUBLIC\n" +" \"-//JBoss Portal//DTD Portlet Instances 2.6//EN\"\n" +" \"http://www.jboss.org/portal/dtd/portlet-instances_2_6.dtd\">\n" +"<deployments>\n" +" <deployment>\n" +" <instance>\n" +" <instance-id>NewsPortletInstance1</instance-id>\n" +" <portlet-ref>NewsPortlet</portlet-ref>\n" +" <preferences>\n" +" <preference>\n" +" <name>expires</name>\n" +" <value>180</value>\n" +" </preference>\n" +" <preference>\n" +" <name>RssXml</name>\n" +" <value>http://finance.yahoo.com/rss/headline?s=rhat</value>\n" +" </preference>\n" +" </preferences>\n" +" <security-constraint>\n" +" <policy-permission>\n" +" <action-name>view</action-name>\n" +" <unchecked/>\n" +" </policy-permission>\n" +" </security-constraint>\n" +" </instance>\n" +" </deployment>\n" +" <deployment>\n" +" <instance>\n" +" <instance-id>NewsPortletInstance2</instance-id>\n" +" <portlet-ref>NewsPortlet</portlet-ref>\n" +" <preferences>\n" +" <preference>\n" +" <name>expires</name>\n" +" <value>180</value>\n" +" </preference>\n" +" <preference>\n" +" <name>RssXml</name>\n" +" <value>http://finance.yahoo.com/rss/headline?s=mcd</value>\n" +" </preference>\n" +" </preferences>\n" +" <security-constraint>\n" +" <policy-permission>\n" +" <action-name>view</action-name>\n" +" <unchecked/>\n" +" </policy-permission>\n" +" </security-constraint>\n" +" </instance>\n" +" </deployment>\n" +"</deployments>\n" +"]]>" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:628 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<deployment>\n" +" <instance>...</instance>\n" +"</deployment>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:630 +#, no-c-format +msgid "" +"The <computeroutput>&lt;deployment&gt;</computeroutput> element, and the " +"embedded <computeroutput>&lt;instance&gt;</computeroutput> element, specify " +"a portlet instance. The <computeroutput>&lt;deployment&gt;</computeroutput> " +"element specifies object deployments, such as portals, pages, windows, and " +"so on. The <computeroutput>&lt;instance&gt;</computeroutput> element creates " +"instances of portlets. The portlet will only be created and configured if " +"the portlet is present, and if an instance with the same name does not " +"already exist." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:636 +#, no-c-format +msgid "<![CDATA[<instance-id>...</instance-id>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:638 +#, no-c-format +msgid "" +"The <computeroutput>&lt;instance-id&gt;</computeroutput> elements defines a " +"<emphasis role=\"bold\">unique name</emphasis> given to an instance of a " +"portlet. The <computeroutput>&lt;instance-id&gt;</computeroutput> value can " +"be named anything, but it must match the value of one of the " +"<computeroutput>&lt;instance-ref&gt;</computeroutput> elements in the " +"<filename>WEB-INF/*-object.xml</filename> file." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:644 +#, no-c-format +msgid "<![CDATA[<portlet-ref>...</portlet-ref>]]>" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:652 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<preferences>\n" +" <preference>...</preference>\n" +"</preferences>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:654 +#, no-c-format +msgid "" +"The <computeroutput>&lt;preference&gt;</computeroutput> element configures a " +"preference as a key-value pair. This value can be composed of a single " +"string value, for example, the preference <emphasis>fruit</emphasis> can " +"have the <emphasis>apple</emphasis> value. As well, this value can be " +"composed of multiple strings, for example, the preference <emphasis>fruits</" +"emphasis> can have values of <emphasis>apple</emphasis>, <emphasis>orange</" +"emphasis>, and <emphasis>kiwi</emphasis>:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:658 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<preferences>\n" +" <preference>\n" +" <name>fruits</name>\n" +" <value>apple</value>\n" +" <value>orange</value>\n" +" <value>kiwi</value>\n" +" </preference>\n" +"</preferences>\n" +"]]>" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:666 +#, no-c-format +msgid "" +"<![CDATA[<security-constraint>\n" +" <policy-permission>\n" +" <action-name>viewrecursive</action-name>\n" +" <unchecked/>\n" +" </policy-permission>\n" +"</security-constraint>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:668 +#, no-c-format +msgid "" +"The <computeroutput>&lt;security-constraint&gt;</computeroutput> element is " +"a container for <computeroutput>&lt;policy-permission&gt;</computeroutput> " +"elements. This example demonstrates the <computeroutput>&lt;security-" +"constraint&gt;</computeroutput> and <computeroutput>&lt;policy-permission&gt;" +"</computeroutput> elements." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:698 +#, no-c-format +msgid "You must define a role that the security constraint will apply to:" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:704 +#, no-c-format +msgid "<computeroutput>unchecked</computeroutput>: anyone can view the page." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:709 +#, no-c-format +msgid "" +"<computeroutput>&lt;role-name&gt;EXAMPLEROLE&lt;/role-name&gt;</" +"computeroutput>: only allow users that are part of the " +"<computeroutput>EXAMPLEROLE</computeroutput> role to access the instance." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:718 +#, no-c-format +msgid "" +"The previous <filename>portlet-instances.xml</filename> example makes " +"reference to items found in other descriptor files. The following diagram " +"illustrates the relationship between the <filename>portlet.xml</filename>, " +"<filename>portlet-instances.xml</filename>, and <filename>*-object.xml</" +"filename> descriptors:" +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:730 +#, no-c-format +msgid "Is the <filename>portlet-instances.xml</filename> descriptor required?" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:731 +#, no-c-format +msgid "" +"Technically, it is not. The portal object hierarchy, such as creating " +"portals, pages, instances, and organizing them on the page, can be defined " +"using the management portlet, which is accessible to JBoss Portal " +"administrators." +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:737 +#, no-c-format +msgid "The <filename>jboss-portlet.xml</filename> Descriptor" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:738 +#, no-c-format +msgid "" +"The <filename>jboss-portlet.xml</filename> descriptor allows you to use " +"JBoss-specific functionality within your portlet application. This " +"descriptor is covered by the <ulink url=\"http://www.jcp.org/en/jsr/detail?" +"id=168\">JSR-168 Portlet Specification</ulink>, and is normally packaged " +"inside your portlet WAR file, alongside the other descriptors in these " +"sections." +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:742 +#, no-c-format +msgid "Injecting Header Content" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:743 +#, no-c-format +msgid "" +"The following example injects a specific style sheet, <computeroutput>/" +"images/management/management.css</computeroutput>, allowing the portlet to " +"leverage a specific style:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:747 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<?xml version=\"1.0\" standalone=\"yes\"?>\n" +"<!DOCTYPE portlet-app PUBLIC\n" +" \"-//JBoss Portal//DTD JBoss Portlet 2.6//EN\"\n" +" \"http://www.jboss.org/portal/dtd/jboss-portlet_2_6.dtd\">\n" +"<portlet-app>\n" +" <portlet>\n" +" <portlet-name>ManagementPortlet</portlet-name>\n" +" <header-content>\n" +" <link rel=\"stylesheet\" type=\"text/css\" href=\"/images/" +"management/management.css\"\n" +" media=\"screen\"/>\n" +" </header-content>\n" +" </portlet>\n" +"</portlet-app>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:749 +#, no-c-format +msgid "" +"Use the <computeroutput>&lt;header-content&gt;</computeroutput> and " +"<computeroutput>&lt;link&gt;</computeroutput> elements to specify a style " +"sheet." +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:754 +#, no-c-format +msgid "Injecting Services in the portlet Context" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:755 +#, no-c-format +msgid "" +"The following example injects the <computeroutput>UserModule</" +"computeroutput> service as an attribute to the portlet context:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:759 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<?xml version=\"1.0\" standalone=\"yes\"?>\n" +"<!DOCTYPE portlet-app PUBLIC\n" +" \"-//JBoss Portal//DTD JBoss Portlet 2.6//EN\"\n" +" \"http://www.jboss.org/portal/dtd/jboss-portlet_2_6.dtd\">\n" +"<portlet-app>\n" +" <service>\n" +" <service-name>UserModule</service-name>\n" +" <service-class>org.jboss.portal.identity.UserModule</service-class>\n" +" <service-ref>:service=Module,type=User</service-ref>\n" +" </service>\n" +"</portlet-app>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:761 +#, no-c-format +msgid "This allows the portlet to leverage the service, for example:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:765 +#, no-c-format +msgid "" +"<![CDATA[\n" +"UserModule userModule = (UserModule) getPortletContext().getAttribute" +"(\"UserModule\");\n" +"String userId = request.getParameters().getParameter(\"userid\");\n" +"User user = userModule.findUserById(userId);]]>" +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:769 +#, no-c-format +msgid "Defining extra portlet Information" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:770 +#, no-c-format +msgid "" +"As of JBoss Portal 2.6.3, icons can be defined for a portlet by using the " +"<computeroutput>&lt;icon&gt;</computeroutput>, <computeroutput>&lt;small-" +"icon&gt;</computeroutput>, and <computeroutput>&lt;large-icon&gt;</" +"computeroutput> elements:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:774 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<?xml version=\"1.0\" standalone=\"yes\"?>\n" +"<!DOCTYPE portlet-app PUBLIC\n" +" \"-//JBoss Portal//DTD JBoss Portlet 2.6//EN\"\n" +" \"http://www.jboss.org/portal/dtd/jboss-portlet_2_6.dtd\">\n" +"<portlet-app>\n" +" <portlet>\n" +" <portlet-name>ManagementPortlet</portlet-name>\n" +" <portlet-info>\n" +" <icon>\n" +" <small-icon>/images/smallIcon.png</small-icon>\n" +" <large-icon>/images/largeIcon.png</small-icon>\n" +" </icon>\n" +" </portlet-info>\n" +" </portlet>\n" +"</portlet-app>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:776 +#, no-c-format +msgid "" +"References to icons can be absolute, for example, <emphasis>http://www." +"example.com/images/smallIcon.png</emphasis>, or relative to the web " +"application context, for example, <computeroutput>/images/smallIcon.png</" +"computeroutput>. Icons can be used by different parts of the portlet user " +"interface." +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:781 +#, no-c-format +msgid "Portlet Session Replication in a Clustered Environment" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:783 +#, no-c-format +msgid "" +"For information about portlet session replication in clustered environments, " +"refer to <xref linkend=\"portlet_session_replication\"/>." +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:788 +#, no-c-format +msgid "Is the <filename>jboss-portlet.xml</filename> descriptor required?" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:789 +#, no-c-format +msgid "" +"Technically, it is not; however, it may be required to access JBoss-specific " +"functionality that is not covered by the Portlet specification." +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:797 +#, no-c-format +msgid "The <filename>portlet.xml</filename> Descriptor" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:798 +#, no-c-format +msgid "" +"The <filename>portlet.xml</filename> descriptor is the standard portlet " +"descriptor covered by the <ulink url=\"http://www.jcp.org/en/jsr/detail?" +"id=168\">JSR-168 Portlet Specification</ulink>. Developers are strongly " +"encouraged to read the <ulink url=\"http://www.jcp.org/en/jsr/detail?id=168" +"\">JSR-168 Portlet Specification</ulink> items covering the correct use of " +"this descriptor, as it is only covered briefly in these sections. Normally " +"the <filename>portlet.xml</filename> descriptor is packaged inside your " +"portlet WAR file, alongside the other descriptors in these sections. The " +"following example is a modified version of the JBoss Portal UserPortlet " +"definition:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:802 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" +"<portlet-app\n" +" xmlns=\"http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd\"... +" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n" +" xsi:schemaLocation=\"http://java.sun.com/xml/ns/portlet/portlet-" +"app_1_0.xsd\n" +" http://java.sun.com/xml/ns/portlet/portlet-app_1_0." +"xsd\"\n" +" version=\"1.0\">\n" +" <portlet>\n" +" <description>Portlet providing user login/logout and profile " +"management</description>\n" +" <portlet-name>UserPortlet</portlet-name>\n" +" <display-name>User Portlet</display-name>\n" +" <portlet-class>org.jboss.portal.core.portlet.user.UserPortlet</portlet-" +"class>\n" +" <init-param>\n" +" <description>Initialize the portlet with a default page to render</" +"description>\n" +" <name>>default-view</name>\n" +" <value>/WEB-INF/jsf/objects.xhtml</value>\n" +" </init-param>\n" +" <supports>\n" +" <mime-type>text/html</mime-type>\n" +" <portlet-mode>VIEW</portlet-mode>\n" +" </supports>\n" +" <supported-locale>en</supported-locale>\n" +" <supported-locale>fr</supported-locale>\n" +" <supported-locale>es</supported-locale>\n" +" <resource-bundle>Resource</resource-bundle>\n" +" <portlet-info>\n" +" <title>User portlet</title>\n" +" </portlet-info>\n" +" </portlet>\n" +"</portlet-app>]]>" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:808 +#, no-c-format +msgid "<![CDATA[<portlet-app>...</portlet-app>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:810 +#, no-c-format +msgid "" +"The <computeroutput>&lt;portlet-app&gt;</computeroutput> element " +"encapsulates the entire document. Multiple portlets can be specified using " +"the <computeroutput>&lt;portlet-app&gt;</computeroutput> element." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:816 +#, no-c-format +msgid "<![CDATA[<portlet>...</portlet>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:818 +#, no-c-format +msgid "" +"The <computeroutput>&lt;portlet&gt;</computeroutput> element defines one " +"portlet that is deployed within this archive." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:824 +#, no-c-format +msgid "<![CDATA[<description>...</description>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:826 +#, no-c-format +msgid "" +"The <computeroutput>&lt;description&gt;</computeroutput> element is a verbal " +"description of the portlet's function." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:832 +#, no-c-format +msgid "<![CDATA[<portlet-name>...</portlet-name>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:834 +#, no-c-format +msgid "" +"The <computeroutput>&lt;portlet-name&gt;</computeroutput> element defines " +"the portlet name. It does not have to be the class name." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:840 +#, no-c-format +msgid "<![CDATA[<portlet-class>...</portlet-class>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:842 +#, no-c-format +msgid "" +"The <computeroutput>&lt;portlet-class&gt;</computeroutput> element defines " +"the Fully Qualified Name (FQN) of the portlet class." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:848 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<init-param>\n" +" <name>...</name>\n" +" <value>...</value>\n" +"</init-param>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:850 +#, no-c-format +msgid "" +"The <computeroutput>&lt;init-param&gt;</computeroutput> element specifies " +"initialization parameters to create an initial state inside your portlet " +"class. This is usually used in the portlet's <emphasis>init()</emphasis> " +"method, but not necessarily. Unlike a preference, an init-parameter is data " +"that does not change at runtime and does not go into a database. If the " +"value is changed in the descriptor, the change takes immediate effect after " +"re-deploying the portlet. Multiple <computeroutput>&lt;init-param&gt;</" +"computeroutput> elements can be used." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:856 +#, no-c-format +msgid "<![CDATA[<supports>...</supports>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:858 +#, no-c-format +msgid "" +"The <computeroutput>&lt;supports&gt;</computeroutput> element declares all " +"of the markup types that a portlet supports. Use the <computeroutput>&lt;" +"mime-type&gt;</computeroutput> element to declare supported capabilities, " +"for example, if the only outputs are text and HTML, use <computeroutput>&lt;" +"mime-type&gt;text/html&lt;/mime-type&gt;</computeroutput>. Use the " +"<computeroutput>&lt;portlet-mode&gt;</computeroutput> element to define the " +"supported portlet modes for the portlet. For example, all portlets must " +"support the <computeroutput>view</computeroutput> portlet mode, which is " +"defined using <computeroutput>&lt;portlet-mode&gt;view&lt;/portlet-mode&gt;</" +"computeroutput>." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:864 +#, no-c-format +msgid "<![CDATA[<supported-locale>...</supported-locale>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:866 +#, no-c-format +msgid "" +"The <computeroutput>&lt;supported-locale&gt;</computeroutput> elements " +"advertise the supported locales for the portlet. Use multiple " +"<computeroutput>&lt;supported-locale&gt;</computeroutput> elements to " +"specify multiple locales." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:872 +#, no-c-format +msgid "<![CDATA[<resource-bundle>...</resource-bundle>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:874 +#, no-c-format +msgid "" +"The <computeroutput>&lt;resource-bundle&gt;</computeroutput> element " +"specifies the resource bundle that contains the localized information for " +"the specified locales." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:880 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<portlet-info>\n" +" <title>...</title>\n" +"</portlet-info>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:882 +#, no-c-format +msgid "" +"The <computeroutput>&lt;title&gt;</computeroutput> element defines the " +"portlet's title, which is displayed in the portlet window's title bar." +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:890 +#, no-c-format +msgid "The <filename>portlet.xml</filename> Example" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:891 +#, no-c-format +msgid "" +"This <filename>portlet.xml</filename> example is not a replacement for what " +"is covered in the <ulink url=\"http://www.jcp.org/en/jsr/detail?id=168\">JSR-" +"168 Portlet Specification</ulink>." +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:899 +#, no-c-format +msgid "JBoss Portal Descriptors" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:900 +#, no-c-format +msgid "" +"This section describes Datasource descriptors, which are required for JBoss " +"Portal to communicate with a database, and briefly covers the " +"<filename>jboss-portal.sar/conf/config.xml</filename> descriptor, which can " +"be used for configuring logging, and configuring which page a user goes to " +"when they log in." +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:904 +#, no-c-format +msgid "Datasource Descriptors (<filename>portal-*-ds.xml</filename>)" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:905 +#, no-c-format +msgid "" +"JBoss Portal requires a Datasource descriptor to be deployed alongside the " +"<filename>jboss-portal.sar</filename>, in order to communicate with a " +"database. This section explains where to obtain template Datasource " +"descriptors, how to compile them from source, and how to configure them for " +"your installation. For an in-depth introduction to datasources, refer to the " +"JBoss AS documentation online on the <ulink url=\"http://wiki.jboss.org/wiki/" +"Wiki.jsp?page=ConfigDataSources\">JBoss Datasource Wiki page</ulink>." +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:909 +#, no-c-format +msgid "Datasource Descriptors included in Binary releases" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:910 +#, no-c-format +msgid "" +"Several template Datasource descriptors are included in the binary and " +"bundled distributions of JBoss Portal. They are commonly located in the " +"<filename>jboss-portal-<replaceable>version</replaceable>/setup/</filename> " +"directory:" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:921 +#, no-c-format +msgid "" +"The <filename>jboss-portal-<replaceable>version</replaceable>/setup/</" +"filename> directory contains sample Datasource descriptors for the MySQL, " +"Microsoft SQL Server, PostgreSQL, and Oracle databases, which can be " +"customized for your own database:" +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:933 +#, no-c-format +msgid "Building Datasource Descriptors from Source" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:934 +#, no-c-format +msgid "To build the Datasource descriptors from source:" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:940 +#, no-c-format +msgid "Obtain the JBoss Portal source code:" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:945 +#, no-c-format +msgid "" +"Configure the <computeroutput>JBOSS_HOME</computeroutput> environment " +"variable:" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:950 +#, no-c-format +msgid "" +"Change into the <filename>JBOSS_PORTAL_SOURCE_DIRECTORY/build/</filename> " +"directory. To build the JBoss Portal source code on Linux, run the " +"<command>sh build.sh deploy</command> command, or, if you are running " +"Windows, run the <command>build.bat deploy</command> command. If this is the " +"first build, third-party libraries are obtained from an online repository, " +"so you must be connected to the Internet. After building, if the " +"<filename>JBOSS_PORTAL_SOURCE_DIRECTORY/thirdparty/</filename> directory " +"does not exist, it is created, and populated with the files required for " +"later steps." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:955 +#, no-c-format +msgid "" +"Change into the <filename>JBOSS_PORTAL_SOURCE_DIRECTORY/core/</filename> " +"directory, and run the <command>sh build.sh datasource</command> command, " +"or, if you are running Windows, run the <command>build.bat datasource</" +"command> command:" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:968 +#, no-c-format +msgid "" +"Note: if the JBoss Portal source was not built as per step 3, the " +"<command>sh build.sh datasource</command> and <command>build.bat datasource</" +"command> commands fail with an error, such as the following:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:972 +#, no-c-format +msgid "" +"<![CDATA[\n" +"BUILD FAILED\n" +"java.io.FileNotFoundException: /jboss-portal-2.6.3.GA-src/core/../thirdparty/" +"libraries.ent \n" +"(No such file or directory)]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:974 +#, no-c-format +msgid "" +"The datasource build process produces the following directory and file " +"structure, with the Datasource descriptors in the " +"<filename>JBOSS_PORTAL_SOURCE_DIRECTORY/core/output/resources/setup</" +"filename> directory:" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:984 +#, no-c-format +msgid "" +"The following is an example Datasource descriptor for a PostgreSQL database:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:988 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" +"<datasources>\n" +" <local-tx-datasource>\n" +" <jndi-name>PortalDS</jndi-name>\n" +" <connection-url>jdbc:postgresql:jbossportal</connection-url>\n" +" <driver-class>org.postgresql.Driver</driver-class>\n" +" <user-name>portal</user-name>\n" +" <password>portalpassword</password>\n" +" </local-tx-datasource>\n" +"</datasources>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:990 +#, no-c-format +msgid "" +"Make sure the <computeroutput>user-name</computeroutput>, " +"<computeroutput>password</computeroutput>, <computeroutput>connection-url</" +"computeroutput>, and <computeroutput>driver-class</computeroutput>, are " +"correct for your chosen database." +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:996 +#, no-c-format +msgid "" +"Portlet Debugging (<filename>jboss-portal.sar/conf/config.xml</filename>)" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:997 +#, no-c-format +msgid "" +"By default, JBoss Portal is configured to display all errors. This behavior " +"can be configured by modifying the <filename>jboss-portal.sar/conf/config." +"xml</filename> file:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:1001 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!-- When a window has restrictedaccess : show or hide values are permitted " +"-->\n" +"<entry key=\"core.render.window_access_denied\">show</entry>\n" +"<!-- When a window is unavailable : show or hide values are permitted -->\n" +"<entry key=\"core.render.window_unavailable\">show</entry>\n" +"<!-- When a window produces an error : show, hide or message_only values are " +"permitted -->\n" +"<entry key=\"core.render.window_error\">message_only</entry>\n" +"<!-- When a window produces an internal error : show, hide are permitted --" +">\n" +"<entry key=\"core.render.window_internal_error\">show</entry>\n" +"<!-- When a window is not found : show or hide values are permitted -->\n" +"<entry key=\"core.render.window_not_found\">show</entry>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:1003 +#, no-c-format +msgid "" +"For these parameters, accepted values are <computeroutput>show</" +"computeroutput> and <computeroutput>hide</computeroutput>. Depending on the " +"setting, and the actual error, either an error message is displayed, or a " +"full stack trace within the portlet window occurs. Additionally, the " +"<computeroutput>core.render.window_error</computeroutput> property supports " +"the <computeroutput>message_only</computeroutput> value. The " +"<computeroutput>message_only</computeroutput> value will only display an " +"error message, whereas the <computeroutput>show</computeroutput> value will, " +"if available, display the full stack trace." +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:1008 +#, no-c-format +msgid "Log in to Dashboard" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:1009 +#, no-c-format +msgid "" +"By default, when a user logs in they are forwarded to the default page of " +"the default portal. In order to forward a user to their Dashboard, set the " +"<computeroutput>core.login.namespace</computeroutput> value to " +"<computeroutput>dashboard</computeroutput> in the <filename>jboss-portal.sar/" +"conf/config.xml</filename> file:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:1014 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<!-- Namespace to use when logging-in, use \"dashboard\" to directly\n" +"log-in the dashboard otherwise use \"default\" -->\n" +"<entry key=\"core.login.namespace\">dashboard</entry>\n" +"]]>" +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:1019 +#, no-c-format +msgid "Descriptor Examples" +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:1021 +#, no-c-format +msgid "Defining a new Portal Page" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:1022 +#, no-c-format +msgid "" +"The sample application descriptor in this section creates a new page, " +"<computeroutput>MyPage</computeroutput>, in a portal. To illustrate this " +"example, download the <ulink url=\"http://anonsvn.jboss.org/repos/" +"portletswap/portlets/2_4/bundles/HelloWorldPortalPage.zip" +"\">HelloWorldPortalPage</ulink> portlet. To use the HelloWorldPortalPage " +"portlet:" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:1028 +#, no-c-format +msgid "" +"Download the <ulink url=\"http://anonsvn.jboss.org/repos/portletswap/" +"portlets/2_4/bundles/HelloWorldPortalPage.zip\">HelloWorldPortalPage</ulink> " +"portlet." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:1033 +#, no-c-format +msgid "Unzip the <filename>HelloWorldPortalPage</filename> ZIP file." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:1038 +#, no-c-format +msgid "" +"To expand the WAR file, which gives you access to the XML descriptors, " +"change into the <filename>HelloWorldPortalPage/</filename> directory, and " +"run the <command>ant explode</command> command." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:1043 +#, no-c-format +msgid "" +"If you did not expand the <filename>helloworldportalpage.war</filename> " +"file, copy the <filename>helloworldportalpage.war</filename> file into the " +"correct JBoss AS or JBoss EAP <filename>deploy/</filename> directory. If you " +"expanded the <filename>helloworldportalpage.war</filename> file, copy the " +"<filename>HelloWorldPortalPage/output/lib/exploded/helloworldportalpage.war/" +"</filename> directory into the correct JBoss AS or JBoss EAP " +"<filename>deploy/</filename> directory. For example, if you are using the " +"<computeroutput>default</computeroutput> JBoss AS profile, copy the WAR file " +"or the expanded directory into the <filename>$JBOSS_HOME/server/default/" +"deploy/</filename> directory." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:1049 +#, no-c-format +msgid "" +"The HelloWorldPortalPage portlet is hot-deployable, so the JBoss EAP or " +"JBoss AS server does not have to be restarted after deploying the " +"HelloWorldPortalPage portlet. The following is an example of the " +"<filename>HelloWorldPortalPage/WEB-INF/helloworld-object.xml</filename> " +"descriptor:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:1053 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" +"<!DOCTYPE deployments PUBLIC\n" +" \"-//JBoss Portal//DTD Portal Object 2.6//EN\"\n" +" \"http://www.jboss.org/portal/dtd/portal-object_2_6.dtd\">\n" +"<deployments>\n" +" <deployment>\n" +" <if-exists>overwrite</if-exists>\n" +" <parent-ref>default</parent-ref>\n" +" <properties/>\n" +" <page>\n" +" <page-name>MyPage</page-name>\n" +" <window>\n" +" <window-name>HelloWorldPortletPageWindow</window-name>\n" +" <instance-ref>HelloWorldPortletPageInstance</instance-ref>\n" +" <region>center</region>\n" +" <height>0</height>\n" +" </window>\n" +" <security-constraint>\n" +" <policy-permission>\n" +" <unchecked/>\n" +" <action-name>viewrecursive</action-name>\n" +" </policy-permission>\n" +" </security-constraint>\n" +" </page>\n" +" </deployment>\n" +"</deployments>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:1055 +#, no-c-format +msgid "" +"A depoloyment is composed of a <computeroutput>&lt;deployments&gt;</" +"computeroutput> element, which is a container for <computeroutput>&lt;" +"deployment&gt;</computeroutput> elements. In the previous example, a page is " +"defined, the portlet is placed as a window on a page, and an instance of the " +"portlet is created. The Mangement portlet (bundled with JBoss Portal) can " +"modify portal instances, page position, and so on." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:1058 +#, no-c-format +msgid "" +"The following list describes elements in a <filename>*-object.xml</filename> " +"file:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:1064 +#, no-c-format +msgid "&lt;if-exists&gt;" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:1070 +#, no-c-format +msgid "&lt;parent-ref&gt;" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:1076 +#, no-c-format +msgid "&lt;properties&gt;" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:1077 +#, no-c-format +msgid "" +"A set of generic properties for the portal object. The <computeroutput>&lt;" +"properties&gt;</computeroutput> elements contains definitions specific to a " +"page. This is commonly used to define the specific theme and layout to use. " +"If not defined, the default portal theme and layout are used." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:1082 +#, no-c-format +msgid "&lt;page&gt;" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:1083 +#, no-c-format +msgid "" +"The start of a page definition. Among others, the <computeroutput>&lt;" +"page&gt;</computeroutput> element is a container for the <computeroutput>&lt;" +"page-name&gt;</computeroutput>, <computeroutput>&lt;window&gt;</" +"computeroutput>, and <computeroutput>&lt;security-constraint&gt;</" +"computeroutput> elements." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:1088 +#, no-c-format +msgid "&lt;page-name&gt;" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:1094 +#, no-c-format +msgid "&lt;window&gt;" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:1100 +#, no-c-format +msgid "&lt;window-name&gt;" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:1106 +#, no-c-format +msgid "&lt;instance-ref&gt;" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:1112 +#, no-c-format +msgid "" +"&lt;region&gt;...&lt;/region&gt;\n" +"&lt;height&gt;...&lt;/height&gt;" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:1118 +#, no-c-format +msgid "&lt;instance&gt;" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:1119 +#, no-c-format +msgid "" +"The <computeroutput>&lt;instance&gt;</computeroutput> element creates " +"instances of portlets. The portlet will only be created and configured if " +"the portlet is present, and if an instance with the same name does not " +"already exist." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:1124 +#, no-c-format +msgid "&lt;instance-name&gt;" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:1125 +#, no-c-format +msgid "" +"The <computeroutput>&lt;instance-name&gt;</computeroutput> element maps to " +"the <computeroutput>&lt;instance-ref&gt;</computeroutput> element." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:1130 +#, no-c-format +msgid "&lt;component-ref&gt;" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:1131 +#, no-c-format +msgid "" +"The <computeroutput>&lt;component-ref&gt;</computeroutput> element takes the " +"name of the application, followed by the name of the portlet, as defined in " +"the <filename>WEB-INF/portlet.xml</filename> file." +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:1141 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<security-constraint>\n" +" <policy-permission>\n" +" <role-name>User</role-name>\n" +" <action-name>view</action-name>\n" +" </policy-permission>\n" +"</security-constraint>\n" +"\n" +"<security-constraint>\n" +" <policy-permission>\n" +" <unchecked/>\n" +" <action-name>view</action-name>\n" +" </policy-permission>\n" +"</security-constraint>]]>" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:1144 +#, no-c-format +msgid "&lt;action-name&gt;" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:1174 +#, no-c-format +msgid "&lt;unchecked/&gt;" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:1180 +#, no-c-format +msgid "&lt;role-name&gt;" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:1186 +#, no-c-format +msgid "&lt;role-name&gt;EXAMPLEROLE&lt;/role-name&gt;" +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:1190 +#, no-c-format +msgid "Defining a new Portal Instance" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:1191 +#, no-c-format +msgid "" +"The sample application descriptor in this section creates a new portal " +"instance, <computeroutput>HelloPortal</computeroutput>, that contains two " +"pages. To illustrate this example, download the <ulink url=\"http://anonsvn." +"jboss.org/repos/portletswap/portlets/2_4/bundles/HelloWorldPortal.zip" +"\">HelloWorldPortal</ulink> portlet. To use the HelloWorldPortal portlet:" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:1197 +#, no-c-format +msgid "" +"Download the <ulink url=\"http://anonsvn.jboss.org/repos/portletswap/" +"portlets/2_4/bundles/HelloWorldPortal.zip\">HelloWorldPortal</ulink> portlet." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:1202 +#, no-c-format +msgid "Unzip the <filename>HelloWorldPortal</filename> ZIP file." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:1207 +#, no-c-format +msgid "" +"To expand the WAR file, which gives you access to the XML descriptors, " +"change into the <filename>HelloWorldPortal/</filename> directory, and run " +"the <command>ant explode</command> command." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:1212 +#, no-c-format +msgid "" +"If you did not expand the <filename>helloworldportal.war</filename> file, " +"copy the <filename>helloworldportal.war</filename> file into the correct " +"JBoss AS or JBoss EAP <filename>deploy/</filename> directory. If you " +"expanded the <filename>helloworldportal.war</filename> file, copy the " +"<filename>HelloWorldPortal/output/lib/exploded/helloworldportal.war/</" +"filename> directory into the correct JBoss AS or JBoss EAP <filename>deploy/" +"</filename> directory. For example, if you are using the " +"<computeroutput>default</computeroutput> JBoss AS profile, copy the WAR file " +"or the expanded directory into the <filename>$JBOSS_HOME/server/default/" +"deploy/</filename> directory." +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:1218 +#, no-c-format +msgid "" +"The HelloWorldPortal portlet is hot-deployable, so the JBoss EAP or JBoss AS " +"server does not have to be restarted after deploying the HelloWorldPortal " +"portlet. The following is an example of the <filename>HelloWorldPortal/WEB-" +"INF/helloworld-object.xml</filename> descriptor:" +msgstr "" + +#. Tag: programlisting +#: XML_Descriptors.xml:1222 +#, no-c-format +msgid "" +"<![CDATA[\n" +"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" +"<!DOCTYPE deployments PUBLIC\n" +" \"-//JBoss Portal//DTD Portal Object 2.6//EN\"\n" +" \"http://www.jboss.org/portal/dtd/portal-object_2_6.dtd\">\n" +"<deployments>\n" +" <deployment>\n" +" <parent-ref/>\n" +" <if-exists>overwrite</if-exists>\n" +" <portal>\n" +" <portal-name>HelloPortal</portal-name>\n" +" <supported-modes>\n" +" <mode>view</mode>\n" +" <mode>edit</mode>\n" +" <mode>help</mode>\n" +" </supported-modes>\n" +" <supported-window-states>\n" +" <window-state>normal</window-state>\n" +" <window-state>minimized</window-state>\n" +" <window-state>maximized</window-state>\n" +" </supported-window-states>\n" +" <properties>\n" +" <!-- Set the layout for the default portal -->\n" +" <!-- see also portal-layouts.xml -->\n" +" <property>\n" +" <name>layout.id</name>\n" +" <value>generic</value>\n" +" </property>\n" +" <!-- Set the theme for the default portal -->\n" +" <!-- see also portal-themes.xml -->\n" +" <property>\n" +" <name>theme.id</name>\n" +" <value>renaissance</value>\n" +" </property>\n" +" <!-- set the default render set name (used by the render tag in " +"layouts) -->\n" +" <!-- see also portal-renderSet.xml -->\n" +" <property>\n" +" <name>theme.renderSetId</name>\n" +" <value>divRenderer</value>\n" +" </property>\n" +" </properties>\n" +" <security-constraint>\n" +" <policy-permission>\n" +" <action-name>personalizerecursive</action-name>\n" +" <unchecked/>\n" +" </policy-permission>\n" +" </security-constraint>\n" +" <page>\n" +" <page-name>default</page-name>\n" +" <security-constraint>\n" +" <policy-permission>\n" +" <action-name>viewrecursive</action-name>\n" +" <unchecked/>\n" +" </policy-permission>\n" +" </security-constraint>\n" +" <window>\n" +" <window-name>MyPortletWindow</window-name>\n" +" <instance-ref>MyPortletInstance</instance-ref>\n" +" <region>center</region>\n" +" <height>0</height>\n" +" </window>\n" +" </page>\n" +" </portal>\n" +" </deployment>\n" +" <deployment>\n" +" <parent-ref>HelloPortal</parent-ref>\n" +" <if-exists>overwrite</if-exists>\n" +" <page>\n" +" <page-name>foobar</page-name>\n" +" <security-constraint>\n" +" <policy-permission>\n" +" <action-name>viewrecursive</action-name>\n" +" <unchecked/>\n" +" </policy-permission>\n" +" </security-constraint>\n" +" <window>\n" +" <window-name>MyPortletWindow</window-name>\n" +" <instance-ref>MyPortletInstance</instance-ref>\n" +" <region>center</region>\n" +" <height>0</height>\n" +" </window>\n" +" </page>\n" +" </deployment>\n" +"</deployments>]]>" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:1224 +#, no-c-format +msgid "" +"When deployed, this example registers a new portal instance, " +"<computeroutput>HelloPortal</computeroutput>, that contains two pages. To " +"view the default page in the <computeroutput>HelloPortal</computeroutput> " +"instance, navigate to <ulink url=\"http://localhost:8080/portal/portal/" +"HelloPortal\"></ulink>, and for the second page, <ulink url=\"http://" +"localhost:8080/portal/portal/HelloPortal/foobar\"></ulink>." +msgstr "" + +#. Tag: title +#: XML_Descriptors.xml:1229 +#, no-c-format +msgid "Portal Instance <computeroutput>default</computeroutput> Page" +msgstr "" + +#. Tag: para +#: XML_Descriptors.xml:1230 +#, no-c-format +msgid "" +"For a portal instance to be accessible via a Web browser, you must define a " +"default page." +msgstr ""