JBoss Portal SVN: r10771 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-05-10 02:12:10 -0400 (Sat, 10 May 2008)
New Revision: 10771
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/urls.xml
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml
Log:
Chapter 7. Portal URLs
- minor revisions
Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/urls.xml
===================================================================
--- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/urls.xml 2008-05-10 05:55:48 UTC (rev 10770)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/urls.xml 2008-05-10 06:12:10 UTC (rev 10771)
@@ -33,13 +33,13 @@
</mediaobject>
</para>
<para>
- Before reading this chapter, be familiar with how to define a page and a portal. Refer to <xref linkend="desc_example_page" /> for details.
+ Before reading the following sections, be familiar with how to define a page and a portal. Refer to <xref linkend="desc_example_page" /> for details.
</para>
</sect1>
<sect1>
<title>Accessing a Portal</title>
<para>
- The <computeroutput>default</computeroutput> portal is special, in that it is the one used when no portal is specified. The following examples detail how selection is done:
+ The <computeroutput>default</computeroutput> portal is used when no portal is specified. The following examples detail how the selection is done:
</para>
<para>
<itemizedlist>
@@ -68,7 +68,7 @@
<sect1>
<title>Accessing CMS Content</title>
<para>
- The <emphasis>CMSPortlet</emphasis> delivers content transparently, without modifying the displayed URL. It is desirable to display binary content, such as GIF, JPEG, PDF, ZIP, and so, outside of the confines of a portal. For example, <computeroutput>/content/default/images/jboss_logo.gif</computeroutput> displays the <computeroutput>jboss_logo.gif</computeroutput> file outside of the portal.
+ The <emphasis>CMSPortlet</emphasis> delivers content transparently, without modifying the displayed URL. It is desirable to display binary content, such as GIF, JPEG, PDF, ZIP, and so on, outside of the confines of the portal. For example, <computeroutput>/content/default/images/jboss_logo.gif</computeroutput> displays the <computeroutput>jboss_logo.gif</computeroutput> file outside of the portal.
</para>
<para>
To display content outside of the portal, the portal interprets any path beginning with <computeroutput>/content</computeroutput> as a request for CMS content. As long as the <computeroutput><mime-type></computeroutput> is not <computeroutput>text/html</computeroutput>, or <computeroutput>text/text</computeroutput>, and the path to the content begins with <computeroutput>/content</computeroutput>, the content will be rendered independently outside of the portal.
Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml
===================================================================
--- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml 2008-05-10 05:55:48 UTC (rev 10770)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml 2008-05-10 06:12:10 UTC (rev 10771)
@@ -2053,7 +2053,7 @@
<note>
<title>Portal Instance <computerouput>default</computerouput> Page</title>
<para>
- To be accessible via a Web browser, you must define a page named <computeroutput>default</computeroutput> for any portal instance.
+ For a portal instance to be accessible via a Web browser, you must define a page named <computeroutput>default</computeroutput>.
</para>
</note>
</para>
16 years, 1 month
JBoss Portal SVN: r10770 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-05-10 01:55:48 -0400 (Sat, 10 May 2008)
New Revision: 10770
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/urls.xml
Log:
7.4. Accessing CMS Content
- revising content
Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/urls.xml
===================================================================
--- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/urls.xml 2008-05-10 04:22:52 UTC (rev 10769)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/urls.xml 2008-05-10 05:55:48 UTC (rev 10770)
@@ -67,19 +67,12 @@
</sect1>
<sect1>
<title>Accessing CMS Content</title>
- <para>The CMSPortlet delivers content transparently, without modifying the url displayed.
- However, if you wish to deliver binary content (gif, jpeg, pdf, zip, etc...), it is
- desirable to display this content outside of the confines of the portal.
- <itemizedlist>
- <listitem>
- <literal>"/content/default/images/jboss_logo.gif"</literal> will display the
- <literal>jboss_logo.gif</literal> outside of the portal. This is accomplished as
- the portal interprets any path beginning with <literal>/content</literal> as a
- request for CMS content. As long as the mime-type is not <literal>text/html</literal>
- or <literal>text/text</literal>, it will be rendered independently of the portal.
- </listitem>
- </itemizedlist>
- </para>
+ <para>
+ The <emphasis>CMSPortlet</emphasis> delivers content transparently, without modifying the displayed URL. It is desirable to display binary content, such as GIF, JPEG, PDF, ZIP, and so, outside of the confines of a portal. For example, <computeroutput>/content/default/images/jboss_logo.gif</computeroutput> displays the <computeroutput>jboss_logo.gif</computeroutput> file outside of the portal.
+ </para>
+ <para>
+ To display content outside of the portal, the portal interprets any path beginning with <computeroutput>/content</computeroutput> as a request for CMS content. As long as the <computeroutput><mime-type></computeroutput> is not <computeroutput>text/html</computeroutput>, or <computeroutput>text/text</computeroutput>, and the path to the content begins with <computeroutput>/content</computeroutput>, the content will be rendered independently outside of the portal.
+ </para>
</sect1>
<!--
<sect1>
16 years, 1 month
JBoss Portal SVN: r10769 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-05-10 00:22:52 -0400 (Sat, 10 May 2008)
New Revision: 10769
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/urls.xml
Log:
7.3. Accessing a Page
- minor revisions
Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/urls.xml
===================================================================
--- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/urls.xml 2008-05-10 04:06:02 UTC (rev 10768)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/urls.xml 2008-05-10 04:22:52 UTC (rev 10769)
@@ -20,7 +20,7 @@
<sect1>
<title>Introduction to Portals</title>
<para>
- Portal URLs are often very complicated; however, it is possible to setup entry points in portals that follow simple pattern.
+ Portal URLs are often very complicated; however, it is possible to setup entry points in portals that follow simple patterns.
</para>
<para>
Each portal container can contain multiple portals. Within a given portal, windows are organized into pages, with a page being a collection of windows associated to a name:
@@ -57,16 +57,13 @@
</para>
</sect1>
<sect1>
- <title>Accessing a page</title>
- <para>It is possible to have multiple pages per portal. As for portal there is a default
- page for a given portal. Once the portal has been selected, then a page must be used and
- all the windows present in that page will be rendered. The page selection mechanism is
- the following.
- <itemizedlist>
- <listitem>"/portal/default/pageName" will render the <literal>pageName</literal>
- page.</listitem>
- </itemizedlist>
- </para>
+ <title>Accessing a Page</title>
+ <para>
+ Each portal can have multiple pages, and each portal has a default page. When a portal is selected, a page must be used, and all windows in that page are rendered. The page selection mechanism is as follows:
+ </para>
+ <para>
+ <computeroutput>/portal/default/<replaceable>page-name</replaceable></computeroutput> renders the <replaceable>page-name</replaceable> page.
+ </para>
</sect1>
<sect1>
<title>Accessing CMS Content</title>
16 years, 1 month
JBoss Portal SVN: r10768 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-05-10 00:06:02 -0400 (Sat, 10 May 2008)
New Revision: 10768
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/urls.xml
Log:
Chapter 7. Portal URLs
- starting to revise
Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/urls.xml
===================================================================
--- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/urls.xml 2008-05-10 00:51:12 UTC (rev 10767)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/urls.xml 2008-05-10 04:06:02 UTC (rev 10768)
@@ -16,29 +16,45 @@
<email>roy(a)jboss.org</email>
</author>
</chapterinfo>
- <title>Portal urls</title>
+ <title>Portal URLs</title>
<sect1>
- <title>Introduction</title>
- <para>Most of the time portals use very complicated urls, however it is possible to setup
- entry points in the portal that follow simple patterns.</para>
- <para>Each portal container can contain multiple portals and within a given portal, windows
- are organized in pages, a page simply being a collection of windows associated to a
- name.</para>
- <para>Before reading this chapter you must know how to define a page and a portal, you can
- refer to the chapter about XML descriptors to have a better understanding of those
- notions.</para>
+ <title>Introduction to Portals</title>
+ <para>
+ Portal URLs are often very complicated; however, it is possible to setup entry points in portals that follow simple pattern.
+ </para>
+ <para>
+ Each portal container can contain multiple portals. Within a given portal, windows are organized into pages, with a page being a collection of windows associated to a name:
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata align="center" fileref="images/tutorials/SpecPortalDef.png" valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ <para>
+ Before reading this chapter, be familiar with how to define a page and a portal. Refer to <xref linkend="desc_example_page" /> for details.
+ </para>
</sect1>
<sect1>
- <title>Accessing a portal</title>
- <para>Each portal container can contains multiple portals, also there is one special portal
- which is the default portal, i.e the one used when no portal is specified in particular.
- <itemizedlist> The following examples show you how the selection is done.
- <listitem>"/portal", will point to the default page of the default portal.</listitem>
- <listitem>"/portal/portalname/" will point to the default page of the portal
- <literal>portalname</literal>
- </listitem>
- </itemizedlist>
- </para>
+ <title>Accessing a Portal</title>
+ <para>
+ The <computeroutput>default</computeroutput> portal is special, in that it is the one used when no portal is specified. The following examples detail how selection is done:
+ </para>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <computeroutput>/portal/</computeroutput> points to the default page of the default portal.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <computeroutput>/portal/<replaceable>portal-name</replaceable>/</computeroutput> points to the default page of the <replaceable>portal-name</replaceable> portal.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
</sect1>
<sect1>
<title>Accessing a page</title>
16 years, 1 month
JBoss Portal SVN: r10767 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-05-09 20:51:12 -0400 (Fri, 09 May 2008)
New Revision: 10767
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml
Log:
minor markup correction (<filename>)
Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml
===================================================================
--- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml 2008-05-10 00:34:51 UTC (rev 10766)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml 2008-05-10 00:51:12 UTC (rev 10767)
@@ -1957,7 +1957,7 @@
</orderedlist>
</para>
<para>
- The HelloWorldPortal portlet is hot-deployable, so the JBoss EAP or JBoss AS server does not have to be restarted after deploying the HelloWorldPortal portlet. The following is an example of the HelloWorldPortal/WEB-INF/helloworld-object.xml descriptor:
+ The HelloWorldPortal portlet is hot-deployable, so the JBoss EAP or JBoss AS server does not have to be restarted after deploying the HelloWorldPortal portlet. The following is an example of the <filename>HelloWorldPortal/WEB-INF/helloworld-object.xml</filename> descriptor:
</para>
<para>
<screen><![CDATA[
16 years, 1 month
JBoss Portal SVN: r10766 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-05-09 20:34:51 -0400 (Fri, 09 May 2008)
New Revision: 10766
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml
Log:
6.4.2. Defining a new Portal Instance
- minor revisions to my previous revisions
Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml
===================================================================
--- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml 2008-05-10 00:06:15 UTC (rev 10765)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml 2008-05-10 00:34:51 UTC (rev 10766)
@@ -1703,7 +1703,7 @@
</listitem>
<listitem>
<para>
- To expand the WAR file, which will give you access to the XML descriptors, change into the <filename>HelloWorldPortalPage/</filename> directory, and run the <command>ant explode</command> command.
+ To expand the WAR file, which gives you access to the XML descriptors, change into the <filename>HelloWorldPortalPage/</filename> directory, and run the <command>ant explode</command> command.
</para>
</listitem>
<listitem>
@@ -1930,7 +1930,7 @@
<sect2 id="desc_example_portal">
<title>Defining a new Portal Instance</title>
<para>
- The sample application descriptor in this section creates a new portal instance, <computeroutput>HelloPortal</computeroutput>, that contains two pages. To illustrate this example, download the <ulink url="http://anonsvn.jboss.org/repos/portletswap/portlets/2_4/bundles/HelloWorl...">HelloPortal</ulink> portlet. To use the HelloWorldPortal portlet:
+ The sample application descriptor in this section creates a new portal instance, <computeroutput>HelloPortal</computeroutput>, that contains two pages. To illustrate this example, download the <ulink url="http://anonsvn.jboss.org/repos/portletswap/portlets/2_4/bundles/HelloWorl...">HelloWorldPortal</ulink> portlet. To use the HelloWorldPortal portlet:
</para>
<para>
<orderedlist>
@@ -1946,12 +1946,12 @@
</listitem>
<listitem>
<para>
- To expand the WAR file, which will give you access to the XML descriptors, change into the <filename>HelloWorldPortal/</filename> directory, and run the <command>ant explode</command> command.
+ To expand the WAR file, which gives you access to the XML descriptors, change into the <filename>HelloWorldPortal/</filename> directory, and run the <command>ant explode</command> command.
</para>
</listitem>
<listitem>
<para>
- If you did not expand the <filename>helloworldportal.war</filename> file, copy the <filename>helloworldportal.war</filename> file into the correct JBoss AS or JBoss EAP <filename>deploy/</filename> directory. If you expanded the <filename>helloworldportal.war</filename> file, copy the <filename>HelloWorldPortal/output/lib/exploded/helloworldportal.war</filename> directory into the correct JBoss AS or JBoss EAP <filename>deploy/</filename> directory. For example, if you are using the <computeroutput>default</computeroutput> JBoss AS profile, copy the WAR file or the expanded directory into the <filename>$JBOSS_HOME/server/default/deploy/</filename> directory.
+ If you did not expand the <filename>helloworldportal.war</filename> file, copy the <filename>helloworldportal.war</filename> file into the correct JBoss AS or JBoss EAP <filename>deploy/</filename> directory. If you expanded the <filename>helloworldportal.war</filename> file, copy the <filename>HelloWorldPortal/output/lib/exploded/helloworldportal.war/</filename> directory into the correct JBoss AS or JBoss EAP <filename>deploy/</filename> directory. For example, if you are using the <computeroutput>default</computeroutput> JBoss AS profile, copy the WAR file or the expanded directory into the <filename>$JBOSS_HOME/server/default/deploy/</filename> directory.
</para>
</listitem>
</orderedlist>
@@ -2047,13 +2047,13 @@
</screen>
</para>
<para>
- When deployed, this example registers a new portal instance, <computeroutput>HelloPortal</computeroutput>, that contains two pages. To view the default page in the <computeroutput>HelloPortal</computeroutput> instance, navigate to <ulink url="http://localhost:8080/portal/portal/HelloPortal" />, and to <ulink url="http://localhost:8080/portal/portal/HelloPortal/foobar" /> for the second page.
+ When deployed, this example registers a new portal instance, <computeroutput>HelloPortal</computeroutput>, that contains two pages. To view the default page in the <computeroutput>HelloPortal</computeroutput> instance, navigate to <ulink url="http://localhost:8080/portal/portal/HelloPortal" />, and for the second page, <ulink url="http://localhost:8080/portal/portal/HelloPortal/foobar" />.
</para>
<para>
<note>
<title>Portal Instance <computerouput>default</computerouput> Page</title>
<para>
- To be accessible via a Web browser, you must define a page named <computerouput>default</computerouput> for any portal instance.
+ To be accessible via a Web browser, you must define a page named <computeroutput>default</computeroutput> for any portal instance.
</para>
</note>
</para>
16 years, 1 month
JBoss Portal SVN: r10765 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-05-09 20:06:15 -0400 (Fri, 09 May 2008)
New Revision: 10765
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml
Log:
6.4.2. Defining a new Portal Instance
- revising
- making consistent with 6.4.1. Defining a new Portal Page
Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml
===================================================================
--- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml 2008-05-09 13:37:49 UTC (rev 10764)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml 2008-05-10 00:06:15 UTC (rev 10765)
@@ -1670,7 +1670,7 @@
<sect2>
<title>Log in to Dashboard</title>
<para>
- By default, when a user logs in, they are forwarded to the default page of the default portal. In order to
+ By default, when a user logs in they are forwarded to the default page of the default portal. In order to
forward a user to their Dashboard, set the <computeroutput>core.login.namespace</computeroutput> value to <computeroutput>dashboard</computeroutput> in the <filename>jboss-portal.sar/conf/config.xml</filename> file:
</para>
<para>
@@ -1714,7 +1714,7 @@
</orderedlist>
</para>
<para>
- The HelloWorldPortalPage portlet is hot-deployable, so the JBoss EAP or JBoss AS server does not have to be restarted after deploying the HelloWorldPortalPage portlet. The following is an example of the <filename>helloworldportalpage.war/WEB-INF/helloworld-object.xml</filename> descriptor:
+ The HelloWorldPortalPage portlet is hot-deployable, so the JBoss EAP or JBoss AS server does not have to be restarted after deploying the HelloWorldPortalPage portlet. The following is an example of the <filename>HelloWorldPortalPage/WEB-INF/helloworld-object.xml</filename> descriptor:
</para>
<para>
<screen><![CDATA[
@@ -1929,20 +1929,38 @@
</sect2>
<sect2 id="desc_example_portal">
<title>Defining a new Portal Instance</title>
- <para>To illustrate our example, we have made available a portlet that you can download
- here:
- <ulink
- url="http://anonsvn.jboss.org/repos/portletswap/portlets/2_4/bundles/HelloWorl..."
- >HelloPortal</ulink>
- .
- </para>
- <para>For our example we make available
- <emphasis>helloworld-object.xml</emphasis>
- located
- under
- <emphasis>helloworldportal.war/WEB-INF/</emphasis>
- , and it looks like this:
- <programlisting><![CDATA[
+ <para>
+ The sample application descriptor in this section creates a new portal instance, <computeroutput>HelloPortal</computeroutput>, that contains two pages. To illustrate this example, download the <ulink url="http://anonsvn.jboss.org/repos/portletswap/portlets/2_4/bundles/HelloWorl...">HelloPortal</ulink> portlet. To use the HelloWorldPortal portlet:
+ </para>
+ <para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Download the <ulink url="http://anonsvn.jboss.org/repos/portletswap/portlets/2_4/bundles/HelloWorl...">HelloWorldPortal</ulink> portlet.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Unzip the <filename>HelloWorldPortal</filename> ZIP file.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To expand the WAR file, which will give you access to the XML descriptors, change into the <filename>HelloWorldPortal/</filename> directory, and run the <command>ant explode</command> command.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If you did not expand the <filename>helloworldportal.war</filename> file, copy the <filename>helloworldportal.war</filename> file into the correct JBoss AS or JBoss EAP <filename>deploy/</filename> directory. If you expanded the <filename>helloworldportal.war</filename> file, copy the <filename>HelloWorldPortal/output/lib/exploded/helloworldportal.war</filename> directory into the correct JBoss AS or JBoss EAP <filename>deploy/</filename> directory. For example, if you are using the <computeroutput>default</computeroutput> JBoss AS profile, copy the WAR file or the expanded directory into the <filename>$JBOSS_HOME/server/default/deploy/</filename> directory.
+ </para>
+ </listitem>
+ </orderedlist>
+ </para>
+ <para>
+ The HelloWorldPortal portlet is hot-deployable, so the JBoss EAP or JBoss AS server does not have to be restarted after deploying the HelloWorldPortal portlet. The following is an example of the HelloWorldPortal/WEB-INF/helloworld-object.xml descriptor:
+ </para>
+ <para>
+<screen><![CDATA[
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE deployments PUBLIC
"-//JBoss Portal//DTD Portal Object 2.6//EN"
@@ -2026,25 +2044,19 @@
</page>
</deployment>
</deployments>]]>
- </programlisting>
+</screen>
</para>
- <para>This example, when deployed, will register a new portal instance named
- <literal>HelloPortal</literal>
- with two pages in it. The portal instance can be
- accessed by navigating to:
- <ulink url="http://localhost:8080/portal/portal/HelloPortal"
- >http://localhost:8080/portal/portal/HelloPortal</ulink>
- for the default page, and
- <ulink url="http://localhost:8080/portal/portal/HelloPortal/foobar"
- >http://localhost:8080/portal/portal/HelloPortal/foobar</ulink>
- , for the second page
- created.
- </para>
- <note>You must define a page named
- <literal>default</literal>
- for any new portal instance
- to be accessible via a web browser.
- </note>
+ <para>
+ When deployed, this example registers a new portal instance, <computeroutput>HelloPortal</computeroutput>, that contains two pages. To view the default page in the <computeroutput>HelloPortal</computeroutput> instance, navigate to <ulink url="http://localhost:8080/portal/portal/HelloPortal" />, and to <ulink url="http://localhost:8080/portal/portal/HelloPortal/foobar" /> for the second page.
+ </para>
+ <para>
+ <note>
+ <title>Portal Instance <computerouput>default</computerouput> Page</title>
+ <para>
+ To be accessible via a Web browser, you must define a page named <computerouput>default</computerouput> for any portal instance.
+ </para>
+ </note>
+ </para>
</sect2>
</sect1>
</chapter>
16 years, 1 month
JBoss Portal SVN: r10764 - in modules/web/trunk/web/src: test/resources/spi/generic/app-war/WEB-INF and 2 other directories.
by portal-commits＠lists.jboss.org
Author: julien(a)jboss.com
Date: 2008-05-09 09:37:49 -0400 (Fri, 09 May 2008)
New Revision: 10764
Added:
modules/web/trunk/web/src/main/java/org/jboss/portal/web/impl/generic/GenericBootstrapServlet.java
Modified:
modules/web/trunk/web/src/test/resources/spi/generic/app-war/WEB-INF/web.xml
modules/web/trunk/web/src/test/resources/support/jboss-4.2-generic/server-war/WEB-INF/web.xml
modules/web/trunk/web/src/test/resources/support/tomcat-6.0-generic/server-war/WEB-INF/web.xml
Log:
renamed PortletContainerBoostrapServlet to GenericBoostrapServlet
Copied: modules/web/trunk/web/src/main/java/org/jboss/portal/web/impl/generic/GenericBootstrapServlet.java (from rev 10502, modules/web/trunk/web/src/main/java/org/jboss/portal/web/impl/generic/PortletContainerBootstrapServlet.java)
===================================================================
--- modules/web/trunk/web/src/main/java/org/jboss/portal/web/impl/generic/GenericBootstrapServlet.java (rev 0)
+++ modules/web/trunk/web/src/main/java/org/jboss/portal/web/impl/generic/GenericBootstrapServlet.java 2008-05-09 13:37:49 UTC (rev 10764)
@@ -0,0 +1,70 @@
+/******************************************************************************
+ * JBoss, a division of Red Hat *
+ * Copyright 2006, 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.web.impl.generic;
+
+import org.jboss.portal.web.command.CommandServlet;
+
+import javax.servlet.ServletException;
+import javax.servlet.ServletContext;
+import java.lang.reflect.Method;
+
+/**
+ * @author <a href="mailto:julien@jboss.org">Julien Viet</a>
+ * @version $Revision: 1.1 $
+ */
+public class GenericBootstrapServlet extends CommandServlet
+{
+
+ /** . */
+ private String contextPath;
+
+ public void init() throws ServletException
+ {
+ try
+ {
+ Method m = ServletContext.class.getMethod("getContextPath", new Class[0]);
+ ServletContext servletContext = getServletContext();
+
+ //
+ String contextPath = (String)m.invoke(servletContext, new Object[0]);
+ ClassLoader classLoader = Thread.currentThread().getContextClassLoader();
+ GenericWebAppContext webAppContext = new GenericWebAppContext(servletContext, contextPath, classLoader);
+
+ //
+ GenericServletContainerContext.instance.register(webAppContext);
+ this.contextPath = contextPath;
+ }
+ catch (Exception e)
+ {
+ e.printStackTrace();
+ }
+ }
+
+ public void destroy()
+ {
+ if (contextPath != null)
+ {
+ GenericServletContainerContext.instance.unregister(contextPath);
+ }
+ }
+}
Modified: modules/web/trunk/web/src/test/resources/spi/generic/app-war/WEB-INF/web.xml
===================================================================
--- modules/web/trunk/web/src/test/resources/spi/generic/app-war/WEB-INF/web.xml 2008-05-09 09:50:03 UTC (rev 10763)
+++ modules/web/trunk/web/src/test/resources/spi/generic/app-war/WEB-INF/web.xml 2008-05-09 13:37:49 UTC (rev 10764)
@@ -28,7 +28,7 @@
<web-app>
<servlet>
<servlet-name>BootstrapServlet</servlet-name>
- <servlet-class>org.jboss.portal.web.impl.generic.PortletContainerBootstrapServlet</servlet-class>
+ <servlet-class>org.jboss.portal.web.impl.generic.GenericBootstrapServlet</servlet-class>
<load-on-startup>0</load-on-startup>
</servlet>
<servlet-mapping>
Modified: modules/web/trunk/web/src/test/resources/support/jboss-4.2-generic/server-war/WEB-INF/web.xml
===================================================================
--- modules/web/trunk/web/src/test/resources/support/jboss-4.2-generic/server-war/WEB-INF/web.xml 2008-05-09 09:50:03 UTC (rev 10763)
+++ modules/web/trunk/web/src/test/resources/support/jboss-4.2-generic/server-war/WEB-INF/web.xml 2008-05-09 13:37:49 UTC (rev 10764)
@@ -44,7 +44,7 @@
</servlet>
<servlet>
<servlet-name>BootstrapServlet</servlet-name>
- <servlet-class>org.jboss.portal.web.impl.generic.PortletContainerBootstrapServlet</servlet-class>
+ <servlet-class>org.jboss.portal.web.impl.generic.GenericBootstrapServlet</servlet-class>
<load-on-startup>0</load-on-startup>
</servlet>
<servlet-mapping>
Modified: modules/web/trunk/web/src/test/resources/support/tomcat-6.0-generic/server-war/WEB-INF/web.xml
===================================================================
--- modules/web/trunk/web/src/test/resources/support/tomcat-6.0-generic/server-war/WEB-INF/web.xml 2008-05-09 09:50:03 UTC (rev 10763)
+++ modules/web/trunk/web/src/test/resources/support/tomcat-6.0-generic/server-war/WEB-INF/web.xml 2008-05-09 13:37:49 UTC (rev 10764)
@@ -44,7 +44,7 @@
</servlet>
<servlet>
<servlet-name>BootstrapServlet</servlet-name>
- <servlet-class>org.jboss.portal.web.impl.generic.PortletContainerBootstrapServlet</servlet-class>
+ <servlet-class>org.jboss.portal.web.impl.generic.GenericBootstrapServlet</servlet-class>
<load-on-startup>0</load-on-startup>
</servlet>
<servlet-mapping>
16 years, 1 month
JBoss Portal SVN: r10763 - in branches/JBoss_Portal_Branch_2_7/core-admin/src: resources/portal-admin-war/jsf and 1 other directory.
by portal-commits＠lists.jboss.org
Author: thomas.heute(a)jboss.com
Date: 2008-05-09 05:50:03 -0400 (Fri, 09 May 2008)
New Revision: 10763
Modified:
branches/JBoss_Portal_Branch_2_7/core-admin/src/main/org/jboss/portal/core/admin/ui/PortletManagerBean.java
branches/JBoss_Portal_Branch_2_7/core-admin/src/resources/portal-admin-war/jsf/dashboardsTemplate.xhtml
branches/JBoss_Portal_Branch_2_7/core-admin/src/resources/portal-admin-war/jsf/instancesTemplate.xhtml
branches/JBoss_Portal_Branch_2_7/core-admin/src/resources/portal-admin-war/jsf/objectTemplate.xhtml
Log:
JBPORTAL-2010: error after deleting a WSRP consumer
Modified: branches/JBoss_Portal_Branch_2_7/core-admin/src/main/org/jboss/portal/core/admin/ui/PortletManagerBean.java
===================================================================
--- branches/JBoss_Portal_Branch_2_7/core-admin/src/main/org/jboss/portal/core/admin/ui/PortletManagerBean.java 2008-05-09 09:47:20 UTC (rev 10762)
+++ branches/JBoss_Portal_Branch_2_7/core-admin/src/main/org/jboss/portal/core/admin/ui/PortletManagerBean.java 2008-05-09 09:50:03 UTC (rev 10763)
@@ -279,8 +279,17 @@
if (portlets == null)
{
portlets = new ArrayList();
- List tmpPortlets = new ArrayList(getSelectedPortletInvoker().getPortlets());
-
+
+ List tmpPortlets = null;
+
+ if (getSelectedPortletInvoker() != null)
+ {
+ tmpPortlets = new ArrayList(getSelectedPortletInvoker().getPortlets());
+ }
+ else
+ {
+ tmpPortlets = new ArrayList(federatingPortletInvoker.getFederatedInvoker("local").getPortlets());
+ }
// Remove content editors
nextPortlet:
for (Iterator i = tmpPortlets.iterator(); i.hasNext();)
@@ -333,7 +342,7 @@
public Portlet getSelectedPortlet()
{
- if (selectedPortlet == null && selectedPortletId != null)
+ if (selectedPortlet == null && selectedPortletId != null && getSelectedPortletInvoker() != null)
{
try
{
Modified: branches/JBoss_Portal_Branch_2_7/core-admin/src/resources/portal-admin-war/jsf/dashboardsTemplate.xhtml
===================================================================
--- branches/JBoss_Portal_Branch_2_7/core-admin/src/resources/portal-admin-war/jsf/dashboardsTemplate.xhtml 2008-05-09 09:47:20 UTC (rev 10762)
+++ branches/JBoss_Portal_Branch_2_7/core-admin/src/resources/portal-admin-war/jsf/dashboardsTemplate.xhtml 2008-05-09 09:50:03 UTC (rev 10763)
@@ -17,7 +17,7 @@
<h:commandLink value="Portlet Instances" action="instances"/>
</li>
<li>
- <h:commandLink value="Portlet Definitions" action="portlets"/>
+ <h:commandLink value="Portlet Definitions" action="#{portletmgr.selectPortlet}"/>
</li>
<li id="currentTab">Dashboards</li>
</ul>
Modified: branches/JBoss_Portal_Branch_2_7/core-admin/src/resources/portal-admin-war/jsf/instancesTemplate.xhtml
===================================================================
--- branches/JBoss_Portal_Branch_2_7/core-admin/src/resources/portal-admin-war/jsf/instancesTemplate.xhtml 2008-05-09 09:47:20 UTC (rev 10762)
+++ branches/JBoss_Portal_Branch_2_7/core-admin/src/resources/portal-admin-war/jsf/instancesTemplate.xhtml 2008-05-09 09:50:03 UTC (rev 10763)
@@ -13,7 +13,7 @@
</li>
<li id="currentTab">Portlet Instances</li>
<li>
- <h:commandLink value="Portlet Definitions" action="portlets"/>
+ <h:commandLink value="Portlet Definitions" action="#{portletmgr.selectPortlet}"/>
</li>
<li>
<h:commandLink value="Dashboards" action="dashboards"/>
Modified: branches/JBoss_Portal_Branch_2_7/core-admin/src/resources/portal-admin-war/jsf/objectTemplate.xhtml
===================================================================
--- branches/JBoss_Portal_Branch_2_7/core-admin/src/resources/portal-admin-war/jsf/objectTemplate.xhtml 2008-05-09 09:47:20 UTC (rev 10762)
+++ branches/JBoss_Portal_Branch_2_7/core-admin/src/resources/portal-admin-war/jsf/objectTemplate.xhtml 2008-05-09 09:50:03 UTC (rev 10763)
@@ -15,7 +15,7 @@
<h:commandLink value="Portlet Instances" action="instances"/>
</li>
<li>
- <h:commandLink value="Portlet Definitions" action="portlets"/>
+ <h:commandLink value="Portlet Definitions" action="#{portletmgr.selectPortlet}"/>
</li>
<li>
<h:commandLink value="Dashboards" action="dashboards"/>
16 years, 1 month
JBoss Portal SVN: r10762 - branches/JBoss_Portal_Branch_2_7/core/src/resources/portal-server-war.
by portal-commits＠lists.jboss.org
Author: thomas.heute(a)jboss.com
Date: 2008-05-09 05:47:20 -0400 (Fri, 09 May 2008)
New Revision: 10762
Modified:
branches/JBoss_Portal_Branch_2_7/core/src/resources/portal-server-war/login.jsp
Log:
JBPORTAL-1922: IE 6.0 Error: Can't move focus to the control
Modified: branches/JBoss_Portal_Branch_2_7/core/src/resources/portal-server-war/login.jsp
===================================================================
--- branches/JBoss_Portal_Branch_2_7/core/src/resources/portal-server-war/login.jsp 2008-05-09 08:39:35 UTC (rev 10761)
+++ branches/JBoss_Portal_Branch_2_7/core/src/resources/portal-server-war/login.jsp 2008-05-09 09:47:20 UTC (rev 10762)
@@ -36,9 +36,20 @@
}
/* ]]> */
</style>
+
+ <script>
+ function setFocusOnLoginForm() {
+ try {
+ document.loginform.j_username.focus();
+ }
+ catch (e) {
+ }
+ }
+ </script>
+
<link rel="stylesheet" href="/portal-core/css/login.css" type="text/css" />
</head>
-<body onload="document.loginform.j_username.focus();">
+<body onload="setFocusOnLoginForm();">
<div class="login-container">
16 years, 1 month