juddi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ks...@apache.org
Subject svn commit: r1135108 [3/3] - in /juddi/site/docs/3.0: devguide/html/ devguide/html_single/ devguide/pdf/ userguide/html/ userguide/html_single/ userguide/pdf/
Date Mon, 13 Jun 2011 12:40:44 GMT
Modified: juddi/site/docs/3.0/userguide/html_single/index.html
URL: http://svn.apache.org/viewvc/juddi/site/docs/3.0/userguide/html_single/index.html?rev=1135108&r1=1135107&r2=1135108&view=diff
==============================================================================
--- juddi/site/docs/3.0/userguide/html_single/index.html (original)
+++ juddi/site/docs/3.0/userguide/html_single/index.html Mon Jun 13 12:40:43 2011
@@ -7,7 +7,7 @@
         This document is a User Guide for jUDDI. jUDDI (pronounced "Judy") is an open
         source Java implementation of the Universal Description, Discovery, and
         Integration (UDDI v3) specification for Web Services.
-		</p></div></div></div><hr/></div><div class="toc"><dl><dt><span class="preface"><a href="#User_Guide-Preface">Preface</a></span></dt><dd><dl><dt><span class="section"><a href="#d0e83">1. Document Conventions</a></span></dt><dd><dl><dt><span class="section"><a href="#d0e93">1.1. Typographic Conventions</a></span></dt><dt><span class="section"><a href="#d0e309">1.2. Pull-quote Conventions</a></span></dt><dt><span class="section"><a href="#d0e328">1.3. Notes and Warnings</a></span></dt></dl></dd><dt><span class="section"><a href="#d0e348">2. We Need Feedback!</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-UDDI_Registry">1. UDDI Registry</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-UDDI_Registry-intro">1.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-UDDI_Registry">1.2. UDDI Registry</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Getting_Started">2. Getting Started</a></span></dt><dd><dl><dt><spa
 n class="section"><a href="#sect-what_should_I_download">2.1. What Should I Download?</a></span></dt><dt><span class="section"><a href="#sect-using_the_jar">2.2. Using the JAR</a></span></dt><dt><span class="section"><a href="#sect-using_the_WAR_file">2.3. Using the WAR File</a></span></dt><dt><span class="section"><a href="#sect-using_the_tomcat_bundle">2.4. Using the Tomcat Bundle</a></span></dt><dt><span class="section"><a href="#sect-Using_jUDDI_webservices">2.5. Using jUDDI Web Services</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Authentication">3. Authentication</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-authentication_intro">3.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-jUDDI_Authentication">3.2. jUDDI Authentication</a></span></dt><dt><span class="section"><a href="#sect-XMLDocAuthentication">3.3. XMLDocAuthentication</a></span></dt><dt><span class="section"><a href="#sect-CryptedXMLDocAuthenticat
 ion">3.4. CryptedXMLDocAuthentication</a></span></dt><dt><span class="section"><a href="#sect-JBoss_Authentication">3.5. JBoss Authentication</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-database_setup">4. Database Setup</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-derby_OOB">4.1. Derby Out-of-the-Box</a></span></dt><dt><span class="section"><a href="#sect-switch_to_mysql">4.2. Switch to MySQL</a></span></dt><dt><span class="section"><a href="#sect-switch_to_postres">4.3. Switch to Postgres</a></span></dt><dt><span class="section"><a href="#sect-switch_to_other_DB">4.4. Switch to &lt;other db&gt;</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-root_seed_data">5. Root Seed Data</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-root_seed_data_intro">5.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-seed_data_files">5.2. Seed Data Files</a></span></dt><dt><span class="section"><a hre
 f="#sect-tokens_in_the_seed_data">5.3. Tokens in the Seed Data</a></span></dt><dt><span class="section"><a href="#sect-custom_seed_data">5.4. Customer Seed Data</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-jUDDI_Configuration">6. jUDDI_Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-config_Introduction">6.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-config_authentication">6.2. Authentication</a></span></dt><dt><span class="section"><a href="#sect-startup">6.3. Startup</a></span></dt><dt><span class="section"><a href="#sect-config_queries">6.4. Queries</a></span></dt><dt><span class="section"><a href="#sect-config_proxy">6.5. Proxy Settings</a></span></dt><dt><span class="section"><a href="#sect-config_keygeneration">6.6. KeyGeneration</a></span></dt><dt><span class="section"><a href="#sect-config_subscription">6.7. Subscription</a></span></dt><dt><span class="section"><a href="#sect-config_transfer
 ">6.8. Transfer</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Using_jUDDI-Client">7. Using the jUDDI-Client</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-jUDDI_Client_intro">7.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-configuration">7.2. Configuration</a></span></dt><dt><span class="section"><a href="#sect-JAX-SW_transport">7.3. JAX-WS Transport</a></span></dt><dt><span class="section"><a href="#sect-RMI_transport">7.4. RMI Transport</a></span></dt><dt><span class="section"><a href="#sect-InVM_transport">7.5. InVM Transport</a></span></dt><dt><span class="section"><a href="#sect-dependencies">7.6. Dependencies</a></span></dt><dt><span class="section"><a href="#sect-sample_code">7.7. Sample Code</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-UDDI_annotations">8. UDDI Annotations</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-intro_annotations">8.1. Introduction</a></span></
 dt><dt><span class="section"><a href="#sect-UDDIService">8.2. UDDIService Annotation</a></span></dt><dt><span class="section"><a href="#sect-UDDIServiceBinding">8.3. UDDIServiceBinding Annotation</a></span></dt><dt><span class="section"><a href="#sect-WebServiceExample">8.4. WebService Example</a></span></dt><dt><span class="section"><a href="#sect-CategoryBag">8.5. CategoryBag Attribute</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-SimplePublish">9. Simple Publishing Using the jUDDI API</a></span></dt><dd><dl><dt><span class="section"><a href="#d0e1535">9.1. UDDI Data Model</a></span></dt><dt><span class="section"><a href="#d0e1561">9.2. jUDDI Additions to the Model</a></span></dt><dt><span class="section"><a href="#d0e1574">9.3. UDDI and jUDDI API</a></span></dt><dt><span class="section"><a href="#d0e1612">9.4. Getting Started</a></span></dt><dd><dl><dt><span class="section"><a href="#d0e1620">9.4.1. Simple Publishing Example</a></span></dt></dl></dd><d
 t><span class="section"><a href="#d0e1662">9.5. Conclusion</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Subscription">10. Subscription</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-subscription_intro">10.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-Two_node_example">10.2. Two node example setup: Sales and Marketing</a></span></dt><dt><span class="section"><a href="#sect-deploy_HelloSales_service">10.3. Deploy the HelloSales Service</a></span></dt><dt><span class="section"><a href="#sect-config_user_create_subscription">10.4. Configure a user to create Subscriptions</a></span></dt><dt><span class="section"><a href="#sect-synchronous_notifications">10.5. Synchronous Notifications</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Administration">11. Administration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-admin_intro">11.1. Introduction</a></span></dt><dt><span class="section
 "><a href="#sect-changing_listener_port">11.2. Changing the Listener Port</a></span></dt><dt><span class="section"><a href="#sect-changing_oracle_sequence_name">11.3. Changing the Oracle Sequence name</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-deployjboss">12. Deploying to JBoss 5.1.0.GA</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-deployjboss">12.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-juddi-war">12.2. Add juddiv3.war</a></span></dt><dt><span class="section"><a href="#sect-datasource">12.3. Configure Datasource</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-deployglassfish">13. Deploying to Glassfish 2.1.1</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-deployglassfish">13.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-glassfish-jars">13.2. Glassfish jars</a></span></dt><dt><span class="section"><a href="#sect-juddi-ds">13.3. Configure the JU
 DDI datasource</a></span></dt><dt><span class="section"><a href="#sect-glassfish-juddi-war">13.4. Add juddiv3-cxf.war</a></span></dt><dt><span class="section"><a href="#sect-run">13.5. Run juddi</a></span></dt></dl></dd><dt><span class="appendix"><a href="#appe-Publican-Revision_History">A. Revision History</a></span></dt></dl></div><div class="preface" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="User_Guide-Preface"/>Preface</h2></div></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="d0e83"/>1. Document Conventions</h2></div></div></div><p>
