juddi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ks...@apache.org
Subject svn commit: r782125 - in /webservices/juddi/branches/v3_trunk: ./ juddi-core/src/test/java/org/apache/juddi/api/impl/ src/ src/site/ src/site/resources/ src/site/resources/css/ src/site/resources/images/ src/site/xdoc/
Date Fri, 05 Jun 2009 20:30:40 GMT
Author: kstam
Date: Fri Jun  5 20:30:38 2009
New Revision: 782125

URL: http://svn.apache.org/viewvc?rev=782125&view=rev
Log:
JUDDI-189 updates to the site to reflect the 3.0.0.beta release

Added:
    webservices/juddi/branches/v3_trunk/src/
    webservices/juddi/branches/v3_trunk/src/site/
    webservices/juddi/branches/v3_trunk/src/site/resources/
    webservices/juddi/branches/v3_trunk/src/site/resources/css/
    webservices/juddi/branches/v3_trunk/src/site/resources/css/mysite.css
    webservices/juddi/branches/v3_trunk/src/site/resources/css/print.css
    webservices/juddi/branches/v3_trunk/src/site/resources/css/site.css
    webservices/juddi/branches/v3_trunk/src/site/resources/css/tigris.css
    webservices/juddi/branches/v3_trunk/src/site/resources/images/
    webservices/juddi/branches/v3_trunk/src/site/resources/images/built-with-forrest-button.png   (with props)
    webservices/juddi/branches/v3_trunk/src/site/resources/images/group-logo.gif   (with props)
    webservices/juddi/branches/v3_trunk/src/site/resources/images/group.svg
    webservices/juddi/branches/v3_trunk/src/site/resources/images/icon.png   (with props)
    webservices/juddi/branches/v3_trunk/src/site/resources/images/juddi.gif   (with props)
    webservices/juddi/branches/v3_trunk/src/site/resources/images/juddi.jpg   (with props)
    webservices/juddi/branches/v3_trunk/src/site/resources/images/juddi.png   (with props)
    webservices/juddi/branches/v3_trunk/src/site/resources/images/portal-preview.png   (with props)
    webservices/juddi/branches/v3_trunk/src/site/resources/images/project-logo.gif   (with props)
    webservices/juddi/branches/v3_trunk/src/site/resources/images/project.svg
    webservices/juddi/branches/v3_trunk/src/site/site.xml
    webservices/juddi/branches/v3_trunk/src/site/xdoc/
    webservices/juddi/branches/v3_trunk/src/site/xdoc/committers.xml
    webservices/juddi/branches/v3_trunk/src/site/xdoc/index.xml
    webservices/juddi/branches/v3_trunk/src/site/xdoc/legal.xml
    webservices/juddi/branches/v3_trunk/src/site/xdoc/library.xml
    webservices/juddi/branches/v3_trunk/src/site/xdoc/list-guidelines.xml
    webservices/juddi/branches/v3_trunk/src/site/xdoc/participate.xml
    webservices/juddi/branches/v3_trunk/src/site/xdoc/releases.xml
    webservices/juddi/branches/v3_trunk/src/site/xdoc/usersguide.xml
    webservices/juddi/branches/v3_trunk/src/site/xdoc/who.xml
Modified:
    webservices/juddi/branches/v3_trunk/juddi-core/src/test/java/org/apache/juddi/api/impl/package.html
    webservices/juddi/branches/v3_trunk/pom.xml

Modified: webservices/juddi/branches/v3_trunk/juddi-core/src/test/java/org/apache/juddi/api/impl/package.html
URL: http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/juddi-core/src/test/java/org/apache/juddi/api/impl/package.html?rev=782125&r1=782124&r2=782125&view=diff
==============================================================================
--- webservices/juddi/branches/v3_trunk/juddi-core/src/test/java/org/apache/juddi/api/impl/package.html (original)
+++ webservices/juddi/branches/v3_trunk/juddi-core/src/test/java/org/apache/juddi/api/impl/package.html Fri Jun  5 20:30:38 2009
@@ -1,11 +1,16 @@
-Unit tests to test the api implementation. Theses tests go all the way down into
+<html>
+<body>
+<p>Unit tests to test the api implementation. Theses tests go all the way down into
 the persistence layer. By default they are using an embedded Java-based database
-called Derby. 
+called Derby. </p>
 
-The order in which the tests are run is irrelevant however some tests are more basic
+<p>The order in which the tests are run is irrelevant however some tests are more basic
 then others. For example, you will need to have a Publisher, before you can persist
 a Business, and you need to have a Business before you can persist a Service. So it
-makes sense to test persisting a Publisher first. 
+makes sense to test persisting a Publisher first.</p>
 
-By default JUnit executes tests in alphabetical order, so to control test execution order we
-use the JUDDI_###_ prefix.
\ No newline at end of file
+<p>By default JUnit executes tests in alphabetical order, so to control test execution order we
+use the JUDDI_###_ prefix.
+</p>
+</body>
+</html>
\ No newline at end of file

Modified: webservices/juddi/branches/v3_trunk/pom.xml
URL: http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/pom.xml?rev=782125&r1=782124&r2=782125&view=diff
==============================================================================
--- webservices/juddi/branches/v3_trunk/pom.xml (original)
+++ webservices/juddi/branches/v3_trunk/pom.xml Fri Jun  5 20:30:38 2009
@@ -86,6 +86,31 @@
 			<email>tcunningham AT apache.org</email>
 			<organization>ASF</organization>
 		</developer>
+		<developer>
+			<id>sviens</id>
+			<name>Steve Viens</name>
+			<email>steve AT viens.net</email>
+			<url>http://www.viens.net</url>
+			<organization>ASF</organization>
+		</developer>
+		<developer>
+			<id>acutright</id>
+			<name>Andy Cutright</name>
+			<email>acutright AT apache.org</email>
+			<organization>ASF</organization>
+		</developer>
+		<developer>
+			<id>anil</id>
+			<name>Anil Saldhana</name>
+			<email>anil AT apache.org</email>
+			<organization>ASF</organization>
+		</developer>
+		<developer>
+			<id>dims</id>
+			<name>Davanum Srinivas</name>
+			<email>dims AT yahoo.com</email>
+			<organization>ASF</organization>
+		</developer>
 	</developers>
 	<licenses>
 		<license>
@@ -114,6 +139,9 @@
 		<plugins>
 			<plugin>
 				<artifactId>maven-javadoc-plugin</artifactId>
+				<configuration>
+				    <aggregate>true</aggregate>
+				</configuration>
 			</plugin>
 			<plugin>
 				<artifactId>maven-project-info-reports-plugin</artifactId>
@@ -133,7 +161,9 @@
 		<module>uddi-tck</module>
 		<module>juddi-core</module>
 		<module>juddi-cxf</module>
+<!--
 		<module>juddi-axis</module>
+-->
 		<module>juddi-tomcat</module>
 		<module>uddi-client</module>
 	</modules>
@@ -205,4 +235,4 @@
 			</build>
 		</profile>
 	</profiles>
-</project>
\ No newline at end of file
+</project>

Added: webservices/juddi/branches/v3_trunk/src/site/resources/css/mysite.css
URL: http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/src/site/resources/css/mysite.css?rev=782125&view=auto
==============================================================================
--- webservices/juddi/branches/v3_trunk/src/site/resources/css/mysite.css (added)
+++ webservices/juddi/branches/v3_trunk/src/site/resources/css/mysite.css Fri Jun  5 20:30:38 2009
@@ -0,0 +1,89 @@
+/*
+ * Other colors:
+ *  - dark blue: #036
+ *  - bluish: #269
+ *
+ */
+
+/*
+ * The Banner section.
+ */
+.banner, .projectLogo, .groupLogo, .projectLogo a, .groupLogo a,
+    .groupLogo a:visited, .projectLogo a:visited,
+    .groupLogo a:link, .projectLogo a:link {
+}
+
+/*
+ * The Status + Footer section.
+ */
+.status, .breadcrumb, .searcher, .tabs {
+}
+
+.selectedTab {
+}
+
+/*
+ * The Menu section.
+ */
+.menuColumn {
+}
+.menubar {
+}
+.menu {
+}
+.menuLabel {
+}
+.menuItem {
+}
+
+/*
+ * The Content section.
+ */
+.contentColumn {
+}
+
+h1, h2, h3, h4 {
+}
+
+h3, h4 {
+ }
+h3 {
+  }
+h4 {  
+}
+
+.code {
+}
+
+.section {
+}
+
+.subsection {
+}
+
+/*
+ * The Footer section.
+ */
+.footer, .copyright, .host, .credit {
+}
+
+/*
+ * General Settings
+ */
+body {
+}
+
+a:link, .menuItem a:visited, .status a:visited {
+ color: #036;
+}
+
+a:active, a:hover {
+
+}
+
+body, th, td {
+}
+
+.logoImage {
+ border: none;
+}

Added: webservices/juddi/branches/v3_trunk/src/site/resources/css/print.css
URL: http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/src/site/resources/css/print.css?rev=782125&view=auto
==============================================================================
--- webservices/juddi/branches/v3_trunk/src/site/resources/css/print.css (added)
+++ webservices/juddi/branches/v3_trunk/src/site/resources/css/print.css Fri Jun  5 20:30:38 2009
@@ -0,0 +1,16 @@
+#banner, #footer, #leftcol, #breadcrumbs, .docs #toc, .docs .courtesylinks	{
+	display: none;
+	}
+body.docs div.docs	{
+	margin: 0 !important;
+	border: none !important
+	}
+
+/* just to be sure */
+#navcolumn {
+ width: 0px;
+}
+
+#leftcol {
+ width: 0px;
+}

