Author: mmcallis
Date: 2008-02-27 00:51:19 -0500 (Wed, 27 Feb 2008)
New Revision: 10132
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml
Log:
6.1.3. The JBoss Portal Object DTD
minor revisions/periodic backup
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-02-27
04:03:42 UTC (rev 10131)
+++
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml 2008-02-27
05:51:19 UTC (rev 10132)
@@ -528,7 +528,7 @@
</screen></term>
<listitem>
<para>
- The <computeroutput><deployment></computeroutput> element is
a generic container for portal object elements. The
<computeroutput><parent-ref></computeroutput> child element
gives the name of the parent object that the current object will use as parent. The
optional <computeroutput><if-exists></computeroutput> element
defines the behavior when a portal object with an identical name is already a child of the
parent element. The default behavior of the
<computeroutput><if-exists></computeroutput> element is to keep
the existing object, and not to create a new object. The last element is the portal object
itself.
+ The <computeroutput><deployment></computeroutput> element is
a generic container for portal object elements. The
<computeroutput><parent-ref></computeroutput> child element
gives the name of the parent object that the current object will use as parent. The
optional <computeroutput><if-exists></computeroutput> element is
used to define the action to take if an instance with the same name already exists. The
default behavior of the
<computeroutput><if-exists></computeroutput> element is to keep
the existing object, and not to create a new object.
</para>
<para>
The following is an example of the
<computeroutput><deployment></computeroutput> and
<computeroutput><parent-ref></computeroutput> elements:
@@ -555,12 +555,12 @@
</listitem>
<listitem>
<para>
- properties: a set of generic properties owned by the portal object. Certain
properties drive the behavior of the object.
+ properties: a set of generic properties owned by the portal object. Certain
properties drive the behavior of the portal object.
</para>
</listitem>
<listitem>
<para>
- security-constraint: defines the security configuration of the portal object.
+ security-constraint: defines the security configuration for the portal object.
</para>
</listitem>
</itemizedlist>
@@ -571,7 +571,7 @@
</screen>
</para>
<para>
- Contains a reference to the parent object. The naming convention for naming object is
to concatenate the names of the path to the object, and separate the names by a period. If
the path is empty, then the empty string must be used. The
<computeroutput><parent-ref></computeroutput> element tells the
portal where the portlet should appear.
+ The <computeroutput><parent-ref></computeroutput> element
contains a reference to the parent object. The naming convention for naming objects is to
concatenate the names of the path to the object, and separate the names by a period. If
the path is empty, then the empty string must be used. The
<computeroutput><parent-ref></computeroutput> element tells the
portal where the portlet should appear. The syntax for the
<computeroutput><parent-ref></computeroutput> element is
<computeroutput><replaceable>portal-instance</replaceable>.<replaceable>portal-page</replaceable></computeroutput>.
</para>
<para>
The following is an example of the root having an empty path:
@@ -613,7 +613,7 @@
</screen></term>
<listitem>
<para>
- The context type of a portal object. A context type represent a node in a tree, which
does not have a visual representation. It only exists under root. A context can only have
children with the portal type.
+ The context type of the portal object. A context type represent a node in a tree, which
does not have a visual representation, and only exists under root. A context can only have
children with the <emphasis>portal</emphasis> type.
</para>
<para>
<screen><![CDATA[
@@ -677,7 +677,7 @@
</screen></term>
<listitem>
<para>
- Use the
<computeroutput><supported-window-states></computeroutput>
element to define the supported window states for the portal. Accepted values are
<computeroutput>normal</computeroutput>,
<computeroutput>minimized</computeroutput>, and
<computeroutput>maximized</computeroutput>. The following is an example of the
<computeroutput><supported-window-states></computeroutput>
element:
+ Use the
<computeroutput><supported-window-states></computeroutput>
element to define the supported window states for the portal. Accepted values are
<computeroutput>normal</computeroutput>,
<computeroutput>minimized</computeroutput>, and
<computeroutput>maximized</computeroutput>. The following is an example of the
<computeroutput><supported-window-states></computeroutput> and
<computeroutput><window-state></computeroutput> elements:
</para>
<para>
<screen><![CDATA[
@@ -704,7 +704,7 @@
</screen></term>
<listitem>
<para>
- A portal object with the type <emphasis>page</emphasis>. A page type
represents a page, and can only have children that use the type
<emphasis>page</emphasis> and <emphasis>window</emphasis>. The
children windows are the windows of the page, and the children pages are the sub-pages of
this page.
+ A portal object with the type <emphasis>page</emphasis>. A page type
represents a page, and can only have children that use the type
<emphasis>page</emphasis> and <emphasis>window</emphasis>. The
children windows are the windows of the page, and the children pages are the subpages of
this page.
</para>
<para>
<screen><![CDATA[
@@ -744,7 +744,7 @@
</screen>
</para>
<para>
- Define the content of the window as a reference to a portlet instance. The value is the
id of the instance.
+ Define the content of the window as a reference to a portlet instance. The value is the
ID of the instance.
</para>
<para>
The following is an example of the
<computeroutput><instance-ref></computeroutput> element:
Show replies by date