+		</p></div></div></div><hr/></div><div class="toc"><dl><dt><span class="preface"><a href="#User_Guide-Preface">Preface</a></span></dt><dd><dl><dt><span class="section"><a href="#d0e83">1. Document Conventions</a></span></dt><dd><dl><dt><span class="section"><a href="#d0e93">1.1. Typographic Conventions</a></span></dt><dt><span class="section"><a href="#d0e309">1.2. Pull-quote Conventions</a></span></dt><dt><span class="section"><a href="#d0e328">1.3. Notes and Warnings</a></span></dt></dl></dd><dt><span class="section"><a href="#d0e348">2. We Need Feedback!</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-UDDI_Registry">1. UDDI Registry</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-UDDI_Registry-intro">1.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-UDDI_Registry">1.2. UDDI Registry</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Getting_Started">2. Getting Started</a></span></dt><dd><dl><dt><spa
 n class="section"><a href="#sect-what_should_I_download">2.1. What Should I Download?</a></span></dt><dt><span class="section"><a href="#sect-using_the_jar">2.2. Using the JAR</a></span></dt><dt><span class="section"><a href="#sect-using_the_WAR_file">2.3. Using the WAR File</a></span></dt><dt><span class="section"><a href="#sect-using_the_tomcat_bundle">2.4. Using the Tomcat Bundle</a></span></dt><dt><span class="section"><a href="#sect-Using_jUDDI_webservices">2.5. Using jUDDI Web Services</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Authentication">3. Authentication</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-authentication_intro">3.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-jUDDI_Authentication">3.2. jUDDI Authentication</a></span></dt><dt><span class="section"><a href="#sect-XMLDocAuthentication">3.3. XMLDocAuthentication</a></span></dt><dt><span class="section"><a href="#sect-CryptedXMLDocAuthenticat
 ion">3.4. CryptedXMLDocAuthentication</a></span></dt><dt><span class="section"><a href="#sect-LDAP_Authentication">3.5. LDAP Authentication</a></span></dt><dt><span class="section"><a href="#sect-JBoss_Authentication">3.6. JBoss Authentication</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-database_setup">4. Database Setup</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-derby_OOB">4.1. Derby Out-of-the-Box</a></span></dt><dt><span class="section"><a href="#sect-switch_to_mysql">4.2. Switch to MySQL</a></span></dt><dt><span class="section"><a href="#sect-switch_to_postres">4.3. Switch to Postgres</a></span></dt><dt><span class="section"><a href="#sect-switch_to_oracle">4.4. Switch to Oracle</a></span></dt><dt><span class="section"><a href="#sect-switch_to_hsql">4.5. Switch to HSQL</a></span></dt><dt><span class="section"><a href="#sect-switch_to_other_DB">4.6. Switch to &lt;other db&gt;</a></span></dt></dl></dd><dt><span class="chapter"><a h
 ref="#chap-root_seed_data">5. Root Seed Data</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-root_seed_data_intro">5.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-seed_data_files">5.2. Seed Data Files</a></span></dt><dt><span class="section"><a href="#sect-tokens_in_the_seed_data">5.3. Token in the Seed Data</a></span></dt><dt><span class="section"><a href="#sect-custom_seed_data">5.4. Customer Seed Data</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-jUDDI_Configuration">6. jUDDI_Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-config_Introduction">6.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-config_authentication">6.2. Authentication</a></span></dt><dt><span class="section"><a href="#sect-startup">6.3. Startup</a></span></dt><dt><span class="section"><a href="#sect-config_queries">6.4. Queries</a></span></dt><dt><span class="section"><a href="#sect-config_p
 roxy">6.5. Proxy Settings</a></span></dt><dt><span class="section"><a href="#sect-config_keygeneration">6.6. KeyGeneration</a></span></dt><dt><span class="section"><a href="#sect-config_subscription">6.7. Subscription</a></span></dt><dt><span class="section"><a href="#sect-config_transfer">6.8. Transfer</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Using_jUDDI-Client">7. Using the jUDDI-Client</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-jUDDI_Client_intro">7.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-configuration">7.2. Configuration</a></span></dt><dt><span class="section"><a href="#sect-JAX-SW_transport">7.3. JAX-WS Transport</a></span></dt><dt><span class="section"><a href="#sect-RMI_transport">7.4. RMI Transport</a></span></dt><dt><span class="section"><a href="#sect-InVM_transport">7.5. InVM Transport</a></span></dt><dt><span class="section"><a href="#sect-dependencies">7.6. Dependencies</a></span></dt
 ><dt><span class="section"><a href="#sect-sample_code">7.7. Sample Code</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-UDDI_annotations">8. UDDI Annotations</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-intro_annotations">8.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-UDDIService">8.2. UDDIService Annotation</a></span></dt><dt><span class="section"><a href="#sect-UDDIServiceBinding">8.3. UDDIServiceBinding Annotation</a></span></dt><dt><span class="section"><a href="#sect-WebServiceExample">8.4. WebService Example</a></span></dt><dt><span class="section"><a href="#sect-CategoryBag">8.5. CategoryBag Attribute</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-SimplePublish">9. Simple Publishing Using the jUDDI API</a></span></dt><dd><dl><dt><span class="section"><a href="#d0e1641">9.1. UDDI Data Model</a></span></dt><dt><span class="section"><a href="#d0e1667">9.2. jUDDI Additions to the Model</a><
 /span></dt><dt><span class="section"><a href="#d0e1680">9.3. UDDI and jUDDI API</a></span></dt><dt><span class="section"><a href="#d0e1718">9.4. Getting Started</a></span></dt><dd><dl><dt><span class="section"><a href="#d0e1726">9.4.1. Simple Publishing Example</a></span></dt></dl></dd><dt><span class="section"><a href="#d0e1768">9.5. Conclusion</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Subscription">10. Subscription</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-subscription_intro">10.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-Two_node_example">10.2. Two node example setup: Sales and Marketing</a></span></dt><dt><span class="section"><a href="#sect-deploy_HelloSales_service">10.3. Deploy the HelloSales Service</a></span></dt><dt><span class="section"><a href="#sect-config_user_create_subscription">10.4. Configure a user to create Subscriptions</a></span></dt><dt><span class="section"><a href="#sect-synchr
 onous_notifications">10.5. Synchronous Notifications</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Administration">11. Administration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-admin_intro">11.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-changing_listener_port">11.2. Changing the Listener Port</a></span></dt><dt><span class="section"><a href="#sect-changing_oracle_sequence_name">11.3. Changing the Oracle Sequence name</a></span></dt><dt><span class="section"><a href="#sect-persistence">11.4. Persistence</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-deployjboss">12. Deploying to JBoss 6.0.0.GA</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-deployjboss">12.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-juddi-war">12.2. Add juddiv3.war</a></span></dt><dt><span class="section"><a href="#sect-web.xml">12.3. Change web.xml</a></span></dt><dt><span class
 ="section"><a href="#sect-datasource">12.4. Configure Datasource</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-deployglassfish">13. Deploying to Glassfish 2.1.1</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-deployglassfish">13.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-glassfish-jars">13.2. Glassfish jars</a></span></dt><dt><span class="section"><a href="#sect-juddi-ds">13.3. Configure the JUDDI datasource</a></span></dt><dt><span class="section"><a href="#sect-glassfish-juddi-war">13.4. Add juddiv3-cxf.war</a></span></dt><dt><span class="section"><a href="#sect-run">13.5. Run juddi</a></span></dt></dl></dd><dt><span class="appendix"><a href="#appe-Publican-Revision_History">A. Revision History</a></span></dt></dl></div><div class="preface" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="User_Guide-Preface"/>Preface</h2></div></div></div><div class="section" lang="en-US"><div class="tit
 lepage"><div><div><h2 class="title"><a id="d0e83"/>1. Document Conventions</h2></div></div></div><p>
 	This manual uses several conventions to highlight certain words and phrases and draw
     attention to specific pieces of information.
     </p><p>
