Author: mmcallis Date: 2008-06-10 00:59:13 -0400 (Tue, 10 Jun 2008) New Revision: 10969 Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/errorhandling.xml docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/themeandlayouts.xml docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml Log: fixing trademarks for JSP (still in progress) Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/errorhandling.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/errorhandling.xml 2008-06-10 04:04:49 UTC (rev 10968) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/errorhandling.xml 2008-06-10 04:59:13 UTC (rev 10969) @@ -118,7 +118,7 @@ <sect2> <title>Portal Policy</title> <para> - 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. + 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 <trademark class="trade">JSP</trademark> 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. </para> </sect2> <sect2> @@ -135,7 +135,7 @@ </listitem> <listitem> <para> - replace the markup of the window using a redirection to a JSP page. + replace the markup of the window using a redirection to a <trademark class="trade">JSP</trademark> page. </para> </listitem> </itemizedlist> @@ -193,7 +193,7 @@ </row> <row> <entry align="center"><computeroutput>control.portal.resource_uri</computeroutput></entry> - <entry align="center">the path of the JSP used for redirections</entry> + <entry align="center">the path of the <trademark class="trade">JSP</trademark> used for redirections</entry> <entry align="center">a valid path to a JSP located in the <filename>portal-core.war/</filename> directory</entry> </row> </tbody> @@ -286,7 +286,7 @@ </row> <row> <entry align="center"><computeroutput>control.page.resource_uri</computeroutput></entry> - <entry align="center">the path of the JSP used for redirections</entry> + <entry align="center">the path of the <trademark class="trade">JSP</trademark> used for redirections</entry> <entry align="center"><computeroutput>ignore</computeroutput>, <computeroutput>jsp</computeroutput> and <computeroutput>hide</computeroutput></entry> </row> </tbody> Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/themeandlayouts.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/themeandlayouts.xml 2008-06-10 04:04:49 UTC (rev 10968) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/themeandlayouts.xml 2008-06-10 04:59:13 UTC (rev 10969) @@ -49,7 +49,7 @@ own entity. <itemizedlist> <para>To implement this encapsulation there are several ways:</para> - <listitem>JSPs that get included from the layout JSP for each region/portlet</listitem> + <listitem><trademark class="trade">JSP</trademark> pages that get included from the layout JSP for each region/portlet</listitem> <listitem>a taglib that allows to place region, window, and decoration tags into the layout JSP </listitem> @@ -131,7 +131,7 @@ <listitem>The first option would simply require to modify the theme CSS, by doing this you could change the fonts, the way tabs are rendered, colors and many other things but not change the content.</listitem> - <listitem>The second option is to modify the provided JSPs, <literal>header.jsp</literal> and + <listitem>The second option is to modify the provided <trademark class="trade">JSP</trademark> files, <literal>header.jsp</literal> and <literal>tabs.jsp</literal>. It gives you more flexibility than the previous solution on modifying the content. Links to legacy application could easily be added, URLs could be arranged differently, the CSS approach could be replaced by good old HTML, CSS style names could be changed... The drawback of @@ -141,14 +141,14 @@ </itemizedlist> </para> <sect3> - <title>Writing his own JSPs</title> - <para>The content of those two parts are displayed thanks to two different JSP pages. By default + <title>Writing his own <trademark class="trade">JSP</trademark> pages</title> + <para>The content of those two parts are displayed thanks to two different <trademark class="trade">JSP</trademark> pages. By default you would find those pages in the directory <literal>portal-core.war/WEB-INF/jsp/header/</literal>. The file <literal>header.jsp</literal> is used to display the links that are displayed on the upper right of the default theme. The file <literal>tabs.jsp</literal> is used to display the pages tabs appearing on the left. </para> - <para> Again, you have several choices, either to edit the included JSPs directly or create your own, + <para> Again, you have several choices, either to edit the included <trademark class="trade">JSP</trademark> files directly or create your own, store them in a web application then edit the following file: <literal>jboss-portal.sar/META-INF/jboss-service.xml</literal>. The interesting part in that file is the following: <programlisting><![CDATA[<mbean @@ -166,7 +166,7 @@ </mbean>]]></programlisting> The three attributes are: <itemizedlist> - <listitem>TargetContextPath: Defines the web application context where the JSPs are located</listitem> + <listitem>TargetContextPath: Defines the web application context where the JSP files are located</listitem> <listitem>HeaderPath: Defines the location (in the web application previously defined) of the JSP in charge of writing the header links</listitem> <listitem>TabsPath: Defines the location (in the web application previously defined) of the JSP in charge of writing the pages links (note that it doesn't have to be renderer as tabs)</listitem> </itemizedlist> @@ -367,7 +367,7 @@ </sect2> --> <sect2> - <title>Layout JSP-tags</title> + <title>Layout <trademark class="trade">JSP</trademark> tags</title> <para>The portal comes with a set of JSP tags that allow the layout developer faster development. <itemizedlist> @@ -803,7 +803,7 @@ swap, or change individual items of it. No compile or redeploy is necessary. Themes can be added or removed while the portal is active. Themes can be deployed in separate web applications furthering even more the flexibility of this approach. Web developers - don't have to work with JSPs. They can stay in their favorite design tool and simple + don't have to work with <trademark class="trade">JSP</trademark> pages. They can stay in their favorite design tool and simple work against the exploded war content that is deployed into the portal. The results can be validated life in the portal. </para> 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-06-10 04:04:49 UTC (rev 10968) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-06-10 04:59:13 UTC (rev 10969) @@ -148,7 +148,7 @@ <sect3> <title>Package Structure</title> <para> - 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, JSPs, and other static or dynamic files. The following is an example of the directory structure of the HelloWorldPortlet portlet: + 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">JSP</trademark>, and other static or dynamic files. The following is an example of the directory structure of the HelloWorldPortlet portlet: </para> <para> <mediaobject> @@ -554,7 +554,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 application 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 <trademark class="trade">JSP</trademark> pages. To expand the <filename>helloworldportlet.war</filename> file: </para> <para> <orderedlist> @@ -640,11 +640,11 @@ </sect3> </sect2> <sect2> - <title>An example JSP Portlet</title> + <title>An example <trademark class="trade">JSP</trademark> portlet</title> <sect3> <title>Introduction</title> <para> - This section describes how to deploy a JSP portlet in JBoss Portal. Before proceeding, download the <ulink url="http://anonsvn.jboss.org/repos/portletswap/portlets/2_4/bundles... from <ulink url="http://labs.jboss.com/portletswap/">JBoss PortletSwap</ulink>. The HelloWorldJSPPortlet demonstrates how to use JSPs for view rendering, and the portlet tag library (taglib) for generating links. + This section describes how to deploy a <trademark class="trade">JSP</trademark> portlet in JBoss Portal. Before proceeding, download the <ulink url="http://anonsvn.jboss.org/repos/portletswap/portlets/2_4/bundles... from <ulink url="http://labs.jboss.com/portletswap/">JBoss PortletSwap</ulink>. The HelloWorldJSPPortlet demonstrates how to use JSP pages for view rendering, and the portlet tag library (taglib) for generating links. </para> </sect3> <sect3> @@ -786,7 +786,7 @@ </screen></term> <listitem> <para> - The <literal>doView</literal> implementation is responsible for dispatching to the appropriate JSP, <filename>HelloWorldJSPPortlet/WEB-INF/jsp/view.jsp</filename> or <filename>HelloWorldJSPPortlet/WEB-INF/jsp/view2.jsp</filename>, depending on the existence of the <literal>yourname</literal> parameter passed in from <literal>processAction</literal>. + The <literal>doView</literal> implementation is responsible for dispatching to the appropriate <trademark class="trade">JSP</trademark>, <filename>HelloWorldJSPPortlet/WEB-INF/jsp/view.jsp</filename> or <filename>HelloWorldJSPPortlet/WEB-INF/jsp/view2.jsp</filename>, depending on the existence of the <literal>yourname</literal> parameter passed in from <literal>processAction</literal>. </para> </listitem> </varlistentry> @@ -794,9 +794,9 @@ </para> </sect3> <sect3> - <title>JSP Files and the Portlet Tag Library</title> + <title><trademark class="trade">JSP</trademark> files and the Portlet Tag Library</title> <para> - The <filename>HelloWorldJSPPortlet/WEB-INF/jsp/view.jsp</filename> and <filename>HelloWorldJSPPortlet/WEB-INF/jsp/view2.jsp</filename> JSP files are included in the HelloWorldJSPPortlet portlet. The <filename>view.jsp</filename> file allows a user to input their name. This is then posted to the <computeroutput>processAction</computeroutput> method in the portlet class, which is set as a <computeroutput>aResponse.setRenderParameter</computeroutput>. The <computeroutput>doView</computeroutput> <literal>render</literal> method is invoked, which dispatches to the <filename>view2.jsp</filename> JSP: + The <filename>HelloWorldJSPPortlet/WEB-INF/jsp/view.jsp</filename> and <filename>HelloWorldJSPPortlet/WEB-INF/jsp/view2.jsp</filename> <trademark class="trade">JSP</trademark> files are included in the HelloWorldJSPPortlet portlet. The <filename>view.jsp</filename> file allows a user to input their name. This is then posted to the <computeroutput>processAction</computeroutput> method in the portlet class, which is set as a <computeroutput>aResponse.setRenderParameter</computeroutput>. The <computeroutput>doView</computeroutput> <literal>render</literal> method is invoked, which dispatches to the <filename>view2.jsp</filename> JSP: </para> <para> <mediaobject> @@ -876,7 +876,7 @@ </para> </sect3> <sect3> - <title>Building your JSP Portlet</title> + <title>Building your <trademark class="trade">JSP</trademark> portlet</title> <para> The <filename>HelloWorldJSPPortlet.zip</filename> file contains a pre-compiled <filename>helloworldjspportlet.war</filename> file; however, to manually build the <filename>helloworldjspportlet.war</filename> file: </para> @@ -910,7 +910,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 application 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 <trademark class="trade">JSP</trademark> pages. To expand the <filename>helloworldjspportlet.war</filename> file: </para> <para> <orderedlist> @@ -951,7 +951,7 @@ </para> </sect3> <sect3> - <title>Deploying your JSP Portlet</title> + <title>Deploying your <trademark class="trade">JSP</trademark> 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 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. </para> @@ -1203,7 +1203,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 application 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 <trademark class="trade">JSP</trademark> pages. To expand the <filename>helloworldjsfsunriportlet.war</filename> file: </para> <para> <orderedlist> @@ -1508,7 +1508,7 @@ 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: + 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 <trademark class="trade">JSP</trademark> pages. To expand the <filename>helloworldjsfmyfacesportlet.war</filename> file: </para> <para> <orderedlist>