JBoss Portal SVN: r9829 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-07 03:15:41 -0500 (Thu, 07 Feb 2008)
New Revision: 9829
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
Log:
minor spelling/sentance corrections 5.1. JSR-168 Overview
to 5.2. Tutorials
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-07 07:36:36 UTC (rev 9828)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-07 08:15:41 UTC (rev 9829)
@@ -19,10 +19,10 @@
<title>Portlet Primer</title>
<sect1 id="portlet_primer">
<title>JSR-168 Overview</title>
- <para>The JSR-168 specification aims at defining portlets that can be used by any JSR-168 portlet container, also known as portals. There are different portals with commercial and non-commercial licenses. This chapter gives a brief overview of the <ulink url="http://www.jcp.org/en/jsr/detail?id=168">JSR-168 Portlet Specification</ulink>. Portlet developers are strongly encouraged to read the <ulink url="http://www.jcp.org/en/jsr/detail?id=168">JSR-168 Portlet Specification</ulink>.
+ <para>The JSR-168 Portlet Specification aims at defining portlets that can be used by any JSR-168 portlet container, also known as a portal. There are different portals with commercial and non-commercial licenses. This chapter gives a brief overview of the <ulink url="http://www.jcp.org/en/jsr/detail?id=168">JSR-168 Portlet Specification</ulink>. Portlet developers are strongly encouraged to read the <ulink url="http://www.jcp.org/en/jsr/detail?id=168">JSR-168 Portlet Specification</ulink>.
</para>
<para>
- JBoss portal is fully JSR-168 compliant, which means any JSR-168 portlet will behave as it should inside the portal.
+ JBoss Portal is fully JSR-168 compliant, which means any JSR-168 portlet will behave as it should inside the portal.
</para>
<sect2>
<title>Portal Pages</title>
@@ -67,7 +67,7 @@
<title>Window States</title>
<para>
Window states are an indicator of how much page real-estate a portlet should consume on any given page.
- The three states defined by the JSR-168 specification:
+ The three states defined by the JSR-168 specification are:
</para>
<para>
<itemizedlist>
@@ -91,18 +91,17 @@
</sect2>
<sect2>
<title>Section Status</title>
- This overview of the portlet specification, is a work in progress. Check back for more in-depth analsis of the
- specification, but please read on for real-world cases of how to leverage the specification.
+ <para>
+ This overview of the JSR-168 Portlet Specification is a work in progress. Check back for more in-depth analsis of the specification. The sections following here after contain real-world cases for how to leverage the specification.
+ </para>
</sect2>
</sect1>
<sect1 id="tutorials_tutorials">
<title>Tutorials</title>
<para>
The tutorials contained in this chapter are targetted toward portlet developers. Although they are a good
- starting and reference point, we do heavily recommend that portlet developers read and understand the
- <ulink url="http://www.jcp.org/en/jsr/detail?id=168">Portlet Specification (JSR-168)</ulink>. We also recommend
- using our <ulink url="http://jboss.org/index.html?module=bb&op=viewforum&f=215">JBoss Portal User
- Forums</ulink> for user-to-user help, when needed.
+ starting and reference point, it is heavily recommend that portlet developers read and understand the
+ <ulink url="http://www.jcp.org/en/jsr/detail?id=168">JSR-168 Portlet Specification</ulink>. Use the <ulink url="http://jboss.org/index.html?module=bb&op=viewforum&f=215">JBoss Portal User Forums</ulink> for user-to-user help.
</para>
<!--<sect2 id="build_instructions">
<title>
16 years, 4 months
- 1
- 0
JBoss Portal SVN: r9828 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-07 02:36:36 -0500 (Thu, 07 Feb 2008)
New Revision: 9828
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
Log:
revising 5.1. JSR-168 Overview to 5.1.3. Window States
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-07 07:15:10 UTC (rev 9827)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-07 07:36:36 UTC (rev 9828)
@@ -26,22 +26,40 @@
</para>
<sect2>
<title>Portal Pages</title>
- <para>A portal can be seen as pages with different areas and inside areas, different windows and each window
- having one portlet.</para>
+ <para>
+ A portal can be seen as pages with different areas, and inside areas, different windows, and each window
+ having one portlet:
+ </para>
+ <para>
<mediaobject>
<imageobject>
<imagedata align="center" fileref="images/tutorials/SpecPortalDef.png" valign="middle"/>
</imageobject>
</mediaobject>
+ </para>
</sect2>
<sect2>
<title>Rendering Modes</title>
- <para>A porlet can have different view modes, three modes are defined by the specification but a portal can
- extend those modes. The 3 modes are:
+ <para>A portlet can have different view modes. Three modes are defined by the JSR-168 specification, but a portal can
+ extend those modes. The three modes are:
+ </para>
+ <para>
<itemizedlist>
- <listitem>VIEW - Generates markup reflecting the current state of the portlet.</listitem>
- <listitem>EDIT - Should allow a user to customize the behavior of the portlet.</listitem>
- <listitem>HELP - Should provide some information to the user as to how to use the portlet.</listitem>
+ <listitem>
+ <para>
+ VIEW - generates markup reflecting the current state of the portlet.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ EDIT - allows a user to customize the behavior of the portlet.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ HELP - provides information to the user as to how to use the portlet.
+ </para>
+ </listitem>
</itemizedlist>
</para>
</sect2>
@@ -49,11 +67,25 @@
<title>Window States</title>
<para>
Window states are an indicator of how much page real-estate a portlet should consume on any given page.
- There are 3 states defined by the specification:
+ The three states defined by the JSR-168 specification:
+ </para>
+ <para>
<itemizedlist>
- <listitem>NORMAL - A portlet shares this page with other portlets.</listitem>
- <listitem>MINIMIZED - A portlet may show very little information or none at all.</listitem>
- <listitem>MAXIMIZED - A portlet may be the only portlet displayed on this page.</listitem>
+ <listitem>
+ <para>
+ NORMAL - a portlet shares this page with other portlets.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ MINIMIZED -a portlet may show very little information, or none at all.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ MAXIMIZED - a portlet may be the only portlet displayed on this page.
+ </para>
+ </listitem>
</itemizedlist>
</para>
</sect2>
16 years, 4 months
- 1
- 0
JBoss Portal SVN: r9827 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-07 02:15:10 -0500 (Thu, 07 Feb 2008)
New Revision: 9827
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:
revising 5.1. JSR-168 Overview, moving 2.3.4.1. Database Setup
2.3.4.2. DataSource Configuration into section 2, instead
of separate sections.
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-07 05:31:34 UTC (rev 9826)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml 2008-02-07 07:15:10 UTC (rev 9827)
@@ -84,7 +84,8 @@
</imageobject>
</mediaobject>
</para>
- <sect3>
+</sect2>
+ <sect2>
<title>Portlet Names</title>
<para>
Names of certain core bundled portlets have changed. Destroy the following instances and use the AdminPortlet to recreate them, or, edit the <emphasis role="bold">JBP_INSTANCES</emphasis> table as follows:
@@ -130,8 +131,8 @@
</listitem>
</orderedlist>
</para>
- </sect3>
- <sect3>
+ </sect2>
+ <sect2>
<title>CMS</title>
<para>
In JBoss Portal 2.6 versions, the way the CMS content is displayed changed significantly. For further information, please refer to <xref linkend="contentintegration"/> and <xref linkend="cmsPortlet"/>. Currently there is no need to have more than one instance of the <emphasis>CMSPortlet</emphasis>. The portlet window displays CMS content, not by referring to that portlet instance, but by having the proper <emphasis>content-type</emphasis> defined. The following configuration is in the <filename>jboss-portal.sar/conf/data/default-object.xml</filename> file:
@@ -191,8 +192,7 @@
</para>
</note>
</para>
- </sect3>
- </sect2>
+ </sect2>
</sect1>
<!--
<para>This chapter addresses migration issues from version 2.2 to 2.4 of JBoss 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-02-07 05:31:34 UTC (rev 9826)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-07 07:15:10 UTC (rev 9827)
@@ -19,21 +19,11 @@
<title>Portlet Primer</title>
<sect1 id="portlet_primer">
<title>JSR-168 Overview</title>
- <para>The JSR-168 specification aims at defining porlets that can be used by any JSR-168 portlet container also
- called portals. There are different portals out there with commercial and non-commercial licences. In this
- chapter we will briefly describe such portlets but for more details you should read the specifications
- available on the web.</para>
+ <para>The JSR-168 specification aims at defining portlets that can be used by any JSR-168 portlet container, also known as portals. There are different portals with commercial and non-commercial licenses. This chapter gives a brief overview of the <ulink url="http://www.jcp.org/en/jsr/detail?id=168">JSR-168 Portlet Specification</ulink>. Portlet developers are strongly encouraged to read the <ulink url="http://www.jcp.org/en/jsr/detail?id=168">JSR-168 Portlet Specification</ulink>.
+ </para>
<para>
- <note>This section is a brief overview of the
- <ulink url="http://www.jcp.org/en/jsr/detail?id=168">JSR-168 Portlet Specification</ulink>
- , and it does not cover the topics in great detail. We strongly encourage portlet developers to read the
- Specification that can be found
- <ulink url="http://www.jcp.org/en/jsr/detail?id=168">here</ulink>
- .
- </note>
+ JBoss portal is fully JSR-168 compliant, which means any JSR-168 portlet will behave as it should inside the portal.
</para>
- <para>As of today, JBoss portal is fully JSR-168 compliant, that means that any JSR-168 portlet will behave
- as it should inside the portal.</para>
<sect2>
<title>Portal Pages</title>
<para>A portal can be seen as pages with different areas and inside areas, different windows and each window
16 years, 4 months
- 1
- 0
JBoss Portal SVN: r9826 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-07 00:31:34 -0500 (Thu, 07 Feb 2008)
New Revision: 9826
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml
Log:
4.1.2.2. CMS fixing type parent_key / PK
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-07 05:22:15 UTC (rev 9825)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml 2008-02-07 05:31:34 UTC (rev 9826)
@@ -150,7 +150,7 @@
</screen>
</para>
<para>
- The following example uses the MySQL Query Browser. Open the <emphasis role="bold">JBP_OBJECT_NODE</emphasis> table in your database schema. Look at the <emphasis role="bold">PATH</emphasis> column to identify any occurrences of CMS in your JBoss Portal deployment. Identify any row referring to <emphasis>CMSPortletWindow</emphasis>, and remember the number in <emphasis role="bold">PARENT_KEY</emphasis> column. The <emphasis role="bold">PARENT_KEY</emphasis> number is needed in the following steps:
+ The following example uses the MySQL Query Browser. Open the <emphasis role="bold">JBP_OBJECT_NODE</emphasis> table in your database schema. Look at the <emphasis role="bold">PATH</emphasis> column to identify any occurrences of CMS in your JBoss Portal deployment. Identify any row referring to <emphasis>CMSPortletWindow</emphasis>, and remember the number in <emphasis role="bold">PK</emphasis> column. The <emphasis role="bold">PK</emphasis> number is needed in the following steps:
</para>
<para>
<mediaobject>
@@ -161,13 +161,13 @@
</para>
<para>
Go to the <emphasis role="bold">JBP_WINDOW</emphasis> table and find a row with the same
- <emphasis role="bold">PARENT_KEY</emphasis> value from the <emphasis role="bold">JBP_OBJECT_NODE</emphasis> table. In such a row, replace <emphasis>CMSPortletInstance</emphasis> with a path to your CMS resource. For example, by default, JBoss Portal displays <filename>/default/index.html</filename>.
+ <emphasis role="bold">PK</emphasis> value from the <emphasis role="bold">JBP_OBJECT_NODE</emphasis> table. In such a row, replace <emphasis>CMSPortletInstance</emphasis> with a path to your CMS resource. For example, by default, JBoss Portal displays <filename>/default/index.html</filename>.
</para>
<para> Go to the <emphasis role="bold">JBP_PORTAL_OBJECT_PROPS</emphasis> table and add a row containing:
<itemizedlist>
<listitem>
<para>
- The <emphasis role="bold">PARENT_KEY</emphasis> number remembered from the <emphasis>OBJECT_KEY</emphasis> column.
+ The <emphasis role="bold">PK</emphasis> number remembered from the <emphasis>OBJECT_KEY</emphasis> column.
</para>
</listitem>
<listitem>
16 years, 4 months
- 1
- 0
JBoss Portal SVN: r9825 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-07 00:22:15 -0500 (Thu, 07 Feb 2008)
New Revision: 9825
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml
Log:
revising 4.1.2.2. CMS
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-07 05:21:26 UTC (rev 9824)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml 2008-02-07 05:22:15 UTC (rev 9825)
@@ -134,15 +134,10 @@
<sect3>
<title>CMS</title>
<para>
- This is probably the less trival part to do directly in database. In JBP 2.6 version the way that CMS
- content is being displayed changed significantly. Please refer to
- <link linkend="contentintegration">Content Integration</link> and <link linkend="cmsPortlet">CMS Portlet</link>
- chapters for more information. Basically currently there is no need to have more than one instance of
- <emphasis>CMSPortlet</emphasis> and the portlet window displays CMS content not by referring to that portlet instance
- but by having proper <emphasis>content-type</emphasis> defined. In "<emphasis>default-object.xml</emphasis>
- you will find following configuration:
- <programlisting>
- <![CDATA[
+ In JBoss Portal 2.6 versions, the way the CMS content is displayed changed significantly. For further information, please refer to <xref linkend="contentintegration"/> and <xref linkend="cmsPortlet"/>. Currently there is no need to have more than one instance of the <emphasis>CMSPortlet</emphasis>. The portlet window displays CMS content, not by referring to that portlet instance, but by having the proper <emphasis>content-type</emphasis> defined. The following configuration is in the <filename>jboss-portal.sar/conf/data/default-object.xml</filename> file:
+ </para>
+ <para>
+<screen><![CDATA[
<window>
<window-name>CMSWindow</window-name>
<content>
@@ -151,53 +146,54 @@
</content>
<region>center</region>
<height>0</height>
-</window>
- ]]>
- </programlisting>
- </para>
+</window>]]>
+</screen>
+</para>
<para>
- Open <emphasis role="bold">JBP_OBJECT_NODE</emphasis> table in your database schema. By looking at
- <emphasis role="bold">PATH</emphasis> column you will easily find any occurances of CMS in your portal
- deployment
+ The following example uses the MySQL Query Browser. Open the <emphasis role="bold">JBP_OBJECT_NODE</emphasis> table in your database schema. Look at the <emphasis role="bold">PATH</emphasis> column to identify any occurrences of CMS in your JBoss Portal deployment. Identify any row referring to <emphasis>CMSPortletWindow</emphasis>, and remember the number in <emphasis role="bold">PARENT_KEY</emphasis> column. The <emphasis role="bold">PARENT_KEY</emphasis> number is needed in the following steps:
</para>
+ <para>
<mediaobject>
<imageobject>
<imagedata align="center" valign="middle" fileref="images/migration/querybrowser2.png"/>
</imageobject>
</mediaobject>
+ </para>
<para>
- For any row you will identify as referring to <emphasis>CMSPortletWindow</emphasis> in your system remember
- the number in <emphasis role="bold">PK</emphasis> column. It will be needed in next steps
+ Go to the <emphasis role="bold">JBP_WINDOW</emphasis> table and find a row with the same
+ <emphasis role="bold">PARENT_KEY</emphasis> value from the <emphasis role="bold">JBP_OBJECT_NODE</emphasis> table. In such a row, replace <emphasis>CMSPortletInstance</emphasis> with a path to your CMS resource. For example, by default, JBoss Portal displays <filename>/default/index.html</filename>.
</para>
- <para> Go to <emphasis role="bold">JBP_WINDOW</emphasis> table and find row with the same
- <emphasis role="bold">PK</emphasis> value like the one from
- <emphasis role="bold">JBP_OBJECT_NODE</emphasis> table. In such row replace
- "<emphasis>CMSPortletInstance</emphasis>" with a path to your CMS resource. For example by default
- portal is displaying "<emphasis>/default/index.html</emphasis>".
- </para>
- <para> Go to <emphasis role="bold">JBP_PORTAL_OBJECT_PROPS</emphasis> table and add a row containing:
+ <para> Go to the <emphasis role="bold">JBP_PORTAL_OBJECT_PROPS</emphasis> table and add a row containing:
<itemizedlist>
<listitem>
- The number you remembered in "<emphasis>OBJECT_KEY</emphasis>" column.
- </listitem>
- <listitem>
- "<emphasis>portal.windowContentType</emphasis>" in "<emphasis>NAME</emphasis>" column.
- </listitem>
- <listitem>
- "<emphasis>cms</emphasis>" in "<emphasis>jbp_VALUE</emphasis>" column.
- </listitem>
- </itemizedlist>
- </para>
+ <para>
+ The <emphasis role="bold">PARENT_KEY</emphasis> number remembered from the <emphasis>OBJECT_KEY</emphasis> column.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>portal.windowContentType</emphasis> in the <emphasis>NAME</emphasis> column.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>cms</emphasis> in the <emphasis>jbp_VALUE</emphasis> column.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
<para>
- <note>Remember that you can also change portlet window content type and configure path to CMS resource
- using AdminPortlet</note>
+ <note>
+ <title>Portlet Content Type and Path to the CMS Resource</title>
+ <para>
+ You can change the portlet window content type and configure the path to the CMS resource
+ using the AdminPortlet.
+ </para>
+ </note>
</para>
</sect3>
</sect2>
-
-
-
- </sect1>
+</sect1>
<!--
<para>This chapter addresses migration issues from version 2.2 to 2.4 of JBoss Portal.</para>
<sect1 id="migrating_database">
16 years, 4 months
- 1
- 0
JBoss Portal SVN: r9824 - modules/portlet/trunk/test/src/main/java/org/jboss/portal/simple/samples.
by portal-commits＠lists.jboss.org
Author: chris.laprun(a)jboss.com
Date: 2008-02-07 00:21:26 -0500 (Thu, 07 Feb 2008)
New Revision: 9824
Modified:
modules/portlet/trunk/test/src/main/java/org/jboss/portal/simple/samples/RemoteControlResourcePortlet.java
Log:
- Make remote control work. I don't like javascript! :p
Modified: modules/portlet/trunk/test/src/main/java/org/jboss/portal/simple/samples/RemoteControlResourcePortlet.java
===================================================================
--- modules/portlet/trunk/test/src/main/java/org/jboss/portal/simple/samples/RemoteControlResourcePortlet.java 2008-02-07 03:54:28 UTC (rev 9823)
+++ modules/portlet/trunk/test/src/main/java/org/jboss/portal/simple/samples/RemoteControlResourcePortlet.java 2008-02-07 05:21:26 UTC (rev 9824)
@@ -29,12 +29,12 @@
{
renderResponse.setContentType("text/html");
PrintWriter printWriter = renderResponse.getWriter();
- printWriter.print("<p><a href=\"");
- String url = "javascript:window.open('";
+ printWriter.print("<script type='text/javascript'>function openRemote(url){window.name='jbp_parent';" +
+ "window.open(url, 'jbp_remote', 'width=400,height=200,scrollable=yes')}</script>");
+ printWriter.print("<p><a href='#' onclick=\"openRemote('");
ResourceURL resource = renderResponse.createResourceURL();
- url += resource + "','Remote Control','width=400,height=200')";
- printWriter.print(url);
- printWriter.print("\">Open remote control!</a></p>");
+ printWriter.print(resource);
+ printWriter.print("')\">Open remote control!</a></p>");
}
@Override
@@ -42,21 +42,27 @@
{
resourceResponse.setContentType("text/html");
PrintWriter writer = resourceResponse.getWriter();
+ writer.print("<script type='text/javascript'>function openLinkInParent(url){window.open(url,'jbp_parent');}</script>");
PortletURL url = resourceResponse.createRenderURL();
url.setWindowState(WindowState.MINIMIZED);
- writer.print("<ul><li><a target='_parent' href='" + url + "'>minimize</a></li>");
+ writer.print("<ul><li><a href='#' onclick=\"" + createParentURL(url) + "\">minimize</a></li>");
url.setWindowState(WindowState.MAXIMIZED);
- writer.print("<li><a href='" + url + "'>maximize</a></li>");
+ writer.print("<li><a href='#' onclick=\"" + createParentURL(url) + "\">maximize</a></li>");
url.setWindowState(WindowState.NORMAL);
- writer.print("<li><a href='" + url + "'>normal</a></li></ul>");
+ writer.print("<li><a href='#' onclick=\"" + createParentURL(url) + "\">normal</a></li></ul>");
writer.print("<p><b>'zipcode'</b> public render parameter value: " + resourceRequest.getParameter(ZIPCODE) + "<br/>");
writer.print("<p>Set value of <b>'zipcode'</b> public render parameter to:");
url.setParameter(ZIPCODE, "80201");
- writer.print("<li><a href='" + url + "'>Denver</a>");
+ writer.print("<li><a href='#' onclick=\"" + createParentURL(url) + "\">Denver</a>");
url.setParameter(ZIPCODE, "94102");
- writer.print("<li><a href='" + url + "'>San Francisco</a>");
+ writer.print("<li><a href='#' onclick=\"" + createParentURL(url) + "\">San Francisco</a>");
url.setParameter(ZIPCODE, "20001");
- writer.print("<li><a href='" + url + "'>Washington, DC</a>");
+ writer.print("<li><a href='#' onclick=\"" + createParentURL(url) + "\">Washington, DC</a>");
writer.print("</ul></p>");
}
+
+ private String createParentURL(PortletURL url)
+ {
+ return "openLinkInParent('" + url + "')";
+ }
}
16 years, 4 months
- 1
- 0
JBoss Portal SVN: r9823 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-06 22:54:28 -0500 (Wed, 06 Feb 2008)
New Revision: 9823
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml
Log:
revising 4.1.2.1. Portlet Names, removing note admonitions,
changing itemized list to orderedlist
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-07 02:04:13 UTC (rev 9822)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml 2008-02-07 03:54:28 UTC (rev 9823)
@@ -85,47 +85,51 @@
</mediaobject>
</para>
<sect3>
- <title>Portlet names</title>
- <para>Names of few core bundled portlets changed. To update them you need to:</para>
+ <title>Portlet Names</title>
<para>
- In <emphasis role="bold">JBP_INSTANCES</emphasis> table:
- <itemizedlist>
- <listitem>Change "<emphasis>local.portal.CMSPorlet</emphasis>" in <emphasis>PORTLET_REF</emphasis> column to
- "<emphasis>local./portal-cms.CMSPortlet</emphasis>"
- </listitem>
- <listitem>Change "<emphasis>local.portal.CMSAdminPorlet</emphasis>" in <emphasis>PORTLET_REF</emphasis> column to
- "<emphasis>local./portal-cms.CMSAdminPortlet</emphasis>"
- </listitem>
- <listitem>Change "<emphasis>local.portal.ManagementPorlet</emphasis>" in <emphasis>PORTLET_REF</emphasis> column to
- "<emphasis>local./portal-admin.AdminPortlet</emphasis>"
- </listitem>
- </itemizedlist>
- </para>
- <note>Instead of editing database you can destroy those instances in AdminPortlet and recreate them.</note>
+ Names of certain core bundled portlets have changed. Destroy the following instances and use the AdminPortlet to recreate them, or, edit the <emphasis role="bold">JBP_INSTANCES</emphasis> table as follows:
+ </para>
+ <para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Change <emphasis>local.portal.CMSPorlet</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>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Change <emphasis>local.portal.ManagementPorlet</emphasis> in the <emphasis>PORTLET_REF</emphasis> column to <emphasis>local./portal-admin.AdminPortlet</emphasis>.
+ </para>
+ </listitem>
+ </orderedlist>
+ </para>
<para>
- <emphasis>NavigationPortlet</emphasis> from JBP 2.4 is not present anymore. Its functionality is now realized by
- <emphasis>PageCustomizerInterceptor</emphasis> so all references to <emphasis>NavigationPortlet</emphasis> should
- be removed from all portal pages. You can do it either by cleaning up database content or by using
- <emphasis>AdminPortlet</emphasis> in Portal interface. In database you should remove:
- <itemizedlist>
- <listitem>
- Rows containing "<emphasis>local.portal.NavigationPortlet</emphasis>" in
- "<emphasis>PORTLET_REF</emphasis>" column in
- "<emphasis>JBP_INSTANCES</emphasis>" table.
- </listitem>
- <listitem>
- Rows containing "<emphasis>NavigationPortletInstance</emphasis>" in
- "<emphasis>INSTANCE_REF</emphasis>" column in
- "<emphasis>JBP_WINDOW</emphasis>" table.
- </listitem>
- <listitem>
- Rows containing "<emphasis>NavigationPortletWindow</emphasis>" in
- "<emphasis>NAME</emphasis>" column in
- "<emphasis>JBP_OBJECT</emphasis>" table.
- </listitem>
- </itemizedlist>
- </para>
- <note>Instead of editing database you can just remove NavigationPortletInstance using AdminPortlet.</note>
+ The <emphasis>NavigationPortlet</emphasis> from JBoss Portal 2.4 has been removed, and its functionality is now replaced by <emphasis>PageCustomizerInterceptor</emphasis>. All references to the <emphasis>NavigationPortlet</emphasis> should be removed from all portal pages. Remove <emphasis>NavigationPortletInstance</emphasis> using the AdminPortlet, or edit the database as follows:
+ </para>
+ <para>
+ <orderedlist>
+ <listitem>
+ <para>
+ In the <emphasis>JBP_INSTANCES</emphasis> table, rows containing <emphasis>local.portal.NavigationPortlet</emphasis> in the <emphasis>PORTLET_REF</emphasis> column.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In the <emphasis>JBP_WINDOW</emphasis> table, rows containing <emphasis>NavigationPortletInstance</emphasis> in the <emphasis>INSTANCE_REF</emphasis> column.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In the <emphasis>JBP_OBJECT</emphasis> table, rows containing <emphasis>NavigationPortletWindow</emphasis> in the <emphasis>NAME</emphasis> column.
+ </para>
+ </listitem>
+ </orderedlist>
+ </para>
</sect3>
<sect3>
<title>CMS</title>
16 years, 4 months
- 1
- 0
JBoss Portal SVN: r9822 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-06 21:04:13 -0500 (Wed, 06 Feb 2008)
New Revision: 9822
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml
Log:
revising 4.1.2. Updating the Database
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-07 01:28:49 UTC (rev 9821)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml 2008-02-07 02:04:13 UTC (rev 9822)
@@ -68,23 +68,22 @@
</sect2>
<sect2 id="upgrade_portal_database">
<title>Updating the Database</title>
- <note>All things described in this section can be done using AdminPortlet. Treat this directions more as guideline
- if you need to automate migration for big portal deployment.</note>
<para>
- Database schema wasn't changed between 2.4 and 2.6 releases, but still content that is kept in it
- changed slightly in few areas. You can easily update the data manually by using tools proper for your
- RDBMS. If you use <emphasis>MySQL</emphasis> you can use <emphasis>MySQL Query Browser</emphasis> that can
- be downloaded from <emphasis>MySQL</emphasis> website.
+ All procedures described in the following sections can performed using the AdminPortlet. Treat the directions as guidelines if you need to automate the migration of a large JBoss Portal deployment.
+ </para>
+ <para>
+ Database schema has not changed between the JBoss Portal 2.4 and 2.6 releases, but certain content that is kept in the databases has changed. Data can be updated manually by using the correct tools for your RDBMS. For example, if you are using a MySQL database, you can use the <ulink url="http://www.mysql.com/products/tools/query-browser/">MySQL Query Browser</ulink>.
</para>
- <note>
- Instructions below refer to standard JBoss Portal 2.4 deployment. If you named core portlets, portlet instances
- or portlet windows differently you will need to make proper modifications in those steps.
- </note>
+ <para>
+ The following instructions refer to a standard JBoss Portal 2.4 deployment. If you named core portlets, portlet instances, or portlet windows differently, you will need to make the appropriate modifications. The following is an example of using the MySQL Query Browser:
+ </para>
+ <para>
<mediaobject>
<imageobject>
<imagedata align="center" valign="middle" fileref="images/migration/querybrowser1.png"/>
</imageobject>
</mediaobject>
+ </para>
<sect3>
<title>Portlet names</title>
<para>Names of few core bundled portlets changed. To update them you need to:</para>
16 years, 4 months
- 1
- 0
JBoss Portal SVN: r9821 - in modules/portlet/trunk/test/src: main/java/org/jboss/portal/portlet/test/jsp/response and 4 other directories.
by portal-commits＠lists.jboss.org
Author: julien(a)jboss.com
Date: 2008-02-06 20:28:49 -0500 (Wed, 06 Feb 2008)
New Revision: 9821
Added:
modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/response/portlet/
modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/response/portlet/PortletChunk.java
modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/response/portlet/PortletMarkupChunk.java
modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/response/portlet/PortletTitleChunk.java
modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/response/portlet/PortletURLChunk.java
modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/taglib/MarkupTag.java
modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/taglib/TitleTag.java
Removed:
modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/response/PortletChunk.java
Modified:
modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/ControllerFilter.java
modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/PagePortletControllerContext.java
modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/taglib/PortletTag.java
modules/portlet/trunk/test/src/test/resources/simple-portal-war/WEB-INF/portal.tld
modules/portlet/trunk/test/src/test/resources/simple-portal-war/index.jsp
Log:
improve taglib with support of markup/title
Modified: modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/ControllerFilter.java
===================================================================
--- modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/ControllerFilter.java 2008-02-07 01:08:46 UTC (rev 9820)
+++ modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/ControllerFilter.java 2008-02-07 01:28:49 UTC (rev 9821)
@@ -25,7 +25,9 @@
import org.jboss.portal.portlet.test.jsp.response.Chunk;
import org.jboss.portal.portlet.test.jsp.response.BytesChunk;
import org.jboss.portal.portlet.test.jsp.response.CharsChunk;
-import org.jboss.portal.portlet.test.jsp.response.PortletChunk;
+import org.jboss.portal.portlet.test.jsp.response.portlet.PortletChunk;
+import org.jboss.portal.portlet.test.jsp.response.portlet.PortletMarkupChunk;
+import org.jboss.portal.portlet.test.jsp.response.portlet.PortletTitleChunk;
import org.jboss.portal.portlet.test.jsp.response.BufferingResponse;
import org.jboss.portal.portlet.test.jsp.response.ResponseBuffer;
import org.jboss.portal.portlet.PortletInvoker;
@@ -214,6 +216,8 @@
//
int count = 0;
+ PortletChunk portletChunk = null;
+ PortletInvocationResponse portletResponse = null;
for (Chunk chunk : page.getChunks())
{
if (chunk instanceof BytesChunk)
@@ -230,15 +234,29 @@
}
else if (chunk instanceof PortletChunk)
{
- PortletChunk portletChunk = (PortletChunk)chunk;
+ portletChunk = (PortletChunk)chunk;
String windowId = "" + count++;
-
- PortletInvocationResponse response = responses.get(windowId);
- if (response != null)
+ portletResponse = responses.get(windowId);
+ }
+ else if (chunk instanceof PortletTitleChunk)
+ {
+ if (portletResponse != null)
{
- if (response instanceof FragmentResponse)
+ if (portletResponse instanceof FragmentResponse)
{
- FragmentResponse fragment = (FragmentResponse)response;
+ FragmentResponse fragment = (FragmentResponse)portletResponse;
+ writer.write(fragment.getTitle());
+ writer.flush();
+ }
+ }
+ }
+ else if (chunk instanceof PortletMarkupChunk)
+ {
+ if (portletResponse != null)
+ {
+ if (portletResponse instanceof FragmentResponse)
+ {
+ FragmentResponse fragment = (FragmentResponse)portletResponse;
if (fragment.getType() != FragmentResponse.TYPE_EMPTY)
{
String frag;
@@ -258,7 +276,7 @@
}
else
{
- writer.write(response.getClass().getSimpleName() + "[" + portletChunk.getPortletName() + "," + portletChunk.getApplicationName() + "]");
+ writer.write(portletResponse.getClass().getSimpleName() + "[" + portletChunk.getPortletName() + "," + portletChunk.getApplicationName() + "]");
writer.flush();
}
}
Modified: modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/PagePortletControllerContext.java
===================================================================
--- modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/PagePortletControllerContext.java 2008-02-07 01:08:46 UTC (rev 9820)
+++ modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/PagePortletControllerContext.java 2008-02-07 01:28:49 UTC (rev 9821)
@@ -24,8 +24,7 @@
import org.jboss.portal.portlet.test.controller.AbstractPortletControllerContext;
import org.jboss.portal.portlet.test.jsp.response.Chunk;
-import org.jboss.portal.portlet.test.jsp.response.PortletChunk;
-import org.jboss.portal.portlet.test.jsp.response.BufferingResponse;
+import org.jboss.portal.portlet.test.jsp.response.portlet.PortletChunk;
import org.jboss.portal.portlet.test.jsp.response.ResponseBuffer;
import org.jboss.portal.portlet.Portlet;
import org.jboss.portal.portlet.PortletInvokerException;
Deleted: modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/response/PortletChunk.java
===================================================================
--- modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/response/PortletChunk.java 2008-02-07 01:08:46 UTC (rev 9820)
+++ modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/response/PortletChunk.java 2008-02-07 01:28:49 UTC (rev 9821)
@@ -1,53 +0,0 @@
-/******************************************************************************
- * JBoss, a division of Red Hat *
- * Copyright 2008, Red Hat Middleware, LLC, and individual *
- * contributors as indicated by the @authors tag. See the *
- * copyright.txt in the distribution for a full listing of *
- * individual contributors. *
- * *
- * This is free software; you can redistribute it and/or modify it *
- * under the terms of the GNU Lesser General Public License as *
- * published by the Free Software Foundation; either version 2.1 of *
- * the License, or (at your option) any later version. *
- * *
- * This software is distributed in the hope that it will be useful, *
- * but WITHOUT ANY WARRANTY; without even the implied warranty of *
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU *
- * Lesser General Public License for more details. *
- * *
- * You should have received a copy of the GNU Lesser General Public *
- * License along with this software; if not, write to the Free *
- * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA *
- * 02110-1301 USA, or see the FSF site: http://www.fsf.org. *
- ******************************************************************************/
-package org.jboss.portal.portlet.test.jsp.response;
-
-/**
- * @author <a href="mailto:julien@jboss.org">Julien Viet</a>
- * @version $Revision: 630 $
- */
-public class PortletChunk extends Chunk
-{
-
- /** . */
- private final String portletName;
-
- /** . */
- private final String applicationName;
-
- public PortletChunk(String portletName, String applicationName)
- {
- this.portletName = portletName;
- this.applicationName = applicationName;
- }
-
- public String getPortletName()
- {
- return portletName;
- }
-
- public String getApplicationName()
- {
- return applicationName;
- }
-}
Added: modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/response/portlet/PortletChunk.java
===================================================================
--- modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/response/portlet/PortletChunk.java (rev 0)
+++ modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/response/portlet/PortletChunk.java 2008-02-07 01:28:49 UTC (rev 9821)
@@ -0,0 +1,86 @@
+/******************************************************************************
+ * JBoss, a division of Red Hat *
+ * Copyright 2008, Red Hat Middleware, LLC, and individual *
+ * contributors as indicated by the @authors tag. See the *
+ * copyright.txt in the distribution for a full listing of *
+ * individual contributors. *
+ * *
+ * This is free software; you can redistribute it and/or modify it *
+ * under the terms of the GNU Lesser General Public License as *
+ * published by the Free Software Foundation; either version 2.1 of *
+ * the License, or (at your option) any later version. *
+ * *
+ * This software is distributed in the hope that it will be useful, *
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of *
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU *
+ * Lesser General Public License for more details. *
+ * *
+ * You should have received a copy of the GNU Lesser General Public *
+ * License along with this software; if not, write to the Free *
+ * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA *
+ * 02110-1301 USA, or see the FSF site: http://www.fsf.org. *
+ ******************************************************************************/
+package org.jboss.portal.portlet.test.jsp.response.portlet;
+
+import org.jboss.portal.Mode;
+import org.jboss.portal.WindowState;
+import org.jboss.portal.portlet.test.jsp.response.Chunk;
+
+import java.util.Set;
+
+/**
+ * @author <a href="mailto:julien@jboss.org">Julien Viet</a>
+ * @version $Revision: 630 $
+ */
+public class PortletChunk extends Chunk
+{
+
+ /** . */
+ private final String portletName;
+
+ /** . */
+ private final String applicationName;
+
+ /** . */
+ private final Mode initialMode;
+
+ /** . */
+ private final Set<Mode> supportedModes;
+
+ /** . */
+ private final Set<WindowState> supportedWindowStates;
+
+ public PortletChunk(String portletName, String applicationName, Mode initialMode, Set<Mode> supportedModes, Set<WindowState> supportedWindowStates)
+ {
+ this.portletName = portletName;
+ this.applicationName = applicationName;
+ this.initialMode = initialMode;
+ this.supportedModes = supportedModes;
+ this.supportedWindowStates = supportedWindowStates;
+ }
+
+ public String getPortletName()
+ {
+ return portletName;
+ }
+
+ public String getApplicationName()
+ {
+ return applicationName;
+ }
+
+ public Mode getInitialMode()
+ {
+ return initialMode;
+ }
+
+ public Set<Mode> getSupportedModes()
+ {
+ return supportedModes;
+ }
+
+ public Set<WindowState> getSupportedWindowStates()
+ {
+ return supportedWindowStates;
+ }
+}
Added: modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/response/portlet/PortletMarkupChunk.java
===================================================================
--- modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/response/portlet/PortletMarkupChunk.java (rev 0)
+++ modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/response/portlet/PortletMarkupChunk.java 2008-02-07 01:28:49 UTC (rev 9821)
@@ -0,0 +1,33 @@
+/******************************************************************************
+ * JBoss, a division of Red Hat *
+ * Copyright 2008, Red Hat Middleware, LLC, and individual *
+ * contributors as indicated by the @authors tag. See the *
+ * copyright.txt in the distribution for a full listing of *
+ * individual contributors. *
+ * *
+ * This is free software; you can redistribute it and/or modify it *
+ * under the terms of the GNU Lesser General Public License as *
+ * published by the Free Software Foundation; either version 2.1 of *
+ * the License, or (at your option) any later version. *
+ * *
+ * This software is distributed in the hope that it will be useful, *
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of *
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU *
+ * Lesser General Public License for more details. *
+ * *
+ * You should have received a copy of the GNU Lesser General Public *
+ * License along with this software; if not, write to the Free *
+ * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA *
+ * 02110-1301 USA, or see the FSF site: http://www.fsf.org. *
+ ******************************************************************************/
+package org.jboss.portal.portlet.test.jsp.response.portlet;
+
+import org.jboss.portal.portlet.test.jsp.response.Chunk;
+
+/**
+ * @author <a href="mailto:julien@jboss.org">Julien Viet</a>
+ * @version $Revision: 630 $
+ */
+public class PortletMarkupChunk extends Chunk
+{
+}
Added: modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/response/portlet/PortletTitleChunk.java
===================================================================
--- modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/response/portlet/PortletTitleChunk.java (rev 0)
+++ modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/response/portlet/PortletTitleChunk.java 2008-02-07 01:28:49 UTC (rev 9821)
@@ -0,0 +1,33 @@
+/******************************************************************************
+ * JBoss, a division of Red Hat *
+ * Copyright 2008, Red Hat Middleware, LLC, and individual *
+ * contributors as indicated by the @authors tag. See the *
+ * copyright.txt in the distribution for a full listing of *
+ * individual contributors. *
+ * *
+ * This is free software; you can redistribute it and/or modify it *
+ * under the terms of the GNU Lesser General Public License as *
+ * published by the Free Software Foundation; either version 2.1 of *
+ * the License, or (at your option) any later version. *
+ * *
+ * This software is distributed in the hope that it will be useful, *
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of *
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU *
+ * Lesser General Public License for more details. *
+ * *
+ * You should have received a copy of the GNU Lesser General Public *
+ * License along with this software; if not, write to the Free *
+ * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA *
+ * 02110-1301 USA, or see the FSF site: http://www.fsf.org. *
+ ******************************************************************************/
+package org.jboss.portal.portlet.test.jsp.response.portlet;
+
+import org.jboss.portal.portlet.test.jsp.response.Chunk;
+
+/**
+ * @author <a href="mailto:julien@jboss.org">Julien Viet</a>
+ * @version $Revision: 630 $
+ */
+public class PortletTitleChunk extends Chunk
+{
+}
Added: modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/response/portlet/PortletURLChunk.java
===================================================================
--- modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/response/portlet/PortletURLChunk.java (rev 0)
+++ modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/response/portlet/PortletURLChunk.java 2008-02-07 01:28:49 UTC (rev 9821)
@@ -0,0 +1,33 @@
+/******************************************************************************
+ * JBoss, a division of Red Hat *
+ * Copyright 2008, Red Hat Middleware, LLC, and individual *
+ * contributors as indicated by the @authors tag. See the *
+ * copyright.txt in the distribution for a full listing of *
+ * individual contributors. *
+ * *
+ * This is free software; you can redistribute it and/or modify it *
+ * under the terms of the GNU Lesser General Public License as *
+ * published by the Free Software Foundation; either version 2.1 of *
+ * the License, or (at your option) any later version. *
+ * *
+ * This software is distributed in the hope that it will be useful, *
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of *
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU *
+ * Lesser General Public License for more details. *
+ * *
+ * You should have received a copy of the GNU Lesser General Public *
+ * License along with this software; if not, write to the Free *
+ * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA *
+ * 02110-1301 USA, or see the FSF site: http://www.fsf.org. *
+ ******************************************************************************/
+package org.jboss.portal.portlet.test.jsp.response.portlet;
+
+import org.jboss.portal.portlet.test.jsp.response.Chunk;
+
+/**
+ * @author <a href="mailto:julien@jboss.org">Julien Viet</a>
+ * @version $Revision: 630 $
+ */
+public class PortletURLChunk extends Chunk
+{
+}
Added: modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/taglib/MarkupTag.java
===================================================================
--- modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/taglib/MarkupTag.java (rev 0)
+++ modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/taglib/MarkupTag.java 2008-02-07 01:28:49 UTC (rev 9821)
@@ -0,0 +1,47 @@
+/******************************************************************************
+ * JBoss, a division of Red Hat *
+ * Copyright 2008, Red Hat Middleware, LLC, and individual *
+ * contributors as indicated by the @authors tag. See the *
+ * copyright.txt in the distribution for a full listing of *
+ * individual contributors. *
+ * *
+ * This is free software; you can redistribute it and/or modify it *
+ * under the terms of the GNU Lesser General Public License as *
+ * published by the Free Software Foundation; either version 2.1 of *
+ * the License, or (at your option) any later version. *
+ * *
+ * This software is distributed in the hope that it will be useful, *
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of *
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU *
+ * Lesser General Public License for more details. *
+ * *
+ * You should have received a copy of the GNU Lesser General Public *
+ * License along with this software; if not, write to the Free *
+ * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA *
+ * 02110-1301 USA, or see the FSF site: http://www.fsf.org. *
+ ******************************************************************************/
+package org.jboss.portal.portlet.test.jsp.taglib;
+
+import org.jboss.portal.portlet.test.jsp.response.BufferingResponse;
+import org.jboss.portal.portlet.test.jsp.response.portlet.PortletTitleChunk;
+import org.jboss.portal.portlet.test.jsp.response.portlet.PortletMarkupChunk;
+
+import javax.servlet.jsp.tagext.SimpleTagSupport;
+import javax.servlet.jsp.JspException;
+import javax.servlet.jsp.PageContext;
+import java.io.IOException;
+
+/**
+ * @author <a href="mailto:julien@jboss.org">Julien Viet</a>
+ * @version $Revision: 630 $
+ */
+public class MarkupTag extends SimpleTagSupport
+{
+ public void doTag() throws JspException, IOException
+ {
+ PageContext pageCtx = (PageContext)getJspContext();
+ pageCtx.getOut().flush();
+ BufferingResponse response = (BufferingResponse)pageCtx.getResponse();
+ response.addChunk(new PortletMarkupChunk());
+ }
+}
Modified: modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/taglib/PortletTag.java
===================================================================
--- modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/taglib/PortletTag.java 2008-02-07 01:08:46 UTC (rev 9820)
+++ modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/taglib/PortletTag.java 2008-02-07 01:28:49 UTC (rev 9821)
@@ -23,26 +23,48 @@
package org.jboss.portal.portlet.test.jsp.taglib;
import org.jboss.portal.portlet.test.jsp.response.BufferingResponse;
-import org.jboss.portal.portlet.test.jsp.response.PortletChunk;
+import org.jboss.portal.portlet.test.jsp.response.portlet.PortletChunk;
+import org.jboss.portal.Mode;
+import org.jboss.portal.WindowState;
+import org.jboss.portal.common.util.Tools;
import javax.servlet.jsp.tagext.SimpleTagSupport;
+import javax.servlet.jsp.tagext.BodyTagSupport;
import javax.servlet.jsp.JspException;
import javax.servlet.jsp.PageContext;
import java.io.IOException;
+import java.util.LinkedHashSet;
+import java.util.Set;
+import java.util.Collections;
/**
* @author <a href="mailto:julien@jboss.org">Julien Viet</a>
* @version $Revision: 630 $
*/
-public class PortletTag extends SimpleTagSupport
+public class PortletTag extends BodyTagSupport
{
/** . */
+ private static final Set<Mode> DEFAULT_MODES = Collections.unmodifiableSet(Tools.toSet(Mode.VIEW, Mode.EDIT, Mode.HELP));
+
+ /** . */
+ private static final Set<WindowState> DEFAULT_WINDOW_STATES = Collections.unmodifiableSet(Tools.toSet(WindowState.NORMAL, WindowState.MAXIMIZED, WindowState.MINIMIZED));
+
+ /** . */
private String name;
/** . */
private String applicationName;
+ /** . */
+ private String supportedWindowStateValues;
+
+ /** . */
+ private String supportedModeValues;
+
+ /** . */
+ private String initialModeValue;
+
public String getName()
{
return name;
@@ -63,11 +85,99 @@
this.applicationName = applicationName;
}
- public void doTag() throws JspException, IOException
+ public String getSupportedWindowStates()
{
- PageContext pageCtx = (PageContext)getJspContext();
- pageCtx.getOut().flush();
- BufferingResponse response = (BufferingResponse)pageCtx.getResponse();
- response.addChunk(new PortletChunk(name, applicationName));
+ return supportedWindowStateValues;
}
+
+ public void setSupportedWindowStates(String supportedWindowStates)
+ {
+ this.supportedWindowStateValues = supportedWindowStates;
+ }
+
+ public String getSupportedModes()
+ {
+ return supportedModeValues;
+ }
+
+ public void setSupportedModes(String supportedModes)
+ {
+ this.supportedModeValues = supportedModes;
+ }
+
+ public String getInitialMode()
+ {
+ return initialModeValue;
+ }
+
+ public void setInitialMode(String initialMode)
+ {
+ this.initialModeValue = initialMode;
+ }
+
+ public int doStartTag() throws JspException
+ {
+ Set<Mode> supportedModes = new LinkedHashSet<Mode>();
+ if (supportedModeValues != null)
+ {
+ for (String supportedModeValue : supportedModeValues.split(","))
+ {
+ Mode mode = Mode.create(supportedModeValue.trim());
+ supportedModes.add(mode);
+ }
+ }
+ else
+ {
+ supportedModes = DEFAULT_MODES;
+ }
+
+ //
+ Set<WindowState> supportedWindowStates = new LinkedHashSet<WindowState>();
+ if (supportedWindowStateValues != null)
+ {
+ for (String supportedWindowStateValue : supportedWindowStateValues.split(","))
+ {
+ WindowState windowState = WindowState.create(supportedWindowStateValue.trim());
+ supportedWindowStates.add(windowState);
+ }
+ }
+ else
+ {
+ supportedWindowStates = DEFAULT_WINDOW_STATES;
+ }
+
+ //
+ Mode initialMode = Mode.VIEW;
+ if (initialModeValue != null)
+ {
+ initialMode = Mode.create(initialModeValue.trim());
+ }
+
+ //
+ try
+ {
+ pageContext.getOut().flush();
+ }
+ catch (IOException e)
+ {
+ throw new JspException(e);
+ }
+
+ //
+ BufferingResponse response = (BufferingResponse)pageContext.getResponse();
+ response.addChunk(new PortletChunk(
+ name,
+ applicationName,
+ initialMode,
+ supportedModes,
+ supportedWindowStates));
+
+ //
+ return EVAL_BODY_INCLUDE;
+ }
+
+ public int doEndTag() throws JspException
+ {
+ return EVAL_PAGE;
+ }
}
Added: modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/taglib/TitleTag.java
===================================================================
--- modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/taglib/TitleTag.java (rev 0)
+++ modules/portlet/trunk/test/src/main/java/org/jboss/portal/portlet/test/jsp/taglib/TitleTag.java 2008-02-07 01:28:49 UTC (rev 9821)
@@ -0,0 +1,46 @@
+/******************************************************************************
+ * JBoss, a division of Red Hat *
+ * Copyright 2008, Red Hat Middleware, LLC, and individual *
+ * contributors as indicated by the @authors tag. See the *
+ * copyright.txt in the distribution for a full listing of *
+ * individual contributors. *
+ * *
+ * This is free software; you can redistribute it and/or modify it *
+ * under the terms of the GNU Lesser General Public License as *
+ * published by the Free Software Foundation; either version 2.1 of *
+ * the License, or (at your option) any later version. *
+ * *
+ * This software is distributed in the hope that it will be useful, *
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of *
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU *
+ * Lesser General Public License for more details. *
+ * *
+ * You should have received a copy of the GNU Lesser General Public *
+ * License along with this software; if not, write to the Free *
+ * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA *
+ * 02110-1301 USA, or see the FSF site: http://www.fsf.org. *
+ ******************************************************************************/
+package org.jboss.portal.portlet.test.jsp.taglib;
+
+import org.jboss.portal.portlet.test.jsp.response.BufferingResponse;
+import org.jboss.portal.portlet.test.jsp.response.portlet.PortletTitleChunk;
+
+import javax.servlet.jsp.tagext.SimpleTagSupport;
+import javax.servlet.jsp.JspException;
+import javax.servlet.jsp.PageContext;
+import java.io.IOException;
+
+/**
+ * @author <a href="mailto:julien@jboss.org">Julien Viet</a>
+ * @version $Revision: 630 $
+ */
+public class TitleTag extends SimpleTagSupport
+{
+ public void doTag() throws JspException, IOException
+ {
+ PageContext pageCtx = (PageContext)getJspContext();
+ pageCtx.getOut().flush();
+ BufferingResponse response = (BufferingResponse)pageCtx.getResponse();
+ response.addChunk(new PortletTitleChunk());
+ }
+}
Modified: modules/portlet/trunk/test/src/test/resources/simple-portal-war/WEB-INF/portal.tld
===================================================================
--- modules/portlet/trunk/test/src/test/resources/simple-portal-war/WEB-INF/portal.tld 2008-02-07 01:08:46 UTC (rev 9820)
+++ modules/portlet/trunk/test/src/test/resources/simple-portal-war/WEB-INF/portal.tld 2008-02-07 01:28:49 UTC (rev 9821)
@@ -17,7 +17,7 @@
<tag>
<name>portlet</name>
<tag-class>org.jboss.portal.portlet.test.jsp.taglib.PortletTag</tag-class>
- <body-content>empty</body-content>
+ <body-content>JSP</body-content>
<attribute>
<name>name</name>
<required>true</required>
@@ -28,6 +28,30 @@
<required>true</required>
<type>java.lang.String</type>
</attribute>
+ <attribute>
+ <name>initialMode</name>
+ <type>java.lang.String</type>
+ </attribute>
+ <attribute>
+ <name>supportedModes</name>
+ <type>java.lang.String</type>
+ </attribute>
+ <attribute>
+ <name>supportedWindowStates</name>
+ <type>java.lang.String</type>
+ </attribute>
</tag>
+ <tag>
+ <name>markup</name>
+ <tag-class>org.jboss.portal.portlet.test.jsp.taglib.MarkupTag</tag-class>
+ <body-content>empty</body-content>
+ </tag>
+
+ <tag>
+ <name>title</name>
+ <tag-class>org.jboss.portal.portlet.test.jsp.taglib.TitleTag</tag-class>
+ <body-content>empty</body-content>
+ </tag>
+
</taglib>
Modified: modules/portlet/trunk/test/src/test/resources/simple-portal-war/index.jsp
===================================================================
--- modules/portlet/trunk/test/src/test/resources/simple-portal-war/index.jsp 2008-02-07 01:08:46 UTC (rev 9820)
+++ modules/portlet/trunk/test/src/test/resources/simple-portal-war/index.jsp 2008-02-07 01:28:49 UTC (rev 9821)
@@ -4,19 +4,37 @@
<html>
<body>
<portal:page>
- ONE
+****************************************************<br/>
<portal:portlet
name="GoogleWeather"
- applicationName="google-weather-portlet"/>
- TWO
+ applicationName="google-weather-portlet">
+-----------------------------------<br/>
+<portal:title/><br/>
+-----------------------------------<br/>
+ <portal:markup/>
+-----------------------------------<br/>
+ </portal:portlet>
+****************************************************<br/>
<portal:portlet
name="GoogleMap"
- applicationName="google-map-portlet"/>
- THREE
+ applicationName="google-map-portlet">
+-----------------------------------<br/>
+<portal:title/><br/>
+-----------------------------------<br/>
+ <portal:markup/>
+-----------------------------------<br/>
+ </portal:portlet>
+****************************************************<br/>
<portal:portlet
name="RemoteControl"
- applicationName="remotecontrol-portlet"/>
- FOUR
+ applicationName="remotecontrol-portlet">
+-----------------------------------<br/>
+<portal:title/><br/>
+-----------------------------------<br/>
+ <portal:markup/>
+-----------------------------------<br/>
+ </portal:portlet>
+****************************************************<br/>
</portal:page>
</body>
</html>
16 years, 4 months
- 1
- 0
JBoss Portal SVN: r9820 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-06 20:08:46 -0500 (Wed, 06 Feb 2008)
New Revision: 9820
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml
Log:
revising 4.1. Manual Upgrade and 4.1.1. Themes
minor corrections to 3.6. Disabling Dynamic
Proxy Un-wrapping
Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml
===================================================================
--- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml 2008-02-07 00:07:31 UTC (rev 9819)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml 2008-02-07 01:08:46 UTC (rev 9820)
@@ -262,10 +262,10 @@
</sect1>
<sect1>
<title>Disabling Dynamic Proxy Un-wrapping</title>
- <para>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 JMX based, tt 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 appears due to the fact that the implementation of the JMX API classes, <emphasis>javax.management.*</emphasis>, provided by the Java Platform, performs synchronization. This does not occur under JDK 1.4 since those classes are implemented by JBoss MX.
+ <para>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 JMX 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 JDK 1.4, since those classes are implemented by JBoss MX.
</para>
<para>
- 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 real plain old java object (POJO) services. This allows the removal of the bottleneck with 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 systems, change into the <filename>$JBOSS_HOME/bin/</filename> directory and run the following command:
+ 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 systems, change into the <filename>$JBOSS_HOME/bin/</filename> directory and run the following command:
</para>
<para>
<screen>
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-07 00:07:31 UTC (rev 9819)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml 2008-02-07 01:08:46 UTC (rev 9820)
@@ -11,52 +11,63 @@
<email>boleslaw dot dawidowicz at redhat dot com</email>
</author>
</chapterinfo>
- <title>Upgrading 2.4 - 2.6</title>
+ <title>Upgrading JBoss Portal 2.4 to 2.6</title>
+ <para>
<warning>
- Before performing any instructions or operations mentioned below remember to backup your database content and
- the whole application server directory!
+ <para>
+ Before performing any instructions or operations in this chapter, back up your database content and
+ the entire JBoss EAP or JBoss AS directory!
+ </para>
</warning>
+ </para>
<sect1 id="manual_migration">
- <title>Manual upgrade</title>
+ <title>Manual Upgrade</title>
<para>
- Although database schema remains the same in JBoss Portal 2.6 there are several differences that prevent from simple deployment
- of newest portal version using JBoss Portal 2.4 database. In this chapter we will list major ones and give
- instructions on how to manually update proper data.
+ Although the database schema remains the same in JBoss Portal 2.6, there are several differences that prevent simply deploying the latest version of JBoss Portal, when using a database created for JBoss Portal 2.4. This chapter describes updating a JBoss Portal 2.4 MySQL database for use with JBoss Portal 2.6.
</para>
<para>
- Upgrading procedure can be quite straightforward:
- <itemizedlist>
+ The upgrade procedure can be straightforward:
+ </para>
+ <para>
+ <orderedlist>
<listitem>
- Remove <emphasis role="bold">$JBOSS_HOME/server/default/deploy/jboss-portal.sar</emphasis> file.
+ <para>
+ If you are using the JBoss Portal binary, remove the <filename>$JBOSS_HOME/server/default/deploy/jboss-portal.sar/</filename> directory. If JBoss Portal was built from source, remove the <filename>$JBOSS_HOME/server/default/deploy/jboss-portal.sar</filename> file.
+ </para>
</listitem>
<!--<listitem>
Remove <emphasis role="bold">$JBOSS_HOME/server/default/data</emphasis> directory.
</listitem>-->
<listitem>
- Update data in portal database like described in following sections of this chapter
+ <para>
+ Update the data in the JBoss Portal database, as described in <xref linkend="upgrade_portal_database"/>.
+ </para>
</listitem>
<listitem>
- Deploy JBoss Portal 2.6
+ <para>
+ Deploy JBoss Portal 2.6.
+ </para>
</listitem>
- </itemizedlist>
+ </orderedlist>
</para>
<sect2>
- <title>Theme</title>
+ <title>Themes</title>
+ <para>
+ Themes in JBoss Portal 2.6 have changed since the Portal pages now contain additional areas, such as the <guiicon>Login</guiicon>, <guiicon>Admin</guiicon>, and <guiicon>Dashboard</guiicon> links, on the top right-hand corner:
+ </para>
+ <para>
<mediaobject>
<imageobject>
<imagedata align="center" valign="middle" fileref="images/migration/theme.png"/>
</imageobject>
</mediaobject>
+ </para>
<para>
- Themes in 2.6 version changed as now they
- contain additional areas - the best example is upper right corner where links like "Login", "Admin", "My Dashboard"
- are visable. If you use default theme like "renaissance" that is present in 2.6, you shouldn't need to do anything. To update your custom themes please
- refer to those bundled with portal as an example.
- </para>
- <note>If you stay with old theme files you may find JBP 2.6 unusable to the point that you may not even be able to log in</note>
+ If you use a default theme that exists in JBoss Portal 2.6, such as renaissance, no configuration should be necessary. Using old themes from JBoss Portal 2.4 may make JBoss Portal 2.6 unusable, for example, not being able to log in. To update custom themes, please refer to those bundled with JBoss Portal as an example.
+ </para>
</sect2>
- <sect2>
- <title>Database</title>
+ <sect2 id="upgrade_portal_database">
+ <title>Updating the Database</title>
<note>All things described in this section can be done using AdminPortlet. Treat this directions more as guideline
if you need to automate migration for big portal deployment.</note>
<para>
16 years, 4 months
- 1
- 0