@@ -252,7 +252,7 @@ books_tests  Desktop1  downloads      im
         </p><div class="figure"><a id="fig-UDDI_services_overview"/><div class="figure-contents"><div class="mediaobject"><img src="images/UDDI_services_overview.png" alt="UDDI Services Overview"/></div></div><p class="title"><b>Figure 2.2. UDDI Services Overview</b></p></div><br class="figure-break"/><p>
         The services page shows you the available endpoints and methods available. Using
         any SOAP client, you should be able to send some sample requests to jUDDI to test:
-        </p><div class="figure"><a id="fig-getting_authToken_soapUI"/><div class="figure-contents"><div class="mediaobject"><img src="images/authToken_SoapUI.png" alt="Getting an authToken using SoapUI"/></div></div><p class="title"><b>Figure 2.3. Getting an authToken using SoapUI</b></p></div><br class="figure-break"/></div></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="chap-Authentication"/>Chapter 3. Authentication</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-authentication_intro">3.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-jUDDI_Authentication">3.2. jUDDI Authentication</a></span></dt><dt><span class="section"><a href="#sect-XMLDocAuthentication">3.3. XMLDocAuthentication</a></span></dt><dt><span class="section"><a href="#sect-CryptedXMLDocAuthentication">3.4. CryptedXMLDocAuthentication</a></span></dt><dt><span class="section"><a href="#sec
 t-JBoss_Authentication">3.5. JBoss Authentication</a></span></dt></dl></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-authentication_intro"/>3.1. Introduction</h2></div></div></div><p>
+        </p><div class="figure"><a id="fig-getting_authToken_soapUI"/><div class="figure-contents"><div class="mediaobject"><img src="images/authToken_SoapUI.png" alt="Getting an authToken using SoapUI"/></div></div><p class="title"><b>Figure 2.3. Getting an authToken using SoapUI</b></p></div><br class="figure-break"/></div></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="chap-Authentication"/>Chapter 3. Authentication</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-authentication_intro">3.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-jUDDI_Authentication">3.2. jUDDI Authentication</a></span></dt><dt><span class="section"><a href="#sect-XMLDocAuthentication">3.3. XMLDocAuthentication</a></span></dt><dt><span class="section"><a href="#sect-CryptedXMLDocAuthentication">3.4. CryptedXMLDocAuthentication</a></span></dt><dt><span class="section"><a href="#sec
 t-LDAP_Authentication">3.5. LDAP Authentication</a></span></dt><dt><span class="section"><a href="#sect-JBoss_Authentication">3.6. JBoss Authentication</a></span></dt></dl></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-authentication_intro"/>3.1. Introduction</h2></div></div></div><p>
         In order to enforce proper write access to jUDDI, each request to jUDDI needs a
         valid <code class="classname">authToken</code>. Note that read access is not restricted
         and therefore queries into the registries are not restricted.
@@ -369,7 +369,23 @@ juddi.cryptor = org.apache.juddi.cryptor
         The authenticate phase checks that the user id and password match a value in the XML
         file. The identify phase simply uses the user id to populate a new
         <code class="classname">UddiEntityPublisher</code>.
