JBoss Portal SVN: r10061 - docs/branches.
by portal-commits＠lists.jboss.org
Author: julien(a)jboss.com
Date: 2008-02-21 07:16:53 -0500 (Thu, 21 Feb 2008)
New Revision: 10061
Added:
docs/branches/JBoss_Portal_Branch_2_7/
Log:
branching 2.7 for docs
Copied: docs/branches/JBoss_Portal_Branch_2_7 (from rev 10060, docs/branches/JBoss_Portal_Branch_2_6)
16 years, 8 months
JBoss Portal SVN: r10060 - branches.
by portal-commits＠lists.jboss.org
Author: julien(a)jboss.com
Date: 2008-02-21 07:10:56 -0500 (Thu, 21 Feb 2008)
New Revision: 10060
Added:
branches/JBoss_Portal_Branch_2_7/
Log:
2.7
Copied: branches/JBoss_Portal_Branch_2_7 (from rev 10059, branches/JBoss_Portal_Branch_2_6)
16 years, 8 months
JBoss Portal SVN: r10059 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-21 02:48:57 -0500 (Thu, 21 Feb 2008)
New Revision: 10059
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml
Log:
s/server/service on a port less than 1024
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-21 07:36:26 UTC (rev 10058)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml 2008-02-21 07:48:57 UTC (rev 10059)
@@ -40,7 +40,7 @@
<warning>
<title>Root User Privileges</title>
<para>
- Linux systems require root user privileges to run a server on a port less than 1024. Starting JBoss EAP or JBoss AS on port 80 as a non-privileged user will not work. Running JBoss EAP or JBoss AS as the root user could lead to security breaches.
+ Linux systems require root user privileges to run a service on a port less than 1024. Starting JBoss EAP or JBoss AS on port 80 as a non-privileged user will not work. Running JBoss EAP or JBoss AS as the root user could lead to security breaches.
</para>
</warning>
</para>
16 years, 8 months
JBoss Portal SVN: r10058 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-21 02:36:26 -0500 (Thu, 21 Feb 2008)
New Revision: 10058
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml
Log:
6.1.1. The JBoss Portlet DTD
minor 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-02-21 05:08:12 UTC (rev 10057)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml 2008-02-21 07:36:26 UTC (rev 10058)
@@ -101,11 +101,11 @@
Use the <computeroutput><remotable></computeroutput> element to configure the default behavior of portlets with respect to WSRP exposure: if no value is given, the value is either the value globally defined at the portlet application level, or <computeroutput>false</computeroutput>.
</para>
<para>
- The <computeroutput><trans-attribute></computeroutput> element specifies the behavior of the portlet when it is invoked at runtime, with respect to the transactional context. Depending on how the portlet is
- invoked, a transaction may or may not exist before the portlet is invoked. The portal transaction is usually present in the local context. By default, the value is <computeroutput>NotSupported</computeroutput>, which means that the portal transaction will be suspended for the duration of the portlet invocation. Accepted values are <computeroutput>Required</computeroutput>, <computeroutput>Mandatory</computeroutput>, <computeroutput>Never</computeroutput>, <computeroutput>Supports</computeroutput>, <computeroutput>NotSupported</computeroutput>, and <computeroutput>RequiresNew</computeroutput>.
+ The <computeroutput><trans-attribute></computeroutput> element specifies the behavior of the portlet when it is invoked at runtime with respect to the transactional context. Depending on how the portlet is
+ invoked, a transaction may or may not exist before the portlet is invoked. The portal transaction is usually present in the local context. The default value is <computeroutput>NotSupported</computeroutput>, which means that the portal transaction will be suspended for the duration of the session. Accepted values are <computeroutput>Required</computeroutput>, <computeroutput>Mandatory</computeroutput>, <computeroutput>Never</computeroutput>, <computeroutput>Supports</computeroutput>, <computeroutput>NotSupported</computeroutput>, and <computeroutput>RequiresNew</computeroutput>.
</para>
<para>
- The following example uses the <computeroutput><portlet-name></computeroutput>, <computeroutput><remotable></computeroutput>, and <computeroutput><trans-attribute></computeroutput> elements:
+ The following is an example section from a <filename>WEB-INF/portlet.xml</filename> file, which uses the <computeroutput><portlet-name></computeroutput>, <computeroutput><remotable></computeroutput>, and <computeroutput><trans-attribute></computeroutput> elements:
</para>
<para>
<screen><![CDATA[
@@ -140,7 +140,7 @@
</screen></term>
<listitem>
<para>
- Use the <computeroutput>ajax</computeroutput> element to configure the Asynchronous JavaScript and XML (AJAX) capabilities of the portlet. If a portlet uses the <computeroutput>true</computeroutput> value for the <computeroutput><partial-refresh></computeroutput> element, the portal uses partial page refreshing and only renders that portlet. If the <computeroutput><partial-refresh></computeroutput> element uses a <computeroutput>false</computeroutput> value, the portal uses a full-page refresh when the portlet is refreshed.
+ Use the <computeroutput>ajax</computeroutput> element to configure the Asynchronous JavaScript and XML (AJAX) capabilities of the portlet.
</para>
<para>
<screen><![CDATA[
@@ -148,7 +148,7 @@
</screen>
</para>
<para>
- If a portlet uses the <computeroutput>true</computeroutput> value for the <computeroutput><partial-refresh></computeroutput> element, the portal uses partial page refreshing and only renders that portlet. If the <computeroutput><partial-refresh></computeroutput> element uses a <computeroutput>false</computeroutput> value, the portal uses a full-page refresh when the portlet is refreshed.
+ If a portlet uses the <computeroutput>true</computeroutput> value for the <computeroutput><partial-refresh></computeroutput> element, the portal uses partial-page refreshing and only renders the portlet. If the <computeroutput><partial-refresh></computeroutput> element uses a <computeroutput>false</computeroutput> value, the portal uses a full-page refresh when the portlet is refreshed.
</para>
</listitem>
</varlistentry>
@@ -157,7 +157,7 @@
</screen></term>
<listitem>
<para>
- The <computeroutput><session-config></computeroutput> configures the portlet session of the portlet. The <computeroutput><distributed></computeroutput> element instructs the container to distribute the session attributes using the portal session replication. This only applies to local portlets, not remote portlets.
+ The <computeroutput><session-config></computeroutput> element configures the portlet session of the portlet. The <computeroutput><distributed></computeroutput> element instructs the container to distribute the session attributes using portal session replication. This only applies to local portlets, not remote portlets.
</para>
<para>
The following is an example of the <computeroutput><session-config></computeroutput> and <computeroutput><distributed></computeroutput> elements:
16 years, 8 months
JBoss Portal SVN: r10057 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-21 00:08:12 -0500 (Thu, 21 Feb 2008)
New Revision: 10057
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml
Log:
6.1.1. The JBoss Portlet DTD
minor revisions, spelling corrections, removing
doubled-up content. Mess almost fixed...
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-21 04:18:31 UTC (rev 10056)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml 2008-02-21 05:08:12 UTC (rev 10057)
@@ -98,10 +98,10 @@
Additional configuration for the portlet. The <computeroutput><portlet-name></computeroutput> element defines the portlet name. It must match a portlet defined in the <filename>WEB-INF/portlet.xml</filename> file for that application.
</para>
<para>
- Use the <computeroutput><remotable></computeroutput> element to configure the default behavior of portlets with respect to WSRP exposure: if no value is given, the value is either the value globally defined at the portlet application level, or <computeroutput>false</computeroutput>. Accepted values are <computeroutput>true</computeroutput> and <computeroutput>false</computeroutput>.
+ Use the <computeroutput><remotable></computeroutput> element to configure the default behavior of portlets with respect to WSRP exposure: if no value is given, the value is either the value globally defined at the portlet application level, or <computeroutput>false</computeroutput>.
</para>
<para>
- The <computeroutput><trans-attribute></computeroutput> element specifies the behavior of the portlet when it is invoked at runtime, with respect to the transactionnal context. Depending on how the portlet is
+ The <computeroutput><trans-attribute></computeroutput> element specifies the behavior of the portlet when it is invoked at runtime, with respect to the transactional context. Depending on how the portlet is
invoked, a transaction may or may not exist before the portlet is invoked. The portal transaction is usually present in the local context. By default, the value is <computeroutput>NotSupported</computeroutput>, which means that the portal transaction will be suspended for the duration of the portlet invocation. Accepted values are <computeroutput>Required</computeroutput>, <computeroutput>Mandatory</computeroutput>, <computeroutput>Never</computeroutput>, <computeroutput>Supports</computeroutput>, <computeroutput>NotSupported</computeroutput>, and <computeroutput>RequiresNew</computeroutput>.
</para>
<para>
@@ -157,7 +157,7 @@
</screen></term>
<listitem>
<para>
- The <computeroutput><session-config></computeroutput> configures the portlet session of the portlet. The <computeroutput><distributed></computeroutput> element instructs the container to distribute the session attributes using the portal session replication. This only applies to local portlets, not remote portlets. Accepted values are <computeroutput>true</computeroutput> and <computeroutput>false</computeroutput>. The default value is <computeroutput>false</computeroutput>.
+ The <computeroutput><session-config></computeroutput> configures the portlet session of the portlet. The <computeroutput><distributed></computeroutput> element instructs the container to distribute the session attributes using the portal session replication. This only applies to local portlets, not remote portlets.
</para>
<para>
The following is an example of the <computeroutput><session-config></computeroutput> and <computeroutput><distributed></computeroutput> elements:
@@ -175,7 +175,7 @@
</screen>
</para>
<para>
- The <computeroutput><distributed></computeroutput> element instructs the container to distribute the session attributes using the portal session replication. This only applies to local portlets, not remote portlets. Accepted values are <computeroutput>true</computeroutput> and <computeroutput>false</computeroutput>. The default value is <computeroutput>false</computeroutput>.
+ Accepted values are <computeroutput>true</computeroutput> and <computeroutput>false</computeroutput>. The default value is <computeroutput>false</computeroutput>.
</para>
</listitem>
</varlistentry>
@@ -184,7 +184,7 @@
</screen></term>
<listitem>
<para>
- Define how the portlet behaves with the transactionnal context. The <computeroutput><trans-attribute></computeroutput> element specifies the behavior of the portlet when it is invoked at runtime, with respect to the transactionnal context. Depending on how the portlet is invoked, a transaction may or may not exist before the portlet is invoked. The portal transaction is usually present in the local context.
+ Define how the portlet behaves with the transactional context. The <computeroutput><trans-attribute></computeroutput> element specifies the behavior of the portlet when it is invoked at runtime, with respect to the transactional context. Depending on how the portlet is invoked, a transaction may or may not exist before the portlet is invoked. The portal transaction is usually present in the local context.
</para>
<para>
The following is an example of the <computeroutput><trans-attribute></computeroutput> element:
@@ -202,7 +202,7 @@
</screen>
</para>
<para>
- The <computeroutput><trans-attribute></computeroutput> value defines the transactionnal behavior. By default, the value is <computeroutput>NotSupported</computeroutput>, which means that the portal transaction will be suspended for the duration of the portlet invocation. Accepted values are <computeroutput>Required</computeroutput>, <computeroutput>Mandatory</computeroutput>, <computeroutput>Never</computeroutput>, <computeroutput>Supports</computeroutput>, <computeroutput>NotSupported</computeroutput>, and <computeroutput>RequiresNew</computeroutput>.
+ The default value is <computeroutput>NotSupported</computeroutput>, which means that the portal transaction will be suspended for the duration of the portlet invocation. Accepted values are <computeroutput>Required</computeroutput>, <computeroutput>Mandatory</computeroutput>, <computeroutput>Never</computeroutput>, <computeroutput>Supports</computeroutput>, <computeroutput>NotSupported</computeroutput>, and <computeroutput>RequiresNew</computeroutput>.
</para>
</listitem>
</varlistentry>
@@ -219,7 +219,7 @@
</screen>
</para>
<para>
- No content is allowed inside an link element.
+ No content is allowed inside a link element.
</para>
<para>
<screen><![CDATA[
@@ -227,7 +227,7 @@
</screen>
</para>
<para>
- The script header element can contain inline script definitions.
+ Use the <computeroutput><script></computeroutput> element for inline script definitions.
</para>
<para>
<screen><![CDATA[
@@ -235,7 +235,7 @@
</screen>
</para>
<para>
- No content is allowed for meta element.
+ No content is allowed for the <computeroutput><meta></computeroutput> element.
</para>
</listitem>
</varlistentry>
@@ -247,7 +247,7 @@
Declare a service that will be injected by the portlet container as an attribute of the portlet context.
</para>
<para>
- For example:
+ The following is an example of the <computeroutput><service></computeroutput> element:
</para>
<para>
<screen><![CDATA[
@@ -258,7 +258,8 @@
</service>]]>
</screen>
</para>
- <para>In the portlet it is then possible to use it by doing a lookup on the service name, for example in the init() lifecycle method :
+ <para>
+ To use an injected service in a portlet, perform a lookup of the <computeroutput><service-name></computeroutput>, for example, using the <computeroutput>init()</computeroutput> lifecycle method:
</para>
<para>
<screen><![CDATA[
@@ -274,7 +275,7 @@
</screen>
</para>
<para>
- The service name that will be used to bind the service as a portlet context attribute.
+ The <computeroutput><service-name></computeroutput> element defines the name that binds the service as a portlet context attribute.
</para>
<para>
<screen><![CDATA[
@@ -282,7 +283,7 @@
</screen>
</para>
<para>
- The full qualified name of the interface that the service implements.
+ The <computeroutput><service-class></computeroutput> element defines the fully qualified name of the interface that the service implements.
</para>
<para>
<screen><![CDATA[
@@ -290,7 +291,7 @@
</screen>
</para>
<para>
- The reference to the service. In the JMX Microkernel environment it consist of the JMX name of the service MBean. For an MBean reference if the domain is left out, then the current domain of the portal will be used.
+ The <computeroutput><service-ref></computeroutput> defines the reference to the service. In the JMX Microkernel environment, this consist of the JMX name of the service MBean. For an MBean reference, if the domain is left out, then the current domain of the portal is used.
</para>
</listitem>
</varlistentry>
16 years, 8 months
JBoss Portal SVN: r10056 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-20 23:18:31 -0500 (Wed, 20 Feb 2008)
New Revision: 10056
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml
Log:
6.1.1. The JBoss Portlet DTD
trying to fix my mess
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-21 03:52:58 UTC (rev 10055)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml 2008-02-21 04:18:31 UTC (rev 10056)
@@ -131,7 +131,7 @@
</screen>
</para>
<para>
- Use the <computeroutput><remotable></computeroutput> element to configure the default behavior of portlets with respect to WSRP exposure: if no value is given, the value is either the value globally defined at the portlet application level, or <computeroutput>false</computeroutput>. Accepted values are <computeroutput>true</computeroutput> and <computeroutput>false</computeroutput>.
+ Accepted values are <computeroutput>true</computeroutput> and <computeroutput>false</computeroutput>.
</para>
</listitem>
</varlistentry>
@@ -169,19 +169,18 @@
</session-config>]]>
</screen>
</para>
-</listitem>
-</varlistentry>
-<varlistentry><term><screen><![CDATA[
-<![CDATA[<!ELEMENT distributed (#PCDATA)>]]>
-</screen></term>
-<listitem>
<para>
+<screen><![CDATA[
+<!ELEMENT distributed (#PCDATA)>]]>
+</screen>
+ </para>
+ <para>
The <computeroutput><distributed></computeroutput> element instructs the container to distribute the session attributes using the portal session replication. This only applies to local portlets, not remote portlets. Accepted values are <computeroutput>true</computeroutput> and <computeroutput>false</computeroutput>. The default value is <computeroutput>false</computeroutput>.
</para>
</listitem>
</varlistentry>
<varlistentry><term><screen><![CDATA[
-<![CDATA[<!ELEMENT transaction (trans-attribute)>]]>
+<!ELEMENT transaction (trans-attribute)>]]>
</screen></term>
<listitem>
<para>
@@ -199,7 +198,7 @@
</para>
<para>
<screen><![CDATA[
-<![CDATA[<!ELEMENT trans-attribute (#PCDATA)>]]>
+<!ELEMENT trans-attribute (#PCDATA)>]]>
</screen>
</para>
<para>
@@ -208,7 +207,7 @@
</listitem>
</varlistentry>
<varlistentry><term><screen><![CDATA[
-<![CDATA[<!ELEMENT header-content (link | script | meta)*>]]>
+<!ELEMENT header-content (link | script | meta)*>]]>
</screen></term>
<listitem>
<para>
@@ -216,7 +215,7 @@
</para>
<para>
<screen><![CDATA[
-<![CDATA[<!ELEMENT link EMPTY>]]>
+<!ELEMENT link EMPTY>]]>
</screen>
</para>
<para>
@@ -224,7 +223,7 @@
</para>
<para>
<screen><![CDATA[
-<![CDATA[<!ELEMENT script (#PCDATA)>]]>
+<!ELEMENT script (#PCDATA)>]]>
</screen>
</para>
<para>
@@ -232,7 +231,7 @@
</para>
<para>
<screen><![CDATA[
-<![CDATA[<!ELEMENT meta EMPTY>]]>
+<!ELEMENT meta EMPTY>]]>
</screen>
</para>
<para>
@@ -241,7 +240,7 @@
</listitem>
</varlistentry>
<varlistentry><term><screen><![CDATA[
-<![CDATA[<!ELEMENT service (service-name,service-class,service-ref)>]]>
+<!ELEMENT service (service-name,service-class,service-ref)>]]>
</screen></term>
<listitem>
<para>
@@ -271,7 +270,7 @@
</para>
<para>
<screen><![CDATA[
-<![CDATA[<!ELEMENT service-name (#PCDATA)>]]>
+<!ELEMENT service-name (#PCDATA)>]]>
</screen>
</para>
<para>
@@ -279,7 +278,7 @@
</para>
<para>
<screen><![CDATA[
-<![CDATA[<!ELEMENT service-class (#PCDATA)>]]>
+<!ELEMENT service-class (#PCDATA)>]]>
</screen>
</para>
<para>
@@ -287,7 +286,7 @@
</para>
<para>
<screen><![CDATA[
-<![CDATA[<!ELEMENT service-ref (#PCDATA)>]]>
+<!ELEMENT service-ref (#PCDATA)>]]>
</screen>
</para>
<para>
16 years, 8 months
JBoss Portal SVN: r10055 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-20 22:52:58 -0500 (Wed, 20 Feb 2008)
New Revision: 10055
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml
Log:
6.1.1. The JBoss Portlet DTD
revising use of lists/layout
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-21 03:11:40 UTC (rev 10054)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml 2008-02-21 03:52:58 UTC (rev 10055)
@@ -125,12 +125,11 @@
<para>
The portlet name.
</para>
-</listitem>
-</varlistentry>
-<varlistentry><term><screen><![CDATA[
+ <para>
+<screen><![CDATA[
<!ELEMENT remotable (#PCDATA)>]]>
-</screen></term>
-<listitem>
+</screen>
+ </para>
<para>
Use the <computeroutput><remotable></computeroutput> element to configure the default behavior of portlets with respect to WSRP exposure: if no value is given, the value is either the value globally defined at the portlet application level, or <computeroutput>false</computeroutput>. Accepted values are <computeroutput>true</computeroutput> and <computeroutput>false</computeroutput>.
</para>
@@ -143,12 +142,11 @@
<para>
Use the <computeroutput>ajax</computeroutput> element to configure the Asynchronous JavaScript and XML (AJAX) capabilities of the portlet. If a portlet uses the <computeroutput>true</computeroutput> value for the <computeroutput><partial-refresh></computeroutput> element, the portal uses partial page refreshing and only renders that portlet. If the <computeroutput><partial-refresh></computeroutput> element uses a <computeroutput>false</computeroutput> value, the portal uses a full-page refresh when the portlet is refreshed.
</para>
-</listitem>
-</varlistentry>
-<varlistentry><term><screen><![CDATA[
+ <para>
+<screen><![CDATA[
<!ELEMENT partial-refresh (#PCDATA)>]]>
-</screen></term>
-<listitem>
+</screen>
+ </para>
<para>
If a portlet uses the <computeroutput>true</computeroutput> value for the <computeroutput><partial-refresh></computeroutput> element, the portal uses partial page refreshing and only renders that portlet. If the <computeroutput><partial-refresh></computeroutput> element uses a <computeroutput>false</computeroutput> value, the portal uses a full-page refresh when the portlet is refreshed.
</para>
@@ -199,12 +197,11 @@
<transaction>]]>
</screen>
</para>
-</listitem>
-</varlistentry>
-<varlistentry><term><screen><![CDATA[
+ <para>
+<screen><![CDATA[
<![CDATA[<!ELEMENT trans-attribute (#PCDATA)>]]>
-</screen></term>
-<listitem>
+</screen>
+ </para>
<para>
The <computeroutput><trans-attribute></computeroutput> value defines the transactionnal behavior. By default, the value is <computeroutput>NotSupported</computeroutput>, which means that the portal transaction will be suspended for the duration of the portlet invocation. Accepted values are <computeroutput>Required</computeroutput>, <computeroutput>Mandatory</computeroutput>, <computeroutput>Never</computeroutput>, <computeroutput>Supports</computeroutput>, <computeroutput>NotSupported</computeroutput>, and <computeroutput>RequiresNew</computeroutput>.
</para>
@@ -215,32 +212,29 @@
</screen></term>
<listitem>
<para>
- Specify content to be included in the portal aggregated page, when the portlet is present on that page. This setting only applies when the portlet is used in the local mode.
+ Specify content to be included in the portal aggregated page when the portlet is present on that page. This setting only applies when the portlet is used in the local mode.
</para>
-</listitem>
-</varlistentry>
-<varlistentry><term><screen><![CDATA[
+ <para>
+<screen><![CDATA[
<![CDATA[<!ELEMENT link EMPTY>]]>
-</screen></term>
-<listitem>
+</screen>
+ </para>
<para>
No content is allowed inside an link element.
</para>
-</listitem>
-</varlistentry>
-<varlistentry><term><screen><![CDATA[
+ <para>
+<screen><![CDATA[
<![CDATA[<!ELEMENT script (#PCDATA)>]]>
-</screen></term>
-<listitem>
+</screen>
+ </para>
<para>
The script header element can contain inline script definitions.
</para>
-</listitem>
-</varlistentry>
-<varlistentry><term><screen><![CDATA[
+ <para>
+<screen><![CDATA[
<![CDATA[<!ELEMENT meta EMPTY>]]>
-</screen></term>
-<listitem>
+</screen>
+ </para>
<para>
No content is allowed for meta element.
</para>
@@ -275,30 +269,27 @@
}]]>
</screen>
</para>
-</listitem>
-</varlistentry>
-<varlistentry><term><screen><![CDATA[
+ <para>
+<screen><![CDATA[
<![CDATA[<!ELEMENT service-name (#PCDATA)>]]>
-</screen></term>
-<listitem>
+</screen>
+ </para>
<para>
The service name that will be used to bind the service as a portlet context attribute.
</para>
-</listitem>
-</varlistentry>
-<varlistentry><term><screen><![CDATA[
+ <para>
+<screen><![CDATA[
<![CDATA[<!ELEMENT service-class (#PCDATA)>]]>
-</screen></term>
-<listitem>
+</screen>
+ </para>
<para>
The full qualified name of the interface that the service implements.
</para>
-</listitem>
-</varlistentry>
-<varlistentry><term><screen><![CDATA[
+ <para>
+<screen><![CDATA[
<![CDATA[<!ELEMENT service-ref (#PCDATA)>]]>
-</screen></term>
-<listitem>
+</screen>
+ </para>
<para>
The reference to the service. In the JMX Microkernel environment it consist of the JMX name of the service MBean. For an MBean reference if the domain is left out, then the current domain of the portal will be used.
</para>
16 years, 8 months
JBoss Portal SVN: r10054 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-20 22:11:40 -0500 (Wed, 20 Feb 2008)
New Revision: 10054
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml
Log:
changing layout of 6.1.1. The JBoss Portlet DTD
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-21 01:56:09 UTC (rev 10053)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml 2008-02-21 03:11:40 UTC (rev 10054)
@@ -91,7 +91,7 @@
</listitem>
</varlistentry>
<varlistentry><term><screen><![CDATA[
- <!ELEMENT portlet (portlet-name,remotable?,ajax?,session-config?,transaction?,header-content?,portlet-info?)>]]>
+<!ELEMENT portlet (portlet-name,remotable?,ajax?,session-config?,transaction?,header-content?,portlet-info?)>]]>
</screen></term>
<listitem>
<para>
@@ -116,12 +116,12 @@
</portlet>]]>
</screen>
</para>
-</listitem>
-</varlistentry>
-<varlistentry><term><screen><![CDATA[
+ <para>
+<screen><![CDATA[
<!ELEMENT portlet-name (#PCDATA)>]]>
-</screen></term>
-<listitem>
+</screen>
+ </para>
+
<para>
The portlet name.
</para>
16 years, 8 months