Author: julien(a)jboss.com Date: 2007-02-12 17:39:38 -0500 (Mon, 12 Feb 2007) New Revision: 6235 Modified: docs/trunk/referenceGuide/en/modules/wsrp.xml Log: added DTD whenever possible in WSRP section Modified: docs/trunk/referenceGuide/en/modules/wsrp.xml =================================================================== --- docs/trunk/referenceGuide/en/modules/wsrp.xml 2007-02-12 22:35:20 UTC (rev 6234) +++ docs/trunk/referenceGuide/en/modules/wsrp.xml 2007-02-12 22:39:38 UTC (rev 6235) @@ -91,15 +91,17 @@ <emphasis>remotable</emphasis> element is optional. </para> <para> - <programlisting> - <![CDATA[ + <programlisting><![CDATA[ +<?xml version="1.0" standalone="yes"?> +<!DOCTYPE portlet-app PUBLIC + "-//JBoss Portal//DTD JBoss Portlet 2.6//EN" + "http://www.jboss.org/portal/dtd/jboss-portlet_2_6.dtd"> <portlet-app> <portlet> <portlet-name>BasicPortlet</portlet-name> <remotable>true</remotable> </portlet> -</portlet-app>]]> - </programlisting> +</portlet-app>]]></programlisting> </para> <para> It is also possible to specify that all the portlets declared within a given <emphasis>jboss-portlet.xml</emphasis> @@ -107,8 +109,11 @@ several portlets without having to specify the status for all the declared portlets. Let's look at an example: </para> <para> - <programlisting> - <![CDATA[ + <programlisting><![CDATA[ +<?xml version="1.0" standalone="yes"?> +<!DOCTYPE portlet-app PUBLIC + "-//JBoss Portal//DTD JBoss Portlet 2.6//EN" + "http://www.jboss.org/portal/dtd/jboss-portlet_2_6.dtd"> <portlet-app> <remotable>true</remotable> <portlet> @@ -189,8 +194,8 @@ need to create a <emphasis>-wsrp.xml</emphasis> file (which we will call here <emphasis>public-bea-wsrp.xml</emphasis> but the name does not matter as long as it ends with <emphasis>-wsrp.xml</emphasis>) as follows: - <programlisting> - <![CDATA[ + <programlisting><![CDATA[ +<?xml version="1.0" standalone="yes"?> <deployments> <deployment> <wsrp-producer> @@ -206,8 +211,7 @@ </registration-data> </wsrp-producer> </deployment> -</deployments>]]> - </programlisting> +</deployments>]]></programlisting> This producer descriptor gives access to BEA's public WSRP producer. We will look at the details of the different elements later. Note for now the <emphasis>producer-id</emphasis> element with a "bea" value. Put this file in the deploy directory and start the server (with JBoss Portal and its WSRP service deployed). @@ -338,8 +342,7 @@ URLs:</para> <para> - <programlisting> - <![CDATA[ + <programlisting><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <deployments> <deployment> @@ -354,16 +357,14 @@ </endpoint-config> </wsrp-producer> </deployment> -</deployments>]]> - </programlisting> +</deployments>]]></programlisting> </para> <para>Here is an example of a WSRP descriptor with endpoint definition via remote WSDL file, registration data and cache expiring every minute:</para> <para> - <programlisting> - <![CDATA[ + <programlisting><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <deployments> <deployment> @@ -380,8 +381,7 @@ </registration-data> </wsrp-producer> </deployment> -</deployments>]]> - </programlisting> +</deployments>]]></programlisting> </para> </sect2> </sect1> @@ -400,14 +400,12 @@ <title>Default configuration</title> <para> Let's look at the default configuration: - <programlisting> - <![CDATA[ + <programlisting><![CDATA[ <producer-configuration> <registration-configuration fullServiceDescriptionRequiresRegistration="true"> <registration-property-validator>org.jboss.portal.registration.policies.DefaultRegistrationPropertyValidator</registration-property-validator> </registration-configuration> -</producer-configuration>]]> - </programlisting> +</producer-configuration>]]></programlisting> The top element <emphasis role="bold">&lt;producer-configuration&gt;</emphasis> contains a single <emphasis role="bold">&lt;registration-configuration&gt;</emphasis> element that defines a <emphasis>fullServiceDescritpionRequiresRegistration</emphasis> attribute with the value "true". This @@ -504,8 +502,7 @@ values for two String registration properties named "name1" and "name2" respectively. The registration service will use the <literal>com.example.portal.SomeCustomRegistrationPolicy</literal> class for its registration policy. - <programlisting> - <![CDATA[ + <programlisting><![CDATA[ <producer-configuration> <registration-configuration fullServiceDescriptionRequiresRegistration="true"> <registration-policy>com.example.portal.SomeCustomRegistrationPolicy</registration-policy> @@ -522,8 +519,7 @@ <label xml:lang="en" resourceName="resource.label2">label2</label> </registration-property-description> </registration-configuration> -</producer-configuration>]]> - </programlisting> +</producer-configuration>]]></programlisting> </para> </sect2> </sect1>