-        </p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-JBoss_Authentication"/>3.5. JBoss Authentication</h2></div></div></div><p>
+        </p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-LDAP_Authentication"/>3.5. LDAP Authentication</h2></div></div></div><p>
+	<code class="classname">LdapSimpleAuthenticator</code> provides a way of authenticating
+	users using Ldap simple authentication.    It is fairly rudimentary and more 
+	LDAP integration is planned in the future, but this class allows you to authenticate
+	a user based on an LDAP prinicipal, provided that the principal and the juddi publisher ID
+	are the same.
+        </p><p>
+        To use this class you must add the following properties to the
+        <code class="filename">juddi.properties</code> file:
+        </p><pre class="programlisting">juddi.auth=org.apache.juddi.auth.LdapSimpleAuthenticator
+juddi.auth.url=ldap://localhost:389
+</pre><p>
+	The <code class="classname">juddi.auth.url</code> property configures the
+        <code class="classname">LdapSimpleAuthenticator</code> class so that it knows where the LDAP
+	server resides.     Future work is planned in this area to use the LDAP uid rather than
+	the LDAP principal as the default publisher id.
+        </p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-JBoss_Authentication"/>3.6. JBoss Authentication</h2></div></div></div><p>
         Finally is it possible to hook up to third party credential stores. If for example
         jUDDI is deployed to the JBoss Application server it is possible to hook up to
         it's authentication machinery. The <code class="classname">JBossAuthenticator</code> class
@@ -392,7 +408,7 @@ juddi.securityDomain=java:/jaas/other</p
         gets bound to the server JNDI tree with name
         <code class="code">java:/jaas/&lt;application-policy-name&gt;</code>. If a lookup refers to a
         non existent application policy it defaults to a policy named other.
-        </p></div></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="chap-database_setup"/>Chapter 4. Database Setup</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-derby_OOB">4.1. Derby Out-of-the-Box</a></span></dt><dt><span class="section"><a href="#sect-switch_to_mysql">4.2. Switch to MySQL</a></span></dt><dt><span class="section"><a href="#sect-switch_to_postres">4.3. Switch to Postgres</a></span></dt><dt><span class="section"><a href="#sect-switch_to_other_DB">4.4. Switch to &lt;other db&gt;</a></span></dt></dl></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-derby_OOB"/>4.1. Derby Out-of-the-Box</h2></div></div></div><p>
+        </p></div></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="chap-database_setup"/>Chapter 4. Database Setup</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-derby_OOB">4.1. Derby Out-of-the-Box</a></span></dt><dt><span class="section"><a href="#sect-switch_to_mysql">4.2. Switch to MySQL</a></span></dt><dt><span class="section"><a href="#sect-switch_to_postres">4.3. Switch to Postgres</a></span></dt><dt><span class="section"><a href="#sect-switch_to_oracle">4.4. Switch to Oracle</a></span></dt><dt><span class="section"><a href="#sect-switch_to_hsql">4.5. Switch to HSQL</a></span></dt><dt><span class="section"><a href="#sect-switch_to_other_DB">4.6. Switch to &lt;other db&gt;</a></span></dt></dl></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-derby_OOB"/>4.1. Derby Out-of-the-Box</h2></div></div></div><p>
         By default jUDDI uses an embedded Derby database. This allows us to build a 
         downloadable distribution that works out-of-the-box, without having to do any 
         database setup work. We recommend switching to an enterprise-level database 
@@ -548,10 +564,52 @@ postgres= GRANT ALL PRIVILEGES ON DATABA
 &lt;property name="hibernate.dialect" value="org.hibernate.dialect.PostgreSQLDialect"/&gt;</pre><p>
         Be sure to have <code class="filename">postgresql-8.3-604.jdbc4.jar</code> in the
         <code class="filename">lib</code> folder!
-        </p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-switch_to_other_DB"/>4.4. Switch to &lt;other db&gt;</h2></div></div></div><p>
+        </p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-switch_to_oracle"/>4.4. Switch to Oracle</h2></div></div></div><p>
+        To switch over to Oracle you need to add the oracle driver (i.e. the<code class="filename">classes12.jar</code>) to the 
+        classpath and you will need to edit the <code class="filename">persistence.xml</code>
+        </p><pre class="programlisting">&lt;property name="hibernate.dialect" value="org.hibernate.dialect.Oracle10gDialect"/&gt;</pre><p>
+        To create a Oracle database name juddiv3 with the ultimate in minimalism use
+        </p><pre class="programlisting">sqlplus&gt; create database juddiv3;</pre><p>
+        then you probably want to switch to a user which is a bit less potent then 'root' and set the appropriate password.
+        </p><div xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="warning"><h2>Warning</h2><p>
+				Tomcat copies the context.xml to conf/CATALINA/localhost/juddiv3.xml, and if you update the context.xml it may not update this copy. 
+				You should simply delete the juddiv3.xml file after updating the context.xml.
+			</p></div><p>
+		Please check the <a class="xref" href="#sect-changing_oracle_sequence_name" title="11.3. Changing the Oracle Sequence name">Section 11.3, “Changing the Oracle Sequence name”</a> if you want to change the Oracle Sequence name.
+		</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-switch_to_hsql"/>4.5. Switch to HSQL</h2></div></div></div><p>First make sure you have a running hsqldb. For a standalone server startup use:</p><pre class="programlisting">
+		java -cp hsqldb.jar org.hsqldb.server.Server --port 1747 --database.0 file:juddi --dbname.0 juddi
+		</pre><p>Next, connect the client manager to this instance using:</p><pre class="programlisting">
+		java -classpath hsqldb.jar org.hsqldb.util.DatabaseManagerSwing --driver org.hsqldb.jdbcDriver --url jdbc:hsqldb:hsql://localhost:1747/juddi  -user sa
+		</pre><p>and create the juddi user:</p><pre class="programlisting">
+		CREATE USER JUDDI PASSWORD "password"  ADMIN;
+		CREATE SCHEMA JUDDI AUTHORIZATION JUDDI;
+		SET DATABASE DEFAULT INITIAL SCHEMA JUDDI;
+		ALTER USER juddi set initial schema juddi;
+		</pre><p>From now on, one can connect as JUDDI user to that database and the database is now ready to go.</p><p>
+        To switch over to HSQL you need to add the hsql driver (i.e. The
+        <code class="filename">hsqldb.jar</code>) to the classpath and you will
+        need to edit the <code class="filename">persistence.xml</code>
+        </p><pre class="programlisting">&lt;property name="hibernate.dialect" value="org.hibernate.dialect.HSQLDialect"/&gt;</pre><p>
+        and the datasource. For tomcat you the <code class="filename">context.xml</code> should
+        look something like
+        </p><pre class="programlisting">&lt;?xml version="1.0" encoding="UTF-8"?&gt;
+&lt;Context&gt;
+    &lt;WatchedResource&gt;WEB-INF/web.xml&lt;/WatchedResource&gt;
+    &lt;!-- HSQL data source --&gt;
+    &lt;Resource name="jdbc/JuddiDS" auth="Container"
+            type="javax.sql.DataSource" username="JUDDI" password="password"
+            driverClassName="org.hsqldb.jdbcDriver"
+            url="jdbc:hsqldb:hsql://localhost:1747/juddi"
+            maxActive="8"
+            /&gt;
+&lt;/Context&gt;</pre><div xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="warning"><h2>Warning</h2><p>
+            Tomcat copies the <code class="filename">context.xml</code> to <code class="filename">conf/CATALINA/localhost/juddiv3.xml</code>, and if
+            you update the <code class="filename">context.xml</code> it may not update this copy. You should simply
+            delete the <code class="filename">juddiv3.xml</code> file after updating the <code class="filename">context.xml</code>.
+            </p></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-switch_to_other_DB"/>4.6. Switch to &lt;other db&gt;</h2></div></div></div><p>
         If you use another database, please document, and send us what you had to change
         to make it work and we will include it here.
