Author: kurtstam
Date: 2010-03-02 01:48:39 -0500 (Tue, 02 Mar 2010)
New Revision: 533
Modified:
trunk/docs/docbook/userguide/src/main/module/uddi.xml
Log:
RIFTSAW-151 adding UDDI integration documentation.
Modified: trunk/docs/docbook/userguide/src/main/module/uddi.xml
===================================================================
--- trunk/docs/docbook/userguide/src/main/module/uddi.xml 2010-03-02 06:45:19 UTC (rev
532)
+++ trunk/docs/docbook/userguide/src/main/module/uddi.xml 2010-03-02 06:48:39 UTC (rev
533)
@@ -152,19 +152,17 @@
<para>The <emphasis>bindingDescription</emphasis> is set to
"BPEL Endpoint deployed by Riftsaw".</para>
- <para>Note that in soa-p-5 the jbossesb-registry.sar/esb.uddi.xml contains
a property
+ <para>Note that in SOA-P-5 the jbossesb-registry.sar/esb.uddi.xml contains
a property
<emphasis>juddi.seed.always</emphasis> which is set to
"true". This means that that it
is always trying to load the root seed data on startup of the server. It is
recommended
to turn this value to "false" once you are content with the UDDI Seed
Data.
</para>
- <warning>In JBossESB-4.7, the root seed data will only be installed if the
UDDI tables are
+ <warning>When running on JBossESB-4.7, the root seed data will only be
installed if the UDDI tables are
still empty. This means that you need to make sure that the jUDDI Root Seed Data
install process
did not run before installing RiftSaw. In other words, do not start JBossESB-4.7
before installing
- RiftSaw</warning>
+ RiftSaw.</warning>
-
-
</section>
</chapter>
Show replies by date