Added: webservices/juddi/branches/v3_trunk/src/site/resources/css/site.css
URL: http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/src/site/resources/css/site.css?rev=782125&view=auto
==============================================================================
--- webservices/juddi/branches/v3_trunk/src/site/resources/css/site.css (added)
+++ webservices/juddi/branches/v3_trunk/src/site/resources/css/site.css Fri Jun  5 20:30:38 2009
@@ -0,0 +1,81 @@
+div#banner {
+ border-top: 1px solid #fff;
+ border-bottom: 1px solid #aaa;
+}
+
+#banner, #banner td {
+ background: #fff;
+ color: #036;
+}
+
+#tabs {
+  text-align: right;
+}
+
+.selectedTab {
+  color: #036;	
+}
+
+ a.unselectedTab {
+  color: #888888;	
+}
+
+#source {
+ background-color: #fff;
+ color: #000;
+ border-right: 1px solid #888;
+ border-left: 1px solid #888;
+ border-top: 1px solid #888;
+ border-bottom: 1px solid #888;
+ margin-right: 7px;
+ margin-left: 7px;
+ margin-top: 1em;
+}
+
+#source pre {
+ margin-right: 7px;
+ margin-left: 7px;
+}
+
+/* make the whole column grey */
+#navcolumn {
+ width: 150px;
+ }
+
+#leftcol {
+ width: 150px;
+}
+
+/*
+ * The Menu section.
+ */
+.menuColumn {
+}
+
+.menu {
+  padding-bottom: .2em;
+  font-size: x-small;
+  text-decoration: none;
+}
+.menuLabel { font-weight: bold; }
+.menuItem {
+  padding-left: 12px;
+  text-decoration: none;
+}
+
+/* breadcrumbs */
+#breadcrumbs
+{
+	font-weight: bold;
+}
+.breadcrumbTrail
+{
+	padding-left: 5px;
+}
+.breadcrumb
+{
+	font-weight: bold;
+}
+.crumbSeparator
+{
+}

Added: webservices/juddi/branches/v3_trunk/src/site/resources/css/tigris.css
URL: http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/src/site/resources/css/tigris.css?rev=782125&view=auto
==============================================================================
--- webservices/juddi/branches/v3_trunk/src/site/resources/css/tigris.css (added)
+++ webservices/juddi/branches/v3_trunk/src/site/resources/css/tigris.css Fri Jun  5 20:30:38 2009
@@ -0,0 +1,469 @@
+/* contains rules unsuitable for Netscape 4.x; simpler rules are in ns4_only.css. see <http://style.tigris.org/> */
+
+/* colors, backgrounds, borders, link indication */ 
+
+body {
+ background: #fff;
+ color: #000;
+ }
+.app h3, .app h4, .app th, .tabs td, .tabs th, .functnbar {
+ background-image: url(images/nw_maj_rond.gif);
+ background-repeat: no-repeat;
+ }
+#navcolumn div div, body.docs #toc li li  {
+ background-image: url(images/strich.gif);
+ background-repeat: no-repeat;
+ background-position: .5em .5em;
+ }
+#navcolumn div div.heading  {
+ background-image: none;
+ }
+.app h3, .app h4 {
+ color: #fff;
+ }
+.app h3 {
+ background-color: #036;
+ }
+.app h4 {
+ background-color: #888;
+ }
+.a td {
+ background: #ddd;
+ }
+.b td {
+ background: #efefef;
+ }
+table, th, td {
+ border: none
+ }
+.mtb {
+ border-top: solid 1px #ddd;
+ }
+div.colbar {
+ background: #bbb;
+ }
+div#banner {
+ border-top: 1px solid #369;
+ border-bottom: 1px solid #003;
+ }
+div#helptext th {
+ border-bottom: 1px solid #996;
+ border-right: 1px solid #996;
+ }
+div#helptext td {
+ border-bottom: 1px solid #cc9;
+ border-right: 1px solid #cc9;
+ }
+.tabs { 
+ border-bottom: .75em #888 solid;
+ }
+.tabs th, .tabs td {
+ border-right: 1px solid #333;
+ }
+.tabs td {
+ border-bottom: 1px solid #ddd;
+ }
+#navcolumn {
+ background: #eee;
+ border-right: 1px solid #aaa;
+ border-bottom: 1px solid #aaa;
+ }
+#breadcrumbs {
+ border-bottom: 1px solid #aaa;
+ background-color: #ddd;
+ }
+#navcolumn, #breadcrumbs {
+ border-top: 1px solid #fff;
+ }
+#rightcol div.www, #rightcol div.help {
+ border: 1px solid #ddd;
+ }
+div#navcolumn div.focus {
+ border-top: 1px solid #aaa;
+ border-left: 1px solid #aaa;
+ background-color: #fff;
+ } 
+body.docs div.docs { 
+ background: #fff;
+ border-left: 1px solid #ddd;
+ border-top: 1px solid #ddd;
+ }
+body.docs { 
+ background: #eee url(images/help_logo.gif) top right no-repeat !important;
+ }
+.docs h3, .docs h4 {
+ border-top: solid 1px #000;
+ }
+#alerterrormessage { 
+ background: url(images/icon_alert.gif) top left no-repeat !important;
+ }
+.functnbar {
+ background-color: #aaa;
+ }
+.functnbar2, .functnbar3  {
+ background: #aaa;
+ }
+.functnbar3 {
+ background-color: #ddd;
+ }
+.functnbar, .functnbar2, .functnbar3 {
+ color: #000;
+ }
+.functnbar a, .functnbar2 a, .functnbar3 a {
+ color: #000;
+ text-decoration: underline;
+ }
+#topmodule {
+ background: #ddd;
+ border-top: 1px solid #fff;
+ border-bottom: 1px solid #aaa; 
+ border-right: 1px solid #aaa; 
+ }
+#topmodule #issueid {
+ border-right: 1px solid #aaa;
+ }
+a:link, #navcolumn a:visited, .app a:visited, .tasknav a:visited {
+ color: blue;
+ }
+a:active, a:hover, #leftcol a:active, #leftcol a:hover {
+ color: #f30 !important;
+ }
+#login a:link, #login a:visited {
+ color: white; 
+ text-decoration: underline;
+ }
+#banner a:active, #banner a:hover {
+ color: #f90 !important;
+ }
+#leftcol a, #breadcrumbs a  {
+ text-decoration: none;
+ }
+a:link.selfref, a:visited.selfref {
+ color: #555 !important;
+ text-decoration: none;
+ }
+h2 .lastchild {
+ color: #777
+ } 
+.tabs td, .tabs th {
+ background-color: #ddd;
+ }
+.app th {
+ background-color: #bbb;
+ }
+.tabs th {
+ background-color: #888;
+ color: #fff;
+ }
+.axial th {
+ background-color: #ddd;
+ color: black
+ }
+.tabs td {
+ background-color: #ddd;
+ }
+.alert { 
+ color: #c00;
+ }
+.confirm {
+ color: green;
+ }
+.info {
+ color: blue;
+ }
+.selection {
+ background: #ffc;
+ }
+#login {
+ color: #fff;
+ }
+#helptext th {
+ background: #cc9;
+ }
+#helptext td {
+ background: #ffc;
+ }
+.tabs a  {
+ text-decoration: none;
+ }
+#navcolumn div strong {
+ color: #000;
+ }
+#banner, #banner td { 
+ background: #036;
+ color: #fff;
+ }
+body #banner #login a { 
+ color: #fff;
+ }
+
+
+/* font and text properties, exclusive of link indication, alignment, text-indent */
+
+body, th, td, input, select, textarea, h2 small {
+ font-family: Verdana, Helvetica, Arial, sans-serif;
+ }
+code, pre {
+ font-family: 'Andale Mono', Courier, monospace;
+ }
+html body, body th, body td, textarea, h2 small, .app h3, .app h4, #rightcol h3, #bodycol pre, #bodycol code {
+ font-size: x-small;
+ voice-family: "\"}\"";
+ voice-family: inherit;
+ font-size: small
+ }
+html>body, html>body th, html>body td, html>body input, html>body select, html>body textarea, html>body h2 small, html>body .app h3, html>body .app h4, html>body #rightcol h3, html>body #bodycol pre, html>body #bodycol code {
+ font-size: small
+ }
+small, div#footer td, div#login, div.tabs th, div.tabs td, input, select, .paginate, .functnbar, .functnbar2, .functnbar3, #breadcrumbs td, .courtesylinks, #rightcol div.help, .colbar, .tasknav, body.docs div#toc, #leftcol {
+ font-size: x-small;
+ voice-family: "\"}\"";
+ voice-family: inherit;
+ font-size: x-small
+ }
+html>body small, html>body div#footer td, html>body div#login, html>body div#helptext td, html>body div#helptext th, html>body div.tabs th, html>body div.tabs td, html>body input, html>body select, html>body .paginate, html>body .functnbar, html>body .functnbar2, html>body .functnbar3, html>body #breadcrumbs td, html>body .courtesylinks, html>body #rightcol div.help, html>body .colbar, html>body .tasknav, html>body.docs #toc {
+ font-size: x-small
+ }
+#bodycol h2 {
+ font-family: Tahoma, Verdana, Helvetica, Arial, sans-serif;
+ font-size: 1.5em;
+ font-weight: normal;
+ }
+h2 small {
+ font-weight: bold;
+ letter-spacing: .06em;
+ }
+dt {
+ font-weight: bold
+ }
+#login .username {
+ font-weight: bold;
+ }
+h4 {
+ font-size: 1em;
+ }
+#breadcrumbs td {
+ font-weight: bold;
+ } 
+.selection {
+ font-weight: bold
+ }
+
+
+/* box properties (exclusive of borders), positioning, alignments, list types, text-indent */
+
+#bodycol h2 {
+ margin-top: .3em;
+ margin-bottom: .5em;
+ }
+p, ul, ol, dl {
+ margin-top: .67em;
+ margin-bottom: .67em;
+ }
+h3, h4 {
+ margin-bottom: 0;
+ }
+form {
+ margin-top: 0;
+ margin-bottom: 0;
+ }
+#bodycol {
+ padding-left: 12px;
+ padding-right: 12px;
+ width: 100%;
+ voice-family: "\"}\"";
+ voice-family: inherit;
+ width: auto;
+ }
+html>body #bodycol {
+ width: auto;
+ }
+.docs {
+ line-height: 1.4;
+ }
+.app h3, .app h4 {
+ padding: 5px;
+ margin-right: 2px;
+ margin-left: 2px;
+ }
+.h3 p, .h4 p, .h3 dt, .h4 dt {
+ margin-right: 7px;
+ margin-left: 7px;
+ }
+.tasknav {
+ margin-bottom: 1.33em
+ }
+div.colbar {
+ padding: 4px;
+ margin: 2px 2px 0;
+ }
+.tabs { 
+ margin-top: .67em;
+ margin-right: 2px;
+ margin-left: 2px;
+ }
+#leftcol {
+ padding-bottom: .5em;
+ }
+#breadcrumbs td {
+ vertical-align: middle;
+ padding: 2px 8px;
+ } 
+#rightcol div.www, #rightcol div.help {
+ padding: 0 .5em
+ }
+#navcolumn {
+ margin: -8px -8px 0 -8px;
+ padding: 4px;
+ }
+#navcolumn div {
+ padding-left: 5px
+ }
+div#navcolumn div div {
+ margin-top: .3em;
+ margin-bottom: .3em;
+ }
+div#navcolumn div.focus { 
+ margin-top: -.1em;
+ padding: .2em 4px; 
+ } 
+body.docs #toc { 
+ position: absolute;
+ top: 15px;
+ left: 0px;
+ width: 120px;
+ padding: 0 20px 0 0
+ }
+body.docs #toc ul, #toc ol {
+ margin-left: 0;
+ padding-left: 0;
+ }
+body.docs #toc li {
+ margin-top: 7px;
+ padding-left: 10px;
+ list-style-type: none;
+ }
+body.docs div.docs { 
+ margin: 61px 0 0 150px;
+ padding: 1em 2em 1em 1em !important;
+ }
+.docs p+p {
+ text-indent: 5%;
+ margin-top: -.67em
+ }
+.docs h3, .docs h4 {
+ margin-bottom: .1em;
+ padding-top: .3em;
+ }
+#alerterrormessage { 
+ padding-left: 100px;
+ }
+.functnbar, .functnbar2, .functnbar3 {
+ padding: 5px;
+ margin: .67em 2px;
+ }
+#topmodule td {
+ vertical-align: middle;
+ padding: 2px 8px
+ } 
+body {
+ padding: 1em;
+ }
+body.composite, body.docs {
+ margin: 0;
+ padding: 0;
+ }
+th, td {
+ text-align: left;
+ vertical-align: top 
+ }
+.right {
+ text-align: right !important;
+ }
+.center {
+ text-align: center !important;
+ }
+.tabs td, .tabs th {
+ padding-left: 7px;
+ padding-right: 7px;
+ }
+.axial th {
+ text-align: right;
+ }
+.app .axial td th {
+ text-align: left;
+ }
+body td .stb {
+ margin-top: 1em;
+ text-indent: 0;
+ }
+body td .mtb {
+ margin-top: 2em;
+ text-indent: 0;
+ }
+dd {
+ margin-bottom: .67em;
+ }
+#footer {
+ margin: 4px
+ }
+#helptext {
+ margin-top: 1em
+ }
+#helptext td div {
+ margin: .5em
+ }
+.courtesylinks {
+ margin-top: 1em;
+ padding-top: 1em
+ }
+#navcolumn div {
+ margin-bottom: .5em;
+ }
+#navcolumn div div {
+ margin-top: .3em
+ }
+#navcolumn div div {
+ padding-left: 1em;
+ }
+#banner, #banner td { 
+ vertical-align: middle;
+ }
+body.docs, body.nonav {
+ margin: 1em
+ }
+
+.note, .warning, .fixme {
+	border-top: 3px solid #900;
+	border-bottom: 3px solid #900;
+	background-image: url(images/icon_error_lrg.gif);
+	background-repeat: no-repeat;
+	background-position: 0 1.33em;
+	margin: 1.33em 0;
+	padding: .33em 0 .67em 36px;
+	min-height: 32px;
+}
+
+
+.fixme {
+	background-image: url(images/icon_warning_lrg.gif);
+	border-color: #c60;
+}
+
+.note {
+	background-image: url(images/icon_info_lrg.gif);
+	border-color: #069;
+}
+
+.label{
+	font-weight: bold;
+}
+
+
+.code { background-color: #F7F7F7;
+        border-color: #CFDCED;
+        border-style: solid; 
+        border-width: 1px; 
+        font-size : 120%;
+        padding: 1em 1.33em 1em 1.33em;
+}