-        </p></div></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="chap-root_seed_data"/>Chapter 5. Root Seed Data</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-root_seed_data_intro">5.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-seed_data_files">5.2. Seed Data Files</a></span></dt><dt><span class="section"><a href="#sect-tokens_in_the_seed_data">5.3. Tokens in the Seed Data</a></span></dt><dt><span class="section"><a href="#sect-custom_seed_data">5.4. Customer Seed Data</a></span></dt></dl></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-root_seed_data_intro"/>5.1. Introduction</h2></div></div></div><p>
+        </p></div></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="chap-root_seed_data"/>Chapter 5. Root Seed Data</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-root_seed_data_intro">5.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-seed_data_files">5.2. Seed Data Files</a></span></dt><dt><span class="section"><a href="#sect-tokens_in_the_seed_data">5.3. Token in the Seed Data</a></span></dt><dt><span class="section"><a href="#sect-custom_seed_data">5.4. Customer Seed Data</a></span></dt></dl></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-root_seed_data_intro"/>5.1. Introduction</h2></div></div></div><p>
         As of UDDI v3, each registry need to have a <code class="literal">“root”</code> publisher.
         The root publisher is the owner of the UDDI services (inquiry, publication, etc).
         There can only be one root publisher per node. JUDDI ships some default seed data
@@ -672,12 +730,15 @@ postgres= GRANT ALL PRIVILEGES ON DATABA
     &lt;/businessServices&gt;
 &lt;/businessEntity&gt;</pre><p>
         Note that the seeding process only kicks off if no publishers exist in the
-        database. So this will only work with a clean database.
-        </p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-tokens_in_the_seed_data"/>5.3. Tokens in the Seed Data</h2></div></div></div><p>
+        database. So this will only work with a clean database, unless you set
+        <code class="literal">juddi.seed.always</code> to true. Then it will re-apply all files with
+        the exception of the root data files. Note that this can lead to losing data that
+        was added to entities that are re-seeded, since data is not merged.
+        </p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-tokens_in_the_seed_data"/>5.3. Token in the Seed Data</h2></div></div></div><p>
         You may have noticed the tokens in the <code class="filename">root_BusinessEntity.xml</code> 
