Author: jeff.yuchang Date: 2012-06-08 04:58:10 -0400 (Fri, 08 Jun 2012) New Revision: 1563 Modified: branches/RiftSaw-2.3.x/docs/docbook/userguide/src/main/en-US/module/uddi.xml Log: FTSAW-494, (apply kurt's fix to 2.3.x branch) updating the documentation to reflect that the uddi.lookup flag no longer exists. Modified: branches/RiftSaw-2.3.x/docs/docbook/userguide/src/main/en-US/module/uddi.xml =================================================================== --- branches/RiftSaw-2.3.x/docs/docbook/userguide/src/main/en-US/module/uddi.xml 2012-06-07 19:40:01 UTC (rev 1562) +++ branches/RiftSaw-2.3.x/docs/docbook/userguide/src/main/en-US/module/uddi.xml 2012-06-08 08:58:10 UTC (rev 1563) @@ -50,7 +50,12 @@ <entry> If set to 'false', the UDDI integration is turned off. The RiftSaw installation process sets this value to 'true' only if the jbossesb-registry.sar is detected containing a jUDDI v3 - registry. In all other case it is defaulted to false. + registry. In all other case it is defaulted to false. If set to true, the creating process of the partner channel will do a lookup by serviceName in the + UDDI, and Endpoint(s) is retrieved. This process makes it easier to move process deployment around within your server farm, without having to update + the partnerlink WSDL files in your BPEL process deployments. If more then one EndPoint (BindingTemplate) is found default + policy the ServiceLocator uses a 'PolicyLocalFirst'. Please see the jUDDI v3 documentation for more + details and on how to switch to the 'PolicyRoundRobin' or a custom Policy. Note that it is still a requirement to + deploy the initial partnerlink WSDL file for each partnerLink. </entry> </row> <row> @@ -98,18 +103,6 @@ in the <filename>riftsaw.uddi.xml</filename>. By default this is set to 'BPEL_clerk'. </entry> </row> - <row> - <entry>bpel.uddi.lookup</entry> - <entry>boolean (true)</entry> - <entry> - If set to true, the creating process of the partner channel will do a lookup by serviceName in the - UDDI, and Endpoint(s) is retrieved. This process makes it easier to move process deployment around within your server farm, without having to update - the partnerlink WSDL files in your BPEL process deployments. If more then one EndPoint (BindingTemplate) is found default - policy the ServiceLocator uses a 'PolicyLocalFirst'. Please see the jUDDI v3 documentation for more - details and on how to switch to the 'PolicyRoundRobin' or a custom Policy. Note that it is still a requirement to - deploy the initial partnerlink WSDL file for each partnerLink. - </entry> - </row> </tbody> </tgroup>