Added: webservices/juddi/branches/v3_trunk/src/site/resources/images/built-with-forrest-button.png
URL: http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/src/site/resources/images/built-with-forrest-button.png?rev=782125&view=auto
==============================================================================
Binary file - no diff available.

Propchange: webservices/juddi/branches/v3_trunk/src/site/resources/images/built-with-forrest-button.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: webservices/juddi/branches/v3_trunk/src/site/resources/images/group-logo.gif
URL: http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/src/site/resources/images/group-logo.gif?rev=782125&view=auto
==============================================================================
Binary file - no diff available.

Propchange: webservices/juddi/branches/v3_trunk/src/site/resources/images/group-logo.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: webservices/juddi/branches/v3_trunk/src/site/resources/images/group.svg
URL: http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/src/site/resources/images/group.svg?rev=782125&view=auto
==============================================================================
--- webservices/juddi/branches/v3_trunk/src/site/resources/images/group.svg (added)
+++ webservices/juddi/branches/v3_trunk/src/site/resources/images/group.svg Fri Jun  5 20:30:38 2009
@@ -0,0 +1,61 @@
+<?xml version="1.0" standalone="no"?>
+
+<!--
+       SVG Anteater logo
+        jefft@apache.org
+
+To get started with SVG, I'd recommend getting the Adobe SVG plugin, and the
+xml-batik CVS module. Then have a look at the xml-batik/samples files. Use the
+SVG spec (http://www.w3.org/TR/SVG/) as a reference.
+-->
+
+<!--
+<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.0//EN"
+"http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd">
+-->
+<svg xmlns="http://www.w3.org/2000/svg"
+     xmlns:xlink="http://www.w3.org/1999/xlink"
+     xmlns:for="http://xml.apache.org/forrest" width="220" height="65" >
+  <title>Anteater logo</title>
+
+  <defs>
+
+    <!--
+    <radialGradient id="radialGradient">
+      <stop style="stop-color:gold" offset="0"/>
+      <stop style="stop-color:orange" offset=".5"/>
+      <stop style="stop-color:crimson" offset="1"/>
+    </radialGradient>
+    <linearGradient id="linearGradient">
+      <stop style="stop-color:gold" offset="0"/>
+      <stop style="stop-color:orange" offset=".5"/>
+      <stop style="stop-color:crimson" offset="1"/>
+    </linearGradient>
+    -->
+
+    <linearGradient id="gradient" x1="0" y1="0" x2="0" y2="1">
+      <stop style="stop-color:white" offset="0"/>
+      <stop style="stop-color:lightgreen" offset="1"/>
+    </linearGradient>
+
+    <filter id="shadowFilter"  filterUnits="objectBoundingBox">
+      <!-- Takes the alpha channel (black outline of the text), blurs it and saves as 'blur' -->
+      <feGaussianBlur in="SourceAlpha" stdDeviation="2 2" result="blur"/>
+      <!-- Takes saved 'blur' and offsets it by 4 pixels, saves as 'offsetBlur' -->
+      <feOffset in="blur" dx="4" dy="4" result="offsetBlur"/>
+      <!-- Merges SourceGraphic (original image) and 'offsetBlur', putting the
+      former 'over' the latter, and using the merged result as the finished
+      image -->
+      <feComposite in="SourceGraphic" in2="offsetBlur" operator="over"/>
+    </filter>
+
+  </defs>
+
+  <g filter="url(#shadowFilter)" fill="url(#gradient)">
+    <text x="40%" y="60%" style="font-size:24pt; font-family:Verdana ; text-anchor: middle">
+    <for:group-name />
+    </text>
+  </g>
+</svg>
+
+

Added: webservices/juddi/branches/v3_trunk/src/site/resources/images/icon.png
URL: http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/src/site/resources/images/icon.png?rev=782125&view=auto
==============================================================================
Binary file - no diff available.

Propchange: webservices/juddi/branches/v3_trunk/src/site/resources/images/icon.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: webservices/juddi/branches/v3_trunk/src/site/resources/images/juddi.gif
URL: http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/src/site/resources/images/juddi.gif?rev=782125&view=auto
==============================================================================
Binary file - no diff available.

Propchange: webservices/juddi/branches/v3_trunk/src/site/resources/images/juddi.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: webservices/juddi/branches/v3_trunk/src/site/resources/images/juddi.jpg
URL: http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/src/site/resources/images/juddi.jpg?rev=782125&view=auto
==============================================================================
Binary file - no diff available.

Propchange: webservices/juddi/branches/v3_trunk/src/site/resources/images/juddi.jpg
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: webservices/juddi/branches/v3_trunk/src/site/resources/images/juddi.png
URL: http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/src/site/resources/images/juddi.png?rev=782125&view=auto
==============================================================================
Binary file - no diff available.

Propchange: webservices/juddi/branches/v3_trunk/src/site/resources/images/juddi.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: webservices/juddi/branches/v3_trunk/src/site/resources/images/portal-preview.png
URL: http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/src/site/resources/images/portal-preview.png?rev=782125&view=auto
==============================================================================
Binary file - no diff available.

Propchange: webservices/juddi/branches/v3_trunk/src/site/resources/images/portal-preview.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: webservices/juddi/branches/v3_trunk/src/site/resources/images/project-logo.gif
URL: http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/src/site/resources/images/project-logo.gif?rev=782125&view=auto
==============================================================================
Binary file - no diff available.

Propchange: webservices/juddi/branches/v3_trunk/src/site/resources/images/project-logo.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: webservices/juddi/branches/v3_trunk/src/site/resources/images/project.svg
URL: http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/src/site/resources/images/project.svg?rev=782125&view=auto
==============================================================================
--- webservices/juddi/branches/v3_trunk/src/site/resources/images/project.svg (added)
+++ webservices/juddi/branches/v3_trunk/src/site/resources/images/project.svg Fri Jun  5 20:30:38 2009
@@ -0,0 +1,61 @@
+<?xml version="1.0" standalone="no"?>
+
+<!--
+       SVG Anteater logo
+        jefft@apache.org
+
+To get started with SVG, I'd recommend getting the Adobe SVG plugin, and the
+xml-batik CVS module. Then have a look at the xml-batik/samples files. Use the
+SVG spec (http://www.w3.org/TR/SVG/) as a reference.
+-->
+
+<!--
+<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.0//EN"
+"http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd">
+-->
+<svg xmlns="http://www.w3.org/2000/svg"
+     xmlns:xlink="http://www.w3.org/1999/xlink"
+     xmlns:for="http://xml.apache.org/forrest" width="220" height="65" >
+  <title>Anteater logo</title>
+
+  <defs>
+
+    <!--
+    <radialGradient id="radialGradient">
+      <stop style="stop-color:gold" offset="0"/>
+      <stop style="stop-color:orange" offset=".5"/>
+      <stop style="stop-color:crimson" offset="1"/>
+    </radialGradient>
+    <linearGradient id="linearGradient">
+      <stop style="stop-color:gold" offset="0"/>
+      <stop style="stop-color:orange" offset=".5"/>
+      <stop style="stop-color:crimson" offset="1"/>
+    </linearGradient>
+    -->
+
+    <linearGradient id="gradient" x1="0" y1="0" x2="0" y2="1">
+      <stop style="stop-color:white" offset="0"/>
+      <stop style="stop-color:lightgreen" offset="1"/>
+    </linearGradient>
+
+    <filter id="shadowFilter"  filterUnits="objectBoundingBox">
+      <!-- Takes the alpha channel (black outline of the text), blurs it and saves as 'blur' -->
+      <feGaussianBlur in="SourceAlpha" stdDeviation="2 2" result="blur"/>
+      <!-- Takes saved 'blur' and offsets it by 4 pixels, saves as 'offsetBlur' -->
+      <feOffset in="blur" dx="4" dy="4" result="offsetBlur"/>
+      <!-- Merges SourceGraphic (original image) and 'offsetBlur', putting the
+      former 'over' the latter, and using the merged result as the finished
+      image -->
+      <feComposite in="SourceGraphic" in2="offsetBlur" operator="over"/>
+    </filter>
+
+  </defs>
+
+  <g filter="url(#shadowFilter)" fill="url(#gradient)">
+    <text x="51%" y="75%" style="font-size:32pt; font-family:Verdana ; text-anchor: middle" >
+    <for:project-name />
+    </text>
+  </g>
+</svg>
+
+

Added: webservices/juddi/branches/v3_trunk/src/site/site.xml
URL: http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/src/site/site.xml?rev=782125&view=auto
==============================================================================
--- webservices/juddi/branches/v3_trunk/src/site/site.xml (added)
+++ webservices/juddi/branches/v3_trunk/src/site/site.xml Fri Jun  5 20:30:38 2009
@@ -0,0 +1,84 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!--
+  ~  Licensed to the Apache Software Foundation (ASF) under one
+  ~  or more contributor license agreements.  See the NOTICE file
+  ~  distributed with this work for additional information
+  ~  regarding copyright ownership.  The ASF licenses this file
+  ~  to you under the Apache License, Version 2.0 (the
+  ~  "License"); you may not use this file except in compliance
+  ~  with the License.  You may obtain a copy of the License at
+  ~
+  ~   http://www.apache.org/licenses/LICENSE-2.0
+  ~
+  ~  Unless required by applicable law or agreed to in writing,
+  ~  software distributed under the License is distributed on an
+  ~   * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+  ~  KIND, either express or implied.  See the License for the
+  ~  specific language governing permissions and limitations
+  ~  under the License.
+  -->
+
+<project name="Apache jUDDI">
+
+    <bannerLeft>
+        <name>Apache jUDDI</name>
+        <src>images/project-logo.gif</src>
+        <href>ws.apache.org/juddi/</href>
+    </bannerLeft>
+    <bannerRight>
+    <src>images/juddi.gif</src>
+  </bannerRight>
+    <skin>
+        <groupId>org.apache.maven.skins</groupId>
+        <artifactId>maven-default-skin</artifactId>
+        <version>1.0</version>
+    </skin>
+
+    <publishDate format="dd MMM yyyy" position="right"/>
+
+    <body>
+        <breadcrumbs>
+      		<item name="Apache" href="http://www.apache.org/"/>
+      		<item name="WebServices" href="http://ws.apache.org/"/>
+    	</breadcrumbs>
+
+        <menu name="Apache jUDDI">
+            <item name="Welcome" href="index.html"/>
+            <item name="Get jUDDI">
+                <item name="Releases" href="releases.html"/>
+                <item name="Source Code" href="source-repository.html"/>
+            </item>
+            <item name="Participation" href="participate.html" description="Participation"/>
+            <item name="Documentation">
+                <item name="jUDDI v3 docs" href="http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/docs/"/>
+                <item name="jUDDI v2 User guide" href="usersguide.html"/>
+                <item name="Wiki" href="http://wiki.apache.org/ws/jUDDI"/>
+                <item name="Reference Library" href="library.html" />
+                <item name="Javadocs v2" href="apidocs/index.html"/>
+                <item name="Javadocs v3" href="apidocs3/index.html"/>
+                <item name="XRef v3" href="xref/index.html"/>
+            </item>
+            <item name="Project Information">
+                <item name="Project Information" href="project-info.html"/>
+                <item name="Mailing Lists" href="mail-lists.html"/>
+                <item name="Issue Tracking" href="issue-tracking.html"/>
+                <item name="Dependencies" href="dependencies.html"/>
+                <item name="Dependency Convergence" href="dependency-convergence.html"/>
+                <item name="Project Team" href="team-list.html"/>
+                <item name="Project Summary" href="project-summary.html"/>
+            </item>
+            <item name="Related Projects">
+    			<item name="Apache Axis" href="http://ws.apache.org/axis/" description="Apache Axis"/>
+    			<item name="Apache Scout" href="http://ws.apache.org/scout/" description="Apache Scout"/>
+  			</item>
+  			<item name="Misc">
+    			<item name="Who We Are" href="who.html" description="Who We Are"/>
+    			<item name="Committer Notes" href="committers.html" description="Committer Notes"/>
+    			<item name="Legal" href="legal.html" description="Legal Stuff"/>
+    			<item name="License" href="license.html" description="Apache 2.0 License"/>
+  			</item>
+        </menu>
+
+    </body>
+</project>
+

Added: webservices/juddi/branches/v3_trunk/src/site/xdoc/committers.xml
URL: http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/src/site/xdoc/committers.xml?rev=782125&view=auto
==============================================================================
--- webservices/juddi/branches/v3_trunk/src/site/xdoc/committers.xml (added)
+++ webservices/juddi/branches/v3_trunk/src/site/xdoc/committers.xml Fri Jun  5 20:30:38 2009
@@ -0,0 +1,86 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "http://forrest.apache.org/dtd/document-v12.dtd">
+<document>
+  <properties>
+    <title>Committer Notes</title>
+  </properties>
+  <body>
+    <section name="Updating the jUDDI Web Site">
+      <p>You'll need the appropriate version of <link href="http://xml.apache.org/forrest/">forrest</link> as
+        well as the appropriate version of <link href="http://ant.apache.org/">ant</link>. This document
+        assumes you generally understand how to use these tools.
+      </p>
+      <p>
+       The site source is located under our source tree at ws-juddi/site. To build the site, simply invoke
+        forrest in ws-juddi/site. The built sources will be located at ws-juddi/build/site. You should
+        get a clean build, and no broken links. There aren't any known issues with the site.
+        </p>
+        <p>
+        You must test your builds locally by running forrest on your local box. You can do this by invoking
+        'forrest run' in ws-juddi/site.
+        </p>
+        <p>
+        The commit process is a bit complicated.
+        The live site is hosted under the ws-site source tree, -not- the ws-juddi src tree. The ws-juddi/build/site
+        directory hierarchy maps to the ws-site/targets/juddi directory hierarchy.
+        Once you've built the site copy the latter hierarchy to the former, and then commit the
+        changes. The live site is updated about every 6 hours from cvs.
+        </p>
+        <p>
+        You must -also- commit the changes you've made under ws-juddi/site to persist the changes for the next
+        committer to be able to reproduce your modifications.
+        </p>
+        <p>
+        To fully clean any site build you've created, you can safely delete everything under ws-juddi/site/build.
+        </p>
+    </section>
+    <section name="Release Process">
+      <p><strong>Release Manager</strong></p>
+      <p>
+      One committer will be elected or hopefully volunteer to assemble the binary releases and label the source tree.
+      </p>
+      <p><strong>Digitally Signing Releases</strong></p>
+      <p>
+        Apache policy requires binary releases be digitaly signed. The Apache process has not been formalized, but a general discussion about creating digital signatures
+        and signing releases is available at
+        <link href="http://nagoya.apache.org/wiki/apachewiki.cgi?SigningReleases">http://nagoya.apache.org/wiki/apachewiki.cgi?SigningReleases</link>.
+        This covers some basics about using <link href="http://www.gnupg.org">GnuPG</link> to create key pairs and sign releases. Our goal here is to
+        discuss jUDDI signing requirements, and provide some useful examples to release managers, not discuss digital signatures or encryption technology.
+        Our discussion uses <link href="http://www.gnupg.org">GnuPG</link>, but any compliant software could be used. The examples below come from the
+        <link href="http://www.gnupg.org/gph/en/manual.html">GnuPG manual</link>. This discussion is not a subsitute for reading that manual.
+      </p>
+      <p>
+        Creating a key pair is pretty simple using <link href="http://www.gnupg.org/gph/en/manual.html#AEN26">gpg</link>. Simply invoke gpg and take all the defaults when prompted. You
+        will have to provide a passphrase. Be sure to remember the passphrase since you'll need it anytime you use the key pair. The passphrase should itself be sufficiently
+        secure; it shouldn't simply be a word in a dictionary, should include a mix of digits and alphanumeric characters, etc.
+       </p>
+        <source>
+          gpg --gen-key
+        </source>
+        <p>
+        You should also generate a <link href="http://www.gnupg.org/gph/en/manual.html#AEN26">revocation certificate</link>. This allows you to declare the key
+        pair invalid publically, if you ever lose your private key, or it becomes compromised.
+      </p>
+        <source>
+          gpg --output revoke.as --gen-revoke mykey
+        </source>
+
+      <p>
+        The release manager is responsible for signing the binaries. The release manager must have a public key listed in the 'KEYS' file at the root of our source tree.
+        The release manager must create a <link href="http://www.gnupg.org/gph/en/manual.html#AEN161">detached signature</link> for each binary. This detached
+        signature must be posted along with our binaries, and allow our users to verify the binary's integrity.
+      </p>
+        <source>
+          gpg --output jUDDI.tar.gzip.asc --detach-sig jUDDI.tar.gzip
+        </source>
+      <p>All jUDDI committers are encouraged to create public/ private key pairs and place the public half into our 'KEYS'
+        file at the root of our source tree. jUDDI committers are also encouraged to verify one another's keys and sign them, to help
+        create a web of trust. Verifying a signature and a binary guarantees (in any real sense) the binary was assembled by the person
+        that signed it. However, it does not prove the person signing it can be trusted.
+        <link href="http://www.gnupg.org/gph/en/manual.html#AEN335">A web of trust</link> can be created by signing one another's keys.
+        This allows users and developers to 'trust' the person who created the document-signature pair to provide a secure, safe
+        binary.
+      </p>
+    </section>
+  </body>
+</document>

Added: webservices/juddi/branches/v3_trunk/src/site/xdoc/index.xml
URL: http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/src/site/xdoc/index.xml?rev=782125&view=auto
==============================================================================
--- webservices/juddi/branches/v3_trunk/src/site/xdoc/index.xml (added)
+++ webservices/juddi/branches/v3_trunk/src/site/xdoc/index.xml Fri Jun  5 20:30:38 2009
@@ -0,0 +1,98 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements.  See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership.  The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License.  You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied.  See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+<document>
+  <properties>
+    <title>Welcome to jUDDI</title>
+  </properties>
+  <body>
+
+      <section name="Intro">
+	      <p>jUDDI (pronounced &quot;Judy&quot;) is an open source Java implementation
+	        of the Universal Description, Discovery, and Integration (UDDI v3) specification
+	        for Web Services.
+	      </p>
+	  </section>
+    
+	 <section name="jUDDI Features">
+	    <ul>
+	      <li>Open Source</li>
+	      <li>Platform Independent</li>
+	      <li>Use with any relational database that supports ANSI standard SQL (MySQL, Oracle, DB2, Sybase, Derby etc.)</li>
+	      <li>Deployable on any Java application server that supports the Servlet 2.3 specification</li>
+	      <li>jUDDI registry supports a clustered deployment configuration.</li>
+	      <li>Easy integration with existing authentication systems</li>
+	      <li>Supports InVM embeddable mode</li>
+	    </ul>
+	    jUDDIv3
+	    <ul>
+	      <li>UDDI Specification version 3.0 compliant</li>
+	      <li>Supports for JDK 1.5 and later</li>
+	      <li>Build on JAXB and JAX-WS standards, tested on CXF</li>
+	      <li>Build on JPA standard, tested with OpenJPA and Hibernate</li>
+	      <li>Pre-configured bundle deployed to Tomcat</li>
+	      <li>UDDI <a href="images/portal-preview.png">portlets</a></li>
+	      <li>Pre-configured portal bundle download</li>
+	      <li>User and Developer Documentation</li>
+	    </ul>
+	    jUDDIv2
+	    <ul>
+	      <li>UDDI version 2.0 compliant</li>
+	      <li>Supports for JDK 1.3.1 and later</li>
+	    </ul>
+	  </section>
+      
+	  <section name="News">
+	    <p><strong>June 5, 2009</strong> Release 3.0.0.beta</p>
+	    <p><strong>May 31, 2009</strong> Release 2.0rc7</p>
+	    <p><strong>Feb 13, 2009</strong> Version 3.0.0.alpha is now available</p>
+	  	<p><strong>Feb 10, 2009</strong> Version 2.0rc6 is now available.</p>
+	    <p><strong>Dec 13, 2007</strong> Version 2.0rc5 is now available.</p>
+	    <p><strong>June 7, 2005</strong> Version 0.9rc4 is now available.</p>
+	    <p><strong>July 2, 2004</strong> Version 0.9rc3 is now available.</p>
+	    <p><strong>June 29, 2004</strong> Version 0.9rc2 is now available.</p>
+	    <p><strong>June 16, 2004</strong> Version 0.9rc1 is now available.</p>
+	    <p><strong>March 24, 2004</strong> jUDDI graduates from the Apache Incubator into Apache Web Services Project.</p>
+	    <p><strong>Oct 08, 2003</strong> The Apache Software Foundation's Web Services PMC (http://ws.apache.org/) voted to accept jUDDI into the Apache Incubator. The move is expected to be complete in early December.</p>
+	    <p><strong>July 22, 2003</strong> A proposal to contribute jUDDI to the Apache Software Foundation's Web Services Project is being considered.</p>
+	    <p><strong>July 22, 2003</strong> Version 0.8.0 is now available.</p>
+	    <p><strong>June 27, 2003</strong> Version 0.7.1 is now available.</p>
+	    <p><strong>April 22, 2003</strong> Version 0.7.0 is now available.</p>
+	  </section>
+
+      <section name="About UDDI">
+        <p>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. 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.
+        </p>
+        <p>Additional information regarding UDDI can be found 
+          at <a href="http://www.uddi.org/">UDDI.org</a>.
+        </p>
+      </section>
+      
+  </body>
+</document>

Added: webservices/juddi/branches/v3_trunk/src/site/xdoc/legal.xml
URL: http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/src/site/xdoc/legal.xml?rev=782125&view=auto
==============================================================================
--- webservices/juddi/branches/v3_trunk/src/site/xdoc/legal.xml (added)
+++ webservices/juddi/branches/v3_trunk/src/site/xdoc/legal.xml Fri Jun  5 20:30:38 2009
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "http://forrest.apache.org/dtd/document-v12.dtd">
+<document>
+  <properties>
+    <title>Legal</title>
+  </properties>
+  <body>
+    <section name="jUDDI - Legal Stuff">
+      <p>All material on this website is Copyright © 1999-2009, The Apache 
+        Software Foundation. 
+      </p>
+      <p>
+        Sun, Sun Microsystems, Solaris, Java, JavaServer 
+        Web Development Kit, and JavaServer Pages are trademarks or registered 
+        trademarks of Sun Microsystems, Inc. UNIX is a registered trademark 
+        in the United States and other countries, exclusively licensed 
+        through X/Open Company, Ltd. Windows, WindowsNT, and Win32 are 
+        registered trademarks of Microsoft Corp. All other product names 
+        mentioned herein and throughout the entire web site are trademarks 
+        of their respective owners. 
+      </p>
+    </section>
+  </body>
+</document>
\ No newline at end of file

Added: webservices/juddi/branches/v3_trunk/src/site/xdoc/library.xml
URL: http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/src/site/xdoc/library.xml?rev=782125&view=auto
==============================================================================
--- webservices/juddi/branches/v3_trunk/src/site/xdoc/library.xml (added)
+++ webservices/juddi/branches/v3_trunk/src/site/xdoc/library.xml Fri Jun  5 20:30:38 2009
@@ -0,0 +1,85 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "http://forrest.apache.org/dtd/document-v12.dtd">
+<document>
+  <properties>
+    <title>Reference Library</title>
+  </properties>
+  <body>
+
+	<section name="Introduction">
+	    <p>The jUDDI Project lives or fails based on its human resources. Users
+	      and contributors alike help the project with ideas and brainpower. A common
+	      foundation of knowledge is required to effectively participate in this
+	      virtual community. The following is a list of documents that we have found
+	      helpful for us and may be helpful to you.
+	    </p>
+    </section>
+
+    <section name="UDDI Specifications">        
+      <p>
+      <strong><a href="http://www.uddi.org/">UDDI.org</a></strong><br/>
+      <strong><a href="http://www.oasis-open.org/committees/uddi-spec/doc/contribs.htm#uddiv1">UDDI Version 1.0 Specification</a></strong><br/>
+      <strong><a href="http://www.oasis-open.org/committees/uddi-spec/doc/tcspecs.htm#uddiv2">UDDI Version 2.0 Specification</a></strong><br/>
+      <strong><a href="http://www.oasis-open.org/committees/uddi-spec/doc/tcspecs.htm#uddiv3">UDDI Version 3.0 Specification</a></strong>
+      </p>
+    </section>
+      
+    <section name="UDDI Taxonomies">            
+
+      <p><strong><a href="http://www.census.gov/epcd/www/naics.html">North American Industry Classification System (NAICS)</a></strong><br/>U.S. Census Bureau</p>
+      <p><strong><a href="http://www.unspsc.org/Defaults.asp">United Nations Standard Products and Services Code System (UNSPSC) Version 3.1</a></strong><br/>U.S. Census Bureau</p>
+    </section>
+      
+    <section name="Articles, Tutorials and Best Practices">            
+      <p><strong><a href="http://www-106.ibm.com/developerworks/webservices/library/ws-version/">Best practices for Web services versioning</a></strong><br/>Keep your Web services current with WSDL and UDDI<br/>Kyle Brown and Michael Ellis, IBM developerWorks<br/>January 2004</p>      
+      <p><strong><a href="http://www.sys-con.com/webservices/article.cfm?id=663">Registering a Web Service in UDDI using the new WSDL mapping model</a></strong><br/>Anne Thomas Manes, WebServices Journal<br/>October 2003</p>      
+      <p><strong><a href="http://www.sys-con.com/webservices/article.cfm?id=664">Bringing Order to Enterprise Service Proliferation</a></strong><br/>The foundation of a flexible infrastructure<br/>Toufic Boubez, WebServices Journal<br/>October 2003</p>      
+      <p><strong><a href="http://www.line56.com/articles/default.asp?ArticleID=4927">A Second Look at UDDI</a></strong><br/>The stepchild of Web services could be a cornerstone of service-oriented architectures beginning to take shape<br/>Jim Ericson, Line56.com<br/>August 2003</p>
+      <p><strong><a href="http://www-106.ibm.com/developerworks/edu/ws-dw-ws-dwsuddi-i.html">Discovering Web Services: UDDI (a Tutorial)</a></strong><br/>Rick Hightower, IBM developerWorks<br/>February 2003</p>      
+      <p><strong><a href="http://www.gotdotnet.com/team/karstenj/docs/rss_in_uddi.aspx">Registering and Discovering RSS Feeds in UDDI</a></strong><br/>Keep your Web services current with WSDL and UDDI<br/>Karsten Januszewski, GotDotNet.com<br/>July 2002</p>
+      <p><strong><a href="http://www.oasis-open.org/committees/uddi-spec/doc/tn/uddi-spec-tc-tn-wsdl-v2.htm">Using WSDL in a UDDI Registry</a></strong><br/>John Colgrave and Karsten Januszewski, UDDI.org<br/>November 2003</p>            
+      <p><strong><a href="http://msdn.microsoft.com/library/en-us/dnuddi/html/runtimeuddi1.asp">Using UDDI at Runtime Part I</a></strong><br/>Building the Web Services Infrastructure to Support Client Applications<br/>Karsten Januszewski, Microsoft<br/>December 2001</p>      
+      <p><strong><a href="http://msdn.microsoft.com/library/en-us/dnuddi/html/runtimeuddi2.asp">Using UDDI at Runtime Part II</a></strong><br/>Dynamically Binding to Multiple Web Service Implementations<br/>Karsten Januszewski, Microsoft<br/>May 2002</p>
+      <p><strong><a href="http://www.onjava.com/pub/a/onjava/2002/02/27/uddi.html">Understanding UDDI and JAXR</a></strong><br/>The why and what of the new approach<br/>Satya Komatineni, O'Reilly ONJava.com<br/>February 2002</p>
+      <p><strong><a href="http://java.sun.com/developer/technicalArticles/WebServices/jaxrws/">Registration and Discovery of Web Services Using JAXR with XML Registries such as UDDI and ebXML</a></strong><br/>The why and what of the new approach<br/>Qusay H. Mahmoud, Sun Microsystems<br/>June 2002</p>      
+      <p><strong><a href="http://java.sun.com/webservices/docs/1.0/tutorial/doc/JAXR.html">Java API for XML Registries (a Tutorial)</a></strong><br/>The why and what of the new approach<br/>Kim Haase, Sun Microsystems</p>      
+      <p><strong><a href="http://www-106.ibm.com/developerworks/webservices/library/ws-udmod1/">A New Approach to UDDI and WSDL Part 1</a></strong><br/>The why and what of the new approach<br/>John Colgrave, IBM developerWorks<br/>August 2003</p>      
+      <p><strong><a href="http://www-106.ibm.com/developerworks/webservices/library/ws-udmod2.html">A New Approach to UDDI and WSDL Part 2</a></strong><br/>Usage scenarios in publishing and finding WSDL service descriptions<br/>John Colgrave, IBM developerWorks<br/>September 2003</p>            
+      <p><strong><a href="http://www.onjava.com/pub/a/onjava/2002/02/27/uddi.html">Understanding UDDI and JAXR</a></strong><br/>Satya Komatineni, O'Reilly OnJava.com<br/>February 2002</p>
+      <p><strong><a href="http://www.sys-con.com/webservices/article.cfm?id=87">Understanding UDDI tModels and Taxonomies</a></strong><br/>The key integration point for products supporting Web services<br/>Andy Grove, Web Services Journal (Volume 1, Issue 2)<br/>January 2001</p>      
+      <p><strong><a href="http://www-106.ibm.com/developerworks/webservices/library/ws-wsdl/">Understanding WSDL in a UDDI Registry Part 1</a></strong><br/>How to publish and find WSDL service descriptions<br/>Peter Brittenham, Francisco Cubera, Dave Ehnebuske, Steve Graham, IBM developerWorks<br/>September 2001 (updated September 2002)</p>      
+      <p><strong><a href="http://www-106.ibm.com/developerworks/webservices/library/ws-wsdl2/">Understanding WSDL in a UDDI Registry Part 2</a></strong><br/>Usage scenarios in publishing and finding WSDL service descriptions<br/>Peter Brittenham, IBM developerWorks<br/>September 2001</p>      
+      <p><strong><a href="http://www-106.ibm.com/developerworks/webservices/library/ws-wsdl3/">Understanding WSDL in a UDDI Registry Part 3</a></strong><br/>How to publish and find WSDL service descriptions<br/>Peter Brittenham, IBM developerWorks<br/>November 2001</p>
+      <p><strong><a href="http://www-106.ibm.com/developerworks/webservices/library/ws-wsdl3/">UDDI - A Foundation for Web Services</a></strong><br/>Thomas A. Bellwood, IBM developerWorks<br/>November 2001</p>
+      <p><strong><a href="http://www.stencilgroup.com/ideas_scope_200104uddi.html">Why UDDI Will Succeed, Quietly: Two Factors Push Web Services Forward</a></strong><br/>Brent Sleeper, The Stencil Group<br/>April 2001</p>
+      <p><strong><a href="http://www.uddi.org/pubs/TN-taxonomy-provider-V1.00-Final-20010717.pdf">Providing a Taxonomy for Use in UDDI Version 2</a></strong><br/>UDDI.org<br/>July 2001</p>
+      <p><strong><a href="http://www.developer.com/services/article.php/1367781">The Role of Taxonomies in UDDI: tModels Demystified</a></strong><br/>Ravi Trivedi, Developer.com</p>
+      <p><strong><a href="http://www.developer.com/services/article.php/3374631">Versioning of Web Services: An UDDI Subscription-Based Approach</a></strong><br/>Aravilli Srinivasa Rao, Developer.com</p>
+      <p><strong><a href="http://www.gotdotnet.com/team/karstenj/docs/rss_in_uddi.aspx">Registering and Discovering RSS Feeds in UDDI</a></strong><br/>Karsten Januszewski, GotDotNet.com</p>
+    </section>
+
+    <section name="Related Specifications">        
+      <p><strong><a href="http://www.w3.org/TR/SOAP/">SOAP W3C Specification</a></strong></p>
+      <p><strong><a href="http://www.w3c.org/TR/wsdl.html">Web Services Description Language (WSDL) 1.1</a></strong></p>
+      <p><strong><a href="http://java.sun.com/xml/jaxr/">Java API for XML Registries (JAXR)</a></strong></p>
+    </section>
+               
+    <section name="Other Resources">        
+      <p><strong><a href="http://java.sun.com/docs/books/jls/index.html">The Java Language Specification</a></strong><br/>
+        Written by the creators of the Java Programming Language, this online
+        book is considered by many to be the bible for programming in Java. A must
+        read.
+      </p>
+      <p><strong><a href="http://java.sun.com/products/jdk/javadoc/index.html">Javadoc</a></strong><br/>
+        Javadoc is the automatic software documentation generator used by Java
+        since it was first released. All code written for this project must be
+        documented using Javadoc conventions.
+      </p> 
+      <p><strong><a href="http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html">The Java Code Conventions</a></strong><br/>
+        This Sun document specifies the de-facto standard way of formatting
+        Java code. All code written for this project must follow these conventions.
+      </p>
+    </section>
+
+  </body>
+</document>
\ No newline at end of file

Added: webservices/juddi/branches/v3_trunk/src/site/xdoc/list-guidelines.xml
URL: http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/src/site/xdoc/list-guidelines.xml?rev=782125&view=auto
==============================================================================
--- webservices/juddi/branches/v3_trunk/src/site/xdoc/list-guidelines.xml (added)
+++ webservices/juddi/branches/v3_trunk/src/site/xdoc/list-guidelines.xml Fri Jun  5 20:30:38 2009
@@ -0,0 +1,48 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "http://forrest.apache.org/dtd/document-v12.dtd">
+<document>
+  <properties>
+    <title>Mailing Lists Guidelines</title>
+  </properties>
+  <body>
+  
+  <anchor id="guidelines"/>
+  <section name="Mailing List Guidelines">
+    <p>Every volunteer project obtains its strength from the people involved in it. Mailing lists provide a simple and effective communication mechanism. 
+    </p>
+    <p>You are welcome to join any of our mailing lists (or all of them if you wish). You can choose to lurk, or actively participate. It's up to you. 
+    </p>
+    <p>Before you join these lists, you should make sure that you read and follow the guidelines below. 
+    </p>
+    <p><strong>Do your best to respect the charter of the mailing list</strong><br/>There are three types of lists that you can join: 
+    </p>
+    <ul>
+      <li>The <a href="#juddi-user">User</a> list is where you should send questions and comments about configuration, setup, usage and other "user" types of questions.</li> 
+      <li>The <a href="#juddi-dev">Developer</a> list is where you should should send questions and comments about the actual software source code and general "development" types of questions.</li> 
+      <li>The <a href="#juddi-cvs">Commit</a> list is used for tracking committer activity in the project's CVS repository. This list is used for informational purposes only.  Please do not post messages to this list.  Questions regarding activity on this list should be posted on the <a href="#juddi-dev">Developer</a> list.</li> 
+    </ul>
+    <p><strong>Join the lists that are appropriate for your discussion</strong><br/>Please make sure that you are joining the list that is appropriate for the topic or 
+      product that you would like to discuss.
+    </p>
+    <p><strong>Do not abuse resources in order to get help</strong><br/>Asking your configuration or user type of question on the developers list because you think that 
+      you will get help more quickly by going directly to the developers instead of to the user base is not very nice. Chances are that doing this will 
+      actually prevent people from answering your question because it is clear that you are trying to abuse resources.
+    </p>
+    <p><strong>Avoid sending HTML or "Stylized" email to the list</strong><br/>Do your best to ensure that you are not sending HTML or "Stylized" email to the list. If 
+      you are using Outlook or Outlook Express or Eudora, chances are that you are sending HTML email by default. There is usually a setting that will allow you to 
+      send "Plain Text" email. If you are using Microsoft products to send email, there are several bugs in the software that prevent you from turning off the sending 
+      of HTML email.
+    </p> 
+    <p><strong>Watch where you are sending email</strong><br/>The majority of our mailing lists have set the Reply-To to go back to the list. That means that when you 
+      Reply to a message, it will go to the list and not to the original author directly. The reason is because it helps facilitate discussion on 
+      the list for everyone to benefit from. Be careful of this as sometimes you may intend to reply to a message directly to someone instead of 
+      the entire list.
+    </p>
+    <p><strong>Do not crosspost messages</strong><br/>In other words, pick a mailing list and send your messages to that mailing list only. Do not send your messages 
+      to multiple mailing lists. The reason is that people may be subscribed to one list and not to the other. Therefore, some people may only see 
+      half of the conversation.
+    </p>
+  </section>
+
+  </body>
+</document>

Added: webservices/juddi/branches/v3_trunk/src/site/xdoc/participate.xml
URL: http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/src/site/xdoc/participate.xml?rev=782125&view=auto
==============================================================================
--- webservices/juddi/branches/v3_trunk/src/site/xdoc/participate.xml (added)
+++ webservices/juddi/branches/v3_trunk/src/site/xdoc/participate.xml Fri Jun  5 20:30:38 2009
@@ -0,0 +1,80 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "http://forrest.apache.org/dtd/document-v12.dtd">
+<document>
+  <properties>
+    <title>Participation</title>
+  </properties>
+  <body>
+	  <section name="Introduction">
+      <p>Every volunteer project obtains its strength from the people involved in it.
+        We invite you to participate as much or as little as you choose. The roles
+        and responsibilities that people can assume in the project are based on
+        merit. Everybody's input matters!
+      </p>
+      <p>There are a variety of ways to participate. Regardless of how you choose
+        to participate, we suggest you join some or all of our <a href="lists.html">mailing lists</a>.
+      </p>
+      </section>
+
+      <section name="Use the Products &amp; Give Us Feedback">
+        <p>Using the products,reporting bugs, making feature requests, etc. is by
+          far the most important role. It's your feedback that allows the technology
+          to evolve.
+          <ul>
+            <li><a href="mail-lists.html">Join Mailing Lists</a></li>
+            <li><a href="releases.html">Download Binary Builds</a></li>
+            <li><a href="http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10401">Report Bugs &amp; Request New Features</a></li>
+          </ul>
+        </p>
+      </section>
+
+      <section name="Contribute Code or Documentation Patches">
+        <p>In this role, you participate in the actual development of the code. If this
+          is the type of role you'd like to play, here are some steps (in addition to
+          the ones above) to get you started:
+          <ul>
+            <li> <a href="list-guidelines.html#guidelines">Read Mailing List Guidelines </a></li>
+            <li> <a href="library.html">Review Reference Library </a></li>
+            <li> <a href="releases.html">Download the Source Code</a></li>
+            <li> <a href="source-repository.html">Access SVN Repository </a></li>
+          </ul>
+        </p>
+        <p>Any and all new development or bug fixing uses the latest code base.
+          If you have a patch, it should be submitted against the latest available
+          code.
+        </p>
+      </section>
+
+      <section name="Getting Support on the Lists">
+        <p>We do all development and bug fixing on the latest available code base.
+          If you've encountered what you think is a bug, please first check the
+          <a href="http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10401">issues database</a> for known issues. If you
+          can't find your bug, make sure you're using the latest code base. We are
+          not able to fix bugs on earlier code bases.
+        </p>
+        <p>Please include any relevant version information and the error message
+            text, if there is one. If you have a problem with a specific interface,
+            like find_business, you'll likely be asked to post a log of the SOAP
+            message exchanges between your client and the jUDDI server. You can
+            use the axis tool
+            <a href="http://ws.apache.org/axis/java/developers-guide.html">TCPMon</a>
+            to capture these messages.
+        </p>
+        <p>Remember, Apache helps those that help themselves. Please take a look
+          at Eric S. Raymond's and Rick Moen's explanation of
+          <a href="http://www.catb.org/~esr/faqs/smart-questions.html">"How to Ask Questions The Smart Way</a>.
+          </p>
+      </section>
+      <section name="jUDDI Wiki">
+        <p>Like other Apache projects, jUDDI maintains a wiki, a sort of virtual
+          meeting place for the jUDDI community. This is a resource available
+          to everyone, and you are encouraged to contribute. This is a good resource
+          for 'HowTos' for common configuration issues.
+          <ul>
+            <li> <a href="http://wiki.apache.org/ws/jUDDI">http://wiki.apache.org/ws/jUDDI</a></li>
+          </ul>
+          </p>
+      </section>
+
+  </body>
+</document>
\ No newline at end of file

Added: webservices/juddi/branches/v3_trunk/src/site/xdoc/releases.xml
URL: http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/src/site/xdoc/releases.xml?rev=782125&view=auto
==============================================================================
--- webservices/juddi/branches/v3_trunk/src/site/xdoc/releases.xml (added)
+++ webservices/juddi/branches/v3_trunk/src/site/xdoc/releases.xml Fri Jun  5 20:30:38 2009
@@ -0,0 +1,68 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "http://forrest.apache.org/dtd/document-v12.dtd">
+<document>
+  <properties>
+    <title>jUDDI Releases</title>
+  </properties>
+  <body>
+    <section name="Releases">    
+        
+      <table>   
+           
+        <tr> 
+          <td><strong>Name</strong></td>
+          <td><strong>Date</strong></td>
+          <td><strong>Description</strong></td>
+        </tr>
+        <tr>
+          <td><a href="http://www.apache.org/dist/ws/juddi/3_0/">3.0.0.beta</a></td>
+          <td>June 5, 2009</td>
+          <td>Stable Release for Version 3.0, with limited console support only.</td>
+        </tr> 
+        <tr>
+          <td><a href="http://www.apache.org/dist/ws/juddi/2_0RC7/">2.0rc7</a></td>
+          <td>May 31, 2009</td>
+          <td>Stable Release Candidate #7 for Version 2.0.</td>
+        </tr> 
+		<tr>
+          <td><a href="http://www.apache.org/dist/ws/juddi/3_0/">3.0.0.alpha</a></td>
+          <td>Februari 13, 2009</td>
+          <td>Unstable Preview Release for Version 3.0.</td>
+        </tr> 
+        <tr>
+          <td><a href="http://www.apache.org/dist/ws/juddi/2_0RC6/">2.0rc6</a></td>
+          <td>Februari 10, 2009</td>
+          <td>Stable Release Candidate #6 for Version 2.0.</td>
+        </tr>        
+		<tr>
+          <td><a href="http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/juddi/juddi/2.0rc5/">2.0rc5</a></td>
+          <td>December 13, 2007</td>
+          <td>Stable Release Candidate #5 for Version 2.0.</td>
+        </tr>
+
+        <tr>
+          <td><a href="http://www.apache.org/dyn/closer.cgi/ws/juddi/0_9RC4/">0.9rc4</a></td>
+          <td>June 14, 2005</td>
+          <td>Stable Release Candidate #4 for Version 0.9.</td>
+        </tr>
+        <tr>
+          <td><a href="http://archive.apache.org/dist/ws/juddi/0_9rc3/">0.9rc3</a></td>
+          <td>July 2, 2004</td>
+          <td>Stable Release Candidate #3 for Version 0.9.</td>
+        </tr>
+        <tr>
+          <td><a href="http://archive.apache.org/dist/ws/juddi/0_9rc2/">0.9rc2</a></td>
+          <td>June 29, 2004</td>
+          <td>Stable Release Candidate #2 for Version 0.9.</td>
+        </tr>
+        <tr>
+          <td><a href="http://archive.apache.org/dist/ws/juddi/0_9rc1/">0.9rc1</a></td>
+          <td>Stable June 16, 2004</td>
+          <td>Release Candidate #1 for Version 0.9.</td>
+        </tr>
+
+      </table>
+		
+    </section>
+  </body>
+</document>

Added: webservices/juddi/branches/v3_trunk/src/site/xdoc/usersguide.xml
URL: http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/src/site/xdoc/usersguide.xml?rev=782125&view=auto
==============================================================================
--- webservices/juddi/branches/v3_trunk/src/site/xdoc/usersguide.xml (added)
+++ webservices/juddi/branches/v3_trunk/src/site/xdoc/usersguide.xml Fri Jun  5 20:30:38 2009
@@ -0,0 +1,179 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "http://forrest.apache.org/dtd/document-v12.dtd">
+<document>
+  <properties>
+    <title>jUDDI User's Guide</title>
+  </properties>
+  <body>
+
+    <anchor id="requirements"/>
+    <section name="Requirements">
+      <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 <link href="http://jakarta.apache.org/tomcat/">Jakarta
+        Tomcat</link>.  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>Instructions for deploying jUDDI to several application servers have
+        been donated and are available in the <link href="http://wiki.apache.org/ws/jUDDI">HOW-TO</link>
+        section of the jUDDI wiki.
+      </p>
+      <p>jUDDI also requires an external datastore in which to persist the 
+        registry data it manages.  Typically this is a relational database
+        management system such as MySQL, Oracle or DB2. Support for several 
+        open source and commercial database products are included. See the 
+        section below titled <link href="#datastore">Persistence</link> for 
+        more information.
+      </p>
+    </section>
+
+    <anchor id="config"/>
+    <section name="Configuration">
+      <p>To properly configure and deploy jUDDI it will be helpful to understand
+        a bit about it's architecture. jUDDI consist of a core request processor
+        that unmarshalls incoming 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 your registry
+        up and running quickly. These sub-components 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 <link href="#moddev">module development</link> section of this 
+        guide for more information regarding jUDDI module development.
+      </p>
+    </section>
+
+    <anchor id="datastore"/>
+    <section name="Persistence (jUDDI DataStore)">
+      <p>jUDDI needs a place to store it's registry data so it should come as 
+        no surprise that jUDDI is pre-configured to use JDBC and any one of 
+        several different DBMSs to do this.
+      </p>            
+      <p>The process of setting this up is straight forward. Start by creating 
+        a new jUDDI database using the instructions for your preferred DBMS 
+        which you will find in the 'sql' directory of your jUDDI distribution. 
+        At the time of this writing instructions for the following products 
+        were available:
+      </p>
+      <p>
+        <ul>
+          <li>MySQL</li>
+          <li>DB2</li>
+          <li>HSQLdb (HypersonicSQL)</li>
+          <li>Sybase</li>
+          <li>PostreSQL</li>
+          <li>Oracle</li>
+          <li>TotalXML</li>
+          <li>JDataStore (Borland)</li>
+        </ul>
+      </p>
+      <p>If support for your DBMS is not listed you might try posting a message
+        to the juddi-user list to see if someone has already developed support
+        for it.  You can also try to create the scripts yourself by using the 
+        instructions for a supported DBMS as a guide. Please consider 
+        contributing your work back to the project so the next person won't 
+        have the same issue.
+      </p>      
+      <p>To complete the DataStore set up you'll need to configure a JNDI
+        Datasource with a name of <b>'jdbc/juddiDB'</b> in the application 
+        server or servlet engine that you're deploying to. Datasource setup 
+        varies on an product-by-product basis so review documentation for 
+        your application server. If you're deploying to Jakarta Tomcat,  take a 
+        look at Tomcat's <link  href="http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jndi-datasource-examples-howto.html">JNDI 
+        Datasource HOW-TO</link> for assistance.
+      </p>
+    </section>
+
+    <anchor id="authenticator"/>
+    <section name="Authentication (jUDDI Authenticator)">
+      <p>Authenticating a jUDDI publisher is a two-step process. The first step
+        confirms that the ID/password combination provided by the user in a 
+        get_authToken request is valid. The default Authenticator implementation 
+        simply approves any authentication attempt. It is expected that a 
+        typical jUDDI deployment will use an external authentication 
+        mechanism.  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 jUDDI Developers Guide for more information on 
+        developing a custom jUDDI authentication module for your environment.
+      </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>
+      <p>
+        <b>
+        <pre>        
+          INSERT INTO PUBLISHER (PUBLISHER_ID,PUBLISHER_NAME,ADMIN,ENABLED)
+          VALUES ('jdoe','John Doe','false','true');
+        </pre>
+        </b>
+      </p>
+      <p>The PUBLISHER table consists of several columns but only four of them
+        are required and they are defined as follows:
+      </p>
+      <p>
+        <table>
+         <tr><th>Column Name</th><th>Description</th></tr>
+         <tr><td>PUBLISHER_ID</td><td>The user ID the publisher uses when authenticating. IMPORTANT: This should be the same value used to authenticate with the external authentication service.</td></tr>
+         <tr><td>PUBLISHER_NAME</td><td>The publisher's name (or in UDDI speak the Authorized Name).</td></tr>
+         <tr><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>
+         <tr><td>ENABLED</td><td>Indicate if the publishers account is enabled and eligible for use.</td></tr>
+        </table>
+      </p>
+      <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>
+    </section>
+
+    <anchor id="uuidgen"/>
+    <section name="UUID Generation (jUDDI UUIDGen)">
+      <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 a UUID typically requires access to hardware level
+        information that (unfortunately) is not easily 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 the jUDDI implements this alternative method.
+      </p>
+    </section>
+
+    <anchor id="logging"/>
+    <section name="Logging">
+      <p>When deploying jUDDI you may wish to make changes to the
+       juddi.properties and log4j.properties 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 log4j.appender.LOGFILE.File which specifies the name and location of
+       the jUDDI log file.
+      </p>
+    </section>
+
+    <anchor id="moddev"/>
+    <section name="Module Development">
+      <p>Coming Soon.
+      </p>
+    </section>
+
+  </body>
+</document>
\ No newline at end of file

Added: webservices/juddi/branches/v3_trunk/src/site/xdoc/who.xml
URL: http://svn.apache.org/viewvc/webservices/juddi/branches/v3_trunk/src/site/xdoc/who.xml?rev=782125&view=auto
==============================================================================
--- webservices/juddi/branches/v3_trunk/src/site/xdoc/who.xml (added)
+++ webservices/juddi/branches/v3_trunk/src/site/xdoc/who.xml Fri Jun  5 20:30:38 2009
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "http://forrest.apache.org/dtd/document-v12.dtd">
+<document>
+  <properties>
+    <title>The jUDDI project team</title>
+  </properties>
+  <body>
+    
+    <section name="Who We Are">
+      <p>
+        The jUDDI Project operates on a meritocracy: the more you do,
+        the more responsibility you will obtain. This page lists all
+        of the people who have gone the extra mile and are
+        Committers. If you would like to get involved, the first step
+        is to join the mailing lists.
+      </p>
+      <p>
+        We ask that you please do not send us emails privately asking
+        for support. We are non-paid volunteers who help out with the
+        project and we do not necessarily have the time or energy to
+        help people on an individual basis. Instead, we have setup
+        mailing lists which often contain hundreds of individuals who
+        will help answer detailed requests for help. The benefit of
+        using mailing lists over private communication is that it is
+        a shared resource where others can also learn from common
+        mistakes and as a community we all grow together.
+      </p>
+    </section>
+
+  </body>
+</document>
\ No newline at end of file



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


Mime
View raw message