-        file (<code class="literal">${juddi.server.name}</code> and
-        <code class="literal">${juddi.server.port}</code> ) . The value of these tokens can set in
-        the <code class="filename">juddiv3.properties</code> file, and you can add your own tokens.
+        file (<code class="literal">${juddi.server.baseurl}</code>. The value of this tokens can set in
+        the <code class="filename">juddiv3.properties</code> file. The value substitution takes place
+        at runtime, so that different nodes can do the substitution  with their own value if needed.
         </p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-custom_seed_data"/>5.4. Customer Seed Data</h2></div></div></div><p>
         In your deployment you probably do not want to use the Seed Data shipped with the
         default jUDDI install. The easiest way to overwrite this data is to add it to a
@@ -720,7 +781,9 @@ juddi.root.publisher=root
 		</p><pre class="programlisting">#
 juddi.seed.always=false
 </pre><p>
-		Forces seeding of the jUDDI data.
+		Forces seeding of the jUDDI data. This will re-apply all files with
+        the exception of the root data files. Note that this can lead to losing data that
+        was added to the entities that are re-seeded, since data is not merged.
 		</p><pre class="programlisting">#
 juddi.load.install.data=false
 </pre><p>
@@ -1017,11 +1080,11 @@ juddi.transfer.expiration.days=3
         </p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-UDDIService"/>8.2. UDDIService Annotation</h2></div></div></div><p>
         The UDDIService annotation is used to register a service under an already existing business in the Registry. The
         annotation should be added at the class level of the java class.
-        </p><div class="table"><a id="d0e1371"/><p class="title"><b>Table 8.1. UDDIService attributes</b></p><div class="table-contents"><table summary="UDDIService attributes" border="1"><colgroup><col/><col/><col/></colgroup><thead><tr><th>attribute</th><th>description</th><th>required</th></tr></thead><tbody><tr><td>serviceName</td><td>The name of the service, by default the clerk will use the one name specified in the WebService annotation</td><td>no</td></tr><tr><td>description</td><td>Human readable description of the service</td><td>yes</td></tr><tr><td>serviceKey</td><td>UDDI v3 Key of the Service</td><td>yes</td></tr><tr><td>businessKey</td><td>UDDI v3 Key of the Business that should own this Service. The business should exist in the registry at time of registration</td><td>yes</td></tr><tr><td>lang</td><td>Language locale which will be used for the name and description, defaults to "en" if omitted</td><td>no</td></tr><tr><td>categoryBag</td><td>Definition of 
 a CategoryBag, see below for details</td><td>no</td></tr></tbody></table></div></div><p><br class="table-break"/>
+        </p><div class="table"><a id="d0e1477"/><p class="title"><b>Table 8.1. UDDIService attributes</b></p><div class="table-contents"><table summary="UDDIService attributes" border="1"><colgroup><col/><col/><col/></colgroup><thead><tr><th>attribute</th><th>description</th><th>required</th></tr></thead><tbody><tr><td>serviceName</td><td>The name of the service, by default the clerk will use the one name specified in the WebService annotation</td><td>no</td></tr><tr><td>description</td><td>Human readable description of the service</td><td>yes</td></tr><tr><td>serviceKey</td><td>UDDI v3 Key of the Service</td><td>yes</td></tr><tr><td>businessKey</td><td>UDDI v3 Key of the Business that should own this Service. The business should exist in the registry at time of registration</td><td>yes</td></tr><tr><td>lang</td><td>Language locale which will be used for the name and description, defaults to "en" if omitted</td><td>no</td></tr><tr><td>categoryBag</td><td>Definition of 
 a CategoryBag, see below for details</td><td>no</td></tr></tbody></table></div></div><p><br class="table-break"/>
         </p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-UDDIServiceBinding"/>8.3. UDDIServiceBinding Annotation</h2></div></div></div><p>
             The UDDIServiceBinding annotation is used to register a BindingTemplate to the UDDI registry. This annotation
             cannot be used by itself. It needs to go along side a UDDIService annotation.
-        	</p><div class="table"><a id="d0e1436"/><p class="title"><b>Table 8.2. UDDIServiceBinding attributes</b></p><div class="table-contents"><table summary="UDDIServiceBinding attributes" border="1"><colgroup><col/><col/><col/></colgroup><thead><tr><th>attribute</th><th>description</th><th>required</th></tr></thead><tbody><tr><td>bindingKey</td><td>UDDI v3 Key of the ServiceBinding</td><td>yes</td></tr><tr><td>description</td><td>Human readable description of the service</td><td>yes</td></tr><tr><td>accessPointType</td><td>UDDI v3 AccessPointType, defaults to wsdlDeployment if omitted</td><td>no</td></tr><tr><td>accessPoint</td><td>Endpoint reference</td><td>yes</td></tr><tr><td>lang</td><td>Language locale which will be used for the name and description, defaults to "en" if omitted</td><td>no</td></tr><tr><td>tModelKeys</td><td>Comma-separated list of tModelKeys key references</td><td>no</td></tr><tr><td>categoryBag</td><td>Definition of a CategoryBag, see below f
 or further details</td><td>no</td></tr></tbody></table></div></div><p><br class="table-break"/>
+        	</p><div class="table"><a id="d0e1542"/><p class="title"><b>Table 8.2. UDDIServiceBinding attributes</b></p><div class="table-contents"><table summary="UDDIServiceBinding attributes" border="1"><colgroup><col/><col/><col/></colgroup><thead><tr><th>attribute</th><th>description</th><th>required</th></tr></thead><tbody><tr><td>bindingKey</td><td>UDDI v3 Key of the ServiceBinding</td><td>yes</td></tr><tr><td>description</td><td>Human readable description of the service</td><td>yes</td></tr><tr><td>accessPointType</td><td>UDDI v3 AccessPointType, defaults to wsdlDeployment if omitted</td><td>no</td></tr><tr><td>accessPoint</td><td>Endpoint reference</td><td>yes</td></tr><tr><td>lang</td><td>Language locale which will be used for the name and description, defaults to "en" if omitted</td><td>no</td></tr><tr><td>tModelKeys</td><td>Comma-separated list of tModelKeys key references</td><td>no</td></tr><tr><td>categoryBag</td><td>Definition of a CategoryBag, see below f
 or further details</td><td>no</td></tr></tbody></table></div></div><p><br class="table-break"/>
         </p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-WebServiceExample"/>8.4. WebService Example</h2></div></div></div><p>
         The annotations can be used on any class that defines a service. Here they are added to a WebService, a POJO with a 
         JAX-WS 'WebService' annotation.
@@ -1080,11 +1143,11 @@ public class HelloWorldImpl implements H
                      "keyedReference=keyName=uddi-org:types:wsdl2;keyValue=wsdlDeployment2;" +
                      "tModelKey=uddi:uddi.org:categorization:types2",
         </pre><p>
-        </p></div></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="chap-SimplePublish"/>Chapter 9. Simple Publishing Using the jUDDI API</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#d0e1535">9.1. UDDI Data Model</a></span></dt><dt><span class="section"><a href="#d0e1561">9.2. jUDDI Additions to the Model</a></span></dt><dt><span class="section"><a href="#d0e1574">9.3. UDDI and jUDDI API</a></span></dt><dt><span class="section"><a href="#d0e1612">9.4. Getting Started</a></span></dt><dd><dl><dt><span class="section"><a href="#d0e1620">9.4.1. Simple Publishing Example</a></span></dt></dl></dd><dt><span class="section"><a href="#d0e1662">9.5. Conclusion</a></span></dt></dl></div><p>
+        </p></div></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="chap-SimplePublish"/>Chapter 9. Simple Publishing Using the jUDDI API</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#d0e1641">9.1. UDDI Data Model</a></span></dt><dt><span class="section"><a href="#d0e1667">9.2. jUDDI Additions to the Model</a></span></dt><dt><span class="section"><a href="#d0e1680">9.3. UDDI and jUDDI API</a></span></dt><dt><span class="section"><a href="#d0e1718">9.4. Getting Started</a></span></dt><dd><dl><dt><span class="section"><a href="#d0e1726">9.4.1. Simple Publishing Example</a></span></dt></dl></dd><dt><span class="section"><a href="#d0e1768">9.5. Conclusion</a></span></dt></dl></div><p>
     One of the most common requests we get on the message board is “How do I publish a service using jUDDI?” This question holds a wide berth, as it can result anywhere from not understanding the UDDI data model, to confusion around how jUDDI is set up, to the
     order of steps required to publish artifacts in the registry, to general use of the API – and everything in between. This article will attempt to answer this “loaded” question and, while not going into too much detail, will hopefully clear some of the
     confusion about publishing into the jUDDI registry.
-  </p><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="d0e1535"/>9.1. UDDI Data Model</h2></div></div></div><p>
+  </p><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="d0e1641"/>9.1. UDDI Data Model</h2></div></div></div><p>
       Before you begin publishing artifacts, you need to know exactly how to break down your data into the UDDI model. This topic is covered extensively in the specification, particularly in section 3, so I only want to gloss over some for details. Readers
       interested in more extensive coverage should most definitely take a look at the UDDI specification.
     </p><p>
@@ -1106,7 +1169,7 @@ public class HelloWorldImpl implements H
     </p><p>
       Binding Templates, as mentioned above, give the details about the technical specification of the service. This can be as simple as just providing the service’s access point, to providing the location of the service WSDL to more complicated scenarios to
       breaking down the technical details of the WSDL (when used in concert with tModels). Once again, getting into these scenarios is beyond the scope of this article but may be the subject of future articles.
-    </p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="d0e1561"/>9.2. jUDDI Additions to the Model</h2></div></div></div><p>
+    </p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="d0e1667"/>9.2. jUDDI Additions to the Model</h2></div></div></div><p>
       Out of the box, jUDDI provides some additional structure to the data model described in the specification. Primarily, this is the concept of the Publisher.
     </p><p>
       The UDDI specification talks about ownership of the entities that are published within the registry, but makes no mention about how ownership should be handled. Basically, it is left up to the particular implementation to decide how to handle “users” that
@@ -1121,7 +1184,7 @@ public class HelloWorldImpl implements H
     </p><p>
       One quick note: ownership is essentially assigned to a given registry entity by using its “authorizedName” field. The “authorizedName” field is defined in the specification in the operationalInfo structure which keeps track of operational info for each
       entity.
-    </p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="d0e1574"/>9.3. UDDI and jUDDI API</h2></div></div></div><p>
+    </p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="d0e1680"/>9.3. UDDI and jUDDI API</h2></div></div></div><p>
       Knowing the UDDI data model is all well and good. But to truly interact with the registry, you need to know how the UDDI API is structured and how jUDDI implements this API. The UDDI API is covered in great detail in chapter 5 of the specification but will be
       summarized here.
     </p><p>
@@ -1150,11 +1213,11 @@ public class HelloWorldImpl implements H
     </p><p>
       One final note, jUDDI defines its own API set. This API set contains methods that deal with handling Publishers as well as other useful maintenance functions (mostly related to jUDDI’s subscription model). This API set is obviously proprietary to jUDDI and
       therefore doesn’t conform to the UDDI specification.
-    </p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="d0e1612"/>9.4. Getting Started</h2></div></div></div><p>
+    </p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="d0e1718"/>9.4. Getting Started</h2></div></div></div><p>
       Now that we’ve covered the basics of the data model and API sets, it’s time to get started with the publishing sample. The first thing that must happen is to get the jUDDI server up and running. Please refer to this
       <a class="ulink" href="http://apachejuddi.blogspot.com/2010/02/getting-started-with-juddi-v3.html">article</a>
       that explains how to start the jUDDI server.
-    </p><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="d0e1620"/>9.4.1. Simple Publishing Example</h3></div></div></div><p>
+    </p><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="d0e1726"/>9.4.1. Simple Publishing Example</h3></div></div></div><p>
         We will now go over the “simple-publish” example found in the documentation. This sample expands upon the HelloWorld example in that after retrieving an authentication token, a Publisher, BusinessEntity and BusinessService are published to the registry.
       </p><p>
         The sample consists of only one class: SimplePublish. Let’s start by taking a look at the constructor:
@@ -1271,7 +1334,7 @@ public class HelloWorldImpl implements H
         You can, of course, customize all of this, but that is left for another article.  The second important point is that when the BusinessService is saved, I’ve had to explicitly set its parent business key (retrieved from previous call saving the 
         business).  This is a necessary step when the service is saved in an independent call like this.  Otherwise you would get an error because jUDDI won’t know where to find the parent entity.  I could have added this service to the BusinessEntity’s service 
         collection and saved it with the call to saveBusiness.  In that scenario I would not have to set the parent business key.
-      </p></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="d0e1662"/>9.5. Conclusion</h2></div></div></div><p>
+      </p></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="d0e1768"/>9.5. Conclusion</h2></div></div></div><p>
       That does it for this article.  Hopefully I managed to clear some of the confusion around the open-ended question, “How do I publish a service using jUDDI?”.
     </p></div></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="chap-Subscription"/>Chapter 10. Subscription</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-subscription_intro">10.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-Two_node_example">10.2. Two node example setup: Sales and Marketing</a></span></dt><dt><span class="section"><a href="#sect-deploy_HelloSales_service">10.3. Deploy the HelloSales Service</a></span></dt><dt><span class="section"><a href="#sect-config_user_create_subscription">10.4. Configure a user to create Subscriptions</a></span></dt><dt><span class="section"><a href="#sect-synchronous_notifications">10.5. Synchronous Notifications</a></span></dt></dl></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-subscription_intro"/>10.1. Introduction</h2></div></div></div><p>
         Subscriptions come to play in a multi-registry setup. Within your company you may
@@ -1308,7 +1371,7 @@ juddi.server.port=8080</pre></li><li><p>
                 <a class="xref" href="#chap-root_seed_data" title="Chapter 5. Root Seed Data">Chapter 5, <i>Root Seed Data</i></a>)
                 </p><pre class="screen">bin/startup.sh</pre></li><li><p>
                 Open your browser to <a class="ulink" href="http://sales:8080/juddiv3">http://sales:8080/juddiv3</a>.  You should see:
