You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@juddi.apache.org by sv...@apache.org on 2003/11/11 15:02:10 UTC
cvs commit: ws-juddi/docs/images components.png conncache.gif deployWiz.gif instApp.gif juddiWebApp.gif juddiprops.gif overview.png resourceref.gif screenshot.png
sviens 2003/11/11 06:02:10
Added: docs deploy.html develop.html download.html
easerver.html faq.html header.html index.html
juddi.css license.html lists.html overview.html
toc.html udditest-uddi4j.html
docs/images components.png conncache.gif deployWiz.gif
instApp.gif juddiWebApp.gif juddiprops.gif
overview.png resourceref.gif screenshot.png
Log:
Moved from jUDDI CVS at SourceForge
Revision Changes Path
1.1 ws-juddi/docs/deploy.html
Index: deploy.html
===================================================================
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<title>jUDDI Deployment Guide</title>
<link rel="stylesheet" href="juddi.css" />
</head>
<table cellspacing="10">
<tr>
<td valign="top" width="100%" height="100%"> <div class="announcement">
<h3>jUDDI Deployment Guide</h3>
</div>
<p>jUDDI is a pure Java web application and as such can be deployed to any
application server or servlet engine that supports version 2.1 or later
of the servlet API. If you need an application server, we recommend <a href="http://jakarta.apache.org/tomcat/index.html" target="_top">Jakarta
Tomcat</a>. Note also that jUDDI requires Java 1.3 or later. As with any
Java web application, deployment to your application server or servlet
engine will vary on a product-by-product basis. </p>
<p>When deploying jUDDI you may wish to make changes to the <a href="../conf/juddi.properties">juddi.properties</a>
and <a href="../conf/log4j.properties">log4j.properties</a> files. These
files are located in the juddi webapp's WEB-INF/classes directory. They're
here because they need to be in the classpath for jUDDI to locate and
load them at runtime. One Log4j property value that you'll most likely
want to set is <strong>log4j.appender.LOGFILE.File</strong> which specifies
the name and location of the jUDDI log file.</p>
<p>You'll need to restart Tomcat or reload the jUDDI web application after
setting these values.</p>
<p>To properly configure and deploy jUDDI it will be helpful to understand
a bit about it's architecture. jUDDI consist a core request processor
that handles unmarshalling UDDI requests, invoking the appropriate UDDI
function and marshalling UDDI responses (marshalling and unmarshalling
is the process of converting XML data to/from Java objects). </p>
<p>To invoke a UDDI function jUDDI employs the services of three configurable
sub-components or modules that handle persistence (the DataStore), authentication
(the Authenticator) and the generation of UUID's (the UUIDGen). jUDDI
is bundled and pre-configured to use default implementations of each of
these modules to help you get jUDDI up and running quickly. Each of these
module categories and a description of the default implementations are
described below.</p>
<p>Several public Java interfaces for creating your own DataStore, Authenticator
and UUIDGen module implementations are available. Please see the <a href="develop.html">jUDDI
Developer's Guide</a> for more information regarding jUDDI module development.</p>
<h4>Persistence (jUDDI DataStore)</h4>
<p>The default jUDDI DataStore is implemented using JDBC and the process
of setting this up is fairly straight forward. Start by creating a new
jUDDI database using one of the following database schemas. </p>
<ol>
<li><a href="dbscripts/juddi_mysql.sql">MySQL</a></li>
<li><a href="dbscripts/juddi_db2.sql">DB2</a></li>
<li><a href="dbscripts/juddi_hsql.sql">HSQL</a></li>
<li><a href="dbscripts/juddi_ase.sql">Sybase ASE</a></li>
<li><a href="dbscripts/juddi_jds.sql">Borland JDataStore</a></li>
<li><a href="dbscripts/juddi_postgresql.sql">PostgreSQL</a></li>
<li><a href="dbscripts/juddi_totalxml.sql">TotalXML</a></li>
</ol>
<p>If a schema for your DBMS is not listed, one simply hasn't been created
yet. If your feeling adventurous you can use the available schemas as
a guide for creating one (and if you're feeling generous please consider
contributing it back to us.)</p>
<p>To complete the DataStore set up you'll need to configure a JNDI Datasource
named 'juddiDB' in the application server or servlet engine that you're
deploying to. Datasource setup varies on an product-by-product basis so
review your application server's documentation. If you're deploying jUDDI
to Jakarta Tomcat, take a look at the <a href="http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html" target="_top">JNDI
Datasource HOW-TO</a> for assistance.</p>
<h4>Authentication (jUDDI Authenticator)</h4>
<p>The authentication of a jUDDI publisher is a two-step process. The first
step confirms that the ID/password combination provided by the user is
valid. It is expected that a typical jUDDI deployment will use an external
authentication mechanism. <strong>The default authentication module simply
approves any authentication attempt.</strong> It is our hope that additional
jUDDI authentication implementations will be developed by jUDDI users
as they determine how they would like authentication to take place in
their particular environment. See the <a href="develop.html">jUDDI Developers
Guide</a> for more information on developing a custom jUDDI authentication
module.</p>
<p>The second step confirms that the publisher has been defined to jUDDI.
A publisher is said to be defined when a row identifying the publisher
exists in the PUBLISHER table of the jUDDI datastore. At the moment the
only way to do this is via SQL. An example of defining a new publisher
named John Doe would look like this:</p>
<blockquote>
<p><font size="-1"><strong>INSERT INTO PUBLISHER (PUBLISHER_ID,PUBLISHER_NAME,ADMIN)<br />
VALUES ('jdoe','John Doe','false');</strong></font></p>
</blockquote>
<p>The PUBLISHER table consists of three columns which are defined as follows:</p>
<table width="80%" border="1" cellpadding="2" cellspacing="0">
<tr bgcolor="#999999">
<td><strong>Column Name</strong></td>
<td><strong>Description</strong></td>
</tr>
<tr valign="top">
<td width="25%" nowrap="nowrap">PUBLISHER_ID</td>
<td width="75%">The user ID the publisher uses when authenticating.<br />
IMPORTANT: This should be the same value used to authenticate with
the external authentication service. </td>
</tr>
<tr valign="top">
<td>PUBLISHER_NAME</td>
<td>The publisher's name (or in UDDI speak the Authorized Name).</td>
</tr>
<tr valign="top">
<td>ADMIN</td>
<td>Indicate if the publisher has administrative privileges. Valid values
for this column are 'true' or 'false'. The ADMIN value is currently
not used.</td>
</tr>
</table>
<p>The jUDDI web application will (eventually) be extended to facilitate
the Publisher creation process. The value of the ADMIN column in the PUBLISHER
table above will be used to determine who has the privilege to create
new jUDDI publishers.</p>
<h4>UUID Generation (jUDDI UUIDGen)</h4>
<p>There's nothing for you to do here but I thought I'd offer a little information
about how, why and where jUDDI makes use of UUID generation.</p>
<p>The UDDI specification indicates that each Business, Service, Binding
and TModel (Technical Model) is to be uniquely identified by a Universally
Unique ID (UUID). Additionally, jUDDI also uses the UUID generator to
create AuthTokens.</p>
<p>Generation of UUID's typically requires access to hardware level information
that (unfortunately) is not accessible from Java. Fortunately, the UUID
specification offers an alternative method for generating these ID's when
this hardware information is not present. By default jUDDI implements
this alternative method.<br />
<br />
</p></td>
</tr>
<tr><td height="14"><div align="left" class="footer">Copyright © 2003, <a href="mailto:steve@viens.net" target="_top">Steve Viens</a> and contributors, All rights reserved</div></td></tr>
</table>
</body>
</html>
1.1 ws-juddi/docs/develop.html
Index: develop.html
===================================================================
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<title>jUDDI Developer's Guide</title>
<link rel="stylesheet" href="juddi.css" />
</head>
<body>
<table cellspacing="10">
<tr>
<td valign="top" width="100%" height="100%">
<div class="announcement"><h3>jUDDI Developer's Guide</h3></div>
<p>This guide is currently under development. Until it is completed, the best
place for jUDDI developer support is the <a href="lists.html">juddi-users</a> mailing lists.</p>
<p></p>
</td>
</tr>
<tr><td height="14"><div align="left" class="footer">Copyright © 2003, <a href="mailto:steve@viens.net" target="_top">Steve Viens</a> and contributors, All rights reserved</div></td></tr>
</table>
</body>
</html>
1.1 ws-juddi/docs/download.html
Index: download.html
===================================================================
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<title>jUDDI Downloads</title>
<link rel="stylesheet" href="juddi.css"/>
</head>
<body>
<table cellspacing="10">
<tr>
<td valign="top" width="100%" height="100%">
<div class="announcement"><h3>jUDDI Downloads</h3></div>
<p>The latest stable version is jUDDI 0.8.0
</p>
<p>The binary distribution contains everything needed to use
jUDDI; the source distribution contains everything needed
to _develop_ with jUDDI. In other words, source and API
Javadocs are not found in the binary distribution. For
further assistance, please subscribe to the
<a href="lists.html">juddi-users</a> mailing list.
</p>
<p>Download releases directly from jUDDI's <a href="http://sourceforge.net/project/showfiles.php?group_id=42875" target="_top">File Release</a> page at SourceForge<font size="-2"><sup>TM</sup></font>.</p>
<p></p>
</td>
</tr>
<tr><td height="14"><div align="left" class="footer">Copyright © 2003, <a href="mailto:steve@viens.net" target="_top">Steve Viens</a> and contributors, All rights reserved</div></td></tr>
</table>
</body>
</html>
1.1 ws-juddi/docs/easerver.html
Index: easerver.html
===================================================================
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<title>jUDDI EAServer Deployment Guide</title>
<link rel="stylesheet" href="juddi.css" />
</head>
<table cellspacing="10">
<tr>
<td valign="top" width="100%" height="100%"> <div class="announcement">
<h3>jUDDI EAServer Deployment Guide</h3>
</div>
<p>Start EAServer and the Jagmgr. Go to the Applications in the LHS(Left Hand Side)
of the JagMgr and right click to Deploy as J2EE ear file, choose the juddi.ear
and click Deploy. <p><IMG src="images/deployWiz.gif">
<p>After the deployment is succesful, Go to your server in the LHS and install the
application - right click on the "Installed Applications" in the LHS,
<p><IMG src="images/instApp.gif">
<p>choose "Install an Existing Application" and then pick jUDDI.
<h4>Resource Reference</h4>
<p>Create a connection cache to your juddiDB
<p><IMG src="images/conncache.gif"></p>
<p>For more information on connection caches visit</p>
<p>http://sybooks.sybase.com/onlinebooks/group-eag/eag0420e/eas_sag/@Generic__BookView?DwebQuery=connection+cache</p>
<p>Open the Installed Application jUDDI and go to the Web Application under that,
right click to choose the "Web Application Properties", go to the
"Resource Refs" tab and change the name to "jdbc/juddiDB".</p>
<p><IMG src="images/resourceref.gif"></p>
<p>In the "Resource
Link" drop down, choose the connection cache for jUDDI DB.</p>
<p>In the "Environment" tab, change the juddi.properties and the
log4j.properties file location.</p>
<p><IMG src="images/juddiprops.gif"></p>
<p>Restart the server and test the deployment with
http://yourserver:8080/juddi/index.html
http://yourserver:8080/juddi/datasource_test.jsp</p>
</td>
</tr>
<tr><td height="14"><div align="left" class="footer">Copyright © 2003, <a href="mailto:steve@viens.net" target="_top">Steve Viens</a> and contributors, All rights reserved</div></td></tr>
</table>
</body>
</html>
1.1 ws-juddi/docs/faq.html
Index: faq.html
===================================================================
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<title>jUDDI FAQ</title>
<link rel="stylesheet" href="juddi.css" />
</head>
<body>
<table cellspacing="10">
<tr>
<td valign="top" width="100%" height="100%">
<div class="announcement"><h3>jUDDI Frequently Asked Questions (FAQ)</h3></div>
<div class=Section1>
<ul type=disc>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo3;tab-stops:list .5in'><a href="#_JDK_Requirements">What
JDK can you use for jUDDI?</a> </li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo3;tab-stops:list .5in'><a href="#_Using_an_embedded">Do
I need to use JNDI?</a> </li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo3;tab-stops:list .5in'><a
href="#_Configuring_Tomcat/_MySQL">How do I configure jUDDI to run with Tomcat,
MySQL and use a JNDI DataSource?</a> </li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo3;tab-stops:list .5in'><a
href="#_Writing_a_pluggable">Can I change the way jUDDI authenticates
publishers?</a> </li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo3;tab-stops:list .5in'><a href="#_Using_a_datastore">Using
a datastore without JDBC</a> </li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo3;tab-stops:list .5in'><a href="#_Can_I_use">Which
Application Servers does jUDDI support?</a> </li>
</ul>
<h3><a name="_JDK_Requirements"></a>JDK Requirements</h3>
<p class=MsoNormal>jUDDI 0.7 requires a 1.4.x JDK. You can compile and run with
a 1.3.x JDK, if you remove the package org.apache.juddi.auth.crypt from your codebase.
</p>
<h3><a name="_Using_an_embedded"></a>Using an embedded database</h3>
<p class=MsoNormal>You can use the juddi.useConnectionPool property (and other
related properties) to avoid using the JNDI lookup. Here's a sample setup of
juddi.properties </p>
<p class=MsoNormal style='margin-right:.5in;mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;margin-left:.5in'># required JDBC DataSource properties<br>
juddi.dataSource = java:comp/env/jdbc/juddiDB<br>
<br>
# required JDBC Driver properties<br>
juddi.useConnectionPool = true<br>
juddi.jdbcDriver = org.hsqldb.jdbcDriver<br>
juddi.jdbcURL =
jdbc:hsqldb:C:/jakarta-tomcat/server/webapps/juddi/WEB-INF/hsql/juddidb<br>
juddi.jdbcUser = sa<br>
juddi.jdbcPassword =<br>
<br>
# optional JDBC Driver connection pool properties<br>
juddi.jdbcMinConnections = 3<br>
juddi.jdbcMaxConnections = 50<br>
juddi.jdbcMaxWaitTime = 15000<br>
juddi.jdbcRetryInterval = 1000</p>
<h3><a name="_Configuring_Tomcat/_MySQL"></a>How do I configure jUDDI to run with Tomcat, MySQL and use a JNDI DataSource?</h3>
<p class=MsoNormal>A good setup is discussed here <a
href="http://sourceforge.net/mailarchive/forum.php?thread_id=2429672&forum_id=7138" target="_setup">http://sourceforge.net/mailarchive/forum.php?thread_id=2429672&forum_id=7138</a>
<h3><a name="_Writing_a_pluggable"></a>Writing a pluggable authentication module</h3>
<p class=MsoNormal>
You can configure jUDDI to use one of the three Authentication modules supplied or you can write your own Authenticator that integrates jUDDI with your organizations authentication mechanism. All you have to do to create your own Authenticator is:
</p>
<ul>
<li>create a class that implements the Authenticator interface (your Authenticator)
<li>create a class that extends the AuthenticatorFactory abstract class (your Authenticator's Factory)
<li>specify your AuthenticatorFactory in jUDDI's property file ("juddi.properties").
</ul>
Example: <b>juddi.authFactory = org.apache.juddi.auth.simple.SimpleAuthenticatorFactory</b>
<p>
In the example above you'll need to replace "org.apache.juddi.auth.simple.SimpleAuthenticatorFactory" with the fully qualified name of your AuthenticatorFactory class. Take a look at the SimpleAuthenticator & SimpleAuthenticationFactory classes in the "org.apache.juddi.auth.simple" package for an example
</p>
<h3><a name="_Using_a_datastore"></a>Using a datastore without JDBC</h3>
<p class=MsoNormal>jUDDI is designed to allow different persistence (datastore)
implementations to be "plugged-in". The JDBCDataStore included with
jUDDI attempts to support as many as the mainstream RDBMS's as possible
(Oracle, DB2, Sybase, MySQL - even HSQLDB). </p>
<p>If you're interested in using something other than JDBC or if you want to
take advantages of proprietary features of your RDBMS (i.e. using stored
procedures to improve performance) then you will need to develop your own
datastore implementation. To do so you'll need to create implementations of the
DataStoreFactory and DataStore interfaces in the org.apache.juddi.datastore package
and make a change to the jUDDI properties file to use your new DataStoreFactory
implementation (i.e. the judd.dataStoreFactory property) instead of the one
supplied. </p>
<p>Check out jUDDI's JDBCDataStoreFactory and JDBCDataStore for examples. </p>
<h3><a name="_Can_I_use"></a>Which Application Servers does jUDDI support?</h3>
<p class=MsoNormal>jUDDI is known to work with a number of application
servers like Tomcat, Sybase EAServer and Borland Enterprise Server 5.2.
A Sybase EAServer deployment guide is available <a href="easerver.html" target="_easerver">here</a>.</p>
<p class=MsoNormal><br />
<b><i>jUDDI FAQ Contributors:<br>
</i></b> <em>Steve Viens</em><br>
<em>Anou Manavalan</em><br>
<em>Rupesh Ramachandran</em><br>
<em>Andy Cutright</em> </p>
<p class=MsoNormal><![if !supportEmptyParas]> <![endif]><o:p></o:p></p>
</div>
</td>
</tr>
<tr><td height="14"><div align="left" class="footer">Copyright © 2003, <a href="mailto:steve@viens.net" target="_top">Steve Viens</a> and contributors, All rights reserved</div></td></tr>
</table>
</body>
</html>
1.1 ws-juddi/docs/header.html
Index: header.html
===================================================================
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<link rel="stylesheet" href="juddi.css"/>
</head>
<body><div class="nav" align="right"><font size="-2"><a href="http://www.juddi.org/" target="_top">jUDDI.org</a></font></div><h1>jUDDI</h1></body></html>
1.1 ws-juddi/docs/index.html
Index: index.html
===================================================================
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<HEAD>
<BASE target="content"/>
<TITLE>jUDDI</TITLE>
</HEAD>
<FRAMESET rows="78,*" frameborder="NO">
<FRAME src="header.html" noresize scrolling="NO">
<FRAMESET rows="100%" frameborder="NO" cols="140,*">
<FRAME src="toc.html" noresize scrolling="NO" name="index">
<FRAME src="overview.html" scrolling="AUTO" noresize name="content">
<NOFRAMES>
<BODY>
<P>To view this page, you need a browser that supports frames.</P>
</BODY>
</NOFRAMES>
</FRAMESET>
</FRAMESET>
</HTML>
1.1 ws-juddi/docs/juddi.css
Index: juddi.css
===================================================================
body {
margin: 0px 10px 10px 10px;
font-family: "Trebuchet MS", sans-serif;
font-size: 10pt;
background: #FFF;
color: #000;
}
h1 {
font-family: "Trebuchet MS", sans-serif;
background: #00005A;
font-weight: normal;
color: White;
padding: 5px 10px;
margin: 0px -10px 10px -10px;
}
h2 {
font-family: "Trebuchet MS", sans-serif;
color: #00005A;
}
h3 {
font-family: "Trebuchet MS", sans-serif;
color: #00005A;
}
h4 {
font-family: "Trebuchet MS", sans-serif;
color: #00005A;
}
.sidebar {
border: 1px solid #00005A;
background: #EEE;
padding: 5px;
}
pre.code_sample {
background: #EEE;
padding: 5px;
}
dt {
font-weight: bold;
}
dl {
margin-left: 3em;
}
td {
font-size: 10pt;
}
DIV.announcement dl {
margin-left: 0px;
}
div.NAV {
background: #000;
margin: 0px -10px;
padding: 2px 10px;
color: #CCC;
font-size: 12pt;
font-weight: bold;
}
div.NAV A {
color: #CCC;
text-decoration: none;
}
div.NAV A:hover {
color: #FFF;
}
.ednote {
color: #999;
font-style: italic;
}
.cvs_id {
color: #999;
font-size: 8pt;
border-top: solid 1px #999;
}
.author {
font-size: 14pt;
font-style: italic;
}
var {
font-style: italic;
color: #900;
}
div.footer {
color: #666699; margin: 0px -10px; padding: 2px 10px; font-size: 8pt; font-weight: normal;
}
div.footer a {
color: #666699; text-decoration: none;
}
div.footer a:hover {
color: #666699; text-decoration: underline;
}
1.1 ws-juddi/docs/license.html
Index: license.html
===================================================================
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<title>jUDDI License</title>
<link rel="stylesheet" href="juddi.css" />
</head>
<body>
<table cellspacing="10">
<tr>
<td valign="top" width="100%" height="100%">
<div class="announcement"><h3>jUDDI License</h3></div>
<pre>
Copyright (c) 2003, Steve Viens and contributors.
All rights reserved. Redistribution and use in source and
binary forms, with or without modification, are permitted
provided that the following conditions are met:
* Redistributions of source code must retain the above
copyright notice, this list of conditions and the
following disclaimer.
* Redistributions in binary form must reproduce the
above copyright notice, this list of conditions and
the following disclaimer in the documentation and/or
other materials provided with the distribution.
* Neither name of Steve Viens nor the names of jUDDI
contributors may be used to endorse or promote products
derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
</pre>
</td>
</tr>
<tr><td height="14"><div align="left" class="footer">Copyright © 2003, <a href="mailto:steve@viens.net" target="_top">Steve Viens</a> and contributors, All rights reserved</div></td></tr>
</table>
</body>
</html>
1.1 ws-juddi/docs/lists.html
Index: lists.html
===================================================================
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<title>jUDDI Mailing Lists</title>
<link rel="stylesheet" href="juddi.css"/>
</head>
<body>
<table cellspacing="10">
<tr>
<td valign="top" width="100%" height="100%">
<div class="announcement"><h3>jUDDI Mailing Lists</h3></div>
The <strong>juddi-announce</strong> mailing list is used to relate general information
about the project such as when new releases become available and other 'Marketing'.
Postings to this list are infrequent.
<p>
<a href="http://lists.sourceforge.net/lists/listinfo/juddi-announce" target="_top">Subscribe</a> /
<a href="http://sourceforge.net/mailarchive/forum.php?forum_id=2809" target="_top">Archives</a>
</p>
The <strong>juddi-users</strong> mailing list is the primary source of support
for anyone using jUDDI. Use this list for posting questions (and answers)
related to the installation, configuration and use of jUDDI.
<p>
<a href="http://lists.sourceforge.net/lists/listinfo/juddi-users" target="_top">Subscribe</a> /
<a href="http://sourceforge.net/mailarchive/forum.php?forum_id=7138 target="_top"">Archives</a></p>
</p>
The <strong>juddi-developers</strong> mailing list is for discussions about
the jUDDI architecture, build process, testing and implementation details.
<p>
<a href="http://lists.sourceforge.net/lists/listinfo/juddi-developers" target="_top">Subscribe</a> /
<a href="http://sourceforge.net/mailarchive/forum.php?forum_id=2811 target="_top"">Archives</a></p>
</p>
</td>
</tr>
<tr><td height="14"><div align="left" class="footer">Copyright © 2003, <a href="mailto:steve@viens.net" target="_top">Steve Viens</a> and contributors, All rights reserved</div></td></tr>
</table>
</body>
</html>
1.1 ws-juddi/docs/overview.html
Index: overview.html
===================================================================
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<title>jUDDI Overview</title>
<link rel="stylesheet" href="juddi.css"/>
</head>
<body>
<table cellspacing="10">
<tr>
<td valign="top" width="100%" height="100%">
<div class="announcement"><h3>jUDDI Overview</h3></div>
<p>jUDDI (pronounced "Judy") is an open source Java implementation
of the Universal Description, Discovery, and Integration (UDDI) specification
for Web Services. jUDDI is licensed under the <a href="license.html">
BSD License</a> and is available for free for any use.</p>
<h4>Key Benefits</h4>
<ul>
<li>Open Source</li>
<li>Platform Independent</li>
<li>Supports for JDK 1.3.1 and later</li>
<li>UDDI version 2.0 compliant implementation</li>
<li>Use with any relational database that supports ANSI standard SQL (MySQL,
DB2, Sybase, etc.)</li>
<li>Deployable on any Java application server that supports the Servlet
2.3 specification (Jakarta Tomcat, WebSphere, WebLogic, JRun, etc.)</li>
<li>jUDDI registry supports a clustered deployment configuration.</li>
<li>Easy integration with existing authentication systems</li>
</ul>
<h4>Project News</h4>
<p><b>July 22, 2003</b><br>A proposal to contribute jUDDI to the Apache Foundation's <a href="http://ws.apache.org/" target="apache">Web
Services Project</a> is currently being considered. Click <a href="http://nagoya.apache.org/wiki/apachewiki.cgi?ProposalForJUDDI" target="apache">here</a>
to view the most resent version of the proposal.</p>
<h4>About UDDI</h4>
<p>UDDI stands for Universal Description, Discovery and Integration. The
UDDI specification enables businesses to quickly, easily, and dynamically
find and transact with one another. UDDI enables a business to (i) describe
its business and its services, (ii) discover other businesses that offer
desired services, and (iii) integrate with these other businesses. UDDI
enables companies to publish how they want to conduct business on the
web, potentially fueling growth of Web services-based electronic commerce.</p>
<p>UDDI benefits businesses of all sizes by creating a global, platform-independent,
open architecture for describing businesses and services, discovering
those businesses and services, and integrating businesses using the
Internet.</p>
<p>The UDDI project is a sweeping industry initiative. The project creates
a platform-independent, open framework for describing services, discovering
businesses, and integrating business services using the Internet, as
well as an operational registry that is available today.</p>
<p>UDDI is the first truly cross-industry effort driven by all major platform
and software providers, as well as marketplace operators and e-business
leaders. These technology and business pioneers are acting as the initial
catalysts to quickly develop UDDI and related technologies.</p>
<p>The UDDI project takes advantage of WorldWide Web Consortium (W3C)
and Internet Engineering Task Force (IETF) standards such as Extensible
Markup Language (XML), and HTTP and Domain Name System (DNS) protocols.
Additionally, cross platform programming features are addressed by adopting
early versions of the proposed Simple Object Access Protocol (SOAP)
known as XML Protocol messaging specifications found at the W3C Web
site. The UDDI protocol is the building block that will enable businesses
to quickly, easily and dynamically find and transact with one another
using their preferred applications.</p>
<p>Additional information regarding UDDI can be found at <a href="http://www.uddi.org/" target="_top">UDDI.org</a>.</p>
<p></p>
</td>
</tr>
<tr><td height="14"><div align="left" class="footer">Copyright © 2003, <a href="mailto:steve@viens.net" target="_top">Steve Viens</a> and contributors, All rights reserved</div></td></tr>
</table>
</body>
</html>
1.1 ws-juddi/docs/toc.html
Index: toc.html
===================================================================
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<link rel="stylesheet" href="juddi.css"/>
</head><body>
<table cellspacing="10">
<tr>
<td valign="top" class="side" nowrap width="100">
<p><a href="overview.html" target="content">Overview</a><br></p>
<p><a href="deploy.html" target="content">Deployment Guide</a></p>
<p><a href="develop.html" target="content">Developer's Guide</a></p>
<p><a href="faq.html" target="content">FAQ</a></p>
<p><a href="lists.html" target="content">Mailing Lists</a><br></p>
<p><a href="download.html" target="content">Download</a></p>
<p><a href="license.html" target="content">License</a><br></p>
<p><a href="http://sourceforge.net/projects/juddi" target="_top">jUDDI at SourceForge</a><font size="-2"><sup>TM</sup></font></p>
<p><a href="http://sourceforge.net/projects/juddi" target="_top"><img src="http://sourceforge.net/sflogo.php?group_id=42875" width="88" height="31" border="0" alt="SourceForge Logo"/></a></p>
</td>
</tr>
</table>
</body>
</html>
1.1 ws-juddi/docs/udditest-uddi4j.html
Index: udditest-uddi4j.html
===================================================================
<HTML>
<HEAD>
<TITLE>jUDDI UDDI4J Test Plan</TITLE>
<link rel="stylesheet" href="juddi.css"/>
</HEAD>
<BODY>
<table cellspacing="10">
<tr>
<td valign="top" width="100%" height="100%">
<div class="announcement"><h3>jUDDI UDDI4J Test Plan</h3></div>
jUDDI can be used with any compliant UDDI client, including UDDI4J. This test suite has two goals: testing compliance with the UDDI 2.x
specification and testing interoperability with the UDDI4J client.
<p>
The suite is organized around the UDDI API. Each test class exersizes a particular method, such as <code>add_PublisherAssertions</code> or
<code>set_publisherAssertions</code>. Each interface aspect exersized is documented under 'Tests'. The tests cover positive and negative
behavior, covering both success and error conditions.
<p>
This document should be synchronized with the jUDDI UDDI4J test source code, to make sure coverage is complete and no unecessary overlaps occur.
<h4>add_publisherAssertions</h4>
<h5>Required working features</h5>
keyedReference, save_business
<h5>Setup</h5>
Create three business entities, each using a distinct authinfo token.
<h5>Tests</h5>
<ol>
<li>Create and destroy peer to peer
<li>Attempt to create peer to peer with one or more invalid keys, should produce
a failed disposition report with E_invalidKeyPassed.
<li>Attempt to create peer to peer with a valid auth token, but not the auth token
used to registered the 'from' business, should produce a failed disposition report with E_userMismatch.
<li>Attempt to create peer to peer with a invalid auth token, should produce a
failed disposition report with E_authTokenRequired
<li>Attempt to create peer to peer with an expired auth token, should produce a failed disposition report with E_authTokenExpired.
</oL>
<h4>save_tModel</h4>
<h5>Required working features</h5>
get_authToken
<h5>Setup</h5>
None
<h5>Tests</h5>
<ol>
<li>Create new tModel, using a blank uuid_key. This should create a new tModel, returning a new distinct uuid_key
<li>Create new tModel, using a blank uuid_key, do not pass a name. This should fail. (? how ?)
<li>Attempt to create a new tModel, passing an invalid token or empty token. This should generate a disposition report
with E_authTokenRequired
<li>Attempt to create a new tModel, passing an expired authorization token. This should generate disposition report with
E_authTokenExpired
</ol>
<h4>set_publisherAssertions</h4>
<h5>Required working features</h5>
add_publisherAssertions
<h4>discard_authToken</h4>
<h5>Required working features</h5>
get_authToken
<h5>Setup</h5>
None
<h5>Tests</h5>
<ol>
<li>Discard auth token
<li>Attempt to dicard an invalid auth token, should produce a failed dispostion report with E_authTokenRequired
</oL>
</td>
</tr>
<tr><td height="14"><div align="left" class="footer">Copyright © 2003, <a href="mailto:steve@viens.net" target="_top">Steve Viens</a> and contributors, All rights reserved</div></td></tr>
</table>
</BODY>
</HTML>
1.1 ws-juddi/docs/images/components.png
<<Binary file>>
1.1 ws-juddi/docs/images/conncache.gif
<<Binary file>>
1.1 ws-juddi/docs/images/deployWiz.gif
<<Binary file>>
1.1 ws-juddi/docs/images/instApp.gif
<<Binary file>>
1.1 ws-juddi/docs/images/juddiWebApp.gif
<<Binary file>>
1.1 ws-juddi/docs/images/juddiprops.gif
<<Binary file>>
1.1 ws-juddi/docs/images/overview.png
<<Binary file>>
1.1 ws-juddi/docs/images/resourceref.gif
<<Binary file>>
1.1 ws-juddi/docs/images/screenshot.png
<<Binary file>>