You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@juddi.apache.org by ks...@apache.org on 2014/02/03 20:34:37 UTC
svn commit: r1564021 [4/5] - in /juddi/docs/trunk: ./ ClientGuide/
ClientGuide/en-US/ Guide/ Guide/Guide/ Guide/en-US/ images/ images/community/
Added: juddi/docs/trunk/Guide/en-US/GuideHowToDeployjUDDITo.asciidoc
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/Guide/en-US/GuideHowToDeployjUDDITo.asciidoc?rev=1564021&view=auto
==============================================================================
--- juddi/docs/trunk/Guide/en-US/GuideHowToDeployjUDDITo.asciidoc (added)
+++ juddi/docs/trunk/Guide/en-US/GuideHowToDeployjUDDITo.asciidoc Mon Feb 3 19:34:34 2014
@@ -0,0 +1,285 @@
+[[chapter-HowToDeployjUDDITo]]
+== How to deploy jUDDI To?
+
+The jUDDI distribution ships preconfigured on Tomcat - it runs out of the box. All you have to do in go into the `juddi-distro-<version>/juddi-tomcat-<version>/bin` directory and start up Tomcat. All of this just as described in <<chapter-GettingStarted>>.
+
+By default the `juddiv3.war` is configured to use OpenJPA and CXF. If you want to change your JPA or WS provider, or you'd like to run on a different container then this chapter may come in handy, as there a number of scripted 'profiles' to change the configuration and dependencies in the `juddiv3.war`. To run these maven based scripts you need to go into `juddi-distro-<version>/juddiv3-war` directory.
+
+=== Tomcat
+
+==== OpenJPA and CXF
+Target platform Tomcat and Derby using OpenJPA and CXF. Both OpenJPA and CXF are packaged up in the juddiv3.war.
+----
+mvn clean package -P openjpa
+----
+Then copy the `target/juddiv3.war` to the `<tomcat>/webapps` directory.
+
+==== Hibernate and CXF
+Target platform Tomcat and Derby using Hibernate and CXF. Both Hibernate and CXF are packaged up in the juddiv3.war.
+----
+mvn clean package -P hibernate
+----
+Then copy the `target/juddiv3.war` to the `<tomcat>/webapps` directory.
+
+==== OpenJPA and Axis2
+
+Target platform Tomcat and Derby using OpenJPA and Apache Axis2. Both Hibernate and Axis2 are packaged up in the juddiv3.war.
+----
+mvn clean package -P axis2
+----
+Then copy the `target/juddiv3.war` to the `<tomcat>/webapps` directory.
+
+=== JBoss
+
+==== JBossAS 6.0.0.GA
+
+This section describes how to deploy juddi to JBoss 6.0.0.GA.
+
+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.
+
+
+===== Hibernate and JBossWS-Native
+
+Target platform JBoss-6.x and HSQL using Hibernate and JBossWS-native. The juddiv3.war relies on Hibernate and JBossWS-native in the appserver.
+----
+mvn clean package -P hibernate-jbossws-native
+----
+Then copy the `target/juddiv3.war` to the `<jboss>/server/default/deploy` directory.
+
+===== Hibernate and JBossWS-CXF
+
+Target platform JBoss-6.x and HSQL using Hibernate and JBossWS-cxf. The juddiv3.war relies on Hibernate and JBossWS-cxf in the appserver.
+----
+mvn clean package -P hibernate-jbossws-cxf
+----
+
+[knownissues]
+.KNOWN ISSUES
+Issue 1::
++
+----
+15:14:37,275 SEVERE [RegistryServlet] jUDDI registry could not be started. org.apache.commons.configuration.ConfigurationException: java.util.zip.ZipException: error in opening zip file: org.apache.commons.configuration.ConfigurationException: org.apache.commons.configuration.ConfigurationException: java.util.zip.ZipException: error in opening zip file
+----
++
+Workaround: deploy juddiv3.war as a directory (not a zip file).
+Issue 2::
++
+JBoss-5.x Note that configuration 3 and 4 will also run on JBoss-5.x, but you may run into the following
++
+----
+ERROR [org.jboss.ws.metadata.wsdl.xmlschema.JBossXSErrorHandler] (main) [domain:http://www.w3.org/TR/xml-schema-1]::[key=src-resolve]::Message=src-resolve: Cannot resolve the name ns1:Signature to a element declaration component.
+----
++
+Workaround: Unzip the deployers/jbossws.deployer/jbossws-native-core.jar and add the xmldsig-core-schema.xsd in the schema directory,
++
+----
+10293 Fri May 27 14:40:40 EDT 2011 schema/xmldsig-core-schema.xsd
+----
++
+Edit the file META-INF/jbossws-entities.properties by adding a line at the bottom saying:
++
+----
+http\://www.w3.org/2000/09/xmldsig#=schema/xmldsig-core-schema.xsd
+----
+
+Copy juddiv3.war to server/default/deploy and unpack it.
+
+Insert jboss-web.xml into the juddiv3.war/WEB-INF directory , should look like the following :
+----
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<!DOCTYPE jboss-web PUBLIC
+ "-//JBoss//DTD Web Application 2.3V2//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss-web_3_2.dtd">
+
+<jboss-web>
+
+ <resource-ref>
+ <res-ref-name>jdbc/JuddiDS</res-ref-name>
+ <jndi-name>java:JuddiDS</jndi-name>
+ </resource-ref>
+ <depends>jboss.jdbc:datasource=JuddiDS,service=metadata</depends>
+
+</jboss-web>
+----
+===== Change web.xml
+Replace the WEB-INF/web.xml with the jbossws-native-web.xml within docs/examples/appserver.
+
+===== Configure Datasource
+The first step for configuring a datasource is to copy your JDBC driver into the classpath. Copy your JDBC driver into ${jboss.home.dir}/server/${configuration}/lib, where configuration is the profile you wish to start with (default, all, etc.). Example :
+----
+cp mysql-connector-java-5.0.8-bin.jar /opt/jboss-5.1.0.GA/server/default/lib
+----
+Next, configure a JBoss datasource file for your db. Listed below is an example datasource for MySQL :
+----
+<?xml version="1.0" encoding="UTF-8"?>
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>JuddiDS</jndi-name>
+ <connection-url>jdbc:mysql://localhost:3306/juddiv3</connection-url>
+ <driver-class>com.mysql.jdbc.Driver</driver-class>
+ <user-name>root</user-name>
+ <password></password>
+ <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter</exception-sorter-class-name>
+
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>mySQL</type-mapping>
+ </metadata>
+ </local-tx-datasource>
+</datasources>
+----
+Next, make a few changes to the juddiv3.war/classes/META-INF/persistence.xml. Change the "hibernate.dialect" property to match the database you have chosen for persistence. For MySQL, change the value of hibernate.dialect to "org.hibernate.dialect.MySQLDialect". A full list of dialects available can be found in the hibernate documentation (https://www.hibernate.org/hib_docs/v3/api/org/hibernate/dialect/package-summary.html). Next, change the <jta-data-source> tags so that it reads <non-jta-data-source>, and change the value from java:comp/env/jdbc/JuddiDS to java:/JuddiDS.
+
+==== JBossAS 7.x/JBossEAP-6.x
+
+This section describes how to deploy juddi to JBossAS 7, WildFly and JBossEAP 6
+
+===== Hibernate and JBossWS-CXF
+
+This profile is not yet scripted as there is an issue with Hibernate, see JUDDI-587.
+
+===== OpenJPA and JBossWS-CXF
+
+Target platform using HSQL using OpenJPA and JBossWS-CXF. The juddiv3.war relies on the openjpa and cxf modules in the appserver.
+
+----
+mvn clean package -P openjpa-jboss7up
+----
+Then copy the `target/juddiv3.war` to the `<jboss>/standalone/deployments` directory.
+
+Not all the JBoss appservers mentioned above shipped a module for openjpa. If it did not then you can create it:
+
+In your appserver create the following directory structure `<jboss>/modules/system/layers/base/org/apache/openjpa/main` and the following files:
+....
+module.xml openjpa-2.2.1.jar serp-1.13.1.jar
+....
+where the contents of the modules.xml should look like
+....
+<module xmlns="urn:jboss:module:1.1" name="org.apache.openjpa">
+ <resources>
+ <resource-root path="openjpa-2.2.1.jar"/>
+ <resource-root path="serp-1.13.1.jar"/>
+ </resources>
+ <dependencies>
+ <module name="javax.persistence.api"/>
+ <module name="javax.transaction.api"/>
+ <module name="javax.validation.api"/>
+ <module name="org.apache.commons.lang"/>
+ <module name="org.apache.commons.collections"/>
+ <module name="org.apache.log4j"/>
+ </dependencies>
+</module>
+....
+
+Next create the directory structure `<jboss>/modules/system/layers/base/org/jboss/as/jpa/openjpa/main` with the files:
+....
+jboss-as-jpa-openjpa-7.1.1.Final.jar module.xml
+....
+where the contents of the modules.xml should look like
+....
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- contains the JPA integration classes for OpenJPA 2.x -->
+<module xmlns="urn:jboss:module:1.1" name="org.jboss.as.jpa.openjpa">
+ <properties>
+ <property name="jboss.api" value="private"/>
+ </properties>
+
+ <resources>
+ <resource-root path="jboss-as-jpa-openjpa-7.1.1.Final.jar"/>
+ <!-- Insert resources here -->
+ </resources>
+
+ <dependencies>
+ <module name="javax.annotation.api"/>
+ <module name="javax.persistence.api"/>
+ <module name="javax.transaction.api"/>
+
+ <module name="org.jboss.as.jpa.spi"/>
+ <module name="org.jboss.logging"/>
+ <module name="org.jboss.jandex"/>
+
+ <module name="org.apache.openjpa" optional="true"/> <!-- org.apache.openjpa:main must be created manually with OpenJPA jars -->
+ </dependencies>
+</module>
+....
+and in the `modules/system/layers/base/org/jboss/as/jpa/main/module.xml
+add dependency
+....
+<module name="org.jboss.as.jpa.openjpa"/>
+....
+
+=== Deploying to Glassfish
+This section describes how to deploy juddi to Glassfish 2.1.1. These instructions will use CXF as a webservice framework.
+
+First, download the glassfish-v2.1.1 installer JAR. Once downloaded,install using the JAR and then run the ant setup script :
+----
+java -jar glassfish-installer-v2.1.1-b31g-linux.jar
+cd glassfish
+ant -f setup.xml
+----
+
+==== Glassfish jars
+Copy the following JARs into domains/domain1/lib/ext. Note that for the purposes of this example, we have copied the MySQL driver to domains/domain1/lib/ext :
+----
+antlr-2.7.6.jar
+cglib-nodep-2.1_3.jar
+commons-collections-3.2.1.jar
+commons-logging-1.1.jar
+dom4j-1.6.1.jar
+hibernate-3.2.5.ga.jar
+hibernate-annotations-3.3.0.ga.jar
+hibernate-commons-annotations-3.0.0.ga.jar
+hibernate-entitymanager-3.3.1.ga.jar
+hibernate-validator-3.0.0.ga.jar
+javassist-3.3.ga.jar
+jboss-common-core-2.0.4.GA.jar
+jta-1.0.1B.jar
+mysql-connector-java-5.0.8-bin.jar
+persistence-api-1.0.jar
+----
+
+==== Configure the JUDDI datasource
+First, using the asadmin administration tool, import the following file :
+----
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE resources PUBLIC "-//Sun Microsystems Inc.//DTD Application Server 9.0 Domain//EN" "*<install directory>/lib/dtds/sun-resources_1_3.dtd*">
+<resources>
+<jdbc-connection-pool name="mysql-pool" datasource-classname="com.mysql.jdbc.jdbc2.optional.MysqlDataSource" res-type="javax.sql.DataSource">
+<property name="user" value="juddi"/>
+<property name="password" value="juddi"/>
+<property name="url" value="jdbc:mysql://localhost:3306/juddiv3"/>
+</jdbc-connection-pool>
+<jdbc-resource enabled="true" jndi-name="jdbc/mysql-resource" object-type="user" pool-name="mysql-pool"/>
+</resources>
+----
+----
+asadmin add-resources resource.xml
+----
+Then use the Glassfish administration console to create a "jdbc/juddiDB" JDBC datasource resource based on the mysql-pool Connection Pool.
+
+==== Add juddiv3-cxf.war
+Unzip the juddiv3-cxf WAR into domains/domain1/autodeploy/juddiv3.war .
+
+Add a sun-web.xml file into juddiv3.war/WEB-INF. Make sure that the JNDI references matches the JNDI location you configured in the Glassfish administration console.
+----
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE sun-web-app PUBLIC '-//Sun Microsystems, Inc.//DTD
+Application Server 9.0 Servlet 2.5//EN'
+'http://www.sun.com/software/appserver/dtds/sun-web-app_2_5-0.dtd'>
+<sun-web-app>
+<resource-ref>
+<res-ref-name>jdbc/juddiDB</res-ref-name>
+<jndi-name>jdbc/juddiDB</jndi-name>
+</resource-ref>
+</sun-web-app>
+----
+Next, make a few changes to juddiv3.war/WEB-INF/classes/META-INF/persistence.xml . Change the "hibernate.dialect" property to match the database that you have chosen for persistence. For MySQL, change the value of hibernate.dialect to "org.hibernate.dialect.MySQLDialect". A full list of dialects available can be found in the hibernate documentation (https://www.hibernate.org/hib_docs/v3/api/org/hibernate/dialect/package-summary.html). Next, change the <jta-data-source> change the value from java:comp/env/jdbc/JuddiDS to java:comp/env/jdbc/JuddiDB.
+
+==== Run jUDDI
+Start up the server :
+----
+cd bin
+asadmin start-domain domain1
+----
+Once the server is deployed, browse to http://localhost:8080/juddiv3
\ No newline at end of file
Added: juddi/docs/trunk/Guide/en-US/GuideRootSeedData.asciidoc
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/Guide/en-US/GuideRootSeedData.asciidoc?rev=1564021&view=auto
==============================================================================
--- juddi/docs/trunk/Guide/en-US/GuideRootSeedData.asciidoc (added)
+++ juddi/docs/trunk/Guide/en-US/GuideRootSeedData.asciidoc Mon Feb 3 19:34:34 2014
@@ -0,0 +1,113 @@
+[[chapter-UDDISeedData]]
+== UDDI Seed Data
+
+This information is relevant for both understanding how jUDDI's default data is set when jUDDI first runs (i.e. to a new database). It's also useful for scripting or automating the deployment of a jUDDI server within your organization which will enable you to prepopulate the data.
+
+As of UDDI v3, each registry need to have a "root" 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 for the root account. The default data can be found in the juddi-core-3.x.jar, under juddi_install_data/. By default jUDDI installs two Publishers: "root" and "uddi". Root owns the root partition, and uddi owns all the other seed data such as pre-defined tModels.
+
+=== Seed Data Files
+For each publisher there are four seed data files that will be read the first time you start jUDDI:
+----
+<publisher>_Publisher.xml
+<publisher>_tModelKeyGen.xml
+<publisher>_BusinessEntity.xml
+<publisher>_tModels.xml
+----
+
+For example the content of the root_Publisher.xml looks like
+----
+<publisher xmlns="urn:juddi-apache-org:api_v3" authorizedName="root">
+ <publisherName>root publisher</publishername>
+ <isAdmin>true</isadmin>
+</publisher>
+----
+
+Each publisher should have its own key generator schema so that custom generated keys cannot end up being identical to keys generated by other publishers. It is therefor that the each publisher need to define their own KenGenerator tModel. The tModel Key Generator is defined in the file root_tModelKeyGen.xml and the content of this file is
+----
+<tModel tModelKey="uddi:juddi.apache.org:keygenerator" xmlns="urn:uddi-org:api_v3">
+ <name>uddi-org:keyGenerator</name>
+ <description>Root domain key generator</description>
+ <overviewDoc>
+ <overviewURL useType="text">
+ http://uddi.org/pubs/uddi_v3.htm#keyGen
+ </overviewurl>
+ </overviewdoc>
+ <categoryBag>
+ <keyedReference tModelKey="uddi:uddi.org:categorization:types"
+ keyName="uddi-org:types:keyGenerator"
+ keyValue="keyGenerator" />
+ </categorybag>
+</tmodel>
+----
+
+This means that the legal format of keys used by the root publisher need to be in the form uddi:juddi.apache.org:<text-of-chioce></text-of-chioce> The use of other types of format will lead to an 'illegal key' error. The root publisher can only own one KeyGenerator while any other publisher can own more then one KeyGenerator. KeyGenerators should not be shared unless there is a good reason to do so. If you want to see your publisher with more then just the one KeyGenerator tModel, you can use the <publisher></publisher>_tModels.xml file.
+Finally, in the <publisher></publisher>_BusinessEntity.xml file can be used to setup Business and Service data. In the root_BusinessEntity.xml we specified the ASF Business, and the UDDI services; Inquiry, Publish, etc.:
+----
+<businessEntity xmlns="urn:uddi-org:api_v3" xmlns:xml="http://www.w3.org/XML/1998/namespace" businessKey="uddi:juddi.apache.org:businesses-asf">
+ <!-- Change the name field to represent the name of your registry -->
+ <name xml:lang="en">An Apache jUDDI Node</name>
+ <!-- Change the description field to provided a brief description of your registry -->
+ <description xml:lang="en">This is a UDDI v3 registry node as implemented by Apache jUDDI.</description>
+ <discoveryURLs>
+ <!-- This discovery URL should point to the home installation URL of jUDDI -->
+ <discoveryURL useType="home">${juddi.server.baseurl}/juddiv3</discoveryURL>
+ </discoveryURLs>
+ <categoryBag>
+ <keyedReference tModelKey="uddi:uddi.org:categorization:nodes" keyValue="node" />
+ </categoryBag>
+ <businessServices>
+ <!-- As mentioned above, you may want to provide user-defined keys for these (and the services/bindingTemplates below. Services that you
+ don't intend to support should be removed entirely -->
+ <businessService serviceKey="uddi:juddi.apache.org:services-inquiry" businessKey="uddi:juddi.apache.org:businesses-asf">
+ <name xml:lang="en">UDDI Inquiry Service</name>
+ <description xml:lang="en">Web Service supporting UDDI Inquiry API</description>
+ <bindingTemplates>
+ <bindingTemplate bindingKey="uddi:juddi.apache.org:servicebindings-inquiry-ws" serviceKey="uddi:juddi.apache.org:services-inquiry">
+ <description>UDDI Inquiry API V3</description>
+ <!-- This should be changed to the WSDL URL of the inquiry API. An access point inside a bindingTemplate will be found for every service
+ in this file. They all must point to their API's WSDL URL -->
+ <accessPoint useType="wsdlDeployment">${juddi.server.baseurl}/services/inquiry?wsdl</accessPoint>
+ <tModelInstanceDetails>
+ <tModelInstanceInfo tModelKey="uddi:uddi.org:v3_inquiry">
+ <instanceDetails>
+ <instanceParms>
+ <![CDATA[
+ <?xml version="1.0" encoding="utf-8" ?>
+ <UDDIinstanceParmsContainer xmlns="urn:uddi-org:policy_v3_instanceParms">
+ <defaultSortOrder>
+ uddi:uddi.org:sortorder:binarysort
+ </defaultSortOrder>
+ </UDDIinstanceParmsContainer>
+ ]]>
+ </instanceParms>
+ </instanceDetails>
+ </tModelInstanceInfo>
+ </tModelInstanceDetails>
+ <categoryBag>
+ <keyedReference keyName="uddi-org:types:wsdl" keyValue="wsdlDeployment" tModelKey="uddi:uddi.org:categorization:types"/>
+ </categoryBag>
+ </bindingTemplate>
+ </bindingTemplates>
+ </businessService>
+<!-- snip -->
+</businessService>
+----
+
+Note that the seeding process only kicks off if no publishers exist in the database. So this will only work with a clean database, unless you set juddi/seed/always 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.
+
+=== Tokens in the Seed Data
+You may have noticed the tokens in the root_BusinessEntity.xml file (${juddi.server.baseurl}. The value of this tokens can set in the juddiv3.xml file. The value substitution takes place at runtime, so that different nodes can do the substitution with their own value if needed.
+
+=== Customer Seed Data
+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 directory call juddi_custom_install_data in the juddiv3.war/WEB-INF/classes/ directory. That way you don't have to modify the juddi-core-3.x.jar. Additionally if your root publisher is not called "root" you will need to set the juddi/root/publisher property in the juddiv3.xml file to something other then
+----
+juddi/root/publisher=root
+----
+The juddiv3.war ships with two example data directory. One for the Sales Affiliate, and one for the Marketing Affiliate. To use the Sales Seed Data, in the juddiv3.war/WEB-INF/classes/, rename the directory
+----
+*nix
+mv RENAME4Sales_juddi_custom_install_data juddi_custom_install_data
+Win*
+ren RENAME4Sales_juddi_custom_install_data juddi_custom_install_data
+----
+before you start jUDDI the first time. It will then use this data to populate the database. If you want to rerun you can trash the database it created and restart tomcat. Don't forget to set the tokens in the juddiv3.xml file.
Added: juddi/docs/trunk/Guide/en-US/GuideTroubleshootingjUDDI.asciidoc
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/Guide/en-US/GuideTroubleshootingjUDDI.asciidoc?rev=1564021&view=auto
==============================================================================
--- juddi/docs/trunk/Guide/en-US/GuideTroubleshootingjUDDI.asciidoc (added)
+++ juddi/docs/trunk/Guide/en-US/GuideTroubleshootingjUDDI.asciidoc Mon Feb 3 19:34:34 2014
@@ -0,0 +1,55 @@
+== Troubleshooting jUDDI
+
+Here are some tips to help you troubleshoot problems with jUDDI, jUDDI-GUI, jUDDI Client and more.
+
+=== jUDDI Web Services, juddiv3.war
+
+==== Enable debugging logging
+
+You can adjust the logging level to provide additional output for troubleshooting purposes. To do so, see the Administration Guide, Logging.
+
+=== jUDDI GUI, juddi-gui.war
+
+Problem: Can't authentication from juddi-gui's top right hand side login box to juddiv3.war services
+Solutions:
+
+* Check the server's log files for both juddi, juddi-gui and the server itself for error messages. This can sometimes be caused by the lack of Java Crypto Extensions (Oracle/Sun JRE/JDK only).
+* Check juddi-gui's configuration page at http://localhost:8080/juddi-gui/settings.jsp, confirm that the URL's that are referenced for the UDDI services are correct and accessible from the server hosting juddi-gui.
+* Make sure you're using a valid username/password ;)
+* Increase the logging level of jUDDI by changing the commons-logging.properties file
+* If you're having problems with Email delivery of subscription updates, enable debug logging by setting config/uddi/mail/debug=true in juddiv3.xml
+
+=== jUDDI Client Java
+
+==== Enable debugging logging
+
+You can adjust the logging level to provide additional output for troubleshooting purposes. To do so, see the Administration Guide, Logging.
+
+=== jUDDI Client .NET
+
+Components based on jUDDI's Client for the .NET Framework can configure logging from their application's config file. This is usually app.config or web.config. To configure logging, the following three settings must appear in the configuration/appSetttings section.
+----
+ <!-- DEBUG, INFO, WARN, ERROR -->
+ <add key="org.apache.juddi.v3.client.log.level" value="INFO" />
+ <!-- options are CONSOLE, EVENTLOG, FILE multiple values can be specified, comma delimited.
+ Notes for EVENTLOG, you must run the juddi-installer as admin before running-->
+ <add key="org.apache.juddi.v3.client.log.target" value="CONSOLE" />
+ <!-- only used when target=FILE -->
+ <add key="org.apache.juddi.v3.client.log.logger.file" value="pathToOutputFile" />
+----
+If nothing is defined, the default log level is "WARN" and the target is "CONSOLE" which is standard out.
+
+
+=== Getting help
+
+There are many different ways to get help with your jUDDI instance. Please refer to the following URLs for more information.
+
+* jUDDI Home Page http://juddi.apache.org/
+* User Guide http://juddi.apache.org/docs/3.x/userguide/html/index.htmlnavbar.help.userguide
+* Developer Guide http://juddi.apache.org/docs/3.x/devguide/html/index.htmlnavbar.help.devguide
+* Developer API Documentation http://juddi.apache.org/docs.html
+* jUDDI Wiki http://wiki.apache.org/juddi
+* jUDDI Issue/Bug Tracker http://juddi.apache.org/issue-tracking.html
+* jUDDI User and Developer Mailing List http://juddi.apache.org/mailing-list.html
+* jUDDI Source Code http://svn.apache.org/viewvc/juddi/
+
Added: juddi/docs/trunk/Guide/en-US/GuideUDDIRegistryIntroduction.asciidoc
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/Guide/en-US/GuideUDDIRegistryIntroduction.asciidoc?rev=1564021&view=auto
==============================================================================
--- juddi/docs/trunk/Guide/en-US/GuideUDDIRegistryIntroduction.asciidoc (added)
+++ juddi/docs/trunk/Guide/en-US/GuideUDDIRegistryIntroduction.asciidoc Mon Feb 3 19:34:34 2014
@@ -0,0 +1,109 @@
+[[UDDI-Registry-Introduction]]
+== Universal Description, Discovery and Integration (UDDI)
+
+=== UDDI Protocol, Specification
+
+The Universal Description, Discovery and Integration (UDDI) protocol is one of the major building blocks required for successful Web services. UDDI creates a standard interoperable platform that enables companies and applications to quickly, easily, and dynamically find and use Web services over the Internet (or Intranet). UDDI also allows operational registries to be maintained for different purposes in different contexts. UDDI is a cross-industry effort driven by major platform and software providers, as well as marketplace operators and e-business leaders within the OASIS standards consortium <<Guide#uddi-oasis-open-org>>. UDDI has gone through 3 revisions and the latest version is 3.0.2 <<Guide#uddi-v3>>. Additional information regarding UDDI can be found at http://uddi.xml.org <<Guide#uddi-xml-org>>.
+
+=== UDDI Registry
+
+The UDDI Registry (((UDDI,registry))) implements the UDDI specification (((UDDI,specification))). UDDI is a Web-based _distributed_ _directory_ (((directory))) that enables businesses to list themselves on the Internet (or Intranet) and discover each other, similar to a traditional phone book's yellow and white pages. The UDDI registry is both a white pages business directory and a technical specifications library. The Registry is designed to store information about Businesses and Services and it holds references to detailed documentation.
+
+[[figure-UDDIREG-InvocationPattern]]
+.Invocation Pattern using the UDDI Registry
+image::images/UDDI_Registry_invocation_pattern.png[Invocation Pattern using the UDDI Registry]
+
+In step 1 of <<figure-UDDIREG-InvocationPattern>> it is shown how a business publishes services to the UDDI registry. In step 2, a client looks up the service in the registry and receives service binding information. Finally in step 3, the client then uses the binding information to invoke the service. The UDDI APIs are SOAP based for interoperability reasons. In this example we've three APIs specified in the UDDI v3 specification, Security, Publication and Inquiry. The UDDI v3 specification defines 9 APIs:
+
+. UDDI_Security_PortType, defines the API to obtain a security token. With a valid security token a publisher can publish to the registry. A security token can be used for the entire session.
+. UDDI_Publication_PortType, defines the API to publish business and service information to the UDDI registry.
+. UDDI_Inquiry_PortType, defines the API to query the UDDI registry. Typically this API does not require a security token.
+. UDDI_CustodyTransfer_PortType, this API can be used to transfer the custody of a business from one UDDI node to another.
+. UDDI_Subscription_PortType, defines the API to register for updates on a particular business of service.
+. UDDI_SubscriptionListener_PortType, defines the API a client must implement to receive subscription notifications from a UDDI node.
+. UDDI_Replication_PortType, defines the API to replicate registry data between UDDI nodes.
+. UDDI_ValueSetValidation_PortType, by nodes to allow external providers of value set validation. Web services to assess whether keyedReferences or keyedReferenceGroups are valid.
+. UDDI_ValueSetCaching_PortType, UDDI nodes may perform validation of publisher references themselves using the cached values obtained from such a Web service.
+
+=== jUDDI Project
+
+Apache jUDDI is server and client-side implementation of the UDDI v3 specification. The server side is the UDDI Registry, the client side are the juddi-client libraries. There is a Java as well as a C# version of the client libraries. The jUDDI GUI uses the client libraries to connect to a UDDI Registry. For more details please see the <<GuideGettingStarted#chapter-GettingStarted>>.
+
+The following is a list of all supported UDDI interfaces provided by this release of jUDDI
+
+.Supported UDDI Interfaces
+[options="header"]
+|========================================================
+| API | Spec | Supported | Notes
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908076[Inquiry] | Required | All Methods |
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908158[Inquiry HTTP GET] | Optional | All Methods | Plus a number of additional methods
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908095[Publication] | Required | All Methods |
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908115[Security] | Optional | All Methods | Pluggable authentication
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908128[Subscription] | Optional | All Methods | HTTP, SMTP delivery implemented, pluggable
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908336[Subscription Listener] |Optional | All Methods | Client and Server side implementations
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908141[Value Set Caching] | Optional | Partial | Scheduled for 3.3
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908141[Value Set Validation] | Optional | Implemented | Scheduled for 3.3
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908180[Replication] | Optional | Partial | Scheduled for 3.3
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908118[Custody and Ownership Transfer] | Optional | All Methods | Only supports user to user transfers on the same node
+| http://uddi.org/pubs/ProgrammersAPI-V2.04-Published-20020719.htm#_Toc25137711[UDDIv2 Inquiry] | Required | BETA | Supported via API translator
+| http://uddi.org/pubs/ProgrammersAPI-V2.04-Published-20020719.htm#_Toc25137722[UDDIv2 Publish] | Required | BETA | Supported via API translator
+
+|========================================================
+
+The following is a list of other features of interest that was either defined in the UDDI specifications or in technical notes.
+
+.jUDDI Features
+[options="header"]
+|========================================================
+| API | Spec | Supported | Notes
+|Digital Signatures | Server req | Full support | Java and .NET clients and in browser signing
+|Client side Subscription Listener | Optional | Full support | Java and .NET clients
+| https://www.oasis-open.org/committees/uddi-spec/doc/tn/uddi-spec-tc-tn-wsdl-v2.htm[WSDL to UDDI] | Recommendation| Full support | Java, .NET clients and web GUI
+| https://www.oasis-open.org/committees/uddi-spec/doc/tn/uddi-spec-tc-tn-wsdl-v2.htm[WADL to UDDI] | Recommendation| Full support | Java, .NET clients and web GUI
+| https://www.oasis-open.org/committees/uddi-spec/doc/tn/uddi-spec-tc-tn-bpel-20040725.htm[BPEL to UDDI] | Recommendation| Full support | Java client
+| UDDI Technical Compliance Kit | - | Full support | Provides a standalone UDDI testing capability
+| Internationalization | Recommendation| Yes | Both end user interfaces (User and Admin web apps) are supported. Error messages from the server are external and can be overwritten.
+| Registration via Annotations | - | Full support | Provides automated registration of classes via Java/.NET Annotations
+|========================================================
+
+UDDI defines a number of http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908080[sorting mechanisms].
+
+.Supported Sort Orders
+[options="header"]
+|========================================================
+| Find Qualifier | Spec | Supported | Notes
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#sortOrd[binarySort] | Required | yes |
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#caseInsensSort[caseInsensitiveSort] | Required | party | Only when using caseInsentitiveMatch, https://issues.apache.org/jira/browse/JUDDI-785[JIRA opened]
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908355[caseSensitiveSort] | Required | yes |
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908356[sortByNameAsc] | Required | yes |
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908357[sortByNameDesc] | Required | yes |
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908358[sortByDateAsc] | Required | yes |
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908359[sortByDateDesc] | Required | yes |
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc42047570[JIS-X4061] | Optional | no | Japanese Character Strings
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#UCASort[UTS-10] | Recommended | yes
+|========================================================
+
+UDDI also defines a number of http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908080[Find Qualifiers], which modify the default search behavior of the http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908076[Inquiry] Find* APIs.
+
+.Supported Find Qualifiers
+[options="header"]
+|========================================================
+| Find Qualifier | Spec |Supported
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908360[andAllKeys] | Required | yes
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908346[approximateMatch] | Required | yes
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908365[bindingSubset] | Required | yes
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908348[caseInsensitiveMatch] | Required | yes
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908349[caseSensitiveMatch] | Required | yes
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908363[combineCategoryBags] | Required | yes
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908350[diacriticInsensitiveMatch] | Optional | yes
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908351[diacriticSensitiveMatch] | Required | yes
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908347[exactMatch] | Required | yes
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908367[signaturePresent] | Required | yes
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908361[orAllKeys] | Required | yes
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908362[orLikeKeys] | Required | yes
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908364[serviceSubset] | Required | yes
+| http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908366[suppressProjectedServices] | Required | yes
+
+|========================================================
+
+
Added: juddi/docs/trunk/Guide/en-US/GuideUDDISubscriptions.asciidoc
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/Guide/en-US/GuideUDDISubscriptions.asciidoc?rev=1564021&view=auto
==============================================================================
--- juddi/docs/trunk/Guide/en-US/GuideUDDISubscriptions.asciidoc (added)
+++ juddi/docs/trunk/Guide/en-US/GuideUDDISubscriptions.asciidoc Mon Feb 3 19:34:34 2014
@@ -0,0 +1,259 @@
+== UDDI Subscriptions
+
+Subscriptions come to play in a multi-registry setup. Within your company you may have the need to run with more then one UDDI, let's say one for each department, where you limit access to the systems in each department to just their own UDDI node. However you may want to share some services cross departments. The subscription API can help you cross registering those services and keeping them up to date by sending out notifications as the registry information in the parent UDDI changes.
+
+There are two type of subscriptions:
+
+* asynchronous - Save a subscription, and the UDDI server sends you alerts according to your search criteria.
+
+* synchronous - Save a subscription, and then the UDDI client polls periodically for updates.
+
+Save a subscription and invoke the get_Subscription and get a synchronous reply.
+The notification can be executed in a synchronous and an asynchronous way. The asynchronous way requires a listener service to be installed on the node to which the notifications should be sent.
+
+=== Two node example setup: Sales and Marketing
+In this example we are setting up a node for 'sales' and a node for 'marketing'. For this you need to deploy jUDDI to two different services, then you need to do the following setup:
+
+Procedure 10.1. Setup Node 1: Sales
+
+Create juddi_custom_install_data.
+----
+cd juddiv3/WEB-INF/classes
+mv RENAME4SALES_juddi_custom_install_data juddi_custom_install_data
+----
+edit: webapps/juddiv3/WEB-INF/classes/juddiv3.properties and set the following property values where 'sales' is the DNS name of your server.
+----
+juddi.server.name=sales
+juddi.server.port=8080
+----
+Start the server (tomcat), which will load the UDDI seed data (since this is the first time you're starting jUDDI, see , Root Seed Data)
+----
+bin/startup.sh
+----
+Open your browser to http://sales:8080/juddiv3. You should see:
+
+image::images/sales_node_installation.png
+
+Figure Sales Node Installation
+
+Procedure 10.2. Setup Node 2: Marketing
+
+Create juddi_custom_install_data.
+----
+cd juddiv3/WEB-INF/classes
+mv RENAME4MARKETING_juddi_custom_install_data juddi_custom_install_data
+----
+edit: webapps/juddiv3/WEB-INF/classes/juddiv3.properties and set the following property values where 'marketing' is the DNS name of your server.
+----
+juddi.server.name=marketing
+juddi.server.port=8080
+----
+Start the server (tomcat), which will load the UDDI seed data (since this is the first time you're starting jUDDI, see Chapter 5, Root Seed Data)
+----
+bin/startup.sh
+----
+Open your browser to http://marketing:8080/juddiv3 . You should see:
+
+image::images/marketing_node_installation.png
+
+Figure 10.2. Marketing Node Installation
+
+Note that we kept the root partition the same as sales and marketing are in the same company, however the Node Id and Name are different and reflect that this node is in 'sales' or 'marketing'.
+
+Finally you will need to replace the sales server's uddi-portlets.war/WEB-INF/classes/META-INF/uddi.xml with uddi-portlets.war/WEB-INF/classes/META-INF/uddi.xml.sales. Then, edit the uddi-portlets.war/WEB-INF/classes/META-INF/uddi.xml and set the following properties:
+
+----
+<name>default</name>
+<properties>
+ <property name="serverName" value="sales"/>
+ <property name="serverPort" value="8080"/>
+ <property name="rmiPort" value="1099"/>
+</properties>
+----
+Log into the sales portal: http://sales:8080/pluto with username/password: sales/sales.
+
+image::images/sales_services.png
+
+Figure 10.3. Sales Services
+
+Before logging into the marketing portal, replace marketing's uddi-portlet.war/WEB-INF/classes/META-INF/uddi.xml with udd-portlet.war/WEB-INF/classes/META-INF/uddi.xml.marketing. Then you will need to edit the uddi-portlet.war/WEB-INF/classes/META_INF/uddi.xml and set the following properties:
+
+----
+<name>default</name>
+<properties>
+ <property name="serverName" value="marketing"/>
+ <property name="serverPort" value="8080"/>
+ <property name="rmiPort" value="1099"/>
+</properties>
+----
+
+Now log into the marketing portal http://marketing:8080/pluto with username/password: marketing/ marketing. In the browser for the marketing node we should now see:
+
+image::images/marketing_services.png
+
+Figure 10.4. Marketing Services
+
+
+Note that the subscriptionlistener is owned by the Marketing Node business (and not the Root Marketing Node). The Marketing Node Business is managed by the marketing publisher.
+
+=== Deploy the HelloSales Service
+
+The sales department developed a service called HelloSales. The HelloSales service is provided in the juddiv3-samples.war, and it is annotated so that it will auto-register. Before deploying the war, edit the juddiv3-samples.war/WEB-INF/classes/META-INF/uddi.xml file to set some property values to 'sales'.
+
+----
+<?xml version="1.0" encoding="ISO-8859-1" ?>
+<uddi>
+ <reloadDelay>5000</reloadDelay>
+ <manager name="example-manager">
+ <nodes>
+ <node>
+ <name>default</name>
+ <description>Sales jUDDI node</description>
+ <properties>
+ <property name="serverName" value="sales"/>
+ <property name="serverPort" value="8080"/>
+ <property name="keyDomain" value="sales.apache.org"/>
+ <property name="department" value="sales" />
+ </properties>
+ <proxyTransport>
+ org.apache.juddi.v3.client.transport.InVMTransport
+ </proxyTransport>
+ <custodyTransferUrl>
+ org.apache.juddi.api.impl.UDDICustodyTransferImpl
+ </custodyTransferUrl>
+ <inquiryUrl>org.apache.juddi.api.impl.UDDIInquiryImpl</inquiryUrl>
+ <publishUrl>org.apache.juddi.api.impl.UDDIPublicationImpl</publishUrl>
+ <securityUrl>org.apache.juddi.api.impl.UDDISecurityImpl</securityUrl>
+ <subscriptionUrl>
+ org.apache.juddi.api.impl.UDDISubscriptionImpl
+ </subscriptionUrl>
+ <subscriptionListenerUrl>
+ org.apache.juddi.api.impl.UDDISubscriptionListenerImpl
+ </subscriptionListenerUrl>
+ <juddiApiUrl>org.apache.juddi.api.impl.JUDDIApiImpl</juddiApiUrl>
+ </node>
+ </nodes>
+ </manager>
+</uddi>
+----
+
+Now deploy the juddiv3-samples.war to the sales registry node, by building the juddiv3-samples.war and deploying. The HelloWorld service should deploy
+
+image::images/registration_by_annotation.png
+
+Figure 10.5. Registration by Annotation, deploying the juddi-samples.war to the sales Node
+
+
+On the Marketing UDDI we'd like to subscribe to the HelloWord service, in the Sales UDDI Node. As mentioned before there are two ways to do this; synchronously and asynchronously.
+
+==== Configure a user to create Subscriptions
+
+For a user to create and save subscriptions the publisher needs to have a valid login to both the sales and the marketing node. Also if the marketing publisher is going to create registry objects in the marketing node, the marketing publisher needs to own the sales keygenerator tModel. Check the marketing_*.xml files in the root seed data of both the marketing and sales node, if you want to learn more about this. It is important to understand that the 'marketing' publisher in the marketing registry owns the following tModels:
+
+----
+<save_tModel xmlns="urn:uddi-org:api_v3">
+ <tModel tModelKey="uddi:marketing.apache.org:keygenerator" xmlns="urn:uddi-org:api_v3">
+ <name>marketing-apache-org:keyGenerator</name>
+ <description>Marketing domain key generator</description>
+ <overviewDoc>
+ <overviewURL useType="text">
+ http://uddi.org/pubs/uddi_v3.htm#keyGen
+ </overviewURL>
+ </overviewDoc>
+ <categoryBag>
+ <keyedReference tModelKey="uddi:uddi.org:categorization:types"
+ keyName="uddi-org:types:keyGenerator"
+ keyValue="keyGenerator" />
+ </categoryBag>
+ </tModel>
+
+ <tModel tModelKey="uddi:marketing.apache.org:subscription:keygenerator"
+ xmlns="urn:uddi-org:api_v3">
+ <name>marketing-apache-org:subscription:keyGenerator</name>
+ <description>Marketing Subscriptions domain key generator</description>
+ <overviewDoc>
+ <overviewURL useType="text">
+ http://uddi.org/pubs/uddi_v3.htm#keyGen
+ </overviewURL>
+ </overviewDoc>
+ <categoryBag>
+ <keyedReference tModelKey="uddi:uddi.org:categorization:types"
+ keyName="uddi-org:types:keyGenerator"
+ keyValue="keyGenerator" />
+ </categoryBag>
+ </tModel>
+
+ <tModel tModelKey="uddi:sales.apache.org:keygenerator" xmlns="urn:uddi-org:api_v3">
+ <name>sales-apache-org:keyGenerator</name>
+ <description>Sales Root domain key generator</description>
+ <overviewDoc>
+ <overviewURL useType="text">
+ http://uddi.org/pubs/uddi_v3.htm#keyGen
+ </overviewURL>
+ </overviewDoc>
+ <categoryBag>
+ <keyedReference tModelKey="uddi:uddi.org:categorization:types"
+ keyName="uddi-org:types:keyGenerator"
+ keyValue="keyGenerator" />
+ </categoryBag>
+ </tModel>
+</save_tModel>
+----
+If we are going to user the marketing publisher to subscribe to updates in the sales registry, then we need to provide this publisher with two clerks in the uddi.xml of the uddi-portlet.war.
+----
+<clerks registerOnStartup="false">
+ <clerk name="MarketingCratchit" node="default"
+ publisher="marketing" password="marketing"/>
+
+ <clerk name="SalesCratchit" node="sales-ws"
+ publisher="marketing" password="marketing"/>
+ <!-- optional
+ <xregister>
+ <servicebinding
+ entityKey="uddi:marketing.apache.org:servicebindings-subscriptionlistener-ws"
+ fromClerk="MarketingCratchit" toClerk="SalesCratchit"/>
+ </xregister>
+ -->
+</clerks>
+----
+Here we created two clerks for this publisher called 'MarketingCratchit' and 'SalesCratchit'. This will allow the publisher to check the existing subscriptions owned by this publisher in each of the two systems.
+
+=== Synchronous Notifications
+While being logged in as the marketing publisher on the marketing portal, we should see the following when selecting the UDDISubscription Portlet.
+
+image::images/a_bothup_b_sales_down.png
+
+Figure 10.6. Subscriptions. In (a) both nodes are up while in (b) the sales node is down
+
+
+When both nodes came up green you can lick on the 'new subscription' icon in the toolbar. Since we are going to use this subscription synchronously only the Binding Key and Notification Interval should be left blank, as shown in Figure 10.7, "Create a New Subscription". Click the save icon to save the subscription.
+
+image::images/create_new_subscription.png
+
+Figure 10.7. Create a New Subscription
+
+
+Make sure that the subscription Key uses the convention of the keyGenerator of the marketing publisher. You should see the orange subscription icon appear under the "sales-ws" UDDI node.
+
+image::images/newly_saved_subscription.png
+
+Figure 10.9. Set the Coverage Period
+
+
+Click the green arrows icon again to invoke the synchronous subscription request. The example finder request will go out to the sales node and look for updates on the HelloWorld service. The raw XML response will be posted in the UDDISubscriptionNotification Portlet.
+
+image::images/raw_XML_response_synchronous_subscription_request.png
+
+Figure 10.10. The Raw XML response of the synchronous Subscription request
+
+
+The response will also be consumed by the marketing node. The marketing node will 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 Figure 10.11, "The registry info of the HelloWorld Service information was imported by the subscription mechanism.".
+
+image::images/registry_info_helloworld.png
+
+Figure 10.11. The registry info of the HelloWorld Service information was imported by the subscription mechanism.
+
+
+=== Using the 3.2+ Subscription callback API
+
+Since 3.2, a newer simplified subscription API was included in the juddi-client JAR file. See the sample in the uddi-samples project.
\ No newline at end of file
Added: juddi/docs/trunk/Guide/en-US/GuideUsingDigitalSignaturesinUDDI.asciidoc
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/Guide/en-US/GuideUsingDigitalSignaturesinUDDI.asciidoc?rev=1564021&view=auto
==============================================================================
--- juddi/docs/trunk/Guide/en-US/GuideUsingDigitalSignaturesinUDDI.asciidoc (added)
+++ juddi/docs/trunk/Guide/en-US/GuideUsingDigitalSignaturesinUDDI.asciidoc Mon Feb 3 19:34:34 2014
@@ -0,0 +1,37 @@
+[[DigitalSignatures]]
+== Digital Signatures
+
+Users of UDDI can use digital signatures to ensure that no unauthorized users alter the content of UDDI. We're sure that one of the first questions one would ask is "can't access control rules handle this problem for us?" The answer is yes, however it does not mitigate the risk of a number of opportunities for electronic attack.
+
+=== Requirements
+
+UDDI supports both the XML Digital Signature specification, which effectively means that you can use PGP Keys and X509 certificates. jUDDI provides out of the box support for X509 certificates and the Public Key Infrastructure (PKI). If you require direct PGP signing support, please open a JIRA ticket.
+
+=== Using Digital Signatures using the jUDDI GUI
+
+Please see <<GuideUsingthejUDDIGUI#UsingDigitalSignatures>>.
+
+[qanda]
+=== Frequently Asked Questions
+
+Doesn't UDDI access control rules prevent alteration of the content?::
+Yes, however it does not mitigate the man in the middle attack vectors. Since UDDI is used to determine the location of the thing you want, it's possible that falsified endpoints can be interjected in transport. The target service requires authentication, then the end user's credentials could be compromised without their knowledge.
+
+How can I sign a business, service, tModel or binding?::
+ Use the juddi-gui's digital signature applet by first located the item in the juddi-gui interface, then click on the "Sign" button. You need write access to the entity.
+
+The digital signature applet doesn't run. Now what?::
+ The applet requires the Java browser plugin. Unfortunately, due to recent (2013) security vulnerabilities, many places of business have heeded Oracle's advice and have disabled the browser plugin. There are other options, however.
+
+What other tools can I use to sign a UDDI entity?::
+
+TBD
+
+What is a signature?::
+ It's basically a cryptographic (a fancy math equation) using a set a keys (one is public and everyone can see/know it, the other only is held by the owner) that proves that the owner signed a piece of data.
+
+How is a signature verified?::
+There's a few ways, we can prove mathematically that the signature is valid (the content hasn't been modified). From there we can also verify that the signing key is valid.
+
+How do we know the signing key is valid?::
+Most certificates (key pairs) have some kind of mechanism in it to verify if the certificate has been revoked. If your certificate has it, it will be labeled with something like OCSP or CRL. Both of these are supported in both .NET and Java juddi-clients as well as via the juddi-gui.
\ No newline at end of file
Added: juddi/docs/trunk/Guide/en-US/_Sidebar.asciidoc
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/Guide/en-US/_Sidebar.asciidoc?rev=1564021&view=auto
==============================================================================
--- juddi/docs/trunk/Guide/en-US/_Sidebar.asciidoc (added)
+++ juddi/docs/trunk/Guide/en-US/_Sidebar.asciidoc Mon Feb 3 19:34:34 2014
@@ -0,0 +1,15 @@
+.Contents
+****
+link:GuideUDDIRegistryIntroduction[UDDI Introduction] +
+link:GuideGettingStarted[Getting Started] +
+link:GuideAdministration[Administration] +
+link:GuideConfigurationServer[Server Configuration] +
+link:GuideRootSeedData[Root Seed Data] +
+link:GuideHowToDeployjUDDITo[How to Deploy To?] +
+link:GuideExtendingUDDI[Extending jUDDI] +
+link:GuideUsingDigitalSignaturesinUDDI[Digital Signatures] +
+link:GuideUDDISubscriptions[Subscriptions] +
+link:GuideTroubleshootingjUDDI[Troubleshooting] +
+link:GuideContributingtojUDDI[Contributing] +
+****
+link:Readme[Readme] +
Added: juddi/docs/trunk/Guide/en-US/asciidoctor.css
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/Guide/en-US/asciidoctor.css?rev=1564021&view=auto
==============================================================================
--- juddi/docs/trunk/Guide/en-US/asciidoctor.css (added)
+++ juddi/docs/trunk/Guide/en-US/asciidoctor.css Mon Feb 3 19:34:34 2014
@@ -0,0 +1,80 @@
+@import url("documentation.css");
+@import url("docnav.css");
+@import url("reports.css");
+@import url("extensions.css");
+@import url("codehighlight.css");
+
+body {
+ background-image:url(../images/community/bkg_gradient.gif);
+ background-repeat:repeat-x;
+ margin:0 auto;
+ font-family:'Lucida Grande', Geneva, Verdana, Arial, sans-serif;
+ font-size:12px;
+ max-width:55em;
+ padding:0em 2em;
+ color:#333;
+ line-height:150%;
+ text-align:justify;
+}
+
+/* Links */
+
+a:link {color:#0066cc;}
+
+a:visited {color:#6699cc;}
+
+div.longdesc-link {
+ float:right;
+ color:#999;
+}
+
+/* Headings */
+
+h1, h2, h3, h4, h5, h6 {
+ color:#4a5d75;
+ line-height:130%;
+ margin-top:0em;
+ font-family:'Lucida Grande', Geneva, Verdana, Arial, sans-serif;
+ background-color:transparent;
+}
+
+h1 {
+ background-image:url(../images/community/title_hdr.png);
+ background-repeat:no-repeat;
+ border-top:1px dotted #CCCCCC;
+ line-height:1.2em;
+ color:#182737;
+ font-size:2em;
+ padding:1.5em;
+}
+
+h2 {font-size:1.6em;}
+
+h3 {
+ font-size:1.3em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+
+h4 {
+ font-size:1.1em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+
+h5.formalpara {
+ font-size:1em;
+ margin-top:2em;
+ margin-bottom:.8em;
+}
+
+/* Element rules */
+
+hr {
+ border-collapse:collapse;
+ border-style:none;
+ border-top:1px dotted #ccc;
+ width:100% !important;
+}
+
+sup {color:#999;}
Added: juddi/docs/trunk/Guide/pom.xml
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/Guide/pom.xml?rev=1564021&view=auto
==============================================================================
--- juddi/docs/trunk/Guide/pom.xml (added)
+++ juddi/docs/trunk/Guide/pom.xml Mon Feb 3 19:34:34 2014
@@ -0,0 +1,194 @@
+<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
+
+ <modelVersion>4.0.0</modelVersion>
+ <parent>
+ <groupId>org.apache.juddi.juddi-docs</groupId>
+ <artifactId>juddi-guide-parent</artifactId>
+ <version>3.2.0-SNAPSHOT</version>
+ </parent>
+ <artifactId>juddi-guide</artifactId>
+ <packaging>jdocbook</packaging>
+ <name>jUDDI Guide</name>
+ <description>The documentation for the Apache jUDDI project.</description>
+
+ <build>
+ <plugins>
+ <plugin>
+ <groupId>org.asciidoctor</groupId>
+ <artifactId>asciidoctor-maven-plugin</artifactId>
+ <version>0.1.4</version>
+ <executions>
+ <execution>
+ <id>output-docbook</id>
+ <phase>generate-resources</phase>
+ <goals>
+ <goal>process-asciidoc</goal>
+ </goals>
+ </execution>
+ </executions>
+ <configuration>
+ <sourceDirectory>en-US</sourceDirectory>
+ <outputDirectory>target/docbook/en-US</outputDirectory>
+ <imagesDir>.</imagesDir>
+ <backend>docbook5</backend>
+ <doctype>book</doctype>
+ </configuration>
+ </plugin>
+ <plugin>
+ <groupId>org.jboss.maven.plugins</groupId>
+ <artifactId>maven-jdocbook-plugin</artifactId>
+ <version>2.3.8</version>
+ <extensions>true</extensions>
+ <dependencies>
+ <dependency>
+ <groupId>org.jboss.pressgang</groupId>
+ <artifactId>pressgang-xslt-ns</artifactId>
+ <version>3.0.0</version>
+ </dependency>
+ <dependency>
+ <groupId>org.jboss.pressgang</groupId>
+ <artifactId>pressgang-jdocbook-style</artifactId>
+ <type>jdocbook-style</type>
+ <version>3.0.0</version>
+ </dependency>
+ </dependencies>
+ <configuration>
+ <sourceDocumentName>Guide.xml</sourceDocumentName>
+ <sourceDirectory>target/docbook/</sourceDirectory>
+ <imageResource>
+ <directory>${project.parent.basedir}/</directory>
+ <includes>
+ <include>images/*</include>
+ <include>images/community/*</include>
+ </includes>
+ </imageResource>
+
+ <formats>
+ <format>
+ <formatName>html</formatName>
+ <stylesheetResource>classpath:/xslt/org/jboss/pressgang/xhtml.xsl</stylesheetResource>
+ <finalName>index.html</finalName>
+ </format>
+ <format>
+ <formatName>html_single</formatName>
+ <stylesheetResource>classpath:/xslt/org/jboss/pressgang/xhtml-single.xsl</stylesheetResource>
+ <finalName>index.html</finalName>
+ </format>
+
+ <format>
+ <formatName>pdf</formatName>
+ <stylesheetResource>classpath:/xslt/org/jboss/pressgang/pdf.xsl</stylesheetResource>
+ <finalName>jUDDI_Guide.pdf</finalName>
+ </format>
+ </formats>
+ <options>
+ <xincludeSupported>true</xincludeSupported>
+ <xmlTransformerType>saxon</xmlTransformerType>
+ <docbookVersion>1.72.0</docbookVersion>
+ <transformerParameters>
+ <property>
+ <name>javax.xml.parsers.DocumentBuilderFactory</name>
+ <value>org.apache.xerces.jaxp.DocumentBuilderFactoryImpl</value>
+ </property>
+ <property>
+ <name>javax.xml.parsers.SAXParserFactory</name>
+ <value>org.apache.xerces.jaxp.SAXParserFactoryImpl</value>
+ </property>
+ </transformerParameters>
+ </options>
+ </configuration>
+ </plugin>
+ </plugins>
+ <pluginManagement>
+ <plugins>
+ <!--This plugin's configuration is used to store Eclipse m2e settings only. It has no influence on the
+ Maven build itself. -->
+ <plugin>
+ <groupId>org.eclipse.m2e</groupId>
+ <artifactId>lifecycle-mapping</artifactId>
+ <version>1.0.0</version>
+ <configuration>
+ <lifecycleMappingMetadata>
+ <pluginExecutions>
+ <pluginExecution>
+ <pluginExecutionFilter>
+ <groupId>org.asciidoctor</groupId>
+ <artifactId>asciidoctor-maven-plugin</artifactId>
+ <versionRange>[0.1.1,)</versionRange>
+ <goals>
+ <goal>process-asciidoc</goal>
+ </goals>
+ </pluginExecutionFilter>
+ <action>
+ <ignore />
+ </action>
+ </pluginExecution>
+ <pluginExecution>
+ <pluginExecutionFilter>
+ <groupId>org.jboss.maven.plugins</groupId>
+ <artifactId>maven-jdocbook-plugin</artifactId>
+ <versionRange>[2.3.8,)</versionRange>
+ <goals>
+ <goal>generate</goal>
+ <goal>resources</goal>
+ </goals>
+ </pluginExecutionFilter>
+ <action>
+ <ignore />
+ </action>
+ </pluginExecution>
+ </pluginExecutions>
+ </lifecycleMappingMetadata>
+ </configuration>
+ </plugin>
+ </plugins>
+ </pluginManagement>
+ </build>
+ <profiles>
+ <!-- START SNIPPET: release-profile -->
+ <!-- this is borrowed from an nov 2009 apache-7 pom release attempt-->
+ <profile>
+ <id>apache-release</id>
+ <build>
+ <plugins>
+ <!-- Create a source-release artifact that contains the fully buildable
+ project directory source structure. This is the artifact which is
+ the official subject of any release vote. -->
+ <plugin>
+ <artifactId>maven-assembly-plugin</artifactId>
+ <dependencies>
+ <dependency>
+ <groupId>org.apache.apache.resources</groupId>
+ <artifactId>apache-source-release-assembly-descriptor</artifactId>
+ <version>1.0.1</version>
+ </dependency>
+ <dependency>
+ <!-- NOTE: The fix for PLXUTILS-120 is crucial for the new assembly descriptor -->
+ <groupId>org.codehaus.plexus</groupId>
+ <artifactId>plexus-utils</artifactId>
+ <version>2.0.1</version>
+ </dependency>
+ </dependencies>
+ <executions>
+ <execution>
+ <id>source-release-assembly</id>
+ <phase>package</phase>
+ <goals>
+ <goal>single</goal>
+ </goals>
+ <configuration>
+ <runOnlyAtExecutionRoot>true</runOnlyAtExecutionRoot>
+ <descriptorRefs>
+ <descriptorRef>${sourceReleaseAssemblyDescriptor}</descriptorRef>
+ </descriptorRefs>
+ <tarLongFileFormat>gnu</tarLongFileFormat>
+ </configuration>
+ </execution>
+ </executions>
+ </plugin>
+ </plugins>
+ </build>
+ </profile>
+ <!-- END SNIPPET: release-profile -->
+ </profiles>
+</project>
Added: juddi/docs/trunk/Home.asciidoc
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/Home.asciidoc?rev=1564021&view=auto
==============================================================================
--- juddi/docs/trunk/Home.asciidoc (added)
+++ juddi/docs/trunk/Home.asciidoc Mon Feb 3 19:34:34 2014
@@ -0,0 +1,8 @@
+Welcome to the juddi wiki!
+
+jUDDI User Guide
+~~~~~~~~~~~~~~~~~
+The link:wiki/Guide[jUDDI Guide] and the link:wiki/ClientGuide[jUDDI Client Guide] are written in http://www.methods.co.nz/asciidoc/[asciidoc] and the source is published right in this wiki. So, you can edit the documentation right on master, see the link:wiki/GuideReadme[Readme] for more detail on this. The http://powerman.name/doc/asciidoc[Asciidoc cheat-sheet] is a nice place to start learning about Asciidoc itself.
+
+* Pages that start with "Guide" make up the link:wiki/Guide[jUDDI Guide]
+* Pages that start with "ClientGuide" make up the link:wiki/ClientGuide[jUDDI Client Guide]
Added: juddi/docs/trunk/Readme.asciidoc
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/Readme.asciidoc?rev=1564021&view=auto
==============================================================================
--- juddi/docs/trunk/Readme.asciidoc (added)
+++ juddi/docs/trunk/Readme.asciidoc Mon Feb 3 19:34:34 2014
@@ -0,0 +1,58 @@
+How to build the jUDDI Guide Book in Docbook format?
+====================================================
+
+This jUDDI wiki is the source of the jUDDI Guide document. The directory layout of the wiki in this example is
+....
+âââ Guide
+â  âââ en-US
+â  âââ Guide-docinfo.xml
+â  âââ Guide.asciidoc
+â  âââ GuideDatabase-Connection-Setup.asciidoc
+â  âââ GuideReadme.asciidoc
+â  âââ _Sidebar.asciidoc
+âââ Home.md
+âââ JUDDI.asciidoc
+âââ Readme.asciidoc
+âââ images
+âââ pom.xml
+....
+
+The Guide document is based on the Asciidoc http://www.methods.co.nz/asciidoc/book.txt[book.txt] example, and a Guide-docinfo.xml include file to support more then one author. The http://asciidoctor.org/[AsciiDoctor] maven plugin converts the asciidoc files into an intermediate Docbook format ('Guide.xml'), which then is used as input for _maven-jdocbook-plugin_ to create HTML and PDF versions. If you want to build these yourself you need to check out the repository locally using:
+----
+git clone git@github.com/UDDI/juddi.wiki.git
+----
+and run:
+----
+mvn clean install
+----
+and it will build HTML and PDF versions in the target/docbook/publish/en-US directory.
+
+[qanda]
+.Q&A
+I spotted a typo, can I fix it?::
+Yes please help us maintain the documentation. Simpy update the
+appropriate page right on
+https://github.com/UDDI/juddi/wiki/Guide[github]. Our nightly
+build will distribute the changes to docbook and the html and pdf
+versions.
+
+How do I add an image?::
+Images can not be uploaded through the github UI. Instead you need to add them to the `images` directory in the root of the juddi.wiki repo and then push it up to github. You can then reference your image on the page using `image::images/<myimage>.ext`.
+NOTE: Make sure to add an empty line before and after this image reference.
+
+How do add a numbering and references?::
+You should add a label -we use the convention
+<type>-<chapter>-<label>, i.e.
+`[[figure-UDDIREG-Invocation Pattern]]`- , a title i.e.
+`.Invocation Pattern using the UDDI Registry.` and then the thing itself -for an
+image use something like `image::images/UDDI_Registry_invocation_pattern.png[Invocation Pattern using the UDDI Registry]`. The label `figure-UDDIREG-Invocation Pattern` can be used to link to this figure using
+`<<figure-UDDIREG-Invocation Pattern>>`. The link:GuideUDDIRegistryIntroduction[UDDIRegistryIntroduction] contains an example.
+
+How do I add a chapter to the book in docbook?::
+We add chapters as different files, and then include them in the
+`Guide.asciidoc` file. At docbook generation time it will pull in the
+chapter into the `Guide.xml` file. Also we add a link in the `_Sidebar.asciidoc`
+page to have a link when looking at it at Github in wiki style.
+
+Why are all the files prefixed with `Guide`?::
+The GitHub wiki flattens out the directory structure on the link:_pages[Pages] page. So in order to group all the files of the Guide together we decided to prefix them all with `Guide`.
Added: juddi/docs/trunk/images/GettingStarted-add_publisher.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/GettingStarted-add_publisher.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/GettingStarted-add_publisher.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/GettingStarted-authToken_SoapUI.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/GettingStarted-authToken_SoapUI.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/GettingStarted-authToken_SoapUI.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/GettingStarted-create_business.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/GettingStarted-create_business.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/GettingStarted-create_business.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/GettingStarted-create_keygenerator.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/GettingStarted-create_keygenerator.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/GettingStarted-create_keygenerator.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/GettingStarted-form_login.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/GettingStarted-form_login.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/GettingStarted-form_login.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/GettingStarted-happy_juddi.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/GettingStarted-happy_juddi.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/GettingStarted-happy_juddi.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/GettingStarted-jUDDI_admin.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/GettingStarted-jUDDI_admin.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/GettingStarted-jUDDI_admin.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/GettingStarted-jUDDI_welcome.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/GettingStarted-jUDDI_welcome.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/GettingStarted-jUDDI_welcome.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/GettingStarted-juddi_services.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/GettingStarted-juddi_services.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/GettingStarted-juddi_services.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/UDDI_Registry_invocation_pattern.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/UDDI_Registry_invocation_pattern.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/UDDI_Registry_invocation_pattern.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/UDDI_services_overview.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/UDDI_services_overview.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/UDDI_services_overview.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/a_bothup_b_sales_down.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/a_bothup_b_sales_down.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/a_bothup_b_sales_down.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/community/community_doc.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/community/community_doc.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/community/community_doc.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/community/jbossorglogo.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/community/jbossorglogo.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/community/jbossorglogo.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/community/title_hdr.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/community/title_hdr.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/community/title_hdr.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/create_new_subscription.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/create_new_subscription.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/create_new_subscription.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/icon.svg
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/icon.svg?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/icon.svg
------------------------------------------------------------------------------
svn:mime-type = image/svg+xml
Added: juddi/docs/trunk/images/jUDDIArchitecture_Gui.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/jUDDIArchitecture_Gui.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/jUDDIArchitecture_Gui.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/jUDDIArchitecture_clientAndGui.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/jUDDIArchitecture_clientAndGui.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/jUDDIArchitecture_clientAndGui.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/jUDDIArchitecture_server.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/jUDDIArchitecture_server.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/jUDDIArchitecture_server.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-admin-configure.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-admin-configure.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-admin-configure.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-admin-home.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-admin-home.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-admin-home.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-admin-juddiapi.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-admin-juddiapi.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-admin-juddiapi.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-admin-mbeans.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-admin-mbeans.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-admin-mbeans.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-admin-stats.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-admin-stats.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-admin-stats.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-admin-status.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-admin-status.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-admin-status.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-gui-browse-business.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-gui-browse-business.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-gui-browse-business.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-gui-browse-business2.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-gui-browse-business2.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-gui-browse-business2.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-gui-browse-options.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-gui-browse-options.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-gui-browse-options.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-gui-browse-services.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-gui-browse-services.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-gui-browse-services.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-gui-browse-tmodel.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-gui-browse-tmodel.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-gui-browse-tmodel.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-gui-create-business.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-gui-create-business.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-gui-create-business.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-gui-create-business2.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-gui-create-business2.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-gui-create-business2.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-gui-create-business3.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-gui-create-business3.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-gui-create-business3.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-gui-fullbootstrap-menu.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-gui-fullbootstrap-menu.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-gui-fullbootstrap-menu.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-gui-import-wsdl.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-gui-import-wsdl.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-gui-import-wsdl.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-gui-login-warning.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-gui-login-warning.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-gui-login-warning.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-gui-menu.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-gui-menu.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-gui-menu.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-gui-mybuz.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-gui-mybuz.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-gui-mybuz.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-gui-nodeswitcher.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-gui-nodeswitcher.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-gui-nodeswitcher.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-gui-publisherassertion.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-gui-publisherassertion.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-gui-publisherassertion.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-gui-publisherassertion2.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-gui-publisherassertion2.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-gui-publisherassertion2.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-gui-publisherassertion3.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-gui-publisherassertion3.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-gui-publisherassertion3.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-gui-search.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-gui-search.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-gui-search.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-gui-service-add1.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-gui-service-add1.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-gui-service-add1.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-gui-service-add2.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-gui-service-add2.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-gui-service-add2.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-gui-sign1.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-gui-sign1.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-gui-sign1.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-gui-sign2.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-gui-sign2.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-gui-sign2.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-gui-signed-invalid.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-gui-signed-invalid.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
Propchange: juddi/docs/trunk/images/juddi-gui-signed-invalid.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: juddi/docs/trunk/images/juddi-gui-signed-valid.png
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/images/juddi-gui-signed-valid.png?rev=1564021&view=auto
==============================================================================
Binary file - no diff available.
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@juddi.apache.org
For additional commands, e-mail: commits-help@juddi.apache.org