-                </p><div class="figure"><a id="fig-sales_node_installation"/><div class="figure-contents"><div class="mediaobject"><img src="images/sales_node_installation.png" alt="Sales Node Installation"/></div></div><p class="title"><b>Figure 10.1. Sales Node Installation</b></p></div><br class="figure-break"/></li></ol></div><div xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="procedure"><a id="d0e1743"/><p class="title"><b>Procedure 10.2. Setup Node 2: Marketing</b></p><ol class="1"><li><p>
+                </p><div class="figure"><a id="fig-sales_node_installation"/><div class="figure-contents"><div class="mediaobject"><img src="images/sales_node_installation.png" alt="Sales Node Installation"/></div></div><p class="title"><b>Figure 10.1. Sales Node Installation</b></p></div><br class="figure-break"/></li></ol></div><div xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="procedure"><a id="d0e1849"/><p class="title"><b>Procedure 10.2. Setup Node 2: Marketing</b></p><ol class="1"><li><p>
                 Create <code class="filename">juddi_custom_install_data</code>.
                 </p><pre class="screen">cd juddiv3/WEB-INF/classes
 mv RENAME4MARKETING_juddi_custom_install_data juddi_custom_install_data</pre></li><li><p>
@@ -1514,7 +1577,7 @@ juddi.server.port=8080</pre></li><li><p>
         import the HelloWorld subscription information, as well as the sales business. So
         after a successful sync you should now see three businesses in the Browser Portlet
         of the marketing node, see <a class="xref" href="#fig-registry_info_HelloWorld" title="Figure 10.11. The registry info of the HelloWorld Service information was imported by the subscription mechanism.">Figure 10.11, “The registry info of the HelloWorld Service information was imported by the subscription mechanism.”</a>.
-        </p><div class="figure"><a id="fig-registry_info_HelloWorld"/><div class="figure-contents"><div class="mediaobject"><img src="images/registry_info_helloworld.png" alt="The registry info of the HelloWorld Service information was imported by the subscription mechanism."/></div></div><p class="title"><b>Figure 10.11. The registry info of the HelloWorld Service information was imported by the subscription mechanism.</b></p></div><br class="figure-break"/></div></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="chap-Administration"/>Chapter 11. Administration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-admin_intro">11.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-changing_listener_port">11.2. Changing the Listener Port</a></span></dt><dt><span class="section"><a href="#sect-changing_oracle_sequence_name">11.3. Changing the Oracle Sequence name</a></
 span></dt></dl></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-admin_intro"/>11.1. Introduction</h2></div></div></div><p>
