JBoss Portal SVN: r10012 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-18 03:25:42 -0500 (Mon, 18 Feb 2008)
New Revision: 10012
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
Log:
5.2.4.4. Building your Apache MyFaces JSF Porlet
revising and adding content to make this section
consistent with 5.2.2.5. Building your JSP Portlet
Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
===================================================================
--- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-18 06:04:52 UTC (rev 10011)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-18 08:25:42 UTC (rev 10012)
@@ -1431,9 +1431,9 @@
</para>
<para>
<note>
- <title>Adding Functionality to a Apache MyFaces JSF Porlet</title>
+ <title>Adding Functionality to an Apache MyFaces JSF Porlet</title>
<para>
- To add functionality to a Apache MyFaces JSF Porlet, sub-class it and create your own class.
+ To add functionality to an Apache MyFaces JSF Porlet, sub-class it and create your own class.
</para>
</note>
</para>
@@ -1482,11 +1482,68 @@
</sect3>
<sect3>
<title>Building your Apache MyFaces JSF Porlet</title>
- <para>If you have downloaded the sample, you can execute the build.xml with ant or inside your IDE.
- Executing <literal>ant</literal> will compile all source files and produce a
- <literal>helloworldjsfportlet.war</literal> file in a way similar to what we saw in
- <xref linkend="first_portlet_build"/>.
- </para>
+ <para>
+ The <filename>HelloWorldJSFMyFaces42Portlet.zip</filename> file contains a pre-compiled <filename>helloworldjsfmyfacesportlet.war</filename> file; however, to manually build the <filename>helloworldjsfmyfacesportlet.war</filename> file:
+ </para>
+ <para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Change into the <filename>HelloWorldJSFMyFaces42Portlet/</filename> directory, and remove the existing <filename>helloworldjsfmyfacesportlet.war</filename> file.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If required, edit the <filename>HelloWorldJSFMyFaces42Portlet/src/main/org/jboss/portlet/hello/bean/User.java</filename> file, and the application descriptors in the <filename>HelloWorldJSFMyFaces42Portlet/src/resources/helloworldjsfmyfacesportlet-war/WEB-INF/</filename> directory.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Change into <filename>HelloWorldJSFMyFaces42Portlet/</filename> directory, and run the <command>ant deploy</command> command. On Linux, the output will be similar to the following:
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata align="center" fileref="images/tutorials/jsf_portlet/myfaces_ant_deploy.png" valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ </orderedlist>
+ </para>
+ <para>
+ Note: the directory names will be different for your system.
+ </para>
+ <para>
+ Expanding the <filename>helloworldjsfmyfacesportlet.war</filename> file allows you to deploy the portlet as an expanded directory, which makes development easier. As well, it gives you access to the application descriptors, resource files, JSF, and JSP pages. To expand the <filename>helloworldjsfmyfacesportlet.war</filename> file:
+ </para>
+ <para>
+ <orderedlist>
+ <listitem>
+ <para>
+ If you do not have the <filename>HelloWorldJSFMyFaces42Portlet/helloworldjsfmyfacesportlet.war</filename> file, change into the <filename>HelloWorldJSFMyFaces42Portlet/</filename> directory, and run the <command>ant deploy</command> command. This creates the <filename>helloworldjsfmyfacesportlet.war</filename> file.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To expand the WAR file, change into the <filename>HelloWorldJSFMyFaces42Portlet/</filename> directory, and run the <command>ant explode</command> command. On Linux, the output will be similar to the following:
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata align="center" fileref="images/tutorials/jsf_portlet/myfaces_ant_explode.png" valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ </orderedlist>
+ </para>
+ <para>
+ Note: the directory names will be different for your system.
+ </para>
+ <para>
+ The expanded WAR file and the application descriptors are located in the <filename>HelloWorldJSFMyFaces42Portlet/output/lib/exploded/helloworldjsfmyfacesportlet.war/WEB-INF/</filename> directory.
+ </para>
</sect3>
<sect3>
<title>Deploying your Apache MyFaces JSF Portlet</title>
16 years, 7 months
JBoss Portal SVN: r10011 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-18 01:04:52 -0500 (Mon, 18 Feb 2008)
New Revision: 10011
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
Log:
5.2.4. An example Apache MyFaces JSF Portlet
minor revisions, fixing my spelling errors
Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
===================================================================
--- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-18 04:12:51 UTC (rev 10010)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-18 06:04:52 UTC (rev 10011)
@@ -1466,7 +1466,7 @@
Without the <filename>faces-config.xml</filename> file, the application would work the same outside of the portlet as it would inside a portlet container. In this example, a basic user bean, <computeroutput><managed-bean-name>user</managed-bean-name></computeroutput>, and a navigation rule are defined, which handle the submission of the original form in the <filename>HelloWorldJSFMyFaces42Portlet/WEB-INF/jsp/index.jsp</filename> file.
</para>
<para>
- The following is an example of the Faces Servlet section from the HelloWorldJSFMyFaces42Portlet/WEB-INF/web.xml file:
+ The following is an example of the <computeroutput><context-parm></computeroutput> section from the <filename>HelloWorldJSFMyFaces42Portlet/WEB-INF/web.xml</filename> file:
</para>
<para>
<screen><![CDATA[
@@ -1477,7 +1477,7 @@
</screen>
</para>
<para>
- These extra parameters let the application server know that the portlet embeds its own libraries. This avoids collision with the Sun JSF RI libraries bundled with JBoss AS And JBoss EAP. For further details, refer to the <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossFaces">Apache MyFaces page on the JBoss Wiki</ulink>.
+ These extra parameters let the application server know that the portlet embeds its own libraries. This avoids collision with the Sun JSF RI libraries bundled with JBoss AS And JBoss EAP. For more information, refer to the <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossFaces">Apache MyFaces page on the JBoss Wiki</ulink>.
</para>
</sect3>
<sect3>
16 years, 7 months
JBoss Portal SVN: r10010 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-17 23:12:51 -0500 (Sun, 17 Feb 2008)
New Revision: 10010
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
Log:
5.2.4. An example Apache MyFaces JSF Portlet
revising to make more consistent with 5.2.1. Deploying your first Portlet
Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
===================================================================
--- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-18 02:28:34 UTC (rev 10009)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-18 04:12:51 UTC (rev 10010)
@@ -1084,6 +1084,18 @@
</para>
</listitem>
</varlistentry>
+<varlistentry><term><screen><![CDATA[
+<supports>
+ <mime-type>text/html</mime-type>
+ <portlet-mode>VIEW</portlet-mode>
+</supports>]]></screen></term>
+ <listitem>
+ <para>
+ The <computeroutput><supports></computeroutput> element allows you to declare all the markup types your portlet supports in the <literal>render</literal> method. This is accomplished via the
+ <computeroutput><mime-type></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 VIEW portlet mode, so this does not have to be declared. Use <computeroutput><mime-type></computeroutput> to define which markup type your portlet supports, which in this example, is <computeroutput>text/html</computeroutput>. This section tells the portal that it will only output text and HTML, and that it only supports the <computeroutput>VIEW</computeroutput> mode.
+ </para>
+</listitem>
+</varlistentry>
</variablelist>
</para>
<para>
@@ -1343,7 +1355,7 @@
</mediaobject>
</para>
<para>
- To create the <filename>WEB-INF/</filename> and <filename>META-INF/</filename> directories, extract the <filename>helloworldjsfmyfacesportlet.war</filename> file. The <filename>WEB-INF/lib/</filename> directory must contain the MyFaces libraries, along with the dependent libraries.
+ To create the <filename>WEB-INF/</filename> and <filename>META-INF/</filename> directories, extract the <filename>helloworldjsfmyfacesportlet.war</filename> file. The <filename>WEB-INF/lib/</filename> directory must contain the Apache MyFaces libraries, along with the dependent libraries.
</para>
</sect3>
<sect3>
@@ -1387,11 +1399,7 @@
</screen></term>
<listitem>
<para>
- Here we specify that MyFacesGenericPortlet will handle all requests/responses from our
- users. There is therefore no need to develop a specific portlet class, MyFaces
- providing a generic implementation bridging the JSF and portlet worlds.
- <note><para>If you wanted to add more functionality to your JSF portlet, not included in the
- MyFacesGenericPortlet, you could sublass it and create your own Class.</para></note>
+ This specifies that the <computeroutput>org.apache.myfaces.portlet.MyFacesGenericPortlet</computeroutput> handles all requests and responses from the users. Therefore, there is no need to develop a specific portlet class, as Apache MyFaces provides a generic implementation which bridges the JSF and portlet worlds.
</para>
</listitem>
</varlistentry>
@@ -1403,14 +1411,33 @@
</screen></term>
<listitem>
<para>
- We need to initialize the portlet with a default view page for it to render, much like
- a welcome page:
+ You must initialize the portlet with a default page to render, similar to a welcome page.
</para>
</listitem>
</varlistentry>
+<varlistentry><term><screen><![CDATA[
+<supports>
+ <mime-type>text/html</mime-type>
+ <portlet-mode>VIEW</portlet-mode>
+</supports>]]></screen></term>
+ <listitem>
+ <para>
+ The <computeroutput><supports></computeroutput> element allows you to declare all the markup types your portlet supports in the <literal>render</literal> method. This is accomplished via the
+ <computeroutput><mime-type></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 VIEW portlet mode, so this does not have to be declared. Use <computeroutput><mime-type></computeroutput> to define which markup type your portlet supports, which in this example, is <computeroutput>text/html</computeroutput>. This section tells the portal that it will only output text and HTML, and that it only supports the <computeroutput>VIEW</computeroutput> mode.
+ </para>
+</listitem>
+</varlistentry>
</variablelist>
</para>
<para>
+ <note>
+ <title>Adding Functionality to a Apache MyFaces JSF Porlet</title>
+ <para>
+ To add functionality to a Apache MyFaces JSF Porlet, sub-class it and create your own class.
+ </para>
+ </note>
+</para>
+<para>
The following is an example <filename>HelloWorldJSFMyFaces42Portlet/WEB-INF/faces-config.xml</filename> file:
</para>
<para>
@@ -1433,48 +1460,26 @@
</navigation-case>
</navigation-rule>
</faces-config>]]>
-
-
- <para><literal>web.xml</literal>
-<programlisting><![CDATA[<context-param>
+</screen>
+</para>
+ <para>
+ Without the <filename>faces-config.xml</filename> file, the application would work the same outside of the portlet as it would inside a portlet container. In this example, a basic user bean, <computeroutput><managed-bean-name>user</managed-bean-name></computeroutput>, and a navigation rule are defined, which handle the submission of the original form in the <filename>HelloWorldJSFMyFaces42Portlet/WEB-INF/jsp/index.jsp</filename> file.
+ </para>
+<para>
+ The following is an example of the Faces Servlet section from the HelloWorldJSFMyFaces42Portlet/WEB-INF/web.xml file:
+</para>
+<para>
+<screen><![CDATA[
+<context-param>
<param-name>org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL</param-name>
<param-value>true</param-value>
-</context-param>]]></programlisting>
- We need this extra parameter to let the application server know that the package embeds its own libraries.
- It will avoid collision with the Sun RI JSF libraries bundled with JBoss AS.
- More details on this procedure can be found at <ulink
- url="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossFaces">http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossFaces</ulink>.
- </para>
- </listitem>
- <listitem>
- <para><literal>faces-config.xml</literal>
-<programlisting><![CDATA[<?xml version="1.0"?>
-<!DOCTYPE faces-config PUBLIC
- "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.0//EN"
- "http://java.sun.com/dtd/web-facesconfig_1_0.dtd">
-<faces-config>
- <managed-bean>
- <description>Basic UserBean</description>
- <managed-bean-name>user</managed-bean-name>
- <managed-bean-class>org.jboss.portlet.hello.bean.User</managed-bean-class>
- <managed-bean-scope>session</managed-bean-scope>
- </managed-bean>
- <navigation-rule>
- <navigation-case>
- <from-outcome>done</from-outcome>
- <to-view-id>/WEB-INF/jsp/result.jsp</to-view-id>
- </navigation-case>
- </navigation-rule>
-</faces-config>]]></programlisting>
- There is nothing special about the <literal>faces-config.xml</literal> file included here. This
- application would work just as well outside of a portlet as it would inside a portlet container.
- In the above lines, we define a basic <literal>User</literal> Bean and a navigation rule to
- handle the submittal of the original form on <literal>index.jsp</literal>.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </sect3>
+</context-param>]]>
+</screen>
+</para>
+<para>
+ These extra parameters let the application server know that the portlet embeds its own libraries. This avoids collision with the Sun JSF RI libraries bundled with JBoss AS And JBoss EAP. For further details, refer to the <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossFaces">Apache MyFaces page on the JBoss Wiki</ulink>.
+</para>
+</sect3>
<sect3>
<title>Building your Apache MyFaces JSF Porlet</title>
<para>If you have downloaded the sample, you can execute the build.xml with ant or inside your IDE.
16 years, 7 months
JBoss Portal SVN: r10009 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-17 21:28:34 -0500 (Sun, 17 Feb 2008)
New Revision: 10009
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
Log:
periodic backup
revising 5.2.4. A simple MyFaces JSF Portlet on JBoss AS 4.2
*** this will break the book until later commits ***
Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
===================================================================
--- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-18 01:52:50 UTC (rev 10008)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-18 02:28:34 UTC (rev 10009)
@@ -1348,14 +1348,15 @@
</sect3>
<sect3>
<title>Application Descriptors</title>
- <para>For the sake of brevity, we only discuss the <literal>portlet.xml</literal>, <literal>web.xml</literal> and
- <literal>faces-config.xml</literal> descriptors here. For discussion on the other descriptors, please
- view <xref linkend="first_portlet_descriptors"/> or the chapter on descriptors:
- <xref linkend="descriptors_portlet"/>.
- <itemizedlist>
- <listitem>
- <para><literal>portlet.xml</literal>
-<programlisting><![CDATA[<?xml version="1.0" encoding="UTF-8"?>
+ <para>
+ For brevity, only the <filename>portlet.xml</filename>, <filename>faces-config.xml</filename>, and <filename>web.xml</filename> descriptors are described here. For more information about application descriptors, refer to <xref linkend="first_portlet_descriptors"/> and <xref linkend="descriptors_portlet"/>.
+ </para>
+ <para>
+ The following is an example of the <filename>HelloWorldJSFMyFaces42Portlet/WEB-INF/portlet.xml</filename> file. This file must adhere to its definition in the JSR-168 Portlet Specification. You may define more than one portlet application in this file:
+ </para>
+ <para>
+<screen><![CDATA[
+<?xml version="1.0" encoding="UTF-8"?>
<portlet-app xmlns="http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd
@@ -1376,36 +1377,65 @@
<title>HelloWorld JSF Portlet</title>
</portlet-info>
</portlet>
-</portlet-app>]]></programlisting>
- This file must adhere to its definition in the Portlet Specification. You may define more than
- one portlet application in this file. Now let's look at the portions that deal with our use of
- JSF:
- <itemizedlist>
- <listitem>
- <para>
- <programlisting><![CDATA[<portlet-class>org.apache.myfaces.portlet.MyFacesGenericPortlet</portlet-class>]]></programlisting>
- Here we specify that MyFacesGenericPortlet will handle all requests/responses from our
- users. There is therefore no need to develop a specific portlet class, MyFaces
- providing a generic implementation bridging the JSF and portlet worlds.
- <note>If you wanted to add more functionality to your JSF portlet, not included in the
- MyFacesGenericPortlet, you could sublass it and create your own Class.</note>
- </para>
- </listitem>
- <listitem>
- <para>
- We need to initialize the portlet with a default view page for it to render, much like
- a welcome page:
- <programlisting><![CDATA[<init-param>
+</portlet-app>]]>
+</screen>
+</para>
+<para>
+ <variablelist>
+ <varlistentry><term><screen><![CDATA[
+<portlet-class>org.apache.myfaces.portlet.MyFacesGenericPortlet</portlet-class>]]>
+</screen></term>
+<listitem>
+ <para>
+ Here we specify that MyFacesGenericPortlet will handle all requests/responses from our
+ users. There is therefore no need to develop a specific portlet class, MyFaces
+ providing a generic implementation bridging the JSF and portlet worlds.
+ <note><para>If you wanted to add more functionality to your JSF portlet, not included in the
+ MyFacesGenericPortlet, you could sublass it and create your own Class.</para></note>
+ </para>
+</listitem>
+</varlistentry>
+<varlistentry><term><screen><![CDATA[
+<init-param>
<name>default-view</name>
<value>/WEB-INF/jsp/index.jsp</value>
-</init-param>]]></programlisting>
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </listitem>
- <listitem>
- <para><literal>web.xml</literal>
+</init-param>]]>
+</screen></term>
+<listitem>
+ <para>
+ We need to initialize the portlet with a default view page for it to render, much like
+ a welcome page:
+ </para>
+</listitem>
+</varlistentry>
+</variablelist>
+</para>
+<para>
+ The following is an example <filename>HelloWorldJSFMyFaces42Portlet/WEB-INF/faces-config.xml</filename> file:
+</para>
+<para>
+<screen><![CDATA[
+<?xml version="1.0"?>
+<!DOCTYPE faces-config PUBLIC
+ "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.0//EN"
+ "http://java.sun.com/dtd/web-facesconfig_1_0.dtd">
+<faces-config>
+ <managed-bean>
+ <description>Basic UserBean</description>
+ <managed-bean-name>user</managed-bean-name>
+ <managed-bean-class>org.jboss.portlet.hello.bean.User</managed-bean-class>
+ <managed-bean-scope>session</managed-bean-scope>
+ </managed-bean>
+ <navigation-rule>
+ <navigation-case>
+ <from-outcome>done</from-outcome>
+ <to-view-id>/WEB-INF/jsp/result.jsp</to-view-id>
+ </navigation-case>
+ </navigation-rule>
+</faces-config>]]>
+
+
+ <para><literal>web.xml</literal>
<programlisting><![CDATA[<context-param>
<param-name>org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL</param-name>
<param-value>true</param-value>
16 years, 7 months
JBoss Portal SVN: r10008 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-17 20:52:50 -0500 (Sun, 17 Feb 2008)
New Revision: 10008
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
Log:
5.2.4.1. Introduction
5.2.4.2. Package Structure
minor revisions
Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
===================================================================
--- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-17 23:15:32 UTC (rev 10007)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-18 01:52:50 UTC (rev 10008)
@@ -1239,7 +1239,8 @@
</para>
<para>
<screen><![CDATA[
-INFO [TomcatDeployer] deploy, ctxPath=/helloworldjsfsunriportlet, warUrl=.../tmp/deploy/tmp9138helloworldjsfsunriportlet-exp.war/]]>
+INFO [TomcatDeployer] deploy, ctxPath=/helloworldjsfsunriportlet,
+warUrl=.../tmp/deploy/tmp9138helloworldjsfsunriportlet-exp.war/]]>
</screen>
</para>
<para>
@@ -1319,30 +1320,34 @@
</sect3>
</sect2>-->
<sect2 id="myfaces_42x">
- <title>A simple MyFaces JSF Portlet on JBoss AS 4.2</title>
+ <title>An example Apache MyFaces JSF Portlet</title>
<sect3>
<title>Introduction</title>
- <para>This section will introduce the reader to deploying a simple JSF portlet in JBoss Portal, using
- Apache's MyFaces JSF implementation on JBoss AS 4.2. It requires you download the HelloWorldJSFMyFaces42Portlet
- from PortletSwap.com, using this link:
- <ulink url="http://anonsvn.jboss.org/repos/portletswap/portlets/2_6/bundles/HelloWorl...">http://anonsvn.jboss.org/repos/portletswap/portlets/2_6/bundles/HelloWorl...</ulink>.
- There are actually different ways to do it, one would be to use MyFaces globally for the whole server and replace the Sun RI
- libraries by the myFaces ones, but in this section the portlet will not affect the application server and embed its
- own libraries.
- </para>
+ <para>
+ This section describes how to deploy a JSF portlet in JBoss Portal, using the Apache MyFaces JSF implementation in JBoss AS or JBoss EAP. Before proceeding, download the <ulink url="http://anonsvn.jboss.org/repos/portletswap/portlets/2_6/bundles/HelloWorl...">HelloWorldJSFMyFaces42Portlet</ulink> from <ulink url="http://labs.jboss.com/portletswap/">JBoss PortletSwap</ulink>.
+ </para>
+ <para>
+ Apache MyFaces can be used globally for the entire server, replacing the Sun JSF RI libraries, but the HelloWorldJSFMyFaces42Portlet uses its own libraries, and will not affect the application server.
+ </para>
</sect3>
<sect3>
- <title>Package Content</title>
+ <title>Package Structure</title>
+ <para>
+ JBoss Portal requires certain descriptors to be included in a portlet WAR file. Some of these descriptors are defined by the JSR-168 Portlet Specification, and others are specific to JBoss Portal. Like a typical JSF application, the HelloWorldJSFMyFaces42Portlet package contains a <filename>faces-config.xml</filename> file that defines managed-beans, converters, validators, navigation rules, and so on. The following is an example of the directory structure of the HelloWorldJSFMyFaces42Portlet portlet:
+ </para>
<para>
<mediaobject>
<imageobject>
<imagedata align="center" fileref="images/tutorials/jsf_portlet/package_myfaces42.png" valign="middle"/>
</imageobject>
</mediaobject>
- Like a typical JSF application, we also package our faces-config.xml that defines our
- managed-beans, converters, validators, navigation rules, etc...
- The <filename>WEB-INF/lib</filename> must contain the MyFaces libraries along with dependent libraries.
+ </para>
+ <para>
+ To create the <filename>WEB-INF/</filename> and <filename>META-INF/</filename> directories, extract the <filename>helloworldjsfmyfacesportlet.war</filename> file. The <filename>WEB-INF/lib/</filename> directory must contain the MyFaces libraries, along with the dependent libraries.
</para>
+ </sect3>
+ <sect3>
+ <title>Application Descriptors</title>
<para>For the sake of brevity, we only discuss the <literal>portlet.xml</literal>, <literal>web.xml</literal> and
<literal>faces-config.xml</literal> descriptors here. For discussion on the other descriptors, please
view <xref linkend="first_portlet_descriptors"/> or the chapter on descriptors:
@@ -1441,12 +1446,15 @@
</para>
</sect3>
<sect3>
- <title>Building and deploying your portlet</title>
+ <title>Building your Apache MyFaces JSF Porlet</title>
<para>If you have downloaded the sample, you can execute the build.xml with ant or inside your IDE.
Executing <literal>ant</literal> will compile all source files and produce a
<literal>helloworldjsfportlet.war</literal> file in a way similar to what we saw in
<xref linkend="first_portlet_build"/>.
</para>
+ </sect3>
+ <sect3>
+ <title>Deploying your Apache MyFaces JSF Portlet</title>
<para>
Deploying the portlet is as easy as copying/moving the <literal>helloworldjsfmyfacesportlet.war</literal> file
to the server <literal>deploy</literal> directory. We can then see our portlet on the Portal default
16 years, 7 months
JBoss Portal SVN: r10007 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-17 18:15:32 -0500 (Sun, 17 Feb 2008)
New Revision: 10007
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
Log:
minor revisions, adding text about having to
deploy the expanded WAR, in order to use the touch
command...
Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
===================================================================
--- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-17 22:53:53 UTC (rev 10006)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-17 23:15:32 UTC (rev 10007)
@@ -618,7 +618,7 @@
</mediaobject>
</para>
<para>
- To re-deploy the portlet, for example, if you have made changes to any of the application descriptors, touch the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/helloworldportlet.war/WEB-INF/web.xml</filename> file. On Linux, run the following command to re-deploy the HelloWorldPortlet:
+ To re-deploy the portlet, for example, if you have made changes to any of the application descriptors, touch the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/helloworldportlet.war/WEB-INF/web.xml</filename> file. This will only work if you copied the <filename>HelloWorldPortlet/output/lib/exploded/helloworldportlet.war/</filename> directory into the JBoss AS or JBoss EAP <filename>deploy/</filename> directory. On Linux, run the following command to re-deploy the HelloWorldPortlet:
</para>
<para>
<screen>
@@ -974,7 +974,7 @@
</mediaobject>
</para>
<para>
- To re-deploy the portlet, for example, if you have made changes to any of the application descriptors, touch the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/helloworldjspportlet.war/WEB-INF/web.xml</filename> file. On Linux, run the following command to re-deploy the HelloWorldJSPPortlet:
+ To re-deploy the portlet, for example, if you have made changes to any of the application descriptors, touch the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/helloworldjspportlet.war/WEB-INF/web.xml</filename> file. This will only work if you copied the <filename>HelloWorldJSPPortlet/output/lib/exploded/helloworldjspportlet.war/</filename> directory into the JBoss AS or JBoss EAP <filename>deploy/</filename> directory. On Linux, run the following command to re-deploy the HelloWorldJSPPortlet:
</para>
<para>
<screen>
@@ -1226,13 +1226,13 @@
Note: the directory names will be different for your system.
</para>
<para>
- The expanded WAR file and the application descriptors are located in the <filename>HelloWorldJSFSunRIPortlet/output/lib/exploded/helloworldjsfsunriportlet.war</filename> directory.
+ The expanded WAR file and the application descriptors are located in the <filename>HelloWorldJSFSunRIPortlet/output/lib/exploded/helloworldjsfsunriportlet.war/WEB-INF/</filename> directory.
</para>
</sect3>
<sect3>
<title>Deploying your JSF Portlet</title>
<para>
- If you did not expand the <filename>helloworldjsfsunriportlet.war</filename> file, copy the <filename>HelloWorldJSFSunRIPortlet/helloworldjsfsunriportlet.war</filename> file into the correct JBoss AS or JBoss EAP <filename>deploy/</filename> directory. If you expanded the <filename>helloworldjsfsunriportlet.war</filename> file, copy the <filename>HelloWorldJSFSunRIPortlet/output/lib/exploded/helloworldjsfsunriportlet.war/</filename> directory into the correct JBoss AS or JBoss EAP <filename>deploy/</filename> directory. For example, if you are using JBoss AS, copy the war file or the expanded directory into the <filename>$JBOSS_HOME/server/default/deploy/</filename> directory.
+ If you did not expand the <filename>helloworldjsfsunriportlet.war</filename> file, copy the <filename>HelloWorldJSFSunRIPortlet/helloworldjsfsunriportlet.war</filename> file into the correct JBoss AS or JBoss EAP <filename>deploy/</filename> directory. If you expanded the <filename>helloworldjsfsunriportlet.war</filename> file, copy the <filename>HelloWorldJSFSunRIPortlet/output/lib/exploded/helloworldjsfsunriportlet.war/</filename> directory into the correct JBoss AS or JBoss EAP <filename>deploy/</filename> directory. For example, if you are using JBoss AS, copy the WAR file or the expanded directory into the <filename>$JBOSS_HOME/server/default/deploy/</filename> directory.
</para>
<para>
Performing this step on a running instance of JBoss AS or JBoss EAP, and JBoss Portal, will trigger a hot-deploy of the portlet:
@@ -1253,7 +1253,7 @@
</mediaobject>
</para>
<para>
- To re-deploy the portlet, for example, if you have made changes to any of the application descriptors, touch the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/helloworldjsfsunriportlet.war/WEB-INF/web.xml</filename> file. On Linux, run the following command to re-deploy the HelloWorldJSFSunRIPortlet:
+ To re-deploy the portlet, for example, if you have made changes to any of the application descriptors, touch the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/helloworldjsfsunriportlet.war/WEB-INF/web.xml</filename> file. This will only work if you copied the <filename>HelloWorldJSFSunRIPortlet/output/lib/exploded/helloworldjsfsunriportlet.war/</filename> directory into the JBoss AS or JBoss EAP <filename>deploy/</filename> directory. On Linux, run the following command to re-deploy the HelloWorldJSFSunRIPortlet:
</para>
<para>
<screen>
16 years, 7 months
JBoss Portal SVN: r10006 - in branches/JBoss_Portal_Branch_2_6/core-cms/src/resources/portal-cms-war/WEB-INF: jsp/cms/admin and 1 other directory.
by portal-commits＠lists.jboss.org
Author: sviluppatorefico
Date: 2008-02-17 17:53:53 -0500 (Sun, 17 Feb 2008)
New Revision: 10006
Modified:
branches/JBoss_Portal_Branch_2_6/core-cms/src/resources/portal-cms-war/WEB-INF/classes/Resource.properties
branches/JBoss_Portal_Branch_2_6/core-cms/src/resources/portal-cms-war/WEB-INF/classes/Resource_it.properties
branches/JBoss_Portal_Branch_2_6/core-cms/src/resources/portal-cms-war/WEB-INF/jsp/cms/admin/main.jsp
Log:
added new param for cms i18n
Modified: branches/JBoss_Portal_Branch_2_6/core-cms/src/resources/portal-cms-war/WEB-INF/classes/Resource.properties
===================================================================
--- branches/JBoss_Portal_Branch_2_6/core-cms/src/resources/portal-cms-war/WEB-INF/classes/Resource.properties 2008-02-17 22:34:20 UTC (rev 10005)
+++ branches/JBoss_Portal_Branch_2_6/core-cms/src/resources/portal-cms-war/WEB-INF/classes/Resource.properties 2008-02-17 22:53:53 UTC (rev 10006)
@@ -94,4 +94,6 @@
CMS_DENY=Deny
CMS_APPROVAL=Pending Items
CMS_PATH=Location
+
+CMS_EMPTY_FOLDER=This folder is empty.
\ No newline at end of file
Modified: branches/JBoss_Portal_Branch_2_6/core-cms/src/resources/portal-cms-war/WEB-INF/classes/Resource_it.properties
===================================================================
--- branches/JBoss_Portal_Branch_2_6/core-cms/src/resources/portal-cms-war/WEB-INF/classes/Resource_it.properties 2008-02-17 22:34:20 UTC (rev 10005)
+++ branches/JBoss_Portal_Branch_2_6/core-cms/src/resources/portal-cms-war/WEB-INF/classes/Resource_it.properties 2008-02-17 22:53:53 UTC (rev 10006)
@@ -94,4 +94,6 @@
CMS_DENY=Nega
CMS_APPROVAL=Oggetti in sospeso
CMS_PATH=Localit\u00e0
+
+CMS_EMPTY_FOLDER=Questa cartella \u00e8 vuota .
\ No newline at end of file
Modified: branches/JBoss_Portal_Branch_2_6/core-cms/src/resources/portal-cms-war/WEB-INF/jsp/cms/admin/main.jsp
===================================================================
--- branches/JBoss_Portal_Branch_2_6/core-cms/src/resources/portal-cms-war/WEB-INF/jsp/cms/admin/main.jsp 2008-02-17 22:34:20 UTC (rev 10005)
+++ branches/JBoss_Portal_Branch_2_6/core-cms/src/resources/portal-cms-war/WEB-INF/jsp/cms/admin/main.jsp 2008-02-17 22:53:53 UTC (rev 10006)
@@ -304,7 +304,7 @@
<tr>
<td>
- <p>This folder is empty.</p>
+ <p>${n:i18n("CMS_EMPTY_FOLDER")}</p>
</td>
</tr>
16 years, 7 months
JBoss Portal SVN: r10005 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-17 17:34:20 -0500 (Sun, 17 Feb 2008)
New Revision: 10005
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
Log:
spelling corrections
* s/war/WAR
* s/porlet/portlet
Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml
===================================================================
--- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml 2008-02-17 22:30:16 UTC (rev 10004)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml 2008-02-17 22:34:20 UTC (rev 10005)
@@ -94,17 +94,17 @@
<orderedlist>
<listitem>
<para>
- Change <emphasis>local.portal.CMSPorlet</emphasis> in the <emphasis>PORTLET_REF</emphasis> column to <emphasis>local./portal-cms.CMSPortlet</emphasis>.
+ Change <emphasis>local.portal.CMSPortlet</emphasis> in the <emphasis>PORTLET_REF</emphasis> column to <emphasis>local./portal-cms.CMSPortlet</emphasis>.
</para>
</listitem>
<listitem>
<para>
- Change <emphasis>local.portal.CMSAdminPorlet</emphasis> in the <emphasis>PORTLET_REF</emphasis> column to <emphasis>local./portal-cms.CMSAdminPortlet</emphasis>.
+ Change <emphasis>local.portal.CMSAdminPortlet</emphasis> in the <emphasis>PORTLET_REF</emphasis> column to <emphasis>local./portal-cms.CMSAdminPortlet</emphasis>.
</para>
</listitem>
<listitem>
<para>
- Change <emphasis>local.portal.ManagementPorlet</emphasis> in the <emphasis>PORTLET_REF</emphasis> column to <emphasis>local./portal-admin.AdminPortlet</emphasis>.
+ Change <emphasis>local.portal.ManagementPortlet</emphasis> in the <emphasis>PORTLET_REF</emphasis> column to <emphasis>local./portal-admin.AdminPortlet</emphasis>.
</para>
</listitem>
</orderedlist>
Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
===================================================================
--- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-17 22:30:16 UTC (rev 10004)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-17 22:34:20 UTC (rev 10005)
@@ -532,7 +532,7 @@
</listitem>
<listitem>
<para>
- If required, edit the <filename>HelloWorldPortlet/src/main/org/jboss/portlet/hello/HelloWorldPortlet.java</filename> file, and the XML descriptors in the <filename>HelloWorldPortlet/src/resources/helloworldportlet-war/WEB-INF/</filename> directory.
+ If required, edit the <filename>HelloWorldPortlet/src/main/org/jboss/portlet/hello/HelloWorldPortlet.java</filename> file, and the application descriptors in the <filename>HelloWorldPortlet/src/resources/helloworldportlet-war/WEB-INF/</filename> directory.
</para>
</listitem>
<listitem>
@@ -553,7 +553,7 @@
Note: the directory names will be different for your system.
</para>
<para>
- Expanding the <filename>helloworldportlet.war</filename> file allows you to deploy the portlet as an expanded directory, which makes development easier. As well, it gives you access to the XML descriptors, resource files, JSF, and JSP pages. To expand the <filename>helloworldportlet.war</filename> file:
+ Expanding the <filename>helloworldportlet.war</filename> file allows you to deploy the portlet as an expanded directory, which makes development easier. As well, it gives you access to the application descriptors, resource files, JSF, and JSP pages. To expand the <filename>helloworldportlet.war</filename> file:
</para>
<para>
<orderedlist>
@@ -564,7 +564,7 @@
</listitem>
<listitem>
<para>
- To expand the war file, change into the <filename>HelloWorldPortlet/</filename> directory, and run the <command>ant explode</command> command. On Microsoft Windows, the output will be similar to the following:
+ To expand the WAR file, change into the <filename>HelloWorldPortlet/</filename> directory, and run the <command>ant explode</command> command. On Microsoft Windows, the output will be similar to the following:
</para>
<para>
<mediaobject>
@@ -590,13 +590,13 @@
</mediaobject>
</para>
<para>
- The expanded war file and the XML descriptors are located in the <filename>HelloWorldPortlet/output/lib/exploded/helloworldportlet.war/WEB-INF/</filename> directory.
+ The expanded WAR file and the application descriptors are located in the <filename>HelloWorldPortlet/output/lib/exploded/helloworldportlet.war/WEB-INF/</filename> directory.
</para>
</sect3>
<sect3>
<title>Deploying your Portlet</title>
<para>
- If you did not expand the <filename>helloworldportlet.war</filename> file, copy the <filename>HelloWorldPortlet/helloworldportlet.war</filename> file into the correct JBoss AS or JBoss EAP <filename>deploy/</filename> directory. If you expanded the <filename>helloworldportlet.war</filename> file, copy the <filename>HelloWorldPortlet/output/lib/exploded/helloworldportlet.war/</filename> directory into the correct JBoss AS or JBoss EAP <filename>deploy/</filename> directory. For example, if you are using JBoss AS, copy the war file or the expanded directory into the <filename>$JBOSS_HOME/server/default/deploy/</filename> directory.
+ If you did not expand the <filename>helloworldportlet.war</filename> file, copy the <filename>HelloWorldPortlet/helloworldportlet.war</filename> file into the correct JBoss AS or JBoss EAP <filename>deploy/</filename> directory. If you expanded the <filename>helloworldportlet.war</filename> file, copy the <filename>HelloWorldPortlet/output/lib/exploded/helloworldportlet.war/</filename> directory into the correct JBoss AS or JBoss EAP <filename>deploy/</filename> directory. For example, if you are using JBoss AS, copy the WAR file or the expanded directory into the <filename>$JBOSS_HOME/server/default/deploy/</filename> directory.
</para>
<para>
Performing this step on a running instance of JBoss AS or JBoss EAP, and JBoss Portal, will trigger a hot-deploy of the portlet:
@@ -618,7 +618,7 @@
</mediaobject>
</para>
<para>
- To re-deploy the portlet, for example, if you have made changes to any of the XML descriptors, touch the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/helloworldportlet.war/WEB-INF/web.xml</filename> file. On Linux, run the following command to re-deploy the HelloWorldPortlet:
+ To re-deploy the portlet, for example, if you have made changes to any of the application descriptors, touch the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/helloworldportlet.war/WEB-INF/web.xml</filename> file. On Linux, run the following command to re-deploy the HelloWorldPortlet:
</para>
<para>
<screen>
@@ -888,7 +888,7 @@
</listitem>
<listitem>
<para>
- If required, edit the <filename>HelloWorldJSPPortlet/src/main/org/jboss/portlet/hello/HelloWorldJSPPortlet.java</filename> file, and the XML descriptors in the <filename>HelloWorldJSPPortlet/src/resources/helloworldjspportlet-war/WEB-INF/</filename> directory.
+ If required, edit the <filename>HelloWorldJSPPortlet/src/main/org/jboss/portlet/hello/HelloWorldJSPPortlet.java</filename> file, and the application descriptors in the <filename>HelloWorldJSPPortlet/src/resources/helloworldjspportlet-war/WEB-INF/</filename> directory.
</para>
</listitem>
<listitem>
@@ -909,7 +909,7 @@
Note: the directory names will be different for your system.
</para>
<para>
- Expanding the <filename>helloworldjspportlet.war</filename> file allows you to deploy the portlet as an expanded directory, which makes development easier. As well, it gives you access to the XML descriptors, resource files, JSF, and JSP pages. To expand the <filename>helloworldjspportlet.war</filename> file:
+ Expanding the <filename>helloworldjspportlet.war</filename> file allows you to deploy the portlet as an expanded directory, which makes development easier. As well, it gives you access to the application descriptors, resource files, JSF, and JSP pages. To expand the <filename>helloworldjspportlet.war</filename> file:
</para>
<para>
<orderedlist>
@@ -920,7 +920,7 @@
</listitem>
<listitem>
<para>
- To expand the war file, change into the <filename>HelloWorldJSPPortlet/</filename> directory, and run the <command>ant explode</command> command. On Linux, the output will be similar to the following:
+ To expand the WAR file, change into the <filename>HelloWorldJSPPortlet/</filename> directory, and run the <command>ant explode</command> command. On Linux, the output will be similar to the following:
</para>
<para>
<mediaobject>
@@ -946,13 +946,13 @@
</mediaobject>
</para>
<para>
- The expanded war file and the XML descriptors are located in the <filename>HelloWorldJSPPortlet/output/lib/exploded/helloworldjspportlet.war/WEB-INF/</filename> directory.
+ The expanded WAR file and the application descriptors are located in the <filename>HelloWorldJSPPortlet/output/lib/exploded/helloworldjspportlet.war/WEB-INF/</filename> directory.
</para>
</sect3>
<sect3>
<title>Deploying your JSP Portlet</title>
<para>
- If you did not expand the <filename>helloworldjspportlet.war</filename> file, copy the <filename>HelloWorldJSPPortlet/helloworldjspportlet.war</filename> file into the correct JBoss AS or JBoss EAP <filename>deploy/</filename> directory. If you expanded the <filename>helloworldjspportlet.war</filename> file, copy the <filename>HelloWorldJSPPortlet/output/lib/exploded/helloworldjspportlet.war/</filename> directory into the correct JBoss AS or JBoss EAP <filename>deploy/</filename> directory. For example, if you are using JBoss AS, copy the war file or the expanded directory into the <filename>$JBOSS_HOME/server/default/deploy/</filename> directory.
+ If you did not expand the <filename>helloworldjspportlet.war</filename> file, copy the <filename>HelloWorldJSPPortlet/helloworldjspportlet.war</filename> file into the correct JBoss AS or JBoss EAP <filename>deploy/</filename> directory. If you expanded the <filename>helloworldjspportlet.war</filename> file, copy the <filename>HelloWorldJSPPortlet/output/lib/exploded/helloworldjspportlet.war/</filename> directory into the correct JBoss AS or JBoss EAP <filename>deploy/</filename> directory. For example, if you are using JBoss AS, copy the WAR file or the expanded directory into the <filename>$JBOSS_HOME/server/default/deploy/</filename> directory.
</para>
<para>
Performing this step on a running instance of JBoss AS or JBoss EAP, and JBoss Portal, will trigger a hot-deploy of the portlet:
@@ -974,7 +974,7 @@
</mediaobject>
</para>
<para>
- To re-deploy the portlet, for example, if you have made changes to any of the XML descriptors, touch the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/helloworldjspportlet.war/WEB-INF/web.xml</filename> file. On Linux, run the following command to re-deploy the HelloWorldJSPPortlet:
+ To re-deploy the portlet, for example, if you have made changes to any of the application descriptors, touch the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/helloworldjspportlet.war/WEB-INF/web.xml</filename> file. On Linux, run the following command to re-deploy the HelloWorldJSPPortlet:
</para>
<para>
<screen>
@@ -1021,7 +1021,7 @@
<note>
<title>Bundled Sun JSF RI</title>
<para>
- JBoss AS version 4.2.<replaceable>x</replaceable> and JBoss EAP bundle Sun's JSF RI in the
+ JBoss AS version 4.2.<replaceable>x</replaceable> and JBoss EAP bundle Sun's JSF RI libraries in the
<filename>$JBOSS_HOME/server/default/deploy/jboss-web.deployer/jsf-libs/</filename> directory. Therefore, you do not need to package the Sun JSF RI libraries with your portlet application.
</para>
</note>
@@ -1080,7 +1080,7 @@
</screen></term>
<listitem>
<para>
- You must initialize the portlet with a default page to render, similar to what is done with the default JBoss Portal page.
+ You must initialize the portlet with a default page to render, similar to a welcome page.
</para>
</listitem>
</varlistentry>
@@ -1112,7 +1112,7 @@
</screen>
</para>
<para>
- Without the <filename>faces-config.xml</filename> file, the application would work the same outside of the portlet, as it would inside a portlet container. In this example, a basic user bean, <computeroutput><managed-bean-name>user</managed-bean-name></computeroutput>, and a navigation rule are defined, which handle submitting the original form in the <filename>HelloWorldJSFSunRIPortlet/WEB-INF/jsp/index.jsp</filename> file.
+ Without the <filename>faces-config.xml</filename> file, the application would work the same outside of the portlet as it would inside a portlet container. In this example, a basic user bean, <computeroutput><managed-bean-name>user</managed-bean-name></computeroutput>, and a navigation rule are defined, which handle the submission of the original form in the <filename>HelloWorldJSFSunRIPortlet/WEB-INF/jsp/index.jsp</filename> file.
</para>
<para>
The following is an example of the <computeroutput>Faces Servlet</computeroutput> section from the <filename>HelloWorldJSFSunRIPortlet/WEB-INF/web.xml</filename> file:
@@ -1143,7 +1143,17 @@
</screen>
</para>
<para>
- For the Sun JSF RI, this definition is mandatory to associate files with <filename>.jsf</filename> extensions with the Apache MyFaces servlet.
+ <variablelist>
+ <varlistentry><term><screen><![CDATA[
+<url-pattern>*.jsf</url-pattern>]]>
+</screen></term>
+<listitem>
+ <para>
+ For the Sun JSF RI, this definition is mandatory to associate files with <filename>.jsf</filename> extensions with the Apache MyFaces servlet.
+ </para>
+</listitem>
+</varlistentry>
+</variablelist>
</para>
<para>
<warning>
@@ -1163,12 +1173,12 @@
<orderedlist>
<listitem>
<para>
- Change into the <filename>HHelloWorldJSFSunRIPortlet</filename> directory, and remove the existing <filename>helloworldjsfsunriportlet.war</filename> file.
+ Change into the <filename>HelloWorldJSFSunRIPortlet/</filename> directory, and remove the existing <filename>helloworldjsfsunriportlet.war</filename> file.
</para>
</listitem>
<listitem>
<para>
- If required, edit the <filename>HelloWorldJSFSunRIPortlet/src/main/org/jboss/portlet/hello/bean/User.java</filename> file, and the XML descriptors in the <filename>HelloWorldJSFSunRIPortlet/src/resources/helloworldjsfsunriportlet-war/WEB-INF/</filename> directory.
+ If required, edit the <filename>HelloWorldJSFSunRIPortlet/src/main/org/jboss/portlet/hello/bean/User.java</filename> file, and the application descriptors in the <filename>HelloWorldJSFSunRIPortlet/src/resources/helloworldjsfsunriportlet-war/WEB-INF/</filename> directory.
</para>
</listitem>
<listitem>
@@ -1189,7 +1199,7 @@
Note: the directory names will be different for your system.
</para>
<para>
- Expanding the <filename>helloworldjsfsunriportlet.war</filename> file allows you to deploy the portlet as an expanded directory, which makes development easier. As well, it gives you access to the XML descriptors, resource files, JSF, and JSP pages. To expand the <filename>helloworldjsfsunriportlet.war</filename> file:
+ Expanding the <filename>helloworldjsfsunriportlet.war</filename> file allows you to deploy the portlet as an expanded directory, which makes development easier. As well, it gives you access to the application descriptors, resource files, JSF, and JSP pages. To expand the <filename>helloworldjsfsunriportlet.war</filename> file:
</para>
<para>
<orderedlist>
@@ -1200,7 +1210,7 @@
</listitem>
<listitem>
<para>
- To expand the war file, change into the <filename>HelloWorldJSFSunRIPortlet/</filename> directory, and run the <command>ant explode</command> command. On Linux, the output will be similar to the following:
+ To expand the WAR file, change into the <filename>HelloWorldJSFSunRIPortlet/</filename> directory, and run the <command>ant explode</command> command. On Linux, the output will be similar to the following:
</para>
<para>
<mediaobject>
@@ -1216,7 +1226,7 @@
Note: the directory names will be different for your system.
</para>
<para>
- The expanded war file and the XML descriptors are located in the <filename>HelloWorldJSFSunRIPortlet/output/lib/exploded/helloworldjsfsunriportlet.war</filename> directory.
+ The expanded WAR file and the application descriptors are located in the <filename>HelloWorldJSFSunRIPortlet/output/lib/exploded/helloworldjsfsunriportlet.war</filename> directory.
</para>
</sect3>
<sect3>
@@ -1233,7 +1243,7 @@
</screen>
</para>
<para>
- To see the HelloWorldJSFPortlet, navigate to <ulink url="http://localhost:8080/portal/">http://localhost:8080/portal/</ulink>, or, if the default JBoss Portal page is already open, refresh the page. The HelloWorldJSFPortlet is added to the bottom of the default JBoss Portal page:
+ To see the HelloWorldJSFSunRIPortlet, navigate to <ulink url="http://localhost:8080/portal/">http://localhost:8080/portal/</ulink>, or, if the default JBoss Portal page is already open, refresh the page. The HelloWorldJSFSunRIPortlet is added to the bottom of the default JBoss Portal page:
</para>
<para>
<mediaobject>
@@ -1243,7 +1253,7 @@
</mediaobject>
</para>
<para>
- To re-deploy the portlet, for example, if you have made changes to any of the XML descriptors, touch the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/helloworldjsfsunriportlet.war/WEB-INF/web.xml</filename> file. On Linux, run the following command to re-deploy the HelloWorldPortlet:
+ To re-deploy the portlet, for example, if you have made changes to any of the application descriptors, touch the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/helloworldjsfsunriportlet.war/WEB-INF/web.xml</filename> file. On Linux, run the following command to re-deploy the HelloWorldJSFSunRIPortlet:
</para>
<para>
<screen>
@@ -1251,7 +1261,7 @@
</screen>
</para>
<para>
- Re-deploying the HelloWorldJSFPortlet will produce output to the JBoss AS or JBoss EAP console, similar to the following:
+ Re-deploying the HelloWorldJSFSunRIPortlet will produce output to the JBoss AS or JBoss EAP console, similar to the following:
</para>
<para>
<screen><![CDATA[
16 years, 7 months
JBoss Portal SVN: r10004 - branches/JBoss_Portal_Branch_2_6/core/src/resources/portal-core-sar/conf/data.
by portal-commits＠lists.jboss.org
Author: sviluppatorefico
Date: 2008-02-17 17:30:16 -0500 (Sun, 17 Feb 2008)
New Revision: 10004
Modified:
branches/JBoss_Portal_Branch_2_6/core/src/resources/portal-core-sar/conf/data/default-object.xml
Log:
added internationalization to members
Modified: branches/JBoss_Portal_Branch_2_6/core/src/resources/portal-core-sar/conf/data/default-object.xml
===================================================================
--- branches/JBoss_Portal_Branch_2_6/core/src/resources/portal-core-sar/conf/data/default-object.xml 2008-02-17 17:54:52 UTC (rev 10003)
+++ branches/JBoss_Portal_Branch_2_6/core/src/resources/portal-core-sar/conf/data/default-object.xml 2008-02-17 22:30:16 UTC (rev 10004)
@@ -374,6 +374,8 @@
</page>
<page>
<page-name>Members</page-name>
+ <display-name xml:lang="en">Members</display-name>
+ <display-name xml:lang="it">Membri</display-name>
<window>
<window-name>IdentityAdminPortletWindow</window-name>
<instance-ref>IdentityAdminPortletInstance</instance-ref>
16 years, 7 months
JBoss Portal SVN: r10003 - in branches/JBoss_Portal_Branch_2_6/core-samples/src/resources/portal-weather-samples-war/WEB-INF: classes and 1 other directory.
by portal-commits＠lists.jboss.org
Author: sviluppatorefico
Date: 2008-02-17 12:54:52 -0500 (Sun, 17 Feb 2008)
New Revision: 10003
Modified:
branches/JBoss_Portal_Branch_2_6/core-samples/src/resources/portal-weather-samples-war/WEB-INF/classes/WeatherResource_it.properties
branches/JBoss_Portal_Branch_2_6/core-samples/src/resources/portal-weather-samples-war/WEB-INF/default-object.xml
Log:
italian updates
Modified: branches/JBoss_Portal_Branch_2_6/core-samples/src/resources/portal-weather-samples-war/WEB-INF/classes/WeatherResource_it.properties
===================================================================
--- branches/JBoss_Portal_Branch_2_6/core-samples/src/resources/portal-weather-samples-war/WEB-INF/classes/WeatherResource_it.properties 2008-02-17 16:10:54 UTC (rev 10002)
+++ branches/JBoss_Portal_Branch_2_6/core-samples/src/resources/portal-weather-samples-war/WEB-INF/classes/WeatherResource_it.properties 2008-02-17 17:54:52 UTC (rev 10003)
@@ -23,4 +23,7 @@
javax.portlet.preference.name.RssXml=URL per RSS
javax.portlet.preference.name.expires=Scadenza
-org.jboss.portal.object.name.Weather=Meteo
\ No newline at end of file
+org.jboss.portal.object.name.Weather=Meteo
+
+org.jboss.portal.instance.name.WeatherPortletInstance=Portlet Meteo
+org.jboss.portal.object.name.default.Weather= Meteo
\ No newline at end of file
Modified: branches/JBoss_Portal_Branch_2_6/core-samples/src/resources/portal-weather-samples-war/WEB-INF/default-object.xml
===================================================================
--- branches/JBoss_Portal_Branch_2_6/core-samples/src/resources/portal-weather-samples-war/WEB-INF/default-object.xml 2008-02-17 16:10:54 UTC (rev 10002)
+++ branches/JBoss_Portal_Branch_2_6/core-samples/src/resources/portal-weather-samples-war/WEB-INF/default-object.xml 2008-02-17 17:54:52 UTC (rev 10003)
@@ -34,6 +34,7 @@
<page-name>Weather</page-name>
<supported-locale>fr</supported-locale>
<supported-locale>en</supported-locale>
+ <supported-locale>it</supported-locale>
<resource-bundle>WeatherResource</resource-bundle>
<properties>
<property>
16 years, 7 months