Author: chris.laprun(a)jboss.com Date: 2007-02-19 23:35:37 -0500 (Mon, 19 Feb 2007) New Revision: 6352 Modified: docs/trunk/referenceGuide/en/modules/wsrp.xml Log: - Updated documentation with respect to format change in -wsrp.xml. Modified: docs/trunk/referenceGuide/en/modules/wsrp.xml =================================================================== --- docs/trunk/referenceGuide/en/modules/wsrp.xml 2007-02-20 04:32:43 UTC (rev 6351) +++ docs/trunk/referenceGuide/en/modules/wsrp.xml 2007-02-20 04:35:37 UTC (rev 6352) @@ -207,9 +207,7 @@ <?xml version="1.0" standalone="yes"?> <deployments> <deployment> - <wsrp-producer> - <producer-id>bea</producer-id> - <expiration-cache>120</expiration-cache> + <wsrp-producer id="bea" expiration-cache="120"> <endpoint-wsdl-url>http://wsrp.bea.com:7001/producer/producer?WSDL</endpoint-wsdl-url> <registration-data> <property> @@ -269,7 +267,8 @@ <para>Let's now look at which information needs to be provided to configure access to a remote producer.</para> <para>First, we need to provide an identifier for the producer we are configuring so that we can refer to it - afterwards. This is accomplished via the <emphasis role="bold">&lt;producer-id&gt;</emphasis> element.</para> + afterwards. This is accomplished via the mandatory <emphasis role="bold">id</emphasis> attribute of the + <emphasis role="bold">&lt;wsrp-producer&gt;</emphasis> element.</para> <para>JBoss Portal also needs to learn about the remote producer's endpoints to be able to connect to the remote web services and perform WSRP invocations. Two options are currently supported to provide this @@ -300,10 +299,10 @@ </itemizedlist> </para> - <para>Both <emphasis role="bold">&lt;producer-id&gt;</emphasis> and either + <para>Both the <emphasis role="bold">id</emphasis> attribute and either <emphasis role="bold">&lt;endpoint-config&gt;</emphasis> or - <emphasis role="bold">&lt;endpoint-wsdl-url&gt;</emphasis> - are required elements for a functional remote producer configuration. + <emphasis role="bold">&lt;endpoint-wsdl-url&gt;</emphasis> elements + are required for a functional remote producer configuration. </para> </sect2> @@ -316,7 +315,8 @@ <para>One such optional configuration concerns caching. To prevent useless roundtrips between the local consumer and the remote producer, it is possible to cache some of the information sent by the producer (such as the list of offered portlets) for a given duration. The rate at which the information is refreshed is - defined by the <emphasis role="bold">&lt;expiration-cache&gt;</emphasis> element which specifies the + defined by the <emphasis role="bold">expiration-cache</emphasis> attribute of the + <emphasis role="bold">&lt;wsrp-producer&gt;</emphasis> element which specifies the refreshing period in seconds. For example, providing a value of 120 for expiration-cache means that the producer information will not be refreshed for 2 minutes after it has been somehow accessed. If no value is provided, JBoss Portal will always access the remote producer regardless of whether the remote @@ -355,9 +355,7 @@ <?xml version="1.0" encoding="UTF-8"?> <deployments> <deployment> - <wsrp-producer> - <producer-id>MyProducer</producer-id> - <expiration-cache>120</expiration-cache> + <wsrp-producer id="MyProducer" expiration-cache="120"> <endpoint-config> <service-description-url>http://www.someproducer.com/portal-wsrp/Servic... <markup-url>http://www.someproducer.com/portal-wsrp/MarkupService</m... @@ -377,9 +375,7 @@ <?xml version="1.0" encoding="UTF-8"?> <deployments> <deployment> - <wsrp-producer> - <producer-id>AnotherProducer</producer-id> - <expiration-cache>60</expiration-cache> + <wsrp-producer id="AnotherProducer" expiration-cache="60"> <endpoint-wsdl-url>http://example.com/producer/producer?WSDL</endpoi... <registration-data> <property>