+        </p><div class="figure"><a id="fig-registry_info_HelloWorld"/><div class="figure-contents"><div class="mediaobject"><img src="images/registry_info_helloworld.png" alt="The registry info of the HelloWorld Service information was imported by the subscription mechanism."/></div></div><p class="title"><b>Figure 10.11. The registry info of the HelloWorld Service information was imported by the subscription mechanism.</b></p></div><br class="figure-break"/></div></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="chap-Administration"/>Chapter 11. Administration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-admin_intro">11.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-changing_listener_port">11.2. Changing the Listener Port</a></span></dt><dt><span class="section"><a href="#sect-changing_oracle_sequence_name">11.3. Changing the Oracle Sequence name</a></
 span></dt><dt><span class="section"><a href="#sect-persistence">11.4. Persistence</a></span></dt></dl></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-admin_intro"/>11.1. Introduction</h2></div></div></div><p>
         General Stuff about administration.
         </p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-changing_listener_port"/>11.2. Changing the Listener Port</h2></div></div></div><p>
         If you want to change the port Tomcat listens on to something non-standard
@@ -1770,18 +1833,14 @@ juddi.server.port=8080</pre></li><li><p>
     &lt;/attributes&gt;
   &lt;/entity&gt;
 &lt;/entity-mappings&gt;
-</pre></div></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="chap-deployjboss"/>Chapter 12. Deploying to JBoss 5.1.0.GA</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-deployjboss">12.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-juddi-war">12.2. Add juddiv3.war</a></span></dt><dt><span class="section"><a href="#sect-datasource">12.3. Configure Datasource</a></span></dt></dl></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-deployjboss"/>12.1. Introduction</h2></div></div></div><p>
-	This section describes how to deploy juddi to JBoss 5.1.0.GA.     These instructions will use CXF as a webservice framework rather than JBoss WS native.
+</pre></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-persistence"/>11.4. Persistence</h2></div></div></div><p>jUDDI supports both OpenJPA and Hibernate as persistence providers.   If you are embedding jUDDI, it is important to note that there are two JARs provided through maven.    If you will be using Hibernate, please use the juddi-core JAR, if you are using OpenJPA, use juddi-core-openjpa.
+	</p><p>The difference between these JARs is that the persistence classes within juddi-core-openjpa have been enhanced (http://people.apache.org/~mprudhom/openjpa/site/openjpa-project/manual/ref_guide_pc_enhance.html).   Unfortunately, the Hibernate classloader does not deal well with these enhanced classes, so it it important to note not to use the juddi-core-openjpa JAR with Hibernate.
+	</p></div></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="chap-deployjboss"/>Chapter 12. Deploying to JBoss 6.0.0.GA</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-deployjboss">12.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-juddi-war">12.2. Add juddiv3.war</a></span></dt><dt><span class="section"><a href="#sect-web.xml">12.3. Change web.xml</a></span></dt><dt><span class="section"><a href="#sect-datasource">12.4. Configure Datasource</a></span></dt></dl></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-deployjboss"/>12.1. Introduction</h2></div></div></div><p>
+	This section describes how to deploy juddi to JBoss 6.0.0.GA.     
         </p><p>
-	First, download jboss-5.1.0.GA - the zip or tar.gz bundle may be found 
+	First, download jboss-6.0.0.GA - the zip or tar.gz bundle may be found 
 at http://www.jboss.org/jbossas/downloads/.      Download the bundle and uncompress it.
-        </p><p>
-	Next, download jbossws-cxf-3.2.0.zip - which can be found at http://www.jboss.org/jbossws/downloads/.     Uncompress it.	
-	</p><p>
-	In the uncompressed jbossws-cxf-3.2.0, rename <code class="filename">ant.properties-example</code> to <code class="filename">ant.properties</code>.    Edit ant.properties and set the jboss.510.home property to the directory where you unpacked your jboss-5.1.0.GA installation.    
-	</p><p>	
-	Next, execute the ant target "ant deploy-jboss510".    Once CXF is deployed, start the server and verify the installation with 'ant tests'.
-	</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-juddi-war"/>12.2. Add juddiv3.war</h2></div></div></div><p>
+        </p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-juddi-war"/>12.2. Add juddiv3.war</h2></div></div></div><p>
 	Copy juddiv3.war to server/default/deploy and unpack it.
 	</p><p>
 	Insert <code class="filename">jboss-web.xml</code> into the juddiv3.war/WEB-INF directory , should look like the following :
@@ -1794,13 +1853,16 @@ at http://www.jboss.org/jbossas/download
 &lt;jboss-web&gt;
 
     &lt;resource-ref&gt;
-        &lt;res-ref-name&gt;jdbc/juddiDB&lt;/res-ref-name&gt;
-        &lt;jndi-name&gt;java:/juddiDB&lt;/jndi-name&gt;
+        &lt;res-ref-name&gt;jdbc/JuddiDS&lt;/res-ref-name&gt;
+        &lt;jndi-name&gt;java:JuddiDS&lt;/jndi-name&gt;
     &lt;/resource-ref&gt;
+    &lt;depends&gt;jboss.jdbc:datasource=JuddiDS,service=metadata&lt;/depends&gt;
 
 &lt;/jboss-web&gt;
 </pre><p>	
-	</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-datasource"/>12.3. Configure Datasource</h2></div></div></div><p>
+	</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-web.xml"/>12.3. Change web.xml</h2></div></div></div><p>
+	Replace the WEB-INF/web.xml with the jbossws-native-web.xml within docs/examples/appserver.
+        </p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="sect-datasource"/>12.4. Configure Datasource</h2></div></div></div><p>
 	The first step for configuring a datasource is to copy your JDBC driver into the classpath.    Copy your JDBC driver into <code class="filename">${jboss.home.dir}/server/${configuration}/lib</code>, where configuration is the profile you wish to start with (default, all, etc.). 
 
 	Example : 

Modified: juddi/site/docs/3.0/userguide/pdf/userguide.pdf
URL: http://svn.apache.org/viewvc/juddi/site/docs/3.0/userguide/pdf/userguide.pdf?rev=1135108&r1=1135107&r2=1135108&view=diff
==============================================================================
Binary files - no diff available.



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@juddi.apache.org
For additional commands, e-mail: commits-help@juddi.apache.org


Mime
View raw message