From do-not-reply at jboss.org Wed Jan 30 21:35:40 2013 Content-Type: multipart/mixed; boundary="===============4235060186244298355==" MIME-Version: 1.0 From: do-not-reply at jboss.org To: gatein-commits at lists.jboss.org Subject: [gatein-commits] gatein SVN: r9102 - epp/docs/branches/6.0/Developer_Guide/en-US. Date: Wed, 30 Jan 2013 21:35:40 -0500 Message-ID: <201301310235.r0V2ZePn017628@svn01.web.mwc.hst.phx2.redhat.com> --===============4235060186244298355== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: jaredmorgs Date: 2013-01-30 21:35:40 -0500 (Wed, 30 Jan 2013) New Revision: 9102 Modified: epp/docs/branches/6.0/Developer_Guide/en-US/chapter-4-GDG_Portal_Develop= ment.xml Log: Changes incorporated for https://docs.jboss.org/author/display/GTNPORTAL35/= Custom+Internationalization+Resource+Bundles Modified: epp/docs/branches/6.0/Developer_Guide/en-US/chapter-4-GDG_Portal_= Development.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- epp/docs/branches/6.0/Developer_Guide/en-US/chapter-4-GDG_Portal_Develo= pment.xml 2013-01-31 01:43:20 UTC (rev 9101) +++ epp/docs/branches/6.0/Developer_Guide/en-US/chapter-4-GDG_Portal_Develo= pment.xml 2013-01-31 02:35:40 UTC (rev 9102) @@ -223,7 +223,7 @@ Custom Skin for a Portlet Source: https://docs.jboss.org/author/display/GTNPORTAL35/= Custom+Skin+for+a+Portlet - This section mentions code from the Portal Extension Examples = available for download from . as= part of your JBoss Portal Platform subscription. + This section mentions code from the Portal Extension Examples = available for download from as = part of your JBoss Portal Platform subscription. The same guidelines that apply when creating a new portlet s= kin also apply when creating a custom skin for a built-in portlet distribut= ed with JBoss Portal Platform. Declare the skin first in the @@ -302,7 +302,7 @@
Custom Navigation and Pages - This section mentions code from the Portal Extension Examples = available for download from . as= part of your JBoss Portal Platform subscription. + This section mentions code from the Portal Extension Examples = available for download from as = part of your JBoss Portal Platform subscription. In Portal Extension quickstart, we have added a couple of na= vigation nodes and pages to the ones available in the default GateIn Portal= installation.
@@ -622,111 +622,101 @@
Custom Internationalization Resource Bundles + Source: https://docs.jboss.org/author/display/GTNPORTAL35/= Custom+Internationalization+Resource+Bundles - This section mentions code from the Portal Extension Examples = available for download from . as= part of your JBoss Portal Platform subscription. + This section mentions code from the Portal Extension Examples = available for download from as = part of your JBoss Portal Platform subscription. There are two resource bundle customization scenarios possib= le with a Portal Extension: - to add new resource bundle items to the ones available i= n default GateIn Portal installation and + to add new resource bundle items to the ones available = in the default JBoss Portal Platform installation. - to assign new values to resource bundle items available = in default GateIn Portal installation + to assign new values to resource bundle items available = in default JBoss Portal Platform installation. - Both scenarios can be demonstrated on + Both scenarios can be demonstrated using the locale.portal.extension - resource bundle. To use this bundle we need to include it in b= oth + resource bundle. To use this bundle, include both init.resources and portal.resource.names - parameters of + parameters for the = BaseResourceBundlePlugin - in +<type> directive in war/src/main/webapp/WEB-INF/conf/sample-ext/common/commo= n-configuration.xml : common-configuration.xml containing declarations of navig= ation resource bundles - -19. <configuration xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-i= nstance" -20. xsi:schemaLocation=3D"http://www.exoplaform.org/xml/ns/kernel= _1_2.xsd http://www.exoplaform.org/xml/ns/kernel_1_2.xsd" xmlns=3D&quo= t;http://www.exoplaform.org/xml/ns/kernel_1_2.xsd"> -21. <external-component-plugins> -22. <!-- The full qualified name of the ResourceBundleService -= -> -23. <target-component>org.exoplatform.services.resources.Res= ourceBundleService</target-component> -24. <component-plugin> -25. <!-- The name of the plugin --> -26. <name>Sample ResourceBundle Plugin</name> -27. <!-- The name of the method to call on the ResourceBund= leService in order to register the ResourceBundles --> -28. <set-method>addResourceBundle</set-method> -29. <!-- The full qualified name of the BaseResourceBundleP= lugin --> -30. <type>org.exoplatform.services.resources.impl.BaseRe= sourceBundlePlugin</type> -31. <init-params> -32. <values-param> -33. <name>init.resources</name> -34. <description>Initiate the following resource= s during the first launch.</description> -35. <value>locale.portal.extension</value> -36. <value>locale.navigation.user.root</value= > -37. <!-- = -38. Note that we actually do not need to name loca= le.navigation.portal.classic and = -39. locale.navigation.group.platform.administrator= s here as they are in init.resources = -40. of the default GateIn installation. But it mak= es no harm to include them once again here. -41. --> -42. <value>locale.navigation.portal.classic</= value> -43. <value>locale.navigation.group.platform.admi= nistrators</value> -44. </values-param> -45. <values-param> -46. <name>portal.resource.names</name> -47. <description>These resources are merged to a= single resource bundle which is accessible from anywhere = -48. in GateIn. All these keys are located in the s= ame bundle, which is separated from the navigation = -49. resource bundles.</description> -50. <value>locale.portal.extension</value> -51. </values-param> -52. </init-params> -53. </component-plugin> -54. </external-component-plugins> -55. </configuration> - + <configuration xmlns:xsi=3D&= quot;http://www.w3.org/2001/XMLSchema-instance" + xsi:schemaLocation=3D"http://www.exoplatform.org/xml/ns/kernel_1_= 2.xsd http://www.exoplatform.org/xml/ns/kernel_1_2.xsd" xmlns=3D"= http://www.exoplatform.org/xml/ns/kernel_1_2.xsd"> + <external-component-plugins> + <!-- The full qualified name of the ResourceBundleService --> + <target-component>org.exoplatform.services.resources.Resourc= eBundleService</target-component> + <component-plugin> + <!-- The name of the plugin --> + <name>Sample ResourceBundle Plugin</name> + <!-- The name of the method to call on the ResourceBundleSe= rvice in order to register the ResourceBundles --> + <set-method>addResourceBundle</set-method> + <!-- The full qualified name of the BaseResourceBundlePlugi= n --> + <type>org.exoplatform.services.resources.impl.BaseResour= ceBundlePlugin</type> + <init-params> + <values-param> + <name>init.resources</name> + <description>Initiate the following resources du= ring the first launch.</description> + <value>locale.portal.extension</value> + <value>locale.navigation.user.root</value> + <!-- = + Note that we actually do not need to name locale.n= avigation.portal.classic and = + locale.navigation.group.platform.administrators he= re as they are in init.resources = + of the default GateIn installation. But it makes n= o harm to include them once again here. + --> + <value>locale.navigation.portal.classic</valu= e> + <value>locale.navigation.group.platform.administ= rators</value> + </values-param> + <values-param> + <name>portal.resource.names</name> + <description>These resources are merged to a sin= gle resource bundle which is accessible from anywhere = + in GateIn. All these keys are located in the same = bundle, which is separated from the navigation = + resource bundles.</description> + <value>locale.portal.extension</value> + </values-param> + </init-params> + </component-plugin> + </external-component-plugins> +</configuration> The English version of - locale.portal.extension - can be found under - war/src/main/webapp/WEB-INF/classes/locale/portal/extens= ion_en.properties - : - + locale.portal.extension is located in = + war/src/main/webapp/WEB-INF/classes/locale/portal/ex= tension_en.properties. English version of locale.portal.extension - -17. UIHomePagePortlet.Label.Slogan=3DCongratulations! -18. UIHomePagePortlet.Label.SubSlogan=3DYou have just installed the GateIn= Portal Extension -19. UIHomePagePortlet.Label.Title=3DSign in as: - + UIHomePagePortlet.Label.Slogan=3DCongratulations! +UIHomePagePortlet.Label.SubSlogan=3DYou have just installed the GateIn Por= tal Extension +UIHomePagePortlet.Label.Title=3DSign in as: UIHomePagePortlet.Label.SubSlogan - is a new key which is not available in default GateIn Portal i= nstallation. - - + is a new key which is not normally available in the default J= Boss Portal Platform installation. + However, UIHomePagePortlet.Label.Slogan is redefined in extension_en.properties - shown above. In - gatein.ear/web.war/WEB-INF/classes/locale/portlet/web/Gr= oovyPortlet_en.properties - it is already defined as - + shown above. + In + JPP_HOME/gatein/gatein.ear/web.war/WEB-INF/classes/l= ocale/portlet/web/GroovyPortlet_en.properties + it is already defined as: UIHomePagePortlet.Label.Slogan=3DThe Best of eXo a= nd JBoss Portal<div>GateIn #{gatein.version}</div> - - and here, within the Portal Extension we assign a new value + Within the Portal Extension, the new value Congratulations! - to it. +is appended to it. - - Please refer to the - prev= ious section - for more details on internationalization of navigation nodes. + Refer to the + for more details on internationalization of naviga= tion nodes.
--===============4235060186244298355==--