This commit was manufactured by cvs2svn to create tag
'v20051021_website_update'.
diff --git a/.dates.txt b/.dates.txt
deleted file mode 100644
index 5d10925..0000000
--- a/.dates.txt
+++ /dev/null
@@ -1,5 +0,0 @@
-Web Tools
-http://www.eclipse.org/webtools
-0.7 07/2005 Completed http://download.eclipse.org/webtools/downloads/drops/R-0.7-200507290654/
-1.0 12/2005 Planned http://www.eclipse.org/webtools/development/planning/milestone_plan_1_0.html
-1.5 06/2006 Planned
diff --git a/.project b/.project
deleted file mode 100644
index c7db386..0000000
--- a/.project
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
- <name>webtools</name>
- <comment></comment>
- <projects>
- </projects>
- <buildSpec>
- </buildSpec>
- <natures>
- </natures>
-</projectDescription>
diff --git a/about.html b/about.html
deleted file mode 100644
index ca46f43..0000000
--- a/about.html
+++ /dev/null
@@ -1,85 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="..//default_style.css" type="text/css">
-<link rel="stylesheet" href="..//webtools/wtp.css" type="text/css">
-<title>About the Web Tools Platform Project</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">About the Web Tools Platform Project</font>
-<br>
-<font class="indexsub">About the Web Tools Platform Project</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="..//images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<br>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<table>
-<tr>
-<td valign="top">
-<table>
-<tr>
-<td valign="top">
-<table WIDTH="100%" CELLPADDING="2" CELLSPACING="5" BORDER="0">
-<tr>
-<td BGCOLOR="#0080C0" COLSPAN="2" VALIGN="TOP" ALIGN="LEFT"><b><font face="Arial,Helvetica" color="#FFFFFF">All About The WTP Project</font></b></td>
-</tr>
-</table>
-<table width="100%" cellpadding="2" cellspacing="5" border="0">
-<tr>
-<td valign="TOP">
- The Eclipse Web Tools Platform Project is an open source project of eclipse.org, overseen
- by a <a class="wikipage" href="pmc.html">Project Management Committee</a> (PMC) and project
- leaders. The PMC Planning Council coordinates identified resources of the project against a
- Project Development Plan. The work is done in subprojects working against a
- <a class="external" href="http://dev.eclipse.org/viewcvs/index.cgi/?cvsroot=WebTools_Project">CVS
- repository</a>. The <a class="wikipage" href="project-charter.html">Eclipse Web Tools Platform
- Project Charter</a> describes the organization of the project, roles and responsibilities of the
- participants, and top-level development process for the project.
- </td>
-</tr>
-</table>
-<table width="100%" cellpadding="2" cellspacing="5" border="0">
- <tr>
- <td width="4%" valign="top" align="right"><img border="0" src="../images/Adarrow.gif"></td><td width="46%" valign="top"><b><a href="project-principles.html">Project Principles</a></b>
-<br>
- The key principles on which this project is run.
- </td><td width="4%" valign="top" align="right"><img border="0" src="../images/Adarrow.gif"></td><td width="46%" valign="top"><b><a href="project-scope.html">Project Scope</a></b>
-<br>
- "Web Tools" is big, very big, so big that it could encompass everything. So
- we've defined a reasonable scope for the Web Tools Platform Project.
- </td>
- </tr>
-
- <tr>
- <td width="4%" valign="top" align="right"><img border="0" src="images/charter.gif"></td><td width="46%" valign="top"><b><a href="project-charter.html">Project Charter</a></b>
-<br>
- Describes the organization of the project, roles and responsibilities of the participants, and
- top-level development process for the project.
- </td>
- <td width="4%"></td>
- <td width="46%"></td>
- </tr>
- </table>
-<table width="100%" cellpadding="2" cellspacing="5" border="0"></table>
-</td><td valign="top"></td>
-</tr>
-</table>
-</td><td valign="top"></td>
-</tr>
-</table>
-</tbody>
-</table>
-<p></p>
-<p>Please see our <a href="http://www.eclipse.org/legal/privacy.html">privacy
- policy</a> and website <a href="http://www.eclipse.org/legal/termsofuse.html">terms
- of use</a>. For problems with the eclipse.org site, please contact the
- <a href="mailto:webmaster@eclipse.org">webmaster</a> or read the
- <a href="..//webmaster/index.html">webmaster FAQ</a> for answers to common questions!</p>
-</body>
-</html>
diff --git a/about.xml b/about.xml
deleted file mode 100644
index d3dafe5..0000000
--- a/about.xml
+++ /dev/null
@@ -1,29 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<?xml-stylesheet type="text/xsl" href="wtphome.xsl"?>
-<sections title="About the Web Tools Platform Project" subtitle="About the Web Tools Platform Project">
- <meta name="root" content="../" />
- <section class="main" name="All About The WTP Project">
- <description>
- The Eclipse Web Tools Platform Project is an open source project of eclipse.org, overseen
- by a <a class="wikipage" href="pmc.html">Project Management Committee</a> (PMC) and project
- leaders. The PMC Planning Council coordinates identified resources of the project against a
- Project Development Plan. The work is done in subprojects working against a
- <a class="external" href="http://dev.eclipse.org/viewcvs/index.cgi/?cvsroot=WebTools_Project">CVS
- repository</a>. The <a class="wikipage" href="project-charter.html">Eclipse Web Tools Platform
- Project Charter</a> describes the organization of the project, roles and responsibilities of the
- participants, and top-level development process for the project.
- </description>
- <section name="Project Principles" link="project-principles.html" icon="../images/Adarrow.gif">
- The key principles on which this project is run.
- </section>
- <section name="Project Scope" link="project-scope.html" icon="../images/Adarrow.gif">
- "Web Tools" is big, very big, so big that it could encompass everything. So
- we've defined a reasonable scope for the Web Tools Platform Project.
- </section>
- <section name="Project Charter" link="project-charter.html" icon="images/charter.gif">
- Describes the organization of the project, roles and responsibilities of the participants, and
- top-level development process for the project.
- </section>
- </section>
-</sections>
-
\ No newline at end of file
diff --git a/build.xml b/build.xml
deleted file mode 100644
index 48af1c0..0000000
--- a/build.xml
+++ /dev/null
@@ -1,141 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!--
-
- Version: $Id: build.xml,v 1.26 2005/09/29 18:56:15 lmandel Exp $
-
- Ant build script for WTP Web Site.
-
- ChangeLog:
-
- 2005-09-22: Arthur Ryman <ryman@ca.ibm.com>
- - Factored out plans build into separate build script.
-
- 2005-09-15: Lawrence Mandel <lmandel@ca.ibm.com>
- - Factored out community build into separate build script.
-
- 2005-09-14: Arthur Ryman <ryman@ca.ibm.com>
- - temporarily comment out XSLT that use xalan:nodeset to avoid build problems
- the offending stylesheets are community.xsl, communityresources.xsl, and pastevents.xsl
- Why do these use xalan: extensions? Our stylesheets should be portable.
-
- 2005-08-26: Lawrence Mandel <lmandel@ca.ibm.com>
- - added community stylesheets back to the build after fixing xalan:nodeset problem
-
- 2005-08-26: Arthur Ryman <ryman@ca.ibm.com>
- - temporarily comment out XSLT that use xalan:nodeset to avoid build problems
-
- 2005-08-23: Lawrence Mandel <lmandel@ca.ibm.com>
- - added community resources build call
- - added community page build call
- - added community past events build call
- - added specific call for presentation archive
-
- 2005-08-10: Lawrence Mandel <lmandel@ca.ibm.com>
- - add faq/CommitterFaq.xml file build call
-
- 2005-08-03: Lawrence Mandel <lmandel@ca.ibm.com>
- - added faq/main.xml file build call
-
- 2005-07-29: Lawrence Mandel <lmandel@ca.ibm.com>
- - added whatsnew.xml file build call
-
- 2005-06-28: Arthur Ryman <ryman@ca.ibm.com>
- - exclude all build.xml files from XSLT transformation
-
- 2005-05-16: Arthur Ryman <ryman@ca.ibm.com>
- - Added call to build people folder.
-
- 2005-05-04: Arthur Ryman <ryman@ca.ibm.com>
- - Added people folder.
-
- 2005-04-11: Arthur Ryman <ryman@ca.ibm.com>
- - Added Presentations page.
-
- 2005-02-21 Lawrence Mandel <lmandel@ca.ibm.com>
- - Added force=true attribute for composite pages.
-
- 2005-02-16 Lawrence Mandel <lmandel@ca.ibm.com>
- - Added news page.
- - Added development/main.xml page.
-
- 2005-02-14 Lawrence Mandel <lmandel@ca.ibm.com>
- - Created separate news.xml file and included it in main.xml.
- - Added about page.
- - Added transform for news XML to RSS.
-
- 2005-02-13: Arthur Ryman <ryman@ca.ibm.com>
- - Added Help Wanted page.
-
- 2005-01-28: Arthur Ryman <ryman@ca.ibm.com>
- - Created.
- - Validate all XML and XSLT files.
- - Transform all XML to HTML.
-
- 2005-02-21: Jeffrey Liu <jeffliu@ca.ibm.com>
- - Added performance improvement plan
--->
-
-<project name="webtools" default="main" basedir=".">
-
- <target name="main" depends="validate, html, rss" description="Build WTP Web site (validate, html, rss)." />
-
- <target name="validate" description="Validates all XML and XSLT files.">
- <xmlvalidate lenient="true">
- <fileset dir="." includes="**/*.xml, **/*.xsl, **/*.xsd, **/*.data" />
- </xmlvalidate>
- <!--
- <xmlvalidate lenient="false">
- <fileset dir="." includes="**/*.xsd"/>
- <attribute name="http://xml.org/sax/features/validation" value="true"/>
- <attribute name="http://apache.org/xml/features/validation/schema" value="true"/>
- <attribute name="http://xml.org/sax/features/namespaces" value="true"/>
- </xmlvalidate>
- -->
- </target>
-
- <target name="html" depends="help-wanted, community, plans, faq" description="Transforms XML to HTML.">
- <xslt in="main.xml" out="main.html" style="wtphome.xsl" force="true" />
-
- <xslt in="about.xml" out="about.html" style="wtphome.xsl" force="true" />
-
- <xslt in="news.xml" out="news.html" style="wtphome.xsl" force="true" />
-
- <xslt in="development/main.xml" out="development/main.html" style="wtphome.xsl" force="true" />
-
- <xslt in="releases/0.7/whatsnew.xml" out="releases/0.7/whatsnew.html" style="wtphome.xsl" force="true" />
-
- <xslt style="development/milestone_plans/stylesheets/milestone-calendar.xsl" in="development/milestone_plans/reports/report-calendar-by-developer.xml" out="development/milestone_plans/reports/report-calendar-by-developer.html" />
-
- <xslt style="development/milestone_plans/stylesheets/milestone-overview.xsl" in="development/milestone_plans/reports/report-milestone-overview.xml" out="development/milestone_plans/reports/report-milestone-overview.html" />
-
- <xslt style="development/milestone_plans/stylesheets/milestone-bulletList.xsl" includes="**/*milestone_plan*.xml" destdir="." />
-
- <xslt style="development/milestone_plans/stylesheets/performance.xsl" in="development/milestone_plans/reports/report-milestone-overview.xml" out="development/milestone_plans/reports/performance.html" force="true" />
-
- <xslt style="wtp.xsl" includes="**/*.xml" excludes="people/**/*.*, **/build.xml, main.xml, about.xml, development/main.xml, releases/0.7/whatsnew.xml, **/filelist.xml, development/milestone_plans/reports/*.xml, **/*milestone_plan*.xml, news.xml, **/*-rss20.xml, faq/**/*.*, community/**/*.*, plans/**/*.*" destdir="." />
-
- <ant dir="people" description="Builds the People pages and Contributors page and index."/>
-
- </target>
-
- <target name="help-wanted" description="generates Help Wanted page.">
- <xslt style="development/milestone_plans/stylesheets/help-wanted.xsl" in="development/milestone_plans/reports/report-milestone-overview.xml" out="development/milestone_plans/reports/help-wanted.html" force="true" />
- </target>
-
- <target name="rss" description="Transforms XML to RSS.">
- <xslt in="news.xml" out="news-rss20.xml" style="rss20.xsl" />
- </target>
-
- <target name="community" description="Transforms community XML to HTML">
- <ant dir="community" description="Builds the community pages."/>
- </target>
-
- <target name="plans" description="Transforms plans XML to HTML">
- <ant dir="plans" description="Builds the plans pages."/>
- </target>
-
- <target name="faq" description="Transforms FAQ XML to HTML">
- <ant dir="faq" description="Builds the FAQ pages."/>
- </target>
-</project>
\ No newline at end of file
diff --git a/commit.html b/commit.html
deleted file mode 100644
index 1540a37..0000000
--- a/commit.html
+++ /dev/null
@@ -1,118 +0,0 @@
-
-
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US"><head>
-<body bgcolor="#FFFFFF">
-<link rel="stylesheet" href="../default_style.css" type="text/css">
-<table border=0 cellspacing=5 cellpadding=2 width="100%" >
- <tr>
- <td align=LEFT valign=TOP colspan="1" bgcolor="#0080C0"><b><font face="Arial,Helvetica" color="#FFFFFF">
- Eclipse Webtools Committers by Subproject</font></b></td>
- <td align=RIGHT valign=TOP colspan="1" bgcolor="#0080C0"><font face="Arial,Helvetica" color="#FFFFFF">
- Thu Nov 11 21:30:02 2004</font></td>
- </tr>
-</TABLE>
-
-<table border=0 cellspacing=5 cellpadding=2 width="100%" >
- <tr bgcolor="#999999">
- <td width="75%" align=left valign=top colspan="2"><b><font face="Arial,Helvetica" color="#ffffff"><a name="webtools"></a><a href="../webtools" target="_top" class="bar">Webtools
- Subproject</a> </font></b></td>
- </tr>
-</table>
-<table width="75%" border="1"></TABLE>
-
-<table border=0 cellspacing=5 cellpadding=2 width="100%" >
- <tr bgcolor="#999999">
- <td width="75%" align=left valign=top colspan="2"><b><font face="Arial,Helvetica" color="#ffffff"><a name="wtp"></a><a href="../wtp" target="_top" class="bar">Wtp
- Subproject</a> </font></b></td>
- </tr>
-</table>
-<table width="75%" border="1"><tr><td width="30%"><b>Phil Avery</b></td> <td>org.eclipse.wtp.releng<br>wtp-jst-home<br>
-wtp-wst-home
-
-<br>
-</td></tr>
-<tr><td width="30%"><b>Chris Brealey</b></td> <td>org.eclipse.wtp.releng<br>wtp-jst-home<br>
-wtp-wst-home
-
-<br>
-</td></tr>
-<tr><td width="30%"><b>Chuck Bridgham</b></td> <td>org.eclipse.wtp.releng<br>wtp-jst-home<br>
-wtp-wst-home
-
-<br>
-</td></tr>
-<tr><td width="30%"><b>Der_Ping Chou</b></td> <td>org.eclipse.wtp.releng<br>wtp-jst-home<br>
-wtp-wst-home
-
-<br>
-</td></tr>
-<tr><td width="30%"><b>Nitin Dahyabhai</b></td> <td>org.eclipse.wtp.releng<br>wtp-jst-home<br>
-wtp-wst-home
-
-<br>
-</td></tr>
-<tr><td width="30%"><b>Naci Dai</b></td> <td>org.eclipse.wtp.releng<br>wtp-jst-home<br>
-wtp-wst-home
-
-<br>
-</td></tr>
-<tr><td width="30%"><b>Timothy Deboer</b></td> <td>org.eclipse.wtp.releng<br>wtp-jst-home<br>
-wtp-wst-home
-
-<br>
-</td></tr>
-<tr><td width="30%"><b>Gorkem Ercan</b></td> <td>org.eclipse.wtp.releng<br>wtp-jst-home<br>
-wtp-wst-home
-
-<br>
-</td></tr>
-<tr><td width="30%"><b>Bjorn Freeman-Benson</b></td> <td>org.eclipse.wtp.releng<br>wtp-jst-home<br>
-wtp-wst-home
-
-<br>
-</td></tr>
-<tr><td width="30%"><b>Sinan Konya</b></td> <td>org.eclipse.wtp.releng<br>wtp-jst-home<br>
-wtp-wst-home
-
-<br>
-</td></tr>
-<tr><td width="30%"><b>Valeriy Pelyushenko</b></td> <td>org.eclipse.wtp.releng<br>wtp-jst-home<br>
-wtp-wst-home
-
-<br>
-</td></tr>
-<tr><td width="30%"><b>Arthur Ryman</b></td> <td>org.eclipse.wtp.releng<br>wtp-jst-home<br>
-wtp-wst-home
-
-<br>
-</td></tr>
-<tr><td width="30%"><b>Craig Salter</b></td> <td>org.eclipse.wtp.releng<br>wtp-jst-home<br>
-wtp-wst-home
-
-<br>
-</td></tr>
-<tr><td width="30%"><b>Deniz Secilir</b></td> <td>org.eclipse.wtp.releng<br>wtp-jst-home<br>
-wtp-wst-home
-
-<br>
-</td></tr>
-<tr><td width="30%"><b>Sheila Sholars</b></td> <td>org.eclipse.wtp.releng<br>wtp-jst-home<br>
-wtp-wst-home
-
-<br>
-</td></tr>
-<tr><td width="30%"><b>Ozgur Tumer</b></td> <td>org.eclipse.wtp.releng<br>wtp-jst-home<br>
-wtp-wst-home
-
-<br>
-</td></tr>
-<tr><td width="30%"><b>David Williams</b></td> <td>org.eclipse.wtp.releng<br>wtp-jst-home<br>
-wtp-wst-home
-
-<br>
-</td></tr>
-</TABLE></body></html>
\ No newline at end of file
diff --git a/committers/list.html b/committers/list.html
deleted file mode 100644
index 0c7bc57..0000000
--- a/committers/list.html
+++ /dev/null
@@ -1,22 +0,0 @@
-<hhtml>
-<head>
-<link rel="stylesheet" href="http://www.eclipse.org/default_style.css" type="text/css">
-</head>
-
-<body bgcolor="#FFFFFF">
-<table border=0 cellspacing=5 cellpadding=2 width="100%" >
- <tr>
- <td align=LEFT valign=TOP colspan="1" bgcolor="#0080C0"><b>
- <font face="Arial,Helvetica" color="#FFFFFF">Committer Infrastructure
- Requests</font></b></td>
- <td align=RIGHT valign=TOP colspan="1" bgcolor="#0080C0">
- <font face="Arial,Helvetica" color="#FFFFFF">December 22, 2004</font></td>
- </tr>
-</TABLE>
-
-<table width="75%" border="1"></TABLE>
-
-<p>The information in this document was sufficiently out-of-date that the
-document has been removed.<br>
-Please contact the Committer Board Representatives for more information.</p>
-</body>
\ No newline at end of file
diff --git a/community/.project b/community/.project
deleted file mode 100644
index 4058af9..0000000
--- a/community/.project
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
- <name>community</name>
- <comment></comment>
- <projects>
- </projects>
- <buildSpec>
- </buildSpec>
- <natures>
- </natures>
-</projectDescription>
diff --git a/community/articles.xml b/community/articles.xml
deleted file mode 100644
index 1e14f21..0000000
--- a/community/articles.xml
+++ /dev/null
@@ -1,63 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<articles xmlns="http://www.eclipse.org/webtools/articles"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://www.eclipse.org/webtools/articles schemas/articles.xsd ">
- <article title="Eclipse Validators"
- link="http://www.ddj.com/documents/s=9410/ddj0412n/0412n.html"
- publicationDate="2004-12-01">
- <publication name="Dr. Dobb's Journal" link="http://www.ddj.com/"/>
- <author name="Lawrence Mandel"/>
- </article>
- <article title="Create, deploy, and debug Apache Geronimo applications"
- link="http://www-128.ibm.com/developerworks/library/os-gerplug/"
- publicationDate="2005-05-01">
- <publication name="developerWorks" link="http://www.ibm.com/developerworks/"/>
- <author name="Tim Francis"/>
- </article>
- <article title="What's New in Eclipse 3.1"
- link="http://java.sys-con.com/read/99729_1.htm"
- publicationDate="2005-06-01">
- <publication name="Java Developer's Journal" link="http://java.sys-con.com/"/>
- <author name="Ed Burnette"/>
- </article>
- <article title="Web Tools Platform And J2EE Development The Eclipse Way"
- link="http://java.sys-con.com/read/111212.htm"
- publicationDate="2005-07-01">
- <publication name="Java Developer's Journal" link="http://java.sys-con.com/"/>
- <author name="Arthur Ryman"/>
- </article>
- <article title="NetBeans 4.1 & Eclipse 3.1"
- link="http://www.ddj.com/documents/s=9825/ddj0508a/0508a.html"
- publicationDate="2005-08-01">
- <publication name="Dr. Dobb's Journal" link="http://www.ddj.com/"/>
- <author name="Eric J. Bruno"/>
- </article>
- <article title="Building Web Applications with Eclipse, WTP, and Derby"
- link="http://www.ibm.com/developerworks/db2/library/techarticle/dm-0509cline/"
- publicationDate="2005-09-01">
- <publication name="developerWorks" link="http://www.ibm.com/developerworks/"/>
- <author name="Susan L. Cline"/>
- </article>
- <article title="Eclipse Web Tools"
- link="http://www.onjava.com/pub/a/onjava/2005/10/05/eclipse-web-tools.html"
- publicationDate="2005-10-05">
- <publication name="O'Reilly OnJava.com" link="http://www.onjava.com"/>
- <author name="Jeffrey Liu"/>
- <author name="Lawrence Mandel"/>
- </article>
- <article title="Overview of the Eclipse Web Tools Platform"
- link="http://dev2dev.bea.com/pub/a/2005/09/eclipse_web_tools_platform.html"
- publicationDate="2005-09-28">
- <publication name="dev2dev" link="http://dev2dev.bea.com"/>
- <author name="Tim Wagner"/>
- <author name="Ted Bashor"/>
- <author name="Paul Meijer"/>
- <author name="Pieter Humphrey"/>
- </article>
- <article title="Persisting EMF models with WTP"
- link="http://www.eclipse.org/articles/Article-WTP-Persisting-EMF/persisting.html"
- publicationDate="2005-10-10">
- <publication name="Eclipse Corner" link="http://www.eclipse.org/articles/"/>
- <author name="Daniel Rohe"/>
- </article>
-</articles>
diff --git a/community/biopages.xml b/community/biopages.xml
deleted file mode 100644
index 9d7f1cb..0000000
--- a/community/biopages.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<bios xmlns="http://www.eclipse.org/webtools/biopages"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://www.eclipse.org/webtools/biopages schemas/biopages.xsd ">
- <bio name="Gorkem Ercan" link="../people/ercan.html"/>
- <bio name="Tim deBoer" link="../people/deboer.html"/>
- <bio name="Naci Dai" link="../people/dai.html"/>
- <bio name="Arthur Ryman" link="../people/ryman.html"/>
- <bio name="Jeffrey Liu" link="../people/liu.html"/>
- <bio name="Lawrence Mandel" link="../people/mandel.html"/>
- <bio name="Chuck Bridgham" link="../people/bridgham.html"/>
- <bio name="Jochen Krause" link="../people/krause.html" />
- <bio name="Craig Salter" link="../people/salter.html" />
- <bio name="David Williams" link="../people/williams.html" />
- <bio name="Der-Ping Chou" link="../people/chou.html" />
- <bio name="Chris Brealey" link="../people/brealey.html" />
- <bio name="Tim Wagner" link="../people/wagner.html"/>
- <bio name="Keith Chong" link="../people/chong.html"/>
- <bio name="Christophe Ney" link="../people/ney.html"/>
- <bio name="Jens Lukowski" link="../people/lukowski.html"/>
- <bio name="Jason Sholl" link="../people/sholl.html"/>
- <bio name="Seng Phung-Lu" link="../people/phung-lu.html"/>
- <bio name="Peter Moogk" link="../people/moogk.html"/>
- <bio name="Ella Belisario" link="../people/belisario.html"/>
- <bio name="Rupam Kuehner" link="../people/kuehner.html"/>
- <bio name="Tim Francis" link="../people/francis.html"/>
- <bio name="Christopher M. Judd" link="../people/judd.html"/>
- <bio name="Ted Bashor" link="../people/bashor.html"/>
- <bio name="Paul Meijer" link="../people/meijer.html"/>
-</bios>
diff --git a/community/books.xml b/community/books.xml
deleted file mode 100644
index 19692b7..0000000
--- a/community/books.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<books xmlns="http://www.eclipse.org/webtools/books"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://www.eclipse.org/webtools/books schemas/books.xsd ">
- <book title="Pro Eclipse JST: Plug-ins for J2EE Development"
- link="http://www.apress.com/book/bookDisplay.html?bID=447"
- image="images/proeclipsejst.gif"
- publicationDate="2005-08-01">
- <publisher name="APress" link="http://www.apress.com/"/>
- <author name="Christopher M. Judd"/>
- <author name="Hakeem Shittu"/>
- </book>
-</books>
diff --git a/community/build.xml b/community/build.xml
deleted file mode 100644
index fad5c41..0000000
--- a/community/build.xml
+++ /dev/null
@@ -1,49 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!--
-
- Ant build script for WTP Web Site community folder.
-
- Change Log:
-
- 2005-09-15: Lawrence Mandel <lmandel@ca.ibm.com>
- - Created separate build script for community.
-
--->
-
-<project name="community" default="main" basedir=".">
-
- <target name="main" depends="validate, community, tutorials" description="Builds WTP Web site community folder."/>
-
- <target name="community" description="Transforms community XML to HTML" depends="presentations">
-
- <xslt in="communityresources.xml" out="communityresources.html" style="stylesheets/communityresources.xsl" force="true" />
- <xslt in="milestonespecificresources.xml" out="milestonespecificresources.html" style="stylesheets/communityresources.xsl" force="true"/>
-
- <xslt in="events.xml" out="community.html" style="stylesheets/community.xsl" force="true" />
- <xslt in="events.xml" out="pastevents.html" style="stylesheets/pastevents.xsl" force="true" />
- <xslt in="presentations.xml" out="presentations.html" style="stylesheets/wtp.xsl" force="true" />
- </target>
-
- <target name="presentations" description="Transforms presentations data to XML page.">
- <xslt in="presentations.data" out="presentations.xml" style="stylesheets/presentations.xsl" />
- </target>
-
- <target name="validate" description="Validate XML files">
- <xmlvalidate failonerror="yes" lenient="true" warn="yes">
- <fileset dir="." includes="*.xml, *.xsl, *.xsd, *.data" excludes="build.xml" />
- <attribute name="http://xml.org/sax/features/namespaces" value="true" />
- <!--
- <attribute name="http://xml.org/sax/features/validation" value="true" />
-
- <attribute name="http://apache.org/xml/features/validation/schema" value="true" />
- <attribute name="http://apache.org/xml/features/validation/schema-full-checking" value="true" />
- -->
- </xmlvalidate>
- </target>
-
- <target name="tutorials" description="Builds the tutorials">
- <xslt style="../wtp.xsl" includes="tutorials/**/*.xml" excludes="" destdir="." />
- </target>
-
-</project>
\ No newline at end of file
diff --git a/community/community.html b/community/community.html
deleted file mode 100644
index 0bf1eff..0000000
--- a/community/community.html
+++ /dev/null
@@ -1,650 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../default_style.css" type="text/css">
-<link rel="stylesheet" href="../../webtools/wtp.css" type="text/css">
-<title>wtp community</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">wtp community</font>
-<br>
-<font class="indexsub"></font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#0080c0">
-<tbody>
-<tr>
-<td width="90%"><b><font face="Arial,Helvetica" color="#ffffff"><a name="top">Activities and resources from around the WTP community...</a></font></b></td><td align="right" width="10%"></td>
-</tr>
-</tbody>
-</table>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td with="16"> </td><td>
-<p>
- The page is about finding more information about WTP from around the WTP community.
- The community has provided many <a href="communityresources.html#articles">articles</a>, <a href="communityresources.html#books">books</a>, <a href="communityresources.html#tutorials">tutorials</a>, and <a href="communityresources.html#white papers">white papers</a>
- that are dedicated to WTP and can help you to make the most of the WTP platform and tools.
- </p>
-<p>
- We'd like these pages to be useful to you - so please open a
- <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Web%20Tools&component=website">bug report</a>
- for any corrections, additions, pointers, or comments!
- </p>
-<p>
- For software licensing, website terms of use, and legal FAQs, please see our
- <a target="_top" href="http://eclipse.org/legal/main.html">legal stuff</a> page.
- </p>
-</td><td width="16"> </td>
-</tr>
-</table>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#0080c0">
-<tbody>
-<tr>
-<td width="90%"><b><font face="Arial,Helvetica" color="#ffffff"><a name="thismonth">This Month at a Glance</a></font></b></td><td align="right" width="10%"><a href="#top">top</a></td>
-</tr>
-</tbody>
-</table>
-<br>
- An overview of this month's events related to WTP.<br>
-<br>
-<center>
-<b><font size="+1">October</font></b>
-<table width="98%" border="1">
-<thead>
-<tr>
-<td align="center" width="14%"><b>Sunday</b></td><td align="center" width="14%"><b>Monday</b></td><td align="center" width="14%"><b>Tuesday</b></td><td align="center" width="14%"><b>Wednesday</b></td><td align="center" width="14%"><b>Thursday</b></td><td align="center" width="14%"><b>Friday</b></td><td align="center" width="14%"><b>Saturday</b></td>
-</tr>
-</thead>
-<tr>
-<td valign="top" width="14%"></td><td valign="top" width="14%"></td><td valign="top" width="14%"></td><td valign="top" width="14%"></td><td valign="top" width="14%"></td><td valign="top" width="14%"></td><td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">1</td>
-</tr>
-<tr>
-<td>
-<br>
-<br>
-<br>
-</td>
-</tr>
-</table>
-</td>
-</tr>
-<tr>
-<td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">2</td>
-</tr>
-<tr>
-<td>
-<br>
-<br>
-<br>
-</td>
-</tr>
-</table>
-</td><td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">3</td>
-</tr>
-<tr>
-<td>
-<br>
-<br>
-<br>
-</td>
-</tr>
-</table>
-</td><td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">4</td>
-</tr>
-<tr>
-<td>
-<br>
-<br>
-<br>
-</td>
-</tr>
-</table>
-</td><td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">5</td>
-</tr>
-<tr>
-<td>
-<br>
-<br>
-<br>
-</td>
-</tr>
-</table>
-</td><td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">6</td>
-</tr>
-<tr>
-<td>
-<br>
-<br>
-<br>
-</td>
-</tr>
-</table>
-</td><td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">7</td>
-</tr>
-<tr>
-<td>
-<br>
-<br>
-<br>
-</td>
-</tr>
-</table>
-</td><td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">8</td>
-</tr>
-<tr>
-<td>
-<br>
-<br>
-<br>
-</td>
-</tr>
-</table>
-</td>
-</tr>
-<tr>
-<td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">9</td>
-</tr>
-<tr>
-<td>
-<br>
-<br>
-<br>
-</td>
-</tr>
-</table>
-</td><td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">10</td>
-</tr>
-<tr>
-<td>
-<br>
-<br>
-<br>
-</td>
-</tr>
-</table>
-</td><td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">11</td>
-</tr>
-<tr>
-<td>
-<li>
-<font size="-2"><a href="#http://www.bea.com/beaworld/uk/index.jsp?PC=12EMWP">BEA World 2005 - London</a></font>
-</li>
-</td>
-</tr>
-</table>
-</td><td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">12</td>
-</tr>
-<tr>
-<td>
-<li>
-<font size="-2"><a href="#http://www.bea.com/beaworld/uk/index.jsp?PC=12EMWP">BEA World 2005 - London</a></font>
-</li>
-</td>
-</tr>
-</table>
-</td><td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">13</td>
-</tr>
-<tr>
-<td>
-<br>
-<br>
-<br>
-</td>
-</tr>
-</table>
-</td><td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">14</td>
-</tr>
-<tr>
-<td>
-<br>
-<br>
-<br>
-</td>
-</tr>
-</table>
-</td><td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">15</td>
-</tr>
-<tr>
-<td>
-<br>
-<br>
-<br>
-</td>
-</tr>
-</table>
-</td>
-</tr>
-<tr>
-<td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">16</td>
-</tr>
-<tr>
-<td>
-<li>
-<font size="-2"><a href="#http://www.oopsla.org/2005/ShowPage.do?id=Home">OOPSLA 2005</a></font>
-</li>
-</td>
-</tr>
-</table>
-</td><td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">17</td>
-</tr>
-<tr>
-<td>
-<li>
-<font size="-2"><a href="#http://www.oopsla.org/2005/ShowPage.do?id=Home">OOPSLA 2005</a></font>
-</li>
-<li>
-<font size="-2"><a href="#http://cas.ibm.com/cascon">CASCON 2005</a></font>
-</li>
-</td>
-</tr>
-</table>
-</td><td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">18</td>
-</tr>
-<tr>
-<td>
-<li>
-<font size="-2"><a href="#http://www.oopsla.org/2005/ShowPage.do?id=Home">OOPSLA 2005</a></font>
-</li>
-<li>
-<font size="-2"><a href="#http://cas.ibm.com/cascon">CASCON 2005</a></font>
-</li>
-<li>
-<font size="-2"><a href="#http://www.bea.com/beaworld/cz/index.jsp?PC=12EMWP">BEA World 2005 - Prague</a></font>
-</li>
-</td>
-</tr>
-</table>
-</td><td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">19</td>
-</tr>
-<tr>
-<td>
-<li>
-<font size="-2"><a href="#http://www.oopsla.org/2005/ShowPage.do?id=Home">OOPSLA 2005</a></font>
-</li>
-<li>
-<font size="-2"><a href="#http://cas.ibm.com/cascon">CASCON 2005</a></font>
-</li>
-<li>
-<font size="-2"><a href="#http://www.bea.com/beaworld/cz/index.jsp?PC=12EMWP">BEA World 2005 - Prague</a></font>
-</li>
-</td>
-</tr>
-</table>
-</td><td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">20</td>
-</tr>
-<tr>
-<td>
-<li>
-<font size="-2"><a href="#http://www.oopsla.org/2005/ShowPage.do?id=Home">OOPSLA 2005</a></font>
-</li>
-<li>
-<font size="-2"><a href="#http://cas.ibm.com/cascon">CASCON 2005</a></font>
-</li>
-</td>
-</tr>
-</table>
-</td><td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">21</td>
-</tr>
-<tr>
-<td>
-<br>
-<br>
-<br>
-</td>
-</tr>
-</table>
-</td><td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">22</td>
-</tr>
-<tr>
-<td>
-<br>
-<br>
-<br>
-</td>
-</tr>
-</table>
-</td>
-</tr>
-<tr>
-<td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">23</td>
-</tr>
-<tr>
-<td>
-<li>
-<font size="-2"><a href="#http://softwaresummit.com">Colorado Software Summit 2005</a></font>
-</li>
-</td>
-</tr>
-</table>
-</td><td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">24</td>
-</tr>
-<tr>
-<td>
-<li>
-<font size="-2"><a href="#http://softwaresummit.com">Colorado Software Summit 2005</a></font>
-</li>
-<li>
-<font size="-2"><a href="#http://cs.senecac.on.ca/sos/2005/">Free Software and Open Source Symposium</a></font>
-</li>
-</td>
-</tr>
-</table>
-</td><td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">25</td>
-</tr>
-<tr>
-<td>
-<li>
-<font size="-2"><a href="#http://softwaresummit.com">Colorado Software Summit 2005</a></font>
-</li>
-</td>
-</tr>
-</table>
-</td><td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">26</td>
-</tr>
-<tr>
-<td>
-<li>
-<font size="-2"><a href="#http://softwaresummit.com">Colorado Software Summit 2005</a></font>
-</li>
-</td>
-</tr>
-</table>
-</td><td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">27</td>
-</tr>
-<tr>
-<td>
-<li>
-<font size="-2"><a href="#http://softwaresummit.com">Colorado Software Summit 2005</a></font>
-</li>
-</td>
-</tr>
-</table>
-</td><td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">28</td>
-</tr>
-<tr>
-<td>
-<li>
-<font size="-2"><a href="#http://softwaresummit.com">Colorado Software Summit 2005</a></font>
-</li>
-</td>
-</tr>
-</table>
-</td><td valign="top" width="14%">
-<table width="100%" border="0" cellpadding="0" cellspacing="0">
-<tr>
-<td align="right">29</td>
-</tr>
-<tr>
-<td>
-<br>
-<br>
-<br>
-</td>
-</tr>
-</table>
-</td>
-</tr>
-</table>
-</center>
-<br>
-<br>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#0080c0">
-<tbody>
-<tr>
-<td width="90%"><b><font face="Arial,Helvetica" color="#ffffff"><a name="upcomingevents">Upcoming WTP Events</a></font></b></td><td align="right" width="10%"><a href="#top">top</a></td>
-</tr>
-</tbody>
-</table>
-<p>
- WTP past event information can be found on the <a href="pastevents.html">past events page</a>.
- </p>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="http://www.oopsla.org/2005/ShowPage.do?id=Home"></a><a target="_top" href="http://www.oopsla.org/2005/ShowPage.do?id=Home"><img border="0" src="images/oopsla05.jpg"></a>
-<br>Oct 16, 2005
- -
- Oct 20, 2005
- , <b><a target="_top" href="http://www.oopsla.org/2005/ShowPage.do?id=Home">OOPSLA 2005</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>Demonstrations</u>
-<ul>
-<li>
-<a target="_top" href="http://www.oopsla.org/2005/ShowEvent.do?id=624">Eclipse Web and J2EE Development</a>
-<br>
-<i>-
- <a href="../people/mandel.html">Lawrence Mandel</a></i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="http://cas.ibm.com/cascon"></a><a target="_top" href="http://cas.ibm.com/cascon"><img border="0" src="images/cascon05.gif"></a>
-<br>Oct 17, 2005
- -
- Oct 20, 2005
- , <b><a target="_top" href="http://cas.ibm.com/cascon">CASCON 2005</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>Workshops</u>
-<ul>
-<li>
-<a target="_top" href="https://www-927.ibm.com/ibm/cas/cascon/workshops/mon.shtml">Hands-On: Dive into Eclipse and the Web Tools Platform Project</a>
-<br>
-<i>-
- <a href="../people/liu.html">Jeffrey Liu</a>
- ,
- <a href="../people/belisario.html">Ella Belisario</a></i>
-</li>
-<li>
-<a target="_top" href="https://www-927.ibm.com/ibm/cas/cascon/workshops/mon.shtml">Hands-On: Using Web Services in the Web Tools Platform (WTP)</a>
-<br>
-<i>-
- <a href="../people/moogk.html">Peter Moogk</a>
- ,
- <a href="../people/kuehner.html">Rupam Kuehner</a>
- ,
- <a href="../people/phung-lu.html">Seng Phung-Lu</a></i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="http://www.bea.com/beaworld/cz/index.jsp?PC=12EMWP"></a><a target="_top" href="http://www.bea.com/beaworld/cz/index.jsp?PC=12EMWP"><img border="0" src="images/beaworld2005.gif"></a>
-<br>Oct 18, 2005
- -
- Oct 19, 2005
- , <b><a target="_top" href="http://www.bea.com/beaworld/cz/index.jsp?PC=12EMWP">BEA World 2005 - Prague</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>Presentation</u>
-<ul>
-<li>
-<a target="_top" href="http://secure.beaworld2005.com/cz/index.cfm?fuseaction=content.Agenda&day=2">Eclipse Web Tool Platform Overview</a>
-<br>
-<i>-
- <a href="../people/dai.html">Naci Dai</a></i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="http://softwaresummit.com"></a><a target="_top" href="http://softwaresummit.com"><img border="0" src="images/coloradosoftwaresummit.gif"></a>
-<br>Oct 23, 2005
- -
- Oct 28, 2005
- , <b><a target="_top" href="http://softwaresummit.com">Colorado Software Summit 2005</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>Presentation</u>
-<ul>
-<li>
-<a target="_top" href="http://softwaresummit.com/2005/speakers/ryman.htm">Developing Web Service with Eclipse</a>
-<br>
-<i>-
- <a href="../people/ryman.html">Arthur Ryman</a></i>
-</li>
-<li>
-<a target="_top" href="http://softwaresummit.com/2005/speakers/ryman.htm">What's New in WSDL 2.0</a>
-<br>
-<i>-
- <a href="../people/ryman.html">Arthur Ryman</a></i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="http://cs.senecac.on.ca/sos/2005/"></a>Oct 24, 2005
- , <b><a target="_top" href="http://cs.senecac.on.ca/sos/2005/">Free Software and Open Source Symposium</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>Presentation</u>
-<ul>
-<li>
-<a target="_top" href="http://cs.senecac.on.ca/soss/2005/presentations/lawrence-jeff.php">Teaching Web and J2EE Development with Eclipse</a>
-<br>
-<i>-
- <a href="../people/liu.html">Jeffrey Liu</a>
- ,
- <a href="../people/mandel.html">Lawrence Mandel</a></i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<p></p>
-<p>Please see our <a href="http://www.eclipse.org/legal/privacy.html">privacy
- policy</a> and website <a href="http://www.eclipse.org/legal/termsofuse.html">terms
- of use</a>. For problems with the eclipse.org site, please contact the
- <a href="mailto:webmaster@eclipse.org">webmaster</a> or read the
- <a href="../../../webmaster/index.html">webmaster FAQ</a> for answers to common questions!</p>
-</body>
-</html>
diff --git a/community/communityresources.html b/community/communityresources.html
deleted file mode 100644
index f2044da..0000000
--- a/community/communityresources.html
+++ /dev/null
@@ -1,522 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../default_style.css" type="text/css">
-<link rel="stylesheet" href="../../webtools/wtp.css" type="text/css">
-<title>wtp community resources</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">wtp community resources</font>
-<br>
-<font class="indexsub"></font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#0080c0">
-<tbody>
-<tr>
-<td width="90%"><b><font face="Arial,Helvetica" color="#ffffff"><a name="top">Resources from around the WTP community...</a></font></b></td><td align="right" width="10%"></td>
-</tr>
-</tbody>
-</table>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td with="16"> </td><td>
-<p>
- The page is about finding more information about WTP from around the WTP community.
- The community has provided many <a href="#articles">articles</a>, <a href="#books">books</a>, <a href="#tutorials">tutorials</a>, and <a href="#white papers">white papers</a>
- that are dedicated to WTP and can help you to make the most of the WTP platform and tools.
- </p>
-<p>
- WTP event information can be found on the <a href="community.html">community page</a>.
- </p>
-<p>
- WTP presentation material can be found on the <a href="presentations.html">WTP presentations archive</a>.
- </p>
-<p>
- We'd like these pages to be useful to you - so please open a
- <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Web%20Tools&component=website">bug report</a>
- for any corrections, additions, pointers, or comments!
- </p>
-<p>
- For software licensing, website terms of use, and legal FAQs, please see our
- <a target="_top" href="http://eclipse.org/legal/main.html">legal stuff</a> page.
- </p>
-</td>
-</tr>
-</table>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#0080c0">
-<tbody>
-<tr>
-<td width="90%"><b><font face="Arial,Helvetica" color="#ffffff"><a name="books">Books about WTP</a></font></b></td><td align="right" width="10%"><a href="#top">top</a></td>
-</tr>
-</tbody>
-</table>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td with="16"> </td><td>
-<p>
-<table cellpadding="2" cellspacing="5" border="0">
-<tr>
-<td valign="top" width="25%"><a target="_top" href="http://www.apress.com/book/bookDisplay.html?bID=447"><img border="0" src="images/proeclipsejst.gif"></a></td><td valign="top" width="75%">
-<p>
-<a target="_top" href="http://www.apress.com/book/bookDisplay.html?bID=447">Pro Eclipse JST: Plug-ins for J2EE Development</a>
-</p>
-<p>
- by:
- Christopher M. Judd
- ,
-
- and
- Hakeem Shittu</p>
-<p>
- Publisher:
- <a target="_top" href="http://www.apress.com/">APress</a>
-</p>
-</td>
-</tr>
-</table>
-</p>
-</td>
-</tr>
-</table>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#0080c0">
-<tbody>
-<tr>
-<td width="90%"><b><font face="Arial,Helvetica" color="#ffffff"><a name="articles">Articles about WTP</a></font></b></td><td align="right" width="10%"><a href="#top">top</a></td>
-</tr>
-</tbody>
-</table>
-<p>
-<table cellpadding="2" cellspacing="5" border="0">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td>October 2005</td><td>-</td><td><a target="_top" href="http://www.eclipse.org/articles/Article-WTP-Persisting-EMF/persisting.html">Persisting EMF models with WTP</a>
- (<a target="_top" href="http://www.eclipse.org/articles/">Eclipse Corner</a>)
-
- by
- Daniel Rohe</td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td>October 2005</td><td>-</td><td><a target="_top" href="http://www.onjava.com/pub/a/onjava/2005/10/05/eclipse-web-tools.html">Eclipse Web Tools</a>
- (<a target="_top" href="http://www.onjava.com">O'Reilly OnJava.com</a>)
-
- by
- <a href="../people/liu.html">Jeffrey Liu</a>
- ,
- <a href="../people/mandel.html">Lawrence Mandel</a></td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td>September 2005</td><td>-</td><td><a target="_top" href="http://dev2dev.bea.com/pub/a/2005/09/eclipse_web_tools_platform.html">Overview of the Eclipse Web Tools Platform</a>
- (<a target="_top" href="http://dev2dev.bea.com">dev2dev</a>)
-
- by
- <a href="../people/wagner.html">Tim Wagner</a>
- ,
- <a href="../people/bashor.html">Ted Bashor</a>
- ,
- <a href="../people/meijer.html">Paul Meijer</a>
- ,
- Pieter Humphrey</td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td>September 2005</td><td>-</td><td><a target="_top" href="http://www.ibm.com/developerworks/db2/library/techarticle/dm-0509cline/">Building Web Applications with Eclipse, WTP, and Derby</a>
- (<a target="_top" href="http://www.ibm.com/developerworks/">developerWorks</a>)
-
- by
- Susan L. Cline</td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td>August 2005</td><td>-</td><td><a target="_top" href="http://www.ddj.com/documents/s=9825/ddj0508a/0508a.html">NetBeans 4.1 & Eclipse 3.1</a>
- (<a target="_top" href="http://www.ddj.com/">Dr. Dobb's Journal</a>)
-
- by
- Eric J. Bruno</td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td>July 2005</td><td>-</td><td><a target="_top" href="http://java.sys-con.com/read/111212.htm">Web Tools Platform And J2EE Development The Eclipse Way</a>
- (<a target="_top" href="http://java.sys-con.com/">Java Developer's Journal</a>)
-
- by
- <a href="../people/ryman.html">Arthur Ryman</a></td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td>June 2005</td><td>-</td><td><a target="_top" href="http://java.sys-con.com/read/99729_1.htm">What's New in Eclipse 3.1</a>
- (<a target="_top" href="http://java.sys-con.com/">Java Developer's Journal</a>)
-
- by
- Ed Burnette</td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td>May 2005</td><td>-</td><td><a target="_top" href="http://www-128.ibm.com/developerworks/library/os-gerplug/">Create, deploy, and debug Apache Geronimo applications</a>
- (<a target="_top" href="http://www.ibm.com/developerworks/">developerWorks</a>)
-
- by
- <a href="../people/francis.html">Tim Francis</a></td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td>December 2004</td><td>-</td><td><a target="_top" href="http://www.ddj.com/documents/s=9410/ddj0412n/0412n.html">Eclipse Validators</a>
- (<a target="_top" href="http://www.ddj.com/">Dr. Dobb's Journal</a>)
-
- by
- <a href="../people/mandel.html">Lawrence Mandel</a></td>
-</tr>
-</table>
-</p>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#0080c0">
-<tbody>
-<tr>
-<td width="90%"><b><font face="Arial,Helvetica" color="#ffffff"><a name="white papers">WTP White Papers</a></font></b></td><td align="right" width="10%"><a href="#top">top</a></td>
-</tr>
-</tbody>
-</table>
-<p>
-<table cellpadding="2" cellspacing="5" border="0">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td>January 2005</td><td>-</td><td><a target="_top" href="../wst/components/rdb/Data%20Tools%20Open%20Source%20Overview%20for%20Eclipse%20database%20Developer.html">Data Tools Open Source Overview for Eclipse Database Developer</a></td>
-</tr>
-</table>
-</p>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#0080c0">
-<tbody>
-<tr>
-<td width="90%"><b><font face="Arial,Helvetica" color="#ffffff"><a name="tutorials">WTP Tutorials</a></font></b></td><td align="right" width="10%"><a href="#top">top</a></td>
-</tr>
-</tbody>
-</table>
-<overview>
- Trying out the latest WTP development driver and looking for milestone
- specific tutorials? Try the <a href="milestonespecificresources.html">
- milestone specific community resources page</a>.
- </overview>
-<p></p>
-<a href="#general">General</a>
- |
- <a href="#rdb">Data Tools</a>
- |
- <a href="#j2ee">J2EE</a>
- |
- <a href="#server">Server/Internet</a>
- |
- <a href="#sse">Structured Source Editing (SSE)</a>
- |
- <a href="#ws">Web Services</a>
- |
- <a href="#xml">XML</a>
-<p>
-<a name="general"></a>
-<table cellpadding="2" cellspacing="5" border="0">
-<tr>
-<td colspan="2"><b>General Tutorials</b></td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="tutorials/DevelopingWTP/DevelopingWTP.html">Developing the WTP with Eclipse</a></b></td>
-</tr>
-<tr>
-<td></td><td>
- This tutorial shows you how to set up your Eclipse environment to develop or modify the
- Web Tools Platform (WTP) project plug-ins. First we will discuss how to connect to the
- CVS repository to check out the WTP source code. We will then set up our target platform.
- Next we will make a modification to the WTP source and run our eclipse application.
- Finally, we will create a patch for our change, which we could submit to the WTP project.
- </td>
-</tr>
-</table>
-</p>
-<hr>
-<p>
-<a name="rdb"></a>
-<table cellpadding="2" cellspacing="5" border="0">
-<tr>
-<td colspan="2"><b>Data Tools Tutorials</b></td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="tutorials/RDBTutorial/RDBTutorial.html">RDB Tutorial</a></b></td>
-</tr>
-<tr>
-<td></td><td>
- This document walks you through the relational database (RDB) open source features in the
- Eclipse Web Tooling Project. You must have either the RDB open source binaries or the source
- code downloaded from the Eclipse Web site.
- </td>
-</tr>
-</table>
-</p>
-<hr>
-<p>
-<a name="j2ee"></a>
-<table cellpadding="2" cellspacing="5" border="0">
-<tr>
-<td colspan="2"><b>J2EE Tutorials</b></td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="tutorials/cmptutorial/CMPScheduleWebApp.html">Building a CMP Based School Schedule Web Application</a></b></td>
-</tr>
-<tr>
-<td></td><td>
- This tutorial is similar to the Building a School Schedule Web Application except
- EJBs are used. This tutorial walks the user through developing a Container Managed Entity Bean (CMP)
- to store a simple schedule. A Session Bean is used to query the CMP. Finally, a Servlet and JSP are
- built to serve as the front end.
- </td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="tutorials/BuildJ2EEWebApp/BuildJ2EEWebApp.html">Building and Running a Web Application</a></b></td>
-</tr>
-<tr>
-<td></td><td>
- This document is the first in a series of tutorials where we will demonstrate how you can
- use the rich set of tools and APIs that comes with the Web Tools Platform Project. This
- first tutorial will give you a step by step tour of using some the tools for web
- development. For this purpose we will build and run a J2EE web application using WTP tools
- and Apache Tomcat.
- </td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="tutorials/SchoolSchedule/BuildingAScheduleWebApp.html">Building a School Schedule Web Application</a></b></td>
-</tr>
-<tr>
-<td></td><td>
- In this tutorial you will create a school schedule Web application. This application
- will allow students to input their courses and create a schedule. This tutorial will
- introduce you to JSP's, servlets and the Web Tools Platform project's server tools.
- </td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="tutorials/ejbtutorial/buildingejbs.html">Building a Simple EJB Application</a></b></td>
-</tr>
-<tr>
-<td></td><td>
- In this tutorial you will create a simple EJB component and a client web application.
- This tutorial will introduce you to Session beans and the Web Tools Platform project's
- support for XDoclet and server tools.
- </td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="tutorials/CactusInWTP/CactusInWTP.html">Cactus Integration in the Web Tools Project</a></b></td>
-</tr>
-<tr>
-<td></td><td>
- This article briefly explains Cactus, its common uses and advantages and then provides a
- step-by-step tutorial on how to use the Cactus integration provided by WTP. The article
- assumes that you are familiar with JUnit and the basics of using WTP to build, deploy and
- run web projects.
- </td>
-</tr>
-</table>
-</p>
-<hr>
-<p>
-<a name="server"></a>
-<table cellpadding="2" cellspacing="5" border="0">
-<tr>
-<td colspan="2"><b>Server/Internet Tutorials</b></td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="tutorials/cmptutorial/CMPScheduleWebApp.html">Building a CMP Based School Schedule Web Application</a></b></td>
-</tr>
-<tr>
-<td></td><td>
- This tutorial is similar to the Building a School Schedule Web Application except
- EJBs are used. This tutorial walks the user through developing a Container Managed Entity Bean (CMP)
- to store a simple schedule. A Session Bean is used to query the CMP. Finally, a Servlet and JSP are
- built to serve as the front end.
- </td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="tutorials/BuildJ2EEWebApp/BuildJ2EEWebApp.html">Building and Running a Web Application</a></b></td>
-</tr>
-<tr>
-<td></td><td>
- This document is the first in a series of tutorials where we will demonstrate how you can
- use the rich set of tools and APIs that comes with the Web Tools Platform Project. This
- first tutorial will give you a step by step tour of using some the tools for web
- development. For this purpose we will build and run a J2EE web application using WTP tools
- and Apache Tomcat.
- </td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="tutorials/SchoolSchedule/BuildingAScheduleWebApp.html">Building a School Schedule Web Application</a></b></td>
-</tr>
-<tr>
-<td></td><td>
- In this tutorial you will create a school schedule Web application. This application
- will allow students to input their courses and create a schedule. This tutorial will
- introduce you to JSP's, servlets and the Web Tools Platform project's server tools.
- </td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="tutorials/ejbtutorial/buildingejbs.html">Building a Simple EJB Application</a></b></td>
-</tr>
-<tr>
-<td></td><td>
- In this tutorial you will create a simple EJB component and a client web application.
- This tutorial will introduce you to Session beans and the Web Tools Platform project's
- support for XDoclet and server tools.
- </td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="tutorials/ServerDefinitionExplained/ServerDefinitionExplained.html">Generic Server - Server Definition File Explained</a></b></td>
-</tr>
-<tr>
-<td></td><td>
- Generic server is a special server and runtime implementation of base server tooling that can
- adjust its behaviour by a server type definition file. Server type definition files are XML
- based meta information files that are introduced using
- "org.eclipse.jst.server.generic.core.serverdefinition" extension point. This document describes
- the different parts of the server definition files.
- </td>
-</tr>
-</table>
-</p>
-<hr>
-<p>
-<a name="sse"></a>
-<table cellpadding="2" cellspacing="5" border="0">
-<tr>
-<td colspan="2"><b>Structured Source Editing (SSE) Tutorials</b></td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="tutorials/ReintroducingSSE/ReintroducingSSE.html">Reintroducing the Structured Source Editing Family of Editors</a></b></td>
-</tr>
-<tr>
-<td></td><td>
- The Structured Source Editing (SSE) family of editors are now available as part of WTP
- 1.0M2. They support editing XML, DTD, HTML, CSS, JavaScript, and JSP files. The SSE
- editors make significant usage of Eclipse frameworks as well as each other. For end users
- it means that they behave consistently with each other as well as with other Eclipse editors.
- </td>
-</tr>
-</table>
-</p>
-<hr>
-<p>
-<a name="ws"></a>
-<table cellpadding="2" cellspacing="5" border="0">
-<tr>
-<td colspan="2"><b>Web Services Tutorials</b></td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="tutorials/BottomUpWebService/BottomUpWebService.html">Creating a Bottom-Up Java Web Service</a></b></td>
-</tr>
-<tr>
-<td></td><td>
- This document is one of a series of tutorials to demonstrate the use of the Web Services tools
- in the Web Tools Platform Project using the WTP 0.7 drivers. This tutorial shows how to create
- a simple Web service and Web service client from a Java class. The Java class in this scenario
- converts between the Celsius and Farenheit temperature scales.
- </td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="tutorials/WebServiceClient/WebServiceClient.html">Creating a Java Web Service Client</a></b></td>
-</tr>
-<tr>
-<td></td><td>
- This document is one of a series of tutorials to demonstrate the use of the Web Services tools
- in the Web Tools Platform Project with the WTP 0.7 drivers. This tutorial shows how to create a
- Web serivce client to the deployed Web service created in the tutorial
- <a xmlns="http://www.eclipse.org/webtools/tutorials" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" href="tutorials/TopDownWebService/TopDownWebService.html">Creating a Top-Down Java
- Web Service Skeleton from a WSDL Document</a>.
- </td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="tutorials/TopDownWebService/TopDownWebService.html">Creating a Top-Down Java Web Service Skeleton from a WSDL Document</a></b></td>
-</tr>
-<tr>
-<td></td><td>
- This document is one of a series of tutorials to demonstrate the use of the Web Services tools
- in the Web Tools Platform Project using the WTP 0.7 drivers. This tutorial shows how to create
- a simple top-down Web service from a WSDL file. The WSDL file in this scenario calculates the
- area of an rectangle.
- </td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="tutorials/WebServiceExplorer/WebServiceExplorer.html">Testing a Web Service with the Web Services Explorer</a></b></td>
-</tr>
-<tr>
-<td></td><td>
- This document is one of a series of tutorials to demonstrate the use of the Web Services tools
- in the Web Tools Platform Project using the WTP 0.7 drivers. This tutorial shows how to use the
- Web Service Explorer to test a Web service via native WSDL and SOAP. It demonstrates how to use
- the Web Services Explorer to invoke operations on a Web service named " Temperature - Weather "
- as available from XMethods on the internet.
- </td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="tutorials/WSDLEditor/WSDLEditorTutorial.html">WSDL Editor Tutorial</a></b></td>
-</tr>
-<tr>
-<td></td><td>
- In this tutorial we look at using the WSDL Editor to create and modify a WSDL file. We explore
- the basic functionality along with some of the more advanced ones.
- </td>
-</tr>
-</table>
-</p>
-<hr>
-<p>
-<a name="xml"></a>
-<table cellpadding="2" cellspacing="5" border="0">
-<tr>
-<td colspan="2"><b>XML Tutorials</b></td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="tutorials/XMLWizards/XMLWizards.html">Creating XML files Tutorial</a></b></td>
-</tr>
-<tr>
-<td></td><td>
- This tutorial demonstrates how you can use XML documents creation wizards that come with
- the Eclipse Web Tools Platform Project. These wizards allow to create XML document from
- DTD or XML Schema.
- </td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="tutorials/WSDLEditor/WSDLEditorTutorial.html">WSDL Editor Tutorial</a></b></td>
-</tr>
-<tr>
-<td></td><td>
- In this tutorial we look at using the WSDL Editor to create and modify a WSDL file. We explore
- the basic functionality along with some of the more advanced ones.
- </td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="tutorials/XMLCatalog/XMLCatalogTutorial.html">XML Catalog Tutorial</a></b></td>
-</tr>
-<tr>
-<td></td><td>
- In this tutorial, we will demonstrate the use of the XML Catalog. Add the Example
- “Editing and validating XML files”. Select File -> New -> Other -> Examples -> Editing and
- Validating XML files.
- </td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="tutorials/XMLSchemaEditor/XMLSchemaEditorTutorial.html">XML Schema Editor Tutorial</a></b></td>
-</tr>
-<tr>
-<td></td><td>
- This tutorial will use the catalog.xsd from the "Editing and validating XML files" Examples.
- </td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="tutorials/XMLValidation/XMLValidationTutorial.html">XML Validation Tutorial</a></b></td>
-</tr>
-<tr>
-<td></td><td>
- Eclipse WTP includes validation tools for XML, DTD, and XML Schema. Validation can be invoked
- manually or automatically after every save.
- </td>
-</tr>
-</table>
-</p>
-<hr>
-<p></p>
-<p>Please see our <a href="http://www.eclipse.org/legal/privacy.html">privacy
- policy</a> and website <a href="http://www.eclipse.org/legal/termsofuse.html">terms
- of use</a>. For problems with the eclipse.org site, please contact the
- <a href="mailto:webmaster@eclipse.org">webmaster</a> or read the
- <a href="../../../webmaster/index.html">webmaster FAQ</a> for answers to common questions!</p>
-</body>
-</html>
diff --git a/community/communityresources.xml b/community/communityresources.xml
deleted file mode 100644
index 6719360..0000000
--- a/community/communityresources.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<resources title="wtp community resources">
- <resource title="Books about WTP" shortTitle="books" src="books.xml"/>
- <resource title="Articles about WTP" shortTitle="articles" src="articles.xml"/>
- <resource title="WTP White Papers" shortTitle="white papers" src="whitepapers.xml"/>
- <resource title="WTP Tutorials" shortTitle="tutorials" src="tutorials.xml">
- <overview>
- Trying out the latest WTP development driver and looking for milestone
- specific tutorials? Try the <a href="milestonespecificresources.html">
- milestone specific community resources page</a>.
- </overview>
- </resource>
-</resources>
diff --git a/community/events.xml b/community/events.xml
deleted file mode 100644
index 1662eb4..0000000
--- a/community/events.xml
+++ /dev/null
@@ -1,378 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<events xmlns="http://www.eclipse.org/webtools/events"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://www.eclipse.org/webtools/events schemas/events.xsd ">
- <event startdate="2005-10-23" enddate="2005-10-28"
- organization="Colorado Software Summit 2005"
- link="http://softwaresummit.com"
- logo="images/coloradosoftwaresummit.gif">
- <presentation type="Presentation"
- link="http://softwaresummit.com/2005/speakers/ryman.htm"
- title="Developing Web Service with Eclipse">
- <presenter name="Arthur Ryman"/>
- </presentation>
- <presentation type="Presentation"
- link="http://softwaresummit.com/2005/speakers/ryman.htm"
- title="What's New in WSDL 2.0">
- <presenter name="Arthur Ryman"/>
- </presentation>
- </event>
- <event startdate="2005-08-29" enddate="2005-08-31"
- organization="EclipseWorld 2005" link="http://www.eclipseworld.net"
- logo="images/EclipseWorld-129.gif">
- <presentation type="Technical Classes"
- title="Creating Your First J2EE Web Application With Eclipse in 90 Minutes"
- link="http://www.bzmedia.com/eclipseworld/tuesday.htm">
- <presenter name="Lawrence Mandel"/>
- <presenter name="Jason Sholl"/>
- </presentation>
- <presentation type="Technical Classes"
- title="Consuming and Producing Web Services With WST and JST"
- link="http://www.bzmedia.com/eclipseworld/tuesday.htm">
- <presenter name="Christopher M. Judd"/>
- </presentation>
- <presentation type="Technical Classes"
- title="Interacting With Relational Databases"
- link="http://www.bzmedia.com/eclipseworld/tuesday.htm">
- <presenter name="Christopher M. Judd"/>
- </presentation>
- <presentation type="Technical Classes"
- title="Developing Web Services With Eclipse"
- link="http://www.bzmedia.com/eclipseworld/tuesday.htm">
- <presenter name="Arthur Ryman"/>
- </presentation>
- <presentation type="Technical Classes"
- title="Java Annotations in Eclipse: Enhancing the JDT Experience"
- link="http://www.bzmedia.com/eclipseworld/tuesday.htm">
- <presenter name="Tim Wagner"/>
- </presentation>
- <presentation type="Technical Classes"
- title="XML Editing With Eclipse"
- link="http://www.bzmedia.com/eclipseworld/tuesday.htm">
- <presenter name="Elliotte Rusty Harold"/>
- </presentation>
- <presentation type="Technical Classes"
- title="Developing Web Services With the Web Tools Platform"
- link="http://www.bzmedia.com/eclipseworld/tuesday.htm">
- <presenter name="David Gallardo"/>
- </presentation>
- <presentation type="Technical Classes"
- title="Developing Enterprise JavaBeans With J2EE Standard Tools"
- link="http://www.bzmedia.com/eclipseworld/wednesday.htm">
- <presenter name="Christopher M. Judd"/>
- </presentation>
- <presentation type="Technical Classes"
- title="Web Application Development With Web Tools Platform, Part I"
- link="http://www.bzmedia.com/eclipseworld/wednesday.htm">
- <presenter name="Tim Wagner"/>
- </presentation>
- <presentation type="Technical Classes"
- title="Web Application Development With Web Tools Platform, Part II: Advanced Topics and Extension Points"
- link="http://www.bzmedia.com/eclipseworld/wednesday.htm">
- <presenter name="Tim Wagner"/>
- </presentation>
- <presentation type="Technical Classes"
- title="Building With the Data Tools Project"
- link="http://www.bzmedia.com/eclipseworld/wednesday.htm">
- <presenter name="John Graham"/>
- <presenter name="Der-Ping Chou"/>
- </presentation>
- <presentation type="Tutorial"
- title="Developing J2EE Applications With the Web Tools Platform Project"
- link="http://www.bzmedia.com/eclipseworld/monday.htm">
- <presenter name="Christopher M. Judd"/>
- </presentation>
- </event>
- <event startdate="2005-05-30" enddate="2005-06-01"
- organization="Holland Open Software Conference 2005"
- link="http://www.hollandopen.nl/"
- logo="images/hollandopen.gif">
- <presentation type="Presentation"
- link="http://www.hollandopen.nl/index.jsp?nr=1704"
- title="Eclipse and the Web Tools Platform">
- <presenter name="Naci Dai"/>
- </presentation>
- </event>
- <event startdate="2005-05-22" enddate="2005-05-26"
- organization="IBM Rational Software Development Conference 2005"
- link="https://www.conferonreg.com/RationalSpeaker2005/Agenda/agenda_main_page.cfm"
- logo="images/rsdc05.gif">
- <presentation type="Presentation"
- link="https://www.conferonreg.com/RationalSpeaker2005/Agenda/agenda_by_track.cfm?track=SDP&#SDP28"
- title="Introduction to the Eclipse Web Tools Platform Project">
- <presenter name="Craig Salter"/>
- <presenter name="Keith Chong"/>
- </presentation>
- </event>
- <event startdate="2005-05-12" enddate="2005-05-12"
- organization="Le club des utilisateurs java"
- link="http://www.club-java.com/"
- logo="images/LogoPetit.gif">
- <presentation type="Presentation"
- link="http://enews.naos.com/servlets/com.naos.enews.HtmlFileFilter?id=183555096&filter=true"
- title="ObjectWeb and Eclipse - the WTP project and beyond">
- <presenter name="Christophe Ney"/>
- </presentation>
- </event>
- <event startdate="2005-05-09" enddate="2005-05-13"
- organization="JAX 2005" link="http://www.jax.de"
- logo="images/jax05-logo.jpg">
- <presentation type="Presentation"
- link="http://www.jax.de/konferenzen/psecom,id,277,nodeid,,.html#EC1"
- title="Eclipse: What's new in 3.1">
- <presenter name="Erich Gamma" />
- <presenter name="Jochen Krause"/>
- </presentation>
- <presentation type="Presentation"
- link="http://www.jax.de/konferenzen/psecom,id,277,nodeid,,.html#EC12"
- title="Extending the SSE">
- <presenter name="Jens Lukowski"/>
- </presentation>
- </event>
-
- <event startdate="2005-02-15" enddate="2005-02-17"
- organization="Web Service Edge 2005 East"
- link="http://www.sys-con.com/edge2005east/index.cfm">
- <presentation type="Case Study"
- link="http://www.sys-con.com/story/?storyid=47527"
- title="Developing Web Services with Eclipse">
- <presenter name="Arthur Ryman"/>
- </presentation>
- </event>
-
- <event startdate="2005-02-23" enddate="2005-02-23"
- organization="École de technologie supérieure"
- link="http://www.etsmtl.ca/"
- logo="images/ecoledetechnologie.gif">
- <presentation type="Presentation"
- link="http://www.etsmtl.ca/zone2/departements/logti/evenements/conference5.pdf"
- title="Formal Specification at W3C">
- <presenter name="Arthur Ryman"/>
- </presentation>
- </event>
-
- <event startdate="2005-02-28" enddate="2005-03-03"
- organization="EclipseCon"
- link="http://www.eclipsecon.org/?ID=EclipseWTP"
- logo="images/eclipsecon.gif">
- <presentation type="Technical Sessions"
- link="http://www.eclipsecon.org/sessions.php"
- title="Extend web tools server tooling for your application server">
- <presenter name="Gorkem Ercan"/>
- <presenter name="Tim deBoer"/>
- </presentation>
- <presentation type="Technical Sessions"
- link="http://www.eclipsecon.org/sessions.php"
- title="Eclipse Web Tools Platform Project Overview">
- <presenter name="Naci Dai"/>
- <presenter name="Arthur Ryman"/>
- </presentation>
- <presentation type="Technical Sessions"
- link="http://www.eclipsecon.org/sessions.php"
- title="Web Services Dev. with Eclipse Web Tools Platform Project">
- <presenter name="Jeffrey Liu"/>
- <presenter name="Lawrence Mandel"/>
- </presentation>
- <presentation type="Tutorials"
- link="http://www.eclipsecon.org/tutorials.php"
- title="Introduction to the Web Tools Platform">
- <presenter name="Chuck Bridgham"/>
- <presenter name="Lawrence Mandel"/>
- </presentation>
- </event>
-
- <event startdate="2005-03-01" enddate="2005-03-01"
- organization="SDForum" link="http://www.sdforum.org/"
- logo="images/sdforum.jpg">
- <presentation type="Presentation" time="6:30pm"
- link="http://www.sdforum.org/SDForum/Templates/Level1.aspx?pid=10108&sid=7"
- title="Eclipse Web Tools Platform Project Overview">
- <presenter name="Tim deBoer"/>
- </presentation>
- </event>
-
- <event startdate="2005-01-25" enddate="2005-01-25"
- organization="Portland Java User's Group" link="http://www.pjug.org/"
- logo="images/pjug.gif">
- <presentation type="Presentation" title="Eclipse Web Tools" time="6:30pm">
- <presenter name="Sean C. Sullivan" />
- </presentation>
- </event>
-
- <event startdate="2005-01-20" enddate="2005-01-22"
- organization="CUTC 2005 : Canadian Undergraduate Technology Conference"
- link="http://www.cutc.ca"
- logo="images/cutc2005.gif">
- <presentation type="TechShop"
- title="Dive into Eclipse and the Web Tools Platform Project">
- <presenter name="Jeffrey Liu"/>
- <presenter name="Lawrence Mandel"/>
- <material type="Tutorial"
- name="Building a School Schedule Web Application"
- link="http://www.eclipse.org/webtools/testtutorials/M2/webapptutorial/BuildingAScheduleWebApp.html" />
- </presentation>
- </event>
- <event startdate="2005-01-19" enddate="2005-01-21"
- organization="ObjectWebCon'05"
- link="http://www.objectweb.org/ObjectWebCon05"
- logo="images/objectwebcon.jpg">
- <presentation type="Speaker Sessions"
- title="Eclipse Web Tools Platform Project Overview">
- <presenter name="Naci Dai"/>
- </presentation>
- <presentation type="Speaker Sessions"
- title="Eclipse Web Tools - Extending the Structured Source Editor">
- <presenter name="Jochen Krause"/>
- </presentation>
- </event>
-
- <event startdate="2005-04-07" enddate="2005-04-07"
- organization="Web Services & SOA China 2005"
- link="http://www.webserviceschina.com/"
- logo="images/wssoachina2005.gif">
- <presentation type="Presentation"
- title="Developing Web Services with Eclipse">
- <presenter name="Arthur Ryman"/>
- </presentation>
- </event>
- <event startdate="2005-06-02" enddate="2005-06-02"
- organization="WTP Open House"
- link="../development/arch_and_design/arch_page.html">
- <presentation type="Presentation"
- title="Common Components">
- <presenter name="Craig Salter"/>
- <material name="Presentation" type="PowerPoint" link="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/06-02-wtp-open-house/common-tools-06-02-1530-highlighted2.ppt"/>
- </presentation>
- </event>
- <event startdate="2005-06-09" enddate="2005-06-09"
- organization="WTP Open House"
- link="../development/arch_and_design/arch_page.html">
- <presentation type="Presentation"
- title="WTP Editors (XML, JSP, etc)">
- <presenter name="David Williams"/>
- <material name="Presentation" type="PowerPoint" link="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/06-09-wtp-open-house/sse-openhouse-6-9.ppt"/>
- </presentation>
- </event>
- <event startdate="2005-06-16" enddate="2005-06-16"
- organization="WTP Open House"
- link="../development/arch_and_design/arch_page.html">
- <presentation type="Presentation"
- title="J2EE">
- <presenter name="Chuck Bridgham"/>
- <material name="Presentations" type="PowerPoint" link="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/06-16-wtp-open-house/j2ee-tools-06-16.ppt"/>
- </presentation>
- </event>
- <event startdate="2005-05-19" enddate="2005-05-19"
- organization="WTP Open House"
- link="../development/arch_and_design/arch_page.html">
- <presentation type="Presentations"
- title="Server and Database Components">
- <presenter name="Tim deBoer"/>
- <presenter name="Der-Ping Chou"/>
- <material name="Server Presentation" type="PowerPoint" link="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/05-19-wtp-open-house/server-tools.ppt"/>
- <material name="Database Presentation" type="PowerPoint" link="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/05-19-wtp-open-house/data-tools.ppt"/>
- </presentation>
- </event>
- <event startdate="2005-05-26" enddate="2005-05-26"
- organization="WTP Open House"
- link="../development/arch_and_design/arch_page.html">
- <presentation type="Presentations"
- title="Web Services">
- <presenter name="Chris Brealey"/>
- <material name="Presentations" type="PowerPoint" link="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/05-26-wtp-open-house/web-service-tools.ppt"/>
- </presentation>
- </event>
- <event startdate="2005-06-27" enddate="2005-06-30"
- organization="JavaOne 2005"
- link="http://java.sun.com/javaone/sf/index.jsp">
- <presentation type="Presentations"
- title="What's New in Eclipse? A Java™ Technology IDE and a Whole Lot More"
- link="https://www28.cplan.com/javaone05_93_1/session_details.jsp?isid=271654&ilocation_id=93-1&ilanguage=english">
- <presenter name="Mike Milinkovich"/>
- <presenter name="Bjorn Freeman-Benson"/>
- </presentation>
- <presentation type="Presentations"
- title="Introduction to the Web Tools Platform Project"
- link="https://www28.cplan.com/javaone05_93_1/session_details.jsp?isid=271909&ilocation_id=93-1&ilanguage=english">
- <presenter name="Tim Wagner"/>
- </presentation>
- </event>
- <event startdate="2005-10-16" enddate="2005-10-20"
- organization="OOPSLA 2005"
- link="http://www.oopsla.org/2005/ShowPage.do?id=Home"
- logo="images/oopsla05.jpg">
- <presentation type="Demonstrations"
- title="Eclipse Web and J2EE Development"
- link="http://www.oopsla.org/2005/ShowEvent.do?id=624">
- <presenter name="Lawrence Mandel"/>
- </presentation>
- </event>
- <event startdate="2005-10-17" enddate="2005-10-20"
- organization="CASCON 2005"
- link="http://cas.ibm.com/cascon"
- logo="images/cascon05.gif">
- <presentation type="Workshops"
- title="Hands-On: Dive into Eclipse and the Web Tools Platform Project"
- link="https://www-927.ibm.com/ibm/cas/cascon/workshops/mon.shtml">
- <presenter name="Jeffrey Liu"/>
- <presenter name="Ella Belisario"/>
- </presentation>
- <presentation type="Workshops"
- title="Hands-On: Using Web Services in the Web Tools Platform (WTP)"
- link="https://www-927.ibm.com/ibm/cas/cascon/workshops/mon.shtml">
- <presenter name="Peter Moogk"/>
- <presenter name="Rupam Kuehner"/>
- <presenter name="Seng Phung-Lu"/>
- </presentation>
- </event>
- <event startdate="2005-09-19" enddate="2005-09-19"
- organization="Java Teknolojileri Derneği"
- link="http://java.org.tr/"
- logo="images/javateknolojileridernegi.gif">
- <presentation type="Presentation"
- title="Eclipse Web Tools Platform Projesi (Turkish)"
- link="http://java.org.tr/seminer.jsp?k=15">
- <presenter name="Gorkem Ercan"/>
- </presentation>
- </event>
- <event startdate="2005-09-28" enddate="2005-09-28"
- organization="Java Teknolojileri Derneği"
- link="http://java.org.tr/"
- logo="images/javateknolojileridernegi.gif">
- <presentation type="Presentation"
- title="Eclipse için plug-in geliştirmek (Turkish)"
- link="http://java.org.tr/seminer.jsp?k=16">
- <presenter name="Gorkem Ercan"/>
- </presentation>
- </event>
- <event startdate="2005-10-24" enddate="2005-10-24"
- organization="Free Software and Open Source Symposium"
- link="http://cs.senecac.on.ca/sos/2005/">
- <presentation type="Presentation"
- title="Teaching Web and J2EE Development with Eclipse"
- link="http://cs.senecac.on.ca/soss/2005/presentations/lawrence-jeff.php">
- <presenter name="Jeffrey Liu"/>
- <presenter name="Lawrence Mandel"/>
- </presentation>
- </event>
- <event startdate="2005-10-11" enddate="2005-10-12"
- organization="BEA World 2005 - London"
- link="http://www.bea.com/beaworld/uk/index.jsp?PC=12EMWP"
- logo="images/beaworld2005.gif">
- <presentation type="Presentation"
- title="Eclipse Web Tool Platform Overview"
- link="http://secure.beaworld2005.com/uk/index.cfm?fuseaction=content.Agenda&day=2">
- <presenter name="Naci Dai"/>
- </presentation>
- </event>
- <event startdate="2005-10-18" enddate="2005-10-19"
- organization="BEA World 2005 - Prague"
- link="http://www.bea.com/beaworld/cz/index.jsp?PC=12EMWP"
- logo="images/beaworld2005.gif">
- <presentation type="Presentation"
- title="Eclipse Web Tool Platform Overview"
- link="http://secure.beaworld2005.com/cz/index.cfm?fuseaction=content.Agenda&day=2">
- <presenter name="Naci Dai"/>
- </presentation>
- </event>
-</events>
diff --git a/community/images/EclipseWorld-129.gif b/community/images/EclipseWorld-129.gif
deleted file mode 100644
index 737c173..0000000
--- a/community/images/EclipseWorld-129.gif
+++ /dev/null
Binary files differ
diff --git a/community/images/LogoPetit.gif b/community/images/LogoPetit.gif
deleted file mode 100644
index 2cf228a..0000000
--- a/community/images/LogoPetit.gif
+++ /dev/null
Binary files differ
diff --git a/community/images/bea_logo.gif b/community/images/bea_logo.gif
deleted file mode 100644
index 54af953..0000000
--- a/community/images/bea_logo.gif
+++ /dev/null
Binary files differ
diff --git a/community/images/beaworld2005.gif b/community/images/beaworld2005.gif
deleted file mode 100644
index 7a81b6c..0000000
--- a/community/images/beaworld2005.gif
+++ /dev/null
Binary files differ
diff --git a/community/images/cascon05.gif b/community/images/cascon05.gif
deleted file mode 100644
index 58d143a..0000000
--- a/community/images/cascon05.gif
+++ /dev/null
Binary files differ
diff --git a/community/images/coloradosoftwaresummit.gif b/community/images/coloradosoftwaresummit.gif
deleted file mode 100644
index c7ed1b3..0000000
--- a/community/images/coloradosoftwaresummit.gif
+++ /dev/null
Binary files differ
diff --git a/community/images/cutc2005.gif b/community/images/cutc2005.gif
deleted file mode 100644
index 5f651ae..0000000
--- a/community/images/cutc2005.gif
+++ /dev/null
Binary files differ
diff --git a/community/images/eclipsecon.gif b/community/images/eclipsecon.gif
deleted file mode 100644
index cfc4688..0000000
--- a/community/images/eclipsecon.gif
+++ /dev/null
Binary files differ
diff --git a/community/images/ecoledetechnologie.gif b/community/images/ecoledetechnologie.gif
deleted file mode 100644
index 759b8b2..0000000
--- a/community/images/ecoledetechnologie.gif
+++ /dev/null
Binary files differ
diff --git a/community/images/geronimo-logo.png b/community/images/geronimo-logo.png
deleted file mode 100644
index 5d2ae66..0000000
--- a/community/images/geronimo-logo.png
+++ /dev/null
Binary files differ
diff --git a/community/images/hollandopen.gif b/community/images/hollandopen.gif
deleted file mode 100644
index 1fa049c..0000000
--- a/community/images/hollandopen.gif
+++ /dev/null
Binary files differ
diff --git a/community/images/javateknolojileridernegi.gif b/community/images/javateknolojileridernegi.gif
deleted file mode 100644
index 74769fa..0000000
--- a/community/images/javateknolojileridernegi.gif
+++ /dev/null
Binary files differ
diff --git a/community/images/jax05-logo.jpg b/community/images/jax05-logo.jpg
deleted file mode 100644
index 105818f..0000000
--- a/community/images/jax05-logo.jpg
+++ /dev/null
Binary files differ
diff --git a/community/images/objectwebcon.jpg b/community/images/objectwebcon.jpg
deleted file mode 100644
index fe717b8..0000000
--- a/community/images/objectwebcon.jpg
+++ /dev/null
Binary files differ
diff --git a/community/images/oopsla05.jpg b/community/images/oopsla05.jpg
deleted file mode 100644
index 1932c72..0000000
--- a/community/images/oopsla05.jpg
+++ /dev/null
Binary files differ
diff --git a/community/images/pjug.gif b/community/images/pjug.gif
deleted file mode 100644
index ebacd3d..0000000
--- a/community/images/pjug.gif
+++ /dev/null
Binary files differ
diff --git a/community/images/proeclipsejst.gif b/community/images/proeclipsejst.gif
deleted file mode 100644
index 99e7bf4..0000000
--- a/community/images/proeclipsejst.gif
+++ /dev/null
Binary files differ
diff --git a/community/images/rsdc05.gif b/community/images/rsdc05.gif
deleted file mode 100644
index a1ca0aa..0000000
--- a/community/images/rsdc05.gif
+++ /dev/null
Binary files differ
diff --git a/community/images/sdforum.jpg b/community/images/sdforum.jpg
deleted file mode 100644
index 4e821f7..0000000
--- a/community/images/sdforum.jpg
+++ /dev/null
Binary files differ
diff --git a/community/images/wssoachina2005.gif b/community/images/wssoachina2005.gif
deleted file mode 100644
index cee8874..0000000
--- a/community/images/wssoachina2005.gif
+++ /dev/null
Binary files differ
diff --git a/community/milestonespecificresources.html b/community/milestonespecificresources.html
deleted file mode 100644
index d256271..0000000
--- a/community/milestonespecificresources.html
+++ /dev/null
@@ -1,145 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../default_style.css" type="text/css">
-<link rel="stylesheet" href="../../webtools/wtp.css" type="text/css">
-<title>wtp milestone specific community resources</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">wtp milestone specific community resources</font>
-<br>
-<font class="indexsub"></font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#0080c0">
-<tbody>
-<tr>
-<td width="90%"><b><font face="Arial,Helvetica" color="#ffffff"><a name="top">Resources from around the WTP community...</a></font></b></td><td align="right" width="10%"></td>
-</tr>
-</tbody>
-</table>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td with="16"> </td><td>
-<overview>
-
-<p>
-
-<b>
- This page contains milestone specific community resources. WTP
- makes no gaurantee that these resources will continue to be
- available.
- </b>
-
-</p>
-
-<p>
-
-<b>
- WTP community resources for the latest WTP release can be found
- <a href="communityresources.html">here</a>.
- </b>
-
-</p>
-
-</overview>
-<p>
- The page is about finding more information about WTP from around the WTP community.
- The community has provided many and <a href="#tutorials">tutorials</a>
- that are dedicated to WTP and can help you to make the most of the WTP platform and tools.
- </p>
-<p>
- WTP event information can be found on the <a href="community.html">community page</a>.
- </p>
-<p>
- WTP presentation material can be found on the <a href="presentations.html">WTP presentations archive</a>.
- </p>
-<p>
- We'd like these pages to be useful to you - so please open a
- <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Web%20Tools&component=website">bug report</a>
- for any corrections, additions, pointers, or comments!
- </p>
-<p>
- For software licensing, website terms of use, and legal FAQs, please see our
- <a target="_top" href="http://eclipse.org/legal/main.html">legal stuff</a> page.
- </p>
-</td>
-</tr>
-</table>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#0080c0">
-<tbody>
-<tr>
-<td width="90%"><b><font face="Arial,Helvetica" color="#ffffff"><a name="tutorials">WTP Tutorials</a></font></b></td><td align="right" width="10%"><a href="#top">top</a></td>
-</tr>
-</tbody>
-</table>
-<p></p>
-<a href="#ws">Web Services</a>
-<p>
-<a name="ws"></a>
-<table cellpadding="2" cellspacing="5" border="0">
-<tr>
-<td colspan="2"><b>Web Services Tutorials</b></td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="../jst/components/ws/1.0M8/tutorials/BottomUpWebService.html">Creating a Bottom-Up Java Web Service (WTP 1.0M8)</a></b><img src="../../images/updated.gif"></td>
-</tr>
-<tr>
-<td></td><td>
- This document is one of a series of tutorials to demonstrate the use of the Web Services tools
- in the Web Tools Platform Project using the WTP 1.0 M8 drivers. This tutorial shows how to create
- a simple Web service and Web service client from a Java class. The Java class in this scenario
- converts between the Celsius and Farenheit temperature scales.
- </td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="../jst/components/ws/1.0M8/tutorials/WebServiceClient.html">Creating a Java Web Service Client (WTP 1.0M8)</a></b><img src="../../images/updated.gif"></td>
-</tr>
-<tr>
-<td></td><td>
- This document is one of a series of tutorials to demonstrate the use of the Web Services tools
- in the Web Tools Platform Project with the WTP 1.0 M8 drivers. This tutorial shows how to create a
- Web serivce client to the deployed Web service created in the tutorial
- <a xmlns="http://www.eclipse.org/webtools/tutorials" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" href="../jst/components/ws/1.0M8/tutorials/TopDownWebService.html">Creating a Top-Down Java
- Web Service Skeleton from a WSDL Document</a>.
- </td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="../jst/components/ws/1.0M8/tutorials/TopDownWebService.html">Creating a Top-Down Java Web Service Skeleton from a WSDL Document (WTP 1.0M8)</a></b><img src="../../images/updated.gif"></td>
-</tr>
-<tr>
-<td></td><td>
- This document is one of a series of tutorials to demonstrate the use of the Web Services tools
- in the Web Tools Platform Project using the WTP 1.0 M8 drivers. This tutorial shows how to create
- a simple top-down Web service from a WSDL file. The WSDL file in this scenario calculates the
- area of an rectangle.
- </td>
-</tr>
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><b><a href="../jst/components/ws/1.0M8/tutorials/WebServiceExplorer.html">Testing a Web Service with the Web Services Explorer (WTP 1.0M8)</a></b><img src="../../images/updated.gif"></td>
-</tr>
-<tr>
-<td></td><td>
- This document is one of a series of tutorials to demonstrate the use of the Web Services tools
- in the Web Tools Platform Project using the WTP 1.0 M8 drivers. This tutorial shows how to use the
- Web Service Explorer to test a Web service via native WSDL and SOAP. It demonstrates how to use
- the Web Services Explorer to invoke operations on a Web service named " Delayed Stock Quote "
- as available from XMethods on the internet.
- </td>
-</tr>
-</table>
-</p>
-<hr>
-<p></p>
-<p>Please see our <a href="http://www.eclipse.org/legal/privacy.html">privacy
- policy</a> and website <a href="http://www.eclipse.org/legal/termsofuse.html">terms
- of use</a>. For problems with the eclipse.org site, please contact the
- <a href="mailto:webmaster@eclipse.org">webmaster</a> or read the
- <a href="../../../webmaster/index.html">webmaster FAQ</a> for answers to common questions!</p>
-</body>
-</html>
diff --git a/community/milestonespecificresources.xml b/community/milestonespecificresources.xml
deleted file mode 100644
index a6b1100..0000000
--- a/community/milestonespecificresources.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<resources title="wtp milestone specific community resources">
- <overview>
- <p>
- <b>
- This page contains milestone specific community resources. WTP
- makes no gaurantee that these resources will continue to be
- available.
- </b>
- </p>
- <p>
- <b>
- WTP community resources for the latest WTP release can be found
- <a href="communityresources.html">here</a>.
- </b>
- </p>
- </overview>
- <resource title="WTP Tutorials" shortTitle="tutorials" src="milestonetutorials.xml"/>
-</resources>
diff --git a/community/milestonetutorials.xml b/community/milestonetutorials.xml
deleted file mode 100644
index 2db7c91..0000000
--- a/community/milestonetutorials.xml
+++ /dev/null
@@ -1,67 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<tutorials xmlns="http://www.eclipse.org/webtools/tutorials"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://www.eclipse.org/webtools/tutorials schemas/tutorials.xsd ">
- <!--
- <category name="General" id="general"/>
- <category name="Data Tools" id="rdb"/>
- <category name="J2EE" id="j2ee"/>
- <category name="Server/Internet" id="server"/>
- <category name="Structured Source Editing (SSE)" id="sse"/>
- -->
- <category name="Web Services" id="ws"/>
- <!--
- <category name="XML" id="xml"/>
- -->
-
- <tutorial title="Creating a Bottom-Up Java Web Service (WTP 1.0M8)"
- link="../jst/components/ws/1.0M8/tutorials/BottomUpWebService.html"
- categories="ws"
- datePosted="2005-06-11"
- lastUpdated="2005-09-20">
- <abstract>
- This document is one of a series of tutorials to demonstrate the use of the Web Services tools
- in the Web Tools Platform Project using the WTP 1.0 M8 drivers. This tutorial shows how to create
- a simple Web service and Web service client from a Java class. The Java class in this scenario
- converts between the Celsius and Farenheit temperature scales.
- </abstract>
- </tutorial>
- <tutorial title="Creating a Top-Down Java Web Service Skeleton from a WSDL Document (WTP 1.0M8)"
- link="../jst/components/ws/1.0M8/tutorials/TopDownWebService.html"
- categories="ws"
- datePosted="2005-06-11"
- lastUpdated="2005-09-20">
- <abstract>
- This document is one of a series of tutorials to demonstrate the use of the Web Services tools
- in the Web Tools Platform Project using the WTP 1.0 M8 drivers. This tutorial shows how to create
- a simple top-down Web service from a WSDL file. The WSDL file in this scenario calculates the
- area of an rectangle.
- </abstract>
- </tutorial>
- <tutorial title="Creating a Java Web Service Client (WTP 1.0M8)"
- link="../jst/components/ws/1.0M8/tutorials/WebServiceClient.html"
- categories="ws"
- datePosted="2005-06-11"
- lastUpdated="2005-09-20">
- <abstract>
- This document is one of a series of tutorials to demonstrate the use of the Web Services tools
- in the Web Tools Platform Project with the WTP 1.0 M8 drivers. This tutorial shows how to create a
- Web serivce client to the deployed Web service created in the tutorial
- <a href="../jst/components/ws/1.0M8/tutorials/TopDownWebService.html">Creating a Top-Down Java
- Web Service Skeleton from a WSDL Document</a>.
- </abstract>
- </tutorial>
- <tutorial title="Testing a Web Service with the Web Services Explorer (WTP 1.0M8)"
- link="../jst/components/ws/1.0M8/tutorials/WebServiceExplorer.html"
- categories="ws"
- datePosted="2005-06-04"
- lastUpdated="2005-09-20">
- <abstract>
- This document is one of a series of tutorials to demonstrate the use of the Web Services tools
- in the Web Tools Platform Project using the WTP 1.0 M8 drivers. This tutorial shows how to use the
- Web Service Explorer to test a Web service via native WSDL and SOAP. It demonstrates how to use
- the Web Services Explorer to invoke operations on a Web service named " Delayed Stock Quote "
- as available from XMethods on the internet.
- </abstract>
- </tutorial>
-</tutorials>
\ No newline at end of file
diff --git a/community/pastevents.html b/community/pastevents.html
deleted file mode 100644
index e2ebc6d..0000000
--- a/community/pastevents.html
+++ /dev/null
@@ -1,740 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../default_style.css" type="text/css">
-<link rel="stylesheet" href="../../webtools/wtp.css" type="text/css">
-<title>wtp community</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">wtp community</font>
-<br>
-<font class="indexsub">past activities</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#0080c0">
-<tbody>
-<tr>
-<td width="90%"><b><font face="Arial,Helvetica" color="#ffffff"><a name="top">Activities and resources from around the WTP community...</a></font></b></td><td align="right" width="10%"></td>
-</tr>
-</tbody>
-</table>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td with="16"> </td><td>
-<p>
- The page is about finding more information about WTP from around the WTP community.
- The community has provided many <a href="communityresources.html#articles">articles</a>, <a href="communityresources.html#books">books</a>, <a href="communityresources.html#tutorials">tutorials</a>, and <a href="communityresources.html#white papers">white papers</a>
- that are dedicated to WTP and can help you to make the most of the WTP platform and tools.
- </p>
-<p>
- Current WTP activity information can be found on the <a href="community.html">community page</a>.
- </p>
-<p>
- We'd like these pages to be useful to you - so please open a
- <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Web%20Tools&component=website">bug report</a>
- for any corrections, additions, pointers, or comments!
- </p>
-<p>
- For software licensing, website terms of use, and legal FAQs, please see our
- <a target="_top" href="http://eclipse.org/legal/main.html">legal stuff</a> page.
- </p>
-</td><td width="16"> </td>
-</tr>
-</table>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#0080c0">
-<tbody>
-<tr>
-<td width="90%"><b><font face="Arial,Helvetica" color="#ffffff"><a name="">Past WTP Activities</a></font></b></td><td align="right" width="10%"><a href="#top">top</a></td>
-</tr>
-</tbody>
-</table>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="http://www.bea.com/beaworld/uk/index.jsp?PC=12EMWP"></a><a target="_top" href="http://www.bea.com/beaworld/uk/index.jsp?PC=12EMWP"><img border="0" src="images/beaworld2005.gif"></a>
-<br>Oct 11, 2005
- -
- Oct 12, 2005
- , <b><a target="_top" href="http://www.bea.com/beaworld/uk/index.jsp?PC=12EMWP">BEA World 2005 - London</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>Presentation</u>
-<ul>
-<li>
-<a target="_top" href="http://secure.beaworld2005.com/uk/index.cfm?fuseaction=content.Agenda&day=2">Eclipse Web Tool Platform Overview</a>
-<br>
-<i>-
- <a href="../people/dai.html">Naci Dai</a></i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="http://java.org.tr/"></a><a target="_top" href="http://java.org.tr/"><img border="0" src="images/javateknolojileridernegi.gif"></a>
-<br>Sep 28, 2005
- , <b><a target="_top" href="http://java.org.tr/">Java Teknolojileri Derneği</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>Presentation</u>
-<ul>
-<li>
-<a target="_top" href="http://java.org.tr/seminer.jsp?k=16">Eclipse için plug-in geliştirmek (Turkish)</a>
-<br>
-<i>-
- <a href="../people/ercan.html">Gorkem Ercan</a></i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="http://java.org.tr/"></a><a target="_top" href="http://java.org.tr/"><img border="0" src="images/javateknolojileridernegi.gif"></a>
-<br>Sep 19, 2005
- , <b><a target="_top" href="http://java.org.tr/">Java Teknolojileri Derneği</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>Presentation</u>
-<ul>
-<li>
-<a target="_top" href="http://java.org.tr/seminer.jsp?k=15">Eclipse Web Tools Platform Projesi (Turkish)</a>
-<br>
-<i>-
- <a href="../people/ercan.html">Gorkem Ercan</a></i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="http://www.eclipseworld.net"></a><a target="_top" href="http://www.eclipseworld.net"><img border="0" src="images/EclipseWorld-129.gif"></a>
-<br>Aug 29, 2005
- -
- Aug 31, 2005
- , <b><a target="_top" href="http://www.eclipseworld.net">EclipseWorld 2005</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>Technical Classes</u>
-<ul>
-<li>
-<a target="_top" href="http://www.bzmedia.com/eclipseworld/tuesday.htm">Creating Your First J2EE Web Application With Eclipse in 90 Minutes</a>
-<br>
-<i>-
- <a href="../people/mandel.html">Lawrence Mandel</a>
- ,
- <a href="../people/sholl.html">Jason Sholl</a></i>
-</li>
-<li>
-<a target="_top" href="http://www.bzmedia.com/eclipseworld/tuesday.htm">Consuming and Producing Web Services With WST and JST</a>
-<br>
-<i>-
- <a href="../people/judd.html">Christopher M. Judd</a></i>
-</li>
-<li>
-<a target="_top" href="http://www.bzmedia.com/eclipseworld/tuesday.htm">Interacting With Relational Databases</a>
-<br>
-<i>-
- <a href="../people/judd.html">Christopher M. Judd</a></i>
-</li>
-<li>
-<a target="_top" href="http://www.bzmedia.com/eclipseworld/tuesday.htm">Developing Web Services With Eclipse</a>
-<br>
-<i>-
- <a href="../people/ryman.html">Arthur Ryman</a></i>
-</li>
-<li>
-<a target="_top" href="http://www.bzmedia.com/eclipseworld/tuesday.htm">Java Annotations in Eclipse: Enhancing the JDT Experience</a>
-<br>
-<i>-
- <a href="../people/wagner.html">Tim Wagner</a></i>
-</li>
-<li>
-<a target="_top" href="http://www.bzmedia.com/eclipseworld/tuesday.htm">XML Editing With Eclipse</a>
-<br>
-<i>-
- Elliotte Rusty Harold</i>
-</li>
-<li>
-<a target="_top" href="http://www.bzmedia.com/eclipseworld/tuesday.htm">Developing Web Services With the Web Tools Platform</a>
-<br>
-<i>-
- David Gallardo</i>
-</li>
-<li>
-<a target="_top" href="http://www.bzmedia.com/eclipseworld/wednesday.htm">Developing Enterprise JavaBeans With J2EE Standard Tools</a>
-<br>
-<i>-
- <a href="../people/judd.html">Christopher M. Judd</a></i>
-</li>
-<li>
-<a target="_top" href="http://www.bzmedia.com/eclipseworld/wednesday.htm">Web Application Development With Web Tools Platform, Part I</a>
-<br>
-<i>-
- <a href="../people/wagner.html">Tim Wagner</a></i>
-</li>
-<li>
-<a target="_top" href="http://www.bzmedia.com/eclipseworld/wednesday.htm">Web Application Development With Web Tools Platform, Part II: Advanced Topics and Extension Points</a>
-<br>
-<i>-
- <a href="../people/wagner.html">Tim Wagner</a></i>
-</li>
-<li>
-<a target="_top" href="http://www.bzmedia.com/eclipseworld/wednesday.htm">Building With the Data Tools Project</a>
-<br>
-<i>-
- John Graham
- ,
- <a href="../people/chou.html">Der-Ping Chou</a></i>
-</li>
-</ul>
-</li>
-<li>
-<u>Tutorial</u>
-<ul>
-<li>
-<a target="_top" href="http://www.bzmedia.com/eclipseworld/monday.htm">Developing J2EE Applications With the Web Tools Platform Project</a>
-<br>
-<i>-
- <a href="../people/judd.html">Christopher M. Judd</a></i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="http://java.sun.com/javaone/sf/index.jsp"></a>Jun 27, 2005
- -
- Jun 30, 2005
- , <b><a target="_top" href="http://java.sun.com/javaone/sf/index.jsp">JavaOne 2005</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>Presentations</u>
-<ul>
-<li>
-<a target="_top" href="https://www28.cplan.com/javaone05_93_1/session_details.jsp?isid=271654&ilocation_id=93-1&ilanguage=english">What's New in Eclipse? A Java™ Technology IDE and a Whole Lot More</a>
-<br>
-<i>-
- Mike Milinkovich
- ,
- Bjorn Freeman-Benson</i>
-</li>
-<li>
-<a target="_top" href="https://www28.cplan.com/javaone05_93_1/session_details.jsp?isid=271909&ilocation_id=93-1&ilanguage=english">Introduction to the Web Tools Platform Project</a>
-<br>
-<i>-
- <a href="../people/wagner.html">Tim Wagner</a></i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="../development/arch_and_design/arch_page.html"></a>Jun 16, 2005
- , <b><a target="_top" href="../development/arch_and_design/arch_page.html">WTP Open House</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>Presentation</u>
-<ul>
-<li>J2EE<br>
-<i>-
- <a href="../people/bridgham.html">Chuck Bridgham</a></i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="../development/arch_and_design/arch_page.html"></a>Jun 9, 2005
- , <b><a target="_top" href="../development/arch_and_design/arch_page.html">WTP Open House</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>Presentation</u>
-<ul>
-<li>WTP Editors (XML, JSP, etc)<br>
-<i>-
- <a href="../people/williams.html">David Williams</a></i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="../development/arch_and_design/arch_page.html"></a>Jun 2, 2005
- , <b><a target="_top" href="../development/arch_and_design/arch_page.html">WTP Open House</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>Presentation</u>
-<ul>
-<li>Common Components<br>
-<i>-
- <a href="../people/salter.html">Craig Salter</a></i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="http://www.hollandopen.nl/"></a><a target="_top" href="http://www.hollandopen.nl/"><img border="0" src="images/hollandopen.gif"></a>
-<br>May 30, 2005
- -
- Jun 1, 2005
- , <b><a target="_top" href="http://www.hollandopen.nl/">Holland Open Software Conference 2005</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>Presentation</u>
-<ul>
-<li>
-<a target="_top" href="http://www.hollandopen.nl/index.jsp?nr=1704">Eclipse and the Web Tools Platform</a>
-<br>
-<i>-
- <a href="../people/dai.html">Naci Dai</a></i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="../development/arch_and_design/arch_page.html"></a>May 26, 2005
- , <b><a target="_top" href="../development/arch_and_design/arch_page.html">WTP Open House</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>Presentations</u>
-<ul>
-<li>Web Services<br>
-<i>-
- <a href="../people/brealey.html">Chris Brealey</a></i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="https://www.conferonreg.com/RationalSpeaker2005/Agenda/agenda_main_page.cfm"></a><a target="_top" href="https://www.conferonreg.com/RationalSpeaker2005/Agenda/agenda_main_page.cfm"><img border="0" src="images/rsdc05.gif"></a>
-<br>May 22, 2005
- -
- May 26, 2005
- , <b><a target="_top" href="https://www.conferonreg.com/RationalSpeaker2005/Agenda/agenda_main_page.cfm">IBM Rational Software Development Conference 2005</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>Presentation</u>
-<ul>
-<li>
-<a target="_top" href="https://www.conferonreg.com/RationalSpeaker2005/Agenda/agenda_by_track.cfm?track=SDP&#SDP28">Introduction to the Eclipse Web Tools Platform Project</a>
-<br>
-<i>-
- <a href="../people/salter.html">Craig Salter</a>
- ,
- <a href="../people/chong.html">Keith Chong</a></i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="../development/arch_and_design/arch_page.html"></a>May 19, 2005
- , <b><a target="_top" href="../development/arch_and_design/arch_page.html">WTP Open House</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>Presentations</u>
-<ul>
-<li>Server and Database Components<br>
-<i>-
- <a href="../people/deboer.html">Tim deBoer</a>
- ,
- <a href="../people/chou.html">Der-Ping Chou</a></i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="http://www.club-java.com/"></a><a target="_top" href="http://www.club-java.com/"><img border="0" src="images/LogoPetit.gif"></a>
-<br>May 12, 2005
- , <b><a target="_top" href="http://www.club-java.com/">Le club des utilisateurs java</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>Presentation</u>
-<ul>
-<li>
-<a target="_top" href="http://enews.naos.com/servlets/com.naos.enews.HtmlFileFilter?id=183555096&filter=true">ObjectWeb and Eclipse - the WTP project and beyond</a>
-<br>
-<i>-
- <a href="../people/ney.html">Christophe Ney</a></i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="http://www.jax.de"></a><a target="_top" href="http://www.jax.de"><img border="0" src="images/jax05-logo.jpg"></a>
-<br>May 9, 2005
- -
- May 13, 2005
- , <b><a target="_top" href="http://www.jax.de">JAX 2005</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>Presentation</u>
-<ul>
-<li>
-<a target="_top" href="http://www.jax.de/konferenzen/psecom,id,277,nodeid,,.html#EC1">Eclipse: What's new in 3.1</a>
-<br>
-<i>-
- Erich Gamma
- ,
- <a href="../people/krause.html">Jochen Krause</a></i>
-</li>
-<li>
-<a target="_top" href="http://www.jax.de/konferenzen/psecom,id,277,nodeid,,.html#EC12">Extending the SSE</a>
-<br>
-<i>-
- <a href="../people/lukowski.html">Jens Lukowski</a></i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="http://www.webserviceschina.com/"></a><a target="_top" href="http://www.webserviceschina.com/"><img border="0" src="images/wssoachina2005.gif"></a>
-<br>Apr 7, 2005
- , <b><a target="_top" href="http://www.webserviceschina.com/">Web Services & SOA China 2005</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>Presentation</u>
-<ul>
-<li>Developing Web Services with Eclipse<br>
-<i>-
- <a href="../people/ryman.html">Arthur Ryman</a></i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="http://www.sdforum.org/"></a><a target="_top" href="http://www.sdforum.org/"><img border="0" src="images/sdforum.jpg"></a>
-<br>Mar 1, 2005
- , <b><a target="_top" href="http://www.sdforum.org/">SDForum</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>Presentation</u>
-<ul>
-<li>
-<a target="_top" href="http://www.sdforum.org/SDForum/Templates/Level1.aspx?pid=10108&sid=7">Eclipse Web Tools Platform Project Overview</a>
-<br>
-<i>-
- <a href="../people/deboer.html">Tim deBoer</a></i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="http://www.eclipsecon.org/?ID=EclipseWTP"></a><a target="_top" href="http://www.eclipsecon.org/?ID=EclipseWTP"><img border="0" src="images/eclipsecon.gif"></a>
-<br>Feb 28, 2005
- -
- Mar 3, 2005
- , <b><a target="_top" href="http://www.eclipsecon.org/?ID=EclipseWTP">EclipseCon</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>Technical Sessions</u>
-<ul>
-<li>
-<a target="_top" href="http://www.eclipsecon.org/sessions.php">Extend web tools server tooling for your application server</a>
-<br>
-<i>-
- <a href="../people/ercan.html">Gorkem Ercan</a>
- ,
- <a href="../people/deboer.html">Tim deBoer</a></i>
-</li>
-<li>
-<a target="_top" href="http://www.eclipsecon.org/sessions.php">Eclipse Web Tools Platform Project Overview</a>
-<br>
-<i>-
- <a href="../people/dai.html">Naci Dai</a>
- ,
- <a href="../people/ryman.html">Arthur Ryman</a></i>
-</li>
-<li>
-<a target="_top" href="http://www.eclipsecon.org/sessions.php">Web Services Dev. with Eclipse Web Tools Platform Project</a>
-<br>
-<i>-
- <a href="../people/liu.html">Jeffrey Liu</a>
- ,
- <a href="../people/mandel.html">Lawrence Mandel</a></i>
-</li>
-</ul>
-</li>
-<li>
-<u>Tutorials</u>
-<ul>
-<li>
-<a target="_top" href="http://www.eclipsecon.org/tutorials.php">Introduction to the Web Tools Platform</a>
-<br>
-<i>-
- <a href="../people/bridgham.html">Chuck Bridgham</a>
- ,
- <a href="../people/mandel.html">Lawrence Mandel</a></i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="http://www.etsmtl.ca/"></a><a target="_top" href="http://www.etsmtl.ca/"><img border="0" src="images/ecoledetechnologie.gif"></a>
-<br>Feb 23, 2005
- , <b><a target="_top" href="http://www.etsmtl.ca/">École de technologie supérieure</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>Presentation</u>
-<ul>
-<li>
-<a target="_top" href="http://www.etsmtl.ca/zone2/departements/logti/evenements/conference5.pdf">Formal Specification at W3C</a>
-<br>
-<i>-
- <a href="../people/ryman.html">Arthur Ryman</a></i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="http://www.sys-con.com/edge2005east/index.cfm"></a>Feb 15, 2005
- -
- Feb 17, 2005
- , <b><a target="_top" href="http://www.sys-con.com/edge2005east/index.cfm">Web Service Edge 2005 East</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>Case Study</u>
-<ul>
-<li>
-<a target="_top" href="http://www.sys-con.com/story/?storyid=47527">Developing Web Services with Eclipse</a>
-<br>
-<i>-
- <a href="../people/ryman.html">Arthur Ryman</a></i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="http://www.pjug.org/"></a><a target="_top" href="http://www.pjug.org/"><img border="0" src="images/pjug.gif"></a>
-<br>Jan 25, 2005
- , <b><a target="_top" href="http://www.pjug.org/">Portland Java User's Group</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>Presentation</u>
-<ul>
-<li>Eclipse Web Tools<br>
-<i>-
- Sean C. Sullivan</i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="http://www.cutc.ca"></a><a target="_top" href="http://www.cutc.ca"><img border="0" src="images/cutc2005.gif"></a>
-<br>Jan 20, 2005
- -
- Jan 22, 2005
- , <b><a target="_top" href="http://www.cutc.ca">CUTC 2005 : Canadian Undergraduate Technology Conference</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>TechShop</u>
-<ul>
-<li>Dive into Eclipse and the Web Tools Platform Project<br>
-<i>-
- <a href="../people/liu.html">Jeffrey Liu</a>
- ,
- <a href="../people/mandel.html">Lawrence Mandel</a></i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<table border="0" cellpadding="2" cellspacing="5">
-<tr>
-<td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td><td><a name="http://www.objectweb.org/ObjectWebCon05"></a><a target="_top" href="http://www.objectweb.org/ObjectWebCon05"><img border="0" src="images/objectwebcon.jpg"></a>
-<br>Jan 19, 2005
- -
- Jan 21, 2005
- , <b><a target="_top" href="http://www.objectweb.org/ObjectWebCon05">ObjectWebCon'05</a></b></td>
-</tr>
-<tr>
-<td align="right" valign="top"> </td><td valign="top">
-<ul type="square">
-<li>
-<u>Speaker Sessions</u>
-<ul>
-<li>Eclipse Web Tools Platform Project Overview<br>
-<i>-
- <a href="../people/dai.html">Naci Dai</a></i>
-</li>
-<li>Eclipse Web Tools - Extending the Structured Source Editor<br>
-<i>-
- <a href="../people/krause.html">Jochen Krause</a></i>
-</li>
-</ul>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-<hr>
-<p></p>
-<p>Please see our <a href="http://www.eclipse.org/legal/privacy.html">privacy
- policy</a> and website <a href="http://www.eclipse.org/legal/termsofuse.html">terms
- of use</a>. For problems with the eclipse.org site, please contact the
- <a href="mailto:webmaster@eclipse.org">webmaster</a> or read the
- <a href="../../../webmaster/index.html">webmaster FAQ</a> for answers to common questions!</p>
-</body>
-</html>
diff --git a/community/presentations.data b/community/presentations.data
deleted file mode 100644
index 88ba3fc..0000000
--- a/community/presentations.data
+++ /dev/null
@@ -1,201 +0,0 @@
-<?xml version="1.0"?>
-<?xml-stylesheet type="text/xsl" href="presentations.xsl"?>
-
-<presentations
- base="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/">
-
- <presentation>
- <title>Developing Web Services with Eclipse</title>
- <presenter>Arthur Ryman</presenter>
- <venue>Web Services Edge East, Boston</venue>
- <date>2005-02-17</date>
- <file>2005/02-17-ws-edge-east/dev-ws-eclipse.ppt</file>
- </presentation>
-
- <presentation>
- <title>An Open Development Platform</title>
- <presenter>Mike Milinkovich</presenter>
- <venue>Web Services Edge East, Boston</venue>
- <date>2005-02-17</date>
- <file>2005/02-17-ws-edge-east/open-dev-platform.ppt</file>
- </presentation>
-
- <presentation>
- <title>
- Extend WTP Server Tools for your Application Server
- </title>
- <presenter>Tim deBoer</presenter>
- <presenter>Gorkem Ercan</presenter>
- <venue>EclipseCon, Burlingame</venue>
- <date>2005-03-01</date>
- <file>2005/03-01-eclipsecon/server-tools.ppt</file>
- </presentation>
-
- <presentation>
- <title>Web Tools Platform Project Overview</title>
- <presenter>Naci Dai</presenter>
- <presenter>Arthur Ryman</presenter>
- <venue>EclipseCon, Burlingame</venue>
- <date>2005-03-02</date>
- <file>2005/03-02-eclipsecon/wtp-overview.ppt</file>
- </presentation>
-
- <presentation>
- <title>Developing Web Services with Eclipse</title>
- <presenter>Arthur Ryman</presenter>
- <venue>Web Services and SOA China, Beijing</venue>
- <date>2005-04-07</date>
- <file>2005/04-07-ws-soa-china/dev-ws-eclipse.ppt</file>
- <translation language="Chinese">
- 2005/04-07-ws-soa-china/dev-ws-eclipse-cn.ppt
- </translation>
- </presentation>
-
- <presentation>
- <title>eclipse: what’s new in 3.1</title>
- <presenter>Jochen Krause</presenter>
- <venue>JAX 2005, Frankfurt</venue>
- <date>2005-05-10</date>
- <file>2005/05-10-jax/whats-new-in-eclipse-3-1.ppt</file>
- </presentation>
-
- <presentation>
- <title>WTP Server Tools Open House</title>
- <presenter>Tim deBoer</presenter>
- <venue>WTP Open House, Web Conference</venue>
- <date>2005-05-19</date>
- <file>2005/05-19-wtp-open-house/server-tools.ppt</file>
- </presentation>
-
- <presentation>
- <title>Component: RDB</title>
- <presenter>Der-Ping Chou</presenter>
- <venue>WTP Open House, Web Conference</venue>
- <date>2005-05-19</date>
- <file>2005/05-19-wtp-open-house/data-tools.ppt</file>
- </presentation>
-
- <presentation>
- <title>Eclipse WTP Project Web Service Tools Open House</title>
- <presenter>Chris Brealey</presenter>
- <venue>WTP Open House, Web Conference</venue>
- <date>2005-05-26</date>
- <file>2005/05-26-wtp-open-house/web-service-tools.ppt</file>
- </presentation>
-
- <presentation>
- <title>Eclipse WTP Project Common Components Open House</title>
- <presenter>Craig Salter</presenter>
- <venue>WTP Open House, Web Conference</venue>
- <date>2005-06-02</date>
- <file>
- 2005/06-02-wtp-open-house/common-tools-06-02-1530-highlighted2.ppt
- </file>
- </presentation>
-
- <presentation>
- <title>
- Eclipse WTP Project Source Editing Components Open House
- </title>
- <presenter>David Williams</presenter>
- <venue>WTP Open House, Web Conference</venue>
- <date>2005-06-09</date>
- <file>2005/06-09-wtp-open-house/sse-openhouse-6-9.ppt</file>
- </presentation>
-
- <presentation>
- <title>
- Eclipse WTP Project J2EE Tools and Flexible Project
- Components Open House
- </title>
- <presenter>Chuck Bridgham, Naci Dai</presenter>
- <venue>WTP Open House, Web Conference</venue>
- <date>2005-06-16</date>
- <file>2005/06-16-wtp-open-house/j2ee-tools-06-16.ppt</file>
- </presentation>
-
- <presentation>
- <title>Introduction to the Web Tools Platform Project</title>
- <presenter>Tim Wagner</presenter>
- <venue>JavaOne, San Francisco</venue>
- <date>2005-06-29</date>
- <file>2005/06-29-javaone/intro-to-wtp-project.ppt</file>
- </presentation>
-
- <presentation>
- <title>Eclipse WTP 0.7 Release Review</title>
- <presenter>Tim Wagner</presenter>
- <venue>WTP Release Review, Web Conference</venue>
- <date>2005-07-06</date>
- <file>
- 2005/07-06-wtp-release-review/eclipse-wtp-0.7-release-review.ppt
- </file>
- </presentation>
-
- <presentation>
- <title>Developing Web Services with Eclipse</title>
- <presenter>Arthur Ryman</presenter>
- <venue>EclipseWorld, New York</venue>
- <date>2005-08-30</date>
- <file>2005/08-30-eclipseworld/ryman-dev-ws-eclipse.ppt</file>
- </presentation>
-
- <presentation>
- <title>
- Developing Web Services with Eclipse - Programming Examples
- </title>
- <presenter>Arthur Ryman</presenter>
- <venue>EclipseWorld, New York</venue>
- <date>2005-08-30</date>
- <file>
- 2005/08-30-eclipseworld/ryman-dev-ws-eclipse-examples.ppt
- </file>
- </presentation>
-
- <presentation>
- <title>
- Developing Web Services with Eclipse - Programming Examples
- Source Code
- </title>
- <presenter>Arthur Ryman</presenter>
- <venue>EclipseWorld, New York</venue>
- <date>2005-08-30</date>
- <file>2005/08-30-eclipseworld/ryman-dev-ws-eclipse-examples-src.zip</file>
- </presentation>
-
- <presentation>
- <title>
- Creating Your First J2EE Web Application with Eclipse in 90 Minutes
- </title>
- <presenter>Jason Sholl</presenter>
- <presenter>Lawrence Mandel</presenter>
- <venue>EclipseWorld, New York</venue>
- <date>2005-08-30</date>
- <file>2005/08-30-eclipseworld/CreatingYourFirstJ2EEApp.ppt</file>
- </presentation>
-
- <presentation>
- <title>
- Web Application Development with WTP Part 1
- </title>
- <presenter>Tim Wagner</presenter>
- <presenter>Paul Meijer</presenter>
- <presenter>Ted Bashor</presenter>
- <venue>EclipseWorld, New York</venue>
- <date>2005-08-31</date>
- <file>2005/08-31-eclipseworld/Web+Application+Development+with+WTP+Part+1.ppt</file>
- </presentation>
-
- <presentation>
- <title>
- Web Application Development with WTP Part 2
- </title>
- <presenter>Tim Wagner</presenter>
- <presenter>Paul Meijer</presenter>
- <presenter>Ted Bashor</presenter>
- <venue>EclipseWorld, New York</venue>
- <date>2005-08-31</date>
- <file>2005/08-31-eclipseworld/Web+Application+Development+with+WTP+Part+2.ppt</file>
- </presentation>
-
-</presentations>
\ No newline at end of file
diff --git a/community/presentations.html b/community/presentations.html
deleted file mode 100644
index a1d085f..0000000
--- a/community/presentations.html
+++ /dev/null
@@ -1,203 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../default_style.css" type="text/css">
-<link rel="stylesheet" href="../../webtools/wtp.css" type="text/css">
-<title>Eclipse Web Tools Platform Project Presentation Archive</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">wtp presentation archive</font>
-<br>
-<font class="indexsub">Eclipse Web Tools Platform Project Presentation Archive</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Introduction</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-This page lists presentations on WTP and related topics.
-Feel free to reuse this material in your own presentations.
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-If you have a presentation that you'd like to share with the WTP community,
-please contribute it by creating a <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Web%20Tools">Bugzilla</a> bug against WTP. Use
-<ul>
-
-<li>
-
-<b>Product:</b> Web Tools</li>
-
-<li>
-
-<b>Component:</b> website</li>
-
-<li>
-
-<b>Severity:</b> enhancement</li>
-
-</ul>
-Include the title, speaker, venue, and date in the bug comments.
-Attach your presentation to the bug report.
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Presentations</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../images/Adarrow.gif"></td><td>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/02-17-ws-edge-east/dev-ws-eclipse.ppt" name="2005/02-17-ws-edge-east/dev-ws-eclipse.ppt">
-<em>Developing Web Services with Eclipse</em>
-</a>, Arthur Ryman, Web Services Edge East, Boston, 2005-02-17. </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../images/Adarrow.gif"></td><td>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/02-17-ws-edge-east/open-dev-platform.ppt" name="2005/02-17-ws-edge-east/open-dev-platform.ppt">
-<em>An Open Development Platform</em>
-</a>, Mike Milinkovich, Web Services Edge East, Boston, 2005-02-17. </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../images/Adarrow.gif"></td><td>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/03-01-eclipsecon/server-tools.ppt" name="2005/03-01-eclipsecon/server-tools.ppt">
-<em>
- Extend WTP Server Tools for your Application Server
- </em>
-</a>, Tim deBoer, Gorkem Ercan, EclipseCon, Burlingame, 2005-03-01. </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../images/Adarrow.gif"></td><td>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/03-02-eclipsecon/wtp-overview.ppt" name="2005/03-02-eclipsecon/wtp-overview.ppt">
-<em>Web Tools Platform Project Overview</em>
-</a>, Naci Dai, Arthur Ryman, EclipseCon, Burlingame, 2005-03-02. </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../images/Adarrow.gif"></td><td>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/04-07-ws-soa-china/dev-ws-eclipse.ppt" name="2005/04-07-ws-soa-china/dev-ws-eclipse.ppt">
-<em>Developing Web Services with Eclipse</em>
-</a> [<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/04-07-ws-soa-china/dev-ws-eclipse-cn.ppt">Chinese</a>], Arthur Ryman, Web Services and SOA China, Beijing, 2005-04-07. </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../images/Adarrow.gif"></td><td>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/05-10-jax/whats-new-in-eclipse-3-1.ppt" name="2005/05-10-jax/whats-new-in-eclipse-3-1.ppt">
-<em>eclipse: what’s new in 3.1</em>
-</a>, Jochen Krause, JAX 2005, Frankfurt, 2005-05-10. </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../images/Adarrow.gif"></td><td>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/05-19-wtp-open-house/server-tools.ppt" name="2005/05-19-wtp-open-house/server-tools.ppt">
-<em>WTP Server Tools Open House</em>
-</a>, Tim deBoer, WTP Open House, Web Conference, 2005-05-19. </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../images/Adarrow.gif"></td><td>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/05-19-wtp-open-house/data-tools.ppt" name="2005/05-19-wtp-open-house/data-tools.ppt">
-<em>Component: RDB</em>
-</a>, Der-Ping Chou, WTP Open House, Web Conference, 2005-05-19. </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../images/Adarrow.gif"></td><td>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/05-26-wtp-open-house/web-service-tools.ppt" name="2005/05-26-wtp-open-house/web-service-tools.ppt">
-<em>Eclipse WTP Project Web Service Tools Open House</em>
-</a>, Chris Brealey, WTP Open House, Web Conference, 2005-05-26. </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../images/Adarrow.gif"></td><td>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/06-02-wtp-open-house/common-tools-06-02-1530-highlighted2.ppt" name="2005/06-02-wtp-open-house/common-tools-06-02-1530-highlighted2.ppt">
-<em>Eclipse WTP Project Common Components Open House</em>
-</a>, Craig Salter, WTP Open House, Web Conference, 2005-06-02. </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../images/Adarrow.gif"></td><td>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/06-09-wtp-open-house/sse-openhouse-6-9.ppt" name="2005/06-09-wtp-open-house/sse-openhouse-6-9.ppt">
-<em>
- Eclipse WTP Project Source Editing Components Open House
- </em>
-</a>, David Williams, WTP Open House, Web Conference, 2005-06-09. </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../images/Adarrow.gif"></td><td>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/06-16-wtp-open-house/j2ee-tools-06-16.ppt" name="2005/06-16-wtp-open-house/j2ee-tools-06-16.ppt">
-<em>
- Eclipse WTP Project J2EE Tools and Flexible Project
- Components Open House
- </em>
-</a>, Chuck Bridgham, Naci Dai, WTP Open House, Web Conference, 2005-06-16. </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../images/Adarrow.gif"></td><td>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/06-29-javaone/intro-to-wtp-project.ppt" name="2005/06-29-javaone/intro-to-wtp-project.ppt">
-<em>Introduction to the Web Tools Platform Project</em>
-</a>, Tim Wagner, JavaOne, San Francisco, 2005-06-29. </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../images/Adarrow.gif"></td><td>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/07-06-wtp-release-review/eclipse-wtp-0.7-release-review.ppt" name="2005/07-06-wtp-release-review/eclipse-wtp-0.7-release-review.ppt">
-<em>Eclipse WTP 0.7 Release Review</em>
-</a>, Tim Wagner, WTP Release Review, Web Conference, 2005-07-06. </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../images/Adarrow.gif"></td><td>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/08-30-eclipseworld/ryman-dev-ws-eclipse.ppt" name="2005/08-30-eclipseworld/ryman-dev-ws-eclipse.ppt">
-<em>Developing Web Services with Eclipse</em>
-</a>, Arthur Ryman, EclipseWorld, New York, 2005-08-30. </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../images/Adarrow.gif"></td><td>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/08-30-eclipseworld/ryman-dev-ws-eclipse-examples.ppt" name="2005/08-30-eclipseworld/ryman-dev-ws-eclipse-examples.ppt">
-<em>
- Developing Web Services with Eclipse - Programming Examples
- </em>
-</a>, Arthur Ryman, EclipseWorld, New York, 2005-08-30. </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../images/Adarrow.gif"></td><td>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/08-30-eclipseworld/ryman-dev-ws-eclipse-examples-src.zip" name="2005/08-30-eclipseworld/ryman-dev-ws-eclipse-examples-src.zip">
-<em>
- Developing Web Services with Eclipse - Programming Examples
- Source Code
- </em>
-</a>, Arthur Ryman, EclipseWorld, New York, 2005-08-30. </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../images/Adarrow.gif"></td><td>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/08-30-eclipseworld/CreatingYourFirstJ2EEApp.ppt" name="2005/08-30-eclipseworld/CreatingYourFirstJ2EEApp.ppt">
-<em>
- Creating Your First J2EE Web Application with Eclipse in 90 Minutes
- </em>
-</a>, Jason Sholl, Lawrence Mandel, EclipseWorld, New York, 2005-08-30. </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../images/Adarrow.gif"></td><td>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/08-31-eclipseworld/Web+Application+Development+with+WTP+Part+1.ppt" name="2005/08-31-eclipseworld/Web+Application+Development+with+WTP+Part+1.ppt">
-<em>
- Web Application Development with WTP Part 1
- </em>
-</a>, Tim Wagner, Paul Meijer, Ted Bashor, EclipseWorld, New York, 2005-08-31. </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../images/Adarrow.gif"></td><td>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/08-31-eclipseworld/Web+Application+Development+with+WTP+Part+2.ppt" name="2005/08-31-eclipseworld/Web+Application+Development+with+WTP+Part+2.ppt">
-<em>
- Web Application Development with WTP Part 2
- </em>
-</a>, Tim Wagner, Paul Meijer, Ted Bashor, EclipseWorld, New York, 2005-08-31. </td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/community/presentations.xml b/community/presentations.xml
deleted file mode 100644
index 3520b6c..0000000
--- a/community/presentations.xml
+++ /dev/null
@@ -1,127 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<html>
-<head>
-<title>Eclipse Web Tools Platform Project Presentation Archive</title>
-</head>
-<body>
-<h1>wtp presentation archive</h1>
-<h2>Introduction</h2>
-<p>
-This page lists presentations on WTP and related topics.
-Feel free to reuse this material in your own presentations.
-</p>
-<p>
-If you have a presentation that you'd like to share with the WTP community,
-please contribute it by creating a <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Web%20Tools">Bugzilla</a> bug against WTP. Use
-<ul>
-<li>
-<b>Product:</b> Web Tools</li>
-<li>
-<b>Component:</b> website</li>
-<li>
-<b>Severity:</b> enhancement</li>
-</ul>
-Include the title, speaker, venue, and date in the bug comments.
-Attach your presentation to the bug report.
-</p>
-<h2>Presentations</h2>
-<h3>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/02-17-ws-edge-east/dev-ws-eclipse.ppt" name="2005/02-17-ws-edge-east/dev-ws-eclipse.ppt">
-<em>Developing Web Services with Eclipse</em>
-</a>, Arthur Ryman, Web Services Edge East, Boston, 2005-02-17. </h3>
-<h3>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/02-17-ws-edge-east/open-dev-platform.ppt" name="2005/02-17-ws-edge-east/open-dev-platform.ppt">
-<em>An Open Development Platform</em>
-</a>, Mike Milinkovich, Web Services Edge East, Boston, 2005-02-17. </h3>
-<h3>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/03-01-eclipsecon/server-tools.ppt" name="2005/03-01-eclipsecon/server-tools.ppt">
-<em>
- Extend WTP Server Tools for your Application Server
- </em>
-</a>, Tim deBoer, Gorkem Ercan, EclipseCon, Burlingame, 2005-03-01. </h3>
-<h3>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/03-02-eclipsecon/wtp-overview.ppt" name="2005/03-02-eclipsecon/wtp-overview.ppt">
-<em>Web Tools Platform Project Overview</em>
-</a>, Naci Dai, Arthur Ryman, EclipseCon, Burlingame, 2005-03-02. </h3>
-<h3>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/04-07-ws-soa-china/dev-ws-eclipse.ppt" name="2005/04-07-ws-soa-china/dev-ws-eclipse.ppt">
-<em>Developing Web Services with Eclipse</em>
-</a> [<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/04-07-ws-soa-china/dev-ws-eclipse-cn.ppt">Chinese</a>], Arthur Ryman, Web Services and SOA China, Beijing, 2005-04-07. </h3>
-<h3>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/05-10-jax/whats-new-in-eclipse-3-1.ppt" name="2005/05-10-jax/whats-new-in-eclipse-3-1.ppt">
-<em>eclipse: what’s new in 3.1</em>
-</a>, Jochen Krause, JAX 2005, Frankfurt, 2005-05-10. </h3>
-<h3>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/05-19-wtp-open-house/server-tools.ppt" name="2005/05-19-wtp-open-house/server-tools.ppt">
-<em>WTP Server Tools Open House</em>
-</a>, Tim deBoer, WTP Open House, Web Conference, 2005-05-19. </h3>
-<h3>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/05-19-wtp-open-house/data-tools.ppt" name="2005/05-19-wtp-open-house/data-tools.ppt">
-<em>Component: RDB</em>
-</a>, Der-Ping Chou, WTP Open House, Web Conference, 2005-05-19. </h3>
-<h3>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/05-26-wtp-open-house/web-service-tools.ppt" name="2005/05-26-wtp-open-house/web-service-tools.ppt">
-<em>Eclipse WTP Project Web Service Tools Open House</em>
-</a>, Chris Brealey, WTP Open House, Web Conference, 2005-05-26. </h3>
-<h3>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/06-02-wtp-open-house/common-tools-06-02-1530-highlighted2.ppt" name="2005/06-02-wtp-open-house/common-tools-06-02-1530-highlighted2.ppt">
-<em>Eclipse WTP Project Common Components Open House</em>
-</a>, Craig Salter, WTP Open House, Web Conference, 2005-06-02. </h3>
-<h3>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/06-09-wtp-open-house/sse-openhouse-6-9.ppt" name="2005/06-09-wtp-open-house/sse-openhouse-6-9.ppt">
-<em>
- Eclipse WTP Project Source Editing Components Open House
- </em>
-</a>, David Williams, WTP Open House, Web Conference, 2005-06-09. </h3>
-<h3>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/06-16-wtp-open-house/j2ee-tools-06-16.ppt" name="2005/06-16-wtp-open-house/j2ee-tools-06-16.ppt">
-<em>
- Eclipse WTP Project J2EE Tools and Flexible Project
- Components Open House
- </em>
-</a>, Chuck Bridgham, Naci Dai, WTP Open House, Web Conference, 2005-06-16. </h3>
-<h3>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/06-29-javaone/intro-to-wtp-project.ppt" name="2005/06-29-javaone/intro-to-wtp-project.ppt">
-<em>Introduction to the Web Tools Platform Project</em>
-</a>, Tim Wagner, JavaOne, San Francisco, 2005-06-29. </h3>
-<h3>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/07-06-wtp-release-review/eclipse-wtp-0.7-release-review.ppt" name="2005/07-06-wtp-release-review/eclipse-wtp-0.7-release-review.ppt">
-<em>Eclipse WTP 0.7 Release Review</em>
-</a>, Tim Wagner, WTP Release Review, Web Conference, 2005-07-06. </h3>
-<h3>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/08-30-eclipseworld/ryman-dev-ws-eclipse.ppt" name="2005/08-30-eclipseworld/ryman-dev-ws-eclipse.ppt">
-<em>Developing Web Services with Eclipse</em>
-</a>, Arthur Ryman, EclipseWorld, New York, 2005-08-30. </h3>
-<h3>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/08-30-eclipseworld/ryman-dev-ws-eclipse-examples.ppt" name="2005/08-30-eclipseworld/ryman-dev-ws-eclipse-examples.ppt">
-<em>
- Developing Web Services with Eclipse - Programming Examples
- </em>
-</a>, Arthur Ryman, EclipseWorld, New York, 2005-08-30. </h3>
-<h3>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/08-30-eclipseworld/ryman-dev-ws-eclipse-examples-src.zip" name="2005/08-30-eclipseworld/ryman-dev-ws-eclipse-examples-src.zip">
-<em>
- Developing Web Services with Eclipse - Programming Examples
- Source Code
- </em>
-</a>, Arthur Ryman, EclipseWorld, New York, 2005-08-30. </h3>
-<h3>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/08-30-eclipseworld/CreatingYourFirstJ2EEApp.ppt" name="2005/08-30-eclipseworld/CreatingYourFirstJ2EEApp.ppt">
-<em>
- Creating Your First J2EE Web Application with Eclipse in 90 Minutes
- </em>
-</a>, Jason Sholl, Lawrence Mandel, EclipseWorld, New York, 2005-08-30. </h3>
-<h3>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/08-31-eclipseworld/Web+Application+Development+with+WTP+Part+1.ppt" name="2005/08-31-eclipseworld/Web+Application+Development+with+WTP+Part+1.ppt">
-<em>
- Web Application Development with WTP Part 1
- </em>
-</a>, Tim Wagner, Paul Meijer, Ted Bashor, EclipseWorld, New York, 2005-08-31. </h3>
-<h3>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/08-31-eclipseworld/Web+Application+Development+with+WTP+Part+2.ppt" name="2005/08-31-eclipseworld/Web+Application+Development+with+WTP+Part+2.ppt">
-<em>
- Web Application Development with WTP Part 2
- </em>
-</a>, Tim Wagner, Paul Meijer, Ted Bashor, EclipseWorld, New York, 2005-08-31. </h3>
-</body>
-</html>
diff --git a/community/schemas/articles.xsd b/community/schemas/articles.xsd
deleted file mode 100644
index d738113..0000000
--- a/community/schemas/articles.xsd
+++ /dev/null
@@ -1,36 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.eclipse.org/webtools/articles" xmlns:tns="http://www.eclipse.org/webtools/articles">
- <element name="articles">
- <complexType>
- <sequence>
- <element ref="tns:article" minOccurs="0" maxOccurs="unbounded"></element>
- </sequence>
- </complexType>
- </element>
-
- <element name="article">
- <complexType>
- <sequence>
- <element ref="tns:publication" minOccurs="1" maxOccurs="1"></element>
- <element ref="tns:author" maxOccurs="unbounded" minOccurs="1"></element>
- </sequence>
- <attribute name="title" type="string" use="required"></attribute>
- <attribute name="link" type="string" use="required"></attribute>
- <attribute name="publicationDate" type="date" use="required"></attribute>
- </complexType>
- </element>
-
- <element name="publication">
- <complexType>
- <attribute name="name" type="string" use="required"></attribute>
- <attribute name="link" type="string" use="optional"></attribute>
- </complexType>
- </element>
-
- <element name="author">
- <complexType>
- <attribute name="name" type="string" use="required"></attribute>
- </complexType>
- </element>
-
-</schema>
\ No newline at end of file
diff --git a/community/schemas/biopages.xsd b/community/schemas/biopages.xsd
deleted file mode 100644
index 8a13a10..0000000
--- a/community/schemas/biopages.xsd
+++ /dev/null
@@ -1,22 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.eclipse.org/webtools/biopages" xmlns:tns="http://www.eclipse.org/webtools/biopages">
- <element name="bios">
- <complexType>
- <sequence>
- <element ref="tns:bio" minOccurs="0" maxOccurs="unbounded"></element>
- </sequence>
- </complexType>
- <key name="name">
- <selector xpath="tns:bio"/>
- <field xpath="@name"/>
- </key>
- </element>
-
- <element name="bio">
- <complexType>
- <attribute name="link" type="anyURI" use="required"></attribute>
- <attribute name="name" type="string" use="required"></attribute>
- </complexType>
- </element>
-
-</schema>
\ No newline at end of file
diff --git a/community/schemas/books.xsd b/community/schemas/books.xsd
deleted file mode 100644
index 03324eb..0000000
--- a/community/schemas/books.xsd
+++ /dev/null
@@ -1,38 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.eclipse.org/webtools/books" xmlns:tns="http://www.eclipse.org/webtools/books">
- <element name="books">
- <complexType>
- <choice>
- <element ref="tns:book" minOccurs="0" maxOccurs="unbounded"></element>
- </choice>
- </complexType>
- </element>
-
- <element name="book">
- <complexType>
- <choice>
- <element ref="tns:publisher" minOccurs="1" maxOccurs="1"/>
- <element ref="tns:author" minOccurs="1" maxOccurs="unbounded"></element>
- </choice>
- <attribute name="title" type="string" use="required"></attribute>
- <attribute name="link" type="anyURI" use="optional"></attribute>
- <attribute name="image" type="anyURI" use="optional"></attribute>
- <attribute name="publicationDate" type="date" use="required"></attribute>
- </complexType>
- </element>
-
- <element name="publisher">
- <complexType>
- <attribute name="name" type="string" use="required"></attribute>
- <attribute name="link" type="anyURI" use="optional"></attribute>
- </complexType>
- </element>
-
- <element name="author">
- <complexType>
- <attribute name="name" type="string" use="required"></attribute>
- <attribute name="bioPage" type="anyURI" use="optional"></attribute>
- </complexType>
- </element>
-
-</schema>
\ No newline at end of file
diff --git a/community/schemas/events.xsd b/community/schemas/events.xsd
deleted file mode 100644
index 5f4bcde..0000000
--- a/community/schemas/events.xsd
+++ /dev/null
@@ -1,51 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.eclipse.org/webtools/events" xmlns:tns="http://www.eclipse.org/webtools/events">
- <element name="events">
- <complexType>
- <choice>
- <element ref="tns:event" minOccurs="0" maxOccurs="unbounded"></element>
- </choice>
- </complexType>
- </element>
-
- <element name="event">
- <complexType>
- <choice>
- <element ref="tns:presentation" minOccurs="0" maxOccurs="unbounded"></element>
- </choice>
- <attribute name="startdate" type="date" use="required"></attribute>
- <attribute name="enddate" type="date" use="required"></attribute>
- <attribute name="organization" type="string" use="required"></attribute>
- <attribute name="link" type="anyURI" use="required"></attribute>
- <attribute name="logo" type="string" use="optional"></attribute>
- </complexType>
- </element>
-
- <element name="presenter">
- <complexType>
- <attribute name="name" type="string" use="required"></attribute>
- </complexType>
- </element>
-
- <element name="presentation">
- <complexType>
- <sequence>
- <element ref="tns:presenter" minOccurs="1" maxOccurs="unbounded"></element>
- <element ref="tns:material" minOccurs="0" maxOccurs="unbounded"></element>
- </sequence>
- <attribute name="type" type="string" use="required"></attribute>
- <attribute name="title" type="string" use="required"></attribute>
- <attribute name="link" type="anyURI" use="optional"></attribute>
- <attribute name="time" type="string" use="optional"></attribute>
- </complexType>
- </element>
-
- <element name="material">
- <complexType>
- <attribute name="type" type="string" use="required"></attribute>
- <attribute name="name" type="string" use="required"></attribute>
- <attribute name="link" type="anyURI" use="required"></attribute>
- </complexType>
- </element>
-
-</schema>
\ No newline at end of file
diff --git a/community/schemas/tutorials.xsd b/community/schemas/tutorials.xsd
deleted file mode 100644
index a39f0aa..0000000
--- a/community/schemas/tutorials.xsd
+++ /dev/null
@@ -1,38 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.eclipse.org/webtools/tutorials" xmlns:tns="http://www.eclipse.org/webtools/tutorials">
- <element name="tutorials">
- <key name="category">
- <selector xpath="tns:category"/>
- <field xpath="@id"/>
- </key>
- <complexType>
- <sequence>
- <element ref="tns:category" minOccurs="1" maxOccurs="unbounded"></element>
- <element ref="tns:tutorial" minOccurs="0" maxOccurs="unbounded"></element>
- </sequence>
- </complexType>
- </element>
-
- <element name="tutorial">
- <complexType>
- <sequence>
- <element ref="tns:abstract" minOccurs="0" maxOccurs="1"></element>
- </sequence>
- <attribute name="link" type="string" use="required"></attribute>
- <attribute name="title" type="string" use="required"></attribute>
- <attribute name="lastUpdated" type="date" use="optional"></attribute>
- <attribute name="datePosted" type="date" use="required"></attribute>
- <attribute name="categories" type="string" use="required"></attribute>
- </complexType>
- </element>
-
- <element name="abstract" type="anyType"></element>
-
- <element name="category">
- <complexType>
- <attribute name="name" type="string" use="required"></attribute>
- <attribute name="id" type="string" use="required"></attribute>
- </complexType>
- </element>
-
-</schema>
\ No newline at end of file
diff --git a/community/schemas/whitepapers.xsd b/community/schemas/whitepapers.xsd
deleted file mode 100644
index d524ec5..0000000
--- a/community/schemas/whitepapers.xsd
+++ /dev/null
@@ -1,19 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.eclipse.org/webtools/whitepapers" xmlns:tns="http://www.eclipse.org/webtools/whitepapers">
- <element name="whitepapers">
- <complexType>
- <sequence>
- <element ref="tns:paper" minOccurs="0" maxOccurs="unbounded"></element>
- </sequence>
- </complexType>
- </element>
-
- <element name="paper">
- <complexType>
- <attribute name="publicationDate" type="date" use="required"></attribute>
- <attribute name="link" type="anyURI" use="required"></attribute>
- <attribute name="title" type="string" use="required"></attribute>
- </complexType>
- </element>
-
-</schema>
\ No newline at end of file
diff --git a/community/stylesheets/community.xsl b/community/stylesheets/community.xsl
deleted file mode 100644
index a45c911..0000000
--- a/community/stylesheets/community.xsl
+++ /dev/null
@@ -1,276 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
- version="1.0"
- xmlns:xalan="http://xml.apache.org/xalan"
- xmlns:events="http://www.eclipse.org/webtools/events"
- xmlns:date="http://exslt.org/dates-and-times"
- exclude-result-prefixes="date events xalan">
-
- <xsl:include href="wtp-common.xsl" />
- <xsl:include href="events.xsl"/>
-
- <xsl:template match="/">
- <xsl:param name="title" select="'wtp community'"/>
- <xsl:param name="subtitle" select="''"/>
- <xsl:param name="root" select="'../..'"/>
- <xsl:call-template name="page">
- <xsl:with-param name="element" select="events:events"/>
- <xsl:with-param name="title" select="$title"/>
- <xsl:with-param name="subtitle" select="$subtitle"/>
- <xsl:with-param name="root" select="$root"/>
- </xsl:call-template>
- </xsl:template>
-
- <xsl:template match="events:events" mode="communityresourcespage">
- <xsl:param name="title" select="'wtp community resources'"/>
- <xsl:param name="subtitle" select="''"/>
- <xsl:param name="root" select="'../..'"/>
- <xsl:call-template name="page">
- <xsl:with-param name="element" select="."/>
- <xsl:with-param name="title" select="$title"/>
- <xsl:with-param name="subtitle" select="$subtitle"/>
- <xsl:with-param name="root" select="$root"/>
- </xsl:call-template>
- </xsl:template>
-
- <xsl:template name="aboutPage">
- <xsl:param name="resources"/>
- <xsl:call-template name="heading">
- <xsl:with-param name="title" select="'Activities and resources from around the WTP community...'"/>
- <xsl:with-param name="alink" select="'top'"/>
- </xsl:call-template>
- <table cellspacing="5" cellpadding="2" border="0">
- <tr>
- <td with="16">    </td>
- <td>
- <p>
- The page is about finding more information about WTP from around the WTP community.
- The community has provided many <xsl:apply-templates select="xalan:nodeset($resources)" mode="body"/>
- that are dedicated to WTP and can help you to make the most of the WTP platform and tools.
- </p>
- <p>
- We'd like these pages to be useful to you - so please open a
- <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Web%20Tools&component=website">bug report</a>
- for any corrections, additions, pointers, or comments!
- </p>
- <p>
- For software licensing, website terms of use, and legal FAQs, please see our
- <a href="http://eclipse.org/legal/main.html" target="_top">legal stuff</a> page.
- </p>
- </td>
- <td width="16"> </td>
- </tr>
- </table>
- </xsl:template>
-
- <xsl:template name="endpage">
- <xsl:param name="root"/>
- <p></p>
- <p>Please see our <a href="http://www.eclipse.org/legal/privacy.html">privacy
- policy</a> and website <a href="http://www.eclipse.org/legal/termsofuse.html">terms
- of use</a>. For problems with the eclipse.org site, please contact the
- <a href="mailto:webmaster@eclipse.org">webmaster</a> or read the
- <a href="{$root}/../webmaster/index.html">webmaster FAQ</a> for answers to common questions!</p>
- </xsl:template>
-
- <xsl:template name="heading">
- <xsl:param name="alink"/>
- <xsl:param name="title"/>
- <xsl:param name="toplink"/>
- <table bgcolor="#0080c0" border="0" cellpadding="2" cellspacing="0" width="100%">
- <tbody>
- <tr>
- <td width="90%">
- <b>
- <font color="#ffffff" face="Arial,Helvetica">
- <a name="{$alink}"><xsl:value-of select="$title"/></a>
- </font>
- </b>
- </td>
- <td width="10%" align="right">
- <xsl:if test="$toplink != ''">
- <a href="{$toplink}">top</a>
- </xsl:if>
- </td>
- </tr>
- </tbody>
- </table>
- </xsl:template>
-
- <xsl:template match="events:events">
- <xsl:param name="root"/>
-
- <xsl:variable name="resources"><xsl:for-each select="document('../communityresources.xml')/resources/resource"><xsl:sort select="@shortTitle"/><xsl:choose><xsl:when test="position() = last()">and <a href="communityresources.html#{@shortTitle}"><xsl:value-of select="@shortTitle"/></a></xsl:when><xsl:otherwise><a href="communityresources.html#{@shortTitle}"><xsl:value-of select="@shortTitle"/></a>, </xsl:otherwise></xsl:choose></xsl:for-each></xsl:variable>
- <xsl:call-template name="aboutPage">
- <xsl:with-param name="resources" select="$resources"/>
- </xsl:call-template>
-
- <!-- Create page sections. -->
- <xsl:call-template name="heading">
- <xsl:with-param name="title" select="'This Month at a Glance'"/>
- <xsl:with-param name="alink" select="'thismonth'"/>
- <xsl:with-param name="toplink" select="'#top'"/>
- </xsl:call-template>
- <br/>
-         An overview of this month's events related to WTP.<br/>
- <xsl:call-template name="createCalendar"/>
- <br/>
- <br/>
- <xsl:call-template name="heading">
- <xsl:with-param name="title" select="'Upcoming WTP Events'"/>
- <xsl:with-param name="alink" select="'upcomingevents'"/>
- <xsl:with-param name="toplink" select="'#top'"/>
- </xsl:call-template>
- <p>
-         WTP past event information can be found on the <a href="pastevents.html">past events page</a>.
- </p><!-- date:format-date(date:date(),'yyyy-MM-dd') -->
- <xsl:variable name="date" select="date:date()"/>
- <xsl:for-each select="events:event[date:year(@enddate) > date:year($date) or (date:year(@enddate) = date:year($date) and date:day-in-year(@enddate) >= date:day-in-year($date))]">
- <xsl:sort select="@startdate"/>
- <xsl:apply-templates select="."/>
- </xsl:for-each>
- <xsl:call-template name="endpage">
- <xsl:with-param name="root" select="$root"/>
- </xsl:call-template>
- </xsl:template>
-
- <xsl:template name="createCalendar"><!-- date:format-date(date:date(), 'MMMMMMMM') -->
- <xsl:variable name="month" select="date:monthName()"/>
- <br/>
- <center>
- <b><font size="+1"><xsl:value-of select="$month"/></font></b>
- <table border="1" width="98%">
- <thead>
- <tr>
- <td width="14%" align="center"><b>Sunday</b></td>
- <td width="14%" align="center"><b>Monday</b></td>
- <td width="14%" align="center"><b>Tuesday</b></td>
- <td width="14%" align="center"><b>Wednesday</b></td>
- <td width="14%" align="center"><b>Thursday</b></td>
- <td width="14%" align="center"><b>Friday</b></td>
- <td width="14%" align="center"><b>Saturday</b></td>
- </tr>
- </thead><!-- date:format-date(date:date(), 'M') -->
- <xsl:variable name="month" select="date:monthInYear()"/><!-- date:format-date(date:date(), 'yyyy-MM-01') -->
- <xsl:variable name="firstofmonth"><xsl:value-of select="date:year()"/>-<xsl:value-of select="date:monthInYear()+1"/>-01</xsl:variable>
- <xsl:variable name="firstweekday" select="date:day-in-week($firstofmonth)"/>
- <xsl:variable name="daysinmonth">
- <xsl:choose>
- <xsl:when test="$month = 1 or $month = 3 or $month = 5 or $month = 7 or $month = 8 or $month = 10 or $month = 12">
- 31
- </xsl:when>
- <xsl:when test="$month = 9 or $month = 4 or $month = 6 or $month = 11">
- 30
- </xsl:when>
- <xsl:when test="$month = 2 and date:leapyear()">
- 29
- </xsl:when>
- <xsl:when test="$month = 2">
- 28
- </xsl:when>
- </xsl:choose>
- </xsl:variable>
-
- <xsl:call-template name="weekloop">
- <xsl:with-param name="startweekday" select="$firstweekday"/>
- <xsl:with-param name="startday" select="'1'"/>
- <xsl:with-param name="daysinmonth" select="number($daysinmonth)"/>
- </xsl:call-template>
- </table>
- </center>
- </xsl:template>
-
- <xsl:template name="weekloop">
- <xsl:param name="daysinmonth"/>
- <xsl:param name="startweekday"/>
- <xsl:param name="startday"/>
-
- <xsl:call-template name="createCalendarWeek">
- <xsl:with-param name="startweekday" select="$startweekday"/>
- <xsl:with-param name="startday" select="$startday"/>
- <xsl:with-param name="daysinmonth" select="$daysinmonth"/>
- </xsl:call-template>
-
- <xsl:if test="$daysinmonth > 8 - $startweekday + $startday">
- <xsl:call-template name="weekloop">
- <xsl:with-param name="startweekday" select="'1'"/>
- <xsl:with-param name="startday" select="8 - $startweekday + $startday"/>
- <xsl:with-param name="daysinmonth" select="$daysinmonth"/>
- </xsl:call-template>
- </xsl:if>
- </xsl:template>
-
- <xsl:template name="createCalendarWeek">
- <xsl:param name="startweekday"/>
- <xsl:param name="startday"/>
- <xsl:param name="daysinmonth"/>
- <tr>
- <xsl:call-template name="weekdayloop">
- <xsl:with-param name="weekday" select="1"/>
- <xsl:with-param name="startweekday" select="$startweekday"/>
- <xsl:with-param name="day" select="$startday"/>
- <xsl:with-param name="daysinmonth" select="$daysinmonth"/>
- </xsl:call-template>
- </tr>
- </xsl:template>
-
- <xsl:template name="weekdayloop">
- <xsl:param name="weekday"/>
- <xsl:param name="startweekday"/>
- <xsl:param name="day"/>
- <xsl:param name="daysinmonth"/>
- <td width="14%" valign="top">
- <xsl:if test="$weekday >= $startweekday and $daysinmonth >= $day">
- <xsl:call-template name="createCalendarDay">
- <xsl:with-param name="date" select="$day"/>
- </xsl:call-template>
- </xsl:if>
- </td>
- <xsl:choose>
- <xsl:when test="$weekday != 7 and $weekday >= $startweekday">
- <xsl:call-template name="weekdayloop">
- <xsl:with-param name="weekday" select="$weekday + 1"/>
- <xsl:with-param name="startweekday" select="$startweekday"/>
- <xsl:with-param name="day" select="$day + 1"/>
- <xsl:with-param name="daysinmonth" select="$daysinmonth"/>
- </xsl:call-template>
- </xsl:when>
- <xsl:when test="$weekday != 7">
- <xsl:call-template name="weekdayloop">
- <xsl:with-param name="weekday" select="$weekday + 1"/>
- <xsl:with-param name="startweekday" select="$startweekday"/>
- <xsl:with-param name="day" select="$day"/>
- <xsl:with-param name="daysinmonth" select="$daysinmonth"/>
- </xsl:call-template>
- </xsl:when>
- </xsl:choose>
- </xsl:template>
-
- <xsl:template name="createCalendarDay">
- <xsl:param name="date"/><!-- date:format-date(date:date(), 'MM') -->
- <xsl:variable name="month" select="date:monthInYear()+1"/><!-- date:format-date(date:date(), 'yyyy') -->
- <xsl:variable name="year" select="date:year()"/>
- <xsl:variable name="thisdate"><xsl:value-of select="$year"/>-<xsl:value-of select="$month"/>-<xsl:value-of select="$date"/></xsl:variable>
- <table cellspacing="0" cellpadding="0" border="0" width="100%">
- <tr>
- <td align="right"><xsl:value-of select="$date"/></td>
- </tr>
- <tr>
- <td>
- <xsl:choose>
- <xsl:when test="/events:events/events:event[date:year(@enddate) >= date:year($thisdate) and date:year(@startdate) <= date:year($thisdate) and date:month-in-year(@enddate) >= date:month-in-year($thisdate) and date:month-in-year(@startdate) <= date:month-in-year($thisdate) and date:day-in-month(@enddate) >= date:day-in-month($thisdate) and date:day-in-month(@startdate) <= date:day-in-month($thisdate)]">
- <xsl:for-each select="/events:events/events:event[date:year(@enddate) >= date:year($thisdate) and date:year(@startdate) <= date:year($thisdate) and date:month-in-year(@enddate) >= date:month-in-year($thisdate) and date:month-in-year(@startdate) <= date:month-in-year($thisdate) and date:day-in-month(@enddate) >= date:day-in-month($thisdate) and date:day-in-month(@startdate) <= date:day-in-month($thisdate)]">
- <li><font size="-2"><a href="#{@link}"><xsl:value-of select="@organization"/></a></font></li>
- </xsl:for-each>
- </xsl:when>
- <xsl:otherwise>
- <br/>
- <br/>
- <br/>
- </xsl:otherwise>
- </xsl:choose>
- </td>
- </tr>
- </table>
- </xsl:template>
-</xsl:stylesheet>
diff --git a/community/stylesheets/communityresources.xsl b/community/stylesheets/communityresources.xsl
deleted file mode 100644
index f2d1799..0000000
--- a/community/stylesheets/communityresources.xsl
+++ /dev/null
@@ -1,390 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
- version="1.0"
- xmlns:xalan="http://xml.apache.org/xalan"
- xmlns:books="http://www.eclipse.org/webtools/books"
- xmlns:articles="http://www.eclipse.org/webtools/articles"
- xmlns:tutorials="http://www.eclipse.org/webtools/tutorials"
- xmlns:whitepapers="http://www.eclipse.org/webtools/whitepapers"
- xmlns:bios="http://www.eclipse.org/webtools/biopages"
- xmlns:date="http://exslt.org/dates-and-times"
- exclude-result-prefixes="xalan date books articles tutorials whitepapers bios">
-
- <xsl:include href="wtp-common.xsl" />
- <xsl:template match="/">
- <xsl:apply-templates mode="communityresourcespage"/>
- </xsl:template>
-
- <xsl:template match="resources" mode="communityresourcespage">
- <xsl:param name="title" select="@title"/>
- <xsl:param name="subtitle" select="''"/>
- <xsl:param name="root" select="'../..'"/>
- <xsl:call-template name="page">
- <xsl:with-param name="element" select="."/>
- <xsl:with-param name="title" select="$title"/>
- <xsl:with-param name="subtitle" select="$subtitle"/>
- <xsl:with-param name="root" select="$root"/>
- </xsl:call-template>
- </xsl:template>
-
- <xsl:template name="aboutPage">
- <xsl:param name="resources"/>
- <xsl:call-template name="heading">
- <xsl:with-param name="title" select="'Resources from around the WTP community...'"/>
- <xsl:with-param name="alink" select="'top'"/>
- </xsl:call-template>
- <table cellspacing="5" cellpadding="2" border="0">
- <tr>
- <td with="16">    </td>
- <td>
- <xsl:apply-templates select="overview" mode="body"/>
- <p>
- The page is about finding more information about WTP from around the WTP community.
- The community has provided many <xsl:apply-templates select="xalan:nodeset($resources)" mode="body"/>
- that are dedicated to WTP and can help you to make the most of the WTP platform and tools.
- </p>
- <p>
- WTP event information can be found on the <a href="community.html">community page</a>.
- </p>
- <p>
- WTP presentation material can be found on the <a href="presentations.html">WTP presentations archive</a>.
- </p>
- <p>
- We'd like these pages to be useful to you - so please open a
- <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Web%20Tools&component=website">bug report</a>
- for any corrections, additions, pointers, or comments!
- </p>
- <p>
- For software licensing, website terms of use, and legal FAQs, please see our
- <a href="http://eclipse.org/legal/main.html" target="_top">legal stuff</a> page.
- </p>
- </td>
- </tr>
- </table>
- </xsl:template>
-
- <xsl:template name="endpage">
- <xsl:param name="root"/>
- <p></p>
- <p>Please see our <a href="http://www.eclipse.org/legal/privacy.html">privacy
- policy</a> and website <a href="http://www.eclipse.org/legal/termsofuse.html">terms
- of use</a>. For problems with the eclipse.org site, please contact the
- <a href="mailto:webmaster@eclipse.org">webmaster</a> or read the
- <a href="{$root}/../webmaster/index.html">webmaster FAQ</a> for answers to common questions!</p>
- </xsl:template>
-
- <xsl:template name="heading">
- <xsl:param name="alink"/>
- <xsl:param name="title"/>
- <xsl:param name="toplink"/>
- <table bgcolor="#0080c0" border="0" cellpadding="2" cellspacing="0" width="100%">
- <tbody>
- <tr>
- <td width="90%">
- <b>
- <font color="#ffffff" face="Arial,Helvetica">
- <a name="{$alink}"><xsl:value-of select="$title"/></a>
- </font>
- </b>
- </td>
- <td width="10%" align="right">
- <xsl:if test="$toplink != ''">
- <a href="{$toplink}">top</a>
- </xsl:if>
- </td>
- </tr>
- </tbody>
- </table>
- </xsl:template>
-
- <xsl:template match="resources">
- <xsl:param name="root"/>
- <xsl:variable name="resources"><xsl:for-each select="resource"><xsl:sort select="@shortTitle"/><xsl:choose><xsl:when test="position() = last()">and <a href="#{@shortTitle}"><xsl:value-of select="@shortTitle"/></a></xsl:when><xsl:otherwise><a href="#{@shortTitle}"><xsl:value-of select="@shortTitle"/></a>, </xsl:otherwise></xsl:choose></xsl:for-each></xsl:variable>
- <xsl:call-template name="aboutPage">
- <xsl:with-param name="resources" select="$resources"/>
- </xsl:call-template>
-
- <!-- Create page sections. -->
- <xsl:for-each select="resource">
- <xsl:call-template name="heading">
- <xsl:with-param name="title" select="@title"/>
- <xsl:with-param name="alink" select="@shortTitle"/>
- <xsl:with-param name="toplink" select="'#top'"/>
- </xsl:call-template>
- <xsl:apply-templates select="overview" mode="body"/>
- <xsl:apply-templates select="document(@src)"/>
- </xsl:for-each>
- <xsl:call-template name="endpage">
- <xsl:with-param name="root" select="$root"/>
- </xsl:call-template>
- </xsl:template>
-
- <xsl:template match="*|@*|text()" mode="communityresourcespage">
- </xsl:template>
-
- <xsl:template match="*|@*|text()">
- </xsl:template>
-
- <xsl:template match="books:books" mode="communityresourcespage">
- <table cellspacing="5" cellpadding="2" border="0">
- <tr>
- <td with="16">  </td>
- <td>
- <p>
- <xsl:for-each select="books:book">
- <table border="0" cellspacing="5" cellpadding="2">
- <tr>
- <td width="25%" valign="top">
- <xsl:if test="@image">
- <xsl:choose>
- <xsl:when test="@link">
- <a href="{@link}" target="_top"><img src="{@image}" border="0"/></a>
- </xsl:when>
- <xsl:otherwise>
- <img src="{@image}"/>
- </xsl:otherwise>
- </xsl:choose>
- </xsl:if>
- </td>
- <td width="75%" valign="top">
- <p>
- <xsl:choose>
- <xsl:when test="@link">
- <a href="{@link}" target="_top"><xsl:value-of select="@title"/></a>
- </xsl:when>
- <xsl:otherwise>
- <xsl:value-of select="@title"/>
- </xsl:otherwise>
- </xsl:choose>
- </p>
- <p>
- by:
- <xsl:for-each select="books:author">
- <xsl:if test="position() = last()">
- and
- </xsl:if>
- <xsl:choose>
- <xsl:when test="@link">
- <a href="{@link}"><xsl:value-of select="@title"/></a>
- </xsl:when>
- <xsl:otherwise>
- <xsl:value-of select="@name"/>
- </xsl:otherwise>
- </xsl:choose>
- <xsl:if test="position() != last()">
- ,
- </xsl:if>
- </xsl:for-each>
- </p>
- <p>
- Publisher:
- <xsl:for-each select="books:publisher">
- <xsl:choose>
- <xsl:when test="@link">
- <a href="{@link}" target="_top"><xsl:value-of select="@name"/></a>
- </xsl:when>
- <xsl:otherwise>
- <xsl:value-of select="@name"/>
- </xsl:otherwise>
- </xsl:choose>
- </xsl:for-each>
- </p>
- </td>
- </tr>
- </table>
- </xsl:for-each>
- </p>
- </td>
- </tr>
- </table>
- </xsl:template>
-
- <!-- Template for articles. This template will create articles that appear as follows:
- > MONTH YEAR - ARTICLE NAME (PUBLICATION) by AUTHOR NAME
- where the article name will link to the article, the publication will link to the
- publication if a link has been provided, and the author name will link to a WTP
- bio page for the author if one as been provided.
- -->
- <xsl:template match="articles:articles" mode="communityresourcespage">
- <p>
- <table border="0" cellspacing="5" cellpadding="2">
- <xsl:for-each select="articles:article">
- <xsl:sort order="descending" select="@publicationDate"/>
- <tr>
- <td valign="top" align="right"><img width="16" height="16" border="0" src="../../images/Adarrow.gif"/></td>
- <xsl:variable name="month" select="date:month-name(@publicationDate)"/>
- <xsl:variable name="year" select="date:year(@publicationDate)"/>
- <td><xsl:value-of select="$month"/> <xsl:value-of select="$year"/>
- </td>
- <td>-</td>
- <td><a href="{@link}" target="_top"><xsl:value-of select="@title"/></a>
- <xsl:choose>
- <xsl:when test="articles:publication/@link">
- (<a href="{articles:publication/@link}" target="_top"><xsl:value-of select="articles:publication/@name"/></a>)
- </xsl:when>
- <xsl:otherwise>
- (<xsl:value-of select="articles:publication/@name"/>)
- </xsl:otherwise>
- </xsl:choose>
- by
- <xsl:for-each select="articles:author">
- <xsl:variable name="authorname" select="@name"/>
- <xsl:choose>
- <xsl:when test="document('../biopages.xml')/bios:bios/bios:bio/@name = $authorname">
- <a href="{document('../biopages.xml')/bios:bios/bios:bio[@name = $authorname]/@link}"><xsl:value-of select="@name"/></a>
- </xsl:when>
- <xsl:otherwise>
- <xsl:value-of select="@name"/>
- </xsl:otherwise>
- </xsl:choose>
- <xsl:if test="position() != last()">
- , 
- </xsl:if>
- </xsl:for-each>
- </td>
- </tr>
- </xsl:for-each>
- </table>
- </p>
- </xsl:template>
-
- <!-- Template for tutorials. This template will create tutorials that appear as follows:
- CATEGORY
- TUTORIAL TITLE
- ABSTRACT
- where the tutorial title is a link to the tutorial and a 'new' or 'updated' image may
- appear next to the title if added or updated within a two week period.
- -->
- <xsl:template match="tutorials:tutorials" mode="communityresourcespage">
- <xsl:variable name="displayChangedDays" select="'30'"/>
- <xsl:variable name="dateToday" select="date:date()"/>
- <p></p>
- <xsl:for-each select="tutorials:category">
- <a href="#{@id}"><xsl:value-of select="@name"/></a>
- <xsl:if test="position() != last()">
-  | 
- </xsl:if>
- </xsl:for-each>
- <xsl:for-each select="tutorials:category">
- <p>
- <a name="{@id}"/>
- <table border="0" cellspacing="5" cellpadding="2">
- <tr>
- <td colspan="2">
- <b><xsl:value-of select="@name"/> Tutorials</b>
- </td>
- </tr>
- <xsl:variable name="categoryId" select="@id"/>
- <xsl:for-each select="/tutorials:tutorials/tutorials:tutorial[contains(@categories,$categoryId)]">
- <xsl:sort select="@title"/>
- <tr>
- <td valign="top" align="right"><img width="16" height="16" border="0" src="../../images/Adarrow.gif"/></td>
- <td>
- <b><a href="{@link}"><xsl:value-of select="@title"/></a></b>
- <!-- Add 'new' or 'updated' images. -->
- <!-- Get days of updated date. -->
- <xsl:variable name="numDaysSincePosted">
- <xsl:call-template name="dateDifference">
- <xsl:with-param name="date1" select="@datePosted"/>
- <xsl:with-param name="date2" select="$dateToday"/>
- </xsl:call-template>
- </xsl:variable>
- <xsl:variable name="numDaysSinceUpdated">
- <xsl:call-template name="dateDifference">
- <xsl:with-param name="date1" select="@lastUpdated"/>
- <xsl:with-param name="date2" select="$dateToday"/>
- </xsl:call-template>
- </xsl:variable>
- <xsl:choose>
- <xsl:when test="$numDaysSincePosted < $displayChangedDays">
- <img src="../../images/new.gif"/>
- </xsl:when>
- <xsl:when test="$numDaysSinceUpdated < $displayChangedDays">
- <img src="../../images/updated.gif"/>
- </xsl:when>
- </xsl:choose>
- </td>
- </tr>
- <tr>
- <td></td>
- <td>
- <xsl:apply-templates select="tutorials:abstract"/>
- </td>
- </tr>
- </xsl:for-each>
- </table>
- </p>
- <hr/>
- </xsl:for-each>
- </xsl:template>
-
- <xsl:template match="tutorials:abstract">
- <xsl:apply-templates select="*|@*|text()" mode="body"/>
- </xsl:template>
-
- <!-- Given two dates, determine the difference between them in days. -->
- <xsl:template name="dateDifference">
- <xsl:param name="date1"/>
- <xsl:param name="date2"/>
-
- <xsl:variable name="numDaysDate1">
- <xsl:call-template name="numDays">
- <xsl:with-param name="date" select="$date1"/>
- </xsl:call-template>
- </xsl:variable>
- <xsl:variable name="numDaysDate2">
- <xsl:call-template name="numDays">
- <xsl:with-param name="date" select="$date2"/>
- </xsl:call-template>
- </xsl:variable>
-
- <xsl:value-of select="$numDaysDate2 - $numDaysDate1"/>
- </xsl:template>
-
- <!-- Given a date, determine the number of days it's been since Jan. 1, 2004 -->
- <xsl:template name="numDays">
- <xsl:param name="date"/>
- <xsl:variable name="day" select="date:day-in-month($date)"/>
- <xsl:variable name="month" select="date:month-in-year($date)"/>
- <xsl:variable name="year" select="date:year($date)"/>
- <xsl:variable name="dayAdd" select="$day"/>
- <xsl:variable name="monthAdd">
- <xsl:choose>
- <xsl:when test="$month = 0">0</xsl:when>
- <xsl:when test="$month = 1">31</xsl:when>
- <xsl:when test="$month = 2">59</xsl:when>
- <xsl:when test="$month = 3">90</xsl:when>
- <xsl:when test="$month = 4">120</xsl:when>
- <xsl:when test="$month = 5">151</xsl:when>
- <xsl:when test="$month = 6">181</xsl:when>
- <xsl:when test="$month = 7">212</xsl:when>
- <xsl:when test="$month = 8">243</xsl:when>
- <xsl:when test="$month = 9">273</xsl:when>
- <xsl:when test="$month = 10">304</xsl:when>
- <xsl:when test="$month = 11">334</xsl:when>
- </xsl:choose>
- </xsl:variable>
- <xsl:variable name="yearAdd" select="($year - 2004) * 365"/>
- <xsl:value-of select="$dayAdd + $monthAdd + $yearAdd"/>
- </xsl:template>
-
- <xsl:template match="whitepapers:whitepapers" mode="communityresourcespage">
- <p>
- <table border="0" cellspacing="5" cellpadding="2">
- <xsl:for-each select="whitepapers:paper">
- <xsl:sort order="descending" select="@publicationDate"/>
- <tr>
- <td valign="top" align="right"><img width="16" height="16" border="0" src="../../images/Adarrow.gif"/></td>
- <xsl:variable name="month" select="date:month-name(@publicationDate)"/>
- <xsl:variable name="year" select="date:year(@publicationDate)"/>
- <td><xsl:value-of select="$month"/> <xsl:value-of select="$year"/>
- </td>
- <td>-</td>
- <td><a href="{@link}" target="_top"><xsl:value-of select="@title"/></a>
- </td>
- </tr>
- </xsl:for-each>
- </table>
- </p>
- </xsl:template>
-</xsl:stylesheet>
diff --git a/community/stylesheets/events.xsl b/community/stylesheets/events.xsl
deleted file mode 100644
index 50b28de..0000000
--- a/community/stylesheets/events.xsl
+++ /dev/null
@@ -1,95 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
- version="1.0"
- xmlns:events="http://www.eclipse.org/webtools/events"
- xmlns:date="http://exslt.org/dates-and-times"
- xmlns:bios="http://www.eclipse.org/webtools/biopages"
- exclude-result-prefixes="date events bios">
-
- <!-- An event will display an optional logo with a link, a date and title with a link,
- and a list of the presentation types for the event with relevant links. -->
- <xsl:template match="events:event">
- <table cellspacing="5" cellpadding="2" border="0">
- <tr>
- <td valign="top" align="right"><img width="16" height="16" border="0" src="../../images/Adarrow.gif"/></td>
- <td><a name="{@link}"/>
- <xsl:if test="@logo">
- <a href="{@link}" target="_top"><img src="{@logo}" border="0"/></a>
- <br/>
- </xsl:if><!-- date:format-date(@startdate,'MMM d, yyyy') -->
- <xsl:call-template name="formatDateForEvent">
- <xsl:with-param name="date" select="@startdate"/>
- </xsl:call-template>
- <xsl:if test="@startdate != @enddate"><!-- date:format-date(@enddate,'MMM d, yyyy') -->
- -
- <xsl:call-template name="formatDateForEvent">
- <xsl:with-param name="date" select="@enddate"/>
- </xsl:call-template>
- </xsl:if>
- , <b><a href="{@link}" target="_top"><xsl:value-of select="@organization"/></a></b>
- </td>
- </tr>
- <tr>
- <td valign="top" align="right"> </td>
- <td valign="top">
- <ul type="square">
- <xsl:for-each select="events:presentation">
- <xsl:sort order="ascending" select="@type"/>
- <xsl:variable name="type" select="@type"/>
- <xsl:variable name="p" select="preceding-sibling::events:presentation"/>
- <xsl:if test="not(preceding-sibling::events:presentation) or preceding-sibling::events:presentation/@type != $type">
- <li>
- <u><xsl:value-of select="$type"/></u>
- <ul>
- <xsl:apply-templates select="../events:presentation[@type=$type]"/>
- </ul>
- </li>
- </xsl:if>
- </xsl:for-each>
- </ul>
- </td>
- </tr>
- </table>
- <hr/>
- </xsl:template>
-
- <!-- A presentation will have an underlined title with an optional link,
- and a list of presenters.
- TODO: Add event resource links. -->
- <xsl:template match="events:presentation">
- <li>
- <xsl:choose>
- <xsl:when test="@link">
- <a href="{@link}" target="_top"><xsl:value-of select="@title"/></a>
- </xsl:when>
- <xsl:otherwise>
- <xsl:value-of select="@title"/>
- </xsl:otherwise>
- </xsl:choose>
- <br/>
- <i>- 
- <xsl:for-each select="events:presenter">
- <xsl:variable name="presentername" select="@name"/>
- <xsl:choose>
- <xsl:when test="document('../biopages.xml')/bios:bios/bios:bio/@name = $presentername">
- <a href="{document('../biopages.xml')/bios:bios/bios:bio[@name = $presentername]/@link}"><xsl:value-of select="@name"/></a>
- </xsl:when>
- <xsl:otherwise>
- <xsl:value-of select="@name"/>
- </xsl:otherwise>
- </xsl:choose>
- <xsl:if test="position() != last()">
- , 
- </xsl:if>
- </xsl:for-each>
- </i>
- </li>
- </xsl:template>
-
- <!-- Given a date put it in the following format MMM d, yyyy
- For example, Sep 1, 2005 -->
- <xsl:template name="formatDateForEvent">
- <xsl:param name="date"/>
- <xsl:value-of select="date:monthAbbreviation($date)"/> <xsl:value-of select="date:dayInMonth($date)"/>, <xsl:value-of select="date:year($date)"/>
- </xsl:template>
-</xsl:stylesheet>
\ No newline at end of file
diff --git a/community/stylesheets/pastevents.xsl b/community/stylesheets/pastevents.xsl
deleted file mode 100644
index bfc6f8e..0000000
--- a/community/stylesheets/pastevents.xsl
+++ /dev/null
@@ -1,127 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
- version="1.0"
- xmlns:xalan="http://xml.apache.org/xalan"
- xmlns:events="http://www.eclipse.org/webtools/events"
- xmlns:date="http://exslt.org/dates-and-times"
- exclude-result-prefixes="date events xalan">
-
- <xsl:include href="wtp-common.xsl" />
- <xsl:include href="events.xsl"/>
-
- <xsl:template match="/">
- <xsl:param name="title" select="'wtp community'"/>
- <xsl:param name="subtitle" select="'past activities'"/>
- <xsl:param name="root" select="'../..'"/>
- <xsl:call-template name="page">
- <xsl:with-param name="element" select="events:events"/>
- <xsl:with-param name="title" select="$title"/>
- <xsl:with-param name="subtitle" select="$subtitle"/>
- <xsl:with-param name="root" select="$root"/>
- </xsl:call-template>
- </xsl:template>
-
- <xsl:template match="events:events" mode="communityresourcespage">
- <xsl:param name="title" select="'wtp community resources'"/>
- <xsl:param name="subtitle" select="''"/>
- <xsl:param name="root" select="'../..'"/>
- <xsl:call-template name="page">
- <xsl:with-param name="element" select="."/>
- <xsl:with-param name="title" select="$title"/>
- <xsl:with-param name="subtitle" select="$subtitle"/>
- <xsl:with-param name="root" select="$root"/>
- </xsl:call-template>
- </xsl:template>
-
- <xsl:template name="aboutPage">
- <xsl:param name="resources"/>
- <xsl:call-template name="heading">
- <xsl:with-param name="title" select="'Activities and resources from around the WTP community...'"/>
- <xsl:with-param name="alink" select="'top'"/>
- </xsl:call-template>
- <table cellspacing="5" cellpadding="2" border="0">
- <tr>
- <td with="16">    </td>
- <td>
- <p>
- The page is about finding more information about WTP from around the WTP community.
- The community has provided many <xsl:apply-templates select="xalan:nodeset($resources)" mode="body"/>
- that are dedicated to WTP and can help you to make the most of the WTP platform and tools.
- </p>
- <p>
- Current WTP activity information can be found on the <a href="community.html">community page</a>.
- </p>
- <p>
- We'd like these pages to be useful to you - so please open a
- <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Web%20Tools&component=website">bug report</a>
- for any corrections, additions, pointers, or comments!
- </p>
- <p>
- For software licensing, website terms of use, and legal FAQs, please see our
- <a href="http://eclipse.org/legal/main.html" target="_top">legal stuff</a> page.
- </p>
- </td>
- <td width="16"> </td>
- </tr>
- </table>
- </xsl:template>
-
- <xsl:template name="endpage">
- <xsl:param name="root"/>
- <p></p>
- <p>Please see our <a href="http://www.eclipse.org/legal/privacy.html">privacy
- policy</a> and website <a href="http://www.eclipse.org/legal/termsofuse.html">terms
- of use</a>. For problems with the eclipse.org site, please contact the
- <a href="mailto:webmaster@eclipse.org">webmaster</a> or read the
- <a href="{$root}/../webmaster/index.html">webmaster FAQ</a> for answers to common questions!</p>
- </xsl:template>
-
- <xsl:template name="heading">
- <xsl:param name="alink"/>
- <xsl:param name="title"/>
- <xsl:param name="toplink"/>
- <table bgcolor="#0080c0" border="0" cellpadding="2" cellspacing="0" width="100%">
- <tbody>
- <tr>
- <td width="90%">
- <b>
- <font color="#ffffff" face="Arial,Helvetica">
- <a name="{$alink}"><xsl:value-of select="$title"/></a>
- </font>
- </b>
- </td>
- <td width="10%" align="right">
- <xsl:if test="$toplink != ''">
- <a href="{$toplink}">top</a>
- </xsl:if>
- </td>
- </tr>
- </tbody>
- </table>
- </xsl:template>
-
- <xsl:template match="events:events">
- <xsl:param name="root"/>
-
- <xsl:variable name="resources"><xsl:for-each select="document('../communityresources.xml')/resources/resource"><xsl:sort select="@shortTitle"/><xsl:choose><xsl:when test="position() = last()">and <a href="communityresources.html#{@shortTitle}"><xsl:value-of select="@shortTitle"/></a></xsl:when><xsl:otherwise><a href="communityresources.html#{@shortTitle}"><xsl:value-of select="@shortTitle"/></a>, </xsl:otherwise></xsl:choose></xsl:for-each></xsl:variable>
- <xsl:call-template name="aboutPage">
- <xsl:with-param name="resources" select="$resources"/>
- </xsl:call-template>
-
- <!-- Create page sections. -->
- <xsl:call-template name="heading">
- <xsl:with-param name="title" select="'Past WTP Activities'"/>
- <xsl:with-param name="alink" select="''"/>
- <xsl:with-param name="toplink" select="'#top'"/>
- </xsl:call-template><!-- date:format-date(date:date(),'yyyy-MM-dd') -->
- <xsl:variable name="date" select="date:date()"/>
- <xsl:for-each select="events:event[date:year(@enddate) < date:year($date) or (date:year(@enddate) = date:year($date) and date:day-in-year(@enddate) <= date:day-in-year($date))]">
- <xsl:sort select="@startdate" order="descending"/>
- <xsl:apply-templates select="."/>
- </xsl:for-each>
- <xsl:call-template name="endpage">
- <xsl:with-param name="root" select="$root"/>
- </xsl:call-template>
- </xsl:template>
-
-</xsl:stylesheet>
diff --git a/community/stylesheets/presentations.xsl b/community/stylesheets/presentations.xsl
deleted file mode 100644
index d909d53..0000000
--- a/community/stylesheets/presentations.xsl
+++ /dev/null
@@ -1,75 +0,0 @@
-<?xml version='1.0' encoding='utf-8'?>
-<xsl:stylesheet xmlns:xsl='http://www.w3.org/1999/XSL/Transform' version='1.0'>
-
-<xsl:output method='xml' indent="yes" />
-
-<xsl:template match='presentations'>
-
-<html>
-<head><title>Eclipse Web Tools Platform Project Presentation Archive</title></head>
-<body>
-
-<h1>wtp presentation archive</h1>
-
-<h2>Introduction</h2>
-
-<p>
-This page lists presentations on WTP and related topics.
-Feel free to reuse this material in your own presentations.
-</p>
-<p>
-If you have a presentation that you'd like to share with the WTP community,
-please contribute it by creating a <a href='https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Web%20Tools'>Bugzilla</a> bug against WTP. Use
-<ul>
-<li><b>Product:</b> Web Tools</li>
-<li><b>Component:</b> website</li>
-<li><b>Severity:</b> enhancement</li>
-</ul>
-Include the title, speaker, venue, and date in the bug comments.
-Attach your presentation to the bug report.
-</p>
-
-<h2>Presentations</h2>
-
-<xsl:apply-templates select='presentation'/>
-
-</body>
-</html>
-
-</xsl:template>
-
-<xsl:template match='presentation'>
-
-<xsl:variable name="file" select="normalize-space(file)"/>
-
-<h3>
-<a name='{$file}' href='{../@base}{$file}'><em><xsl:value-of select='title'/></em></a>
-
-<xsl:apply-templates select='translation'/>
-
-<xsl:apply-templates select='presenter'/>
-
-<xsl:text>, </xsl:text>
-<xsl:value-of select='venue'/>
-
-<xsl:text>, </xsl:text>
-<xsl:value-of select='date'/>
-
-<xsl:text>. </xsl:text>
-</h3>
-
-</xsl:template>
-
-<xsl:template match='translation'>
-<xsl:variable name="file" select="normalize-space(.)"/>
-<xsl:text> [</xsl:text>
-<a href='{../../@base}{$file}'><xsl:value-of select='@language'/></a>
-<xsl:text>]</xsl:text>
-</xsl:template>
-
-<xsl:template match='presenter'>
-<xsl:text>, </xsl:text>
-<xsl:value-of select='.'/>
-</xsl:template>
-
-</xsl:stylesheet>
diff --git a/community/stylesheets/wtp-common.xsl b/community/stylesheets/wtp-common.xsl
deleted file mode 100644
index 178f9b3..0000000
--- a/community/stylesheets/wtp-common.xsl
+++ /dev/null
@@ -1,159 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
-<xsl:template name="infobox">
-<xsl:param name="root"/>
-<xsl:param name="title" />
-<xsl:param name="icon" />
-<xsl:param name="description" />
-<xsl:param name="items" />
-<TABLE cellspacing="0" cellpadding="0" width="275" border="0">
- <TR>
- <TD rowspan="3" height="15" bgcolor="#0080C0" style="padding-top: 5px; padding-bottom: 5px;"><center><SPAN
- style="color: #ffffff; font-weight:bold; font-size: 11px; font-family: Verdana,Arial,Helvetica; padding-left: 5px; padding-right: 5px;"><xsl:value-of select="$title"/></SPAN></center></TD>
- <TD rowspan="1" height="13" width="57%"></TD>
- </TR>
- <TR>
- <TD height="3" bgcolor="#0080C0"><IMG
- src="{$root}/images/c.gif"
- width="1" height="10"/></TD>
- </TR>
-</TABLE>
-<TABLE cellspacing="0" cellpadding="0" width="275" border="0">
- <TR>
- <TD bgcolor="#0080C0"><IMG
- src="{$root}/images/c.gif"
- width="2" height="1"/></TD>
- <TD bgcolor="white"><IMG
- src="{$root}/images/c.gif"
- width="5" height="1"/></TD>
- <TD width="100%">
- <xsl:if test="$icon != ''">
- <img border="0" align="right">
- <xsl:attribute name="src">
- <xsl:value-of select="$icon"/>
- </xsl:attribute>
- </img>
- </xsl:if>
- <xsl:if test="$description">
- <xsl:apply-templates select="$description/*|$description/@*|$description/text()" mode="body"/>
- </xsl:if>
- <TABLE border="0" cellspacing="2">
- <TBODY>
- <!-- xsl:value-of select="$items/*"/-->
- <xsl:for-each select="$items">
-
- <TR>
-
- <!-- TD valign="top">
- <xsl:if test="attribute::icon">
- <img border="0">
- <xsl:attribute name="src">
- <xsl:value-of select="attribute::icon"/>
- </xsl:attribute>
- </img>
- </xsl:if>
- </TD-->
- <TD>
- <xsl:if test="count(child::item) > 0">
-
- <xsl:for-each select="item">
- <xsl:choose>
- <xsl:when test="@link and @title">
- <a>
- <xsl:attribute name="href">
- <xsl:value-of select="attribute::link"/>
- </xsl:attribute>
- <b><xsl:value-of select="attribute::title"/></b>
- </a>
-
- </xsl:when>
- <xsl:otherwise>
- <xsl:if test="@title">
- <b>
- <xsl:value-of select="attribute::title"/>
- </b>
- </xsl:if>
- </xsl:otherwise>
- </xsl:choose>
- <table border="0">
- <tr>
- <xsl:if test="count(child::*) > 0 or child::text()">
- <td valign="top">
- <img src="{$root}/images/Adarrow.gif"/>
- </td>
- <td valign="top">
- <xsl:apply-templates select="*|@*|text()" mode="infobox"/>
- </td>
- </xsl:if>
- </tr>
- </table>
- </xsl:for-each>
- </xsl:if>
- </TD>
- </TR>
-
-
-
- </xsl:for-each>
- </TBODY>
- </TABLE>
-
-</TD>
- <TD bgcolor="white"><IMG
- src="{$root}/images/c.gif"
- width="5" height="1"/></TD>
- <TD bgcolor="#0080C0"><IMG
- src="{$root}/images/c.gif"
- width="2" height="1"/></TD>
- </TR>
- <TR>
- <TD bgcolor="#0080C0" colspan="5"><!--IMG
- src="{$root}/images/c.gif"
- width="1" height="2"/--></TD>
- </TR>
-</TABLE>
-</xsl:template>
-
-<xsl:template name="page">
-<xsl:param name="element"/>
-<xsl:param name="title"/>
-<xsl:param name="subtitle"/>
-<xsl:param name="root"/>
-<html>
- <head>
- <meta content="text/html; charset=iso-8859-1" http-equiv="Content-Type" />
- <link type="text/css" href="{$root}/default_style.css" rel="stylesheet" />
- <link type="text/css" href="{$root}/webtools/wtp.css" rel="stylesheet" />
- <title><xsl:value-of select="$title"/></title>
- </head>
-<body>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody>
- <tr>
- <td align="left" width="60%"><font class="indextop"><xsl:value-of select="$title"/></font><br />
- <font class="indexsub"><xsl:value-of select="$subtitle"/></font></td>
- <td width="40%"> <img src="{$root}/images/Idea.jpg" align="middle" height="86" hspace="50" width="120" /></td>
- </tr>
- </tbody>
- </table>
-<xsl:apply-templates select="$element">
- <xsl:with-param name="root" select="$root"/>
-</xsl:apply-templates>
-</body>
-</html>
-</xsl:template>
-
-
-<xsl:template match="*|@*|text()" mode="infobox">
- <xsl:copy>
- <xsl:apply-templates select="*|@*|text()" mode="infobox"/>
- </xsl:copy>
-</xsl:template>
-
-<xsl:template match="*|@*|text()" mode="body">
- <xsl:copy>
- <xsl:apply-templates select="*|@*|text()" mode="body"/>
- </xsl:copy>
-</xsl:template>
-
-</xsl:stylesheet>
\ No newline at end of file
diff --git a/community/stylesheets/wtp.xsl b/community/stylesheets/wtp.xsl
deleted file mode 100644
index 7ff5234..0000000
--- a/community/stylesheets/wtp.xsl
+++ /dev/null
@@ -1,98 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-
-<!--
- This XSLT sytlesheet formats the pages for the WTP Web site using the standard Eclipse look and feel.
-
- Change Log:
-
- 2005-05-08: Arthur Ryman <ryman@ca.ibm.com>
- - Added column widths to force proper alignment.
-
- 2005-01-01: Arthur Ryman <ryman@ca.ibm.com>
- - Created.
--->
-
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
-
-<xsl:variable name="root">
- <xsl:choose>
- <xsl:when test="/html/head/meta[@name='root']/@content">
- <xsl:value-of select="/html/head/meta[@name='root']/@content"/>
- </xsl:when>
- <xsl:otherwise>
- <xsl:text>../..</xsl:text>
- </xsl:otherwise>
- </xsl:choose>
- </xsl:variable>
-
-<xsl:template match="/">
- <xsl:apply-templates/>
-</xsl:template>
-
-<xsl:template match="html">
- <html>
- <head>
- <meta content="text/html; charset=iso-8859-1" http-equiv="Content-Type" />
- <link type="text/css" href="{$root}/default_style.css" rel="stylesheet" />
- <link type="text/css" href="{$root}/webtools/wtp.css" rel="stylesheet" />
- <xsl:apply-templates select="head/title"/>
- </head>
- <body>
- <xsl:apply-templates select="body/h1" mode="banner"/>
- <table border="0" cellpadding="2" cellspacing="5" width="100%">
- <col width="16" />
- <col width="*" />
- <tbody>
- <xsl:apply-templates select="body/*" mode="body"/>
- </tbody>
- </table>
- </body>
- </html>
-</xsl:template>
-
-<xsl:template match="h1" mode="banner">
- <table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody>
- <tr>
- <td align="left" width="60%"><font class="indextop"><xsl:value-of select="."/></font><br />
- <font class="indexsub"><xsl:value-of select="/html/head/title"/></font></td>
- <td width="40%"> <img src="{$root}/images/Idea.jpg" align="middle" height="86" hspace="50" width="120" /></td>
- </tr>
- </tbody>
- </table>
-</xsl:template>
-
-<xsl:template match="h1" mode="body"/>
-
-<xsl:template match="h2" mode="body">
- <tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica"><xsl:apply-templates/></font></b></td>
- </tr>
-</xsl:template>
-
-<xsl:template match="h3" mode="body">
- <tr>
- <td align="right" valign="top"><img src="{$root}/images/Adarrow.gif" border="0" height="16" width="16" /></td>
- <td><xsl:apply-templates/></td>
- </tr>
-</xsl:template>
-
-<xsl:template match="*" mode="body">
- <tr>
- <td align="right" valign="top"> </td>
- <td valign="top">
- <xsl:copy>
- <xsl:apply-templates select="*|@*|text()"/>
- </xsl:copy>
- </td>
- </tr>
-</xsl:template>
-
-<xsl:template match="*|@*|text()">
- <xsl:copy>
- <xsl:apply-templates select="*|@*|text()"/>
- </xsl:copy>
-</xsl:template>
-
-</xsl:stylesheet>
diff --git a/community/tutorials.xml b/community/tutorials.xml
deleted file mode 100644
index 0c9bcf9..0000000
--- a/community/tutorials.xml
+++ /dev/null
@@ -1,232 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<tutorials xmlns="http://www.eclipse.org/webtools/tutorials"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://www.eclipse.org/webtools/tutorials schemas/tutorials.xsd ">
- <category name="General" id="general"/>
- <category name="Data Tools" id="rdb"/>
- <category name="J2EE" id="j2ee"/>
- <category name="Server/Internet" id="server"/>
- <category name="Structured Source Editing (SSE)" id="sse"/>
- <category name="Web Services" id="ws"/>
- <category name="XML" id="xml"/>
- <tutorial title="Servlet Creation and Deployment on Tomcat"
- link="tutorials/ServletScenario/ServletScenario.html"
- categories="J2EE,Server/Internet"
- datePosted="2005-02-05"
- lastUpdated="2005-02-05">
- <abstract>
- This tutorial will show you how to set up, create, and deploy a simple Hello World
- servlet on the Tomcat server using the Eclipse Web Tools Project.
- </abstract>
- </tutorial>
- <tutorial title="Building a School Schedule Web Application"
- link="tutorials/SchoolSchedule/BuildingAScheduleWebApp.html"
- categories="j2ee,server"
- datePosted="2005-01-24"
- lastUpdated="2005-01-24">
- <abstract>
- In this tutorial you will create a school schedule Web application. This application
- will allow students to input their courses and create a schedule. This tutorial will
- introduce you to JSP's, servlets and the Web Tools Platform project's server tools.
- </abstract>
- </tutorial>
- <tutorial title="Building a CMP Based School Schedule Web Application"
- link="tutorials/cmptutorial/CMPScheduleWebApp.html"
- categories="j2ee,server"
- datePosted="2005-09-11"
- lastUpdated="2005-09-11">
- <abstract>
- This tutorial is similar to the Building a School Schedule Web Application except
- EJBs are used. This tutorial walks the user through developing a Container Managed Entity Bean (CMP)
- to store a simple schedule. A Session Bean is used to query the CMP. Finally, a Servlet and JSP are
- built to serve as the front end.
- </abstract>
- </tutorial>
-
- <tutorial title="Building a Simple EJB Application"
- link="tutorials/ejbtutorial/buildingejbs.html"
- categories="j2ee,server"
- datePosted="2005-02-23"
- lastUpdated="2005-02-23">
- <abstract>
- In this tutorial you will create a simple EJB component and a client web application.
- This tutorial will introduce you to Session beans and the Web Tools Platform project's
- support for XDoclet and server tools.
- </abstract>
- </tutorial>
- <tutorial title="Building and Running a Web Application"
- link="tutorials/BuildJ2EEWebApp/BuildJ2EEWebApp.html"
- categories="j2ee,server"
- datePosted="2004-12-07"
- lastUpdated="2004-24-07">
- <abstract>
- This document is the first in a series of tutorials where we will demonstrate how you can
- use the rich set of tools and APIs that comes with the Web Tools Platform Project. This
- first tutorial will give you a step by step tour of using some the tools for web
- development. For this purpose we will build and run a J2EE web application using WTP tools
- and Apache Tomcat.
- </abstract>
- </tutorial>
- <tutorial title="Cactus Integration in the Web Tools Project"
- link="tutorials/CactusInWTP/CactusInWTP.html"
- categories="j2ee"
- datePosted="2005-05-31"
- lastUpdated="2005-05-31">
- <abstract>
- This article briefly explains Cactus, its common uses and advantages and then provides a
- step-by-step tutorial on how to use the Cactus integration provided by WTP. The article
- assumes that you are familiar with JUnit and the basics of using WTP to build, deploy and
- run web projects.
- </abstract>
- </tutorial>
- <tutorial title="Creating XML files Tutorial"
- link="tutorials/XMLWizards/XMLWizards.html"
- categories="xml"
- datePosted="2004-12-15"
- lastUpdated="2005-09-02">
- <abstract>
- This tutorial demonstrates how you can use XML documents creation wizards that come with
- the Eclipse Web Tools Platform Project. These wizards allow to create XML document from
- DTD or XML Schema.
- </abstract>
- </tutorial>
- <tutorial title="Developing the WTP with Eclipse"
- link="tutorials/DevelopingWTP/DevelopingWTP.html"
- categories="general"
- datePosted="2005-02-21"
- lastUpdated="2005-02-21">
- <abstract>
- This tutorial shows you how to set up your Eclipse environment to develop or modify the
- Web Tools Platform (WTP) project plug-ins. First we will discuss how to connect to the
- CVS repository to check out the WTP source code. We will then set up our target platform.
- Next we will make a modification to the WTP source and run our eclipse application.
- Finally, we will create a patch for our change, which we could submit to the WTP project.
- </abstract>
- </tutorial>
- <tutorial title="Reintroducing the Structured Source Editing Family of Editors"
- link="tutorials/ReintroducingSSE/ReintroducingSSE.html"
- categories="sse"
- datePosted="2005-03-24"
- lastUpdated="2005-03-24">
- <abstract>
- The Structured Source Editing (SSE) family of editors are now available as part of WTP
- 1.0M2. They support editing XML, DTD, HTML, CSS, JavaScript, and JSP files. The SSE
- editors make significant usage of Eclipse frameworks as well as each other. For end users
- it means that they behave consistently with each other as well as with other Eclipse editors.
- </abstract>
- </tutorial>
- <tutorial title="RDB Tutorial"
- link="tutorials/RDBTutorial/RDBTutorial.html"
- categories="rdb"
- datePosted="2005-01-10"
- lastUpdated="2005-02-19">
- <abstract>
- This document walks you through the relational database (RDB) open source features in the
- Eclipse Web Tooling Project. You must have either the RDB open source binaries or the source
- code downloaded from the Eclipse Web site.
- </abstract>
- </tutorial>
- <tutorial title="XML Catalog Tutorial"
- link="tutorials/XMLCatalog/XMLCatalogTutorial.html"
- categories="xml"
- datePosted="2004-12-17"
- lastUpdated="2005-08-10">
- <abstract>
- In this tutorial, we will demonstrate the use of the XML Catalog. Add the Example
- “Editing and validating XML files”. Select File -> New -> Other -> Examples -> Editing and
- Validating XML files.
- </abstract>
- </tutorial>
- <tutorial title="XML Schema Editor Tutorial"
- link="tutorials/XMLSchemaEditor/XMLSchemaEditorTutorial.html"
- categories="xml"
- datePosted="2004-12-23"
- lastUpdated="2004-12-23">
- <abstract>
- This tutorial will use the catalog.xsd from the "Editing and validating XML files" Examples.
- </abstract>
- </tutorial>
- <tutorial title="WSDL Editor Tutorial"
- link="tutorials/WSDLEditor/WSDLEditorTutorial.html"
- categories="ws,xml"
- datePosted="2005-02-21"
- lastUpdated="2005-08-10">
- <abstract>
- In this tutorial we look at using the WSDL Editor to create and modify a WSDL file. We explore
- the basic functionality along with some of the more advanced ones.
- </abstract>
- </tutorial>
- <tutorial title="XML Validation Tutorial"
- link="tutorials/XMLValidation/XMLValidationTutorial.html"
- categories="xml"
- datePosted="2004-12-22"
- lastUpdated="2005-08-10">
- <abstract>
- Eclipse WTP includes validation tools for XML, DTD, and XML Schema. Validation can be invoked
- manually or automatically after every save.
- </abstract>
- </tutorial>
- <tutorial title="Generic Server - Server Definition File Explained"
- link="tutorials/ServerDefinitionExplained/ServerDefinitionExplained.html"
- categories="server"
- datePosted="2005-04-29"
- lastUpdated="2005-04-29">
- <abstract>
- Generic server is a special server and runtime implementation of base server tooling that can
- adjust its behaviour by a server type definition file. Server type definition files are XML
- based meta information files that are introduced using
- "org.eclipse.jst.server.generic.core.serverdefinition" extension point. This document describes
- the different parts of the server definition files.
- </abstract>
- </tutorial>
- <tutorial title="Creating a Bottom-Up Java Web Service"
- link="tutorials/BottomUpWebService/BottomUpWebService.html"
- categories="ws"
- datePosted="2005-06-11"
- lastUpdated="2005-08-11">
- <abstract>
- This document is one of a series of tutorials to demonstrate the use of the Web Services tools
- in the Web Tools Platform Project using the WTP 0.7 drivers. This tutorial shows how to create
- a simple Web service and Web service client from a Java class. The Java class in this scenario
- converts between the Celsius and Farenheit temperature scales.
- </abstract>
- </tutorial>
- <tutorial title="Creating a Top-Down Java Web Service Skeleton from a WSDL Document"
- link="tutorials/TopDownWebService/TopDownWebService.html"
- categories="ws"
- datePosted="2005-06-11"
- lastUpdated="2005-08-11">
- <abstract>
- This document is one of a series of tutorials to demonstrate the use of the Web Services tools
- in the Web Tools Platform Project using the WTP 0.7 drivers. This tutorial shows how to create
- a simple top-down Web service from a WSDL file. The WSDL file in this scenario calculates the
- area of an rectangle.
- </abstract>
- </tutorial>
- <tutorial title="Creating a Java Web Service Client"
- link="tutorials/WebServiceClient/WebServiceClient.html"
- categories="ws"
- datePosted="2005-06-11"
- lastUpdated="2005-08-11">
- <abstract>
- This document is one of a series of tutorials to demonstrate the use of the Web Services tools
- in the Web Tools Platform Project with the WTP 0.7 drivers. This tutorial shows how to create a
- Web serivce client to the deployed Web service created in the tutorial
- <a href="tutorials/TopDownWebService/TopDownWebService.html">Creating a Top-Down Java
- Web Service Skeleton from a WSDL Document</a>.
- </abstract>
- </tutorial>
- <tutorial title="Testing a Web Service with the Web Services Explorer"
- link="tutorials/WebServiceExplorer/WebServiceExplorer.html"
- categories="ws"
- datePosted="2005-06-04"
- lastUpdated="2005-08-04">
- <abstract>
- This document is one of a series of tutorials to demonstrate the use of the Web Services tools
- in the Web Tools Platform Project using the WTP 0.7 drivers. This tutorial shows how to use the
- Web Service Explorer to test a Web service via native WSDL and SOAP. It demonstrates how to use
- the Web Services Explorer to invoke operations on a Web service named " Temperature - Weather "
- as available from XMethods on the internet.
- </abstract>
- </tutorial>
-</tutorials>
diff --git a/community/tutorials/BottomUpWebService/BottomUpWebService.html b/community/tutorials/BottomUpWebService/BottomUpWebService.html
deleted file mode 100644
index 33f1f15..0000000
--- a/community/tutorials/BottomUpWebService/BottomUpWebService.html
+++ /dev/null
@@ -1,454 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../..//default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../..//webtools/wtp.css" type="text/css">
-<title>Bottom Up Web Service Supporting Flexible Projects</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">Bottom Up Web Service Supporting Flexible Projects</font>
-<br>
-<font class="indexsub">Bottom Up Web Service Supporting Flexible Projects</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../..//images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>By Kathy Chan</b>
-
-<br>
- Aug 11, 2005
- <br>
-
-<br>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Introduction</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- This document is one of a series of tutorials to
- demonstrate the use of the Web Services tools in the Web
- Tools Platform Project using the <b>WTP 0.7 drivers</b>.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- This tutorial shows how to create a simple Web service and
- Web service client from a Java class. The Java class in this
- scenario converts between the Celsius and Farenheit
- temperature scales.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Set Up</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Before creating the Web service, there are three
- prerequisites:
- <ol>
-
-<li>
-
-<a href="../InstallTomcat/InstallTomcat.html">
- Install Apache Tomcat
- </a>
-
-</li>
-
-<li>
- Set the <b>J2EE Project Module Preference</b> to
- allow multiple modules per project. Open
- <b>Window -> Preferences... -> J2EE Project Modules Preference
- </b> and check the <b>Allow Multiple modules per project</b> option.
- </li>
-
-<li>Create a Web project</li>
-
-<ol>
-
-<li>
- Open
- <b>
- File -> New -> Other... -> Web -> Dynamic Web Project
- </b>
- to create a new flexible project and Web module.
- </li>
-
-<li>Click <b>Next</b>.</li>
-
-<li>Add a new project by clicking <b>New...</b> beside the project name field.</li>
-
-<li>
- Enter
- <tt>ConverterProject</tt>
- into the
- <b>Name</b>
- field.
- </li>
-
-
-<li>
- Ensure that the
- <b>Target server</b>
- is set to
- <b>Apache Tomcat v5.0</b>
- . If you have not previously configured
- a server runtime use the <b>New...</b>
- button beside the <b>Target server</b> field to
- do so. Result:
- </li>
-
-
-<br>
-
-<img border="0" SRC="images/ConverterProject.JPG">
- <br>
-
-
-<li>Click <b>Finish</b> to go back to the <b>Dynamic Web Project</b> wizard.</li>
-
-
-<li>
- Enter
- <tt>converter</tt>
- into the
- <b>Module Name</b>
- field. Result:
- </li>
-
-
-<br>
-
-<img border="0" SRC="images/converter.JPG">
- <br>
-
-
-<li>
- Click
- <b>Finish</b>
- .
- </li>
-
-<li>
- Say <b>Yes</b> to open the J2EE perspective and you will
- see the <tt>ConverterProject</tt> you created listed
- under <b>Dynamic Web Projects</b> in the <b>Project Explorer</b>
- view. Expand the <tt>ConverterProject</tt> project to
- see its contents.
- </li>
-
-</ol>
-
-</ol>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">
- Creating a bottom up Java bean Web service and Web service
- client
- </font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ol>
-
-<li>
- Import the
- <a href="srcfiles/Converter.java">
- wtp/Converter.java
- </a>
- class into Converter/JavaSource (be sure to preserve the
- package).
- </li>
-
-<li>
- Select the
- <b>Converter.java</b>
- file.
- </li>
-
-<li>
- Open <b>File -> New -> Other... -> Web Services
- -> Web Service</b>.
- </li>
-
-<li>
- Click <b>Next</b>.
- </li>
-
-<li>
- Select
- <b>Generate a proxy</b>
- .
- </li>
-
-<li>
- Select
- <b>Test the Web service</b>
- .
- </li>
-
-<li>
- Select
- <b>Monitor the Web service</b>
- .
- </li>
-
-<li>
- Select
- <b>Overwrite files without warning</b>
- .
- </li>
-
-<li>
- Result:
- </li>
-
-
-<br>
-
-<img border="0" src="images/bu1.JPG">
- <br>
-
-
-<li>
- Click
- <b>Next</b>
- . Result:
- </li>
-
-
-<br>
-
-<img border="0" src="images/bu2.JPG">
- <br>
-
-
-<li>
- Click
- <b>Next</b>
- to get to the
- <b>Service Deployment Configuration Page</b>
- . Result:
- </li>
-
-
-<br>
-
-<img border="0" src="images/bu3.JPG">
- <br>
-
-
-<li>
- If you want to choose a server different from the one
- defaulted by the wizard, click the
- <b>Edit</b>
- button to:
- <a href="../SelectServer/SelectServer.html">
- select a server
- </a>
- .
- </li>
-
-<li>
- Click
- <b>Finish</b>
- .
- </li>
-
-<li>
- It will take about one minute for the wizard to assemble
- the Web service and Web service client Web projects,
- start Apache Tomcat, and deploy the projects to Tomcat.
- Once finished, the generated Sample JSP Web application
- will appear in the browser view, maximized here for
- clarity:
- </li>
-
-
-<br>
-
-<img border="0" src="images/bu4.JPG">
- <br>
-
-
-<li>
- Under
- <b>Methods</b>
- , click on
- <b>celsiusToFarenheit(float)</b>
- .
- </li>
-
-<li>
- Under
- <b>Inputs</b>
- , enter
- <tt>37</tt>
- into the
- <b>celsius</b>
- entry field.
- </li>
-
-<li>
- Click on
- <b>Invoke</b>.
- In the <b>Result</b> view, you should get a response of
- <b>98.6</b>.
- </li>
-
-
-<br>
-
-<img border="0" src="images/bu5.JPG">
- <br>
-
-
-<li>
-
-<p>
- Since you selected the "Monitor Web service" checkbox,
- a TCP/IP port is automatically created on the
- Tomcat server. When you invoke the Web service,
- the <b>TCP/IP Monitor</b> view comes up automatically showing
- the SOAP message request and response. Double-click
- on the <b>TCP/IP Monitor</b> view and select XML view in the drop-down
- combo for both request and response. Result:
- </p>
-
-</li>
-
-
-<br>
-
-<img border="0" src="images/bu6.JPG">
- <br>
-
-
-</ol>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Explanation</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The Web Service wizard is orchestrating the end-to-end
- generation, assembly, deployment, installation and execution
- of the Web service, Web service client, and sample JSPs. In
- this scenario, we clicked Finish on page one. In effect, this
- is allowing the wizard to pick reasonable defaults according
- to the basic high-level choices made on the first page. If
- you repeat this scenario, but use the Next button to work
- through the wizard, you will learn more about the kinds of
- choices that are available and the kinds of defaults being
- assumed.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- After completing this scenario, the WSDL for the Converter
- Web service can be found in
- <tt>Converter/WebContent/wsdl/Converter.wsdl</tt>.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Now that your Web service is running, there are a few
- interesting things you can do with this WSDL file. Examples:
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ol>
-
-<li>
- You can double-click on the WSDL to open the WSDL
- graphical editor.
- </li>
-
-
-<li>
- You can right-click on the WSDL and choose
- <b>
- Web Services -> Test with Web Services Explorer
- </b>
- to test the service.
- </li>
-
-
-<li>
- You can right-click on the WSDL and choose
- <b>Web Services -> Publish WSDL file</b>
- to publish the service to a public UDDI registry.
- </li>
-
-
-<li>
- You can click on the WSDL and choose
- <b>
- New -> Other... -> Web Services ->
- Web Service Client
- </b>
- to generate a Web service client. Note, however, that we
- have already witnessed the internal and visual features
- of the Web Service Client wizard since, in addition to
- being its own wizard, it is quite literally embedded
- within the larger Web Service wizard.
- </li>
-
-</ol>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/community/tutorials/BottomUpWebService/BottomUpWebService.xml b/community/tutorials/BottomUpWebService/BottomUpWebService.xml
deleted file mode 100644
index 34d051d..0000000
--- a/community/tutorials/BottomUpWebService/BottomUpWebService.xml
+++ /dev/null
@@ -1,328 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<?xml-stylesheet type="text/xsl" href="../../../wtp.xsl"?>
-<html>
- <head>
- <meta name="root" content="../../../../" />
- <title>Bottom Up Web Service Supporting Flexible Projects</title>
- </head>
- <body>
- <h1>Bottom Up Web Service Supporting Flexible Projects</h1>
- <p>
- <b>By Kathy Chan</b>
- <br />
- Aug 11, 2005
- <br />
- <br />
- </p>
-
- <h2>Introduction</h2>
- <br></br>
- <p>
- This document is one of a series of tutorials to
- demonstrate the use of the Web Services tools in the Web
- Tools Platform Project using the <b>WTP 0.7 drivers</b>.
- </p>
- <p>
- This tutorial shows how to create a simple Web service and
- Web service client from a Java class. The Java class in this
- scenario converts between the Celsius and Farenheit
- temperature scales.
- </p>
- <br></br>
-
- <h2>Set Up</h2>
- <br></br>
- <p>
- Before creating the Web service, there are three
- prerequisites:
- <ol>
- <li>
- <a href="../InstallTomcat/InstallTomcat.html">
- Install Apache Tomcat
- </a>
- </li>
- <li>
- Set the <b>J2EE Project Module Preference</b> to
- allow multiple modules per project. Open
- <b>Window -> Preferences... -> J2EE Project Modules Preference
- </b> and check the <b>Allow Multiple modules per project</b> option.
- </li>
- <li>Create a Web project</li>
- <ol>
- <li>
- Open
- <b>
- File -> New -> Other... -> Web -> Dynamic Web Project
- </b>
- to create a new flexible project and Web module.
- </li>
- <li>Click <b>Next</b>.</li>
- <li>Add a new project by clicking <b>New...</b> beside the project name field.</li>
- <li>
- Enter
- <tt>ConverterProject</tt>
- into the
- <b>Name</b>
- field.
- </li>
-
- <li>
- Ensure that the
- <b>Target server</b>
- is set to
- <b>Apache Tomcat v5.0</b>
- . If you have not previously configured
- a server runtime use the <b>New...</b>
- button beside the <b>Target server</b> field to
- do so. Result:
- </li>
-
- <br></br>
- <img border="0"
- SRC="images/ConverterProject.JPG" />
- <br></br>
-
- <li>Click <b>Finish</b> to go back to the <b>Dynamic Web Project</b> wizard.</li>
-
- <li>
- Enter
- <tt>converter</tt>
- into the
- <b>Module Name</b>
- field. Result:
- </li>
-
- <br/>
- <img border="0"
- SRC="images/converter.JPG" />
- <br/>
-
- <li>
- Click
- <b>Finish</b>
- .
- </li>
- <li>
- Say <b>Yes</b> to open the J2EE perspective and you will
- see the <tt>ConverterProject</tt> you created listed
- under <b>Dynamic Web Projects</b> in the <b>Project Explorer</b>
- view. Expand the <tt>ConverterProject</tt> project to
- see its contents.
- </li>
- </ol>
- </ol>
- </p>
-
- <h2>
- Creating a bottom up Java bean Web service and Web service
- client
- </h2>
- <br></br>
- <ol>
- <li>
- Import the
- <a
- href="srcfiles/Converter.java">
- wtp/Converter.java
- </a>
- class into Converter/JavaSource (be sure to preserve the
- package).
- </li>
- <li>
- Select the
- <b>Converter.java</b>
- file.
- </li>
- <li>
- Open <b>File -> New -> Other... -> Web Services
- -> Web Service</b>.
- </li>
- <li>
- Click <b>Next</b>.
- </li>
- <li>
- Select
- <b>Generate a proxy</b>
- .
- </li>
- <li>
- Select
- <b>Test the Web service</b>
- .
- </li>
- <li>
- Select
- <b>Monitor the Web service</b>
- .
- </li>
- <li>
- Select
- <b>Overwrite files without warning</b>
- .
- </li>
- <li>
- Result:
- </li>
-
- <br></br>
- <img border="0"
- src="images/bu1.JPG" />
- <br/>
-
- <li>
- Click
- <b>Next</b>
- . Result:
- </li>
-
- <br></br>
- <img border="0"
- src="images/bu2.JPG" />
- <br/>
-
- <li>
- Click
- <b>Next</b>
- to get to the
- <b>Service Deployment Configuration Page</b>
- . Result:
- </li>
-
- <br></br>
- <img border="0"
- src="images/bu3.JPG" />
- <br/>
-
- <li>
- If you want to choose a server different from the one
- defaulted by the wizard, click the
- <b>Edit</b>
- button to:
- <a href="../SelectServer/SelectServer.html">
- select a server
- </a>
- .
- </li>
- <li>
- Click
- <b>Finish</b>
- .
- </li>
- <li>
- It will take about one minute for the wizard to assemble
- the Web service and Web service client Web projects,
- start Apache Tomcat, and deploy the projects to Tomcat.
- Once finished, the generated Sample JSP Web application
- will appear in the browser view, maximized here for
- clarity:
- </li>
-
- <br></br>
- <img border="0"
- src="images/bu4.JPG" />
- <br/>
-
- <li>
- Under
- <b>Methods</b>
- , click on
- <b>celsiusToFarenheit(float)</b>
- .
- </li>
- <li>
- Under
- <b>Inputs</b>
- , enter
- <tt>37</tt>
- into the
- <b>celsius</b>
- entry field.
- </li>
- <li>
- Click on
- <b>Invoke</b>.
- In the <b>Result</b> view, you should get a response of
- <b>98.6</b>.
- </li>
-
- <br></br>
- <img border="0"
- src="images/bu5.JPG" />
- <br/>
-
- <li>
- <p>
- Since you selected the "Monitor Web service" checkbox,
- a TCP/IP port is automatically created on the
- Tomcat server. When you invoke the Web service,
- the <b>TCP/IP Monitor</b> view comes up automatically showing
- the SOAP message request and response. Double-click
- on the <b>TCP/IP Monitor</b> view and select XML view in the drop-down
- combo for both request and response. Result:
- </p>
- </li>
-
- <br></br>
- <img border="0"
- src="images/bu6.JPG" />
- <br/>
-
- </ol>
- <h2>Explanation</h2>
- <p>
- The Web Service wizard is orchestrating the end-to-end
- generation, assembly, deployment, installation and execution
- of the Web service, Web service client, and sample JSPs. In
- this scenario, we clicked Finish on page one. In effect, this
- is allowing the wizard to pick reasonable defaults according
- to the basic high-level choices made on the first page. If
- you repeat this scenario, but use the Next button to work
- through the wizard, you will learn more about the kinds of
- choices that are available and the kinds of defaults being
- assumed.
- </p>
- <p>
- After completing this scenario, the WSDL for the Converter
- Web service can be found in
- <tt>Converter/WebContent/wsdl/Converter.wsdl</tt>.
- </p>
- <p>
- Now that your Web service is running, there are a few
- interesting things you can do with this WSDL file. Examples:
- </p>
- <ol>
- <li>
- You can double-click on the WSDL to open the WSDL
- graphical editor.
- </li>
-
- <li>
- You can right-click on the WSDL and choose
- <b>
- Web Services -> Test with Web Services Explorer
- </b>
- to test the service.
- </li>
-
- <li>
- You can right-click on the WSDL and choose
- <b>Web Services -> Publish WSDL file</b>
- to publish the service to a public UDDI registry.
- </li>
-
- <li>
- You can click on the WSDL and choose
- <b>
- New -> Other... -> Web Services ->
- Web Service Client
- </b>
- to generate a Web service client. Note, however, that we
- have already witnessed the internal and visual features
- of the Web Service Client wizard since, in addition to
- being its own wizard, it is quite literally embedded
- within the larger Web Service wizard.
- </li>
- </ol>
-
- </body>
-</html>
diff --git a/community/tutorials/BottomUpWebService/images/ConverterProject.JPG b/community/tutorials/BottomUpWebService/images/ConverterProject.JPG
deleted file mode 100644
index 410809d..0000000
--- a/community/tutorials/BottomUpWebService/images/ConverterProject.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BottomUpWebService/images/bu1.JPG b/community/tutorials/BottomUpWebService/images/bu1.JPG
deleted file mode 100644
index 24fa8a0..0000000
--- a/community/tutorials/BottomUpWebService/images/bu1.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BottomUpWebService/images/bu2.JPG b/community/tutorials/BottomUpWebService/images/bu2.JPG
deleted file mode 100644
index 539ba08..0000000
--- a/community/tutorials/BottomUpWebService/images/bu2.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BottomUpWebService/images/bu3.JPG b/community/tutorials/BottomUpWebService/images/bu3.JPG
deleted file mode 100644
index 151a5cf..0000000
--- a/community/tutorials/BottomUpWebService/images/bu3.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BottomUpWebService/images/bu4.JPG b/community/tutorials/BottomUpWebService/images/bu4.JPG
deleted file mode 100644
index 22fd574..0000000
--- a/community/tutorials/BottomUpWebService/images/bu4.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BottomUpWebService/images/bu5.JPG b/community/tutorials/BottomUpWebService/images/bu5.JPG
deleted file mode 100644
index 048d867..0000000
--- a/community/tutorials/BottomUpWebService/images/bu5.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BottomUpWebService/images/bu6.JPG b/community/tutorials/BottomUpWebService/images/bu6.JPG
deleted file mode 100644
index 4b23fac..0000000
--- a/community/tutorials/BottomUpWebService/images/bu6.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BottomUpWebService/images/converter.JPG b/community/tutorials/BottomUpWebService/images/converter.JPG
deleted file mode 100644
index 00f23ee..0000000
--- a/community/tutorials/BottomUpWebService/images/converter.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BottomUpWebService/srcfiles/Converter.java b/community/tutorials/BottomUpWebService/srcfiles/Converter.java
deleted file mode 100644
index 3902400..0000000
--- a/community/tutorials/BottomUpWebService/srcfiles/Converter.java
+++ /dev/null
@@ -1,14 +0,0 @@
-package wtp;
-
-public class Converter
-{
- public float celsiusToFarenheit ( float celsius )
- {
- return (celsius * 9 / 5) + 32;
- }
-
- public float farenheitToCelsius ( float farenheit )
- {
- return (farenheit - 32) * 5 / 9;
- }
-}
diff --git a/community/tutorials/BuildJ2EEWebApp/BuildJ2EEWebApp.html b/community/tutorials/BuildJ2EEWebApp/BuildJ2EEWebApp.html
deleted file mode 100644
index be4f625..0000000
--- a/community/tutorials/BuildJ2EEWebApp/BuildJ2EEWebApp.html
+++ /dev/null
@@ -1,388 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html><head><title>Web Tools Platform</title>
-
-<link href="../../../../../default_style.css" rel="stylesheet"></head>
-
-
-<body>
-
-<div align="right">
- <font face="Times New Roman, Times, serif" size="2">Copyright © 2004 Naci Dai.</font>
- <table border="0" cellpadding="2" cellspacing="0" width="100%">
- <tbody>
- <tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font face="Arial,Helvetica"><font color="#ffffff">Eclipse
- Article</font></font></b></td>
- </tr>
- </tbody>
- </table>
-</div>
-<div align="left">
- <h1 title="RCP Tutorial"><img src="../../../../../images/Idea.jpg" align="middle" height="86" width="120"></h1>
-</div>
-<h1 align="center">WTP Tutorials Building and Running a Web Application</h1>
-<p class="summary">This document is the first in a series of tutorials where
- we will demonstrate how you can use the rich set of tools and APIs that comes
- with the Web Tools Platform Project. This first tutorial will give you a step
- by step tour of using some the tools for web development. For this purpose
-we will build and run a J2EE web application using WTP tools and Apache Tomcat. </p>
-<p><b>By Naci Dai, Eteration A.S.</b><br>
-<font size="-1">December 7, 2004</font></p>
-<div align="right">
- <table border="0" cellpadding="2" cellspacing="0" width="100%">
- <tbody>
- <tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font face="Arial,Helvetica"><font color="#ffffff">Introduction</font></font></b></td>
- </tr>
- </tbody>
- </table>
-</div>
-<p>This document is the first in a series of tutorials where we will demonstrate
- how you can use the rich set of tools and APIs that comes with the Web Tools
- Platform Project. This first tutorial will give you a step by step tour of
- using some the tools for web development. For this purpose we will build and
-run a J2EE web application using <a href="../../../">WTP</a> tools and <a href="http://jakarta.apache.org/tomcat" target="_top">Apache Tomcat</a>. </p>
-<div align="right">
- <table border="0" cellpadding="2" cellspacing="0" width="100%">
- <tbody>
- <tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font face="Arial,Helvetica"><font color="#ffffff">Getting
- Started</font></font></b></td>
- </tr>
- </tbody>
- </table>
-</div>
-
-<p><h3>Java Development Kit</h3>
- You will need a Java Development Kit (JDK) version 1.4.2 and above as Eclipse
- 3.1 requires it. Java Runtime Environment (JRE) is sufficient for Eclipse
- but it will not be suitable for web application development. You can get
- latest JDK from <a href="http://java.sun.com" target="_top">Sun</a>.<br>
-</p>
-<p>
-<img src="images/note.gif" alt="Note: " height="13" width="62">
-Most server
- runtimes require tools, such as the java compiler (found in tools.jar), that
-are only found in the JDK but not the JRE.</p>
-
-<p>
-<h3>Server Runtime</h3>
-We are going to be build a web application that runs on a server. To do this
-tutorial you will need a server runtime that is supported by WTP. <a href="http://jakarta.apache.org/tomcat" target="_top">Apache Tomcat</a>,
-<a href="http://jonas.objectweb.org" target="_top">ObjectWeb Jonas</a>, and <a href="http://www.jboss.org" target="_top">JBoss</a> are some of the OSS licensed server runtimes supported
-by WTP. You will need to download and install the server runtime before you can
-start working with WTP. It does not come with one. Later you will learn how to
-tell WTP to use your preferred server runtime.<br>
-</p>
-
-
-<h3>Eclipse and other Eclipse Projects</h3>
-<p>Obviously, you will need an eclipse installation. The Eclipse driver used
- in this tutorial is eclipse-SDK-3.1M3-linux-gtk.zip. You can find a suitable
- driver for your platform at here. WTP uses components from other eclipse projects:
- The eclipse modeling framework, emf, java emf model, jem, are used to define
- models for artifacts defined in many java, w3c, xml and j2ee standards; The
- graphical editing framework, gef, is used to provide graphical editing capabilities
- for xml, xsd and wsdl editors, etc. You can obtain these components from their
-projects.</p>
-<ul>
- <li><a href="http://www.eclipse.org/emf" target="_top">EMF</a></li>
- <li><a href="http://www.eclipse.org/gef" target="_top">GEF</a></li>
- <li><a href="http://www.eclipse.org/vep" target="_top">JEM</a></li>
-</ul>
-<h3>Web Tools Platform</h3>
-<p>You will need to download the full WTP package that is used in this tutorial
-from <a href="http://download.eclipse.org/webtools/downloads">wtp downloads</a>. You will need a WTP runtime.</p>
-<p>Once you have everything downloaded, install JDK and your favorite server
- runtime, and unzip eclipse, emf, gef, jem and wtp zip files to a folder. You
-are ready to go!</p>
-<div align="right">
- <table border="0" cellpadding="2" cellspacing="0" width="100%">
- <tbody>
- <tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font face="Arial,Helvetica"><font color="#ffffff">Setup</font></font></b></td>
- </tr>
- </tbody>
- </table>
-</div>
-
-<p>
-<h3>Preferences</h3>
-
-<p>After you launch eclipse for the first time, but before we can build our first
- web application, we need to do a little eclipse house keeping: If it is not
- already defined, you will need to set the Java preferences to point to your
- JDK installation (see figure). You should have obtained the latest JDK from
-<a href="http://java.sun.com" target="_top">Sun</a>.</p>
-<p><img src="images/figure1.png" width="392" height="365"></p>
-<h3>Choose a Server Runtime Environment</h3>
-<p>This step involves changing or creating the settings for Installed Server
- Runtimes. During web application development, we will need a server runtime
- environment to test, debug and run our project. We begin by telling wtp what
- our server runtime is, and where it is located. A “server runtime environment” is
- not a server. It provides the environment, libraries and infrastructure that
- a “server” needs. A server is an instance of the server runtime
- that can host our web applications and other server-side components. To define
-a server runtime, we need to visit the appropriate Preferences page:</p>
-<p><img src="images/figure2.png" width="404" height="402"></p>
-<p>Here you will find a list of server runtimes that have been defined previously.
- You can choose a server runtime and change its properties. To add a new one
- click “Add…”. A wizard will popup and display a list of server
- runtimes that are supported by WTP. Choose your server runtime from the list.
- Jonas and JBoss are currently supported under the “Generic Server Runtime”.
- Basic “J2EE Runtime Library” is not a true server runtime, but
- can be used for coding support only. It does not provide a server instance
-that can be used to run web artifacts.</p>
-<p>After you click “Next”, you will have to choose the JDK and the
- folder where you have installed your server runtime. Of course, based on your
- choice of the server runtime, you will be asked to provide different properties.
- Click finish. Now we can do the fun part.<br>
-<img src="images/figure3.png" width="317" height="364"></p>
-<p> <img src="images/note.gif" alt="Note: " height="13" width="62"> We
- chose Apache Tomcat. You can also choose another server such as ObjectWeb Jonas.
- If you would like to use them as your runtime, select the “Generic Server”,
- and follow the wizard to define the properties for Jonas, JBoss or Weblogic.
- There are differences between for server runtimes; Apache Tomcat provides dynamic
- development support; i.e: the ability to run the web application from the eclipse
- project without the need to publish the artifacts to a server. Generic server
- does not support dynamic development, but it will automatically publish the
-artifacts (your web application) to the server when you run.</p>
-<div align="right">
- <table border="0" cellpadding="2" cellspacing="0" width="100%">
- <tbody>
- <tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font color="#FFFFFF"face="Arial,Helvetica">Developing
- the Application</font></b></td>
- </tr>
- </tbody>
- </table>
-</div>
-
-<p>In this section we will create a J2EE web application that contains typical
- components such as servlets and JSPs. We will:<br>
- •
- Create a project with a web module<br>
- •
- Create a servlet<br>
- •
- Edit deployment descriptor<br>
- •
-Create and edit a JSP
-<p><h3>Create a J2EE Web Project with a web module</h3>
-<p>Go to New->Project. Choose Web category from the list of available wizards
- to create a new eclipse resource. You will find two project types available
- under this category. Simple Web Project is a basic Eclipse resource project
- that can be associated with a server. We are interested in creating a J2EE
- Web Application, so we will choose the J2EE Web Project here:<br>
-<img src="images/figure4.png" width="327" height="380"></p>
-<p>A J2EE Web Project is a type of Java project that has been initialized to
- host a server-side application. It needs to be associated with a Target Server. <br>
- A target server provides the container which will be used to execute our web
- application. Specifically, it will provide a set of libraries (jars), that
- are added to the project classpath, which are needed to compile our custom
- classes. E.g.: to create a new Servlet, we need javax.servlet.* packages. These
- are not a part of the JDK libraries. Server runtime provides them to the project.
- If yiu have skipped the previos step where we defined a server runtime, you
- will get a chance to define one here by clicking on the New….<br>
- Make sure that “Add module to an EAR project” is not selected.
- We will create a standalone web application that can be deployed as a standard
- web module.<br>
- Finally, we will change the context root to “tutorial”. This is
- used when you access the web application with a URL, i.e. http://localhost:8080/tutorial <br>
- <img src="images/figure5.png" width="493" height="486"> </p>
-<p>When the wizard completes its tasks, you will find that it has create a new
- Java Project and has initialized it so that you can start with your development
- right away: It has created a java source folder. You will add your custom java
- packages and classes here. It has defined the classpath (JRE and Tomcat) so
- that you will have J2EE libraries in your project classpath. It has created
- a resource folder named “Web Content”, which mimics the standard
- WAR structure from the J2EE specification. It will contain the web resources
- that will be packaged with your J2EE web module. All artifacts inside this
- folder are accessible from the Web Application context.</p>
-<p><img src="images/figure6.png" width="577" height="416"></p>
-<p><h3>The Design</h3>
-<p>This is a simple Hello WTP application. We will call a simple “snoop
- servlet” that will display information about the client browser in a
- JSP file.<br>
-<img src="images/figure7.png" width="439" height="383"> </p>
-<p><h3>Create a Servlet</h3>
- <p>Go to New->Class. Create a new Java class that is a subclass of the standard
-javax.servlet.http.HttpServlet:</p>
- <p><br>
- <img src="images/figure8.png" width="490" height="555"></p>
-<p>Add the code provided in Listing 1 to the servlet:</p>
- <p><b>Listing 1. SnoopServlet.java</b></p>
-<pre>package org.eclipse.wtp.tutorial;
-
-import java.io.IOException;
-
-import javax.servlet.ServletException;
-import javax.servlet.http.HttpServlet;
-import javax.servlet.http.HttpServletRequest;
-import javax.servlet.http.HttpServletResponse;
-
-public class SnoopServlet extends HttpServlet {
- public void doGet(HttpServletRequest req, HttpServletResponse resp)
- throws ServletException, IOException {
- String userAgent = req.getHeader("user-agent");
- String clientBrowser = "Not known!";
- if( userAgent != null)
- clientBrowser = userAgent;
- req.setAttribute("client.browser",clientBrowser );
- req.getRequestDispatcher("/showBrowser.jsp").forward(req,resp);
- }
-}</pre>
-
-<p>
-<h3>Edit Web Module Deployment Descriptor</h3>
-Web modules in J2EE has a deployment descriptor where you configure the web application
-and its components. This deployment descriptors is called the web.xml. According
-to the J2EE specification, it must be located in the WEB-INF folder. web.xml
-must have definitions for the Servlet and the Servlet URI mapping. Enter the
-following lines into web.xml:</p>
-
-<p><b>Listing 2. Deployment Descriptor web.xml
-</b></p>
-<pre> <servlet><br> <servlet-name>Snoop Servlet</servlet-name><br> <servlet-class>org.eclipse.wtp.tutorial.SnoopServlet</servlet-class><br> </servlet><br> <servlet-mapping><br> <servlet-name>Snoop Servlet</servlet-name><br> <url-pattern>/snoop/*</url-pattern><br> </servlet-mapping><br>
-</pre>
-
-<p>
-You can obtain code assist from the WTP XML editor during this process by hitting
-[Ctrl]+[Space] as usual.</p>
-<p><img src="images/figure9.png" width="380" height="160"></p>
-
-
-
-<h3>Add JSP</h3>
-<p>
-Go to New->File. Select the WebContent folder and enter showBrowser.jsp as
-the file name.
-</p>
-<p><img src="images/figure10.png" width="381" height="580"></p>
-<p>Our JSP file will be opened with a “JSP Source Page Editor”. Hit
- [Ctrl]+[Space] and choose html template. You can get HTML, JavaScript, JSP
-and Java code assist in a JSP Editor.</p>
-<p><img src="images/figure11.png" width="312" height="206"></p>
-<p>JSP Source Page Editor also provides java code assist. Try the following inside
-a JSP expression:</p>
-<p><img src="images/figure12.png" width="385" height="80"></p>
-<p>At the end your JSP should have the following code </p>
-<p><img src="images/tip.gif" alt="Tip: " height="13" width="62">Use
- the table template</p>
-<p><b>Listing 3. showBrowser.jsp</b></p>
-<pre><html><br><head><title>Show Browser</title></head><br><body><br><table border="1"><br> <tr> <th>Header</th><th>Value</th><br> </tr><br> <tr><br> <td>user-agent</td><br> <td><%= request.getAttribute("client.browser")%></td><br> </tr><br></table><br></body><br></html></pre>
-
-
-<h3>Exploring our work:</h3>
-<p>Go to the menu Window >Show View and select the Project Explorer view from
-the J2EE category.</p>
-
-<p><img src="images/figure13.png" width="295" height="160"></p>
-<p>Project explorer is a smart navigator that knows about the web and J2EE artifacts.
- You will be able to browse your web module, deployment descriptors and the
- contents of these. For example, we can navigate to the deployment descriptor
-and observer our servlet and its mapping.</p>
-<p><img src="images/figure14.png" width="284" height="258"></p>
-<p> </p>
-<div align="right">
- <table border="0" cellpadding="2" cellspacing="0" width="100%">
- <tbody>
- <tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font color="#FFFFFF"face="Arial,Helvetica">Running
- the Application</font></b></td>
- </tr>
- </tbody>
- </table>
-</div>
-
-
-
-<p>In this section we will run our recently developed web application on a server.
- In order to do this, we will:<br>
- •
- Create a server<br>
- •
- Add our web module to a server<br>
- •
- Run the server<br>
- •
- Run the web application.<br>
-</p>
-<h3>Project has Server Properties</h3>
-<p>In the Java Package explorer or the J2EE Project Explorer, highlight your
- project name WTP-Tutorial-I and using the right-click menu (mouse menu) choose
- properties. Alternatively, you can hit [Alt]+[Enter]. This will display project
- properties window. Here we can set the target runtime and the default server
- for the project. Remember that we have chosen the target runtime when we created
- the project. This runtime has provided the classpath for the project. You can
- choose a different runtime here. This will change the libraries that are used
- to compile your application. Here we can also choose a default server. The
- default server is the server on which our application will be deployed and
- run. If you have not previously defined a server as set it as default, you
- will see a message in the properties view. To create a server you will have
-to cancel this window and come back to it after you have created the server.</p>
-<p><img src="images/figure15.png" width="429" height="255"></p>
-<p> </p>
-<h3>Create a Server</h3>
-<p>
-Servers can be created using the Server View. To open a server view go to Window->Show
-View->Other…, and choose the Servers under the Server category.</p>
-<p><img src="images/figure16.png" width="296" height="421"></p>
-<p>The server view allows you to create servers for the currently installed server
-runtime environments. Use the right click menu to create a new server. In the
- following wizard, choose the server address where you will deploy (publish)
- your web module. You will also have to choose the server type and, if you have
- defined more than one installed environment for this server (see preferences),
-choose the server runtime. When you click finish, you have a Server!</p>
-<table width="100%" border="0">
- <tr>
- <td><img src="images/figure17.png" width="350" height="63"></td>
- <td><img src="images/figure18.png" width="363" height="413"></td>
- </tr>
-</table>
-<p>Now you can go back to the project properties and set your default server.</p>
-<table width="100%" border="0">
- <tr>
- <td><img src="images/figure19.png" width="389" height="121"></td>
- <td><img src="images/figure20.png" width="370" height="274"></td>
- </tr>
-</table>
-<h3>Start the Server</h3>
-<p> In the server view, do a menu-click on your server and choose start, or you
- can simply click the start button. You will see the “Status” of
- the server from Stopped to “Starting”, and when the server is ready
-it will change its status to "Started".</p>
-<p><img src="images/figure21.png" width="353" height="253"> </p>
-<h3> </h3>
-<h3>Running the Application</h3>
-<p> Open your favorite browser and type http://localhost:8080/tutorial/snoop.</p>
-<p><img src="images/figure22.png" width="462" height="149"></p>
-<p><h3>Can it be easier?</h3>
- <p>Well, now that you have been through all this trouble to run your application,
- did you know that you could have done all this with almost just one click?
- Try to select you WebContents on try “Run on server…”.
- The web application will popup inside the WTP web browser in almost an instant.
- You can then try to call your servlet as usual.<br>
-</p>
- <table width="100%" border="0">
- <tr>
- <td><img src="images/figure23.png" width="360" height="91"></td>
- <td><img src="images/figure24.png" width="463" height="323"></td>
- </tr>
- </table>
- <p> </p>
- <h3>Conclusion</h3>
-<p>In this tutorial, we looked at what is necessary to create a
-simple web application. The next part will show
- how we can debug our web application and monitor http traffic.
-</p>
-
-<h3><br>
-</h3>
-<p><small>Java and all Java-based trademarks and logos are trademarks or
-registered trademarks of Sun Microsystems, Inc. in the United States, other
-countries, or both.</small></p>
-<p><small>Other company, product, and service names may be trademarks or service
-marks of others.</small></p>
-
-</body></html>
\ No newline at end of file
diff --git a/community/tutorials/BuildJ2EEWebApp/images/figure1.png b/community/tutorials/BuildJ2EEWebApp/images/figure1.png
deleted file mode 100644
index c242404..0000000
--- a/community/tutorials/BuildJ2EEWebApp/images/figure1.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BuildJ2EEWebApp/images/figure10.png b/community/tutorials/BuildJ2EEWebApp/images/figure10.png
deleted file mode 100644
index 1ebf1b6..0000000
--- a/community/tutorials/BuildJ2EEWebApp/images/figure10.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BuildJ2EEWebApp/images/figure11.png b/community/tutorials/BuildJ2EEWebApp/images/figure11.png
deleted file mode 100644
index 2bcc637..0000000
--- a/community/tutorials/BuildJ2EEWebApp/images/figure11.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BuildJ2EEWebApp/images/figure12.png b/community/tutorials/BuildJ2EEWebApp/images/figure12.png
deleted file mode 100644
index a3b81ca..0000000
--- a/community/tutorials/BuildJ2EEWebApp/images/figure12.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BuildJ2EEWebApp/images/figure13.png b/community/tutorials/BuildJ2EEWebApp/images/figure13.png
deleted file mode 100644
index 4415e41..0000000
--- a/community/tutorials/BuildJ2EEWebApp/images/figure13.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BuildJ2EEWebApp/images/figure14.png b/community/tutorials/BuildJ2EEWebApp/images/figure14.png
deleted file mode 100644
index c00642e..0000000
--- a/community/tutorials/BuildJ2EEWebApp/images/figure14.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BuildJ2EEWebApp/images/figure15.png b/community/tutorials/BuildJ2EEWebApp/images/figure15.png
deleted file mode 100644
index be7a0f0..0000000
--- a/community/tutorials/BuildJ2EEWebApp/images/figure15.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BuildJ2EEWebApp/images/figure16.png b/community/tutorials/BuildJ2EEWebApp/images/figure16.png
deleted file mode 100644
index 01a4e4e..0000000
--- a/community/tutorials/BuildJ2EEWebApp/images/figure16.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BuildJ2EEWebApp/images/figure17.png b/community/tutorials/BuildJ2EEWebApp/images/figure17.png
deleted file mode 100644
index d17f8de..0000000
--- a/community/tutorials/BuildJ2EEWebApp/images/figure17.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BuildJ2EEWebApp/images/figure18.png b/community/tutorials/BuildJ2EEWebApp/images/figure18.png
deleted file mode 100644
index 5813942..0000000
--- a/community/tutorials/BuildJ2EEWebApp/images/figure18.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BuildJ2EEWebApp/images/figure19.png b/community/tutorials/BuildJ2EEWebApp/images/figure19.png
deleted file mode 100644
index 8f3804b..0000000
--- a/community/tutorials/BuildJ2EEWebApp/images/figure19.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BuildJ2EEWebApp/images/figure2.png b/community/tutorials/BuildJ2EEWebApp/images/figure2.png
deleted file mode 100644
index fbacb3b..0000000
--- a/community/tutorials/BuildJ2EEWebApp/images/figure2.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BuildJ2EEWebApp/images/figure20.png b/community/tutorials/BuildJ2EEWebApp/images/figure20.png
deleted file mode 100644
index 0db0428..0000000
--- a/community/tutorials/BuildJ2EEWebApp/images/figure20.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BuildJ2EEWebApp/images/figure21.png b/community/tutorials/BuildJ2EEWebApp/images/figure21.png
deleted file mode 100644
index 8236929..0000000
--- a/community/tutorials/BuildJ2EEWebApp/images/figure21.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BuildJ2EEWebApp/images/figure22.png b/community/tutorials/BuildJ2EEWebApp/images/figure22.png
deleted file mode 100644
index cd87327..0000000
--- a/community/tutorials/BuildJ2EEWebApp/images/figure22.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BuildJ2EEWebApp/images/figure23.png b/community/tutorials/BuildJ2EEWebApp/images/figure23.png
deleted file mode 100644
index 9aebfd4..0000000
--- a/community/tutorials/BuildJ2EEWebApp/images/figure23.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BuildJ2EEWebApp/images/figure24.png b/community/tutorials/BuildJ2EEWebApp/images/figure24.png
deleted file mode 100644
index 28e50d3..0000000
--- a/community/tutorials/BuildJ2EEWebApp/images/figure24.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BuildJ2EEWebApp/images/figure3.png b/community/tutorials/BuildJ2EEWebApp/images/figure3.png
deleted file mode 100644
index 3edf5a2..0000000
--- a/community/tutorials/BuildJ2EEWebApp/images/figure3.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BuildJ2EEWebApp/images/figure4.png b/community/tutorials/BuildJ2EEWebApp/images/figure4.png
deleted file mode 100644
index d849c15..0000000
--- a/community/tutorials/BuildJ2EEWebApp/images/figure4.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BuildJ2EEWebApp/images/figure5.png b/community/tutorials/BuildJ2EEWebApp/images/figure5.png
deleted file mode 100644
index af46b4f..0000000
--- a/community/tutorials/BuildJ2EEWebApp/images/figure5.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BuildJ2EEWebApp/images/figure6.png b/community/tutorials/BuildJ2EEWebApp/images/figure6.png
deleted file mode 100644
index 2ba2754..0000000
--- a/community/tutorials/BuildJ2EEWebApp/images/figure6.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BuildJ2EEWebApp/images/figure7.png b/community/tutorials/BuildJ2EEWebApp/images/figure7.png
deleted file mode 100644
index cb8fc33..0000000
--- a/community/tutorials/BuildJ2EEWebApp/images/figure7.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BuildJ2EEWebApp/images/figure8.png b/community/tutorials/BuildJ2EEWebApp/images/figure8.png
deleted file mode 100644
index a1df9b1..0000000
--- a/community/tutorials/BuildJ2EEWebApp/images/figure8.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BuildJ2EEWebApp/images/figure9.png b/community/tutorials/BuildJ2EEWebApp/images/figure9.png
deleted file mode 100644
index 52b0362..0000000
--- a/community/tutorials/BuildJ2EEWebApp/images/figure9.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BuildJ2EEWebApp/images/note.gif b/community/tutorials/BuildJ2EEWebApp/images/note.gif
deleted file mode 100644
index f6260db..0000000
--- a/community/tutorials/BuildJ2EEWebApp/images/note.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/BuildJ2EEWebApp/images/tip.gif b/community/tutorials/BuildJ2EEWebApp/images/tip.gif
deleted file mode 100644
index 77b2451..0000000
--- a/community/tutorials/BuildJ2EEWebApp/images/tip.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/CactusInWTP/CactusInWTP.html b/community/tutorials/CactusInWTP/CactusInWTP.html
deleted file mode 100644
index 9f6e5e3..0000000
--- a/community/tutorials/CactusInWTP/CactusInWTP.html
+++ /dev/null
@@ -1,173 +0,0 @@
-<html>
-
-<head>
-<meta HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1252">
-<title>Cactus Integration in WTP</title>
-<link rel="stylesheet" href="../../../../default_style.css">
-</head>
-
-<body LINK="#0000ff" VLINK="#800080">
-<div align="right"> <font face="Times New Roman, Times, serif" size="2">Copyright
- © BEA Systems, Inc</font>
- <table border=0 cellspacing=0 cellpadding=2 width="100%">
- <tr>
- <td align=LEFT valign=TOP colspan="2" bgcolor="#0080C0"><b><font face="Arial,Helvetica"><font color="#FFFFFF"> </font></font></b></td>
- </tr>
- </table>
-</div>
-<div align="left">
- <h1><img src="../../../../images/Idea.jpg" height=86 width=120 align=CENTER></h1>
-</div>
-<p> </p>
-
-<h1 ALIGN="CENTER">Cactus Integration in the Web Tools Project</h1>
-
-<blockquote>
-<b>Summary</b>
-
-<br>
- This article briefly explains Cactus, its common uses and advantages and then provides a step-by-step tutorial on how to use the Cactus integration provided by WTP. The article assumes that you are familiar with <a href="http://www.junit.org/" target="_top">JUnit</a> and the basics of using WTP to build, deploy and run web projects.
- <p><b> Daniel R Somerfield, BEA Systems</b> <br>
- <font size="-1">May 31, 2005</font> </p>
-</blockquote>
-<hr width="100%">
-<h2>What is Cactus?</h2>
-<p>
- Cactus is actually very, very simple. It is often valuable to be able to test components (plain Java classes, Servlets, EJBs, etc.) within the container in which they will eventually be deployed. Cactus provides proxies for unit tests so that although you run the vanilla JUnit client (or any other JUnit client) locally, the tests are actually invoked on the target container. A servlet within the container fields requests from your local test case and delegates that actual running of the test to the test case running on the server and reports back the results. The test case can be deployed locally or remotely. Either way, Cactus works the same since it uses HTTP to do the invocation and reporting.
-</p>
-<p>
- Really, the only trick to using Cactus is setup and deployment. Fortunately, we get help from the Web Tools Project on the deployment. At the present, setup is still a manual process (something that will hopefully change in the future).
-</p>
-<hr width="100%">
-<h2>Using WTP Cactus Integration</h2>
-<p>
-We start off with an existing web project and a class we want to test on Tomcat or any other WTP-supported servlet container. Let's say we have a <a href="code/components/security/PermissionManager.java">PermissionManager</a> class we want to test to see if it is correctly managing the permissions in the HTTP session. The important part of the PermissionManager is this method:
- <pre>
- public void validate(HttpServletRequest request)
- throws InsufficientPermissionsException
- {
- Permission permission = (Permission) request.getSession().getAttribute(TOKEN_KEY);
- if (!permission.implies(fPermissionRequired))
- {
- throw new InsufficientPermissionsException("You do not have permission for that operation");
- }
- }
- </pre>
- In theory, it should check whether the user has permissions for the operation and if not, it should throw an <a href="code/components/security/InsufficientPermissionsException.java">InsufficientPermissionsException</a>. To check that it is doing it's job, we will want to write a unit test.
-</p>
-<p>
- But first, we need to get the cactus dependencies available on the class path. You will want to put them in the WebModule under WEB-INF/lib so that they are visible in the web module at runtime. The dependencies are all from the Cactus 1.7 distribution (available at <a href="http://jakarta.apache.org/site/downloads/downloads_cactus.cgi">http://jakarta.apache.org/site/downloads/downloads_cactus.cgi</a>). As of the writing of this document, they are:
- <ul>
- <li>cactus-1.7.jar
- <li>junit-3.8.1.jar
- <li>aspectjrt-1.2.1.jar
- <li>commons-logging-1.0.4.jar
- <li>commons-httpclient-2.0.2.jar
- </ul>
- Once you have added the libraries to the WEB-INF/lib (you can simply drag and drop them there), you can either add the libraries to the the build path by editing the build path in the project properties, or by right-clicking them while in the Java Perspective and choosing "Build Path->Add to Build Path".
-</p>
-<p>
- Now that we have the dependencies on the classpath, we can write our test. Rather than the usual JUnit TestCase, we need to extend ServletTestCase. As in JUnit, the testXXX() methods are discovered via introspection and run when the test executes. Unless you have any special needs via the beginXXX() and endXXX() client-side methods, the test will really look like any other unit test (see the cactus docs for more details on using beginXXX() and endXXX()).
-
- First let's write a test method to make sure the PermissionManager class is allowing requests it is supposed to. In the JavaSource folder, create the <a href="code/components/security/test/PermissionManagerTest.java">PermissionManagerTest</a> class and add the following method:
-<pre>
- public void testPermissionManagerAllow() throws Exception
- {
- //Make sure that the AllPermission gives us permission to our test permission
- session.setAttribute(PermissionManager.TOKEN_KEY, new AllPermission());
- PermissionManager manager = new PermissionManager(new TestPermission("Test"));
- manager.validate(request);
- }
-</pre>
-
- The test is quite simple. It just calls the validate method. If the validation fails, an InsufficientPermissionException will be thrown and the test will fail.
-
- Before we can run the test, we need to set up Cactus. In the web module, under WebContent/WEB-INF there should be a web.xml. To this file, add the following mark-up before the final web-app tag:
-
-<pre>
-
- <filter>
- <filter-name>FilterRedirector</filter-name>
- <filter-class>org.apache.cactus.server.FilterTestRedirector</filter-class>
- </filter>
-
- <filter-mapping>
- <filter-name>FilterRedirector</filter-name>
- <url-pattern>/FilterRedirector</url-pattern>
- </filter-mapping>
-
- <servlet>
- <servlet-name>ServletRedirector</servlet-name>
- <servlet-class>org.apache.cactus.server.ServletTestRedirector</servlet-class>
- </servlet>
-
- <servlet>
- <servlet-name>JspRedirector</servlet-name>
- <jsp-file>/jspRedirector.jsp</jsp-file>
- </servlet>
-
- <servlet-mapping>
- <servlet-name>ServletRedirector</servlet-name>
- <url-pattern>/ServletRedirector</url-pattern>
- </servlet-mapping>
-
- <servlet-mapping>
- <servlet-name>JspRedirector</servlet-name>
- <url-pattern>/JspRedirector</url-pattern>
- </servlet-mapping>
-</pre>
-
-</p>
-<p>
- This configures the redirectors that need to field the HTTP requests from Cactus and execute the unit test in the container.
-
- Once you have saved the web.xml, you might need to restart the HTTP container if you have already started it. Otherwise, you can right-click on the test case and choose "Run->Run on Server". If you want to debug the component or the test you can choose "Debug->Debug on Server" instead. Assuming our test passes, we should get that wonderful JUnit "green bar" in the JUnit window.
-</p>
-<!-- Note: this behavior changed in RC1. Leaving the comment just in case it changes back.
-<p>
- Incidentally, by default the JUnit window will only appear on a failure. If you would like the JUnit window to appear all the time, go to the Preferences under Java->JUnit and disable "Show junit results view only when a failure or error occurs".
-</p>
--->
-<p>
- Now we write a second test method to make sure the PermissionManager is denying requests if you only have the insufficient <a href="code/components/security/ApplicationPermission.java">ApplicationPermission</a>:
-<pre>
- public void testPermissionManagerDisallow() throws Exception
- {
- try
- {
- //Make sure that the ApplicationPermission does not give test permission
- session.setAttribute(PermissionManager.TOKEN_KEY, new ApplicationPermission("Login"));
- PermissionManager manager = new PermissionManager(new TestPermission("Test"));
- manager.validate(request);
-
- } catch (InsufficientPermissionsException e)
- {
- }
- fail("Should not have allowed this request");
- }
-</pre>
-Ooops--the red bar. It looks like our test failed. Looking at it, it is obvious why. If the InsufficientPermissionsException is being caught and execution is falling through to the fail() call. What we really meant was this:
-<pre>
- public void testPermissionManagerDisallow() throws Exception
- {
- try
- {
- //Make sure that the ApplicationPermission does not give test permission
- session.setAttribute(PermissionManager.TOKEN_KEY, new ApplicationPermission("Login"));
- PermissionManager manager = new PermissionManager(new TestPermission("Test"));
- manager.validate(request);
- fail("Should not have allowed this request");
- } catch (InsufficientPermissionsException e)
- {
- }
- }
-</pre>
-Much better. Back to the green bar.
-</p>
-That's really all there is to it. All the normal JUnit best practices apply. You can aggregate tests with Suites and run Cactus tests and vanilla JUnit tests side-by-side. For more sophisticated Cactus test development, such as testing JSPs and Filters and using authentication, consult the <a href="http://jakarta.apache.org/cactus/" target="_top">Cactus website</a>.
-<hr width="100%">
-<h2>Source Code</h2>
-<p>The source code for this article is pretty contrived and you could easily come up with your own, but if you want it, the entire web project is available in this <a href="code/CactusWebProject.zip">zip file</a>.
-<hr width="100%">
-</body>
-</html>
diff --git a/community/tutorials/CactusInWTP/code/CactusWebProject.zip b/community/tutorials/CactusInWTP/code/CactusWebProject.zip
deleted file mode 100644
index c988798..0000000
--- a/community/tutorials/CactusInWTP/code/CactusWebProject.zip
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/CactusInWTP/code/components/security/ApplicationPermission.java b/community/tutorials/CactusInWTP/code/components/security/ApplicationPermission.java
deleted file mode 100644
index ad9903d..0000000
--- a/community/tutorials/CactusInWTP/code/components/security/ApplicationPermission.java
+++ /dev/null
@@ -1,15 +0,0 @@
-package components.security;
-
-import java.security.BasicPermission;
-
-public class ApplicationPermission extends BasicPermission {
-
- private static final long serialVersionUID = 1L;
-
- public ApplicationPermission(String name) {
- super(name);
- }
-
-
-
-}
diff --git a/community/tutorials/CactusInWTP/code/components/security/InsufficientPermissionsException.java b/community/tutorials/CactusInWTP/code/components/security/InsufficientPermissionsException.java
deleted file mode 100644
index faf7f98..0000000
--- a/community/tutorials/CactusInWTP/code/components/security/InsufficientPermissionsException.java
+++ /dev/null
@@ -1,12 +0,0 @@
-package components.security;
-
-public class InsufficientPermissionsException extends Exception {
-
- private static final long serialVersionUID = 1L;
-
- public InsufficientPermissionsException(String message)
- {
- super(message);
- }
-
-}
diff --git a/community/tutorials/CactusInWTP/code/components/security/PermissionManager.java b/community/tutorials/CactusInWTP/code/components/security/PermissionManager.java
deleted file mode 100644
index 745d5c1..0000000
--- a/community/tutorials/CactusInWTP/code/components/security/PermissionManager.java
+++ /dev/null
@@ -1,37 +0,0 @@
-package components.security;
-
-import java.security.BasicPermission;
-import java.security.Permission;
-
-import javax.servlet.http.HttpServletRequest;
-
-public class PermissionManager {
-
- public static final String TOKEN_KEY = "token";
- private Permission fPermissionRequired;
-
- public PermissionManager(Permission permissionRequired)
- {
- fPermissionRequired = permissionRequired;
- }
-
- public void validate(HttpServletRequest request)
- throws InsufficientPermissionsException
- {
- Permission permission = (Permission) request.getSession().getAttribute(TOKEN_KEY);
- if (!permission.implies(fPermissionRequired))
- {
- throw new InsufficientPermissionsException("You do not have permission for that operation");
- }
- }
-
- public class ApplicationPermission extends BasicPermission {
-
- private static final long serialVersionUID = 1L;
-
- public ApplicationPermission(String name) {
- super(name);
- }
-
- }
-}
diff --git a/community/tutorials/CactusInWTP/code/components/security/test/PermissionManagerTest.java b/community/tutorials/CactusInWTP/code/components/security/test/PermissionManagerTest.java
deleted file mode 100644
index d64aa78..0000000
--- a/community/tutorials/CactusInWTP/code/components/security/test/PermissionManagerTest.java
+++ /dev/null
@@ -1,46 +0,0 @@
-package components.security.test;
-
-import java.security.AllPermission;
-import java.security.BasicPermission;
-
-import org.apache.cactus.ServletTestCase;
-
-import components.security.ApplicationPermission;
-import components.security.InsufficientPermissionsException;
-import components.security.PermissionManager;
-
-public class PermissionManagerTest extends ServletTestCase{
-
- public void testPermissionManagerAllow() throws Exception
- {
- //Make sure that the AllPermission gives us permission to our test permission
- session.setAttribute(PermissionManager.TOKEN_KEY, new AllPermission());
- PermissionManager manager = new PermissionManager(new TestPermission("Test"));
- manager.validate(request);
- }
-
- public void testPermissionManagerDisallow() throws Exception
- {
- try
- {
- //Make sure that the ApplicationPermission does not give test permission
- session.setAttribute(PermissionManager.TOKEN_KEY, new ApplicationPermission("Login"));
- PermissionManager manager = new PermissionManager(new TestPermission("Test"));
- manager.validate(request);
- fail("Should not have allowed this request");
- } catch (InsufficientPermissionsException e)
- {
- }
- }
-
- private class TestPermission extends BasicPermission
- {
-
- private static final long serialVersionUID = 1L;
-
- public TestPermission(String name) {
- super(name);
- }
-
- }
-}
diff --git a/community/tutorials/DevelopingWTP/DevelopingWTP.html b/community/tutorials/DevelopingWTP/DevelopingWTP.html
deleted file mode 100644
index 60ed450..0000000
--- a/community/tutorials/DevelopingWTP/DevelopingWTP.html
+++ /dev/null
@@ -1,449 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../..//default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../..//webtools/wtp.css" type="text/css">
-<title>WTP Tutorials - Developing the WTP with Eclipse</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">WTP Tutorials - Developing the WTP with Eclipse</font>
-<br>
-<font class="indexsub">WTP Tutorials - Developing the WTP with Eclipse</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../..//images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>By Mark Hutchinson, IBM</b>
-
-<BR>
- February 21, 2005
- <BR>
-
-<BR>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- This tutorial shows you how to set up your Eclipse
- environment to develop or modify the Web Tools Platform (WTP) project plug-ins. First
- we will discuss how to connect to the CVS repository to check
- out the WTP source code. We will then set up our target platform.
- Next we will make a modification to the WTP source and run
- our eclipse application. Finally, we will create a patch
- for our change, which we could submit to the WTP project.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Checking Out the Source Code</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ol>
-
-<li>
- Access the source code for the Eclipse Web Tools Platform
- from the Concurrent Versions System (CVS) repository.
- To access the CVS repository select Window > Open
- Perspective > Other and select CVS Repository Exploring.
- <br>
-<br>
-</li>
-
-<li>
- The CVS Repositories view is now on the left side of your
- screen. Select the Add CVS Repository icon
- <img src="images/addrepositoryicon.gif" alt="Add Repository Icon" width="25" heigt="23" border="0">
- and in the Add CVS repository dialog enter the following values:
- <br>
-
-<b>Host:</b>
- dev.eclipse.org
- <br>
-
-<b>Repository Path:</b>
- /cvsroot/webtools
- <br>
-
-<b>User:</b>
- anonymous
- <br>
- Select finish.
- <br>
-
-
-<img src="images/addrepository.gif" width="438" height="542" border="0" alt="Add CVS Repository">
- <br>
-
-<br>
-
-</li>
-
-<li>
- Navigate through the folders and find the plug-ins that you
- are interested in having the source for. The most recent
- code is in HEAD. The
- <a href="http://www.eclipse.org/webtools/wst/main.html">Web Standards Tools</a>
- plug-ins are found in the wst folder, and the
- <a href="http://www.eclipse.org/webtools/jst/main.html">J2EE Standard Tools</a>
- plug-ins are found in the jst folder. For this tutorial we will modify
- <b>HEAD/wst/components/xml/plugins/org.eclipse.wst.xml.ui</b>
-
-<br>
-<br>
-</li>
-
-<li>
- Add the source into your local workspace by right clicking
- on that plug-in and selecting "Check Out".
- <br>
-
-<img src="images/repositories.gif" alt="check out source code" width="487" height="689" border="0">
- <br>
-
-<br>
-
-</li>
-
-<li>
- Switch back to the Java perspective. The source code for the
- plug-in you downloaded is now in your workspace.
- </li>
-
-</ol>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Setting up the Target Platform</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The target platform specified contains the eclipse plug-ins
- which your code will be compiled against. Having a target
- platform allows you to compile and run your modified code
- without having to bring all of the source code into your
- development workbench. The target platform should be the
- same platform you are developing for.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>To set up your target platform:</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ol>
-
-<li>
-
-<a href="http://download.eclipse.org/webtools/downloads/">Download</a>
- and install the desired Eclipse and WTP versions in a separate folder from your current development
- Eclipse platform. Ensure that this new platform runs. This
- will be your target platform.
- <br>
-<br>
-</li>
-
-<li>
- From your development workbench select Window > Preferences
- > Plug-in development > Target Platform.
- <br>
-<br>
-</li>
-
-<li>
- Enter the location of the platform you wish to target.
- <br>
-<br>
-</li>
-
-<li>
- Select the "Not in Workspace" button. This ensures the
- source code in your workspace will be run rather than
- the plug-ins from the target platform.
- <img src="images/targetplatform.gif" alt="target platform preferences" width="652" height="505" border="0">
- </li>
-
-</ol>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Modifying the Source Code</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- As an example, we are going to add to the pop-up menu shown
- when the user right clicks on an XML file in the
- Navigator view. First we need to add to the plugin.xml file
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ol>
-
-<li>
- In the Java perspective, open the plugin.xml file for the
- org.eclipse.wst.xml.ui plug-in you just checked out.
- <br>
-<br>
-</li>
-
-<li>
- Add the following to the source of plugin.xml:
- <pre>
-<!-- =============================================================================== -->
-<!-- My Popup Menu -->
-<!-- =============================================================================== -->
- <extension point="org.eclipse.ui.popupMenus">
- <objectContribution
- objectClass="org.eclipse.core.resources.IFile"
- nameFilter="*.xml"
- id="org.eclipse.wst.xml.ui.actions">
- <action
- label="Show a Message Dialog"
- class="org.eclipse.wst.xml.ui.actions.PopUp"
- menubarPath="My Menu"
- enablesFor="1"
- id="org.eclipse.wst.xml.ui.actions.PopUp" />
- </objectContribution>
- </extension>
- </pre>
-
-</li>
-
-<li>
- In the package Explorer expand "src" and right click on
- org.eclipse.wxt.xml.ui.actions and select new class.
-
- Name this class PopUp.
- <br>
-<br>
-</li>
-
-<li>
- Add this source code to PopUp.java:
- <pre>
-package org.eclipse.wst.xml.ui.actions;
-
-import org.eclipse.jface.action.IAction;
-import org.eclipse.jface.dialogs.MessageDialog;
-import org.eclipse.swt.widgets.Shell;
-import org.eclipse.ui.actions.ActionDelegate;
-import org.eclipse.wst.xml.ui.internal.XMLUIPlugin;
-
-public class PopUp extends ActionDelegate {
- public void run(IAction action) {
- MessageDialog message;
- Shell shell = XMLUIPlugin.getInstance().getWorkbench()
- .getActiveWorkbenchWindow().getShell();
- String labels[] = new String[1];
- labels[0] = "OK";
- message = new MessageDialog(shell, "My Message Dialog", null,
- "I have modified eclipse!", 2, labels, 1);
- message.open();
- }
-}
- </pre>
-
-</li>
-
-</ol>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Running Your Eclipse Application</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ol>
-
-<li>
- In the Java perspective from the menu bar select Run > Run.
- <br>
-<br>
-</li>
-
-<li>
- In the Run dialog select the Eclipse Application option,
- then select new.
- <br>
-<br>
-</li>
-
-<li>
- Enter the location of the desired workspace, and select Run.
-
- <br>
-
-<img src="images/run.gif" alt="run" width="729" height="599" border="0">
- </li>
-
-</ol>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- When this version of Eclipse is run it compiles the source code in your
- workspace, and runs from your target platform. A
- second instance of Eclipse is now running and you are now
- able to test any code modifications you have made.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>Now test out your modification:</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ol start="4">
-
-<li>
- We need a project in the navigator to test this on. Select
- File > New > Example > Editing and Validating XML Files.
- <br>
-<br>
-</li>
-
-<li>
- Right click on any XML file, for example Invoice.xml. Notice
- that the new option "Show Message Dialog" has been
- added to this menu.
- <br>
-
-<img src="images/menu.gif" alt="menu" border="0" width="370" height="663">
- <br>
-
-<br>
-
-</li>
-
-<li>
- Select "Show a Message Dialog." A message dialog appears.
- <br>
-
-<img src="images/dialog.gif" alt="My Message Dialog" border="0" width="444" height="142">
- </li>
-
-</ol>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Creating a Patch for your Modification</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- To contribute an enhancement to WTP, you can submit
- your code changes as a patch.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ol>
-
-<li>In the Package Explorer view, right click on the modified plug-in
- project and select Team > Create Patch.
- <br>
-
-<img src="images/createpatchmenu.gif" alt="select Team > Create Patch" width="601" height="679">
- <br>
-<br>
-
-</li>
-
-<li>Select "Save in File System" and enter the file name. Select Next.
- <br>
-
-<img src="images/createpatch.gif" alt="Create Patch" border="0" width="543" height="543">
- <br>
-<br>
-
-</li>
-
-<li>Ensure the Diff Output Format is set to "unified." Select Finish.<br>
-<br>
-</li>
-
-<li>The patch has been saved to your file system. If this were an actual feature
- enhancement the patch could be submitted to the webtools project using
- <a href="https://bugs.eclipse.org/bugs/">
- Bugzilla
- </a>
-
-</li>
-
-</ol>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Summary</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>In this tutorial you learned how to set up your Eclipse environment to get started developing
- Web Tools Platform plug-ins by creating a simple addition to the user interface.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p></p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p></p>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/community/tutorials/DevelopingWTP/DevelopingWTP.xml b/community/tutorials/DevelopingWTP/DevelopingWTP.xml
deleted file mode 100644
index d1d4e80..0000000
--- a/community/tutorials/DevelopingWTP/DevelopingWTP.xml
+++ /dev/null
@@ -1,267 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<?xml-stylesheet type="text/xsl" href="../../../wtp.xsl"?>
-<html>
- <head>
- <meta name="root" content="../../../../" />
- <title>WTP Tutorials - Developing the WTP with Eclipse</title>
- </head>
-
- <body>
- <h1>WTP Tutorials - Developing the WTP with Eclipse</h1>
-
- <p>
- <b>By Mark Hutchinson, IBM</b>
- <BR />
- February 21, 2005
- <BR />
- <BR />
- </p>
- <p>
- This tutorial shows you how to set up your Eclipse
- environment to develop or modify the Web Tools Platform (WTP) project plug-ins. First
- we will discuss how to connect to the CVS repository to check
- out the WTP source code. We will then set up our target platform.
- Next we will make a modification to the WTP source and run
- our eclipse application. Finally, we will create a patch
- for our change, which we could submit to the WTP project.
- </p>
- <br/>
- <h2>Checking Out the Source Code</h2>
-
- <ol>
- <li>
- Access the source code for the Eclipse Web Tools Platform
- from the Concurrent Versions System (CVS) repository.
- To access the CVS repository select Window > Open
- Perspective > Other and select CVS Repository Exploring.
- <br/><br/></li>
- <li>
- The CVS Repositories view is now on the left side of your
- screen. Select the Add CVS Repository icon
- <img src="images/addrepositoryicon.gif" alt="Add Repository Icon"
- width="25" heigt="23" border="0" />
- and in the Add CVS repository dialog enter the following values:
- <br />
- <b>Host:</b>
- dev.eclipse.org
- <br />
- <b>Repository Path:</b>
- /cvsroot/webtools
- <br />
- <b>User:</b>
- anonymous
- <br />
- Select finish.
- <br />
-
- <img src="images/addrepository.gif" width="438" height="542"
- border="0" alt="Add CVS Repository" />
- <br />
- <br />
- </li>
- <li>
- Navigate through the folders and find the plug-ins that you
- are interested in having the source for. The most recent
- code is in HEAD. The
- <a href="http://www.eclipse.org/webtools/wst/main.html">Web Standards Tools</a>
- plug-ins are found in the wst folder, and the
- <a href="http://www.eclipse.org/webtools/jst/main.html">J2EE Standard Tools</a>
- plug-ins are found in the jst folder. For this tutorial we will modify
- <b>HEAD/wst/components/xml/plugins/org.eclipse.wst.xml.ui</b>
- <br/><br/></li>
- <li>
- Add the source into your local workspace by right clicking
- on that plug-in and selecting "Check Out".
- <br />
- <img src="images/repositories.gif" alt="check out source code"
- width="487" height="689" border="0" />
- <br />
- <br />
- </li>
- <li>
- Switch back to the Java perspective. The source code for the
- plug-in you downloaded is now in your workspace.
- </li>
- </ol>
- <br/>
- <h2>Setting up the Target Platform</h2>
- <p>
- The target platform specified contains the eclipse plug-ins
- which your code will be compiled against. Having a target
- platform allows you to compile and run your modified code
- without having to bring all of the source code into your
- development workbench. The target platform should be the
- same platform you are developing for.
- </p>
- <p>To set up your target platform:</p>
- <ol>
- <li>
- <a href="http://download.eclipse.org/webtools/downloads/">Download</a>
- and install the desired Eclipse and WTP versions in a separate folder from your current development
- Eclipse platform. Ensure that this new platform runs. This
- will be your target platform.
- <br/><br/></li>
- <li>
- From your development workbench select Window > Preferences
- > Plug-in development > Target Platform.
- <br/><br/></li>
- <li>
- Enter the location of the platform you wish to target.
- <br/><br/></li>
- <li>
- Select the "Not in Workspace" button. This ensures the
- source code in your workspace will be run rather than
- the plug-ins from the target platform.
- <img src="images/targetplatform.gif"
- alt="target platform preferences" width="652" height="505"
- border="0" />
- </li>
- </ol>
- <br/>
- <h2>Modifying the Source Code</h2>
- <p>
- As an example, we are going to add to the pop-up menu shown
- when the user right clicks on an XML file in the
- Navigator view. First we need to add to the plugin.xml file
- </p>
- <ol>
- <li>
- In the Java perspective, open the plugin.xml file for the
- org.eclipse.wst.xml.ui plug-in you just checked out.
- <br/><br/></li>
- <li>
- Add the following to the source of plugin.xml:
- <pre>
-<!-- =============================================================================== -->
-<!-- My Popup Menu -->
-<!-- =============================================================================== -->
- <extension point="org.eclipse.ui.popupMenus">
- <objectContribution
- objectClass="org.eclipse.core.resources.IFile"
- nameFilter="*.xml"
- id="org.eclipse.wst.xml.ui.actions">
- <action
- label="Show a Message Dialog"
- class="org.eclipse.wst.xml.ui.actions.PopUp"
- menubarPath="My Menu"
- enablesFor="1"
- id="org.eclipse.wst.xml.ui.actions.PopUp" />
- </objectContribution>
- </extension>
- </pre>
- </li>
- <li>
- In the package Explorer expand "src" and right click on
- org.eclipse.wxt.xml.ui.actions and select new class.
-
- Name this class PopUp.
- <br/><br/></li>
- <li>
- Add this source code to PopUp.java:
- <pre>
-package org.eclipse.wst.xml.ui.actions;
-
-import org.eclipse.jface.action.IAction;
-import org.eclipse.jface.dialogs.MessageDialog;
-import org.eclipse.swt.widgets.Shell;
-import org.eclipse.ui.actions.ActionDelegate;
-import org.eclipse.wst.xml.ui.internal.XMLUIPlugin;
-
-public class PopUp extends ActionDelegate {
- public void run(IAction action) {
- MessageDialog message;
- Shell shell = XMLUIPlugin.getInstance().getWorkbench()
- .getActiveWorkbenchWindow().getShell();
- String labels[] = new String[1];
- labels[0] = "OK";
- message = new MessageDialog(shell, "My Message Dialog", null,
- "I have modified eclipse!", 2, labels, 1);
- message.open();
- }
-}
- </pre>
- </li>
- </ol>
-
- <h2>Running Your Eclipse Application</h2>
- <ol>
- <li>
- In the Java perspective from the menu bar select Run > Run.
- <br/><br/></li>
- <li>
- In the Run dialog select the Eclipse Application option,
- then select new.
- <br/><br/></li>
- <li>
- Enter the location of the desired workspace, and select Run.
-
- <br />
- <img src="images/run.gif" alt="run" width="729" height="599"
- border="0" />
- </li>
- </ol>
-
- <p>
- When this version of Eclipse is run it compiles the source code in your
- workspace, and runs from your target platform. A
- second instance of Eclipse is now running and you are now
- able to test any code modifications you have made.
- </p>
- <p>Now test out your modification:</p>
- <ol start="4">
- <li>
- We need a project in the navigator to test this on. Select
- File > New > Example > Editing and Validating XML Files.
- <br/><br/></li>
- <li>
- Right click on any XML file, for example Invoice.xml. Notice
- that the new option "Show Message Dialog" has been
- added to this menu.
- <br />
- <img src="images/menu.gif" alt="menu" border="0" width="370"
- height="663" />
- <br />
- <br />
- </li>
- <li>
- Select "Show a Message Dialog." A message dialog appears.
- <br />
- <img src="images/dialog.gif" alt="My Message Dialog" border="0"
- width="444" height="142" />
- </li>
- </ol>
- <br/>
- <h2>Creating a Patch for your Modification</h2>
- <p>
- To contribute an enhancement to WTP, you can submit
- your code changes as a patch.
- </p>
- <ol>
- <li>In the Package Explorer view, right click on the modified plug-in
- project and select Team > Create Patch.
- <br/>
- <img src="images/createpatchmenu.gif" alt="select Team > Create Patch" width="601" height="679"/>
- <br/><br/>
- </li>
- <li>Select "Save in File System" and enter the file name. Select Next.
- <br/>
- <img src="images/createpatch.gif" alt="Create Patch" border="0" width="543" height="543"/>
- <br/><br/>
- </li>
- <li>Ensure the Diff Output Format is set to "unified." Select Finish.<br/><br/></li>
- <li>The patch has been saved to your file system. If this were an actual feature
- enhancement the patch could be submitted to the webtools project using
- <a href="https://bugs.eclipse.org/bugs/">
- Bugzilla
- </a>
- </li>
- </ol>
- <br/>
- <h2>Summary</h2>
- <p>In this tutorial you learned how to set up your Eclipse environment to get started developing
- Web Tools Platform plug-ins by creating a simple addition to the user interface.
- </p>
- <p></p><p></p>
- </body>
-</html>
-
diff --git a/community/tutorials/DevelopingWTP/images/addrepository.gif b/community/tutorials/DevelopingWTP/images/addrepository.gif
deleted file mode 100644
index a68204b..0000000
--- a/community/tutorials/DevelopingWTP/images/addrepository.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/DevelopingWTP/images/addrepositoryicon.gif b/community/tutorials/DevelopingWTP/images/addrepositoryicon.gif
deleted file mode 100644
index cc97c40..0000000
--- a/community/tutorials/DevelopingWTP/images/addrepositoryicon.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/DevelopingWTP/images/createpatch.gif b/community/tutorials/DevelopingWTP/images/createpatch.gif
deleted file mode 100644
index ee38055..0000000
--- a/community/tutorials/DevelopingWTP/images/createpatch.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/DevelopingWTP/images/createpatchmenu.gif b/community/tutorials/DevelopingWTP/images/createpatchmenu.gif
deleted file mode 100644
index 3c757b4..0000000
--- a/community/tutorials/DevelopingWTP/images/createpatchmenu.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/DevelopingWTP/images/dialog.gif b/community/tutorials/DevelopingWTP/images/dialog.gif
deleted file mode 100644
index 03a5c73..0000000
--- a/community/tutorials/DevelopingWTP/images/dialog.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/DevelopingWTP/images/menu.gif b/community/tutorials/DevelopingWTP/images/menu.gif
deleted file mode 100644
index 928020e..0000000
--- a/community/tutorials/DevelopingWTP/images/menu.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/DevelopingWTP/images/repositories.gif b/community/tutorials/DevelopingWTP/images/repositories.gif
deleted file mode 100644
index 2c1f1c5..0000000
--- a/community/tutorials/DevelopingWTP/images/repositories.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/DevelopingWTP/images/run.gif b/community/tutorials/DevelopingWTP/images/run.gif
deleted file mode 100644
index cde4319..0000000
--- a/community/tutorials/DevelopingWTP/images/run.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/DevelopingWTP/images/targetplatform.gif b/community/tutorials/DevelopingWTP/images/targetplatform.gif
deleted file mode 100644
index 6271991..0000000
--- a/community/tutorials/DevelopingWTP/images/targetplatform.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/InstallTomcat/InstallTomcat.html b/community/tutorials/InstallTomcat/InstallTomcat.html
deleted file mode 100644
index 36f97dd..0000000
--- a/community/tutorials/InstallTomcat/InstallTomcat.html
+++ /dev/null
@@ -1,140 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../..//default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../..//webtools/wtp.css" type="text/css">
-<title>Installing Apache Tomcat Server</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">Installing Apache Tomcat Server</font>
-<br>
-<font class="indexsub">Installing Apache Tomcat Server</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../..//images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>By Kathy Chan</b>
-
-<br>
- April 29, 2005
- <br>
-
-<br>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- In this tutorial, you will install an Apache Tomcat server
- using the Server Installed Runtimes preference page.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Installing server runtime</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ol>
-
-<li>
- If you do not have Apache Tomcat on your machine, you
- will first need to download and unzip
- <a href="http://jakarta.apache.org/tomcat/" target="_top">
- Apache Tomcat
- </a>
- (this scenario was written using Apache Tomcat version
- 5.0.28, but other versions can be substituted).
- </li>
-
-
-<li>Start the Eclipse WTP workbench.</li>
-
-
-<li>
- Open
- <b>
- Window -> Preferences -> Server -> Installed
- Runtimes
- </b>
- to create a Tomcat installed runtime.
- </li>
-
-
-<li>
- Click on
- <b>Add...</b>
- to open the
- <b>New Server Runtime</b>
- dialog, then select your runtime under
- <b>Apache</b>
- (Apache Tomcat v5.0 in this example):
- </li>
-
-
-<br>
-
-<img border="0" src="images/InstallTomcat1.JPG">
- <li>
- Click
- <b>Next</b>
- , and fill in your
- <b>Tomcat installation directory</b>
- :
- </li>
-
-<br>
-
-<img border="0" src="images/InstallTomcat2.JPG">
- <li>
- Ensure the selected
- <b>JRE</b>
- is a full JDK and is of a version that will satisfy
- Apache Tomcat (this scenario was written using SUN JDK
- 1.4.2_06). If necessary, you can click on
- <b>Installed JREs...</b>
- to add JDKs to Eclipse.
- </li>
-
-
-<li>
- Click
- <b>Finish</b>
- .
- </li>
-
-</ol>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/community/tutorials/InstallTomcat/InstallTomcat.xml b/community/tutorials/InstallTomcat/InstallTomcat.xml
deleted file mode 100644
index 1443a3f..0000000
--- a/community/tutorials/InstallTomcat/InstallTomcat.xml
+++ /dev/null
@@ -1,87 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?xml-stylesheet type="text/xsl" href="../../../wtp.xsl"?>
-<html>
- <head>
- <meta name="root" content="../../../../" />
- <title>Installing Apache Tomcat Server</title>
- </head>
- <body>
- <h1>Installing Apache Tomcat Server</h1>
- <p>
- <b>By Kathy Chan</b>
- <br />
- April 29, 2005
- <br />
- <br />
- </p>
-
- <br></br>
- <p>
- In this tutorial, you will install an Apache Tomcat server
- using the Server Installed Runtimes preference page.
- </p>
- <br></br>
- <h2>Installing server runtime</h2>
- <br></br>
- <ol>
- <li>
- If you do not have Apache Tomcat on your machine, you
- will first need to download and unzip
- <a href="http://jakarta.apache.org/tomcat/" target="_top">
- Apache Tomcat
- </a>
- (this scenario was written using Apache Tomcat version
- 5.0.28, but other versions can be substituted).
- </li>
-
- <li>Start the Eclipse WTP workbench.</li>
-
- <li>
- Open
- <b>
- Window -> Preferences -> Server -> Installed
- Runtimes
- </b>
- to create a Tomcat installed runtime.
- </li>
-
- <li>
- Click on
- <b>Add...</b>
- to open the
- <b>New Server Runtime</b>
- dialog, then select your runtime under
- <b>Apache</b>
- (Apache Tomcat v5.0 in this example):
- </li>
-
- <br></br>
- <img border="0" src="images/InstallTomcat1.JPG" />
- <li>
- Click
- <b>Next</b>
- , and fill in your
- <b>Tomcat installation directory</b>
- :
- </li>
- <br></br>
- <img border="0" src="images/InstallTomcat2.JPG" />
- <li>
- Ensure the selected
- <b>JRE</b>
- is a full JDK and is of a version that will satisfy
- Apache Tomcat (this scenario was written using SUN JDK
- 1.4.2_06). If necessary, you can click on
- <b>Installed JREs...</b>
- to add JDKs to Eclipse.
- </li>
-
- <li>
- Click
- <b>Finish</b>
- .
- </li>
- </ol>
-
- </body>
-</html>
diff --git a/community/tutorials/InstallTomcat/images/InstallTomcat1.JPG b/community/tutorials/InstallTomcat/images/InstallTomcat1.JPG
deleted file mode 100644
index 94b4360..0000000
--- a/community/tutorials/InstallTomcat/images/InstallTomcat1.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/InstallTomcat/images/InstallTomcat2.JPG b/community/tutorials/InstallTomcat/images/InstallTomcat2.JPG
deleted file mode 100644
index 1c69242..0000000
--- a/community/tutorials/InstallTomcat/images/InstallTomcat2.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/RDBTutorial.html b/community/tutorials/RDBTutorial/RDBTutorial.html
deleted file mode 100644
index 31ebbf3..0000000
--- a/community/tutorials/RDBTutorial/RDBTutorial.html
+++ /dev/null
@@ -1,628 +0,0 @@
-<html xmlns:v="urn:schemas-microsoft-com:vml"
-xmlns:o="urn:schemas-microsoft-com:office:office"
-xmlns:w="urn:schemas-microsoft-com:office:word"
-xmlns:st1="urn:schemas-microsoft-com:office:smarttags"
-xmlns="http://www.w3.org/TR/REC-html40">
-
-<head>
-<meta http-equiv=Content-Type content="text/html; charset=windows-1252">
-<meta name=ProgId content=Word.Document>
-<meta name=Generator content="Microsoft Word 10">
-<meta name=Originator content="Microsoft Word 10">
-<!--[if !mso]>
-<style>
-v\:* {behavior:url(#default#VML);}
-o\:* {behavior:url(#default#VML);}
-w\:* {behavior:url(#default#VML);}
-.shape {behavior:url(#default#VML);}
-</style>
-<![endif]-->
-<title>WST</title>
-<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
- name="City"/>
-<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
- name="place"/>
-<!--[if gte mso 9]><xml>
- <o:DocumentProperties>
- <o:Author>Der Ping Chou</o:Author>
- <o:LastAuthor>Der Ping Chou</o:LastAuthor>
- <o:Revision>2</o:Revision>
- <o:TotalTime>1784</o:TotalTime>
- <o:Created>2005-02-19T06:52:00Z</o:Created>
- <o:LastSaved>2005-02-19T06:52:00Z</o:LastSaved>
- <o:Pages>1</o:Pages>
- <o:Words>584</o:Words>
- <o:Characters>3333</o:Characters>
- <o:Company>IBM</o:Company>
- <o:Lines>27</o:Lines>
- <o:Paragraphs>7</o:Paragraphs>
- <o:CharactersWithSpaces>3910</o:CharactersWithSpaces>
- <o:Version>10.2625</o:Version>
- </o:DocumentProperties>
-</xml><![endif]--><!--[if gte mso 9]><xml>
- <w:WordDocument>
- <w:SpellingState>Clean</w:SpellingState>
- <w:GrammarState>Clean</w:GrammarState>
- <w:Compatibility>
- <w:BreakWrappedTables/>
- <w:SnapToGridInCell/>
- <w:WrapTextWithPunct/>
- <w:UseAsianBreakRules/>
- <w:UseFELayout/>
- </w:Compatibility>
- <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
- </w:WordDocument>
-</xml><![endif]--><!--[if !mso]><object
- classid="clsid:38481807-CA0E-42D2-BF39-B33AF135CC4D" id=ieooui></object>
-<style>
-st1\:*{behavior:url(#ieooui) }
-</style>
-<![endif]-->
-<style>
-<!--
- /* Font Definitions */
- @font-face
- {font-family:Courier;
- panose-1:2 7 4 9 2 2 5 2 4 4;
- mso-font-charset:0;
- mso-generic-font-family:modern;
- mso-font-format:other;
- mso-font-pitch:fixed;
- mso-font-signature:3 0 0 0 1 0;}
-@font-face
- {font-family:PMingLiU;
- panose-1:2 1 6 1 0 1 1 1 1 1;
- mso-font-alt:"Arial Unicode MS";
- mso-font-charset:136;
- mso-generic-font-family:auto;
- mso-font-format:other;
- mso-font-pitch:variable;
- mso-font-signature:1 134742016 16 0 1048576 0;}
-@font-face
- {font-family:"\@PMingLiU";
- panose-1:0 0 0 0 0 0 0 0 0 0;
- mso-font-charset:136;
- mso-generic-font-family:auto;
- mso-font-format:other;
- mso-font-pitch:variable;
- mso-font-signature:1 134742016 16 0 1048576 0;}
- /* Style Definitions */
- p.MsoNormal, li.MsoNormal, div.MsoNormal
- {mso-style-parent:"";
- margin:0in;
- margin-bottom:.0001pt;
- mso-pagination:widow-orphan;
- font-size:12.0pt;
- font-family:"Times New Roman";
- mso-fareast-font-family:PMingLiU;}
-h1
- {mso-style-next:Normal;
- margin-top:12.0pt;
- margin-right:0in;
- margin-bottom:3.0pt;
- margin-left:0in;
- mso-pagination:widow-orphan;
- page-break-after:avoid;
- mso-outline-level:1;
- font-size:16.0pt;
- font-family:Arial;
- mso-font-kerning:16.0pt;}
-h3
- {mso-style-link:"Heading 3 Char";
- mso-style-next:Normal;
- margin-top:12.0pt;
- margin-right:0in;
- margin-bottom:3.0pt;
- margin-left:0in;
- mso-pagination:widow-orphan;
- page-break-after:avoid;
- mso-outline-level:3;
- font-size:13.0pt;
- font-family:Arial;}
-span.Heading3Char
- {mso-style-name:"Heading 3 Char";
- mso-style-link:"Heading 3";
- mso-ansi-font-size:13.0pt;
- mso-bidi-font-size:13.0pt;
- font-family:Arial;
- mso-ascii-font-family:Arial;
- mso-fareast-font-family:PMingLiU;
- mso-hansi-font-family:Arial;
- mso-bidi-font-family:Arial;
- mso-ansi-language:EN-US;
- mso-fareast-language:ZH-TW;
- mso-bidi-language:AR-SA;
- font-weight:bold;}
-span.SpellE
- {mso-style-name:"";
- mso-spl-e:yes;}
-span.GramE
- {mso-style-name:"";
- mso-gram-e:yes;}
-@page Section1
- {size:8.5in 11.0in;
- margin:1.0in 1.25in 1.0in 1.25in;
- mso-header-margin:.5in;
- mso-footer-margin:.5in;
- mso-paper-source:0;}
-div.Section1
- {page:Section1;}
- /* List Definitions */
- @list l0
- {mso-list-id:199588104;
- mso-list-type:hybrid;
- mso-list-template-ids:2088654226 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
-@list l0:level1
- {mso-level-tab-stop:.5in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-@list l1
- {mso-list-id:262808332;
- mso-list-type:hybrid;
- mso-list-template-ids:-1723032724 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
-@list l1:level1
- {mso-level-tab-stop:.5in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-@list l2
- {mso-list-id:377050404;
- mso-list-type:hybrid;
- mso-list-template-ids:1608701434 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
-@list l2:level1
- {mso-level-tab-stop:.5in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-@list l3
- {mso-list-id:384645706;
- mso-list-type:hybrid;
- mso-list-template-ids:-1305694066 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
-@list l3:level1
- {mso-level-tab-stop:.5in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-@list l4
- {mso-list-id:738476941;
- mso-list-type:hybrid;
- mso-list-template-ids:-2031159454 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
-@list l4:level1
- {mso-level-tab-stop:.25in;
- mso-level-number-position:left;
- margin-left:.25in;
- text-indent:-.25in;}
-@list l5
- {mso-list-id:845051182;
- mso-list-type:hybrid;
- mso-list-template-ids:1881680384 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
-@list l5:level1
- {mso-level-tab-stop:.5in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-@list l6
- {mso-list-id:1374689416;
- mso-list-type:hybrid;
- mso-list-template-ids:-1094386728 67698689 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
-@list l6:level1
- {mso-level-number-format:bullet;
- mso-level-text:\F0B7;
- mso-level-tab-stop:.75in;
- mso-level-number-position:left;
- margin-left:.75in;
- text-indent:-.25in;
- font-family:Symbol;}
-ol
- {margin-bottom:0in;}
-ul
- {margin-bottom:0in;}
--->
-</style>
-<!--[if gte mso 10]>
-<style>
- /* Style Definitions */
- table.MsoNormalTable
- {mso-style-name:"Table Normal";
- mso-tstyle-rowband-size:0;
- mso-tstyle-colband-size:0;
- mso-style-noshow:yes;
- mso-style-parent:"";
- mso-padding-alt:0in 5.4pt 0in 5.4pt;
- mso-para-margin:0in;
- mso-para-margin-bottom:.0001pt;
- mso-pagination:widow-orphan;
- font-size:10.0pt;
- font-family:"Times New Roman";}
-</style>
-<![endif]-->
-</head>
-
-<body lang=EN-US style='tab-interval:.5in'>
-
-<div class=Section1>
-
-<h1 align=center style='text-align:center'>RDB Tutorial</h1>
-
-<p class=MsoNormal>This document walks you through the relational database (RDB)
-open source features in the Eclipse Web Tooling Project.<span
-style='mso-spacerun:yes'> </span>You must have either the RDB open source binaries
-or the source code downloaded from the Eclipse Web site. </p>
-
-<p class=MsoNormal><o:p> </o:p></p>
-
-<p class=MsoNormal>The supported features include the following:<o:p></o:p></p>
-
-<p class=MsoNormal><o:p> </o:p></p>
-
-<p class=MsoNormal><b style='mso-bidi-font-weight:normal'>Connection Wizard</b>
- Create a live connection to the database server using the JDBC driver.</p>
-
-<p class=MsoNormal><b style='mso-bidi-font-weight:normal'>Server Explorer</b>
-Support the live view of database server elements including tables, views, stored
-procedures, and user-defined functions. In the Server Explorer, you can also
-view a database sever in an offline mode.</p>
-
-<p class=MsoNormal><b style='mso-bidi-font-weight:normal'>Data Browse</b>
-Browse table content from the connected database server.</p>
-
-<p class=MsoNormal><b style='mso-bidi-font-weight:normal'>SQL Scrapbook</b> A
-SQL utility/editor which can be used to construct SQL commands to be executed
-to a connected server in the Server Explorer.</p>
-
-<p class=MsoNormal><o:p> </o:p></p>
-
-<p class=MsoNormal><span class=Heading3Char><span style='font-size:13.0pt'>Opening
-the RDB related view</span></span><br style='mso-special-character:line-break'>
-<![if !supportLineBreakNewLine]><br style='mso-special-character:line-break'>
-<![endif]></p>
-
-<p class=MsoNormal>From the Window -> Show View -> Others -> Server
-Explorer, select <b style='mso-bidi-font-weight:normal'>DB Output</b> and <b
-style='mso-bidi-font-weight:normal'>Server Explorer</b>.</p>
-
-<p class=MsoNormal><o:p> </o:p></p>
-
-<p class=MsoNormal><!--[if gte vml 1]><v:shapetype id="_x0000_t75" coordsize="21600,21600"
- o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe" filled="f"
- stroked="f">
- <v:stroke joinstyle="miter"/>
- <v:formulas>
- <v:f eqn="if lineDrawn pixelLineWidth 0"/>
- <v:f eqn="sum @0 1 0"/>
- <v:f eqn="sum 0 0 @1"/>
- <v:f eqn="prod @2 1 2"/>
- <v:f eqn="prod @3 21600 pixelWidth"/>
- <v:f eqn="prod @3 21600 pixelHeight"/>
- <v:f eqn="sum @0 0 1"/>
- <v:f eqn="prod @6 1 2"/>
- <v:f eqn="prod @7 21600 pixelWidth"/>
- <v:f eqn="sum @8 21600 0"/>
- <v:f eqn="prod @7 21600 pixelHeight"/>
- <v:f eqn="sum @10 21600 0"/>
- </v:formulas>
- <v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect"/>
- <o:lock v:ext="edit" aspectratio="t"/>
-</v:shapetype><v:shape id="_x0000_i1025" type="#_x0000_t75" style='width:221.25pt;
- height:315pt'>
- <v:imagedata src="images/image001.png" o:title=""/>
-</v:shape><![endif]--><![if !vml]><img width=295 height=420
-src="images/image002.jpg" v:shapes="_x0000_i1025"><![endif]></p>
-
-<p class=MsoNormal><o:p> </o:p></p>
-
-<p class=MsoNormal><span class=Heading3Char><span style='font-size:13.0pt'>Creating
-a new connection using the Connection wizard</span></span></p>
-
-<p class=MsoNormal><o:p> </o:p></p>
-
-<p class=MsoNormal>To create a new connection using the Connection wizard:</p>
-
-<p class=MsoNormal><o:p> </o:p></p>
-
-<ol style='margin-top:0in' start=1 type=1>
- <li class=MsoNormal style='mso-list:l5 level1 lfo1;tab-stops:list .5in'>In the
- Server Explorer window, right-click and select <b style='mso-bidi-font-weight:
- normal'>New Connection</b>.</li>
- <li class=MsoNormal style='mso-list:l5 level1 lfo1;tab-stops:list .5in'>Select
- the database that you would like to connect to, and fill in the JDBC
- connection information.</li>
-</ol>
-
-<p class=MsoNormal style='margin-left:.25in'><br>
-Note: The Connection wizard in the milestone II release only uses the final <b
-style='mso-bidi-font-weight:normal'>Connection</b> <b style='mso-bidi-font-weight:
-normal'>URL</b> string and the <b style='mso-bidi-font-weight:normal'>JDBC
-driver class </b>name to connect. The <b style='mso-bidi-font-weight:normal'>Test
-Connection</b> and <b style='mso-bidi-font-weight:normal'>Next</b> buttons will
-not show up unless all of the required information has been filled in.</p>
-
-<p class=MsoNormal><o:p> </o:p></p>
-
-<p class=MsoNormal style='margin-left:.75in;text-indent:-.25in;mso-list:l6 level1 lfo2;
-tab-stops:list .75in'><![if !supportLists]><span style='font-family:Symbol;
-mso-fareast-font-family:Symbol;mso-bidi-font-family:Symbol'><span
-style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>
-</span></span></span><![endif]>To connect to a <st1:City><st1:place>Derby</st1:place></st1:City>
-database:<br style='mso-special-character:line-break'>
-<![if !supportLineBreakNewLine]><br style='mso-special-character:line-break'>
-<![endif]></p>
-
-<p class=MsoNormal style='margin-left:.5in'><!--[if gte vml 1]><v:shape id="_x0000_i1026"
- type="#_x0000_t75" style='width:6in;height:6in'>
- <v:imagedata src="images/image003.png" o:title=""/>
-</v:shape><![endif]--><![if !vml]><img width=576 height=576
-src="images/image004.jpg" v:shapes="_x0000_i1026"><![endif]></p>
-
-<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
-
-<p class=MsoNormal style='margin-left:.75in;text-indent:-.25in;mso-list:l6 level1 lfo2;
-tab-stops:list .75in'><![if !supportLists]><span style='font-family:Symbol;
-mso-fareast-font-family:Symbol;mso-bidi-font-family:Symbol'><span
-style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>
-</span></span></span><![endif]>To connect to the SQL Server 2000 database<span
-class=GramE>:</span><br>
-<br>
-Note:<span style='mso-spacerun:yes'> </span>If you are connecting to SQL
-Server 2000 using the MS JDBC driver, you must specify the path to the three
-required jar files (for example, <span class=SpellE>mssqlserver.jar</span>, <span
-class=SpellE>msbase.jar</span>, and <span class=SpellE>msutil.jar</span>).</p>
-
-<p class=MsoNormal style='margin-left:.5in'><br>
-<!--[if gte vml 1]><v:shape id="_x0000_i1027" type="#_x0000_t75" style='width:6in;
- height:6in'>
- <v:imagedata src="images/image005.png" o:title=""/>
-</v:shape><![endif]--><![if !vml]><img width=576 height=576
-src="images/image006.jpg" v:shapes="_x0000_i1027"><![endif]></p>
-
-<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
-
-<p class=MsoNormal style='margin-left:.25in'>3.<span style='mso-spacerun:yes'>
-</span><span style='mso-spacerun:yes'> </span>Click <b style='mso-bidi-font-weight:
-normal'>Test Connection</b>.<o:p></o:p></p>
-
-<p class=MsoNormal><o:p> </o:p></p>
-
-<p class=MsoNormal style='margin-left:.25in'><!--[if gte vml 1]><v:shape id="_x0000_i1028"
- type="#_x0000_t75" style='width:330.75pt;height:109.5pt'>
- <v:imagedata src="images/image007.png" o:title=""/>
-</v:shape><![endif]--><![if !vml]><img width=441 height=146
-src="images/image008.jpg" v:shapes="_x0000_i1028"><![endif]></p>
-
-<p class=MsoNormal style='margin-left:.25in'><o:p> </o:p></p>
-
-<ol style='margin-top:0in' start=3 type=1>
- <li class=MsoNormal style='mso-list:l5 level1 lfo1;tab-stops:list .5in'>Click <b
- style='mso-bidi-font-weight:normal'>Next</b>.</li>
- <li class=MsoNormal style='mso-list:l5 level1 lfo1;tab-stops:list .5in'>Set
- filters as appropriate.<span style='mso-spacerun:yes'> </span>You can
- also filter after the connection is made.<br>
- <br>
- In a future milestone, you will be able to filter schemas, tables, views,
- stored procedures, and so on, from the folder in your Server Explorer.</li>
- <li class=MsoNormal style='mso-list:l5 level1 lfo1;tab-stops:list .5in'>Click <b
- style='mso-bidi-font-weight:normal'>Finish</b>.</li>
-</ol>
-
-<p class=MsoNormal style='margin-left:.25in'><o:p> </o:p></p>
-
-<p class=MsoNormal style='margin-left:.25in'>In the Server Explorer, expand the
-Server node and view the folders for schemas, tables, views, stored procedures,
-and so on.</p>
-
-<p class=MsoNormal><o:p> </o:p></p>
-
-<p class=MsoNormal style='margin-left:.25in'><!--[if gte vml 1]><v:shape id="_x0000_i1029"
- type="#_x0000_t75" style='width:459pt;height:140.25pt'>
- <v:imagedata src="images/image009.png" o:title=""/>
-</v:shape><![endif]--><![if !vml]><img width=612 height=187
-src="images/image010.jpg" v:shapes="_x0000_i1029"><![endif]></p>
-
-<p class=MsoNormal><o:p> </o:p></p>
-
-<p class=MsoNormal><span class=Heading3Char><span style='font-size:13.0pt'>Reconnecting
-to a server from the Server Explorer</span></span></p>
-
-<p class=MsoNormal><br>
-From the Server Explorer, you can reconnect to a server.<span
-style='mso-spacerun:yes'> </span>Right-click on the disconnected server, and
-select <b style='mso-bidi-font-weight:normal'>Reconnect</b>.</p>
-
-<p class=MsoNormal><o:p> </o:p></p>
-
-<p class=MsoNormal><!--[if gte vml 1]><v:shape id="_x0000_i1030" type="#_x0000_t75"
- style='width:6in;height:132.75pt'>
- <v:imagedata src="images/image011.png" o:title=""/>
-</v:shape><![endif]--><![if !vml]><img width=576 height=177
-src="images/image012.jpg" v:shapes="_x0000_i1030"><![endif]></p>
-
-<p class=MsoNormal><o:p> </o:p></p>
-
-<p class=MsoNormal>Work offline in Server Explorer:<br style='mso-special-character:
-line-break'>
-<![if !supportLineBreakNewLine]><br style='mso-special-character:line-break'>
-<![endif]></p>
-
-<p class=MsoNormal>To save a new object in the Server Explorer, right-click a
-server connection, and select <b style='mso-bidi-font-weight:normal'>Update
-Offline Items</b>.<span style='mso-spacerun:yes'> </span>Currently, the Server
-Explorer only supports read-only mode.<span style='mso-spacerun:yes'>
-</span>You can get read/write mode by generating a DDL to run on the database
-Server.</p>
-
-<p class=MsoNormal><o:p> </o:p></p>
-
-<p class=MsoNormal><!--[if gte vml 1]><v:shape id="_x0000_i1031" type="#_x0000_t75"
- style='width:6in;height:132pt'>
- <v:imagedata src="images/image013.png" o:title=""/>
-</v:shape><![endif]--><![if !vml]><img width=576 height=176
-src="images/image014.jpg" v:shapes="_x0000_i1031"><![endif]></p>
-
-<p class=MsoNormal><span class=Heading3Char><span style='font-size:13.0pt'><o:p> </o:p></span></span></p>
-
-<p class=MsoNormal><span class=Heading3Char><span style='font-size:13.0pt'>Browse
-Data feature<o:p></o:p></span></span></p>
-
-<p class=MsoNormal><o:p> </o:p></p>
-
-<p class=MsoNormal>To browse data:</p>
-
-<p class=MsoNormal><br>
-In the Server Explorer, right-click a table, and select <b style='mso-bidi-font-weight:
-normal'>Data -> Browse</b>.</p>
-
-<p class=MsoNormal><o:p> </o:p></p>
-
-<p class=MsoNormal><!--[if gte vml 1]><v:shape id="_x0000_i1039" type="#_x0000_t75"
- style='width:468pt;height:143.25pt'>
- <v:imagedata src="images/image015.png" o:title=""/>
-</v:shape><![endif]--><![if !vml]><img width=624 height=191
-src="images/image016.jpg" v:shapes="_x0000_i1039"><![endif]></p>
-
-<p class=MsoNormal><o:p> </o:p></p>
-
-<p class=MsoNormal>Here is an example of a result set of a table with data:<br>
-<span style='mso-spacerun:yes'> </span></p>
-
-<p class=MsoNormal><!--[if gte vml 1]><v:shape id="_x0000_i1032" type="#_x0000_t75"
- style='width:459pt;height:147.75pt'>
- <v:imagedata src="images/image017.png" o:title=""/>
-</v:shape><![endif]--><![if !vml]><img width=612 height=197
-src="images/image018.jpg" v:shapes="_x0000_i1032"><![endif]></p>
-
-<p class=MsoNormal><span class=Heading3Char><span style='font-size:13.0pt'><o:p> </o:p></span></span></p>
-
-<p class=MsoNormal><span class=Heading3Char><span style='font-size:13.0pt'>Opening
-the SQL Scrapbook</span></span><br style='mso-special-character:line-break'>
-<![if !supportLineBreakNewLine]><br style='mso-special-character:line-break'>
-<![endif]><b><span style='font-size:13.0pt;font-family:Arial'><o:p></o:p></span></b></p>
-
-<p class=MsoNormal>To open the SQL Scrapbook, you must have a project and a folder
-created.<span style='mso-spacerun:yes'> </span>You can open the SQL Scrapbook
-in two different ways:</p>
-
-<p class=MsoNormal><o:p> </o:p></p>
-
-<ol style='margin-top:0in' start=1 type=1>
- <li class=MsoNormal style='mso-list:l3 level1 lfo7;tab-stops:list .5in'>From
- the Server Explorer, click the <b style='mso-bidi-font-weight:normal'>Open
- SQL Scrapbook </b>icon.<br>
- <br>
- <!--[if gte vml 1]><v:shape id="_x0000_i1033" type="#_x0000_t75" style='width:6in;
- height:122.25pt'>
- <v:imagedata src="images/image019.png" o:title=""/>
- </v:shape><![endif]--><![if !vml]><img width=576 height=163
- src="images/image020.jpg" v:shapes="_x0000_i1033"><![endif]><br
- style='mso-special-character:line-break'>
- <![if !supportLineBreakNewLine]><br style='mso-special-character:line-break'>
- <![endif]></li>
- <li class=MsoNormal style='mso-list:l3 level1 lfo7;tab-stops:list .5in'>Choose
- a connection to associate your scrapbook with.<br>
- <br>
- <!--[if gte vml 1]><v:shape id="_x0000_i1034" type="#_x0000_t75" style='width:229.5pt;
- height:170.25pt'>
- <v:imagedata src="images/image021.png" o:title=""/>
- </v:shape><![endif]--><![if !vml]><img width=306 height=227
- src="images/image022.jpg" v:shapes="_x0000_i1034"><![endif]><br
- style='mso-special-character:line-break'>
- <![if !supportLineBreakNewLine]><br style='mso-special-character:line-break'>
- <![endif]></li>
- <li class=MsoNormal style='mso-list:l3 level1 lfo7;tab-stops:list .5in'>Specify
- a folder name and a name for your sqlpage file.<br style='mso-special-character:
- line-break'>
- <![if !supportLineBreakNewLine]><br style='mso-special-character:line-break'>
- <![endif]></li>
-</ol>
-
-<p class=MsoNormal><u>OR<br style='mso-special-character:line-break'>
-<![if !supportLineBreakNewLine]><br style='mso-special-character:line-break'>
-<![endif]><o:p></o:p></u></p>
-
-<ol style='margin-top:0in' start=1 type=1>
- <li class=MsoNormal style='mso-list:l2 level1 lfo5;tab-stops:list .5in'>Select
- the folder.</li>
- <li class=MsoNormal style='mso-list:l2 level1 lfo5;tab-stops:list .5in'>Click <b
- style='mso-bidi-font-weight:normal'>File -> New -> Others -> Data
- -> SQL Scrapbook page</b>.<br style='mso-special-character:line-break'>
- <![if !supportLineBreakNewLine]><br style='mso-special-character:line-break'>
- <![endif]></li>
-</ol>
-
-<p class=MsoNormal style='margin-left:.25in'><!--[if gte vml 1]><v:shape id="_x0000_i1035"
- type="#_x0000_t75" style='width:375pt;height:375pt'>
- <v:imagedata src="images/image023.png" o:title=""/>
-</v:shape><![endif]--><![if !vml]><img width=500 height=500
-src="images/image024.jpg" v:shapes="_x0000_i1035"><![endif]><br
-style='mso-special-character:line-break'>
-<![if !supportLineBreakNewLine]><br style='mso-special-character:line-break'>
-<![endif]></p>
-
-<ol style='margin-top:0in' start=3 type=1>
- <li class=MsoNormal style='mso-list:l2 level1 lfo5;tab-stops:list .5in'>Click <b
- style='mso-bidi-font-weight:normal'>Next</b>.</li>
- <li class=MsoNormal style='mso-list:l2 level1 lfo5;tab-stops:list .5in'>Type a
- name for your sqlpage file.<span style='mso-spacerun:yes'> </span>For
- example, CreateTable.sqlpage.</li>
- <li class=MsoNormal style='mso-list:l2 level1 lfo5;tab-stops:list .5in'>Click <b
- style='mso-bidi-font-weight:normal'>Finish</b>.</li>
- <li class=MsoNormal style='mso-list:l2 level1 lfo5;tab-stops:list .5in'>Click
- the <b style='mso-bidi-font-weight:normal'>Select Connection</b> icon on
- the toolbar to associate a connection to a SQL Scrapbook or a sqlpage
- file.<span style='mso-spacerun:yes'> </span>The Server Selection window
- opens.<span style='mso-spacerun:yes'> </span><br>
- <br>
- <!--[if gte vml 1]><v:shape id="_x0000_i1036" type="#_x0000_t75" style='width:372.75pt;
- height:425.25pt'>
- <v:imagedata src="images/image025.png" o:title=""/>
- </v:shape><![endif]--><![if !vml]><img width=497 height=567
- src="images/image026.jpg" v:shapes="_x0000_i1036"><![endif]><br
- style='mso-special-character:line-break'>
- <![if !supportLineBreakNewLine]><br style='mso-special-character:line-break'>
- <![endif]></li>
- <li class=MsoNormal style='mso-list:l2 level1 lfo5;tab-stops:list .5in'>Select
- a server, and click <b style='mso-bidi-font-weight:normal'>OK</b>.<br
- style='mso-special-character:line-break'>
- <![if !supportLineBreakNewLine]><br style='mso-special-character:line-break'>
- <![endif]></li>
-</ol>
-
-<p class=MsoNormal style='margin-left:.5in'><!--[if gte vml 1]><v:shape id="_x0000_i1037"
- type="#_x0000_t75" style='width:229.5pt;height:170.25pt'>
- <v:imagedata src="images/image021.png" o:title=""/>
-</v:shape><![endif]--><![if !vml]><img width=306 height=227
-src="images/image022.jpg" v:shapes="_x0000_i1037"><![endif]></p>
-
-<p class=MsoNormal>You can now start typing a SQL statement in the SQL
-scrapbook. <span style='mso-spacerun:yes'> </span>For example, <br
-style='mso-special-character:line-break'>
-<![if !supportLineBreakNewLine]><br style='mso-special-character:line-break'>
-<![endif]></p>
-
-<p class=MsoNormal><span style='font-family:Courier'>Create table <span
-class=SpellE>APP.Parent</span> (col1 integer not null, col2 <span class=GramE>char(</span>11),
-primary key(col1))<br style='mso-special-character:line-break'>
-<![if !supportLineBreakNewLine]><br style='mso-special-character:line-break'>
-<![endif]><o:p></o:p></span></p>
-
-<p class=MsoNormal>To run the SQL, click the <b style='mso-bidi-font-weight:
-normal'>Execute the SQL statement</b> icon. <br style='mso-special-character:
-line-break'>
-<![if !supportLineBreakNewLine]><br style='mso-special-character:line-break'>
-<![endif]></p>
-
-<p class=MsoNormal><!--[if gte vml 1]><v:shape id="_x0000_i1038" type="#_x0000_t75"
- style='width:441.75pt;height:282pt'>
- <v:imagedata src="images/image027.png" o:title=""/>
-</v:shape><![endif]--><![if !vml]><img width=589 height=376
-src="images/image028.jpg" v:shapes="_x0000_i1038"><![endif]></p>
-
-<p class=MsoNormal><o:p> </o:p></p>
-
-<p class=MsoNormal>After you run the SQL, the view is automatically
-refreshed.<span style='mso-spacerun:yes'> </span>If you want to manually
-refresh the view, right-click the folder in the Server Explorer, and select <b
-style='mso-bidi-font-weight:normal'>Refresh</b>.</p>
-
-<p class=MsoNormal><o:p> </o:p></p>
-
-</div>
-
-</body>
-
-</html>
diff --git a/community/tutorials/RDBTutorial/images/image001.png b/community/tutorials/RDBTutorial/images/image001.png
deleted file mode 100644
index 39fbadc..0000000
--- a/community/tutorials/RDBTutorial/images/image001.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image002.jpg b/community/tutorials/RDBTutorial/images/image002.jpg
deleted file mode 100644
index a3ce4bc..0000000
--- a/community/tutorials/RDBTutorial/images/image002.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image003.png b/community/tutorials/RDBTutorial/images/image003.png
deleted file mode 100644
index d64323d..0000000
--- a/community/tutorials/RDBTutorial/images/image003.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image004.jpg b/community/tutorials/RDBTutorial/images/image004.jpg
deleted file mode 100644
index f82074f..0000000
--- a/community/tutorials/RDBTutorial/images/image004.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image005.png b/community/tutorials/RDBTutorial/images/image005.png
deleted file mode 100644
index c2a964f..0000000
--- a/community/tutorials/RDBTutorial/images/image005.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image006.jpg b/community/tutorials/RDBTutorial/images/image006.jpg
deleted file mode 100644
index 21082e1..0000000
--- a/community/tutorials/RDBTutorial/images/image006.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image007.png b/community/tutorials/RDBTutorial/images/image007.png
deleted file mode 100644
index f351b98..0000000
--- a/community/tutorials/RDBTutorial/images/image007.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image008.jpg b/community/tutorials/RDBTutorial/images/image008.jpg
deleted file mode 100644
index a59c563..0000000
--- a/community/tutorials/RDBTutorial/images/image008.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image009.png b/community/tutorials/RDBTutorial/images/image009.png
deleted file mode 100644
index 7c89f53..0000000
--- a/community/tutorials/RDBTutorial/images/image009.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image010.jpg b/community/tutorials/RDBTutorial/images/image010.jpg
deleted file mode 100644
index 7738bbb..0000000
--- a/community/tutorials/RDBTutorial/images/image010.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image011.png b/community/tutorials/RDBTutorial/images/image011.png
deleted file mode 100644
index 94f6e65..0000000
--- a/community/tutorials/RDBTutorial/images/image011.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image012.jpg b/community/tutorials/RDBTutorial/images/image012.jpg
deleted file mode 100644
index d006a7c..0000000
--- a/community/tutorials/RDBTutorial/images/image012.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image013.png b/community/tutorials/RDBTutorial/images/image013.png
deleted file mode 100644
index fb258a0..0000000
--- a/community/tutorials/RDBTutorial/images/image013.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image014.jpg b/community/tutorials/RDBTutorial/images/image014.jpg
deleted file mode 100644
index 8d218b7..0000000
--- a/community/tutorials/RDBTutorial/images/image014.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image015.png b/community/tutorials/RDBTutorial/images/image015.png
deleted file mode 100644
index db03e9b..0000000
--- a/community/tutorials/RDBTutorial/images/image015.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image016.jpg b/community/tutorials/RDBTutorial/images/image016.jpg
deleted file mode 100644
index d52a314..0000000
--- a/community/tutorials/RDBTutorial/images/image016.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image017.png b/community/tutorials/RDBTutorial/images/image017.png
deleted file mode 100644
index 3b87a6e..0000000
--- a/community/tutorials/RDBTutorial/images/image017.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image018.jpg b/community/tutorials/RDBTutorial/images/image018.jpg
deleted file mode 100644
index 378e814..0000000
--- a/community/tutorials/RDBTutorial/images/image018.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image019.png b/community/tutorials/RDBTutorial/images/image019.png
deleted file mode 100644
index 1757fc6..0000000
--- a/community/tutorials/RDBTutorial/images/image019.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image020.jpg b/community/tutorials/RDBTutorial/images/image020.jpg
deleted file mode 100644
index 2be6fc3..0000000
--- a/community/tutorials/RDBTutorial/images/image020.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image021.png b/community/tutorials/RDBTutorial/images/image021.png
deleted file mode 100644
index 46bd296..0000000
--- a/community/tutorials/RDBTutorial/images/image021.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image022.jpg b/community/tutorials/RDBTutorial/images/image022.jpg
deleted file mode 100644
index 9ba922b..0000000
--- a/community/tutorials/RDBTutorial/images/image022.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image023.png b/community/tutorials/RDBTutorial/images/image023.png
deleted file mode 100644
index d9bc475..0000000
--- a/community/tutorials/RDBTutorial/images/image023.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image024.jpg b/community/tutorials/RDBTutorial/images/image024.jpg
deleted file mode 100644
index 94be6a6..0000000
--- a/community/tutorials/RDBTutorial/images/image024.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image025.png b/community/tutorials/RDBTutorial/images/image025.png
deleted file mode 100644
index 0211c3c..0000000
--- a/community/tutorials/RDBTutorial/images/image025.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image026.jpg b/community/tutorials/RDBTutorial/images/image026.jpg
deleted file mode 100644
index 46ee408..0000000
--- a/community/tutorials/RDBTutorial/images/image026.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image027.png b/community/tutorials/RDBTutorial/images/image027.png
deleted file mode 100644
index c72fed3..0000000
--- a/community/tutorials/RDBTutorial/images/image027.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/RDBTutorial/images/image028.jpg b/community/tutorials/RDBTutorial/images/image028.jpg
deleted file mode 100644
index 196980c..0000000
--- a/community/tutorials/RDBTutorial/images/image028.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ReintroducingSSE/ReintroducingSSE.html b/community/tutorials/ReintroducingSSE/ReintroducingSSE.html
deleted file mode 100644
index 7854dcd..0000000
--- a/community/tutorials/ReintroducingSSE/ReintroducingSSE.html
+++ /dev/null
@@ -1,999 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../../..//default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../../..//webtools/wtp.css" type="text/css">
-<title>
- Reintroducing the Structured Source Editing family of
- editors
- </title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">
- Reintroducing the Structured Source Editing family of
- editors
- </font>
-<br>
-<font class="indexsub">
- Reintroducing the Structured Source Editing family of
- editors
- </font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../../..//images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Structured Source Editing in Milestone 2</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The Structured Source Editing (SSE) family of editors are
- now available as part of WTP 1.0M2. They support editing
- XML, DTD, HTML, CSS, JavaScript, and JSP files. The SSE
- editors make significant usage of Eclipse frameworks as well
- as each other.
-
- For end users it means that they behave consistently with
- each other as well as with other Eclipse editors. Users of
- the JDT's Java editor will recognize many of the features
- they're used to seeing there available in many of the SSE
- editors:
- <ul>
-
-<li>Configurable syntax highlighting</li>
-
-<li>Editing of external files</li>
-
-<li>Quick Diff</li>
-
-<li>Delimiter matching</li>
-
-<li>Content Assist Templates</li>
-
-<li>Outline view with functional context menu</li>
-
-<li>Properties view</li>
-
-<li>
- Comment toggling and block commenting and
- uncommenting
- </li>
-
-<li>Line shifting</li>
-
-<li>Next/Previous Annotation navigation</li>
-
-<li>Finding All Occurrences in the file</li>
-
-<li>
- Highlighting for remote files (ex.: files opened
- from the CVS Explorer)
- </li>
-
-<li>
-
-<i>Source</i>
- menu actions in the Navigator
- </li>
-
-<li>
-
-<i>Navigate|Show In</i>
- menu in the editors
- </li>
-
-</ul>
- Settings for one language are reflected when editing other
- languages. For example, the CSS highlighting preferences are
- obeyed in the HTML editor while the CSS, HTML, and Java
- highlighting preferences are obeyed in the JSP editor.
- Refactoring changes made to Java files affect references in
- JSP files (and vice versa) and JSP files are included in
- Java search results.
- <br>
-
-<br>
- And there's
- <b>much</b>
- more. See the
- <a href="../../../wst/components/sse/featureTables/featureSummary.html">feature summary</a>
- for an overview of what editing feature is supported by
- which editor. Also see the
- <a href="../XMLCatalog/XMLCatalogTutorial.html">
- XML Catalog Tutorial
- </a>
- and the
- <a href="../XMLWizards/XMLWizards.html">
- New XML File Tutorial
- </a>
- for related information.
-
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">
- Content Assist
- <a name="contentassist"></a>
- </font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Content Assist provides a list of proposals, basically "text
- available to insert into the document", at the current
- cursor location. You can invoke Content Assist from the
- menu, or by pressing
- <b>Ctrl+Space</b>
- . Content Assist will always try to leave the document in a
- well-formed state after a proposal is inserted.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Content Assist is very sensitive to context. You will get
- different proposals depending where the caret is in the
- document.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- In a JSP file you have many different content types. In the
- HTML regions, you will get appropriate HTML tag proposals
- when you invoke content assist. In server-side scripting
- regions,(
- <code><%...%></code>
- ), you will get proposals for the scripting language of the
- JSP file. If the language is Java, you will get appropriate
- Java proposals for that cursor position.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- In a XML file, proposals may come from a referenced
- <i>content model</i>
- if a DTD or Schema is specified for the file, and then
- possibly through the
- <a href="#xml_catalog">XML Catalog</a>
- . This will give you "smarter" proposals, such as specific
- child element proposals within a given element, or required
- attribute proposals.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- In a HTML file, if you invoke Content Assist within a
- <b>style</b>
- tag or attribute you will get CSS Content Assist proposals:
- <br>
-
-<code>
- <b><p style="|"> text </p></b>
- </code>
-
-<br>
-
-<br>
-
- here you will get JavaScript proposals:
- <br>
-
-<code>
- <b><button onclick="|"> text </button></b>
- </code>
-
-<br>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">
- XML Catalog
- <a name="xml_catalog"></a>
- </font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Web Tools allows you to store DTDs or Schemas locally in the
- XML Catalog and have the documents map to PUBLIC ids. These
- ids are usually specified in XML documents via the
- <br>
-
-<code><!DOCTYPE></code>
- declaration. Users have the option of specifying a
- DTD/Schema via a SYSTEM id (local file system) or PUBLIC id
- (for pure catalog-based lookup).
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Examples of instructions placed at the top of an XML file
- defining grammar constraints :
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<code>
- <!DOCTYPE JobPosting SYSTEM "JobPosting.dtd">
- </code>
-
-<br>
- (looked up locally in the same folder as the XML file)
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<code>
- <!DOCTYPE JobPosting PUBLIC
- "www.blah.com/blah.dtd">
- </code>
-
-<br>
- (looked up in the catalog with "www.blah.com/blah.dtd" as a
- key)
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<code>
- <po:purchaseOrder xmlns:po="http://www.ibm.com"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://www.ibm.com PurchaseOrder.xsd
- ">
- </code>
-
-<br>
- (looked up in catalog with "http://www.ibm.com
- PurchaseOrder.xsd " as a key)
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>What are catalog entries used for?</b>
-
-<br>
- The DTD/Schema entries are used for a number of things. They
- can give you context sensitive
- <a href="#contentassist">Content Assist</a>
- proposals in a XML document. They give rules for what to
- mark as errors in as-you-type validation.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The Structured source editors support editing XHTML files.
- When users use any of the XHTML
- <code>DOCTYPE</code>
- (XHTML 1.0 Strict, XHTML 1.0 Transitional, XHTML 1.0
- Frameset) the content model for that particular
- <code>DOCTYPE</code>
- is followed. When users perform Content Assist within the
- document, they get the correct list of tags and attributes.
- Other editor functions will also respect the new
- well-formedness and validity constraints.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>When should you use catalog entries?</b>
- <b></b>
- Typically, DTDs and Schemas in a document are specified so
- they are availble via URL download as well as identified by
- ID. So if you are connected to the internet there would be
- no reason you would be required to use a catalog entry.
- However, if you ever work disconnected, you can download
- your own copy of the DTD to your local file system, and
- create a catalog entry for it, so it can be found whether
- connected or not. And, since the priority order of "lookup"
- is that it looks for catalog entries first, and then the
- network URL's, there is sometimes some performance advantage
- to having a local copy.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Editor-relevant preferences</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- All Structured source editors have a "Preferences.." action
- in the editor context menu. When this action is performed,
- the preferences relative to this editor are displayed in a
- dialog to the user.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><img border="0" src="images/pref_menu.jpg" alt="In editor preferences menu"></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- This allows users to change editor preferences easily and
- immediately without having to navigate the entire preference
- page tree.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<img border="0" src="images/pref_dialog.jpg" alt="In editor preferences">
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Hover Help</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Hover help is displayed when users mouse over text in
- Structured source editors.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><img border="1" src="images/hover.jpg" alt="Hover help"></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- There are several different types of hover help that can
- appear for the user.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<table border="BORDER">
-
-<tbody>
-
-<tr>
-
-<th width="50%">Text Hover Name</th>
- <th width="50%">Description</th>
-
-</tr>
-
-<tr>
-
-<td>Annotation Description</td>
- <td>
- Displays description of the current annotation
- shown in text. For example, if a task is
- highlighted in the editor and the user mouses
- over the task text, hover help displays the name
- of the task.
- </td>
-
-</tr>
-
-<tr>
-
-<td>Documentation Description</td>
- <td>
- Displays documentation of the text. For XML
- elements and attributes, the content model of
- the current element/attribute is displayed. If
- additional documentation information is included
- in the associated schema, that information is
- also displayed. For HTML elements, a description
- of the current tag is displayed. For HTML
- attributes and JSP tags/attributes, the content
- model of the currently selected tag/element is
- displayed. For JSP Java content, the JavaDoc for
- the currently selected object/method is
- displayed.
- </td>
-
-</tr>
-
-<tr>
-
-<td>Problem Description</td>
- <td>
- Displays description of the current problem
- shown in text. For example, if the user has an
- error in a XML file and the user mouse overs the
- text with the error indication, hover help
- displays the error description.
- </td>
-
-</tr>
-
-<tr>
-
-<td>Combined Hover</td>
- <td>
- Displays the description from the previously
- mentioned hover help types that best fits the
- currently selected text.
- </td>
-
-</tr>
-
-</tbody>
-
-</table>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The hover help displayed depends on the modifier keys users
- press when hovering over text. Users can control the type of
- hover help displayed in the Structured Text Editors Hovers
- preference page.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<img border="0" src="images/hoverspref.jpg" alt="Hover help preferences">
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Open Selection [with hyper-link support]</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Users are able to open on/navigate to the
- source/declaration/referred to file of certain tag
- attributes by using the Open Selection menu item (shortcut
- key F3 by default). They are also able to perform the same
- action by using a combination of pressing a modifier key
- (the Ctrl key by default) and their mouse to hover over the
- tag users want to open selection on. A hyperlink will then
- appear for users to click on to Open Selection.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<img border="1" src="images/openonlink.jpg" alt="Open on hyperlink">
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The file opened depends on the type of tag the user Open
- Selections on.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<table border="BORDER">
-
-<tbody>
-
-<tr>
-
-<th width="50%">Tag</th>
- <th width="50%">File opened</th>
-
-</tr>
-
-<tr>
-
-<td>
- any HTML tag that contains a URI attribute (as
- defined by the HTML 4.01 DTD) such as the Anchor
- tag
- </td>
- <td>the file located in the URI attribute value</td>
-
-</tr>
-
-<tr>
-
-<td>
- any JSP tag that contains a URI attribute (as
- defined by the JSP 1.2 Specification) such as
- the jsp:forward tag
- </td>
- <td>the file located in the URI attribute value</td>
-
-</tr>
-
-<tr>
-
-<td>jsp:useBean</td>
- <td>the class referenced by the useBean action</td>
-
-</tr>
-
-<tr>
-
-<td>JSP scriptlets</td>
- <td>selected Java element's declaration</td>
-
-</tr>
-
-<tr>
-
-<td>DOCTYPE Declaration</td>
- <td>the file referenced by the public/system ID</td>
-
-</tr>
-
-<tr>
-
-<td>Schema location attribute</td>
- <td>
- the file referenced by the schema location
- attribute
- </td>
-
-</tr>
-
-</tbody>
-
-</table>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Users can control behaviour of the hyperlink navigation in
- the Structured Text Editors Navigation preference page.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<img border="0" src="images/openonprefs.jpg" alt="Open on navigation preferences">
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">As-you-type validation</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Errors are found and displayed in the editor while editing
- the document.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>General XML syntax:</b>
-
-<br>
- General syntax for XML will be marked as you type. This
- includes errors such as missing quotes, missing brackets,
- missing end tags...
- <a href="#quickfix" alt="Quick Fix">Quick fix</a>
- will be provided for many of these syntax errors.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>DTD/Schema backed validation:</b>
-
-<br>
- If a DTD/Schema is specified in the XML file, as-you-type
- validation will enforce these constraints (eg. number of
- elements, children, names...), and mark errors in the file
- accordingly.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>JSP-Java validation:</b>
-
-<br>
- Server-side script regions (for the Java language) in JSP
- files will be marked with Java as-you-type errors (eg.
- missing imports, bad Java symbol references).
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>XML Catalog:</b>
-
-<br>
- The DTD/Schema specified in the XML can be available locally
- in the XML Catalog. An Internet connection need not be
- available.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Expand Selection To menu</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- You can quickly select XML elements using the Structured
- Selection feature. Highlight a XML element and press
- Alt+Shift+Arrow Up or select
- <b>Edit > Expand Selection To > Enclosing Element</b>
- from the menu bar - the selection will be expanded to the
- smallest XML element that contains the selection. You can
- then further expand the selection to the enclosing element,
- the next element, the previous element, or restore the last
- selection by selecting Enclosing Element, Next Element,
- Previous Element, or Restore Last Selection from the Edit >
- Expands Selection To menu bar respectively.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Smart Insert</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The XML Editor has a Smart Insert mode which can be toggled
- via
- <b>Edit > Smart Insert Mode</b>
- or Ctrl+Shift+Insert (by default). In Smart Insert mode, the
- editor provides language-specific extras. For example, when
- you start typing an end tag, "</", in a XML file after a
- start tag with its end tag missing, Smart Insert completes
- the end tag automatically. When you start typing the opening
- of a XML comment, "<!—", Smart Insert ends the comment
- for you by inserting the closing "-->", leaving the caret
- in the middle of the comment tag so you can continue typing
- the comment text.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Linked Editing</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- In Linked Edit mode, you may change multiple occurrences of
- a string in the file simultaneously. This is most easily
- seen through
- <a href="#quickfix" alt="Quick Fix">
- Quick Fix and Quick Assist
- </a>
- , such as the Quick Assist shown below for renaming an
- element:
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<img src="images/linkedit.jpg" alt="XML tag name linked editing">
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Formatting and Cleanup</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- XML Formatting lets you reformat the indentations and line
- delimiters, and reflow long lines of the selected XML
- element or the whole XML document. XML Formatting makes the
- document easier to read and better for printing. The XML
- formatting options are configured on the XML Source
- preference page (
- <b>
- Window > Preferences > Web and XML > XML Files
- > XML Source
- </b>
- ).
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<img src="images/format_block.jpg" alt="preference page block for XML formatting">
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Highlight a XML element and press Ctrl+I or select
- <b>Source > Format > Active Elements</b>
- from the menu bar to format the selected XML element. Press
- Ctrl+Shift+F or select
- <b>Source > Format > Document</b>
- from the menu bar to format the whole XML document.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- XML Cleanup lets you correct simple errors in the XML
- document such as adding required attributes that are
- missing, inserting missing begin or end tags, and quoting
- unquoted attribute values. Some convenient options, such as
- compressing empty element tags, formating the source, and
- converting line delimiters, are provided to make documents
- more consistent.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<img src="images/cleanup_dialog.jpg" alt="popup Cleanup dialog">
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">JavaScript Editor with Preview</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- With the help of the Outline view, the JavaScript Editor
- gives you a clear hierarchy view of the JavaScript variables
- and functions you have in the JavaScript file. JavaScript
- keywords are highlighted in different colors and Content
- Assist provides you with a list of suggested completions for
- partially entered strings along with visual indicators for
- the web browsers that support the method.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<img src="images/js_multipageeditor.jpg" alt="JavaScript Editor">
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- SSE provides two JavaScript editors differing only by the
- presence of a Preview page. The Preview Page in the
- JavaScript Editor lets you test your code by wrapping the
- file in a simple HTML file using a
- <b>script</b>
- tag. You may also preview the JavaScript file with any HTML
- file in the project that includes the JavaScript file.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<img src="images/js_default_preview.jpg" alt="JavaScript Editor's Preview page">
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Quick Fix and Quick Assist</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<a name="quickfix"></a>
- In the XML editor, if you see an error underlined with a
- squiggly line, position the caret inside the underlined
- range and press Ctrl+1 or select
- <b>Edit > Quick Fix</b>
- to see a list of suggested corrections.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<img src="images/quickfix.jpg" alt="XML Quick Fix example">
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Quick Assist proposals are available even if there is no
- problem or warning.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<img src="images/quickassist1.jpg" alt="XML Quick Assist example">
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Depending on the Quick Assist proposal, you may enter the
- Linked Edit mode where you may change multiple occurrences
- of a string in the file simultaneously.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<img src="images/quickassist2.jpg" alt="XML Quick Assist example with Rename Element chosen">
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Quick Fix and Quick Assist proposals for Java code embedded
- in JSP files are also available.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<img src="images/quickfix_java.jpg" alt="Quick Fix example of Java in the JSP editor">
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">JSP semantic highlighting</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The JSP editor allows you to highlight JSP and custom action
- tags differently from HTML and XML to help distinguish the
- JSP content from the its template content.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<img src="images/jsp_styles.jpg" alt="JSP Style preference page; the Java source is not itself highlighted in this preference page">
- <br>
-
-<i>
- Did you know that clicking in the sample text area
- automatically shows the style settings for that text's
- content type?
- </i>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">JSP Debugging</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The JSP editor can set breakpoints compatible with JSR-045
- compliant servers such as Apache Tomcat 5.0 and newer. As in
- the JDT Java editor, breakpoints are set using the ruler's
- context menu.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<img src="images/jsp_togglebreakpoint.jpg" alt="the JSP editor ruler context menu">
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- When stepping, local variables are visible as well as the
- JSP source itself.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<img src="images/jsp_debug1.jpg" alt="a JSP being debugged">
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The Debug perspective's Run menu and its accelerators are
- also made available.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<img src="images/jsp_debugmenu.jpg" alt="The Debug perspective's Run menu">
- </p>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/community/tutorials/ReintroducingSSE/ReintroducingSSE.xml b/community/tutorials/ReintroducingSSE/ReintroducingSSE.xml
deleted file mode 100644
index 1548c71..0000000
--- a/community/tutorials/ReintroducingSSE/ReintroducingSSE.xml
+++ /dev/null
@@ -1,643 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!-- Edited solely within the Web Tools Project XML Source Page Editor -->
-<?xml-stylesheet type="text/xsl" href="../../../../wtp.xsl"?>
-<html>
- <head>
- <meta name="root" content="../../../../../" />
- <title>
- Reintroducing the Structured Source Editing family of
- editors
- </title>
- </head>
- <body>
- <h1>
- Reintroducing the Structured Source Editing family of
- editors
- </h1>
-
- <h2>Structured Source Editing in Milestone 2</h2>
- <p>
- The Structured Source Editing (SSE) family of editors are
- now available as part of WTP 1.0M2. They support editing
- XML, DTD, HTML, CSS, JavaScript, and JSP files. The SSE
- editors make significant usage of Eclipse frameworks as well
- as each other.
-
- For end users it means that they behave consistently with
- each other as well as with other Eclipse editors. Users of
- the JDT's Java editor will recognize many of the features
- they're used to seeing there available in many of the SSE
- editors:
- <ul>
- <li>Configurable syntax highlighting</li>
- <li>Editing of external files</li>
- <li>Quick Diff</li>
- <li>Delimiter matching</li>
- <li>Content Assist Templates</li>
- <li>Outline view with functional context menu</li>
- <li>Properties view</li>
- <li>
- Comment toggling and block commenting and
- uncommenting
- </li>
- <li>Line shifting</li>
- <li>Next/Previous Annotation navigation</li>
- <li>Finding All Occurrences in the file</li>
- <li>
- Highlighting for remote files (ex.: files opened
- from the CVS Explorer)
- </li>
- <li>
- <i>Source</i>
- menu actions in the Navigator
- </li>
- <li>
- <i>Navigate|Show In</i>
- menu in the editors
- </li>
- </ul>
- Settings for one language are reflected when editing other
- languages. For example, the CSS highlighting preferences are
- obeyed in the HTML editor while the CSS, HTML, and Java
- highlighting preferences are obeyed in the JSP editor.
- Refactoring changes made to Java files affect references in
- JSP files (and vice versa) and JSP files are included in
- Java search results.
- <br />
- <br />
- And there's
- <b>much</b>
- more. See the
- <a href="../../../wst/components/sse/featureTables/featureSummary.html">feature summary</a>
- for an overview of what editing feature is supported by
- which editor. Also see the
- <a
- href="../XMLCatalog/XMLCatalogTutorial.html">
- XML Catalog Tutorial
- </a>
- and the
- <a
- href="../XMLWizards/XMLWizards.html">
- New XML File Tutorial
- </a>
- for related information.
-
- </p>
- <h2>
- Content Assist
- <a name="contentassist" />
- </h2>
-
- <p>
- Content Assist provides a list of proposals, basically "text
- available to insert into the document", at the current
- cursor location. You can invoke Content Assist from the
- menu, or by pressing
- <b>Ctrl+Space</b>
- . Content Assist will always try to leave the document in a
- well-formed state after a proposal is inserted.
- </p>
- <p>
- Content Assist is very sensitive to context. You will get
- different proposals depending where the caret is in the
- document.
- </p>
- <p>
- In a JSP file you have many different content types. In the
- HTML regions, you will get appropriate HTML tag proposals
- when you invoke content assist. In server-side scripting
- regions,(
- <code><%...%></code>
- ), you will get proposals for the scripting language of the
- JSP file. If the language is Java, you will get appropriate
- Java proposals for that cursor position.
- </p>
-
- <p>
- In a XML file, proposals may come from a referenced
- <i>content model</i>
- if a DTD or Schema is specified for the file, and then
- possibly through the
- <a href="#xml_catalog">XML Catalog</a>
- . This will give you "smarter" proposals, such as specific
- child element proposals within a given element, or required
- attribute proposals.
- </p>
- <p>
- In a HTML file, if you invoke Content Assist within a
- <b>style</b>
- tag or attribute you will get CSS Content Assist proposals:
- <br />
- <code>
- <b><p style="|"> text </p></b>
- </code>
- <br />
- <br />
-
- here you will get JavaScript proposals:
- <br />
- <code>
- <b><button onclick="|"> text </button></b>
- </code>
- <br />
- </p>
- <h2>
- XML Catalog
- <a name="xml_catalog" />
- </h2>
- <p>
- Web Tools allows you to store DTDs or Schemas locally in the
- XML Catalog and have the documents map to PUBLIC ids. These
- ids are usually specified in XML documents via the
- <br /><!-- prevent browsers from breaking the DOCTYPE decl into two lines -->
- <code><!DOCTYPE></code>
- declaration. Users have the option of specifying a
- DTD/Schema via a SYSTEM id (local file system) or PUBLIC id
- (for pure catalog-based lookup).
- </p>
- <p>
- Examples of instructions placed at the top of an XML file
- defining grammar constraints :
- </p>
- <p>
- <code>
- <!DOCTYPE JobPosting SYSTEM "JobPosting.dtd">
- </code>
- <br />
- (looked up locally in the same folder as the XML file)
- </p>
-
- <p>
- <code>
- <!DOCTYPE JobPosting PUBLIC
- "www.blah.com/blah.dtd">
- </code>
- <br />
- (looked up in the catalog with "www.blah.com/blah.dtd" as a
- key)
- </p>
-
- <p>
- <code>
- <po:purchaseOrder xmlns:po="http://www.ibm.com"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://www.ibm.com PurchaseOrder.xsd
- ">
- </code>
- <br />
- (looked up in catalog with "http://www.ibm.com
- PurchaseOrder.xsd " as a key)
- </p>
-
- <p>
- <b>What are catalog entries used for?</b>
- <br />
- The DTD/Schema entries are used for a number of things. They
- can give you context sensitive
- <a href="#contentassist">Content Assist</a>
- proposals in a XML document. They give rules for what to
- mark as errors in as-you-type validation.
- </p>
- <p>
- The Structured source editors support editing XHTML files.
- When users use any of the XHTML
- <code>DOCTYPE</code>
- (XHTML 1.0 Strict, XHTML 1.0 Transitional, XHTML 1.0
- Frameset) the content model for that particular
- <code>DOCTYPE</code>
- is followed. When users perform Content Assist within the
- document, they get the correct list of tags and attributes.
- Other editor functions will also respect the new
- well-formedness and validity constraints.
- </p>
- <p>
- <b>When should you use catalog entries?</b>
- <b />
- Typically, DTDs and Schemas in a document are specified so
- they are availble via URL download as well as identified by
- ID. So if you are connected to the internet there would be
- no reason you would be required to use a catalog entry.
- However, if you ever work disconnected, you can download
- your own copy of the DTD to your local file system, and
- create a catalog entry for it, so it can be found whether
- connected or not. And, since the priority order of "lookup"
- is that it looks for catalog entries first, and then the
- network URL's, there is sometimes some performance advantage
- to having a local copy.
- </p>
- <h2>Editor-relevant preferences</h2>
-
- <p>
- All Structured source editors have a "Preferences.." action
- in the editor context menu. When this action is performed,
- the preferences relative to this editor are displayed in a
- dialog to the user.
- </p>
- <img border="0" src="images/pref_menu.jpg"
- alt="In editor preferences menu" />
- <p>
- This allows users to change editor preferences easily and
- immediately without having to navigate the entire preference
- page tree.
- </p>
- <p>
- <img border="0" src="images/pref_dialog.jpg"
- alt="In editor preferences" />
- </p>
- <h2>Hover Help</h2>
- <p>
- Hover help is displayed when users mouse over text in
- Structured source editors.
- </p>
- <img border="1" src="images/hover.jpg" alt="Hover help" />
- <p>
- There are several different types of hover help that can
- appear for the user.
- </p>
- <table border="BORDER">
- <tbody>
- <tr>
- <th width="50%">Text Hover Name</th>
- <th width="50%">Description</th>
- </tr>
- <tr>
- <td>Annotation Description</td>
- <td>
- Displays description of the current annotation
- shown in text. For example, if a task is
- highlighted in the editor and the user mouses
- over the task text, hover help displays the name
- of the task.
- </td>
- </tr>
- <tr>
- <td>Documentation Description</td>
- <td>
- Displays documentation of the text. For XML
- elements and attributes, the content model of
- the current element/attribute is displayed. If
- additional documentation information is included
- in the associated schema, that information is
- also displayed. For HTML elements, a description
- of the current tag is displayed. For HTML
- attributes and JSP tags/attributes, the content
- model of the currently selected tag/element is
- displayed. For JSP Java content, the JavaDoc for
- the currently selected object/method is
- displayed.
- </td>
- </tr>
- <tr>
- <td>Problem Description</td>
- <td>
- Displays description of the current problem
- shown in text. For example, if the user has an
- error in a XML file and the user mouse overs the
- text with the error indication, hover help
- displays the error description.
- </td>
- </tr>
- <tr>
- <td>Combined Hover</td>
- <td>
- Displays the description from the previously
- mentioned hover help types that best fits the
- currently selected text.
- </td>
- </tr>
- </tbody>
- </table>
- <p>
- The hover help displayed depends on the modifier keys users
- press when hovering over text. Users can control the type of
- hover help displayed in the Structured Text Editors Hovers
- preference page.
- </p>
- <p>
- <img border="0" src="images/hoverspref.jpg"
- alt="Hover help preferences" />
- </p>
- <h2>Open Selection [with hyper-link support]</h2>
- <p>
- Users are able to open on/navigate to the
- source/declaration/referred to file of certain tag
- attributes by using the Open Selection menu item (shortcut
- key F3 by default). They are also able to perform the same
- action by using a combination of pressing a modifier key
- (the Ctrl key by default) and their mouse to hover over the
- tag users want to open selection on. A hyperlink will then
- appear for users to click on to Open Selection.
- </p>
- <p>
- <img border="1" src="images/openonlink.jpg"
- alt="Open on hyperlink" />
- </p>
- <p>
- The file opened depends on the type of tag the user Open
- Selections on.
- </p>
- <table border="BORDER">
- <tbody>
- <tr>
- <th width="50%">Tag</th>
- <th width="50%">File opened</th>
- </tr>
- <tr>
- <td>
- any HTML tag that contains a URI attribute (as
- defined by the HTML 4.01 DTD) such as the Anchor
- tag
- </td>
- <td>the file located in the URI attribute value</td>
- </tr>
- <tr>
- <td>
- any JSP tag that contains a URI attribute (as
- defined by the JSP 1.2 Specification) such as
- the jsp:forward tag
- </td>
- <td>the file located in the URI attribute value</td>
- </tr>
- <tr>
- <td>jsp:useBean</td>
- <td>the class referenced by the useBean action</td>
- </tr>
- <tr>
- <td>JSP scriptlets</td>
- <td>selected Java element's declaration</td>
- </tr>
- <tr>
- <td>DOCTYPE Declaration</td>
- <td>the file referenced by the public/system ID</td>
- </tr>
- <tr>
- <td>Schema location attribute</td>
- <td>
- the file referenced by the schema location
- attribute
- </td>
- </tr>
- </tbody>
- </table>
- <br />
- <p>
- Users can control behaviour of the hyperlink navigation in
- the Structured Text Editors Navigation preference page.
- </p>
- <p>
- <img border="0" src="images/openonprefs.jpg"
- alt="Open on navigation preferences" />
- </p>
- <h2>As-you-type validation</h2>
- <p>
- Errors are found and displayed in the editor while editing
- the document.
- </p>
- <p>
- <b>General XML syntax:</b>
- <br />
- General syntax for XML will be marked as you type. This
- includes errors such as missing quotes, missing brackets,
- missing end tags...
- <a href="#quickfix" alt="Quick Fix">Quick fix</a>
- will be provided for many of these syntax errors.
- </p>
- <p>
- <b>DTD/Schema backed validation:</b>
- <br />
- If a DTD/Schema is specified in the XML file, as-you-type
- validation will enforce these constraints (eg. number of
- elements, children, names...), and mark errors in the file
- accordingly.
- </p>
- <p>
- <b>JSP-Java validation:</b>
- <br />
- Server-side script regions (for the Java language) in JSP
- files will be marked with Java as-you-type errors (eg.
- missing imports, bad Java symbol references).
- </p>
- <p>
- <b>XML Catalog:</b>
- <br />
- The DTD/Schema specified in the XML can be available locally
- in the XML Catalog. An Internet connection need not be
- available.
- </p>
- <h2>Expand Selection To menu</h2>
-
- <p>
- You can quickly select XML elements using the Structured
- Selection feature. Highlight a XML element and press
- Alt+Shift+Arrow Up or select
- <b>Edit > Expand Selection To > Enclosing Element</b>
- from the menu bar - the selection will be expanded to the
- smallest XML element that contains the selection. You can
- then further expand the selection to the enclosing element,
- the next element, the previous element, or restore the last
- selection by selecting Enclosing Element, Next Element,
- Previous Element, or Restore Last Selection from the Edit >
- Expands Selection To menu bar respectively.
- </p>
- <h2>Smart Insert</h2>
-
- <p>
- The XML Editor has a Smart Insert mode which can be toggled
- via
- <b>Edit > Smart Insert Mode</b>
- or Ctrl+Shift+Insert (by default). In Smart Insert mode, the
- editor provides language-specific extras. For example, when
- you start typing an end tag, "</", in a XML file after a
- start tag with its end tag missing, Smart Insert completes
- the end tag automatically. When you start typing the opening
- of a XML comment, "<!—", Smart Insert ends the comment
- for you by inserting the closing "-->", leaving the caret
- in the middle of the comment tag so you can continue typing
- the comment text.
- </p>
-
- <h2>Linked Editing</h2>
-
- <p>
- In Linked Edit mode, you may change multiple occurrences of
- a string in the file simultaneously. This is most easily
- seen through
- <a href="#quickfix" alt="Quick Fix">
- Quick Fix and Quick Assist
- </a>
- , such as the Quick Assist shown below for renaming an
- element:
- </p>
- <p>
- <img src="images/linkedit.jpg"
- alt="XML tag name linked editing" />
- </p>
-
- <h2>Formatting and Cleanup</h2>
- <p>
- XML Formatting lets you reformat the indentations and line
- delimiters, and reflow long lines of the selected XML
- element or the whole XML document. XML Formatting makes the
- document easier to read and better for printing. The XML
- formatting options are configured on the XML Source
- preference page (
- <b>
- Window > Preferences > Web and XML > XML Files
- > XML Source
- </b>
- ).
- </p>
- <p>
- <img src="images/format_block.jpg"
- alt="preference page block for XML formatting" />
- </p>
- <p>
- Highlight a XML element and press Ctrl+I or select
- <b>Source > Format > Active Elements</b>
- from the menu bar to format the selected XML element. Press
- Ctrl+Shift+F or select
- <b>Source > Format > Document</b>
- from the menu bar to format the whole XML document.
- </p>
- <p>
- XML Cleanup lets you correct simple errors in the XML
- document such as adding required attributes that are
- missing, inserting missing begin or end tags, and quoting
- unquoted attribute values. Some convenient options, such as
- compressing empty element tags, formating the source, and
- converting line delimiters, are provided to make documents
- more consistent.
- </p>
- <p>
- <img src="images/cleanup_dialog.jpg"
- alt="popup Cleanup dialog" />
- </p>
- <h2>JavaScript Editor with Preview</h2>
-
- <p>
- With the help of the Outline view, the JavaScript Editor
- gives you a clear hierarchy view of the JavaScript variables
- and functions you have in the JavaScript file. JavaScript
- keywords are highlighted in different colors and Content
- Assist provides you with a list of suggested completions for
- partially entered strings along with visual indicators for
- the web browsers that support the method.
- </p>
- <p>
- <img src="images/js_multipageeditor.jpg"
- alt="JavaScript Editor" />
- </p>
- <p>
- SSE provides two JavaScript editors differing only by the
- presence of a Preview page. The Preview Page in the
- JavaScript Editor lets you test your code by wrapping the
- file in a simple HTML file using a
- <b>script</b>
- tag. You may also preview the JavaScript file with any HTML
- file in the project that includes the JavaScript file.
- </p>
- <p>
- <img src="images/js_default_preview.jpg"
- alt="JavaScript Editor's Preview page" />
- </p>
-
- <h2>Quick Fix and Quick Assist</h2>
- <p>
- <a name="quickfix" />
- In the XML editor, if you see an error underlined with a
- squiggly line, position the caret inside the underlined
- range and press Ctrl+1 or select
- <b>Edit > Quick Fix</b>
- to see a list of suggested corrections.
- </p>
- <p>
- <img src="images/quickfix.jpg"
- alt="XML Quick Fix example" />
- </p>
-
- <p>
- Quick Assist proposals are available even if there is no
- problem or warning.
- </p>
- <p>
- <img src="images/quickassist1.jpg"
- alt="XML Quick Assist example" />
- </p>
-
- <p>
- Depending on the Quick Assist proposal, you may enter the
- Linked Edit mode where you may change multiple occurrences
- of a string in the file simultaneously.
- </p>
- <p>
- <img src="images/quickassist2.jpg"
- alt="XML Quick Assist example with Rename Element chosen" />
- </p>
-
- <p>
- Quick Fix and Quick Assist proposals for Java code embedded
- in JSP files are also available.
- </p>
- <p>
- <img src="images/quickfix_java.jpg"
- alt="Quick Fix example of Java in the JSP editor" />
- </p>
-
- <h2>JSP semantic highlighting</h2>
- <p>
- The JSP editor allows you to highlight JSP and custom action
- tags differently from HTML and XML to help distinguish the
- JSP content from the its template content.
- </p>
- <p>
- <img src="images/jsp_styles.jpg"
- alt="JSP Style preference page; the Java source is not itself highlighted in this preference page" />
- <br />
- <i>
- Did you know that clicking in the sample text area
- automatically shows the style settings for that text's
- content type?
- </i>
- </p>
-
- <h2>JSP Debugging</h2>
- <p>
- The JSP editor can set breakpoints compatible with JSR-045
- compliant servers such as Apache Tomcat 5.0 and newer. As in
- the JDT Java editor, breakpoints are set using the ruler's
- context menu.
- </p>
- <p>
- <img src="images/jsp_togglebreakpoint.jpg"
- alt="the JSP editor ruler context menu" />
- </p>
- <p>
- When stepping, local variables are visible as well as the
- JSP source itself.
- </p>
- <p>
- <img src="images/jsp_debug1.jpg"
- alt="a JSP being debugged" />
- </p>
- <p>
- The Debug perspective's Run menu and its accelerators are
- also made available.
- </p>
- <p>
- <img src="images/jsp_debugmenu.jpg"
- alt="The Debug perspective's Run menu" />
- </p>
- <!-- removed info about 'debug mode' since its not required, and confused some users
- <p>
- You may have to enable the Server's
- <b>Tomcat debug mode</b>
- option to see the JSP source with Apache Tomcat servers.
- </p>
- <p>
- <img src="images/serverdebug.jpg"
- alt="The Debug perspective's Run menu" />
- </p>
- -->
-
- </body>
-</html>
\ No newline at end of file
diff --git a/community/tutorials/ReintroducingSSE/images/cleanup_dialog.jpg b/community/tutorials/ReintroducingSSE/images/cleanup_dialog.jpg
deleted file mode 100644
index 4a5d2f6..0000000
--- a/community/tutorials/ReintroducingSSE/images/cleanup_dialog.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ReintroducingSSE/images/format_block.jpg b/community/tutorials/ReintroducingSSE/images/format_block.jpg
deleted file mode 100644
index 7179feb..0000000
--- a/community/tutorials/ReintroducingSSE/images/format_block.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ReintroducingSSE/images/hover.jpg b/community/tutorials/ReintroducingSSE/images/hover.jpg
deleted file mode 100644
index 7ce445c..0000000
--- a/community/tutorials/ReintroducingSSE/images/hover.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ReintroducingSSE/images/hoverspref.jpg b/community/tutorials/ReintroducingSSE/images/hoverspref.jpg
deleted file mode 100644
index c394739..0000000
--- a/community/tutorials/ReintroducingSSE/images/hoverspref.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ReintroducingSSE/images/js_default_preview.jpg b/community/tutorials/ReintroducingSSE/images/js_default_preview.jpg
deleted file mode 100644
index 9e51e76..0000000
--- a/community/tutorials/ReintroducingSSE/images/js_default_preview.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ReintroducingSSE/images/js_multipageeditor.jpg b/community/tutorials/ReintroducingSSE/images/js_multipageeditor.jpg
deleted file mode 100644
index af6443a..0000000
--- a/community/tutorials/ReintroducingSSE/images/js_multipageeditor.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ReintroducingSSE/images/jsp_debug1.jpg b/community/tutorials/ReintroducingSSE/images/jsp_debug1.jpg
deleted file mode 100644
index 8b52ff0..0000000
--- a/community/tutorials/ReintroducingSSE/images/jsp_debug1.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ReintroducingSSE/images/jsp_debugmenu.jpg b/community/tutorials/ReintroducingSSE/images/jsp_debugmenu.jpg
deleted file mode 100644
index b4ff2e5..0000000
--- a/community/tutorials/ReintroducingSSE/images/jsp_debugmenu.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ReintroducingSSE/images/jsp_styles.jpg b/community/tutorials/ReintroducingSSE/images/jsp_styles.jpg
deleted file mode 100644
index 22dc9c3..0000000
--- a/community/tutorials/ReintroducingSSE/images/jsp_styles.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ReintroducingSSE/images/jsp_togglebreakpoint.jpg b/community/tutorials/ReintroducingSSE/images/jsp_togglebreakpoint.jpg
deleted file mode 100644
index 9dc0842..0000000
--- a/community/tutorials/ReintroducingSSE/images/jsp_togglebreakpoint.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ReintroducingSSE/images/linkedit.jpg b/community/tutorials/ReintroducingSSE/images/linkedit.jpg
deleted file mode 100644
index d42db25..0000000
--- a/community/tutorials/ReintroducingSSE/images/linkedit.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ReintroducingSSE/images/openonlink.jpg b/community/tutorials/ReintroducingSSE/images/openonlink.jpg
deleted file mode 100644
index 649f048..0000000
--- a/community/tutorials/ReintroducingSSE/images/openonlink.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ReintroducingSSE/images/openonprefs.jpg b/community/tutorials/ReintroducingSSE/images/openonprefs.jpg
deleted file mode 100644
index 63a49a1..0000000
--- a/community/tutorials/ReintroducingSSE/images/openonprefs.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ReintroducingSSE/images/pref_dialog.jpg b/community/tutorials/ReintroducingSSE/images/pref_dialog.jpg
deleted file mode 100644
index 0ec7a63..0000000
--- a/community/tutorials/ReintroducingSSE/images/pref_dialog.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ReintroducingSSE/images/pref_menu.jpg b/community/tutorials/ReintroducingSSE/images/pref_menu.jpg
deleted file mode 100644
index e87bd09..0000000
--- a/community/tutorials/ReintroducingSSE/images/pref_menu.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ReintroducingSSE/images/quickassist1.jpg b/community/tutorials/ReintroducingSSE/images/quickassist1.jpg
deleted file mode 100644
index 4100fd9..0000000
--- a/community/tutorials/ReintroducingSSE/images/quickassist1.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ReintroducingSSE/images/quickassist2.jpg b/community/tutorials/ReintroducingSSE/images/quickassist2.jpg
deleted file mode 100644
index aef9352..0000000
--- a/community/tutorials/ReintroducingSSE/images/quickassist2.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ReintroducingSSE/images/quickfix.jpg b/community/tutorials/ReintroducingSSE/images/quickfix.jpg
deleted file mode 100644
index 65c01dd..0000000
--- a/community/tutorials/ReintroducingSSE/images/quickfix.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ReintroducingSSE/images/quickfix_java.jpg b/community/tutorials/ReintroducingSSE/images/quickfix_java.jpg
deleted file mode 100644
index cfe190d..0000000
--- a/community/tutorials/ReintroducingSSE/images/quickfix_java.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/SchoolSchedule/BuildingAScheduleWebApp.html b/community/tutorials/SchoolSchedule/BuildingAScheduleWebApp.html
deleted file mode 100644
index 4788db5..0000000
--- a/community/tutorials/SchoolSchedule/BuildingAScheduleWebApp.html
+++ /dev/null
@@ -1,599 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../..//default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../..//webtools/wtp.css" type="text/css">
-<title>WTP Tutorials - Building a School Schedule Web Application</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">WTP Tutorials - Building a School Schedule Web Application</font>
-<br>
-<font class="indexsub">WTP Tutorials - Building a School Schedule Web Application</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../..//images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>By Lawrence Mandel</b>
-<BR>
-January 24, 2005<BR>
-
-<BR>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>In this tutorial you will create a school schedule Web application. This application will allow students to input their courses and create a schedule. This tutorial will introduce you to JSP's, servlets and the Web Tools Platform project's server tools.
-<BR>
-
-
-</P>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Prerequisites For The Tutorial</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>Web Tools Platform (WTP) project<BR>The WTP project can be downloaded from <a href="http://download.eclipse.org/webtools/downloads/">http://download.eclipse.org/webtools/downloads/</a>
-<BR>
-<BR>
-
-</LI>
-
-<LI>Tomcat 5.0.28<BR>Tomcat is available from <a href="http://jakarta.apache.org/tomcat/" target="_top">http://jakarta.apache.org/tomcat/</a>
-<BR>
-<BR>
-</LI>
-
-<LI>JDK 1.4.2<BR>Sun's JDK is available from <a href="http://java.sun.com/j2se/1.4.2/download.html" target="_top">http://java.sun.com/j2se/1.4.2/download.html</a>
-<BR>
-<BR>
-
-</LI>
-
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Installing The Tomcat Runtime In Eclipse</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>In order to run the Web application from Eclipse (which will allow you to test and debug the application) Eclipse has to be told where to find Tomcat and where to find the JDK. Tomcat requires a JDK so it can compile servlets and JSPs.</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>Select Window -> Preferences<B></B>.<BR>
-
-<IMG border="0" src="images/webapp1.gif" width="550" height="340"><BR>
-<BR>
-</LI>
-
-<LI>Select Java -> Installed JREs from the menu on the left.<BR>
-
-<IMG border="0" src="images/webapp2.gif" width="574" height="513"><BR>
-<BR>
-</LI>
-
-<LI>Select Add... The Add JRE dialog will open. Select Browse for the JRE home directory and choose the location where you installed the JDK 1.4.2. Name the runtime Sun JDK 1.4.2 and click OK.<BR>
-
-<IMG border="0" src="images/webapp3.gif" width="485" height="441"><BR>
-<BR>
-</LI>
-
-<LI>The Sun JDK 1.4.2 now shows on the list of installed runtimes. Click OK.<BR>
-
-<IMG border="0" src="images/webapp4.gif" width="574" height="513"><BR>
-<BR>
-</LI>
-
-<LI>Select Window -> Preferences.<BR>
-<BR>
-</LI>
-
-<LI>Select Server -> Installed Runtimes from the menu on the left.<BR>
-
-<IMG border="0" src="images/webapp5.gif" width="574" height="513"><BR>
-<BR>
-</LI>
-
-<LI>Click on Add... Select Apache -> Apache Tomcat v5.0 and click Next. Click Browse and select the location where you installed Tomcat. Select the Sun JDK 1.4.2 that you just installed and click Finish.<BR>
-
-<IMG border="0" src="images/webapp6.gif" width="438" height="422"><BR>
-<BR>
-</LI>
-
-<LI>Click OK to close the preferences dialog. Both the JDK and Tomcat are now configured in Eclipse.</LI>
-
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Creating A J2EE Project</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>You will now create a J2EE Web project in which you will create the School Schedule application.</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>Select File -> New -> Project. Select Web -> J2EE Web Project and click Next.<BR>
-
-<IMG border="0" src="images/webapp7.gif" width="500" height="500"><BR>
-<BR>
-</LI>
-
-<LI>Name the project SchoolSchedule, deselect Add module to an EAR project and click Finish. <BR>
-
-<IMG border="0" src="images/webapp8.gif" width="504" height="502">
- <BR>You will be prompted to switch to the J2EE perspective. Click Yes.<BR>
-<BR>
-</LI>
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Creating Class and Schedule Containers</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>For your web application to pass class information between the JSP page that displays the schedule and the servlet that registers the classes with the schedule you will need a representation of a class and a representation of a schedule. A class will have a title, day of week, start time and end time. A schedule will be a collection of classes. To implement these two objects you will create two classes; SchoolClass and SchoolSchedule.</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>Right click on the JavaSource folder and select New -> Class. Name the class SchoolClass and set the package to org.eclipse.wtp.sample.classschedule. Click Finish. The SchoolClass class will now appear in the JavaSource folder and open in the Java editor.<BR>
-
-<IMG border="0" src="images/webapp9.gif" width="495" height="563"><BR>
-<BR>
-</LI>
-
-<LI>We said earlier that a SchoolClass object will need to hold a title, day, start time and end time. Create private variables for each of these.The title should be of type String and the rest should be of type int.<P id="code">private String title;<BR>
- private int startTime;<BR>
- private int endTime;<BR>
- private int day;</P>
-</LI>
-
-<LI>This information should be set when an instance of SchoolClass is created so you will need to create a constructor that will accept the four pieces of information. Create a constructor that takes in the four parameters and sets the class variables.<P id="code">public SchoolClass(String title, int startTime,
- int endTime, int day)<BR>
- {<BR>
- this.title = title;<BR>
- this.startTime = startTime;<BR>
- this.endTime = endTime;<BR>
- this.day = day;<BR>
- }</P>
-</LI>
-
-<LI>You now need to create a way to access the object's information. Right click in the editor and select Source -> Generate Getters and Setters... (Note: ensure you click within the class' curly braces.)<BR>
-
-<IMG border="0" src="images/webapp10.gif" width="640" height="396"><BR>
-<BR>
-</LI>
-
-<LI>Click Select Getters on the right. The four getter methods are now selected. Click OK.<BR>
-
-<IMG border="0" src="images/webapp11.gif" width="432" height="581"><BR>
-<BR>
-</LI>
-
-<LI>Save the SchoolClass file.<BR>
-<BR>
-</LI>
-
-<LI>You will now create the SchoolSchedule class which will act as a container for all of the classes. Right click on the package org.eclipse.wtp.sample.classschedule and select New -> Class. Notice that the package field is automatically populated. Name the class SchoolSchedule and click Finish.<BR>
-<BR>
-</LI>
-
-<LI>Add a private list of classes to the SchoolSchedule class.
- <P id="code">private List classes = new ArrayList();</P>The List and ArrayList classes are underlined and flagged as errors as they have not yet been imported. Right click in the editor and select Source -> Organize Imports. Select java.util.List and click Finish. The necessary import statements will be added to the class.<BR>
-<BR>
-</LI>
-
-<LI>Create the getter method for the classes list by right clicking in the editor within the class and selecting Source -> Generate Getters and Setters... Click Select Getters on the right and click OK.<BR>
-<BR>
-</LI>
-
-<LI>You now need to create a method to add new classes to the list. Create a method named addClass that takes a parameter of SchoolClass and adds it to the list.
- <P id="code">
- public void addClass(SchoolClass schoolClass)<BR>
- {<BR>
- classes.add(schoolClass);<BR>
- }
- </P>
-</LI>
-
-<LI>Save the file.<BR>
-<BR>
-</LI>
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Adding Classes To The Schedule</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P> You will now create a Java Server Page (JSP) that will allow students to add a class to their schedule. JSPs provide a way to access information stored in Java objects and perform Java operations within an HTML page. Your JSP will contain a form where students can submit their information. In the following section you will create an action to process the form submission.</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>Right click on the WebContent folder and select New -> Other... Select Simple and then File. Click Next.<BR>
-
-<IMG border="0" src="images/webapp12.gif" width="500" height="400">
- <BR>Name the file Schedule.jsp and click Finish.
- The Schedule.jsp file opens in the JSP source page editor.<BR>
-<BR>
-</LI>
-
-<LI>You now need to create the form to submit courses. The structure of a JSP page is very similar to that of an HTML page. A JSP page can simply use more tags and offer more functionality. In this step you will really just be creating an HTML page with a form. Create an HTML page with a form that has a text box for submitting a title, check boxes for the days of the week, and a drop-down menu for both the start time and end time of the class. The form will also need a submit button. You should ignore the action attribute on the FORM element for now. We will look at this in the next section when you create your submit action.<P id="code">
- <HTML><BR>
- <HEAD><BR>
- <TITLE>Student Schedule</TITLE><BR>
- </HEAD><BR>
-
-<BR>
- <BODY><BR>
- <FORM action="" method="post"><BR>
- Course Name: <INPUT type="text" name="title" size="35"><BR><BR>
- Course Time: <BR>
- Sun<INPUT type="checkbox" name="day" value="sun"> <BR>
- Mon<INPUT type="checkbox" name="day" value="mon"> <BR>
- Tue<INPUT type="checkbox" name="day" value="tue"> <BR>
- Wed<INPUT type="checkbox" name="day" value="wed"> <BR>
- Thu<INPUT type="checkbox" name="day" value="thu"> <BR>
- Fri<INPUT type="checkbox" name="day" value="fri"> <BR>
- Sat<INPUT type="checkbox" name="day" value="sat"> <BR>
- <SELECT name="starttime"><BR>
- <OPTION value="8">8:00am</OPTION><BR>
- <OPTION value="9">9:00am</OPTION><BR>
- <OPTION value="10">10:00am</OPTION><BR>
- <OPTION value="11">11:00am</OPTION><BR>
- <OPTION value="12">12:00pm</OPTION><BR>
- <OPTION value="13">1:00pm</OPTION><BR>
- <OPTION value="14">2:00pm</OPTION><BR>
- <OPTION value="15">3:00pm</OPTION><BR>
- <OPTION value="16">4:00pm</OPTION><BR>
- <OPTION value="17">5:00pm</OPTION><BR>
- <OPTION value="18">6:00pm</OPTION><BR>
- <OPTION value="19">7:00pm</OPTION><BR>
- <OPTION value="20">8:00pm</OPTION><BR>
- <OPTION value="21">9:00pm</OPTION><BR>
- </SELECT> <BR>
- to <BR>
- <SELECT name="endtime"><BR>
- <OPTION value="9">9:00am</OPTION><BR>
- <OPTION value="10">10:00am</OPTION><BR>
- <OPTION value="11">11:00am</OPTION><BR>
- <OPTION value="12">12:00pm</OPTION><BR>
- <OPTION value="13">1:00pm</OPTION><BR>
- <OPTION value="14">2:00pm</OPTION><BR>
- <OPTION value="15">3:00pm</OPTION><BR>
- <OPTION value="16">4:00pm</OPTION><BR>
- <OPTION value="17">5:00pm</OPTION><BR>
- <OPTION value="18">6:00pm</OPTION><BR>
- <OPTION value="19">7:00pm</OPTION><BR>
- <OPTION value="20">8:00pm</OPTION><BR>
- <OPTION value="21">9:00pm</OPTION><BR>
- <OPTION value="22">10:00pm</OPTION><BR>
- </SELECT><BR>
- <BR><BR>
- <BR><BR>
- <INPUT type="submit" name="Submit" value="Add Course"><BR>
- </FORM><BR>
-
-<BR>
- </BODY><BR>
- </HTML></P>Save the file.</LI>
-
-<LI>You should now test that your page looks correct. To do this you will run the current version of your application of the Tomcat server you configured earlier. Right click on Schedule.jsp and select Run As -> Run on Server... Select Tomcat v5.0 Server. Ensure that Set server as project default is selected and click Next.<BR>
-
-<IMG border="0" src="images/webapp13.gif" width="536" height="594"><BR>
-<BR>
-
-</LI>
-
-<LI>Ensure that your SchoolSchedule project is listed under Configured projects. If it is not, add it to the list of Configured projects by selecting it and then selecting Add. Click Finish.<BR>
-<BR>
-</LI>
-
-<LI>Eclipse will now startup the Tomcat server and then display your page in the internal Web browser. Your page should look something like the following screen shot.<BR>
-
-<IMG border="0" src="images/webapp14.gif" width="653" height="408"></LI>
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">The Submit Action</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>When the form in Schedule.jsp is submitted an action needs to be performed on the data. In this section you will create a servlet that processes the input from the form, creates the necessary SchoolClass objects and adds them to the SchoolSchedule. A servlet is a Java class that executes on the server. In order to have the class information from previous submits stay available the SchoolSchedule will be added to a session object. (If you do not do this the schedule will only be able to show the information from the last form submission.)</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>To create the servlet right click on the org.eclipse.wtp.sample.classschedule package and select New -> Class. Name the servlet ScheduleServlet. Select Browse next to Superclass and select javax.servlet.http.HttpServlet. Select Add next to Interfaces and add javax.servlet.Servlet. Click Finish.<BR>
-
-<IMG border="0" src="images/webapp15.gif" width="495" height="563"><BR>
-<BR>
-
-</LI>
-
-<LI>Your newly created ScheduleServlet will appear in the JavaSource folder and open in the Java editor. Right click in the editor and select Source -> Override/Implement Methods...<BR>
-
-<IMG border="0" src="images/webapp16.gif" width="595" height="327"><BR>
-<BR>
-
-</LI>
-
-<LI>Select the doPost(HttpServletRequest, HttpServletResponse) method and click OK. The doPost method will now show in your ScheduleServlet class. Rename arg0 to request and arg1 to response.<BR>
-<BR>
-</LI>
-
-<LI>The doPost method is where you will take the input from the form and
- perform your actions. The doPost method is used because you specified that
- your form would submit data using the POST method. You could also have
- used the GET method in which case your servlet would need to implement
- doGet instead of doPost.<BR>
-
-<BR>
- The first thing you need to do in the doPost method is read in the information submitted by the form. This information can be obtained through the request object's getParameter method. the getParameterValues method is used for the days as there may be more than one day selected.<P id="code">String title = request.getParameter("title");<BR>
- int starttime = Integer.parseInt(request.getParameter("starttime"));<BR>
- int endtime = Integer.parseInt(request.getParameter("endtime"));<BR>
- String[] days = request.getParameterValues("day");
-</P>
-
-</LI>
-
-<LI>The next step is to obtain the existing SchoolSchedule, if there is one, or to create a new one if one hasn't been created yet.
- <P id="code">SchoolSchedule schedule = <BR>
- (SchoolSchedule)request.getSession(true).getAttribute("schoolschedule");<BR>
- if(schedule == null)<BR>
- {<BR>
- schedule = new SchoolSchedule();<BR>
- }
- </P>
-</LI>
-
-<LI>Now you will create new SchoolClass objects. As there may be many days for the school class you are adding you will iterate over all of the days and create a new SchoolClass object for each day that was selected. Creating SchoolClass objects in this way will make displaying them via the Schedule.jsp easier.
- After a SchoolClass object is created you will add it to the schedule.<P id="code">
- if(days != null)<BR>
- {<BR>
- for(int i = 0; i < days.length; i++)<BR>
- {<BR>
- String dayString = days[i];<BR>
- int day;<BR>
- if(dayString.equalsIgnoreCase("SUN")) day = 0;<BR>
- else if(dayString.equalsIgnoreCase("MON")) day = 1;<BR>
- else if(dayString.equalsIgnoreCase("TUE")) day = 2;<BR>
- else if(dayString.equalsIgnoreCase("WED")) day = 3;<BR>
- else if(dayString.equalsIgnoreCase("THU")) day = 4;<BR>
- else if(dayString.equalsIgnoreCase("FRI")) day = 5;<BR>
- else day = 6;<BR>
-
-<BR>
- SchoolClass clazz = new SchoolClass(title, starttime, endtime, day);<BR>
- schedule.addClass(clazz);<BR>
- }<BR>
- }
- </P>
-
-</LI>
-
-<LI>You need to set the schedule in the session so Schedule.jsp will have access to it and forward control back to Schedule.jsp.
- <P id="code">request.getSession().setAttribute("schoolschedule", schedule);<BR>
- getServletContext().getRequestDispatcher("/Schedule.jsp").forward(request, response);
- </P>
-
-</LI>
-
-<LI>Save the class.<BR>
-<BR>
-</LI>
-
-<LI>You have now created your servlet but your Web application does not yet know about it. In order for your Web application to know about the servlet you will have to define it in the Deployment Descriptor. Double click on the Deployment Descriptor under the SchoolSchedule project and copy the following lines under the display element
- <P id="code">
- <servlet><BR>
- <description></description><BR>
- <display-name>Schedule</display-name><BR>
- <servlet-name>Schedule</servlet-name><BR>
- <servlet-class><BR>
- org.eclipse.wtp.sample.classschedule.ScheduleServlet<BR>
- </servlet-class><BR>
- </servlet><BR>
- <servlet-mapping><BR>
- <servlet-name>Schedule</servlet-name><BR>
- <url-pattern>/Schedule</url-pattern><BR>
- </servlet-mapping>
- </P>
-
-</LI>
-
-<LI>
- Now that you have defined where your servlet action is located you can specify the location in your Schedule JSP. Open the Schedule.jsp file and specify the action location of your form.
- <P id="code">
- <FORM action="/SchoolSchedule/Schedule" method="post"><BR>
-
-</P>
-
-</LI>
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Displaying The Schedule</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>
-Your servlet has now been defined with your Web application and is ready to be used. You can now return to Schedule.jsp and work on displaying the Schedule. In this section you will use some of the custom tag libraries that are available for working with JSPs.</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>In order to use the standard tag libraries you will first have to download and install them into our project. Open your Web browser to <a href="http://jakarta.apache.org/taglibs/" target="_top">http://jakarta.apache.org/taglibs/</a>. Under JCP Standardized Tag Libraries on the left select Standar-1.1:JSTL 1.1(2.0). Scroll down to the Download section and select the first link, Download the Standard Tag Library Release from an Apache Jakara Project Mirror. Select Taglibs and then Library Releases. Select standard and then select to download
- jakarta-taglibs-standard-current.zip. Once the zip file download, open it and extract jstl.jar and standard.jar into the WebContent/WEB-INF/lib folder in your project. Select your project, right click on it and select Refresh. The libraries are automatically added to your Java classpath. Your project should now look like this.<BR>
-
-<IMG border="0" src="images/webapp17.gif" width="265" height="436"><BR>
-<BR>
-</LI>
-
-<LI>Open Schedule.jsp in the JSP source page editor.<BR>
-<BR>
-</LI>
-
-<LI>In order to use the tag libraries you have just downloaded you will have to declare them in your JSP. At the top of the JSP file (above the HTML element) add in the following line
- <P id="code"><%@taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c"%></P>
-
-</LI>
-
-<LI>Next we will dynamically
- create a table that will hold our schedule. The table will list the days of the week and the time from 8:00am until 9:00pm. For each time slot we will check to see if there is a class and if there is we will display the title of the class.<BR>
-
-<BR>
- First create the header of the table as follows.<P id="code"><TABLE border="1" cellspacing="0"><BR>
- <TBODY><BR>
- <TR><BR>
- <TH align="center" valign="middle" width="80"></TH><BR>
- <TH align="center" valign="middle" width="100">Sunday</TH><BR>
- <TH align="center" valign="middle">Monday</TH><BR>
- <TH align="center" valign="middle">Tuesday</TH><BR>
- <TH align="center" valign="middle">Wednesday</TH><BR>
- <TH align="center" valign="middle">Thursday</TH><BR>
- <TH align="center" valign="middle">Friday</TH><BR>
- <TH align="center" valign="middle">Saturday</TH><BR>
- </TR></P>
-
-</LI>
-
-<LI>Now you will create the content of the table.
- In order to create the content you will iterate through the times of the day and the days of the week. As your schedule will display from 8:00am to 9:00pm you will iterate from 8 to 21 for the time. For the days of the week you will iterate from 0 to 6. There is some simple logic for displaying the time in a nice way. As you can see below, the tags that are prefixed with 'c' are from the custom tag library you imported earlier. These tags allow for the iteration and conditional logic you are using. In the third forEach loop you can see where the information is retrieved from the school schedule object your servlet creates and where the individual information is retrieved from each SchoolClass object.<P id="code"> <c:forEach begin="8" end="21" step="1" var="time"><BR>
- <TR><BR>
- <TD align="center" valign="middle" width="80"><BR>
- <c:choose><BR>
- <c:when test="${time == 12}"><BR>
- <c:out value="${time}" />:00pm<BR>
- </c:when><BR>
- <c:when test="${time > 12}"><BR>
- <c:out value="${time - 12}" />:00pm<BR>
- </c:when><BR>
- <c:otherwise><BR>
- <c:out value="${time}" />:00am<BR>
- </c:otherwise><BR>
- </c:choose></TD><BR>
- <c:forEach begin="0" end="6" step="1" var="day"><BR>
- <TD align="center" valign="middle" width="100"><BR>
- <c:forEach items="${schoolschedule.classes}" var="clazz"><BR>
- <c:if test="${clazz.startTime <= time <BR>
- && clazz.endTime > time <BR>
- && clazz.day == day}"><BR>
- <c:out value="${clazz.title}" /><BR>
- </c:if><BR>
- </c:forEach><BR>
- </TD><BR>
- </c:forEach><BR>
- </TR><BR>
- </c:forEach><BR>
- </TBODY><BR>
- </TABLE></P>
-
-</LI>
-
-<LI>Save the Schedule.jsp file.</LI>
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Running And Testing The School Schedule Web Application</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>Your school schedule application is now complete. Now it is time to take it for a spin.</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>Right click on Schedule.jsp and select Run As -> Run on Server...<BR>
-<BR>
-</LI>
-
-<LI>A Web browser window will open with the application. Notice that the calendar is initially empty. Add a class to the calendar and click Add Course. The course is now added to the calendar. For example, if you add the course "Intro to Computer Programming 101" on Mon, Wed and Fri from 10:00am until 11:00am your schedule will now look like the following.<BR>
-
-<IMG border="0" src="images/webapp18.gif" width="655" height="603"><BR>
-<BR>
-
-</LI>
-
-<LI>Experiment adding more courses into your schedule.</LI>
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Summary</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>In this tutorial you learned how to configure Eclipse to work with Tomcat and create a J2EE Web project that uses a servlet and a JSP to create a student class schedule Web application. This application, while simple, provides a good introduction to Java Web development and some of the Web development tools available in the Eclipse Web Tools Platform project.</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P></P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>
-
-</P>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/community/tutorials/SchoolSchedule/BuildingAScheduleWebApp.xml b/community/tutorials/SchoolSchedule/BuildingAScheduleWebApp.xml
deleted file mode 100644
index 474de82..0000000
--- a/community/tutorials/SchoolSchedule/BuildingAScheduleWebApp.xml
+++ /dev/null
@@ -1,331 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<?xml-stylesheet type="text/xsl" href="../../../wtp.xsl"?>
-<html>
-<head>
- <meta name="root" content="../../../../" />
- <title>WTP Tutorials - Building a School Schedule Web Application</title>
-</head>
-
-<body>
-<h1>WTP Tutorials - Building a School Schedule Web Application</h1>
-<p>
-<b>By Lawrence Mandel</b><BR/>
-January 24, 2005<BR/>
-<BR/>
-</p>
-<P>In this tutorial you will create a school schedule Web application. This application will allow students to input their courses and create a schedule. This tutorial will introduce you to JSP's, servlets and the Web Tools Platform project's server tools.
-<BR/>
-
-</P>
-<h2>Prerequisites For The Tutorial</h2>
-<OL>
- <LI>Web Tools Platform (WTP) project<BR/>The WTP project can be downloaded from <a href="http://download.eclipse.org/webtools/downloads/">http://download.eclipse.org/webtools/downloads/</a><BR/><BR/>
- </LI>
- <LI>Tomcat 5.0.28<BR/>Tomcat is available from <a href="http://jakarta.apache.org/tomcat/" target="_top">http://jakarta.apache.org/tomcat/</a><BR/><BR/></LI>
- <LI>JDK 1.4.2<BR/>Sun's JDK is available from <a href="http://java.sun.com/j2se/1.4.2/download.html" target="_top">http://java.sun.com/j2se/1.4.2/download.html</a><BR/><BR/>
- </LI>
-
-</OL>
-
-<h2>Installing The Tomcat Runtime In Eclipse</h2>
-<P>In order to run the Web application from Eclipse (which will allow you to test and debug the application) Eclipse has to be told where to find Tomcat and where to find the JDK. Tomcat requires a JDK so it can compile servlets and JSPs.</P>
-<OL>
- <LI>Select Window -> Preferences<B></B>.<BR/>
- <IMG border="0" src="images/webapp1.gif" width="550" height="340"/><BR/><BR/></LI>
- <LI>Select Java -> Installed JREs from the menu on the left.<BR/>
- <IMG border="0" src="images/webapp2.gif" width="574" height="513"/><BR/><BR/></LI>
- <LI>Select Add... The Add JRE dialog will open. Select Browse for the JRE home directory and choose the location where you installed the JDK 1.4.2. Name the runtime Sun JDK 1.4.2 and click OK.<BR/>
- <IMG border="0" src="images/webapp3.gif" width="485" height="441"/><BR/><BR/></LI>
- <LI>The Sun JDK 1.4.2 now shows on the list of installed runtimes. Click OK.<BR/>
- <IMG border="0" src="images/webapp4.gif" width="574" height="513"/><BR/><BR/></LI>
- <LI>Select Window -> Preferences.<BR/><BR/></LI>
- <LI>Select Server -> Installed Runtimes from the menu on the left.<BR/>
- <IMG border="0" src="images/webapp5.gif" width="574" height="513"/><BR/><BR/></LI>
- <LI>Click on Add... Select Apache -> Apache Tomcat v5.0 and click Next. Click Browse and select the location where you installed Tomcat. Select the Sun JDK 1.4.2 that you just installed and click Finish.<BR/>
- <IMG border="0" src="images/webapp6.gif" width="438" height="422"/><BR/><BR/></LI>
- <LI>Click OK to close the preferences dialog. Both the JDK and Tomcat are now configured in Eclipse.</LI>
-
-</OL><h2>Creating A J2EE Project</h2>
-<P>You will now create a J2EE Web project in which you will create the School Schedule application.</P>
-<OL>
- <LI>Select File -> New -> Project. Select Web -> J2EE Web Project and click Next.<BR/>
- <IMG border="0" src="images/webapp7.gif" width="500" height="500"/><BR/><BR/></LI>
- <LI>Name the project SchoolSchedule, deselect Add module to an EAR project and click Finish. <BR/>
- <IMG border="0" src="images/webapp8.gif" width="504" height="502"/>
- <BR/>You will be prompted to switch to the J2EE perspective. Click Yes.<BR/><BR/></LI>
- </OL>The Project Explorer is populated with different types of Web
- applications. Your newly created project is located under Dynamic Web
- Projects. Expand your SchoolSchedule project. The Deployment Descriptor
- contains information about your Web project such as the servlets that
- your project contains. Expanding the Java Resources folder will reveal
- the JavaSource folder. This is where you will store all of your Java
- files including any servlets and supporting classes you create. The
- WebContent folder holds all of the files that will be directly
- accessible from your project once it is deployed. This folder will hold
- the JSP you will create that will display the schedule for your
- application.
-
-<BR/>
-<h2>Creating Class and Schedule Containers</h2>
-<P>For your web application to pass class information between the JSP page that displays the schedule and the servlet that registers the classes with the schedule you will need a representation of a class and a representation of a schedule. A class will have a title, day of week, start time and end time. A schedule will be a collection of classes. To implement these two objects you will create two classes; SchoolClass and SchoolSchedule.</P>
-<OL>
- <LI>Right click on the JavaSource folder and select New -> Class. Name the class SchoolClass and set the package to org.eclipse.wtp.sample.classschedule. Click Finish. The SchoolClass class will now appear in the JavaSource folder and open in the Java editor.<BR/>
- <IMG border="0" src="images/webapp9.gif" width="495" height="563"/><BR/><BR/></LI>
- <LI>We said earlier that a SchoolClass object will need to hold a title, day, start time and end time. Create private variables for each of these.The title should be of type String and the rest should be of type int.<P id="code">private String title;<BR/>
- private int startTime;<BR/>
- private int endTime;<BR/>
- private int day;</P></LI>
- <LI>This information should be set when an instance of SchoolClass is created so you will need to create a constructor that will accept the four pieces of information. Create a constructor that takes in the four parameters and sets the class variables.<P id="code">public SchoolClass(String title, int startTime,
- int endTime, int day)<BR/>
- {<BR/>
- this.title = title;<BR/>
- this.startTime = startTime;<BR/>
- this.endTime = endTime;<BR/>
- this.day = day;<BR/>
- }</P></LI>
- <LI>You now need to create a way to access the object's information. Right click in the editor and select Source -> Generate Getters and Setters... (Note: ensure you click within the class' curly braces.)<BR/>
- <IMG border="0" src="images/webapp10.gif" width="640" height="396"/><BR/><BR/></LI>
- <LI>Click Select Getters on the right. The four getter methods are now selected. Click OK.<BR/>
- <IMG border="0" src="images/webapp11.gif" width="432" height="581"/><BR/><BR/></LI>
- <LI>Save the SchoolClass file.<BR/><BR/></LI>
- <LI>You will now create the SchoolSchedule class which will act as a container for all of the classes. Right click on the package org.eclipse.wtp.sample.classschedule and select New -> Class. Notice that the package field is automatically populated. Name the class SchoolSchedule and click Finish.<BR/><BR/></LI>
- <LI>Add a private list of classes to the SchoolSchedule class.
- <P id="code">private List classes = new ArrayList();</P>The List and ArrayList classes are underlined and flagged as errors as they have not yet been imported. Right click in the editor and select Source -> Organize Imports. Select java.util.List and click Finish. The necessary import statements will be added to the class.<BR/><BR/></LI>
- <LI>Create the getter method for the classes list by right clicking in the editor within the class and selecting Source -> Generate Getters and Setters... Click Select Getters on the right and click OK.<BR/><BR/></LI>
- <LI>You now need to create a method to add new classes to the list. Create a method named addClass that takes a parameter of SchoolClass and adds it to the list.
- <P id="code">
- public void addClass(SchoolClass schoolClass)<BR/>
- {<BR/>
- classes.add(schoolClass);<BR/>
- }
- </P></LI>
- <LI>Save the file.<BR/><BR/></LI>
-</OL>
-<h2>Adding Classes To The Schedule</h2>
-<P> You will now create a Java Server Page (JSP) that will allow students to add a class to their schedule. JSPs provide a way to access information stored in Java objects and perform Java operations within an HTML page. Your JSP will contain a form where students can submit their information. In the following section you will create an action to process the form submission.</P>
-<OL>
- <LI>Right click on the WebContent folder and select New -> Other... Select Simple and then File. Click Next.<BR/>
- <IMG border="0" src="images/webapp12.gif" width="500" height="400"/>
- <BR/>Name the file Schedule.jsp and click Finish.
- The Schedule.jsp file opens in the JSP source page editor.<BR/><BR/></LI>
- <LI>You now need to create the form to submit courses. The structure of a JSP page is very similar to that of an HTML page. A JSP page can simply use more tags and offer more functionality. In this step you will really just be creating an HTML page with a form. Create an HTML page with a form that has a text box for submitting a title, check boxes for the days of the week, and a drop-down menu for both the start time and end time of the class. The form will also need a submit button. You should ignore the action attribute on the FORM element for now. We will look at this in the next section when you create your submit action.<P id="code">
- <HTML><BR/>
- <HEAD><BR/>
- <TITLE>Student Schedule</TITLE><BR/>
- </HEAD><BR/>
- <BR/>
- <BODY><BR/>
- <FORM action="" method="post"><BR/>
- Course Name: <INPUT type="text" name="title" size="35"><BR><BR/>
- Course Time: <BR/>
- Sun<INPUT type="checkbox" name="day" value="sun"> <BR/>
- Mon<INPUT type="checkbox" name="day" value="mon"> <BR/>
- Tue<INPUT type="checkbox" name="day" value="tue"> <BR/>
- Wed<INPUT type="checkbox" name="day" value="wed"> <BR/>
- Thu<INPUT type="checkbox" name="day" value="thu"> <BR/>
- Fri<INPUT type="checkbox" name="day" value="fri"> <BR/>
- Sat<INPUT type="checkbox" name="day" value="sat"> <BR/>
- <SELECT name="starttime"><BR/>
- <OPTION value="8">8:00am</OPTION><BR/>
- <OPTION value="9">9:00am</OPTION><BR/>
- <OPTION value="10">10:00am</OPTION><BR/>
- <OPTION value="11">11:00am</OPTION><BR/>
- <OPTION value="12">12:00pm</OPTION><BR/>
- <OPTION value="13">1:00pm</OPTION><BR/>
- <OPTION value="14">2:00pm</OPTION><BR/>
- <OPTION value="15">3:00pm</OPTION><BR/>
- <OPTION value="16">4:00pm</OPTION><BR/>
- <OPTION value="17">5:00pm</OPTION><BR/>
- <OPTION value="18">6:00pm</OPTION><BR/>
- <OPTION value="19">7:00pm</OPTION><BR/>
- <OPTION value="20">8:00pm</OPTION><BR/>
- <OPTION value="21">9:00pm</OPTION><BR/>
- </SELECT> <BR/>
- to <BR/>
- <SELECT name="endtime"><BR/>
- <OPTION value="9">9:00am</OPTION><BR/>
- <OPTION value="10">10:00am</OPTION><BR/>
- <OPTION value="11">11:00am</OPTION><BR/>
- <OPTION value="12">12:00pm</OPTION><BR/>
- <OPTION value="13">1:00pm</OPTION><BR/>
- <OPTION value="14">2:00pm</OPTION><BR/>
- <OPTION value="15">3:00pm</OPTION><BR/>
- <OPTION value="16">4:00pm</OPTION><BR/>
- <OPTION value="17">5:00pm</OPTION><BR/>
- <OPTION value="18">6:00pm</OPTION><BR/>
- <OPTION value="19">7:00pm</OPTION><BR/>
- <OPTION value="20">8:00pm</OPTION><BR/>
- <OPTION value="21">9:00pm</OPTION><BR/>
- <OPTION value="22">10:00pm</OPTION><BR/>
- </SELECT><BR/>
- <BR><BR/>
- <BR><BR/>
- <INPUT type="submit" name="Submit" value="Add Course"><BR/>
- </FORM><BR/>
- <BR/>
- </BODY><BR/>
- </HTML></P>Save the file.</LI>
- <LI>You should now test that your page looks correct. To do this you will run the current version of your application of the Tomcat server you configured earlier. Right click on Schedule.jsp and select Run As -> Run on Server... Select Tomcat v5.0 Server. Ensure that Set server as project default is selected and click Next.<BR/>
- <IMG border="0" src="images/webapp13.gif" width="536" height="594"/><BR/><BR/>
- </LI>
- <LI>Ensure that your SchoolSchedule project is listed under Configured projects. If it is not, add it to the list of Configured projects by selecting it and then selecting Add. Click Finish.<BR/><BR/></LI>
- <LI>Eclipse will now startup the Tomcat server and then display your page in the internal Web browser. Your page should look something like the following screen shot.<BR/>
- <IMG border="0" src="images/webapp14.gif" width="653" height="408"/></LI>
-</OL>
-<h2>The Submit Action</h2>
-<P>When the form in Schedule.jsp is submitted an action needs to be performed on the data. In this section you will create a servlet that processes the input from the form, creates the necessary SchoolClass objects and adds them to the SchoolSchedule. A servlet is a Java class that executes on the server. In order to have the class information from previous submits stay available the SchoolSchedule will be added to a session object. (If you do not do this the schedule will only be able to show the information from the last form submission.)</P>
-<OL>
- <LI>To create the servlet right click on the org.eclipse.wtp.sample.classschedule package and select New -> Class. Name the servlet ScheduleServlet. Select Browse next to Superclass and select javax.servlet.http.HttpServlet. Select Add next to Interfaces and add javax.servlet.Servlet. Click Finish.<BR/>
- <IMG border="0" src="images/webapp15.gif" width="495" height="563"/><BR/><BR/>
- </LI>
- <LI>Your newly created ScheduleServlet will appear in the JavaSource folder and open in the Java editor. Right click in the editor and select Source -> Override/Implement Methods...<BR/>
- <IMG border="0" src="images/webapp16.gif" width="595" height="327"/><BR/><BR/>
- </LI>
- <LI>Select the doPost(HttpServletRequest, HttpServletResponse) method and click OK. The doPost method will now show in your ScheduleServlet class. Rename arg0 to request and arg1 to response.<BR/><BR/></LI>
- <LI>The doPost method is where you will take the input from the form and
- perform your actions. The doPost method is used because you specified that
- your form would submit data using the POST method. You could also have
- used the GET method in which case your servlet would need to implement
- doGet instead of doPost.<BR/>
- <BR/>
- The first thing you need to do in the doPost method is read in the information submitted by the form. This information can be obtained through the request object's getParameter method. the getParameterValues method is used for the days as there may be more than one day selected.<P id="code">String title = request.getParameter("title");<BR/>
- int starttime = Integer.parseInt(request.getParameter("starttime"));<BR/>
- int endtime = Integer.parseInt(request.getParameter("endtime"));<BR/>
- String[] days = request.getParameterValues("day");
-</P>
- </LI>
- <LI>The next step is to obtain the existing SchoolSchedule, if there is one, or to create a new one if one hasn't been created yet.
- <P id="code">SchoolSchedule schedule = <BR/>
- (SchoolSchedule)request.getSession(true).getAttribute("schoolschedule");<BR/>
- if(schedule == null)<BR/>
- {<BR/>
- schedule = new SchoolSchedule();<BR/>
- }
- </P></LI>
- <LI>Now you will create new SchoolClass objects. As there may be many days for the school class you are adding you will iterate over all of the days and create a new SchoolClass object for each day that was selected. Creating SchoolClass objects in this way will make displaying them via the Schedule.jsp easier.
- After a SchoolClass object is created you will add it to the schedule.<P id="code">
- if(days != null)<BR/>
- {<BR/>
- for(int i = 0; i < days.length; i++)<BR/>
- {<BR/>
- String dayString = days[i];<BR/>
- int day;<BR/>
- if(dayString.equalsIgnoreCase("SUN")) day = 0;<BR/>
- else if(dayString.equalsIgnoreCase("MON")) day = 1;<BR/>
- else if(dayString.equalsIgnoreCase("TUE")) day = 2;<BR/>
- else if(dayString.equalsIgnoreCase("WED")) day = 3;<BR/>
- else if(dayString.equalsIgnoreCase("THU")) day = 4;<BR/>
- else if(dayString.equalsIgnoreCase("FRI")) day = 5;<BR/>
- else day = 6;<BR/>
- <BR/>
- SchoolClass clazz = new SchoolClass(title, starttime, endtime, day);<BR/>
- schedule.addClass(clazz);<BR/>
- }<BR/>
- }
- </P>
- </LI>
- <LI>You need to set the schedule in the session so Schedule.jsp will have access to it and forward control back to Schedule.jsp.
- <P id="code">request.getSession().setAttribute("schoolschedule", schedule);<BR/>
- getServletContext().getRequestDispatcher("/Schedule.jsp").forward(request, response);
- </P>
- </LI>
- <LI>Save the class.<BR/><BR/></LI>
- <LI>You have now created your servlet but your Web application does not yet know about it. In order for your Web application to know about the servlet you will have to define it in the Deployment Descriptor. Double click on the Deployment Descriptor under the SchoolSchedule project and copy the following lines under the display element
- <P id="code">
- <servlet><BR/>
- <description></description><BR/>
- <display-name>Schedule</display-name><BR/>
- <servlet-name>Schedule</servlet-name><BR/>
- <servlet-class><BR/>
- org.eclipse.wtp.sample.classschedule.ScheduleServlet<BR/>
- </servlet-class><BR/>
- </servlet><BR/>
- <servlet-mapping><BR/>
- <servlet-name>Schedule</servlet-name><BR/>
- <url-pattern>/Schedule</url-pattern><BR/>
- </servlet-mapping>
- </P>
- </LI>
- <LI>
- Now that you have defined where your servlet action is located you can specify the location in your Schedule JSP. Open the Schedule.jsp file and specify the action location of your form.
- <P id="code">
- <FORM action="/SchoolSchedule/Schedule" method="post"><BR/>
- </P>
- </LI>
-</OL>
-<h2>Displaying The Schedule</h2>
-<P>
-Your servlet has now been defined with your Web application and is ready to be used. You can now return to Schedule.jsp and work on displaying the Schedule. In this section you will use some of the custom tag libraries that are available for working with JSPs.</P>
-<OL>
- <LI>In order to use the standard tag libraries you will first have to download and install them into our project. Open your Web browser to <a href="http://jakarta.apache.org/taglibs/" target="_top">http://jakarta.apache.org/taglibs/</a>. Under JCP Standardized Tag Libraries on the left select Standar-1.1:JSTL 1.1(2.0). Scroll down to the Download section and select the first link, Download the Standard Tag Library Release from an Apache Jakara Project Mirror. Select Taglibs and then Library Releases. Select standard and then select to download
- jakarta-taglibs-standard-current.zip. Once the zip file download, open it and extract jstl.jar and standard.jar into the WebContent/WEB-INF/lib folder in your project. Select your project, right click on it and select Refresh. The libraries are automatically added to your Java classpath. Your project should now look like this.<BR/>
- <IMG border="0" src="images/webapp17.gif" width="265" height="436"/><BR/><BR/></LI>
- <LI>Open Schedule.jsp in the JSP source page editor.<BR/><BR/></LI>
- <LI>In order to use the tag libraries you have just downloaded you will have to declare them in your JSP. At the top of the JSP file (above the HTML element) add in the following line
- <P id="code"><%@taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c"%></P>
- </LI>
- <LI>Next we will dynamically
- create a table that will hold our schedule. The table will list the days of the week and the time from 8:00am until 9:00pm. For each time slot we will check to see if there is a class and if there is we will display the title of the class.<BR/>
- <BR/>
- First create the header of the table as follows.<P id="code"><TABLE border="1" cellspacing="0"><BR/>
- <TBODY><BR/>
- <TR><BR/>
- <TH align="center" valign="middle" width="80"></TH><BR/>
- <TH align="center" valign="middle" width="100">Sunday</TH><BR/>
- <TH align="center" valign="middle">Monday</TH><BR/>
- <TH align="center" valign="middle">Tuesday</TH><BR/>
- <TH align="center" valign="middle">Wednesday</TH><BR/>
- <TH align="center" valign="middle">Thursday</TH><BR/>
- <TH align="center" valign="middle">Friday</TH><BR/>
- <TH align="center" valign="middle">Saturday</TH><BR/>
- </TR></P>
- </LI>
- <LI>Now you will create the content of the table.
- In order to create the content you will iterate through the times of the day and the days of the week. As your schedule will display from 8:00am to 9:00pm you will iterate from 8 to 21 for the time. For the days of the week you will iterate from 0 to 6. There is some simple logic for displaying the time in a nice way. As you can see below, the tags that are prefixed with 'c' are from the custom tag library you imported earlier. These tags allow for the iteration and conditional logic you are using. In the third forEach loop you can see where the information is retrieved from the school schedule object your servlet creates and where the individual information is retrieved from each SchoolClass object.<P id="code"> <c:forEach begin="8" end="21" step="1" var="time"><BR/>
- <TR><BR/>
- <TD align="center" valign="middle" width="80"><BR/>
- <c:choose><BR/>
- <c:when test="${time == 12}"><BR/>
- <c:out value="${time}" />:00pm<BR/>
- </c:when><BR/>
- <c:when test="${time > 12}"><BR/>
- <c:out value="${time - 12}" />:00pm<BR/>
- </c:when><BR/>
- <c:otherwise><BR/>
- <c:out value="${time}" />:00am<BR/>
- </c:otherwise><BR/>
- </c:choose></TD><BR/>
- <c:forEach begin="0" end="6" step="1" var="day"><BR/>
- <TD align="center" valign="middle" width="100"><BR/>
- <c:forEach items="${schoolschedule.classes}" var="clazz"><BR/>
- <c:if test="${clazz.startTime <= time <BR/>
- && clazz.endTime > time <BR/>
- && clazz.day == day}"><BR/>
- <c:out value="${clazz.title}" /><BR/>
- </c:if><BR/>
- </c:forEach><BR/>
- </TD><BR/>
- </c:forEach><BR/>
- </TR><BR/>
- </c:forEach><BR/>
- </TBODY><BR/>
- </TABLE></P>
- </LI>
- <LI>Save the Schedule.jsp file.</LI>
-</OL>
-<h2>Running And Testing The School Schedule Web Application</h2>
-<P>Your school schedule application is now complete. Now it is time to take it for a spin.</P>
-<OL>
- <LI>Right click on Schedule.jsp and select Run As -> Run on Server...<BR/><BR/></LI>
- <LI>A Web browser window will open with the application. Notice that the calendar is initially empty. Add a class to the calendar and click Add Course. The course is now added to the calendar. For example, if you add the course "Intro to Computer Programming 101" on Mon, Wed and Fri from 10:00am until 11:00am your schedule will now look like the following.<BR/>
- <IMG border="0" src="images/webapp18.gif" width="655" height="603"/><BR/><BR/>
- </LI>
- <LI>Experiment adding more courses into your schedule.</LI>
-</OL>
-<h2>Summary</h2>
-<P>In this tutorial you learned how to configure Eclipse to work with Tomcat and create a J2EE Web project that uses a servlet and a JSP to create a student class schedule Web application. This application, while simple, provides a good introduction to Java Web development and some of the Web development tools available in the Eclipse Web Tools Platform project.</P>
-<P></P>
-<P>
-</P>
-</body>
-</html>
diff --git a/community/tutorials/SchoolSchedule/images/webapp1.gif b/community/tutorials/SchoolSchedule/images/webapp1.gif
deleted file mode 100644
index 228e7b0..0000000
--- a/community/tutorials/SchoolSchedule/images/webapp1.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/SchoolSchedule/images/webapp10.gif b/community/tutorials/SchoolSchedule/images/webapp10.gif
deleted file mode 100644
index f91eee2..0000000
--- a/community/tutorials/SchoolSchedule/images/webapp10.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/SchoolSchedule/images/webapp11.gif b/community/tutorials/SchoolSchedule/images/webapp11.gif
deleted file mode 100644
index 1aa78b8..0000000
--- a/community/tutorials/SchoolSchedule/images/webapp11.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/SchoolSchedule/images/webapp12.gif b/community/tutorials/SchoolSchedule/images/webapp12.gif
deleted file mode 100644
index bdec4b9..0000000
--- a/community/tutorials/SchoolSchedule/images/webapp12.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/SchoolSchedule/images/webapp13.gif b/community/tutorials/SchoolSchedule/images/webapp13.gif
deleted file mode 100644
index 5f61e15..0000000
--- a/community/tutorials/SchoolSchedule/images/webapp13.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/SchoolSchedule/images/webapp14.gif b/community/tutorials/SchoolSchedule/images/webapp14.gif
deleted file mode 100644
index fedf53b..0000000
--- a/community/tutorials/SchoolSchedule/images/webapp14.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/SchoolSchedule/images/webapp15.gif b/community/tutorials/SchoolSchedule/images/webapp15.gif
deleted file mode 100644
index bb2d7d7..0000000
--- a/community/tutorials/SchoolSchedule/images/webapp15.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/SchoolSchedule/images/webapp16.gif b/community/tutorials/SchoolSchedule/images/webapp16.gif
deleted file mode 100644
index e5c42bc..0000000
--- a/community/tutorials/SchoolSchedule/images/webapp16.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/SchoolSchedule/images/webapp17.gif b/community/tutorials/SchoolSchedule/images/webapp17.gif
deleted file mode 100644
index 4920cae..0000000
--- a/community/tutorials/SchoolSchedule/images/webapp17.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/SchoolSchedule/images/webapp18.gif b/community/tutorials/SchoolSchedule/images/webapp18.gif
deleted file mode 100644
index 8c63319..0000000
--- a/community/tutorials/SchoolSchedule/images/webapp18.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/SchoolSchedule/images/webapp2.gif b/community/tutorials/SchoolSchedule/images/webapp2.gif
deleted file mode 100644
index b0e53ad..0000000
--- a/community/tutorials/SchoolSchedule/images/webapp2.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/SchoolSchedule/images/webapp3.gif b/community/tutorials/SchoolSchedule/images/webapp3.gif
deleted file mode 100644
index 99eedf0..0000000
--- a/community/tutorials/SchoolSchedule/images/webapp3.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/SchoolSchedule/images/webapp4.gif b/community/tutorials/SchoolSchedule/images/webapp4.gif
deleted file mode 100644
index 9aeae75..0000000
--- a/community/tutorials/SchoolSchedule/images/webapp4.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/SchoolSchedule/images/webapp5.gif b/community/tutorials/SchoolSchedule/images/webapp5.gif
deleted file mode 100644
index 08ccc64..0000000
--- a/community/tutorials/SchoolSchedule/images/webapp5.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/SchoolSchedule/images/webapp6.gif b/community/tutorials/SchoolSchedule/images/webapp6.gif
deleted file mode 100644
index 14688ac..0000000
--- a/community/tutorials/SchoolSchedule/images/webapp6.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/SchoolSchedule/images/webapp7.gif b/community/tutorials/SchoolSchedule/images/webapp7.gif
deleted file mode 100644
index 8b4c0ca..0000000
--- a/community/tutorials/SchoolSchedule/images/webapp7.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/SchoolSchedule/images/webapp8.gif b/community/tutorials/SchoolSchedule/images/webapp8.gif
deleted file mode 100644
index be0651f..0000000
--- a/community/tutorials/SchoolSchedule/images/webapp8.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/SchoolSchedule/images/webapp9.gif b/community/tutorials/SchoolSchedule/images/webapp9.gif
deleted file mode 100644
index 29b8a45..0000000
--- a/community/tutorials/SchoolSchedule/images/webapp9.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/SelectServer/SelectServer.html b/community/tutorials/SelectServer/SelectServer.html
deleted file mode 100644
index ffd19fd..0000000
--- a/community/tutorials/SelectServer/SelectServer.html
+++ /dev/null
@@ -1,81 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../..//default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../..//webtools/wtp.css" type="text/css">
-<title>Selecting servers for Web Service Scenarios</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">Selecting Servers for Web Service Scenarios</font>
-<br>
-<font class="indexsub">Selecting servers for Web Service Scenarios</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../..//images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>By Kathy Chan</b>
-
-<br>
- April 29, 2005
- <br>
-
-<br>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- You can either create a new server or choose an existing
- server.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>
- To create a new server, expand
- <b>Server Types</b>
- and select the correct server type (expand Apache Tomcat
- v5.0 and select Tomcat v5.0 Server in this example).
- Click
- <b>OK</b>
- .
- </li>
-
-<br>
-
-<img border="0" src="images/SelectNewServer.JPG">
- <li>
- To use an existing server, expand
- <b>Existing Servers</b>
- and select the server (for example, select Tomcat v5.0
- server @ localhost). Click
- <b>OK</b>
- .
- </li>
-
-<br>
-
-<img border="0" src="images/SelectExistingServer.JPG">
- </ul>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/community/tutorials/SelectServer/SelectServer.xml b/community/tutorials/SelectServer/SelectServer.xml
deleted file mode 100644
index 7768ab2..0000000
--- a/community/tutorials/SelectServer/SelectServer.xml
+++ /dev/null
@@ -1,48 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<?xml-stylesheet type="text/xsl" href="../../../wtp.xsl"?>
-<html>
- <head>
- <meta name="root" content="../../../../" />
- <title>Selecting servers for Web Service Scenarios</title>
- </head>
- <body>
- <h1>Selecting Servers for Web Service Scenarios</h1>
- <p>
- <b>By Kathy Chan</b>
- <br />
- April 29, 2005
- <br />
- <br />
- </p>
- <p>
- You can either create a new server or choose an existing
- server.
- </p>
- <ul>
- <li>
- To create a new server, expand
- <b>Server Types</b>
- and select the correct server type (expand Apache Tomcat
- v5.0 and select Tomcat v5.0 Server in this example).
- Click
- <b>OK</b>
- .
- </li>
- <br></br>
- <img border="0"
- src="images/SelectNewServer.JPG" />
- <li>
- To use an existing server, expand
- <b>Existing Servers</b>
- and select the server (for example, select Tomcat v5.0
- server @ localhost). Click
- <b>OK</b>
- .
- </li>
- <br></br>
- <img border="0"
- src="images/SelectExistingServer.JPG" />
- </ul>
-
- </body>
-</html>
diff --git a/community/tutorials/SelectServer/images/SelectExistingServer.JPG b/community/tutorials/SelectServer/images/SelectExistingServer.JPG
deleted file mode 100644
index 398dbe4..0000000
--- a/community/tutorials/SelectServer/images/SelectExistingServer.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/SelectServer/images/SelectNewServer.JPG b/community/tutorials/SelectServer/images/SelectNewServer.JPG
deleted file mode 100644
index 95f6b44..0000000
--- a/community/tutorials/SelectServer/images/SelectNewServer.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ServerDefinitionExplained/ServerDefinitionExplained.html b/community/tutorials/ServerDefinitionExplained/ServerDefinitionExplained.html
deleted file mode 100644
index 9f79780..0000000
--- a/community/tutorials/ServerDefinitionExplained/ServerDefinitionExplained.html
+++ /dev/null
@@ -1,391 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../..//default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../..//webtools/wtp.css" type="text/css">
-<title>Generic server - Server Definition file explained</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">Generic server - Server Definition file explained</font>
-<br>
-<font class="indexsub">Generic server - Server Definition file explained</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../..//images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>By Gorkem Ercan</b>
-
-<br>
- April 29, 2005
- <br>
-
-<br>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Introduction</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Generic server is a special server and runtime implementation of
- base server tooling that can adjust its behaviour by a server
- type definition file. Server type definition files are XML based meta information files
- that are introduced using
- <i>"org.eclipse.jst.server.generic.core.serverdefinition"</i> extension point</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- This document describes the different parts of the server definition files.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Server definition file introduction</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- A server definition file virtually has two parts; Properties and Server information.
- Properties are variables that is something that can be manipulated and changed
- using generic server graphical user interface. Server information is used by the
- generic server to perform server tooling functionality. This information can be
- defined so that properties are used to determine their values.
- <br>
-<br>
- If we define a property like;
- <pre>
-<strong>
- <font color="#0000FF"><property id=</font>"serverAddress"
- <font color="#0000FF">label=</font>"Address:"
- <font color="#0000FF">type=</font>"string"
- <font color="#0000FF">context=</font>"server"
- <font color="#0000FF">default=</font>"127.0.0.1" />
- </strong>
-
-</pre>
-
-<br>
- And if we refer to this property in a server information element such as:
- <pre>
-
-<strong>
- <font color="#0000FF"><jndiConnection></font>
- <font color="#0000FF"> <providerUrl></font>iiop://${serverAddress}:2001<font color="#0000FF"></providerUrl></font>
- <font color="#0000FF"> <initialContextFactory></font>org.objectweb.carol.jndi.spi.MultiOrbInitialContextFactory<font color="#0000FF"></initialContextFactory></font>
- <font color="#0000FF"></jndiConnection></font></strong>
-
-</pre>
-
-<br>
- When used in the generic server tooling the provider URL becomes<br>
-
-<pre>
-<strong><font color="#009933"> iiop://127.0.0.1:2001</font></strong>
-</pre>
-
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">
- Properties to collect user data
- </font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p> The defined properties show up in the generic server user interface for
- collecting user data. A property element must have all the following attributes:
- <br>
-<br>
-
-<b>id:</b> A property is referred in the server definition and the generic server APIs with this value.
- If you wish to refer to this property later in the server definiton file wrap it inside <i>${.. }</i>. Ids must be unique.
- <br>
-<br>
-
-
-<b>label:</b> User friendly alias for the property. This is value is shown to users.
- <br>
-<br>
-
-<b>type:</b> Properties are string valued. This attribute determines the type of GUI
- to use. The allowed values, <i>"string"</i> renders a text widget,
- <i>"boolean"</i> renders a check box,
- <i>"directory"</i> renders a file path dialog,
- <i>"file"</i> renders a file dialog.
- <br>
-<br>
-
-<b>context:</b>Determined whether the property is part of server runtime or a server instance.
- The user is asked for the value of the property in new Server Runtime wizard or New Server wizard
- depending on this value. Allowed values are <i>"server"</i>, and <i>"runtime"</i>
-
-
-<br>
-<br>
-
-<b>default:</b> This is the initial value presented to user.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Defining classpaths</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Well defined classpaths are an important part of server definitions. A classpath definition
- can be referred in more than one section of the server definition. It can be used to
- start, stop server or define the entries to be added to a project' s build path.
- Classpaths are defined using the classpath element.
- <pre>
-
-<strong>
- <font color="#0000FF"><classpath id="</font>jonas<font color="#0000FF">"></font>
- <font color="#0000FF"> <archive path="</font>${classPath}/lib/common/ow_jonas_bootstrap.jar<font color="#0000FF">" /></font>
- <font color="#0000FF"> <archive path="</font>${classPath}/conf<font color="#0000FF">" /></font>
- <font color="#0000FF"></classpath></font>
- </strong>
-
-</pre>
-
-<br>
-
-<b>id:</b> Is the name that this classpath is referred to in server definition file and the generic
- server APIs
- <br>
-<br>
-
-<b>archive and path:</b> this element points either to a directory or a java library that will be a part of the
- classpath.
- <br>
-<br>
- If a flexible project is targeted for a generic server its build path is updated by
- the generic server tooling to include required libraries by the server. In server definition
- files the project element is used to determine which classpath
- definition is used for project build paths.
- <br>
-<br>
-
-<b>project:</b> element contains only one element that refers to a classpath definition.
- <pre>
-<strong>
- <font color="#0000FF"><project></font>
- <font color="#0000FF"> <classpathReference></font>jonas<font color="#0000FF"></classpathReference></font>
- <font color="#0000FF"></project></font>
- </strong>
-</pre>
-
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Information to start and stop your server</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The start and stop elements are very similiar tags that are used to define parameters to launch
- a server, and stop a running server respectively. They are both consist of the same elements. Generic server
- framework support two kinds of launches. A java launch and external launch. The type of the launch is determined
- by the launchType attribute in start or stop tag. The valid values are external and java.
-
- <br>
-<br>
-
-<b>workingDirectory:</b> This is the directory in which the application server starts.
- <br>
-<br>
-
-<b>programArguments:</b> Specific values that the server is expecting (a user name or a URLs, configuration
- params, for example).
- <br>
-<br>
- If a java launch is configured you should define mainClass, vmParameters, classpathReference tags in addition to above.
- <br>
-<br>
-
-<b>mainClass</b> A java application server is a Java application after all. Like any other Java application
- you will need a class with a main method to start it. This the name of that class.
- <br>
-<br>
-
-<b>vmParameters:</b> Values that are used as parameters to java virtual machine.
- <br>
-<br>
-
-<b>classpathReference:</b> This is the classpath definition used to invoke the main class.
- <br>
-<br>
- when defining an external launch use the external, and debugPort tags with workingDirectory and programArguments.
- <br>
-<br>
-
-<b>debugPort:</b>This is the port number that eclipse debugger will connect to when the server is started in debug mode.
- <br>
-<br>
-
-<b>external:</b>This is the external executable or script that will be used for launching the server. The os attribute in the
- tag indicates the platform of the definition. You can have as many external tags as the number of platform you wish to support.
-
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Publishers</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Generic publishers are general purpose publishers that can be used for publishing to different
- servers. It is also possible to implement a server specific publisher, if the publishing
- mechanisms of the server requires it. A new publisher is introduced using
- <i>org.eclipse.jst.server.generic.core.genericpublisher</i> extension point. WTP includes the
- general purpose ANT publisher. ANT based publisher simply calls specific targets on an ANT script to
- publish modules to a server.
- <br>
-<br>
- A server definition file can contain some server specific information that is used for initializing
- the publisher. The publisher element in the server definiton can be used for this purpose.
- <br>
-<br>
-
-<pre>
-<strong>
- <font color="#0000FF"><publisher id="</font>org.eclipse.jst.server.generic.antpublisher<font color="#0000FF">"></font>
- <font color="#0000FF"> <publisherdata></font>
- <font color="#0000FF"> <dataname></font>build.file<font color="#0000FF"></dataname></font>
- <font color="#0000FF"> <datavalue></font>/buildfiles/jonas.xml<font color="#0000FF"></datavalue></font>
- <font color="#0000FF"> </publisherdata></font>
- <font color="#0000FF"></publisher></font>
- </strong>
-
-</pre>
-
-<br>
-
-<b>id:</b> This is the id of the publisher. This value must match the value in the <i>plugin.xml</i>
- where the publisher is defined.
- <br>
-<br>
-
-<b>publisherdata:</b> A single name value pair that will be passed to publisher.
-
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Modules</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The <i>module</i> element shows the module types this server definition can work.
- It also includes information on publishing the module.
- <br>
-<br>
-
-<b>type:</b> The module type. This value must match the value in the <i>plugin.xml</i> where the
- module type is defined.
- <br>
-<br>
-
-<b>publishDir:</b> The directory where the final module will be published to.
- <br>
-<br>
-
-<b>publisherReference:</b> The id of the generic publisher that should be used to publishing
- of this module type.
-
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Ports</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- the <i>port</i> element indicates the ports and the protocols that the server starts on. These
- values are used to determine if a server is alive.
- <br>
-<br>
-
-<b>no:</b> The port number.
- <br>
-<br>
-
-<b>protocol:</b> The protocol supported by this port.
- <br>
-<br>
-
-<b>name:</b> User friendly name of the port' s protocol.
-
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">JNDI properties</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The JNDI properties for a server are needed for any clients that need jndi such as EJB testers. The
- <i>jndiConnection</i> element is used to provide the jndi information for accessing an application server.
- <br>
-<br>
-
-<b>providerUrl:</b> The url to jndi server.
- <br>
-<br>
-
-<b>initialContextFactory:</b> Name of the initial context factory class for the server' s jndi implementation.
- <br>
-<br>
-
-<b>jndiProperty:</b> Name, value pairs that may be used for establishing jndi connection, such as usernames, passwords, etc.
- </p>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/community/tutorials/ServerDefinitionExplained/ServerDefinitionExplained.xml b/community/tutorials/ServerDefinitionExplained/ServerDefinitionExplained.xml
deleted file mode 100644
index 7583237..0000000
--- a/community/tutorials/ServerDefinitionExplained/ServerDefinitionExplained.xml
+++ /dev/null
@@ -1,226 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<?xml-stylesheet type="text/xsl" href="../../../wtp.xsl"?>
-<html>
- <head>
- <meta name="root" content="../../../../" />
- <title>Generic server - Server Definition file explained</title>
- </head>
- <body>
- <h1>Generic server - Server Definition file explained</h1>
- <p>
- <b>By Gorkem Ercan</b>
- <br />
- April 29, 2005
- <br />
- <br />
- </p>
-
- <h2>Introduction</h2>
- <br></br>
- <p>
- Generic server is a special server and runtime implementation of
- base server tooling that can adjust its behaviour by a server
- type definition file. Server type definition files are XML based meta information files
- that are introduced using
- <i>"org.eclipse.jst.server.generic.core.serverdefinition"</i> extension point</p>
-
- <p>
- This document describes the different parts of the server definition files.
- </p>
-
- <br></br>
-
- <h2>Server definition file introduction</h2>
- <br></br>
- <p>
- A server definition file virtually has two parts; Properties and Server information.
- Properties are variables that is something that can be manipulated and changed
- using generic server graphical user interface. Server information is used by the
- generic server to perform server tooling functionality. This information can be
- defined so that properties are used to determine their values.
- <br/><br/>
- If we define a property like;
- <pre><strong>
- <font color="#0000FF"><property id=</font>"serverAddress"
- <font color="#0000FF">label=</font>"Address:"
- <font color="#0000FF">type=</font>"string"
- <font color="#0000FF">context=</font>"server"
- <font color="#0000FF">default=</font>"127.0.0.1" />
- </strong>
- </pre>
- <br/>
- And if we refer to this property in a server information element such as:
- <pre>
- <strong>
- <font color="#0000FF"><jndiConnection></font>
- <font color="#0000FF"> <providerUrl></font>iiop://${serverAddress}:2001<font color="#0000FF"></providerUrl></font>
- <font color="#0000FF"> <initialContextFactory></font>org.objectweb.carol.jndi.spi.MultiOrbInitialContextFactory<font color="#0000FF"></initialContextFactory></font>
- <font color="#0000FF"></jndiConnection></font></strong>
- </pre>
- <br/>
- When used in the generic server tooling the provider URL becomes<br/>
- <pre><strong><font color="#009933"> iiop://127.0.0.1:2001</font></strong></pre>
-
- </p>
-
- <h2>
- Properties to collect user data
- </h2>
- <br></br>
- <p> The defined properties show up in the generic server user interface for
- collecting user data. A property element must have all the following attributes:
- <br/><br/>
- <b>id:</b> A property is referred in the server definition and the generic server APIs with this value.
- If you wish to refer to this property later in the server definiton file wrap it inside <i>${.. }</i>. Ids must be unique.
- <br/><br/>
-
- <b>label:</b> User friendly alias for the property. This is value is shown to users.
- <br/><br/>
- <b>type:</b> Properties are string valued. This attribute determines the type of GUI
- to use. The allowed values, <i>"string"</i> renders a text widget,
- <i>"boolean"</i> renders a check box,
- <i>"directory"</i> renders a file path dialog,
- <i>"file"</i> renders a file dialog.
- <br/><br/>
- <b>context:</b>Determined whether the property is part of server runtime or a server instance.
- The user is asked for the value of the property in new Server Runtime wizard or New Server wizard
- depending on this value. Allowed values are <i>"server"</i>, and <i>"runtime"</i>
-
- <br/><br/>
- <b>default:</b> This is the initial value presented to user.
- </p>
-
- <h2>Defining classpaths</h2>
- <p>
- Well defined classpaths are an important part of server definitions. A classpath definition
- can be referred in more than one section of the server definition. It can be used to
- start, stop server or define the entries to be added to a project' s build path.
- Classpaths are defined using the classpath element.
- <pre>
- <strong>
- <font color="#0000FF"><classpath id="</font>jonas<font color="#0000FF">"></font>
- <font color="#0000FF"> <archive path="</font>${classPath}/lib/common/ow_jonas_bootstrap.jar<font color="#0000FF">" /></font>
- <font color="#0000FF"> <archive path="</font>${classPath}/conf<font color="#0000FF">" /></font>
- <font color="#0000FF"></classpath></font>
- </strong>
- </pre>
- <br/>
- <b>id:</b> Is the name that this classpath is referred to in server definition file and the generic
- server APIs
- <br/><br/>
- <b>archive and path:</b> this element points either to a directory or a java library that will be a part of the
- classpath.
- <br/><br/>
- If a flexible project is targeted for a generic server its build path is updated by
- the generic server tooling to include required libraries by the server. In server definition
- files the project element is used to determine which classpath
- definition is used for project build paths.
- <br/><br/>
- <b>project:</b> element contains only one element that refers to a classpath definition.
- <pre><strong>
- <font color="#0000FF"><project></font>
- <font color="#0000FF"> <classpathReference></font>jonas<font color="#0000FF"></classpathReference></font>
- <font color="#0000FF"></project></font>
- </strong></pre>
-
- </p>
-
- <h2>Information to start and stop your server</h2>
- <p>
- The start and stop elements are very similiar tags that are used to define parameters to launch
- a server, and stop a running server respectively. They are both consist of the same elements. Generic server
- framework support two kinds of launches. A java launch and external launch. The type of the launch is determined
- by the launchType attribute in start or stop tag. The valid values are external and java.
-
- <br/><br/>
- <b>workingDirectory:</b> This is the directory in which the application server starts.
- <br/><br/>
- <b>programArguments:</b> Specific values that the server is expecting (a user name or a URLs, configuration
- params, for example).
- <br/><br/>
- If a java launch is configured you should define mainClass, vmParameters, classpathReference tags in addition to above.
- <br/><br/>
- <b>mainClass</b> A java application server is a Java application after all. Like any other Java application
- you will need a class with a main method to start it. This the name of that class.
- <br/><br/>
- <b>vmParameters:</b> Values that are used as parameters to java virtual machine.
- <br/><br/>
- <b>classpathReference:</b> This is the classpath definition used to invoke the main class.
- <br/><br/>
- when defining an external launch use the external, and debugPort tags with workingDirectory and programArguments.
- <br/><br/>
- <b>debugPort:</b>This is the port number that eclipse debugger will connect to when the server is started in debug mode.
- <br/><br/>
- <b>external:</b>This is the external executable or script that will be used for launching the server. The os attribute in the
- tag indicates the platform of the definition. You can have as many external tags as the number of platform you wish to support.
-
- </p>
- <h2>Publishers</h2>
- <p>
- Generic publishers are general purpose publishers that can be used for publishing to different
- servers. It is also possible to implement a server specific publisher, if the publishing
- mechanisms of the server requires it. A new publisher is introduced using
- <i>org.eclipse.jst.server.generic.core.genericpublisher</i> extension point. WTP includes the
- general purpose ANT publisher. ANT based publisher simply calls specific targets on an ANT script to
- publish modules to a server.
- <br/><br/>
- A server definition file can contain some server specific information that is used for initializing
- the publisher. The publisher element in the server definiton can be used for this purpose.
- <br/><br/>
- <pre><strong>
- <font color="#0000FF"><publisher id="</font>org.eclipse.jst.server.generic.antpublisher<font color="#0000FF">"></font>
- <font color="#0000FF"> <publisherdata></font>
- <font color="#0000FF"> <dataname></font>build.file<font color="#0000FF"></dataname></font>
- <font color="#0000FF"> <datavalue></font>/buildfiles/jonas.xml<font color="#0000FF"></datavalue></font>
- <font color="#0000FF"> </publisherdata></font>
- <font color="#0000FF"></publisher></font>
- </strong>
- </pre>
- <br/>
- <b>id:</b> This is the id of the publisher. This value must match the value in the <i>plugin.xml</i>
- where the publisher is defined.
- <br/><br/>
- <b>publisherdata:</b> A single name value pair that will be passed to publisher.
-
- </p>
- <h2>Modules</h2>
- <p>
- The <i>module</i> element shows the module types this server definition can work.
- It also includes information on publishing the module.
- <br/><br/>
- <b>type:</b> The module type. This value must match the value in the <i>plugin.xml</i> where the
- module type is defined.
- <br/><br/>
- <b>publishDir:</b> The directory where the final module will be published to.
- <br/><br/>
- <b>publisherReference:</b> The id of the generic publisher that should be used to publishing
- of this module type.
-
- </p>
- <h2>Ports</h2>
- <p>
- the <i>port</i> element indicates the ports and the protocols that the server starts on. These
- values are used to determine if a server is alive.
- <br/><br/>
- <b>no:</b> The port number.
- <br/><br/>
- <b>protocol:</b> The protocol supported by this port.
- <br/><br/>
- <b>name:</b> User friendly name of the port' s protocol.
-
- </p>
- <h2>JNDI properties</h2>
- <p>
- The JNDI properties for a server are needed for any clients that need jndi such as EJB testers. The
- <i>jndiConnection</i> element is used to provide the jndi information for accessing an application server.
- <br/><br/>
- <b>providerUrl:</b> The url to jndi server.
- <br/><br/>
- <b>initialContextFactory:</b> Name of the initial context factory class for the server' s jndi implementation.
- <br/><br/>
- <b>jndiProperty:</b> Name, value pairs that may be used for establishing jndi connection, such as usernames, passwords, etc.
- </p>
-
-
- </body>
-</html>
diff --git a/community/tutorials/ServletScenario/ServletScenario.html b/community/tutorials/ServletScenario/ServletScenario.html
deleted file mode 100644
index a8f6cb1..0000000
--- a/community/tutorials/ServletScenario/ServletScenario.html
+++ /dev/null
@@ -1,416 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../../../default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../../../webtools/wtp.css" type="text/css">
-<title>jst j2ee</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">WTP Tutorials - Testing the Creation of Annotated and Non-Annotated Servlets in the
- Web Tools Project</font>
-<br>
-<font class="indexsub">jst j2ee</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../../../images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>
-<B>John Lanuti </B>
-<BR>
- IBM Rational <BR>
- February 24,2005 <BR>
-<BR>
-<BR>
-
- This tutorial will show you how to set up, create, and deploy a simple Hello World servlet on
- the Tomcat server using the Eclipse Web Tools Project. <BR>
-</P>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Prerequisites For The Tutorial</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>Web Tools Platform (WTP) project<BR>The WTP project can be downloaded from <a href="http://download.eclipse.org/webtools/downloads/">http://download.eclipse.org/webtools/downloads/</a>
-<BR>
-<BR>
-
-</LI>
-
-<LI>XDoclet 1.2.2<BR>XDoclet is available from <a href="http://xdoclet.sourceforge.net" target="_top">http://xdoclet.sourceforge.net</a>
-<BR>
-<BR>
-</LI>
-
-<LI>Tomcat Server<BR>Tomcat is available from <a href="http://jakarta.apache.org/tomcat/" target="_top">http://jakarta.apache.org/tomcat/</a>
-<BR>
-<BR>
-</LI>
-
-<LI>JDK 1.4.2<BR>Sun's JDK is available from <a href="http://java.sun.com/j2se/1.4.2/download.html" target="_top">http://java.sun.com/j2se/1.4.2/download.html</a>
-<BR>
-<BR>
-
-</LI>
-
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Workspace Configuration </font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>Open the J2EE Perspective. Window->Open Perspective->Other...->J2EE.</LI>
-
-<LI>Set up XDoclet preferences. Window->Preferences->J2EE Annotations->XDoclet.
- Make sure the "Enable XDoclet Builder" option
- is checked. Select your desired version level and navigate to your XDoclet home directory. Hit OK. <BR>
-<BR>
-
-<IMG src="images/ServletScenario_Image22.jpg"><BR>
-<BR>
-</LI>
-
-<LI>Add the Tomcat server. Window->Preferences->Server->Installed Runtimes.
- Hit the "Add" button. <BR>
-<BR>
-
-<IMG src="images/ServletScenario_Image14.jpg"><BR>
-<BR>
-</LI>
-
-<LI>Select the appropriate Apache Tomcat level for your Tomcat server and
- hit the "Next" button. Fill in the appropriate Tomcat
- home directory. Hit the "Finish" button.<BR>
-<BR>
-
-<IMG src="images/ServletScenario_Image13.jpg"><BR>
-<BR>
-</LI>
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Dynamic Web Project Creation</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>From the J2EE Project Explorer, right click on the "Dynamic Web Projects" group.
- Select New->Dynamic Web Project. <BR>
-<BR>
-
-<IMG src="images/ServletScenario_Image1.jpg"> <BR>
-<BR>
-</LI>
-
-<LI>Type the project name, "HelloWorld". Make sure the "Add Module
- to EAR project" selection is unchecked. Tomcat does not support the use of EAR
- projects so we will only make a stand alone web application. <BR>
-<BR>
-
-<IMG src="images/ServletScenario_Image2.jpg"><BR>
-<BR>
-</LI>
-
-<LI>Ensure the appropriate servlet version is selected to match your level of Tomcat.
- Hit finish.</LI>
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff"> Non Annotated Servlet Creation </font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>Expand the "Dynamic Web Projects" group to the HelloWorld web project,
- and then to the "Servlets" catgeory.</LI>
-
-<LI>Right click on "Servlets" and select New->Servlet. <BR>
-<BR>
-
-<IMG src="images/ServletScenario_Image3.jpg"><BR>
-<BR>
-</LI>
-
-<LI>Type "test" in as the default java package. Type the Servlet Name, "HelloWorld".
- Uncheck the "Generate an annotated servlet class" checkbox. Hit next. <BR>
-<BR>
-
-<IMG src="images/ServletScenario_Image5.jpg"><BR>
-<BR>
-</LI>
-
-<LI> Take all the defaults. Hit next. <BR>
-<BR>
-
-<IMG src="images/ServletScenario_Image4.jpg"><BR>
-<BR>
-</LI>
-
-<LI>Select the doDelete and doPut method checkboxes in addition to the defaults. <BR>
-<BR>
-
-<IMG src="images/ServletScenario_Image6.jpg"><BR>
-<BR>
-</LI>
-
-<LI>Hit "Finish" to create the non annotated servlet. </LI>
-
-<LI>Because it is non-annotated, the web deployment descriptor metadata
- artifacts will be created for you as well. We can verify their
- existence by looking in the project explorer "Servlets"
- section for the HelloWorld web application. The HelloWorld servlet and
- servlet mapping should now show up.<BR>
-<BR>
-
-<IMG src="images/ServletScenario_Image7.jpg"><BR>
-<BR>
-</LI>
-
-<LI>The servlet java class should also show up with the methods defined
- that were selected in the wizard. <BR>
-<BR>
-
-<IMG src="images/ServletScenario_Image8.jpg"><BR>
-<BR>
-</LI>
-
-<LI>Double click on the HelloWorld class in the Project Explorer.
- Add the following code to the doGet method, , as well as an import statement for
- java.io.PrintWriter:<BR>
-
-<P> PrintWriter out = new PrintWriter(System.out); <BR>
- out = response.getWriter(); <BR>
- out.println("Hello world!");<BR>
- out.close(); </P>
-</LI>
-
-<LI>Save and close the editor.</LI>
-<BR>
-<BR>
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Annotated Servlet Creation </font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>Expand the "Dynamic Web Projects" group to the
- HelloWorld web project, and then to the "Servlets" catgeory.</LI>
-
-<LI>Right click on "Servlets" and select New->Servlet. <BR>
-<BR>
-
-<IMG src="images/ServletScenario_Image3.jpg"><BR>
-<BR>
-</LI>
-
-<LI>Type "test" in as the default java package. Type the Servlet Name,
- "XDcoletHelloWorld". Make sure "Generate an annotated servlet class"
- is checked. Hit next. <BR>
-<BR>
-
-<IMG src="images/ServletScenario_Image11.jpg"><BR>
-<BR>
-</LI>
-
-<LI> Take the defaults. Hit next. <BR>
-<BR>
-
-<IMG src="images/ServletScenario_Image23.jpg"><BR>
-<BR>
-</LI>
-
-<LI>Select the doDelete and doPut method checkboxes in addition to the defaults. <BR>
-<BR>
-
-<IMG src="images/ServletScenario_Image6.jpg"><BR>
-<BR>
-</LI>
-
-<LI>Hit "Finish" to create the annotated servlet.</LI>
-
-<LI>Because it is annotated, the web deployment descriptor metadata
- artifacts will be created during a build. The servlet annotated tags will be parsed
- and the xdoclet engine will generate the web.xml servlet nodel. We can verify their
- existence by looking in the project explorer "Servlets"
- section for the HelloWorld web application. The XDocletHelloWorld servlet and
- servlet mapping should now show up.<BR>
-</LI>
-
-<LI>The servlet java class should also show up with the methods
- defined that were selected in the wizard. <BR>
-<BR>
-
-<IMG src="images/ServletScenario_Image15.jpg"><BR>
-<BR>
-</LI>
-
-<LI>Double click on the XDocletHelloWorld class in the Project Explorer. Add
- the following code to the doGet method, as well as an import statement for
- java.io.PrintWriter:<BR>
-
-<P> PrintWriter out = new PrintWriter(System.out); <BR>
- out = response.getWriter(); <BR>
- out.println("Hello world!");<BR>
- out.close(); </P>
-</LI>
-
-<LI>Save and close the editor.</LI>
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Running the Servlets on the Tomcat Server </font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>Select the "HelloWorld" web project. Right click and select
- Run As->Run on Server... <BR>
-<BR>
-
-<IMG src="images/ServletScenario_Image16.jpg"><BR>
-<BR>
-</LI>
-
-<LI>Choose to manually define a new Server. Select the Apache Tomcat version
- you have installed. Hit next. <BR>
-<BR>
-
-<IMG src="images/ServletScenario_Image17.jpg"><BR>
-<BR>
-</LI>
-
-<LI>Ensure the Helloworld.war is added to the server. <BR>
-<BR>
-
-<IMG src="images/ServletScenario_Image18.jpg"><BR>
-<BR>
-</LI>
-
-<LI>Hit Finish.</LI>
-
-<LI>Make sure if you double click the Tomcat server instance that the
- HelloWorld project is configured correctly. Edit and restart. <BR>
-<BR>
-
-<IMG src="images/ServletScenario_Image21.jpg"> <BR>
-<BR>
-</LI>
-
-<LI>Wait for the Tomcat server to start and the web browser to open.
- Type http://localhost:8080/HelloWorld/HelloWorld in the address window. Hit enter. <BR>
-<BR>
-
-<IMG src="images/ServletScenario_Image19.jpg"><BR>
-<BR>
-</LI>
-
-<LI>Now try the annotated servlet, http://localhost:8080/HelloWorld/XDocletHelloWorld. <BR>
-<BR>
-
-<IMG src="images/ServletScenario_Image20.jpg"><BR>
-<BR>
-</LI>
-
-</OL>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/community/tutorials/ServletScenario/ServletScenario.xml b/community/tutorials/ServletScenario/ServletScenario.xml
deleted file mode 100644
index c689618..0000000
--- a/community/tutorials/ServletScenario/ServletScenario.xml
+++ /dev/null
@@ -1,145 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?xml-stylesheet type="text/xsl" href="../../../../wtp.xsl"?>
-<html>
-<head>
- <meta name="root" content="../../../../.." />
- <title>jst j2ee</title>
-</head>
-<body>
- <h1>WTP Tutorials - Testing the Creation of Annotated and Non-Annotated Servlets in the
- Web Tools Project</h1>
- <P><B>John Lanuti </B><BR/>
- IBM Rational <BR/>
- February 24,2005 <BR/> <BR/> <BR/>
-
- This tutorial will show you how to set up, create, and deploy a simple Hello World servlet on
- the Tomcat server using the Eclipse Web Tools Project. <BR/></P>
-
- <h2>Prerequisites For The Tutorial</h2>
- <OL>
- <LI>Web Tools Platform (WTP) project<BR/>The WTP project can be downloaded from <a href="http://download.eclipse.org/webtools/downloads/">http://download.eclipse.org/webtools/downloads/</a><BR/><BR/>
- </LI>
- <LI>XDoclet 1.2.2<BR/>XDoclet is available from <a href="http://xdoclet.sourceforge.net" target="_top">http://xdoclet.sourceforge.net</a><BR/><BR/></LI>
- <LI>Tomcat Server<BR/>Tomcat is available from <a href="http://jakarta.apache.org/tomcat/" target="_top">http://jakarta.apache.org/tomcat/</a><BR/><BR/></LI>
- <LI>JDK 1.4.2<BR/>Sun's JDK is available from <a href="http://java.sun.com/j2se/1.4.2/download.html" target="_top">http://java.sun.com/j2se/1.4.2/download.html</a><BR/><BR/>
- </LI>
-
- </OL>
- <h2>Workspace Configuration </h2><BR/>
- <OL>
- <LI>Open the J2EE Perspective. Window->Open Perspective->Other...->J2EE.</LI>
- <LI>Set up XDoclet preferences. Window->Preferences->J2EE Annotations->XDoclet.
- Make sure the "Enable XDoclet Builder" option
- is checked. Select your desired version level and navigate to your XDoclet home directory. Hit OK. <BR/> <BR/>
- <IMG src="images/ServletScenario_Image22.jpg" /><BR/> <BR/> </LI>
- <LI>Add the Tomcat server. Window->Preferences->Server->Installed Runtimes.
- Hit the "Add" button. <BR/> <BR/>
- <IMG src="images/ServletScenario_Image14.jpg" /><BR/> <BR/> </LI>
- <LI>Select the appropriate Apache Tomcat level for your Tomcat server and
- hit the "Next" button. Fill in the appropriate Tomcat
- home directory. Hit the "Finish" button.<BR/> <BR/>
- <IMG src="images/ServletScenario_Image13.jpg" /><BR/><BR/></LI>
- </OL> <BR/> <BR/>
-
- <h2>Dynamic Web Project Creation</h2> <BR/> <BR/>
- <OL>
- <LI>From the J2EE Project Explorer, right click on the "Dynamic Web Projects" group.
- Select New->Dynamic Web Project. <BR/> <BR/>
- <IMG src="images/ServletScenario_Image1.jpg" /> <BR/> <BR/></LI>
- <LI>Type the project name, "HelloWorld". Make sure the "Add Module
- to EAR project" selection is unchecked. Tomcat does not support the use of EAR
- projects so we will only make a stand alone web application. <BR/> <BR/>
- <IMG src="images/ServletScenario_Image2.jpg" /><BR/> <BR/> </LI>
- <LI>Ensure the appropriate servlet version is selected to match your level of Tomcat.
- Hit finish.</LI>
- </OL> <BR/> <BR/>
-
- <h2> Non Annotated Servlet Creation </h2><BR/>
- <OL>
- <LI>Expand the "Dynamic Web Projects" group to the HelloWorld web project,
- and then to the "Servlets" catgeory.</LI>
- <LI>Right click on "Servlets" and select New->Servlet. <BR/> <BR/>
- <IMG src="images/ServletScenario_Image3.jpg" /><BR/> <BR/> </LI>
- <LI>Type "test" in as the default java package. Type the Servlet Name, "HelloWorld".
- Uncheck the "Generate an annotated servlet class" checkbox. Hit next. <BR/> <BR/>
- <IMG src="images/ServletScenario_Image5.jpg" /><BR/><BR/></LI>
- <LI> Take all the defaults. Hit next. <BR/> <BR/>
- <IMG src="images/ServletScenario_Image4.jpg" /><BR/> <BR/></LI>
- <LI>Select the doDelete and doPut method checkboxes in addition to the defaults. <BR/> <BR/>
- <IMG src="images/ServletScenario_Image6.jpg" /><BR/><BR/></LI>
- <LI>Hit "Finish" to create the non annotated servlet. </LI>
- <LI>Because it is non-annotated, the web deployment descriptor metadata
- artifacts will be created for you as well. We can verify their
- existence by looking in the project explorer "Servlets"
- section for the HelloWorld web application. The HelloWorld servlet and
- servlet mapping should now show up.<BR/><BR/>
- <IMG src="images/ServletScenario_Image7.jpg" /><BR/><BR/></LI>
- <LI>The servlet java class should also show up with the methods defined
- that were selected in the wizard. <BR/><BR/>
- <IMG src="images/ServletScenario_Image8.jpg" /><BR/><BR/></LI>
- <LI>Double click on the HelloWorld class in the Project Explorer.
- Add the following code to the doGet method, , as well as an import statement for
- java.io.PrintWriter:<BR/>
- <P> PrintWriter out = new PrintWriter(System.out); <BR/>
- out = response.getWriter(); <BR/>
- out.println("Hello world!");<BR/>
- out.close(); </P></LI>
- <LI>Save and close the editor.</LI> <BR/> <BR/>
- </OL>
-
- <h2>Annotated Servlet Creation </h2><BR/> <BR/>
- <OL>
- <LI>Expand the "Dynamic Web Projects" group to the
- HelloWorld web project, and then to the "Servlets" catgeory.</LI>
- <LI>Right click on "Servlets" and select New->Servlet. <BR/><BR/>
- <IMG src="images/ServletScenario_Image3.jpg" /><BR/><BR/></LI>
- <LI>Type "test" in as the default java package. Type the Servlet Name,
- "XDcoletHelloWorld". Make sure "Generate an annotated servlet class"
- is checked. Hit next. <BR/><BR/>
- <IMG src="images/ServletScenario_Image11.jpg" /><BR/><BR/></LI>
- <LI> Take the defaults. Hit next. <BR/><BR/>
- <IMG src="images/ServletScenario_Image23.jpg" /><BR/><BR/></LI>
- <LI>Select the doDelete and doPut method checkboxes in addition to the defaults. <BR/><BR/>
- <IMG src="images/ServletScenario_Image6.jpg" /><BR/><BR/></LI>
- <LI>Hit "Finish" to create the annotated servlet.</LI>
- <LI>Because it is annotated, the web deployment descriptor metadata
- artifacts will be created during a build. The servlet annotated tags will be parsed
- and the xdoclet engine will generate the web.xml servlet nodel. We can verify their
- existence by looking in the project explorer "Servlets"
- section for the HelloWorld web application. The XDocletHelloWorld servlet and
- servlet mapping should now show up.<BR/></LI>
- <LI>The servlet java class should also show up with the methods
- defined that were selected in the wizard. <BR/><BR/>
- <IMG src="images/ServletScenario_Image15.jpg"/><BR/><BR/></LI>
- <LI>Double click on the XDocletHelloWorld class in the Project Explorer. Add
- the following code to the doGet method, as well as an import statement for
- java.io.PrintWriter:<BR/>
- <P> PrintWriter out = new PrintWriter(System.out); <BR/>
- out = response.getWriter(); <BR/>
- out.println("Hello world!");<BR/>
- out.close(); </P></LI>
- <LI>Save and close the editor.</LI>
- </OL> <BR/> <BR/>
-
- <h2>Running the Servlets on the Tomcat Server </h2> <BR/>
- <OL>
- <LI>Select the "HelloWorld" web project. Right click and select
- Run As->Run on Server... <BR/><BR/>
- <IMG src="images/ServletScenario_Image16.jpg" /><BR/><BR/></LI>
- <LI>Choose to manually define a new Server. Select the Apache Tomcat version
- you have installed. Hit next. <BR/><BR/>
- <IMG src="images/ServletScenario_Image17.jpg" /><BR/><BR/></LI>
- <LI>Ensure the Helloworld.war is added to the server. <BR/><BR/>
- <IMG src="images/ServletScenario_Image18.jpg" /><BR/><BR/></LI>
- <LI>Hit Finish.</LI>
- <LI>Make sure if you double click the Tomcat server instance that the
- HelloWorld project is configured correctly. Edit and restart. <BR/><BR/>
- <IMG src="images/ServletScenario_Image21.jpg" /> <BR/><BR/></LI>
- <LI>Wait for the Tomcat server to start and the web browser to open.
- Type http://localhost:8080/HelloWorld/HelloWorld in the address window. Hit enter. <BR/><BR/>
- <IMG src="images/ServletScenario_Image19.jpg" /><BR/><BR/></LI>
- <LI>Now try the annotated servlet, http://localhost:8080/HelloWorld/XDocletHelloWorld. <BR/><BR/>
- <IMG src="images/ServletScenario_Image20.jpg" /><BR/><BR/></LI>
- </OL>
-</body>
-</html>
diff --git a/community/tutorials/ServletScenario/images/ServletScenario_Image1.jpg b/community/tutorials/ServletScenario/images/ServletScenario_Image1.jpg
deleted file mode 100644
index 4c223d2..0000000
--- a/community/tutorials/ServletScenario/images/ServletScenario_Image1.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ServletScenario/images/ServletScenario_Image10.jpg b/community/tutorials/ServletScenario/images/ServletScenario_Image10.jpg
deleted file mode 100644
index 4e6d869..0000000
--- a/community/tutorials/ServletScenario/images/ServletScenario_Image10.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ServletScenario/images/ServletScenario_Image11.jpg b/community/tutorials/ServletScenario/images/ServletScenario_Image11.jpg
deleted file mode 100644
index 292fd95..0000000
--- a/community/tutorials/ServletScenario/images/ServletScenario_Image11.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ServletScenario/images/ServletScenario_Image12.jpg b/community/tutorials/ServletScenario/images/ServletScenario_Image12.jpg
deleted file mode 100644
index d0b1b75..0000000
--- a/community/tutorials/ServletScenario/images/ServletScenario_Image12.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ServletScenario/images/ServletScenario_Image13.jpg b/community/tutorials/ServletScenario/images/ServletScenario_Image13.jpg
deleted file mode 100644
index 9a0ddce..0000000
--- a/community/tutorials/ServletScenario/images/ServletScenario_Image13.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ServletScenario/images/ServletScenario_Image14.jpg b/community/tutorials/ServletScenario/images/ServletScenario_Image14.jpg
deleted file mode 100644
index 3c5ce08..0000000
--- a/community/tutorials/ServletScenario/images/ServletScenario_Image14.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ServletScenario/images/ServletScenario_Image15.jpg b/community/tutorials/ServletScenario/images/ServletScenario_Image15.jpg
deleted file mode 100644
index b464b4a..0000000
--- a/community/tutorials/ServletScenario/images/ServletScenario_Image15.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ServletScenario/images/ServletScenario_Image16.jpg b/community/tutorials/ServletScenario/images/ServletScenario_Image16.jpg
deleted file mode 100644
index 0de7c82..0000000
--- a/community/tutorials/ServletScenario/images/ServletScenario_Image16.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ServletScenario/images/ServletScenario_Image17.jpg b/community/tutorials/ServletScenario/images/ServletScenario_Image17.jpg
deleted file mode 100644
index d3fa7ca..0000000
--- a/community/tutorials/ServletScenario/images/ServletScenario_Image17.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ServletScenario/images/ServletScenario_Image18.jpg b/community/tutorials/ServletScenario/images/ServletScenario_Image18.jpg
deleted file mode 100644
index 9c395ec..0000000
--- a/community/tutorials/ServletScenario/images/ServletScenario_Image18.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ServletScenario/images/ServletScenario_Image19.jpg b/community/tutorials/ServletScenario/images/ServletScenario_Image19.jpg
deleted file mode 100644
index 8691bae..0000000
--- a/community/tutorials/ServletScenario/images/ServletScenario_Image19.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ServletScenario/images/ServletScenario_Image2.jpg b/community/tutorials/ServletScenario/images/ServletScenario_Image2.jpg
deleted file mode 100644
index 88f636a..0000000
--- a/community/tutorials/ServletScenario/images/ServletScenario_Image2.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ServletScenario/images/ServletScenario_Image20.jpg b/community/tutorials/ServletScenario/images/ServletScenario_Image20.jpg
deleted file mode 100644
index e8b393a..0000000
--- a/community/tutorials/ServletScenario/images/ServletScenario_Image20.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ServletScenario/images/ServletScenario_Image21.jpg b/community/tutorials/ServletScenario/images/ServletScenario_Image21.jpg
deleted file mode 100644
index bc3015f..0000000
--- a/community/tutorials/ServletScenario/images/ServletScenario_Image21.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ServletScenario/images/ServletScenario_Image22.jpg b/community/tutorials/ServletScenario/images/ServletScenario_Image22.jpg
deleted file mode 100644
index 19a8833..0000000
--- a/community/tutorials/ServletScenario/images/ServletScenario_Image22.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ServletScenario/images/ServletScenario_Image23.jpg b/community/tutorials/ServletScenario/images/ServletScenario_Image23.jpg
deleted file mode 100644
index 11064dc..0000000
--- a/community/tutorials/ServletScenario/images/ServletScenario_Image23.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ServletScenario/images/ServletScenario_Image3.jpg b/community/tutorials/ServletScenario/images/ServletScenario_Image3.jpg
deleted file mode 100644
index 4e6c065..0000000
--- a/community/tutorials/ServletScenario/images/ServletScenario_Image3.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ServletScenario/images/ServletScenario_Image4.jpg b/community/tutorials/ServletScenario/images/ServletScenario_Image4.jpg
deleted file mode 100644
index b299a20..0000000
--- a/community/tutorials/ServletScenario/images/ServletScenario_Image4.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ServletScenario/images/ServletScenario_Image5.jpg b/community/tutorials/ServletScenario/images/ServletScenario_Image5.jpg
deleted file mode 100644
index ba2fc4d..0000000
--- a/community/tutorials/ServletScenario/images/ServletScenario_Image5.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ServletScenario/images/ServletScenario_Image6.jpg b/community/tutorials/ServletScenario/images/ServletScenario_Image6.jpg
deleted file mode 100644
index 8a7a095..0000000
--- a/community/tutorials/ServletScenario/images/ServletScenario_Image6.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ServletScenario/images/ServletScenario_Image7.jpg b/community/tutorials/ServletScenario/images/ServletScenario_Image7.jpg
deleted file mode 100644
index d3c571a..0000000
--- a/community/tutorials/ServletScenario/images/ServletScenario_Image7.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ServletScenario/images/ServletScenario_Image8.jpg b/community/tutorials/ServletScenario/images/ServletScenario_Image8.jpg
deleted file mode 100644
index 55673da..0000000
--- a/community/tutorials/ServletScenario/images/ServletScenario_Image8.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ServletScenario/images/ServletScenario_Image9.jpg b/community/tutorials/ServletScenario/images/ServletScenario_Image9.jpg
deleted file mode 100644
index 9a9d884..0000000
--- a/community/tutorials/ServletScenario/images/ServletScenario_Image9.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/TopDownWebService/TopDownWebService.html b/community/tutorials/TopDownWebService/TopDownWebService.html
deleted file mode 100644
index 03bbb2b..0000000
--- a/community/tutorials/TopDownWebService/TopDownWebService.html
+++ /dev/null
@@ -1,301 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../..//default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../..//webtools/wtp.css" type="text/css">
-<title>Top Down Web Service Supporting Flexible Projects</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">Top Down Web Service Supporting Flexible Projects</font>
-<br>
-<font class="indexsub">Top Down Web Service Supporting Flexible Projects</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../..//images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>By Kathy Chan</b>
-
-<br>
- August 11, 2005
- <br>
-
-<br>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Introduction</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- This document is one of a series of tutorials to
- demonstrate the use of the Web Services tools in the Web
- Tools Platform Project using the <b>WTP 0.7 drivers</b>.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- This tutorial shows how to create a simple top-down Web
- service from a WSDL file. The WSDL file in this scenario
- calculates the area of an rectangle.
-
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Set Up</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Before creating the Web service, there are three
- prerequisites:
- <ol>
-
-<li>
-
-<a href="../InstallTomcat/InstallTomcat.html">
- Install Apache Tomcat
- </a>
-
-</li>
-
-<li>
- Set the <b>J2EE Project Module Preference</b> to
- allow multiple modules per project. Open
- <b>Window -> Preferences... -> J2EE Project Modules Preference
- </b> and check the <b>Allow Multiple modules per project</b> option.
- </li>
-
-<li>Create a Web project</li>
-
-<ol>
-
-<li>
- Open
- <b>
- File -> New -> Other... -> Web -> Dynamic Web
- Project
- </b>
- to create a new flexible project and Web module.
- </li>
-
-<li>Click <b>Next</b>.</li>
-
-<li>Add a new project by clicking <b>New...</b> beside the project name field.</li>
-
-<li>
- Enter
- <tt>AreaProject</tt>
- into the
- <b>Name</b>
- field.
- </li>
-
-
-<li>
- Ensure that the
- <b>Target server</b>
- is set to
- <b>Apache Tomcat v5.0</b>
- . If you have not previously configured
- a server runtime use the <b>New...</b>
- button beside the <b>Target server</b> field to
- do so. Result:
- </li>
-
-
-<br>
-
-<img border="0" SRC="images/AreaProject.JPG">
- <br>
-
-
-<li>Click <b>Finish</b> to go back to the <b>Dynamic Web Project</b> wizard.</li>
-
-<li>
- Enter
- <tt>area</tt>
- into the
- <b>Module Name</b>
- field. Result:
- </li>
-
-<br>
-
-<img border="0" SRC="images/area.JPG">
- <br>
-
-<li>
- Click
- <b>Finish</b>.
- </li>
-
-<li>
- Say <b>Yes</b> to open the J2EE perspective and you will
- see the <tt>AreaProject</tt> you created listed
- under <b>Dynamic Web Projects</b> in the <b>Project Explorer</b>
- view. Expand the <tt>AreaProject</tt> project to
- see its contents.
- </li>
-
-</ol>
-
-
-</ol>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Create a top down Java bean Web service</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ol>
-
-<li>
- Import the file
- <a href="srcfiles/AreaService.wsdl">AreaService.wsdl</a>
- into AreaProject/area/WebContent.
- </li>
-
-
-<li>Select the <b>AreaService.wsdl</b> file.</li>
-
-
-<li>
- Open File -> New -> Other... -> Web Services -> Web
- Service.
- </li>
-
-<li>Click <b>Next</b>
-</li>
-
-<li>
- In the Web service type combo, select
- <b>Top down Java bean Web Service</b>
- .
- </li>
-
-
-<li>
- Select
- <b>Overwrite files without warning</b>
- . Result:
- </li>
-
-
-<br>
-
-<img border="0" SRC="images/td1.JPG">
- <br>
-
-
-<li>
- Click
- <b>Next</b>
- . Result:
- </li>
-
-
-<br>
-
-<img border="0" src="images/td2.JPG">
- <br>
-
-
-<li>
- Click
- <b>Next</b>
- to get to the
- <b>Service Deployment Configuration Page</b>
- . Result:
- </li>
-
-
-<br>
-
-<img border="0" src="images/td3.JPG">
- <br>
-
-
-<li>
- If you want to choose a server different
- from the one defaulted by the wizard, click the
- <b>Edit</b>
- button to:
- <a href="../SelectServer/SelectServer.html">
- select a server
- </a>
-
-</li>
-
-<li>
- Click
- <b>Finish</b>.
- </li>
-
-<li>
- It will take about one minute for the wizard to assemble
- the Web service projects, start Apache Tomcat and deploy
- the projects to Tomcat. Once finished, the Java
- implementation file
- <b>AreaServiceSOAPImpl.java</b>
- will appear in the browser view. Fill in the expression
- <b>parameters.getHeight()*parameters.getWidth()</b>
- as the return value for the <tt>calculateRectArea</tt> method and save the file.
- </li>
-
-
-<br>
-
-<img border="0" SRC="images/td4.JPG">
- </ol>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Follow the instructions at
- <a href="../WebServiceClient/WebServiceClient.html">
- Creating Web Service Client
- </a>
- to create a Web service client that you can then use to test this Web service.
- </p>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/community/tutorials/TopDownWebService/TopDownWebService.xml b/community/tutorials/TopDownWebService/TopDownWebService.xml
deleted file mode 100644
index 09a81ad..0000000
--- a/community/tutorials/TopDownWebService/TopDownWebService.xml
+++ /dev/null
@@ -1,210 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?xml-stylesheet type="text/xsl" href="../../../wtp.xsl"?>
-<html>
- <head>
- <meta name="root" content="../../../../" />
- <title>Top Down Web Service Supporting Flexible Projects</title>
- </head>
- <body>
- <h1>Top Down Web Service Supporting Flexible Projects</h1>
- <p>
- <b>By Kathy Chan</b>
- <br />
- August 11, 2005
- <br />
- <br />
- </p>
-
- <h2>Introduction</h2>
- <br></br>
- <p>
- This document is one of a series of tutorials to
- demonstrate the use of the Web Services tools in the Web
- Tools Platform Project using the <b>WTP 0.7 drivers</b>.
- </p>
- <p>
- This tutorial shows how to create a simple top-down Web
- service from a WSDL file. The WSDL file in this scenario
- calculates the area of an rectangle.
-
- </p>
- <br></br>
-
-
- <h2>Set Up</h2>
- <br></br>
- <p>
- Before creating the Web service, there are three
- prerequisites:
- <ol>
- <li>
- <a href="../InstallTomcat/InstallTomcat.html">
- Install Apache Tomcat
- </a>
- </li>
- <li>
- Set the <b>J2EE Project Module Preference</b> to
- allow multiple modules per project. Open
- <b>Window -> Preferences... -> J2EE Project Modules Preference
- </b> and check the <b>Allow Multiple modules per project</b> option.
- </li>
- <li>Create a Web project</li>
- <ol>
- <li>
- Open
- <b>
- File -> New -> Other... -> Web -> Dynamic Web
- Project
- </b>
- to create a new flexible project and Web module.
- </li>
- <li>Click <b>Next</b>.</li>
- <li>Add a new project by clicking <b>New...</b> beside the project name field.</li>
- <li>
- Enter
- <tt>AreaProject</tt>
- into the
- <b>Name</b>
- field.
- </li>
-
- <li>
- Ensure that the
- <b>Target server</b>
- is set to
- <b>Apache Tomcat v5.0</b>
- . If you have not previously configured
- a server runtime use the <b>New...</b>
- button beside the <b>Target server</b> field to
- do so. Result:
- </li>
-
- <br></br>
- <img border="0"
- SRC="images/AreaProject.JPG" />
- <br></br>
-
- <li>Click <b>Finish</b> to go back to the <b>Dynamic Web Project</b> wizard.</li>
- <li>
- Enter
- <tt>area</tt>
- into the
- <b>Module Name</b>
- field. Result:
- </li>
- <br></br>
- <img border="0"
- SRC="images/area.JPG" />
- <br></br>
- <li>
- Click
- <b>Finish</b>.
- </li>
- <li>
- Say <b>Yes</b> to open the J2EE perspective and you will
- see the <tt>AreaProject</tt> you created listed
- under <b>Dynamic Web Projects</b> in the <b>Project Explorer</b>
- view. Expand the <tt>AreaProject</tt> project to
- see its contents.
- </li>
- </ol>
-
- </ol>
- </p>
-
-
- <h2>Create a top down Java bean Web service</h2>
-
- <ol>
- <li>
- Import the file
- <a href="srcfiles/AreaService.wsdl">AreaService.wsdl</a>
- into AreaProject/area/WebContent.
- </li>
-
- <li>Select the <b>AreaService.wsdl</b> file.</li>
-
- <li>
- Open File -> New -> Other... -> Web Services -> Web
- Service.
- </li>
- <li>Click <b>Next</b></li>
- <li>
- In the Web service type combo, select
- <b>Top down Java bean Web Service</b>
- .
- </li>
-
- <li>
- Select
- <b>Overwrite files without warning</b>
- . Result:
- </li>
-
- <br/>
- <img border="0"
- SRC="images/td1.JPG" />
- <br/>
-
- <li>
- Click
- <b>Next</b>
- . Result:
- </li>
-
- <br></br>
- <img border="0"
- src="images/td2.JPG" />
- <br></br>
-
- <li>
- Click
- <b>Next</b>
- to get to the
- <b>Service Deployment Configuration Page</b>
- . Result:
- </li>
-
- <br></br>
- <img border="0"
- src="images/td3.JPG" />
- <br></br>
-
- <li>
- If you want to choose a server different
- from the one defaulted by the wizard, click the
- <b>Edit</b>
- button to:
- <a href="../SelectServer/SelectServer.html">
- select a server
- </a>
- </li>
- <li>
- Click
- <b>Finish</b>.
- </li>
- <li>
- It will take about one minute for the wizard to assemble
- the Web service projects, start Apache Tomcat and deploy
- the projects to Tomcat. Once finished, the Java
- implementation file
- <b>AreaServiceSOAPImpl.java</b>
- will appear in the browser view. Fill in the expression
- <b>parameters.getHeight()*parameters.getWidth()</b>
- as the return value for the <tt>calculateRectArea</tt> method and save the file.
- </li>
-
- <br />
- <img border="0"
- SRC="images/td4.JPG" />
- </ol>
- <p>
- Follow the instructions at
- <a href="../WebServiceClient/WebServiceClient.html">
- Creating Web Service Client
- </a>
- to create a Web service client that you can then use to test this Web service.
- </p>
-
- </body>
-</html>
diff --git a/community/tutorials/TopDownWebService/images/AreaProject.JPG b/community/tutorials/TopDownWebService/images/AreaProject.JPG
deleted file mode 100644
index 753e7bb..0000000
--- a/community/tutorials/TopDownWebService/images/AreaProject.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/TopDownWebService/images/area.JPG b/community/tutorials/TopDownWebService/images/area.JPG
deleted file mode 100644
index 11930b6..0000000
--- a/community/tutorials/TopDownWebService/images/area.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/TopDownWebService/images/td1.JPG b/community/tutorials/TopDownWebService/images/td1.JPG
deleted file mode 100644
index 8cbf705..0000000
--- a/community/tutorials/TopDownWebService/images/td1.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/TopDownWebService/images/td2.JPG b/community/tutorials/TopDownWebService/images/td2.JPG
deleted file mode 100644
index b2cca51..0000000
--- a/community/tutorials/TopDownWebService/images/td2.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/TopDownWebService/images/td3.JPG b/community/tutorials/TopDownWebService/images/td3.JPG
deleted file mode 100644
index 4a8bccd..0000000
--- a/community/tutorials/TopDownWebService/images/td3.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/TopDownWebService/images/td4.JPG b/community/tutorials/TopDownWebService/images/td4.JPG
deleted file mode 100644
index c2fda77..0000000
--- a/community/tutorials/TopDownWebService/images/td4.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/TopDownWebService/srcfiles/AreaService.wsdl b/community/tutorials/TopDownWebService/srcfiles/AreaService.wsdl
deleted file mode 100644
index 0bd31ca..0000000
--- a/community/tutorials/TopDownWebService/srcfiles/AreaService.wsdl
+++ /dev/null
@@ -1,45 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://tempuri.org/AreaService/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="AreaService" targetNamespace="http://tempuri.org/AreaService/">
- <wsdl:types>
- <xsd:schema targetNamespace="http://tempuri.org/AreaService/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- <xsd:element name="area" type="xsd:float"/>
- <xsd:element name="parameters" type="tns:dimensions"/>
- <xsd:complexType name="dimensions">
- <xsd:sequence>
- <xsd:element name="width" type="xsd:float"></xsd:element>
- <xsd:element name="height" type="xsd:float"></xsd:element>
- </xsd:sequence>
- </xsd:complexType>
-
- </xsd:schema>
- </wsdl:types>
- <wsdl:message name="CalculateRectAreaResponse">
- <wsdl:part element="tns:area" name="area"/>
- </wsdl:message>
- <wsdl:message name="CalculateRectAreaRequest">
- <wsdl:part element="tns:parameters" name="parameters"/>
- </wsdl:message>
- <wsdl:portType name="AreaService">
- <wsdl:operation name="CalculateRectArea">
- <wsdl:input message="tns:CalculateRectAreaRequest"/>
- <wsdl:output message="tns:CalculateRectAreaResponse"/>
- </wsdl:operation>
- </wsdl:portType>
- <wsdl:binding name="AreaServiceSOAP" type="tns:AreaService">
- <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
- <wsdl:operation name="CalculateRectArea">
- <soap:operation soapAction="http://tempuri.org/AreaService/NewOperation"/>
- <wsdl:input>
- <soap:body use="literal"/>
- </wsdl:input>
- <wsdl:output>
- <soap:body use="literal"/>
- </wsdl:output>
- </wsdl:operation>
- </wsdl:binding>
- <wsdl:service name="AreaService">
- <wsdl:port binding="tns:AreaServiceSOAP" name="AreaServiceSOAP">
- <soap:address location="http://tempuri.org"/>
- </wsdl:port>
- </wsdl:service>
-</wsdl:definitions>
diff --git a/community/tutorials/WSDLEditor/WSDLEditorTutorial.html b/community/tutorials/WSDLEditor/WSDLEditorTutorial.html
deleted file mode 100644
index b0ecdf8..0000000
--- a/community/tutorials/WSDLEditor/WSDLEditorTutorial.html
+++ /dev/null
@@ -1,348 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../..//default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../..//webtools/wtp.css" type="text/css">
-<title>WSDL Editor Tutorial</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">WSDL Editor Tutorial</font>
-<br>
-<font class="indexsub">WSDL Editor Tutorial</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../..//images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>By Richard Mah</b>
-<BR>
-Created on February 21, 2005<BR>
-Updated on August 10, 2005<BR>
-
-<BR>
-
-<P>
-In this tutorial we look at using the WSDL Editor to create and modify a WSDL file. We explore the basic functionality along with some of the more advanced ones.
-</P>
-
-
-<P>
-
-<div align="right">
-
-<table border="0" cellpadding="2" cellspacing="0" width="100%">
-
-<tbody>
-
-<tr>
-
-<td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font face="Arial,Helvetica"><font color="#ffffff">New WSDL Wizard</font></font></b></td>
-
-</tr>
-
-</tbody>
-
-</table>
-
-</div>
-
-
-<BR>
-
-</P>
-
-<OL>
-
-<LI>Create a new project called "WSDL Example".</LI>
-
-<LI>Launch the new WSDL Wizard (File --> New --> Other --> XML --> WSDL). Select "WSDL" under the "XML" folder and click on "Next".</LI>
-
-<LI>Enter "Employee.wsdl" as the name for the WSDL file and select "WSDL Example" as the project where the WSDL should be created. Click on "Next".</LI>
-
-<LI>The first two fields of the "Options" dialog page are used to set the target namespace and prefix of the WSDL. For our example, use the default values. (Figure 1).</LI>
-
-</OL>
-
-
-<B>Figure 1</B>
-
-<BR>
-
-<IMG border="0" src="images/wsdleditor-new-wizard.jpg">
-
-
-
-<P>
-The next option is the "Create WSDL Skeleton". If this option is selected, the wizard will create a simple WSDL skeleton from which we can quickly modify the WSDL as we see fit. We will discuss the contents of the generated skeleton below.
-<BR>
-<BR>
-If the "Create WSDL Skeleton" is selected, we are presented with additional options to configure. The first is the protocol. From this dropdown menu we can select either the SOAP or HTTP protocol. Next are the Binding Options. The choices listed here will depend on the protocol selected. Only Binding Options which apply to the selected protocol will be displayed. The Protocol and Binding Options selected here will be used to generate the Binding for the WSDL Skeleton.
-<BR>
-<BR>
-For our example, use the default Protocol and Binding options (SOAP Protocol and document literal Binding Option) and click on "Finish".
-<BR>
-<BR>
-Below we see the generated WSDL skeleton (Graph View).
-</P>
-
-
-<B>Figure 2</B>
-
-<BR>
-
-<IMG border="0" src="images/wsdleditor-new-skeleton.jpg">
-
-<P>
-The graph view above displays the WSDL in an easy to read format. The view is divided into several groups with each containing instances of that particular element.
-<BR>
-<BR>
-Selecting a WSDL element in the graph view also shows it's relationship to the other elements by connecting arrow lines. For example, if we select "NewOperationRequest" Part (Figure 2), arrow lines will be drawn from the Port --> Binding Input --> Port Type Input --> Part --> XML Schema Element.
-</P>
-
-
-<P>
-
-<div align="right">
-
-<table border="0" cellpadding="2" cellspacing="0" width="100%">
-
-<tbody>
-
-<tr>
-
-<td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font face="Arial,Helvetica"><font color="#ffffff">Editing the WSDL</font></font></b></td>
-
-</tr>
-
-</tbody>
-
-</table>
-
-</div>
-
-
-<BR>
-
-</P>
-
-
-<P>
-
-<B>1) Renaming WSDL Elements</B>
-
-<BR>
-
-</P>
-
-
-<P>
-Renaming a WSDL Element is done by right-clicking on the element and selecting "Rename". Alternatively, rename can be done through the properties view.
-<BR>
-<BR>
-For our example, rename the Operation "NewOperation" to "EmployeeInfoById". Notice the multiple renamings which occur. The Operation is renamed along with it's associated Messages, Parts, and XML Schema Elements. (Figure 3).
-</P>
-
-
-<B>Figure 3</B>
-
-<BR>
-
-<IMG border="0" src="images/wsdleditor-smart-rename1.jpg">
-
-
-<P>
-
-<B>2) Creating a new WSDL Operation</B>
-
-<BR>
-
-</P>
-
-
-<P>
-To create an Operation, select the Port Type "Employee". Right-click and select "Add Operation". The Add Operation dialog will appear. See Figure 4
-</P>
-
-
-<B>Figure 4</B>
-
-<BR>
-
-<IMG border="0" src="images/wsdleditor-new-operation.jpg">
-
-<P>
-The dialog contains the option "Create default messages". Selecting this option will create a new Operation along with the following associated elements:<BR>
-
-<UL>
-
-<LI>Input and Output</LI>
-
-<LI>Two Messages with one Part each</LI>
-
-<LI>Two XML Schema Elements. One for each Part</LI>
-
-</UL>
-
-<BR>
-Without the "Create default messages" option selected, only the Opeation along with an input and output will be created.
-<BR>
-<BR>
-For our example, select the "Create default messages" option and type in "EmployeeInfoByName" as the name. Click on "Ok".
-Notice the names used for the newly created WSDL and XML Schema objects.
-</P>
-
-
-
-<P>
-
-<B>3) Editing the Inline Schema</B>
-
-<BR>
-
-</P>
-
-
-<P>
-We shall use the XML Schema View to modify the inline schema. In the "Types" group, double-click on the inline schema. The XML Schema View will appear showing four XML Schema Elements. Follow the steps below to edit the XML Schema:
-<OL>
-
-<LI>Create a Complex Type by right-clicking in the "Types" group and selecting "Add Complex Type".</LI>
-
-<LI>Double-click on the Complex Type to drilldown into it.</LI>
-
-<LI>Rename the Complex Type to "EmployeeInfo".</LI>
-
-<LI>Right-click on the Complex Type and select "Add Sequence".</LI>
-
-<LI>Select the newly created sequence and add three Elements by right-clicking and selecting "Add Element".</LI>
-
-<LI>Modify the newly created Elements so they appear like Figure 5.</LI>
-
-
-<BR>
-<BR>
-
-<B>Figure 5</B>
-
-<BR>
-
-<IMG border="0" src="images/wsdleditor-complex-type.jpg">
-<BR>
-<BR>
-
-
-
-
-
-
-
-<LI>Move up from the Element view to the Schema view using the back
-<IMG border="0" src="images/wsdleditor-backbutton.jpg">
-button located at the top.</LI>
-
-<LI>Select the Element "EmployeeInfoByIdRequest". In the properties view, change the Type from "string" to "integer".</LI>
-
-<LI>Double-click on the Element "EmployeeInfoByIdResponse" to drilldown into the Element.</LI>
-
-<LI>Rename the Element to "EmployeeInfo".</LI>
-
-<LI>In the properties view, change the Type from "string" to "EmployeeInfo" and click on "Ok". See Figure 6</LI>
-
-
-<BR>
-<BR>
-
-<B>Figure 6</B>
-
-<BR>
-
-<IMG border="0" src="images/wsdleditor-settype-dialog.jpg">
-<BR>
-<BR>
-
-
-<LI>Move up from the Element view to the Schema view using the back button located at the top.</LI>
-
-<LI>Next, delete the Element "EmplyeeInfoByNameResponse". Right-click on the Element and select "Delete".</LI>
-
-<LI>Move back from the Schema view to the WSDL view using the back button located at the top.</LI>
-
-<LI>We must now modify "EmployeeInfoByIdResponse" and "EmployeeInfoByNameResponse" Parts to reference the renamed XML Schema Element "EmployeeInfo". Right-click on the Part and select "Set Element" --> "Existing Element..." from the context menu. In the dialog, select the "EmployeeInfo" Element and click on "Finish". See Figure 7</LI>
-
-</OL>
-
-
-<B>Figure 7</B>
-
-<BR>
-
-<IMG border="0" src="images/wsdleditor-setelement-dialog.jpg">
-
-</P>
-
-
-
-<P>
-
-<B>3) Re-generating the Binding</B>
-
-<BR>
-
-</P>
-
-
-<P>
-The last step required is the re-generation of the Binding. The Binding was originally based on the Operation generated by the wizard. But since then we have modified and created a brand-new Operation. Right-click on the "EmployeeSOAP" Binding and select "Generate Binding Content...".
-Select the "Overwrite existing binding information" option and click-on "Finish". See Figure 8.
-</P>
-
-
-<B>Figure 8</B>
-
-<BR>
-
-<IMG border="0" src="images/wsdleditor-binding.jpg">
-
-<P>
-The finished WSDL file is shown in Figure 9.
-</P>
-
-
-<B>Figure 9</B>
-
-<BR>
-
-<IMG border="0" src="images/wsdleditor-finished-wsdl.jpg">
-
-<P>
-Automatic binding generation is also available. The Bindings will be regenerated to reflect the changes made to the Port Types when a Save is executed. By default, this option is enabled but may be turned off via the WSDL Preferences ("Window" --> "Preferences" --> "Web and XML" --> "WSDL Files"). See Figure 10.
-</P>
-
-
-<B>Figure 10</B>
-
-<BR>
-
-<IMG border="0" src="images/wsdleditor-preferences.jpg">
-
-<P>
-Now that we've finished editing the WSDL, you can save the file.
-</P>
-
-</p>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/community/tutorials/WSDLEditor/WSDLEditorTutorial.xml b/community/tutorials/WSDLEditor/WSDLEditorTutorial.xml
deleted file mode 100644
index 8a52de1..0000000
--- a/community/tutorials/WSDLEditor/WSDLEditorTutorial.xml
+++ /dev/null
@@ -1,212 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<?xml-stylesheet type="text/xsl" href="../../../wtp.xsl"?>
-<html>
-<head>
- <meta name="root" content="../../../../" />
- <title>WSDL Editor Tutorial</title>
-</head>
-<body>
-
-<h1>WSDL Editor Tutorial</h1>
-<p>
-<b>By Richard Mah</b><BR/>
-Created on February 21, 2005<BR/>
-Updated on August 10, 2005<BR/>
-<BR/>
-<P>
-In this tutorial we look at using the WSDL Editor to create and modify a WSDL file. We explore the basic functionality along with some of the more advanced ones.
-</P>
-
-<P>
-<div align="right">
- <table border="0" cellpadding="2" cellspacing="0" width="100%">
- <tbody>
- <tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font face="Arial,Helvetica"><font color="#ffffff">New WSDL Wizard</font></font></b></td>
- </tr>
- </tbody>
- </table>
-</div>
-
-<BR/>
-</P>
-<OL>
- <LI>Create a new project called "WSDL Example".</LI>
- <LI>Launch the new WSDL Wizard (File --> New --> Other --> XML --> WSDL). Select "WSDL" under the "XML" folder and click on "Next".</LI>
- <LI>Enter "Employee.wsdl" as the name for the WSDL file and select "WSDL Example" as the project where the WSDL should be created. Click on "Next".</LI>
- <LI>The first two fields of the "Options" dialog page are used to set the target namespace and prefix of the WSDL. For our example, use the default values. (Figure 1).</LI>
-</OL>
-
-<B>Figure 1</B>
-<BR/>
-<IMG border="0" src="images/wsdleditor-new-wizard.jpg"/>
-
-
-
-<P>
-The next option is the "Create WSDL Skeleton". If this option is selected, the wizard will create a simple WSDL skeleton from which we can quickly modify the WSDL as we see fit. We will discuss the contents of the generated skeleton below.
-<BR/><BR/>
-If the "Create WSDL Skeleton" is selected, we are presented with additional options to configure. The first is the protocol. From this dropdown menu we can select either the SOAP or HTTP protocol. Next are the Binding Options. The choices listed here will depend on the protocol selected. Only Binding Options which apply to the selected protocol will be displayed. The Protocol and Binding Options selected here will be used to generate the Binding for the WSDL Skeleton.
-<BR/><BR/>
-For our example, use the default Protocol and Binding options (SOAP Protocol and document literal Binding Option) and click on "Finish".
-<BR/><BR/>
-Below we see the generated WSDL skeleton (Graph View).
-</P>
-
-<B>Figure 2</B>
-<BR/>
-<IMG border="0" src="images/wsdleditor-new-skeleton.jpg"/>
-
-<P>
-The graph view above displays the WSDL in an easy to read format. The view is divided into several groups with each containing instances of that particular element.
-<BR/><BR/>
-Selecting a WSDL element in the graph view also shows it's relationship to the other elements by connecting arrow lines. For example, if we select "NewOperationRequest" Part (Figure 2), arrow lines will be drawn from the Port --> Binding Input --> Port Type Input --> Part --> XML Schema Element.
-</P>
-
-<P>
-<div align="right">
- <table border="0" cellpadding="2" cellspacing="0" width="100%">
- <tbody>
- <tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font face="Arial,Helvetica"><font color="#ffffff">Editing the WSDL</font></font></b></td>
- </tr>
- </tbody>
- </table>
-</div>
-
-<BR/>
-</P>
-
-<P>
-<B>1) Renaming WSDL Elements</B>
-<BR/>
-</P>
-
-<P>
-Renaming a WSDL Element is done by right-clicking on the element and selecting "Rename". Alternatively, rename can be done through the properties view.
-<BR/><BR/>
-For our example, rename the Operation "NewOperation" to "EmployeeInfoById". Notice the multiple renamings which occur. The Operation is renamed along with it's associated Messages, Parts, and XML Schema Elements. (Figure 3).
-</P>
-
-<B>Figure 3</B>
-<BR/>
-<IMG border="0" src="images/wsdleditor-smart-rename1.jpg"/>
-
-
-<P>
-<B>2) Creating a new WSDL Operation</B>
-<BR/>
-</P>
-
-<P>
-To create an Operation, select the Port Type "Employee". Right-click and select "Add Operation". The Add Operation dialog will appear. See Figure 4
-</P>
-
-<B>Figure 4</B>
-<BR/>
-<IMG border="0" src="images/wsdleditor-new-operation.jpg"/>
-
-<P>
-The dialog contains the option "Create default messages". Selecting this option will create a new Operation along with the following associated elements:<BR/>
-<UL>
- <LI>Input and Output</LI>
- <LI>Two Messages with one Part each</LI>
- <LI>Two XML Schema Elements. One for each Part</LI>
-</UL>
-<BR/>
-Without the "Create default messages" option selected, only the Opeation along with an input and output will be created.
-<BR/><BR/>
-For our example, select the "Create default messages" option and type in "EmployeeInfoByName" as the name. Click on "Ok".
-Notice the names used for the newly created WSDL and XML Schema objects.
-</P>
-
-
-<P>
-<B>3) Editing the Inline Schema</B>
-<BR/>
-</P>
-
-<P>
-We shall use the XML Schema View to modify the inline schema. In the "Types" group, double-click on the inline schema. The XML Schema View will appear showing four XML Schema Elements. Follow the steps below to edit the XML Schema:
-<OL>
- <LI>Create a Complex Type by right-clicking in the "Types" group and selecting "Add Complex Type".</LI>
- <LI>Double-click on the Complex Type to drilldown into it.</LI>
- <LI>Rename the Complex Type to "EmployeeInfo".</LI>
- <LI>Right-click on the Complex Type and select "Add Sequence".</LI>
- <LI>Select the newly created sequence and add three Elements by right-clicking and selecting "Add Element".</LI>
- <LI>Modify the newly created Elements so they appear like Figure 5.</LI>
-
-<BR/><BR/>
-<B>Figure 5</B>
-<BR/>
-<IMG border="0" src="images/wsdleditor-complex-type.jpg"/>
-<BR/><BR/>
-
-
-
-
-
-
-<LI>Move up from the Element view to the Schema view using the back
-<IMG border="0" src="images/wsdleditor-backbutton.jpg"/>
-button located at the top.</LI>
-<LI>Select the Element "EmployeeInfoByIdRequest". In the properties view, change the Type from "string" to "integer".</LI>
-<LI>Double-click on the Element "EmployeeInfoByIdResponse" to drilldown into the Element.</LI>
-<LI>Rename the Element to "EmployeeInfo".</LI>
-<LI>In the properties view, change the Type from "string" to "EmployeeInfo" and click on "Ok". See Figure 6</LI>
-
-<BR/><BR/>
-<B>Figure 6</B>
-<BR/>
-<IMG border="0" src="images/wsdleditor-settype-dialog.jpg"/>
-<BR/><BR/>
-
-<LI>Move up from the Element view to the Schema view using the back button located at the top.</LI>
-<LI>Next, delete the Element "EmplyeeInfoByNameResponse". Right-click on the Element and select "Delete".</LI>
-<LI>Move back from the Schema view to the WSDL view using the back button located at the top.</LI>
-<LI>We must now modify "EmployeeInfoByIdResponse" and "EmployeeInfoByNameResponse" Parts to reference the renamed XML Schema Element "EmployeeInfo". Right-click on the Part and select "Set Element" --> "Existing Element..." from the context menu. In the dialog, select the "EmployeeInfo" Element and click on "Finish". See Figure 7</LI>
-</OL>
-
-<B>Figure 7</B>
-<BR/>
-<IMG border="0" src="images/wsdleditor-setelement-dialog.jpg"/>
-
-</P>
-
-
-<P>
-<B>3) Re-generating the Binding</B>
-<BR/>
-</P>
-
-<P>
-The last step required is the re-generation of the Binding. The Binding was originally based on the Operation generated by the wizard. But since then we have modified and created a brand-new Operation. Right-click on the "EmployeeSOAP" Binding and select "Generate Binding Content...".
-Select the "Overwrite existing binding information" option and click-on "Finish". See Figure 8.
-</P>
-
-<B>Figure 8</B>
-<BR/>
-<IMG border="0" src="images/wsdleditor-binding.jpg"/>
-
-<P>
-The finished WSDL file is shown in Figure 9.
-</P>
-
-<B>Figure 9</B>
-<BR/>
-<IMG border="0" src="images/wsdleditor-finished-wsdl.jpg"/>
-
-<P>
-Automatic binding generation is also available. The Bindings will be regenerated to reflect the changes made to the Port Types when a Save is executed. By default, this option is enabled but may be turned off via the WSDL Preferences ("Window" --> "Preferences" --> "Web and XML" --> "WSDL Files"). See Figure 10.
-</P>
-
-<B>Figure 10</B>
-<BR/>
-<IMG border="0" src="images/wsdleditor-preferences.jpg"/>
-
-<P>
-Now that we've finished editing the WSDL, you can save the file.
-</P>
-</p>
-</body>
-</html>
diff --git a/community/tutorials/WSDLEditor/images/wsdleditor-backbutton.jpg b/community/tutorials/WSDLEditor/images/wsdleditor-backbutton.jpg
deleted file mode 100644
index ebcd1c7..0000000
--- a/community/tutorials/WSDLEditor/images/wsdleditor-backbutton.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/WSDLEditor/images/wsdleditor-binding.jpg b/community/tutorials/WSDLEditor/images/wsdleditor-binding.jpg
deleted file mode 100644
index be74d57..0000000
--- a/community/tutorials/WSDLEditor/images/wsdleditor-binding.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/WSDLEditor/images/wsdleditor-choose-type.jpg b/community/tutorials/WSDLEditor/images/wsdleditor-choose-type.jpg
deleted file mode 100644
index 3dd5398..0000000
--- a/community/tutorials/WSDLEditor/images/wsdleditor-choose-type.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/WSDLEditor/images/wsdleditor-complex-type.jpg b/community/tutorials/WSDLEditor/images/wsdleditor-complex-type.jpg
deleted file mode 100644
index 15d6071..0000000
--- a/community/tutorials/WSDLEditor/images/wsdleditor-complex-type.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/WSDLEditor/images/wsdleditor-dotbutton.jpg b/community/tutorials/WSDLEditor/images/wsdleditor-dotbutton.jpg
deleted file mode 100644
index 68b7e99..0000000
--- a/community/tutorials/WSDLEditor/images/wsdleditor-dotbutton.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/WSDLEditor/images/wsdleditor-finished-wsdl.jpg b/community/tutorials/WSDLEditor/images/wsdleditor-finished-wsdl.jpg
deleted file mode 100644
index 9c56342..0000000
--- a/community/tutorials/WSDLEditor/images/wsdleditor-finished-wsdl.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/WSDLEditor/images/wsdleditor-new-operation.jpg b/community/tutorials/WSDLEditor/images/wsdleditor-new-operation.jpg
deleted file mode 100644
index 8dc34a3..0000000
--- a/community/tutorials/WSDLEditor/images/wsdleditor-new-operation.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/WSDLEditor/images/wsdleditor-new-skeleton.jpg b/community/tutorials/WSDLEditor/images/wsdleditor-new-skeleton.jpg
deleted file mode 100644
index 57ddb29..0000000
--- a/community/tutorials/WSDLEditor/images/wsdleditor-new-skeleton.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/WSDLEditor/images/wsdleditor-new-wizard.jpg b/community/tutorials/WSDLEditor/images/wsdleditor-new-wizard.jpg
deleted file mode 100644
index 50553f6..0000000
--- a/community/tutorials/WSDLEditor/images/wsdleditor-new-wizard.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/WSDLEditor/images/wsdleditor-preferences.jpg b/community/tutorials/WSDLEditor/images/wsdleditor-preferences.jpg
deleted file mode 100644
index 1568e4c..0000000
--- a/community/tutorials/WSDLEditor/images/wsdleditor-preferences.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/WSDLEditor/images/wsdleditor-setelement-dialog.jpg b/community/tutorials/WSDLEditor/images/wsdleditor-setelement-dialog.jpg
deleted file mode 100644
index f48165e..0000000
--- a/community/tutorials/WSDLEditor/images/wsdleditor-setelement-dialog.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/WSDLEditor/images/wsdleditor-settype-dialog.jpg b/community/tutorials/WSDLEditor/images/wsdleditor-settype-dialog.jpg
deleted file mode 100644
index 8a36a66..0000000
--- a/community/tutorials/WSDLEditor/images/wsdleditor-settype-dialog.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/WSDLEditor/images/wsdleditor-smart-rename1.jpg b/community/tutorials/WSDLEditor/images/wsdleditor-smart-rename1.jpg
deleted file mode 100644
index cc68a44..0000000
--- a/community/tutorials/WSDLEditor/images/wsdleditor-smart-rename1.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/WSDLEditor/images/wsdleditor-specify-element.jpg b/community/tutorials/WSDLEditor/images/wsdleditor-specify-element.jpg
deleted file mode 100644
index 55b61fa..0000000
--- a/community/tutorials/WSDLEditor/images/wsdleditor-specify-element.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/WebServiceClient/WebServiceClient.html b/community/tutorials/WebServiceClient/WebServiceClient.html
deleted file mode 100644
index a4f2d90..0000000
--- a/community/tutorials/WebServiceClient/WebServiceClient.html
+++ /dev/null
@@ -1,188 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../..//default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../..//webtools/wtp.css" type="text/css">
-<title>Web Service Client Supporting Flexible Projects</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">Web Service Client Supporting Flexible Projects</font>
-<br>
-<font class="indexsub">Web Service Client Supporting Flexible Projects</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../..//images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>By Kathy Chan</b>
-
-<br>
- Aug 4, 2005
- <br>
-
-<br>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Introduction</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- This document is one of a series of tutorials to
- demonstrate the use of the Web Services tools in the Web
- Tools Platform Project with the <b>WTP 0.7 drivers</b>.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- This tutorial shows how to create a Web serivce client to a
- deployed Web service created in
- <a href="../TopDownWebService/TopDownWebService.html">
- Creating a top down Web service
- </a>.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Create a Web service Client</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ol>
-
-<li>
- Select the <b>AreaServiceSOAP.wsdl</b> file in the
- <b>AreaProject\area\WebContent\wsdl</b> folder created in
- <a href="../TopDownWebService/TopDownWebService.html">
- Creating a top down Web service
- </a> tutorial.
- <br>
-<b>Do not</b> select the AreaService.wsdl
- file in AreaProject\area\WebContent.
- </li>
-
-
-<li>
- Open <b>File -> New -> Other... -> Web Services -> Web
- Service Client</b>.
- </li>
-
-<li>Click <b>Next</b>.</li>
-
-<li>
- Select
- <b>Test the Web service</b>
- and
- <b>Overwrite files without warning</b>.
- </li>
-
-
-<br>
-
-<img border="0" SRC="images/client1.JPG">
- <br>
-
-
-<li>Click <b>Next</b>.</li>
-
-
-<br>
-
-<img border="0" SRC="images/client2.JPG">
- <br>
-
-
-<li>
- Click <b>Next</b> and accept the defaults on the <b>Web Service Selection Page</b>.
- </li>
-
-<li>
- On the <b>Client Environment Configuration</b> page, type in
- <b>AreaProjectClient</b>
- as the name of the Client project and <b>areaClient</b> as the Client module.
- <br>
- If you want to choose a server different from the one
- defaulted by the wizard, click the
- <b>Edit</b>
- button to:
- <a href="../SelectServer/SelectServer.html">select a server</a>.
- </li>
-
-<br>
-
-<img border="0" SRC="images/client3.JPG">
-
- <li>
- Click <b>Finish</b>.
- </li>
-
-
-<li>
- It will take about one minute for the wizard to assemble
- the Web service client Web projects, start Apache
- Tomcat, and deploy the project to Tomcat. Once
- finished, the generated Sample JSP Web application will
- appear in the browser view.
- </li>
-
-
-<li>
- Under
- <b>Methods</b>, click on
- <b>calculateRectArea</b>
- .
- </li>
-
-
-<li>
- Under
- <b>Inputs</b>, enter
- <tt>2.0</tt>
- and
- <tt>5.0</tt>
- into the height and width entry field.
- </li>
-
-
-<li>
- Click on
- <b>Invoke</b>. In the <b>Result</b> view, you should get a response of
- <b>10.0</b>.
- </li>
-
-<br>
-
-<img border="0" SRC="images/client4.JPG">
-
- </ol>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/community/tutorials/WebServiceClient/WebServiceClient.xml b/community/tutorials/WebServiceClient/WebServiceClient.xml
deleted file mode 100644
index 2c4b548..0000000
--- a/community/tutorials/WebServiceClient/WebServiceClient.xml
+++ /dev/null
@@ -1,127 +0,0 @@
-<?xml-stylesheet type="text/xsl" href="../../../wtp.xsl"?>
-<html>
- <head>
- <meta name="root" content="../../../../" />
- <title>Web Service Client Supporting Flexible Projects</title>
- </head>
- <body>
- <h1>Web Service Client Supporting Flexible Projects</h1>
- <p>
- <b>By Kathy Chan</b>
- <br />
- Aug 4, 2005
- <br />
- <br />
- </p>
-
- <h2>Introduction</h2>
- <br></br>
- <p>
- This document is one of a series of tutorials to
- demonstrate the use of the Web Services tools in the Web
- Tools Platform Project with the <b>WTP 0.7 drivers</b>.
- </p>
- <p>
- This tutorial shows how to create a Web serivce client to a
- deployed Web service created in
- <a href="../TopDownWebService/TopDownWebService.html">
- Creating a top down Web service
- </a>.
- </p>
- <br />
-
- <h2>Create a Web service Client</h2>
-
- <ol>
- <li>
- Select the <b>AreaServiceSOAP.wsdl</b> file in the
- <b>AreaProject\area\WebContent\wsdl</b> folder created in
- <a href="../TopDownWebService/TopDownWebService.html">
- Creating a top down Web service
- </a> tutorial.
- <br/><b>Do not</b> select the AreaService.wsdl
- file in AreaProject\area\WebContent.
- </li>
-
- <li>
- Open <b>File -> New -> Other... -> Web Services -> Web
- Service Client</b>.
- </li>
- <li>Click <b>Next</b>.</li>
- <li>
- Select
- <b>Test the Web service</b>
- and
- <b>Overwrite files without warning</b>.
- </li>
-
- <br/>
- <img border="0"
- SRC="images/client1.JPG" />
- <br/>
-
- <li>Click <b>Next</b>.</li>
-
- <br/>
- <img border="0"
- SRC="images/client2.JPG" />
- <br/>
-
- <li>
- Click <b>Next</b> and accept the defaults on the <b>Web Service Selection Page</b>.
- </li>
- <li>
- On the <b>Client Environment Configuration</b> page, type in
- <b>AreaProjectClient</b>
- as the name of the Client project and <b>areaClient</b> as the Client module.
- <br/>
- If you want to choose a server different from the one
- defaulted by the wizard, click the
- <b>Edit</b>
- button to:
- <a href="../SelectServer/SelectServer.html">select a server</a>.
- </li>
- <br />
- <img border="0"
- SRC="images/client3.JPG" />
-
- <li>
- Click <b>Finish</b>.
- </li>
-
- <li>
- It will take about one minute for the wizard to assemble
- the Web service client Web projects, start Apache
- Tomcat, and deploy the project to Tomcat. Once
- finished, the generated Sample JSP Web application will
- appear in the browser view.
- </li>
-
- <li>
- Under
- <b>Methods</b>, click on
- <b>calculateRectArea</b>
- .
- </li>
-
- <li>
- Under
- <b>Inputs</b>, enter
- <tt>2.0</tt>
- and
- <tt>5.0</tt>
- into the height and width entry field.
- </li>
-
- <li>
- Click on
- <b>Invoke</b>. In the <b>Result</b> view, you should get a response of
- <b>10.0</b>.
- </li>
- <br></br>
- <img border="0"
- SRC="images/client4.JPG" />
-
- </ol>
- </body>
-</html>
diff --git a/community/tutorials/WebServiceClient/images/client1.JPG b/community/tutorials/WebServiceClient/images/client1.JPG
deleted file mode 100644
index b4cf325..0000000
--- a/community/tutorials/WebServiceClient/images/client1.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/WebServiceClient/images/client2.JPG b/community/tutorials/WebServiceClient/images/client2.JPG
deleted file mode 100644
index 61d680d..0000000
--- a/community/tutorials/WebServiceClient/images/client2.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/WebServiceClient/images/client3.JPG b/community/tutorials/WebServiceClient/images/client3.JPG
deleted file mode 100644
index a660312..0000000
--- a/community/tutorials/WebServiceClient/images/client3.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/WebServiceClient/images/client4.JPG b/community/tutorials/WebServiceClient/images/client4.JPG
deleted file mode 100644
index e96d3af..0000000
--- a/community/tutorials/WebServiceClient/images/client4.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/WebServiceExplorer/WebServiceExplorer.html b/community/tutorials/WebServiceExplorer/WebServiceExplorer.html
deleted file mode 100644
index 1c00d81..0000000
--- a/community/tutorials/WebServiceExplorer/WebServiceExplorer.html
+++ /dev/null
@@ -1,271 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../..//default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../..//webtools/wtp.css" type="text/css">
-<title>Using Web Service Explorer to test a Web service</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">Using Web Service Explorer to test a Web service</font>
-<br>
-<font class="indexsub">Using Web Service Explorer to test a Web service</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../..//images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>By Kathy Chan</b>
-
-<br>
- Aug 4, 2005
- <br>
-
-<br>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Introduction</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- This document is one of a series of tutorials to
- demonstrate the use of the Web Services tools in the Web
- Tools Platform Project using the <b>WTP 0.7 drivers</b>.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- This tutorial shows how to use the Web Service Explorer to
- test a Web service via native WSDL and SOAP. It demonstrates
- how to use the Web Services Explorer to invoke operations on
- a Web service named "
- <a href="http://www.xmethods.net/ve2/ViewListing.po;jsessionid=TZdF2D6E_KB9KKIY5_DG4FJw(QHyMHiRM)?key=uuid:477CEED8-1EDD-89FA-1070-6C2DBE1685F8" target="_top">
- Temperature - Weather
- </a>
- " as available from
- <a href="http://www.xmethods.net/" target="_top">XMethods</a>
- on the internet.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The only prerequisite is that you be connected to the
- internet. If you are connected via a firewall, you can use
- the Internet preferences page (choose
- <b>Preferences -> Internet</b>
- from the main menu). Otherwise, you can begin with a
- completely fresh workspace and no installed servers.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Using the Web Services Explorer to test a Web service</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ol>
-
-<li>Launch the Eclipse WTP workbench.</li>
-
-
-<li>
- From the main menu bar, select
- <b>Run -> Launch the Web Services Explorer</b>. This will take a few moments the first time while
- Eclipse's internal Tomcat server starts up and loads the
- Web Services Explorer application.
- </li>
-
-
-<li>
- After the Web Browser view opens, maximize it. Result:
- </li>
-
-<br>
-
-<img border="0" SRC="images/imageU71.JPG">
- <li>
- In the Web Service Explorer's toolbar (top-right), click
- on the
- <b>WSDL Page</b>
- icon,
- </li>
-
-<br>
-
-<img border="0" SRC="images/wsdl.gif">
- <br>
-
-<img border="0" SRC="images/imageEJ9.JPG">
-
- <li>
- Click on the
- <img border="0" SRC="images/wsdl_main.gif">
- <b>WSDL Main</b>
- icon. Result:
- </li>
-
-<br>
-
-<img border="0" SRC="images/imageIAI.JPG">
-
- <li>
- In the
- <b>WSDL URL</b>
- field, enter the URL
- <tt>
- http://www.xmethods.net/sd/2001/TemperatureService.wsdl
- </tt>, then click on
- <b>Go</b>
- . Result:
- </li>
-
-<br>
-
-<img border="0" SRC="images/imageO78.JPG">
-
- <li>
- Under
- <b>Operations</b>
- in the right hand pane, click on
- <b>getTemp</b>. Result:
- </li>
-
-<br>
-
-<img border="0" SRC="images/image99L.JPG">
-
- <li>
- In the
- <b>zipcode string</b>
- entry field, enter
- <tt>90210</tt>, then click on
- <b>Go</b>
- . In the
- <b>Status</b>
- pane, you should see an answer like this:
- </li>
-
-
-<br>
-
-<b>return (float): 57.0</b>
-
-<p>
- You may need to move the horizontal bar separating the
- <b>Actions</b>
- and
- <b>Status</b>
- panes upwards a bit to get a better view. Result:
- </p>
-
-<br>
-
-<img border="0" SRC="images/imageLKF.JPG">
-
- </ol>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Explanation</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The Web Services Explorer is a JSP Web application hosted on
- the Apache Tomcat servlet engine contained within Eclipse.
- It is integrated into Eclipse on two levels: visually by
- virtue of it running in the embedded browser, and logically
- by virtue of it running as a thread in the Eclipse JRE.
- Though not demonstrated in this scenario, this latter type
- of integration allows the Web Services Explorer to access
- resources in the workspace, write resources into the
- workspace, and launch various Web services wizards.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The Web Services Explorer provides three key services to the
- user:
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ol>
-
-<li>
- Comprehensive support for discovering Web services in
- WS-Inspection 1.0 documents, and in UDDI v2 or v3
- registries using the UDDI v2 protocol.
- </li>
-
-
-<li>
- Comprehensive support for publishing Web services to
- UDDI v2 or v3 registries using the UDDI v2 protocol.
- </li>
-
-
-<li>
- Comprehensive support for browsing and invoking Web
- services natively via their WSDL and XSD.
- </li>
-
-</ol>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<img border="0" SRC="images/note.gif" alt="Note: ">
- <br>
- A key point of the scenario above is that no code was
- generated and no servers were required in order to invoke
- operations on the WSDL.
- </p>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/community/tutorials/WebServiceExplorer/WebServiceExplorer.xml b/community/tutorials/WebServiceExplorer/WebServiceExplorer.xml
deleted file mode 100644
index a1d7fb5..0000000
--- a/community/tutorials/WebServiceExplorer/WebServiceExplorer.xml
+++ /dev/null
@@ -1,183 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?xml-stylesheet type="text/xsl" href="../../../wtp.xsl"?>
-<html>
- <head>
- <meta name="root" content="../../../../" />
- <title>Using Web Service Explorer to test a Web service</title>
- </head>
- <body>
- <h1>Using Web Service Explorer to test a Web service</h1>
- <p>
- <b>By Kathy Chan</b>
- <br />
- Aug 4, 2005
- <br />
- <br />
- </p>
-
- <h2>Introduction</h2>
- <br></br>
- <p>
- This document is one of a series of tutorials to
- demonstrate the use of the Web Services tools in the Web
- Tools Platform Project using the <b>WTP 0.7 drivers</b>.
- </p>
- <p>
- This tutorial shows how to use the Web Service Explorer to
- test a Web service via native WSDL and SOAP. It demonstrates
- how to use the Web Services Explorer to invoke operations on
- a Web service named "
- <a
- href="http://www.xmethods.net/ve2/ViewListing.po;jsessionid=TZdF2D6E_KB9KKIY5_DG4FJw(QHyMHiRM)?key=uuid:477CEED8-1EDD-89FA-1070-6C2DBE1685F8" target="_top">
- Temperature - Weather
- </a>
- " as available from
- <a href="http://www.xmethods.net/" target="_top">XMethods</a>
- on the internet.
- </p>
- <p>
- The only prerequisite is that you be connected to the
- internet. If you are connected via a firewall, you can use
- the Internet preferences page (choose
- <b>Preferences -> Internet</b>
- from the main menu). Otherwise, you can begin with a
- completely fresh workspace and no installed servers.
- </p>
-
- <br />
-
- <h2>Using the Web Services Explorer to test a Web service</h2>
- <br></br>
- <ol>
- <li>Launch the Eclipse WTP workbench.</li>
-
- <li>
- From the main menu bar, select
- <b>Run -> Launch the Web Services Explorer</b>. This will take a few moments the first time while
- Eclipse's internal Tomcat server starts up and loads the
- Web Services Explorer application.
- </li>
-
- <li>
- After the Web Browser view opens, maximize it. Result:
- </li>
- <br></br>
- <img border="0"
- SRC="images/imageU71.JPG" />
- <li>
- In the Web Service Explorer's toolbar (top-right), click
- on the
- <b>WSDL Page</b>
- icon,
- </li>
- <br></br>
- <img border="0" SRC="images/wsdl.gif" />
- <br></br>
- <img border="0"
- SRC="images/imageEJ9.JPG" />
-
- <li>
- Click on the
- <img border="0"
- SRC="images/wsdl_main.gif" />
- <b>WSDL Main</b>
- icon. Result:
- </li>
- <br />
- <img border="0"
- SRC="images/imageIAI.JPG" />
-
- <li>
- In the
- <b>WSDL URL</b>
- field, enter the URL
- <tt>
- http://www.xmethods.net/sd/2001/TemperatureService.wsdl
- </tt>, then click on
- <b>Go</b>
- . Result:
- </li>
- <br />
- <img border="0"
- SRC="images/imageO78.JPG" />
-
- <li>
- Under
- <b>Operations</b>
- in the right hand pane, click on
- <b>getTemp</b>. Result:
- </li>
- <br></br>
- <img border="0"
- SRC="images/image99L.JPG" />
-
- <li>
- In the
- <b>zipcode string</b>
- entry field, enter
- <tt>90210</tt>, then click on
- <b>Go</b>
- . In the
- <b>Status</b>
- pane, you should see an answer like this:
- </li>
-
- <br />
- <b>return (float): 57.0</b>
- <p>
- You may need to move the horizontal bar separating the
- <b>Actions</b>
- and
- <b>Status</b>
- panes upwards a bit to get a better view. Result:
- </p>
- <br></br>
- <img border="0"
- SRC="images/imageLKF.JPG" />
-
- </ol>
- <h2>Explanation</h2>
- <br />
- <p>
- The Web Services Explorer is a JSP Web application hosted on
- the Apache Tomcat servlet engine contained within Eclipse.
- It is integrated into Eclipse on two levels: visually by
- virtue of it running in the embedded browser, and logically
- by virtue of it running as a thread in the Eclipse JRE.
- Though not demonstrated in this scenario, this latter type
- of integration allows the Web Services Explorer to access
- resources in the workspace, write resources into the
- workspace, and launch various Web services wizards.
- </p>
- <p>
- The Web Services Explorer provides three key services to the
- user:
- </p>
- <ol>
- <li>
- Comprehensive support for discovering Web services in
- WS-Inspection 1.0 documents, and in UDDI v2 or v3
- registries using the UDDI v2 protocol.
- </li>
-
- <li>
- Comprehensive support for publishing Web services to
- UDDI v2 or v3 registries using the UDDI v2 protocol.
- </li>
-
- <li>
- Comprehensive support for browsing and invoking Web
- services natively via their WSDL and XSD.
- </li>
- </ol>
- <p>
- <img border="0" SRC="images/note.gif"
- alt="Note: " />
- <br />
- A key point of the scenario above is that no code was
- generated and no servers were required in order to invoke
- operations on the WSDL.
- </p>
-
- </body>
-</html>
diff --git a/community/tutorials/WebServiceExplorer/images/image99L.JPG b/community/tutorials/WebServiceExplorer/images/image99L.JPG
deleted file mode 100644
index 506abdb..0000000
--- a/community/tutorials/WebServiceExplorer/images/image99L.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/WebServiceExplorer/images/imageEJ9.JPG b/community/tutorials/WebServiceExplorer/images/imageEJ9.JPG
deleted file mode 100644
index be7350e..0000000
--- a/community/tutorials/WebServiceExplorer/images/imageEJ9.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/WebServiceExplorer/images/imageIAI.JPG b/community/tutorials/WebServiceExplorer/images/imageIAI.JPG
deleted file mode 100644
index d2f625c..0000000
--- a/community/tutorials/WebServiceExplorer/images/imageIAI.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/WebServiceExplorer/images/imageLKF.JPG b/community/tutorials/WebServiceExplorer/images/imageLKF.JPG
deleted file mode 100644
index ff98f42..0000000
--- a/community/tutorials/WebServiceExplorer/images/imageLKF.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/WebServiceExplorer/images/imageO78.JPG b/community/tutorials/WebServiceExplorer/images/imageO78.JPG
deleted file mode 100644
index 67077f8..0000000
--- a/community/tutorials/WebServiceExplorer/images/imageO78.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/WebServiceExplorer/images/imageU71.JPG b/community/tutorials/WebServiceExplorer/images/imageU71.JPG
deleted file mode 100644
index 9ee0430..0000000
--- a/community/tutorials/WebServiceExplorer/images/imageU71.JPG
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/WebServiceExplorer/images/note.gif b/community/tutorials/WebServiceExplorer/images/note.gif
deleted file mode 100644
index f6260db..0000000
--- a/community/tutorials/WebServiceExplorer/images/note.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/WebServiceExplorer/images/wsdl.gif b/community/tutorials/WebServiceExplorer/images/wsdl.gif
deleted file mode 100644
index 8fb844f..0000000
--- a/community/tutorials/WebServiceExplorer/images/wsdl.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/WebServiceExplorer/images/wsdl_main.gif b/community/tutorials/WebServiceExplorer/images/wsdl_main.gif
deleted file mode 100644
index 9f074e8..0000000
--- a/community/tutorials/WebServiceExplorer/images/wsdl_main.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/XMLCatalog/XMLCatalogTutorial.html b/community/tutorials/XMLCatalog/XMLCatalogTutorial.html
deleted file mode 100644
index 51e154d..0000000
--- a/community/tutorials/XMLCatalog/XMLCatalogTutorial.html
+++ /dev/null
@@ -1,225 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../..//default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../..//webtools/wtp.css" type="text/css">
-<title>XML Catalog Tutorial</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">XML Catalog Tutorial</font>
-<br>
-<font class="indexsub">XML Catalog Tutorial</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../..//images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>By Richard Mah</b>
-<BR>
-Created on December 17, 2004<BR>
-Updated on August 10, 2005<BR>
-
-<BR>
-In this tutorial, we will demonstrate the use of the XML Catalog. Add the Example “Editing and validating XML files”.
-Select File -> New -> Other -> Examples -> Editing and Validating XML files.
-
-To demonstrate the XML Catalog, let’s use Invoice.dtd and Invoice.xml located in the XMLExamples project.
-
-<ol>
-
-<li>
-Create a new folder “Invoice2” in the project “XMLExamples”.
-</li>
-
-<li>
-Move Invoice.dtd located in XMLExamples\Invoice\ to the new location XMLExamples\Invoice2.
-</li>
-
-<li>
-Validate Invoice.xml. See the validating XML tutorial. Notice the validation has generated a warning. This is because Invoice.dtd cannot be found. To fix this problem, we shall add an entry into the XML Catalog (demonstrated below).
-</li>
-
-</ol>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<div align="right">
-
-<table border="0" cellpadding="2" cellspacing="0" width="100%">
-
-<tbody>
-
-<tr>
-
-<td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font face="Arial,Helvetica"><font color="#ffffff">Adding and Removing from the XML Catalog</font></font></b></td>
-
-</tr>
-
-</tbody>
-
-</table>
-
-</div>
-
-<BR>
-The XML Catalog can be accessed through the preferences.
-<ol>
-
-<li>
- Select “Window -> Preferences” to launch the Preferences dialog.
-</li>
-
-<li>
- Expand the “Web and XML” heading and select “XML Catalog”.
-</li>
-
-</ol>
-The dialog should appear as in Figure 1.
-
-<p>
-<b>Figure 1</b>
-<br>
-
-<IMG border="0" src="images/XMLCatalog-Figure1.jpg"></p>
-
-
-
-<H4>Adding an XML Catalog Entry</H4>
-
-<ol>
-
-<li>
-From the Preferences XML Catalog dialog, select “Add…”.</li>
-
-<li>
-In the “New XML Catalog Entry” dialog, fill in the values as they
-appear Figure 2.
-<p>
-<b>Figure 2</b>
-<br>
-
-<IMG border="0" src="images/XMLCatalog-Figure2.jpg"></p>
-
-</li>
-
-<li>
-Click “OK” to finish. Notice there is a new entry, InvoiceId, under
-“User Specified Entries”.</li>
-
-
-<li>
-Validate Invoice.xml again. Notice it is now valid.</li>
-
-</ol>
-
-
-<h4>Removing and Editing an XML Catalog Entry</h4>
-To remove or edit an entry, simply select the entry and click on “Delete”
-or “Edit…”.
-<BR>
-
-<BR>
-
-<div align="right">
-
-<table border="0" cellpadding="2" cellspacing="0" width="100%">
-
-<tbody>
-
-<tr>
-
-<td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font face="Arial,Helvetica"><font color="#ffffff">Importing and Exporting a Catalog</font></font></b></td>
-
-</tr>
-
-</tbody>
-
-</table>
-
-</div>
-
-<BR>
-XML Catalog entries can be saved to a file for later use. This avoids
-users having to add entries to an XML Catalog when they have already done
-so in a previous workspace.
-From the “Advanced XML Catalog Preferences” dialog, the importing and
-exporting XML Catalog options are available. See Figure 3.
-
-<p>
-<b>Figure 3</b>
-<br>
-
-<IMG border="0" src="images/XMLCatalog-Figure3.jpg"></p>
-
-
-<h4>Exporting XML Catalog settings:</h4>
-
-<ol>
-
-<li>
-Selecting the “Export…” button on the “Advanced XML Catalog Preferences”
-dialog.</li>
-
-
-<li>
-The “Export XML Catalog Settings” dialog will appear. See Figure
-4. Select the Project “Catalog” (create if ncecessary) as the location to store the XML
-Catalog settings file. Enter “.xmlcatalog” as the file name.
-Click “OK” to finish. The entries specified in the XML Catalog will
-now be saved in the file.</li>
-
-</ol>
-
-
-<p>
-<b>Figure 4</b>
-<br>
-
-<IMG border="0" src="images/XMLCatalog-Figure4.jpg"></p>
-
-
-
-<H4>Importing XML Catalog settings:</H4>
-
-<ol>
-
-<li>
-Selecting the “Import…” button on the “Advanced XML Catalog Preferences” dialog.
-</li>
-
-<li>
-The “Import XML Catalog Settings” dialog will appear. See Figure 5. Select the file containing the XML Catalog settings (.xmlcatalog) and click “OK” to finish. The entries specified in the file will now be in the XML Catalog.
-</li>
-
-</ol>
-
-
-<p>
-<b>Figure 5</b>
-<br>
-
-<IMG border="0" src="images/XMLCatalog-Figure5.jpg"></p>
-
-
-</p>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/community/tutorials/XMLCatalog/XMLCatalogTutorial.xml b/community/tutorials/XMLCatalog/XMLCatalogTutorial.xml
deleted file mode 100644
index 3fc0a07..0000000
--- a/community/tutorials/XMLCatalog/XMLCatalogTutorial.xml
+++ /dev/null
@@ -1,135 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<?xml-stylesheet type="text/xsl" href="../../../wtp.xsl"?>
-<html>
-<head>
- <meta name="root" content="../../../../" />
- <title>XML Catalog Tutorial</title>
-</head>
-<body>
-
-<h1>XML Catalog Tutorial</h1>
-<p>
-<b>By Richard Mah</b><BR/>
-Created on December 17, 2004<BR/>
-Updated on August 10, 2005<BR/>
-<BR/>
-In this tutorial, we will demonstrate the use of the XML Catalog. Add the Example “Editing and validating XML files”.
-Select File -> New -> Other -> Examples -> Editing and Validating XML files.
-
-To demonstrate the XML Catalog, let’s use Invoice.dtd and Invoice.xml located in the XMLExamples project.
-
-<ol>
-<li>
-Create a new folder “Invoice2” in the project “XMLExamples”.
-</li>
-<li>
-Move Invoice.dtd located in XMLExamples\Invoice\ to the new location XMLExamples\Invoice2.
-</li>
-<li>
-Validate Invoice.xml. See the validating XML tutorial. Notice the validation has generated a warning. This is because Invoice.dtd cannot be found. To fix this problem, we shall add an entry into the XML Catalog (demonstrated below).
-</li>
-</ol>
-</p>
-
-<p>
-<div align="right">
- <table border="0" cellpadding="2" cellspacing="0" width="100%">
- <tbody>
- <tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font face="Arial,Helvetica"><font color="#ffffff">Adding and Removing from the XML Catalog</font></font></b></td>
- </tr>
- </tbody>
- </table>
-</div>
-<BR/>
-The XML Catalog can be accessed through the preferences.
-<ol>
-<li>
- Select “Window -> Preferences” to launch the Preferences dialog.
-</li>
-<li>
- Expand the “Web and XML” heading and select “XML Catalog”.
-</li>
-</ol>
-The dialog should appear as in Figure 1.
-
-<p><b>Figure 1</b><br/>
-<IMG border="0" src="images/XMLCatalog-Figure1.jpg"/></p>
-
-
-<H4>Adding an XML Catalog Entry</H4>
-<ol>
-<li>
-From the Preferences XML Catalog dialog, select “Add…”.</li>
-<li>
-In the “New XML Catalog Entry” dialog, fill in the values as they
-appear Figure 2.
-<p><b>Figure 2</b><br/>
-<IMG border="0" src="images/XMLCatalog-Figure2.jpg"/></p>
-</li>
-<li>
-Click “OK” to finish. Notice there is a new entry, InvoiceId, under
-“User Specified Entries”.</li>
-
-<li>
-Validate Invoice.xml again. Notice it is now valid.</li>
-</ol>
-
-<h4>Removing and Editing an XML Catalog Entry</h4>
-To remove or edit an entry, simply select the entry and click on “Delete”
-or “Edit…”.
-<BR/>
-<BR/>
-<div align="right">
- <table border="0" cellpadding="2" cellspacing="0" width="100%">
- <tbody>
- <tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font face="Arial,Helvetica"><font color="#ffffff">Importing and Exporting a Catalog</font></font></b></td>
- </tr>
- </tbody>
- </table>
-</div>
-<BR/>
-XML Catalog entries can be saved to a file for later use. This avoids
-users having to add entries to an XML Catalog when they have already done
-so in a previous workspace.
-From the “Advanced XML Catalog Preferences” dialog, the importing and
-exporting XML Catalog options are available. See Figure 3.
-
-<p><b>Figure 3</b><br/>
-<IMG border="0" src="images/XMLCatalog-Figure3.jpg"/></p>
-
-<h4>Exporting XML Catalog settings:</h4>
-<ol>
-<li>
-Selecting the “Export…” button on the “Advanced XML Catalog Preferences”
-dialog.</li>
-
-<li>
-The “Export XML Catalog Settings” dialog will appear. See Figure
-4. Select the Project “Catalog” (create if ncecessary) as the location to store the XML
-Catalog settings file. Enter “.xmlcatalog” as the file name.
-Click “OK” to finish. The entries specified in the XML Catalog will
-now be saved in the file.</li>
-</ol>
-
-<p><b>Figure 4</b><br/>
-<IMG border="0" src="images/XMLCatalog-Figure4.jpg"/></p>
-
-
-<H4>Importing XML Catalog settings:</H4>
-<ol>
-<li>
-Selecting the “Import…” button on the “Advanced XML Catalog Preferences” dialog.
-</li>
-<li>
-The “Import XML Catalog Settings” dialog will appear. See Figure 5. Select the file containing the XML Catalog settings (.xmlcatalog) and click “OK” to finish. The entries specified in the file will now be in the XML Catalog.
-</li>
-</ol>
-
-<p><b>Figure 5</b><br/>
-<IMG border="0" src="images/XMLCatalog-Figure5.jpg"/></p>
-
-</p>
-</body>
-</html>
diff --git a/community/tutorials/XMLCatalog/images/XMLCatalog-Figure1.jpg b/community/tutorials/XMLCatalog/images/XMLCatalog-Figure1.jpg
deleted file mode 100644
index 1c01b6f..0000000
--- a/community/tutorials/XMLCatalog/images/XMLCatalog-Figure1.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/XMLCatalog/images/XMLCatalog-Figure2.jpg b/community/tutorials/XMLCatalog/images/XMLCatalog-Figure2.jpg
deleted file mode 100644
index 8e46d53..0000000
--- a/community/tutorials/XMLCatalog/images/XMLCatalog-Figure2.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/XMLCatalog/images/XMLCatalog-Figure3.jpg b/community/tutorials/XMLCatalog/images/XMLCatalog-Figure3.jpg
deleted file mode 100644
index 5d87d0c..0000000
--- a/community/tutorials/XMLCatalog/images/XMLCatalog-Figure3.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/XMLCatalog/images/XMLCatalog-Figure4.jpg b/community/tutorials/XMLCatalog/images/XMLCatalog-Figure4.jpg
deleted file mode 100644
index c334bbf..0000000
--- a/community/tutorials/XMLCatalog/images/XMLCatalog-Figure4.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/XMLCatalog/images/XMLCatalog-Figure5.jpg b/community/tutorials/XMLCatalog/images/XMLCatalog-Figure5.jpg
deleted file mode 100644
index a94614e..0000000
--- a/community/tutorials/XMLCatalog/images/XMLCatalog-Figure5.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/XMLSchemaEditor/XMLSchemaEditorTutorial.html b/community/tutorials/XMLSchemaEditor/XMLSchemaEditorTutorial.html
deleted file mode 100644
index 3f3f80f..0000000
--- a/community/tutorials/XMLSchemaEditor/XMLSchemaEditorTutorial.html
+++ /dev/null
@@ -1,141 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../..//default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../..//webtools/wtp.css" type="text/css">
-<title>XML Schema Editor Tutorial</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">XML Schema Editor Tutorial</font>
-<br>
-<font class="indexsub">XML Schema Editor Tutorial</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../..//images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>By Keith Chong and Craig Salter</b>
-<BR>
-December 23, 2004<BR>
-
-<BR>
-
-<P>
-This tutorial will use the catalog.xsd from the "Editing and validating XML files" Examples. To create it,
-select New -> Examples... to launch the wizard. Follow the instructions described in the wizard, then click Finish to create the example project.
-</P>
-
-<P>
-Once created, under the PublicationCatalogue folder, locate the Catalogue.xsd file and double click the file to open it in the XML Schema Editor. As shown below, an Outline and Properties view is provided in addition
-to the editor pane. At the bottom of the editor area you'll see that there is a 'Source' and a 'Graph' tab at the bottom of the editor area. The 'Source' tab is used
-for basic XML source editing. The 'Graph' tab is used for higher level graphical editing. Select the 'Graph' tab so that you're looking at the Graph view. As shown
-below you should see a 'top level' view of the XML Schema that summarizes all of the components (e.g. elements and types) that are defined in the schema.
-<BR>
-
-<BR>
-
-<IMG border="0" src="images/xsdeditor-figure1.jpg">
-</P>
-
-<P>In order to see these components in detail you can 'drill down' on a component of interest by double clicking on it. For example,
-if we double click on the 'Book' component, the editor will display the structure of the 'Book' element as shown below. Notice that the +/- controls can
-be used to navigate into an element's containment structure. To return to the 'top level' view, press the back button
-<IMG border="0" src="images/xsdeditor-backbutton.jpg">
-at the top left of the editor, or right clicking within the editor and selecting 'Back to Schema' from the context menu.<BR>
-
-<BR>
-
-<IMG border="0" src="images/xsdeditor-figure2.jpg">
-</P>
-
-<P>Editing the schema is achieved by invoking context menu actions on selected objects in the Graph view and
-using the properties view to modify the properties of the selected object. Follow the steps below to create a new element
-declaration and define its content.</P>
-
-<OL>
-
-<LI>right click within the 'Elements' section of the top level schema and choose 'Add Global Element'</LI>
-
-<LI>use the properties view to change the name of the element to 'Paper'
- <IMG border="0" src="images/xsdeditor-figure3.jpg">
- </LI>
-
-<LI>now double click on the element in the editor to drill down on the element so that we can edit its structure</LI>
-
-<LI>right click on Paper and select 'Add Sequence' to specify that the element will contain a sequence of child elements.<BR>
-
-<IMG border="0" src="images/xsdeditor-figure4.jpg">
- <BR>
-
-</LI>
-
-<LI>click on the anonymous complex type, and then from the properties view, click on the [...] button for Base Type.<BR>
-
-<IMG border="0" src="images/xsdeditor-figure5.jpg">
- <BR>
-
-<BR>
-
-</LI>
-
-<LI>
- The Available Types dialog will appear. Select the User Defined Complex Types radio button, then select PublicationType, and click OK
- <IMG border="0" src="images/xsdeditor-figure6.jpg">
- <br>
-
-<BR>
-
-</LI>
-
-<LI>
- Paper's type is now shown below. Right click on the sequence node and add an element.<BR>
-
-<IMG border="0" src="images/xsdeditor-figure7.jpg">
- <BR>
-
-<BR>
-
-</LI>
-
-<LI>
- Name the newly added element 'URL', because, say, the paper is found on the web.<BR>
-
-<IMG border="0" src="images/xsdeditor-figure8.jpg">
- <br>
-</LI>
-
-<LI>
- Click on the Paper element. In the properties view, click on the 'Other' tab. For the
- substitutionGroup property, click in the cell editor to the right of the label. A drop-down
- combobox will appear. Select PublisherType. Your editor should look like this:<BR>
-
-<BR>
-
-<IMG border="0" src="images/xsdeditor-figure9.jpg">
- <BR>
-
-</LI>
-
-<BR>
-
-<LI>Now that we've finished editing the XML Schema you can save the file.</LI>
-
-</OL>
-
-</p>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/community/tutorials/XMLSchemaEditor/XMLSchemaEditorTutorial.xml b/community/tutorials/XMLSchemaEditor/XMLSchemaEditorTutorial.xml
deleted file mode 100644
index 25a9f78..0000000
--- a/community/tutorials/XMLSchemaEditor/XMLSchemaEditorTutorial.xml
+++ /dev/null
@@ -1,83 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<?xml-stylesheet type="text/xsl" href="../../../wtp.xsl"?>
-<html>
-<head>
- <meta name="root" content="../../../../" />
- <title>XML Schema Editor Tutorial</title>
-</head>
-<body>
-
-<h1>XML Schema Editor Tutorial</h1>
-<p>
-<b>By Keith Chong and Craig Salter</b><BR/>
-December 23, 2004<BR/>
-<BR/>
-<P>
-This tutorial will use the catalog.xsd from the "Editing and validating XML files" Examples. To create it,
-select New -> Examples... to launch the wizard. Follow the instructions described in the wizard, then click Finish to create the example project.
-</P>
-<P>
-Once created, under the PublicationCatalogue folder, locate the Catalogue.xsd file and double click the file to open it in the XML Schema Editor. As shown below, an Outline and Properties view is provided in addition
-to the editor pane. At the bottom of the editor area you'll see that there is a 'Source' and a 'Graph' tab at the bottom of the editor area. The 'Source' tab is used
-for basic XML source editing. The 'Graph' tab is used for higher level graphical editing. Select the 'Graph' tab so that you're looking at the Graph view. As shown
-below you should see a 'top level' view of the XML Schema that summarizes all of the components (e.g. elements and types) that are defined in the schema.
-<BR/>
-<BR/>
-<IMG border="0" src="images/xsdeditor-figure1.jpg"/>
-</P>
-<P>In order to see these components in detail you can 'drill down' on a component of interest by double clicking on it. For example,
-if we double click on the 'Book' component, the editor will display the structure of the 'Book' element as shown below. Notice that the +/- controls can
-be used to navigate into an element's containment structure. To return to the 'top level' view, press the back button
-<IMG border="0" src="images/xsdeditor-backbutton.jpg"/>
-at the top left of the editor, or right clicking within the editor and selecting 'Back to Schema' from the context menu.<BR/>
-<BR/>
-<IMG border="0" src="images/xsdeditor-figure2.jpg"/>
-</P>
-<P>Editing the schema is achieved by invoking context menu actions on selected objects in the Graph view and
-using the properties view to modify the properties of the selected object. Follow the steps below to create a new element
-declaration and define its content.</P>
-<OL>
- <LI>right click within the 'Elements' section of the top level schema and choose 'Add Global Element'</LI>
- <LI>use the properties view to change the name of the element to 'Paper'
- <IMG border="0" src="images/xsdeditor-figure3.jpg"/>
- </LI>
- <LI>now double click on the element in the editor to drill down on the element so that we can edit its structure</LI>
- <LI>right click on Paper and select 'Add Sequence' to specify that the element will contain a sequence of child elements.<BR/>
- <IMG border="0" src="images/xsdeditor-figure4.jpg"/>
- <BR/>
- </LI>
- <LI>click on the anonymous complex type, and then from the properties view, click on the [...] button for Base Type.<BR/>
- <IMG border="0" src="images/xsdeditor-figure5.jpg"/>
- <BR/>
- <BR/>
- </LI>
- <LI>
- The Available Types dialog will appear. Select the User Defined Complex Types radio button, then select PublicationType, and click OK
- <IMG border="0" src="images/xsdeditor-figure6.jpg"/>
- <br/>
- <BR/>
- </LI>
- <LI>
- Paper's type is now shown below. Right click on the sequence node and add an element.<BR/>
- <IMG border="0" src="images/xsdeditor-figure7.jpg"/>
- <BR/>
- <BR/>
- </LI>
- <LI>
- Name the newly added element 'URL', because, say, the paper is found on the web.<BR/>
- <IMG border="0" src="images/xsdeditor-figure8.jpg"/>
- <br/></LI>
- <LI>
- Click on the Paper element. In the properties view, click on the 'Other' tab. For the
- substitutionGroup property, click in the cell editor to the right of the label. A drop-down
- combobox will appear. Select PublisherType. Your editor should look like this:<BR/>
- <BR/>
- <IMG border="0" src="images/xsdeditor-figure9.jpg"/>
- <BR/>
- </LI>
- <BR/>
- <LI>Now that we've finished editing the XML Schema you can save the file.</LI>
-</OL>
-</p>
-</body>
-</html>
diff --git a/community/tutorials/XMLSchemaEditor/XSDEditorDemo/XSDEditorDemo.jpg b/community/tutorials/XMLSchemaEditor/XSDEditorDemo/XSDEditorDemo.jpg
deleted file mode 100644
index d4ceaf0..0000000
--- a/community/tutorials/XMLSchemaEditor/XSDEditorDemo/XSDEditorDemo.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/XMLSchemaEditor/XSDEditorDemo/XSDEditorDemo.swf b/community/tutorials/XMLSchemaEditor/XSDEditorDemo/XSDEditorDemo.swf
deleted file mode 100644
index d02b12b..0000000
--- a/community/tutorials/XMLSchemaEditor/XSDEditorDemo/XSDEditorDemo.swf
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/XMLSchemaEditor/XSDEditorDemo/XSDEditorDemo_viewlet_swf.html b/community/tutorials/XMLSchemaEditor/XSDEditorDemo/XSDEditorDemo_viewlet_swf.html
deleted file mode 100644
index c2364c1..0000000
--- a/community/tutorials/XMLSchemaEditor/XSDEditorDemo/XSDEditorDemo_viewlet_swf.html
+++ /dev/null
@@ -1,57 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../../..//default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../../..//webtools/wtp.css" type="text/css">
-<title>XML Schema Editor Demo</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">XML Schema Editor Demonstration</font>
-<br>
-<font class="indexsub">XML Schema Editor Demo</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../../..//images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>By Ella Belisario</b>
-<br>
-January 18, 2005<br>
-<br>
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>This demo shows building a simple XML Schema for keeping records of university students. Click on the image links below to run the demo.</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<center>
-
-<object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=5,0,0,0" width="800" height="616">
- <param name="movie" value="XSDEditorDemo.swf">
- <param name="quality" value="high">
- <param name="bgcolor" value="#ffffff">
-
-<embed src="XSDEditorDemo.swf" quality="high" bgcolor="#ffffff" width="800" height="616" type="application/x-shockwave-flash" pluginspage="http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash"></embed>
-
-</object>
- </center>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/community/tutorials/XMLSchemaEditor/XSDEditorDemo/XSDEditorDemo_viewlet_swf.xml b/community/tutorials/XMLSchemaEditor/XSDEditorDemo/XSDEditorDemo_viewlet_swf.xml
deleted file mode 100644
index e4de8c9..0000000
--- a/community/tutorials/XMLSchemaEditor/XSDEditorDemo/XSDEditorDemo_viewlet_swf.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<?xml-stylesheet type="text/xsl" href="../../../../wtp.xsl"?>
-<html>
-<head>
- <meta name="root" content="../../../../../" />
- <title>XML Schema Editor Demo</title>
- <meta name="Keywords" content="qarbon,viewlet,viewletbuilder, demo software, animation software, on line training, flash tutorial, flash demo, multimedia presentation, interactive software, training, software, online presentation, it help desk software, presentation software, learning software, online documentation, simulation software, viewlets" />
- <meta name="Description" content="text" />
-</head>
-<body>
-
-<h1>XML Schema Editor Demonstration</h1>
-<p>
-<b>By Ella Belisario</b><br/>
-January 18, 2005<br/><br/></p>
-
-<p>This demo shows building a simple XML Schema for keeping records of university students. Click on the image links below to run the demo.</p>
-
- <center>
- <object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=5,0,0,0" width="800" height="616">
- <param name="movie" value="XSDEditorDemo.swf"/>
- <param name="quality" value="high"/>
- <param name="bgcolor" value="#ffffff"/>
- <embed src="XSDEditorDemo.swf" quality="high" bgcolor="#ffffff" width="800" height="616" type="application/x-shockwave-flash" pluginspage="http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash"/>
- </object>
- </center>
-</body>
-</html>
diff --git a/community/tutorials/XMLSchemaEditor/images/xsdeditor-backbutton.jpg b/community/tutorials/XMLSchemaEditor/images/xsdeditor-backbutton.jpg
deleted file mode 100644
index 2092605..0000000
--- a/community/tutorials/XMLSchemaEditor/images/xsdeditor-backbutton.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure1.jpg b/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure1.jpg
deleted file mode 100644
index f3b4f6f..0000000
--- a/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure1.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure2.jpg b/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure2.jpg
deleted file mode 100644
index 518c606..0000000
--- a/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure2.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure3.jpg b/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure3.jpg
deleted file mode 100644
index a66b6e7..0000000
--- a/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure3.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure4.jpg b/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure4.jpg
deleted file mode 100644
index 2a187da..0000000
--- a/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure4.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure5.jpg b/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure5.jpg
deleted file mode 100644
index b9622ef..0000000
--- a/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure5.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure6.jpg b/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure6.jpg
deleted file mode 100644
index 6e253b8..0000000
--- a/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure6.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure7.jpg b/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure7.jpg
deleted file mode 100644
index dfb7523..0000000
--- a/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure7.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure8.jpg b/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure8.jpg
deleted file mode 100644
index ef61772..0000000
--- a/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure8.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure9.jpg b/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure9.jpg
deleted file mode 100644
index 664eecc..0000000
--- a/community/tutorials/XMLSchemaEditor/images/xsdeditor-figure9.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/XMLValidation/XMLValidationTutorial.html b/community/tutorials/XMLValidation/XMLValidationTutorial.html
deleted file mode 100644
index 36739a9..0000000
--- a/community/tutorials/XMLValidation/XMLValidationTutorial.html
+++ /dev/null
@@ -1,282 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../..//default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../..//webtools/wtp.css" type="text/css">
-<title>Validation Tutorial</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">Validation Tutorial</font>
-<br>
-<font class="indexsub">Validation Tutorial</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../..//images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>By Richard Mah</b>
-<BR>
-Created on December 22, 2004<BR>
-Updated on August 10, 2005<BR>
-
-<BR>
-Eclipse WTP includes validation tools for XML, DTD, and XML Schema. Validation can be invoked manually or automatically after every save.
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<div align="right">
-
-<table border="0" cellpadding="2" cellspacing="0" width="100%">
-
-<tbody>
-
-<tr>
-
-<td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font face="Arial,Helvetica"><font color="#ffffff">Manually Invoking the Validator</font></font></b></td>
-
-</tr>
-
-</tbody>
-
-</table>
-
-</div>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>The validator can be invoked manually by right-clicking on a resource (XML, DTD, or XML Schema file), and selecting the "Validate (XML/DTD/XML Schema) File" menu item. See <B>Figure 1</B>.
-</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><B>Figure 1</B></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><img border="0" src="images/Validate_XML_Menu.jpg"></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>Manually invoking the validator will display a message dialog informing the user the validity of the resource. For example, the dialog shown in <B>Figure 2</B> will be displayed when a valid XML file is validated.
-</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><B>Figure 2</B></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><img border="0" src="images/Validate_XML_Success.jpg"></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>Similarly, the dialog shown in <B>Figure 3</B> will be displayed when an invalid XML file is validated.
-</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><B>Figure 3</B></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><img border="0" src="images/Validate_XML_Fail.jpg"></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<div align="right">
-
-<table border="0" cellpadding="2" cellspacing="0" width="100%">
-
-<tbody>
-
-<tr>
-
-<td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font face="Arial,Helvetica"><font color="#ffffff">Automatically Invoking the Validator After Every Save</font></font></b></td>
-
-</tr>
-
-</tbody>
-
-</table>
-
-</div>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>
-To invoke the validator after every save, right-click on the project (XMLExamples) and select Properties. Select the "Validation" heading and select the "Override validation preferences" checkbox. Also select the "Run validation automatically when you save changes to XMLExamples resources." checkbox. <B>See Figure 4</B>.
-</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><B>Figure 4</B></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><img border="0" src="images/Validate_XML_Save_Dialog.jpg"></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>
-No message dialogs will appear with results from the validation. Only updates to the Problems view will be done. If the resource being validated is valid, no errors will appear in the Problems view. If there are problems, new entries will be created in the view.
-</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<div align="right">
-
-<table border="0" cellpadding="2" cellspacing="0" width="100%">
-
-<tbody>
-
-<tr>
-
-<td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font face="Arial,Helvetica"><font color="#ffffff">Locating Errors in the Resource</font></font></b></td>
-
-</tr>
-
-</tbody>
-
-</table>
-
-</div>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>
-Further information explaining the cause of the validation error will appear in the Problems view (To open the Problems view, select Problems from the menu bar. Window --> Show View --> Problems). Selecting the error in the Problems view will highlight the error in the Source view allowing users to quickly locate and correct the problem. See <B>Figure 5</B>.
-</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><B>Figure 5</B></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><img border="0" src="images/Validate_XML_Problems_View.jpg"></td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/community/tutorials/XMLValidation/XMLValidationTutorial.xml b/community/tutorials/XMLValidation/XMLValidationTutorial.xml
deleted file mode 100644
index 98a1fdd..0000000
--- a/community/tutorials/XMLValidation/XMLValidationTutorial.xml
+++ /dev/null
@@ -1,105 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<?xml-stylesheet type="text/xsl" href="../../../wtp.xsl"?>
-<html>
-<head>
- <meta name="root" content="../../../../" />
- <title>Validation Tutorial</title>
-</head>
-<body>
-<h1>Validation Tutorial</h1>
-<p>
-<b>By Richard Mah</b><BR/>
-Created on December 22, 2004<BR/>
-Updated on August 10, 2005<BR/>
-<BR/>
-Eclipse WTP includes validation tools for XML, DTD, and XML Schema. Validation can be invoked manually or automatically after every save.
-</p>
-<BR/>
-<div align="right">
- <table border="0" cellpadding="2" cellspacing="0" width="100%">
- <tbody>
- <tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font face="Arial,Helvetica"><font color="#ffffff">Manually Invoking the Validator</font></font></b></td>
- </tr>
- </tbody>
- </table>
-</div>
-<P>The validator can be invoked manually by right-clicking on a resource (XML, DTD, or XML Schema file), and selecting the "Validate (XML/DTD/XML Schema) File" menu item. See <B>Figure 1</B>.
-</P>
-
-<BR/>
-<B>Figure 1</B>
-<BR/>
-<img border="0" src="images/Validate_XML_Menu.jpg"/>
-
-<BR/>
-
-<P>Manually invoking the validator will display a message dialog informing the user the validity of the resource. For example, the dialog shown in <B>Figure 2</B> will be displayed when a valid XML file is validated.
-</P>
-<BR/>
-<BR/>
-
-<B>Figure 2</B>
-<BR/>
-<img border="0" src="images/Validate_XML_Success.jpg"/>
-
-<BR/>
-A similar dialog will appear for DTD and XML Schema files.
-<BR/>
-<BR/>
-<P>Similarly, the dialog shown in <B>Figure 3</B> will be displayed when an invalid XML file is validated.
-</P>
-<BR/>
-<B>Figure 3</B>
-<BR/>
-<img border="0" src="images/Validate_XML_Fail.jpg"/>
-
-<BR/>
-A similar dialog will appear for DTD and XML Schema files.
-
-<BR/>
-<BR/>
-<div align="right">
- <table border="0" cellpadding="2" cellspacing="0" width="100%">
- <tbody>
- <tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font face="Arial,Helvetica"><font color="#ffffff">Automatically Invoking the Validator After Every Save</font></font></b></td>
- </tr>
- </tbody>
- </table>
-</div>
-<P>
-To invoke the validator after every save, right-click on the project (XMLExamples) and select Properties. Select the "Validation" heading and select the "Override validation preferences" checkbox. Also select the "Run validation automatically when you save changes to XMLExamples resources." checkbox. <B>See Figure 4</B>.
-</P>
-<BR/>
-<B>Figure 4</B>
-<BR/>
-<img border="0" src="images/Validate_XML_Save_Dialog.jpg"/>
-
-<BR/>
-<P>
-No message dialogs will appear with results from the validation. Only updates to the Problems view will be done. If the resource being validated is valid, no errors will appear in the Problems view. If there are problems, new entries will be created in the view.
-</P>
-<BR/>
-
-<BR/>
-<div align="right">
- <table border="0" cellpadding="2" cellspacing="0" width="100%">
- <tbody>
- <tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font face="Arial,Helvetica"><font color="#ffffff">Locating Errors in the Resource</font></font></b></td>
- </tr>
- </tbody>
- </table>
-</div>
-<P>
-Further information explaining the cause of the validation error will appear in the Problems view (To open the Problems view, select Problems from the menu bar. Window --> Show View --> Problems). Selecting the error in the Problems view will highlight the error in the Source view allowing users to quickly locate and correct the problem. See <B>Figure 5</B>.
-</P>
-
-<BR/>
-<B>Figure 5</B>
-<BR/>
-<img border="0" src="images/Validate_XML_Problems_View.jpg"/>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/community/tutorials/XMLValidation/images/Validate_XML_Fail.jpg b/community/tutorials/XMLValidation/images/Validate_XML_Fail.jpg
deleted file mode 100644
index 2035eb8..0000000
--- a/community/tutorials/XMLValidation/images/Validate_XML_Fail.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/XMLValidation/images/Validate_XML_Menu.jpg b/community/tutorials/XMLValidation/images/Validate_XML_Menu.jpg
deleted file mode 100644
index 0c39cae..0000000
--- a/community/tutorials/XMLValidation/images/Validate_XML_Menu.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/XMLValidation/images/Validate_XML_Problems_View.jpg b/community/tutorials/XMLValidation/images/Validate_XML_Problems_View.jpg
deleted file mode 100644
index e47c4b1..0000000
--- a/community/tutorials/XMLValidation/images/Validate_XML_Problems_View.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/XMLValidation/images/Validate_XML_Save_Dialog.jpg b/community/tutorials/XMLValidation/images/Validate_XML_Save_Dialog.jpg
deleted file mode 100644
index ee781ce..0000000
--- a/community/tutorials/XMLValidation/images/Validate_XML_Save_Dialog.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/XMLValidation/images/Validate_XML_Success.jpg b/community/tutorials/XMLValidation/images/Validate_XML_Success.jpg
deleted file mode 100644
index 71008bd..0000000
--- a/community/tutorials/XMLValidation/images/Validate_XML_Success.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/XMLWizards/XMLWizards.html b/community/tutorials/XMLWizards/XMLWizards.html
deleted file mode 100644
index af9198c..0000000
--- a/community/tutorials/XMLWizards/XMLWizards.html
+++ /dev/null
@@ -1,339 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../..//default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../..//webtools/wtp.css" type="text/css">
-<title>Creating XML files Tutorial</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">Creating XML files Tutorial</font>
-<br>
-<font class="indexsub">Creating XML files Tutorial</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../..//images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>By Ella Belisario</b>
-<br>
- August 18, 2004<br>
-<br>
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- This tutorial demonstrates how you can use XML documents
- creation wizards that come with the Eclipse Web Tools
- Platform Project. These wizards allow to create XML document
- from DTD or XML Schema.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- After finishing this tutorial you will be able to do the
- following:
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<ul>
-
-<li>creating an XML file from scratch</li>
-
-<li>creating an XML file from an XML schema</li>
-
-<li>creating an XML file from a DTD</li>
-
-</ul>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Getting Started</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- In order to work with content of this tutorial you will need
- to download Web Standard Tools package from
- <a href="http://download.eclipse.org/webtools/downloads/">
- wtp downloads.
- </a>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Once you have downloaded WST and prerequisites, unzip them
- to the same folder and you are ready to go!
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Next, launch Eclipse workbench and select
- <b>
- File>New>Examples>XML>Editing and validating
- XML files
- </b>
- to bring up the wizard to create a simple project with the
- sample XML files.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Creating XML files using wizard</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../..//images/Adarrow.gif"></td><td>
- <b>Creating an XML file from scratch</b>
- </td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- To create an XML file from scratch, invoke
- <b>New XML File</b>
- wizard using workbench menu
- <b>File>New>Other>XML>XML</b>
- .
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- On the first page of the wizard select
- <b>Create XML file from scratch</b>
- option and proceed with the wizard.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../..//images/Adarrow.gif"></td><td>
- <b>Creating an XML file from DTD or XML Schema</b>
- </td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Generating an XML file from a DTD or XML Schema can be
- useful if you want to quickly create an XML file that is
- based on your gramma file.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- To create an XML file from a gramma file follow these steps:
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ol>
-
-<li>
- Invoke
- <b>New XML File</b>
- wizard using workbench menu
- <b>File>New>Other>XML>XML.</b>
-
-</li>
-
-<li>
- On the first page select depending on what type of
- gramma file you need choose
- <b>Create XML file from DTD file</b>
- or
- <b>Create XML file from an XML Schema file</b>
- radio button.
- </li>
-
-<li>
- On
- <b>XML File Name</b>
- page select a project or folder to contain the XML file
- and type a name for it. The name of the file must end in
- *.xml.
- </li>
-
-<li>
- The next choice you have to do is to select your gramma
- file. You can select it from the workspace (you can
- import files into the workspace if they are not there)
- Another possibility is to use DTD and XML files defined
- in
- <b>XML Catalog</b>
- .
- </li>
-
-<li>
- On the
- <b>Select Root Element</b>
- page select from the following content options:
- <br>
-
-<ul>
-
-<li>
- Create optional attributes - both mandatory and
- optional attributes will be generated.
- </li>
-
-<li>
- Create optional elements - both mandatory and
- optional elements will be generated.
- </li>
-
-<li>
- Create first choice of required choice - the
- first option of a required choice will be
- generated in your XML file.
- </li>
-
-<li>
- Fill elements and attributes with data - any
- elements and attributes generated will be filled
- with sample data.
- </li>
-
-</ul>
-
-<p>
- If you do not select any of these options, then only
- the minimum amount of content required for the XML
- file will be created.
- </p>
-
-</li>
-
-<li>
- The last this is to specify document type (Figure 2) for
- DTD or namespace (Figure 3) for XML Schema information.
- <p>For <b>DTD:</b>
-</p>
-
-<ul>
-
-<li>
- Specify the Public ID or System ID. You do not
- need to specify both. If you do, the Public ID
- will be used before the System ID.
- </li>
-
-</ul>
-
-<p>For <b>XML Schema:</b>
-</p>
-
-<ul>
-
-<li>
- The Namespace information section contains
- information about the target namespace of the
- XML schema, its prefix, and the schema location
- </li>
-
-</ul>
-
-</li>
-
-</ol>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><b>Figure 2: Selecting Root Element page based on DTD file:</b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><img border="0" src="images/selectRootElementDTD.png" width="522" height="609"></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><b>Figure 3: Selecting Root Element page based on XML Schema file:</b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><img border="0" src="images/selectRootElementXSD.png" width="526" height="653"></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- When wizard finished the XML file will only contain the
- selected root element and any elements or attributes
- contained in the root element. You can now add elements,
- attributes, entities, and notations to the XML file,
- however, they must follow the rules established in the DTD
- or XML Schema file that you used to create the XML file.
- </p>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/community/tutorials/XMLWizards/XMLWizards.xml b/community/tutorials/XMLWizards/XMLWizards.xml
deleted file mode 100644
index f1c1212..0000000
--- a/community/tutorials/XMLWizards/XMLWizards.xml
+++ /dev/null
@@ -1,192 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<?xml-stylesheet type="text/xsl" href="../../../wtp.xsl"?>
-<html>
- <head>
- <meta name="root" content="../../../../" />
- <title>Creating XML files Tutorial</title>
- </head>
- <body>
- <h1>Creating XML files Tutorial</h1>
- <p>
- <b>By Ella Belisario</b><br/>
- August 18, 2004<br/><br/></p>
- <p>
- This tutorial demonstrates how you can use XML documents
- creation wizards that come with the Eclipse Web Tools
- Platform Project. These wizards allow to create XML document
- from DTD or XML Schema.
- </p>
- <p>
- After finishing this tutorial you will be able to do the
- following:
- </p>
- <p>
- <ul>
- <li>creating an XML file from scratch</li>
- <li>creating an XML file from an XML schema</li>
- <li>creating an XML file from a DTD</li>
- </ul>
- </p>
- <h2>Getting Started</h2>
- <br />
- <p>
- In order to work with content of this tutorial you will need
- to download Web Standard Tools package from
- <a href="http://download.eclipse.org/webtools/downloads/">
- wtp downloads.
- </a>
- </p>
- <p>
- Once you have downloaded WST and prerequisites, unzip them
- to the same folder and you are ready to go!
- </p>
- <p>
- Next, launch Eclipse workbench and select
- <b>
- File>New>Examples>XML>Editing and validating
- XML files
- </b>
- to bring up the wizard to create a simple project with the
- sample XML files.
- </p>
-
-
- <br />
- <h2>Creating XML files using wizard</h2>
- <br />
- <h3>
- <b>Creating an XML file from scratch</b>
- </h3>
- <br />
- <p>
- To create an XML file from scratch, invoke
- <b>New XML File</b>
- wizard using workbench menu
- <b>File>New>Other>XML>XML</b>
- .
- </p>
- <p>
- On the first page of the wizard select
- <b>Create XML file from scratch</b>
- option and proceed with the wizard.
- </p>
- <br />
- <h3>
- <b>Creating an XML file from DTD or XML Schema</b>
- </h3>
- <br />
- <p>
- Generating an XML file from a DTD or XML Schema can be
- useful if you want to quickly create an XML file that is
- based on your gramma file.
- </p>
- <p>
- To create an XML file from a gramma file follow these steps:
- </p>
-
- <ol>
- <li>
- Invoke
- <b>New XML File</b>
- wizard using workbench menu
- <b>File>New>Other>XML>XML.</b>
- </li>
- <li>
- On the first page select depending on what type of
- gramma file you need choose
- <b>Create XML file from DTD file</b>
- or
- <b>Create XML file from an XML Schema file</b>
- radio button.
- </li>
- <li>
- On
- <b>XML File Name</b>
- page select a project or folder to contain the XML file
- and type a name for it. The name of the file must end in
- *.xml.
- </li>
- <li>
- The next choice you have to do is to select your gramma
- file. You can select it from the workspace (you can
- import files into the workspace if they are not there)
- Another possibility is to use DTD and XML files defined
- in
- <b>XML Catalog</b>
- .
- </li>
- <li>
- On the
- <b>Select Root Element</b>
- page select from the following content options:
- <br />
- <ul>
- <li>
- Create optional attributes - both mandatory and
- optional attributes will be generated.
- </li>
- <li>
- Create optional elements - both mandatory and
- optional elements will be generated.
- </li>
- <li>
- Create first choice of required choice - the
- first option of a required choice will be
- generated in your XML file.
- </li>
- <li>
- Fill elements and attributes with data - any
- elements and attributes generated will be filled
- with sample data.
- </li>
- </ul>
- <p>
- If you do not select any of these options, then only
- the minimum amount of content required for the XML
- file will be created.
- </p>
- </li>
- <li>
- The last this is to specify document type (Figure 2) for
- DTD or namespace (Figure 3) for XML Schema information.
- <p>For <b>DTD:</b></p>
- <ul>
- <li>
- Specify the Public ID or System ID. You do not
- need to specify both. If you do, the Public ID
- will be used before the System ID.
- </li>
- </ul>
- <p>For <b>XML Schema:</b></p>
- <ul>
- <li>
- The Namespace information section contains
- information about the target namespace of the
- XML schema, its prefix, and the schema location
- </li>
- </ul>
- </li>
- </ol>
-
- <b>Figure 2: Selecting Root Element page based on DTD file:</b>
- <br/>
- <img border="0"
- src="images/selectRootElementDTD.png" width="522"
- height="609" />
- <br/>
- <b>Figure 3: Selecting Root Element page based on XML Schema file:</b>
- <br/>
- <img border="0"
- src="images/selectRootElementXSD.png" width="526"
- height="653" />
- <p>
- When wizard finished the XML file will only contain the
- selected root element and any elements or attributes
- contained in the root element. You can now add elements,
- attributes, entities, and notations to the XML file,
- however, they must follow the rules established in the DTD
- or XML Schema file that you used to create the XML file.
- </p>
-
- </body>
-</html>
\ No newline at end of file
diff --git a/community/tutorials/XMLWizards/images/selectRootElementDTD.png b/community/tutorials/XMLWizards/images/selectRootElementDTD.png
deleted file mode 100644
index ff0db0a..0000000
--- a/community/tutorials/XMLWizards/images/selectRootElementDTD.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/XMLWizards/images/selectRootElementXSD.png b/community/tutorials/XMLWizards/images/selectRootElementXSD.png
deleted file mode 100644
index 7c5aa59..0000000
--- a/community/tutorials/XMLWizards/images/selectRootElementXSD.png
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/CMPScheduleWebApp.html b/community/tutorials/cmptutorial/CMPScheduleWebApp.html
deleted file mode 100644
index 61050ee..0000000
--- a/community/tutorials/cmptutorial/CMPScheduleWebApp.html
+++ /dev/null
@@ -1,1005 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../..//default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../..//webtools/wtp.css" type="text/css">
-<title>WTP Tutorials - Building a CMP Based School Schedule Web Application</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">WTP Tutorials - Building a CMP Based School Schedule Web Application</font>
-<br>
-<font class="indexsub">WTP Tutorials - Building a CMP Based School Schedule Web Application</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../..//images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>By Jason Sholl</b>
-<BR>
-September 11, 2005<BR>
-
-<BR>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>In this tutorial you will create a CMP based school schedule Web application. You will learn how to create a Container Managed Entity Bean to store the schedule. A Session bean will be used to interact with the CMP. A JSP and Servlet will serve as the front end. The Web portion of this tutorial was adapted from the <a href="../SchoolSchedule/BuildingAScheduleWebApp.html">Building a School Schedule Web Application</a> tutorial by Lawrence Mandel.
-<BR>
-
-
-</P>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Prerequisites For The Tutorial</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>Web Tools Platform (WTP) project<BR>The WTP project can be downloaded from <a href="http://download.eclipse.org/webtools/downloads/">http://download.eclipse.org/webtools/downloads/</a>
-<BR>
-<BR>
-</LI>
-
-<LI>Tomcat 5.0.28<BR>Tomcat is available from <a href="http://jakarta.apache.org/tomcat/" target="_top">http://jakarta.apache.org/tomcat/</a>
-<BR>
-<BR>
-</LI>
-
-<LI>JDK 1.4.2<BR>Sun's JDK is available from <a href="http://java.sun.com/j2se/1.4.2/download.html" target="_top">http://java.sun.com/j2se/1.4.2/download.html</a>
-<BR>
-<BR>
-</LI>
-
-<LI>JBoss 3.2.3<BR>JBoss is available from <a href="http://www.jboss.org/products/jbossas/downloads" target="_top">http://www.jboss.org/products/jbossas/downloads</a>
-<BR>
-<BR>
-</LI>
-
-<LI>XDoclet 1.2.3<BR>XDoclet is available from <a href="http://xdoclet.sourceforge.net/xdoclet/install.html" target="_top">http://xdoclet.sourceforge.net/xdoclet/install.html</a>
-<BR>
-<BR>
-</LI>
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Creating An EJB Project</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>The first step is to create an EJB project for the EJB Module</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>Select File -> New -> Project-> EJB -> EJB Project<BR>
-
-<IMG border="0" src="images/newejbproj.jpg" width="500" height="500"><BR>
-<BR>
-</LI>
-
-<LI>Click Next and fill in 'ScheduleEJB' for the EJB project name, expand the advanced section and fill in 'ScheduleEAR' for the EAR Application name, uncheck EJB client JAR support, and check Add Support for Annotated Java Classes<BR>
-
-<IMG border="0" src="images/newejbproj2.jpg" width="512" height="492"><BR>
-<BR>
-</LI>
-
-<LI>Click the 'New' button next to the Server Target Dropdown and then expand Generic Example and select 'Generic JBoss 3.2.3'<BR>
-
-<IMG border="0" src="images/newejbproj3.jpg" width="438" height="415"><BR>
-<BR>
-</LI>
-
-<LI>Click Next and fill in the location of your JBoss installation and click finish.<BR>
-
-<IMG border="0" src="images/newejbproj4.jpg" width="438" height="415"><BR>
-<BR>
-</LI>
-
-<LI>Now back in the EJB Project wizard, change the EJB version to 2.0 and select your newly created server target and click finish. <BR>
-
-<IMG border="0" src="images/newejbproj5.jpg" width="514" height="492"><BR>
-<BR>
-</LI>
-
-<LI>Once the wizard finishes, switch to the J2EE Perspective and see your newly created EJB Project<BR>
-
-<IMG border="0" src="images/newejbproj6.jpg" width="482" height="379"><BR>
-<BR>
-</LI>
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Creating An EJB Session Bean</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>Now you will create a Session bean in the ScheduleEJB EJB project.</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>Select File -> New -> Other-> EJB -> Enterprise Java Bean<BR>
-
-<IMG border="0" src="images/newsession.jpg" width="500" height="500"><BR>
-<BR>
-</LI>
-
-<LI>Click Next<BR>
-
-<IMG border="0" src="images/newsession2.jpg" width="500" height="500"><BR>
-<BR>
-</LI>
-
-<LI>Click the 'preferences' link to specify your annotations provider. Now, enable the builder, fill in the location of your XDoclet installation, and select its version.<BR>
-
-<IMG border="0" src="images/newsession3.jpg" width="653" height="174"><BR>
-<BR>
-</LI>
-
-<LI>Also, be sure to specify JBoss under both the EJB and Web preferences and set the versions to 3.2 and 3.2 respectively. Finally, click ok.<BR>
-
-<IMG border="0" src="images/newsession4.jpg" width="653" height="206"><BR>
-<BR>
-
-<IMG border="0" src="images/newsession5.jpg" width="658" height="197"><BR>
-<BR>
-</LI>
-
-<LI>Now back in the Session Wizard, click next. Fill in 'ejbs' for the package, 'ScheduleSessionBean' for the class name, and be sure check the box for generating annotated beans.<BR>
-
-<IMG border="0" src="images/newsession6.jpg" width="500" height="500"><BR>
-<BR>
-</LI>
-
-<LI>Click finish to create your Session bean and see it in the Project Explorer. The annotations builder should have run and generated local and remote, and local and remote home interfaces.<BR>
-
-<IMG border="0" src="images/newsession7.jpg" width="960" height="640"><BR>
-<BR>
-</LI>
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>It is important to remember when developing EJBs using XDoclet to only edit the actual bean classes (e.g. ejbs.ScheduleSessionBean). All deployment descriptor metadata, as well as the various EJB interfaces are generated using the XDoclet javadoc tags. If you open ScheduleSessionBean, you can see some of these tags. Full documentation on how to use these tags can be found in the XDoclet docs.</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><IMG border="0" src="images/newsession8.jpg" width="651" height="838"></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Creating A CMP Bean</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>At the time of this writing, there is no tooling support Entity beans. Entity beans may be created, however, using JDT tools and XDoclet tags.</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>Select File -> New -> Other-> Java -> Class -> And fill in the following information: Package: ejbs, Name: ScheduleItemBean, Superclass: java.lang.Object, Modifiers: public and abstract, Interfaces: javax.ejb.EntityBean. Then click finish.<BR>
-
-<IMG border="0" src="images/newcmp.jpg" width="495" height="599"><BR>
-<BR>
-</LI>
-
-<LI>Now, open ejb.ScheduleItemBean.java in the Java editor. XDoclet tags need to be added in order for XDoclet to properly generate all the necessary code and ejb meta data. Start by adding the following javadoc to the bean class itself (right above the line: public abstract class ScheduleItemBean). This code specifies that this bean is a CMP, should only have local interface, defines the interfaces names, and specifies that the primary key is type java.lang.Integer and is handled by field 'id'.<BR>
-<BR>
-
-<pre id="code">
-/**
- * Bean implementation class for Entity Bean: ScheduleItem
- *
- * @ejb.bean name="ScheduleItem" type="CMP" cmp-version="2.x"
- * schema="ScheduleItem"
- * local-jndi-name="ejb/ejbs/ScheduleItemLocalHome" view-type="local"
- * reentrant="true" primkey-field="id"
- *
- * @ejb.home local-class="ejbs.ScheduleItemLocalHome"
- *
- * @ejb.interface local-class="ejbs.ScheduleItemLocal"
- *
- * @ejb.pk class="java.lang.Integer"
- */
-</pre>
-</LI>
-
-<LI>Now add the necessary getters/setters and XDoclet tags for the primary key.<BR>
-<BR>
-
-<pre id="code">
- /**
- * @ejb.persistence read-only="false"
- * @ejb.interface-method view-type="local"
- */
- public abstract Integer getId();
-
- /**
- * @ejb.persistence
- */
- public abstract void setId(Integer id);
-</pre>
-</LI>
-
-<LI>At this point, if you save ScheduleItemBean, the XDoclet builder should run cleanly.<BR>
-
-<IMG border="0" src="images/newcmp2.jpg" width="291" height="433"><BR>
-<BR>
-</LI>
-
-<LI>Now, to add a few more CMP attributes to ScheduleItem bean, add getters/setters and XDoclet tags<BR>
-
-<pre id="code">
- /**
- * @ejb.persistence read-only="false"
- * @ejb.interface-method view-type="local"
- */
- public abstract java.lang.String getName();
-
- /**
- * @ejb.persistence
- * @ejb.interface-method view-type="local"
- */
- public abstract void setName(java.lang.String newName);
-
- /**
- * @ejb.persistence read-only="false"
- * @ejb.interface-method view-type="local"
- */
- public abstract int getStartTime();
-
- /**
- * @ejb.persistence
- * @ejb.interface-method view-type="local"
- */
- public abstract void setStartTime(int newStartTime);
-
- /**
- * @ejb.persistence read-only="false"
- * @ejb.interface-method view-type="local"
- */
- public abstract int getEndTime();
-
- /**
- * @ejb.persistence
- * @ejb.interface-method view-type="local"
- */
- public abstract void setEndTime(int newEndTime);
-
- /**
- * @ejb.persistence read-only="false"
- * @ejb.interface-method view-type="local"
- */
- public abstract int getDay();
-
- /**
- * @ejb.persistence
- * @ejb.interface-method view-type="local"
- */
- public abstract void setDay(int newDay);
-
- /**
- * @ejb.persistence read-only="false"
- * @ejb.interface-method view-type="local"
- */
- public abstract java.lang.String getScheduleID();
-
- /**
- * @ejb.persistence
- * @ejb.interface-method view-type="local"
- */
- public abstract void setScheduleID(java.lang.String newScheduleID);
-</pre>
-</LI>
-
-<LI>Next is to add a means by which to create ScheduleItemBean. The create method will take the Name for the new ScheduleItem and autogenerate a new key. The rudimentry key generation code is for example purposes only. After you paste the code below, do an organized imports (Control-Shift-o) to add an import for CreateException.<BR>
-
-<pre id="code">
-private static int PRIMKEY = (int) System.currentTimeMillis();
-
- /**
- * ejbCreate
- *
- * @ejb.create-method view-type="local"
- */
- public java.lang.Integer ejbCreate(java.lang.String name)
- throws CreateException {
- setId(new Integer(PRIMKEY++));
- setName(name);
- return null;
- }
-
- /**
- * ejbPostCreate
- */
- public void ejbPostCreate(java.lang.String name) throws CreateException {
- }
-</pre>
-</LI>
-
-<LI>The last step is to add a few finder definitions. These should be added to the class level javadoc (right below the @ejb.pk class definition added before).<BR>
-
-<pre id="code">
- * @ejb.finder signature="java.util.Collection findAll()" query="select
- * object(o) from ScheduleItem o"
- *
- * @ejb.finder signature="java.util.Collection findByScheduleID(java.lang.String
- * scheduleID)" query="select object(o) from ScheduleItem o where
- * o.scheduleID = (?1)"
- *
- * @ejb.finder signature="java.util.Collection findByName(java.lang.String
- * name)" query="select object(o) from ScheduleItem o where o.name =
- * (?1)"
-</pre>
-</LI>
-
-<LI>At this point if you save and build, you should be abloe to open ScheduleItemLocal and ScheduleItemLocalHome and see all method stubs were appropriatly generated. Do not edit these files. Once you are done inspecting them, close them both.<BR>
-
-<IMG border="0" src="images/newcmp3.jpg" width="688" height="663"><BR>
-<BR>
-
-<IMG border="0" src="images/newcmp4.jpg" width="686" height="658"><BR>
-<BR>
-</LI>
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Adding purpose to ScheduleSessionBean</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>If ScheduleSessionBean is not open, open it in the JavaEditor. The first thing we need to do is add a local reference from the ScheduleSessionBean to the ScheduleItemLocal. This requires the following XDoclet tag at the class level (put this right below the * @ejb.bean name="ScheduleSession" block). The second tag which starts with @jboss.ejb-local-ref is a JBoss specific XDoclet tag used to setup the JNDI name; other vendors also have their own specific tags where needed.<BR>
-
-<pre id="code">
- * @ejb.ejb-ref ejb-name="ScheduleItem" view-type="local"
- *
- * @jboss.ejb-local-ref ref-name="ScheduleItemLocal"
- * jndi-name="ejb/ejbs/ScheduleItemLocalHome"
- *
-</pre>
-</LI>
-
-
-<LI>Since ScheduleSessionBean will be used by the forthcoming web client instead of ScheduleItemBean, it is necessary to add a few methods to access ScheduleItems. The below code supplies a way for clients to create new ScheduleItems, and find existing ones using the finders we specified previously. Note that ScheduleItems beans are not returned directly, but, rather their data is wrapped up in a ScheduleItemWrapper. The ScheduleItemWrapper will be created in the next step. Delete the existing 'foo' method and add the following methods to ScheduleSessionBean. You will have several compile errors which can be fixed using organized imports (Control-Shift-o); just be sure you select the correct types if there are multiple choices (javax.naming.Context, javax.rmi.PortableRemoteObject, ,java.util.List, java.util.Iterator) <BR>
-
-<pre id="code">
- /**
- * @ejb.interface-method view-type="both"
- */
- public ScheduleItemWrapper addScheduleItem(String name, int startTime,
- int endTime, int day, String scheduleID) {
- ScheduleItemLocalHome home = getScheduleItemLocalHome();
- try {
- ScheduleItemLocal scheduleItem = home.create(name);
- scheduleItem.setStartTime(startTime);
- scheduleItem.setEndTime(endTime);
- scheduleItem.setDay(day);
- scheduleItem.setScheduleID(scheduleID);
- return new ScheduleItemWrapper(name, startTime, endTime, day,
- scheduleID);
- } catch (CreateException e) {
- // TODO Auto-generated catch block
- e.printStackTrace();
- }
- return null;
- }
-
- /**
- * @ejb.interface-method view-type="both"
- */
- public List getScheduleItem(String name) {
- ScheduleItemLocalHome home = getScheduleItemLocalHome();
- try {
- Collection items = home.findByName(name);
- return wrapScheduleItemsInList(items);
- } catch (FinderException e) {
- // TODO Auto-generated catch block
- e.printStackTrace();
- }
- return null;
- }
-
- /**
- * @ejb.interface-method view-type="both"
- */
- public List getAllScheduleItems() {
- ScheduleItemLocalHome home = getScheduleItemLocalHome();
- try {
- Collection items = home.findAll();
- return wrapScheduleItemsInList(items);
- } catch (FinderException e) {
- // TODO Auto-generated catch block
- e.printStackTrace();
- }
- return null;
- }
-
- /**
- * @ejb.interface-method view-type="both"
- */
- public List getScheduleItemesForScheduleID(String scheduleID) {
- ScheduleItemLocalHome home = getScheduleItemLocalHome();
- try {
- Collection items = home.findByScheduleID(scheduleID);
- return wrapScheduleItemsInList(items);
- } catch (FinderException e) {
- // TODO Auto-generated catch block
- e.printStackTrace();
- }
- return null;
- }
-
- private List wrapScheduleItemsInList(Collection items) {
- Iterator iterator = items.iterator();
- List list = new ArrayList(items.size());
- while (iterator.hasNext()) {
- ScheduleItemLocal scheduleItem = (ScheduleItemLocal) iterator
- .next();
- ScheduleItemWrapper wrapper = new ScheduleItemWrapper(scheduleItem
- .getName(), scheduleItem.getStartTime(), scheduleItem
- .getEndTime(), scheduleItem.getDay(), scheduleItem
- .getScheduleID());
- list.add(wrapper);
- }
- return list;
- }
-
- private ScheduleItemLocalHome getScheduleItemLocalHome() {
- try {
- Context context = new InitialContext();
- Object obj = context.lookup("java:comp/env/ejb/ScheduleItemLocal");
- ScheduleItemLocalHome home = (ScheduleItemLocalHome) PortableRemoteObject
- .narrow(obj, ScheduleItemLocalHome.class);
- return home;
- } catch (NamingException e) {
- // TODO Auto-generated catch block
- e.printStackTrace();
- }
- return null;
- }
-</pre>
-</LI>
-
-<LI>Next, ScheduleItemWrapper needs to be created. Create a new JavaClass called ScheduleItemWrapper in the ejbs package. Be sure to add the java.io.Serializable interface.<BR>
-
-<IMG border="0" src="images/wrapper.jpg" width="495" height="599"><BR>
-<BR>
-</LI>
-
-<LI>Next, open ScheduleItemWrapper in the Java editor and add the following fields.<BR>
-
-<pre id="code">
- public java.lang.String name;
-
- public int starttime;
-
- public int endtime;
-
- public int day;
-
- public java.lang.String scheduleId;
- </pre>
-</LI>
-
-<LI>Right click on ScheduleItemWrapper in the source editor and select Source -> Generate Getters and Setters. Generate a getter and setter for each field.<BR>
-
-<IMG border="0" src="images/wrapper2.jpg" width="630" height="630"><BR>
-<BR>
-
-<IMG border="0" src="images/wrapper3.jpg" width="480" height="601"><BR>
-<BR>
-</LI>
-
-<LI>Finally, add the following constructor.<BR>
-
-<pre id="code">
- public ScheduleItemWrapper(java.lang.String name, int starttime,
- int endtime, int day, java.lang.String scheduleId) {
- this.name = name;
- this.starttime = starttime;
- this.endtime = endtime;
- this.day = day;
- this.scheduleId = scheduleId;
- }
- </pre>
-</LI>
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Building a Web Client</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>The first step is to create a Web project.</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>Select File -> New -> Project -> Web -> Dynamic Web Project<BR>
-
-<IMG border="0" src="images/newwebproj1.jpg" width="500" height="500"><BR>
-<BR>
-</LI>
-
-<LI>Click Next and fill in 'ScheduleWeb' for the Web project name, expand the advanced section and select '2.3' for the module version, 'Generic JBoss 3.2.3' for server target, 'ScheduleEAR' for the EAR Application name, and check Add Support for annotated Java classes. Click finish.<BR>
-
-<IMG border="0" src="images/newwebproj2.jpg" width="514" height="495"><BR>
-<BR>
-</LI>
-
-<LI>Expand the 'Dynamic Web Projects' node in the project explorer, and right click on ScheduleWeb and select 'Properties'.<BR>
-
-<IMG border="0" src="images/newwebproj3.jpg" width="361" height="529"><BR>
-<BR>
-</LI>
-
-<LI>Select the 'Java JAR Dependencies' properties page, and then click the checkbox next to 'ScheduleEJB.jar' to add a module dependency to the EJB module.<BR>
-
-<IMG border="0" src="images/newwebproj4.jpg" width="619" height="562"><BR>
-<BR>
-</LI>
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Creating a Servlet</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>Now you will create a servlet which calls the ScheduleSessionBean.</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>Select File -> New -> Other -> WEB -> Servlet and then click next. Fill in 'servlets' for the package, and 'ServletExample' for the Classname. Check 'Generate an annotated servlet class' and then click finish.<BR>
-
-<IMG border="0" src="images/newservlet1.jpg" width="500" height="500"><BR>
-<BR>
-</LI>
-
-<LI>Similar to the EJB reference from ScheduleSessionBean to ScheduleItemLocal, we are going to create a reference from ScheduleExample to ScheduleSessionLocal by entering the following XDoclet tags to the class level JavaDoc (right below the @web.servlet-mapping line in ScheduleExample).<BR>
-
-<pre id="code">
- * @web.ejb-local-ref home="ejbs.ScheduleSessionLocalHome"
- * local="ejbs.ScheduleSessionLocal"
- * name="ejb/ScheduleSession" type="Session"
- * link="ScheduleSession"
- *
- * @jboss.ejb-local-ref ref-name="ScheduleSession"
- * jndi-name="ejb/ejbs/ScheduleSessionHome"
- </pre>
-</LI>
-
-<LI>Next, add the following methods to ScheduleExample to access ScheduleSessionBean. An organize imports will clean up the compile errors. Be sure to select the correct types (javax.nameing.Context and javax.rmi.PortableRemoteObject).<BR>
-
-<pre id="code">
- private ScheduleSessionLocalHome scheduleSessionLocalHome;
-
- private ScheduleSessionLocal getScheduleSession() {
- if (null == scheduleSessionLocalHome) {
- try {
- Context context = new InitialContext();
- Object obj = context
- .lookup("java:comp/env/ejb/ScheduleSession");
- scheduleSessionLocalHome = (ScheduleSessionLocalHome) PortableRemoteObject
- .narrow(obj, ScheduleSessionLocalHome.class);
- } catch (NamingException e) {
- // TODO Auto-generated catch block
- e.printStackTrace();
- }
- }
- try {
- return scheduleSessionLocalHome.create();
- } catch (CreateException e) {
- // TODO Auto-generated catch block
- e.printStackTrace();
- }
- return null;
- }
- </pre>
-</LI>
-
-<LI>Next, fill the currently empty implementation of doPost() with the following code. An organize imports (select java.util.List) will clean up most of the errors.<BR>
-
-<pre id="code">
- response.setContentType("text/plain");
- PrintWriter out = response.getWriter();
-
- ScheduleSessionLocal scheduleSession = getScheduleSession();
-
- String scheduleid = request.getParameter("multidayscheduleid");
- if (scheduleid != null) {
- String title = request.getParameter("title");
- int starttime = Integer.parseInt(request.getParameter("starttime"));
- int endtime = Integer.parseInt(request.getParameter("endtime"));
- String[] days = request.getParameterValues("day");
-
- if (days != null) {
- for (int i = 0; i < days.length; i++) {
- String dayString = days[i];
- int day;
- if (dayString.equalsIgnoreCase("SUN"))
- day = 0;
- else if (dayString.equalsIgnoreCase("MON"))
- day = 1;
- else if (dayString.equalsIgnoreCase("TUE"))
- day = 2;
- else if (dayString.equalsIgnoreCase("WED"))
- day = 3;
- else if (dayString.equalsIgnoreCase("THU"))
- day = 4;
- else if (dayString.equalsIgnoreCase("FRI"))
- day = 5;
- else
- day = 6;
-
- scheduleSession.addScheduleItem(title, starttime, endtime,
- day, scheduleid);
- }
- request.getSession().setAttribute(
- "schoolschedule",
- scheduleSession
- .getScheduleItemesForScheduleID(scheduleid));
- getServletContext().getRequestDispatcher("/TestSchedule.jsp")
- .forward(request, response);
- }
- }
-
- String name = request.getParameter("nameGet");
- if (name != null) {
- List items = scheduleSession.getScheduleItem(name);
- out.println("Schedule Item retrieved:");
- printTable(out, items);
- return;
- }
- String scheduleID = request.getParameter("scheduleID");
- if (scheduleID != null) {
- List items = scheduleSession
- .getScheduleItemesForScheduleID(scheduleID);
- out.println("ScheduleIDs matching " + scheduleID + ":");
- printTable(out, items);
- return;
- }
- List items = scheduleSession.getAllScheduleItems();
- out.println("All Schedule Items:");
- printTable(out, items);
- return;
- </pre>
-</LI>
-
-<LI>Lastly, add the missing printTable() method and perform an organized imports.<BR>
-
-<pre id="code">
- private void printTable(PrintWriter out, List items) {
- out.println("<TABLE border=\"1\" cellspacing=\"0\"><TBODY><TR>");
- out.println("<TH align=\"center\" valign=\"middle\">Name</TH>");
- out.println("<TH align=\"center\" valign=\"middle\">StartTime</TH>");
- out.println("<TH align=\"center\" valign=\"middle\">EndTime</TH>");
- out.println("<TH align=\"center\" valign=\"middle\">Day</TH>");
- out.println("<TH align=\"center\" valign=\"middle\">ScheduleID</TH></TR>");
- for (int i = 0; i < items.size(); i++) {
- ScheduleItemWrapper item = (ScheduleItemWrapper) items.get(i);
- out.println("<TR>");
- out.println("<TD>" + item.getName() + "</TD>");
- out.println("<TD>" + item.getStarttime() + "</TD>");
- out.println("<TD>" + item.getEndtime() + "</TD>");
- out.println("<TD>" + item.getDay() + "</TD>");
- out.println("<TD>" + item.getScheduleId() + "</TD>");
- out.println("</TR>");
- }
- out.println("</TBODY></TABLE>");
- }
- </pre>
-</LI>
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Creating A JSP</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>This is the final piece of this example schedule application, and works with ServletExample created above to provide a user interface.</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>Select File -> New -> Other-> Web -> JSP and click next. Select the WebContent directory under ScheduleWeb, and fill in TestSchedule.jsp for the file name. Click finish.<BR>
-
-<IMG border="0" src="images/newjsp1.jpg" width="500" height="578"><BR>
-<BR>
-</LI>
-
-<LI>Open TestSchedule.jsp with the JSP Editor and add a meaninggul title where it says 'Insert title here', e.g. 'Schedule Example'.<BR>
-</LI>
-
-<LI>In order to use the standard tag libraries you will first have to download and install them into our project. Open your Web browser to <A HREF="http://jakarta.apache.org/taglibs/">http://jakarta.apache.org/taglibs/</A>. Under JCP Standardized Tag Libraries on the left select Standar-1.1:JSTL 1.0(2.0) (Be sure you select 1.0 and not 1.1!). Scroll down to the Download section and select the first link, Download the Standard Tag Library Release from an Apache Jakara Project Mirror. Select Taglibs and then Library Releases. Select standard and then select to download
- jakarta-taglibs-standard-current.zip. Once the zip file download, open it and extract jstl.jar and standard.jar into the WebContent/WEB-INF/lib folder in your project. Select your project, right click on it and select Refresh. The libraries are automatically added to your Java classpath. There is currently a bug which hids the contents of the lib directory in the Project Explorer view, but if you switch to the Navigator view, your project should look like this:<BR>
-
-<IMG border="0" src="images/newjsp2.jpg" width="233" height="358"><BR>
-<BR>
-</LI>
-
-<LI>In order to use the tag libraries you have just downloaded you will have to declare them in your JSP. At the top of the JSP file (right above <!DOCTYPE HTML) add in the following line
- <pre id="code">
- <%@taglib uri="http://java.sun.com/jstl/core" prefix="c"%>
- </pre>
-
-<IMG border="0" src="images/newjsp3.jpg" width="631" height="320"><BR>
-<BR>
-</LI>
-
-<LI>Finally, add the following code to within the body tags:<BR>
-
-
-<pre id="code">
-<FORM action="/ScheduleWeb/ScheduleExample" method="post">Schedule<INPUT
- type="text" name="multidayscheduleid" size="35"><BR>
-Course Name: <INPUT type="text" name="title" size="35"><BR>
-Course Time: Sun<INPUT type="checkbox" name="day" value="sun"> Mon<INPUT
- type="checkbox" name="day" value="mon"> Tue<INPUT type="checkbox"
- name="day" value="tue"> Wed<INPUT type="checkbox" name="day"
- value="wed"> Thu<INPUT type="checkbox" name="day" value="thu"> Fri<INPUT
- type="checkbox" name="day" value="fri"> Sat<INPUT type="checkbox"
- name="day" value="sat"> <SELECT name="starttime">
- <OPTION value="8">8:00am</OPTION>
- <OPTION value="9">9:00am</OPTION>
- <OPTION value="10">10:00am</OPTION>
- <OPTION value="11">11:00am</OPTION>
- <OPTION value="12">12:00pm</OPTION>
- <OPTION value="13">1:00pm</OPTION>
- <OPTION value="14">2:00pm</OPTION>
- <OPTION value="15">3:00pm</OPTION>
- <OPTION value="16">4:00pm</OPTION>
- <OPTION value="17">5:00pm</OPTION>
- <OPTION value="18">6:00pm</OPTION>
- <OPTION value="19">7:00pm</OPTION>
- <OPTION value="20">8:00pm</OPTION>
- <OPTION value="21">9:00pm</OPTION>
-</SELECT> to <SELECT name="endtime">
- <OPTION value="9">9:00am</OPTION>
- <OPTION value="10">10:00am</OPTION>
- <OPTION value="11">11:00am</OPTION>
- <OPTION value="12">12:00pm</OPTION>
- <OPTION value="13">1:00pm</OPTION>
- <OPTION value="14">2:00pm</OPTION>
- <OPTION value="15">3:00pm</OPTION>
- <OPTION value="16">4:00pm</OPTION>
- <OPTION value="17">5:00pm</OPTION>
- <OPTION value="18">6:00pm</OPTION>
- <OPTION value="19">7:00pm</OPTION>
- <OPTION value="20">8:00pm</OPTION>
- <OPTION value="21">9:00pm</OPTION>
- <OPTION value="22">10:00pm</OPTION>
-</SELECT> <BR>
-<BR>
-<INPUT type="submit" name="Submit" value="AddCourse"></FORM>
-
-<TABLE border="1" cellspacing="0">
- <TBODY>
- <TR>
- <TH align="center" valign="middle" width="80"></TH>
- <TH align="center" valign="middle" width="100">Sunday</TH>
- <TH align="center" valign="middle">Monday</TH>
- <TH align="center" valign="middle">Tuesday</TH>
- <TH align="center" valign="middle">Wednesday</TH>
- <TH align="center" valign="middle">Thursday</TH>
- <TH align="center" valign="middle">Friday</TH>
- <TH align="center" valign="middle">Saturday</TH>
- </TR>
- <c:forEach begin="8" end="21" step="1" var="time">
- <TR>
- <TD align="center" valign="middle" width="80"><c:choose>
- <c:when test="${time == 12}">
- <c:out value="${time}" />:00pm
-</c:when>
- <c:when test="${time > 12}">
- <c:out value="${time - 12}" />:00pm
-</c:when>
- <c:otherwise>
- <c:out value="${time}" />:00am
-</c:otherwise>
- </c:choose></TD>
- <c:forEach begin="0" end="6" step="1" var="day">
- <TD align="center" valign="middle" width="100"><c:forEach
- items="${schoolschedule}" var="clazz">
- <c:if
- test="${clazz.starttime <= time
-&& clazz.endtime > time
-&& clazz.day == day}">
- <c:out value="${clazz.name}" />
- </c:if>
- </c:forEach></TD>
- </c:forEach>
- </TR>
- </c:forEach>
- </TBODY>
-</TABLE>
-
-<FORM method="post" action="/ScheduleWeb/ScheduleExample">Schedule:<INPUT
- type="text" name="scheduleID" size="20"><br>
-<INPUT type="submit" value="Get Schedule"></FORM>
-
-
-<FORM method="post" action="/ScheduleWeb/ScheduleExample">Course Name:<INPUT
- type="text" name="nameGet" size="20"><br>
-<INPUT type="submit" value="Find Schedules"></FORM>
-
-
-<FORM method="post" action="/ScheduleWeb/ScheduleExample"><INPUT
- type="submit" value="Get All Schedules"></FORM>
- </pre>
-</LI>
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Running And Testing The School Schedule Web Application</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>Your school schedule application is now complete. Now it is time to take it for a spin.</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>Right click on the servers view and select New -> Server.<BR>
-<BR>
-
-<IMG border="0" src="images/run1.jpg" width="619" height="200"><BR>
-<BR>
-</LI>
-
-<LI>Select 'Generic JBoss 3.2.3' under Generic Examples and click Finish.<BR>
-<BR>
-
-<IMG border="0" src="images/run2.jpg" width="500" height="538"><BR>
-<BR>
-</LI>
-
-<LI>Right click on the newly created server in the Servers view and select run. Wait a few seconds to ensure the server started up correctly. The Console view should look something like this:<BR>
-<BR>
-
-<IMG border="0" src="images/run3.jpg" width="1079" height="299"><BR>
-<BR>
-</LI>
-
-<LI>Flip back to the servers view. Right click on the new running server and select 'Add and Remove Projects...' which will bring up the dialog below. Select ScheduleEAR from the left panel and click 'Add >' to add it to the right panel as shown below. Click Finish.<BR>
-<BR>
-
-<IMG border="0" src="images/run4.jpg" width="500" height="485"><BR>
-<BR>
-</LI>
-
-<LI>Wait a few more seconds while the project is added to the server and started. Once it is finished, the Console view should look like this:<BR>
-<BR>
-
-<IMG border="0" src="images/run5.jpg" width="1085" height="313"><BR>
-<BR>
-</LI>
-
-<LI>Now, back in the Project Explorer right click on 'TestSchedule.jsp' and select 'Run As' -> 'Run on Server'. This will bring up the below dialog. Click Finish.<BR>
-<BR>
-
-<IMG border="0" src="images/run6.jpg" width="500" height="627"><BR>
-<BR>
-</LI>
-
-<LI>An embedded web browser should open showing the following page.<BR>
-<BR>
-
-<IMG border="0" src="images/run7.jpg" width="836" height="751"><BR>
-<BR>
-</LI>
-
-<LI>The 'Schedule' field (backed by scheduleID in the CMP) differentiates one schedule from another (e.g. John's schedule from Mary's schedule). Hopefully, the rest is straight forward enough.<BR>
-<BR>
- The fields below the calendar use the various finder methods we defined on th CMP. Below are a few examples. The first is after a few courses were added to 'John's Schedule'<BR>
-<BR>
-
-<IMG border="0" src="images/run8.jpg" width="836" height="753"><BR>
-<BR>
-</LI>
-
-<LI>Next is the result of clicking 'Get Schedule' for 'John's Schedule'<BR>
-<BR>
-
-<IMG border="0" src="images/run9.jpg" width="399" height="303"><BR>
-<BR>
-</LI>
-
-<LI>Next is the result of clicking 'Find Schedules' for 'Math'<BR>
-<BR>
-
-<IMG border="0" src="images/run10.jpg" width="384" height="276"><BR>
-<BR>
-</LI>
-
-<LI>Finally, here is the result of clicking 'Get All Schedules'.<BR>
-<BR>
-
-<IMG border="0" src="images/run11.jpg" width="452" height="424"><BR>
-<BR>
-</LI>
-
-<LI>Experiment adding more courses into your schedule.</LI>
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Summary</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>In this tutorial you learned how to configure Eclipse to work with JBoss and create J2EE EJB and Web projects that uses a CMP Bean, a Session Bean, a servlet, and a JSP to create a student class schedule J2EE Web application. This application, while simple, provides a good introduction to Java Web development and some of the Web development tools available in the Eclipse Web Tools Platform project.</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P></P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>
-
-</P>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/community/tutorials/cmptutorial/CMPScheduleWebApp.xml b/community/tutorials/cmptutorial/CMPScheduleWebApp.xml
deleted file mode 100644
index d452453..0000000
--- a/community/tutorials/cmptutorial/CMPScheduleWebApp.xml
+++ /dev/null
@@ -1,634 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<?xml-stylesheet type="text/xsl" href="../../../wtp.xsl"?>
-<html>
-<head>
- <meta name="root" content="../../../../" />
- <title>WTP Tutorials - Building a CMP Based School Schedule Web Application</title>
-</head>
-
-<body>
-<h1>WTP Tutorials - Building a CMP Based School Schedule Web Application</h1>
-<p>
-<b>By Jason Sholl</b><BR/>
-September 11, 2005<BR/>
-<BR/>
-</p>
-<P>In this tutorial you will create a CMP based school schedule Web application. You will learn how to create a Container Managed Entity Bean to store the schedule. A Session bean will be used to interact with the CMP. A JSP and Servlet will serve as the front end. The Web portion of this tutorial was adapted from the <a href="../SchoolSchedule/BuildingAScheduleWebApp.html">Building a School Schedule Web Application</a> tutorial by Lawrence Mandel.
-<BR/>
-
-</P>
-<h2>Prerequisites For The Tutorial</h2>
-<OL>
- <LI>Web Tools Platform (WTP) project<BR/>The WTP project can be downloaded from <a href="http://download.eclipse.org/webtools/downloads/">http://download.eclipse.org/webtools/downloads/</a><BR/><BR/></LI>
- <LI>Tomcat 5.0.28<BR/>Tomcat is available from <a href="http://jakarta.apache.org/tomcat/" target="_top">http://jakarta.apache.org/tomcat/</a><BR/><BR/></LI>
- <LI>JDK 1.4.2<BR/>Sun's JDK is available from <a href="http://java.sun.com/j2se/1.4.2/download.html" target="_top">http://java.sun.com/j2se/1.4.2/download.html</a><BR/><BR/></LI>
- <LI>JBoss 3.2.3<BR/>JBoss is available from <a href="http://www.jboss.org/products/jbossas/downloads" target="_top">http://www.jboss.org/products/jbossas/downloads</a><BR/><BR/></LI>
- <LI>XDoclet 1.2.3<BR/>XDoclet is available from <a href="http://xdoclet.sourceforge.net/xdoclet/install.html" target="_top">http://xdoclet.sourceforge.net/xdoclet/install.html</a><BR/><BR/></LI>
-</OL>
-
-<h2>Creating An EJB Project</h2>
-<P>The first step is to create an EJB project for the EJB Module</P>
-<OL>
- <LI>Select File -> New -> Project-> EJB -> EJB Project<BR/>
- <IMG border="0" src="images/newejbproj.jpg" width="500" height="500"/><BR/><BR/></LI>
- <LI>Click Next and fill in 'ScheduleEJB' for the EJB project name, expand the advanced section and fill in 'ScheduleEAR' for the EAR Application name, uncheck EJB client JAR support, and check Add Support for Annotated Java Classes<BR/>
- <IMG border="0" src="images/newejbproj2.jpg" width="512" height="492"/><BR/><BR/></LI>
- <LI>Click the 'New' button next to the Server Target Dropdown and then expand Generic Example and select 'Generic JBoss 3.2.3'<BR/>
- <IMG border="0" src="images/newejbproj3.jpg" width="438" height="415"/><BR/><BR/></LI>
- <LI>Click Next and fill in the location of your JBoss installation and click finish.<BR/>
- <IMG border="0" src="images/newejbproj4.jpg" width="438" height="415"/><BR/><BR/></LI>
- <LI>Now back in the EJB Project wizard, change the EJB version to 2.0 and select your newly created server target and click finish. <BR/>
- <IMG border="0" src="images/newejbproj5.jpg" width="514" height="492"/><BR/><BR/></LI>
- <LI>Once the wizard finishes, switch to the J2EE Perspective and see your newly created EJB Project<BR/>
- <IMG border="0" src="images/newejbproj6.jpg" width="482" height="379"/><BR/><BR/></LI>
-</OL>
-<h2>Creating An EJB Session Bean</h2>
-<P>Now you will create a Session bean in the ScheduleEJB EJB project.</P>
-<OL>
- <LI>Select File -> New -> Other-> EJB -> Enterprise Java Bean<BR/>
- <IMG border="0" src="images/newsession.jpg" width="500" height="500"/><BR/><BR/></LI>
- <LI>Click Next<BR/>
- <IMG border="0" src="images/newsession2.jpg" width="500" height="500"/><BR/><BR/></LI>
- <LI>Click the 'preferences' link to specify your annotations provider. Now, enable the builder, fill in the location of your XDoclet installation, and select its version.<BR/>
- <IMG border="0" src="images/newsession3.jpg" width="653" height="174"/><BR/><BR/></LI>
- <LI>Also, be sure to specify JBoss under both the EJB and Web preferences and set the versions to 3.2 and 3.2 respectively. Finally, click ok.<BR/>
- <IMG border="0" src="images/newsession4.jpg" width="653" height="206"/><BR/><BR/>
- <IMG border="0" src="images/newsession5.jpg" width="658" height="197"/><BR/><BR/></LI>
- <LI>Now back in the Session Wizard, click next. Fill in 'ejbs' for the package, 'ScheduleSessionBean' for the class name, and be sure check the box for generating annotated beans.<BR/>
- <IMG border="0" src="images/newsession6.jpg" width="500" height="500"/><BR/><BR/></LI>
- <LI>Click finish to create your Session bean and see it in the Project Explorer. The annotations builder should have run and generated local and remote, and local and remote home interfaces.<BR/>
- <IMG border="0" src="images/newsession7.jpg" width="960" height="640"/><BR/><BR/></LI>
-</OL>
-<P>It is important to remember when developing EJBs using XDoclet to only edit the actual bean classes (e.g. ejbs.ScheduleSessionBean). All deployment descriptor metadata, as well as the various EJB interfaces are generated using the XDoclet javadoc tags. If you open ScheduleSessionBean, you can see some of these tags. Full documentation on how to use these tags can be found in the XDoclet docs.</P>
- <IMG border="0" src="images/newsession8.jpg" width="651" height="838"/><BR/><BR/>
-
-<h2>Creating A CMP Bean</h2>
-<P>At the time of this writing, there is no tooling support Entity beans. Entity beans may be created, however, using JDT tools and XDoclet tags.</P>
-<OL>
- <LI>Select File -> New -> Other-> Java -> Class -> And fill in the following information: Package: ejbs, Name: ScheduleItemBean, Superclass: java.lang.Object, Modifiers: public and abstract, Interfaces: javax.ejb.EntityBean. Then click finish.<BR/>
- <IMG border="0" src="images/newcmp.jpg" width="495" height="599"/><BR/><BR/></LI>
- <LI>Now, open ejb.ScheduleItemBean.java in the Java editor. XDoclet tags need to be added in order for XDoclet to properly generate all the necessary code and ejb meta data. Start by adding the following javadoc to the bean class itself (right above the line: public abstract class ScheduleItemBean). This code specifies that this bean is a CMP, should only have local interface, defines the interfaces names, and specifies that the primary key is type java.lang.Integer and is handled by field 'id'.<BR/><BR/>
-<pre id="code">
-/**
- * Bean implementation class for Entity Bean: ScheduleItem
- *
- * @ejb.bean name="ScheduleItem" type="CMP" cmp-version="2.x"
- * schema="ScheduleItem"
- * local-jndi-name="ejb/ejbs/ScheduleItemLocalHome" view-type="local"
- * reentrant="true" primkey-field="id"
- *
- * @ejb.home local-class="ejbs.ScheduleItemLocalHome"
- *
- * @ejb.interface local-class="ejbs.ScheduleItemLocal"
- *
- * @ejb.pk class="java.lang.Integer"
- */
-</pre></LI>
- <LI>Now add the necessary getters/setters and XDoclet tags for the primary key.<BR/><BR/>
-<pre id="code">
- /**
- * @ejb.persistence read-only="false"
- * @ejb.interface-method view-type="local"
- */
- public abstract Integer getId();
-
- /**
- * @ejb.persistence
- */
- public abstract void setId(Integer id);
-</pre></LI>
- <LI>At this point, if you save ScheduleItemBean, the XDoclet builder should run cleanly.<BR/>
- <IMG border="0" src="images/newcmp2.jpg" width="291" height="433"/><BR/><BR/></LI>
- <LI>Now, to add a few more CMP attributes to ScheduleItem bean, add getters/setters and XDoclet tags<BR/>
-<pre id="code">
- /**
- * @ejb.persistence read-only="false"
- * @ejb.interface-method view-type="local"
- */
- public abstract java.lang.String getName();
-
- /**
- * @ejb.persistence
- * @ejb.interface-method view-type="local"
- */
- public abstract void setName(java.lang.String newName);
-
- /**
- * @ejb.persistence read-only="false"
- * @ejb.interface-method view-type="local"
- */
- public abstract int getStartTime();
-
- /**
- * @ejb.persistence
- * @ejb.interface-method view-type="local"
- */
- public abstract void setStartTime(int newStartTime);
-
- /**
- * @ejb.persistence read-only="false"
- * @ejb.interface-method view-type="local"
- */
- public abstract int getEndTime();
-
- /**
- * @ejb.persistence
- * @ejb.interface-method view-type="local"
- */
- public abstract void setEndTime(int newEndTime);
-
- /**
- * @ejb.persistence read-only="false"
- * @ejb.interface-method view-type="local"
- */
- public abstract int getDay();
-
- /**
- * @ejb.persistence
- * @ejb.interface-method view-type="local"
- */
- public abstract void setDay(int newDay);
-
- /**
- * @ejb.persistence read-only="false"
- * @ejb.interface-method view-type="local"
- */
- public abstract java.lang.String getScheduleID();
-
- /**
- * @ejb.persistence
- * @ejb.interface-method view-type="local"
- */
- public abstract void setScheduleID(java.lang.String newScheduleID);
-</pre></LI>
-<LI>Next is to add a means by which to create ScheduleItemBean. The create method will take the Name for the new ScheduleItem and autogenerate a new key. The rudimentry key generation code is for example purposes only. After you paste the code below, do an organized imports (Control-Shift-o) to add an import for CreateException.<BR/>
-<pre id="code">
-private static int PRIMKEY = (int) System.currentTimeMillis();
-
- /**
- * ejbCreate
- *
- * @ejb.create-method view-type="local"
- */
- public java.lang.Integer ejbCreate(java.lang.String name)
- throws CreateException {
- setId(new Integer(PRIMKEY++));
- setName(name);
- return null;
- }
-
- /**
- * ejbPostCreate
- */
- public void ejbPostCreate(java.lang.String name) throws CreateException {
- }
-</pre></LI>
-<LI>The last step is to add a few finder definitions. These should be added to the class level javadoc (right below the @ejb.pk class definition added before).<BR/>
-<pre id="code">
- * @ejb.finder signature="java.util.Collection findAll()" query="select
- * object(o) from ScheduleItem o"
- *
- * @ejb.finder signature="java.util.Collection findByScheduleID(java.lang.String
- * scheduleID)" query="select object(o) from ScheduleItem o where
- * o.scheduleID = (?1)"
- *
- * @ejb.finder signature="java.util.Collection findByName(java.lang.String
- * name)" query="select object(o) from ScheduleItem o where o.name =
- * (?1)"
-</pre></LI>
- <LI>At this point if you save and build, you should be abloe to open ScheduleItemLocal and ScheduleItemLocalHome and see all method stubs were appropriatly generated. Do not edit these files. Once you are done inspecting them, close them both.<BR/>
- <IMG border="0" src="images/newcmp3.jpg" width="688" height="663"/><BR/><BR/>
- <IMG border="0" src="images/newcmp4.jpg" width="686" height="658"/><BR/><BR/></LI>
-</OL>
-
-<h2>Adding purpose to ScheduleSessionBean</h2>
-<OL>
- <LI>If ScheduleSessionBean is not open, open it in the JavaEditor. The first thing we need to do is add a local reference from the ScheduleSessionBean to the ScheduleItemLocal. This requires the following XDoclet tag at the class level (put this right below the * @ejb.bean name="ScheduleSession" block). The second tag which starts with @jboss.ejb-local-ref is a JBoss specific XDoclet tag used to setup the JNDI name; other vendors also have their own specific tags where needed.<BR/>
-<pre id="code">
- * @ejb.ejb-ref ejb-name="ScheduleItem" view-type="local"
- *
- * @jboss.ejb-local-ref ref-name="ScheduleItemLocal"
- * jndi-name="ejb/ejbs/ScheduleItemLocalHome"
- *
-</pre></LI>
-
- <LI>Since ScheduleSessionBean will be used by the forthcoming web client instead of ScheduleItemBean, it is necessary to add a few methods to access ScheduleItems. The below code supplies a way for clients to create new ScheduleItems, and find existing ones using the finders we specified previously. Note that ScheduleItems beans are not returned directly, but, rather their data is wrapped up in a ScheduleItemWrapper. The ScheduleItemWrapper will be created in the next step. Delete the existing 'foo' method and add the following methods to ScheduleSessionBean. You will have several compile errors which can be fixed using organized imports (Control-Shift-o); just be sure you select the correct types if there are multiple choices (javax.naming.Context, javax.rmi.PortableRemoteObject, ,java.util.List, java.util.Iterator) <BR/>
-<pre id="code">
- /**
- * @ejb.interface-method view-type="both"
- */
- public ScheduleItemWrapper addScheduleItem(String name, int startTime,
- int endTime, int day, String scheduleID) {
- ScheduleItemLocalHome home = getScheduleItemLocalHome();
- try {
- ScheduleItemLocal scheduleItem = home.create(name);
- scheduleItem.setStartTime(startTime);
- scheduleItem.setEndTime(endTime);
- scheduleItem.setDay(day);
- scheduleItem.setScheduleID(scheduleID);
- return new ScheduleItemWrapper(name, startTime, endTime, day,
- scheduleID);
- } catch (CreateException e) {
- // TODO Auto-generated catch block
- e.printStackTrace();
- }
- return null;
- }
-
- /**
- * @ejb.interface-method view-type="both"
- */
- public List getScheduleItem(String name) {
- ScheduleItemLocalHome home = getScheduleItemLocalHome();
- try {
- Collection items = home.findByName(name);
- return wrapScheduleItemsInList(items);
- } catch (FinderException e) {
- // TODO Auto-generated catch block
- e.printStackTrace();
- }
- return null;
- }
-
- /**
- * @ejb.interface-method view-type="both"
- */
- public List getAllScheduleItems() {
- ScheduleItemLocalHome home = getScheduleItemLocalHome();
- try {
- Collection items = home.findAll();
- return wrapScheduleItemsInList(items);
- } catch (FinderException e) {
- // TODO Auto-generated catch block
- e.printStackTrace();
- }
- return null;
- }
-
- /**
- * @ejb.interface-method view-type="both"
- */
- public List getScheduleItemesForScheduleID(String scheduleID) {
- ScheduleItemLocalHome home = getScheduleItemLocalHome();
- try {
- Collection items = home.findByScheduleID(scheduleID);
- return wrapScheduleItemsInList(items);
- } catch (FinderException e) {
- // TODO Auto-generated catch block
- e.printStackTrace();
- }
- return null;
- }
-
- private List wrapScheduleItemsInList(Collection items) {
- Iterator iterator = items.iterator();
- List list = new ArrayList(items.size());
- while (iterator.hasNext()) {
- ScheduleItemLocal scheduleItem = (ScheduleItemLocal) iterator
- .next();
- ScheduleItemWrapper wrapper = new ScheduleItemWrapper(scheduleItem
- .getName(), scheduleItem.getStartTime(), scheduleItem
- .getEndTime(), scheduleItem.getDay(), scheduleItem
- .getScheduleID());
- list.add(wrapper);
- }
- return list;
- }
-
- private ScheduleItemLocalHome getScheduleItemLocalHome() {
- try {
- Context context = new InitialContext();
- Object obj = context.lookup("java:comp/env/ejb/ScheduleItemLocal");
- ScheduleItemLocalHome home = (ScheduleItemLocalHome) PortableRemoteObject
- .narrow(obj, ScheduleItemLocalHome.class);
- return home;
- } catch (NamingException e) {
- // TODO Auto-generated catch block
- e.printStackTrace();
- }
- return null;
- }
-</pre></LI>
- <LI>Next, ScheduleItemWrapper needs to be created. Create a new JavaClass called ScheduleItemWrapper in the ejbs package. Be sure to add the java.io.Serializable interface.<BR/>
- <IMG border="0" src="images/wrapper.jpg" width="495" height="599"/><BR/><BR/></LI>
- <LI>Next, open ScheduleItemWrapper in the Java editor and add the following fields.<BR/>
- <pre id="code">
- public java.lang.String name;
-
- public int starttime;
-
- public int endtime;
-
- public int day;
-
- public java.lang.String scheduleId;
- </pre></LI>
- <LI>Right click on ScheduleItemWrapper in the source editor and select Source -> Generate Getters and Setters. Generate a getter and setter for each field.<BR/>
- <IMG border="0" src="images/wrapper2.jpg" width="630" height="630"/><BR/><BR/>
- <IMG border="0" src="images/wrapper3.jpg" width="480" height="601"/><BR/><BR/></LI>
- <LI>Finally, add the following constructor.<BR/>
- <pre id="code">
- public ScheduleItemWrapper(java.lang.String name, int starttime,
- int endtime, int day, java.lang.String scheduleId) {
- this.name = name;
- this.starttime = starttime;
- this.endtime = endtime;
- this.day = day;
- this.scheduleId = scheduleId;
- }
- </pre></LI>
-</OL>
-<h2>Building a Web Client</h2>
-<P>The first step is to create a Web project.</P>
-<OL>
- <LI>Select File -> New -> Project -> Web -> Dynamic Web Project<BR/>
- <IMG border="0" src="images/newwebproj1.jpg" width="500" height="500"/><BR/><BR/></LI>
- <LI>Click Next and fill in 'ScheduleWeb' for the Web project name, expand the advanced section and select '2.3' for the module version, 'Generic JBoss 3.2.3' for server target, 'ScheduleEAR' for the EAR Application name, and check Add Support for annotated Java classes. Click finish.<BR/>
- <IMG border="0" src="images/newwebproj2.jpg" width="514" height="495"/><BR/><BR/></LI>
- <LI>Expand the 'Dynamic Web Projects' node in the project explorer, and right click on ScheduleWeb and select 'Properties'.<BR/>
- <IMG border="0" src="images/newwebproj3.jpg" width="361" height="529"/><BR/><BR/></LI>
- <LI>Select the 'Java JAR Dependencies' properties page, and then click the checkbox next to 'ScheduleEJB.jar' to add a module dependency to the EJB module.<BR/>
- <IMG border="0" src="images/newwebproj4.jpg" width="619" height="562"/><BR/><BR/></LI>
-</OL>
-
-<h2>Creating a Servlet</h2>
-<P>Now you will create a servlet which calls the ScheduleSessionBean.</P>
-<OL>
- <LI>Select File -> New -> Other -> WEB -> Servlet and then click next. Fill in 'servlets' for the package, and 'ServletExample' for the Classname. Check 'Generate an annotated servlet class' and then click finish.<BR/>
- <IMG border="0" src="images/newservlet1.jpg" width="500" height="500"/><BR/><BR/></LI>
- <LI>Similar to the EJB reference from ScheduleSessionBean to ScheduleItemLocal, we are going to create a reference from ScheduleExample to ScheduleSessionLocal by entering the following XDoclet tags to the class level JavaDoc (right below the @web.servlet-mapping line in ScheduleExample).<BR/>
- <pre id="code">
- * @web.ejb-local-ref home="ejbs.ScheduleSessionLocalHome"
- * local="ejbs.ScheduleSessionLocal"
- * name="ejb/ScheduleSession" type="Session"
- * link="ScheduleSession"
- *
- * @jboss.ejb-local-ref ref-name="ScheduleSession"
- * jndi-name="ejb/ejbs/ScheduleSessionHome"
- </pre></LI>
- <LI>Next, add the following methods to ScheduleExample to access ScheduleSessionBean. An organize imports will clean up the compile errors. Be sure to select the correct types (javax.nameing.Context and javax.rmi.PortableRemoteObject).<BR/>
- <pre id="code">
- private ScheduleSessionLocalHome scheduleSessionLocalHome;
-
- private ScheduleSessionLocal getScheduleSession() {
- if (null == scheduleSessionLocalHome) {
- try {
- Context context = new InitialContext();
- Object obj = context
- .lookup("java:comp/env/ejb/ScheduleSession");
- scheduleSessionLocalHome = (ScheduleSessionLocalHome) PortableRemoteObject
- .narrow(obj, ScheduleSessionLocalHome.class);
- } catch (NamingException e) {
- // TODO Auto-generated catch block
- e.printStackTrace();
- }
- }
- try {
- return scheduleSessionLocalHome.create();
- } catch (CreateException e) {
- // TODO Auto-generated catch block
- e.printStackTrace();
- }
- return null;
- }
- </pre></LI>
- <LI>Next, fill the currently empty implementation of doPost() with the following code. An organize imports (select java.util.List) will clean up most of the errors.<BR/>
- <pre id="code">
- response.setContentType("text/plain");
- PrintWriter out = response.getWriter();
-
- ScheduleSessionLocal scheduleSession = getScheduleSession();
-
- String scheduleid = request.getParameter("multidayscheduleid");
- if (scheduleid != null) {
- String title = request.getParameter("title");
- int starttime = Integer.parseInt(request.getParameter("starttime"));
- int endtime = Integer.parseInt(request.getParameter("endtime"));
- String[] days = request.getParameterValues("day");
-
- if (days != null) {
- for (int i = 0; i < days.length; i++) {
- String dayString = days[i];
- int day;
- if (dayString.equalsIgnoreCase("SUN"))
- day = 0;
- else if (dayString.equalsIgnoreCase("MON"))
- day = 1;
- else if (dayString.equalsIgnoreCase("TUE"))
- day = 2;
- else if (dayString.equalsIgnoreCase("WED"))
- day = 3;
- else if (dayString.equalsIgnoreCase("THU"))
- day = 4;
- else if (dayString.equalsIgnoreCase("FRI"))
- day = 5;
- else
- day = 6;
-
- scheduleSession.addScheduleItem(title, starttime, endtime,
- day, scheduleid);
- }
- request.getSession().setAttribute(
- "schoolschedule",
- scheduleSession
- .getScheduleItemesForScheduleID(scheduleid));
- getServletContext().getRequestDispatcher("/TestSchedule.jsp")
- .forward(request, response);
- }
- }
-
- String name = request.getParameter("nameGet");
- if (name != null) {
- List items = scheduleSession.getScheduleItem(name);
- out.println("Schedule Item retrieved:");
- printTable(out, items);
- return;
- }
- String scheduleID = request.getParameter("scheduleID");
- if (scheduleID != null) {
- List items = scheduleSession
- .getScheduleItemesForScheduleID(scheduleID);
- out.println("ScheduleIDs matching " + scheduleID + ":");
- printTable(out, items);
- return;
- }
- List items = scheduleSession.getAllScheduleItems();
- out.println("All Schedule Items:");
- printTable(out, items);
- return;
- </pre></LI>
- <LI>Lastly, add the missing printTable() method and perform an organized imports.<BR/>
- <pre id="code">
- private void printTable(PrintWriter out, List items) {
- out.println("<TABLE border=\"1\" cellspacing=\"0\"><TBODY><TR>");
- out.println("<TH align=\"center\" valign=\"middle\">Name</TH>");
- out.println("<TH align=\"center\" valign=\"middle\">StartTime</TH>");
- out.println("<TH align=\"center\" valign=\"middle\">EndTime</TH>");
- out.println("<TH align=\"center\" valign=\"middle\">Day</TH>");
- out.println("<TH align=\"center\" valign=\"middle\">ScheduleID</TH></TR>");
- for (int i = 0; i < items.size(); i++) {
- ScheduleItemWrapper item = (ScheduleItemWrapper) items.get(i);
- out.println("<TR>");
- out.println("<TD>" + item.getName() + "</TD>");
- out.println("<TD>" + item.getStarttime() + "</TD>");
- out.println("<TD>" + item.getEndtime() + "</TD>");
- out.println("<TD>" + item.getDay() + "</TD>");
- out.println("<TD>" + item.getScheduleId() + "</TD>");
- out.println("</TR>");
- }
- out.println("</TBODY></TABLE>");
- }
- </pre></LI>
-</OL>
-
-<h2>Creating A JSP</h2>
-<P>This is the final piece of this example schedule application, and works with ServletExample created above to provide a user interface.</P>
-<OL>
- <LI>Select File -> New -> Other-> Web -> JSP and click next. Select the WebContent directory under ScheduleWeb, and fill in TestSchedule.jsp for the file name. Click finish.<BR/>
- <IMG border="0" src="images/newjsp1.jpg" width="500" height="578"/><BR/><BR/></LI>
- <LI>Open TestSchedule.jsp with the JSP Editor and add a meaninggul title where it says 'Insert title here', e.g. 'Schedule Example'.<BR/></LI>
- <LI>In order to use the standard tag libraries you will first have to download and install them into our project. Open your Web browser to <A HREF="http://jakarta.apache.org/taglibs/">http://jakarta.apache.org/taglibs/</A>. Under JCP Standardized Tag Libraries on the left select Standar-1.1:JSTL 1.0(2.0) (Be sure you select 1.0 and not 1.1!). Scroll down to the Download section and select the first link, Download the Standard Tag Library Release from an Apache Jakara Project Mirror. Select Taglibs and then Library Releases. Select standard and then select to download
- jakarta-taglibs-standard-current.zip. Once the zip file download, open it and extract jstl.jar and standard.jar into the WebContent/WEB-INF/lib folder in your project. Select your project, right click on it and select Refresh. The libraries are automatically added to your Java classpath. There is currently a bug which hids the contents of the lib directory in the Project Explorer view, but if you switch to the Navigator view, your project should look like this:<BR/>
- <IMG border="0" src="images/newjsp2.jpg" width="233" height="358"/><BR/><BR/></LI>
- <LI>In order to use the tag libraries you have just downloaded you will have to declare them in your JSP. At the top of the JSP file (right above <!DOCTYPE HTML) add in the following line
- <pre id="code">
- <%@taglib uri="http://java.sun.com/jstl/core" prefix="c"%>
- </pre>
- <IMG border="0" src="images/newjsp3.jpg" width="631" height="320"/><BR/><BR/></LI>
- <LI>Finally, add the following code to within the body tags:<BR/>
-
- <pre id="code">
-<FORM action="/ScheduleWeb/ScheduleExample" method="post">Schedule<INPUT
- type="text" name="multidayscheduleid" size="35"><BR>
-Course Name: <INPUT type="text" name="title" size="35"><BR>
-Course Time: Sun<INPUT type="checkbox" name="day" value="sun"> Mon<INPUT
- type="checkbox" name="day" value="mon"> Tue<INPUT type="checkbox"
- name="day" value="tue"> Wed<INPUT type="checkbox" name="day"
- value="wed"> Thu<INPUT type="checkbox" name="day" value="thu"> Fri<INPUT
- type="checkbox" name="day" value="fri"> Sat<INPUT type="checkbox"
- name="day" value="sat"> <SELECT name="starttime">
- <OPTION value="8">8:00am</OPTION>
- <OPTION value="9">9:00am</OPTION>
- <OPTION value="10">10:00am</OPTION>
- <OPTION value="11">11:00am</OPTION>
- <OPTION value="12">12:00pm</OPTION>
- <OPTION value="13">1:00pm</OPTION>
- <OPTION value="14">2:00pm</OPTION>
- <OPTION value="15">3:00pm</OPTION>
- <OPTION value="16">4:00pm</OPTION>
- <OPTION value="17">5:00pm</OPTION>
- <OPTION value="18">6:00pm</OPTION>
- <OPTION value="19">7:00pm</OPTION>
- <OPTION value="20">8:00pm</OPTION>
- <OPTION value="21">9:00pm</OPTION>
-</SELECT> to <SELECT name="endtime">
- <OPTION value="9">9:00am</OPTION>
- <OPTION value="10">10:00am</OPTION>
- <OPTION value="11">11:00am</OPTION>
- <OPTION value="12">12:00pm</OPTION>
- <OPTION value="13">1:00pm</OPTION>
- <OPTION value="14">2:00pm</OPTION>
- <OPTION value="15">3:00pm</OPTION>
- <OPTION value="16">4:00pm</OPTION>
- <OPTION value="17">5:00pm</OPTION>
- <OPTION value="18">6:00pm</OPTION>
- <OPTION value="19">7:00pm</OPTION>
- <OPTION value="20">8:00pm</OPTION>
- <OPTION value="21">9:00pm</OPTION>
- <OPTION value="22">10:00pm</OPTION>
-</SELECT> <BR>
-<BR>
-<INPUT type="submit" name="Submit" value="AddCourse"></FORM>
-
-<TABLE border="1" cellspacing="0">
- <TBODY>
- <TR>
- <TH align="center" valign="middle" width="80"></TH>
- <TH align="center" valign="middle" width="100">Sunday</TH>
- <TH align="center" valign="middle">Monday</TH>
- <TH align="center" valign="middle">Tuesday</TH>
- <TH align="center" valign="middle">Wednesday</TH>
- <TH align="center" valign="middle">Thursday</TH>
- <TH align="center" valign="middle">Friday</TH>
- <TH align="center" valign="middle">Saturday</TH>
- </TR>
- <c:forEach begin="8" end="21" step="1" var="time">
- <TR>
- <TD align="center" valign="middle" width="80"><c:choose>
- <c:when test="${time == 12}">
- <c:out value="${time}" />:00pm
-</c:when>
- <c:when test="${time > 12}">
- <c:out value="${time - 12}" />:00pm
-</c:when>
- <c:otherwise>
- <c:out value="${time}" />:00am
-</c:otherwise>
- </c:choose></TD>
- <c:forEach begin="0" end="6" step="1" var="day">
- <TD align="center" valign="middle" width="100"><c:forEach
- items="${schoolschedule}" var="clazz">
- <c:if
- test="${clazz.starttime <= time
-&& clazz.endtime > time
-&& clazz.day == day}">
- <c:out value="${clazz.name}" />
- </c:if>
- </c:forEach></TD>
- </c:forEach>
- </TR>
- </c:forEach>
- </TBODY>
-</TABLE>
-
-<FORM method="post" action="/ScheduleWeb/ScheduleExample">Schedule:<INPUT
- type="text" name="scheduleID" size="20"><br>
-<INPUT type="submit" value="Get Schedule"></FORM>
-
-
-<FORM method="post" action="/ScheduleWeb/ScheduleExample">Course Name:<INPUT
- type="text" name="nameGet" size="20"><br>
-<INPUT type="submit" value="Find Schedules"></FORM>
-
-
-<FORM method="post" action="/ScheduleWeb/ScheduleExample"><INPUT
- type="submit" value="Get All Schedules"></FORM>
- </pre></LI>
-</OL>
-
-<h2>Running And Testing The School Schedule Web Application</h2>
-<P>Your school schedule application is now complete. Now it is time to take it for a spin.</P>
-<OL>
- <LI>Right click on the servers view and select New -> Server.<BR/><BR/>
- <IMG border="0" src="images/run1.jpg" width="619" height="200"/><BR/><BR/></LI>
- <LI>Select 'Generic JBoss 3.2.3' under Generic Examples and click Finish.<BR/><BR/>
- <IMG border="0" src="images/run2.jpg" width="500" height="538"/><BR/><BR/></LI>
- <LI>Right click on the newly created server in the Servers view and select run. Wait a few seconds to ensure the server started up correctly. The Console view should look something like this:<BR/><BR/>
- <IMG border="0" src="images/run3.jpg" width="1079" height="299"/><BR/><BR/></LI>
- <LI>Flip back to the servers view. Right click on the new running server and select 'Add and Remove Projects...' which will bring up the dialog below. Select ScheduleEAR from the left panel and click 'Add >' to add it to the right panel as shown below. Click Finish.<BR/><BR/>
- <IMG border="0" src="images/run4.jpg" width="500" height="485"/><BR/><BR/></LI>
- <LI>Wait a few more seconds while the project is added to the server and started. Once it is finished, the Console view should look like this:<BR/><BR/>
- <IMG border="0" src="images/run5.jpg" width="1085" height="313"/><BR/><BR/></LI>
- <LI>Now, back in the Project Explorer right click on 'TestSchedule.jsp' and select 'Run As' -> 'Run on Server'. This will bring up the below dialog. Click Finish.<BR/><BR/>
- <IMG border="0" src="images/run6.jpg" width="500" height="627"/><BR/><BR/></LI>
- <LI>An embedded web browser should open showing the following page.<BR/><BR/>
- <IMG border="0" src="images/run7.jpg" width="836" height="751"/><BR/><BR/></LI>
- <LI>The 'Schedule' field (backed by scheduleID in the CMP) differentiates one schedule from another (e.g. John's schedule from Mary's schedule). Hopefully, the rest is straight forward enough.<BR/><BR/>
- The fields below the calendar use the various finder methods we defined on th CMP. Below are a few examples. The first is after a few courses were added to 'John's Schedule'<BR/><BR/>
- <IMG border="0" src="images/run8.jpg" width="836" height="753"/><BR/><BR/></LI>
- <LI>Next is the result of clicking 'Get Schedule' for 'John's Schedule'<BR/><BR/>
- <IMG border="0" src="images/run9.jpg" width="399" height="303"/><BR/><BR/></LI>
- <LI>Next is the result of clicking 'Find Schedules' for 'Math'<BR/><BR/>
- <IMG border="0" src="images/run10.jpg" width="384" height="276"/><BR/><BR/></LI>
- <LI>Finally, here is the result of clicking 'Get All Schedules'.<BR/><BR/>
- <IMG border="0" src="images/run11.jpg" width="452" height="424"/><BR/><BR/></LI>
- <LI>Experiment adding more courses into your schedule.</LI>
-</OL>
-<h2>Summary</h2>
-<P>In this tutorial you learned how to configure Eclipse to work with JBoss and create J2EE EJB and Web projects that uses a CMP Bean, a Session Bean, a servlet, and a JSP to create a student class schedule J2EE Web application. This application, while simple, provides a good introduction to Java Web development and some of the Web development tools available in the Eclipse Web Tools Platform project.</P>
-<P></P>
-<P>
-</P>
-
-</body>
-</html>
diff --git a/community/tutorials/cmptutorial/images/newcmp.jpg b/community/tutorials/cmptutorial/images/newcmp.jpg
deleted file mode 100644
index 8542920..0000000
--- a/community/tutorials/cmptutorial/images/newcmp.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/newcmp2.jpg b/community/tutorials/cmptutorial/images/newcmp2.jpg
deleted file mode 100644
index 8a7d5ad..0000000
--- a/community/tutorials/cmptutorial/images/newcmp2.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/newcmp3.jpg b/community/tutorials/cmptutorial/images/newcmp3.jpg
deleted file mode 100644
index dc7cacb..0000000
--- a/community/tutorials/cmptutorial/images/newcmp3.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/newcmp4.jpg b/community/tutorials/cmptutorial/images/newcmp4.jpg
deleted file mode 100644
index d8aa171..0000000
--- a/community/tutorials/cmptutorial/images/newcmp4.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/newejbproj.jpg b/community/tutorials/cmptutorial/images/newejbproj.jpg
deleted file mode 100644
index 2aaa752..0000000
--- a/community/tutorials/cmptutorial/images/newejbproj.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/newejbproj2.jpg b/community/tutorials/cmptutorial/images/newejbproj2.jpg
deleted file mode 100644
index f2a585a..0000000
--- a/community/tutorials/cmptutorial/images/newejbproj2.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/newejbproj3.jpg b/community/tutorials/cmptutorial/images/newejbproj3.jpg
deleted file mode 100644
index 7874346..0000000
--- a/community/tutorials/cmptutorial/images/newejbproj3.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/newejbproj4.jpg b/community/tutorials/cmptutorial/images/newejbproj4.jpg
deleted file mode 100644
index 1924c9f..0000000
--- a/community/tutorials/cmptutorial/images/newejbproj4.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/newejbproj5.jpg b/community/tutorials/cmptutorial/images/newejbproj5.jpg
deleted file mode 100644
index 6ff38c9..0000000
--- a/community/tutorials/cmptutorial/images/newejbproj5.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/newejbproj6.jpg b/community/tutorials/cmptutorial/images/newejbproj6.jpg
deleted file mode 100644
index 717ccec..0000000
--- a/community/tutorials/cmptutorial/images/newejbproj6.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/newjsp1.jpg b/community/tutorials/cmptutorial/images/newjsp1.jpg
deleted file mode 100644
index acc521d..0000000
--- a/community/tutorials/cmptutorial/images/newjsp1.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/newjsp2.jpg b/community/tutorials/cmptutorial/images/newjsp2.jpg
deleted file mode 100644
index cab2541..0000000
--- a/community/tutorials/cmptutorial/images/newjsp2.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/newjsp3.jpg b/community/tutorials/cmptutorial/images/newjsp3.jpg
deleted file mode 100644
index fc977b2..0000000
--- a/community/tutorials/cmptutorial/images/newjsp3.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/newservlet1.jpg b/community/tutorials/cmptutorial/images/newservlet1.jpg
deleted file mode 100644
index e2ef72e..0000000
--- a/community/tutorials/cmptutorial/images/newservlet1.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/newsession.jpg b/community/tutorials/cmptutorial/images/newsession.jpg
deleted file mode 100644
index 475e877..0000000
--- a/community/tutorials/cmptutorial/images/newsession.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/newsession2.jpg b/community/tutorials/cmptutorial/images/newsession2.jpg
deleted file mode 100644
index 9257cb0..0000000
--- a/community/tutorials/cmptutorial/images/newsession2.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/newsession3.jpg b/community/tutorials/cmptutorial/images/newsession3.jpg
deleted file mode 100644
index 726080b..0000000
--- a/community/tutorials/cmptutorial/images/newsession3.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/newsession4.jpg b/community/tutorials/cmptutorial/images/newsession4.jpg
deleted file mode 100644
index db9cdae..0000000
--- a/community/tutorials/cmptutorial/images/newsession4.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/newsession5.jpg b/community/tutorials/cmptutorial/images/newsession5.jpg
deleted file mode 100644
index 91fe644..0000000
--- a/community/tutorials/cmptutorial/images/newsession5.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/newsession6.jpg b/community/tutorials/cmptutorial/images/newsession6.jpg
deleted file mode 100644
index 8b81a42..0000000
--- a/community/tutorials/cmptutorial/images/newsession6.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/newsession7.jpg b/community/tutorials/cmptutorial/images/newsession7.jpg
deleted file mode 100644
index 98b0e96..0000000
--- a/community/tutorials/cmptutorial/images/newsession7.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/newsession8.jpg b/community/tutorials/cmptutorial/images/newsession8.jpg
deleted file mode 100644
index 95276ce..0000000
--- a/community/tutorials/cmptutorial/images/newsession8.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/newwebproj1.jpg b/community/tutorials/cmptutorial/images/newwebproj1.jpg
deleted file mode 100644
index 76c3f99..0000000
--- a/community/tutorials/cmptutorial/images/newwebproj1.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/newwebproj2.jpg b/community/tutorials/cmptutorial/images/newwebproj2.jpg
deleted file mode 100644
index e281be3..0000000
--- a/community/tutorials/cmptutorial/images/newwebproj2.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/newwebproj3.jpg b/community/tutorials/cmptutorial/images/newwebproj3.jpg
deleted file mode 100644
index e388c81..0000000
--- a/community/tutorials/cmptutorial/images/newwebproj3.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/newwebproj4.jpg b/community/tutorials/cmptutorial/images/newwebproj4.jpg
deleted file mode 100644
index dd425e2..0000000
--- a/community/tutorials/cmptutorial/images/newwebproj4.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/run1.jpg b/community/tutorials/cmptutorial/images/run1.jpg
deleted file mode 100644
index 1cc9370..0000000
--- a/community/tutorials/cmptutorial/images/run1.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/run10.jpg b/community/tutorials/cmptutorial/images/run10.jpg
deleted file mode 100644
index ecf4180..0000000
--- a/community/tutorials/cmptutorial/images/run10.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/run11.jpg b/community/tutorials/cmptutorial/images/run11.jpg
deleted file mode 100644
index 840e838..0000000
--- a/community/tutorials/cmptutorial/images/run11.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/run2.jpg b/community/tutorials/cmptutorial/images/run2.jpg
deleted file mode 100644
index bd99b6f..0000000
--- a/community/tutorials/cmptutorial/images/run2.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/run3.jpg b/community/tutorials/cmptutorial/images/run3.jpg
deleted file mode 100644
index 2cb1f3b..0000000
--- a/community/tutorials/cmptutorial/images/run3.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/run4.jpg b/community/tutorials/cmptutorial/images/run4.jpg
deleted file mode 100644
index 314efb8..0000000
--- a/community/tutorials/cmptutorial/images/run4.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/run5.jpg b/community/tutorials/cmptutorial/images/run5.jpg
deleted file mode 100644
index c5acbcd..0000000
--- a/community/tutorials/cmptutorial/images/run5.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/run6.jpg b/community/tutorials/cmptutorial/images/run6.jpg
deleted file mode 100644
index 4710b2b..0000000
--- a/community/tutorials/cmptutorial/images/run6.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/run7.jpg b/community/tutorials/cmptutorial/images/run7.jpg
deleted file mode 100644
index 77ee31e..0000000
--- a/community/tutorials/cmptutorial/images/run7.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/run8.jpg b/community/tutorials/cmptutorial/images/run8.jpg
deleted file mode 100644
index 3da1598..0000000
--- a/community/tutorials/cmptutorial/images/run8.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/run9.jpg b/community/tutorials/cmptutorial/images/run9.jpg
deleted file mode 100644
index a5cca92..0000000
--- a/community/tutorials/cmptutorial/images/run9.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/wrapper.jpg b/community/tutorials/cmptutorial/images/wrapper.jpg
deleted file mode 100644
index e6bdff5..0000000
--- a/community/tutorials/cmptutorial/images/wrapper.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/wrapper2.jpg b/community/tutorials/cmptutorial/images/wrapper2.jpg
deleted file mode 100644
index 94c5006..0000000
--- a/community/tutorials/cmptutorial/images/wrapper2.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/cmptutorial/images/wrapper3.jpg b/community/tutorials/cmptutorial/images/wrapper3.jpg
deleted file mode 100644
index 8872c9c..0000000
--- a/community/tutorials/cmptutorial/images/wrapper3.jpg
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ejbtutorial/buildingejbs.html b/community/tutorials/ejbtutorial/buildingejbs.html
deleted file mode 100644
index 9957b2c..0000000
--- a/community/tutorials/ejbtutorial/buildingejbs.html
+++ /dev/null
@@ -1,517 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../..//default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../..//webtools/wtp.css" type="text/css">
-<title>WTP Tutorials - Building a Simple EJB Application</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">WTP Tutorials - Building a Simple EJB Application</font>
-<br>
-<font class="indexsub">WTP Tutorials - Building a Simple EJB Application</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../..//images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>By Naci Dai</b>
-<BR>
-Eteration A.S.<BR>
-February 23, 2005<BR>
-
-<BR>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>In this tutorial you will create a simple EJB component and a client web application. This tutorial will introduce you to Session beans and the Web Tools Platform project's support for XDoclet and server tools.
-<BR>
-
-
-</P>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Prerequisites For The Tutorial</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>Web Tools Platform (WTP) project<BR>The WTP project can be downloaded from <a href="http://download.eclipse.org/webtools/downloads/">http://download.eclipse.org/webtools/downloads/</a>
-<BR>
-<BR>
-
-</LI>
-
-<LI>XDoclet 1.2.3<BR>XDoclet is available from <a href="http://xdoclet.sourceforge.net" target="_top">http://xdoclet.sourceforge.net</a>
-<BR>
-<BR>
-</LI>
-
-<LI>JBoss 3.2.3<BR>JBoss is available from <a href="http://www.jboss.org" target="_top">www.jboss.org</a>
-<BR>
-<BR>
-</LI>
-
-<LI>JDK 1.4.2<BR>Sun's JDK is available from <a href="http://java.sun.com/j2se/1.4.2/download.html" target="_top">http://java.sun.com/j2se/1.4.2/download.html</a>
-<BR>
-<BR>
-
-</LI>
-
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Installing The JBoss and XDoclet Runtimes In Eclipse</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>In order to run the EJB and Web modules from Eclipse (which will allow you to test and debug the modules) Eclipse has to be told where to find JBoss, XDoclet and where to find the JDK. JBoss requires a JDK so it can compile servlets and JSPs.</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>Select Window -> Preferences<B></B>.<BR>
-
-<IMG border="0" src="images/buildejb01.gif" width="550" height="340"><BR>
-<BR>
-</LI>
-
-<LI>Select Java -> Installed JREs from the menu on the left.<BR>
-
-<IMG border="0" src="images/buildejb02.gif" width="574" height="513"><BR>
-<BR>
-</LI>
-
-<LI>Select Add... The Add JRE dialog will open. Select Browse for the JRE home directory and choose the location where you installed the JDK 1.4.2. Name the runtime Sun JDK 1.4.2 and click OK.<BR>
-
-<IMG border="0" src="images/buildejb03.gif" width="485" height="441"><BR>
-<BR>
-</LI>
-
-<LI>The Sun JDK 1.4.2 now shows on the list of installed runtimes. Click OK.<BR>
-
-<IMG border="0" src="images/buildejb03a.gif" width="574" height="513"><BR>
-<BR>
-</LI>
-
-<LI>Select Window -> Preferences.<BR>
-<BR>
-</LI>
-
-<LI>Select Server -> Installed Runtimes from the menu on the left.<BR>
-
-<IMG border="0" src="images/buildejb04.gif"><BR>
-<BR>
-</LI>
-
-<LI>Click on Add... Select Generic Server Runtime -> JBoss v3.2.3 and click Next. Click Browse and select the location where you installed JBoss. and click Finish.<BR>
-
-<IMG border="0" src="images/buildejb06.gif"><BR>
-<BR>
-</LI>
-
-<LI>Select XDoclet. Make sure the builder item is selected. Click on the Browse... button and choose the directory where you have installed XDoclet. Make sure that you choose the correct version. Click Apply.<BR>
-
-<IMG border="0" src="images/buildejb07.gif"><BR>
-<BR>
-</LI>
-
-<LI>Select XDoclet->ejbdoclet This is where you can modify the ejbdoclet generation options. You will be able to select specific application servers and their versions. XDoclet will generate deployment descriptors for these application servers only. Make sure nothing is selected. Click Apply.<BR>
-
-<IMG border="0" src="images/buildejb08.gif"><BR>
-<BR>
-</LI>
-
-<LI>Click OK to close the preferences dialog. JDK, XDoclet and JBoss are now configured in Eclipse.</LI>
-
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Creating EJB and Web Modules</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>You will now create flexible projects with EJB and Web modules. In the project with an EJB module you will create a simple Session EJB, and in the project with the web module you will create a client web application to this EJB component.</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>Select File -> New -> Other. Select EJB -> J2EE EJB Module and click Next.<BR>
-
-<IMG border="0" src="images/buildejb09.gif"><BR>
-<BR>
-</LI>
-
-<LI>Click New... for the project, name the project ZooBeansProject and choose the server you have defined and click OK. Enter ZooBeans for the module name. Click advanced and deselect Add module to an EAR project. Select Create an EJB Client JAR, make sure the EJB version 2.0 is selected and click Finish to accept the defaults. <BR>
-
-<IMG border="0" src="images/buildejb10.gif"><BR>
-<BR>
-</LI>
-
-<LI>You will be prompted to switch to the J2EE perspective. Click Yes.<BR>
-<BR>
-</LI>
-
-<LI>The Project Explorer is populated with different types of Web and EJB
- applications. Your newly created project is located under EJB
- Projects. Expand your EJB project. The Deployment Descriptor
- contains information about your EJB project such as the EJBs that
- your project contains. Expanding the ZooBeans folder will reveal
- the ejbModule folder. This is where you will store all of your Java
- files including any EJBs and supporting classes you create. ZooBeansClient project holds the common classes that will be packed into the EJB client jar. We will need this project for the EJB module and the web module.<BR>
-
-<IMG border="0" src="images/buildejb10a.gif"><BR>
-<BR>
-</LI>
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<BR>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Creating a Session EJB</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>Here we will create the simplest of all EJBs; A stateless session bean.</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>Right click on the ejbModule folder and select New -> Other...-> EJB ->EnterpriseJava Bean. Choose SessionBean in the first tab, in the next tab. Set the package to com.zoo. Next enter the class name; class name must end with a "Bean" so name it the bean TigerBean, Click Next. Click Finish. The TigerBean class will now appear in the ejbModule folder and XDoclet builder will generate Tiger, TigerBean, TigerHome, TigerUtil and other related classes for you. TigerBean is an XDoclet annotated Session Bean and other classes are derived classes. Open TigerBean in the Java editor.<BR>
-
-<table>
-<tr>
-<td><IMG border="0" src="images/buildejb11.gif"></td><td><IMG border="0" src="images/buildejb11a.gif"></td>
-</tr>
-</table>
-<BR>
-<IMG border="0" src="images/buildejb11b.gif"><BR>
-</LI>
-
-<LI>XDoclet is an extended Javadoc Doclet engine. It's a generic Java tool that lets you create custom Javadoc @tags and based on those @tags generate source code or other files (such as xml-ish deployment descriptors) using a template engine it provides. XDoclet supports a set of common standard tasks such as web.xml or ejb-jar.xml generation. XDoclet uses special JavaDoc @tags to define
- settings for each component. For example putting a <span style="font-size:10.0pt;font-family:Courier; color:#3F5FBF;background:white; ">@ejb.bean</span><span style="font-size:10.0pt; font-family:Courier;color:windowtext; background:white;"> </span><span style="font-size:10.0pt; font-family:Courier;color:#3F5FBF; background:white;">name="Tiger"</span><span style="font-size:10.0pt;font-family:Courier; color:windowtext;background:white;"> </span><span style="font-size:10.0pt;font-family:Courier; color:#3F5FBF;background:white;">jndi</span><span style="font-size:10.0pt;font-family:Courier; color:#7F7F9F;background:white;">-</span><span style="font-size:10.0pt;font-family:Courier; color:#3F5FBF;background:white;">name="Tiger"</span><span style="font-size:10.0pt;font-family:Courier; color:windowtext;background:white;"> </span><span style="font-size:10.0pt;font-family:Courier; color:#3F5FBF;background:white;">type="Stateless"</span><span style="font-size:10.0pt;font-family:Courier; color:windowtext;background:white;"> </span><i>in TigerBean.java</i>
-
-<BR>
-
-<BR>
-
-<pre id="code">
-/**
- *
- *
- * A generated session bean
- *
- * *
- *
- * @ejb.bean name="Tiger"
- * description="A session bean named Tiger"
- * display-name="Tiger"
- * jndi-name="Tiger"
- * type="Stateless"
- * transaction-type="Container"
- *
- *
- * @generated
- */
-
-public abstract class TigerBean implements javax.ejb.SessionBean {
-
- /**
- *
- *
- * @ejb.interface-method view-type="remote"
- *
- * @generated
- *
- * //TODO: Must provide implementation for bean method stub
- */
- public String foo(String param) {
- return null;
- }
-}
- </pre>
-
-
-</LI>
-
-<LI>TigerBean is the only class you will edit. All others are automatically generated and XDoclet will regenerate them each time you make a change to the TigerBean class. WTP provides code-assist for XDoclet tags. To get help hit crtl-space anywhere inside a xdoclet Javadoc. Edit the TigerBean class and change the foo method to look like this:<BR>
-
-<pre id="code">
- /**
- *
- *
- * @ejb.interface-method view-type="remote"
- *
- *
- */
- public String roar() {
- return "Roar!";
- }
- </pre>
-
-</LI>
-
-
-<LI>XDoclet builder will start working again and update your classes.
- At the end your projects will look like the following: The ZooBeansProject
- that hosts the EJB mmodule will have two classes TigerBean.java and
- TigerSession.java. These are server side classes. ZooBeansClient project will have
- the public interfaces such as the Tiger.java and TigerHome.java. These are the classes
- that will be needed by all clients.<BR>
-<BR>
-
-<IMG border="0" src="images/buildejb12.gif"><BR>
-<BR>
-
-<IMG border="0" src="images/buildejb12a.gif"><BR>
-<BR>
-</LI>
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Publishing the EJB to the server</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P> Here we will publish the newly created ZooBeans to a server.</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI> Select the server view from the workbench menu Window>Show View>Other>Server>Servers. Right click on the server view window select New -> Server... Select All>Generic Server Support and then Click Next. Keep the setting for JBoss 3.2.3 and click Next.<BR>
-
-<IMG border="0" src="images/buildejb13.gif">
- <BR>Choose the ZooBeans project from the Available Projects list and click Add and then Click Finish.<BR>
-<BR>
-<BR>
-
-</LI>
-
-<LI>You have setup your server to run your EJB module. Click on the server right click. Choose Start.<BR>
-
-<IMG border="0" src="images/buildejb14.gif"><BR>
-
-</LI>
-
-<LI>You should now observe the console output. JBoss will print a message similar to the following indicating that the EJB Tiger has been deployed successfully.<BR>
-
-<pre id="code">
-12:46:38,899 INFO [MainDeployer] Starting deployment of package: ZooBeans.jar
-12:46:39,249 INFO [EjbModule] Deploying Tiger
-12:46:39,409 INFO [StatelessSessionInstancePool] Started jboss.j2ee:jndiName=Tiger,plugin=pool,service=EJB
-12:46:39,409 INFO [StatelessSessionContainer] Started jboss.j2ee:jndiName=Tiger,service=EJB
-12:46:39,409 INFO [EjbModule] Started jboss.j2ee:module=ZooBeans.jar,service=EjbModule
-12:46:39,409 INFO [EJBDeployer] Deployed: ZooBeans.jar
-
- </pre>
-<BR>
-<BR>
-
-</LI>
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Testing the Tiger! Building a client web application</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>
-Your EJB has now been defined with your EJB Project and it has been deployed. It is ready to be used. You can now build a test client to make the Tiger EJB Roar! To make this create a Flexible Project with a Web Module named ZooWebProject. Use the same server (JBoss) for this project too. You can follow the step described in the tutorials <a href="../SchoolSchedule/BuildingAScheduleWebApp.html">Building a School Schedule Web Application</a> or <a href="../BuildJ2EEWebApp/BuildJ2EEWebApp.html">Building and Running a Web Application</a> if you are not familiar with the process.</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>When you have created the ZooWebProject. You will end up with a project that looks like the following:<BR>
-
-<IMG border="0" src="images/buildejb16.gif"><BR>
-<BR>
- This Web module will be client to the EJB. Therefore it needs to know about the EJB module we have created.
- To do this we will set the project build path and use the Flexible projects to dynamically include the EJB client jar
- with our web module.
- </LI>
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Using Flexible projects to link the web module with the an EJB Client module</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>We will need to access the EJB interface types such as Tiger and TigerHome in client applications. These classes are in the ZooBeansClient project, and are packaged in an EJB client jar (ZooBeansClient.jar).
- We need to add the client classes to the build path and inlcude the client.jar in the web module
- when it is deployed to a server.</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>In the Project or Package Explorer, right click on the ZooBeansWeb project and Choose Properties... In the Java buildpath, add the ZooBeansClient project to the project references.
- This will help allows us to compile against the latest ejb client classes in this web project.<BR>
-
-<IMG border="0" src="images/buildejb15a.gif"><BR>
-<BR>
-
-</LI>
-
-<LI>Now we have to add a dependent module to the ZooWeb web module. We will use the flexible project support to do this.
- Currently, WTP does not have a user interface to add dependent modules, so we will edit a file named ".wtpmodules", which can be found at the root of each
- flexible project. However, this is a hidden file so too see it, one must use the "Resource Perspective". To go to the resource perspective
- go Window>Open Perspective>Other and choose resource. Open the .wtpmodules file and edit the contents to add the following:
- <br>
-
-<pre id="code">
-
- <dependent-module deploy-path="/WEB-INF/lib"
- handle="module:/resource/ZooBeansClient/ZooBeansClient">
- <dependency-type>uses</dependency-type>
- </dependent-module>
- </pre>
-
-<BR>
-
-<BR>
- Here we have asked the flexible project support to include the ejb client jar
- inside the WEB-INF/lib folder of the web module during runtime deployment. Flexible
- project support will do the tasks of building a new jar and including it with our web
- module each time the ejb changes.
- <BR>
-
-<BR>
-
-
-<IMG border="0" src="images/buildejb15b.gif"><BR>
-<BR>
-
-</LI>
-
-
-<LI>
- Now Create a file named test.jsp
- <BR>
- Open test.jsp in the JSP source page editor.<BR>
-<BR>
-</LI>
-
-<LI>Add the following lines to test.jsp
- <pre id="code">
-<html>
-<head>
-<title>Insert title here</title>
-</head>
-<body>
-<%
- com.zoo.Tiger tiger = null;
- try{
- com.zoo.TigerHome home = com.zoo.TigerUtil.getHome();
- tiger = home.create();
-
- }catch(Exception exception)
- {
-
- }
-
-
-%>
-<b><%= tiger.roar() %></b>
-</body>
-</html>
- </pre>
-
-</LI>
-
-<LI>Save the test file.</LI>
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Running And Testing The Web Application</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>Your web application is now complete. Now it is time to take it for a spin.</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<OL>
-
-<LI>Right click on test.jsp and select Run As -> Run on Server...<BR>
-<BR>
-</LI>
-
-<LI>A Web browser window will open with the application. Beware of the tiger!.<BR>
-
-<IMG border="0" src="images/buildejb17.gif"><BR>
-<BR>
-
-</LI>
-
-<LI>Experiment adding more methods and ejbs.</LI>
-
-</OL>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Summary</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>In this tutorial you learned how to configure Eclipse to work with XDoclet and create a J2EE EJB project that has a Session Bean. You created a client Web application. This application, while simple, provides a good introduction to EJB development and some of the Web development tools available in the Eclipse Web Tools Platform project.</P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P></P>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<P>
-
-</P>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/community/tutorials/ejbtutorial/buildingejbs.xml b/community/tutorials/ejbtutorial/buildingejbs.xml
deleted file mode 100644
index 3bda93f..0000000
--- a/community/tutorials/ejbtutorial/buildingejbs.xml
+++ /dev/null
@@ -1,276 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<?xml-stylesheet type="text/xsl" href="../../../wtp.xsl"?>
-<html>
-<head>
- <meta name="root" content="../../../../" />
- <title>WTP Tutorials - Building a Simple EJB Application</title>
-</head>
-
-<body>
-<h1>WTP Tutorials - Building a Simple EJB Application</h1>
-<p>
-<b>By Naci Dai</b><BR/>
-Eteration A.S.<BR/>
-February 23, 2005<BR/>
-<BR/>
-</p>
-<P>In this tutorial you will create a simple EJB component and a client web application. This tutorial will introduce you to Session beans and the Web Tools Platform project's support for XDoclet and server tools.
-<BR/>
-
-</P>
-<h2>Prerequisites For The Tutorial</h2>
-<OL>
- <LI>Web Tools Platform (WTP) project<BR/>The WTP project can be downloaded from <a href="http://download.eclipse.org/webtools/downloads/">http://download.eclipse.org/webtools/downloads/</a><BR/><BR/>
- </LI>
- <LI>XDoclet 1.2.3<BR/>XDoclet is available from <a href="http://xdoclet.sourceforge.net" target="_top">http://xdoclet.sourceforge.net</a><BR/><BR/></LI>
- <LI>JBoss 3.2.3<BR/>JBoss is available from <a href="http://www.jboss.org" target="_top">www.jboss.org</a><BR/><BR/></LI>
- <LI>JDK 1.4.2<BR/>Sun's JDK is available from <a href="http://java.sun.com/j2se/1.4.2/download.html" target="_top">http://java.sun.com/j2se/1.4.2/download.html</a><BR/><BR/>
- </LI>
-
-</OL>
-
-<h2>Installing The JBoss and XDoclet Runtimes In Eclipse</h2>
-<P>In order to run the EJB and Web modules from Eclipse (which will allow you to test and debug the modules) Eclipse has to be told where to find JBoss, XDoclet and where to find the JDK. JBoss requires a JDK so it can compile servlets and JSPs.</P>
-<OL>
- <LI>Select Window -> Preferences<B></B>.<BR/>
- <IMG border="0" src="images/buildejb01.gif" width="550" height="340"/><BR/><BR/></LI>
- <LI>Select Java -> Installed JREs from the menu on the left.<BR/>
- <IMG border="0" src="images/buildejb02.gif" width="574" height="513"/><BR/><BR/></LI>
- <LI>Select Add... The Add JRE dialog will open. Select Browse for the JRE home directory and choose the location where you installed the JDK 1.4.2. Name the runtime Sun JDK 1.4.2 and click OK.<BR/>
- <IMG border="0" src="images/buildejb03.gif" width="485" height="441"/><BR/><BR/></LI>
- <LI>The Sun JDK 1.4.2 now shows on the list of installed runtimes. Click OK.<BR/>
- <IMG border="0" src="images/buildejb03a.gif" width="574" height="513"/><BR/><BR/></LI>
- <LI>Select Window -> Preferences.<BR/><BR/></LI>
- <LI>Select Server -> Installed Runtimes from the menu on the left.<BR/>
- <IMG border="0" src="images/buildejb04.gif" /><BR/><BR/></LI>
- <LI>Click on Add... Select Generic Server Runtime -> JBoss v3.2.3 and click Next. Click Browse and select the location where you installed JBoss. and click Finish.<BR/>
- <IMG border="0" src="images/buildejb06.gif" /><BR/><BR/></LI>
- <LI>Select XDoclet. Make sure the builder item is selected. Click on the Browse... button and choose the directory where you have installed XDoclet. Make sure that you choose the correct version. Click Apply.<BR/>
- <IMG border="0" src="images/buildejb07.gif" /><BR/><BR/></LI>
- <LI>Select XDoclet->ejbdoclet This is where you can modify the ejbdoclet generation options. You will be able to select specific application servers and their versions. XDoclet will generate deployment descriptors for these application servers only. Make sure nothing is selected. Click Apply.<BR/>
- <IMG border="0" src="images/buildejb08.gif" /><BR/><BR/></LI>
- <LI>Click OK to close the preferences dialog. JDK, XDoclet and JBoss are now configured in Eclipse.</LI>
-
-</OL><h2>Creating EJB and Web Modules</h2>
-<P>You will now create flexible projects with EJB and Web modules. In the project with an EJB module you will create a simple Session EJB, and in the project with the web module you will create a client web application to this EJB component.</P>
-<OL>
- <LI>Select File -> New -> Other. Select EJB -> J2EE EJB Module and click Next.<BR/>
- <IMG border="0" src="images/buildejb09.gif"/><BR/><BR/></LI>
- <LI>Click New... for the project, name the project ZooBeansProject and choose the server you have defined and click OK. Enter ZooBeans for the module name. Click advanced and deselect Add module to an EAR project. Select Create an EJB Client JAR, make sure the EJB version 2.0 is selected and click Finish to accept the defaults. <BR/>
- <IMG border="0" src="images/buildejb10.gif" /><BR/><BR/></LI>
- <LI>You will be prompted to switch to the J2EE perspective. Click Yes.<BR/><BR/></LI>
- <LI>The Project Explorer is populated with different types of Web and EJB
- applications. Your newly created project is located under EJB
- Projects. Expand your EJB project. The Deployment Descriptor
- contains information about your EJB project such as the EJBs that
- your project contains. Expanding the ZooBeans folder will reveal
- the ejbModule folder. This is where you will store all of your Java
- files including any EJBs and supporting classes you create. ZooBeansClient project holds the common classes that will be packed into the EJB client jar. We will need this project for the EJB module and the web module.<BR/>
- <IMG border="0" src="images/buildejb10a.gif" /><BR/><BR/></LI>
-</OL>
-
-<BR/>
-<h2>Creating a Session EJB</h2>
-<P>Here we will create the simplest of all EJBs; A stateless session bean.</P>
-<OL>
- <LI>Right click on the ejbModule folder and select New -> Other...-> EJB ->EnterpriseJava Bean. Choose SessionBean in the first tab, in the next tab. Set the package to com.zoo. Next enter the class name; class name must end with a "Bean" so name it the bean TigerBean, Click Next. Click Finish. The TigerBean class will now appear in the ejbModule folder and XDoclet builder will generate Tiger, TigerBean, TigerHome, TigerUtil and other related classes for you. TigerBean is an XDoclet annotated Session Bean and other classes are derived classes. Open TigerBean in the Java editor.<BR/>
- <table><tr><td><IMG border="0" src="images/buildejb11.gif" /></td><td><IMG border="0" src="images/buildejb11a.gif" /></td></tr></table><BR/><IMG border="0" src="images/buildejb11b.gif" /><BR/></LI>
- <LI>XDoclet is an extended Javadoc Doclet engine. It's a generic Java tool that lets you create custom Javadoc @tags and based on those @tags generate source code or other files (such as xml-ish deployment descriptors) using a template engine it provides. XDoclet supports a set of common standard tasks such as web.xml or ejb-jar.xml generation. XDoclet uses special JavaDoc @tags to define
- settings for each component. For example putting a <span style='font-size:10.0pt;font-family:Courier;
- color:#3F5FBF;background:white;
- '>@ejb.bean</span><span style='font-size:10.0pt;
- font-family:Courier;color:windowtext;
- background:white;'> </span><span style='font-size:10.0pt;
- font-family:Courier;color:#3F5FBF;
- background:white;'>name="Tiger"</span><span
- style='font-size:10.0pt;font-family:Courier;
- color:windowtext;background:white;'> </span><span
- style='font-size:10.0pt;font-family:Courier;
- color:#3F5FBF;background:white;'>jndi</span><span
- style='font-size:10.0pt;font-family:Courier;
- color:#7F7F9F;background:white;'>-</span><span
- style='font-size:10.0pt;font-family:Courier;
- color:#3F5FBF;background:white;'>name="Tiger"</span><span
- style='font-size:10.0pt;font-family:Courier;
- color:windowtext;background:white;'> </span><span
- style='font-size:10.0pt;font-family:Courier;
- color:#3F5FBF;background:white;'>type="Stateless"</span><span
- style='font-size:10.0pt;font-family:Courier;
- color:windowtext;background:white;'> </span><i>in TigerBean.java</i>
- <BR/>
- <BR/>
- <pre id="code">
-/**
- *
- * <!-- begin-user-doc -->
- * A generated session bean
- * <!-- end-user-doc -->
- * *
- * <!-- begin-xdoclet-definition -->
- * @ejb.bean name="Tiger"
- * description="A session bean named Tiger"
- * display-name="Tiger"
- * jndi-name="Tiger"
- * type="Stateless"
- * transaction-type="Container"
- *
- * <!-- end-xdoclet-definition -->
- * @generated
- */
-
-public abstract class TigerBean implements javax.ejb.SessionBean {
-
- /**
- *
- * <!-- begin-xdoclet-definition -->
- * @ejb.interface-method view-type="remote"
- * <!-- end-xdoclet-definition -->
- * @generated
- *
- * //TODO: Must provide implementation for bean method stub
- */
- public String foo(String param) {
- return null;
- }
-}
- </pre>
-
- </LI>
- <LI>TigerBean is the only class you will edit. All others are automatically generated and XDoclet will regenerate them each time you make a change to the TigerBean class. WTP provides code-assist for XDoclet tags. To get help hit crtl-space anywhere inside a xdoclet Javadoc. Edit the TigerBean class and change the foo method to look like this:<BR/>
- <pre id="code">
- /**
- *
- * <!-- begin-xdoclet-definition -->
- * @ejb.interface-method view-type="remote"
- * <!-- end-xdoclet-definition -->
- *
- */
- public String roar() {
- return "Roar!";
- }
- </pre>
- </LI>
-
- <LI>XDoclet builder will start working again and update your classes.
- At the end your projects will look like the following: The ZooBeansProject
- that hosts the EJB mmodule will have two classes TigerBean.java and
- TigerSession.java. These are server side classes. ZooBeansClient project will have
- the public interfaces such as the Tiger.java and TigerHome.java. These are the classes
- that will be needed by all clients.<BR/><BR/>
- <IMG border="0" src="images/buildejb12.gif" /><BR/><BR/>
- <IMG border="0" src="images/buildejb12a.gif" /><BR/><BR/></LI>
-</OL>
-<h2>Publishing the EJB to the server</h2>
-<P> Here we will publish the newly created ZooBeans to a server.</P>
-<OL>
- <LI> Select the server view from the workbench menu Window>Show View>Other>Server>Servers. Right click on the server view window select New -> Server... Select All>Generic Server Support and then Click Next. Keep the setting for JBoss 3.2.3 and click Next.<BR/>
- <IMG border="0" src="images/buildejb13.gif" />
- <BR/>Choose the ZooBeans project from the Available Projects list and click Add and then Click Finish.<BR/><BR/><BR/>
- </LI>
- <LI>You have setup your server to run your EJB module. Click on the server right click. Choose Start.<BR/>
- <IMG border="0" src="images/buildejb14.gif" /><BR/>
- </LI>
- <LI>You should now observe the console output. JBoss will print a message similar to the following indicating that the EJB Tiger has been deployed successfully.<BR/>
- <pre id="code">
-12:46:38,899 INFO [MainDeployer] Starting deployment of package: ZooBeans.jar
-12:46:39,249 INFO [EjbModule] Deploying Tiger
-12:46:39,409 INFO [StatelessSessionInstancePool] Started jboss.j2ee:jndiName=Tiger,plugin=pool,service=EJB
-12:46:39,409 INFO [StatelessSessionContainer] Started jboss.j2ee:jndiName=Tiger,service=EJB
-12:46:39,409 INFO [EjbModule] Started jboss.j2ee:module=ZooBeans.jar,service=EjbModule
-12:46:39,409 INFO [EJBDeployer] Deployed: ZooBeans.jar
-
- </pre><BR/><BR/>
- </LI>
-</OL>
-
-<h2>Testing the Tiger! Building a client web application</h2>
-<P>
-Your EJB has now been defined with your EJB Project and it has been deployed. It is ready to be used. You can now build a test client to make the Tiger EJB Roar! To make this create a Flexible Project with a Web Module named ZooWebProject. Use the same server (JBoss) for this project too. You can follow the step described in the tutorials <a href="../SchoolSchedule/BuildingAScheduleWebApp.html">Building a School Schedule Web Application</a> or <a href="../BuildJ2EEWebApp/BuildJ2EEWebApp.html">Building and Running a Web Application</a> if you are not familiar with the process.</P>
-<OL>
- <LI>When you have created the ZooWebProject. You will end up with a project that looks like the following:<BR/>
- <IMG border="0" src="images/buildejb16.gif" /><BR/><BR/>
- This Web module will be client to the EJB. Therefore it needs to know about the EJB module we have created.
- To do this we will set the project build path and use the Flexible projects to dynamically include the EJB client jar
- with our web module.
- </LI>
-</OL>
-<h2>Using Flexible projects to link the web module with the an EJB Client module</h2>
-<P>We will need to access the EJB interface types such as Tiger and TigerHome in client applications. These classes are in the ZooBeansClient project, and are packaged in an EJB client jar (ZooBeansClient.jar).
- We need to add the client classes to the build path and inlcude the client.jar in the web module
- when it is deployed to a server.</P>
-<OL>
- <LI>In the Project or Package Explorer, right click on the ZooBeansWeb project and Choose Properties... In the Java buildpath, add the ZooBeansClient project to the project references.
- This will help allows us to compile against the latest ejb client classes in this web project.<BR/>
- <IMG border="0" src="images/buildejb15a.gif" /><BR/><BR/>
- </LI>
- <LI>Now we have to add a dependent module to the ZooWeb web module. We will use the flexible project support to do this.
- Currently, WTP does not have a user interface to add dependent modules, so we will edit a file named ".wtpmodules", which can be found at the root of each
- flexible project. However, this is a hidden file so too see it, one must use the "Resource Perspective". To go to the resource perspective
- go Window>Open Perspective>Other and choose resource. Open the .wtpmodules file and edit the contents to add the following:
- <br/>
- <pre id="code">
-
- <dependent-module deploy-path="/WEB-INF/lib"
- handle="module:/resource/ZooBeansClient/ZooBeansClient">
- <dependency-type>uses</dependency-type>
- </dependent-module>
- </pre>
- <BR/>
- <BR/>
- Here we have asked the flexible project support to include the ejb client jar
- inside the WEB-INF/lib folder of the web module during runtime deployment. Flexible
- project support will do the tasks of building a new jar and including it with our web
- module each time the ejb changes.
- <BR/>
- <BR/>
-
- <IMG border="0" src="images/buildejb15b.gif" /><BR/><BR/>
- </LI>
-
- <LI>
- Now Create a file named test.jsp
- <BR/>
- Open test.jsp in the JSP source page editor.<BR/><BR/></LI>
- <LI>Add the following lines to test.jsp
- <pre id="code">
-<html>
-<head>
-<title>Insert title here</title>
-</head>
-<body>
-<%
- com.zoo.Tiger tiger = null;
- try{
- com.zoo.TigerHome home = com.zoo.TigerUtil.getHome();
- tiger = home.create();
-
- }catch(Exception exception)
- {
-
- }
-
-
-%>
-<b><%= tiger.roar() %></b>
-</body>
-</html>
- </pre>
- </LI>
- <LI>Save the test file.</LI>
-</OL>
-<h2>Running And Testing The Web Application</h2>
-<P>Your web application is now complete. Now it is time to take it for a spin.</P>
-<OL>
- <LI>Right click on test.jsp and select Run As -> Run on Server...<BR/><BR/></LI>
- <LI>A Web browser window will open with the application. Beware of the tiger!.<BR/>
- <IMG border="0" src="images/buildejb17.gif" /><BR/><BR/>
- </LI>
- <LI>Experiment adding more methods and ejbs.</LI>
-</OL>
-<h2>Summary</h2>
-<P>In this tutorial you learned how to configure Eclipse to work with XDoclet and create a J2EE EJB project that has a Session Bean. You created a client Web application. This application, while simple, provides a good introduction to EJB development and some of the Web development tools available in the Eclipse Web Tools Platform project.</P>
-<P></P>
-<P>
-</P>
-</body>
-</html>
diff --git a/community/tutorials/ejbtutorial/images/buildejb01.gif b/community/tutorials/ejbtutorial/images/buildejb01.gif
deleted file mode 100644
index 228e7b0..0000000
--- a/community/tutorials/ejbtutorial/images/buildejb01.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ejbtutorial/images/buildejb02.gif b/community/tutorials/ejbtutorial/images/buildejb02.gif
deleted file mode 100644
index b0e53ad..0000000
--- a/community/tutorials/ejbtutorial/images/buildejb02.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ejbtutorial/images/buildejb03.gif b/community/tutorials/ejbtutorial/images/buildejb03.gif
deleted file mode 100644
index 99eedf0..0000000
--- a/community/tutorials/ejbtutorial/images/buildejb03.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ejbtutorial/images/buildejb03a.gif b/community/tutorials/ejbtutorial/images/buildejb03a.gif
deleted file mode 100644
index 9aeae75..0000000
--- a/community/tutorials/ejbtutorial/images/buildejb03a.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ejbtutorial/images/buildejb04.gif b/community/tutorials/ejbtutorial/images/buildejb04.gif
deleted file mode 100644
index 58974cc..0000000
--- a/community/tutorials/ejbtutorial/images/buildejb04.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ejbtutorial/images/buildejb06.gif b/community/tutorials/ejbtutorial/images/buildejb06.gif
deleted file mode 100644
index 118f158..0000000
--- a/community/tutorials/ejbtutorial/images/buildejb06.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ejbtutorial/images/buildejb07.gif b/community/tutorials/ejbtutorial/images/buildejb07.gif
deleted file mode 100644
index 297a420..0000000
--- a/community/tutorials/ejbtutorial/images/buildejb07.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ejbtutorial/images/buildejb08.gif b/community/tutorials/ejbtutorial/images/buildejb08.gif
deleted file mode 100644
index 56b9c7e..0000000
--- a/community/tutorials/ejbtutorial/images/buildejb08.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ejbtutorial/images/buildejb09.gif b/community/tutorials/ejbtutorial/images/buildejb09.gif
deleted file mode 100644
index 627f103..0000000
--- a/community/tutorials/ejbtutorial/images/buildejb09.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ejbtutorial/images/buildejb10.gif b/community/tutorials/ejbtutorial/images/buildejb10.gif
deleted file mode 100644
index 3f96376..0000000
--- a/community/tutorials/ejbtutorial/images/buildejb10.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ejbtutorial/images/buildejb10a.gif b/community/tutorials/ejbtutorial/images/buildejb10a.gif
deleted file mode 100644
index 5d114bc..0000000
--- a/community/tutorials/ejbtutorial/images/buildejb10a.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ejbtutorial/images/buildejb11.gif b/community/tutorials/ejbtutorial/images/buildejb11.gif
deleted file mode 100644
index fa69f2b..0000000
--- a/community/tutorials/ejbtutorial/images/buildejb11.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ejbtutorial/images/buildejb11a.gif b/community/tutorials/ejbtutorial/images/buildejb11a.gif
deleted file mode 100644
index 3958bbd..0000000
--- a/community/tutorials/ejbtutorial/images/buildejb11a.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ejbtutorial/images/buildejb11b.gif b/community/tutorials/ejbtutorial/images/buildejb11b.gif
deleted file mode 100644
index 6e23796..0000000
--- a/community/tutorials/ejbtutorial/images/buildejb11b.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ejbtutorial/images/buildejb12.gif b/community/tutorials/ejbtutorial/images/buildejb12.gif
deleted file mode 100644
index 9fb43e8..0000000
--- a/community/tutorials/ejbtutorial/images/buildejb12.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ejbtutorial/images/buildejb12a.gif b/community/tutorials/ejbtutorial/images/buildejb12a.gif
deleted file mode 100644
index 31e66ba..0000000
--- a/community/tutorials/ejbtutorial/images/buildejb12a.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ejbtutorial/images/buildejb13.gif b/community/tutorials/ejbtutorial/images/buildejb13.gif
deleted file mode 100644
index 647aedf..0000000
--- a/community/tutorials/ejbtutorial/images/buildejb13.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ejbtutorial/images/buildejb14.gif b/community/tutorials/ejbtutorial/images/buildejb14.gif
deleted file mode 100644
index 40e91ba..0000000
--- a/community/tutorials/ejbtutorial/images/buildejb14.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ejbtutorial/images/buildejb15.gif b/community/tutorials/ejbtutorial/images/buildejb15.gif
deleted file mode 100644
index 6b4545b..0000000
--- a/community/tutorials/ejbtutorial/images/buildejb15.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ejbtutorial/images/buildejb15a.gif b/community/tutorials/ejbtutorial/images/buildejb15a.gif
deleted file mode 100644
index 6fa2a96..0000000
--- a/community/tutorials/ejbtutorial/images/buildejb15a.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ejbtutorial/images/buildejb15b.gif b/community/tutorials/ejbtutorial/images/buildejb15b.gif
deleted file mode 100644
index b194fed..0000000
--- a/community/tutorials/ejbtutorial/images/buildejb15b.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ejbtutorial/images/buildejb16.gif b/community/tutorials/ejbtutorial/images/buildejb16.gif
deleted file mode 100644
index 1eef890..0000000
--- a/community/tutorials/ejbtutorial/images/buildejb16.gif
+++ /dev/null
Binary files differ
diff --git a/community/tutorials/ejbtutorial/images/buildejb17.gif b/community/tutorials/ejbtutorial/images/buildejb17.gif
deleted file mode 100644
index f263776..0000000
--- a/community/tutorials/ejbtutorial/images/buildejb17.gif
+++ /dev/null
Binary files differ
diff --git a/community/whitepapers.xml b/community/whitepapers.xml
deleted file mode 100644
index 14d9abe..0000000
--- a/community/whitepapers.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<whitepapers xmlns="http://www.eclipse.org/webtools/whitepapers"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://www.eclipse.org/webtools/whitepapers schemas/whitepapers.xsd ">
- <paper link="../wst/components/rdb/Data%20Tools%20Open%20Source%20Overview%20for%20Eclipse%20database%20Developer.html"
- title="Data Tools Open Source Overview for Eclipse Database Developer"
- publicationDate="2005-01-01"/>
-</whitepapers>
diff --git a/development/WTPDevelopmentPractice.html b/development/WTPDevelopmentPractice.html
deleted file mode 100644
index 5ed81ee..0000000
--- a/development/WTPDevelopmentPractice.html
+++ /dev/null
@@ -1,263 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta name="GENERATOR" content="IBM Software Development Platform" />
-<link rel="stylesheet" href="http://www.eclipse.org/default_style.css"
- type="text/css" />
-<title>WTP Development Practices</title>
-<!-- David Williams, 10/25/04 (david_williams@us.ibm.com) -->
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000"
- vlink="#551a8b">
-
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
-
- <tbody>
- <tr>
-
- <td width="60%">
- <p align="LEFT"><FONT size="6"><B><FONT
- face="Verdana, Arial, Helvetica, sans-serif">WTP Development
- Practices</FONT></B></FONT><FONT size="1"><FONT
- face="Arial, Helvetica, sans-serif"><FONT color="#8080ff"><br />
- WTP Development Practices</FONT></FONT></FONT></p>
- </td>
-
-
- <td></td>
-
- <td rowspan="2" width="19%"><img
- src="http://www.eclipse.org/images/Idea.jpg" border="0" height="86"
- width="120" alt="" /></td>
-
- </tr>
-
-
- </tbody>
-</table>
-<p>This document is to describe some guidelines, procedures, and
-"best practices" for doing WTP development. In some cases its
-simply covers consistency/procedure issues, but also recommends best
-practices to help community review and involvement. While all component
-teams can have their own practices, if anyone has some good tips or
-recommendations, please post to wtp-dev for discussion or suggest that
-they be added here.</p>
-<h2>Code into CVS</h2>
-
-<p>The component developers should provide the following information to
-accompany code checked into CVS. Some of this information will become
-part of the components 'development' directory in cvs, or on the
-component's WTP website, and should be kept up to date as changes take
-place and development progresses. (See <A
- href="#webanddevelopmentresources" target="_self">Web and development
-resources</A> for guidelines on what goes where).</p>
-
-<ul>
- <li>
- <p>A brief description of the component. This might be an initial
- design document, if it exists, but the actual design document can come
- later. This brief description should overview the function provided by
- the component, but should also list at least a few API's, extension
- points, or other "starting points" for anyone wanting to use
- or extend the component. (See <A href="../wst/components/sse/archiveOfOldish/PluginOverview.html">PluginOverview.html</A>
- for example).</p>
- </li>
-
- <li>
- <p>A brief initial work plan: describing what development tasks are
- expected for the next milestone or two (or simply in "future"
- if not yet planned for a specific milestone). Specific bugs and feature
- requests can be tracked with bugzilla, but this plan should be given as
- a prose "overview" or highlights of work that is planned
- towards refactoring or making the component "platform
- quality". (See <A href="../wst/components/sse/archiveOfOldish/SSEDevelopmentPlan.html">SSEDevelopmentPlan.html</A>
- for example). In particular, if there are areas that can be explicity
- tagged with "HELP WANTED", that would be good since can help
- let potenital contributors know what areas</p>
- </li>
-
- <li>
- <p>Each plugin and build feature should contain a 'description' in the
- plugin.xml (or feature.xml) file (there is a description tag for such
- purpose).</p>
- </li>
-
- <li>
- <p>A plan for how the component will be documented: both the
- "developers guide" type of information (see Platform Plugin
- Developers Guide and JDT Plugin Developers Guide in the base Eclipse
- for examples) and also the status and plan for design overviews and
- "javadoc" type of information.</p>
- </li>
-
- <li>
- <p>All copyrights and appropriate license files should be correctly
- provided.</p>
- </li>
- <LI><b>CVS Hygiene</b></LI>
- <ul>
- <li>
- <p><B>Team Project Set.</B> Each component team should have a
- "team project set" in their 'development' directory to make
- it easy for others to check out what is needed for that particular
- component.</p>
- </li>
-
- <li>
- <p><B>Source Folders</B> A minor consistency point: If there's only
- one "source directory" it should be named 'src'. If there's
- more than one, the additional ones should be named similar to
- src-wizards, so its obvious both that's its source, and what its
- conceptual division is. Multiple folders are not typically required,
- but can be handy when one team has responsibility for one part, and
- another team responsibility for another part of the plugin.</p>
- </li>
-
- <LI>
- <P><B>Compiled code jar.</B> Its recommended the jar for the plugin be
- in the "root" of the plugin. Its also recommended a directory such as
- "runtime" be reserved for those few cases where a pre-existing binary
- jar is shipped with a plugin.</P>
- </LI>
-
- <li>
- <p><B>cvsignore</B> A .cvsignore file should be provided which has at
- least 'bin' in it to prevent the check in of .class files -- please do
- this before bin is committed to the repository (since you can not
- ignore after its there). Typically, other "transient files"
- (such as a non-custom build.xml, etc) are also added to this
- .cvsignore file.</p>
- </li>
-
- <li>
- <p><B>Source Formatting</B> Source should be formatted according to
- some stated standard (e.g. see /wtp-jst-home/development/format) and
- appropriate Eclipse compiler options used (e.g. see
- /wtp-jst-home/development/compilersettings) to produce "clean
- code" (no unnecessary casts, no unused imports, etc.) Its also
- recommended the source originally have 'sorted members'. The intent
- here is to have clean, consistent code that makes it easier for others
- to do diffs, compares, and supply patches.</p>
- </li>
- <LI>
- <P><B>Obsolete directories in CVS. </B> If, due to renaming,
- refactoring, or just spelling mistakes, a directory in CVS should
- literally be deleted, to avoid a large of confusing directories,
- please use following procedure. First, if it contains source, its
- recommend to version that plugin's source, with a name such as
- "obsolete<date>". Next delete the source, and leave in
- its place a single file named "obsolete.txt" . If
- appropriate, that file can contain information about why obsolete,
- where the replacement is, etc. Lastly, someone will occasionally delete those directories from CVS (not
- typically an desirable thing to do, since it is a source code control
- system! Note: if some code or project simply become old or outdated, it is usually not appropriate to delete it since it might be required for simple historical reason. In these cases, its recommed to version the final version with some descriptive name like "outdated<date>" and leave a file in the directory called something like "outdated.txt" with some description of when and why, if there's a similar function offered elsewhere, etc. </P>
- </LI>
- </ul>
-</ul>
-<H3>Modified Code into CVS</H3>
-<P>As features are added to bugzilla and fixes done and patches are
-applied, enter the <B>CVS commit comment</B> as<BR>
-<CODE>[BUGNO] Bugzilla abstract or explanation (eg: [6788] Fixed NPE on
-open) </CODE><BR>
-This will allow us to generate a "what is fixed " list
-automatically with links to bugzilla with each build. For an example of
-output in another project, see <BR>
-<A
- href="http://download.eclipse.org/tools/emf/scripts/news-release-notes.php?ver=2.1.0#I200411180800">http://download.eclipse.org/tools/emf/scripts/news-release-notes.php?ver=2.1.0#I200411180800</A><BR>
-</P>
-<H2>Plugin Design Conventions</H2>
-<P><B>Avoid using the export="true" attribute on pre-req
-(imported) plugins</B>.
-</P>
-<P>Its never appropriate to use it just so your upstream clients save
-typing a line in their plugin.xml file. But, sometimes it is appropriate
-to use it -- when the classes/interfaces in pre-req plugin really are
-part of the pre-reqing plugins API. If it fits this later case,
-that is it is part of the plugin's API, please document what part of the API requires it. For example: <BR>
-<CODE> <!-- need to re-export org.eclipse.text since our API depends
-on it, <BR>
-such as IStructuredDocument extends IDocument <BR>
---> <BR>
-<import plugin="org.eclipse.text"
-export="true"/> </CODE><BR>The reason for this convention is that it forces upstream clients to stay better aware of exactly what they are pre-reqing instead of picking up some classes simply as a side effect of pre-reqing your plugin. </P>
-<h2><A name="webanddevelopmentresources">Web and development resources</A></h2>
-<P>By convention, a directory named 'development' should be used in the
-component's CVS directory structure. This directory would be a peer with
-'features' and 'plugins'. These directories should hold things that may
-be useful or relevant not only to the developers of the components, but
-others interested in contributing (e.g. project team sets, Rose source
-files of designs, etc). Things in these directories are not intended to
-be in a build. If they are intended for an SDK build, they would be part
-of the plugins directory structure.</P>
-<P>[Note: there's some CVS work still needed to map the website to an
-area in CVS, so the following paragraph will be expanded after that is
-established]</P>
-<P>For resources that are to be published or linked on the WTP web site,
-there will be an area in CVS that parallels the website, so resources
-that are placed there will be periodically copied to the whosoever for
-proper serving.</P>
-<H2>Streams and Builds</H2>
-<H3>Code into a Build</H3>
-<UL>
- <LI>Code can go into a build before its part of a milestone plan, since
- frequent builds are important to stay integrated.</LI>
- <LI>The component team must be able to do a "local build" (to
- work out major kinks in definitions and pre-reqs).</LI>
-
- <LI>In addition to the code itself being in a build, automated unit
- tests should also be submitted for the build process.</LI>
-</UL>
-<H3>Nightly, Weekly, Milestone Builds</H3>
-<BLOCKQUOTE>
-<P>Nightly builds will be built from the head stream. Occasional compile
-errors or unit tests failures would not be abnormal, but should be fixed
-by the next nightly build.</P>
-</BLOCKQUOTE>
-<BLOCKQUOTE>
-<P>Weekly integration builds will be built from developer tagged
-versions. There should never be compile errors or unit tests failures in
-an integration build, but if that happens then 1) immediate fixes are
-required and 2) the offender must wear a red clown nose for the day :).
-Integration builds are expected to be of sufficient quality they can be
-used as the target in the development environment, though will have
-received little or no testing.</P>
-</BLOCKQUOTE>
-<BLOCKQUOTE>
-<P>Milestone builds are like weekly integration builds except they get
-substantial testing. The expectation is that milestone builds be of
-sufficient quality that they can be used to self host development.</P>
-</BLOCKQUOTE>
-<H3>Streams, Streams, and more Streams</H3>
-<BLOCKQUOTE>
-<P>Most development should take place in the HEAD stream. However, if a
-component knows its making large breaking changes that would cause
-clients a lot of churn (such as daily changes, to avoid breaking nightly
-build), they can do the major changes in a temporary branch. The
-component team should keep everyone informed that major development is
-occurring in a branch, and naturally, well coordinate the merge back
-into the HEAD stream. A good guideline is that development on a branch
-should not occur for more than 3 weeks without being merged back into
-HEAD.</P>
-</BLOCKQUOTE>
-<H2>Self Assessment</H2>
-
-<p>The following criteria can be useful to self-measure the success of a
-milestone or release. Component leads should monitor their progress with
-these expectations in mind.</p>
-<ul>
- <li>Made the date</li>
- <li>Promised function complete</li>
- <li>Unit tests and performance tests complete and running as
- "passed"</li>
- <li>Test plan with use cases</li>
- <li>Function available one week before milestone for testing</li>
- <li>Design and APIs reviewed and issues answered before milestone</li>
- <li>Community-users buy-in and/or excitement</li>
- <li>Included community contributed code.</li>
- <li>All "priority 1" defects resolved and all "severity
- 1" defects addressed.</li>
-</ul>
-</body>
-</html>
diff --git a/development/apiscanner/apiscanner.html b/development/apiscanner/apiscanner.html
deleted file mode 100644
index 036df88..0000000
--- a/development/apiscanner/apiscanner.html
+++ /dev/null
@@ -1,263 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../webtools/wtp.css" type="text/css">
-<title>Eclipse API Scanner</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">Eclipse API Scanner</font>
-<br>
-<font class="indexsub">Eclipse API Scanner</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><em>Updated 2005-02-07</em></td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Introduction</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-This document summarizes the usage of the Eclipse API scanner.
-The goal of the Eclipse API scanner is to identify any internal API references in
-any Eclipse-based products. You can view the requirements document
-<a href="http://dev.eclipse.org/viewcvs/index.cgi/*checkout*/org.eclipse.wtp.releng/apitools/api-usage-checking.html?rev=HEAD&cvsroot=WebTools_Project&content-type=text/html">here</a>, and the design document
-<a href="http://dev.eclipse.org/viewcvs/index.cgi/*checkout*/org.eclipse.wtp.releng/apitools/api-usage-checking-design.html?rev=HEAD&cvsroot=WebTools_Project&content-type=text/html">here</a>.
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p></p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Downloading and running the Eclipse API scanner</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-A binary version of the Eclipse API scanner is available here:
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/apiscanner.zip">Download the Eclipse API scanner</a>.
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-The source of the Eclipse API scanner is also available in
-<a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.wtp.releng/apitools/?cvsroot=WebTools_Project">CVS</a>.
-Check out the <b>org.eclipse.wtp.releng.tools.component.core</b> project and the
-<b>org.eclipse.wtp.releng.tools.component.ui</b> project.
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>Running the Eclipse API scanner from the command line environment</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-Before running the Eclipse API scanner, you should get yourself familiar with what is a
-component. For a definition of component, visit the
-<a href="http://dev.eclipse.org/viewcvs/index.cgi/*checkout*/org.eclipse.wtp.releng/apitools/api-usage-checking-design.html?rev=HEAD&cvsroot=WebTools_Project&content-type=text/html">design document</a>.
-To begin, have your Eclipse components/plug-ins and your component.xml files ready.
-The Eclipse API scanner will scan all the API references in each component and check whether
-they are internal API references. An API violation report will be generated for each component.
-To generate the API violation reports, run:
-<pre>
-genViolation.bat -eclipseDir <eclipseDir> -compXMLDir <compXMLDir> -compRefDir <compRefDir> -compVioDir <compVioDir> -genHTML -debug
-</pre>
-where:
-<ul>
-
-<li>
-<b>eclipseDir</b> - a space separated list of directories containing the plug-ins
- for your product. These directories do not have to include the base Eclipse plug-ins
- (ex: org.eclipse.jdt.core). You only need the plug-ins that you want to generate API
- violation reports for.</li>
-
-<li>
-<b>compXMLDir</b> - a space separated list of directories containing component.xml
- files for your product. The Eclipse API scanner will generate an API violation report for each component.xml
- found in these directories. So, if you do not want to generate violation reports for the
- Eclipse components (ex: org.eclipse.jdt.core), do not include their component.xml files here.</li>
-
-<li>
-<b>compRefDir</b> - a space separated list of directories containing component.xml
- files that your product/components depend on. For example, the component.xml files
- for org.eclipse.jdt.core goes here.</li>
-
-<li>
-<b>compVioDir</b> - the output directory of the API violation reports.</li>
-
-<li>
-<b>genHTML</b> - generates the API violation report in HTML (default is XML format).</li>
-
-<li>
-<b>debug</b> - generates debug information (ex: line numbers).</li>
-
-</ul>
-For a list of all the options available, simply run genViolation.bat without any arguments.
-Note that genViolation.bat uses relative paths. Therefore, if you want to run it
-out-of-the-box, we must "cd" to genViolation.bat's directory before running it. Other
-options include:
-<ul>
-
-<li>
-<b>include</b> - a space separated list of package names to be included in the scan.</li>
-
-<li>
-<b>exclude</b> - a space separated list of package names to be excluded in the scan.
- For example, if you specify "java.lang. sun.", then the API violation report will not include
- internal API references to those two packages.</li>
-
-<li>
-<b>genAPI</b> - generates a component-api.xml file per component. This file lists all
- the public APIs that a component has.</li>
-
-<li>
-<b>genUsage</b> - generates a component-use.xml file per component. This file lists all
- the API references that a component has.</li>
-
-<li>
-<b>classRefOnly</b> - treats all API references as class reference. By default,
- the Eclipse API scanner will categorize API references into different categories such
- as class references, method references, field references and etc. By specifying this
- option, all API references are consider class references. This speeds up the scanning
- process.</li>
-
-</ul>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-To get you started more quickly, you can use <b>genComponent.bat</b> to generate a component.xml
-file per plugin. Any packages with the word "internal" in it will be excluded from the generated
-component.xml file. To generate default component.xml files, run:
-<pre>
-genComponent.bat -eclipseDir <eclipseDir> -compXMLDir <compXMLDir>
-</pre>
-where:
-<ul>
-
-<li>
-<b>eclipseDir</b> - a space separated list of directories containing the plug-ins
- for your product. Again, do not include base Eclipse plug-ins in here.</li>
-
-<li>
-<b>compXMLDir</b> - the output directory of the generated component.xml files.</li>
-
-</ul>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>Running the Eclipse API scanner within Eclipse</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-The Eclipse API scanner is also available as two Eclipse plug-ins. Therefore, you can overlay
-them on top of an Eclipse driver and use them to check API violations as you develop your
-product/plug-ins. To get these plug-ins, go to:
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.wtp.releng/apitools/?cvsroot=WebTools_Project">http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.wtp.releng/apitools/?cvsroot=WebTools_Project</a>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-and check out the <b>org.eclipse.wtp.releng.tools.component.core</b> project and the
-<b>org.eclipse.wtp.releng.tools.component.ui</b> project. They provide an
-editor for editing component.xml files.
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-<img src="./figure01.gif"></p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-They will also scan the plug-ins in your workspace and generate API violations in the problems
-views. The figure below shows a plug-in in my workspace called <b>org.eclipse.sample</b>.
-I have also created a component.xml file for this plugin.
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-<img src="./figure02.gif"></p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-In the next figure, I have added a reference to one of the Eclipse internal class. The
-Eclipse API scanner will flag this as an API violation and display it in the problems
-view.
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-<img src="./figure03.gif"></p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-You can find some sample component.xml files
-<a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.wtp.releng/apitools/components/?cvsroot=WebTools_Project">here</a>.
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>Disclaimer:</b> these sample component.xml files are provided as an example only. They
-<b>DO NOT</b> reflect the actual APIs provided by the Eclipse projects.
-</p>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/development/apiscanner/apiscanner.xml b/development/apiscanner/apiscanner.xml
deleted file mode 100644
index 80d3edb..0000000
--- a/development/apiscanner/apiscanner.xml
+++ /dev/null
@@ -1,139 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<?xml-stylesheet type="text/xsl" href="../../wtp.xsl"?>
-<html>
-<head>
- <title>Eclipse API Scanner</title>
- <meta name="root" content="../../.." />
-</head>
-<body>
-
-<h1>Eclipse API Scanner</h1>
-<em>Updated 2005-02-07</em>
-
-<h2>Introduction</h2>
-<p>
-This document summarizes the usage of the Eclipse API scanner.
-The goal of the Eclipse API scanner is to identify any internal API references in
-any Eclipse-based products. You can view the requirements document
-<a href="http://dev.eclipse.org/viewcvs/index.cgi/*checkout*/org.eclipse.wtp.releng/apitools/api-usage-checking.html?rev=HEAD&cvsroot=WebTools_Project&content-type=text/html">here</a>, and the design document
-<a href="http://dev.eclipse.org/viewcvs/index.cgi/*checkout*/org.eclipse.wtp.releng/apitools/api-usage-checking-design.html?rev=HEAD&cvsroot=WebTools_Project&content-type=text/html">here</a>.
-</p>
-<p></p>
-
-<h2>Downloading and running the Eclipse API scanner</h2>
-<p>
-A binary version of the Eclipse API scanner is available here:
-</p>
-<p>
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/apiscanner.zip">Download the Eclipse API scanner</a>.
-</p>
-
-<p>
-The source of the Eclipse API scanner is also available in
-<a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.wtp.releng/apitools/?cvsroot=WebTools_Project">CVS</a>.
-Check out the <b>org.eclipse.wtp.releng.tools.component.core</b> project and the
-<b>org.eclipse.wtp.releng.tools.component.ui</b> project.
-</p>
-
-<h3>Running the Eclipse API scanner from the command line environment</h3>
-<p>
-Before running the Eclipse API scanner, you should get yourself familiar with what is a
-component. For a definition of component, visit the
-<a href="http://dev.eclipse.org/viewcvs/index.cgi/*checkout*/org.eclipse.wtp.releng/apitools/api-usage-checking-design.html?rev=HEAD&cvsroot=WebTools_Project&content-type=text/html">design document</a>.
-To begin, have your Eclipse components/plug-ins and your component.xml files ready.
-The Eclipse API scanner will scan all the API references in each component and check whether
-they are internal API references. An API violation report will be generated for each component.
-To generate the API violation reports, run:
-<pre>
-genViolation.bat -eclipseDir <eclipseDir> -compXMLDir <compXMLDir> -compRefDir <compRefDir> -compVioDir <compVioDir> -genHTML -debug
-</pre>
-where:
-<ul>
- <li><b>eclipseDir</b> - a space separated list of directories containing the plug-ins
- for your product. These directories do not have to include the base Eclipse plug-ins
- (ex: org.eclipse.jdt.core). You only need the plug-ins that you want to generate API
- violation reports for.</li>
- <li><b>compXMLDir</b> - a space separated list of directories containing component.xml
- files for your product. The Eclipse API scanner will generate an API violation report for each component.xml
- found in these directories. So, if you do not want to generate violation reports for the
- Eclipse components (ex: org.eclipse.jdt.core), do not include their component.xml files here.</li>
- <li><b>compRefDir</b> - a space separated list of directories containing component.xml
- files that your product/components depend on. For example, the component.xml files
- for org.eclipse.jdt.core goes here.</li>
- <li><b>compVioDir</b> - the output directory of the API violation reports.</li>
- <li><b>genHTML</b> - generates the API violation report in HTML (default is XML format).</li>
- <li><b>debug</b> - generates debug information (ex: line numbers).</li>
-</ul>
-For a list of all the options available, simply run genViolation.bat without any arguments.
-Note that genViolation.bat uses relative paths. Therefore, if you want to run it
-out-of-the-box, we must "cd" to genViolation.bat's directory before running it. Other
-options include:
-<ul>
- <li><b>include</b> - a space separated list of package names to be included in the scan.</li>
- <li><b>exclude</b> - a space separated list of package names to be excluded in the scan.
- For example, if you specify "java.lang. sun.", then the API violation report will not include
- internal API references to those two packages.</li>
- <li><b>genAPI</b> - generates a component-api.xml file per component. This file lists all
- the public APIs that a component has.</li>
- <li><b>genUsage</b> - generates a component-use.xml file per component. This file lists all
- the API references that a component has.</li>
- <li><b>classRefOnly</b> - treats all API references as class reference. By default,
- the Eclipse API scanner will categorize API references into different categories such
- as class references, method references, field references and etc. By specifying this
- option, all API references are consider class references. This speeds up the scanning
- process.</li>
-</ul>
-</p>
-<p>
-To get you started more quickly, you can use <b>genComponent.bat</b> to generate a component.xml
-file per plugin. Any packages with the word "internal" in it will be excluded from the generated
-component.xml file. To generate default component.xml files, run:
-<pre>
-genComponent.bat -eclipseDir <eclipseDir> -compXMLDir <compXMLDir>
-</pre>
-where:
-<ul>
- <li><b>eclipseDir</b> - a space separated list of directories containing the plug-ins
- for your product. Again, do not include base Eclipse plug-ins in here.</li>
- <li><b>compXMLDir</b> - the output directory of the generated component.xml files.</li>
-</ul>
-</p>
-
-<h3>Running the Eclipse API scanner within Eclipse</h3>
-<p>
-The Eclipse API scanner is also available as two Eclipse plug-ins. Therefore, you can overlay
-them on top of an Eclipse driver and use them to check API violations as you develop your
-product/plug-ins. To get these plug-ins, go to:
-</p>
-<p>
-<a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.wtp.releng/apitools/?cvsroot=WebTools_Project">http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.wtp.releng/apitools/?cvsroot=WebTools_Project</a>
-</p>
-<p>
-and check out the <b>org.eclipse.wtp.releng.tools.component.core</b> project and the
-<b>org.eclipse.wtp.releng.tools.component.ui</b> project. They provide an
-editor for editing component.xml files.
-</p>
-<p><img src="./figure01.gif"/></p>
-<p>
-They will also scan the plug-ins in your workspace and generate API violations in the problems
-views. The figure below shows a plug-in in my workspace called <b>org.eclipse.sample</b>.
-I have also created a component.xml file for this plugin.
-</p>
-<p><img src="./figure02.gif"/></p>
-<p>
-In the next figure, I have added a reference to one of the Eclipse internal class. The
-Eclipse API scanner will flag this as an API violation and display it in the problems
-view.
-</p>
-<p><img src="./figure03.gif"/></p>
-<p>
-You can find some sample component.xml files
-<a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.wtp.releng/apitools/components/?cvsroot=WebTools_Project">here</a>.
-</p>
-<p>
-<b>Disclaimer:</b> these sample component.xml files are provided as an example only. They
-<b>DO NOT</b> reflect the actual APIs provided by the Eclipse projects.
-</p>
-
-</body>
-</html>
diff --git a/development/apiscanner/figure01.gif b/development/apiscanner/figure01.gif
deleted file mode 100644
index 3032325..0000000
--- a/development/apiscanner/figure01.gif
+++ /dev/null
Binary files differ
diff --git a/development/apiscanner/figure02.gif b/development/apiscanner/figure02.gif
deleted file mode 100644
index b2272d0..0000000
--- a/development/apiscanner/figure02.gif
+++ /dev/null
Binary files differ
diff --git a/development/apiscanner/figure03.gif b/development/apiscanner/figure03.gif
deleted file mode 100644
index af4d68b..0000000
--- a/development/apiscanner/figure03.gif
+++ /dev/null
Binary files differ
diff --git a/development/arch_and_design/ArchitectureOverview.html b/development/arch_and_design/ArchitectureOverview.html
deleted file mode 100644
index fa813df..0000000
--- a/development/arch_and_design/ArchitectureOverview.html
+++ /dev/null
@@ -1,266 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1" ?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta name="GENERATOR" content="IBM Software Development Platform" />
-<title>Eclipse Webtools Architecture Overview</title>
-</head>
-<body>
-<div align="center">
-<table border="1" cellpadding="10" height="50%" width="70%">
- <tbody>
- <tr align="left" valign="middle">
- <td valign="middle" align="left">
- <blockquote style="">
- <p><cite>The background and status of this document:</cite></p>
- <p><cite>This version is a second draft of WTP Architecture Overview
- and has incorporated comments received. Comments to wtp-dev list are welcome. </cite></p>
- <p><cite> Version 0.3 December 2, 2004. </cite></p>
- </blockquote>
- </td>
- </tr>
- </tbody>
-</table>
-</div>
-<h1>Eclipse Webtools Architecture Overview</h1>
-<p>The <a href="http://www.eclipse.org/webtools/main.html">Web Tooling
-Platform (WTP) Project</a> is made up of two subprojects, <a
- href="http://www.eclipse.org/webtools/wst/main.html">Web Standard Tools
-(WST)</a> and <a href="http://www.eclipse.org/webtools/jst/main.html">J2EE
-Standard Tools (JST)</a>.</p>
-<p>The <a href="http://www.eclipse.org/webtools/wst/components.html">list
-of components for WST</a> and the<a
- href="http://www.eclipse.org/webtools/jst/components.html"> list of
-components for JST</a> give descriptions of the components and
-[eventually will contain] links to that component's specific design
-documents.
-<p>This document describes the <b>subsystems</b> that these components
-form. These divisions into subsystems are important because they form
-the basis of what is available to other projects, and end-user update
-manager features, and features for maintenance streams. Also, it allows
-a high level description of internal and external dependancies.</p>
-
-<p>For end-users, there is currently only one news group, <a
- href="news:org.eclipse.dev/eclipse.webtools">eclipse.webtools</a>. For
-developers, there are currently three mailing lists <a
- href="mailto:wtp-dev@eclipse.org">wtp-dev</a>, <a
- href="mailto:wtp-wst-dev@eclipse.org">wtp-wst-dev</a>, and <a
- href="mailto:wtp-jst-dev@eclipse.org">wtp-jst-dev</a>. As the project
-continues, if traffic seems "heavy" for a particular component, then new
-mailing lists and/or news groups will be created as needed.</p>
-
-<p>This document decribes the <a href="#subsystemview">Subsystem View</a>, <a
- href="#eclipsedependancies">Dependancies on the Eclipse Project</a>, <a
- href="#toolsdependancies">Dependancies on Tools Projects</a>, <a
- href="#relationtootherprojects">Relation to other Projects and Products</a>, <a
- href="#graphicalsummary">Summary in Graphical form</a>, and <a
- href="#deployrmentview">Deployment View</a>.</p>
-<h1><a name="subsystemview">Subsystem View</a></h1>
-<h2>WST Project</h2>
-
-<h3>Build and Test Subsystem</h3>
-<p>For completeness, I'll mention our build and test component, highly
-modeled after the base Eclipse build and test components.</p>
-<ul>
- <li>org.eclipse.wtp.releng</li>
-</ul>
-
-<h3>Common Subsystem</h3>
-<p>Components in this subsystem have no dependancies on other webtooling
-components and are not specific to web tooling functionality, but are
-needed by other web tooling components.
-<ul>
- <li>Common Component
- <ul>
- <li>Extensible Navigator</li>
- <li>Tabbed Property View</li>
- <li>Snippets View</li>
- <li>Extensible URI Resolver</li>
- </ul>
- </li>
- <li>Validation Framework Component</li>
- <li>Command Framework Component</li>
-</ul>
-
-<h3>Server Subsystem</h3>
-<ul>
- <li>Server Component</li>
- <li>Internet Component</li>
-</ul>
-<h3>Database Subsystem</h3>
-
-<p>Will be an update manager feature.</p>
-<ul>
- <li>RDB/SQL</li>
-</ul>
-<h3>XML Subsystem</h3>
-<p>Will be an update manager feature.</p>
-
-<ul>
- <li>XML Component</li>
- <li>Schema Component</li>
- <li>DTD Component</li>
- <li>SSE Component</li>
-</ul>
-
-<h3>Web Services Subsystem</h3>
-
-<ul>
- <li>WS Component</li>
- <li>WSDL Component</li>
- <li>WSI Component</li>
-</ul>
-
-<h3>Web Resources Subsystem</h3>
-
-<ul>
- <li>HTML Component</li>
- <li>CSS Component</li>
- <li>JavaScript Component</li>
-</ul>
-<h3>Generic Web Module Subsystem</h3>
-
-<ul>
- <li>Web Component</li>
-</ul>
-
-<h2>JST Project</h2>
-
-<h3>Server Subsystem</h3>
-
-<ul>
- <li>Server Component</li>
-</ul>
-
-<h3>JSP Resources Subsystem</h3>
-
-<p>Will be an update manager feature.</p>
-<ul>
- <li>JSP Component</li>
-</ul>
-
-
-<h3>Basic J2EE Subsystem</h3>
-
-<ul>
- <li>Servlet Component</li>
- <li>J2EE Component</li>
-</ul>
-
-<h3>Advanced J2EE Subsystem</h3>
-
-<ul>
- <li>EJB Component</li>
- <li>WS Component</li>
-</ul>
-
-<h1><a name="eclipsedependancies">Dependancies on the Eclipse Project</a></h1>
-<h2>Platform</h2>
-<p>All components pervasively required by both WST and JST. Note, there
-might be a few not required in short term, such as debug component, but
-long term it is easily imagined to be needed.</p>
-<h2>JDT</h2>
-<p>Not required by WST, but required by JST. Note: we don't rule out
-that we might require it someday in WST ... but no known cases
-currently.</p>
-<h2>PDE</h2>
-<p>Not required, though obviously want to verify co-existence.</p>
-<h2>WebDav</h2>
-<p>While not an official platform project or component, we do want to
-verify co-existence.</p>
-<h1><a name="toolsdependancies">Dependancies on Tools Projects</a></h1>
-<p>In addition to the base Eclipse, the following projects/packages are
-prerequisites of the Webtooling Platform. GEF, EMF, and XSD are
-pre-req'd by enough of WST to say its always required. The JEM package
-is only pre-req'd by JST.</p>
-<h2>EMF</h2>
-<p>EMF, <a href="http://www.eclipse.org/emf/" target="_top">Eclipse
-Modeling Framework</a>, is a way to define meta models, and then
-instantiate specific instances of those models. Its particularly famous
-for being useful to maintain models across multiple products, especially
-when the model may change from one release to another (the way that
-deployment descriptors and J2EE specs change from version to version.</p>
-<h2>XSD</h2>
-<p>The <a href="http://www.eclipse.org/xsd/" target="_top">XSD, XML
-Schema Infoset Model, Project</a> provides a model and API for querying
-detailed information about schemas and manipulating them. [Note:
-technically XSD Infoset is part of Technology Project, but is
-distributed with EMF]</p>
-<h2>GEF</h2>
-<p>GEF, <a href="http://www.eclipse.org/gef/" target="_top">Graphical
-Editing Framework</a>, is a framework "on top" of SWT that
-makes it easier to develop sophisticated, highly customizable user
-interfaces that go beyond typical widgets .</p>
-<h2>JEM Package</h2>
-<p>The JEM package, Java EMF Model, is actually part of the <a
- href="http://www.eclipse.org/vep/" target="_top">VE Project</a>. The VE
-team has recently made it available as separate download from their <a
- href="http://download.eclipse.org/tools/ve/downloads/drops/S-1.0M2-200407301410/index.html"
- target="_top">VE build pages</a>. In addition to allowing easier
-interaction with other EMF models, it also incorporates BeanInfo into
-its models (not just reflection). We use it in connection to our J2EE
-EMF-based models. From what I hear, there's no ISV documentation for
-this package, but the rose models that are used to create the meta model
-can be found in CVS on dev.eclipse.org<br />
-/home/tools<br />
-under<br />
-/org.eclipse.jem/rose<br />
-To load into rose (from workspace) you'd also have to have
-org.eclipse.emf.ecore in workspace, and define, in Rose, an EditPathMap
-of WorkspaceRoot as what ever your workspace root is on your filesystem
-(then it can find included files/models automatically).</p>
-
-<h2>Others</h2>
-<p><b>Xerces</b>. We currently ship Xerces binaries within plugin's
-runtimes that require them. [There's been some discussion that with OSGI
-classloading of PPS (Platform (bootloader), Pre-reqs, Self), that it
-should be easier to provide a common Xerces plugin, as long as there's
-no version requirements conflicts, and no custom class loaders involved,
-and appropriate factories used to "get" the specific parts of
-Xerces needed that are not part of the platforms runtime].</p>
-
-<h1><a name="relationtootherprojects">Relation to other Projects</a> and Products</h1>
-<h2>J2EE Servers</h2>
-<ul>
- <li>Apache Tomcat</li>
- <li>JBoss</li>
- <li>(Jonas)b </li>
-</ul>
-<h2>Database Servers</h2>
-<ul>
- <li>Apache Derby (Cloudscape)</li>
- <li>With adapters for other products as well, db2.iseries, db2.luw, db2.zseries, informix, oracle, sqlserver, sybase</li>
-</ul>
-
-<h1><a name="graphicalsummary">Summary in Graphical form</a></h1>
-<p>The following diagrams summarize the subsystem and relationships
-described above.</p>
-<p></p>
-<p><img src="images/wstandjstdependancies.png" width="867" height="454"
- border="2" /></p>
-<p><br />
-The darker shaded subsystems are accessible by end-users and other
-components via update manager.</p>
-<p><img src="images/wstsubsystems.png" width="606" height="450"
- border="2" /></p>
-<p><br />The darker shaded subsystem (orange) is accessible by end-users and other
-components via update manager.
-<br />The white subsytems indicate the "links" into the WST subsystem. The JDT and JEM components indicate two <br />components from other projects required in JST, but not required in WST.
-</p>
-<h1><img src="images/jstsubsystems.png" width="769" height="475"
- border="2" /><a name="deployrmentview"><br />
-Deployment View</a></h1>
-<p>This section makes explicit what is currently planned to be made available as deployable features via update manager. This is paritally driven by views expressed by community users, and partially dirven by the expressed needs of other projects. It may not be the perfect "slice and dice" of the whole package that would suit everyone, but the expecation is that other projects can always download more than they need, and pick and choose the exact components they want to re-distribute.</p>
-<p>All deployment features below will have a "binary" runtime
-version, and an SDK version, with all source and developer
-documentation. </p>
-<p>At the hightest level, is JST and WST seperately. (With JST requireing
-WST). </p>
-<p>Within JST, user's can choose all of JST, or JSP Subsystem. </p>
-<p>Within WST, users's can choose all of WST, or the XML Subsystem
-(includes Schema and DTD components), or the Data Subsystem </p>
-<p>Of Course, at any point of a decision, the choosen "subcomponent" will still "pull allong" all that its dependent on. </p>
-<p></p>
-</body>
-</html>
diff --git a/development/arch_and_design/ArchitectureOverviewInitial.html b/development/arch_and_design/ArchitectureOverviewInitial.html
deleted file mode 100644
index b0ef1f1..0000000
--- a/development/arch_and_design/ArchitectureOverviewInitial.html
+++ /dev/null
@@ -1,527 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1" ?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta name="GENERATOR" content="Pseudo WTP" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<link href="theme/default_style.css" rel="stylesheet" type="text/css" />
-<!--
-<link href="theme/Master.css" rel="stylesheet" type="text/css" />
--->
-<title>Eclipse WTP Architecture Overview</title>
-<style type="text/css">
-<!--
-dt {
- font-weight: bold
-}
--->
-</style>
-</head>
-<body>
-<div align="center">
-<h1>Eclipse Webtools Architecture Overview</h1>
-</div>
-
-<div align="center">
-<table border="1" cellpadding="10" height="50%" width="70%">
- <tbody>
- <tr align="left" valign="middle">
- <td valign="middle" align="left">
- <blockquote>
- <p><cite>The background and status of this document.</cite></p>
- <p><cite> Version 0.1 August 16, 2004. </cite></p>
- <p><cite>While this document is a work product of the <a
- href="#architecturegroup">WTP Architecture Group</a> I will have to take
- full responsibility for all the many errors and omissions it contains,
- but will give credit both to the Architecture Group and the many other
- teams for their many valuable contributions to it and the time they spend
- educating me.</cite></p>
- <p><cite>This first version of this document is being distributed now,
- even though still rough and incomplete (I'd guess about 50% incomplete), to get some community
- readership to determine if it represents a useful direction and if it
- should be continued. Feedback, questions, and comments can be made to
- the wtp-dev mailing list.</cite></p>
- <p>Thank you for your contributions, David Williams (david_williams@us.ibm.com)</p>
- </blockquote></td>
- </tr>
- </tbody>
-</table>
-</div>
-<h2>Purpose and Objectives</h2>
-
-
-<p>Given a heterogeneous group of people, companies, and contributions, it
-would be difficult for WTP to be easily "open" to a community without some
-overview of its architecture. The
-purpose of this document is to give a high-level view of the
-architecture that is implicit in most of the initial contributions. Over time, this document will capture the architecture of the Eclipse Web Tooling Platform. This document is not the Architectural Plan, as required by the <a
- href="http://www.eclipse.org/org/documents/Eclipse%20Development%20Process%202003_11_09%20FINAL.pdf">Eclipse
-Development Process</a> listed on the Eclipse <a
- href="http://www.eclipse.org/org/documents/main.html" target="_top">Governance</a> page. That Plan will be written later, but, hopefully, as an outgrowth of this docuent. </p>
-
-<p>This
-Overview documents the current and desired architecture of WTP
-as a whole -- that is, contributed components will (still) be expected to
-document their own architecture, designs, APIs, and how they fit in to
-overall architecture -- and, since it is a comunity based project, the level and timing of that documentation will vary greatly. </p>
-<p>
-The benefit of having an overall document is that it can capture things
-that are not captured by individual pieces: both across component relationships and
-also things which might seem unique when individual pieces are examined,
-but which are really common when the system is viewed as a whole.</p>
-
-<p>The
-primary reason for doing this work is to make it easier for others to
-contribute to WTP and to integrate with it. That is, it is to serve as
-something of a road map, guiding contributors and integrators on the
-most scenic areas of interest. It is definitely not intended to be a "how to" manual -- it won't give all the answers to specific questions (and actully in most cases not any of the answers to specific questions) -- but hopefully will make it easier to find where to look for the answers. Also, it is definitely not intended to be a
-return to centralized development practices, but simply to help guide
-decentralized development. To stretch a commonly used open source
-metaphor, the architecture document is to be more of architecture of a
-bazaar, rather than the architecture of a cathedral (and, to be
-explicit, the best bazaars do have some organization -- they are not
-just random anarchy!).</p>
-
-<p>A second reason for doing this work is to help keep track of holes or errors in
-current architecture -- or, stated another way, find things that are not
-architected, but merely implemented. </p>
-
-<p>
-This architecture document may summarize the
-extensible and pluggable areas where components can be easily changed or
-extended. But that's primarily documented component by component. </p>
-
-<p>It
-is hoped this document will also be useful as planning and requirements
-input, for example, if there are missing or redundant pieces, it would
-be easier to plan what to do about that, given some overall
-documentation, rather than trying to decide each individual case in
-isolation. Eventually, in the long run, hopefully it'll evolve to work in the opposite direction too, input from requirements and plannning can be used to modify this document and the architecture itself.</p>
-
-<p>This architecture document is expected to be a "living" document,
-updated at least every milestone both to remain "current" and to be
-improved with feedback from the community. It is also anticipated that
-people contributing to this document will be code-contributing members.... that
-is, its no ivory tower where work goes on in isolation!</p>
-
-<h2>Web Standard Tools vs. J2EE Standard Tools</h2>
-<p>Overall the project is "split" into Web Standard Tools (WST) and J2EE Standard Tools (JST), as is well described by the links from the description of the project <a
- href="http://www.eclipse.org/webtools/index.html" target="_top">Eclipse Web Tools
-Platform Project </a>.</p>
-<p>Architecturally, the J2EE components depend on the Web Standard components, but not vice versa. (That is, I should say this will be case, there's still some case of refactoring needed to have "perfect" separation).</p>
-<h2>Architecturally significant use cases</h2>
-<p>High level uses case are document here to give a high level idea of the what this overview is meant to cover.
-</p>
-<p>[4 to 6 more high level use cases to be added later.]</p>
-<ul>
- <li>Create a web application, including deployment descriptors, HTML, JSP, and
-Java files, and run them from the WTP-IDE on a local or remote test
-server.</li>
-</ul>
-
-<h2>Architectural Viewpoints</h2>
-<p>The architecture is described from several points of view. Each
-point of view highlights particular aspects of the system, and different
-readers may be interested in one view over others. Overall, though, this document focuses on documenting the "model-driven" architecture, meaning that the system is described in terms of the model objects, their properties, and how they interact with each other. For example, its not intended to document an editor for a web resource, but that fact that it can be modified by changing specific models is the architecturally important part. </p>
-
-<blockquote>
-<h3>Static Development system Viewpoint</h3>
-</blockquote>
-<blockquote>
-<p>This is the system as its "actively idle" ... that is, a
-developer in using it to create a web application, using editors,
-wizards, properties, etc. to create artifacts, but does not include
-actually running, debugging, deploying, or publishing anything.</p>
-</blockquote>
-
-<blockquote>
-<h3>Run/Debug Development viewpoint</h3>
-</blockquote>
-<blockquote>
-<p>This view point highlights those areas of the system that come into
-play while running or debugging on a test server, to test that the
-application works correctly.</p>
-</blockquote>
-<blockquote>
-<h3>Components view point</h3>
-</blockquote>
-
-<blockquote>
-<p>This view point shows the systems as "logical collections",
-typically "owned" by one team, typically in same geographical area.</p>
-</blockquote>
-
-<blockquote>
-<p>In addition to the logical grouping, the Components view point will
-mention significant supporting classes or pre-reqs which might not be
-obvious from the other view points.</p>
-</blockquote>
-<hr />
-<h2>Static Development system</h2>
-
-<h3>Server/Runtime target</h3>
-<blockquote>
-<p>The server/runtime target defines the properties and runtime class
-library of a particular server. These properties and runtime class
-library is used by the web project to know what's appropriate for that
-web project, given certain servers. </p>
-</blockquote>
-
-<blockquote>
-<p>This figure of a simplified view of the server target shows how its definition comes from an Eclipse Extension, but that a particular defined instance of a server would have extra info associated (and saved) with it, such as where the runtime jars are located on the local file system. The runtime jars are needed for "static development", but of course the "real" runtime jars are used when the server is ran. </p>
-<p><img title="Target Server Instance" src="images/server.png" width="566" height="246" name="ServerTargetInstance" alt="ServerTargetInstance"/></p>
-</blockquote>
-<h3>WebProject and Webnature</h3>
-
-<blockquote>
-<p>The WebProject and WebNature describes how and where various deployment artifacts (resources such as web.xml files, etc.) are stored, and other information that's important at "development time" such as the intended target server. </p>
-</blockquote>
-
-<blockquote>
-<p>Its important to note that the actual deployment descriptor for a web
-app, namely web.xml, is, in our system, conceptually just a serialized
-form of the web app model. This is a frequent pattern though out the framework. And, of course, the web.xml file is still standard, can still be deployed as usual, etc. Of course, there is occasions when there is extra information we'd like to keep track of due to being in an IDE enviroinment that is not really part of the standard deployment descriptor, so that is written to some meta data file associated with the project. These relationships are shown in the following figure. <br />
-<br />
-<img src="images/webAppAndServerTarget.png" width="645" height="246" />
-</p>
-</blockquote>
-<h3>Web resources (html, jsp, xml files, etc).</h3>
-
-<blockquote>
-<p>The main model object used to manipulate web resources are a
-StructuredModel and a StructuedDocument. XML, JSP, and HTML all have a
-special DOM Model associated with them. DTD and CSS have similar
-DOM-like models associated with them, but technically don't meet the DOM
-spec. (DTD is very close, CSS is more like a list of nodes, rather can a
-hierachey of nodes). The StructuredDocument is very similar to the
-IDocument interface, and just adds some specialized events to make
-incremental updates possible. The following figure shows these relationships as they might be while editing a web.xml resource.<br />
-<img src="images/ModelEditing.png" width="668" height="236" />
-<br />
-</p>
-</blockquote>
-<blockquote><p></p>
-<p>I hope the careful reader is wondering what happens if the web app model and the DOM Model both want to update the web.xml text. There's certainly the usual "resource changed" listeners that are common in Eclipse to help things keep in synch, but sometimes changes are desired from one source or the other without actually saving the resource. This leads to another typcial pattern used in our systems, that of model-to-model adapters, as shown in the following figure. <img src="images/modelToModel.png" width="766" height="383" />
-</p>
-</blockquote>
-<h3>Database Model</h3>
-<blockquote>
-<p>[more to be provided later]</p>
-</blockquote>
-<blockquote>
-<p>Models for databases, connections, tables, etc.</p>
-</blockquote>
-<h3>Database Queries</h3>
-<blockquote>
-<p>[more to be provided later]</p>
-</blockquote>
-<blockquote>
-<p>SQL Model based on SQL-99 Standard. Uses/depends on EMF.</p>
-</blockquote>
-<h3>WebServices</h3>
-<blockquote>
-<p>[more to be provided later]</p>
-</blockquote><hr />
-<h2>Run/Debug Development viewpoint</h2>
-
-<blockquote>
-<p><b>[Obviously ... this section is very incomplete .... more to come ... if deemed important, and if there's time, which I only say since it could be one of the more complicated to document usefully]</b></p>
-</blockquote>
-<h4>Server (proxy)</h4>
-<blockquote>
-<p>This server object differs some from the server/runtime target, in
-that it actually controls the "running" on the server. In the
-standard (contributed) case, this server depends on a
-"standard" Eclipse project layout. (A future work item is to
-allow more flexible project structures.)</p>
-</blockquote>
-<h4>TCPIP Monitor</h4>
-<blockquote>
-<p>Its probably worth noting that the TCPIP monitor actually setups a
-"proxy" server, to monitor traffic to and from the test server
-(it can not monitor traffic from any arbitrary server)..</p>
-</blockquote>
-<hr />
-<h2>Components view point</h2>
-<p>[Editors note: it is in this seciton I'd like to (in the long run) have links to the specfic components design and API documentation.]</p>
-<p>Defintion of terms [open to debate]: I've tried to use <i>Subsystem</i> which seems the term the <a
- href="http://www.eclipse.org/org/documents/Eclipse%20Development%20Process%202003_11_09%20FINAL.pdf">Eclipse
-Development Process</a> uses to denote a large, logically related set of components, which are fairly ndependent of other subsystems, at least conceptually. I've used the term <i>Component</i> to mean that part of as subsystem that conceptually has meaning by itself, and which would be recognized or seen by an end-user as "part of the system" and identifiable with some standard or specification. Sub-component is similar, but maybe highly related to other components (due to re-use) but which is typically transparent to the end-user. </p>
-<h2>Subsystem: Server-tools</h2>
-
-
-
-<blockquote>
-<h4>WST Component: Server Framework</h4>
-</blockquote><blockquote>
-<p>This framework handles definition of any (or, at least many) servers
-and server types, but the actual server support is provided in
-subcomponents.</p>
-</blockquote>
-
-
-
-<blockquote>
-<h4>WST Component HTTP standard server tools</h4>
-</blockquote>
-<blockquote>
-<h4>WST Component - Internet (Built in Browser, tcpip montior,
-Proxy preferenes)</h4>
-</blockquote>
-<blockquote>
-<h4>JST Component tomcat standard server tools</h4>
-</blockquote>
-
-<h2>Subsystem: Web Resources </h2>
-
-<blockquote>
-<p>This framework is used for deployment descriptors (XML source) [Note:
-no special deployment editors are in current contribution, so they are
-just treated as xml files. And, of course, true web resources (XML,
-HTML, XHTML, CSS, JavaScript). </p>
-</blockquote>
-<blockquote>
-<h4>WST Component Structured Source Editors framework</h4>
-</blockquote>
-<blockquote>
-<p>The primary purpose of extended the base text editing support is to
-provide specialized models and events which can lead to better
-performance, and easier interaction between other models. In particular,
-its thought the most used model in this framework will be the DOM model,
-which implements DOM Level 2 APIs but is a "custom"
-implementation, which can 1. handle ill formed markup (as it always is
-during editing) 2. can be done incrementally (as opposed to
-"batch" processing, as most DOM parsers do), and 3. provides a
-few "extra" APIs that make the DOM more suitable for use in
-tools. Note: the JavaScript editor does not make use of "Structured
-Source Editor" models and there is no "JavaScript" model
-to interact with ... that interaction is all done at a document level.</p>
-</blockquote>
-
-
-
-<blockquote>
-<h4>JST Component JSPs (editing, menus, wizards, indexing, refactoroing, etc.)</h4>
-</blockquote>
-<blockquote>
-<p>In our framework, JSP's are treated as a "marked up"
-document. Technically this is not required by the JSP Specification, but
-in practice seems to be the common (maybe only!) case. This allows
-interaction with the DOM model of the JSP to modify it, search it, etc.
-</p>
-</blockquote>
-<blockquote>
-<h4>WTP Component HTML (editing, menus, wizards, indexing,
-refactoroing, etc.)</h4>
-</blockquote>
-
-<blockquote>
-<h4>WTP Component CSS (editing, menus, wizards, indexing,
-refactoroing, etc.)</h4>
-</blockquote>
-<blockquote>
-<h4>WTP Component JavaScript (editing, menus)</h4>
-</blockquote>
-<blockquote>
-<h4>WST Subcomponent XML base tools (URI Resolvers, ContentModels, XML and Schema Validation)</h4>
-</blockquote>
-
-<blockquote>
-<p>Many functions relay on some "low level"
-models, which are important enough to call out for special attention.
-URI Resolvers are critical in correctly "finding" related
-resources in a web project, and "content models" are used to
-define the "legal content" of XML, Schema, TLDs, HTML, and JSPs.
-These content models also have behavior and extension points to allow "extra data" to be
-associated, such as the information used in "hover help".
-Includes URI Resolvers, ContentModel Interface (and implementation for
-for DTDs and Schemas). This project subcomonent also provides project-based validation of XML files. -- One item for the future is that this component may relay on Xerces, so make use of its XMI interace, to provided better information in validation errors and warnings. The Xerces dependancy is currently intentionally an "internal" dependancy, not shared amount the project. This subcompent has dependancy on EMF.</p>
-</blockquote>
-
-
-
-<h2>SubSystem: Web Applications and Projects</h2>
-
-
-
-<blockquote>
-<h4>WST Subcomponent Common Archive Framework</h4>
-</blockquote>
-
-
-
-<blockquote>
-<blockquote>
-<p>Handles loading/storing archives using pluggable strategies</p>
-</blockquote>
-</blockquote>
-
-<blockquote>
-<h4>WST Subcomponent Project Support</h4>
-</blockquote>
-
-<blockquote>
-<blockquote>
-<p>Import/Export/Creation Support</p>
-</blockquote>
-</blockquote>
-
-
-<blockquote>
-<h4>WST Subcomponent Common Navigator</h4>
-</blockquote>
-
-
-
-<blockquote>
-<blockquote>
-<p>Extensible framework that provides content to resources in workbench</p>
-</blockquote>
-</blockquote>
-
-
-
-
-
-<h2>SubSystem: J2EE Applications and Projects</h2>
-
-
-
-
-<blockquote>
-<h4>JST Subcomponent J2EE Resources</h4>
-</blockquote>
-
-
-
-<blockquote>
-<blockquote>
-<p>EMF based models</p>
-</blockquote>
-<blockquote>
-<p>Also depends on JEM package.</p>
-</blockquote>
-</blockquote>
-
-
-
-<blockquote>
-<blockquote>
-<p>Provides specialized J2EE EMF Resource handling</p>
-</blockquote>
-</blockquote>
-
-
-
-
-<h2>SubSystem: Database</h2>
-<blockquote>
-<h4>Component: Data Tools</h4>
-</blockquote>
-
-<blockquote>
-<h4>Component: SQL'99 Tools and models</h4>
-</blockquote>
-<h2>SubSystem: Webservices</h2>
-<blockquote>
-<h4>WTP Component WSI</h4>
-</blockquote>
-<blockquote>
-<h4>WTP Component WSDL</h4>
-</blockquote>
-<blockquote>
-<h4>WTP Component WS Models (soap, uddi, wsil)</h4>
-</blockquote>
-
-<h2>SubSystem: XML and Schemas</h2>
-<blockquote>
-<h4>WTP Component: XML Validation</h4>
-<h4>WTP Component: XML/Schema Generation</h4>
-<p>Provides "extras" to standard source edinting, the ability to generate and xml instance file from a DTD or Schema is one of the coolist. </p>
-</blockquote>
-<h2>SubSystem: Web Tooling Common Base</h2>
-
-
-
-<blockquote>
-<p>These are tools and frameworks required by multiple higher level
-components, which must be at low level in the stack of components to
-be shared, or, with careful review, common utilities.</p>
-</blockquote>
-
-
-
-<blockquote>
-<h4>WTP Component - Validation Framework</h4>
-</blockquote>
-
-
-
-<blockquote>
-<blockquote>
-<p>Special Eclipse builder, that allows validation of resources.
-Typically, higher level components provide extensions to this framework
-to handle validating their particular models and resources, such as XML,
-EJBs, etc.</p>
-</blockquote>
-</blockquote>
-<h1>Pointers to prerequiste projects</h1>
-<p>In addition to the base Eclipse, the following projects/packages are prerequistes of the Webtooling Platform. </p>
-<h2>EMF</h2>
-<p>EMF, <a href="http://www.eclipse.org/emf/" target="_top">Eclipse Modeling Framework</a>, is a way to define meta models, and then instantiate specific instances of those models. Its particularly famous for being useful to maintain models across multiple products, espcially when the model may change from one release to another (the way that deployment descriptors and J2EE specs change from verison to version. </p>
-<h2>GEF</h2>
-<p>GEF, <a href="http://www.eclipse.org/gef/" target="_top">Graphical Editing
-Framework</a>, is a framework "on top" of SWT that makes it easier to develop sophistocated, highly customizable user interfaces that go beyond typical widgets (I believe we only use this in our snippets view, subuilder, and schema editor -- though there's been some discussions of using it with XML editor in the future). .</p>
-<h2>JEM Package</h2>
-<p>The JEM package, Java EMF Model, is actually part of the <a
- href="http://www.eclipse.org/vep/" target="_top">VE Project</a>. The VE team has recently made it available as seperate download from their <a
- href="http://download.eclipse.org/tools/ve/downloads/drops/S-1.0M2-200407301410/index.html" target="_top">VE
-build pages</a>. In addition to allowing easier interaction with other EMF models, it also incorporates BeanInfo into its models (not just reflection). We use it in connection to our J2EE EMF-based models. From what I hear, there's no ISV documentation for this package, but the rose models that are used to create the meta model can be found in CVS on dev.eclipse.org<br />/home/tools<br />under<br />/org.eclipse.jem/rose<br />To load into rose (from workspace) you'd also have to have org.eclipse.emf.ecore in workspace, and define, in Rose, an EditPathMap of WorkspaceRoot as what ever your workspace root is on your filesystem (then it can find included files/models automatically). </p>
-<h2>XSD</h2>
-<p>The <a href="http://www.eclipse.org/xsd/" target="_top">XSD, XML Schema Infoset
-Model, Project</a> provides a model and API for querying detailed information about schemas and manipulating them. </p>
-<h2>Others</h2>
-<p>[Eventually, we may document here certain packages we use and ship internally, such as Xerces, just to help avoid duplicating such internal packages.]</p>
-<h1>Known Architectural/Design Issues</h1>
-
-
-
-<p>This section is just to be explicit about architectural issues
-that are known and which the architecture committee will be discussing various solutions to. </p>
-
-
-
-<p>Note always a clear seperation between "model" and "view" objects ... yes, we confess, occasionally, given some bit of a codes history or deadline driven design, our model/view seperation is less than perfect (but don't get me wrong, its pretty good!). </p>
-<p>Multiple java models (JDT and JEM).
- Maybe not a real issue per se,
-but not sure weve documented differences between them, when to use one
-vs. the other, etc.)</p>
-
-
-
-<p>Multiple operation/command frameworks are in
-initial contribution need to resolve to one and/or coordinate with
-base Eclipse plans.</p>
-
-
-<p>Currently "meta data" or "extra information" is stored inconsistently
-(and hard to find/understand). Sometimes in (several) files with no names,
-sometimes as OSGI preferences, but theres no framework for common,
-easy access.</p>
-
-
-<p>There are currently two (or more!) frameworks for providing URI resolution. Some work is needed to determine if the Extensible URI Resolution framework can be used to replace all of them. </p>
-<hr />
-<dl>
- <dt><a name="architecturegroup">WTP Architecture Group</a></dt>
- <dd>David Williams, IBM</dd>
- <dd>Chuck Bridgham, IBM</dd>
- <dd>Erich Gamma, IBM</dd>
- <dd>Henrik Lindberg, Frameworx</dd>
- <dd>Naci Dai, Eteration</dd>
-</dl>
-<p></p>
-
-</body>
-</html>
diff --git a/development/arch_and_design/M4ArchCheckPoint.html b/development/arch_and_design/M4ArchCheckPoint.html
deleted file mode 100644
index 943d930..0000000
--- a/development/arch_and_design/M4ArchCheckPoint.html
+++ /dev/null
@@ -1,636 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../webtools/wtp.css" type="text/css">
-<title>Preliminary Architectural Assessment</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">WTP Architectural Assessment at M4</font>
-<br>
-<font class="indexsub">Preliminary Architectural Assessment</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<table border="1" cellpadding="10" height="50%" width="70%">
-
-<tbody>
-
-<tr align="left" valign="middle">
-
-<td valign="middle" align="left">
-
-<blockquote style="">
-
-<p>
-
-<cite>
- The background and status of this
- document:
- </cite>
-
-</p>
-
-<p>
-
-<cite>
- 4/26/05 - this is just a preliminary
- rough draft of some of my initial
- personal observations of where we
- are architecturally at M4.
- <br>
- Updated based on review meetings
- held 5/3.
- <br>
-
-<br>
- Comments to wtp-dev list are
- welcome.
- </cite>
-
-</p>
-
-<p>
-
-<cite>Version 0.3 May 11, 2005.</cite>
-
-</p>
-
-<p>
-
-<cite>David Williams</cite>
-
-</p>
-
-</blockquote>
-
-</td>
-
-</tr>
-
-</tbody>
-
-</table>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">General impressions of status</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- In "quick assessments" such as this one, its easy to seem critical, and
- hard to write all the good and complimentary things I see in
- WTP, so I hope this general statement suffices. There are a
- lot of good things, tremendous progress has been made, and
- all teams are working very hard to provide good function and
- true platform quality code and APIs. Its hard to ask for
- more than that, but below are some items that could use more
- work before Release 1.0 (and this is just in my humble,
- off hand impressions, so I may have missed things, or may have
- misinterpreted some things). I intend these remarks only as
- constructive suggestions or questions to make WTP even better than
- it is.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>State of plugin structure</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>Overall, We still have too many plugins.</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>
- Many divisions still determined by "function" rather
- than component.
- </li>
-
-<li>
- Many divisions still determined by "team" or "site"
- rather than component.
- </li>
-
-
-<li>
- many appear to be used by only one other plugin, so
- why separate? (there's even one not pre-req'd by any
- plugin .. pure extension).
- </li>
-
-
-<li>
- Many "validation" ones are separate ... is there a
- reason for this? [AR] wsi command line validation is
- required. [DW] but does this require separate
- plugins?
- </li>
-
-
-<li>
- Many "annotation" ones are separate ... is there a
- reason for this?
- </li>
-
-
-<li>
- Some need to renamed to make obvious "core vs. ui"
- </li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>
- Need more granular feature definitions (both for end
- users, and products building on WTP that may not use all
- of WTP).
- </td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>
- General agreement should be primarily from "end user
- point of view".
- </li>
-
-<li>
- Should be based on subsystems, as defined below.
- </li>
-
-<li>
- Still need to investigate model vs. UI packaging.
- </li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>
- Need to define and set proper expectation and definition
- of "internal.provisional".
- </td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- they are, first and foremost, 'internal', subject to
- change, even removal. there is no implied support. They
- have been named "provisional" as a signal that we'd like
- review comments and statements of need from community
- for future releases. All cases of 'internal' are so
- named so that clients who use them assume the risk of
- re-working their code in future versions. We would like
- it if when any internal package found to be needed,
- feature requests were opened so appropriate solutions
- could be designed to satisfy needs of community (and
- still provide platform quality APIs).
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Note: in M4, much effort was made to assess what could
- be API, and what could not. In some cases, the "could
- not" cases did not get renamed in time for M4. Will do
- early in M5 cycle.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>We have no "friend" APIs defined for WTP.</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- 'Friend' meaning ok for some "outside" component to use,
- while still inside project. We could not meaningful do
- this for release 1. This is something we should do for
- future releases.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>
- API violations in our use of base Eclipse and pre-reqs?
- </td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- This is currently a fairly large "unknown" and we need
- improved reports (and component definitions from base
- Eclipse). I suspect we have a lot. I suspect some can be
- "cleaned up" and some can not (and will need more work
- with base to know if "future requirement" or if we are
- doing something wrong.)
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Summary of components and API status</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- For those items below marked
- <b>"ready for review"</b>
- I have opened bugzilla meta-bugs to encourage explicit comments
- from community and clients specifically during M5 cycle
- review. These reviews are not so much for feature requests (those
- could be seperate bugzillas) but for things like if JavaDoc is wrong or
- in adequeate, if something appears not to be evolvable, or even if
- the design or problem to solve seems unclear so that you could not
- write to the APIs. Or ... you could include a few compliments :)
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Note: following "subsystem" don't match Arch. Doc.
- exactly (it needs to be updated), but concept is the same. Features,
- dependencies, etc., still flow from the subsystem
- definitions.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>Common Subsystem/Feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>Common Component</li>
-
-<ul>
-
-<li>
- Extensible Navigator --> internalProvisional,
- moving to base 3.2
- </li>
-
-<li>
- Tabbed Property View --> internalProvisional,
- moving to base 3.2
- </li>
-
-<li>
- Snippets View --> internalProvisional. Belongs
- here in WTP. Needs more work to better integrate
- with Eclipse Templates (if possible)
- </li>
-
-<li>
- Extensible URI Resolver --> internalProvisional.
- </li>
-
-<p>
- Appears not to handle several use-cases,
- question is if it ever could. Some question on
- OASIS standards.
- </p>
-
-
-<li>common frameworks</li>
-
-<ul>
-
-<li>
- data operations - IDataModel -
- <b>ready for review.</b>
- <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=94889">94889</a>
-
-</li>
-
-<p>
- [need review from Chris B., to see if he
- could move to it post release 1.0]
- </p>
-
-<li>data wizards - provisional</li>
-
-</ul>
-
-</ul>
-
-<li>
- Validation Framework Component -->
- internalProvisional.
- </li>
-
-<p>
- good client design and requirements sessions, but
- may be trying to cover too much.
- </p>
-
-
-<li>Command Framework Component</li>
-
-<p>
- I don't think should be a "component". (since we
- don't want to introduce yet another 'command' or
- 'operation' framework). I don't think it should have
- provisional API. Could it be integrated with
- "DataOperations"? There is fundamental question if
- "running headless eclipse application" suffices, or
- if we really need to provide an API that does not
- pre-req Eclipse at all.
- </p>
-
-
-<li>
- common.componentcore (needed for flexible projects)
- -
- <b>Ready for Review</b>
- <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=94890">94890</a>
-
-
-</li>
-
-<p>
- But pure resource part rightfully belongs in base.
- Need better distinction between flexible project
- consumers, and Flexible project providers (those
- that define what the flexible project is). (former
- might be evolvable API, but not sure later could be
- without being in proper project). My advice is to
- publish as internal .provisional ... but don't mind
- pushing forward with review, since part of it
- belongs in base, since not sure if it works well
- with base's "logical resources". since providing
- team same as client team, since base is looking at
- "non-local resources" in 3.2 ... all of which could
- impact design. especially need review from base to
- determine if evolvable with their plans.
- </p>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>Server Subsystem/Feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>
- Server Component --
- <b>Ready for Review</b>
- <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=94891">94891</a>
-
-
-</li>
-
-<p>
- some review already indicated some issues to resolve
- especially with server providers
- </p>
-
-<li>Internet Component</li>
-
-<ul>
-
-<li>
- browser/launch URL API --> moved to Eclipse 3.1.
- </li>
-
-<li>Pref. --> 3.2</li>
-
-<li>
- Monitor --> internal.provisional, pending post
- 1.0 review with TPTP
- </li>
-
-</ul>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>Database Subsystem/Feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>
- DB/SQL - internal, not API due to probable DTP
- project merge
- </li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>XML Subsystem/Feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>
- XML Component - some internal provisional .. need
- better design documents .. more refactoring
- </li>
-
-<li>
- Schema Component - some internal provisional .. need
- better design documents .. more refactoring
- </li>
-
-<li>
- DTD Component some minimal internal provisional ..
- need better design documents .. more refactoring
- </li>
-
-<li>
- SSE Component some internal provisional .. need
- better design documents ... .. more refactoring,
- especially need better distinction between language
- consumer APIs and language provider APIs.
- </li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>Web Services Subsystem/Feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>WS Component ... some internal provisional</li>
-
-<li>
- WSDL Component.
- <b>Ready For Review</b>
- <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=94892">94892</a>
-
- . WSDL Spec Model API (see "EMF Models" notes).
- </li>
-
-<li>
- WSI Component ... ? some API (provisional?) from
- WSTV project ?
- </li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>Web Resources Subsystem/Feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>
- HTML Component .. some internal provisional .. need
- better design documents
- </li>
-
-<li>
- CSS Component ... some internal provisional .. need
- better design documents
- </li>
-
-<li>
- JavaScript Component some minimal internal
- provisional .. need better design documents
- </li>
-
-<li>
- Web Project Component - no api, HTML Web Project
- </li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>JST Server Subsystem/Feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>
- Server Component -
- <b>Ready For Review</b>
- <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=94893">94893</a>
-
-</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>J2EE Web Subsystem/Feature (WAR)</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>
- J2EE Core Web Model Component [Issue: not currently
- packaged this way]
- <b>Ready For Review</b>
- <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=94887">94887</a>
- (see "EMF Models" notes).
- </li>
-
-<li>
- Servlet Component/J2EEWebProject ... some API,
- create web component API
- </li>
-
-<li>
- JSP Component ... some internal provisional .. need
- better design documents
- </li>
-
-<li>WS Web Component (JAXRPC)</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>
- J2EE Enterprise Subsystem/Feature (EARs, EJBJar,
- EJBClientJar, RARs)
- </h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>
- J2EE Core Enterprise Model Component [Issue: not
- currently packaged this way]
- <b>Ready For Review</b>
- <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=94887">94887</a>
- (see "EMF Models" notes).
- </li>
-
-<li>EJB Component</li>
-
-<li>WS Component</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Note: EMF Models for J2EE and WSDL have expressed the
- primary API part of their models is intended to be the
- interfaces defined by respective specifications. But
- general consensus in 5/3 review meeting that its "ok to
- assume EMF model" is part of the API. Still, components
- encouraged to "spec" how generated, intended use, etc.
- </p>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/development/arch_and_design/M4ArchCheckPoint.xml b/development/arch_and_design/M4ArchCheckPoint.xml
deleted file mode 100644
index 0ea9bd7..0000000
--- a/development/arch_and_design/M4ArchCheckPoint.xml
+++ /dev/null
@@ -1,420 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?xml-stylesheet type="text/xsl" href="../../wtp.xsl"?>
-<html>
- <head>
- <meta name="root" content="../../.." />
- <title>Preliminary Architectural Assessment</title>
- </head>
- <body>
- <h1>WTP Architectural Assessment at M4</h1>
- <table border="1" cellpadding="10" height="50%" width="70%">
- <tbody>
- <tr align="left" valign="middle">
- <td valign="middle" align="left">
- <blockquote style="">
- <p>
- <cite>
- The background and status of this
- document:
- </cite>
- </p>
- <p>
- <cite>
- 4/26/05 - this is just a preliminary
- rough draft of some of my initial
- personal observations of where we
- are architecturally at M4.
- <br />
- Updated based on review meetings
- held 5/3.
- <br />
- <br />
- Comments to wtp-dev list are
- welcome.
- </cite>
- </p>
- <p>
- <cite>Version 0.3 May 11, 2005.</cite>
- </p>
- <p>
- <cite>David Williams</cite>
- </p>
- </blockquote>
- </td>
- </tr>
- </tbody>
- </table>
-
- <h2>General impressions of status</h2>
-
- <p>
- In "quick assessments" such as this one, its easy to seem critical, and
- hard to write all the good and complimentary things I see in
- WTP, so I hope this general statement suffices. There are a
- lot of good things, tremendous progress has been made, and
- all teams are working very hard to provide good function and
- true platform quality code and APIs. Its hard to ask for
- more than that, but below are some items that could use more
- work before Release 1.0 (and this is just in my humble,
- off hand impressions, so I may have missed things, or may have
- misinterpreted some things). I intend these remarks only as
- constructive suggestions or questions to make WTP even better than
- it is.
- </p>
-
- <h3>State of plugin structure</h3>
- <p>Overall, We still have too many plugins.</p>
- <ul>
- <li>
- Many divisions still determined by "function" rather
- than component.
- </li>
- <li>
- Many divisions still determined by "team" or "site"
- rather than component.
- </li>
-
- <li>
- many appear to be used by only one other plugin, so
- why separate? (there's even one not pre-req'd by any
- plugin .. pure extension).
- </li>
-
- <li>
- Many "validation" ones are separate ... is there a
- reason for this? [AR] wsi command line validation is
- required. [DW] but does this require separate
- plugins?
- </li>
-
- <li>
- Many "annotation" ones are separate ... is there a
- reason for this?
- </li>
-
- <li>
- Some need to renamed to make obvious "core vs. ui"
- </li>
- </ul>
-
- <h3>
- Need more granular feature definitions (both for end
- users, and products building on WTP that may not use all
- of WTP).
- </h3>
- <ul>
- <li>
- General agreement should be primarily from "end user
- point of view".
- </li>
- <li>
- Should be based on subsystems, as defined below.
- </li>
- <li>
- Still need to investigate model vs. UI packaging.
- </li>
- </ul>
-
-
- <h3>
- Need to define and set proper expectation and definition
- of "internal.provisional".
- </h3>
- <p>
- they are, first and foremost, 'internal', subject to
- change, even removal. there is no implied support. They
- have been named "provisional" as a signal that we'd like
- review comments and statements of need from community
- for future releases. All cases of 'internal' are so
- named so that clients who use them assume the risk of
- re-working their code in future versions. We would like
- it if when any internal package found to be needed,
- feature requests were opened so appropriate solutions
- could be designed to satisfy needs of community (and
- still provide platform quality APIs).
- </p>
- <p>
- Note: in M4, much effort was made to assess what could
- be API, and what could not. In some cases, the "could
- not" cases did not get renamed in time for M4. Will do
- early in M5 cycle.
- </p>
-
- <h3>We have no "friend" APIs defined for WTP.</h3>
- <p>
- 'Friend' meaning ok for some "outside" component to use,
- while still inside project. We could not meaningful do
- this for release 1. This is something we should do for
- future releases.
- </p>
-
- <h3>
- API violations in our use of base Eclipse and pre-reqs?
- </h3>
- <p>
- This is currently a fairly large "unknown" and we need
- improved reports (and component definitions from base
- Eclipse). I suspect we have a lot. I suspect some can be
- "cleaned up" and some can not (and will need more work
- with base to know if "future requirement" or if we are
- doing something wrong.)
- </p>
-
- <h2>Summary of components and API status</h2>
-
- <p>
- For those items below marked
- <b>"ready for review"</b>
- I have opened bugzilla meta-bugs to encourage explicit comments
- from community and clients specifically during M5 cycle
- review. These reviews are not so much for feature requests (those
- could be seperate bugzillas) but for things like if JavaDoc is wrong or
- in adequeate, if something appears not to be evolvable, or even if
- the design or problem to solve seems unclear so that you could not
- write to the APIs. Or ... you could include a few compliments :)
- </p>
-
- <p>
- Note: following "subsystem" don't match Arch. Doc.
- exactly (it needs to be updated), but concept is the same. Features,
- dependencies, etc., still flow from the subsystem
- definitions.
- </p>
-
-
-
- <h4>Common Subsystem/Feature</h4>
-
- <ul>
- <li>Common Component</li>
- <ul>
- <li>
- Extensible Navigator --> internalProvisional,
- moving to base 3.2
- </li>
- <li>
- Tabbed Property View --> internalProvisional,
- moving to base 3.2
- </li>
- <li>
- Snippets View --> internalProvisional. Belongs
- here in WTP. Needs more work to better integrate
- with Eclipse Templates (if possible)
- </li>
- <li>
- Extensible URI Resolver --> internalProvisional.
- </li>
- <p>
- Appears not to handle several use-cases,
- question is if it ever could. Some question on
- OASIS standards.
- </p>
-
- <li>common frameworks</li>
- <ul>
- <li>
- data operations - IDataModel -
- <b>ready for review.</b>
- <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=94889">94889</a>
- </li>
- <p>
- [need review from Chris B., to see if he
- could move to it post release 1.0]
- </p>
- <li>data wizards - provisional</li>
- </ul>
- </ul>
- <li>
- Validation Framework Component -->
- internalProvisional.
- </li>
- <p>
- good client design and requirements sessions, but
- may be trying to cover too much.
- </p>
-
- <li>Command Framework Component</li>
- <p>
- I don't think should be a "component". (since we
- don't want to introduce yet another 'command' or
- 'operation' framework). I don't think it should have
- provisional API. Could it be integrated with
- "DataOperations"? There is fundamental question if
- "running headless eclipse application" suffices, or
- if we really need to provide an API that does not
- pre-req Eclipse at all.
- </p>
-
- <li>
- common.componentcore (needed for flexible projects)
- -
- <b>Ready for Review</b>
- <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=94890">94890</a>
-
- </li>
- <p>
- But pure resource part rightfully belongs in base.
- Need better distinction between flexible project
- consumers, and Flexible project providers (those
- that define what the flexible project is). (former
- might be evolvable API, but not sure later could be
- without being in proper project). My advice is to
- publish as internal .provisional ... but don't mind
- pushing forward with review, since part of it
- belongs in base, since not sure if it works well
- with base's "logical resources". since providing
- team same as client team, since base is looking at
- "non-local resources" in 3.2 ... all of which could
- impact design. especially need review from base to
- determine if evolvable with their plans.
- </p>
- </ul>
-
- <h4>Server Subsystem/Feature</h4>
- <ul>
- <li>
- Server Component --
- <b>Ready for Review</b>
- <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=94891">94891</a>
-
- </li>
- <p>
- some review already indicated some issues to resolve
- especially with server providers
- </p>
- <li>Internet Component</li>
- <ul>
- <li>
- browser/launch URL API --> moved to Eclipse 3.1.
- </li>
- <li>Pref. --> 3.2</li>
- <li>
- Monitor --> internal.provisional, pending post
- 1.0 review with TPTP
- </li>
- </ul>
- </ul>
-
- <h4>Database Subsystem/Feature</h4>
- <ul>
- <li>
- DB/SQL - internal, not API due to probable DTP
- project merge
- </li>
- </ul>
- <h4>XML Subsystem/Feature</h4>
- <ul>
- <li>
- XML Component - some internal provisional .. need
- better design documents .. more refactoring
- </li>
- <li>
- Schema Component - some internal provisional .. need
- better design documents .. more refactoring
- </li>
- <li>
- DTD Component some minimal internal provisional ..
- need better design documents .. more refactoring
- </li>
- <li>
- SSE Component some internal provisional .. need
- better design documents ... .. more refactoring,
- especially need better distinction between language
- consumer APIs and language provider APIs.
- </li>
- </ul>
- <h4>Web Services Subsystem/Feature</h4>
- <ul>
- <li>WS Component ... some internal provisional</li>
- <li>
- WSDL Component.
- <b>Ready For Review</b>
- <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=94892">94892</a>
-
- . WSDL Spec Model API (see "EMF Models" notes).
- </li>
- <li>
- WSI Component ... ? some API (provisional?) from
- WSTV project ?
- </li>
- </ul>
- <h4>Web Resources Subsystem/Feature</h4>
- <ul>
- <li>
- HTML Component .. some internal provisional .. need
- better design documents
- </li>
- <li>
- CSS Component ... some internal provisional .. need
- better design documents
- </li>
- <li>
- JavaScript Component some minimal internal
- provisional .. need better design documents
- </li>
- <li>
- Web Project Component - no api, HTML Web Project
- </li>
- </ul>
-
-
- <h4>JST Server Subsystem/Feature</h4>
- <ul>
- <li>
- Server Component -
- <b>Ready For Review</b>
- <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=94893">94893</a>
- </li>
- </ul>
-
-
- <h4>J2EE Web Subsystem/Feature (WAR)</h4>
- <ul>
- <li>
- J2EE Core Web Model Component [Issue: not currently
- packaged this way]
- <b>Ready For Review</b>
- <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=94887">94887</a>
- (see "EMF Models" notes).
- </li>
- <li>
- Servlet Component/J2EEWebProject ... some API,
- create web component API
- </li>
- <li>
- JSP Component ... some internal provisional .. need
- better design documents
- </li>
- <li>WS Web Component (JAXRPC)</li>
- </ul>
- <h4>
- J2EE Enterprise Subsystem/Feature (EARs, EJBJar,
- EJBClientJar, RARs)
- </h4>
- <ul>
- <li>
- J2EE Core Enterprise Model Component [Issue: not
- currently packaged this way]
- <b>Ready For Review</b>
- <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=94887">94887</a>
- (see "EMF Models" notes).
- </li>
- <li>EJB Component</li>
- <li>WS Component</li>
- </ul>
-
-
- <p>
- Note: EMF Models for J2EE and WSDL have expressed the
- primary API part of their models is intended to be the
- interfaces defined by respective specifications. But
- general consensus in 5/3 review meeting that its "ok to
- assume EMF model" is part of the API. Still, components
- encouraged to "spec" how generated, intended use, etc.
- </p>
- </body>
-</html>
-
-
-
-
diff --git a/development/arch_and_design/arch_page.html b/development/arch_and_design/arch_page.html
deleted file mode 100644
index dff22ee..0000000
--- a/development/arch_and_design/arch_page.html
+++ /dev/null
@@ -1,331 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../webtools/wtp.css" type="text/css">
-<title>Architecture Group Page</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">WTP Architecture Group Page</font>
-<br>
-<font class="indexsub">Architecture Group Page</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Architecture Documents</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><a href="subsystems/SubsystemsAndFeatures.html">
- Proposed Architecture Document (10/09/2005)
- </a></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><a href="http://www.eclipse.org/org/councils/AC/wtpsnapshot/wtp_project_architecture.html">
- Current Architecture Document (2/15/2005)
- </a></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><a href="ArchitectureOverview.html">
- Previous Architecture Document (12/2/2004)
- </a></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><a href="ArchitectureOverviewInitial.html">
- Previous Architecture Document (8/16/2004)
- </a></td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Assessments</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><a href="M4ArchCheckPoint.html">
- Overall Architectural Assessment at M4 (5/12/2005)
- </a></td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">
- Pre-release Components
- <a name="openhouse">Open</a>
- House
- </font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>
- <i>
- This series of open house presentations is complete for our
- July (0.7) Release. Much thanks to all those who participated
- as presenters and attendees.
- </i>
- </b>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>What</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The Architecture Group is hosting a "Components Open House"
- to give a chance for more direct presentations from
- component leads to the PMC and other interested parties. The
- primary goal is to help promote steady progress towards our
- Eclipse release review. The secondary goal is that WTP is
- large and complex and even for a technical audience it helps
- to have someone "walk you through it" (as in a true "open
- house"). The presentations are not for end-users to learn
- 'how to' nor product managers to learn of plans and
- schedules (there are other avenues for those activities) but
- instead is more oriented towards describing the current
- state of the components to the project leads, PMC, and
- others who might be developing add-ins or add-ons to WTP.
- This is intended to be a sharing of information to help
- others get oriented to the project and components and hear
- of any issues (or gracious compliments :) that should be
- documented.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The presentations from lead developers will briefly cover
- <ul>
-
-<li>current end-user features</li>
-
-<li>current designs and APIs</li>
-
-<li>current quality</li>
-
-</ul>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The presentations will be made available on our mirrored
- <a href="http://www.eclipse.org/webtools/community/presentations.html">
- download-presentations-archive
- </a>
- (in advance, when possible).
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>How</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The presentations will be given via
- <a href="openhouse/webconference.html">"web conference"</a>
- concurrent with a
- <a href="openhouse/phoneInfo.html">conference phone.</a>
- For the web conference, there is a special "sign up"
- required for those outside IBM to gain a userid and password
- (it is not a confidential meeting, but it does access some
- IBM based services which require pre-registration and the
- sign-on).
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>When</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<center>
-
-<p>
- Below is the current schedule --
- <b>Thursdays, 12 to 2 EDT.</b>
-
-<br>
-
-</p>
-
-</center>
-
-<table align="center" width="70%" border="1" cellpadding="2" cellspacing="2">
-
-<tbody>
-
-<tr>
-
-<th>Date</th>
- <th>SubSystems/Components/Topics</th>
- <th>Organizer/Presenter</th>
-
-</tr>
-
-<tr valign="top">
-
-<td>5/19/2005</td>
- <td>
- Server Components
- <br>
-
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/05-19-wtp-open-house/server-tools.ppt" name="2005/05-19-wtp-open-house/server-tools.ppt">
- <em>WTP Server Tools Open House</em>
- </a>
-
-<br>
- Database Components
- <a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/05-19-wtp-open-house/data-tools.ppt" name="2005/05-19-wtp-open-house/data-tools.ppt">
- <em>Component: RDB</em>
- </a>
- </td>
- <td>
- Tim DeBoer
- <br>
-
-<br>
- Der Ping Chou
- <br>
-
-</td>
-
-</tr>
-
-<tr valign="top">
-
-<td>5/26/2005</td>
- <td>
- Web Services
- <br>
-
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/05-26-wtp-open-house/web-service-tools.ppt" name="2005/05-26-wtp-open-house/web-service-tools.ppt">
- <em>
- Eclipse WTP Project Web Service
- Tools Open House
- </em>
- </a>
-
-<br>
-
-</td>
- <td>Chris Brealey</td>
-
-</tr>
-
-<tr valign="top">
-
-<td>6/2/2005</td>
- <td>
- Common Components
- <br>
-
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/06-02-wtp-open-house/common-tools-06-02-1530-highlighted2.ppt" name="2005/06-02-wtp-open-house/common-tools-06-02-1530-highlighted2.ppt">
- <em>
- Eclipse WTP Project Common
- Components Open House
- </em>
- </a>
-
-<br>
-
-</td>
- <td>Craig Salter</td>
-
-</tr>
-
-<tr valign="top">
-
-<td>
- 6/9/2005
- <br>
-
-<br>
-
-</td>
- <td>
- WTP Source Editors (XML, JSP, etc)
- <br>
-
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/06-09-wtp-open-house/sse-openhouse-6-9.ppt" name="2005/06-09-wtp-open-house/sse-openhouse-6-9.ppt">
- <em>
- Eclipse WTP Project Source Editing
- Components Open House
- </em>
- </a>
-
-<br>
-
-</td>
- <td>
- David Williams
- <br>
-
-<br>
-
-</td>
-
-</tr>
-
-<tr valign="top">
-
-<td>6/16/2005</td>
- <td>
- J2EE (and Flexible Projects)
- <br>
-
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/06-16-wtp-open-house/j2ee-tools-06-16.ppt" name="2005/06-16-wtp-open-house/j2ee-tools-06-16.ppt"><em>Eclipse WTP Project J2EE Tools and Flexible Project Components Open House</em></a>
-<br>
-
-</td>
- <td>Chuck Bridgham</td>
-
-</tr>
-
-</tbody>
-
-</table>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Current Members</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>
- David Williams, IBM. Architecture Group Lead and Eclipse
- Architecture Council representative from WTP
- </li>
-
-<li>Chuck Bridgham, IBM</li>
-
-<li>Kevin Haaland, IBM</li>
-
-<li>Ted Bashor, BEA</li>
-
-<li>Naci Dai, Eteration</li>
-
-</ul>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/development/arch_and_design/arch_page.xml b/development/arch_and_design/arch_page.xml
deleted file mode 100644
index e0709e1..0000000
--- a/development/arch_and_design/arch_page.xml
+++ /dev/null
@@ -1,226 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?xml-stylesheet type="text/xsl" href="../../wtp.xsl"?>
-<html>
- <head>
- <meta
- name="root"
- content="../../.." />
- <title>Architecture Group Page</title>
- </head>
- <body>
- <h1>WTP Architecture Group Page</h1>
- <h2>Architecture Documents</h2>
- <a
- href="subsystems/SubsystemsAndFeatures.html">
- Proposed Architecture Document (10/09/2005)
- </a>
- <a
- href="http://www.eclipse.org/org/councils/AC/wtpsnapshot/wtp_project_architecture.html">
- Current Architecture Document (2/15/2005)
- </a>
- This is the one reviewed and approved by Eclipse Foundation
- Board, and is the "official one". Any updates to it should be
- consistent, or differences explained.
- <a href="ArchitectureOverview.html">
- Previous Architecture Document (12/2/2004)
- </a>
- <a href="ArchitectureOverviewInitial.html">
- Previous Architecture Document (8/16/2004)
- </a>
- <h2>Assessments</h2>
- <a href="M4ArchCheckPoint.html">
- Overall Architectural Assessment at M4 (5/12/2005)
- </a>
- <h2>
- Pre-release Components
- <a name="openhouse">Open</a>
- House
- </h2>
- <p>
- <b>
- <i>
- This series of open house presentations is complete for our
- July (0.7) Release. Much thanks to all those who participated
- as presenters and attendees.
- </i>
- </b>
- </p>
- <h3>What</h3>
- <p>
- The Architecture Group is hosting a "Components Open House"
- to give a chance for more direct presentations from
- component leads to the PMC and other interested parties. The
- primary goal is to help promote steady progress towards our
- Eclipse release review. The secondary goal is that WTP is
- large and complex and even for a technical audience it helps
- to have someone "walk you through it" (as in a true "open
- house"). The presentations are not for end-users to learn
- 'how to' nor product managers to learn of plans and
- schedules (there are other avenues for those activities) but
- instead is more oriented towards describing the current
- state of the components to the project leads, PMC, and
- others who might be developing add-ins or add-ons to WTP.
- This is intended to be a sharing of information to help
- others get oriented to the project and components and hear
- of any issues (or gracious compliments :) that should be
- documented.
- </p>
- <p>
- The presentations from lead developers will briefly cover
- <ul>
- <li>current end-user features</li>
- <li>current designs and APIs</li>
- <li>current quality</li>
- </ul>
- </p>
- <p>
- The presentations will be made available on our mirrored
- <a
- href="http://www.eclipse.org/webtools/community/presentations.html">
- download-presentations-archive
- </a>
- (in advance, when possible).
- </p>
- <h3>How</h3>
- <p>
- The presentations will be given via
- <a href="openhouse/webconference.html">"web conference"</a>
- concurrent with a
- <a href="openhouse/phoneInfo.html">conference phone.</a>
- For the web conference, there is a special "sign up"
- required for those outside IBM to gain a userid and password
- (it is not a confidential meeting, but it does access some
- IBM based services which require pre-registration and the
- sign-on).
- </p>
- <h3>When</h3>
- <p>
- <center>
- <p>
- Below is the current schedule --
- <b>Thursdays, 12 to 2 EDT.</b>
- <br />
- </p>
- </center>
- <table
- align="center"
- width="70%"
- border="1"
- cellpadding="2"
- cellspacing="2">
- <tbody>
- <tr>
- <th>Date</th>
- <th>SubSystems/Components/Topics</th>
- <th>Organizer/Presenter</th>
- </tr>
- <tr valign="top">
- <td>5/19/2005</td>
- <td>
- Server Components
- <br />
- <a
- href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/05-19-wtp-open-house/server-tools.ppt"
- name="2005/05-19-wtp-open-house/server-tools.ppt">
- <em>WTP Server Tools Open House</em>
- </a>
- <br />
- Database Components
- <a
- href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/05-19-wtp-open-house/data-tools.ppt"
- name="2005/05-19-wtp-open-house/data-tools.ppt">
- <em>Component: RDB</em>
- </a>
- </td>
- <td>
- Tim DeBoer
- <br />
- <br />
- Der Ping Chou
- <br />
- </td>
- </tr>
- <tr valign="top">
- <td>5/26/2005</td>
- <td>
- Web Services
- <br />
- <a
- href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/05-26-wtp-open-house/web-service-tools.ppt"
- name="2005/05-26-wtp-open-house/web-service-tools.ppt">
- <em>
- Eclipse WTP Project Web Service
- Tools Open House
- </em>
- </a>
- <br />
- </td>
- <td>Chris Brealey</td>
- </tr>
- <tr valign="top">
- <td>6/2/2005</td>
- <td>
- Common Components
- <br />
- <a
- href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/06-02-wtp-open-house/common-tools-06-02-1530-highlighted2.ppt"
- name="2005/06-02-wtp-open-house/common-tools-06-02-1530-highlighted2.ppt">
- <em>
- Eclipse WTP Project Common
- Components Open House
- </em>
- </a>
- <br />
- </td>
- <td>Craig Salter</td>
- </tr>
- <tr valign="top">
- <td>
- 6/9/2005
- <br />
- <br />
- </td>
- <td>
- WTP Source Editors (XML, JSP, etc)
- <br />
- <a
- href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/06-09-wtp-open-house/sse-openhouse-6-9.ppt"
- name="2005/06-09-wtp-open-house/sse-openhouse-6-9.ppt">
- <em>
- Eclipse WTP Project Source Editing
- Components Open House
- </em>
- </a>
- <br />
- </td>
- <td>
- David Williams
- <br />
- <br />
- </td>
- </tr>
- <tr valign="top">
- <td>6/16/2005</td>
- <td>
- J2EE (and Flexible Projects)
- <br />
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/presentations/2005/06-16-wtp-open-house/j2ee-tools-06-16.ppt" name="2005/06-16-wtp-open-house/j2ee-tools-06-16.ppt"><em>Eclipse WTP Project J2EE Tools and Flexible Project Components Open House</em></a> <br />
- </td>
- <td>Chuck Bridgham</td>
- </tr>
- </tbody>
- </table>
- </p>
- <h2>Current Members</h2>
- <ul>
- <li>
- David Williams, IBM. Architecture Group Lead and Eclipse
- Architecture Council representative from WTP
- </li>
- <li>Chuck Bridgham, IBM</li>
- <li>Kevin Haaland, IBM</li>
- <li>Ted Bashor, BEA</li>
- <li>Naci Dai, Eteration</li>
- </ul>
- </body>
-</html>
diff --git a/development/arch_and_design/images/ModelEditing.png b/development/arch_and_design/images/ModelEditing.png
deleted file mode 100644
index d3295d7..0000000
--- a/development/arch_and_design/images/ModelEditing.png
+++ /dev/null
Binary files differ
diff --git a/development/arch_and_design/images/jstsubsystems.png b/development/arch_and_design/images/jstsubsystems.png
deleted file mode 100644
index 0f4a5e5..0000000
--- a/development/arch_and_design/images/jstsubsystems.png
+++ /dev/null
Binary files differ
diff --git a/development/arch_and_design/images/modelToModel.png b/development/arch_and_design/images/modelToModel.png
deleted file mode 100644
index 9e714ba..0000000
--- a/development/arch_and_design/images/modelToModel.png
+++ /dev/null
Binary files differ
diff --git a/development/arch_and_design/images/server.png b/development/arch_and_design/images/server.png
deleted file mode 100644
index 87e0b48..0000000
--- a/development/arch_and_design/images/server.png
+++ /dev/null
Binary files differ
diff --git a/development/arch_and_design/images/webAppAndServerTarget.png b/development/arch_and_design/images/webAppAndServerTarget.png
deleted file mode 100644
index 5ea9d94..0000000
--- a/development/arch_and_design/images/webAppAndServerTarget.png
+++ /dev/null
Binary files differ
diff --git a/development/arch_and_design/images/wstandjstdependancies.png b/development/arch_and_design/images/wstandjstdependancies.png
deleted file mode 100644
index 5b25496..0000000
--- a/development/arch_and_design/images/wstandjstdependancies.png
+++ /dev/null
Binary files differ
diff --git a/development/arch_and_design/images/wstsubsystems.png b/development/arch_and_design/images/wstsubsystems.png
deleted file mode 100644
index 4abb935..0000000
--- a/development/arch_and_design/images/wstsubsystems.png
+++ /dev/null
Binary files differ
diff --git a/development/arch_and_design/openhouse/phoneInfo.html b/development/arch_and_design/openhouse/phoneInfo.html
deleted file mode 100644
index 6d95b6b..0000000
--- a/development/arch_and_design/openhouse/phoneInfo.html
+++ /dev/null
@@ -1,62 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../../default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../../webtools/wtp.css" type="text/css">
-<title>PHONE CONFERENCE INFO</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">
- General Information about Phone Conference for WTP
- Components Open House
- </font>
-<br>
-<font class="indexsub">PHONE CONFERENCE INFO</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../../images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">DIAL-IN NUMBERS and PASSCODES</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<br>
- Toll Number:
- <br>
- 1-203-566-8316
- <br>
- TollFree Number:
- <br>
-
-<b>866-818-8668</b>
-
-<br>
- Passcode:
- <b>334004</b>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>Press * 6 to mute or unmute your line.</b>
-
-</p>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/development/arch_and_design/openhouse/phoneInfo.xml b/development/arch_and_design/openhouse/phoneInfo.xml
deleted file mode 100644
index 8690840..0000000
--- a/development/arch_and_design/openhouse/phoneInfo.xml
+++ /dev/null
@@ -1,32 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?xml-stylesheet type="text/xsl" href="../../../wtp.xsl"?>
-<html>
- <head>
- <meta name="root" content="../../../.." />
- <title>PHONE CONFERENCE INFO</title>
- </head>
- <body>
- <h1>
- General Information about Phone Conference for WTP
- Components Open House
- </h1>
-
- <h2>DIAL-IN NUMBERS and PASSCODES</h2>
- <p>
- <br />
- Toll Number:
- <br />
- 1-203-566-8316
- <br />
- TollFree Number:
- <br />
- <b>866-818-8668</b>
- <br />
- Passcode:
- <b>334004</b>
- </p>
- <p>
- <b>Press * 6 to mute or unmute your line.</b>
- </p>
- </body>
-</html>
\ No newline at end of file
diff --git a/development/arch_and_design/openhouse/webconference.html b/development/arch_and_design/openhouse/webconference.html
deleted file mode 100644
index ea0ac0a..0000000
--- a/development/arch_and_design/openhouse/webconference.html
+++ /dev/null
@@ -1,110 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../../default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../../webtools/wtp.css" type="text/css">
-<title>WEB CONFERENCE INFO</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">
- General Information about Web Conference for WTP Components
- Open House
- </font>
-<br>
-<font class="indexsub">WEB CONFERENCE INFO</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../../images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">PREPARE FOR THE WEB CONFERENCE</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../../images/Adarrow.gif"></td><td>Customers, business partners and vendors:</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- + When joining the web conference, you will be asked for an
- IBM ID and password. - To verify an existing IBM ID and
- password, please visit
- <a href="http://www.ibm.com/account/profile">
- http://www.ibm.com/account/profile
- </a>
- to ensure valid sign in credentials and review your
- registration information.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- - If you need a new IBM ID and password, visit
- <a href="http://www.ibm.com/account/profile/us?page=reg">
- http://www.ibm.com/account/profile
- </a>
- to register. The ID should be active for usage on
- <a href="http://www.ibm.com/collaboration/collaboratenow">
- http://www.ibm.com/collaboration/collaboratenow
- </a>
- within 10 minutes of submission.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- + If this is your first IBM Web Conference, attend the
- special "test" meeting to make sure that you can join
- easily. Please visit
- <a href="http://www.ibm.com/collaboration/collaboratenow">
- http://www.ibm.com/collaboration/collaboratenow
- </a>
- and click
- <b>"test meeting"</b>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- + To join the conference, a Windows 2000 or Windows XP
- computer is required.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../../images/Adarrow.gif"></td><td>IBM employees:</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>+ Please use your w3.ibm.com intranet ID and password.</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- + If this is your first IBM Web Conference, attend the
- special "test" meeting to make sure that you can join
- easily. Please visit
- <a href="http://w3.ibm.com/e-meetings/webconferences">
- http://w3.ibm.com/e-meetings/webconferences
- </a>
- and click
- <b>"Connectivity Test"</b>
-
-</p>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/development/arch_and_design/openhouse/webconference.xml b/development/arch_and_design/openhouse/webconference.xml
deleted file mode 100644
index 6289df3..0000000
--- a/development/arch_and_design/openhouse/webconference.xml
+++ /dev/null
@@ -1,105 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?xml-stylesheet type="text/xsl" href="../../../wtp.xsl"?>
-<html>
- <head>
- <meta name="root" content="../../../.." />
- <title>WEB CONFERENCE INFO</title>
- </head>
- <body>
- <h1>
- General Information about Web Conference for WTP Components
- Open House
- </h1>
- <h2>PREPARE FOR THE WEB CONFERENCE</h2>
-
- <h3>Customers, business partners and vendors:</h3>
-
- <p>
- + When joining the web conference, you will be asked for an
- IBM ID and password. - To verify an existing IBM ID and
- password, please visit
- <a href="http://www.ibm.com/account/profile">
- http://www.ibm.com/account/profile
- </a>
- to ensure valid sign in credentials and review your
- registration information.
- </p>
- <p>
- - If you need a new IBM ID and password, visit
- <a href="http://www.ibm.com/account/profile/us?page=reg">
- http://www.ibm.com/account/profile
- </a>
- to register. The ID should be active for usage on
- <a href="http://www.ibm.com/collaboration/collaboratenow">
- http://www.ibm.com/collaboration/collaboratenow
- </a>
- within 10 minutes of submission.
- </p>
-
- <p>
- + If this is your first IBM Web Conference, attend the
- special "test" meeting to make sure that you can join
- easily. Please visit
- <a href="http://www.ibm.com/collaboration/collaboratenow">
- http://www.ibm.com/collaboration/collaboratenow
- </a>
- and click
- <b>"test meeting"</b>
- </p>
-
- <p>
- + To join the conference, a Windows 2000 or Windows XP
- computer is required.
- </p>
-
- <h3>IBM employees:</h3>
-
- <p>+ Please use your w3.ibm.com intranet ID and password.</p>
-
- <p>
- + If this is your first IBM Web Conference, attend the
- special "test" meeting to make sure that you can join
- easily. Please visit
- <a href="http://w3.ibm.com/e-meetings/webconferences">
- http://w3.ibm.com/e-meetings/webconferences
- </a>
- and click
- <b>"Connectivity Test"</b>
- </p>
-
-<!-- obsolete information, but general info above left here for re-use
- <h2>JOIN THE WEB CONFERENCE</h2>
-
- <p>
- Join the conference up to 15 minutes prior to the start of
- the meeting.
- </p>
-
- <p>
- Go to
- <a href="http://w3.ibm.com/e-meetings/webconferences">
- http://w3.ibm.com/e-meetings/webconferences
- </a>
- </p>
-
- <p>
- When asked, enter your user name (or IBM ID) and password.
- </p>
-
- <p>
- Enter the exact meeting name (case sensitive) into the empty
- text field in the web conferences portal.
- <br />
- Conference name:
- <b>WTP Component Open House</b>
- </p>
-
- <p>
- When prompted, enter the web conference
- <br />
- password:
- <b>ninet33n</b>
- </p>
--->
- </body>
-</html>
\ No newline at end of file
diff --git a/development/arch_and_design/pq-apis-20041115.ppt b/development/arch_and_design/pq-apis-20041115.ppt
deleted file mode 100644
index edc0c46..0000000
--- a/development/arch_and_design/pq-apis-20041115.ppt
+++ /dev/null
Binary files differ
diff --git a/development/arch_and_design/snapshot/images/WTP.gif b/development/arch_and_design/snapshot/images/WTP.gif
deleted file mode 100644
index e14fb15..0000000
--- a/development/arch_and_design/snapshot/images/WTP.gif
+++ /dev/null
Binary files differ
diff --git a/development/arch_and_design/snapshot/images/bullet.gif b/development/arch_and_design/snapshot/images/bullet.gif
deleted file mode 100644
index 9640dad..0000000
--- a/development/arch_and_design/snapshot/images/bullet.gif
+++ /dev/null
Binary files differ
diff --git a/development/arch_and_design/snapshot/images/jstsubsystems.jpg b/development/arch_and_design/snapshot/images/jstsubsystems.jpg
deleted file mode 100644
index 6baf722..0000000
--- a/development/arch_and_design/snapshot/images/jstsubsystems.jpg
+++ /dev/null
Binary files differ
diff --git a/development/arch_and_design/snapshot/images/wstsubsystems.jpg b/development/arch_and_design/snapshot/images/wstsubsystems.jpg
deleted file mode 100644
index 25f3790..0000000
--- a/development/arch_and_design/snapshot/images/wstsubsystems.jpg
+++ /dev/null
Binary files differ
diff --git a/development/arch_and_design/snapshot/jst_subproject_architecture.html b/development/arch_and_design/snapshot/jst_subproject_architecture.html
deleted file mode 100644
index 41c40d7..0000000
--- a/development/arch_and_design/snapshot/jst_subproject_architecture.html
+++ /dev/null
@@ -1,211 +0,0 @@
-<!-- ----------------------------------------------------------------------------- -->
-<!--
-Project: Web Tooling Platform (WTP) Project
-
-Contact: David Williams (david_williams@us.ibm.com)
--->
-<!-- ----------------------------------------------------------------------------- -->
-
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<title>J2EE Standard Tools (JST)</title>
-<meta
- http-equiv="Content-Type"
- content="text/html; charset=iso-8859-1" />
-<link
- rel="stylesheet"
- type="text/css"
- href="theme/eclipse_style.css" />
-</head>
-<body>
-
-<div id="page_header">J2EE Standard Tools</div>
-<div id="page_sub_header">Project architecture</div>
-
-<div id="section_header">Project description</div>
-<div class="content">
-<p>The initial scope of the <a
- href="http://www.eclipse.org/webtools/jst/main.html">J2EE Standard Tools</a>
-subproject will be to provide a to provide common infrastructure for
-developing applications based on J2EE 1.4 targeting J2EE-compliant
-application servers, as well as a more generic J2EE tooling
-infrastructure for other Eclipse-based development products.</p>
-<p>Tools provided will include a workbench for developing, deploying,
-testing and debugging J2EE applications on JCP-compliant server
-environments, as well as an exemplary implementation of a plug-in for at
-least one JSR-88 compliant J2EE Server. Included will be a range of
-tools simplifying development with J2EE APIs including EJB, Servlet,
-JSP, JCA, JDBC, JTA, JMS, JMX, JNDI, and Web Services. This
-infrastructure will be architected for extensibility for higher-level
-development constructs providing architectural separations of concern
-and technical abstraction above the level of the J2EE specifications</p>
-<p>The integrated workbench to be delivered would support use cases such
-as " - Develop a JSP page, Enhance the "PetStore" blue-print
-application, Expose a Session Bean as a Web Service".</p>
-
-<p>Refer to the <a href="wtp_project_main.html">WTP Project overview</a>
-for additional WTP Project information. You can click on the image below
-for additional information for the subsystems of JST</p>
-</div>
-
-
-<!-- Remove this section if you do not have an additional diagram -->
-<div id="section_header">Project architecture</div>
-<div class="image_map"><img
- src="images/jstsubsystems.jpg"
- width="497"
- height="421"
- usemap="#jstsubsystems"
- alt="" /><map
- id="jstsubsystems"
- name="jstsubsystems">
- <area
- shape="rect"
- href="#JSTServer"
- coords="384,201,481,276"
- alt="" />
- <area
- shape="rect"
- href="#BasicJ2EE"
- coords="293,118,407,192"
- alt="" />
- <area
- shape="rect"
- href="#AdvancedJ2EE"
- coords="201,30,337,107"
- alt="" />
- <area
- shape="rect"
- href="#JSP"
- coords="97,119,195,188"
- alt="" />
- <area
- shape="default"
- nohref="nohref"
- alt="" />
-</map><span class="img_caption">Figure 1. JST Subsystems</span></div>
-
-<div id="section_header">JST Subsystem descriptions</div>
-<div class="content">
-<dl id="subsys_list">
- <dt><a name="JSTServer">Server Subsystem</a></dt>
- <dd>This subsystem has components associated with servering, browsing,
- and monitoring web resources.
- <p>This subsystem has the following components:</p>
- <table id="tbl_info">
- <tr>
- <th id="name">Name</th>
- <th id="desc">Description</th>
- </tr>
- <tr>
- <td headers="name"><a href="http://www.eclipse.org/webtools/jst/components.html#jstserver">Server</a></td>
- <td headers="desc">The server component contains the J2EE Server
- Tools framework and adapters for selected popular J2EE servers such
- as Apache Tomcat. The component leads are Naci Dai and Tim deBoer.</td>
- </tr>
- </table>
- </dd>
- <dt><a name="JSP">JSP Subsystem</a></dt>
- <dd>Models and UI needed for developing JSP resources.
- <p>This subsystem has the following components:</p>
- <table id="tbl_info">
- <tr>
- <th id="name">Name</th>
- <th id="desc">Description</th>
- </tr>
- <tr>
- <td headers="name"><a href="http://www.eclipse.org/webtools/jst/components.html#jsp">JSP</a></td>
- <td headers="desc">The jsp component contains the JSP editor, model,
- views, wizards, etc. The component lead is David Williams.</td>
- </tr>
- </table>
- </dd>
- <dt><a name="BasicJ2EE">Basic J2EE Subsystem</a></dt>
- <dd>This Subsystem contains models, UI, and Tools, for basic J2EE
- development, such as servlets.
- <p>This subsystem has the following components:</p>
- <table id="tbl_info">
- <tr>
- <th id="name">Name</th>
- <th id="desc">Description</th>
- </tr>
- <tr>
- <td headers="name"><a href="http://www.eclipse.org/webtools/jst/components.html#servlet">Servlet</a></td>
- <td headers="desc">The servlet component contains the servlet
- editors, models, views, wizards, etc. The component lead is Naci Dai.</td>
- </tr>
- <tr>
- <td headers="name"><a href="http://www.eclipse.org/webtools/jst/components.html#j2ee">J2EE</a></td>
- <td headers="desc">The jst project component contains common j2ee
- models, natures and builders for J2EE projects, and j2ee modules
- views, wizards, etc. including the new support for flexible project
- layouts. The component leads are Naci Dai and Chuck Bridgham.</td>
- </tr>
- </table>
- </dd>
- <dt><a name="AdvancedJ2EE">Advanced J2EE Subsystem</a></dt>
- <dd>Models, UI, and Tools to support development of EJBs and J2EE Web
- Services.
- <p>This subsystem has the following components:</p>
- <table id="tbl_info">
- <tr>
- <th id="name">Name</th>
- <th id="desc">Description</th>
- </tr>
- <tr>
- <td headers="name"><a href="http://www.eclipse.org/webtools/jst/components.html#ejb">EJB</a></td>
- <td headers="desc">The ejb component contains the ejb editors,
- models, views, wizards, etc. The component lead is Naci Dai.</td>
- </tr>
- <tr>
- <td headers="name"><a href="http://www.eclipse.org/webtools/jst/components.html#ws">WS</a></td>
- <td headers="desc">The ws component contains the Java Web service
- wizard and adapters for selected popular J2EE Web service engines
- such as Apache Axis. The component lead is Chris Brealey.</td>
- </tr>
- </table>
- </dd>
- <dd>
- <p></p>
-
- </dd>
-
- <!-- template version to use in above table
- <dt><subsystem></dt>
- <dd><descriptions>
- <p>This subsystem has the following components:</p>
- <table id="tbl_info">
- <tr>
- <th id="name">Name</th>
- <th id="desc">Description</th>
- </tr>
- <tr>
- <td headers="name">org.eclipse.wtp.releng</td>
- <td headers="desc">Build infrastructure, map files</td>
- </tr>
- <tr>
- <td headers="name">performance</td>
- <td headers="desc">custom performance tests</td>
- </tr>
- <tr>
- <td headers="name">test</td>
- <td headers="desc">junit test infrastructure</td>
- </tr>
- </table>
- </dd>
--->
-
-
-</dl>
-</div>
-
-<div class="section_divider"></div>
-<div class="content">
-<div id="copyright">See <a
- href="http://www.eclipse.org/legal/termsofuse.html">Terms of Use</a>.
-</div>
-</div>
-</body>
-</html>
diff --git a/development/arch_and_design/snapshot/projectsubsystem_architecture.html b/development/arch_and_design/snapshot/projectsubsystem_architecture.html
deleted file mode 100644
index b24f3c4..0000000
--- a/development/arch_and_design/snapshot/projectsubsystem_architecture.html
+++ /dev/null
@@ -1,68 +0,0 @@
-<!-- ----------------------------------------------------------------------------- -->
-<!--
-Project: Web Tooling Platform (WTP) Project
-
-Contact: David Williams (david_williams@us.ibm.com)
--->
-<!-- ----------------------------------------------------------------------------- -->
-
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-
- <head>
- <title><YOUR_SUBPROJECT_NAME - SUBSYSTEM></title>
- <meta HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
- <link rel="stylesheet" type="text/css" href="theme/eclipse_style.css" >
- </head>
- <body>
- <div id="page_header"><SUBPROJECT_NAME - SUBSYSTEM></div>
- <div id="page_sub_header">Project architecture</div>
-
- <div id="section_header">Subsystem description</div>
- <div class="content">
-
- <p><Description of subsystem></p>
- <p>Link to the main <a href="../arch_and_design/project_architecture.html">project site</a>.</p>
- </div>
-
- <!-- You can leave the following section out if there is no diagram at this level -->
- <div id="section_header">Subsystem architecture</div>
- <div class="image_map"><img src="../arch_and_design/images/c.gif" height="200" alt="Component architecture overview"><br>
- <span class="img_caption">Figure 1. <Caption describing the architecture diagram></span></div>
-
- <div id="section_divider"></div>
-
-
- <div id="section_header">Component list</div>
- <div class="content">
- <p>Info about each component:</p>
- <dl id="comp_list">
- <dd><a name="ui"></a><COMPONENT A></dd>
- <dt><COMPONENT A description>
- <table id="tbl_info" id="ui_table">
- <tr>
- <th id="name">Committers</th>
- </tr>
- <tr>
- <td headers="name">n/a</td>
- </tr>
- </table>
- </dt>
- <dd><a name="ui"></a><COMPONENT B></dd>
- <dt><COMPONENT B description>
- <table id="tbl_info" id="ui_table">
- <tr>
- <th id="name">Committers</th>
- </tr>
- <tr>
- <td headers="name">n/a</td>
- </tr>
- </table>
- </dt>
- </dl>
- </div>
- <div id="section_divider"></div>
- <div id="copyright"><INSERT_LEGAL_STATEMENTS></div>
- </body>
-</html>
\ No newline at end of file
diff --git a/development/arch_and_design/snapshot/theme/eclipse_style.css b/development/arch_and_design/snapshot/theme/eclipse_style.css
deleted file mode 100644
index febda4a..0000000
--- a/development/arch_and_design/snapshot/theme/eclipse_style.css
+++ /dev/null
@@ -1,431 +0,0 @@
-/* ******************************************************************************************* */
-/* Eclipse.org style sheet */
-/* Version: 0.1 */
-/* Create date: Dec 15, 2004 */
-/* Author: Nellie Klump */
-/* Last update: Jan 6, 2005 */
-/* ******************************************************************************************* */
-
-/* ============================ Page heading ============================ */
-#page_header {
- background-color:#FFFFFF;
- margin: 5px 0 0 15px;
- width: 100%;
- height: 25px;
- text-align: left;
- font: bold 18pt Verdana;
- clear:left;
-}
-#page_sub_header {
- margin: 5px 0 18px 15px;
- background-color:#FFFFFF;
- text-align: left;
- font: normal 8pt Arial;
- color: blue;
-}
-
-/* ============================ Section heading & dividers ============================ */
-#section_header {
- background-color:#0080C0;
- margin: 10px 0 0 0;
- float:left;
- width: 100%;
- height: 20px;
- text-align: left;
- clear:both;
- font: bold 14px Arial;
- color: #FFFFFF;
- text-indent: 10px;
-}
-
-#section_hlight {
- border: 2px outset #6699FF;
- background-color:#f0f8ff;
- margin: 5px 0 0 0;
- width: 540px;
- height: 22px;
- text-align: left;
- font-family: Arial, Tahoma, Sans-serif; font-size: 12px; font-weight: 800; font-style: normal; text-decoration: none;
- color: #000000;
- text-indent: 10px;
-}
-
-#section_divider {
- border-bottom: 4px solid #0070a0;
- background-color: #FFFFFF
- margin: 10px 0 0 0;
- float:left;
- width: 100%;
- height: 1px;
- clear:both;
-}
-
-/* ============================ Legal statements ============================ */
-#copyright {
- float: left;
- margin: 20px 0 0 0;
- font-family: Arial, Tahoma, Sans-serif; font-size: 10px; font-weight: 100; font-style: normal; text-decoration: none;
- color: #000000;
- clear: both;
-}
-
-/* ============================ Right-column: Resources ============================ */
-#rightcol_res {
- border: 2px outset #6699FF;
- background-color:#FFFFFF;
- margin: 5px 0 10px 0;
- width: 150px;
- height: 120px;
- text-align: left;
- font-family: Arial, Tahoma, Sans-serif; font-size: 12px; font-weight: 400; font-style: normal; text-decoration: none;
-}
-
-#rightcol_heading {
- background-color:#f0f8ff;
- border-bottom: 1px solid #000000;
- margin: 0 0 5px 0;
- width: 150px;
- height: 22px;
- text-align:center;
- font-family: Arial, Tahoma, Sans-serif; font-size: 12px; font-weight:800; font-style: normal; text-decoration: none;
-}
-
-/* ============================ Lists ============================ */
-ul{
- list-style-type: none;
- font-family: Arial, Tahoma, Sans-serif; font-size: 12px; font-weight:400; font-style: normal; text-decoration: none;
- margin: 5px 0 5px 4px;
-}
-li {
- margin:0px;
-}
-
-/* ============================ General list ============================ */
-dl#gen_list{
- list-style-type: none;
- margin: 0;
- padding: 0;
-}
-
-dl#gen_list dd{
- margin: 10px 0 0 0;
- color:black;
- font-family: Arial, Tahoma, Sans-serif; font-size: 12px; font-weight: 800; font-style: normal; text-decoration: bold;
- clear:both;
- text-indent: 15px;
-
-}
-
-dl#gen_list dt{
- margin: 5px 0 5px 10px;
- clear:both;
- display: inline;
-
-}
-
-.shift_left
-{
- padding-left:50px;
-}
-
-/* ============================ Component definition list ============================ */
-dl#comp_list{
- list-style-type: none;
- margin: 0;
- padding: 0;
-}
-
-dl#comp_list dd{
- margin: 20px 0 0 0;
- color:black;
- font-family: Arial, Tahoma, Sans-serif; font-size: 14px; font-weight: 800; font-style: normal; text-decoration: bold;
- clear:both;
- background-image:url("../../arch_and_design/theme/images/bullet.gif");
- background-repeat:no-repeat;
- text-indent: 15px;
-
-}
-
-dl#comp_list dt{
- margin: 5px 0 5px 20px;
- clear:both;
-}
-
-/* ============================ Subsystem lists ============================ */
-dl#subsys_list{
- list-style-type: none;
- margin: 0;
- padding: 0;
- width:100%;
-}
-
-dl#subsys_list dd{
- margin: 5px 0 5px 20px;
- color:black;
- font-family: Arial, Tahoma, Sans-serif; font-size: 14px; font-style: normal; text-decoration: none;
-}
-
-dl#subsys_list dt{
- border-top: 1px solid #666;
- margin: 10px 0 5px 0px;
- font-family: Arial, Tahoma, Sans-serif; font-size: 14px; font-weight: 800; font-style: normal; text-decoration: bold;
- clear:both;
-}
-
-
-/* ============================ Pipe list =========================== */
-#pipelist_container { margin-left: 30px; }
-
-#pipelist
-{
-list-style: none;
-padding: 0;
-margin: 0;
-}
-
-#pipelist li
-{
-display: inline;
-padding: 0;
-margin: 0;
-}
-
-#pipelist li:before { content: "| "; }
-#pipelist li:first-child:before { content: ""; }
-
-/*IE workaround*/
-/*All IE browsers*/
-* html #pipelist li
-{
-border-left: 1px solid black;
-padding: 0 0.4em 0 0.4em;
-margin: 0 0.4em 0 -0.4em;
-}
-
-/*Win IE browsers - hide from Mac IE\*/
-* html #pipelist { height: 1%; }
-
-* html #pipelist li
-{
-display: block;
-float: left;
-}
-
-/*End hide*/
-/*Mac IE 5*/
-* html #pipelist li:first-child { border-left: 0; }
-
-
-/* ============================ Image Maps ============================ */
-.image_map {
- float:left;
- width:700px;
- clear:both;
- margin: 15px 0 0 0;
- border: 0px solid #000000;
- background-color:#FFFFFF;
-}
-.img_caption {
- float:left;
- font-family: Arial, Tahoma, Sans-serif; font-size: 10px; font-weight: 400; font-style: normal; text-decoration: none;
-}
-
-/* ============================ General Content ============================ */
-.content {
- float:left;
- width: 100%;
- margin: 5px auto;
- clear:both;
- font-family: Arial, Tahoma, Sans-serif; font-size: 12px; font-weight: 400; font-style: normal; text-decoration: none;
-}
-
-.main_content {
- width: 540px;
- clear:both;
- font-family: Arial, Tahoma, Sans-serif; font-size: 12px; font-weight: 400; font-style: normal; text-decoration: none;
-}
-
-/* ============================ Table ============================ */
-table#tbl_info {
- float:inherit;
- margin: 10px 0 10px 0;
- border-collapse:collapse;
- border:black solid 1px;
- padding:5px;
- clear:both;
-}
-
-table#tbl_info th{
- background-color:#99CCFF;
- font-family: Arial, Tahoma, Sans-serif; font-size: 12px; font-weight: 800; font-style: normal; text-decoration: bold;
- border: black solid 1px;
- width:200px;
-}
-
-table#tbl_info td{
- border: black solid 1px;
- font-family: Arial, Tahoma, Sans-serif; font-size: 12px; font-weight: 400; font-style: normal; text-decoration: none;
-}
-
-/* ============================ Tabbed container ============================ */
- #navcontainer ul
-{
-padding: 1px 0;
-margin: 10px 0 0 0;
-border-bottom: 10px solid #0070a0;
-font: bold 8px Verdana, sans-serif;
-}
-
-#navcontainer li
-{
-list-style: none;
-margin: 0;
-display: inline;
-line-height:18px;
-padding: 2px 0.5em;
-margin-left: 2px;
-border: 1px solid #0070a0;
-border-bottom: none;
-background: #99CCFF;
-}
-
-#navcontainer a
-{
-
-text-decoration: none;
-}
-
-#navcontainer a:link
-{
-color: #ffffff;
-text-decoration: none;
-padding-left: 0.25em;
-padding-right: 0.25em;
-}
-
-#navcontainer a:visited
-{
-color: #FFFFFF;
-}
-
-#navcontainerclear { display: none; }
-
-html>body #navcontainerclear
-{
-display: block;
-clear: both;
-}
-
-#navcontainer li#link1
-{
-background-color: #99CCFF;
-color: #FFFFFF;
-border: 1px solid #0070a0;
-}
-
-#navcontainer li#link2
-{
-background-color: #99CCFF;
-color: #FFFFFF;
-border: 1px solid #0070a0;
-}
-#navcontainer li#link3
-{
-background-color: #99CCFF;
-color: #FFFFFF;
-border: 1px solid #0070a0;
-}
-#navcontainer li#link4
-{
-background-color: #99CCFF;
-color: #FFFFFF;
-border: 1px solid #0070a0;
-}
-#navcontainer li#link5
-{
-background-color: #99CCFF;
-color: #FFFFFF;
-border: 1px solid #0070a0;
-}
-#navcontainer li#link6
-{
-background-color: #99CCFF;
-color: #FFFFFF;
-border: 1px solid #0070a0;
-}
-
-#navcontainer li#link7
-{
-background-color: #99CCFF;
-color: #FFFFFF;
-border: 1px solid #0070a0;
-}
-
-#navcontainer li#link8
-{
-background-color: #99CCFF;
-color: #FFFFFF;
-border: 1px solid #0070a0;
-}
-
-#navcontainer li#enh1
-{
-background-color: #3399FF;
-color: #FFFFFF;
-border: 1px solid #0070a0;
-}
-
-#navcontainer li#enh2
-{
-background-color: #3399FF;
-color: #FFFFFF;
-border: 1px solid #0070a0;
-}
-
-#navcontainer li#enh3
-{
-background-color: #3399FF;
-color: #FFFFFF;
-border: 1px solid #0070a0;
-}
-
-/* ********************** Navigation bar container ******************************* */
-#navbar_container {
-width: 200px;
-background-color:#6699CC;
-}
-
-#navbar_container ul
-{
-margin-left: 0;
-padding-left: 0;
-list-style-type: none;
-font-family: Arial, Helvetica, sans-serif;
-}
-#navbar_container li
-{
-list-style: none;
-background-color: #90C8FF;
-color: #000000;
-border-bottom: 1px solid #CFFFFF;
-text-indent:5px;
-}
-
-
-#navbar_container a
-{
-display: block;
-padding: 3px;
-width: 160px;
-text-decoration: none;
-color:#000000;
-}
-#navbar_container a:visited
-{
-display: block;
-padding: 3px;
-width: 160px;
-text-decoration: none;
-color: #000000;
-}
-
diff --git a/development/arch_and_design/snapshot/wst_subproject_architecture.html b/development/arch_and_design/snapshot/wst_subproject_architecture.html
deleted file mode 100644
index 3fd7b63..0000000
--- a/development/arch_and_design/snapshot/wst_subproject_architecture.html
+++ /dev/null
@@ -1,346 +0,0 @@
-<!-- ----------------------------------------------------------------------------- -->
-<!--
-Project: Web Tooling Platform (WTP) Project
-
-Contact: David Williams (david_williams@us.ibm.com)
--->
-<!-- ----------------------------------------------------------------------------- -->
-
-
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-
-<head>
-<title>Web Standard Tools (WST)</title>
-<meta
- http-equiv="Content-Type"
- content="text/html; charset=iso-8859-1" />
-
-<link
- rel="stylesheet"
- href="theme/eclipse_style.css"
- type="text/css" />
-
-
-</head>
-<body>
-
-<div id="page_header">Web Standard Tools (WST)</div>
-<div id="page_sub_header">Project architecture</div>
-
-<div id="section_header">Project description</div>
-<div class="content">
-<p><a href="http://www.eclipse.org/webtools/wst/main.html">Web Standard
-Tools</a> is a subproject of <a
- href="http://www.eclipse.org/webtools/main.html">Web Tooling Platform
-(WTP) Project</a>. It aims to provide common infrastructure available to
-any Eclipse-based development environment targeting Web-enabled
-applications. Within scope will be tools for the development of
-three-tier (presentation, business and data logic) and server
-publication of corresponding system artifacts. Outside scope will be
-language or web framework specific technology, which will be left to
-other subprojects like the J2EE Web Tools subproject.</p>
-<p>Tools provided will include editors, validators and document
-generators for artifacts developed in a wide range of standard languages
-(for example, HTML/XHMTL, Web services, XQueries, SQL, etc.) Supporting
-infrastructure will likely comprise a specialized workbench supporting
-actions such as publish, run, start and stop of Web application code
-across target server environments.</p>
-<p>Refer to the <a href="../arch_and_design/project_main.html">WTP Project overview</a> for
-additional WTP Project information. You can click on the image below for
-additional information for the subsystems of WST</p>
-</div>
-
-<!-- Remove this section if you do not have an additional diagram -->
-
-<div id="section_header">Project architecture</div>
-
-<div class="image_map"><img
- src="images/wstsubsystems.jpg"
- width="607"
- height="545"
- usemap="#wstsubsystems" /><map name="wstsubsystems" id="wstsubsystems">
- <area
- shape="rect"
- href="#Common"
- coords="56,445,207,530" />
- <area
- shape="rect"
- href="#WSTServer"
- coords="419,447,587,524" />
- <area
- shape="rect"
- href="#WebProject"
- coords="398,273,577,358" />
- <area
- shape="rect"
- href="#Data"
- coords="233,273,384,360" />
- <area
- shape="rect"
- href="#XML"
- coords="49,280,199,361" />
- <area
- shape="rect"
- href="#WebServices"
- coords="338,125,509,221" />
- <area
- shape="rect"
- href="#WebResources"
- coords="81,122,296,217" />
- <area
- shape="default"
- nohref="nohref" />
-</map><span class="img_caption">Figure 1.WST Subsystems</span></div>
-<div id="section_header">Subsystem descriptions</div>
-<div class="content">
-<dl id="subsys_list">
- <dt><a name="BuildAndAssembly">Build and Assembly</a></dt>
- <dd>This subsystem includes our build and test component, modeled after
- the base Eclipse build and test components.
- <p>This subsystem has the following components:</p>
- <table id="tbl_info">
- <tr>
- <th id="name">Name</th>
- <th id="desc">Description</th>
- </tr>
- <tr>
- <td headers="name">org.eclipse.wtp.releng</td>
- <td headers="desc">Build infrastructure, map files</td>
- </tr>
- <tr>
- <td headers="name">performance</td>
- <td headers="desc">custom performance tests</td>
- </tr>
- <tr>
- <td headers="name">test</td>
- <td headers="desc">junit test infrastructure</td>
- </tr>
- </table>
- </dd>
-
- <dt><a name="Common">Common</a></dt>
- <dd>Components in this subsystem have no dependancies on other
- webtooling components and are not specific to web tooling
- functionality, but are needed by other web tooling components.
- <p>This subsystem has the following components:</p>
- <table
- id="tbl_info"
- id="ui_table">
- <tr>
- <th id="name">Name</th>
- <th id="desc">Description</th>
- </tr>
- <tr>
- <td headers="name"><a href="http://www.eclipse.org/webtools/wst/components.html#wstcommon">Common
- Component</a></td>
- <td headers="desc">Extensible Navigator, Tabbed Property View,
- Snippets View, Extensible URI Resolver. The component lead is Craig
- Salter.</td>
- </tr>
- <tr>
- <td headers="name"><a href="http://www.eclipse.org/webtools/wst/components.html#validation">Validation
- Component</a></td>
- <td headers="desc">Infrastructure to handle preferences and to manage
- running of validators. The component lead is Chuck Bridgham.</td>
- </tr>
- <tr>
- <td headers="name"><a href="http://www.eclipse.org/webtools/wst/components.html#j2ee">Command
- Component</a></td>
- <td headers="desc">Infrastructure to allow command environment. The
- component lead is Chris Brealey.</td>
- </tr>
- </table>
- </dd>
- <dt><a name="WSTServer">Server Subsystem</a></dt>
- <dd>This subsystem has components associated with serving, browsing,
- and monitoring web resources.
- <p>This subsystem has the following components:</p>
- <table id="tbl_info">
- <tr>
- <th id="name">Name</th>
- <th id="desc">Description</th>
- </tr>
- <tr>
- <td headers="name"><a href="http://www.eclipse.org/webtools/wst/components.html#wstserver">Server</a></td>
- <td headers="desc">Basic server support (HTTP). The component lead is
- Tim deBoer.</td>
- </tr>
- <tr>
- <td headers="name"><a href="http://www.eclipse.org/webtools/wst/components.html#internet">Internet</a></td>
- <td headers="desc">Browser, TCP/IP Monitor, and Preferences needed
- for internet developement. The component lead is Tim deBoer.</td>
- </tr>
- </table>
- </dd>
- <dt><a name="Data">Data Subystem</a></dt>
- <dd>Models and UI needed for data base access and queries.
- <p>This subsystem is currently planned to be seperately installable via
- update manager for the convenience of other project neededing to re-use
- it (e.g. BIRT).</p>
- <p>This subsystem has the following components:</p>
- <table id="tbl_info">
- <tr>
- <th id="name">Name</th>
- <th id="desc">Description</th>
- </tr>
- <tr>
- <td headers="name"><a href="http://www.eclipse.org/webtools/wst/components.html#rdbsql">RDB/SQL</a></td>
- <td headers="desc">The rdb component contains the relational database
- model which is derived from <a
- href="../arch_and_design/components/rdb/WebPublishedSQLModel/SQLModel.htm">RDBModel -
- Based on SQL 99/2003</a> , <a
- href="../arch_and_design/components/rdb/SQLModelJavaDoc/index.html">RDBModel Java Docs</a>
- , vendor-specific database definitions and relational utilities. It
- also provides a database server explorer with the ability to connect
- to databases and sample data. A SQLScrapbook editor allows you to
- enter and execute SQL, displaying the results in an Output view. The
- co-leads are Der Ping Chou and Sheila Sholars.</td>
- </tr>
- </table>
- </dd>
- <dt><a name="XML">XML</a></dt>
- <dd>This Subsystem contains models, UI, and Tools, for XML, DTD, and
- XML Schema.
- <p>This subsystem is currently planned to be seperately installable via
- update manager for the convenience of users and other project neededing
- to re-use it (e.g. Voice XML).</p>
- <p>This subsystem has the following components:</p>
- <table id="tbl_info">
- <tr>
- <th id="name">Name</th>
- <th id="desc">Description</th>
- </tr>
- <tr>
- <td headers="name"><a href="http://www.eclipse.org/webtools/wst/components.html#xml">XML</a></td>
- <td headers="desc">The xml component contains the XML editor, model,
- views, wizards, etc. It contains an incremental, fault tolerant DOM
- parser, which is also the basis of several other similar models in
- HTML and JSP. The component lead is David Williams.</td>
- </tr>
- <tr>
- <td headers="name"><a href="http://www.eclipse.org/webtools/wst/components.html#dtd">DTD</a></td>
- <td headers="desc">The dtd component contains the DTD editor, model,
- views, wizards, etc. The component lead is Nitin Dahyabhai.</td>
- </tr>
- <tr>
- <td headers="name"><a href="http://www.eclipse.org/webtools/wst/components.html#xmlschema">XML
- Schema</a></td>
- <td headers="desc">The xsd component contains the XSD editor, views,
- wizards, etc. The component lead is Craig Salter.</td>
- </tr>
- <tr>
- <td headers="name"><a href="http://www.eclipse.org/webtools/wst/components.html#sse">SSE</a></td>
- <td headers="desc">Infrastructure to parse, model, and edit
- structured text. The component lead is David Williams.</td>
- </tr>
- </table>
- </dd>
- <dt><a name="WebServices">Web Services Subsystem</a></dt>
- <dd>Models, UI, and Tools to support development of Web Services.
- <p>This subsystem has the following components:</p>
- <table id="tbl_info">
- <tr>
- <th id="name">Name</th>
- <th id="desc">Description</th>
- </tr>
- <tr>
- <td headers="name"><a href="http://www.eclipse.org/webtools/wst/components.html#wstws">WS</a></td>
- <td headers="desc">The ws component contains the Web Service
- explorer, SOAP, UDDI, and WSIL models, and views. The component lead
- is Chris Brealey.</td>
- </tr>
- <tr>
- <td headers="name"><a href="http://www.eclipse.org/webtools/wst/components.html#wsdl">WSDL</a></td>
- <td headers="desc">The wsdl component contains the WSDL editor,
- model, views, wizards, etc. The component lead is Craig Salter.</td>
- </tr>
- <tr>
- <td headers="name"><a href="http://www.eclipse.org/webtools/wst/components.html#wsi">WSI</a></td>
- <td headers="desc">The wsi component contains WS-I Test Tools which
- will be repatriated from the WSVT project. The component lead is
- Craig Salter.</td>
- </tr>
- </table>
- </dd>
- <dt><a name="WebResources">Web Resources Subsystem</a></dt>
- <dd>Models, UI, and Tools for creating and editing HTML, CSS, and
- JavaScript
- <p>This subsystem has the following components:</p>
- <table id="tbl_info">
- <tr>
- <th id="name">Name</th>
- <th id="desc">Description</th>
- </tr>
- <tr>
- <td headers="name"><a href="http://www.eclipse.org/webtools/wst/components.html#html">HTML</a></td>
- <td headers="desc">The html component contains the HTML/XHTML editor,
- model, views, wizards, etc. The component lead is David Williams.</td>
- </tr>
- <tr>
- <td headers="name"><a href="http://www.eclipse.org/webtools/wst/components.html#css">CSS</a></td>
- <td headers="desc">The css component contains the CSS editor, model,
- views, wizards, etc. The component lead is David Williams.</td>
- </tr>
- <tr>
- <td headers="name"><a href="http://www.eclipse.org/webtools/wst/components.html#javascript">JavaScript</a></td>
- <td headers="desc">The javascript component contains the JavaScript
- editor, model, views, wizards, etc. The component lead is David
- Williams.</td>
- </tr>
- </table>
- </dd>
- <dt><a name="WebProject">Web Project Subsystem</a></dt>
- <dd>Contains models and UI for "static" web projects.
- <p>This subsystem has the following components:</p>
- <table id="tbl_info">
- <tr>
- <th id="name">Name</th>
- <th id="desc">Description</th>
- </tr>
- <tr>
- <td headers="name"><a href="http://www.eclipse.org/webtools/wst/components.html#web">Web</a></td>
- <td headers="desc">The web component contains models, natures and
- builders for Web projects. The component lead is Chuck Bridgham.</td>
- </tr>
- </table>
- </dd>
-
- <!-- template version to use in above table
- <dt><subsystem></dt>
- <dd><descriptions>
- <p>This subsystem has the following components:</p>
- <table id="tbl_info">
- <tr>
- <th id="name">Name</th>
- <th id="desc">Description</th>
- </tr>
- <tr>
- <td headers="name">org.eclipse.wtp.releng</td>
- <td headers="desc">Build infrastructure, map files</td>
- </tr>
- <tr>
- <td headers="name">performance</td>
- <td headers="desc">custom performance tests</td>
- </tr>
- <tr>
- <td headers="name">test</td>
- <td headers="desc">junit test infrastructure</td>
- </tr>
- </table>
- </dd>
--->
-
-
-</dl>
-</div>
-
-<div class="section_divider"></div>
-<div class="content">
-<div id="copyright">See <a
- href="http://www.eclipse.org/legal/termsofuse.html">Terms of Use</a>.
-</div>
-</div>
-</body>
-</html>
diff --git a/development/arch_and_design/snapshot/wtp_project_architecture.html b/development/arch_and_design/snapshot/wtp_project_architecture.html
deleted file mode 100644
index d241f84..0000000
--- a/development/arch_and_design/snapshot/wtp_project_architecture.html
+++ /dev/null
@@ -1,80 +0,0 @@
-<!-- ----------------------------------------------------------------------------- -->
-<!--
-Project: Web Tooling Platform (WTP) Project
-
-Contact: David Williams (david_williams@us.ibm.com)
--->
-<!-- ----------------------------------------------------------------------------- -->
-
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-
-<head>
-<title>WTP Architecture</title>
-<meta
- http-equiv="Content-Type"
- content="text/html; charset=iso-8859-1" />
-<link
- rel="stylesheet"
- type="text/css"
- href="theme/eclipse_style.css" />
-</head>
-<body>
-
-<div id="page_header">Web Tooling Platform (WTP) Project</div>
-<div id="page_sub_header">Project architecture</div>
-
-<div id="section_header">Project description</div>
-<div class="content">
-<p>The <a href="http://www.eclipse.org/webtools/main.html">Web Tooling
-Platform (WTP) Project</a> is made up of two subprojects, <a
- href="http://www.eclipse.org/webtools/wst/main.html">Web Standard Tools
-(WST)</a> and <a href="http://www.eclipse.org/webtools/jst/main.html">J2EE
-Standard Tools (JST)</a>. In addition to depending on the Tools
-Platform, WST depends on EMF, XSD InfoSet, and GEF, while JST depends on
-WST and JDT.</p>
-
-<p>Refer to the <a href="wtp_project_main.html">WTP Project overview</a> for
-additional WTP Project information. You can click on the image below for
-additional information for the <a
- href="jst_subproject_architecture.html">JST</a> and <a
- href="wst_subproject_architecture.html">WST</a> sub-projects.</p>
-</div>
-
-<div id="section_header">Project architecture</div>
-<div
- class="image_map"><img
- src="images/WTP.gif"
- width="540"
- height="330"
- usemap="#WTP"
- alt="" /><map
- id="WTP"
- name="WTP">
- <area
- shape="rect"
- href="jst_subproject_architecture.html"
- alt=""
- coords="135,8,255,90" />
- <area
- shape="rect"
- href="wst_subproject_architecture.html"
- alt=""
- coords="268,85,386,165" />
- <area
- shape="default"
- alt=""
- nohref="nohref" />
-</map>
-<span class="img_caption">Figure 1. Web Tools Platform consist of WST
-and JST</span></div>
-
-<div class="section_divider"></div>
-<div class="content">
-<div id="copyright">See <a
- href="http://www.eclipse.org/legal/termsofuse.html">Terms of Use</a>.
-</div>
-</div>
-</body>
-</html>
diff --git a/development/arch_and_design/snapshot/wtp_project_main.html b/development/arch_and_design/snapshot/wtp_project_main.html
deleted file mode 100644
index c7dfb28..0000000
--- a/development/arch_and_design/snapshot/wtp_project_main.html
+++ /dev/null
@@ -1,168 +0,0 @@
-<!-- ----------------------------------------------------------------------------- -->
-<!--
-Project: Web Tooling Platform (WTP) Project
-
-Contact: David Williams (david_williams@us.ibm.com)
--->
-<!-- ----------------------------------------------------------------------------- -->
-
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-
-<head>
-<title>Web Tooling Platform (WTP)</title>
-<meta
- http-equiv="Content-Type"
- content="text/html; charset=iso-8859-1" />
-<link
- rel="stylesheet"
- type="text/css"
- href="theme/eclipse_style.css" />
-</head>
-<body>
-
-<div id="page_header">Web Tooling Platform (WTP) Project</div>
-<div id="page_sub_header">Project overview</div>
-
-<div id="section_header">Project description</div>
-<div class="content">
-
-<p>The <a href="http://www.eclipse.org/webtools/main.html">Web Tooling
-Platform (WTP) Project</a> is made up of two subprojects, <a
- href="http://www.eclipse.org/webtools/wst/main.html">Web Standard Tools
-(WST)</a> and <a href="http://www.eclipse.org/webtools/jst/main.html">J2EE
-Standard Tools (JST)</a>.</p>
-<p>The <a href="http://www.eclipse.org/webtools/wst/main.html">Web
-Standard Tools</a> subproject aims to provide common infrastructure
-available to any Eclipse-based development environment targeting
-Web-enabled applications. Within scope will be tools for the development
-of three-tier (presentation, business and data logic) and server
-publication of corresponding system artifacts. Outside scope will be
-language or web framework specific technology, which will be left to
-other subprojects like the J2EE Web Tools subproject.</p>
-<p>Tools provided will include editors, validators and document
-generators for artifacts developed in a wide range of standard languages
-(for example, HTML/xHMTL, Web services, XQueries, SQL, etc.) Supporting
-infrastructure will likely comprise a specialized workbench supporting
-actions such as publish, run, start and stop of Web application code
-across target server environments.</p>
-<p>The initial scope of the <a
- href="http://www.eclipse.org/webtools/jst/main.html">J2EE Standard Tools</a>
-subproject will be to provide a to provide common infrastructure for
-developing applications based on J2EE 1.4 targeting J2EE-compliant
-application servers, as well as a more generic J2EE tooling
-infrastructure for other Eclipse-based development products.</p>
-<p>Tools provided will include a workbench for developing, deploying,
-testing and debugging J2EE applications on JCP-compliant server
-environments, as well as an exemplary implementation of a plug-in for at
-least one JSR-88 compliant J2EE Server. Included will be a range of
-tools simplifying development with J2EE APIs including EJB, Servlet,
-JSP, JCA, JDBC, JTA, JMS, JMX, JNDI, and Web Services. This
-infrastructure will be architected for extensibility for higher-level
-development constructs providing architectural separations of concern
-and technical abstraction above the level of the J2EE specifications</p>
-<p>The integrated workbench to be delivered would support use cases such
-as " - Develop a JSP page, Enhance the "PetStore" blue-print
-application, Expose a Session Bean as a Web Service".</p>
-<p>The <a href="wtp_project_architecture.html">WTP Project Architecture
-Overview</a> provides a high-level description of the project and
-sub-projects with links to more specific component designs.</p>
-</div>
-
-<div id="section_header">Project attributes</div>
-<div class="content">
-<dl id="gen_list">
- <dt>Downloads:</dt>
- <dd>
- <div id="pipelist_container">
- <ul id="pipelist">
- <li><a href="http://download.eclipse.org/webtools/downloads/">Current
- drivers</a></li>
- </ul>
- </div>
- </dd>
-
- <dt>Development plan:</dt>
- <dd>
- <div id="pipelist_container">
- <ul id="pipelist">
- <li><a
- href="http://www.eclipse.org/webtools/development/planning/milestone_plan_1_0.html">Milestone
- plan</a></li>
- </ul>
- </div>
- </dd>
- <dt>Developers Mailing lists:</dt>
- <dd>
- <div id="pipelist_container">
- <ul id="pipelist">
- <li><a href="mailto:wtp-dev@eclipse.org">wtp-dev</a></li>
- <li><a href="mailto:wtp-wst-dev@eclipse.org">wtp-wst-dev</a></li>
- <li><a href="mailto:wtp-jst-dev@eclipse.org">wtp-jst-dev</a></li>
- </ul>
- </div>
- </dd>
-
- <dt>Users and co-developers Newsgroup:</dt>
- <dd>
- <div id="pipelist_container">
- <ul id="pipelist">
- <li><a href="news:org.eclipse.dev/eclipse.webtools">eclipse.webtools</a></li>
- </ul>
- </div>
- </dd>
- <dt>Dependancies:</dt>
- <dd>
- <div id="pipelist_container">
- <ul id="pipelist">
- <li><a
- href="http://www.eclipse.org/emf/"
- target="_top">Eclipse Modeling Framework</a></li>
- <li><a
- href="http://www.eclipse.org/xsd/"
- target="_top">XSD, XML Schema Infoset Model</a></li>
- <li><a
- href="http://www.eclipse.org/gef/"
- target="_top">Graphical Editing Framework</a></li>
- <li><a href="http://www.eclipse.org/vep/">Java EMF Model (JEM)</a></li>
- </ul>
- </div>
- </dd>
-
- <dt>Projects:</dt>
- <dd>
- <div id="pipelist_container">
- <ul id="pipelist">
- <li><a href="http://www.eclipse.org/webtools/wst/main.html">Web
- Standard Tools (WST)</a></li>
- <li><a href="http://www.eclipse.org/webtools/jst/main.html">J2EE
- Standard Tools (JST)</a></li>
- </ul>
- </div>
- </dd>
-
- <dt>Documentation:</dt>
- <dd>
- <div id="pipelist_container">
- <ul id="pipelist">
- <li><a href="http://www.eclipse.org/webtools/community/community.html">User
- community resources</a></li>
- <li><a href="http://www.eclipse.org/webtools/development/main.html">Developer
- resources</a></li>
- </ul>
- </div>
- </dd>
-
-
-</dl>
-</div>
-
-<div id="section_divider"></div>
-<div id="content">
-<div id="copyright">See <a
- href="http://www.eclipse.org/legal/termsofuse.html">Terms of Use</a>.
-</div>
-</div>
-</body>
-</html>
diff --git a/development/arch_and_design/subsystems/.cvsignore b/development/arch_and_design/subsystems/.cvsignore
deleted file mode 100644
index 8a21ddd..0000000
--- a/development/arch_and_design/subsystems/.cvsignore
+++ /dev/null
@@ -1 +0,0 @@
-buildworkingset.html
diff --git a/development/arch_and_design/subsystems/SubsystemsAndFeatures.html b/development/arch_and_design/subsystems/SubsystemsAndFeatures.html
deleted file mode 100644
index 8ad03bc..0000000
--- a/development/arch_and_design/subsystems/SubsystemsAndFeatures.html
+++ /dev/null
@@ -1,1927 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../../default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../../webtools/wtp.css" type="text/css">
-<title>Subsystems And Features in WTP</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">Subsystems And Features in WTP</font>
-<br>
-<font class="indexsub">Subsystems And Features in WTP</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../../images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<table border="1" cellpadding="10" height="50%" width="70%">
-
-<tbody>
-
-<tr align="left" valign="middle">
-
-<td valign="middle" align="left">
-
-<blockquote style="">
-
-<p>
-
-<cite>
- The background and status of this
- document:
- </cite>
-
-</p>
-
-<p>
-
-<cite>
- 10/09/05 - this is a preliminary
- draft.
- </cite>
-
-</p>
-
-<p>
-
-<cite>
- Version 0.2 October 9, 2005.
- </cite>
-
-</p>
-
-<p>
-
-<cite>David Williams</cite>
-
-</p>
-
-</blockquote>
-
-</td>
-
-</tr>
-
-</tbody>
-
-</table>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Introduction and Background</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The purpose of this document is help organize the large
- thing that WTP is, into smaller chunks that can be
- maintained, documented, composed into other products, etc.
- [Not everything described in this document has to be
- accomplished "all at once", but much progress can be made
- "under the covers", gradually, and iteratively to better
- partition our deliverables, builds, tests, etc. The goal,
- however, is to have the fundamental pattern in place by M8
- and completely implemented by M9].
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- WTP is now over two hundred plugins, if you include the
- documentation and test plugins. While we've tried to reduce
- this number -- and still will be! -- we'll never get to a
- small enough number that a "list of plugins" is a very good
- description of WTP.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- In other words, Eclipse Members who want to extend a subset
- of WTP would have a hard time picking out which plugins to
- bundle. And, even if they could, there are parts of our code
- and process that assume's other parts are there. For
- example, if someone was only going to use a subset WTP, it
- is not tenable for them to use our one "test package" --
- they would either have to do a lot of "hand editing" or not
- run our tests ... or, we could structure things to make it
- easier for them to pick out the tests appropriate to their
- subset of WTP.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Plus, there's some of our deliverables, such as user
- documentation or "isv docs", which can not be packaged on a
- plugin-by-plugin bases. Even our definition of "components"
- is a little too fined grained for most meaningful
- documentation (for example, you can not talk too much about
- XML, without also talking about both DTD's and XML Schemas
- ... but our code plugins for xml, dtds, and schemas are
- separate. Some things, like "generate XML from DTD"
- logically require both XML and DTD to be present.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Hence, this document is to lay out a way to conceptualize
- and specify dependencies in WTP that is more helpful Eclipse
- Members who want to "extend" or "repackage" WTP. While we
- can never satisfy all needs, and some will always want to
- pick and choose things on a plugin by plugin bases, I think
- our architectural subsystems is a more meaningful level of
- composition -- and, basically, the only level we support. As
- a concrete example, if someone really wanted only the
- JavaScript Editor, there might be some different subset of
- code plugins they could extract, but we would not provide
- different packaging for docs, sdk, etc., than simply the WST
- Web Development.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- There has been a concept of architectural "subsystems" in
- WTP for a while, with some refinements being discussed along
- the way. This document is to update (make current) the
- previously documented subsystem, and relate them to the
- desired end-user features and build components. You can read
- our
- <a href="http://www.eclipse.org/org/councils/AC/wtpsnapshot/wst_subproject_architecture.html">
- current architecture document
- </a>
- to see the previous description of sub-systems and their
- dependances. This document is just a refinement of that
- document, not a fundamental change. (and, eventually, all
- the information will be merged to one document).
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- One reason this is important to get clear on, is that it
- effects the way user and SDK docs are assembled. They
- should, basically, be able to be 'assembled" the same way as
- the subsystem can be.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- To help keep this clearest, I'll first describe a few terms.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>Architecural Subsystems.</b>
- This term refers to a collection of plugins which "go
- together" to provide a general class of function, which, as
- a group, have a clear dependency relationship to other
- subsystems.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- This is basically the level we provide our function. For
- example, if we were going to change some XML related
- function, it is easy to imagine it might effect our DTD and
- Schema function (and docs, and tests) but would be less
- likely to effect other parts of WTP.
-
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>End-User Features.</b>
- This term refers to what a user can install (such as via
- update manager), where the dependencies on other features
- needs to be clear and obvious, for updates and maintenance
- and "co-existence" with other Eclipse projects.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>Build Components.</b>
- These are, one the one hand, literally units of the build,
- where obviously dependencies have to be correct to compile.
- On the other hand, these are the lowest level PDE features,
- by which all other features are
- <i>assembled</i>
- . This level is especially important to extenders and "add
- on" providers to WTP, since, sometimes, they may not want to
- pre-req ALL of WTP, but parts of it, and, typically, they do
- not want to assemble their own features on a
- plugin-by-plugin basis, but at a feature level, to ensure
- everything fits together, and "co-exists" with other
- add-on's which may share some dependencies, and not share
- others.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>Delivered packages.</b>
- These correspond to the zip files that can be downloaded
- from our WTP download page. I am not proposing these change
- (much), just the "PDE features" that define what they are.
- While we need further investigation, the "dependency" and
- "include feature" parts of a PDE feature appear to work
- quite well and should make the dependency and packaging
- clearly specifiable.
-
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">End-User Features</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- These are what would be available via update manager. (We do
- need some investigation here to make sure the right things
- are "visible" in update manager, without requiring all
- dependencies to be visible to the end-user).
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>JST</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Business as usual, just what you'd think, what it currently
- is.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>WST</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Business as usual, just what you'd think, what it currently
- is.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>Web Development (WTP 1.0 or 1.5?)</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Like WST, but without Database Feature (I believe the plan
- is to be using DTP project in the WTP 1.5 time-frame, so I
- think advantageous to prepare for that in our 1.0
- timeframe.)
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>XML Development (WTP 1.0 or 1.5?)</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Components required for XML, Schema, and DTD development
- (editing, validation, etc). I'm listing this here as a
- commonly requested subsystem from user community, though am
- unaware of other needs [should be easy to do, however, if
- this proposal accepted].
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Architectural Features</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>Common Subsystem/Feature (wst-common)</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>Common Component</li>
-
-<ul>
-
-<li>
- Extensible Navigator
- <p>
- internalProvisional, proposed to move to Eclipse
- Base 3.2
- </p>
-
-</li>
-
-<li>
- Tabbed Property View
- <p>
- internalProvisional, proposed to move to Eclipse
- Base 3.2
- </p>
-
-</li>
-
-<li>Snippets View</li>
-
-<li>Extensible URI Resolver</li>
-
-<li>common frameworks</li>
-
-<ul>
-
-<li>data operations - IDataModel</li>
-
-<li>data wizards - provisional</li>
-
-<li>environment framework</li>
-
-</ul>
-
-<li>project facets framework</li>
-
-</ul>
-
-<li>Validation Framework Component</li>
-
-<li>
- common.componentcore
- <p>foundation for web project component</p>
-
-</li>
-
-<li>Internet Proxy Settings</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>Web Server Subsystem/Feature (wst-server)</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>Server Component</li>
-
-<li>Internet Component</li>
-
-<ul>
-
-<li>Lightweight Server/Internet Monitor</li>
-
-</ul>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>Database Subsystem/Feature (wst-rdb)</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>DB/SQL - probable DTP project merge</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>XML Subsystem/Feature (wst-xml)</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>XML Component</li>
-
-<li>Schema Component</li>
-
-<li>DTD Component</li>
-
-<li>SSE Component</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>Web Services Subsystem/Feature (wst-ws)</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>WS Component</li>
-
-<li>WSDL Component.</li>
-
-<li>WSI Component</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>Web Resources Subsystem/Feature (wst-web)</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>HTML Component</li>
-
-<li>CSS Component</li>
-
-<li>JavaScript</li>
-
-<li>Web Project Component, HTML Web Project</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>JST Server Subsystem/Feature (jst-server)</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>Server Component</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>
- J2EE Web Subsystem/Feature (WAR, servlets, JSPs) (jst-web)
- </h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>
- J2EE Core Web Model Component [Issue: not currently
- packaged this way]
- </li>
-
-<li>
- Servlet Component/J2EEWebProject ... some API, create
- web component API
- </li>
-
-<li>
- JSP Component ... some internal provisional .. need
- better design documents
- </li>
-
-<li>WS Web Component (JAXRPC)</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>
- J2EE Enterprise Subsystem/Feature (EARs, EJBJar,
- EJBClientJar, RARs) (jst-enterprise)
- </h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>
- J2EE Core Enterprise Model Component [Issue: not
- currently packaged this way]
- </li>
-
-<li>EJB Component</li>
-
-<li>WS Component</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Build Components</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>General Pattern of the Build Components of a Subsystem.</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Each subsystem follows a predictable pattern, with minor
- deviations here and there.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Each of the following "categories" would be one build
- component, for the subsystem -- for 5 per subsystem, which,
- yes, means 45 total build components. Luckily, they all
- follow a standard pattern in their make up and dependencies.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>
- Model/Core plugins (
- <b>-core</b>
- )
- </li>
-
-<p>
- These represent function that has no UI dependencies at
- all. This is where most of the interesting API would be.
- </p>
-
-<li>
- UI plugins and Info plugins (
- <b>-ui</b>
- )
- </li>
-
-<p>
- The "UI" portion is hopefully obvious ... anything
- related to the display, presentation, editors, menus,
- wizards, preference pages (though, note, many
- preferences still have a model or core aspect). In
- particular, any thing that pre-req's SWT (directly or
- indirectly) is considered "UI").
- </p>
-
-<p>
- The info-plugins consist of infopop's (dynamic help)
- which is tied to the UI via "IDs" but has links to the
- user-docs. These info plugins may have NL fragments, but
- those are "pure assembly", added to an install of other
- components, and not part of an WTP build or official
- deliverable.
- </p>
-
-<li>
- User Doc plugins (
- <b>-userdocs</b>
- )
- </li>
-
-<p>
- User docs consists of the xhtml documentation that is
- "browsable" and searchable. They can be packaged as
- "just docs" for serving on the web via an "info center"
- or shipped with product code for offline access via the
- Eclipse help system. These are "just assembled" and do
- not need the code to build, although they are typically
- assembled with the code build, to ensure there is the
- same integration process as with other component teams.
- </p>
-
-<p>
- The point of putting them in well defined places in the
- architecture is to define what content goes where, so as
- new products bundle our subsystems, the documentation
- provided is appropriate. These can have NL fragments for
- translated versions of docs (again, pure "assembly", not
- part of any WTP build or deliverable.
- </p>
-
-<li>
- JUnit Tests and Performance Tests (
- <b>-tests</b>
- )
- </li>
-
-<p>
- The JUnit tests are an important part of every build,
- since they (somewhat) verify the integrity of the build
- without complete testing "by hand".
- </p>
-
-<p>
- While performance tests are not ran at the same time as
- the build or other JUnit tests (because the performance
- tests are ran on a pristine machine) there is little
- cost with building and packaging them together.
- </p>
-
-<p>
- The most important thing is that someone getting only a
- part of WTP, should be able to get the tests relevant to
- that part, and those tests should still succeed without
- tweaking or re-packaging or changing of scripts.
- </p>
-
-<li>
- SKD components (
- <b>-sdk</b>
- )
- <p>
- Source plugin, ISV Documentation, example plugins,
- sdk tools, if any.
- </p>
-
-</li>
-
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h5>
- Dependancies within a subsystem, between build components.
- </h5>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The following figure shows how the build components within
- one subsystem are dependant on each other, using
- 'wst-common' as the example. Here 'depends on' (labeled
- "uses" in the figure) means that plugins in one plugin, can
- 'require' plugins in the dependent build-component. For
- example, things in any common-ui component plugin can use
- any plugin in common-core component plugins (but not
- <i>vice versa</i>
- ).
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><img src="./images/GeneralPattern.gif" alt="Common pattern of inter-subsystem dependencies" border="1" align="bottom"></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h5>
- Dependancies between subsystems, between build components.
- </h5>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The following figure shows how build components are
- specified to be dependent on each other, using wst-xml and
- wst-common as examples. Note that for "plugin dependancies"
- the rule is that anything "on a path" would be allowable,
- though not always shown expllicitly in the figure. For
- example, a plugin in xml-ui feature could require a plugin
- in common-core, even though there is no direct "uses" arrow
- between the two ... there is an indirect one though in that
- xml-ui uses xml-core which uses common-core.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><img src="./images/GeneralPatternCrossSystems.gif" alt="Common pattern of intra-subsystem dependencies" border="1" align="bottom"></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h5>
- Summary of dependancies between build-components of all
- subsystems.
- </h5>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The following shows a summary of how the components from
- subsystems are dependent on each other (the exact UI and
- core paths are not shown, but UI and core would be used in
- the PDE features). Also not shown are the dependancies on
- third-party or how product-adapter components.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><img src="./images/WTPSubsystems.gif" alt="Summary pattern of WTP dependencies" border="1" align="bottom"></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>Additions to the general pattern.</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- For some cases there are some additional build components
- for subsystems: third party code and product specific
- adapters.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>
- Third Party Code (
- <b>third-party-code</b>
- )
- </li>
-
-<p>
- These deviate from the general pattern a little, since
- for many purposes they are summarized as "a collection
- of plugins", in reality, each should be a feature-plugin
- pair (so future updates are easier, and in principle
- could be made available from anywhere, such as the
- original third-party source!.)
- </p>
-
-<p>
- We only package and distribute non-SDK version of the
- third-party code.
- </p>
-
-<li>
- Product Specific Adapters (
- <b>product-adapters</b>
- )
- </li>
-
-<p>
- While we do not ship "other products" in WTP, we do ship
- adapters (or "configuration definitions") for some other
- products ... in the Database components and the
- JST-Server components. We can split those out separately
- for purposes of builds, maintenance releases, etc., so
- this allows WTP extenders to decide to include or not
- include them, without having to create new features of
- the core functionality. This is important for proper
- "co-existence" if an end-user decided to install
- products from two WTP extenders ... we need to provide
- an easy way for only one intact version of the "core
- features" to be used in those cases.
- </p>
-
-<p>
- This also allows the future growth that these "product
- adapters" can be "hosted" by the specific product sites,
- instead of WTP per se.
- </p>
-
-<p>
- This does add a fair amount to complexity, though. (And
- will need to iterate on the exact definition and content
- of this build-component).
- </p>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Relationship to Eclipse Capabilities</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Eclipse has the ability to turn certain capabilities on or
- off. For example, in the base Eclipse install, you could
- turn off Plugin development if you were not going to use
- that. The purpose of this aspect of Eclipse is to simplify
- the interface for the user who does not need certain things.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The distinctions in this document are often highly related
- to "Eclipse Capabilities", but is not a substitute for the
- work we still need to do in that area, and this document is
- to solve a different set of problems.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- There are two implications. One is that we
- <b>will</b>
- want to define some "capabilities" in WTP that correspond to
- our subsystems. For example, even if RDB is installed, we
- might still have a capability for database work, so users
- who are not using it, will not have to see certain menu
- options, etc. But there are other, more detailed kinds of
- capabilities that we might implement some day. A common
- suggestion is that some users "produce" certain components,
- such as web services, or EJBs, etc, but other users only
- "consume" them during their development. So, the "consuming"
- user could have a simplified experience if we had "produce
- and consume" capabilities where appropriate. Our
- "capabilities" work has yet to be designed and planned for,
- but the point I wanted to make here was that in some cases
- the same effect might be achieved by what extenders could
- "package" (e.g. leave out RDB if their product didn't need
- it), but in come cases it could not be -- we will not offer
- separate "PDE features" for the produce vs. consume
- dimension, but (hopefully) someday will offer that improved
- user experience through Eclipse capabilities.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Build Components)</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The listed plugins are preliminary, for review. Its my
- current "best guess" of the right partitions, but will need
- careful study and review from all component teams.
- Eventually, these exact lists and relationships will be
- defined and document "in the code" (via the feature.xml
- files) but until then, thought this would help get a head
- start on reviewing some concrete proposal.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>jst.enterprise_core.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.jst.j2ee</li>
-
-<li>org.eclipse.jst.j2ee.core</li>
-
-<li>org.eclipse.jst.j2ee.ejb</li>
-
-<li>org.eclipse.jst.j2ee.ejb.annotation.model</li>
-
-<li>org.eclipse.jst.j2ee.ejb.annotations.emitter</li>
-
-<li>org.eclipse.jst.j2ee.ejb.annotations.xdoclet</li>
-
-<li>org.eclipse.jst.j2ee.jca</li>
-
-<li>org.eclipse.jst.j2ee.webservice</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>jst.enterprise_tests.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.jst.j2ee.core.tests</li>
-
-<li>org.eclipse.jst.j2ee.core.tests.performance</li>
-
-<li>org.eclipse.jst.j2ee.tests</li>
-
-<li>org.eclipse.jst.j2ee.tests.performance</li>
-
-<li>org.eclipse.jst.validation.sample</li>
-
-<li>org.eclipse.jst.validation.test</li>
-
-<li>org.eclipse.jst.ws.tests</li>
-
-<li>org.eclipse.jst.ws.tests.performance</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>jst.enterprise-ui.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.jst.ejb.ui</li>
-
-<li>org.eclipse.jst.j2ee.ejb.annotations.ui</li>
-
-<li>org.eclipse.jst.j2ee.jca.ui</li>
-
-<li>org.eclipse.jst.j2ee.navigator.ui</li>
-
-<li>org.eclipse.jst.j2ee.ui</li>
-
-<li>org.eclipse.jst.j2ee.webservice.ui</li>
-
-<li>org.eclipse.jst.ws.axis.creation.ui</li>
-
-<li>org.eclipse.jst.ws.consumption</li>
-
-<li>org.eclipse.jst.ws.consumption.ui</li>
-
-<li>org.eclipse.jst.ws.creation.ui</li>
-
-<li>org.eclipse.jst.ws.uddiregistry</li>
-
-<li>org.eclipse.jst.ws.ui</li>
-
-<li>org.eclipse.jst.j2ee.infopop</li>
-
-<li>org.eclipse.jst.ws.axis.infopop</li>
-
-<li>org.eclipse.jst.ws.creation.ejb.ui</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>jst.enterprise_userdoc.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.jst.ejb.doc.user</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>jst.server_core.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.jst.server.core</li>
-
-<li>org.eclipse.jst.server.generic.core</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>jst.server_product_adapters</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.jst.server.generic.serverdefinitions</li>
-
-<li>org.eclipse.jst.server.tomcat.core</li>
-
-<li>org.eclipse.jst.server.tomcat.core.tests</li>
-
-<li>org.eclipse.jst.server.tomcat.tests.performance</li>
-
-<li>org.eclipse.jst.server.tomcat.ui</li>
-
-<li>org.eclipse.jst.server.tomcat.ui.tests</li>
-
-<li>org.eclipse.jst.server.websphere.core</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>jst.server_tests.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.jst.server.core.tests</li>
-
-<li>org.eclipse.jst.server.generic.tests</li>
-
-<li>org.eclipse.jst.server.tomcat.core.tests</li>
-
-<li>org.eclipse.jst.server.tomcat.tests.performance</li>
-
-<li>org.eclipse.jst.server.tomcat.ui.tests</li>
-
-<li>org.eclipse.jst.server.ui.tests</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>jst.server_ui.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.jst.server.generic.ui</li>
-
-<li>org.eclipse.jst.server.ui</li>
-
-<li>org.eclipse.jst.server.ui.infopop</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>jst.server_userdoc.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.jst.server.ui.doc.user</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>jst.web_core.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.jst.common.annotations.controller</li>
-
-<li>org.eclipse.jst.common.annotations.core</li>
-
-<li>org.eclipse.jst.common.frameworks</li>
-
-<li>org.eclipse.jst.common.navigator.java</li>
-
-<li>org.eclipse.jst.j2ee.web</li>
-
-<li>org.eclipse.jst.jsp.core</li>
-
-<li>org.eclipse.jst.ws</li>
-
-<li>org.eclipse.jst.ws.axis.consumption.core</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>jst.web_tests.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.jst.jsp.core.tests</li>
-
-<li>org.eclipse.jst.jsp.tests.encoding</li>
-
-<li>org.eclipse.jst.jsp.ui.tests</li>
-
-<li>org.eclipse.jst.jsp.ui.tests.performance</li>
-
-<li>org.eclipse.jst.servlet.tests</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>jst.web_ui.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.jst.common.annotations.ui</li>
-
-<li>org.eclipse.jst.jsp.ui</li>
-
-<li>org.eclipse.jst.servlet.ui</li>
-
-<li>org.eclipse.jst.ws.axis.consumption.ui</li>
-
-<li>org.eclipse.jst.jsp.ui.infopop</li>
-
-<li>org.eclipse.jst.ws.consumption.infopop</li>
-
-<li>org.eclipse.jst.ws.infopop</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.xml_core.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.dtd.core</li>
-
-<li>org.eclipse.wst.sse.core</li>
-
-<li>org.eclipse.wst.xml.core</li>
-
-<li>org.eclipse.wst.xsd.core</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.xml_sdk.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.xml.source</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.xml_tests.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.dtd.ui.tests</li>
-
-<li>org.eclipse.wst.sse.core.tests</li>
-
-<li>org.eclipse.wst.sse.ui.tests</li>
-
-<li>org.eclipse.wst.sse.ui.tests.performance</li>
-
-<li>org.eclipse.wst.xml.core.tests</li>
-
-<li>org.eclipse.wst.xml.tests.encoding</li>
-
-<li>org.eclipse.wst.xml.ui.tests</li>
-
-<li>org.eclipse.wst.xml.ui.tests.performance</li>
-
-<li>org.eclipse.wst.xml.validation.tests</li>
-
-<li>org.eclipse.wst.xsd.tests.performance</li>
-
-<li>org.eclipse.wst.xsd.validation.tests</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.xml_third_party_plugins</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.apache.xerces</li>
-
-<li>org.apache.xerces.feature</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.xml_ui.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.dtd.ui</li>
-
-<li>org.eclipse.wst.sse.ui</li>
-
-<li>org.eclipse.wst.xml.ui</li>
-
-<li>org.eclipse.wst.xsd.ui</li>
-
-<li>org.eclipse.wst.dtd.ui.infopop</li>
-
-<li>org.eclipse.wst.sse.ui.infopop</li>
-
-<li>org.eclipse.wst.xml.ui.infopop</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.xml_userdoc.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.dtdeditor.doc.user</li>
-
-<li>org.eclipse.wst.sse.doc.user</li>
-
-<li>org.eclipse.wst.xmleditor.doc.user</li>
-
-<li>org.eclipse.wst.xsdeditor.doc.user</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.common_core.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.command.env</li>
-
-<li>org.eclipse.wst.command.env.core</li>
-
-<li>org.eclipse.wst.common.emf</li>
-
-<li>org.eclipse.wst.common.environment</li>
-
-<li>org.eclipse.wst.common.frameworks</li>
-
-<li>org.eclipse.wst.common.modulecore</li>
-
-<li>org.eclipse.wst.common.project.facet.core</li>
-
-<li>org.eclipse.wst.common.uriresolver</li>
-
-<li>org.eclipse.wst.internet.cache</li>
-
-<li>org.eclipse.wst.validation</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.common_sdk.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.common.isvdoc</li>
-
-<li>org.eclipse.wst.common.sdk.source</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.common_tests.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.common.tests</li>
-
-<li>org.eclipse.wst.common.tests.collector</li>
-
-<li>org.eclipse.wst.common.tests.performance</li>
-
-<li>org.eclipse.wst.common.tests.ui</li>
-
-<li>org.eclipse.wst.internet.cache.tests</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.common_ui.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.command.env.ui</li>
-
-<li>org.eclipse.wst.common.frameworks.ui</li>
-
-<li>org.eclipse.wst.common.navigator.views</li>
-
-<li>org.eclipse.wst.common.navigator.workbench</li>
-
-<li>org.eclipse.wst.common.project.facet.ui</li>
-
-<li>org.eclipse.wst.common.snippets</li>
-
-<li>org.eclipse.wst.common.ui</li>
-
-<li>org.eclipse.wst.common.ui.properties</li>
-
-<li>org.eclipse.wst.internet.proxy</li>
-
-<li>org.eclipse.wst.validation.ui</li>
-
-<li>org.eclipse.wst.common.infopop</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.common_userdoc.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.common.user.doc</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.rdb_core.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.rdb.core</li>
-
-<li>org.eclipse.wst.rdb.data.core</li>
-
-<li>org.eclipse.wst.rdb.models.sql</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.rdb_product_adapters.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.rdb.derby</li>
-
-<li>org.eclipse.wst.rdb.mysql</li>
-
-<li>org.eclipse.wst.rdb.dbdefinition.db2.iseries</li>
-
-<li>org.eclipse.wst.rdb.dbdefinition.db2.luw</li>
-
-<li>org.eclipse.wst.rdb.dbdefinition.db2.zseries</li>
-
-<li>org.eclipse.wst.rdb.dbdefinition.derby</li>
-
-<li>org.eclipse.wst.rdb.dbdefinition.informix</li>
-
-<li>org.eclipse.wst.rdb.dbdefinition.mysql</li>
-
-<li>org.eclipse.wst.rdb.dbdefinition.oracle</li>
-
-<li>org.eclipse.wst.rdb.dbdefinition.sqlserver</li>
-
-<li>org.eclipse.wst.rdb.dbdefinition.sybase</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.rdb-sdk.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.rdb.source</li>
-
-<li>org.eclipse.wst.rdp.isvdoc</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.rdb_tests.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.rdb.tests.performance</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.rdb_ui.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.rdb.connection.ui</li>
-
-<li>org.eclipse.wst.rdb.core.ui</li>
-
-<li>org.eclipse.wst.rdb.data.ui</li>
-
-<li>org.eclipse.wst.rdb.derby.ui</li>
-
-<li>org.eclipse.wst.rdb.fe.ui</li>
-
-<li>org.eclipse.wst.rdb.fe.ui.actions</li>
-
-<li>org.eclipse.wst.rdb.models.dbdefinition</li>
-
-<li>org.eclipse.wst.rdb.models.sql.edit</li>
-
-<li>org.eclipse.wst.rdb.outputview</li>
-
-<li>org.eclipse.wst.rdb.server.extensions</li>
-
-<li>org.eclipse.wst.rdb.server.ui</li>
-
-<li>org.eclipse.wst.rdb.sqleditor</li>
-
-<li>org.eclipse.wst.rdb.sqlscrapbook</li>
-
-<li>org.eclipse.wst.rdb.connection.ui.infopop</li>
-
-<li>org.eclipse.wst.rdb.fe.ui.infopop</li>
-
-<li>org.eclipse.wst.rdb.outputview.infopop</li>
-
-<li>org.eclipse.wst.rdb.server.ui.infopop</li>
-
-<li>org.eclipse.wst.rdb.sqleditor.infopop</li>
-
-<li>org.eclipse.wst.rdb.sqlscrapbook.infopop</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.rdb_userdoc.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.datatools.connection.ui.doc.user</li>
-
-<li>org.eclipse.wst.datatools.fe.ui.doc.user</li>
-
-<li>org.eclipse.wst.datatools.server.ui.doc.user</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.server_core.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.internet.monitor.core</li>
-
-<li>org.eclipse.wst.server.core</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.server_sdk.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.rdb.isvdoc</li>
-
-<li>org.eclipse.wst.server.source</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.server_tests.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.internet.monitor.core.tests</li>
-
-<li>org.eclipse.wst.internet.monitor.ui.tests</li>
-
-<li>org.eclipse.wst.server.core.tests</li>
-
-<li>org.eclipse.wst.server.tests.performance</li>
-
-<li>org.eclipse.wst.server.ui.tests</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.server_ui.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.internet.monitor.ui</li>
-
-<li>org.eclipse.wst.server.ui</li>
-
-<li>org.eclipse.wst.server.ui.infopop</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.server_userdoc.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.server.ui.doc.user</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.web_core.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.common.emfworkbench.integration</li>
-
-<li>org.eclipse.wst.css.core</li>
-
-<li>org.eclipse.wst.html.core</li>
-
-<li>org.eclipse.wst.javascript.core</li>
-
-<li>org.eclipse.wst.web</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.web_sdk.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.web.isv.doc</li>
-
-<li>org.eclipse.wst.web.source</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.web_tests.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.css.core.tests</li>
-
-<li>org.eclipse.wst.css.tests.encoding</li>
-
-<li>org.eclipse.wst.css.ui.tests</li>
-
-<li>org.eclipse.wst.css.ui.tests.performance</li>
-
-<li>org.eclipse.wst.html.core.tests</li>
-
-<li>org.eclipse.wst.html.tests.encoding</li>
-
-<li>org.eclipse.wst.html.ui.tests</li>
-
-<li>org.eclipse.wst.html.ui.tests.performance</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.web_third_party_plugins</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.html.standard.dtds</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.web_ui.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.css.ui</li>
-
-<li>org.eclipse.wst.html.ui</li>
-
-<li>org.eclipse.wst.javascript.ui</li>
-
-<li>org.eclipse.wst.web.ui</li>
-
-<li>org.eclipse.wst.css.ui.infopop</li>
-
-<li>org.eclipse.wst.html.ui.infopop</li>
-
-<li>org.eclipse.wst.javascript.ui.infopop</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.web_userdoc.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.webtools.doc.user</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.ws_core.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.ws</li>
-
-<li>org.eclipse.wst.ws.parser</li>
-
-<li>org.eclipse.wst.wsdl</li>
-
-<li>org.eclipse.wst.wsi</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.ws_sdk.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.webservice.source</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.ws_tests.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.ws.tests</li>
-
-<li>org.eclipse.wst.wsdl.tests</li>
-
-<li>org.eclipse.wst.wsdl.tests.performance</li>
-
-<li>org.eclipse.wst.wsdl.tests.ui</li>
-
-<li>org.eclipse.wst.wsdl.validation.tests</li>
-
-<li>org.eclipse.wst.wsi.tests</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>jst.ws_third_party_plugins</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.apache.wsil4j</li>
-
-<li>org.uddi4j</li>
-
-<li>org.wsdl4j</li>
-
-<li>org.apache.wsil4j.feature</li>
-
-<li>org.uddi4j.feature</li>
-
-<li>org.wsdl4j.feature</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.ws_ui.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.ws.explorer</li>
-
-<li>org.eclipse.wst.ws.ui</li>
-
-<li>org.eclipse.wst.wsdl.ui</li>
-
-<li>org.eclipse.wst.wsdl.validation</li>
-
-<li>org.eclipse.wst.wsi.ui</li>
-
-<li>org.eclipse.wst.ws.infopop</li>
-
-<li>org.eclipse.wst.wsdl.ui.doc.user</li>
-
-<li>org.eclipse.wst.wsi.ui.doc.user</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<h4>wst.ws_userdoc.feature</h4>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.wst.wsdleditor.doc.user</li>
-
-</ul>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/development/arch_and_design/subsystems/SubsystemsAndFeatures.xml b/development/arch_and_design/subsystems/SubsystemsAndFeatures.xml
deleted file mode 100644
index e8da2fa..0000000
--- a/development/arch_and_design/subsystems/SubsystemsAndFeatures.xml
+++ /dev/null
@@ -1,1009 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?xml-stylesheet type="text/xsl" href="../../../wtp.xsl"?>
-<html>
- <head>
- <meta
- name="root"
- content="../../../.." />
- <title>Subsystems And Features in WTP</title>
- </head>
- <body>
- <h1>Subsystems And Features in WTP</h1>
- <table
- border="1"
- cellpadding="10"
- height="50%"
- width="70%">
- <tbody>
- <tr
- align="left"
- valign="middle">
- <td
- valign="middle"
- align="left">
- <blockquote style="">
- <p>
- <cite>
- The background and status of this
- document:
- </cite>
- </p>
- <p>
- <cite>
- 10/09/05 - this is a preliminary
- draft.
- </cite>
- </p>
- <p>
- <cite>
- Version 0.2 October 9, 2005.
- </cite>
- </p>
- <p>
- <cite>David Williams</cite>
- </p>
- </blockquote>
- </td>
- </tr>
- </tbody>
- </table>
- <h2>Introduction and Background</h2>
- <p>
- The purpose of this document is help organize the large
- thing that WTP is, into smaller chunks that can be
- maintained, documented, composed into other products, etc.
- [Not everything described in this document has to be
- accomplished "all at once", but much progress can be made
- "under the covers", gradually, and iteratively to better
- partition our deliverables, builds, tests, etc. The goal,
- however, is to have the fundamental pattern in place by M8
- and completely implemented by M9].
- </p>
- <p>
- WTP is now over two hundred plugins, if you include the
- documentation and test plugins. While we've tried to reduce
- this number -- and still will be! -- we'll never get to a
- small enough number that a "list of plugins" is a very good
- description of WTP.
- </p>
- <p>
- In other words, Eclipse Members who want to extend a subset
- of WTP would have a hard time picking out which plugins to
- bundle. And, even if they could, there are parts of our code
- and process that assume's other parts are there. For
- example, if someone was only going to use a subset WTP, it
- is not tenable for them to use our one "test package" --
- they would either have to do a lot of "hand editing" or not
- run our tests ... or, we could structure things to make it
- easier for them to pick out the tests appropriate to their
- subset of WTP.
- </p>
- <p>
- Plus, there's some of our deliverables, such as user
- documentation or "isv docs", which can not be packaged on a
- plugin-by-plugin bases. Even our definition of "components"
- is a little too fined grained for most meaningful
- documentation (for example, you can not talk too much about
- XML, without also talking about both DTD's and XML Schemas
- ... but our code plugins for xml, dtds, and schemas are
- separate. Some things, like "generate XML from DTD"
- logically require both XML and DTD to be present.
- </p>
- <p>
- Hence, this document is to lay out a way to conceptualize
- and specify dependencies in WTP that is more helpful Eclipse
- Members who want to "extend" or "repackage" WTP. While we
- can never satisfy all needs, and some will always want to
- pick and choose things on a plugin by plugin bases, I think
- our architectural subsystems is a more meaningful level of
- composition -- and, basically, the only level we support. As
- a concrete example, if someone really wanted only the
- JavaScript Editor, there might be some different subset of
- code plugins they could extract, but we would not provide
- different packaging for docs, sdk, etc., than simply the WST
- Web Development.
- </p>
- <p>
- There has been a concept of architectural "subsystems" in
- WTP for a while, with some refinements being discussed along
- the way. This document is to update (make current) the
- previously documented subsystem, and relate them to the
- desired end-user features and build components. You can read
- our
- <a
- href="http://www.eclipse.org/org/councils/AC/wtpsnapshot/wst_subproject_architecture.html">
- current architecture document
- </a>
- to see the previous description of sub-systems and their
- dependances. This document is just a refinement of that
- document, not a fundamental change. (and, eventually, all
- the information will be merged to one document).
- </p>
- <p>
- One reason this is important to get clear on, is that it
- effects the way user and SDK docs are assembled. They
- should, basically, be able to be 'assembled" the same way as
- the subsystem can be.
- </p>
- <p>
- To help keep this clearest, I'll first describe a few terms.
- </p>
- <p>
- <b>Architecural Subsystems.</b>
- This term refers to a collection of plugins which "go
- together" to provide a general class of function, which, as
- a group, have a clear dependency relationship to other
- subsystems.
- </p>
- <p>
- This is basically the level we provide our function. For
- example, if we were going to change some XML related
- function, it is easy to imagine it might effect our DTD and
- Schema function (and docs, and tests) but would be less
- likely to effect other parts of WTP.
-
- </p>
- <p>
- <b>End-User Features.</b>
- This term refers to what a user can install (such as via
- update manager), where the dependencies on other features
- needs to be clear and obvious, for updates and maintenance
- and "co-existence" with other Eclipse projects.
- </p>
- <p>
- <b>Build Components.</b>
- These are, one the one hand, literally units of the build,
- where obviously dependencies have to be correct to compile.
- On the other hand, these are the lowest level PDE features,
- by which all other features are
- <i>assembled</i>
- . This level is especially important to extenders and "add
- on" providers to WTP, since, sometimes, they may not want to
- pre-req ALL of WTP, but parts of it, and, typically, they do
- not want to assemble their own features on a
- plugin-by-plugin basis, but at a feature level, to ensure
- everything fits together, and "co-exists" with other
- add-on's which may share some dependencies, and not share
- others.
- </p>
- <p>
- <b>Delivered packages.</b>
- These correspond to the zip files that can be downloaded
- from our WTP download page. I am not proposing these change
- (much), just the "PDE features" that define what they are.
- While we need further investigation, the "dependency" and
- "include feature" parts of a PDE feature appear to work
- quite well and should make the dependency and packaging
- clearly specifiable.
-
- </p>
- <h2>End-User Features</h2>
- <p>
- These are what would be available via update manager. (We do
- need some investigation here to make sure the right things
- are "visible" in update manager, without requiring all
- dependencies to be visible to the end-user).
- </p>
- <h4>JST</h4>
- <p>
- Business as usual, just what you'd think, what it currently
- is.
- </p>
- <h4>WST</h4>
- <p>
- Business as usual, just what you'd think, what it currently
- is.
- </p>
- <h4>Web Development (WTP 1.0 or 1.5?)</h4>
- <p>
- Like WST, but without Database Feature (I believe the plan
- is to be using DTP project in the WTP 1.5 time-frame, so I
- think advantageous to prepare for that in our 1.0
- timeframe.)
- </p>
- <h4>XML Development (WTP 1.0 or 1.5?)</h4>
- <p>
- Components required for XML, Schema, and DTD development
- (editing, validation, etc). I'm listing this here as a
- commonly requested subsystem from user community, though am
- unaware of other needs [should be easy to do, however, if
- this proposal accepted].
- </p>
-
- <h2>Architectural Features</h2>
-
- <h4>Common Subsystem/Feature (wst-common)</h4>
-
- <ul>
- <li>Common Component</li>
- <ul>
- <li>
- Extensible Navigator
- <p>
- internalProvisional, proposed to move to Eclipse
- Base 3.2
- </p>
- </li>
- <li>
- Tabbed Property View
- <p>
- internalProvisional, proposed to move to Eclipse
- Base 3.2
- </p>
- </li>
- <li>Snippets View</li>
- <li>Extensible URI Resolver</li>
- <li>common frameworks</li>
- <ul>
- <li>data operations - IDataModel</li>
- <li>data wizards - provisional</li>
- <li>environment framework</li>
- </ul>
- <li>project facets framework</li>
- </ul>
- <li>Validation Framework Component</li>
- <li>
- common.componentcore
- <p>foundation for web project component</p>
- </li>
- <li>Internet Proxy Settings</li>
- </ul>
-
- <h4>Web Server Subsystem/Feature (wst-server)</h4>
- <ul>
- <li>Server Component</li>
- <li>Internet Component</li>
- <ul>
- <li>Lightweight Server/Internet Monitor</li>
- </ul>
- </ul>
-
- <h4>Database Subsystem/Feature (wst-rdb)</h4>
- <ul>
- <li>DB/SQL - probable DTP project merge</li>
- </ul>
- <h4>XML Subsystem/Feature (wst-xml)</h4>
- <ul>
- <li>XML Component</li>
- <li>Schema Component</li>
- <li>DTD Component</li>
- <li>SSE Component</li>
- </ul>
- <h4>Web Services Subsystem/Feature (wst-ws)</h4>
- <ul>
- <li>WS Component</li>
- <li>WSDL Component.</li>
- <li>WSI Component</li>
- </ul>
- <h4>Web Resources Subsystem/Feature (wst-web)</h4>
- <ul>
- <li>HTML Component</li>
- <li>CSS Component</li>
- <li>JavaScript</li>
- <li>Web Project Component, HTML Web Project</li>
- </ul>
-
-
- <h4>JST Server Subsystem/Feature (jst-server)</h4>
- <ul>
- <li>Server Component</li>
- </ul>
-
-
- <h4>
- J2EE Web Subsystem/Feature (WAR, servlets, JSPs) (jst-web)
- </h4>
- <ul>
- <li>
- J2EE Core Web Model Component [Issue: not currently
- packaged this way]
- </li>
- <li>
- Servlet Component/J2EEWebProject ... some API, create
- web component API
- </li>
- <li>
- JSP Component ... some internal provisional .. need
- better design documents
- </li>
- <li>WS Web Component (JAXRPC)</li>
- </ul>
- <h4>
- J2EE Enterprise Subsystem/Feature (EARs, EJBJar,
- EJBClientJar, RARs) (jst-enterprise)
- </h4>
- <ul>
- <li>
- J2EE Core Enterprise Model Component [Issue: not
- currently packaged this way]
- </li>
- <li>EJB Component</li>
- <li>WS Component</li>
- </ul>
-
-
- <h2>Build Components</h2>
-
- <h4>General Pattern of the Build Components of a Subsystem.</h4>
- <p>
- Each subsystem follows a predictable pattern, with minor
- deviations here and there.
- </p>
- <p>
- Each of the following "categories" would be one build
- component, for the subsystem -- for 5 per subsystem, which,
- yes, means 45 total build components. Luckily, they all
- follow a standard pattern in their make up and dependencies.
- </p>
- <ul>
- <li>
- Model/Core plugins (
- <b>-core</b>
- )
- </li>
- <p>
- These represent function that has no UI dependencies at
- all. This is where most of the interesting API would be.
- </p>
- <li>
- UI plugins and Info plugins (
- <b>-ui</b>
- )
- </li>
- <p>
- The "UI" portion is hopefully obvious ... anything
- related to the display, presentation, editors, menus,
- wizards, preference pages (though, note, many
- preferences still have a model or core aspect). In
- particular, any thing that pre-req's SWT (directly or
- indirectly) is considered "UI").
- </p>
- <p>
- The info-plugins consist of infopop's (dynamic help)
- which is tied to the UI via "IDs" but has links to the
- user-docs. These info plugins may have NL fragments, but
- those are "pure assembly", added to an install of other
- components, and not part of an WTP build or official
- deliverable.
- </p>
- <li>
- User Doc plugins (
- <b>-userdocs</b>
- )
- </li>
- <p>
- User docs consists of the xhtml documentation that is
- "browsable" and searchable. They can be packaged as
- "just docs" for serving on the web via an "info center"
- or shipped with product code for offline access via the
- Eclipse help system. These are "just assembled" and do
- not need the code to build, although they are typically
- assembled with the code build, to ensure there is the
- same integration process as with other component teams.
- </p>
- <p>
- The point of putting them in well defined places in the
- architecture is to define what content goes where, so as
- new products bundle our subsystems, the documentation
- provided is appropriate. These can have NL fragments for
- translated versions of docs (again, pure "assembly", not
- part of any WTP build or deliverable.
- </p>
- <li>
- JUnit Tests and Performance Tests (
- <b>-tests</b>
- )
- </li>
- <p>
- The JUnit tests are an important part of every build,
- since they (somewhat) verify the integrity of the build
- without complete testing "by hand".
- </p>
- <p>
- While performance tests are not ran at the same time as
- the build or other JUnit tests (because the performance
- tests are ran on a pristine machine) there is little
- cost with building and packaging them together.
- </p>
- <p>
- The most important thing is that someone getting only a
- part of WTP, should be able to get the tests relevant to
- that part, and those tests should still succeed without
- tweaking or re-packaging or changing of scripts.
- </p>
- <li>
- SKD components (
- <b>-sdk</b>
- )
- <p>
- Source plugin, ISV Documentation, example plugins,
- sdk tools, if any.
- </p>
- </li>
-
- </ul>
- <h5>
- Dependancies within a subsystem, between build components.
- </h5>
- <p>
- The following figure shows how the build components within
- one subsystem are dependant on each other, using
- 'wst-common' as the example. Here 'depends on' (labeled
- "uses" in the figure) means that plugins in one plugin, can
- 'require' plugins in the dependent build-component. For
- example, things in any common-ui component plugin can use
- any plugin in common-core component plugins (but not
- <i>vice versa</i>
- ).
- </p>
- <img
- src="./images/GeneralPattern.gif"
- alt="Common pattern of inter-subsystem dependencies"
- border="1"
- align="bottom" />
- <h5>
- Dependancies between subsystems, between build components.
- </h5>
- <p>
- The following figure shows how build components are
- specified to be dependent on each other, using wst-xml and
- wst-common as examples. Note that for "plugin dependancies"
- the rule is that anything "on a path" would be allowable,
- though not always shown expllicitly in the figure. For
- example, a plugin in xml-ui feature could require a plugin
- in common-core, even though there is no direct "uses" arrow
- between the two ... there is an indirect one though in that
- xml-ui uses xml-core which uses common-core.
- </p>
- <img
- src="./images/GeneralPatternCrossSystems.gif"
- alt="Common pattern of intra-subsystem dependencies"
- border="1"
- align="bottom" />
- <h5>
- Summary of dependancies between build-components of all
- subsystems.
- </h5>
- <p>
- The following shows a summary of how the components from
- subsystems are dependent on each other (the exact UI and
- core paths are not shown, but UI and core would be used in
- the PDE features). Also not shown are the dependancies on
- third-party or how product-adapter components.
- </p>
- <img
- src="./images/WTPSubsystems.gif"
- alt="Summary pattern of WTP dependencies"
- border="1"
- align="bottom" />
-
- <h4>Additions to the general pattern.</h4>
- <p>
- For some cases there are some additional build components
- for subsystems: third party code and product specific
- adapters.
- </p>
- <ul>
- <li>
- Third Party Code (
- <b>third-party-code</b>
- )
- </li>
- <p>
- These deviate from the general pattern a little, since
- for many purposes they are summarized as "a collection
- of plugins", in reality, each should be a feature-plugin
- pair (so future updates are easier, and in principle
- could be made available from anywhere, such as the
- original third-party source!.)
- </p>
- <p>
- We only package and distribute non-SDK version of the
- third-party code.
- </p>
- <li>
- Product Specific Adapters (
- <b>product-adapters</b>
- )
- </li>
- <p>
- While we do not ship "other products" in WTP, we do ship
- adapters (or "configuration definitions") for some other
- products ... in the Database components and the
- JST-Server components. We can split those out separately
- for purposes of builds, maintenance releases, etc., so
- this allows WTP extenders to decide to include or not
- include them, without having to create new features of
- the core functionality. This is important for proper
- "co-existence" if an end-user decided to install
- products from two WTP extenders ... we need to provide
- an easy way for only one intact version of the "core
- features" to be used in those cases.
- </p>
- <p>
- This also allows the future growth that these "product
- adapters" can be "hosted" by the specific product sites,
- instead of WTP per se.
- </p>
- <p>
- This does add a fair amount to complexity, though. (And
- will need to iterate on the exact definition and content
- of this build-component).
- </p>
- </ul>
- <h2>Relationship to Eclipse Capabilities</h2>
- <p>
- Eclipse has the ability to turn certain capabilities on or
- off. For example, in the base Eclipse install, you could
- turn off Plugin development if you were not going to use
- that. The purpose of this aspect of Eclipse is to simplify
- the interface for the user who does not need certain things.
- </p>
- <p>
- The distinctions in this document are often highly related
- to "Eclipse Capabilities", but is not a substitute for the
- work we still need to do in that area, and this document is
- to solve a different set of problems.
- </p>
- <p>
- There are two implications. One is that we
- <b>will</b>
- want to define some "capabilities" in WTP that correspond to
- our subsystems. For example, even if RDB is installed, we
- might still have a capability for database work, so users
- who are not using it, will not have to see certain menu
- options, etc. But there are other, more detailed kinds of
- capabilities that we might implement some day. A common
- suggestion is that some users "produce" certain components,
- such as web services, or EJBs, etc, but other users only
- "consume" them during their development. So, the "consuming"
- user could have a simplified experience if we had "produce
- and consume" capabilities where appropriate. Our
- "capabilities" work has yet to be designed and planned for,
- but the point I wanted to make here was that in some cases
- the same effect might be achieved by what extenders could
- "package" (e.g. leave out RDB if their product didn't need
- it), but in come cases it could not be -- we will not offer
- separate "PDE features" for the produce vs. consume
- dimension, but (hopefully) someday will offer that improved
- user experience through Eclipse capabilities.
- </p>
- <h2>Build Components)</h2>
- <p>
- The listed plugins are preliminary, for review. Its my
- current "best guess" of the right partitions, but will need
- careful study and review from all component teams.
- Eventually, these exact lists and relationships will be
- defined and document "in the code" (via the feature.xml
- files) but until then, thought this would help get a head
- start on reviewing some concrete proposal.
- </p>
-
-
-
-<h4>jst.enterprise_core.feature</h4>
-<ul>
-<li>org.eclipse.jst.j2ee</li>
-<li>org.eclipse.jst.j2ee.core</li>
-<li>org.eclipse.jst.j2ee.ejb</li>
-<li>org.eclipse.jst.j2ee.ejb.annotation.model</li>
-<li>org.eclipse.jst.j2ee.ejb.annotations.emitter</li>
-<li>org.eclipse.jst.j2ee.ejb.annotations.xdoclet</li>
-<li>org.eclipse.jst.j2ee.jca</li>
-<li>org.eclipse.jst.j2ee.webservice</li>
-</ul>
-
-<h4>jst.enterprise_tests.feature</h4>
-<ul>
-<li>org.eclipse.jst.j2ee.core.tests</li>
-<li>org.eclipse.jst.j2ee.core.tests.performance</li>
-<li>org.eclipse.jst.j2ee.tests</li>
-<li>org.eclipse.jst.j2ee.tests.performance</li>
-<li>org.eclipse.jst.validation.sample</li>
-<li>org.eclipse.jst.validation.test</li>
-<li>org.eclipse.jst.ws.tests</li>
-<li>org.eclipse.jst.ws.tests.performance</li>
-</ul>
-
-<h4>jst.enterprise-ui.feature</h4>
-<ul>
-<li>org.eclipse.jst.ejb.ui</li>
-<li>org.eclipse.jst.j2ee.ejb.annotations.ui</li>
-<li>org.eclipse.jst.j2ee.jca.ui</li>
-<li>org.eclipse.jst.j2ee.navigator.ui</li>
-<li>org.eclipse.jst.j2ee.ui</li>
-<li>org.eclipse.jst.j2ee.webservice.ui</li>
-<li>org.eclipse.jst.ws.axis.creation.ui</li>
-<li>org.eclipse.jst.ws.consumption</li>
-<li>org.eclipse.jst.ws.consumption.ui</li>
-<li>org.eclipse.jst.ws.creation.ui</li>
-<li>org.eclipse.jst.ws.uddiregistry</li>
-<li>org.eclipse.jst.ws.ui</li>
-<li>org.eclipse.jst.j2ee.infopop</li>
-<li>org.eclipse.jst.ws.axis.infopop</li>
-<li>org.eclipse.jst.ws.creation.ejb.ui</li>
-</ul>
-
-<h4>jst.enterprise_userdoc.feature</h4>
-<ul>
-<li>org.eclipse.jst.ejb.doc.user</li>
-</ul>
-
-<h4>jst.server_core.feature</h4>
-<ul>
-<li>org.eclipse.jst.server.core</li>
-<li>org.eclipse.jst.server.generic.core</li>
-</ul>
-
-<h4>jst.server_product_adapters</h4>
-<ul>
-<li>org.eclipse.jst.server.generic.serverdefinitions</li>
-<li>org.eclipse.jst.server.tomcat.core</li>
-<li>org.eclipse.jst.server.tomcat.core.tests</li>
-<li>org.eclipse.jst.server.tomcat.tests.performance</li>
-<li>org.eclipse.jst.server.tomcat.ui</li>
-<li>org.eclipse.jst.server.tomcat.ui.tests</li>
-<li>org.eclipse.jst.server.websphere.core</li>
-</ul>
-
-<h4>jst.server_tests.feature</h4>
-<ul>
-<li>org.eclipse.jst.server.core.tests</li>
-<li>org.eclipse.jst.server.generic.tests</li>
-<li>org.eclipse.jst.server.tomcat.core.tests</li>
-<li>org.eclipse.jst.server.tomcat.tests.performance</li>
-<li>org.eclipse.jst.server.tomcat.ui.tests</li>
-<li>org.eclipse.jst.server.ui.tests</li>
-</ul>
-
-<h4>jst.server_ui.feature</h4>
-<ul>
-<li>org.eclipse.jst.server.generic.ui</li>
-<li>org.eclipse.jst.server.ui</li>
-<li>org.eclipse.jst.server.ui.infopop</li>
-</ul>
-
-<h4>jst.server_userdoc.feature</h4>
-<ul>
-<li>org.eclipse.jst.server.ui.doc.user</li>
-</ul>
-
-<h4>jst.web_core.feature</h4>
-<ul>
-<li>org.eclipse.jst.common.annotations.controller</li>
-<li>org.eclipse.jst.common.annotations.core</li>
-<li>org.eclipse.jst.common.frameworks</li>
-<li>org.eclipse.jst.common.navigator.java</li>
-<li>org.eclipse.jst.j2ee.web</li>
-<li>org.eclipse.jst.jsp.core</li>
-<li>org.eclipse.jst.ws</li>
-<li>org.eclipse.jst.ws.axis.consumption.core</li>
-</ul>
-
-<h4>jst.web_tests.feature</h4>
-<ul>
-<li>org.eclipse.jst.jsp.core.tests</li>
-<li>org.eclipse.jst.jsp.tests.encoding</li>
-<li>org.eclipse.jst.jsp.ui.tests</li>
-<li>org.eclipse.jst.jsp.ui.tests.performance</li>
-<li>org.eclipse.jst.servlet.tests</li>
-</ul>
-
-<h4>jst.web_ui.feature</h4>
-<ul>
-<li>org.eclipse.jst.common.annotations.ui</li>
-<li>org.eclipse.jst.jsp.ui</li>
-<li>org.eclipse.jst.servlet.ui</li>
-<li>org.eclipse.jst.ws.axis.consumption.ui</li>
-<li>org.eclipse.jst.jsp.ui.infopop</li>
-<li>org.eclipse.jst.ws.consumption.infopop</li>
-<li>org.eclipse.jst.ws.infopop</li>
-</ul>
-
-<h4>wst.xml_core.feature</h4>
-<ul>
-<li>org.eclipse.wst.dtd.core</li>
-<li>org.eclipse.wst.sse.core</li>
-<li>org.eclipse.wst.xml.core</li>
-<li>org.eclipse.wst.xsd.core</li>
-</ul>
-
-<h4>wst.xml_sdk.feature</h4>
-<ul>
-<li>org.eclipse.wst.xml.source</li>
-</ul>
-
-<h4>wst.xml_tests.feature</h4>
-<ul>
-<li>org.eclipse.wst.dtd.ui.tests</li>
-<li>org.eclipse.wst.sse.core.tests</li>
-<li>org.eclipse.wst.sse.ui.tests</li>
-<li>org.eclipse.wst.sse.ui.tests.performance</li>
-<li>org.eclipse.wst.xml.core.tests</li>
-<li>org.eclipse.wst.xml.tests.encoding</li>
-<li>org.eclipse.wst.xml.ui.tests</li>
-<li>org.eclipse.wst.xml.ui.tests.performance</li>
-<li>org.eclipse.wst.xml.validation.tests</li>
-<li>org.eclipse.wst.xsd.tests.performance</li>
-<li>org.eclipse.wst.xsd.validation.tests</li>
-</ul>
-
-<h4>wst.xml_third_party_plugins</h4>
-<ul>
-<li>org.apache.xerces</li>
-<li>org.apache.xerces.feature</li>
-</ul>
-
-<h4>wst.xml_ui.feature</h4>
-<ul>
-<li>org.eclipse.wst.dtd.ui</li>
-<li>org.eclipse.wst.sse.ui</li>
-<li>org.eclipse.wst.xml.ui</li>
-<li>org.eclipse.wst.xsd.ui</li>
-<li>org.eclipse.wst.dtd.ui.infopop</li>
-<li>org.eclipse.wst.sse.ui.infopop</li>
-<li>org.eclipse.wst.xml.ui.infopop</li>
-</ul>
-
-<h4>wst.xml_userdoc.feature</h4>
-<ul>
-<li>org.eclipse.wst.dtdeditor.doc.user</li>
-<li>org.eclipse.wst.sse.doc.user</li>
-<li>org.eclipse.wst.xmleditor.doc.user</li>
-<li>org.eclipse.wst.xsdeditor.doc.user</li>
-</ul>
-
-<h4>wst.common_core.feature</h4>
-<ul>
-<li>org.eclipse.wst.command.env</li>
-<li>org.eclipse.wst.command.env.core</li>
-<li>org.eclipse.wst.common.emf</li>
-<li>org.eclipse.wst.common.environment</li>
-<li>org.eclipse.wst.common.frameworks</li>
-<li>org.eclipse.wst.common.modulecore</li>
-<li>org.eclipse.wst.common.project.facet.core</li>
-<li>org.eclipse.wst.common.uriresolver</li>
-<li>org.eclipse.wst.internet.cache</li>
-<li>org.eclipse.wst.validation</li>
-</ul>
-
-
-<h4>wst.common_sdk.feature</h4>
-<ul>
-<li>org.eclipse.wst.common.isvdoc</li>
-<li>org.eclipse.wst.common.sdk.source</li>
-</ul>
-
-<h4>wst.common_tests.feature</h4>
-<ul>
-<li>org.eclipse.wst.common.tests</li>
-<li>org.eclipse.wst.common.tests.collector</li>
-<li>org.eclipse.wst.common.tests.performance</li>
-<li>org.eclipse.wst.common.tests.ui</li>
-<li>org.eclipse.wst.internet.cache.tests</li>
-</ul>
-
-<h4>wst.common_ui.feature</h4>
-<ul>
-<li>org.eclipse.wst.command.env.ui</li>
-<li>org.eclipse.wst.common.frameworks.ui</li>
-<li>org.eclipse.wst.common.navigator.views</li>
-<li>org.eclipse.wst.common.navigator.workbench</li>
-<li>org.eclipse.wst.common.project.facet.ui</li>
-<li>org.eclipse.wst.common.snippets</li>
-<li>org.eclipse.wst.common.ui</li>
-<li>org.eclipse.wst.common.ui.properties</li>
-<li>org.eclipse.wst.internet.proxy</li>
-<li>org.eclipse.wst.validation.ui</li>
-<li>org.eclipse.wst.common.infopop</li>
-</ul>
-
-<h4>wst.common_userdoc.feature</h4>
-<ul>
-<li>org.eclipse.wst.common.user.doc</li>
-</ul>
-
-<h4>wst.rdb_core.feature</h4>
-<ul>
-<li>org.eclipse.wst.rdb.core</li>
-<li>org.eclipse.wst.rdb.data.core</li>
-<li>org.eclipse.wst.rdb.models.sql</li>
-</ul>
-
-<h4>wst.rdb_product_adapters.feature</h4>
-<ul>
-<li>org.eclipse.wst.rdb.derby</li>
-<li>org.eclipse.wst.rdb.mysql</li>
-<li>org.eclipse.wst.rdb.dbdefinition.db2.iseries</li>
-<li>org.eclipse.wst.rdb.dbdefinition.db2.luw</li>
-<li>org.eclipse.wst.rdb.dbdefinition.db2.zseries</li>
-<li>org.eclipse.wst.rdb.dbdefinition.derby</li>
-<li>org.eclipse.wst.rdb.dbdefinition.informix</li>
-<li>org.eclipse.wst.rdb.dbdefinition.mysql</li>
-<li>org.eclipse.wst.rdb.dbdefinition.oracle</li>
-<li>org.eclipse.wst.rdb.dbdefinition.sqlserver</li>
-<li>org.eclipse.wst.rdb.dbdefinition.sybase</li>
-</ul>
-
-<h4>wst.rdb-sdk.feature</h4>
-<ul>
-<li>org.eclipse.wst.rdb.source</li>
-<li>org.eclipse.wst.rdp.isvdoc</li>
-</ul>
-
-<h4>wst.rdb_tests.feature</h4>
-<ul>
-<li>org.eclipse.wst.rdb.tests.performance</li>
-</ul>
-
-<h4>wst.rdb_ui.feature</h4>
-<ul>
-<li>org.eclipse.wst.rdb.connection.ui</li>
-<li>org.eclipse.wst.rdb.core.ui</li>
-<li>org.eclipse.wst.rdb.data.ui</li>
-<li>org.eclipse.wst.rdb.derby.ui</li>
-<li>org.eclipse.wst.rdb.fe.ui</li>
-<li>org.eclipse.wst.rdb.fe.ui.actions</li>
-<li>org.eclipse.wst.rdb.models.dbdefinition</li>
-<li>org.eclipse.wst.rdb.models.sql.edit</li>
-<li>org.eclipse.wst.rdb.outputview</li>
-<li>org.eclipse.wst.rdb.server.extensions</li>
-<li>org.eclipse.wst.rdb.server.ui</li>
-<li>org.eclipse.wst.rdb.sqleditor</li>
-<li>org.eclipse.wst.rdb.sqlscrapbook</li>
-<li>org.eclipse.wst.rdb.connection.ui.infopop</li>
-<li>org.eclipse.wst.rdb.fe.ui.infopop</li>
-<li>org.eclipse.wst.rdb.outputview.infopop</li>
-<li>org.eclipse.wst.rdb.server.ui.infopop</li>
-<li>org.eclipse.wst.rdb.sqleditor.infopop</li>
-<li>org.eclipse.wst.rdb.sqlscrapbook.infopop</li>
-</ul>
-
-<h4>wst.rdb_userdoc.feature</h4>
-<ul>
-<li>org.eclipse.wst.datatools.connection.ui.doc.user</li>
-<li>org.eclipse.wst.datatools.fe.ui.doc.user</li>
-<li>org.eclipse.wst.datatools.server.ui.doc.user</li>
-</ul>
-
-<h4>wst.server_core.feature</h4>
-<ul>
-<li>org.eclipse.wst.internet.monitor.core</li>
-<li>org.eclipse.wst.server.core</li>
-</ul>
-
-<h4>wst.server_sdk.feature</h4>
-<ul>
-<li>org.eclipse.wst.rdb.isvdoc</li>
-<li>org.eclipse.wst.server.source</li>
-</ul>
-
-<h4>wst.server_tests.feature</h4>
-<ul>
-<li>org.eclipse.wst.internet.monitor.core.tests</li>
-<li>org.eclipse.wst.internet.monitor.ui.tests</li>
-<li>org.eclipse.wst.server.core.tests</li>
-<li>org.eclipse.wst.server.tests.performance</li>
-<li>org.eclipse.wst.server.ui.tests</li>
-</ul>
-
-<h4>wst.server_ui.feature</h4>
-<ul>
-<li>org.eclipse.wst.internet.monitor.ui</li>
-<li>org.eclipse.wst.server.ui</li>
-<li>org.eclipse.wst.server.ui.infopop</li>
-</ul>
-
-<h4>wst.server_userdoc.feature</h4>
-<ul>
-<li>org.eclipse.wst.server.ui.doc.user</li>
-</ul>
-
-<h4>wst.web_core.feature</h4>
-<ul>
-<li>org.eclipse.wst.common.emfworkbench.integration</li>
-<li>org.eclipse.wst.css.core</li>
-<li>org.eclipse.wst.html.core</li>
-<li>org.eclipse.wst.javascript.core</li>
-<li>org.eclipse.wst.web</li>
-</ul>
-
-<h4>wst.web_sdk.feature</h4>
-<ul>
-<li>org.eclipse.wst.web.isv.doc</li>
-<li>org.eclipse.wst.web.source</li>
-</ul>
-
-<h4>wst.web_tests.feature</h4>
-<ul>
-<li>org.eclipse.wst.css.core.tests</li>
-<li>org.eclipse.wst.css.tests.encoding</li>
-<li>org.eclipse.wst.css.ui.tests</li>
-<li>org.eclipse.wst.css.ui.tests.performance</li>
-<li>org.eclipse.wst.html.core.tests</li>
-<li>org.eclipse.wst.html.tests.encoding</li>
-<li>org.eclipse.wst.html.ui.tests</li>
-<li>org.eclipse.wst.html.ui.tests.performance</li>
-</ul>
-
-<h4>wst.web_third_party_plugins</h4>
-<ul>
-<li>org.eclipse.wst.html.standard.dtds</li>
-</ul>
-
-<h4>wst.web_ui.feature</h4>
-<ul>
-<li>org.eclipse.wst.css.ui</li>
-<li>org.eclipse.wst.html.ui</li>
-<li>org.eclipse.wst.javascript.ui</li>
-<li>org.eclipse.wst.web.ui</li>
-<li>org.eclipse.wst.css.ui.infopop</li>
-<li>org.eclipse.wst.html.ui.infopop</li>
-<li>org.eclipse.wst.javascript.ui.infopop</li>
-</ul>
-
-<h4>wst.web_userdoc.feature</h4>
-<ul>
-<li>org.eclipse.wst.webtools.doc.user</li>
-</ul>
-
-<h4>wst.ws_core.feature</h4>
-<ul>
-<li>org.eclipse.wst.ws</li>
-<li>org.eclipse.wst.ws.parser</li>
-<li>org.eclipse.wst.wsdl</li>
-<li>org.eclipse.wst.wsi</li>
-</ul>
-
-<h4>wst.ws_sdk.feature</h4>
-<ul>
-<li>org.eclipse.wst.webservice.source</li>
-</ul>
-
-<h4>wst.ws_tests.feature</h4>
-<ul>
-<li>org.eclipse.wst.ws.tests</li>
-<li>org.eclipse.wst.wsdl.tests</li>
-<li>org.eclipse.wst.wsdl.tests.performance</li>
-<li>org.eclipse.wst.wsdl.tests.ui</li>
-<li>org.eclipse.wst.wsdl.validation.tests</li>
-<li>org.eclipse.wst.wsi.tests</li>
-</ul>
-
-<h4>jst.ws_third_party_plugins</h4>
-<ul>
-<li>org.apache.wsil4j</li>
-<li>org.uddi4j</li>
-<li>org.wsdl4j</li>
-<li>org.apache.wsil4j.feature</li>
-<li>org.uddi4j.feature</li>
-<li>org.wsdl4j.feature</li>
-</ul>
-
-<h4>wst.ws_ui.feature</h4>
-<ul>
-<li>org.eclipse.wst.ws.explorer</li>
-<li>org.eclipse.wst.ws.ui</li>
-<li>org.eclipse.wst.wsdl.ui</li>
-<li>org.eclipse.wst.wsdl.validation</li>
-<li>org.eclipse.wst.wsi.ui</li>
-<li>org.eclipse.wst.ws.infopop</li>
-<li>org.eclipse.wst.wsdl.ui.doc.user</li>
-<li>org.eclipse.wst.wsi.ui.doc.user</li>
-</ul>
-
-<h4>wst.ws_userdoc.feature</h4>
-<ul>
-<li>org.eclipse.wst.wsdleditor.doc.user</li>
-</ul>
-
-
-
-
-
- </body>
-</html>
-
-
-
-
diff --git a/development/arch_and_design/subsystems/buildworkingset.xml b/development/arch_and_design/subsystems/buildworkingset.xml
deleted file mode 100644
index 4f26345..0000000
--- a/development/arch_and_design/subsystems/buildworkingset.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<project
- name="workingsetconversion"
- default="main"
- basedir=".">
- <copy tofile="./localworkingsets.xml" file="D:/builds/Workspaces/pureHeadWTP/.metadata/.plugins/org.eclipse.ui.workbench/workingsets.xml"></copy>
- <target
- name="main"
- description="Converts localworkingsets.xml to produce localworkingset.html">
- <xslt
- in="localworkingsets.xml"
- out="localworkingsets.html"
- style="WorkingSetToHTML.xsl"
- force="true" />
- </target>
-</project>
\ No newline at end of file
diff --git a/development/arch_and_design/subsystems/images/GeneralPattern.gif b/development/arch_and_design/subsystems/images/GeneralPattern.gif
deleted file mode 100644
index 141a203..0000000
--- a/development/arch_and_design/subsystems/images/GeneralPattern.gif
+++ /dev/null
Binary files differ
diff --git a/development/arch_and_design/subsystems/images/GeneralPatternCrossSystems.gif b/development/arch_and_design/subsystems/images/GeneralPatternCrossSystems.gif
deleted file mode 100644
index 30fbb88..0000000
--- a/development/arch_and_design/subsystems/images/GeneralPatternCrossSystems.gif
+++ /dev/null
Binary files differ
diff --git a/development/arch_and_design/subsystems/images/WTPSubsystems.gif b/development/arch_and_design/subsystems/images/WTPSubsystems.gif
deleted file mode 100644
index a528199..0000000
--- a/development/arch_and_design/subsystems/images/WTPSubsystems.gif
+++ /dev/null
Binary files differ
diff --git a/development/arch_and_design/subsystems/localworkingsets.html b/development/arch_and_design/subsystems/localworkingsets.html
deleted file mode 100644
index 9724bc7..0000000
--- a/development/arch_and_design/subsystems/localworkingsets.html
+++ /dev/null
@@ -1,604 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<workingSetManager>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="allToSynch" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.common.annotations.core"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.ws.infopop" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.monitor.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.proxy"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.ejb.annotations.xdoclet"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.ws.creation.ejb.ui" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.server.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.tests.encoding"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.validation"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl.tests.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.ejb"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.ejb.annotation.model"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=JSPExamples"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/www" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xsd.validation.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.command.env.core"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.sse.doc.user" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.common.frameworks"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.validation.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.project.facet.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/releng-doc" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.uddi4j.feature" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.environment"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.creation.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.javascript.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ejb.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.jca"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.j2ee.infopop" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl.validation"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.validation.test"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.server.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.tests"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.html.standard.dtds" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.dtd.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.tests.encoding"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsi"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/releng.builder" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.ws.consumption.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.apache.wsil4j.feature" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.tests.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/releng.wtpbuilder" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.web"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.generic.serverdefinitions"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.css.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl.validation.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.uddiregistry"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.command.env"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.navigator.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.wsdleditor.doc.user" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.frameworks.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.webtools.doc.user" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.tomcat.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.apache.xerces"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.javascript.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.tomcat.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.webservice"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.server.ui.doc.user" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.xsdeditor.doc.user" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.xmleditor.doc.user" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.jsp.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.html.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.server.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.monitor.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.ui.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.jca.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.command.env.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.ws.infopop" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.project.facet.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.tomcat.tests.performance"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.common.infopop" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.ejb.annotations.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsi.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.core.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.ejb.annotations.emitter"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.navigator.views"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.web.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.tests.collector"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.dtd.ui.tests"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/releng" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.sse.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.servlet.tests"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.xml.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.cache"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.snippets"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.datatools.fe.ui.doc.user" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.uddi4j"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.datatools.connection.ui.doc.user" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.common.annotations.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.frameworks"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.wsdl4j"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.server.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.validation.sample"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.generic.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.ui.tests"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.ws.axis.infopop" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.axis.consumption.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.validation.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.cache.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.ui.tests"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.wsdl4j.feature" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.consumption"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.web"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.datatools.server.ui.doc.user" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.ui.properties"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.ws.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.server.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.axis.consumption.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.ui.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.tests.encoding"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.apache.axis.feature" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.common.annotations.controller"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=TestStartup"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.wsdl.ui.doc.user" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.ui.tests.performance"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.server.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.emf"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.ws"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.modulecore"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.common.navigator.java"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsi.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.wsi.ui.doc.user" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.ui.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.servlet.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.ws.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.ui.tests.performance"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.javascript.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.ws.explorer"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xsd.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xsd.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.generic.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.dtd.core"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.dtdeditor.doc.user" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.websphere.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.uriresolver"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.webservice.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.consumption.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.emfworkbench.integration"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.apache.axis"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/WTPArchAndDesignDocs" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.axis.creation.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.tests.encoding"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.ejb.doc.user" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.apache.wsil4j"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.navigator.workbench"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.generic.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.monitor.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.tomcat.ui.tests"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.dtd.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.ws.parser"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.monitor.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.tomcat.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xsd.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.server.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.ui.tests"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="editing" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.dtd.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.javascript.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.javascript.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.dtd.core"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="editing - examplesAndTools" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.tests.linestyle"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.unittests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=JSPExamples"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=com.ibm.tools.stagedrefactoring"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=Servlet 2.4 Examples"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="features" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.xml.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.doc.user.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.common.feature.core" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.server.feature.core" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.web.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.sdk" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.uddi4j.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.common.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.web.feature.core" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.apache.wsil4j.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.doc.user.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.xml.feature.core" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.server.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.wsdl4j.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.doc.isv.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.tests.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.doc.isv.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.tests.performance.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.sdk" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.tests.performance.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.tests" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="jst.enterprise_core.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.ejb"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.ejb.annotation.model"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.ejb.annotations.emitter"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.ejb.annotations.xdoclet"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.jca"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.webservice"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="jst.enterprise_tests.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.core.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.validation.sample"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.validation.test"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.tests.performance"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="jst.enterprise-ui.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ejb.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.ejb.annotations.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.jca.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.navigator.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.webservice.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.axis.creation.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.consumption"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.consumption.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.creation.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.uddiregistry"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.j2ee.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.ws.axis.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.ws.creation.ejb.ui" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="jst.enterprise_userdoc.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.ejb.doc.user" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="jst.server_core.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.generic.core"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="jst.server_product_adapters" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.generic.serverdefinitions"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.tomcat.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.tomcat.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.tomcat.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.tomcat.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.tomcat.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.websphere.core"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="jst.server_tests.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.generic.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.tomcat.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.tomcat.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.tomcat.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.ui.tests"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="jst.server_ui.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.generic.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.server.ui.infopop" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="jst.server_userdoc.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.server.ui.doc.user" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="jst.web_core.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.common.annotations.controller"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.common.annotations.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.common.frameworks"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.common.navigator.java"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.web"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.axis.consumption.core"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="jst.web_tests.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.tests.encoding"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.ui.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.servlet.tests"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="jst.web_ui.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.common.annotations.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.servlet.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.axis.consumption.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.jsp.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.ws.consumption.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.ws.infopop" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="non-code-dev-www" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/releng" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/SSE Design and Migration Notes" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.apache.axis.feature" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.apache.axis"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=TestStartup"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/WTPArchAndDesignDocs" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/releng.wtpbuilder" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/www" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/releng.builder" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/releng-doc" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="tests" editPageId="org.eclipse.pde.ui.pluginWorkingSet">
-<item factoryID="org.eclipse.pde.ui.elementFactory" org.eclipse.pde.workingSetKey="org.eclipse.wst.sse.tests.linestyle"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.xml_core.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.dtd.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xsd.core"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.xml_sdk.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.source"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.xml_tests.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.dtd.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.ui.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.tests.encoding"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.ui.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.validation.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xsd.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xsd.validation.tests"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.xml_third_party_plugins" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.apache.xerces"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.apache.xerces.feature" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.xml_ui.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.dtd.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xsd.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.dtd.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.sse.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.xml.ui.infopop" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.xml_userdoc.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.dtdeditor.doc.user" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.sse.doc.user" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.xmleditor.doc.user" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.xsdeditor.doc.user" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.common_core.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.command.env"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.command.env.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.emf"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.environment"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.frameworks"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.modulecore"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.project.facet.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.uriresolver"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.cache"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.validation"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wstCommonFeatures" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.common_tests.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.common_ui.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.common_core.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.common_sdk.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.common_userdoc.feature" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.common_sdk.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.isvdoc"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.sdk.source"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.common_tests.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.tests.collector"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.tests.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.cache.tests"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.common_ui.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.command.env.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.frameworks.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.navigator.views"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.navigator.workbench"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.project.facet.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.snippets"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.ui.properties"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.proxy"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.validation.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.common.infopop" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.common_userdoc.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.user.doc"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.rdb_core.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.data.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.models.sql"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.rdb_product_adapters.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.derby"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.mysql"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.dbdefinition.db2.iseries" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.dbdefinition.db2.luw" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.dbdefinition.db2.zseries" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.dbdefinition.derby" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.dbdefinition.informix" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.dbdefinition.mysql" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.dbdefinition.oracle" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.dbdefinition.sqlserver" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.dbdefinition.sybase" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.rdb-sdk.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.source"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdp.isvdoc"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.rdb_tests.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.tests.performance"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.rdb_ui.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.connection.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.core.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.data.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.derby.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.fe.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.fe.ui.actions"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.models.dbdefinition"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.models.sql.edit"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.outputview"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.server.extensions"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.server.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.sqleditor"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.sqlscrapbook"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.connection.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.fe.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.outputview.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.server.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.sqleditor.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.sqlscrapbook.infopop" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.rdb_userdoc.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.datatools.connection.ui.doc.user" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.datatools.fe.ui.doc.user" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.datatools.server.ui.doc.user" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.server_core.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.monitor.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.server.core"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.server_sdk.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.isvdoc"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.server.source"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.server_tests.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.monitor.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.monitor.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.server.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.server.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.server.ui.tests"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.server_ui.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.monitor.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.server.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.server.ui.infopop" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.server_userdoc.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.server.ui.doc.user" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.web_core.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.emfworkbench.integration"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.javascript.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.web"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.web_sdk.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.web.isv.doc"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.web.source"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.web_tests.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.tests.encoding"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.ui.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.tests.encoding"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.ui.tests.performance"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.web_third_party_plugins" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.html.standard.dtds" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.web_ui.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.javascript.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.web.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.css.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.html.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.javascript.ui.infopop" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.web_userdoc.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.webtools.doc.user" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.ws_core.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.ws"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.ws.parser"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsi"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.ws_sdk.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.webservice.source"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.ws_tests.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.ws.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl.tests.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl.validation.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsi.tests"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="jst.ws_third_party_plugins" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.apache.wsil4j"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.uddi4j"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.wsdl4j"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.apache.wsil4j.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.uddi4j.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.wsdl4j.feature" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.ws_ui.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.ws.explorer"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.ws.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl.validation"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsi.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.ws.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.wsdl.ui.doc.user" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.wsi.ui.doc.user" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.ws_userdoc.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.wsdleditor.doc.user" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wstXMLFeatures" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.xml_ui.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.xml_userdoc.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.xml_tests.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.xml_sdk.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.xml_core.feature" type="4"/>
-</workingSet>
-<mruList name="allToSynch"/>
-<mruList name="tests"/>
-<mruList name="wst.xml_tests.feature"/>
-<mruList name="jst.web_tests.feature"/>
-<mruList name="jst.web_core.feature"/>
-</workingSetManager>
\ No newline at end of file
diff --git a/development/arch_and_design/subsystems/localworkingsets.xml b/development/arch_and_design/subsystems/localworkingsets.xml
deleted file mode 100644
index 9724bc7..0000000
--- a/development/arch_and_design/subsystems/localworkingsets.xml
+++ /dev/null
@@ -1,604 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<workingSetManager>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="allToSynch" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.common.annotations.core"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.ws.infopop" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.monitor.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.proxy"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.ejb.annotations.xdoclet"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.ws.creation.ejb.ui" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.server.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.tests.encoding"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.validation"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl.tests.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.ejb"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.ejb.annotation.model"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=JSPExamples"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/www" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xsd.validation.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.command.env.core"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.sse.doc.user" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.common.frameworks"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.validation.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.project.facet.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/releng-doc" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.uddi4j.feature" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.environment"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.creation.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.javascript.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ejb.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.jca"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.j2ee.infopop" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl.validation"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.validation.test"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.server.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.tests"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.html.standard.dtds" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.dtd.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.tests.encoding"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsi"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/releng.builder" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.ws.consumption.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.apache.wsil4j.feature" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.tests.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/releng.wtpbuilder" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.web"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.generic.serverdefinitions"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.css.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl.validation.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.uddiregistry"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.command.env"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.navigator.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.wsdleditor.doc.user" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.frameworks.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.webtools.doc.user" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.tomcat.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.apache.xerces"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.javascript.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.tomcat.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.webservice"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.server.ui.doc.user" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.xsdeditor.doc.user" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.xmleditor.doc.user" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.jsp.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.html.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.server.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.monitor.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.ui.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.jca.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.command.env.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.ws.infopop" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.project.facet.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.tomcat.tests.performance"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.common.infopop" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.ejb.annotations.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsi.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.core.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.ejb.annotations.emitter"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.navigator.views"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.web.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.tests.collector"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.dtd.ui.tests"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/releng" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.sse.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.servlet.tests"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.xml.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.cache"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.snippets"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.datatools.fe.ui.doc.user" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.uddi4j"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.datatools.connection.ui.doc.user" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.common.annotations.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.frameworks"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.wsdl4j"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.server.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.validation.sample"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.generic.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.ui.tests"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.ws.axis.infopop" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.axis.consumption.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.validation.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.cache.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.ui.tests"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.wsdl4j.feature" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.consumption"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.web"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.datatools.server.ui.doc.user" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.ui.properties"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.ws.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.server.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.axis.consumption.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.ui.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.tests.encoding"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.apache.axis.feature" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.common.annotations.controller"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=TestStartup"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.wsdl.ui.doc.user" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.ui.tests.performance"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.server.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.emf"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.ws"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.modulecore"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.common.navigator.java"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsi.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.wsi.ui.doc.user" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.ui.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.servlet.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.ws.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.ui.tests.performance"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.javascript.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.ws.explorer"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xsd.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xsd.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.generic.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.dtd.core"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.dtdeditor.doc.user" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.websphere.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.uriresolver"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.webservice.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.consumption.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.emfworkbench.integration"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.apache.axis"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/WTPArchAndDesignDocs" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.axis.creation.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.tests.encoding"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.ejb.doc.user" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.apache.wsil4j"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.navigator.workbench"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.generic.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.monitor.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.tomcat.ui.tests"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.dtd.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.ws.parser"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.monitor.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.tomcat.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xsd.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.server.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.ui.tests"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="editing" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.dtd.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.javascript.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.javascript.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.dtd.core"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="editing - examplesAndTools" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.tests.linestyle"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.unittests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=JSPExamples"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=com.ibm.tools.stagedrefactoring"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=Servlet 2.4 Examples"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="features" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.xml.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.doc.user.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.common.feature.core" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.server.feature.core" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.web.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.sdk" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.uddi4j.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.common.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.web.feature.core" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.apache.wsil4j.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.doc.user.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.xml.feature.core" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.server.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.wsdl4j.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.doc.isv.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.tests.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.doc.isv.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.tests.performance.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.sdk" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.tests.performance.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.tests" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="jst.enterprise_core.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.ejb"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.ejb.annotation.model"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.ejb.annotations.emitter"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.ejb.annotations.xdoclet"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.jca"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.webservice"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="jst.enterprise_tests.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.core.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.validation.sample"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.validation.test"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.tests.performance"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="jst.enterprise-ui.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ejb.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.ejb.annotations.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.jca.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.navigator.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.webservice.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.axis.creation.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.consumption"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.consumption.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.creation.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.uddiregistry"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.j2ee.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.ws.axis.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.ws.creation.ejb.ui" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="jst.enterprise_userdoc.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.ejb.doc.user" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="jst.server_core.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.generic.core"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="jst.server_product_adapters" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.generic.serverdefinitions"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.tomcat.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.tomcat.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.tomcat.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.tomcat.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.tomcat.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.websphere.core"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="jst.server_tests.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.generic.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.tomcat.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.tomcat.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.tomcat.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.ui.tests"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="jst.server_ui.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.generic.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.server.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.server.ui.infopop" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="jst.server_userdoc.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.server.ui.doc.user" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="jst.web_core.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.common.annotations.controller"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.common.annotations.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.common.frameworks"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.common.navigator.java"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.j2ee.web"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.axis.consumption.core"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="jst.web_tests.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.tests.encoding"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.ui.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.servlet.tests"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="jst.web_ui.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.common.annotations.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.jsp.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.servlet.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.jst.ws.axis.consumption.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.jsp.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.ws.consumption.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.ws.infopop" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="non-code-dev-www" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/releng" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/SSE Design and Migration Notes" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.apache.axis.feature" type="4"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.apache.axis"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=TestStartup"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/WTPArchAndDesignDocs" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.jst.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/releng.wtpbuilder" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/www" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/releng.builder" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/releng-doc" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="tests" editPageId="org.eclipse.pde.ui.pluginWorkingSet">
-<item factoryID="org.eclipse.pde.ui.elementFactory" org.eclipse.pde.workingSetKey="org.eclipse.wst.sse.tests.linestyle"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.xml_core.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.dtd.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xsd.core"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.xml_sdk.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.source"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.xml_tests.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.dtd.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.ui.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.tests.encoding"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.ui.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.validation.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xsd.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xsd.validation.tests"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.xml_third_party_plugins" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.apache.xerces"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.apache.xerces.feature" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.xml_ui.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.dtd.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.sse.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xml.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.xsd.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.dtd.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.sse.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.xml.ui.infopop" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.xml_userdoc.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.dtdeditor.doc.user" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.sse.doc.user" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.xmleditor.doc.user" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.xsdeditor.doc.user" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.common_core.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.command.env"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.command.env.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.emf"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.environment"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.frameworks"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.modulecore"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.project.facet.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.uriresolver"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.cache"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.validation"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wstCommonFeatures" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.common_tests.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.common_ui.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.common_core.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.common_sdk.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.common_userdoc.feature" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.common_sdk.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.isvdoc"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.sdk.source"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.common_tests.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.tests.collector"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.tests.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.cache.tests"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.common_ui.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.command.env.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.frameworks.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.navigator.views"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.navigator.workbench"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.project.facet.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.snippets"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.ui.properties"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.proxy"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.validation.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.common.infopop" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.common_userdoc.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.user.doc"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.rdb_core.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.data.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.models.sql"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.rdb_product_adapters.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.derby"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.mysql"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.dbdefinition.db2.iseries" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.dbdefinition.db2.luw" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.dbdefinition.db2.zseries" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.dbdefinition.derby" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.dbdefinition.informix" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.dbdefinition.mysql" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.dbdefinition.oracle" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.dbdefinition.sqlserver" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.dbdefinition.sybase" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.rdb-sdk.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.source"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdp.isvdoc"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.rdb_tests.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.tests.performance"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.rdb_ui.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.connection.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.core.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.data.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.derby.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.fe.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.fe.ui.actions"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.models.dbdefinition"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.models.sql.edit"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.outputview"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.server.extensions"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.server.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.sqleditor"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.sqlscrapbook"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.connection.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.fe.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.outputview.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.server.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.sqleditor.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.rdb.sqlscrapbook.infopop" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.rdb_userdoc.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.datatools.connection.ui.doc.user" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.datatools.fe.ui.doc.user" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.datatools.server.ui.doc.user" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.server_core.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.monitor.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.server.core"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.server_sdk.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.rdb.isvdoc"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.server.source"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.server_tests.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.monitor.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.monitor.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.server.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.server.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.server.ui.tests"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.server_ui.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.internet.monitor.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.server.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.server.ui.infopop" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.server_userdoc.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.server.ui.doc.user" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.web_core.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.common.emfworkbench.integration"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.javascript.core"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.web"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.web_sdk.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.web.isv.doc"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.web.source"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.web_tests.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.tests.encoding"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.ui.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.core.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.tests.encoding"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.ui.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.ui.tests.performance"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.web_third_party_plugins" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.html.standard.dtds" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.web_ui.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.css.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.html.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.javascript.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.web.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.css.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.html.ui.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.javascript.ui.infopop" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.web_userdoc.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.webtools.doc.user" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.ws_core.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.ws"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.ws.parser"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsi"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.ws_sdk.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.webservice.source"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.ws_tests.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.ws.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl.tests.performance"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl.tests.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl.validation.tests"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsi.tests"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="jst.ws_third_party_plugins" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.apache.wsil4j"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.uddi4j"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.wsdl4j"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.apache.wsil4j.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.uddi4j.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.wsdl4j.feature" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.ws_ui.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.ws.explorer"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.ws.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl.ui"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsdl.validation"/>
-<item factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory" elementID="=org.eclipse.wst.wsi.ui"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.ws.infopop" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.wsdl.ui.doc.user" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.wsi.ui.doc.user" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wst.ws_userdoc.feature" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.wsdleditor.doc.user" type="4"/>
-</workingSet>
-<workingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="wstXMLFeatures" editPageId="org.eclipse.jdt.ui.JavaWorkingSetPage">
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.xml_ui.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.xml_userdoc.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.xml_tests.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.xml_sdk.feature" type="4"/>
-<item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.wst.xml_core.feature" type="4"/>
-</workingSet>
-<mruList name="allToSynch"/>
-<mruList name="tests"/>
-<mruList name="wst.xml_tests.feature"/>
-<mruList name="jst.web_tests.feature"/>
-<mruList name="jst.web_core.feature"/>
-</workingSetManager>
\ No newline at end of file
diff --git a/development/arch_and_design/subsystems/workingSetToHTML.xsl b/development/arch_and_design/subsystems/workingSetToHTML.xsl
deleted file mode 100644
index 29faa0c..0000000
--- a/development/arch_and_design/subsystems/workingSetToHTML.xsl
+++ /dev/null
@@ -1,65 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<xsl:stylesheet
- version="1.0"
- xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
-
- <xsl:template match="/">
- <html>
- <body>
- <xsl:apply-templates select="workingSetManager" />
- </body>
- </html>
- </xsl:template>
-
- <xsl:template match="workingSetManager">
- <h2>Build Components (by plugins)</h2>
- <p>The listed plugins are preliminary, for review.</p>
- <xsl:apply-templates select="workingSet" />
-
- </xsl:template>
-
- <xsl:template match="workingSetManager/workingSet">
-
- <xsl:variable
- name="toplevelname"
- select="substring(@name,1,3)">
- </xsl:variable>
-
- <xsl:if test="$toplevelname = 'jst' or $toplevelname = 'wst'">
-
- <h3>
- <xsl:value-of select="$toplevelname" />
- <xsl:text>Build Components</xsl:text>
- </h3>
-
- <xsl:call-template name="doItems" />
- </xsl:if>
- </xsl:template>
-
- <xsl:template
- name="doItems"
- match="item">
-
- <h4>
- <xsl:value-of select="@name" />
- </h4>
- <ul>
-
- <xsl:for-each select="item">
- <xsl:if test="@elementID">
- <li>
- <xsl:value-of select="substring(@elementID, 2)" />
- </li>
- </xsl:if>
- <xsl:if test="@path">
- <li>
- <xsl:value-of select="substring(@path, 2)" />
- </li>
- </xsl:if>
- </xsl:for-each>
- </ul>
-
- </xsl:template>
-
-
-</xsl:stylesheet>
\ No newline at end of file
diff --git a/development/arch_and_design/theme/default_style.css b/development/arch_and_design/theme/default_style.css
deleted file mode 100644
index af2b27a..0000000
--- a/development/arch_and_design/theme/default_style.css
+++ /dev/null
@@ -1,18 +0,0 @@
-p, table, td, th { font-family: arial, helvetica, geneva; font-size: 10pt}
-pre { font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code { font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup { font-family: arial,helvetica,geneva; font-size: 10px}
-h3 { font-family: arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li { font-family: arial, helvetica, geneva; font-size: 10pt}
-h1 { font-family: arial, helvetica, geneva; font-size: 28px; font-weight: bold}
-body { font-family: arial, helvetica, geneva; font-size: 10pt; clip: rect( ); margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large;; font-family: Verdana, Arial, Helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small;; font-family: Arial, Helvetica, sans-serif; color: #8080FF}
-a.bar:link { text-decoration: none; color: #FFFFFF}
-a.bar:visited { color: #FFFFFF; text-decoration: none}
-a.bar:hover { color: #FFFFFF; text-decoration: underline}
-a.bar { color: #FFFFFF}
-.jump { font-size: smaller;; font-family: Arial, Helvetica, sans-serif; color: #8080FF ; font-style: normal; text-decoration: none}
-.jump:link { font-size: smaller;; font-family: Arial, Helvetica, sans-serif; color: #8080FF; text-decoration: none}
-.jump:hover { font-size: smaller;; font-family: Arial, Helvetica, sans-serif; color: #0000FF; text-decoration: underline; font-style: normal}
diff --git a/development/bugs/bugs.html b/development/bugs/bugs.html
deleted file mode 100644
index 03af2f2..0000000
--- a/development/bugs/bugs.html
+++ /dev/null
@@ -1,328 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../webtools/wtp.css" type="text/css">
-<title>Web Tools Platform Bug Reports</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">WTP bugs</font>
-<br>
-<font class="indexsub">Web Tools Platform Bug Reports</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p align="right">
-<em>Updated 2005-06-14</em>
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Bug Reports</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<table>
-
-
-<tr>
-<td><img src="../../../images/Adarrow.gif">
-Action items (<a href="https://bugs.eclipse.org/bugs/buglist.cgi?short_desc_type=allwordssubstr&short_desc=%5Baction%5D&product=Web+Tools&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED">text</a>)
-</td>
-</tr>
-
-
-<tr>
-<td><img src="../../../images/Adarrow.gif">
-Help wanted (<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=priority&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=helpwanted&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by priority</a> /
-<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=helpwanted&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by severity</a>)
-</td>
-</tr>
-
-
-<tr>
-<td><img src="../../../images/Adarrow.gif">
-NEW/ASSIGNED/REOPENED bugs, no enhancements
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=version&y_axis_field=priority&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=bug_severity&type0-0-0=notequals&value0-0-0=enhancement">by priority</a>)
-</td>
-</tr>
-
-
-<tr>
-<td><img src="../../../images/Adarrow.gif">
-NEW/ASSIGNED/REOPENED bugs
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=version&y_axis_field=bug_severity&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by severity</a>)
-</td>
-</tr>
-
-
-<tr>
-<td><img src="../../../images/Adarrow.gif">
-P1/P2 bugs
-<p>
-
-<ul>
-
-
-<li>
-Targeted for WTP 0.7
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=priority&y_axis_field=assigned_to&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&target_milestone=1.0+M3&target_milestone=1.0+M4&target_milestone=1.0+M5&target_milestone=1.0+M6&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&priority=P2&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by owner</a> /
-<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=priority&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&target_milestone=1.0+M3&target_milestone=1.0+M4&target_milestone=1.0+M5&target_milestone=1.0+M6&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&priority=P2&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by component</a>)
-</li>
-
-
-<li>
-Post WTP 0.7
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=priority&y_axis_field=assigned_to&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&target_milestone=---&target_milestone=1.0+M10&target_milestone=1.0+M8&target_milestone=1.0+M9&target_milestone=1.5+M1&target_milestone=1.5+M2&target_milestone=1.5+M3&target_milestone=1.5+M4&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&priority=P2&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by owner</a> /
-<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=priority&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&target_milestone=---&target_milestone=1.0+M10&target_milestone=1.0+M8&target_milestone=1.0+M9&target_milestone=1.5+M1&target_milestone=1.5+M2&target_milestone=1.5+M3&target_milestone=1.5+M4&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&priority=P2&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by component</a>)
-</li>
-
-
-</ul>
-
-</p>
-
-</td>
-</tr>
-
-
-<tr>
-<td><img src="../../../images/Adarrow.gif">
-Blocking/Critical/Major bugs
-<p>
-
-<ul>
-
-
-<li>
-Targeted for WTP 0.7
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=assigned_to&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&target_milestone=1.0+M3&target_milestone=1.0+M4&target_milestone=1.0+M5&target_milestone=1.0+M6&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&bug_severity=major&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by owner</a> /
-<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&target_milestone=1.0+M3&target_milestone=1.0+M4&target_milestone=1.0+M5&target_milestone=1.0+M6&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&bug_severity=major&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by component</a>)
-
-</li>
-
-
-<li>
-Deferred without justification
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=assigned_to&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&target_milestone=---&target_milestone=1.0+M10&target_milestone=1.0+M8&target_milestone=1.0+M9&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&bug_severity=major&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=priority&type0-0-0=notequals&value0-0-0=P4">by owner</a> /
-<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&target_milestone=---&target_milestone=1.0+M10&target_milestone=1.0+M8&target_milestone=1.0+M9&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&bug_severity=major&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=priority&type0-0-0=notequals&value0-0-0=P4">by component</a>)
-</li>
-
-
-<li>
-Deferred with justification
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=assigned_to&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&target_milestone=---&target_milestone=1.0+M10&target_milestone=1.0+M8&target_milestone=1.0+M9&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&bug_severity=major&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=priority&type0-0-0=equals&value0-0-0=P4">by owner</a> /
-<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&target_milestone=---&target_milestone=1.0+M10&target_milestone=1.0+M8&target_milestone=1.0+M9&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&bug_severity=major&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=priority&type0-0-0=equals&value0-0-0=P4">by component</a>)
-</li>
-
-
-</ul>
-
-</p>
-
-</td>
-</tr>
-
-
-<tr>
-<td><img src="../../../images/Adarrow.gif">
-Resolved, unverified bugs
-<p>
-
-<ul>
-
-
-<li>
-Top 10 inactive > 14 days
-(<a href="top10Resolved.php">by reporter</a> /
-<a href="top10ResolvedByComp.php">by component</a>)
-</li>
-
-
-<li>
-Inactive > 14 days
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=reporter&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=RESOLVED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=%28to_days%28now%28%29%29+-+to_days%28bugs.delta_ts%29%29&type0-0-0=greaterthan&value0-0-0=14&field0-1-0=resolution&type0-1-0=nowords&value0-1-0=LATER+REMIND">by reporter</a> /
-<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=RESOLVED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=%28to_days%28now%28%29%29+-+to_days%28bugs.delta_ts%29%29&type0-0-0=greaterthan&value0-0-0=14&field0-1-0=resolution&type0-1-0=nowords&value0-1-0=LATER+REMIND">by component</a>)
-</li>
-
-
-<li>
-All
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=reporter&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=RESOLVED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=resolution&type0-0-0=nowords&value0-0-0=LATER+REMIND">by reporter</a> /
-<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=RESOLVED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=resolution&type0-0-0=nowords&value0-0-0=LATER+REMIND">by component</a> /
-<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=version&y_axis_field=priority&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=RESOLVED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=resolution&type0-0-0=nowords&value0-0-0=LATER+REMIND">by priority</a>)
-</li>
-
-
-</ul>
-
-</p>
-
-</td>
-</tr>
-
-
-<tr>
-<td><img src="../../../images/Adarrow.gif">
-Verified, not closed bugs
-<p>
-
-<ul>
-
-
-<li>
-Top 10 inactive > 14 days
-(<a href="top10Verified.php">by owner</a> /
-<a href="top10VerifiedByComp.php">by component</a>)
-</li>
-
-
-<li>
-Inactive > 14 days
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=assigned_to&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=VERIFIED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=%28to_days%28now%28%29%29+-+to_days%28bugs.delta_ts%29%29&type0-0-0=greaterthan&value0-0-0=14">by owner</a> /
-<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=VERIFIED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=%28to_days%28now%28%29%29+-+to_days%28bugs.delta_ts%29%29&type0-0-0=greaterthan&value0-0-0=14">by component</a>)
-
-</li>
-
-
-<li>
-All
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=assigned_to&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=VERIFIED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by owner</a> /
-<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=VERIFIED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by component</a>)
-
-</li>
-
-
-</ul>
-
-</p>
-
-</td>
-</tr>
-
-
-<tr>
-<td><img src="../../../images/Adarrow.gif">
-Bugs @ inboxes
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=assigned_to&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=regexp&email1=inbox@%7Cwtp-dev@&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">chart</a> /
-<a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=regexp&email1=inbox@%7Cwtp-dev@&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=map_assigned_to.login_name,bugs.bug_severity,bugs.priority,bugs.bug_id&field0-0-0=noop&type0-0-0=noop&value0-0-0=">text</a>)
-</td>
-</tr>
-
-
-<tr>
-<td><img src="../../../images/Adarrow.gif">
-Performance bugs
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=assigned_to&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=keywords&type0-0-0=anywordssubstr&value0-0-0=Performance+performance&field0-0-1=short_desc&type0-0-1=anywordssubstr&value0-0-1=Performance%3A+performance%3A+%5BPerformance%5D+%5Bperformance%5D+Performance+performance">by owner</a> /
-<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=keywords&type0-0-0=anywordssubstr&value0-0-0=Performance+performance&field0-0-1=short_desc&type0-0-1=anywordssubstr&value0-0-1=Performance%3A+performance%3A+%5BPerformance%5D+%5Bperformance%5D+Performance+performance">by component</a>)
-</td>
-</tr>
-
-
-<tr>
-<td><img src="../../../images/Adarrow.gif">
-TVT bugs
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=assigned_to&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=TVT&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by owner</a> /
-<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=TVT&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by component</a>)
-</td>
-</tr>
-
-
-<tr>
-<td><img src="../../../images/Adarrow.gif">
-Internal API bugs
-(<a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=anywordssubstr&short_desc=%5Binternal+API%5D&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Assignee&field0-0-0=noop&type0-0-0=noop&value0-0-0=">text</a>)
-</td>
-</tr>
-
-
-<tr>
-<td><img src="../../../images/Adarrow.gif">
-All open bugs
-(<a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">text</a>)
-<a href="graphOpenBugs.html"><img border="0" src="graph.gif"></a>
-</td>
-</tr>
-
-
-<tr>
-<td><img src="../../../images/Adarrow.gif">
-Most wanted
-<p>
-
-<ul>
-
-
-<li>
-Bug fixes
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?y_axis_field=component&x_axis_field=bug_severity&query_format=report-table&product=Web+Tools&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_severity=trivial&votes=1&order=bugs.votes,bugs.bug_severity,map_components.name,bugs.bug_id&format=table&action=wrap">chart</a>
-/
-<a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&product=Web+Tools&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_severity=trivial&votes=1&order=bugs.votes,bugs.bug_severity,map_components.name,bugs.bug_id">text</a>)
-</li>
-
-
-<li>
-Enhancements
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?y_axis_field=component&x_axis_field=bug_severity&query_format=report-table&product=Web%20Tools&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=enhancement&votes=1&order=bugs.votes,map_components.name,bugs.bug_id&format=table&action=wrap">chart</a>
-/
-<a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&product=Web%20Tools&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=enhancement&bug_id=&votes=1&order=bugs.votes,map_components.name,bugs.bug_id">text</a>)
-</li>
-
-
-</ul>
-
-</p>
-
-</td>
-</tr>
-
-
-</table>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Certain columns not showing up (ex. the reporter column)?</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-By default, your Bugzilla preference filters out some columns when you search for bugs--for example, the reporter column.
-Since these bug reports are sorted by columns that are not enabled by default, you will need to enable some columns manually.
-To enable a column:
-<ol>
-
-<li>Click on any of the text reports above.</li>
-
-<li>When the results come back, scroll down to the bottom of the page and click on the <b>Change Columns</b> link.
-<p>
-<img src="fig1.gif" alt="picture highlighting the 'Change Columns' link"></p>
-</li>
-
-<li>Select the <b>Reporter</b> checkbox and click on the <b>Change Columns</b> button.
-<p>
-<img src="fig2.gif" alt="picture of the column selection checklist"></p>
-</li>
-
-</ol>
-
-</p>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/development/bugs/bugs.xml b/development/bugs/bugs.xml
deleted file mode 100644
index e47bd15..0000000
--- a/development/bugs/bugs.xml
+++ /dev/null
@@ -1,216 +0,0 @@
-<?xml-stylesheet type="text/xsl" href="../../wtphome.xsl"?>
-<html>
-<head>
- <title>Web Tools Platform Bug Reports</title>
- <meta name="root" content="../../.." />
-</head>
-<body>
-
-<h1>WTP bugs</h1>
-<p align="right"><em>Updated 2005-06-14</em></p>
-
-<h2>Bug Reports</h2>
-<p>
-<table>
-
-<tr><td><img src="../../../images/Adarrow.gif"/>
-Action items (<a href="https://bugs.eclipse.org/bugs/buglist.cgi?short_desc_type=allwordssubstr&short_desc=%5Baction%5D&product=Web+Tools&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED">text</a>)
-</td></tr>
-
-<tr><td><img src="../../../images/Adarrow.gif"/>
-Help wanted (<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=priority&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=helpwanted&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by priority</a> /
-<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=helpwanted&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by severity</a>)
-</td></tr>
-
-<tr><td><img src="../../../images/Adarrow.gif"/>
-NEW/ASSIGNED/REOPENED bugs, no enhancements
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=version&y_axis_field=priority&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=bug_severity&type0-0-0=notequals&value0-0-0=enhancement">by priority</a>)
-</td></tr>
-
-<tr><td><img src="../../../images/Adarrow.gif"/>
-NEW/ASSIGNED/REOPENED bugs
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=version&y_axis_field=bug_severity&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by severity</a>)
-</td></tr>
-
-<tr><td><img src="../../../images/Adarrow.gif"/>
-P1/P2 bugs
-<p>
-<ul>
-
-<li>
-Targeted for WTP 0.7
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=priority&y_axis_field=assigned_to&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&target_milestone=1.0+M3&target_milestone=1.0+M4&target_milestone=1.0+M5&target_milestone=1.0+M6&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&priority=P2&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by owner</a> /
-<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=priority&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&target_milestone=1.0+M3&target_milestone=1.0+M4&target_milestone=1.0+M5&target_milestone=1.0+M6&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&priority=P2&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by component</a>)
-</li>
-
-<li>
-Post WTP 0.7
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=priority&y_axis_field=assigned_to&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&target_milestone=---&target_milestone=1.0+M10&target_milestone=1.0+M8&target_milestone=1.0+M9&target_milestone=1.5+M1&target_milestone=1.5+M2&target_milestone=1.5+M3&target_milestone=1.5+M4&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&priority=P2&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by owner</a> /
-<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=priority&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&target_milestone=---&target_milestone=1.0+M10&target_milestone=1.0+M8&target_milestone=1.0+M9&target_milestone=1.5+M1&target_milestone=1.5+M2&target_milestone=1.5+M3&target_milestone=1.5+M4&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&priority=P2&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by component</a>)
-</li>
-
-</ul>
-</p>
-</td></tr>
-
-<tr><td><img src="../../../images/Adarrow.gif"/>
-Blocking/Critical/Major bugs
-<p>
-<ul>
-
-<li>
-Targeted for WTP 0.7
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=assigned_to&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&target_milestone=1.0+M3&target_milestone=1.0+M4&target_milestone=1.0+M5&target_milestone=1.0+M6&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&bug_severity=major&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by owner</a> /
-<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&target_milestone=1.0+M3&target_milestone=1.0+M4&target_milestone=1.0+M5&target_milestone=1.0+M6&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&bug_severity=major&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by component</a>)
-<!--
-<a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&target_milestone=1.0+M3&target_milestone=1.0+M4&target_milestone=1.0+M5&target_milestone=1.0+M6&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&bug_severity=major&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=map_assigned_to.login_name,bugs.bug_severity,bugs.priority,bugs.bug_id&field0-0-0=noop&type0-0-0=noop&value0-0-0=">text</a>
--->
-</li>
-
-<li>
-Deferred without justification
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=assigned_to&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&target_milestone=---&target_milestone=1.0+M10&target_milestone=1.0+M8&target_milestone=1.0+M9&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&bug_severity=major&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=priority&type0-0-0=notequals&value0-0-0=P4">by owner</a> /
-<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&target_milestone=---&target_milestone=1.0+M10&target_milestone=1.0+M8&target_milestone=1.0+M9&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&bug_severity=major&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=priority&type0-0-0=notequals&value0-0-0=P4">by component</a>)
-</li>
-
-<li>
-Deferred with justification
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=assigned_to&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&target_milestone=---&target_milestone=1.0+M10&target_milestone=1.0+M8&target_milestone=1.0+M9&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&bug_severity=major&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=priority&type0-0-0=equals&value0-0-0=P4">by owner</a> /
-<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&target_milestone=---&target_milestone=1.0+M10&target_milestone=1.0+M8&target_milestone=1.0+M9&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&bug_severity=major&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=priority&type0-0-0=equals&value0-0-0=P4">by component</a>)
-</li>
-
-</ul>
-</p>
-</td></tr>
-
-<tr><td><img src="../../../images/Adarrow.gif"/>
-Resolved, unverified bugs
-<p>
-<ul>
-
-<li>
-Top 10 inactive > 14 days
-(<a href="top10Resolved.php">by reporter</a> /
-<a href="top10ResolvedByComp.php">by component</a>)
-</li>
-
-<li>
-Inactive > 14 days
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=reporter&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=RESOLVED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=%28to_days%28now%28%29%29+-+to_days%28bugs.delta_ts%29%29&type0-0-0=greaterthan&value0-0-0=14&field0-1-0=resolution&type0-1-0=nowords&value0-1-0=LATER+REMIND">by reporter</a> /
-<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=RESOLVED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=%28to_days%28now%28%29%29+-+to_days%28bugs.delta_ts%29%29&type0-0-0=greaterthan&value0-0-0=14&field0-1-0=resolution&type0-1-0=nowords&value0-1-0=LATER+REMIND">by component</a>)
-</li>
-
-<li>
-All
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=reporter&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=RESOLVED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=resolution&type0-0-0=nowords&value0-0-0=LATER+REMIND">by reporter</a> /
-<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=RESOLVED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=resolution&type0-0-0=nowords&value0-0-0=LATER+REMIND">by component</a> /
-<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=version&y_axis_field=priority&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=RESOLVED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=resolution&type0-0-0=nowords&value0-0-0=LATER+REMIND">by priority</a>)
-</li>
-
-</ul>
-</p>
-</td></tr>
-
-<tr><td><img src="../../../images/Adarrow.gif"/>
-Verified, not closed bugs
-<p>
-<ul>
-
-<li>
-Top 10 inactive > 14 days
-(<a href="top10Verified.php">by owner</a> /
-<a href="top10VerifiedByComp.php">by component</a>)
-</li>
-
-<li>
-Inactive > 14 days
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=assigned_to&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=VERIFIED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=%28to_days%28now%28%29%29+-+to_days%28bugs.delta_ts%29%29&type0-0-0=greaterthan&value0-0-0=14">by owner</a> /
-<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=VERIFIED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=%28to_days%28now%28%29%29+-+to_days%28bugs.delta_ts%29%29&type0-0-0=greaterthan&value0-0-0=14">by component</a>)
-<!--
-<a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=VERIFIED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=map_reporter.login_name%2Cbugs.bug_severity%2Cbugs.priority%2Cbugs.bug_id&field0-0-0=%28to_days%28now%28%29%29+-+to_days%28bugs.delta_ts%29%29&type0-0-0=greaterthan&value0-0-0=14">text</a>
--->
-</li>
-
-<li>
-All
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=assigned_to&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=VERIFIED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by owner</a> /
-<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=VERIFIED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by component</a>)
-<!--
-<a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Web%20Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords! &keywords=&bug_status=VERIFIED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&field0-0-0=noop&type0-0-0=noop&value0-0-0=&order=map_reporter.login_name%2Cbugs.bug_severity%2Cbugs.priority%2Cbugs.bug_id&query_based_on=">text</a>
--->
-</li>
-
-</ul>
-</p>
-</td></tr>
-
-<tr><td><img src="../../../images/Adarrow.gif"/>
-Bugs @ inboxes
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=assigned_to&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=regexp&email1=inbox@%7Cwtp-dev@&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">chart</a> /
-<a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=regexp&email1=inbox@%7Cwtp-dev@&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=map_assigned_to.login_name,bugs.bug_severity,bugs.priority,bugs.bug_id&field0-0-0=noop&type0-0-0=noop&value0-0-0=">text</a>)
-</td></tr>
-
-<tr><td><img src="../../../images/Adarrow.gif"/>
-Performance bugs
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=assigned_to&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=keywords&type0-0-0=anywordssubstr&value0-0-0=Performance+performance&field0-0-1=short_desc&type0-0-1=anywordssubstr&value0-0-1=Performance%3A+performance%3A+%5BPerformance%5D+%5Bperformance%5D+Performance+performance">by owner</a> /
-<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=keywords&type0-0-0=anywordssubstr&value0-0-0=Performance+performance&field0-0-1=short_desc&type0-0-1=anywordssubstr&value0-0-1=Performance%3A+performance%3A+%5BPerformance%5D+%5Bperformance%5D+Performance+performance">by component</a>)
-</td></tr>
-
-<tr><td><img src="../../../images/Adarrow.gif"/>
-TVT bugs
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=assigned_to&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=TVT&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by owner</a> /
-<a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=TVT&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by component</a>)
-</td></tr>
-
-<tr><td><img src="../../../images/Adarrow.gif"/>
-Internal API bugs
-(<a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=anywordssubstr&short_desc=%5Binternal+API%5D&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Assignee&field0-0-0=noop&type0-0-0=noop&value0-0-0=">text</a>)
-</td></tr>
-
-<tr><td><img src="../../../images/Adarrow.gif"/>
-All open bugs
-(<a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">text</a>)
-<a href="graphOpenBugs.html"><img border="0" src="graph.gif"/></a>
-</td></tr>
-
-<tr><td><img src="../../../images/Adarrow.gif"/>
-Most wanted
-<p>
-<ul>
-
-<li>
-Bug fixes
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?y_axis_field=component&x_axis_field=bug_severity&query_format=report-table&product=Web+Tools&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_severity=trivial&votes=1&order=bugs.votes,bugs.bug_severity,map_components.name,bugs.bug_id&format=table&action=wrap">chart</a>
-/
-<a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&product=Web+Tools&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_severity=trivial&votes=1&order=bugs.votes,bugs.bug_severity,map_components.name,bugs.bug_id">text</a>)
-</li>
-
-<li>
-Enhancements
-(<a href="https://bugs.eclipse.org/bugs/report.cgi?y_axis_field=component&x_axis_field=bug_severity&query_format=report-table&product=Web%20Tools&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=enhancement&votes=1&order=bugs.votes,map_components.name,bugs.bug_id&format=table&action=wrap">chart</a>
-/
-<a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&product=Web%20Tools&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=enhancement&bug_id=&votes=1&order=bugs.votes,map_components.name,bugs.bug_id">text</a>)
-</li>
-
-</ul>
-</p>
-</td></tr>
-
-</table>
-</p>
-<h2>Certain columns not showing up (ex. the reporter column)?</h2>
-<p>
-By default, your Bugzilla preference filters out some columns when you search for bugs--for example, the reporter column.
-Since these bug reports are sorted by columns that are not enabled by default, you will need to enable some columns manually.
-To enable a column:
-<ol>
-<li>Click on any of the text reports above.</li>
-<li>When the results come back, scroll down to the bottom of the page and click on the <b>Change Columns</b> link.
-<p><img src="fig1.gif" alt="picture highlighting the 'Change Columns' link"/></p></li>
-<li>Select the <b>Reporter</b> checkbox and click on the <b>Change Columns</b> button.
-<p><img src="fig2.gif" alt="picture of the column selection checklist"/></p></li>
-</ol>
-</p>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/development/bugs/fig1.gif b/development/bugs/fig1.gif
deleted file mode 100644
index 2d5ce14..0000000
--- a/development/bugs/fig1.gif
+++ /dev/null
Binary files differ
diff --git a/development/bugs/fig2.gif b/development/bugs/fig2.gif
deleted file mode 100644
index d31cf45..0000000
--- a/development/bugs/fig2.gif
+++ /dev/null
Binary files differ
diff --git a/development/bugs/graph.gif b/development/bugs/graph.gif
deleted file mode 100644
index c7906c3..0000000
--- a/development/bugs/graph.gif
+++ /dev/null
Binary files differ
diff --git a/development/bugs/graphOpenBugs.html b/development/bugs/graphOpenBugs.html
deleted file mode 100644
index 4c1204f..0000000
--- a/development/bugs/graphOpenBugs.html
+++ /dev/null
@@ -1,5 +0,0 @@
-<html>
-<body>
-<embed width="100%" height="100%" src="graphOpenBugs.php" type="image/svg+xml">
-</body>
-</html>
\ No newline at end of file
diff --git a/development/bugs/graphOpenBugs.php b/development/bugs/graphOpenBugs.php
deleted file mode 100644
index 5526fc1..0000000
--- a/development/bugs/graphOpenBugs.php
+++ /dev/null
@@ -1,175 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" height="100%" width="100%">
-<?php
- function drawGraph($title, $xmax, $ymax, $xlegend, $ylegend)
- {
- echo "<text style=\"text-anchor:middle\" x=\"50%\" y=\"10%\">$title</text>";
- echo "<line style=\"stroke:rgb(128,128,128);stroke-width:1\" x1=\"15%\" y1=\"15%\" x2=\"15%\" y2=\"85%\"/>";
- echo "<line style=\"stroke:rgb(128,128,128);stroke-width:1\" x1=\"15%\" y1=\"85%\" x2=\"85%\" y2=\"85%\"/>";
- echo "<text style=\"text-anchor:middle\" x=\"50%\" y=\"93%\">$xlegend</text>";
- echo "<text style=\"text-anchor:middle\" x=\"8%\" y=\"50%\">$ylegend</text>";
- $delta = (int)$ymax/10;
- for ($i = 0; $i < $ymax; $i++)
- {
- if ($i % $delta == 0)
- {
- $y = 85 - ($i/$ymax*70);
- echo "<text style=\"text-anchor:end\" x=\"14.5%\" y=\"$y%\">$i</text>";
- echo "<line style=\"stroke:rgb(128,128,128);stroke-width:1\" x1=\"14.5%\" y1=\"$y%\" x2=\"15.5%\" y2=\"$y%\"/>";
- }
- }
- }
-
- function countTimeIntervals($start, $end)
- {
- $count = 0;
- while ($start < $end)
- {
- $count++;
- $start = date("YmdHis", mktime(substr($start, 8, 2), substr($start, 10, 2), substr($start, 12, 2), substr($start, 4, 2), substr($start, 6, 2) + 7, substr($start, 0, 4)));
- }
- $count++;
- return $count;
- }
-
- function plot($xmax, $ymax, $width, $height, $xstart, $ystart, $prevx, $prevy, $currx, $curry, $x, $y, $r, $g, $b, $text)
- {
- $x1 = $prevx/$xmax*$width + $xstart;
- $y1 = $ystart - ($prevy/$ymax*$height);
- $x2 = $currx/$xmax*$width + $xstart;
- $y2 = $ystart - ($curry/$ymax*$height);
- echo "<line style=\"stroke:rgb($r,$g,$b);stroke-width:1\" x1=\"$x1%\" y1=\"$y1%\" x2=\"$x2%\" y2=\"$y2%\"/>\n";
- if ($text != null)
- {
- echo "<text fill=\"rgb($r,$g,$b)\" style=\"text-anchor:middle\" x=\"$x2%\" y=\"";
- echo $y2 - 1;
- echo "%\">$text</text>";
- }
- $i = (int)$xmax/10;
- if ($currx == 0 || $currx % $i == 0)
- {
- echo "<text style=\"text-anchor:middle\" x=\"$x2%\" y=\"88%\">";
- echo substr($x, 0, 8);
- echo "</text>";
- echo "<line style=\"stroke:rgb(128,128,128);stroke-width:1\" x1=\"$x2%\" y1=\"84.5%\" x2=\"$x2%\" y2=\"85.5%\"/>";
- }
- }
-?>
-<?php
- require_once "/home/data/httpd/eclipse-php-classes/system/dbconnection_bugs_ro.class.php";
-
- # Connect to database
- $allBugsQuery = "SELECT
- BUG.bug_id,
- BUG.creation_ts
- FROM
- bugs AS BUG
- INNER JOIN products AS PROD ON PROD.id = BUG.product_id
- WHERE
- PROD.name='Web Tools'
- ORDER BY
- BUG.creation_ts";
-
- $resolvedBugsQuery = "SELECT
- BUG_ACT.bug_id,
- BUG_ACT.bug_when,
- BUG_ACT.added
- FROM
- bugs_activity AS BUG_ACT
- INNER JOIN bugs AS BUG ON BUG.bug_id = BUG_ACT.bug_id
- INNER JOIN products AS PROD ON PROD.id = BUG.product_id
- INNER JOIN fielddefs AS FIELD ON FIELD.fieldid = BUG_ACT.fieldid
- WHERE
- PROD.name='Web Tools'
- AND FIELD.fieldid=8
- AND (BUG_ACT.added='RESOLVED' OR BUG_ACT.added='REOPENED')
- ORDER BY
- BUG_ACT.bug_when";
-
- $dbc = new DBConnectionBugs();
- $dbh = $dbc->connect();
- $rs = mysql_query($allBugsQuery, $dbh);
-
- if(mysql_errno($dbh) > 0)
- {
- echo "There was an error processing this request".
-
- # For debugging purposes - don't display this stuff in a production page.
- # echo mysql_error($dbh);
-
- # Mysql disconnects automatically, but I like my disconnects to be explicit.
- $dbc->disconnect();
- exit;
- }
-
- $today = date("YmdHis");
- $cutoff = 20040801000000;
- $prevBugCount = 0;
- $currBugCount = 0;
- $dateCount = 0;
- $xmax = countTimeIntervals($cutoff, $today);
- $ymax = mysql_num_rows($rs);
- drawGraph("New / Assigned / Reopened Bugs", $xmax, $ymax, "Time", "# Bugs");
- $total = array();
- while($myrow = mysql_fetch_assoc($rs))
- {
- $creation_ts = $myrow['creation_ts'];
- $creation_ts = substr($creation_ts, 0, 4) . substr($creation_ts, 5, 2) . substr($creation_ts, 8, 2) . substr($creation_ts, 11, 2) . substr($creation_ts, 14, 2) . substr($creation_ts, 17, 2);
- if ($creation_ts > $cutoff)
- {
- $total[] = $currBugCount;
- plot($xmax, $ymax, 70, 70, 15, 85, $dateCount, $prevBugCount, $dateCount + 1, $currBugCount, $cutoff, $currBugCount, 0, 0, 128, null);
- $prevBugCount = $currBugCount;
- $dateCount++;
- $cutoff = date("YmdHis", mktime(substr($cutoff, 8, 2), substr($cutoff, 10, 2), substr($cutoff, 12, 2), substr($cutoff, 4, 2), substr($cutoff, 6, 2) + 7, substr($cutoff, 0, 4)));
- }
- $currBugCount++;
- }
- $total[] = $currBugCount;
- plot($xmax, $ymax, 70, 70, 15, 85, $dateCount, $prevBugCount, $dateCount + 1, $currBugCount, $cutoff, $currBugCount, 0, 0, 128, "Total: " . $currBugCount);
-
- $rs = mysql_query($resolvedBugsQuery, $dbh);
-
- if(mysql_errno($dbh) > 0)
- {
- echo "There was an error processing this request".
-
- # For debugging purposes - don't display this stuff in a production page.
- # echo mysql_error($dbh);
-
- # Mysql disconnects automatically, but I like my disconnects to be explicit.
- $dbc->disconnect();
- exit;
- }
-
- $cutoff = 20040801000000;
- $prevBugCount = 0;
- $currBugCount = 0;
- $dateCount = 0;
- while($myrow = mysql_fetch_assoc($rs))
- {
- $bug_when = $myrow['bug_when'];
- $bug_when = substr($bug_when, 0, 4) . substr($bug_when, 5, 2) . substr($bug_when, 8, 2) . substr($bug_when, 11, 2) . substr($bug_when, 14, 2) . substr($bug_when, 17, 2);
- if ($bug_when > $cutoff)
- {
- plot($xmax, $ymax, 70, 70, 15, 85, $dateCount, $prevBugCount, $dateCount + 1, $total[$dateCount] - $currBugCount, $cutoff, $total[$dateCount] - $currBugCount, 255, 128, 0, null);
- $prevBugCount = $total[$dateCount] - $currBugCount;
- $dateCount++;
- $cutoff = date("YmdHis", mktime(substr($cutoff, 8, 2), substr($cutoff, 10, 2), substr($cutoff, 12, 2), substr($cutoff, 4, 2), substr($cutoff, 6, 2) + 7, substr($cutoff, 0, 4)));
- }
- if ($myrow['added'] == "REOPENED")
- {
- $currBugCount--;
- }
- else
- {
- $currBugCount++;
- }
- }
- plot($xmax, $ymax, 70, 70, 15, 85, $dateCount, $prevBugCount, $dateCount + 1, $total[$dateCount] - $currBugCount, $cutoff, $total[$dateCount] - $currBugCount, 255, 128, 0, "New/Assigned/Reopened: " . ($total[$dateCount] - $currBugCount));
-
- $dbc->disconnect();
- $rs = null;
- $dbh = null;
- $dbc = null;
-?>
-</svg>
\ No newline at end of file
diff --git a/development/bugs/test.php b/development/bugs/test.php
deleted file mode 100644
index 7e26e9b..0000000
--- a/development/bugs/test.php
+++ /dev/null
@@ -1,99 +0,0 @@
-<html>
-<body>
-<?php
- require_once "/home/data/httpd/eclipse-php-classes/system/dbconnection_bugs_ro.class.php";
-
- # Connect to database
- /*
- $sqlquery = "SELECT
- fieldid,
- name
- FROM
- fielddefs";
- */
- $sqlquery = "SELECT
- BUG.bug_id,
- BUG.creation_ts
- FROM
- bugs AS BUG
- INNER JOIN products AS PROD ON PROD.id = BUG.product_id
- WHERE
- PROD.name='Web Tools'
- ORDER BY
- BUG.creation_ts";
- $sqlquery2 = "SELECT
- BUG_ACT.bug_id,
- BUG_ACT.bug_when,
- BUG_ACT.added
- FROM
- bugs_activity AS BUG_ACT
- INNER JOIN bugs AS BUG ON BUG.bug_id = BUG_ACT.bug_id
- INNER JOIN products AS PROD ON PROD.id = BUG.product_id
- INNER JOIN fielddefs AS FIELD ON FIELD.fieldid = BUG_ACT.fieldid
- WHERE
- PROD.name='Web Tools'
- AND FIELD.fieldid=8
- AND (BUG_ACT.added='RESOLVED' OR BUG_ACT.added='REOPENED')
- ORDER BY
- BUG_ACT.bug_when";
- $dbc = new DBConnectionBugs();
- $dbh = $dbc->connect();
- $rs = mysql_query($sqlquery, $dbh);
-
- if(mysql_errno($dbh) > 0)
- {
- echo "There was an error processing this request".
-
- # For debugging purposes - don't display this stuff in a production page.
- # echo mysql_error($dbh);
-
- # Mysql disconnects automatically, but I like my disconnects to be explicit.
- $dbc->disconnect();
- exit;
- }
-
- $i = 1;
- while($myrow = mysql_fetch_assoc($rs))
- {
- //echo $myrow['fieldid'] . " " . $myrow['name'] . "<br>";
- echo $i . ". " . $myrow['bug_id'] . " " . $myrow['creation_ts'] . "<br>";
- $i++;
- }
-
- echo "<br><br>--------------------------------------------------------------------------------<br><br>";
-
- $rs = mysql_query($sqlquery2, $dbh);
-
- if (mysql_errno($dbh) > 0)
- {
- echo "There was an error processing this request".
-
- # For debugging purposes - don't display this stuff in a production page.
- # echo mysql_error($dbh);
-
- # Mysql disconnects automatically, but I like my disconnects to be explicit.
- $dbc->disconnect();
- exit;
- }
-
- $i = 1;
- while($myrow = mysql_fetch_assoc($rs))
- {
- echo $i . ". " . $myrow['bug_id'] . " " . $myrow['bug_when'] . "<br>";
- if ($myrow['added'] == "REOPENED")
- {
- $i--;
- }
- else
- {
- $i++;
- }
- }
-
- $dbc->disconnect();
- $rs = null;
- $dbh = null;
- $dbc = null;
-?>
-</body>
-</html>
\ No newline at end of file
diff --git a/development/bugs/top10.php b/development/bugs/top10.php
deleted file mode 100644
index 9a10811..0000000
--- a/development/bugs/top10.php
+++ /dev/null
@@ -1,149 +0,0 @@
-<?php
- function shiftDown($array, $size, $start)
- {
- for ($i = $size; $i > $start; $i--)
- {
- $array[$i] = $array[$i - 1];
- }
- return $array;
- }
-
- function genTop10($sqlquery, $urlquery, $col2name, $dayBuffer)
- {
- require_once "/home/data/httpd/eclipse-php-classes/system/dbconnection_bugs_ro.class.php";
-
- # Connect to database
- $dbc = new DBConnectionBugs();
- $dbh = $dbc->connect();
- $rs = mysql_query($sqlquery, $dbh);
-
- if(mysql_errno($dbh) > 0)
- {
- echo "There was an error processing this request".
-
- # For debugging purposes - don't display this stuff in a production page.
- # echo mysql_error($dbh);
-
- # Mysql disconnects automatically, but I like my disconnects to be explicit.
- $dbc->disconnect();
- exit;
- }
-
- $currReporter = null;
- $reporter[1] = null;
- $reporter[2] = null;
- $reporter[3] = null;
- $reporter[4] = null;
- $reporter[5] = null;
- $reporter[6] = null;
- $reporter[7] = null;
- $reporter[8] = null;
- $reporter[9] = null;
- $reporter[10] = null;
- $currCount = 0;
- $count[1] = 0;
- $count[2] = 0;
- $count[3] = 0;
- $count[4] = 0;
- $count[5] = 0;
- $count[6] = 0;
- $count[7] = 0;
- $count[8] = 0;
- $count[9] = 0;
- $count[10] = 0;
- if ($dayBuffer == null)
- $dayBuffer = 0;
- $cutoff = date("YmdHis", mktime(date("H"), date("i"), date("s"), date("m"), date("d") - $dayBuffer, date("Y")));
- while($myrow = mysql_fetch_assoc($rs))
- {
- if ($myrow['reporter'] == null || $myrow['reporter'] == "")
- {
- $currReporter = null;
- $currCount = 0;
- continue;
- }
- if ($myrow['delta_ts'] != null && $cutoff < $myrow['delta_ts'])
- {
- continue;
- }
- if ($myrow['reporter'] != $currReporter)
- {
- if ($currReporter != null && $currCount > 0)
- {
- for ($i = 10; $i > 0; $i--)
- {
- if ($reporter[$i] == null)
- {
- if ($i == 1)
- {
- $reporter[1] = $currReporter;
- $count[1] = $currCount;
- break;
- }
- else
- {
- continue;
- }
- }
- else if ($currCount > $count[$i])
- {
- if ($i == 1)
- {
- $reporter = shiftDown($reporter, 10, 1);
- $count = shiftDown($count, 10, 1);
- $reporter[1] = $currReporter;
- $count[1] = $currCount;
- break;
- }
- else
- {
- continue;
- }
- }
- else if ($i != 10)
- {
- $reporter = shiftDown($reporter, 10, $i + 1);
- $count = shiftDown($count, 10, $i + 1);
- $reporter[$i + 1] = $currReporter;
- $count[$i + 1] = $currCount;
- break;
- }
- else
- {
- break;
- }
- }
- }
- $currReporter = $myrow['reporter'];
- $currCount = 1;
- }
- else
- {
- $currCount++;
- }
- }
-
- $dbc->disconnect();
- $rs = null;
- $dbh = null;
- $dbc = null;
-
- echo "<table border=\"1\" cellspacing=\"0\" align=\"center\">";
- echo "<tr><th>Rank</th><th>$col2name</th><th>Bug count</th></tr>";
- for ($i = 1; $i <= 10; $i++)
- {
- if ($reporter[$i] != null && $count[$i] > 0)
- {
- if ($i % 2 != 0)
- {
- echo "<tr><td align=\"center\" bgcolor=\"#dddddd\">$i</td><td bgcolor=\"#dddddd\" align=\"right\">$reporter[$i]</td><td bgcolor=\"#dddddd\" align=\"right\"><a href=\"$urlquery\">$count[$i]</a></td></tr>";
- }
- else
- {
- echo "<tr><td align=\"center\">$i</td><td align=\"right\">$reporter[$i]</td><td align=\"right\"><a href=\"$urlquery\">$count[$i]</a></td></tr>";
- }
- }
- }
- echo "</table>";
- }
-?>
\ No newline at end of file
diff --git a/development/bugs/top10Resolved.php b/development/bugs/top10Resolved.php
deleted file mode 100644
index 6c8bcc8..0000000
--- a/development/bugs/top10Resolved.php
+++ /dev/null
@@ -1,40 +0,0 @@
-<html>
-
-<head>
-<title>Top 10: Resolved, Unverified Bugs</title>
-</head>
-
-<body>
-<table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%">
- <tr>
- <td WIDTH="100%">
- <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" BGCOLOR="#006699">
- <tr>
- <td BGCOLOR="#000000" width="116">
- <img src="http://bugs.eclipse.org/bugs/images/EclipseBannerPic.jpg" width="115" height="50">
- </td>
- <td WIDTH="637">
- <a href=http://www.eclipse.org><img SRC="http://bugs.eclipse.org/bugs/images/gradient.jpg" BORDER=0 height=50 width=282></a>
- </td>
- <td WIDTH="250">
- <img src="http://bugs.eclipse.org/bugs/images/eproject-simple.gif" width="250" height="48">
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</table>
-
-<table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%">
- <tr>
- <td><h2>Top 10: Resolved, Unverified Bugs</h2></td>
- </tr>
-</table>
-
-<?php
-include 'top10.php';
-genTop10("SELECT USR.realname AS reporter, BUG.bug_severity, BUG.delta_ts FROM bugs AS BUG INNER JOIN products AS PROD ON PROD.id = BUG.product_id INNER JOIN profiles AS USR ON USR.userid = BUG.reporter WHERE PROD.name='Web Tools' AND BUG.bug_status='RESOLVED' AND BUG.resolution NOT IN ('REMIND','LATER') ORDER BY USR.realname", "https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=reporter&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=RESOLVED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=%28to_days%28now%28%29%29+-+to_days%28bugs.delta_ts%29%29&type0-0-0=greaterthan&value0-0-0=14&field0-1-0=resolution&type0-1-0=nowords&value0-1-0=LATER+REMIND", "Reporter", 14);
-?>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/development/bugs/top10ResolvedByComp.php b/development/bugs/top10ResolvedByComp.php
deleted file mode 100644
index 5a67e4f..0000000
--- a/development/bugs/top10ResolvedByComp.php
+++ /dev/null
@@ -1,40 +0,0 @@
-<html>
-
-<head>
-<title>Top 10: Resolved, Unverified Bugs</title>
-</head>
-
-<body>
-<table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%">
- <tr>
- <td WIDTH="100%">
- <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" BGCOLOR="#006699">
- <tr>
- <td BGCOLOR="#000000" width="116">
- <img src="http://bugs.eclipse.org/bugs/images/EclipseBannerPic.jpg" width="115" height="50">
- </td>
- <td WIDTH="637">
- <a href=http://www.eclipse.org><img SRC="http://bugs.eclipse.org/bugs/images/gradient.jpg" BORDER=0 height=50 width=282></a>
- </td>
- <td WIDTH="250">
- <img src="http://bugs.eclipse.org/bugs/images/eproject-simple.gif" width="250" height="48">
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</table>
-
-<table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%">
- <tr>
- <td><h2>Top 10: Resolved, Unverified Bugs</h2></td>
- </tr>
-</table>
-
-<?php
-include 'top10.php';
-genTop10("SELECT COMP.name AS reporter, BUG.bug_severity, BUG.delta_ts FROM bugs AS BUG INNER JOIN products AS PROD ON PROD.id = BUG.product_id INNER JOIN components AS COMP ON COMP.id = BUG.component_id WHERE PROD.name='Web Tools' AND BUG.bug_status='RESOLVED' AND BUG.resolution NOT IN ('REMIND','LATER') ORDER BY COMP.name", "https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=RESOLVED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=%28to_days%28now%28%29%29+-+to_days%28bugs.delta_ts%29%29&type0-0-0=greaterthan&value0-0-0=14&field0-1-0=resolution&type0-1-0=nowords&value0-1-0=LATER+REMIND", "Component", 14);
-?>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/development/bugs/top10Verified.php b/development/bugs/top10Verified.php
deleted file mode 100644
index b8252a5..0000000
--- a/development/bugs/top10Verified.php
+++ /dev/null
@@ -1,40 +0,0 @@
-<html>
-
-<head>
-<title>Top 10: Verified, Not Closed Bugs</title>
-</head>
-
-<body>
-<table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%">
- <tr>
- <td WIDTH="100%">
- <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" BGCOLOR="#006699">
- <tr>
- <td BGCOLOR="#000000" width="116">
- <img src="http://bugs.eclipse.org/bugs/images/EclipseBannerPic.jpg" width="115" height="50">
- </td>
- <td WIDTH="637">
- <a href=http://www.eclipse.org><img SRC="http://bugs.eclipse.org/bugs/images/gradient.jpg" BORDER=0 height=50 width=282></a>
- </td>
- <td WIDTH="250">
- <img src="http://bugs.eclipse.org/bugs/images/eproject-simple.gif" width="250" height="48">
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</table>
-
-<table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%">
- <tr>
- <td><h2>Top 10: Verified, Not Closed Bugs</h2></td>
- </tr>
-</table>
-
-<?php
-include 'top10.php';
-genTop10("SELECT USR.realname AS reporter, BUG.bug_severity, BUG.delta_ts FROM bugs AS BUG INNER JOIN products AS PROD ON PROD.id = BUG.product_id INNER JOIN profiles AS USR ON USR.userid = BUG.assigned_to WHERE PROD.name='Web Tools' AND BUG.bug_status='VERIFIED' ORDER BY USR.realname", "https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=assigned_to&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=VERIFIED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=%28to_days%28now%28%29%29+-+to_days%28bugs.delta_ts%29%29&type0-0-0=greaterthan&value0-0-0=14", "Owner", 14);
-?>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/development/bugs/top10VerifiedByComp.php b/development/bugs/top10VerifiedByComp.php
deleted file mode 100644
index 761a9ac..0000000
--- a/development/bugs/top10VerifiedByComp.php
+++ /dev/null
@@ -1,40 +0,0 @@
-<html>
-
-<head>
-<title>Top 10: Verified, Not Closed Bugs</title>
-</head>
-
-<body>
-<table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%">
- <tr>
- <td WIDTH="100%">
- <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" BGCOLOR="#006699">
- <tr>
- <td BGCOLOR="#000000" width="116">
- <img src="http://bugs.eclipse.org/bugs/images/EclipseBannerPic.jpg" width="115" height="50">
- </td>
- <td WIDTH="637">
- <a href=http://www.eclipse.org><img SRC="http://bugs.eclipse.org/bugs/images/gradient.jpg" BORDER=0 height=50 width=282></a>
- </td>
- <td WIDTH="250">
- <img src="http://bugs.eclipse.org/bugs/images/eproject-simple.gif" width="250" height="48">
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</table>
-
-<table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%">
- <tr>
- <td><h2>Top 10: Verified, Not Closed Bugs</h2></td>
- </tr>
-</table>
-
-<?php
-include 'top10.php';
-genTop10("SELECT COMP.name AS reporter, BUG.bug_severity, BUG.delta_ts FROM bugs AS BUG INNER JOIN products AS PROD ON PROD.id = BUG.product_id INNER JOIN components AS COMP ON COMP.id = BUG.component_id WHERE PROD.name='Web Tools' AND BUG.bug_status='VERIFIED' ORDER BY COMP.name", "https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=VERIFIED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=%28to_days%28now%28%29%29+-+to_days%28bugs.delta_ts%29%29&type0-0-0=greaterthan&value0-0-0=14", "Component", 14);
-?>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/development/contributing.html b/development/contributing.html
deleted file mode 100644
index adb6697..0000000
--- a/development/contributing.html
+++ /dev/null
@@ -1,112 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
- "http://www.w3.org/TR/html4/loose.dtd">
-
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-<link rel="stylesheet" href="../../default_style.css" type="text/css">
-</head>
-<body text="#000000" bgcolor="#ffffff" link="#0000ee" vlink="#551a8b" alink="#ff0000">
-
-<table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
- <tr>
- <td ALIGN=LEFT width="60%"><font class=indextop>eclipse web tools platform project</font><br>
- <font class=indexsub>contributing to the wtp project</font></td>
- <td WIDTH="40%">
- <img SRC="../../images/Idea.jpg" HSPACE=50 height=86 width=120 align=CENTER></td>
- </tr>
-</table>
-<table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
- <tr>
- <td ALIGN=LEFT VALIGN=TOP> <I>This document was inspired by the <A CLASS="external" HREF="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/cdt-home/developer/Commitment.html?cvsroot=Tools_Project" target="_top">Contributing
- to the CDT document</A><!-- This image doesn't exist. <img class="outlink" src="../jst/images/out.png" alt="" width="6" height="6" />--></I>
- </td>
- </tr>
-
-
-
- <tr>
- <td ALIGN=LEFT VALIGN=TOP BGCOLOR="#0080C0"><b>
- <font face="Arial,Helvetica" color="#FFFFFF">Introduction</font></b></td>
- </tr>
-
-
-
- <tr>
- <td valign="top">
-
-
-
-
-
-
-
-
-
-
-
-<P>
-People often ask, "What does it take to get involved with the development of the WTP?" There are many ways to get involved. On the lightweight end of scale, there is involvement by using the WTP and providing feedback and sharing your experiences on the Eclipse and WTP newsgroups. Beyond that, you can report problems that you discover, so that they may be addressed in future releases. A deeper level of involvement would be to actually solve some of the problems that you or others have uncovered by modifying/writing the necessary code and creating patches that can applied by the project committers. The final, and most beneficial way to get involved is to take responsibility for a significant piece of development work, whether it's enhancing a particular area of the tool or creating new functionality.
-<P>
-The purpose of this document is to help people and organizations understand what it means to "commit" to WTP Development at this highest level. Basically, it involves a commitment to describe, develop, test and document your contributions.
- </td>
- </tr>
-
-
-
- <tr>
- <td ALIGN=LEFT VALIGN=TOP BGCOLOR="#0080C0"><b>
- <font face="Arial,Helvetica" color="#FFFFFF">Commitment to Development</font></b></td>
- </tr>
- <tr>
- <td valign="top">
-<H4>Communicating Your Desires/Intentions</H4>
-<p>The first step involves letting the WTP user community and other WTP development
-team members what you propose. The mechanism for this is to create Bugzilla
-entries to describe the enhancements or new capabilities you propose to do. The
-mailing lists and/or newgroups could also be used for discussing or proposing,
-in a more informal way, enhancements or new capabilities. Anyway Bugzilla is seen
-here as a central repository of reference for enhancement demands. </p>
-<P>
-Bugzilla is the open source change management system used by Eclipse projects. To set these Bugzilla entries apart from other problem reports, the word "plan" should be used in the keywords field, and the severity of the entry should be set to "enhancement". Following these guidelines will ensure that all of these proposals get picked up by the appropriate query and recorded in the plan for the upcoming release.
-<P>
-Feature specifications (what your code will do) and design specifications (how it will do it) are an important aspect of the development effort. These specifications will allow the WTP community and the rest of the WTP development team to understand what you are doing and to provide feedback. The format of these documents is not important, the content is.
-<P>
-<H4>Becoming a committer</H4>
-<p>Every developer's contribution is welcomed. And by the time, developers can become committers. A committer is a developer who has write access to the source code repository for the associated subproject (or component), and has voting rights allowing to affect the future of the subproject (or component); other developers define patches and submit them, indirectly, through committers. A developer gains such committer rights through frequent and valuable contributions to a subproject, or component of a subproject (in the case of large subprojects). For more information in what it means to be or to become an Eclipse project or subproject committer, see the
-<a CLASS="wikipage" href="../project-charter.html">WTP Project Charter</a>. We should point out that creating and submitting quality patches is the best way to obtain committer privileges for future work.
-</p>
-<P>
-<P>
-<H4>Delivering the Code</H4>
-<p>Once the feature and design documents have been floated to the rest of the WTP community and feedback has been harvested, its time to start pushing the code changes into the development stream. For those that have committer privileges, these changes can be pushed directly into the stream. Those without committer privileges create patches that get reviewed and applied by committers. Patch requests are communicated via
-attachments to Bugzilla bugs. Being a committer entails certain responsibilities on its own which won't be discussed here.
-</p>
-<P>
-<H4>Commitment To Testing</H4>
-<p>Everyone that contributes content to Eclipse projects is expected to test their contributions. When contributing a significant enhancement or feature, that commitment means more than just assuring the community that the code has been tested. It means documenting a test plan and committing to execute that testing on release candidate builds. The Eclipse way of generating releases is to generate a series of release candidate builds after all of the development has been completed. Each release candidate goes through a test-fix cycle where everyone tests their contributions and communicates their findings. A collective decision is made as to which problems will get fixed for the next release candidate, and the process is repeated. Fewer and fewer fixes will be "blessed" as we progress through the release candidates.
-</p>
-<P>
-So, committing to contribute significant code to the WTP also means committing to participate in the test-fix cycles by executing your test plans against the release candidates build leading up to the final release build.
-<P>
-<H4>Commitment to Documentation</H4>
-<p>An important part of any enhancement or addition to the WTP is making sure that the on-line help of the tool stays current with the changes. The responsibility for updating/modifying/writing the on-line help content that is associated with some part of the tool lies with the contributors of the code. Unless the contributors have commit privileges, the on-line documentation content would get submitted as a patch, much the same as code. And, like code, producing and submitting quality documentation patches is the way to obtain documentation committer privileges.
-</p>
-<P>
- <I>Until a Documentation Style Guide is available for the WTP project, you may
- refer to the <A CLASS="external" HREF="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/cdt-home/user/docs.html?cvsroot=Tools_Project" target="_top">CDT
- Documentation Style Guide</A> to help maintain a constant look and feel
- for documentation originating from different contributors. There also a
- couple of links that take you to additional information on how to contribute
- help content for Eclipse projects.
- <P>
-So, finally, committing to contribute code to the WTP also means committing to contributing the associated on-line documentation content for the part of the tool that is being enhanced or created.</i><P></td>
-</tr>
-
-</table>
-
-</body>
-
-</html>
diff --git a/development/eclipse_WTP_project_plan_1_0.html b/development/eclipse_WTP_project_plan_1_0.html
deleted file mode 100644
index 9683115..0000000
--- a/development/eclipse_WTP_project_plan_1_0.html
+++ /dev/null
@@ -1,326 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
- <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
- <TITLE>Eclipse Project DRAFT 3.0 Plan</TITLE>
- <META NAME="GENERATOR" CONTENT="OpenOffice.org 1.1.2 (Win32)">
- <META NAME="AUTHOR" CONTENT="Eclipse Project PMC">
- <META NAME="CREATED" CONTENT="20040906;11223146">
- <META NAME="CHANGEDBY" CONTENT="D D">
- <META NAME="CHANGED" CONTENT="20040917;13293107">
- <META NAME="ProgId" CONTENT="FrontPage.Editor.Document">
- <!-- saved from url=(0072)http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_0.html -->
- <STYLE>
- <!--
- TD P { margin-left: 0.3cm; font-family: "arial", "helvetica", "geneva"; font-size: 10pt }
- H1 { margin-left: 0.3cm; font-family: "arial", "helvetica", "geneva"; font-size: 21pt }
- P { margin-left: 0.3cm; font-family: "arial", "helvetica", "geneva"; font-size: 10pt }
- H2 { margin-left: 0.3cm; font-family: "arial", "helvetica", "geneva"; line-height: 0.37cm }
- H4 { margin-left: 0.3cm }
- TH P { margin-left: 0.3cm; font-family: "arial", "helvetica", "geneva"; font-size: 10pt }
- -->
- </STYLE>
-</HEAD>
-<BODY LANG="fr-FR" DIR="LTR">
-<H1>Eclipse WTP Project 1.0 Plan (Draft)</H1>
-<P>Last revised Monday, September 17, 2004.<BR><BR>
-<I>Please send comments about this draft plan to the
-</I><A HREF="mailto:wtp-dev@eclipse.org">wtp-dev@eclipse.org</A> <I>developer
-mailing list.</I></P>
-<P>This document lays out the feature and API set for the next
-feature release of Eclipse WTP 1.0.
-</P>
-<UL>
- <LI><P STYLE="margin-bottom: 0cm"><A HREF="#Deliverables">Release
- deliverables</A>
- </P>
- <LI><P STYLE="margin-bottom: 0cm"><A HREF="#Milestones">Release
- milestones</A>
- </P>
- <LI><P STYLE="margin-bottom: 0cm"><A HREF="#TargetOperatingEnvironments">Target
- operating environments</A>
- </P>
- <LI><P STYLE="margin-bottom: 0cm"><A HREF="#Compatibility">Compatibility
- with previous releases</A>
- </P>
- <LI><P STYLE="margin-bottom: 0cm"><A HREF="#Themes">Themes</A>
- </P>
-</UL>
-<P><BR><BR>
-</P>
-<P>Plans do not materialize out of nowhere, nor are they entirely
-static. To ensure the planning process is transparent and open to the
-entire Eclipse community, we (the Eclipse WTP PMC) post plans in an
-embryonic form and revise them throughout the release cycle.
-</P>
-<P>The first part of the plan deals with the important matters of
-release deliverables, release milestones, target operating
-environments, and release-to-release compatibility. These are all
-things that need to be clear for any release, even if no features
-were to change.
-</P>
-<P>The remainder of the plan consists of themes underlying the
-development of the various Eclipse WTP subprojects.
-</P>
-<P>The current plan does not contain plan items for the various
-Eclipse WTP subprojects. The plan items are given into the detailed
-<A HREF="./milestone_plans/reports/report-milestone-overview.html">Eclipse
- WTP 1.0 Milestone Plan</A>
-</P>
-<H2><A NAME="Deliverables"></A>Release deliverables</H2>
-<P>The release deliverables have the same form as previous releases,
-namely:
-</P>
-<UL>
- <LI><P STYLE="margin-bottom: 0cm">Source code release for Eclipse
- WTP Project, available as versions tagged "R1_0" in the
- Eclipse WTP Project <A HREF="http://dev.eclipse.org/viewcvs/index.cgi/?cvsroot=WebTools_Project">CVS
- repository</A>.
- </P>
- <LI><P STYLE="margin-bottom: 0cm">Eclipse WTP Web Standard Tools
- runtime binary and SDK distribution (downloadable).
- </P>
- <LI><P STYLE="margin-bottom: 0cm">Eclipse WTP Web+J2EE Standard
- Tools runtime binary and SDK distribution (downloadable).
- </P>
-</UL>
-<H2><A NAME="Milestones"></A>Release milestones</H2>
-<P>Release milestones occurring at roughly 8 week intervals exist to
-facilitate coarse-grained planning and staging.</P>
-
-<P>
-See the
-<A HREF="./milestone_plans/reports/report-milestone-overview.html">Eclipse
- WTP 1.0 Milestone Plan</A> for details.
-</P>
-
-<H2><A NAME="TargetOperatingEnvironments"></A>Target Operating
-Environments</H2>
-<P>Eclipse WTP is built above Eclipse itself.
-</P>
-<P>Most of the Eclipse WTP is "pure" Java™ code and
-has no direct dependence on the underlying operating system. The
-chief dependence is therefore on Eclipse. The 1.0 release of the
-Eclipse WTP Project is written and compiled against version 1.4 of
-the Java 2 Platform APIs, and targeted to run on version 1.4 of the
-Java 2 Runtime Environment, Standard Edition.</P>
-<P>Eclipse WTP is tested and validated on the following reference
-platforms (this list is updated over the course of the release
-cycle):</P>
-<TABLE WIDTH=821 BORDER=1 CELLPADDING=2 CELLSPACING=3>
- <COL WIDTH=204>
- <COL WIDTH=75>
- <COL WIDTH=58>
- <COL WIDTH=451>
- <TR BGCOLOR="#cccccc">
- <TH COLSPAN=4 WIDTH=809>
- <P ALIGN=CENTER><FONT SIZE=4>Eclipse WTP Reference Platforms</FONT>
- </P>
- </TH>
- </TR>
- <TR>
- <TD WIDTH=204>
- <P><B>Operating system</B></P>
- </TD>
- <TD WIDTH=75>
- <P><B>Processor architecture</B></P>
- </TD>
- <TD WIDTH=58>
- <P><B>Window system</B></P>
- </TD>
- <TD WIDTH=451>
- <P><B>Java 2 Platform</B></P>
- </TD>
- </TR>
- <TR>
- <TD WIDTH=204>
- <P>Microsoft Windows XP</P>
- </TD>
- <TD WIDTH=75>
- <P>Intel x86</P>
- </TD>
- <TD WIDTH=58>
- <P>Win32</P>
- </TD>
- <TD WIDTH=451>
- <P>Sun Java 2 SDK, Standard Edition, version 1.4.2_05 for
- Microsoft Windows</P>
- </TD>
- </TR>
- <TR>
- <TD WIDTH=204>
- <P>Microsoft Windows XP</P>
- </TD>
- <TD WIDTH=75>
- <P>Intel x86</P>
- </TD>
- <TD WIDTH=58>
- <P>Win32</P>
- </TD>
- <TD WIDTH=451>
- <P>IBM 32-bit SDK for Windows, Java 2 Technology Edition, Version
- 1.4.1</P>
- </TD>
- </TR>
- <TR>
- <TD WIDTH=204>
- <P>Red Hat Enterprise Linux WS 3</P>
- </TD>
- <TD WIDTH=75>
- <P>Intel x86</P>
- </TD>
- <TD WIDTH=58>
- <P>GTK</P>
- </TD>
- <TD WIDTH=451>
- <P>Sun Java 2 SDK, Standard Edition, 1.4.2_05 for Linux x86</P>
- </TD>
- </TR>
- <TR>
- <TD WIDTH=204>
- <P>Red Hat Enterprise Linux WS 3</P>
- </TD>
- <TD WIDTH=75>
- <P>Intel x86</P>
- </TD>
- <TD WIDTH=58>
- <P>GTK</P>
- </TD>
- <TD WIDTH=451>
- <P>IBM 32-bit SDK for Linux on Intel architecture, Java 2
- Technology Edition, Version 1.4.1</P>
- </TD>
- </TR>
- <TR>
- <TD WIDTH=204>
- <P>SuSE Linux 8.2</P>
- </TD>
- <TD WIDTH=75>
- <P>Intel x86</P>
- </TD>
- <TD WIDTH=58>
- <P>GTK</P>
- </TD>
- <TD WIDTH=451>
- <P>Sun Java 2 SDK, Standard Edition, 1.4.2_05 for Linux x86</P>
- </TD>
- </TR>
- <TR>
- <TD WIDTH=204>
- <P>SuSE Linux 8.2</P>
- </TD>
- <TD WIDTH=75>
- <P>Intel x86</P>
- </TD>
- <TD WIDTH=58>
- <P>GTK</P>
- </TD>
- <TD WIDTH=451>
- <P>IBM 32-bit SDK for Linux on Intel architecture, Java 2
- Technology Edition, Version 1.4.1</P>
- </TD>
- </TR>
-</TABLE>
-<P>Although untested, Eclipse WTP should work fine on other OSes that
-support the same window system. See also <A HREF="http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_1.html#TargetOperatingEnvironments">Eclipse
-Target Operating Environments</A>.
-</P>
-<P>Eclipse WTP is planned to support models for projects, editors,
-web and J2EE artifacts, servers. Whereas Eclipse WTP would not add OS
-dependencies to support the first three, projects, editors and
-artifacts, integrating servers to Eclipse WTP would imply some OS
-dependencies. Eclipse WTP is targeted to be OS independent through a
-modular conception. So, components for servers integration will be
-availabe out of Eclipse WTP Web, or J2EE, Standard Tools runtime
-binary distributions.</P>
-<P>Servers integrated into Eclipse WTP deliverables will be tested
-and validated on the same platforms listed above. Tests for other
-platforms will be relying on the community support.</P>
-<H4>Internationalization</H4>
-<P>The Eclipse WTP is designed as the basis for internationalized
-products. The user interface elements provided by the Eclipse SDK
-components, including dialogs and error messages, are externalized.
-The English strings are provided as the default resource bundles.
-Other language support, if any, will rely on the community support.</P>
-<H2><A NAME="Compatibility"></A>Compatibility with Other Eclipse
-Releases</H2>
-<P>There is no previous Eclipse WTP release. So, there is no
-compatibility issue for Eclipse WTP.</P>
-<P>Eclipse WTP deliverables will be compatible with Eclipse 3.1. No
-special attention will give for being compatible with previous
-Eclipse versions.</P>
-<H2><A NAME="Themes"></A>Themes</H2>
-<P>The Eclipse WTP Project consists of 2 subprojects. These themes
-are common to both subprojects.</P>
-<UL>
- <LI><P STYLE="margin-bottom: 0cm"><B>Built to last </B>- Eclipse has
- always been a platform for delivering integrated software tools.
- With a large and growing base of both free and commercial offerings
- based on Eclipse, it's critical for continued success to ensure that
- the platform scales well. This theme includes work to measure and
- improve the performance of key operations under various loads
- (number of installed plug-ins, number of resources in the workspace,
- etc.). This theme also includes support for user settings in order
- to let users choosing their own compromise between features and
- performance.
- </P>
- <LI><P STYLE="margin-bottom: 0cm"><B>Simple to use</B> - Eclipse WTP
- needs to not only provide the features that advanced users demand,
- but also be something that most users find simple to use. This theme
- includes ease-of-use reviews of existing features, and work that
- helps make Eclipse-based products simple to use for users with
- widely-varying backgrounds and skill sets.
- </P>
- <LI><P STYLE="margin-bottom: 0cm"><B>Large-scale development </B>-
- Large software projects are long-term collaborations involving large
- teams of developers playing a variety of roles. In order to be
- effective for large projects, software tools and processes must fit
- well into this reality. This theme includes laying the groundwork in
- the Eclipse WTP that will enable large teams to make effective use
- of Eclipse-based products. This theme will rely on components
- integration and flexible layout projects.</P>
- <LI><P STYLE="margin-bottom: 0cm"><B>User experience </B>- Improving
- Eclipse from the point of view of the end user. This includes
- improving both the "out of the box" experience so that new
- users are productive faster, and finding better ways to scale up to
- large numbers of plug-ins without overwhelming the user. This theme
- deals with reading, writing, and navigating in code, integrating
- information from different sources and providing guidance to users
- and making as explicit as possible how Eclipse works in order to
- improve Eclipse interaction.</P>
- <LI><P STYLE="margin-bottom: 0cm"><B>Responsive UI </B>- Making it
- easier to write Eclipse plug-ins that keep the UI responsive. Areas
- for improvement run the gamut from the UI becoming sluggish (or
- temporarily freezing) when blocking operations are done in the UI
- thread, to long-running operations like builds and searches which
- could be performed in the background while the user continues to
- work.</P>
- <LI><P STYLE="margin-bottom: 0cm"><B>Seamless edition of resources </B>-
- Generalize support to handle more members of the Java family than
- just Java source files. This includes widening to handle Java-like
- languages (such as JSP and SQLj), and embracing non-Java files (such
- as PHP, XSLT stylesheets, plug-in manifest files and J2EE deployment
- descriptors). Web and J2EE resources such as JSPs, XML, CSS, HTML,
- and deployment descriptors should be editable with the all the full
- features other well behaved Eclipse editors have, as applied to
- their specific needs, such as quick fix could "fix"
- xml/html syntax, rename/move should refactor links as well as java
- code, etc.</P>
- <LI><P STYLE="margin-bottom: 0cm"><B>Flexible project layout –</B>
- Users will have the ability to layout their projects in many ways,
- and still be able to deploy them in the standard J2EE ways. Ideally,
- they would still retain the ability to "run/debug in place"
- without doing the actual deployment, for performance reasons.</P>
- <LI><P STYLE="margin-bottom: 0cm"><B>Vendor ecosystem support –</B>
- Eclipse WTP is targeted to integrate with servers or external
- runtimes. Eclipse WTP respects vendor neutrality. This theme will
- rely on componentization and extensibility, to strengthen the
- long-term product value propositions of the widest possible range of
- application development implementations.</P>
-</UL>
-<P STYLE="margin-bottom: 0cm"><BR>
-</P>
-<P STYLE="margin-bottom: 0cm"><BR>
-</P>
-</BODY>
-</HTML>
diff --git a/development/guidelines/naming-conventions.html b/development/guidelines/naming-conventions.html
deleted file mode 100644
index 9aee129..0000000
--- a/development/guidelines/naming-conventions.html
+++ /dev/null
@@ -1,184 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../webtools/wtp.css" type="text/css">
-<title>wtp project naming conventions</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">naming conventions</font>
-<br>
-<font class="indexsub">wtp project naming conventions</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><em>Updated 2004-11-05</em></td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Introduction</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-This document summarizes the WTP project naming conventions for plug-ins, packages, and CVS modules.
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>Plug-ins and Packages</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-One of the main goals of this naming convention is to make it easy to find the component that any class belongs to.
-This is achieved by adopting the convention of putting the component name in the package or plug-in name, preferably as the fourth
-component.
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-The <a target="_top" href="http://help.eclipse.org/help30/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/misc/naming.html">Eclipse
-Platform Naming Conventions</a> state that following org.eclipse, the third component of the package or plug-in name
-should be the subproject name, which in our case is wst or jst.
-The fourth component is the component name, e.g. xml or jsp, unless the code is non-API which
-is signalled by the use of one of the following reserved words:
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>internal - code internal to the plug-in, i.e. not part of its API</li>
-
-<li>examples - example code</li>
-
-<li>tests - test cases</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-If one of the reserved works appears as the fourth part of the name, then the fifth part should be the component name.
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-In the WTP project we are relaxing this convention so that the reserved word may appear after the
-fourth component. For example, org.eclipse.wst.xml.tests indicates test cases that are used for the xml component
-of the wst subproject.
-The prefered usage is to put the reserved names in the fifth position, leaving the fourth position for the component name.
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-Consider the following examples for the server component of the wst subproject:
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>org.eclipse.server.ui.internal.debug - OK and the preferred naming</li>
-
-<li>org.eclipse.server.internal.ui.debug - OK for compatibility with Eclipse platform guidelines, but not preferred</li>
-
-<li>org.eclipse.server.ui.debug.internal - OK but not preferred</li>
-
-<li>org.eclipse.ui.debug.internal - WRONG since the component name is missing</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>CVS Modules</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-The WTP project <a href="http://dev.eclipse.org/viewcvs/index.cgi/?cvsroot=WebTools_Project">CVS</a> repository is organized as follows.
-The top level folder is the subproject name, i.e. wst or jst.
-The second level contains a components folders.
-The components folder contains one folder per component, e.g. xml or jsp.
-Each component folder contains the following folders:
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>features - the component features</li>
-
-<li>plugins - the comnponent plug-ins</li>
-
-<li>tests - the component test suites packaged as plug-ins</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-Any of the features, plugins, and tests folders may be absent if they do not apply to the component.
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-For example, the <a href="http://dev.eclipse.org/viewcvs/index.cgi/wst/components/server/?cvsroot=WebTools_Project">server</a>
-component of the wst subproject is organized as follows:
-<ul>
-
-<li>wst</li>
-
-<ul>
-
-<li>components</li>
-
-<ul>
-
-<li>server</li>
-
-<ul>
-
-<li>features</li>
-
-<li>plugins</li>
-
-<li>tests</li>
-
-</ul>
-
-</ul>
-
-</ul>
-
-</ul>
-
-</p>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/development/guidelines/naming-conventions.xml b/development/guidelines/naming-conventions.xml
deleted file mode 100644
index 6c0442c..0000000
--- a/development/guidelines/naming-conventions.xml
+++ /dev/null
@@ -1,92 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<?xml-stylesheet type="text/xsl" href="../../wtp.xsl"?>
-<html>
-<head>
- <title>wtp project naming conventions</title>
- <meta name="root" content="../../.." />
-</head>
-<body>
-
-<h1>naming conventions</h1>
-<em>Updated 2004-11-05</em>
-
-<h2>Introduction</h2>
-<p>
-This document summarizes the WTP project naming conventions for plug-ins, packages, and CVS modules.
-</p>
-
-<h3>Plug-ins and Packages</h3>
-<p>
-One of the main goals of this naming convention is to make it easy to find the component that any class belongs to.
-This is achieved by adopting the convention of putting the component name in the package or plug-in name, preferably as the fourth
-component.
-</p>
-<p>
-The <a target="_top" href="http://help.eclipse.org/help30/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/misc/naming.html">Eclipse
-Platform Naming Conventions</a> state that following org.eclipse, the third component of the package or plug-in name
-should be the subproject name, which in our case is wst or jst.
-The fourth component is the component name, e.g. xml or jsp, unless the code is non-API which
-is signalled by the use of one of the following reserved words:
-</p>
-<ul>
-<li>internal - code internal to the plug-in, i.e. not part of its API</li>
-<li>examples - example code</li>
-<li>tests - test cases</li>
-</ul>
-<p>
-If one of the reserved works appears as the fourth part of the name, then the fifth part should be the component name.
-</p>
-<p>
-In the WTP project we are relaxing this convention so that the reserved word may appear after the
-fourth component. For example, org.eclipse.wst.xml.tests indicates test cases that are used for the xml component
-of the wst subproject.
-The prefered usage is to put the reserved names in the fifth position, leaving the fourth position for the component name.
-</p>
-<p>
-Consider the following examples for the server component of the wst subproject:
-</p>
-<ul>
-<li>org.eclipse.server.ui.internal.debug - OK and the preferred naming</li>
-<li>org.eclipse.server.internal.ui.debug - OK for compatibility with Eclipse platform guidelines, but not preferred</li>
-<li>org.eclipse.server.ui.debug.internal - OK but not preferred</li>
-<li>org.eclipse.ui.debug.internal - WRONG since the component name is missing</li>
-</ul>
-
-
-<h3>CVS Modules</h3>
-<p>
-The WTP project <a href="http://dev.eclipse.org/viewcvs/index.cgi/?cvsroot=WebTools_Project">CVS</a> repository is organized as follows.
-The top level folder is the subproject name, i.e. wst or jst.
-The second level contains a components folders.
-The components folder contains one folder per component, e.g. xml or jsp.
-Each component folder contains the following folders:
-</p>
-<ul>
-<li>features - the component features</li>
-<li>plugins - the comnponent plug-ins</li>
-<li>tests - the component test suites packaged as plug-ins</li>
-</ul>
-<p>
-Any of the features, plugins, and tests folders may be absent if they do not apply to the component.
-</p>
-<p>
-For example, the <a href="http://dev.eclipse.org/viewcvs/index.cgi/wst/components/server/?cvsroot=WebTools_Project">server</a>
-component of the wst subproject is organized as follows:
-<ul>
-<li>wst</li>
-<ul>
-<li>components</li>
-<ul>
-<li>server</li>
-<ul>
-<li>features</li>
-<li>plugins</li>
-<li>tests</li>
-</ul>
-</ul>
-</ul>
-</ul>
-</p>
-
-</body>
-</html>
diff --git a/development/main.html b/development/main.html
deleted file mode 100644
index 25d1c74..0000000
--- a/development/main.html
+++ /dev/null
@@ -1,504 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../default_style.css" type="text/css">
-<link rel="stylesheet" href="../../webtools/wtp.css" type="text/css">
-<title>wtp project development</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">wtp project development</font>
-<br>
-<font class="indexsub">Eclipse Web Tools Platform (WTP) Project Development</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<br>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<table>
-<tr>
-<td valign="top">
-<table>
-<tr>
-<td valign="top">
-<table WIDTH="100%" CELLPADDING="2" CELLSPACING="5" BORDER="0">
-<tr>
-<td BGCOLOR="#0080C0" COLSPAN="2" VALIGN="TOP" ALIGN="LEFT"><b><font face="Arial,Helvetica" color="#FFFFFF">Development Tools</font></b></td>
-</tr>
-</table>
-<table width="100%" cellpadding="2" cellspacing="5" border="0">
-<tr>
-<td valign="TOP"></td>
-</tr>
-</table>
-<table width="100%" cellpadding="2" cellspacing="5" border="0">
- <tr>
- <td width="4%" valign="top" align="right"><img border="0" src="../../images/Adarrow.gif"></td><td width="46%" valign="top"><b><a href="http://www.eclipse.org/webtools/plans/1.0/reports/help-wanted.html">Help Wanted</a></b>
-<br>
- If you would like to contribute to the project, read this page to find work items.
- </td><td width="4%" valign="top" align="right"><img border="0" src="../../images/Adarrow.gif"></td><td width="46%" valign="top"><b><a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Web%20Tools">Bug Reports</a></b>
-<br>
- The WTP uses <a target="_top" href="http://bugzilla.mozilla.org/">Bugzilla</a> for bug tracking.
- <a href="bugs/bugs.html">View WTP bug reports</a> or
- <a target="_top" href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Web%20Tools">open new bugs</a>.
- </td>
- </tr>
-
- <tr>
- <td width="4%" valign="top" align="right"><img border="0" src="../../images/Adarrow.gif"></td><td width="46%" valign="top"><b><a href="http://www.eclipse.org/webtools/development/apiscanner/apiscanner.html">Eclipse API Scanner</a></b>
-<br>
- Describe the API of a component and scan plug-ins for API violations.
- </td><td width="4%" valign="top" align="right"><img border="0" src="../../images/Adarrow.gif"></td><td width="46%" valign="top"><b><a href="http://www.eclipse.org/webtools/development/piitools/piitools.html">Check Unused Properties Tool</a></b>
-<br>
- Scan property files for unused messages.
- </td>
- </tr>
-
- <tr>
- <td width="4%" valign="top" align="right"><img border="0" src="../../images/Adarrow.gif"></td><td width="46%" valign="top"><b><a href="http://www.eclipse.org/webtools/development/proposals/index.html">Technical Proposals</a></b>
-<br>
- Review available technical proposals.
- </td><td width="4%" valign="top" align="right"><img border="0" src="../../images/Adarrow.gif"></td><td width="46%" valign="top"><b><a href="http://dev.eclipse.org/viewcvs/index.cgi/?cvsroot=WebTools_Project">CVS Repository</a></b>
-<br>
- WTP development is carried out in a CVS repository. Both "pserver" and "extssh" are supported. See <a href="http://dev.eclipse.org/cvshowto.html">Using Eclipse with CVS</a> for instructions.
-
- </td>
- </tr>
- </table>
-<table width="100%" cellpadding="2" cellspacing="5" border="0"></table>
-</td><td valign="top"></td>
-</tr>
-</table>
-<table>
-<tr>
-<td valign="top">
-<table WIDTH="100%" CELLPADDING="2" CELLSPACING="5" BORDER="0">
-<tr>
-<td BGCOLOR="#0080C0" COLSPAN="2" VALIGN="TOP" ALIGN="LEFT"><b><font face="Arial,Helvetica" color="#FFFFFF">Development Resources - Learn about WTP Development</font></b></td>
-</tr>
-</table>
-<table width="100%" cellpadding="2" cellspacing="5" border="0">
-<tr>
-<td valign="TOP"></td>
-</tr>
-</table>
-<table width="100%" cellpadding="2" cellspacing="5" border="0">
- <tr>
- <td width="4%" valign="top" align="right"><img border="0" src="../../images/Adarrow.gif"></td><td width="46%" valign="top"><b><a href="contributing.html">Contributing to the WTP Project</a></b>
-<br>
- Learn what's involved in developing and contributing enhancements or new capabilities for the WTP.
- </td><td width="4%" valign="top" align="right"><img border="0" src="../../images/Adarrow.gif"></td><td width="46%" valign="top"><b><a href="http://dev.eclipse.org/viewcvs/index.cgi/*checkout*/org.eclipse.wtp.releng/readme.html?cvsroot=WebTools_Project">Build Process</a></b>
-<br>
- The WTP continuous build process is modeled after other Eclipse project build processes. The <a href="http://dev.eclipse.org/viewcvs/indexwebtools.cgi/%7Echeckout%7E/org.eclipse.wtp.releng/project_plan.html">build plan</a> and <a href="http://dev.eclipse.org/viewcvs/indexwebtools.cgi/%7Echeckout%7E/org.eclipse.wtp.releng/project_plan.html">build workflow for developers</a> are also documented.
- </td>
- </tr>
-
- <tr>
- <td width="4%" valign="top" align="right"><img border="0" src="../../images/Adarrow.gif"></td><td width="46%" valign="top"><b><a href="maintenance/R0_7_maintenance.html">Maintenance Stream Process</a></b>
-<br>
- This document talks about how to create and work with a maintenance stream/branch.
- </td><td width="4%" valign="top" align="right"><img border="0" src="../../images/Adarrow.gif"></td><td width="46%" valign="top"><b><a href="arch_and_design/pq-apis-20041115.ppt">Platform Quality APIs</a></b>
-<br>
- A presentation given by Jim des Rivières to some component teams in Raleigh, N.C., on 11/15/2004. It describes some principles and tips on producing platform quality designs and APIs. See slide 28 for a little laugh.
- </td>
- </tr>
-
- <tr>
- <td width="4%" valign="top" align="right"><img border="0" src="../../images/Adarrow.gif"></td><td width="46%" valign="top"><b><a href="guidelines/naming-conventions.html">Conventions and Guidelines</a></b>
-<br>
- Look here for the for the coding standards, naming conventions, and other guidelines we use to help ensure eclipse presents to users and developers as a unified whole rather than as a loose collection of parts.
- </td><td width="4%" valign="top" align="right"><img border="0" src="../../images/Adarrow.gif"></td><td width="46%" valign="top"><b><a href="arch_and_design/ArchitectureOverview.html">Architectural Overview</a></b>
-<br>
- A high level summary of the components and their architecture.
- </td>
- </tr>
-
- <tr>
- <td width="4%" valign="top" align="right"><img border="0" src="../../images/Adarrow.gif"></td><td width="46%" valign="top"><b><a href="status-telecons/index.html">Status Telecons</a></b>
-<br>
- Weekly development telecons to review status and discuss issues.
- </td><td width="4%" valign="top" align="right"><img border="0" src="../../images/Adarrow.gif"></td><td width="46%" valign="top"><b><a href="requirements/index.html">Project Requirements</a></b>
-<br>
- A description of the project requirements, requirements group, and requirements process.
- </td>
- </tr>
-
- <tr>
- <td width="4%" valign="top" align="right"><img border="0" src="../../images/Adarrow.gif"></td><td width="46%" valign="top"><b>Documents</b>
-<br>
-
-<a href="../faq/CommitterFAQ.html">Committer FAQ</a>
-<br>
-
-<a href="tests.html">Automated Testing</a>
-<br>
-
-<a href="WTPDevelopmentPractice.html">Development Practices</a>
-<br>
-
-<a href="../community/tutorials/DevelopingWTP/DevelopingWTP.html">Developing the WTP with Eclipse</a>
- </td><td width="4%" valign="top" align="right"><img border="0" src="../../images/Adarrow.gif"></td><td width="46%" valign="top"><b><a href="../people/contributors.html">Contributors and Committers</a></b>
-<br>
- List of Eclipse Web Tools Platform Project contributors and
- <A href="http://eclipse.org/webtools/commit.html">committers</A>.
- </td>
- </tr>
-
- <tr>
- <td width="4%" valign="top" align="right"><img border="0" src="../../images/Adarrow.gif"></td><td width="46%" valign="top"><b>Components and Teams</b>
-<br>
- Look here for details about the components and associated team members, grouped by subproject: <a href="http://www.eclipse.org/webtools/wst/components.html">Web Standard Tools components</a>, <a href="http://www.eclipse.org/webtools/jst/components.html">Java Standard Tools components</a>.
- </td>
- <td width="4%"></td>
- <td width="46%"></td>
- </tr>
- </table>
-<table width="100%" cellpadding="2" cellspacing="5" border="0"></table>
-</td><td valign="top"></td>
-</tr>
-</table>
-<table>
-<tr>
-<td valign="top">
-<table WIDTH="100%" CELLPADDING="2" CELLSPACING="5" BORDER="0">
-<tr>
-<td BGCOLOR="#0080C0" COLSPAN="2" VALIGN="TOP" ALIGN="LEFT"><b><font face="Arial,Helvetica" color="#FFFFFF">Initial WTP Code Contributions</font></b></td>
-</tr>
-</table>
-<table width="100%" cellpadding="2" cellspacing="5" border="0">
-<tr>
-<td valign="TOP">
-<a href="http://www.ibm.com" target="_top">IBM</a> and <a href="http://www.objectweb.org/" target="_top">ObjectWeb</a> provided initial code contributions to start the Web Tools Platform project. This code is has been moved into the <a href="http://dev.eclipse.org/viewcvs/index.cgi/?cvsroot=WebTools_Project">CVS repository</a>.<br>
-<br>
-The initial code contribution from IBM is now available as the <a href="http://www.alphaworks.ibm.com/tech/webtools" target="_top">IBM Web Tools for Eclipse</a> project hosted by <a href="http://www.alphaworks.ibm.com" target="_top">alphaWorks</a>.
-</td>
-</tr>
-</table>
-<table width="100%" cellpadding="2" cellspacing="5" border="0"></table>
-<table width="100%" cellpadding="2" cellspacing="5" border="0"></table>
-</td><td valign="top"></td>
-</tr>
-</table>
-</td><td valign="top">
-<TABLE border="0" width="275" cellpadding="0" cellspacing="0">
-<TR>
-<TD style="padding-top: 5px; padding-bottom: 5px;" bgcolor="#0080C0" height="15" rowspan="3">
-<center>
-<SPAN style="color: #ffffff; font-weight:bold; font-size: 11px; font-family: Verdana,Arial,Helvetica; padding-left: 5px; padding-right: 5px;">Releases</SPAN>
-</center>
-</TD><TD width="57%" height="13" rowspan="1"></TD>
-</TR>
-<TR>
-<TD bgcolor="#0080C0" height="3"><IMG height="10" width="1" src="../../images/c.gif"></TD>
-</TR>
-</TABLE>
-<TABLE border="0" width="275" cellpadding="0" cellspacing="0">
-<TR>
-<TD bgcolor="#0080C0"><IMG height="1" width="2" src="../../images/c.gif"></TD><TD bgcolor="white"><IMG height="1" width="5" src="../../images/c.gif"></TD><TD width="100%"><img align="right" border="0" src="../images/download.gif"><TABLE cellspacing="2" border="0">
-<TBODY>
-<TR>
-<TD><b>WTP 1.0</b>
-<table border="0">
-<tr></tr>
-</table>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top">
- <a href="http://download.eclipse.org/webtools/downloads/">Downloads</a>
- </td>
-</tr>
-</table>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top">
- <a href="http://www.eclipse.org/webtools/development/planning/roadmap.html">Roadmap</a>
- </td>
-</tr>
-</table>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top">
- <a href="http://www.eclipse.org/webtools/plans/1.0/">Release Plans</a>
- </td>
-</tr>
-</table>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top">
- <a href="http://www.eclipse.org/webtools/plans/1.0/#Bugzilla">Bug List Reports</a>
- </td>
-</tr>
-</table>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top">
- <a href="http://www.eclipse.org/webtools/plans/1.0/#Milestone-Plans">Milestone Plans</a>
- </td>
-</tr>
-</table>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top">
- <a href="http://www.eclipse.org/webtools/plans/1.0/#Test-Plans">Test Plans</a>
- </td>
-</tr>
-</table>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top">
- <a href="http://www.eclipse.org/webtools/development/eclipse_WTP_project_plan_1_0.html">Project Plan</a>
- </td>
-</tr>
-</table>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top">
- <a href="http://www.eclipse.org/webtools/plans/1.0/reports/performance.html">Performance Improvement Plan</a>
- </td>
-</tr>
-</table>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top">
- <a href="http://www.eclipse.org/webtools/development/pmc_call_notes.html">Weekly PMC Conference Call Notes</a>
- </td>
-</tr>
-</table>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top">
- <a href="http://www.eclipse.org/webtools/development/requirements/index.html">Project Requirements</a>
- </td>
-</tr>
-</table>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top">
- <a href="http://www.eclipse.org/webtools/development/arch_and_design/arch_page.html">Architecture Group</a>
- </td>
-</tr>
-</table>
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-</TD><TD bgcolor="white"><IMG height="1" width="5" src="../../images/c.gif"></TD><TD bgcolor="#0080C0"><IMG height="1" width="2" src="../../images/c.gif"></TD>
-</TR>
-<TR>
-<TD colspan="5" bgcolor="#0080C0"></TD>
-</TR>
-</TABLE>
-<br>
-<TABLE border="0" width="275" cellpadding="0" cellspacing="0">
-<TR>
-<TD style="padding-top: 5px; padding-bottom: 5px;" bgcolor="#0080C0" height="15" rowspan="3">
-<center>
-<SPAN style="color: #ffffff; font-weight:bold; font-size: 11px; font-family: Verdana,Arial,Helvetica; padding-left: 5px; padding-right: 5px;">Mailing Lists</SPAN>
-</center>
-</TD><TD width="57%" height="13" rowspan="1"></TD>
-</TR>
-<TR>
-<TD bgcolor="#0080C0" height="3"><IMG height="10" width="1" src="../../images/c.gif"></TD>
-</TR>
-</TABLE>
-<TABLE border="0" width="275" cellpadding="0" cellspacing="0">
-<TR>
-<TD bgcolor="#0080C0"><IMG height="1" width="2" src="../../images/c.gif"></TD><TD bgcolor="white"><IMG height="1" width="5" src="../../images/c.gif"></TD><TD width="100%">
- WTP mailing lists are meant for discussion of development of the WTP project itself. For all other questions please use the <a href="../community/community.html#help">newsgroup</a> and report bugs through <a href="https://bugs.eclipse.org/bugs/query.cgi?product=Web%20Tools">Bugzilla</a>.
- <TABLE cellspacing="2" border="0">
-<TBODY>
-<TR>
-<TD><a href="https://dev.eclipse.org/mailman/listinfo/wtp-dev"><b>wtp-dev</b></a>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top" title="wtp-dev" link="https://dev.eclipse.org/mailman/listinfo/wtp-dev" icon="../../images/Adarrow.gif">
- General discussion of project-wide or architectural issues.
- </td>
-</tr>
-</table>
-<a href="https://dev.eclipse.org/mailman/listinfo/wtp-jst-dev"><b>wtp-jst-dev</b></a>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top" title="wtp-jst-dev" link="https://dev.eclipse.org/mailman/listinfo/wtp-jst-dev" icon="../../images/Adarrow.gif">
- J2EE Standard Tools developer discussions
- </td>
-</tr>
-</table>
-<a href="https://dev.eclipse.org/mailman/listinfo/wtp-wst-dev"><b>wtp-wst-dev</b></a>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top" title="wtp-wst-dev" link="https://dev.eclipse.org/mailman/listinfo/wtp-wst-dev" icon="../../images/Adarrow.gif">
- Web Standard Tools developer discussions.
- </td>
-</tr>
-</table>
-<a href="https://dev.eclipse.org/mailman/listinfo/wtp-releng"><b>wtp-releng</b></a>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top" title="wtp-releng" link="https://dev.eclipse.org/mailman/listinfo/wtp-releng" icon="../../images/Adarrow.gif">
- Release engineering discussions and notifications.
- </td>
-</tr>
-</table>
-<a href="http://dev.eclipse.org/mailman/listinfo/wtp-requirements"><b>wtp-requirements</b></a>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top" title="wtp-requirements" link="http://dev.eclipse.org/mailman/listinfo/wtp-requirements" icon="../../images/Adarrow.gif">
- Discussions of project-wide requirements.
- </td>
-</tr>
-</table>
-<a href="http://dev.eclipse.org/mailman/listinfo/wtp-pmc"><b>wtp-pmc</b></a>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top" title="wtp-pmc" link="http://dev.eclipse.org/mailman/listinfo/wtp-pmc" icon="../../images/Adarrow.gif">
- WTP PMC communications (including coordination, announcements, and Group discussions)
- </td>
-</tr>
-</table>
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-</TD><TD bgcolor="white"><IMG height="1" width="5" src="../../images/c.gif"></TD><TD bgcolor="#0080C0"><IMG height="1" width="2" src="../../images/c.gif"></TD>
-</TR>
-<TR>
-<TD colspan="5" bgcolor="#0080C0"></TD>
-</TR>
-</TABLE>
-<br>
-<TABLE border="0" width="275" cellpadding="0" cellspacing="0">
-<TR>
-<TD style="padding-top: 5px; padding-bottom: 5px;" bgcolor="#0080C0" height="15" rowspan="3">
-<center>
-<SPAN style="color: #ffffff; font-weight:bold; font-size: 11px; font-family: Verdana,Arial,Helvetica; padding-left: 5px; padding-right: 5px;">Related Projects</SPAN>
-</center>
-</TD><TD width="57%" height="13" rowspan="1"></TD>
-</TR>
-<TR>
-<TD bgcolor="#0080C0" height="3"><IMG height="10" width="1" src="../../images/c.gif"></TD>
-</TR>
-</TABLE>
-<TABLE border="0" width="275" cellpadding="0" cellspacing="0">
-<TR>
-<TD bgcolor="#0080C0"><IMG height="1" width="2" src="../../images/c.gif"></TD><TD bgcolor="white"><IMG height="1" width="5" src="../../images/c.gif"></TD><TD width="100%">
-<TABLE cellspacing="2" border="0">
-<TBODY>
-<TR>
-<TD><b>Eclipse Projects</b>
-<table border="0">
-<tr></tr>
-</table>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top">
- <a href="http://www.eclipse.org/gmt/" target="_top">GMT</a> Generative Model Transformer (MDA)
- </td>
-</tr>
-</table>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top">
- <a href="http://www.eclipse.org/xsd/" target="_top">XSD</a> XML Schema Infoset Model
- </td>
-</tr>
-</table>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top">
- <a href="http://www.eclipse.org/wsvt/" target="_top">WSVT</a> Web Service Validation Tools
- </td>
-</tr>
-</table>
-<b>Apache Projects</b>
-<table border="0">
-<tr></tr>
-</table>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top">
- <a href="http://ws.apache.org/axis/" target="_top">Axis</a>
- </td>
-</tr>
-</table>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top">
- <a href="http://incubator.apache.org/projects/derby.html" target="_top">Derby</a>
- </td>
-</tr>
-</table>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top">
- <a href="http://geronimo.apache.org/" target="_top">Geronimo</a>
- </td>
-</tr>
-</table>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top">
- <a href="http://jakarta.apache.org/tomcat/index.html" target="_top">Tomcat</a>
- </td>
-</tr>
-</table>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top">
- <a href="http://incubator.apache.org/woden/" target="_top">Woden</a>
- </td>
-</tr>
-</table>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top">
- <a href="http://xml.apache.org/xerces2-j/" target="_top">Xerces</a>
- </td>
-</tr>
-</table>
-<b>Other Projects</b>
-<table border="0">
-<tr></tr>
-</table>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top">
- <a href="http://www.jboss.org/products/jbossas" target="_top">JBoss Application Server</a>
- </td>
-</tr>
-</table>
-<table border="0">
-<tr>
-<td valign="top"><img src="../../images/Adarrow.gif"></td><td valign="top">
- <a href="http://jonas.objectweb.org/" target="_top">JOnAS application server</a>
- </td>
-</tr>
-</table>
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-</TD><TD bgcolor="white"><IMG height="1" width="5" src="../../images/c.gif"></TD><TD bgcolor="#0080C0"><IMG height="1" width="2" src="../../images/c.gif"></TD>
-</TR>
-<TR>
-<TD colspan="5" bgcolor="#0080C0"></TD>
-</TR>
-</TABLE>
-<br>
-</td>
-</tr>
-</table>
-</tbody>
-</table>
-<p></p>
-<p>Please see our <a href="http://www.eclipse.org/legal/privacy.html">privacy
- policy</a> and website <a href="http://www.eclipse.org/legal/termsofuse.html">terms
- of use</a>. For problems with the eclipse.org site, please contact the
- <a href="mailto:webmaster@eclipse.org">webmaster</a> or read the
- <a href="../../webmaster/index.html">webmaster FAQ</a> for answers to common questions!</p>
-</body>
-</html>
diff --git a/development/main.xml b/development/main.xml
deleted file mode 100644
index ec4bd31..0000000
--- a/development/main.xml
+++ /dev/null
@@ -1,177 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<?xml-stylesheet type="text/xsl" href="../wtphome.xsl"?>
-<sections title="wtp project development" subtitle="Eclipse Web Tools Platform (WTP) Project Development">
- <meta name="root" content="../.." />
-<section class="infobox" name="Releases" icon="../images/download.gif">
- <item title="WTP 1.0" icon="../../images/Adarrow.gif"/>
- <item>
- <a href="http://download.eclipse.org/webtools/downloads/">Downloads</a>
- </item>
- <item>
- <a href="http://www.eclipse.org/webtools/development/planning/roadmap.html">Roadmap</a>
- </item>
- <item>
- <a href="http://www.eclipse.org/webtools/plans/1.0/">Release Plans</a>
- </item>
- <item>
- <a href="http://www.eclipse.org/webtools/plans/1.0/#Bugzilla">Bug List Reports</a>
- </item>
- <item>
- <a href="http://www.eclipse.org/webtools/plans/1.0/#Milestone-Plans">Milestone Plans</a>
- </item>
- <item>
- <a href="http://www.eclipse.org/webtools/plans/1.0/#Test-Plans">Test Plans</a>
- </item>
- <item>
- <a href="http://www.eclipse.org/webtools/development/eclipse_WTP_project_plan_1_0.html">Project Plan</a>
- </item>
- <item>
- <a href="http://www.eclipse.org/webtools/plans/1.0/reports/performance.html">Performance Improvement Plan</a>
- </item>
- <item>
- <a href="http://www.eclipse.org/webtools/development/pmc_call_notes.html">Weekly PMC Conference Call Notes</a>
- </item>
- <item>
- <a href="http://www.eclipse.org/webtools/development/requirements/index.html">Project Requirements</a>
- </item>
- <item>
- <a href="http://www.eclipse.org/webtools/development/arch_and_design/arch_page.html">Architecture Group</a>
- </item>
-</section>
-<section class="infobox" name="Mailing Lists">
- <description>
- WTP mailing lists are meant for discussion of development of the WTP project itself. For all other questions please use the <a href="../community/community.html#help">newsgroup</a> and report bugs through <a href="https://bugs.eclipse.org/bugs/query.cgi?product=Web%20Tools">Bugzilla</a>.
- </description>
- <item title="wtp-dev" link="https://dev.eclipse.org/mailman/listinfo/wtp-dev" icon="../../images/Adarrow.gif">
- General discussion of project-wide or architectural issues.
- </item>
- <item title="wtp-jst-dev" link="https://dev.eclipse.org/mailman/listinfo/wtp-jst-dev" icon="../../images/Adarrow.gif">
- J2EE Standard Tools developer discussions
- </item>
- <item title="wtp-wst-dev" link="https://dev.eclipse.org/mailman/listinfo/wtp-wst-dev" icon="../../images/Adarrow.gif">
- Web Standard Tools developer discussions.
- </item>
- <item title="wtp-releng" link="https://dev.eclipse.org/mailman/listinfo/wtp-releng" icon="../../images/Adarrow.gif">
- Release engineering discussions and notifications.
- </item>
- <item title="wtp-requirements" link="http://dev.eclipse.org/mailman/listinfo/wtp-requirements" icon="../../images/Adarrow.gif">
- Discussions of project-wide requirements.
- </item>
- <item title="wtp-pmc" link="http://dev.eclipse.org/mailman/listinfo/wtp-pmc" icon="../../images/Adarrow.gif">
- WTP PMC communications (including coordination, announcements, and Group discussions)
- </item>
-</section>
-<section class="infobox" name="Related Projects">
- <item title="Eclipse Projects"/>
- <item>
- <a href="http://www.eclipse.org/gmt/" target="_top">GMT</a> Generative Model Transformer (MDA)
- </item>
- <item>
- <a href="http://www.eclipse.org/xsd/" target="_top">XSD</a> XML Schema Infoset Model
- </item>
- <item>
- <a href="http://www.eclipse.org/wsvt/" target="_top">WSVT</a> Web Service Validation Tools
- </item>
- <item title="Apache Projects"/>
- <item>
- <a href="http://ws.apache.org/axis/" target="_top">Axis</a>
- </item>
- <item>
- <a href="http://incubator.apache.org/projects/derby.html" target="_top">Derby</a>
- </item>
- <item>
- <a href="http://geronimo.apache.org/" target="_top">Geronimo</a>
- </item>
- <item>
- <a href="http://jakarta.apache.org/tomcat/index.html" target="_top">Tomcat</a>
- </item>
- <item>
- <a href="http://incubator.apache.org/woden/" target="_top">Woden</a>
- </item>
- <item>
- <a href="http://xml.apache.org/xerces2-j/" target="_top">Xerces</a>
- </item>
- <item title="Other Projects"/>
- <item>
- <a href="http://www.jboss.org/products/jbossas" target="_top">JBoss Application Server</a>
- </item>
- <item>
- <a href="http://jonas.objectweb.org/" target="_top">JOnAS application server</a>
- </item>
-</section>
-
-<section class="main" name="Development Tools">
- <section name="Help Wanted" link="http://www.eclipse.org/webtools/plans/1.0/reports/help-wanted.html" icon="../../images/Adarrow.gif">
- If you would like to contribute to the project, read this page to find work items.
- </section>
- <section name="Bug Reports" link="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Web%20Tools" icon="../../images/Adarrow.gif">
- The WTP uses <a target="_top" href="http://bugzilla.mozilla.org/">Bugzilla</a> for bug tracking.
- <a href="bugs/bugs.html">View WTP bug reports</a> or
- <a target="_top" href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Web%20Tools">open new bugs</a>.
- </section>
- <section name="Eclipse API Scanner" link="http://www.eclipse.org/webtools/development/apiscanner/apiscanner.html" icon="../../images/Adarrow.gif">
- Describe the API of a component and scan plug-ins for API violations.
- </section>
- <section name="Check Unused Properties Tool" link="http://www.eclipse.org/webtools/development/piitools/piitools.html" icon="../../images/Adarrow.gif">
- Scan property files for unused messages.
- </section>
- <section name="Technical Proposals" link="http://www.eclipse.org/webtools/development/proposals/index.html" icon="../../images/Adarrow.gif">
- Review available technical proposals.
- </section>
- <section name="CVS Repository" link="http://dev.eclipse.org/viewcvs/index.cgi/?cvsroot=WebTools_Project" icon="../../images/Adarrow.gif">
- WTP development is carried out in a CVS repository. Both "pserver" and "extssh" are supported. See <a href="http://dev.eclipse.org/cvshowto.html">Using Eclipse with CVS</a> for instructions.
- <!-- Use :pserver:anonymous@dev.eclipse.org:/home/webtools to access the repository. -->
- </section>
- </section>
-<section class="main" name="Development Resources - Learn about WTP Development">
- <section name="Contributing to the WTP Project" link="contributing.html" icon="../../images/Adarrow.gif">
- Learn what's involved in developing and contributing enhancements or new capabilities for the WTP.
- </section>
- <section name="Build Process" link="http://dev.eclipse.org/viewcvs/index.cgi/*checkout*/org.eclipse.wtp.releng/readme.html?cvsroot=WebTools_Project" icon="../../images/Adarrow.gif">
- The WTP continuous build process is modeled after other Eclipse project build processes. The <a href="http://dev.eclipse.org/viewcvs/indexwebtools.cgi/%7Echeckout%7E/org.eclipse.wtp.releng/project_plan.html">build plan</a> and <a href="http://dev.eclipse.org/viewcvs/indexwebtools.cgi/%7Echeckout%7E/org.eclipse.wtp.releng/project_plan.html">build workflow for developers</a> are also documented.
- </section>
- <section name="Maintenance Stream Process" link="maintenance/R0_7_maintenance.html" icon="../../images/Adarrow.gif">
- This document talks about how to create and work with a maintenance stream/branch.
- </section>
- <section name="Platform Quality APIs" link="arch_and_design/pq-apis-20041115.ppt" icon="../../images/Adarrow.gif">
- A presentation given by Jim des Rivières to some component teams in Raleigh, N.C., on 11/15/2004. It describes some principles and tips on producing platform quality designs and APIs. See slide 28 for a little laugh.
- </section>
- <section name="Conventions and Guidelines" link="guidelines/naming-conventions.html" icon="../../images/Adarrow.gif">
- Look here for the for the coding standards, naming conventions, and other guidelines we use to help ensure eclipse presents to users and developers as a unified whole rather than as a loose collection of parts.
- </section>
- <section name="Architectural Overview" link="arch_and_design/ArchitectureOverview.html" icon="../../images/Adarrow.gif">
- A high level summary of the components and their architecture.
- </section>
- <section name="Status Telecons" link="status-telecons/index.html" icon="../../images/Adarrow.gif">
- Weekly development telecons to review status and discuss issues.
- </section>
- <section name="Project Requirements" link="requirements/index.html" icon="../../images/Adarrow.gif">
- A description of the project requirements, requirements group, and requirements process.
- </section>
- <section name="Documents" icon="../../images/Adarrow.gif">
- <a href="../faq/CommitterFAQ.html">Committer FAQ</a><br/>
- <a href="tests.html">Automated Testing</a><br/>
- <a href="WTPDevelopmentPractice.html">Development Practices</a><br/>
- <a href="../community/tutorials/DevelopingWTP/DevelopingWTP.html">Developing the WTP with Eclipse</a>
- </section>
- <!-- section name="Development Practices" link="WTPDevelopmentPractice.html" icon="../../images/Adarrow.gif">
- This document describes guidelines, procedures, and "best practices" for WTP development.
- </section-->
- <section name="Contributors and Committers" link="../people/contributors.html" icon="../../images/Adarrow.gif">
- List of Eclipse Web Tools Platform Project contributors and
- <A href="http://eclipse.org/webtools/commit.html">committers</A>.
- </section>
- <!-- section name="Automated Testing" link="tests.html" icon="../../images/Adarrow.gif">
- This document outlines the principles of WTP automated testing. It also provides some guidelines for creating and running test cases.
- </section-->
- <section name="Components and Teams" icon="../../images/Adarrow.gif">
- Look here for details about the components and associated team members, grouped by subproject: <a href="http://www.eclipse.org/webtools/wst/components.html">Web Standard Tools components</a>, <a href="http://www.eclipse.org/webtools/jst/components.html">Java Standard Tools components</a>.
- </section>
-</section>
-<section class="main" name="Initial WTP Code Contributions">
-<description>
-<a href="http://www.ibm.com" target="_top">IBM</a> and <a href="http://www.objectweb.org/" target="_top">ObjectWeb</a> provided initial code contributions to start the Web Tools Platform project. This code is has been moved into the <a href="http://dev.eclipse.org/viewcvs/index.cgi/?cvsroot=WebTools_Project">CVS repository</a>.<br/><br/>
-The initial code contribution from IBM is now available as the <a href="http://www.alphaworks.ibm.com/tech/webtools" target="_top">IBM Web Tools for Eclipse</a> project hosted by <a href="http://www.alphaworks.ibm.com" target="_top">alphaWorks</a>.
-</description>
-</section>
-</sections>
\ No newline at end of file
diff --git a/development/maintenance/R0_7_maintenance.html b/development/maintenance/R0_7_maintenance.html
deleted file mode 100644
index 0e7ec98..0000000
--- a/development/maintenance/R0_7_maintenance.html
+++ /dev/null
@@ -1,159 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../webtools/wtp.css" type="text/css">
-<title>Web Tools Platform 0.7 maintenance stream proposal</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">WTP 0.7 maintenance stream proposal</font>
-<br>
-<font class="indexsub">Web Tools Platform 0.7 maintenance stream proposal</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p align="right">
-<em>Updated 2005-08-03</em>
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Introduction</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-Branch name: <b>R0_7_maintenance</b>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-The process described in this document follows the maintenance release process used by the
-Eclipse platform project. This process requires us to branch all the build related project.
-In WTP, that would be the <b>releng</b> and the <b>releng.builder</b> project. Unlike the build
-projects, plug-in projects and feature projects will be branched on demand, meaning we need to
-branch them when a fixed is needed in the maintenance stream.
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-There will not be any "HEAD" build for the maintenance stream. That means a maintenance build will
-always be built from the branched map files. The advantage for this approach is that we don't need
-to branch everything. If we want to do "HEAD" builds in the maintenance stream, then all plug-ins/features need
-to be branched regardless of whether changes are made to them or not. To keep things simple, let's
-stay away from "HEAD" builds. This means, you need to release all your changes before they would
-actually show up in a maintenance build. Releasing changes to the maintenance stream is the same
-as releasing changes to the 1.0 stream. The only difference is that you MUST release to the branched
-map files, not the HEAD map files.
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Creating a branch for a plug-in/feature</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-Creating a branch for a plug-in/feature is fairly easy, here's a laundry list of what needs to be done:
-<ol>
-
-<li>Check out the plug-in/feature project that you want to branch.</li>
-
-<li>Right click on the project > Team > Branch...</li>
-
-<li>Enter <b>R0_7_maintenance</b> as the branch name > OK.</li>
-
-<li>That's it. You have successfully created a branch. The following figures show you the
-difference between a HEAD branch project and a 0.7 maintenance branch project.</li>
-
-</ol>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<img src="figure1.gif">
-<img src="figure2.gif">
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Checking out from a branch</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-To check out from a branch:
-<ol>
-
-<li>Create a CVS location just like you normally would.</li>
-
-<li>Expand the HEAD branch, and right click on the project that you want to work with > Configure Branches and Versions...</li>
-
-<li>A dialog opens. In the <b>Browse files for tags</b> section of this dialog (top left region), select any file that has
-been branched. For example (I branched the <b>component-api.xsd</b> file for testing purposes)
-<br>
-<img src="figure3.gif">
-</li>
-
-<li>Once you have selected the file, the <b>New tags found in the selected files</b> section (top right region) should be
-updated with the 0.7 maintenance branch name. Make sure only the <b>R0_7_Maintenance</b> branch is checked.</li>
-
-<li>Click on the <b>Add Checked Tags</b> button.</li>
-
-<li>Click <b>OK</b>.</li>
-
-<li>A new branch should be created in your CVS location. You can check out and commit to branch just like the HEAD branch.
-<br>
-<img src="figure4.gif">
-</li>
-
-</ol>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-For changes that need to go into both the HEAD and 0.7 branch, I find that retrofitting/merging changes manually is the easiest.
-Since our 0.7 branch is limited to critical and NL fixes only, there shouldn't be too much work. However, if you like the Eclipse
-CVS tools, they do come with some merging tool that you can use. It helps you merge 0.7 branch change back into HEAD.
-This <a href="http://www.eclipse.org/articles/Article-CVS-branching/eclipse_branch.html">article</a> talks about this tool.
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Tracking 0.7 maintenance fixes in bugzilla</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-We now have a <b>1.0 M7.1</b> target in bugzilla. I suggest when a fix is retrofitted from the 1.0 stream
-to the 0.7 maintenance stream, we change the target of the corresponding bug to <b>1.0 M7.1</b>.
-We can then create a bugzilla query to see what fixes went into the maintenance stream.
-</p>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/development/maintenance/R0_7_maintenance.xml b/development/maintenance/R0_7_maintenance.xml
deleted file mode 100644
index ac298cb..0000000
--- a/development/maintenance/R0_7_maintenance.xml
+++ /dev/null
@@ -1,91 +0,0 @@
-<?xml-stylesheet type="text/xsl" href="../../wtphome.xsl"?>
-<html>
-<head>
- <title>Web Tools Platform 0.7 maintenance stream proposal</title>
- <meta name="root" content="../../.." />
-</head>
-<body>
-
-<h1>WTP 0.7 maintenance stream proposal</h1>
-<p align="right"><em>Updated 2005-08-03</em></p>
-
-<h2>Introduction</h2>
-
-<p>
-Branch name: <b>R0_7_maintenance</b>
-</p>
-
-<p>
-The process described in this document follows the maintenance release process used by the
-Eclipse platform project. This process requires us to branch all the build related project.
-In WTP, that would be the <b>releng</b> and the <b>releng.builder</b> project. Unlike the build
-projects, plug-in projects and feature projects will be branched on demand, meaning we need to
-branch them when a fixed is needed in the maintenance stream.
-</p>
-
-<p>
-There will not be any "HEAD" build for the maintenance stream. That means a maintenance build will
-always be built from the branched map files. The advantage for this approach is that we don't need
-to branch everything. If we want to do "HEAD" builds in the maintenance stream, then all plug-ins/features need
-to be branched regardless of whether changes are made to them or not. To keep things simple, let's
-stay away from "HEAD" builds. This means, you need to release all your changes before they would
-actually show up in a maintenance build. Releasing changes to the maintenance stream is the same
-as releasing changes to the 1.0 stream. The only difference is that you MUST release to the branched
-map files, not the HEAD map files.
-</p>
-
-<h2>Creating a branch for a plug-in/feature</h2>
-
-<p>
-Creating a branch for a plug-in/feature is fairly easy, here's a laundry list of what needs to be done:
-<ol>
-<li>Check out the plug-in/feature project that you want to branch.</li>
-<li>Right click on the project > Team > Branch...</li>
-<li>Enter <b>R0_7_maintenance</b> as the branch name > OK.</li>
-<li>That's it. You have successfully created a branch. The following figures show you the
-difference between a HEAD branch project and a 0.7 maintenance branch project.</li>
-</ol>
-</p>
-<p>
-<img src="figure1.gif"/>
-<img src="figure2.gif"/>
-</p>
-
-<h2>Checking out from a branch</h2>
-
-<p>
-To check out from a branch:
-<ol>
-<li>Create a CVS location just like you normally would.</li>
-<li>Expand the HEAD branch, and right click on the project that you want to work with > Configure Branches and Versions...</li>
-<li>A dialog opens. In the <b>Browse files for tags</b> section of this dialog (top left region), select any file that has
-been branched. For example (I branched the <b>component-api.xsd</b> file for testing purposes)
-<br/><img src="figure3.gif"/>
-</li>
-<li>Once you have selected the file, the <b>New tags found in the selected files</b> section (top right region) should be
-updated with the 0.7 maintenance branch name. Make sure only the <b>R0_7_Maintenance</b> branch is checked.</li>
-<li>Click on the <b>Add Checked Tags</b> button.</li>
-<li>Click <b>OK</b>.</li>
-<li>A new branch should be created in your CVS location. You can check out and commit to branch just like the HEAD branch.
-<br/><img src="figure4.gif"/>
-</li>
-</ol>
-</p>
-
-<p>
-For changes that need to go into both the HEAD and 0.7 branch, I find that retrofitting/merging changes manually is the easiest.
-Since our 0.7 branch is limited to critical and NL fixes only, there shouldn't be too much work. However, if you like the Eclipse
-CVS tools, they do come with some merging tool that you can use. It helps you merge 0.7 branch change back into HEAD.
-This <a href="http://www.eclipse.org/articles/Article-CVS-branching/eclipse_branch.html">article</a> talks about this tool.
-</p>
-
-<h2>Tracking 0.7 maintenance fixes in bugzilla</h2>
-
-<p>
-We now have a <b>1.0 M7.1</b> target in bugzilla. I suggest when a fix is retrofitted from the 1.0 stream
-to the 0.7 maintenance stream, we change the target of the corresponding bug to <b>1.0 M7.1</b>.
-We can then create a bugzilla query to see what fixes went into the maintenance stream.
-</p>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/development/maintenance/figure1.gif b/development/maintenance/figure1.gif
deleted file mode 100644
index b7fa09b..0000000
--- a/development/maintenance/figure1.gif
+++ /dev/null
Binary files differ
diff --git a/development/maintenance/figure2.gif b/development/maintenance/figure2.gif
deleted file mode 100644
index 0423648..0000000
--- a/development/maintenance/figure2.gif
+++ /dev/null
Binary files differ
diff --git a/development/maintenance/figure3.gif b/development/maintenance/figure3.gif
deleted file mode 100644
index f640be9..0000000
--- a/development/maintenance/figure3.gif
+++ /dev/null
Binary files differ
diff --git a/development/maintenance/figure4.gif b/development/maintenance/figure4.gif
deleted file mode 100644
index 6c89d70..0000000
--- a/development/maintenance/figure4.gif
+++ /dev/null
Binary files differ
diff --git a/development/milestone_plans/milestonePlan.xsd b/development/milestone_plans/milestonePlan.xsd
deleted file mode 100644
index a6d7375..0000000
--- a/development/milestone_plans/milestonePlan.xsd
+++ /dev/null
@@ -1,108 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xsd:schema targetNamespace="http://www.eclipse.org/webtools/milestonePlan.xsd" xmlns:tns="http://www.eclipse.org/webtools/milestonePlan.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.w3.org/2001/XMLSchema http://www.w3.org/2001/XMLSchema.xsd" elementFormDefault="qualified">
- <xsd:element name="plan">
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element ref="tns:component" minOccurs="0" maxOccurs="unbounded"></xsd:element>
- </xsd:sequence>
- <xsd:attribute name="scheduleInfo" type="xsd:boolean"></xsd:attribute>
- </xsd:complexType>
- </xsd:element>
- <xsd:element name="component">
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element ref="tns:description"></xsd:element>
- <xsd:element name="milestone" minOccurs="0" maxOccurs="unbounded">
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="title" type="xsd:string"></xsd:element>
- <xsd:element ref="tns:description" minOccurs="0"></xsd:element>
- <xsd:element name="category" maxOccurs="unbounded" minOccurs="0">
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element ref="tns:item" minOccurs="0" maxOccurs="unbounded"/>
- </xsd:sequence>
- <xsd:attribute name="name" type="xsd:string" use="required" />
- </xsd:complexType>
- </xsd:element>
- </xsd:sequence>
- <xsd:attribute name="name" type="xsd:string" use="required"></xsd:attribute>
- </xsd:complexType>
- </xsd:element>
- </xsd:sequence>
- <xsd:attribute name="name" type="xsd:string" use="required" />
- <xsd:attribute name="subproject" type="tns:subprojectValue" use="required"></xsd:attribute>
- </xsd:complexType>
- </xsd:element>
- <xsd:element name="item">
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element ref="tns:description" />
- <xsd:element name="detail" type="xsd:anyType" minOccurs="0"></xsd:element>
- <xsd:element maxOccurs="unbounded" ref="tns:developer" minOccurs="0" />
- <xsd:element name="step" minOccurs="0" maxOccurs="unbounded">
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element minOccurs="0" ref="tns:description" />
- <xsd:element minOccurs="0" ref="tns:developer" maxOccurs="unbounded" />
- </xsd:sequence>
- <xsd:attribute name="start" type="xsd:integer" />
- <xsd:attribute name="length" type="xsd:integer" />
- <xsd:attribute name="status" type="tns:statusValue" />
- <xsd:attribute name="pds" type="xsd:integer"></xsd:attribute>
- </xsd:complexType>
- </xsd:element>
- <xsd:element ref="tns:bugzilla" minOccurs="0" maxOccurs="unbounded"></xsd:element>
- <xsd:element ref="tns:junit-test" minOccurs="0" maxOccurs="unbounded"></xsd:element>
- <xsd:element name="verification" type="xsd:anyType" minOccurs="0"></xsd:element>
- </xsd:sequence>
- <xsd:attribute name="status" type="tns:statusValue" />
- <xsd:attribute name="pds" type="xsd:integer"></xsd:attribute>
- <xsd:attribute name="priority" type="tns:priorityValue"></xsd:attribute>
- <xsd:attribute name="helpWanted" type="xsd:boolean"></xsd:attribute>
- </xsd:complexType>
- </xsd:element>
- <xsd:element name="developer">
- <xsd:complexType>
- <xsd:attribute name="name" type="xsd:string" use="required" />
- </xsd:complexType>
- </xsd:element>
- <xsd:element name="description"></xsd:element>
- <xsd:simpleType name="statusValue">
- <xsd:restriction base="xsd:string">
- <xsd:enumeration value="in-progress"></xsd:enumeration>
- <xsd:enumeration value="done"></xsd:enumeration>
- <xsd:enumeration value="deferred"></xsd:enumeration>
- <xsd:enumeration value="time-permitted"></xsd:enumeration>
- <xsd:enumeration value="new"></xsd:enumeration>
- <xsd:enumeration value="investigate"></xsd:enumeration>
- </xsd:restriction>
- </xsd:simpleType>
- <xsd:simpleType name="priorityValue">
- <xsd:restriction base="xsd:string">
- <xsd:enumeration value="low"></xsd:enumeration>
- <xsd:enumeration value="medium"></xsd:enumeration>
- <xsd:enumeration value="high"></xsd:enumeration>
- </xsd:restriction>
- </xsd:simpleType>
-
- <xsd:simpleType name="subprojectValue">
- <xsd:restriction base="xsd:string">
- <xsd:enumeration value="wst"></xsd:enumeration>
- <xsd:enumeration value="jst"></xsd:enumeration>
- </xsd:restriction>
- </xsd:simpleType>
-
- <xsd:element name="bugzilla">
- <xsd:complexType>
- <xsd:attribute name="link" type="xsd:anyURI"></xsd:attribute>
- </xsd:complexType>
- </xsd:element>
-
- <xsd:element name="junit-test">
- <xsd:complexType>
- <xsd:attribute name="link" type="xsd:anyURI"></xsd:attribute>
- </xsd:complexType>
- </xsd:element>
-
-</xsd:schema>
diff --git a/development/milestone_plans/reports/help-wanted.html b/development/milestone_plans/reports/help-wanted.html
deleted file mode 100644
index 22fee20..0000000
--- a/development/milestone_plans/reports/help-wanted.html
+++ /dev/null
@@ -1,124 +0,0 @@
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
-<head>
-<title>eclipse WTP help wanted</title>
-<link rel="stylesheet" type="text/css" href="../stylesheets/images/default_style.css"/>
-</head>
-<body>
-<table border="0" width="100%" cellPadding="2" cellSpacing="5">
-<tr>
-<td>
-<font class="indextop">eclipse WTP help wanted</font>
-<br/>
-<font class="indexsub">eclipse web tools platform project help wanted</font>
-</td>
-<td>
-<br/>
-</td>
-<td width="28%">
-<img height="86" width="120" src="../../../development/milestone_plans/stylesheets/images/Idea.jpe"/>
-</td>
-</tr>
-</table>
-<table width="100%">
-<tr>
-<td colspan="2" bgcolor="#0080c0" height="20">
-<b>
-<font color="#ffffff">Help Wanted</font>
-</b>
-</td>
-</tr>
-<tr>
-<td colspan="2">
- Like all Open Source projects, WTP depends on an active community of contributors to accomplish its goals.
- This page lists work items where help is needed.
- If you'd like to contribute, please review this page to find a task that matches your interests and skills,
- then send a note to <a href="mailto:wtp-dev@eclipse.org">wtp-dev@eclipse.org</a> volunteering your assistance.
- The responsible component lead will contact you to coordinate your work.
- </td>
-</tr>
-</table>
-<br/>
-<table width="100%">
-<tr>
-<td>
-<img src="../../../development/milestone_plans/stylesheets/images/new.gif"/>
- You can also see the list of help wanted bugs <a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=priority&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=helpwanted&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by priority</a> and
- <a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=helpwanted&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by severity</a>
-</td>
-</tr>
-</table>
-<br/>
-<table width="100%">
-<tr align="left">
-<th>Yes, I'll Help!</th>
-<th>Milestone</th>
-<th>Priority</th>
-<th>Subproject</th>
-<th>Component</th>
-<th>Category</th>
-<th>Description</th>
-</tr>
-</table>
-<br/>
-<br/>
-<table border="0" width="100%" cellpadding="2" cellspacing="5">
-<tbody>
-<tr>
-<td colspan="4" bgcolor="#0080c0" width="100%" align="left" valign="top">
-<b>
-<font face="Arial,Helvetica">
-<font color="#ffffff">Legend</font>
-</font>
-</b>
-</td>
-</tr>
-<tr>
-<td valign="top">
-<img width="14" height="5" src="../../../development/milestone_plans/stylesheets/images/progress.gif"/>
-</td>
-<td width="50%">item is under development.</td>
-<td valign="top">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/glass.gif"/>
-</td>
-<td width="50%">item is under investigation.</td>
-</tr>
-<tr>
-<td valign="top">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/ok.gif"/>
-</td>
-<td width="50%">item is finished.</td>
-<td valign="top">
-<img width="40" height="12" src="../../../development/milestone_plans/stylesheets/images/help.gif"/>
-</td>
-<td width="50%">help wanted</td>
-</tr>
-<tr>
-<td valign="top">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/defer.gif"/>
-</td>
-<td width="50%">item is deferred.</td>
-<td valign="top">
-<font class="indexsub">
-<img src="../../../development/milestone_plans/stylesheets/images/new.gif"/>
-</font>
-</td>
-<td width="50%">new</td>
-</tr>
-</tbody>
-</table>
-<br/>
-<br/>
-<br/>
-<p>
- Please see our
- <a href="http://eclipse.org/legal/privacy.html">privacy policy</a>
- and website
- <a href="http://eclipse.org/legal/termsofuse.html">terms of use</a>
- . For problems with the eclipse.org site, please contact the
- <a href="mailto:webmaster@eclipse.org">webmaster</a>
- or read the
- <a href="http://eclipse.org/webmaster/index.html">webmaster FAQ</a>
- for answers to common questions!
- </p>
-</body>
-</html>
diff --git a/development/milestone_plans/reports/milestoneDates.xml b/development/milestone_plans/reports/milestoneDates.xml
deleted file mode 100644
index defb151..0000000
--- a/development/milestone_plans/reports/milestoneDates.xml
+++ /dev/null
@@ -1,39 +0,0 @@
-<milestoneDates>
- <milestone name="M3">
- <week date="Jan 3-7" />
- <week date="Jan 10-14" />
- <week date="Jan 17-21" />
- <week date="Jan 24-28" />
- <week date="Jan 31-Feb 4" />
- <week date="Feb 7-11" />
- <!-- last 2 weeks of milestone are reserved for testing -->
- <!-- <week date="Feb 14-18" /> -->
- <!-- <week date="Feb 21-25" /> -->
- </milestone>
- <milestone name="M4">
- <week date="Feb 28-Mar 4" />
- <week date="Mar 7-11" />
- <week date="Mar 14-18" />
- <week date="Mar 21-25" />
- <week date="Mar 28-Apr 1" />
- <week date="Apr 4-8" />
- <week date="Apr 11-15" />
- </milestone>
- <milestone name="M5">
- <week date="May 2 -May 6" />
- <week date="May 9 -May 13" />
- <week date="May 16-May 20" />
- <week date="May 23-May 27" />
- <week date="May 30-Jun 3" />
- <week date="Jun 6-Jun 10" />
- <week date="Jun 13-Jun 17" />
- <week date="Jun 20-Jun 24" />
- <week date="Jun 27-Jul 1" />
- </milestone>
- <milestone name="M6">
- <week date="Jul 4-Jul 8" />
- <week date="Jul 11-Jul 15" />
- <week date="Jul 18-Jul 22" />
- <week date="Jul 25-Jul 29" />
- </milestone>
-</milestoneDates>
\ No newline at end of file
diff --git a/development/milestone_plans/reports/performance.html b/development/milestone_plans/reports/performance.html
deleted file mode 100644
index 1223851..0000000
--- a/development/milestone_plans/reports/performance.html
+++ /dev/null
@@ -1,82 +0,0 @@
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
-<head>
-<title>Eclipse WTP performance improvement plan</title>
-<link rel="stylesheet" type="text/css" href="../stylesheets/images/default_style.css"/>
-</head>
-<body>
-<table border="0" width="100%" cellPadding="2" cellSpacing="5">
-<tr>
-<td>
-<font class="indextop">Eclipse WTP performance improvement plan</font>
-<br/>
-<font class="indexsub">Eclipse Web Tools Platform project performance improvements</font>
-</td>
-<td>
-<br/>
-</td>
-<td width="28%">
-<img height="86" width="120" src="../../../development/milestone_plans/stylesheets/images/Idea.jpe"/>
-</td>
-</tr>
-</table>
-<table border="0" width="100%" cellpadding="2" cellspacing="5">
-<tbody>
-<tr>
-<td colspan="4" bgcolor="#0080c0" width="100%" align="left" valign="top">
-<b>
-<font face="Arial,Helvetica">
-<font color="#ffffff">Legend</font>
-</font>
-</b>
-</td>
-</tr>
-<tr>
-<td valign="top">
-<img width="14" height="5" src="../../../development/milestone_plans/stylesheets/images/progress.gif"/>
-</td>
-<td width="50%">item is under development.</td>
-<td valign="top">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/glass.gif"/>
-</td>
-<td width="50%">item is under investigation.</td>
-</tr>
-<tr>
-<td valign="top">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/ok.gif"/>
-</td>
-<td width="50%">item is finished.</td>
-<td valign="top">
-<img width="40" height="12" src="../../../development/milestone_plans/stylesheets/images/help.gif"/>
-</td>
-<td width="50%">help wanted</td>
-</tr>
-<tr>
-<td valign="top">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/defer.gif"/>
-</td>
-<td width="50%">item is deferred.</td>
-<td valign="top">
-<font class="indexsub">
-<img src="../../../development/milestone_plans/stylesheets/images/new.gif"/>
-</font>
-</td>
-<td width="50%">new</td>
-</tr>
-</tbody>
-</table>
-<br/>
-<br/>
-<br/>
-<p>
- Please see our
- <a href="http://eclipse.org/legal/privacy.html">privacy policy</a>
- and website
- <a href="http://eclipse.org/legal/termsofuse.html">terms of use</a>
- . For problems with the eclipse.org site, please contact the
- <a href="mailto:webmaster@eclipse.org">webmaster</a>
- or read the
- <a href="http://eclipse.org/webmaster/index.html">webmaster FAQ</a>
- for answers to common questions!
- </p>
-</body>
-</html>
diff --git a/development/milestone_plans/reports/report-calendar-by-developer.html b/development/milestone_plans/reports/report-calendar-by-developer.html
deleted file mode 100644
index 29acc56..0000000
--- a/development/milestone_plans/reports/report-calendar-by-developer.html
+++ /dev/null
@@ -1,784 +0,0 @@
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
-<head>
-<title>Milestone Plan - Calendar View</title>
-<link rel="stylesheet" type="text/css" href="../stylesheets/images/default_style.css"/>
-</head>
-<body>
-<table border="0" width="100%" cellPadding="2" cellSpacing="5">
-<tr>
-<td>
-<font class="indextop">Example Team Plan</font>
-<br/>
-<font class="indexsub"/>
-</td>
-<td>
-<br/>
-</td>
-<td width="28%">
-<img height="86" width="120" src="../../../development/milestone_plans/stylesheets/images/Idea.jpe"/>
-</td>
-</tr>
-</table>
-<table border="1" width="100%">
-<tbody>
-<tr>
-<td/>
-<td width="20%"/>
-<td colspan="9">
-<b>
- milestone
- M4</b>
-</td>
-</tr>
-<tr>
-<td/>
-<td width="200"/>
-<td width="100">
-<b>Feb 28-Mar 4</b>
-</td>
-<td width="100">
-<b>Mar 7-11</b>
-</td>
-<td width="100">
-<b>Mar 14-18</b>
-</td>
-<td width="100">
-<b>Mar 21-25</b>
-</td>
-<td width="100">
-<b>Mar 28-Apr 1</b>
-</td>
-<td width="100">
-<b>Apr 4-8</b>
-</td>
-<td width="100">
-<b>Apr 11-15</b>
-</td>
-</tr>
-<tr>
-<td bgcolor="#0080c0" height="30" colspan="9">
-<b>
-<font color="#ffffff">ebelisar@ca.ibm.com
- (
- 15
- )
- </font>
-</b>
-</td>
-</tr>
-<tr>
-<td/>
-<td height="100">
-<ul>
-<img width="13" height="5" src="../../../development/milestone_plans/stylesheets/images/progress.gif"/>
- [xml]
- <description>Provide API for XML Catalog entry contributions via extension point</description>
- (2)
- </ul>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<p>
-<font size="1" color="red">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/default.gif"/>
-<font size="1" scolor="#999999">[complete]</font>
-</font>
-</p>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-</tr>
-<tr>
-<td/>
-<td height="100">
-<ul>
-<img width="13" height="5" src="../../../development/milestone_plans/stylesheets/images/progress.gif"/>
- [xml]
- <description>Investigate API requirements for XML Catalog model</description>
- (3)
- </ul>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<p>
-<font size="1" color="blue">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/default.gif"/>
-<font size="1" scolor="#999999">[complete]</font>
-</font>
-</p>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-</tr>
-<tr>
-<td/>
-<td height="100">
-<ul>
- [xml]
- <description>Support OASIS standard XML Catalog format</description>
- (10)
- </ul>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<p>
-<font size="1" color="black">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/default.gif"/>
-<font size="1" scolor="#999999">[complete]</font>
-</font>
-</p>
-</td>
-<td>
-<p>
-<font size="1" color="black">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/default.gif"/>
-<font size="1" scolor="#999999">[complete]</font>
-</font>
-</p>
-</td>
-<td>
-<font>.</font>
-</td>
-</tr>
-<tr>
-<td bgcolor="#0080c0" height="30" colspan="9">
-<b>
-<font color="#ffffff">kboo@ca.ibm.com
- (
- 17
- )
- </font>
-</b>
-</td>
-</tr>
-<tr>
-<td/>
-<td height="100">
-<ul>
- [wsdl]
- <description>Provide WSDL model API</description>
- (11)
- </ul>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<p>
-<font size="1" color="red">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/default.gif"/>
-<description>Provide core model API</description> (5)</font>
-</p>
-</td>
-<td>
-<p>
-<font size="1" color="red">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/default.gif"/>
-<description>Provide API/extension point for extensibility element models</description> (2)</font>
-</p>
-<p>
-<font size="1" color="red">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/default.gif"/>
-<description>Provide API for SOAP binding model for WSDL</description> (2)</font>
-</p>
-</td>
-<td>
-<p>
-<font size="1" color="red">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/default.gif"/>
-<description>Provide API for HTTP/MIME binding model for WSDL</description> (2)</font>
-</p>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-</tr>
-<tr>
-<td/>
-<td height="100">
-<ul>
- [wsdl]
- <description>Ensure complete JUnit test coverage for API</description>
- (6)
- </ul>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<p>
-<font size="1" color="red">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/default.gif"/>
-<font size="1" color="#999999"> [1/3 complete]</font>
-</font>
-</p>
-</td>
-<td>
-<p>
-<font size="1" color="red">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/default.gif"/>
-<font size="1" color="#999999"> [2/3 complete]</font>
-</font>
-</p>
-</td>
-<td>
-<p>
-<font size="1" color="red">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/default.gif"/>
-<font size="1" color="#999999">[complete]</font>
-</font>
-</p>
-</td>
-</tr>
-<tr>
-<td bgcolor="#0080c0" height="30" colspan="9">
-<b>
-<font color="#ffffff">kchong@ca.ibm.com
- (
- 6
- )
- </font>
-</b>
-</td>
-</tr>
-<tr>
-<td/>
-<td height="100">
-<ul>
- [xsd]
- <description>Support API for contributing menu items to XSD editor menus</description>
- (2)
- </ul>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<p>
-<font size="1" color="red">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/default.gif"/>
-<font size="1" scolor="#999999">[complete]</font>
-</font>
-</p>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-</tr>
-<tr>
-<td/>
-<td height="100">
-<ul>
- [xsd]
- <description>Plan/prototype API for specialized <i>annotation</i> editing views</description>
- (4)
- </ul>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<p>
-<font size="1" color="black">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/default.gif"/>
-<font size="1" scolor="#999999">[complete]</font>
-</font>
-</p>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-</tr>
-<tr>
-<td bgcolor="#0080c0" height="30" colspan="9">
-<b>
-<font color="#ffffff">lauzond@ca.ibm.com
- (
- 17
- )
- </font>
-</b>
-</td>
-</tr>
-<tr>
-<td/>
-<td height="100">
-<ul>
- [wsi]
- <description>Provide initial WSDL validator</description>
- (13)
- </ul>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<p>
-<font size="1" color="blue">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/default.gif"/>
-<description>migrate code from WSVT</description> (5)</font>
-</p>
-</td>
-<td>
-<p>
-<font size="1" color="blue">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/default.gif"/>
-<description>refactor code to provide WS-I validator as a WSDL validator extension</description> (8)<font color="#999999"> [1/2 complete]</font>
-</font>
-</p>
-</td>
-<td>
-<p>
-<font size="1" color="blue">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/default.gif"/>refactor code
- ...
- <font size="1" color="#999999">[complete]</font>
-</font>
-</p>
-</td>
-<td>
-<font>.</font>
-</td>
-</tr>
-<tr>
-<td/>
-<td height="100">
-<ul>
- [wsi]
- <description>Add JUnit tests for WSI validator</description>
- (4)
- </ul>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<p>
-<font size="1" color="blue">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/default.gif"/>
-<font size="1" scolor="#999999">[complete]</font>
-</font>
-</p>
-</td>
-<td>
-<font>.</font>
-</td>
-</tr>
-<tr>
-<td bgcolor="#0080c0" height="30" colspan="9">
-<b>
-<font color="#ffffff">lmandel@ca.ibm.com
- (
- 18
- )
- </font>
-</b>
-</td>
-</tr>
-<tr>
-<td/>
-<td height="100">
-<ul>
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/ok.gif"/>
- [wsdl]
- <description>Provide initial WSDL validator</description>
- (10)
- </ul>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<p>
-<font size="1" color="blue">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/ok.gif"/>
-<description>migrate code from WSVT</description> (5)</font>
-</p>
-</td>
-<td>
-<p>
-<font size="1" color="blue">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/ok.gif"/>
-<description>refactor code (if req'd) to support WS-I validation extensions</description> (5)</font>
-</p>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-</tr>
-<tr>
-<td/>
-<td height="100">
-<ul>
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/ok.gif"/>
- [wsdl]
- <description>Add JUnit tests for WSDL validator</description>
- (4)
- </ul>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<p>
-<font size="1" color="blue">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/ok.gif"/>
-<font size="1" scolor="#999999">[complete]</font>
-</font>
-</p>
-</td>
-<td>
-<font>.</font>
-</td>
-</tr>
-<tr>
-<td/>
-<td height="100">
-<ul>
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/ok.gif"/>
- [xsd]
- <description>Add JUnit tests for XSD validator</description>
- (4)
- </ul>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<p>
-<font size="1" color="blue">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/default.gif"/>
-<font size="1" scolor="#999999">[complete]</font>
-</font>
-</p>
-</td>
-<td>
-<font>.</font>
-</td>
-</tr>
-<tr>
-<td bgcolor="#0080c0" height="30" colspan="9">
-<b>
-<font color="#ffffff">mhutchin@ca.ibm.com
- (
- 7
- )
- </font>
-</b>
-</td>
-</tr>
-<tr>
-<td/>
-<td height="100">
-<ul>
-<img width="13" height="5" src="../../../development/milestone_plans/stylesheets/images/progress.gif"/>
- [wsdl]
- <description>Add squiggle support for WSDL validator</description>
- (7)
- </ul>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<p>
-<font size="1" color="black">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/ok.gif"/>
-<description>Provide squiggle support for WSDL validator</description> (3)</font>
-</p>
-<p>
-<font size="1" color="black">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/glass.gif"/>
-<description>Ensure squiggle strategies are designed in an easily reusable way</description> (2)</font>
-</p>
-</td>
-<td>
-<p>
-<font size="1" color="black">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/glass.gif"/>
-<description>Investigate how squiggle strategies would be provided by validator extensions</description> (2)</font>
-</p>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-</tr>
-<tr>
-<td bgcolor="#0080c0" height="30" colspan="9">
-<b>
-<font color="#ffffff">rmah@ca.ibm.com
- (
- 14
- )
- </font>
-</b>
-</td>
-</tr>
-<tr>
-<td/>
-<td height="100">
-<ul>
- [wsdl]
- <description>Provide API/extension points for UI(<i>investigate push down to xml.ui</i>)</description>
- (9)
- </ul>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<p>
-<font size="1" color="blue">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/default.gif"/>
-<description>customized icons</description> (3)</font>
-</p>
-</td>
-<td>
-<p>
-<font size="1" color="blue">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/default.gif"/>
-<description>customized cell editors</description> (3)</font>
-</p>
-</td>
-<td>
-<p>
-<font size="1" color="blue">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/default.gif"/>
-<description>guided editing filters (to narrow suggestions for 'any' elements)</description> (3)</font>
-</p>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-</tr>
-<tr>
-<td/>
-<td height="100">
-<ul>
- [wsdl]
- <description>Prototype extensible WSDL binding generator</description>
- (5)
- </ul>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<font>.</font>
-</td>
-<td>
-<p>
-<font size="1" color="black">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/default.gif"/>
-<font size="1" scolor="#999999">[complete]</font>
-</font>
-</p>
-</td>
-<td>
-<font>.</font>
-</td>
-</tr>
-</tbody>
-</table>
-<table border="0" width="100%" cellpadding="2" cellspacing="5">
-<tbody>
-<tr>
-<td colspan="4" bgcolor="#0080c0" width="100%" align="left" valign="top">
-<b>
-<font face="Arial,Helvetica">
-<font color="#ffffff">Legend</font>
-</font>
-</b>
-</td>
-</tr>
-<tr>
-<td valign="top">
-<img width="14" height="5" src="../../../development/milestone_plans/stylesheets/images/progress.gif"/>
-</td>
-<td width="50%">item is under development.</td>
-<td valign="top">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/glass.gif"/>
-</td>
-<td width="50%">item is under investigation.</td>
-</tr>
-<tr>
-<td valign="top">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/ok.gif"/>
-</td>
-<td width="50%">item is finished.</td>
-<td valign="top">
-<img width="40" height="12" src="../../../development/milestone_plans/stylesheets/images/help.gif"/>
-</td>
-<td width="50%">help wanted</td>
-</tr>
-<tr>
-<td valign="top">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/defer.gif"/>
-</td>
-<td width="50%">item is deferred.</td>
-<td valign="top">
-<font class="indexsub">
-<img src="../../../development/milestone_plans/stylesheets/images/new.gif"/>
-</font>
-</td>
-<td width="50%">new</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/development/milestone_plans/reports/report-calendar-by-developer.xml b/development/milestone_plans/reports/report-calendar-by-developer.xml
deleted file mode 100644
index 946d823..0000000
--- a/development/milestone_plans/reports/report-calendar-by-developer.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-<?xml-stylesheet type="text/xsl" href="../stylesheets/milestone-calendar.xsl"?>
-<report>
- <title>Example Team Plan</title>
- <description>An example of a team plan for WTP M3 development.</description>
- <milestoneDates location="../reports/milestoneDates.xml"/>
- <milestone name="M4"/>
- <plan location="../../../wst/components/xml/M4/milestone_plan.xml" />
- <plan location="../../../wst/components/xsd/M4/milestone_plan.xml" />
- <plan location="../../../wst/components/wsdl/M4/milestone_plan.xml" />
- <plan location="../../../wst/components/wsi/M4/milestone_plan.xml" />
- <developer name="ebelisar@ca.ibm.com"/>
- <developer name="kboo@ca.ibm.com"/>
- <developer name="kchong@ca.ibm.com"/>
- <developer name="lauzond@ca.ibm.com"/>
- <developer name="rmah@ca.ibm.com"/>
- <developer name="lmandel@ca.ibm.com"/>
- <developer name="mhutchin@ca.ibm.com"/>
-</report>
\ No newline at end of file
diff --git a/development/milestone_plans/reports/report-milestone-overview.html b/development/milestone_plans/reports/report-milestone-overview.html
deleted file mode 100644
index 3e64bd2..0000000
--- a/development/milestone_plans/reports/report-milestone-overview.html
+++ /dev/null
@@ -1,226 +0,0 @@
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
-<head>
-<title>Eclipse WTP 0.7 Milestone Plan (Development Overview)</title>
-<link rel="stylesheet" type="text/css" href="../stylesheets/images/default_style.css"/>
-</head>
-<body>
-<table border="0" width="100%" cellPadding="2" cellSpacing="5">
-<tr>
-<td>
-<font class="indextop">Eclipse WTP 0.7 Milestone Plan (Development Overview)</font>
-<br/>
-<font class="indexsub">the eclipse web tools platform project milestone contents</font>
-</td>
-<td>
-<br/>
-</td>
-<td width="28%">
-<img height="86" width="120" src="../../../development/milestone_plans/stylesheets/images/Idea.jpe"/>
-</td>
-</tr>
-</table>
-<table cellpadding="4" cellspacing="0" width="100%">
-<tr>
-<td colspan="2" bgcolor="#0080c0" height="20">
-<b>
-<font color="#ffffff">Status of this document</font>
-</b>
-</td>
-</tr>
-<tr>
-<td colspan="2">This is the final plan.</td>
-</tr>
-<tr>
-<td width="3%" vAlign="top">
-<p align="right">
-<img alt="" name="Image2" border="0" align="bottom" width="16" src="../stylesheets/images/Adarrow.gif" height="16"/>
-</p>
-</td>
-<td width="97%">
-<p>
-<a href="#M0">
-<b>M0</b>
-</a>
-<br><contentDescription>Initial CVS module structure, build infrastructure, and Server Tools.</contentDescription>
-</br>
-</p>
-</td>
-</tr>
-<tr>
-<td width="3%" vAlign="top">
-<p align="right">
-<img alt="" name="Image2" border="0" align="bottom" width="16" src="../stylesheets/images/Adarrow.gif" height="16"/>
-</p>
-</td>
-<td width="97%">
-<p>
-<a href="#M1">
-<b>M1</b>
-</a>
- -
- <statusDescription>October 15, 2004</statusDescription>
-<br>
-<contentDescription>Flexible project layout. Initial XML, JSP and EJB Tools.</contentDescription>
-</br>
-</p>
-</td>
-</tr>
-<tr>
-<td width="3%" vAlign="top">
-<p align="right">
-<img alt="" name="Image2" border="0" align="bottom" width="16" src="../stylesheets/images/Adarrow.gif" height="16"/>
-</p>
-</td>
-<td width="97%">
-<p>
-<a href="#M2">
-<b>M2</b>
-</a>
- -
- <statusDescription>December 22, 2004</statusDescription>
-<br>
-<contentDescription>Initial J2EE and Structured Source Editing tools. Based on 3.1M4.</contentDescription>
-</br>
-</p>
-</td>
-</tr>
-<tr>
-<td width="3%" vAlign="top">
-<p align="right">
-<img alt="" name="Image2" border="0" align="bottom" width="16" src="../stylesheets/images/Adarrow.gif" height="16"/>
-</p>
-</td>
-<td width="97%">
-<p>
-<a href="#M3">
-<b>M3</b>
-</a>
- -
- <statusDescription>February 25, 2005</statusDescription>
-<br>
-<contentDescription>Improved XML, JSP and EJB Tools. Database Tools and Initial Web Services. Will be based on 3.1M5.</contentDescription>
-</br>
-</p>
-</td>
-</tr>
-<tr>
-<td width="3%" vAlign="top">
-<p align="right">
-<img alt="" name="Image2" border="0" align="bottom" width="16" src="../stylesheets/images/Adarrow.gif" height="16"/>
-</p>
-</td>
-<td width="97%">
-<p>
-<a href="#M4">
-<b>M4</b>
-</a>
- -
- <statusDescription>April 29, 2005</statusDescription>
-<br>
-<contentDescription>WTP 0.7 API Definition Complete. Based on Eclipse 3.1 M6</contentDescription>
-</br>
-</p>
-</td>
-</tr>
-<tr>
-<td width="3%" vAlign="top">
-<p align="right">
-<img alt="" name="Image2" border="0" align="bottom" width="16" src="../stylesheets/images/Adarrow.gif" height="16"/>
-</p>
-</td>
-<td width="97%">
-<p>
-<a href="#M5">
-<b>M5</b>
-</a>
- -
- <statusDescription>July 1, 2005</statusDescription>
-<br>
-<contentDescription>WTP 0.7 API Implementation Complete. Based on Eclipse 3.1 M7</contentDescription>
-</br>
-</p>
-</td>
-</tr>
-<tr>
-<td width="3%" vAlign="top">
-<p align="right">
-<img alt="" name="Image2" border="0" align="bottom" width="16" src="../stylesheets/images/Adarrow.gif" height="16"/>
-</p>
-</td>
-<td width="97%">
-<p>
-<a href="#M6-Endgame">
-<b>M6</b>
-</a>
- -
- <statusDescription>July 29, 2005</statusDescription>
-<br>
-<contentDescription>WTP 0.7. Stabilization, final bug fixes. Based on Eclipse 3.1 Release</contentDescription>
-</br>
-</p>
-</td>
-</tr>
-</table>
-<br/>
-<br/>
-<table border="0" width="100%" cellpadding="2" cellspacing="5">
-<tbody>
-<tr>
-<td colspan="4" bgcolor="#0080c0" width="100%" align="left" valign="top">
-<b>
-<font face="Arial,Helvetica">
-<font color="#ffffff">Legend</font>
-</font>
-</b>
-</td>
-</tr>
-<tr>
-<td valign="top">
-<img width="14" height="5" src="../../../development/milestone_plans/stylesheets/images/progress.gif"/>
-</td>
-<td width="50%">item is under development.</td>
-<td valign="top">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/glass.gif"/>
-</td>
-<td width="50%">item is under investigation.</td>
-</tr>
-<tr>
-<td valign="top">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/ok.gif"/>
-</td>
-<td width="50%">item is finished.</td>
-<td valign="top">
-<img width="40" height="12" src="../../../development/milestone_plans/stylesheets/images/help.gif"/>
-</td>
-<td width="50%">help wanted</td>
-</tr>
-<tr>
-<td valign="top">
-<img width="10" height="10" src="../../../development/milestone_plans/stylesheets/images/defer.gif"/>
-</td>
-<td width="50%">item is deferred.</td>
-<td valign="top">
-<font class="indexsub">
-<img src="../../../development/milestone_plans/stylesheets/images/new.gif"/>
-</font>
-</td>
-<td width="50%">new</td>
-</tr>
-</tbody>
-</table>
-<br/>
-<br/>
-<br/>
-<p>
- Please see our
- <a href="http://eclipse.org/legal/privacy.html">privacy policy</a>
- and website
- <a href="http://eclipse.org/legal/termsofuse.html">terms of use</a>
- . For problems with the eclipse.org site, please contact the
- <a href="mailto:webmaster@eclipse.org">webmaster</a>
- or read the
- <a href="http://eclipse.org/webmaster/index.html">webmaster FAQ</a>
- for answers to common questions!
- </p>
-</body>
-</html>
diff --git a/development/milestone_plans/reports/report-milestone-overview.xml b/development/milestone_plans/reports/report-milestone-overview.xml
deleted file mode 100644
index ffe914c..0000000
--- a/development/milestone_plans/reports/report-milestone-overview.xml
+++ /dev/null
@@ -1,88 +0,0 @@
-<?xml-stylesheet type="text/xsl" href="../stylesheets/milestone-overview.xsl"?>
-<report current-milestone="1.0M8">
- <title>Eclipse WTP 0.7 Milestone Plan (Development Overview)</title>
- <description>the eclipse web tools platform project milestone contents</description>
- <status>This is the final plan.</status>
- <milestone name="M0">
- <description>M0</description>
- <contentDescription>Initial CVS module structure, build infrastructure, and Server Tools.</contentDescription>
- </milestone>
- <milestone name="M1">
- <description>M1</description>
- <statusDescription>October 15, 2004</statusDescription>
- <contentDescription>Flexible project layout. Initial XML, JSP and EJB Tools.</contentDescription>
- </milestone>
- <milestone name="M2">
- <description>M2</description>
- <statusDescription>December 22, 2004</statusDescription>
- <contentDescription>Initial J2EE and Structured Source Editing tools. Based on 3.1M4.</contentDescription>
- <plan location="../../../wst/components/sse/M2/Milestone 2 Source Editing Plan.xml" />
- <plan location="../../../jst/components/j2ee/M2/milestone_plan.xml" />
- </milestone>
- <milestone name="M3">
- <description>M3</description>
- <statusDescription>February 25, 2005</statusDescription>
- <contentDescription>Improved XML, JSP and EJB Tools. Database Tools and Initial Web Services. Will be based on 3.1M5.</contentDescription>
- <plan location="../../../wst/components/css/M3/milestone_plan.xml" />
- <plan location="../../../wst/components/dtd/M3/milestone_plan.xml" />
- <plan location="../../../wst/components/html/M3/milestone_plan.xml" />
- <plan location="../../../wst/components/internet/M3/milestone_plan.xml" />
- <plan location="../../../wst/components/javascript/M3/milestone_plan.xml" />
- <plan location="../../../wst/components/rdb/M3/milestone_plan.xml" />
- <plan location="../../../wst/components/server/M3/milestone_plan.xml" />
- <plan location="../../../wst/components/sse/M3/milestone_plan.xml" />
- <plan location="../../../wst/components/wsdl/M3/milestone_plan.xml" />
- <plan location="../../../wst/components/wsi/M3/milestone_plan.xml" />
- <plan location="../../../wst/components/xml/M3/milestone_plan.xml" />
- <plan location="../../../wst/components/xsd/M3/milestone_plan.xml" />
- <plan location="../../../wst/components/ws/M3/milestone_plan.xml" />
- <plan location="../../../wst/components/command/M3/milestone_plan.xml" />
- <plan location="../../../jst/components/jsp/M3/milestone_plan.xml" />
- <plan location="../../../jst/components/server/M3/milestone_plan.xml" />
- <plan location="../../../jst/components/j2ee/M3/milestone_plan.xml" />
- <plan location="../../../jst/components/ws/M3/milestone_plan.xml" />
- </milestone>
- <milestone name="M4">
- <description>M4</description>
- <statusDescription>April 29, 2005</statusDescription>
- <contentDescription>WTP 0.7 API Definition Complete. Based on Eclipse 3.1 M6</contentDescription>
- <plan location="../../../wst/components/css/M4/milestone_plan.xml" />
- <plan location="../../../wst/components/dtd/M4/milestone_plan.xml" />
- <plan location="../../../wst/components/html/M4/milestone_plan.xml" />
- <plan location="../../../wst/components/internet/M4/milestone_plan.xml" />
- <plan location="../../../wst/components/javascript/M4/milestone_plan.xml" />
- <!-- <plan location="../../../wst/components/rdb/M4/milestone_plan.xml" /> -->
- <plan location="../../../wst/components/server/M4/milestone_plan.xml" />
- <plan location="../../../wst/components/sse/M4/milestone_plan.xml" />
- <plan location="../../../wst/components/wsdl/M4/milestone_plan.xml" />
- <plan location="../../../wst/components/wsi/M4/milestone_plan.xml" />
- <plan location="../../../wst/components/xml/M4/milestone_plan.xml" />
- <plan location="../../../wst/components/xsd/M4/milestone_plan.xml" />
- <plan location="../../../wst/components/ws/M4/milestone_plan.xml" />
- <plan location="../../../wst/components/command/M4/milestone_plan.xml" />
- <plan location="../../../jst/components/jsp/M4/milestone_plan.xml" />
- <plan location="../../../jst/components/server/M4/milestone_plan.xml" />
- <plan location="../../../jst/components/j2ee/M4/milestone_plan.xml" />
- <plan location="../../../jst/components/ws/M4/milestone_plan.xml" />
- </milestone>
- <milestone name="M5">
- <description>M5</description>
- <statusDescription>July 1, 2005</statusDescription>
- <contentDescription>WTP 0.7 API Implementation Complete. Based on Eclipse 3.1 M7</contentDescription>
- <plan location="../../../jst/components/ws/M5/milestone_plan.xml"/>
- <plan location="../../../wst/components/command/M5/milestone_plan.xml"/>
- <plan location="../../../wst/components/css/M5/milestone_plan.xml"/>
- <plan location="../../../wst/components/dtd/M5/milestone_plan.xml"/>
- <plan location="../../../wst/components/html/M5/milestone_plan.xml"/>
- <plan location="../../../wst/components/javascript/M5/milestone_plan.xml"/>
- <plan location="../../../wst/components/sse/M5/milestone_plan.xml"/>
- <plan location="../../../wst/components/ws/M5/milestone_plan.xml"/>
- <plan location="../../../wst/components/xml/M5/milestone_plan.xml"/>
- <plan location="../../../jst/components/j2ee/M5/milestone_plan.xml" />
- </milestone>
- <milestone name="M6-Endgame">
- <description>M6</description>
- <statusDescription>July 29, 2005</statusDescription>
- <contentDescription>WTP 0.7. Stabilization, final bug fixes. Based on Eclipse 3.1 Release</contentDescription>
- </milestone>
-</report>
\ No newline at end of file
diff --git a/development/milestone_plans/stylesheets/help-wanted.xsl b/development/milestone_plans/stylesheets/help-wanted.xsl
deleted file mode 100644
index 14cb3ea..0000000
--- a/development/milestone_plans/stylesheets/help-wanted.xsl
+++ /dev/null
@@ -1,211 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!--
-
- Generates Help Wanted page from Milestone plans.
-
- ChangeLog:
-
- 2005-02-13: Arthur Ryman, ryman@ca.ibm.com
- - cloned from milestone-overview.xsl
--->
-
-<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.w3.org/1999/xhtml">
- <xsl:output method="html" encoding="UTF-8" />
- <xsl:include href="../stylesheets/milestone-common.xsl" />
- <xsl:variable name="plans" select="document(/report/milestone/plan/@location)/plan" />
- <xsl:variable name="rel" select="'../../../'" />
- <xsl:variable name="title" select="'eclipse WTP help wanted'" />
- <xsl:template match="report">
- <html>
- <head>
- <title>
- <xsl:value-of select="$title" />
- </title>
- <link href="../stylesheets/images/default_style.css" type="text/css" rel="stylesheet" />
- </head>
- <body>
-
- <xsl:call-template name="printHeader">
- <xsl:with-param name="rel" select="$rel" />
- <xsl:with-param name="title" select="$title" />
- <xsl:with-param name="description" select="'eclipse web tools platform project help wanted'" />
- </xsl:call-template>
-
- <table width="100%">
- <tr>
- <td height="20" bgcolor="#0080c0" colspan="2">
- <b>
- <font color="#ffffff">Help Wanted</font>
- </b>
- </td>
- </tr>
- <tr>
- <td colspan="2">
- Like all Open Source projects, WTP depends on an active community of contributors to accomplish its goals.
- This page lists work items where help is needed.
- If you'd like to contribute, please review this page to find a task that matches your interests and skills,
- then send a note to <a href="mailto:wtp-dev@eclipse.org">wtp-dev@eclipse.org</a> volunteering your assistance.
- The responsible component lead will contact you to coordinate your work.
- </td>
- </tr>
-
- </table>
-
- <br />
-
- <table width="100%">
- <tr>
- <td>
- <img>
- <xsl:attribute name="src">
- <xsl:value-of select="concat($rel, 'development/milestone_plans/stylesheets/images/new.gif')" />
- </xsl:attribute>
- </img>
- You can also see the list of help wanted bugs <a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=priority&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=helpwanted&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by priority</a> and
- <a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=helpwanted&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=">by severity</a>
- </td>
- </tr>
- </table>
-
- <br />
-
- <table width="100%">
- <tr align="left">
- <th>Yes, I'll Help!</th>
- <th>Milestone</th>
- <th>Priority</th>
- <th>Subproject</th>
- <th>Component</th>
- <th>Category</th>
- <th>Description</th>
- </tr>
- <xsl:for-each select="document(/report/milestone[substring(@name, 5) >= substring(/report/@current-milestone, 5)]/plan/@location)/plan/component/milestone/category/item[@helpWanted='true']">
- <xsl:sort data-type="number" select="ancestor::milestone/@name" />
- <xsl:sort select="translate(substring(@priority,1,1),'hml','123')" />
- <xsl:sort select="ancestor::component/@subproject" />
- <xsl:sort select="ancestor::component/@name" />
- <xsl:sort select="ancestor::category/@name" />
-
- <xsl:variable name="milestoneName" select="ancestor::component/milestone[1]/@name" />
- <xsl:variable name="component" select="ancestor::component" />
- <xsl:variable name="url" select="concat($rel, $component/@subproject, '/components/', $component/@name, '/', $milestoneName, '/', 'milestone_plan.html')" />
-
- <xsl:variable name="subject">
- <xsl:text>[Help Wanted] </xsl:text>
- <xsl:value-of select="ancestor::milestone/@name" />
- <xsl:text> </xsl:text>
- <xsl:value-of select="ancestor::component/@subproject" />
- <xsl:text>.</xsl:text>
- <xsl:value-of select="ancestor::component/@name" />
- <xsl:text>: </xsl:text>
- <xsl:value-of select="ancestor::category/@name" />
- </xsl:variable>
- <xsl:variable name="url-encoded-subject">
- <xsl:call-template name="url-encode">
- <xsl:with-param name="s" select="$subject" />
- </xsl:call-template>
- </xsl:variable>
-
- <xsl:variable name="body">
- <xsl:text>I'd like to help with the item: </xsl:text>
- <xsl:value-of select="description" />
- </xsl:variable>
- <xsl:variable name="url-encoded-body">
- <xsl:call-template name="url-encode">
- <xsl:with-param name="s" select="$body" />
- </xsl:call-template>
- </xsl:variable>
-
- <!-- TODO: would be nice if this could read the developer element for contact info -->
- <xsl:variable name="mailto-url">
- <xsl:text>mailto:wtp-dev@eclipse.org?subject=</xsl:text>
- <xsl:value-of select="$url-encoded-subject" />
- <xsl:text>&body=</xsl:text>
- <xsl:value-of select="$url-encoded-body" />
- </xsl:variable>
-
- <tr>
- <td><a href="{$mailto-url}">Send</a></td>
- <td><xsl:value-of select="ancestor::milestone/@name" /></td>
- <td><xsl:value-of select="@priority" /></td>
- <td><xsl:value-of select="ancestor::component/@subproject" /></td>
-
- <td>
- <a href="{$url}">
- <xsl:value-of select="$component/@name" />
- </a>
- </td>
-
- <td><xsl:value-of select="../@name" /></td>
-
- <td>
- <xsl:call-template name="drawStatus">
- <xsl:with-param name="rel" select="$rel" />
- <xsl:with-param name="value" select="@status" />
- <xsl:with-param name="defaultImage" select="'default.gif'" />
- </xsl:call-template>
- <xsl:text>  </xsl:text>
- <xsl:value-of select="description" />
- <xsl:value-of select="' '" />
- <xsl:call-template name="drawHelpWanted">
- <xsl:with-param name="rel" select="$rel" />
- </xsl:call-template>
-
- </td>
- </tr>
- </xsl:for-each>
- </table>
-
- <br />
- <br />
- <xsl:call-template name="printLegend">
- <xsl:with-param name="rel" select="$rel" />
- </xsl:call-template>
- <br />
- <br />
- <br />
- <p>
- Please see our
- <a href="http://eclipse.org/legal/privacy.html">privacy policy</a>
- and website
- <a href="http://eclipse.org/legal/termsofuse.html">terms of use</a>
- . For problems with the eclipse.org site, please contact the
- <a href="mailto:webmaster@eclipse.org">webmaster</a>
- or read the
- <a href="http://eclipse.org/webmaster/index.html">webmaster FAQ</a>
- for answers to common questions!
- </p>
- </body>
- </html>
- </xsl:template>
-
- <!-- URL encodes a string by replacing unsafe characters with %dd where dd is the hex for the character. -->
- <xsl:template name="url-encode">
- <xsl:param name="s" />
- <xsl:if test="string-length($s) > 0">
- <xsl:variable name="c" select="substring($s, 1, 1)" />
- <xsl:choose>
- <xsl:when test="$c = ' '">
- <xsl:text>%20</xsl:text>
- </xsl:when>
- <xsl:when test="$c = '%'">
- <xsl:text>%25</xsl:text>
- </xsl:when>
- <xsl:when test="$c = '&'">
- <xsl:text>%26</xsl:text>
- </xsl:when>
- <xsl:when test="$c = '?'">
- <xsl:text>%3F</xsl:text>
- </xsl:when>
- <xsl:otherwise>
- <xsl:value-of select="$c" />
- </xsl:otherwise>
- </xsl:choose>
- <xsl:call-template name="url-encode">
- <xsl:with-param name="s" select="substring($s, 2)" />
- </xsl:call-template>
- </xsl:if>
- </xsl:template>
-
-</xsl:stylesheet>
\ No newline at end of file
diff --git a/development/milestone_plans/stylesheets/images/Adarrow.gif b/development/milestone_plans/stylesheets/images/Adarrow.gif
deleted file mode 100644
index 1848247..0000000
--- a/development/milestone_plans/stylesheets/images/Adarrow.gif
+++ /dev/null
Binary files differ
diff --git a/development/milestone_plans/stylesheets/images/Idea.jpe b/development/milestone_plans/stylesheets/images/Idea.jpe
deleted file mode 100644
index 119ce70..0000000
--- a/development/milestone_plans/stylesheets/images/Idea.jpe
+++ /dev/null
Binary files differ
diff --git a/development/milestone_plans/stylesheets/images/default.gif b/development/milestone_plans/stylesheets/images/default.gif
deleted file mode 100644
index f3251c3..0000000
--- a/development/milestone_plans/stylesheets/images/default.gif
+++ /dev/null
Binary files differ
diff --git a/development/milestone_plans/stylesheets/images/default_style.css b/development/milestone_plans/stylesheets/images/default_style.css
deleted file mode 100644
index f2fe2fa..0000000
--- a/development/milestone_plans/stylesheets/images/default_style.css
+++ /dev/null
@@ -1,42 +0,0 @@
-P {
- FONT-SIZE: 10pt; FONT-FAMILY: arial, helvetica, geneva
-}
-TABLE {
- FONT-SIZE: 10pt; FONT-FAMILY: arial, helvetica, geneva
-}
-TD {
- FONT-SIZE: 10pt; FONT-FAMILY: arial, helvetica, geneva
-}
-TH {
- FONT-SIZE: 10pt; FONT-FAMILY: arial, helvetica, geneva
-}
-PRE {
- FONT-SIZE: 10pt; FONT-FAMILY: "Courier New", Courier, mono
-}
-H2 {
- FONT-WEIGHT: bold; FONT-SIZE: 18pt; LINE-HEIGHT: 14px; FONT-FAMILY: arial, helvetica, geneva
-}
-CODE {
- FONT-SIZE: 10pt; FONT-FAMILY: "Courier New", Courier, mono
-}
-SUP {
- FONT-SIZE: 10px; FONT-FAMILY: arial,helvetica,geneva
-}
-H3 {
- FONT-WEIGHT: bold; FONT-SIZE: 14pt; FONT-FAMILY: arial, helvetica, geneva
-}
-LI {
- FONT-SIZE: 10pt; FONT-FAMILY: arial, helvetica, geneva
-}
-H1 {
- FONT-WEIGHT: bold; FONT-SIZE: 28px; FONT-FAMILY: arial, helvetica, geneva
-}
-BODY {
- MARGIN-TOP: 5mm; FONT-SIZE: 10pt; MARGIN-LEFT: 3mm; FONT-FAMILY: arial, helvetica, geneva
-}
-.indextop {
- FONT-WEIGHT: bold; FONT-SIZE: x-large; FONT-FAMILY: Verdana, Arial, Helvetica, sans-serif
-}
-.indexsub {
- FONT-SIZE: xx-small; COLOR: #8080ff; FONT-FAMILY: Arial, Helvetica, sans-serif
-}
diff --git a/development/milestone_plans/stylesheets/images/defer.gif b/development/milestone_plans/stylesheets/images/defer.gif
deleted file mode 100644
index de15c78..0000000
--- a/development/milestone_plans/stylesheets/images/defer.gif
+++ /dev/null
Binary files differ
diff --git a/development/milestone_plans/stylesheets/images/detail.gif b/development/milestone_plans/stylesheets/images/detail.gif
deleted file mode 100644
index 96bf7c0..0000000
--- a/development/milestone_plans/stylesheets/images/detail.gif
+++ /dev/null
Binary files differ
diff --git a/development/milestone_plans/stylesheets/images/glass.gif b/development/milestone_plans/stylesheets/images/glass.gif
deleted file mode 100644
index 2ebf26f..0000000
--- a/development/milestone_plans/stylesheets/images/glass.gif
+++ /dev/null
Binary files differ
diff --git a/development/milestone_plans/stylesheets/images/help.gif b/development/milestone_plans/stylesheets/images/help.gif
deleted file mode 100644
index 138ba15..0000000
--- a/development/milestone_plans/stylesheets/images/help.gif
+++ /dev/null
Binary files differ
diff --git a/development/milestone_plans/stylesheets/images/new.gif b/development/milestone_plans/stylesheets/images/new.gif
deleted file mode 100644
index c406057..0000000
--- a/development/milestone_plans/stylesheets/images/new.gif
+++ /dev/null
Binary files differ
diff --git a/development/milestone_plans/stylesheets/images/ok.gif b/development/milestone_plans/stylesheets/images/ok.gif
deleted file mode 100644
index 689e523..0000000
--- a/development/milestone_plans/stylesheets/images/ok.gif
+++ /dev/null
Binary files differ
diff --git a/development/milestone_plans/stylesheets/images/progress.gif b/development/milestone_plans/stylesheets/images/progress.gif
deleted file mode 100644
index bb7a15f..0000000
--- a/development/milestone_plans/stylesheets/images/progress.gif
+++ /dev/null
Binary files differ
diff --git a/development/milestone_plans/stylesheets/milestone-bulletList.xsl b/development/milestone_plans/stylesheets/milestone-bulletList.xsl
deleted file mode 100644
index 321ddca..0000000
--- a/development/milestone_plans/stylesheets/milestone-bulletList.xsl
+++ /dev/null
@@ -1,184 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!--
-
- ChangeLog:
-
- 2005-02-24 Phil Avery, pavery@us.ibm.com
- - added 'onmouseover' and 'onmouseout' actions
- to display 'detail' info in a new window
-
--->
-
-<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xalan="http://xml.apache.org/xslt" xmlns="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <xsl:output method="html" encoding="UTF-8" />
- <xsl:include href="milestone-common.xsl" />
- <xsl:variable name="rel" select="'../../../../'"/>
- <xsl:template match="/">
- <html>
- <head>
- <xsl:variable name="component" select="/plan/component[1]" />
- <title><xsl:value-of select="concat($component/@name, ' ', $component/milestone[1]/@name, ' milestone plan')" /></title>
- <link href="../../../../development/milestone_plans/stylesheets/images/default_style.css" type="text/css" rel="stylesheet" />
- <script type="text/javascript" src="../../../../popup.js">
- // script is linked
- </script>
- </head>
- <body>
- <xsl:for-each select="//component">
- <xsl:sort select="@name" />
- <xsl:apply-templates select="." />
- </xsl:for-each>
- <br />
- </body>
- </html>
- </xsl:template>
-
-
- <xsl:template match="component">
- <table cellSpacing="5" cellPadding="2" width="100%" border="0">
- <tr>
- <td>
- <font class="indextop">
- <xsl:value-of select="concat(@name, ' ', milestone[1]/@name)" />
- </font>
- <br />
- <font class="indexsub">
- <xsl:value-of select="description" />
- </font>
- </td>
- <td>
- <br />
- </td>
- <td width="28%">
- <img src="../../../../development/milestone_plans/stylesheets/images/Idea.jpe" width="120" height="86" />
- </td>
- </tr>
- </table>
-
-
- <!-- in this case print the Legend after the first milestone -->
- <!-- and then print the rest of the milestones -->
- <xsl:apply-templates select="//milestone[1]" />
- <xsl:call-template name="printLegend">
- <xsl:with-param name="rel" select="$rel"/>
- </xsl:call-template>
- <xsl:for-each select="//milestone[position() > 1]">
- <xsl:sort select="@name" />
- <xsl:apply-templates select="." />
- </xsl:for-each>
-
- </xsl:template>
-
- <xsl:template match="milestone">
- <table cellSpacing="5" cellPadding="2" width="100%" border="0">
- <tr>
- <a name="Overall_Planning">
- <td valign="top" align="left" width="100%" bgColor="#0080c0" colSpan="2" rowspan="3">
- <b>
- <font face="Arial,Helvetica">
- <font color="#ffffff">
- <xsl:copy-of select="title/text()" />
- </font>
- </font>
- </b>
- </td>
- </a>
- </tr>
- </table>
- <table cellspacing="5" width="100%">
- <tr>
- <td>
- <xsl:copy-of select="description" />
- </td>
- </tr>
- </table>
- <xsl:for-each select=".//category">
- <!-- <xsl:sort select="@name" /> -->
- <xsl:apply-templates select="." />
- </xsl:for-each>
- </xsl:template>
-
- <xsl:template match="category">
- <tr>
- <td>
- <table>
- <tr>
- <td valign="top">
- <img src="../../../../development/milestone_plans/stylesheets/images/Adarrow.gif" nosave="" border="0" height="16" />
- </td>
- <td>
- <b>
- <xsl:value-of select="@name" />
- </b>
- <ul>
- <xsl:apply-templates select="*" />
- </ul>
- </td>
- </tr>
- </table>
- </td>
- </tr>
- </xsl:template>
-
-
- <xsl:template match="item">
- <li>
- <xsl:call-template name="drawStatus">
- <xsl:with-param name="rel" select="$rel"/>
- <xsl:with-param name="value" select="@status" />
- </xsl:call-template>
- <xsl:if test="@bug">
- <xsl:call-template name="drawBug">
- <xsl:with-param name="bug" select="@bug"/>
- </xsl:call-template>
- </xsl:if>
- <xsl:copy-of select="description" />
- <xsl:if test="@priority">
- <font color="8080FF">
- <xsl:value-of select="concat(' [',@priority,']')"/>
- </font>
- </xsl:if>
- <xsl:if test="detail">
- <xsl:call-template name="drawDetail">
- <xsl:with-param name="detail" select="detail" />
- <xsl:with-param name="rel" select="$rel" />
- </xsl:call-template>
- </xsl:if>
- <xsl:if test="@helpWanted">
- <xsl:call-template name="drawHelpWanted">
- <xsl:with-param name="rel" select="$rel" />
- </xsl:call-template>
- </xsl:if>
- <xsl:if test="/plan/@scheduleInfo">
- <font color="C1C1C1">
- <xsl:choose>
- <xsl:when test="developer/@name">
- (
- <xsl:value-of select="developer/@name" />
- )
- </xsl:when>
- <xsl:otherwise>(unassigned)</xsl:otherwise>
- </xsl:choose>
- </font>
- </xsl:if>
- </li>
- <xsl:if test="step/description">
- <ul>
- <xsl:apply-templates select="step" />
- </ul>
- </xsl:if>
- </xsl:template>
-
-
- <xsl:template match="step">
- <li>
- <xsl:call-template name="drawStatus">
- <xsl:with-param name="rel" select="$rel" />
- <xsl:with-param name="value" select="@status" />
- </xsl:call-template>
- <xsl:copy-of select="description" />
- </li>
- </xsl:template>
-
-</xsl:stylesheet>
diff --git a/development/milestone_plans/stylesheets/milestone-calendar.xsl b/development/milestone_plans/stylesheets/milestone-calendar.xsl
deleted file mode 100644
index bfa887e..0000000
--- a/development/milestone_plans/stylesheets/milestone-calendar.xsl
+++ /dev/null
@@ -1,235 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xalan="http://xml.apache.org/xslt" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.w3.org/1999/xhtml">
- <xsl:output method="html" encoding="UTF-8" />
- <xsl:include href="../stylesheets/milestone-common.xsl" />
- <xsl:variable name="datesDocument" select="/report/milestoneDates/@location" />
- <xsl:variable name="targetMilestone" select="/report/milestone/@name" />
- <xsl:variable name="milestoneDates" select="document($datesDocument)//milestone[@name = $targetMilestone]" />
- <xsl:variable name="weeks" select="$milestoneDates//week" />
- <xsl:variable name="plans" select="document(/report/plan/@location)/plan" />
- <xsl:variable name="developers" select="/report/developer" />
- <xsl:variable name="rel" select="'../../../'" />
-
- <xsl:template match="report">
- <html>
- <head>
- <title>Milestone Plan - Calendar View</title>
- <link href="../stylesheets/images/default_style.css" type="text/css" rel="stylesheet" />
- </head>
- <body>
-
- <xsl:call-template name="printHeader">
- <xsl:with-param name="rel" select="$rel"></xsl:with-param>
- <xsl:with-param name="title" select="/report/title" />
- <xsl:with-param name="description" select="/report/desrcription" />
- </xsl:call-template>
-
- <table border="1">
- <xsl:attribute name="width">
- <xsl:value-of select="concat(count(/report/milestone) * 100, '%')" />
- </xsl:attribute>
- <tbody>
- <tr>
- <td></td>
- <td width="20%"></td>
- <xsl:for-each select="$milestoneDates">
- <td>
- <xsl:attribute name="colspan">
- <xsl:value-of select="count(week) + 2" />
- </xsl:attribute>
- <b>
- milestone
- <xsl:value-of select="@name" />
- </b>
- </td>
- </xsl:for-each>
- </tr>
- <tr>
- <td></td>
- <td width="200"></td>
- <xsl:for-each select="$weeks">
- <td width="100">
- <b>
- <xsl:value-of select="@date" />
- </b>
- </td>
- </xsl:for-each>
- </tr>
- <xsl:call-template name="generateRowsForDevelopers" />
- </tbody>
- </table>
- <xsl:call-template name="printLegend">
- <xsl:with-param name="rel" select="$rel" />
- </xsl:call-template>
- </body>
- </html>
- </xsl:template>
-
- <xsl:template name="generateRowsForDevelopers">
- <xsl:for-each select="$developers">
- <xsl:sort select="@name" />
- <xsl:variable name="theName" select="@name"></xsl:variable>
- <xsl:variable name="items" select="$plans//item[developer/@name = $theName][ancestor::milestone/@name = $targetMilestone]" />
- <tr>
- <td height="30" bgcolor="#0080c0">
- <xsl:attribute name="colspan">
- <xsl:value-of select="count($weeks) + 2" />
- </xsl:attribute>
- <b>
- <font color="#ffffff">
- <xsl:value-of select="@name" />
- (
- <xsl:value-of select="sum($items//@pds)" />
- )
- </font>
- </b>
- </td>
- </tr>
- <xsl:choose>
- <xsl:when test="count($items) > 0">
- <xsl:apply-templates select="$items">
- <xsl:with-param name="developerName" select="$theName"></xsl:with-param>
- <xsl:sort select="ancestor::milestone/@name" />
- </xsl:apply-templates>
- </xsl:when>
- <xsl:otherwise>
- <tr>
- <td></td>
- <td>
- <xsl:attribute name="colspan">
- <xsl:value-of select="count($weeks) + 2" />
- </xsl:attribute>
- no items
- </td>
- </tr>
- </xsl:otherwise>
- </xsl:choose>
- </xsl:for-each>
- </xsl:template>
-
- <xsl:template match="item">
- <xsl:param name="developerName"></xsl:param>
- <tr>
- <td />
- <xsl:variable name="theItem" select="."></xsl:variable>
- <td height="100">
- <ul>
- <xsl:call-template name="drawStatus">
- <xsl:with-param name="rel" select="$rel"></xsl:with-param>
- <xsl:with-param name="value" select="$theItem/@status" />
- </xsl:call-template>
- <xsl:value-of select="' '" />
- [<xsl:value-of select="ancestor::component/@name" />]
- <xsl:copy-of select="description" />
- (<xsl:value-of select="sum($theItem//@pds)" />)
- </ul>
- </td>
-
- <xsl:for-each select="$milestoneDates">
- <xsl:variable name="milestoneName" select="@name" />
- <xsl:choose>
- <xsl:when test="$theItem/ancestor::milestone/@name = $milestoneName">
- <xsl:for-each select="week">
- <td>
- <xsl:variable name="p" select="position()" />
- <xsl:variable name="steps" select="$theItem/step[not(developer)] | $theItem/step[developer/@name = $developerName]" />
- <xsl:variable name="newSteps" select="$steps[@start = $p]" />
- <xsl:variable name="oldSteps" select="$steps[@length][@start < $p][@start + @length > $p]" />
- <xsl:for-each select="$newSteps">
- <p>
- <xsl:if test="@start = $p">
- <font size="1">
- <xsl:call-template name="setFontColorForStep">
- <xsl:with-param name="step" select="."></xsl:with-param>
- </xsl:call-template>
- <xsl:call-template name="drawStatus">
- <xsl:with-param name="rel" select="$rel" />
- <xsl:with-param name="value" select="@status" />
- <xsl:with-param name="defaultImage" select="'default.gif'" />
- </xsl:call-template>
- <xsl:choose>
- <xsl:when test="description">
- <xsl:copy-of select="description" />
- <xsl:value-of select="concat(' (', @pds, ')')" />
- <xsl:if test="@length > 1">
- <font color="#999999">
- <xsl:value-of select="concat(' [1/', @length, ' complete]')" />
- </font>
- </xsl:if>
- </xsl:when>
- <xsl:when test="@length > 1">
- <font color="#999999" size="1">
- <xsl:value-of select="concat(' [', ($p - @start + 1), '/', @length, ' complete]')" />
- </font>
- </xsl:when>
- <xsl:otherwise>
- <font scolor="#999999" size="1">[complete]</font>
- </xsl:otherwise>
- </xsl:choose>
- </font>
- </xsl:if>
- </p>
- </xsl:for-each>
- <xsl:for-each select="$oldSteps">
- <p>
- <font size="1">
- <xsl:call-template name="setFontColorForStep">
- <xsl:with-param name="step" select="."></xsl:with-param>
- </xsl:call-template>
- <xsl:call-template name="drawStatus">
- <xsl:with-param name="rel" select="$rel" />
- <xsl:with-param name="value" select="@status" />
- <xsl:with-param name="defaultImage" select="'default.gif'" />
- </xsl:call-template>
- <xsl:if test="description">
- <xsl:value-of select="substring(description, 0, 15)" />
- ...
- </xsl:if>
- <xsl:choose>
- <xsl:when test="@start + @length -1 = $p">
- <font color="#999999" size="1">[complete]</font>
- </xsl:when>
- <xsl:otherwise>
- <font color="#999999" size="1">
- <xsl:value-of select="concat(' [', ($p - @start + 1), '/', @length, ' complete]')" />
- </font>
- </xsl:otherwise>
- </xsl:choose>
- </font>
- </p>
- </xsl:for-each>
- <xsl:if test="count($newSteps | $oldSteps) = 0">
- <font>.</font>
- </xsl:if>
- </td>
- </xsl:for-each>
- </xsl:when>
- <xsl:otherwise>
- <xsl:for-each select="week">
- <td>
- <center>.</center>
- </td>
- </xsl:for-each>
- </xsl:otherwise>
- </xsl:choose>
- </xsl:for-each>
- </tr>
- </xsl:template>
-
-
- <xsl:template name="setFontColorForStep">
- <xsl:param name="step"></xsl:param>
- <xsl:variable name="priority" select="$step/ancestor::item/@priority" />
- <xsl:choose>
- <xsl:when test="$priority = 'high'">
- <xsl:attribute name="color">red</xsl:attribute>
- </xsl:when>
- <xsl:when test="$priority = 'medium'">
- <xsl:attribute name="color">blue</xsl:attribute>
- </xsl:when>
- <xsl:otherwise>
- <xsl:attribute name="color">black</xsl:attribute>
- </xsl:otherwise>
- </xsl:choose>
- </xsl:template>
-</xsl:stylesheet>
\ No newline at end of file
diff --git a/development/milestone_plans/stylesheets/milestone-common.xsl b/development/milestone_plans/stylesheets/milestone-common.xsl
deleted file mode 100644
index a6ddc6c..0000000
--- a/development/milestone_plans/stylesheets/milestone-common.xsl
+++ /dev/null
@@ -1,219 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!--
-
- ChangeLog:
-
- 2005-02-24 Phil Avery, pavery@us.ibm.com
- - added 'onmouseover' and 'onmouseout' actions
- to display 'detail' info in a new window
-
--->
-
-<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xalan="http://xml.apache.org/xslt" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.w3.org/1999/xhtml">
-
- <xsl:template name="printHeader">
- <xsl:param name="rel"></xsl:param>
- <xsl:param name="title"></xsl:param>
- <xsl:param name="description"></xsl:param>
- <table cellSpacing="5" cellPadding="2" width="100%" border="0">
- <tr>
- <td>
- <font class="indextop">
- <xsl:value-of select="$title" />
- </font>
- <br />
- <font class="indexsub">
- <xsl:value-of select="$description" />
- </font>
- </td>
- <td>
- <br />
- </td>
- <td width="28%">
- <img width="120" height="86">
- <xsl:attribute name="src">
- <xsl:value-of select="concat($rel, 'development/milestone_plans/stylesheets/images/Idea.jpe')" />
- </xsl:attribute>
- </img>
- </td>
- </tr>
- </table>
- </xsl:template>
-
- <xsl:template name="printLegend">
- <xsl:param name="rel" />
- <xsl:variable name="prefix" select="concat($rel, 'development/milestone_plans/stylesheets/images/')" />
- <table cellspacing="5" cellpadding="2" width="100%" border="0">
- <tbody>
- <tr>
- <td valign="top" align="left" width="100%" bgcolor="#0080c0" colspan="4">
- <b>
- <font face="Arial,Helvetica">
- <font color="#ffffff">Legend</font>
- </font>
- </b>
- </td>
- </tr>
- <tr>
- <td valign="top">
- <img height="5" width="14">
- <xsl:attribute name="src">
- <xsl:value-of select="concat($prefix, 'progress.gif')" />
- </xsl:attribute>
- </img>
- </td>
- <td width="50%">item is under development.</td>
- <td valign="top">
- <img height="10" width="10">
- <xsl:attribute name="src">
- <xsl:value-of select="concat($prefix, 'glass.gif')" />
- </xsl:attribute>
- </img>
- </td>
- <td width="50%">item is under investigation.</td>
- </tr>
- <tr>
- <td valign="top">
- <img height="10" width="10">
- <xsl:attribute name="src">
- <xsl:value-of select="concat($prefix, 'ok.gif')" />
- </xsl:attribute>
- </img>
- </td>
- <td width="50%">item is finished.</td>
- <td valign="top">
- <img height="12" width="40">
- <xsl:attribute name="src">
- <xsl:value-of select="concat($prefix, 'help.gif')" />
- </xsl:attribute>
- </img>
- </td>
- <td width="50%">help wanted</td>
- </tr>
- <tr>
- <td valign="top">
- <img height="10" width="10">
- <xsl:attribute name="src">
- <xsl:value-of select="concat($prefix, 'defer.gif')" />
- </xsl:attribute>
- </img>
- </td>
- <td width="50%">item is deferred.</td>
- <td valign="top">
- <font class="indexsub">
- <img>
- <xsl:attribute name="src">
- <xsl:value-of select="concat($prefix, 'new.gif')" />
- </xsl:attribute>
- </img>
- </font>
- </td>
- <td width="50%">new</td>
- </tr>
- </tbody>
- </table>
- </xsl:template>
-
- <xsl:template name="drawHelpWanted">
- <xsl:param name="rel"></xsl:param>
- <xsl:variable name="prefix" select="concat($rel, 'development/milestone_plans/stylesheets/images/')"></xsl:variable>
- <img height="12" width="40">
- <xsl:attribute name="src">
- <xsl:value-of select="concat($prefix, 'help.gif')" />
- </xsl:attribute>
- </img>
- </xsl:template>
-
- <xsl:template name="drawDetail">
- <xsl:param name="rel"></xsl:param>
- <xsl:param name="detail"></xsl:param>
- <xsl:variable name="prefix" select="concat($rel, 'development/milestone_plans/stylesheets/images/')"></xsl:variable>
- <xsl:variable name="apos">'</xsl:variable>
- <xsl:variable name="quote">"</xsl:variable>
- <xsl:variable name="apos-translated"></xsl:variable>
- <xsl:variable name="detail-escapedMarkup">
- <xsl:apply-templates select="$detail" mode="escape-detail" />
- </xsl:variable>
- <xsl:variable name="detail-escaped" select="translate($detail-escapedMarkup, $quote, $apos)"></xsl:variable>
- <img height="15" width="16">
- <xsl:attribute name="src">
- <xsl:value-of select="concat($prefix, 'detail.gif')" />
- </xsl:attribute>
- <xsl:attribute name="onmouseout">
- <xsl:value-of select="'hidePopup()'" />
- </xsl:attribute>
- <xsl:attribute name="onmouseover">
- <xsl:value-of select='concat( "showPopup(" , $quote, normalize-space($detail-escaped) , $quote, ")")' />
- </xsl:attribute>
- </img>
- </xsl:template>
-
- <xsl:template name="drawBug">
- <xsl:param name="bug"></xsl:param>
- [<a>
- <xsl:attribute name="href">
- <xsl:value-of select="concat('https://bugs.eclipse.org/bugs/show_bug.cgi?id=', $bug)" />
- </xsl:attribute>
- <xsl:value-of select="$bug" />
- </a>]
- </xsl:template>
-
- <xsl:template name="drawStatus">
- <xsl:param name="rel"></xsl:param>
- <xsl:param name="value"></xsl:param>
- <xsl:param name="defaultImage"></xsl:param>
- <xsl:variable name="prefix" select="concat($rel, 'development/milestone_plans/stylesheets/images/')"></xsl:variable>
- <xsl:choose>
- <xsl:when test="$value = 'in-progress'">
- <img height="5" width="13">
- <xsl:attribute name="src">
- <xsl:value-of select="concat($prefix, 'progress.gif')" />
- </xsl:attribute>
- </img>
- </xsl:when>
- <xsl:when test="$value = 'done'">
- <img height="10" width="10">
- <xsl:attribute name="src">
- <xsl:value-of select="concat($prefix, 'ok.gif')" />
- </xsl:attribute>
- </img>
- </xsl:when>
- <xsl:when test="$value = 'investigate'">
- <img height="10" width="10">
- <xsl:attribute name="src">
- <xsl:value-of select="concat($prefix, 'glass.gif')" />
- </xsl:attribute>
- </img>
- </xsl:when>
- <xsl:when test="$value = 'deferred'">
- <img height="10" width="10">
- <xsl:attribute name="src">
- <xsl:value-of select="concat($prefix, 'defer.gif')" />
- </xsl:attribute>
- </img>
- </xsl:when>
- <xsl:otherwise>
- <xsl:if test="$defaultImage">
- <img height="10" width="10">
- <xsl:attribute name="src">
- <xsl:value-of select="concat($prefix, $defaultImage)" />
- </xsl:attribute>
- </img>
- </xsl:if>
- </xsl:otherwise>
- </xsl:choose>
- </xsl:template>
-
- <!-- the following templates are used to escape HTML markup in order to render detail content -->
- <xsl:template match="*|@*|comment()|processing-instruction()|text()" mode="escape-detail">
- <xsl:copy>
- <xsl:apply-templates select="*|@*|comment()|processing-instruction()|text()" mode="escape-detail"/>
- </xsl:copy>
- </xsl:template>
- <xsl:template match="*" mode="escape-detail">
- <<xsl:value-of select="name(.)"/>>
- <xsl:apply-templates select="*|@*|comment()|processing-instruction()|text()" mode="escape-detail"/>
- </<xsl:value-of select="name(.)"/>>
- </xsl:template>
-</xsl:stylesheet>
\ No newline at end of file
diff --git a/development/milestone_plans/stylesheets/milestone-overview.xsl b/development/milestone_plans/stylesheets/milestone-overview.xsl
deleted file mode 100644
index 1b42347..0000000
--- a/development/milestone_plans/stylesheets/milestone-overview.xsl
+++ /dev/null
@@ -1,215 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!--
-
- ChangeLog:
-
- 2005-08-24 Nitin Dahyabhai, nitind@us.ibm.com
- - switch to n.nMxx naming scheme for milestones
-
- 2005-01-31 Arthur Ryman, ryman@ca.ibm.com
- - generate links to milestone_plan.html instead of milesone_plan.xml
--->
-
-<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xalan="http://xml.apache.org/xslt" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.w3.org/1999/xhtml">
- <xsl:output method="html" encoding="UTF-8" />
- <xsl:include href="../stylesheets/milestone-common.xsl" />
-
- <xsl:variable name="plans" select="document(/report/milestone[substring(@name, 5) >= substring(/report/@current-milestone, 5)]/plan/@location)/plan" />
- <xsl:variable name="rel" select="'../../../'" />
- <xsl:template match="report">
- <html>
- <head>
- <title>
- <xsl:value-of select="/report/title" />
- </title>
- <link href="../stylesheets/images/default_style.css" type="text/css" rel="stylesheet" />
- </head>
- <body>
-
- <xsl:call-template name="printHeader">
- <xsl:with-param name="rel" select="$rel" />
- <xsl:with-param name="title" select="/report/title" />
- <xsl:with-param name="description" select="/report/description" />
- </xsl:call-template>
-
- <table width="100%" cellspacing="0" cellpadding="4">
- <tr>
- <td height="20" bgcolor="#0080c0" colspan="2">
- <b>
- <font color="#ffffff">Status of this document</font>
- </b>
- </td>
- </tr>
- <tr>
- <td colspan="2">
- <xsl:value-of select="/report/status" />
- </td>
- </tr>
- <xsl:for-each select="milestone">
- <tr>
- <xsl:if test="@name = /report/@current-milestone">
- <xsl:attribute name="bgcolor">yellow</xsl:attribute>
- </xsl:if>
- <td vAlign="top" width="3%">
- <p align="right">
- <img height="16" src="../stylesheets/images/Adarrow.gif" width="16" align="bottom" border="0" name="Image2" alt="" />
- </p>
- </td>
- <td width="97%">
- <p>
- <a href="#{@name}">
- <b>
- <xsl:value-of select="description" />
- </b>
- </a>
- <xsl:if test="statusDescription">
- -
- <xsl:copy-of select="statusDescription" />
- </xsl:if>
- <br>
- <xsl:copy-of select="contentDescription" />
- </br>
- </p>
- </td>
- </tr>
- </xsl:for-each>
- </table>
- <xsl:for-each select="/report/milestone[substring(@name, 5) >= substring(/report/@current-milestone, 5)]">
- <xsl:sort data-type="number" select="@name" />
- <table width="100%">
- <tr>
- <td height="20" bgcolor="#0080c0" width="100%">
- <a name="{@name}"/>
- <b>
- <font color="#ffffff">
- <xsl:value-of select="description" />
- </font>
- </b>
- </td>
- </tr>
- <xsl:call-template name="prioritySection">
- <xsl:with-param name="title" select="'High Priority'" />
- <xsl:with-param name="priorityValue" select="'high'" />
- <xsl:with-param name="milestoneName" select="@name" />
- </xsl:call-template>
- <xsl:call-template name="prioritySection">
- <xsl:with-param name="title" select="'Medium Priority'" />
- <xsl:with-param name="priorityValue" select="'medium'" />
- <xsl:with-param name="milestoneName" select="@name" />
- </xsl:call-template>
- <xsl:call-template name="prioritySection">
- <xsl:with-param name="title" select="'Low Priority'" />
- <xsl:with-param name="priorityValue" select="'low'" />
- <xsl:with-param name="milestoneName" select="@name" />
- </xsl:call-template>
- <!--
- <xsl:call-template name="prioritySection">
- <xsl:with-param name="title" select="'Unprioritized'" />
- <xsl:with-param name="priorityValue" select="'none'" />
- <xsl:with-param name="milestoneName" select="@name" />
- </xsl:call-template>
- -->
- </table>
- </xsl:for-each>
- <br />
- <br />
- <xsl:call-template name="printLegend">
- <xsl:with-param name="rel" select="$rel" />
- </xsl:call-template>
- <br />
- <br />
- <br />
- <p>
- Please see our
- <a href="http://eclipse.org/legal/privacy.html">privacy policy</a>
- and website
- <a href="http://eclipse.org/legal/termsofuse.html">terms of use</a>
- . For problems with the eclipse.org site, please contact the
- <a href="mailto:webmaster@eclipse.org">webmaster</a>
- or read the
- <a href="http://eclipse.org/webmaster/index.html">webmaster FAQ</a>
- for answers to common questions!
- </p>
- </body>
- </html>
- </xsl:template>
-
- <xsl:template name="prioritySection">
- <xsl:param name="title" />
- <xsl:param name="priorityValue" />
- <xsl:param name="milestoneName" />
- <tr>
- <td>
- <xsl:variable name="jstItems" select="$plans/component[@subproject='jst']//item[$priorityValue='all' or (not(@priority) and $priorityValue='none')or @priority=$priorityValue][ancestor::milestone/@name=$milestoneName]"></xsl:variable>
- <xsl:variable name="wstItems" select="$plans/component[@subproject='wst']//item[$priorityValue='all' or (not(@priority) and $priorityValue='none')or @priority=$priorityValue][ancestor::milestone/@name=$milestoneName]"></xsl:variable>
- <xsl:if test="count($jstItems) + count($wstItems) > 0">
- <b>
- <xsl:value-of select="$title" />
- </b>
- <ul>
- <xsl:call-template name="subprojectSection">
- <xsl:with-param name="subprojectName" select="'jst'" />
- <xsl:with-param name="priorityItems" select="$jstItems" />
- </xsl:call-template>
- <xsl:call-template name="subprojectSection">
- <xsl:with-param name="subprojectName" select="'wst'" />
- <xsl:with-param name="priorityItems" select="$wstItems" />
- </xsl:call-template>
- </ul>
- </xsl:if>
- </td>
- </tr>
- </xsl:template>
-
- <xsl:template name="subprojectSection">
- <xsl:param name="subprojectName" />
- <xsl:param name="priorityItems" />
- <xsl:variable name="theItems" select="$priorityItems[ancestor::component/@subproject = $subprojectName]" />
- <xsl:if test="count($theItems) > 0">
- <table>
- <tr><td width="15" colspan="2">
- <b><xsl:value-of select="$subprojectName"/></b>
- </td>
- <td/>
- </tr>
- <xsl:apply-templates select="$priorityItems">
- <xsl:sort select="ancestor::component/@name" />
- <xsl:sort select="description" />
- </xsl:apply-templates>
- </table>
- </xsl:if>
- </xsl:template>
-
-
- <xsl:template match="item">
- <xsl:variable name="milestoneName" select="ancestor::component/milestone[1]/@name" />
- <xsl:variable name="component" select="ancestor::component" />
- <xsl:variable name="url" select="concat($rel, $component/@subproject, '/components/', $component/@name, '/', $milestoneName, '/', 'milestone_plan.html')" />
- <tr>
- <td/>
- <td width="20" align="center">
- <xsl:call-template name="drawStatus">
- <xsl:with-param name="rel" select="$rel"></xsl:with-param>
- <xsl:with-param name="value" select="@status" />
- <xsl:with-param name="defaultImage" select="'default.gif'" />
- </xsl:call-template>
- </td>
- <td>
- <xsl:value-of select="'['" />
- <a href="{$url}">
- <xsl:value-of select="$component/@name" />
- </a>
- <xsl:value-of select="'] '" />
-
- <xsl:copy-of select="description" />
- <xsl:if test="@helpWanted">
- <xsl:value-of select="' '" />
- <xsl:call-template name="drawHelpWanted">
- <xsl:with-param name="rel" select="$rel" />
- </xsl:call-template>
- </xsl:if>
- </td>
- </tr>
- </xsl:template>
-</xsl:stylesheet>
\ No newline at end of file
diff --git a/development/milestone_plans/stylesheets/performance.xsl b/development/milestone_plans/stylesheets/performance.xsl
deleted file mode 100644
index 8ae9793..0000000
--- a/development/milestone_plans/stylesheets/performance.xsl
+++ /dev/null
@@ -1,170 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xalan="http://xml.apache.org/xslt" xmlns="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
-
- <xsl:output method="html" encoding="UTF-8" />
- <xsl:include href="../stylesheets/milestone-common.xsl" />
- <xsl:variable name="plans" select="document(/report/milestone/plan/@location)/plan" />
- <xsl:variable name="rel" select="'../../../'" />
- <xsl:variable name="title" select="'Eclipse WTP performance improvement plan'" />
-
- <xsl:template match="report">
- <html>
- <head>
- <title><xsl:value-of select="$title"/></title>
- <link href="../stylesheets/images/default_style.css" type="text/css" rel="stylesheet" />
- </head>
- <body>
- <xsl:call-template name="printHeader">
- <xsl:with-param name="rel" select="$rel" />
- <xsl:with-param name="title" select="$title" />
- <xsl:with-param name="description" select="'Eclipse Web Tools Platform project performance improvements'" />
- </xsl:call-template>
- <xsl:for-each select="/report/milestone[substring(@name, 5) >= substring(/report/@current-milestone, 5)]/plan">
- <xsl:apply-templates select="." />
- </xsl:for-each>
- <xsl:call-template name="printLegend">
- <xsl:with-param name="rel" select="$rel" />
- </xsl:call-template>
- <br />
- <br />
- <br />
- <p>
- Please see our
- <a href="http://eclipse.org/legal/privacy.html">privacy policy</a>
- and website
- <a href="http://eclipse.org/legal/termsofuse.html">terms of use</a>
- . For problems with the eclipse.org site, please contact the
- <a href="mailto:webmaster@eclipse.org">webmaster</a>
- or read the
- <a href="http://eclipse.org/webmaster/index.html">webmaster FAQ</a>
- for answers to common questions!
- </p>
- </body>
- </html>
- </xsl:template>
-
- <xsl:template match="plan">
- <xsl:variable name="plan" select="document(@location)"/>
- <xsl:for-each select="$plan/plan/component" >
- <xsl:sort select="@subproject"/>
- <xsl:sort select="@name"/>
- <xsl:apply-templates select="."/>
- </xsl:for-each>
- </xsl:template>
-
- <xsl:template match="component">
- <xsl:for-each select="milestone">
- <xsl:sort data-type="number" select="@name"/>
- <xsl:apply-templates select="."/>
- </xsl:for-each>
- </xsl:template>
-
- <xsl:template match="milestone">
- <xsl:for-each select="category">
- <xsl:apply-templates select="."/>
- </xsl:for-each>
- </xsl:template>
-
- <xsl:template match="category">
- <xsl:if test="@name='Performance' or @name='performance'">
- <table width="100%">
- <tr>
- <td height="20" bgcolor="#0080c0" colspan="2">
- <a><xsl:attribute name="name"><xsl:value-of select="concat(../../@subproject, '', ../../@name, '', ../@name)" /></xsl:attribute></a>
- <b>
- <font color="#ffffff"><xsl:value-of select="concat(../../@subproject, ' ', ../../@name, ' ', ../@name)" /></font>
- </b>
- </td>
- <td>
- <xsl:value-of select="@description"/>
- </td>
- </tr>
- </table>
- <xsl:for-each select="item">
- <xsl:apply-templates select="."/>
- </xsl:for-each>
- </xsl:if>
- </xsl:template>
-
- <xsl:template match="item">
- <table>
- <tr>
- <td>
- <img src="../stylesheets/images/Adarrow.gif" nosave="" border="0" height="16" />
- </td>
- <td>
- <xsl:call-template name="drawStatus">
- <xsl:with-param name="rel" select="$rel" />
- <xsl:with-param name="value" select="@status" />
- <xsl:with-param name="defaultImage" select="'default.gif'" />
- </xsl:call-template>
- <b><xsl:value-of select="description" /></b>
-  [<xsl:value-of select="@priority"/>]
- <xsl:if test="@helpWanted">
- <xsl:call-template name="drawHelpWanted">
- <xsl:with-param name="rel" select="$rel" />
- </xsl:call-template>
- </xsl:if>
- </td>
- </tr>
- </table>
- <table>
- <xsl:if test="detail">
- <tr>
- <td valign="top"><i>Detail:</i></td>
- <td><xsl:apply-templates select="detail" mode="markup"/></td>
- </tr>
- </xsl:if>
- <xsl:if test="step">
- <tr>
- <td valign="top"><i>Steps:</i></td>
- <td>
- <ol>
- <xsl:for-each select="step">
- <li><xsl:apply-templates select="description" mode="markup"/></li>
- </xsl:for-each>
- </ol>
- </td>
- </tr>
- </xsl:if>
- <xsl:if test="bugzilla">
- <tr>
- <td valign="top"><i>Bugzillas:</i></td>
- <td><a href="{bugzilla[1]/@link}"><xsl:value-of select="bugzilla[1]/@link"/></a></td>
- </tr>
- <xsl:for-each select="bugzilla[position() > 1]">
- <tr>
- <td></td>
- <td><a href="{@link}"><xsl:value-of select="@link"/></a></td>
- </tr>
- </xsl:for-each>
- </xsl:if>
- <xsl:if test="junit-test">
- <tr>
- <td valign="top"><i>JUnit tests:</i></td>
- <td><a href="{junit-test[1]/@link}"><xsl:value-of select="junit-test[1]/@link"/></a></td>
- </tr>
- <xsl:for-each select="junit-test[position() > 1]">
- <tr>
- <td></td>
- <td><a href="{@link}"><xsl:value-of select="@link"/></a></td>
- </tr>
- </xsl:for-each>
- </xsl:if>
- <xsl:if test="verification">
- <tr>
- <td valign="top"><i>Verification:</i></td>
- <td><xsl:apply-templates select="verification" mode="markup"/></td>
- </tr>
- </xsl:if>
- </table>
- <br/>
- </xsl:template>
-
- <xsl:template match="*|@*|text()" mode="markup">
- <xsl:copy>
- <xsl:apply-templates select="*|@*|text()" mode="markup"/>
- </xsl:copy>
- </xsl:template>
-
-</xsl:stylesheet>
diff --git a/development/milestone_test_plan_overview.html b/development/milestone_test_plan_overview.html
deleted file mode 100644
index 00e6987..0000000
--- a/development/milestone_test_plan_overview.html
+++ /dev/null
@@ -1,636 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../..//default_style.css" type="text/css">
-<link rel="stylesheet" href="../..//webtools/wtp.css" type="text/css">
-<title>WTP milestone test plan overview</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">WTP milestone test plan overview</font>
-<br>
-<font class="indexsub">WTP milestone test plan overview</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../..//images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Status of this Document</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Test Plan overview for WTP milestones.
- <br>
-<i>Last updated on 09/13/2005.</i>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">1.0M8</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Links to the most recent Test Plans for each component:
- <p>
-
-<b>jst</b>
-
-<ul>
-
-<li>
-<a href="../plans/1.0/jst/jsp/M8/milestone_test_plan.html">JSP</a>
-</li>
-
-</ul>
-
-</p>
-
-<p>
-
-<b>wst</b>
-
-<ul>
-
-<li>
-<a href="../plans/1.0/wst/css/M8/milestone_test_plan.html">CSS</a>
-</li>
-
-<li>
-<a href="../plans/1.0/wst/dtd/M8/milestone_test_plan.html">DTD</a>
-</li>
-
-<li>
-<a href="../plans/1.0/wst/html/M8/milestone_test_plan.html">HTML</a>
-</li>
-
-<li>
-<a href="../plans/1.0/wst/javascript/M8/milestone_test_plan.html">Javascript</a>
-</li>
-
-<li>
-<a href="../plans/1.0/wst/sse/M8/milestone_test_plan.html">SSE</a>
-</li>
-
-<li>
-<a href="../plans/1.0/wst/xml/M8/milestone_test_plan.html">XML</a>
-</li>
-
-</ul>
-
-</p>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p></p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">M5</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Here are the links to the component test plans:
- <p>
-
-<b>jst</b>
-
-<ul>
-
-<li>j2ee
- <ul>
-
-<li>
-<a href="../jst/components/j2ee/M5/test_plan.html">J2EE Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>jsp
- <ul>
-
-<li>
-<a href="../jst/components/jsp/M5/milestone_test_plan.html">JSP Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>ws
- <ul>
-
-<li>
-<a href="../jst/components/ws/M5/test_plan.html">JST Web Services Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-</ul>
-
-</p>
-
-<p>
-
-<b>wst</b>
-<br>
-
-<ul>
-
-<li>command
- <ul>
-
-<li>
-<a href="../wst/components/command/M5/test_plan.html">Command Component Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>css
- <ul>
-
-<li>
-<a href="../wst/components/css/M5/milestone_test_plan.html">CSS Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>dtd
- <ul>
-
-<li>
-<a href="../wst/components/dtd/M5/milestone_test_plan.html">DTD Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>html
- <ul>
-
-<li>
-<a href="../wst/components/html/M5/milestone_test_plan.html">HTML Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>javascript
- <ul>
-
-<li>
-<a href="../wst/components/javascript/M5/milestone_test_plan.html">Javascript Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>sse
- <ul>
-
-<li>
-<a href="../wst/components/sse/M5/milestone_test_plan.html">SSE Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>ws
- <ul>
-
-<li>
-<a href="../wst/components/ws/M5/test_plan.html">WST Web Services Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-
-<li>xml
- <ul>
-
-<li>
-<a href="../wst/components/xml/M5/milestone_test_plan.html">XML Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-
-</ul>
-
-</p>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p></p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">M4</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Here are the links to the component test plans:
- <p>
-
-<b>jst</b>
-
-<ul>
-
-<li>j2ee
- <ul>
-
-<li>
-<a href="../jst/components/j2ee/M4/test_plan.html">J2EE Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>jsp
- <ul>
-
-<li>
-<a href="../jst/components/jsp/M4/milestone_test_plan.html">JSP Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>ws
- <ul>
-
-<li>
-<a href="../jst/components/ws/M4/test_plan.html">JST Web Services Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-</ul>
-
-</p>
-
-<p>
-
-<b>wst</b>
-<br>
-
-<ul>
-
-<li>command
- <ul>
-
-<li>
-<a href="../wst/components/command/M4/test_plan.html">Command Component Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>css
- <ul>
-
-<li>
-<a href="../wst/components/css/M4/milestone_test_plan.html">CSS Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>dtd
- <ul>
-
-<li>
-<a href="../wst/components/dtd/M4/milestone_test_plan.html">DTD Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>html
- <ul>
-
-<li>
-<a href="../wst/components/html/M4/milestone_test_plan.html">HTML Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>javascript
- <ul>
-
-<li>
-<a href="../wst/components/javascript/M4/milestone_test_plan.html">Javascript Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>sse
- <ul>
-
-<li>
-<a href="../wst/components/sse/M4/milestone_test_plan.html">SSE Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>ws
- <ul>
-
-<li>
-<a href="../wst/components/ws/M4/test_plan.html">WST Web Services Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>wsdl
- <ul>
-
-<li>
-<a href="../wst/components/wsdl/M4/milestone_test_plan.html">WSDL Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>xml
- <ul>
-
-<li>
-<a href="../wst/components/xml/M4/milestone_test_plan.html">XML Test Plan</a>
-</li>
-
-<li>
-<a href="../wst/components/xml/M4/xml-editor_test_plan.html">XML Editor Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>xsd
- <ul>
-
-<li>
-<a href="../wst/components/xsd/M4/milestone_test_plan.html">XSD Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-
-</ul>
-
-</p>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p></p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">M3</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Here are the links to the component test plans:
- <p>
-
-<b>jst</b>
-
-<ul>
-
-<li>j2ee
- <ul>
-
-<li>
-<a href="../jst/components/j2ee/M3/test_plan.html">J2EE Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>jsp
- <ul>
-
-<li>
-<a href="../jst/components/jsp/M3/milestone_test_plan.html">JSP Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>ws
- <ul>
-
-<li>
-<a href="../jst/components/ws/M3/test_plan.html">JST Web Services Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-</ul>
-
-</p>
-
-<p>
-
-<b>wst</b>
-<br>
-
-<ul>
-
-<li>command
- <ul>
-
-<li>
-<a href="../wst/components/command/M3/test_plan.html">Command Component Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>css
- <ul>
-
-<li>
-<a href="../wst/components/css/M3/milestone_test_plan.html">CSS Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>dtd
- <ul>
-
-<li>
-<a href="../wst/components/dtd/M3/milestone_test_plan.html">DTD Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>html
- <ul>
-
-<li>
-<a href="../wst/components/html/M3/milestone_test_plan.html">HTML Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>javascript
- <ul>
-
-<li>
-<a href="../wst/components/javascript/M3/milestone_test_plan.html">Javascript Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>sse
- <ul>
-
-<li>
-<a href="../wst/components/sse/M3/milestone_test_plan.html">SSE Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>ws
- <ul>
-
-<li>
-<a href="../wst/components/ws/M3/test_plan.html">WST Web Services Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>wsdl
- <ul>
-
-<li>
-<a href="../wst/components/wsdl/M3/WSDL_Editor_M3_Test_Plan.html">WSDL Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>xml
- <ul>
-
-<li>
-<a href="../wst/components/xml/M3/milestone_test_plan.html">XML Test Plan</a>
-</li>
-
-<li>
-<a href="../wst/components/xml/M3/xml-catalog_test_plan.html">XML Catalog Test Plan</a>
-</li>
-
-<li>
-<a href="../wst/components/xml/M3/xml-dtd-xsd-validation_test_plan.html">XML Validation Test Plan</a>
-</li>
-
-<li>
-<a href="../wst/components/xml/M3/xml-editor_test_plan.html">XML Editor Test Plan</a>
-</li>
-
-<li>
-<a href="../wst/components/xml/M3/xml-examples_test_plan.html">XML Examples Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-<li>xsd
- <ul>
-
-<li>
-<a href="../wst/components/xsd/M3/xsd-editor_M3TestPlan.html">XSD Test Plan</a>
-</li>
-
-</ul>
-
-</li>
-
-
-</ul>
-
-</p>
-
-</p>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/development/milestone_test_plan_overview.xml b/development/milestone_test_plan_overview.xml
deleted file mode 100644
index e14b259..0000000
--- a/development/milestone_test_plan_overview.xml
+++ /dev/null
@@ -1,293 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<?xml-stylesheet type="text/xsl" href="../wtp.xsl"?>
-<html>
-
- <head>
- <meta name="root" content="../../" />
- <title>WTP milestone test plan overview</title>
- </head>
- <body>
-
- <h1>WTP milestone test plan overview</h1>
-
- <h2>Status of this Document</h2>
- <p>
- Test Plan overview for WTP milestones.
- <br/><i>Last updated on 09/13/2005.</i>
- </p>
-
- <h2>1.0M8</h2>
- <p>
- Links to the most recent Test Plans for each component:
- <p>
- <b>jst</b>
- <ul>
- <li><a href="../plans/1.0/jst/jsp/M8/milestone_test_plan.html">JSP</a></li>
- </ul>
- </p>
- <p>
- <b>wst</b>
- <ul>
- <li><a href="../plans/1.0/wst/css/M8/milestone_test_plan.html">CSS</a></li>
- <li><a href="../plans/1.0/wst/dtd/M8/milestone_test_plan.html">DTD</a></li>
- <li><a href="../plans/1.0/wst/html/M8/milestone_test_plan.html">HTML</a></li>
- <li><a href="../plans/1.0/wst/javascript/M8/milestone_test_plan.html">Javascript</a></li>
- <li><a href="../plans/1.0/wst/sse/M8/milestone_test_plan.html">SSE</a></li>
- <li><a href="../plans/1.0/wst/xml/M8/milestone_test_plan.html">XML</a></li>
- </ul>
- </p>
- </p>
- <p></p>
-
- <h2>M5</h2>
- <p>
- Here are the links to the component test plans:
- <p>
- <b>jst</b>
- <ul>
- <li>j2ee
- <ul>
- <li><a href="../jst/components/j2ee/M5/test_plan.html">J2EE Test Plan</a></li>
- </ul>
- </li>
- <li>jsp
- <ul>
- <li><a href="../jst/components/jsp/M5/milestone_test_plan.html">JSP Test Plan</a></li>
- </ul>
- </li>
- <li>ws
- <ul>
- <li><a href="../jst/components/ws/M5/test_plan.html">JST Web Services Test Plan</a></li>
- </ul>
- </li>
- </ul>
- </p>
- <p>
- <b>wst</b><br/>
- <ul>
- <li>command
- <ul>
- <li><a href="../wst/components/command/M5/test_plan.html">Command Component Test Plan</a></li>
- </ul>
- </li>
- <li>css
- <ul>
- <li><a href="../wst/components/css/M5/milestone_test_plan.html">CSS Test Plan</a></li>
- </ul>
- </li>
- <li>dtd
- <ul>
- <li><a href="../wst/components/dtd/M5/milestone_test_plan.html">DTD Test Plan</a></li>
- </ul>
- </li>
- <li>html
- <ul>
- <li><a href="../wst/components/html/M5/milestone_test_plan.html">HTML Test Plan</a></li>
- </ul>
- </li>
- <li>javascript
- <ul>
- <li><a href="../wst/components/javascript/M5/milestone_test_plan.html">Javascript Test Plan</a></li>
- </ul>
- </li>
- <li>sse
- <ul>
- <li><a href="../wst/components/sse/M5/milestone_test_plan.html">SSE Test Plan</a></li>
- </ul>
- </li>
- <li>ws
- <ul>
- <li><a href="../wst/components/ws/M5/test_plan.html">WST Web Services Test Plan</a></li>
- </ul>
- </li>
- <!--
- <li>wsdl
- <ul>
- <li><a href="../wst/components/wsdl/M5/milestone_test_plan.html">WSDL Test Plan</a></li>
- </ul>
- </li>
- -->
- <li>xml
- <ul>
- <li><a href="../wst/components/xml/M5/milestone_test_plan.html">XML Test Plan</a></li>
- </ul>
- </li>
- <!--
- <li>xsd
- <ul>
- <li><a href="../wst/components/xsd/M5/milestone_test_plan.html">XSD Test Plan</a></li>
- </ul>
- </li>
- -->
- </ul>
- </p>
- </p>
- <p></p>
- <h2>M4</h2>
- <p>
- Here are the links to the component test plans:
- <p>
- <b>jst</b>
- <ul>
- <li>j2ee
- <ul>
- <li><a href="../jst/components/j2ee/M4/test_plan.html">J2EE Test Plan</a></li>
- </ul>
- </li>
- <li>jsp
- <ul>
- <li><a href="../jst/components/jsp/M4/milestone_test_plan.html">JSP Test Plan</a></li>
- </ul>
- </li>
- <li>ws
- <ul>
- <li><a href="../jst/components/ws/M4/test_plan.html">JST Web Services Test Plan</a></li>
- </ul>
- </li>
- </ul>
- </p>
- <p>
- <b>wst</b><br/>
- <ul>
- <li>command
- <ul>
- <li><a href="../wst/components/command/M4/test_plan.html">Command Component Test Plan</a></li>
- </ul>
- </li>
- <li>css
- <ul>
- <li><a href="../wst/components/css/M4/milestone_test_plan.html">CSS Test Plan</a></li>
- </ul>
- </li>
- <li>dtd
- <ul>
- <li><a href="../wst/components/dtd/M4/milestone_test_plan.html">DTD Test Plan</a></li>
- </ul>
- </li>
- <li>html
- <ul>
- <li><a href="../wst/components/html/M4/milestone_test_plan.html">HTML Test Plan</a></li>
- </ul>
- </li>
- <li>javascript
- <ul>
- <li><a href="../wst/components/javascript/M4/milestone_test_plan.html">Javascript Test Plan</a></li>
- </ul>
- </li>
- <li>sse
- <ul>
- <li><a href="../wst/components/sse/M4/milestone_test_plan.html">SSE Test Plan</a></li>
- </ul>
- </li>
- <li>ws
- <ul>
- <li><a href="../wst/components/ws/M4/test_plan.html">WST Web Services Test Plan</a></li>
- </ul>
- </li>
- <li>wsdl
- <ul>
- <li><a href="../wst/components/wsdl/M4/milestone_test_plan.html">WSDL Test Plan</a></li>
- </ul>
- </li>
- <li>xml
- <ul>
- <li><a href="../wst/components/xml/M4/milestone_test_plan.html">XML Test Plan</a></li>
- <li><a href="../wst/components/xml/M4/xml-editor_test_plan.html">XML Editor Test Plan</a></li>
- </ul>
- </li>
- <li>xsd
- <ul>
- <li><a href="../wst/components/xsd/M4/milestone_test_plan.html">XSD Test Plan</a></li>
- </ul>
- </li>
-
- </ul>
- </p>
- </p>
- <p></p>
- <h2>M3</h2>
- <p>
- Here are the links to the component test plans:
- <p>
- <b>jst</b>
- <ul>
- <li>j2ee
- <ul>
- <li><a href="../jst/components/j2ee/M3/test_plan.html">J2EE Test Plan</a></li>
- </ul>
- </li>
- <li>jsp
- <ul>
- <li><a href="../jst/components/jsp/M3/milestone_test_plan.html">JSP Test Plan</a></li>
- </ul>
- </li>
- <li>ws
- <ul>
- <li><a href="../jst/components/ws/M3/test_plan.html">JST Web Services Test Plan</a></li>
- </ul>
- </li>
- </ul>
- </p>
- <p>
- <b>wst</b><br/>
- <ul>
- <li>command
- <ul>
- <li><a href="../wst/components/command/M3/test_plan.html">Command Component Test Plan</a></li>
- </ul>
- </li>
- <li>css
- <ul>
- <li><a href="../wst/components/css/M3/milestone_test_plan.html">CSS Test Plan</a></li>
- </ul>
- </li>
- <li>dtd
- <ul>
- <li><a href="../wst/components/dtd/M3/milestone_test_plan.html">DTD Test Plan</a></li>
- </ul>
- </li>
- <li>html
- <ul>
- <li><a href="../wst/components/html/M3/milestone_test_plan.html">HTML Test Plan</a></li>
- </ul>
- </li>
- <li>javascript
- <ul>
- <li><a href="../wst/components/javascript/M3/milestone_test_plan.html">Javascript Test Plan</a></li>
- </ul>
- </li>
- <li>sse
- <ul>
- <li><a href="../wst/components/sse/M3/milestone_test_plan.html">SSE Test Plan</a></li>
- </ul>
- </li>
- <li>ws
- <ul>
- <li><a href="../wst/components/ws/M3/test_plan.html">WST Web Services Test Plan</a></li>
- </ul>
- </li>
- <li>wsdl
- <ul>
- <li><a href="../wst/components/wsdl/M3/WSDL_Editor_M3_Test_Plan.html">WSDL Test Plan</a></li>
- </ul>
- </li>
- <li>xml
- <ul>
- <li><a href="../wst/components/xml/M3/milestone_test_plan.html">XML Test Plan</a></li>
- <li><a href="../wst/components/xml/M3/xml-catalog_test_plan.html">XML Catalog Test Plan</a></li>
- <li><a href="../wst/components/xml/M3/xml-dtd-xsd-validation_test_plan.html">XML Validation Test Plan</a></li>
- <li><a href="../wst/components/xml/M3/xml-editor_test_plan.html">XML Editor Test Plan</a></li>
- <li><a href="../wst/components/xml/M3/xml-examples_test_plan.html">XML Examples Test Plan</a></li>
- </ul>
- </li>
- <li>xsd
- <ul>
- <li><a href="../wst/components/xsd/M3/xsd-editor_M3TestPlan.html">XSD Test Plan</a></li>
- </ul>
- </li>
-
- </ul>
- </p>
- </p>
- </body>
-</html>
\ No newline at end of file
diff --git a/development/news/0.7.html b/development/news/0.7.html
deleted file mode 100644
index 924fafe..0000000
--- a/development/news/0.7.html
+++ /dev/null
@@ -1,77 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<head>
-<title>WTP 0.7 News</title>
-<link type="text/css" rel="stylesheet" href="default_style.css">
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-</head>
-<body>
-<table>
- <tbody valign="top">
- <tr>
- <td>
- <h1>WTP 0.7 - New and Noteworthy</h1>
-
- <p>Here are some of the more noteworthy features
- available in WTP 0.7 (July 29, 2005), which is now
- available for download <a
- href="http://download.eclipse.org/webtools/downloads/drops/R-0.7-200507290654/">
- here</a> and Update Manager <a href="../updatesite/updatesite.html">installation</a>.
-
- </p>
- </td>
- <td align="right"><img src="../../../images/Idea.jpg"
- alt="Idea image"></td>
- </tr>
- </tbody>
-</table>
-<p></p>
-
-<!-- N&N are now separated by component instead of by teams and thus shouldn't link to each other -->
-
-<blockquote>
-<h3>New and Noteworthy in WST</h3>
-<ul>
- <!-- <li><a href="../../wst/components/command/M5/new_and_noteworthy/command-news-m5.html">Command</a></li> -->
- <!-- <li><a href="../../wst/components/common/M5/new_and_noteworthy/common-news-m5.html">Common</a></li> -->
- <!-- <li><a href="../../wst/components/css/M5/new_and_noteworthy/css-news-m5.html">CSS</a></li> -->
- <!-- <li><a href="../../wst/components/dtd/M5/new_and_noteworthy/dtd-news-m5.html">DTD</a></li> -->
- <!-- <li><a href="../../wst/components/html/M5/new_and_noteworthy/html-news-m5.html">HTML</a></li> -->
- <!-- <li><a href="../../wst/components/internet/M5/new_and_noteworthy/internet-news-m5.html">Internet</a></li> -->
- <!-- <li><a href="../../wst/components/javascript/M5/new_and_noteworthy/javascript-news-m5.html">Javascript</a></li> -->
- <!-- <li><a href="../../wst/components/rdb/M5/new_and_noteworthy/rdb-news-M5.html">Relational Database Tools</a></li> -->
- <!-- <li><a href="../../wst/components/server/M5/new_and_noteworthy/server-news-M5.html">Server Tools</a></li> -->
- <!-- <li><a href="../../wst/components/sse/M5/new_and_noteworthy/sse-news-m5.html">Structured Source Editing</a></li> -->
- <!-- <li><a href="../../wst/components/validation/M5/new_and_noteworthy/validation-news-m5.html">Validation</a></li> -->
- <!-- <li><a href="../../wst/components/web/M5/new_and_noteworthy/web-news-m5.html">Web</a></li> -->
- <!-- <li><a href="../../wst/components/ws/M5/new_and_noteworthy/ws-news-m5.html">Web Services Tools</a></li> -->
- <!-- <li><a href="../../wst/components/wsdl/M5/new_and_noteworthy/wsdl-news-m5.html">WSDL Tools</a></li> -->
- <!-- <li><a href="../../wst/components/wsi/M5/new_and_noteworthy/wsi-news-m5.html">WS-I Tools</a></li> -->
- <!-- <li><a href="../../wst/components/xml/M5/new_and_noteworthy/xml-news-m5.html">XML</a></li> -->
- <!-- <li><a href="../../wst/components/xsd/M5/new_and_noteworthy/xsd-news-m5.html">XSD</a></li> -->
-</ul>
-<h3>New and Noteworthy in JST</h3>
-<ul>
- <!-- <li><a href="../../jst/components/common/M5/new_and_noteworthy/common-news-m5.html">Common</a></li> -->
- <!-- <li><a href="../../jst/components/ejb/M5/new_and_noteworthy/ejb-news-m5.html">EJB Tools</a></li> -->
- <!-- <li><a href="../../jst/components/j2ee/M5/news/j2ee-news-M5.html">J2EE Tools</a></li> -->
- <!-- <li><a href="../../jst/components/jsp/M5/new_and_noteworthy/jsp-news-m5.html">JSP</a></li> -->
- <!-- <li><a href="../../jst/components/server/M5/news/server-m5.html">Server Tools</a></li> -->
- <!-- <li><a href="../../jst/components/servlet/M5/new_and_noteworthy/servlet-news-m5.html">Servlet Tools</a></li> -->
- <li><a href="../../jst/components/ws/0.7/news/jst-ws-0.7news.html">Web Services Tools</a></li>
-</ul>
-</blockquote>
-<p></p>
-<p>You can also look at which <a href="https://bugs.eclipse.org/bugs/buglist.cgi?product=Web+Tools&resolution=FIXED&chfieldfrom=2005-07-01&chfieldto=2005-07-29&chfield=resolution&order=bugs.bug_id">bugs were fixed</a> during this milestone.</p>
-<p>The above features are just the ones that are new since the previous
-milestone build. Summaries for earlier milestone builds:</p>
-<ul>
- <li><a href="0.7M5.html">New for WTP milestone build 0.7 M5 (July 1, 2005)</a></li>
- <li><a href="1.0M4.html">New for WTP milestone build 0.7 M4 (April 29, 2005)</a></li>
- <li><a href="1.0M3.html">New for WTP milestone build 0.7 M3 (February 25, 2005)</a></li>
- <li><a href="1.0M2.html">New for WTP milestone build 0.7 M2 (December 23, 2004)</a></li>
-</ul>
-</body>
-</html>
-
diff --git a/development/news/0.7M5.html b/development/news/0.7M5.html
deleted file mode 100644
index 27dafe3..0000000
--- a/development/news/0.7M5.html
+++ /dev/null
@@ -1,91 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<head>
-<title>WTP 0.7 M5 News</title>
-<link type="text/css" rel="stylesheet" href="default_style.css">
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-</head>
-<body>
-<table>
- <tbody valign="top">
- <tr>
- <td>
- <h1>WTP 0.7 M5 - New and Noteworthy</h1>
-
- <p>This milestone saw the July release renumbered from 1.0 to 0.7. 0.7
- will be a full release in terms of the intended end-user content and
- stability, but the change greatly increases the window of time for feedback on proposed
- APIs by ISVs. 0.7M5 is a major milestone in respects to
- new function provided and APIs proposed for the Web Tools
- Platform's 1.0 release. Here are some of the more noteworthy features
- available in milestone build M5 (July 1, 2005) which is now
- available for download <a
- href="http://download.eclipse.org/webtools/downloads/drops/S-1.0M5-200506302219/">
- here</a>.
-
- <!--
- See the <a
- href="http://download.eclipse.org/webtools/downloads/drops/S-1.0M5-200506302219/buildNotes.php">
- M5 build notes</a> for details about bugs fixed and other changes.
- -->
- </p>
- </td>
- <td align="right"><img src="../../../images/Idea.jpg"
- alt="Idea image"></td>
- </tr>
- </tbody>
-</table>
-<p></p>
-<p>
-
-<!-- N&N are now separated by component instead of by teams and thus shouldn't link to each other -->
-
-<blockquote>
-<h3>New and Noteworthy in WST</h3>
-<ul>
- <!-- <li><a href="../../wst/components/command/M5/new_and_noteworthy/command-news-m5.html">Command</a></li> -->
- <!-- <li><a href="../../wst/components/common/M5/new_and_noteworthy/common-news-m5.html">Common</a></li> -->
- <li><a href="../../wst/components/css/M5/new_and_noteworthy/css-news-m5.html">CSS</a></li>
- <li><a href="../../wst/components/dtd/M5/new_and_noteworthy/dtd-news-m5.html">DTD</a></li>
- <!-- <li><a href="../../wst/components/html/M5/new_and_noteworthy/html-news-m5.html">HTML</a></li> -->
- <li><a href="../../wst/components/internet/0.7/M5/new_and_noteworthy/internet-news-m5.html">Internet</a></li>
- <!-- <li><a href="../../wst/components/javascript/M5/new_and_noteworthy/javascript-news-m5.html">Javascript</a></li> -->
- <!-- <li><a href="../../wst/components/rdb/M5/new_and_noteworthy/rdb-news-M5.html">Relational Database Tools</a></li> -->
- <!-- <li><a href="../../wst/components/server/M5/new_and_noteworthy/server-news-M5.html">Server Tools</a></li> -->
- <li><a href="../../wst/components/sse/M5/new_and_noteworthy/sse-news-m5.html">Structured Source Editing</a></li>
- <!-- <li><a href="../../wst/components/validation/M5/new_and_noteworthy/validation-news-m5.html">Validation</a></li> -->
- <!-- <li><a href="../../wst/components/web/M5/new_and_noteworthy/web-news-m5.html">Web</a></li> -->
- <!-- <li><a href="../../wst/components/ws/M5/new_and_noteworthy/ws-news-m5.html">Web Services Tools</a></li> -->
- <!-- <li><a href="../../wst/components/wsdl/M5/new_and_noteworthy/wsdl-news-m5.html">WSDL Tools</a></li> -->
- <!-- <li><a href="../../wst/components/wsi/M5/new_and_noteworthy/wsi-news-m5.html">WS-I Tools</a></li> -->
- <li><a href="../../wst/components/xml/M5/new_and_noteworthy/xml-news-m5.html">XML</a></li>
- <!-- <li><a href="../../wst/components/xsd/M5/new_and_noteworthy/xsd-news-m5.html">XSD</a></li> -->
-</ul>
-<h3>New and Noteworthy in JST</h3>
-<ul>
- <!-- <li><a href="../../jst/components/common/M5/new_and_noteworthy/common-news-m5.html">Common</a></li> -->
- <!-- <li><a href="../../jst/components/ejb/M5/new_and_noteworthy/ejb-news-m5.html">EJB Tools</a></li> -->
- <li><a href="../../jst/components/j2ee/M5/news/j2ee-news-M5.html">J2EE Tools</a></li>
- <li><a href="../../jst/components/jsp/M5/new_and_noteworthy/jsp-news-m5.html">JSP</a></li>
- <li><a href="../../jst/components/server/0.7/M5/news/server-m5.html">Server Tools</a></li>
- <!-- <li><a href="../../jst/components/servlet/M5/new_and_noteworthy/servlet-news-m5.html">Servlet Tools</a></li> -->
- <li><a href="../../jst/components/ws/M5/news/jst-ws-m5news.html">Web Services Tools</a></li>
-<!--
-</ul>
--->
-</blockquote>
-</p>
-<p></p>
-<p>You can also look at which <a href="https://bugs.eclipse.org/bugs/buglist.cgi?product=Web+Tools&resolution=FIXED&chfieldfrom=2005-04-30&chfieldto=2005-06-30&chfield=resolution&order=bugs.bug_id">bugs were fixed</a> during this milestone.</p>
-<p>The above features are just the ones that are new since the previous
-milestone build. Summaries for earlier milestone builds:
-<ul>
- <li><a href="1.0M4.html">New for WTP milestone build 0.7 M4 (April 29, 2005)</a></li>
- <li><a href="1.0M3.html">New for WTP milestone build 0.7 M3 (February 25, 2005)</a></li>
- <li><a href="1.0M2.html">New for WTP milestone build 0.7 M2 (December 23, 2004)</a></li>
-</ul>
-</p>
-</body>
-</html>
-
diff --git a/development/news/1.0M2.html b/development/news/1.0M2.html
deleted file mode 100644
index 1d7246a..0000000
--- a/development/news/1.0M2.html
+++ /dev/null
@@ -1,27 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
- "http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<head>
-<title>WTP 1.0 M2 News</title>
-<link rel="stylesheet" href="default_style.css" />
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/ >
-</head>
-<body>
-<h1>WTP 1.0 M2 - New and Noteworthy</h1>
-<p>M2 focussed on reintroducing much of what was first seen in the
-ObjectWeb, Lomboz, and IBM initial code contributions. Here are some of
-the highlights of milestone build M2 (December 23, 2004). See the <a
- href="http://download.eclipse.org/webtools/downloads/drops/S-1.0M2-200412230036/buildNotes.php">M2
-build notes</a> for details about bugs fixed and other changes.
-Milestone M2 is now available for download <a
- href="http://download.eclipse.org/webtools/downloads/drops/S-1.0M2-200412230036/index.html">here</a>.</p>
-<p></p>
-<blockquote>
-<ul>
- <li><a href="../../wst/components/sse/M2/m2.html">Structured Source
- Editing</a></li>
-</ul>
-</blockquote>
-<p></p>
-</body>
-</html>
diff --git a/development/news/1.0M3.html b/development/news/1.0M3.html
deleted file mode 100644
index d121f18..0000000
--- a/development/news/1.0M3.html
+++ /dev/null
@@ -1,50 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
- "http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<head>
-<title>WTP 1.0 M3 News</title>
-<link rel="stylesheet" href="default_style.css" />
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/ >
-</head>
-<body>
-<table>
- <tbody valign="top">
- <tr>
- <td>
- <h1>WTP 1.0 M3 - New and Noteworthy</h1>
- <p>There's been a lot of activity leading up to the build that will
- shown at EclipseCON 2005. Here are some of the more noteworthy
- features available in milestone build M3 (Feb. 25, 2005) which is now
- available for download <a
- href="http://download.eclipse.org/webtools/downloads/drops/S-1.0M3-200502260707/index.html">here</a>.
- See the <a
- href="http://download.eclipse.org/webtools/downloads/drops/S-1.0M3-200502260707/buildNotes.php">M3
- build notes</a> for details about bugs fixed and other changes.</p>
- </td>
- <td align="right"><img src="../../../images/Idea.jpg"
- alt="Idea image" /></td>
- </tr>
- </tbody>
-</table>
-<p></p>
-<blockquote>
-<ul>
- <li><a href="../../jst/components/j2ee/M3/news/j2ee-news-m3.html">J2EE and Validation</a></li>
- <li><a href="../../wst/components/sse/M3/news/sse-m3.html">Structured Source Editing</a></li>
- <li><a href="../../wst/components/server/0.7/M3/news/server-m3.html">Server Tools</a></li>
- <li><a href="../../wst/components/xml/M3/new_and_noteworthy/xml-m3.html">XML, XSD, and WSDL</a></li>
- <li><a href="../../jst/components/ws/M3/news/jst-ws-m3news.html">Web Services Tools</a></li>
-</ul>
-
-<li><a href="releaseNotes.html">WTP Release Notes</a></li>
-
-
-</blockquote>
-<p>The above features are just the ones that are new since the previous
-milestone build. Summaries for earlier 1.0 milestone builds:</p>
-<ul>
- <li><a href="1.0M2.html">New for WTP milestone build M2 (December 23,
- 2004)</a></li>
-</ul>
-</body>
-</html>
diff --git a/development/news/1.0M4.html b/development/news/1.0M4.html
deleted file mode 100644
index e27112d..0000000
--- a/development/news/1.0M4.html
+++ /dev/null
@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<head>
-<title>WTP 1.0 M4 News</title>
-<link type="text/css" rel="stylesheet" href="default_style.css">
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-</head>
-<body>
-<table>
- <tbody valign="top">
- <tr>
- <td>
- <h1>WTP 1.0 M4 - New and Noteworthy</h1>
-
- <p>This milestone release of WTP is a major milestone in respects to
- new function provided and final API definition for the Web Tools
- Platform's 1.0 release. Here are some of the more noteworthy features
- available in milestone build M4 (April. 29, 2005) which is now
- available for download <a
- href="http://download.eclipse.org/webtools/downloads/drops/S-1.0M4-200504292037/">
- here</a>.
-
- <!--
- See the <a
- href="http://download.eclipse.org/webtools/downloads/drops/S-1.0M4-200504292037/buildNotes.php">
- M4 build notes</a> for details about bugs fixed and other changes.
- -->
- </p>
- </td>
- <td align="right"><img src="../../../images/Idea.jpg"
- alt="Idea image"></td>
- </tr>
- </tbody>
-</table>
-<p></p>
-<blockquote>
-<ul>
- <li><a href="../../jst/components/j2ee/M4/news/j2ee-news-m4.html">J2EE and Validation</a></li>
- <li><a href="../../wst/components/sse/M4/news/sse-m4.html">Structured Source Editing</a></li>
- <li><a href="../../wst/components/server/0.7/M4/news/server-m4.html">Server Tools</a></li>
- <li><a href="../../wst/components/xml/M4/new_and_noteworthy/xml-m4.html">XML, XSD, and WSDL</a></li>
- <li><a href="../../jst/components/ws/M4/news/jst-ws-m4news.html">Web Services Tools</a></li>
-</ul>
-
-</blockquote>
-
-<p>The above features are just the ones that are new since the previous
-milestone build. Summaries for earlier 1.0 milestone builds:</p>
-
-<ul>
- <li><a href="1.0M3.html">New for WTP milestone build M3 (February 25, 2005)</a></li>
- <li><a href="1.0M2.html">New for WTP milestone build M2 (December 23, 2004)</a></li>
-</ul>
-</body>
-</html>
-
diff --git a/development/news/1.0M8.html b/development/news/1.0M8.html
deleted file mode 100644
index 48a060e..0000000
--- a/development/news/1.0M8.html
+++ /dev/null
@@ -1,78 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<head>
-<title>WTP 1.0 M8 News</title>
-<link type="text/css" rel="stylesheet" href="default_style.css">
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-</head>
-<body>
-<table>
- <tbody valign="top">
- <tr>
- <td>
- <h1>WTP 1.0 M8 - New and Noteworthy</h1>
-
- <p>Here are some of the more noteworthy features
- available in WTP 1.0 M8 (September 23, 2005), which is now
- available for download <a
- href="http://download.eclipse.org/webtools/downloads/drops/S-1.0M8-200509230840/">
- here</a>
-
- </p>
- </td>
- <td align="right"><img src="../../../images/Idea.jpg"
- alt="Idea image"></td>
- </tr>
- </tbody>
-</table>
-<p></p>
-
-<!-- N&N are now separated by component instead of by teams and thus shouldn't link to each other -->
-
-<blockquote>
-<h3>New and Noteworthy in WST</h3>
-<ul>
- <!-- <li><a href="../../wst/components/command/M8/new_and_noteworthy/command-news-M8.html">Command</a></li> -->
- <!-- <li><a href="../../wst/components/common/M8/new_and_noteworthy/common-news-M8.html">Common</a></li> -->
- <!-- <li><a href="../../wst/components/css/M8/new_and_noteworthy/css-news-M8.html">CSS</a></li> -->
- <!-- <li><a href="../../wst/components/dtd/M8/new_and_noteworthy/dtd-news-M8.html">DTD</a></li> -->
- <!-- <li><a href="../../wst/components/html/M8/new_and_noteworthy/html-news-M8.html">HTML</a></li> -->
- <!-- <li><a href="../../wst/components/internet/M8/new_and_noteworthy/internet-news-M8.html">Internet</a></li> -->
- <!-- <li><a href="../../wst/components/javascript/M8/new_and_noteworthy/javascript-news-M8.html">Javascript</a></li> -->
- <!-- <li><a href="../../wst/components/rdb/M8/new_and_noteworthy/rdb-news-M8.html">Relational Database Tools</a></li> -->
- <!-- <li><a href="../../wst/components/server/M8/new_and_noteworthy/server-news-M8.html">Server Tools</a></li> -->
- <!-- <li><a href="../../wst/components/sse/M8/new_and_noteworthy/sse-news-M8.html">Structured Source Editing</a></li> -->
- <!-- <li><a href="../../wst/components/validation/M8/new_and_noteworthy/validation-news-M8.html">Validation</a></li> -->
- <!-- <li><a href="../../wst/components/web/M8/new_and_noteworthy/web-news-M8.html">Web</a></li> -->
- <!-- <li><a href="../../wst/components/ws/M8/new_and_noteworthy/ws-news-M8.html">Web Services Tools</a></li> -->
- <!-- <li><a href="../../wst/components/wsdl/M8/new_and_noteworthy/wsdl-news-M8.html">WSDL Tools</a></li> -->
- <!-- <li><a href="../../wst/components/wsi/M8/new_and_noteworthy/wsi-news-M8.html">WS-I Tools</a></li> -->
- <!-- <li><a href="../../wst/components/xml/M8/new_and_noteworthy/xml-news-M8.html">XML</a></li> -->
- <!-- <li><a href="../../wst/components/xsd/M8/new_and_noteworthy/xsd-news-M8.html">XSD</a></li> -->
-</ul>
-<h3>New and Noteworthy in JST</h3>
-<ul>
- <!-- <li><a href="../../jst/components/common/M8/new_and_noteworthy/common-news-M8.html">Common</a></li> -->
- <!-- <li><a href="../../jst/components/ejb/M8/new_and_noteworthy/ejb-news-M8.html">EJB Tools</a></li> -->
- <!-- <li><a href="../../jst/components/j2ee/M8/news/j2ee-news-M8.html">J2EE Tools</a></li> -->
- <!-- <li><a href="../../jst/components/jsp/M8/new_and_noteworthy/jsp-news-M8.html">JSP</a></li> -->
- <li><a href="../../jst/components/server/M8/new_and_noteworthy/server-M8.html">Server Tools</a></li>
- <!-- <li><a href="../../jst/components/servlet/M8/new_and_noteworthy/servlet-news-M8.html">Servlet Tools</a></li> -->
- <li><a href="../../jst/components/ws/1.0M8/news/jst-ws-1.0M8news.html">Web Services Tools</a></li>
-</ul>
-</blockquote>
-<p></p>
-<p>You can also look at which <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&target_milestone=1.0+M8&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&resolution=FIXED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">bugs were fixed</a> during this milestone.</p>
-<p>The above features are just the ones that are new since the previous
-milestone build. Summaries for earlier milestone builds:</p>
-<ul>
- <li><a href="0.7.html">New for WTP 0.7 (July 29, 2005)</a></li>
- <li><a href="0.7M5.html">New for WTP milestone build 0.7 M5 (July 1, 2005)</a></li>
- <li><a href="1.0M4.html">New for WTP milestone build 0.7 M4 (April 29, 2005)</a></li>
- <li><a href="1.0M3.html">New for WTP milestone build 0.7 M3 (February 25, 2005)</a></li>
- <li><a href="1.0M2.html">New for WTP milestone build 0.7 M2 (December 23, 2004)</a></li>
-</ul>
-</body>
-</html>
-
diff --git a/development/news/default_style.css b/development/news/default_style.css
deleted file mode 100644
index 2d41e87..0000000
--- a/development/news/default_style.css
+++ /dev/null
@@ -1,15 +0,0 @@
-p, table, td, th { font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre { font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code { font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup { font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 { font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li { font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 { font-family: verdana, arial, helvetica, geneva; font-size: 28px; font-weight: bold}
-body { font-family: verdana, arial, helvetica, geneva; font-size: 10pt; clip: rect( ); margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large;; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small;; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link { text-decoration: none; color: #FFFFFF}
-a.bar:visited { color: #FFFFFF; text-decoration: none}
-a.bar:hover { color: #FFFFFF; text-decoration: underline}
-a.bar { color: #FFFFFF}
diff --git a/development/news/geronimo.html b/development/news/geronimo.html
deleted file mode 100644
index 2faec3f..0000000
--- a/development/news/geronimo.html
+++ /dev/null
@@ -1,12 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
-<meta http-equiv="Refresh" content="5; URL=http://www.eclipse.org/webtools/jst/components/server/M4/news/geronimo.html" />
-<link rel="stylesheet" href="../../../default_style.css" type="text/css" />
-<link rel="stylesheet" href="../../../webtools/wtp.css" type="text/css" />
-<title>Eclipse Web Tools Platform - Apache Geronimo Server Adapter</title>
-</head>
-<body>
-The detailed announcement for the Apache Geronimo server adapter has been moved. You will be redirected to its new and permanent location at <a href="http://www.eclipse.org/webtools/jst/components/server/M4/news/geronimo.html">http://www.eclipse.org/webtools/jst/components/server/M4/news/geronimo.html</a> within 10 seconds.
-</body>
-</html>
diff --git a/development/news/index.html b/development/news/index.html
deleted file mode 100644
index 67c29c3..0000000
--- a/development/news/index.html
+++ /dev/null
@@ -1,29 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
- "http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<head>
-<title>Web Tools Platform New and Noteworthy</title>
-<link rel="stylesheet" href="default_style.css" />
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/ >
-<meta name="GENERATOR" content="WTP HTML Source Editor" />
-</head>
-<body>
-<h1>WTP - New and Noteworthy</h1>
-<p>
-<blockquote>
-<ul>
- <li><a href="0.7M5.html">New for WTP 0.7 milestone build M5 (July 31, 2005)</a></li>
- <li><a href="1.0M4.html">New for WTP 1.0 milestone build M4 (April 29, 2005)</a></li>
- <li><a href="1.0M3.html">New for WTP 1.0 milestone build M3 (February 25, 2005)</a></li>
- <li><a href="1.0M2.html">New for WTP 1.0 milestone build M2 (December 23, 2004)</a></li>
-</ul>
-
-<!--
-<ul>
- <li><a href="releaseNotes.html">WTP Release Notes</a></li>
-</ul>
--->
-</blockquote>
-</p>
-</body>
-</html>
diff --git a/development/news/releaseNotes.html b/development/news/releaseNotes.html
deleted file mode 100644
index 0bf4798..0000000
--- a/development/news/releaseNotes.html
+++ /dev/null
@@ -1,48 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../..//default_style.css" type="text/css">
-<link rel="stylesheet" href="../../..//webtools/wtp.css" type="text/css">
-<title>Release Notes</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">WTP Release Notes</font>
-<br>
-<font class="indexsub">Release Notes</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../..//images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">M3</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<ul>
-
-<li>The Flexible Project Structure framework/tooling/api released in M3 is experimental and not gone through a lot of testing. It is only available on web modules. It will be refined and made enabled on other J2EE modules in M4. </li>
-
-<li>For EJB 2.0 project creation the optional web services jars available on the M3 build page are required.</li>
-
-<li>The JBOSS server version supported in M3 is JBOSS 3.2.3</li>
-
-<li>The JOnAS server version supported in M3 is JOnAS 4.1.4</li>
-
-</ul>
-
-</p>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/development/news/releaseNotes.xml b/development/news/releaseNotes.xml
deleted file mode 100644
index da0a9e6..0000000
--- a/development/news/releaseNotes.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?xml-stylesheet type="text/xsl" href="../../wtp.xsl"?>
-<html>
- <head>
- <meta name="root" content="../../../" />
- <title>Release Notes</title>
- </head>
-
- <body>
- <h1>WTP Release Notes</h1>
-
- <h2>M3</h2>
- <p>
- <ul>
- <li>The Flexible Project Structure framework/tooling/api released in M3 is experimental and not gone through a lot of testing. It is only available on web modules. It will be refined and made enabled on other J2EE modules in M4. </li>
- <li>For EJB 2.0 project creation the optional web services jars available on the M3 build page are required.</li>
- <li>The JBOSS server version supported in M3 is JBOSS 3.2.3</li>
- <li>The JOnAS server version supported in M3 is JOnAS 4.1.4</li>
- </ul>
- </p>
- </body>
-</html>
\ No newline at end of file
diff --git a/development/piitools/figure01.gif b/development/piitools/figure01.gif
deleted file mode 100644
index 5b5d3ec..0000000
--- a/development/piitools/figure01.gif
+++ /dev/null
Binary files differ
diff --git a/development/piitools/figure02.gif b/development/piitools/figure02.gif
deleted file mode 100644
index 58a5ee5..0000000
--- a/development/piitools/figure02.gif
+++ /dev/null
Binary files differ
diff --git a/development/piitools/piitools.html b/development/piitools/piitools.html
deleted file mode 100644
index 9f56e37..0000000
--- a/development/piitools/piitools.html
+++ /dev/null
@@ -1,75 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../webtools/wtp.css" type="text/css">
-<title>PII tools</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">PII tools</font>
-<br>
-<font class="indexsub">PII tools</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><em>Updated 2005-04-07</em></td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Downloading and running the check unused properties tool</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-A binary version of the tool is available
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/checkUnusedProperties.zip">here</a>.
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-The source is also available in
-<a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.wtp.releng/piitools/org.eclipse.wtp.releng.tools.pii.ui/?cvsroot=WebTools_Project">CVS</a>.
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-To run this tool:
-<ol>
-
-<li>Unzip checkUnusedProperties.zip to your Eclipse installation directory.</li>
-
-<li>Restart your workbench with the -consoleLog option.</li>
-
-<li>Click on the scan properties toolbar icon.
- <p>
-<img src="figure01.gif"></p>
-
-</li>
-
-<li>Check the console for results.
- <p>
-<img src="figure02.gif"></p>
-
-</li>
-
-</ol>
-
-</p>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/development/piitools/piitools.xml b/development/piitools/piitools.xml
deleted file mode 100644
index 4019941..0000000
--- a/development/piitools/piitools.xml
+++ /dev/null
@@ -1,39 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<?xml-stylesheet type="text/xsl" href="../../wtp.xsl"?>
-<html>
-<head>
- <title>PII tools</title>
- <meta name="root" content="../../.." />
-</head>
-<body>
-
-<h1>PII tools</h1>
-<em>Updated 2005-04-07</em>
-
-<h2>Downloading and running the check unused properties tool</h2>
-<p>
-A binary version of the tool is available
-<a href="http://www.eclipse.org/downloads/download.php?file=/webtools/downloads/checkUnusedProperties.zip">here</a>.
-</p>
-
-<p>
-The source is also available in
-<a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.wtp.releng/piitools/org.eclipse.wtp.releng.tools.pii.ui/?cvsroot=WebTools_Project">CVS</a>.
-</p>
-
-<p>
-To run this tool:
-<ol>
- <li>Unzip checkUnusedProperties.zip to your Eclipse installation directory.</li>
- <li>Restart your workbench with the -consoleLog option.</li>
- <li>Click on the scan properties toolbar icon.
- <p><img src="figure01.gif"/></p>
- </li>
- <li>Check the console for results.
- <p><img src="figure02.gif"/></p>
- </li>
-</ol>
-</p>
-
-</body>
-</html>
diff --git a/development/planning/default_style.css b/development/planning/default_style.css
deleted file mode 100644
index e26fec7..0000000
--- a/development/planning/default_style.css
+++ /dev/null
@@ -1,18 +0,0 @@
-p, table, td, th { font-family: arial, helvetica, geneva; font-size: 10pt}
-pre { font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code { font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup { font-family: arial,helvetica,geneva; font-size: 10px}
-h3 { font-family: arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li { font-family: arial, helvetica, geneva; font-size: 10pt}
-h1 { font-family: arial, helvetica, geneva; font-size: 28px; font-weight: bold}
-body { font-family: arial, helvetica, geneva; font-size: 10pt; clip: rect( ); margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large;; font-family: Verdana, Arial, Helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small;; font-family: Arial, Helvetica, sans-serif; color: #8080FF}
-a.bar:link { text-decoration: none; color: #FFFFFF}
-a.bar:visited { color: #FFFFFF; text-decoration: none}
-a.bar:hover { color: #FFFFFF; text-decoration: underline}
-a.bar { color: #FFFFFF}
-.jump { font-size: smaller;; font-family: Arial, Helvetica, sans-serif; color: #8080FF ; font-style: normal; text-decoration: none}
-.jump:link { font-size: smaller;; font-family: Arial, Helvetica, sans-serif; color: #8080FF; text-decoration: none}
-.jump:hover { font-size: smaller;; font-family: Arial, Helvetica, sans-serif; color: #0000FF; text-decoration: underline; font-style: normal}
diff --git a/development/planning/milestone-content.html b/development/planning/milestone-content.html
deleted file mode 100644
index fa15d5b..0000000
--- a/development/planning/milestone-content.html
+++ /dev/null
@@ -1,207 +0,0 @@
-<html>
-<head>
- <meta http-equiv="Content-Type"
- content="text/html; charset=iso-8859-1">
- <title>eclipse webtools milestone content</title>
- <link rel="stylesheet" href="../../../default_style.css" type="text/css">
-</head>
-<body text="#000000" bgcolor="#ffffff" link="#0000ee" vlink="#551a8b"
- alink="#ff0000">
-
-<table border="0" cellspacing="5" cellpadding="2" width="100%">
- <tbody>
- <tr>
- <td align="left" width="60%">
- <font class="indextop">eclipse webtools milestone content</font><br>
- <font class="indexsub">the eclipse web tools platform project milestone content</font>
- </td>
- <td width="40%"><img src="../../../images/Idea.jpg" hspace="50" height="86" width="120" align="middle"></td>
- </tr>
- </tbody>
-</table>
-
-<table border="0" cellspacing="5" cellpadding="2" width="100%">
- <tbody>
- <tr>
- <td align="left" valign="top" colspan="2" bgcolor="#0080c0">
- <b><font color="#ffffff" face="Arial,Helvetica">Status of this Document</font></b>
- </td>
- </tr>
-
- <tr>
- <td align="right" valign="top"> </td>
- <td>
-This is a preliminary plan. It is undergoing review and change.
-It includes initial ideas for the following Milestones:
-</td>
- </tr>
-
- <tr>
- <td align="right" valign="top"><img src="../../../images/Adarrow.gif" width="16" height="16" border="0"></td>
- <td><b><a href="#M0">M0</a></b><br>
-Initial CVS module structure, build infrastructure, and Server Tools.</td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../../images/Adarrow.gif" width="16" height="16" border="0"></td>
- <td><b><a href="#M1">M1</a></b><br>
-Finalize build infrastructure and Server Tools.</td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../../images/Adarrow.gif" width="16" height="16" border="0"></td>
- <td><a href="#M2"><b>M2</b></a><br>
-Flexible project layout. Initial Structured Source Editing and EJB Tools.</td>
- </tr>
-
- <tr>
- <td align="left" valign="top" colspan="2" bgcolor="#0080c0"><b><font face="Arial,Helvetica">
- <font color="#ffffff"><a name="M0">M0</a></font></font></b></td>
- </tr>
-
-<tr>
- <td> </td>
- <td>
-The goal of M0 is to create the initial CVS module structure and to populate it with the Server Tools.
-This allows us to verify our build infrastructure and enables us to begin the creation of
-server adapters.
-</td>
-</tr>
-
-<tr>
- <td> </td>
- <td>
-<b>High Priority</b>
-<br>
-<ul>
-<li>Create and commit initial CVS module structure</li>
-<li>Commit Server Tools into CVS</li>
-<li>Run the first public automatic build</li>
-<li>Update website with downloads/what's new links (ala EMF)</li>
-</ul>
-
- </td>
-</tr>
-
- <tr>
- <td align="left" valign="top" colspan="2" bgcolor="#0080c0"><b><font face="Arial,Helvetica">
- <font color="#ffffff"><a name="M1">M1</a></font></font></b></td>
- </tr>
-
-<tr>
- <td> </td>
- <td>
-<b>High Priority</b>
-<br>
-<ul>
-<li>Finalize WTP Build Infrastructure</li>
- <ul>
- <li>Run report automatic builds/tests</li>
- <li>CVS structure</li>
- <li>Updating web site with build info automatically (what's new etc.)</li>
- </ul>
-<li>Server Runtime Support for Tomcat</li>
- <ul>
- <li>Launch Server (Start) (In debug ro run modes)</li>
- <li>Be able to run (and debug) Java Servlet</li>
- <li>Stop Server</li>
- </ul>
-</ul>
- </td>
-</tr>
-
-
-<tr>
- <td> </td>
- <td>
-<b>Medium Priority</b>
-<br>
-<ul>
-<li>Integrate Lomboz Generic Server Runtime Support using XML Server Definitions (JBoss, Jonas)</li>
- <ul>
- <li>Launch Server (Start) (In debug and run modes)</li>
- <li>Stop Server</li>
- </ul>
-<li>"Run on server" for Web artifacts (e.g. .html)</li>
- <ul>
- <li>Start server</li>
- <li>Display in IDE browser</li>
- </ul>
- </ul>
- </td>
-</tr>
-
-<tr>
- <td> </td>
- <td>
-
-<b>Low Priority</b>
-<br>
-<ul>
-<li>Apache server adapter</li>
- <ul>
- <li>Add/remove Web project to configuration</li>
- <li>Start and stop server</li>
- <li>"Run on server" for Web artifacts (e.g. .html)</li>
- </ul>
-</ul>
- </td>
-</tr>
-
- <tr>
- <td align="left" valign="top" colspan="2" bgcolor="#0080c0"><b><font face="Arial,Helvetica">
- <font color="#ffffff"><a name="M2">M2</a></font></font></b></td>
- </tr>
-
-<tr>
- <td> </td>
- <td>
-<b>High Priority</b>
-<br>
-<ul>
-<li>Project Layouts for Web Modules (WARs or Web Project in IBM contributions)</li>
- <ul>
- <li>Simple Web project layouts</li>
- <li>Flexible project layouts, i.e. (One project for many web modules, Maven)</li>
- </ul>
-<li>Structured Source Editor</li>
- <ul>
- <li>Simple JSP Editing (which, by implication pulls in some amount of XML, HTML, CSS, JavaScript)</li>
- <li>Set breakpoints</li>
- </ul>
-<li>Debug JSP</li>
- <ul>
- <li>JSR 45</li>
- </ul>
-<li>Medium Priority Items from M1</li>
- <ul>
- <li>Integrate Lomboz Generic Server Runtime Support using XML Server Definitions (JBoss, Jonas)</li>
- <li>"Run on server" for Web artifacts (e.g. .html)</li>
- </ul>
-</ul>
- </td>
-</tr>
-
-<tr>
- <td> </td>
- <td>
-<b>Medium Priority</b>
-<br>
-<ul>
-<li>EJB Wizards</li>
- <ul>
- <li>Simple EJB Wizards to generate annotated Java Sources from templates</li>
- <li>Session Beans only</li>
- </ul>
-</ul>
- </td>
-</tr>
-</tbody>
-</table>
-<br>
-<p>Please see our <a href="/legal/privacy.html">privacy policy</a> and website <a href="/legal/termsofuse.html">terms
- of use</a>.
-For problems with the eclipse.org site, please contact the <a href="mailto:webmaster@eclipse.org">webmaster</a>
- or read the <a href="/webmaster/index.html">webmaster FAQ</a> for answers to
- common questions!</p>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/development/planning/milestone_plan_1_0-new.html b/development/planning/milestone_plan_1_0-new.html
deleted file mode 100644
index 3212e1f..0000000
--- a/development/planning/milestone_plan_1_0-new.html
+++ /dev/null
@@ -1,883 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
- <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
- <TITLE>eclipse WTP milestone plan (Draft)</TITLE>
- <META NAME="GENERATOR" CONTENT="Microsoft FrontPage 5.0">
- <META NAME="CREATED" CONTENT="20040920;14213332">
- <META NAME="CHANGEDBY" CONTENT="D D">
- <META NAME="CHANGED" CONTENT="20040928;14404493">
- <link rel="stylesheet" href="../../../default_style.css" type="text/css">
-
-</HEAD>
-<BODY LANG="fr-FR" TEXT="#000000" LINK="#0000ee" VLINK="#551a8b" BGCOLOR="#ffffff" DIR="LTR">
-<TABLE WIDTH=100% BORDER=0 CELLPADDING=2 CELLSPACING=5 STYLE="page-break-before: always">
- <TR>
- <TD WIDTH=60%>
- <P ALIGN=LEFT><B><FONT SIZE=6><FONT FACE="Verdana, Arial, Helvetica, sans-serif">eclipse
- WTP milestone plan (Draft)</FONT></FONT></B><BR><FONT SIZE=1><FONT FACE="Arial, Helvetica, sans-serif"><FONT COLOR="#8080ff">the
- eclipse web tools platform project milestone content</FONT></FONT></FONT>
- </P>
- </TD>
- <TD WIDTH=40%>
-
- <P><IMG SRC="http://www.eclipse.org/images/Idea.jpg" NAME="Image1" ALIGN=MIDDLE HSPACE=50 WIDTH=120 HEIGHT=86 BORDER=0></P>
- </TD>
- </TR>
-</TABLE>
-<TABLE WIDTH=100% BORDER=0 CELLPADDING=2 CELLSPACING=0>
- <COL WIDTH=7*>
- <COL WIDTH=249*>
- <TR>
- <TD COLSPAN=2 WIDTH=100% VALIGN=TOP BGCOLOR="#0080c0">
-
- <P ALIGN=LEFT><B><FONT FACE="Arial, Helvetica"><FONT COLOR="#ffffff">Status
- of this Document</FONT></FONT></B>
- </P>
-
- </TD>
- </TR>
- <TR>
- <TD WIDTH=3% VALIGN=TOP>
- <P ALIGN=RIGHT> </P>
- </TD>
-
- <TD WIDTH=97%>
- <P>This is a preliminary plan. It is undergoing review and change.
- It includes initial ideas for the following Milestones:
- </P>
-
- </TD>
- </TR>
- <TR>
- <TD WIDTH=3% VALIGN=TOP>
- <P ALIGN=RIGHT><IMG SRC="http://www.eclipse.org/images/Adarrow.gif" NAME="Image2" ALIGN=BOTTOM WIDTH=16 HEIGHT=16 BORDER=0></P>
-
- </TD>
-
- <TD WIDTH=97%>
- <P><A HREF="#M0"><B>M0</B></A><BR>Initial CVS module structure,
- build infrastructure, and Server Tools.</P>
-
- </TD>
- </TR>
- <TR>
- <TD WIDTH=3% VALIGN=TOP>
-
- <P ALIGN=RIGHT><IMG SRC="http://www.eclipse.org/images/Adarrow.gif" NAME="Image3" ALIGN=BOTTOM WIDTH=16 HEIGHT=16 BORDER=0></P>
-
- </TD>
- <TD WIDTH=97%>
- <P><A HREF="#M1"><B>M1</B></A> - <span lang="en-us">completed </span>October 15<BR>Finalize build infrastructure
- and Server Tools.</P>
-
- </TD>
-
- </TR>
- <TR>
-
- <TD WIDTH=3% VALIGN=TOP bgcolor="#CCFFFF">
- <P ALIGN=RIGHT><IMG SRC="http://www.eclipse.org/images/Adarrow.gif" NAME="Image4" ALIGN=BOTTOM WIDTH=16 HEIGHT=16 BORDER=0></P>
- </TD>
- <TD WIDTH=97% bgcolor="#CCFFFF">
- <P><A HREF="#M2"><B>M2</B></A> - December <span lang="en-us">22</span><BR>Flexible
- project layout. Initial Structured Source Editing and EJB Tools.<span lang="en-us">
- Will be based on 3.1M4.</span></P>
-
- </TD>
-
- </TR>
- <TR>
- <TD WIDTH=3% VALIGN=TOP>
- <P ALIGN=RIGHT><IMG SRC="http://www.eclipse.org/images/Adarrow.gif" NAME="Image4" ALIGN=BOTTOM WIDTH=16 HEIGHT=16 BORDER=0></P>
- </TD>
- <TD WIDTH=97%>
- <P><A HREF="#M3"><B>M3</B></A> - February <span lang="en-us">25</span><BR>Improved
- Structured Source Editing and EJB Tools. Database Tools and
- Initial Web Services.<span lang="en-us"> Will be based on 3.1M5.</span></P>
-
- </TD>
- </TR>
-
-
- <TR>
- <TD WIDTH=3% VALIGN=TOP>
- <P ALIGN=RIGHT><IMG SRC="http://www.eclipse.org/images/Adarrow.gif" NAME="Image4" ALIGN=BOTTOM WIDTH=16 HEIGHT=16 BORDER=0></P>
- </TD>
- <TD WIDTH=97%>
- <P><A HREF="#M4"><B>M4</B></A> - April <span lang="en-us">8</span><BR>More efficient tools
- and more about Web Services.
- <span lang="en-us"> Will be based on 3.1M6.</span></P>
-
- </TD>
- </TR>
-
- <TR>
- <TD WIDTH=3% VALIGN=TOP>
- <P ALIGN=RIGHT><IMG SRC="http://www.eclipse.org/images/Adarrow.gif" NAME="Image4" ALIGN=BOTTOM WIDTH=16 HEIGHT=16 BORDER=0></P>
- </TD>
- <TD WIDTH=97%>
- <P><A HREF="#M5"><B>M5</B></A> - one week after 3.1M7 release (end of May)<BR>
- <span lang="en-us"> Will be based on 3.1M7.</span></P>
-
- </TD>
- </TR>
-
- <TR>
- <TD COLSPAN=2 WIDTH=100% VALIGN=TOP BGCOLOR="#0080c0">
- <P ALIGN=LEFT><A NAME="M0"><FONT COLOR="#ffffff"><FONT FACE="Arial, Helvetica"><B>M0</B></FONT></FONT></A></P>
- </TD>
- </TR>
- <TR>
-
- <TD WIDTH=3%>
- <P> </P>
- </TD>
- <TD WIDTH=97%>
- <P>The goal of M0 is to create the initial CVS module structure
- and to populate it with the Server Tools. This allows us to verify
- our build infrastructure and enables us to begin the creation of
- server adapters.
- </P>
- </TD>
- </TR>
- <TR>
-
- <TD WIDTH=3%>
- <P> </P>
- </TD>
- <TD WIDTH=97%>
- <P><B>High Priority</B>
- </P>
- <UL>
- <LI>Create and commit initial CVS
- module structure
- <LI>Commit Server Tools into CVS
- <LI>Run the first public automatic
- build
- <LI>Update website with downloads/what's new links (ala EMF)
-
- </UL>
-
- </TD>
- </TR>
- <TR>
- <TD COLSPAN=2 WIDTH=100% VALIGN=TOP BGCOLOR="#0080c0">
- <P ALIGN=LEFT><A NAME="M1"><FONT COLOR="#ffffff"><FONT FACE="Arial, Helvetica"><B>M1</B></FONT></FONT></A></P>
- </TD>
- </TR>
- <TR>
-
- <TD WIDTH=3%>
- <P> </P>
- </TD>
- <TD WIDTH=97%>
- <P>M1 <span lang="en-us">was completed</span> October 15
- </P>
- </TD>
-
- </TR>
- <TR>
-
- <TD WIDTH=3%>
- <P> </P>
- </TD>
- <TD WIDTH=97%>
- <P><B>High Priority</B>
- </P>
-
- <UL>
- <LI>Finalize WTP Build
- Infrastructure
-
- <UL>
-
- <LI>Run report automatic
- builds/tests
-
- <LI>CVS structure
-
- <LI>Updating web site with build
- info automatically (what's new etc.)
-
- </UL>
- <LI>Server Runtime Support for
- Tomcat
-
- <UL>
- <LI>Launch Server (Start) (In
- debug ro run modes)
-
- <LI>Be able to run (and debug)
- Java Servlet
-
- <LI>Stop Server
-
- </UL>
-
- </UL>
- </TD>
-
- </TR>
- <TR>
- <TD WIDTH=3%>
- <P> </P>
- </TD>
- <TD WIDTH=97%>
-
- <P><B>Medium Priority</B>
- </P>
-
- <UL>
-
- <LI>Integrate Lomboz Generic Server
- Runtime Support using XML Server Definitions (JBoss, JOnAS)
-
- <UL>
- <LI>Launch Server (Start) (In
- debug and run modes)
-
- <LI>Stop Server
-
- </UL>
- <LI>"Run on server" for
- Web artifacts (e.g. .html)
-
- <UL>
-
- <LI>Start server
-
- <LI>Display in IDE browser
-
- </UL>
-
- </UL>
-
- </TD>
- </TR>
- <TR>
- <TD WIDTH=3%>
- <P> </P>
-
- </TD>
- <TD WIDTH=97%>
-
- <P><B>Low Priority</B>
- </P>
-
- <UL>
- <LI>Apache server adapter
-
- <UL>
- <LI>Add/remove Web project to
- configuration
-
- <LI>Start and stop server
-
- <LI>"Run on server" for Web artifacts (e.g. .html)
-
- </UL>
-
- </UL>
- </TD>
- </TR>
-
- <TR>
- <TD COLSPAN=2 WIDTH=100% VALIGN=TOP BGCOLOR="#0080c0">
- <P ALIGN=LEFT><A NAME="M2"><FONT COLOR="#ffffff"><FONT FACE="Arial, Helvetica"><B>M2</B></FONT></FONT></A></P>
- </TD>
-
- </TR>
-
- <TR>
-
- <TD WIDTH=3% bgcolor="#CCFFFF">
- <P> </P>
- </TD>
- <TD WIDTH=97% bgcolor="#CCFFFF">
- <P>M2 is expected for December <span lang="en-us">22 and will be
- based on the Platform 3.1M4</span>
- </P>
-
- </TD>
- </TR>
-
- <TR>
- <TD WIDTH=3% bgcolor="#CCFFFF">
- <P> </P>
-
- </TD>
- <TD WIDTH=97% bgcolor="#CCFFFF">
- <P><B>High Priority</B>
- </P>
-
- <UL>
-
- <LI>Project Layouts for Web/J2EE
- Modules
-
- <UL>
- <LI>Simple Web/J2EE project
- layouts
-
- </UL>
- <LI>Structured Source Editor
-
- <UL>
-
- <LI>XML Editing
-
- </UL>
- <LI>Database Tool
- <UL>
-
- <LI>Table content browsing
- </UL>
-
- <LI>Medium Priority Items from M1
-
- <UL>
- <LI>Integrate Lomboz Generic
- Server Runtime Support using XML Server Definitions (JBoss,
- JOnAS)
-
- <LI>"Run on server" for Web artifacts (e.g. .html)
-
- </UL>
-
- </UL>
- </TD>
-
- </TR>
- <TR>
-
- <TD WIDTH=3% bgcolor="#CCFFFF">
- <P> </P>
- </TD>
- <TD WIDTH=97% bgcolor="#CCFFFF">
- <P><B>Medium Priority</B>
- </P>
-
- <UL>
- <LI>Structured Source Editor
-
- <UL>
-
- <LI>Simple JSP Editing (which, by
- implication pulls in some amount of XML, HTML, CSS, JavaScript)
-
- <LI>Set breakpoints
-
- </UL>
- <LI>Debug JSP
-
- <UL>
- <LI>JSR 45
- </UL>
-
- <LI>EJB Wizards
-
- <UL>
-
- <LI>Simple EJB Wizards to generate
- annotated Java Sources from templates
- <LI>Session Beans only
- </UL>
-
- </UL>
- </TD>
- </TR>
-</TABLE>
-<TABLE WIDTH=100% BORDER=0 CELLPADDING=2 CELLSPACING=0>
-
- <COL WIDTH=7*>
- <COL WIDTH=249*>
- <TR>
-
- <TD COLSPAN=2 WIDTH=100% VALIGN=TOP BGCOLOR="#0080c0">
-
- <P ALIGN=LEFT><A NAME="M3"><FONT COLOR="#ffffff"><FONT FACE="Arial, Helvetica"><B>M3</B></FONT></FONT></A></P>
- </TD>
- </TR>
-
- <TR>
-
- <TD WIDTH=3%>
- <P> </P>
- </TD>
- <TD WIDTH=97%>
-
- <P>M3 is expected for February <span lang="en-us">25 and will be
- based on the Platform 3.1M5</span>
- </P>
-
- </TD>
- </TR>
- <TR>
- <TD WIDTH=3%>
- <P> </P>
- </TD>
-
- <TD WIDTH=97%>
-
- <P><B>High Priority</B>
- </P>
-
- <UL>
- <LI>Project Layouts for Web/J2EE
- Modules
-
- <UL>
- <LI>Complex Web/J2EE project
- layouts
- <LI>Flexible project layouts, i.e.
- (One project for many web modules, Maven style)
- </UL>
- <LI>Web Services
-
- <UL>
- <LI>Axis adapter
- <LI>Develop a Web Service based on
- Session Beans
- <LI>Develop a Web Service based on
- JavaBeans
- <LI>Create Web Service Clients
- <LI><FONT COLOR="#E00000">Deployment of Web Services</FONT>
- </UL>
-
- <LI>Medium Priority Items from M2
- <UL>
- <LI>Structured Source Editor
-
- <UL>
- <LI>Simple JSP Editing (which, by
- implication pulls in some amount of XML, HTML, CSS, JavaScript)
-
- <LI>Set breakpoints
-
- </UL>
-
- <LI>Debug JSP
-
- <UL>
- <LI>JSR 45
-
- </UL>
-
- <LI>EJB Wizards
-
- <UL>
- <LI>Simple EJB Wizards to
- generate annotated Java Sources from templates
-
- <LI>Session Beans only
-
- </UL>
- </UL>
- </UL>
-
- </TD>
- </TR>
- <TR>
-
- <TD WIDTH=3%>
- <P> </P>
- </TD>
- <TD WIDTH=97%>
- <P><B>Medium Priority</B>
- </P>
-
- <UL>
- <LI>EJB Wizards
-
- <UL>
-
- <LI>EJB Wizards to generate
- annotated Java Sources from templates
- <LI>All EJB types
- </UL>
- <LI>XQuery editor
- <LI>Database Tool
- <UL>
- <LI>SQL Query graphical editor
-
- </UL>
-
- <LI>Web Services
- <UL>
-
- <LI><FONT COLOR="#E00000">UDDI registry adapter</FONT>
- <LI><STRIKE><FONT COLOR="#E00000">Develop and</FONT></STRIKE> publish WSDL
- schema on UDDI registries (<FONT COLOR="#E00000">remove as WSDL editor should be based on schema editor, present from M4 only</FONT>)
- <LI>Test Web services for WS-I compliance
-
- </UL>
-
- </UL>
- </TD>
- </TR>
- <TR>
- <TD WIDTH=3%>
-
- <P><BR>
- </P>
-
- </TD>
-
- <TD WIDTH=97%>
- <P><BR>
- </P>
- </TD>
- </TR>
-
-</TABLE>
-
-
-
-
-
-
-
-
-
-
-
-<TABLE WIDTH=100% BORDER=0 CELLPADDING=2 CELLSPACING=0>
-
- <COL WIDTH=7*>
- <COL WIDTH=249*>
- <TR>
-
- <TD COLSPAN=2 WIDTH=100% VALIGN=TOP BGCOLOR="#0080c0">
-
- <P ALIGN=LEFT><A NAME="M4"><FONT COLOR="#ffffff"><FONT FACE="Arial, Helvetica">
- <B>M4</B></FONT></FONT></A></P>
- </TD>
- </TR>
-
- <TR>
-
- <TD WIDTH=3%>
- <P> </P>
- </TD>
- <TD WIDTH=97%>
-
- <P>M4 is expected for April <span lang="en-us">8 and will be
- based on the Platform 3.1M6</span>
- </P>
-
- </TD>
- </TR>
- <TR>
- <TD WIDTH=3%>
- <P> </P>
- </TD>
-
- <TD WIDTH=97%>
-
- <P><B>High Priority</B>
- </P>
-
- <UL>
- <LI><i>Including M3 items with previous 'Medium Priority', quoted here with <b>[from M3]</b></i></LI>
-
- <LI>Project Layouts for Web/J2EE Modules</LI>
- <UL>
- <LI>Project management tools</LI>
- <LI>Tools for navigation (e.g. J2EE integrated view)</LI>
- </UL>
- <LI>Structured Source Editor</LI>
- <UL>
- <LI>Complex JSP Editing (formatting, quick fixes, refactoring...)</LI>
- <LI>Content-based selection</LI>
- <LI>XQuery editor</LI> <b><i>[from M3]</b></i>
- </UL>
- <LI>XML schema</LI>
- <UL>
- <LI>Schema graphical edition</LI>
- </UL>
-
- <LI>EJB Wizards
-
- <UL>
-
- <LI>EJB Wizards to generate
- annotated Java Sources from templates <b><i>[from M3]</b></i>
- <LI>All EJB types <b><i>[from M3]</b></i>
- </UL>
-
- <LI>Database Tool
- <UL>
- <LI>SQL Query graphical editor <b><i>[from M3]</b></i>
-
- </UL>
-
- <LI>Web Services
- <UL>
-
- <LI>UDDI registry adapter <b><i>[from M3]</b></i>
- <LI>Develop a Web Service skeleton based on WSDL and associated test client
- <LI>Publish WSDL
- schema on UDDI registries <b><i>[from M3]</b></i>
- <LI>Import of WSDL definitions from UDDI registries
- <LI>Test Web services for WS-I compliance <b><i>[from M3]</b></i>
- <LI>Explore UDDI registries and dynamically test web services via WSDL
-
- </UL>
-
- </UL>
-
- </TD>
- </TR>
- <TR>
-
- <TD WIDTH=3%>
- <P> </P>
- </TD>
- <TD WIDTH=97%>
- <P><B>Medium Priority</B>
- </P>
-
- <UL>
- <LI>Develop a J2EE Web Application
- <UL>
- <LI>Edit deployment descriptors</LI>
- <LI>Graphical wizards for EJB generation</LI>
- <LI>Develop tag libraries</LI>
- <LI>Develop Servlets and Servlet Filters</LI>
-
- </UL>
- <LI>XML schema
- <UL>
- <LI>Sample XML document generation</LI>
-
- </UL>
- <LI>Flow Builder
- <UL>
- <LI>Definition of a generic flow builder <FONT COLOR="#E00000">
- (similar to <a href="http://sourceforge.net/projects/flow4jeclipse/">Flow4J</a>,
- see <a href="http://flow4jeclipse.sourceforge.net/docs/screenshots/index.html">screenshots</a>)</FONT></LI>
- </UL>
- <LI>Web Services
- <UL>
- <LI>WSDL graphical editor</LI>
-
- </UL>
-
-
-
- </UL>
- </TD>
- </TR>
- <TR>
- <TD WIDTH=3%>
-
- <P><BR>
- </P>
-
- </TD>
-
- <TD WIDTH=97%>
- <P><BR>
- </P>
- </TD>
- </TR>
-
-</TABLE>
-
-
-
-<TABLE WIDTH=100% BORDER=0 CELLPADDING=2 CELLSPACING=0>
-
- <COL WIDTH=7*>
- <COL WIDTH=249*>
- <TR>
-
- <TD COLSPAN=2 WIDTH=100% VALIGN=TOP BGCOLOR="#0080c0">
-
- <P ALIGN=LEFT><A NAME="M5"><FONT COLOR="#ffffff"><FONT FACE="Arial, Helvetica">
- <B>M5</B></FONT></FONT></A></P>
- </TD>
- </TR>
-
- <TR>
-
- <TD WIDTH=3%>
- <P> </P>
- </TD>
- <TD WIDTH=97%>
-
- <P>M5 <span lang="en-us">will be
- based on the Platform 3.1M7</span> and is expected for one week after the 3.1M7 release (end of May)
- </P>
-
- </TD>
- </TR>
- <TR>
- <TD WIDTH=3%>
- <P> </P>
- </TD>
-
- <TD WIDTH=97%>
-
- <P><B>High Priority</B>
- </P>
-
- <UL>
-
-
- <LI><i>Including M4 items with previous 'Medium Priority', quoted here with <b>[from M4]</b></i></LI>
-
- <LI>Project Layouts for Web/J2EE Modules</LI>
- <UL>
- <LI>Validators for J2EE projects and resources
- (on top of a validator framework)</LI>
- </UL>
- <LI>Develop a J2EE Web Application</LI>
- <UL>
- <LI>Edit deployment descriptors <i><b>[from M4]</b></i></LI>
- <LI>Graphical wizards for EJB generation <i><b>[from M4]</b></i></LI>
- <LI>Develop tag libraries <i><b>[from M4]</b></i></LI>
- <LI>Develop Servlets and Servlet Filters <i><b>[from M4]</b></i></LI>
- </UL>
- <LI>Database tool</LI>
- <UL>
- <LI>O/R mapping tool</LI>
- </UL>
- <LI>XML Schema</LI>
- <UL>
- <LI>Sample XML document generation <i><b>[from M4]</b></i></LI>
- </UL>
- <LI>Flow Builder
- <UL>
- <LI>Definition of a generic flow builder <i><b>[from M4]</b></i> <FONT COLOR="#E00000">
- (similar to <a href="http://sourceforge.net/projects/flow4jeclipse/">Flow4J</a>,
- see <a href="http://flow4jeclipse.sourceforge.net/docs/screenshots/index.html">screenshots</a>)</FONT></LI>
- </UL>
- <LI>Web services</LI>
- <UL>
- <LI>Extension of the flow builder to an editor that create and deploy BPEL4WS</LI>
- <LI>Extension of TCP/IP monitor for SOAP message capture and logging</LI>
- <LI>WSDL graphical editor <i><b>[from M4]</b></i></LI>
- </UL>
-
-
-
- </UL>
- </UL>
-
- </TD>
- </TR>
- <TR>
-
- <TD WIDTH=3%>
- <P> </P>
- </TD>
- <TD WIDTH=97%>
- <P><B>Medium Priority</B>
- </P>
-
- <UL>
- <LI>Snippet view</LI>
- <UL>
- <LI>Possibility to develop libraries of code snippets</LI>
- <LI>Drag&drop possibility of code snippets</LI>
- </UL>
- <LI>Database Tool
- <UL>
- <LI>Graphical representation of tables relationships</LI>
- </UL>
-
-
-
- </UL>
- </TD>
- </TR>
- <TR>
-
- <TD WIDTH=3%>
- <P> </P>
- </TD>
- <TD WIDTH=97%>
- <P><B>Low Priority</B>
- </P>
-
- <UL>
- <LI>Structured Source Editor</LI>
- <UL>
- <LI>Exemplar PHP editor</LI>
- </UL>
-
-
-
- </UL>
- </TD>
- </TR>
- <TR>
- <TD WIDTH=3%>
-
- <P><BR>
- </P>
-
- </TD>
-
- <TD WIDTH=97%>
- <P><BR>
- </P>
- </TD>
- </TR>
-
-</TABLE>
-
-<hr>
-<FONT COLOR="#E00000">
-<ul>
-<li>Not yet scheduled (comments are welcome):
- <ul>
- <li>SVG => need to talk to Xinjie Zhang who has shown interest in SVG.
- Could be an interesting topic as an alternative to Flex
- (announcement of <a href="http://www.theserverside.com/news/thread.tss?thread_id=29545">Flex version 1.5</a>
- and announcement of <a href="http://www.theserverside.com/news/thread.tss?thread_id=28246">Flex Builder (IDE for Flex)</a>.
- According to
- <a href="http://www.macromedia.com/software/flex/whitepapers/pdf/flex15_tech_wp.pdf">this</a> technical paper:
- <i>Flex developers use an extensible library of UI components and an XML tagbased
-language to define the user interface and an object-oriented scripting
-language (ActionScript) to handle procedural logic.</i>)</li>
- <li>XSLT => limited noise, up to now, about an XSLT editor in WTP, not yet scheduled </li>
- <li>WSIL (that belongs to the 'web services' area) => the above schedule is limited to UDDI registry</li>
- <li>WSDL documentation generator</li>
- <li>WebDAV</li>
- <li>...</li>
- </ul>
-</li>
-<li>Call for comments:
- <ul>
- <li>O/R mapping tool item is in M5. Different O/R mapping strategies exist and different Java targets for mapping (EJB, POJO).
- I think a generic tool could be enabled. Anyway, I want to hear more technical people on that item.</li>
- </ul>
-</li>
-<li>Implicit items to explicit:
- <ul>
- <li>Item: a view for the management of the servers => I think it as implicitely included in M1-M3. Where ? To confirm.</li>
- <li>Item: JAR, WAR, EAR packaging => I think it as implicitely included in M1-M3. Where = 'flexible project layout'. To confirm.</li>
- <li>To explicit (!?) in milestones: deployment mode on servers (unit test mode, local mode, remote mode)</li>
- </ul>
-</li>
-</ul>
-</font>
-<hr>
-<P STYLE="margin-top: 0.5cm; margin-bottom: 0cm"><BR>
-</P>
-<P>Please see our <A HREF="http://eclipse.org/legal/privacy.html">privacy
-policy</A> and website <A HREF="http://eclipse.org/legal/termsofuse.html">terms
-of use</A>. For problems with the eclipse.org site, please contact
-the <A HREF="mailto:webmaster@eclipse.org">webmaster</A> or read the
-
-
-<A HREF="http://eclipse.org/webmaster/index.html">webmaster FAQ</A>
-for answers to common questions!</P>
-</BODY>
-
-</HTML>
-
-
diff --git a/development/planning/milestone_plan_1_0.html b/development/planning/milestone_plan_1_0.html
deleted file mode 100644
index afbb2b9..0000000
--- a/development/planning/milestone_plan_1_0.html
+++ /dev/null
@@ -1,878 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<!-- saved from url=(0076)http://www.eclipse.org/webtools/development/planning/milestone_plan_1_0.html -->
-<html>
-<head>
-<title>Eclipse WTP 0.7 Milestone Plan (Overview)</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link href="milestone_plan_1_0_files/default_style.css" type="text/css"
- rel="stylesheet">
-</head>
-<body dir="ltr" text="#000000" vlink="#551a8b" link="#0000ee"
- bgcolor="#ffffff">
-<table style="PAGE-BREAK-BEFORE: always" cellspacing="5" cellpadding="2"
- width="100%" border="0">
- <tbody>
- <tr>
- <td width="60%">
- <p align="left"><b><FONT face="Verdana, Arial, Helvetica, sans-serif"><font
- size="6">Eclipse WTP 1.0 Milestone Plan</font></font></b><br>
- <font size="1" color="#8080ff">The Eclipse Web Tools Platform Project
- Milestone contents</font></p>
- </td>
- <td width="40%"><img border="0" src="../../../images/Idea.jpg"
- width="120" height="86" alt=""></td>
- </tr>
- </tbody>
-</table>
-<table cellspacing="0" cellpadding="2" width="100%" border="0">
- <colgroup>
- <col width="7">
- <col width="249">
- </colgroup>
- <tbody>
- <tr>
- <td valign="top" width="100%" bgcolor="#0080c0" colspan="2">
- <p align="left"><b><font color="#ffffff">Status of this Document</font></b></p>
- </td>
- </tr>
- <tr>
- <td valign="top" width="3%">
- <p align="right"> </p>
- </td>
- <td width="97%">
- <p>This is a preliminary plan. It is undergoing review and change. It
- includes initial ideas for the following Milestones:</p>
- </td>
- </tr>
- <tr>
- <td valign="top" width="3%">
- <p align="right"><img height="16"
- src="milestone_plan_1_0_files/Adarrow.gif" width="16" align="bottom"
- border="0" name="Image2" alt=""></p>
- </td>
- <td width="97%">
- <p><a
- href="#M0"><b>M0</b></a><br>
- Initial CVS module structure, build infrastructure, and Server Tools.</p>
- </td>
- </tr>
- <tr>
- <td valign="top" width="3%">
- <p align="right"><img height="16"
- src="milestone_plan_1_0_files/Adarrow.gif" width="16" align="bottom"
- border="0" name="Image3" alt=""></p>
- </td>
- <td width="97%">
- <p><a
- href="#M1"><b>M1</b></a>
- - <span lang="en-us">completed </span>October 15<br>
- Finalize build infrastructure and Server Tools. Based on Eclipse 3.0.</p>
- </td>
- </tr>
- <tr>
- <td valign="top" width="3%">
- <p align="right"><img height="16"
- src="milestone_plan_1_0_files/Adarrow.gif" width="16" align="bottom"
- border="0" name="Image4" alt=""></p>
- </td>
- <td width="97%">
- <p><a
- href="#M2"><b>M2</b></a>
- - December <span lang="en-us">22</span>, 2004<br>
- Flexible project layout. Initial XML, JSP and EJB Tools.<span
- lang="en-us"> Based on Eclipse 3.1M4.</span></p>
- </td>
- </tr>
- <tr>
- <td valign="top" width="3%">
- <p align="right"><img height="16"
- src="milestone_plan_1_0_files/Adarrow.gif" width="16" align="bottom"
- border="0" name="Image4" alt=""></p>
- </td>
- <td width="97%">
- <p><a
- href="#M3"><b>M3</b></a>
- - February <span lang="en-us">25</span>, 2005<br>
- Improved XML, JSP and EJB Tools. Database Tools and Initial Web
- Services.<span lang="en-us"> Based on Eclipse 3.1M5.</span></p>
- </td>
- </tr>
- <tr>
- <td valign="top" width="3%">
- <p align="right"><img height="16"
- src="milestone_plan_1_0_files/Adarrow.gif" width="16" align="bottom"
- border="0" name="Image3" alt=""></p>
- </td>
- <td width="97%">
- <p><a
- href="#M4"><b>M4</b></a>
- - April 29, 2005<br>
- WTP 0.7 API Definition Complete. Based on Eclipse 3.1M6.</p>
- </td>
- </tr>
- <tr>
- <td valign="top" width="3%">
- <p align="right"><img height="16"
- src="milestone_plan_1_0_files/Adarrow.gif" width="16" align="bottom"
- border="0" name="Image3" alt=""></p>
- </td>
- <td width="97%">
- <p><a
- href="#M5"><b>M5</b></a>
- - July 1, 2005<br>
- WTP 0.7 API Implementation Complete. Based on Eclipse 3.1 Release Candidate.</p>
- </td>
- </tr>
- <tr>
- <td valign="top" width="3%">
- <p align="right"><img height="16"
- src="milestone_plan_1_0_files/Adarrow.gif" width="16" align="bottom"
- border="0" name="Image3" alt=""></p>
- </td>
- <td width="97%" >
- <p><a
- href="#0.7RC1"><b>0.7RC1</b></a>
- - July 13, 2005<br>
- First Release Candidate for 0.7. Based on Eclipse 3.1 Release.</p>
- </td>
- </tr>
- <tr>
- <td valign="top" width="3%">
- <p align="right"><img height="16"
- src="milestone_plan_1_0_files/Adarrow.gif" width="16" align="bottom"
- border="0" name="Image3" alt=""></p>
- </td>
- <td width="97%">
- <p><a
- href="#0.7RC2"><b>0.7RC2</b></a>
- - July 22, 2005<br>
- Second Release Candidate for 0.7. Based on Eclipse 3.1 Release.</p>
- </td>
- </tr>
- <tr>
- <td valign="top" width="3%">
- <p align="right"><img height="16"
- src="milestone_plan_1_0_files/Adarrow.gif" width="16" align="bottom"
- border="0" name="Image3" alt=""></p>
- </td>
- <td width="97%">
- <p><a
- href="#0.7"><b>0.7 Release</b></a>
- - July 29, 2005<br>
- WTP 0.7 stabilization and final bug fixes. Based on Eclipse 3.1
- Release.</p>
- </td>
- </tr>
- <tr>
- <td valign="top" width="3%" bgcolor="#ccffff">
- <p align="right"><img height="16"
- src="milestone_plan_1_0_files/Adarrow.gif" width="16" align="bottom"
- border="0" name="Image4" alt=""></p>
- </td>
- <td width="97%" bgcolor="#ccffff">
- <p><a href="#1.0M8"><b>1.0M8</b></a> - September 23, 2005<br>
- <span lang="en-us">Based on Eclipse 3.1.</span></p>
- </td>
- </tr>
- <tr>
- <td valign="top" width="3%">
- <p align="right"><img height="16"
- src="milestone_plan_1_0_files/Adarrow.gif" width="16" align="bottom"
- border="0" name="Image4" alt=""></p>
- </td>
- <td width="97%">
- <p><a href="#1.0M9"><b>1.0M9</b></a> - November 18, 2005<br>
- <span lang="en-us">Based on Eclipse 3.1.</span></p>
- </td>
- </tr>
- <tr>
- <td valign="top" width="3%">
- <p align="right"><img height="16"
- src="milestone_plan_1_0_files/Adarrow.gif" width="16" align="bottom"
- border="0" name="Image4" alt=""></p>
- </td>
- <td width="97%">
- <p><a href="#1.0"><b>1.0</b></a> - December 16, 2005<br>
- <span lang="en-us">Based on Eclipse 3.1 or a 3.1 maintenance release.</span></p>
- </td>
- </tr>
- <tr>
- <td valign="top" width="100%" bgcolor="#0080c0" colspan="2">
- <p align="left"><a name="M0"><font color="#ffffff"><b>M0</b></font></a></p>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p>The goal of M0 is to create the initial CVS module structure and
- to populate it with the Server Tools. This allows us to verify our
- build infrastructure and enables us to begin the creation of server
- adapters.</p>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p><b>High Priority</b></p>
- <ul>
- <li>Create and commit initial CVS module structure</li>
- <li>Commit Server Tools into CVS</li>
- <li>Run the first public automatic build</li>
- <li>Update website with downloads/what's new links (ala EMF)</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td valign="top" width="100%" bgcolor="#0080c0" colspan="2">
- <p align="left"><a name="M1"><font color="#ffffff"><b>M1</b></font></a></p>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p>M1 <span lang="en-us">was completed</span> October 15</p>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p><b>High Priority</b></p>
- <ul>
- <li>Finalize WTP Build Infrastructure
- <ul>
- <li>Run report automatic builds/tests</li>
- <li>CVS structure</li>
- <li>Updating web site with build info automatically (what's new
- etc.)</li>
- </ul>
- </li>
- <li>Server Runtime Support for Tomcat
- <ul>
- <li>Launch Server (Start) (In debug ro run modes)</li>
- <li>Be able to run (and debug) Java Servlet</li>
- <li>Stop Server</li>
- </ul>
- </li>
- </ul>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p><b>Medium Priority</b></p>
- <ul>
- <li>Integrate Lomboz Generic Server Runtime Support using XML Server
- Definitions (JBoss, Jonas)
- <ul>
- <li>Launch Server (Start) (In debug and run modes)</li>
- <li>Stop Server</li>
- </ul>
- </li>
- <li>"Run on server" for Web artifacts (e.g. .html)
- <ul>
- <li>Start server</li>
- <li>Display in IDE browser</li>
- </ul>
- </li>
- </ul>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p><b>Low Priority</b></p>
- <ul>
- <li>Apache server adapter
- <ul>
- <li>Add/remove Web project to configuration</li>
- <li>Start and stop server</li>
- <li>"Run on server" for Web artifacts (e.g. .html)</li>
- </ul>
- </li>
- </ul>
- </td>
- </tr>
- <tr>
- <td valign="top" width="100%" bgcolor="#0080c0" colspan="2">
- <p align="left"><a name="M2"><font color="#ffffff"><b>M2</b></font></a></p>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p>M2 was delivered on December 22 and is based on Eclipse 3.1M4</p>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p><b>High Priority</b></p>
- <ul>
- <li>Project Layouts for Web/J2EE Modules
- <ul>
- <li>Simple Web/J2EE project layouts</li>
- </ul>
- </li>
- <li>XML
- <ul>
- <li>XML Source Page Editor</li>
- <li>Validation for XML</li>
- </ul>
- </li>
- <li>Database Tool
- <ul>
- <li>Table content browsing</li>
- </ul>
- </li>
- <li>Medium Priority Items from M1</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p><b>Medium Priority</b></p>
- <ul>
- <li>JSP
- <ul>
- <li>Simple JSP Source Editing (which, by implication pulls in some
- amount of XML, HTML, CSS, JavaScript)</li>
- <li>Set breakpoints</li>
- <li>Debug JSP (JSR 45)</li>
- </ul>
- </li>
- <li>XML
- <ul>
- <li>XML creation wizards (creates skeleton XML given DTD or XML
- Schema)</li>
- <li>Graphical XML Schema editor</li>
- <li>XML catalog support</li>
- <li>Validation for XML Schema and DTD</li>
- <li>XML example project to jump start users</li>
- </ul>
- </li>
- <li>EJB Wizards
- <ul>
- <li>Simple EJB Wizards to generate annotated Java Sources from
- templates</li>
- <li>Session Beans only</li>
- </ul>
- <ul>
- </ul>
- </li>
- </ul>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p><b>Low Priority</b></p>
- <ul>
- <li>Snippets View</li>
- <li>Task Tags in Comments of Many Languages</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p><b>M2 Shutdown Testing to begin 12/10</b></p>
-
- <ul>
- <p>We'd like the community to stay aware of this date, so hopefully
- we can have many people test it a few days, either to help execute
- our test cases, or come up with some of your own. (Normally it would
- be exactly one week, but we are allowing extra time due to holiday's
- and to allow an upgrade to Eclipse M4 on 17th)</p>
- <ul>
- <li>12/10 Build Candidate for Milestone</li>
- <ul>
- <li>Code Complete</li>
- <li>component test plans for <a href="../../jst/components.html">JST</a>
- and <a href="../../wst/components.html">WST</a> complete</li>
- <li>Top-to-Bottom mini-tutorials will be created will created for
- testing (for example, see <a
- href="../../testtutorials/M2/tutorial1/wtp-tutorial-I.html">WTP
- Tutorials-Building and Running a Web Application</a>)</li>
- <li>milestone plans updated, if appropriate, to accurately reflect
- M2 content (e.g. if there's any "early" or
- "experimental" function)</li>
- <li>exit criteria:</li>
- <ul>
- <li>High priority items working</li>
- <li>Fixed all priority 1 defects, and fix or answer all Blocker,
- Critical, and Major defects</li>
- <li>All running unit tests passing</li>
- <li>Plugin.xml PDE flagged errors eliminated</li>
- </ul>
- </ul>
- </ul>
- </ul>
-
-
- </td>
- </tr>
- </tbody>
-</table>
-
-<table cellspacing="0" cellpadding="2" width="100%" border="0">
- <colgroup>
- <col width="7">
- <col width="249">
- </colgroup>
- <tbody>
- <tr>
- <td valign="top" width="100%" bgcolor="#0080c0" colspan="2">
- <p align="left"><a name="M3"><font color="#ffffff"><b>M3</b></font></a></p>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p>M3 was delivered on February 25 and was
- based on Eclipse 3.1M5</p>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p><b>High Priority</b></p>
- <ul>
- <li>Project Layouts for Web/J2EE Modules
- <ul>
- <li>Complex Web/J2EE project layouts</li>
- <li>Flexible project layouts, i.e. (One project for many web
- modules, Maven style)</li>
- </ul>
- </li>
- <li>Web Services
- <ul>
- <li>Axis adapter</li>
- <li>Develop a Web Service based on Session Beans</li>
- <li>Develop a Web Service based on JavaBeans</li>
- <li>Create Web Service Client</li>
- <li>Graphical WSDL editor</li>
- <li>Validation for WSDL</li>
- </ul>
- </li>
- <li>Medium Priority Items from M2</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p><b>Medium Priority</b></p>
- <ul>
- <li>EJB Wizards
- <ul>
- <li>EJB Wizards to generate annotated Java Sources from templates</li>
- <li>All EJB types</li>
- </ul>
- </li>
- <li>XQuery editor</li>
- <li>Database Tool
- <ul>
- <li>SQL Query graphical editor</li>
- </ul>
- </li>
- <li>Web Services
- <ul>
- <li>Develop and publish WSDL schema on UDDI registries</li>
- <li>Test Web services for WS-I compliance</li>
- </ul>
- </li>
- </ul>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p><br>
- </p>
- </td>
- <td width="97%">
- <p><br>
- </p>
- </td>
- </tr>
- </tbody>
-</table>
-
-<table cellspacing="0" cellpadding="2" width="100%" border="0">
- <colgroup>
- <col width="7">
- <col width="249">
- </colgroup>
- <tbody>
- <tr>
- <td valign="top" width="100%" bgcolor="#0080c0" colspan="2">
- <p align="left"><a name="M4"><font color="#ffffff"><b>M4</b></font></a></p>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p><p>M4 was delivered on April 29 and was
- based on Eclipse 3.1M6.</p>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p><b>High Priority</b></p>
- <ul>
- <li>Server Tooling API</li>
- <li>API for Flexible Java projects featuring multiple modules and complex layouts</li>
- <li>Medium Priority Items from M3</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p><b>Medium Priority</b></p>
- <ul>
- <li>Web Services
- <ul>
- <li>Simplify installation burden for users</li>
- </ul>
- </li>
- </ul>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p><br>
- </p>
- </td>
- <td width="97%">
- <p><br>
- </p>
- </td>
- </tr>
- </tbody>
-</table>
-<table cellspacing="0" cellpadding="2" width="100%" border="0">
- <colgroup>
- <col width="7">
- <col width="249">
- </colgroup>
- <tbody>
- <tr>
- <td valign="top" width="100%" bgcolor="#0080c0" colspan="2">
- <p align="left"><a name="M5"><font color="#ffffff"><b>M5</b></font></a></p>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p>M5 was delivered on July 1 and was
- based on Eclipse 3.1.</p>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p><b>High Priority</b></p>
- <ul>
- <li>Medium Priority Items from M5</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p><b>Medium Priority</b></p>
- <ul>
- <li>JSP
- <ul>
- <li>JSP Expression Language Support (Content Assist, Syntax Coloring)</li>
- </ul>
- </li>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p><b>Low Priority</b></p>
- <ul>
- <li>SSE
- <ul>
- <li>Non-builder-based Task Tag support for multiple languages</li>
- </ul>
- </li>
- </ul>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p><br>
- </p>
- </td>
- <td width="97%">
- <p><br>
- </p>
- </td>
- </tr>
- </tbody>
-</table>
-<table cellspacing="0" cellpadding="2" width="100%" border="0">
- <colgroup>
- <col width="7">
- <col width="249">
- </colgroup>
- <tbody>
- <tr>
- <td valign="top" width="100%" bgcolor="#0080c0" colspan="2">
- <p align="left"><a name="0.7RC1"><font color="#ffffff"><b>0.7 Release Candidate 1</b></font></a></p>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p> The first 0.7 Release Candidate was delivered on July 15th and is
- based on Eclipse 3.1.
- </p>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p><b>High Priority</b></p>
- <ul>
- <li>Blocking, major, critical, and non-destabilizing fixes</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p><b>Medium Priority</b></p>
- <ul>
- <li>High user impact bugs and cosmetic fixes</li>
- </ul>
- </td>
- </tr>
- </tbody>
-</table>
-
-<table cellspacing="0" cellpadding="2" width="100%" border="0">
- <colgroup>
- <col width="7">
- <col width="249">
- </colgroup>
- <tbody>
- <tr>
- <td valign="top" width="100%" bgcolor="#0080c0" colspan="2">
- <p align="left"><a name="0.7RC2"><font color="#ffffff"><b>0.7 Release Candidate 2</b></font></a></p>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p>The second 0.7 Release Candidate is expected on July 22nd and will be
- based on Eclipse 3.1. More Release Candidates will be published if necessary.</p>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p><b>High Priority</b></p>
- <ul>
- <li>Blocking defects</li>
- </ul>
- </td>
- </tr>
- </tbody>
-</table>
-<table cellspacing="0" cellpadding="2" width="100%" border="0">
- <colgroup>
- <col width="7">
- <col width="249">
- </colgroup>
- <tbody>
- <tr>
- <td valign="top" width="100%" bgcolor="#0080c0" colspan="2">
- <p align="left"><a name="0.7"><font color="#ffffff"><b>0.7 Release</b></font></a></p>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p>Release 0.7 was delivered on July 29 and is be
- based on the Eclipse 3.1 release.</p>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p><br>
- </p>
- </td>
- <td width="97%">
- <p><br>
- </p>
- </td>
- </tr>
- </tbody>
-</table>
-<table cellspacing="0" cellpadding="2" width="100%" border="0">
- <colgroup>
- <col width="7">
- <col width="249">
- </colgroup>
- <tbody>
- <tr>
- <td valign="top" width="100%" bgcolor="#0080c0" colspan="2">
- <p align="left"><a name="1.0M8"><font color="#ffffff"><b>1.0M8</b></font></a></p>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p>Milestone 1.0M8 is expected on September 23, 2005 and is to be
- based on the Eclipse 3.1 release.</p>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p><br>
- </p>
- </td>
- <td width="97%">
- <p><br>
- </p>
- </td>
- </tr>
- </tbody>
-</table>
-<table cellspacing="0" cellpadding="2" width="100%" border="0">
- <colgroup>
- <col width="7">
- <col width="249">
- </colgroup>
- <tbody>
- <tr>
- <td valign="top" width="100%" bgcolor="#0080c0" colspan="2">
- <p align="left"><a name="1.0M9"><font color="#ffffff"><b>1.0M9</b></font></a></p>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p>Milestone 1.0M9 is expected on November 18, 2005 and is to be
- based on the Eclipse 3.1 release.</p>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p><br>
- </p>
- </td>
- <td width="97%">
- <p><br>
- </p>
- </td>
- </tr>
- </tbody>
-</table>
-<table cellspacing="0" cellpadding="2" width="100%" border="0">
- <colgroup>
- <col width="7">
- <col width="249">
- </colgroup>
- <tbody>
- <tr>
- <td valign="top" width="100%" bgcolor="#0080c0" colspan="2">
- <p align="left"><a name="1.0"><font color="#ffffff"><b>1.0</b></font></a></p>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <p>Release 1.0 is expected on December 16, 2005 and will be
- based on Eclipse 3.1 or a 3.1 maintenance release.</p>
- </td>
- </tr>
- <tr>
- <td width="3%">
- <p><br>
- </p>
- </td>
- <td width="97%">
- <p><br>
- </p>
- </td>
- </tr>
- </tbody>
-</table>
-<p style="MARGIN-TOP: 0.5cm; MARGIN-BOTTOM: 0cm"><br>
-</p>
-<p>Please see our <a href="http://eclipse.org/legal/privacy.html">privacy
-policy</a> and website <a
- href="http://eclipse.org/legal/termsofuse.html">terms of use</a>. For
-problems with the eclipse.org site, please contact the <a
- href="mailto:webmaster@eclipse.org">webmaster</a> or read the <a
- href="http://eclipse.org/webmaster/index.html">webmaster FAQ</a> for
-answers to common questions!</p>
-</body>
-</html>
\ No newline at end of file
diff --git a/development/planning/milestone_plan_1_0_files/Adarrow.gif b/development/planning/milestone_plan_1_0_files/Adarrow.gif
deleted file mode 100644
index 1848247..0000000
--- a/development/planning/milestone_plan_1_0_files/Adarrow.gif
+++ /dev/null
Binary files differ
diff --git a/development/planning/milestone_plan_1_0_files/Idea.jpg b/development/planning/milestone_plan_1_0_files/Idea.jpg
deleted file mode 100644
index 119ce70..0000000
--- a/development/planning/milestone_plan_1_0_files/Idea.jpg
+++ /dev/null
Binary files differ
diff --git a/development/planning/milestone_plan_1_0_files/default_style.css b/development/planning/milestone_plan_1_0_files/default_style.css
deleted file mode 100644
index af2b27a..0000000
--- a/development/planning/milestone_plan_1_0_files/default_style.css
+++ /dev/null
@@ -1,18 +0,0 @@
-p, table, td, th { font-family: arial, helvetica, geneva; font-size: 10pt}
-pre { font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code { font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup { font-family: arial,helvetica,geneva; font-size: 10px}
-h3 { font-family: arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li { font-family: arial, helvetica, geneva; font-size: 10pt}
-h1 { font-family: arial, helvetica, geneva; font-size: 28px; font-weight: bold}
-body { font-family: arial, helvetica, geneva; font-size: 10pt; clip: rect( ); margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large;; font-family: Verdana, Arial, Helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small;; font-family: Arial, Helvetica, sans-serif; color: #8080FF}
-a.bar:link { text-decoration: none; color: #FFFFFF}
-a.bar:visited { color: #FFFFFF; text-decoration: none}
-a.bar:hover { color: #FFFFFF; text-decoration: underline}
-a.bar { color: #FFFFFF}
-.jump { font-size: smaller;; font-family: Arial, Helvetica, sans-serif; color: #8080FF ; font-style: normal; text-decoration: none}
-.jump:link { font-size: smaller;; font-family: Arial, Helvetica, sans-serif; color: #8080FF; text-decoration: none}
-.jump:hover { font-size: smaller;; font-family: Arial, Helvetica, sans-serif; color: #0000FF; text-decoration: underline; font-style: normal}
diff --git a/development/planning/roadmap.html b/development/planning/roadmap.html
deleted file mode 100644
index 72eb042..0000000
--- a/development/planning/roadmap.html
+++ /dev/null
@@ -1,543 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../webtools/wtp.css" type="text/css">
-<title>Eclipse Web Tools Platform Project Roadmap</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">WTP Roadmap</font>
-<br>
-<font class="indexsub">Eclipse Web Tools Platform Project Roadmap</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<em>2005-08-23</em>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Introduction</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- This document describes the roadmap for the Eclipse Web
- Tools Platform (WTP) Project. The content of each release is
- determined by a combination of both specific requirements
- derived from the Eclipse community and some general
- principles. The following general principles apply to all
- releases:
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>
-
-<strong>Eclipse Platform Currency</strong>
-
-<p>
- The WTP project will take advantage of new
- capabilities as they are added to the Eclipse
- Platform in order to achieve user interface
- consistency and seamless integration. WTP releases
- will closely follow Eclipse releases so that WTP
- users can quickly take advantage the latest Eclipse
- platform innovations. WTP operating system coverage
- will match that of the Eclipse platform.
- </p>
-
-<p>
- The WTP will extend the Eclipse Platform with the
- addition of server runtime environments and Web and
- J2EE development artifacts such as HTML, CSS,
- Javascript, JSP, XML, WSDL, J2EE Deployment
- Descriptors, etc. The WTP user interface will extend
- all the standard Eclipse Platform functions such as
- content assist, quick fixes, refactoring, and
- semantic search to these new artifacts in a
- seamless, consistent fashion.
- </p>
-
-</li>
-
-<li>
-
-<strong>WTP API Definition</strong>
-
-<p>
- A key goal of the WTP project is the definition of a
- stable, robust, functional API that add-in providers
- can build on. Our objective is ensure that plug-ins
- that use WTP APIs will run without recompilation on
- future WTP releases. Plug-ins that use internal WTP
- code may require modification to run in future
- releases. The definition of APIs for the initial
- code base will take several releases to complete,
- and new APIs will continue to be introduced as the
- project grows.
- </p>
-
-</li>
-
-<li>
-
-<strong>Web and J2EE Standards Currency</strong>
-
-<p>
- The scope of the WTP project includes Web and J2EE
- standards, and these standards are currently
- undergoing rapid evolution, especially in the area
- of XML and Web services. Each release of WTP will
- both upgrade support for exisiting key standards and
- introduce new support for industrially relevant
- emerging standards.
- </p>
-
-</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Development Process</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>The WTP project uses the following development process:</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>
-
-<strong>Milestone Process</strong>
-
-<p>
- The overall release content is staged into a
- sequence of milestones. The detailed content of each
- milestone is defined by a planning process. Each
- milestone contains a subset of stable function that
- supports a set of development scenarios. Milestone
- builds are suitable for end user testing and
- feedback. Milestones are scheduled bimonthly, but
- are not defined by the schedule. The milestone
- release is declared when all the high priority
- functions are complete.
- </p>
-
-</li>
-
-<li>
-
-<strong>Continuous Integration</strong>
-
-<p>
- The WTP project practices continuous integration.
- The complete product is built nightly. The build
- process include the execution of unit tests,
- performance tests, and API violation and breakage
- scans. Nightly builds may be unstable and are mainly
- of interest to WTP developers.
- </p>
-
-<p>
- Once a week, the code base base is stabilized in an
- integration build. Integration builds are suitable
- for testing and for evaluation by other projects
- that use WTP.
- </p>
-
-<p>
- Approximately bimonthly, a milestone build is
- declared. As mentioned above, milestone builds are
- declared when the high priority items are complete.
- Milestone builds are of interest to WTP users.
- </p>
-
-<p>
- WTP product releases occur approximately annually in
- conjunction with Eclipse product releases. Our goal
- is to follow Eclipse releases as soon as possible so
- that other projects can move to new Eclipse and WTP
- releases at the same time. In practice, we
- anticipate a two to four week period between Eclipse
- and WTP releases, during which time WTP will perform
- testing on the final Eclipse release.
- </p>
-
-</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">WTP 0.7, 3Q2005</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- WTP 0.7 is the initial release. The goal of this release is
- to integrate the initial code contributions and define an
- initial API. The high priority APIs are the Server Tools and
- Flexible Project Layout. Other API will be defined on a best
- effort basis, as permitted by the available resource and
- schedule. Most elements of the API will be defered to WTP
- 1.0.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- This release was previously called WTP 1.0, but it was
- decided to renumber it to WTP 0.7 since the APIs were too
- new to be finalized. Most documents have been updated to
- reflect this new numbering scheme. One exception is Bugzilla
- which still refers to the following milestones as being part
- of WTP 1.0. To avoid confusion, we have skipped M7 and
- started the real WTP 1.0 milestones at M8.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- WTP 0.7 is based on Eclipse 3.1. See
- <a href="../milestone_plans/reports/report-milestone-overview.html">
- Eclipse WTP 0.7 Milestone Plan
- </a>
- for details. The milestone plan summary for WTP 0.7 is as
- follows:
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>
-
-<strong>M1: October 15, 2004.</strong>
-
-<p>Server Tools. Based on Eclipse 3.1 M3.</p>
-
-</li>
-
-<li>
-
-<strong>M2: December 24, 2004.</strong>
-
-<p>
- Web Tools, XML Tools, SSE Framework. Based on
- Eclipse 3.1 M4.
- </p>
-
-</li>
-
-<li>
-
-<strong>M3: February 25, 2005.</strong>
-
-<p>
- EJB Tools, Web Service Tools, Data Tools, Flexible
- Project Layout. Based on Eclipse 3.1 M5.
- </p>
-
-</li>
-
-<li>
-
-<strong>M4: April 29, 2005.</strong>
-
-<p>
- WTP 0.7 API Definition Complete. Based on Eclipse
- 3.1 M6.
- </p>
-
-</li>
-
-<li>
-
-<strong>M5: July 1, 2005.</strong>
-
-<p>
- WTP 0.7 API Implementation Complete. Based on
- Eclipse 3.1 M7.
- </p>
-
-</li>
-
-<li>
-
-<strong>M6 Final: July 29, 2005.</strong>
-
-<p>Stabilization. Based on Eclipse 3.1 Final.</p>
-
-</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">WTP 1.0, 4Q2005</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- WTP 1.0 will be based on a
- <a href="http://www.eclipse.org/eclipse/development/eclipse_maintenance_schedule_3_1_x.html">
- maintenance release of Eclipse 3.1
- </a>
- . Based on the current plan, WTP 1.0 will pick up Eclipse
- 3.1.1, which is scheduled for Fall, 2005, probably in
- September. The purpose of this release is to upgrade WTP 0.7
- to a state that is suitable for adoption by tool vendors.
- The main work items are stabilization of APIs and resolution
- of outstanding NL and Accessibility bugs.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>
- Promote selected provisional APIs to platform status
- based on vendor requirements.
- </li>
-
-<li>
- Componentize WTP into Features to enable adopters to
- select subsets of function.
- </li>
-
-<li>Fix National Language bugs.</li>
-
-<li>Fix Accessibility bugs.</li>
-
-<li>
- Fix other important bugs, with high priority given to
- those required by adopters.
- </li>
-
-<li>Upgrade Help system content.</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>The following milestones are planned:</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>
-
-<strong>1.0 M8: September 23, 2005</strong>
-
-</li>
-
-<li>
-
-<strong>1.0 M9: November 18, 2005</strong>
-
-</li>
-
-<li>
-
-<strong>1.0 M10 Final: December 16, 2005</strong>
-
-</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Since we anticipate that vendors will adopt WTP 1.0, we will
- also have a maintenance stream. The current Eclipse 3.1 plan
- is to have an Eclipse 3.1.2 maintenance release in Winter
- 2006, probably early January. We should therefore plan to
- move to that version, and to fix critical bugs in a WTP
- 1.0.1 maintenance release in late January, 2006. This
- maintenance plan needs to be ratified by the WTP PMC.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">WTP 1.5, 2Q2006</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- WTP 1.5 is based on
- <a href="http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_2.html">
- Eclipse 3.2
- </a>
- . Detailed WTP 1.5 planning has not been performed, but the
- following list gives some candidate items:
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>Exploitation of Eclipse 3.2 innovations.</li>
-
-<li>Improvements to user interface consistency.</li>
-
-<li>Further elaboration of the WTP platform API.</li>
-
-<li>Exploitation of JDK 1.5.</li>
-
-<li>
- Support for new Web standards as as SOAP 1.2, WSDL 2.0,
- and their reference implementations, Axis 2 and Woden.
- </li>
-
-<li>Support for JEE 5.0 including:</li>
-
-<ul>
-
-<li>JSR 175: Code Annotations</li>
-
-<li>JSR 181: Code Annontations for Web Services</li>
-
-<li>
- JSR 127: JSF Tools, based on the
- <a target="_top" href="http://www.eclipse.org/proposals/eclipse-jsf/">
- JavaServer Faces Tooling Project
- </a>
- proposal from Oracle.
- </li>
-
-<li>
- JSR 220: EJB 3.0 Entity Bean ORM Tools, based on the
- <a target="_top" href="http://www.eclipse.org/proposals/eclipse-jsr220-orm/index.html">
- JSR220-ORM Project
- </a>
- proposal from Versant and the
- <a target="_top" href="http://www.eclipse.org/proposals/eclipse-ejb30-orm/index.html">
- EJB 3.0 Object-Relational Mapping Project
- </a>
- proposal from Oracle
- </li>
-
-</ul>
-
-<li>
- JSR 88: JMX Server Control, based on proposed
- <a target="_top" href="http://labs.jboss.com/portal/index.html?ctrl:id=page.default.info&project=jsr88ide">
- JSR88 Plugin by The JBossIDE Team
- </a>
- contribution
-
-
- </li>
-
-<li>
- Migration of WTP Data Tools to the
- <a target="_top" href="http://eclipse.org/datatools/">
- Data Tools Platform Project
- </a>
- (DTP)
- </li>
-
-<li>
- Architectural harmonization with other Eclipse projects
- such as the Eclipse Platform and TPTP.
- </li>
-
-<li>DITA based XML Help.</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The following dates have been adjusted to
- reflect the Eclipse 3.2 plan. The latest plan for Eclipse
- 3.2 is to have a concurrent release of the platform and all
- major projects, including WTP, on June 30, 2006.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>
-
-<strong>
- 1.5 M1: February 10, 2006
- </strong>
-
-</li>
-
-<li>
-
-<strong>
- 1.5 M2: April 7, 2006
- </strong>
-
-</li>
-
-<li>
-
-<strong>
- 1.5 M3: June 2, 2006
- </strong>
-
-</li>
-
-<li>
-
-<strong>
- 1.5 M4 Final: June 30, 2006
- </strong>
-
-</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">WTP 2.0, 3Q2007</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- WTP 2.0 is based on Eclipse 4.0, which we assume will be
- released in 2Q2007.
- </p>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/development/planning/roadmap.xml b/development/planning/roadmap.xml
deleted file mode 100644
index eb161dd..0000000
--- a/development/planning/roadmap.xml
+++ /dev/null
@@ -1,347 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<?xml-stylesheet type="text/xsl" href="../../wtp.xsl"?>
-<html>
- <head>
- <title>Eclipse Web Tools Platform Project Roadmap</title>
- <meta name="root" content="../../.." />
- </head>
- <body>
- <h1>WTP Roadmap</h1>
- <p>
- <em>2005-08-23</em>
- </p>
- <h2>Introduction</h2>
- <p>
- This document describes the roadmap for the Eclipse Web
- Tools Platform (WTP) Project. The content of each release is
- determined by a combination of both specific requirements
- derived from the Eclipse community and some general
- principles. The following general principles apply to all
- releases:
- </p>
- <ul>
- <li>
- <strong>Eclipse Platform Currency</strong>
- <p>
- The WTP project will take advantage of new
- capabilities as they are added to the Eclipse
- Platform in order to achieve user interface
- consistency and seamless integration. WTP releases
- will closely follow Eclipse releases so that WTP
- users can quickly take advantage the latest Eclipse
- platform innovations. WTP operating system coverage
- will match that of the Eclipse platform.
- </p>
- <p>
- The WTP will extend the Eclipse Platform with the
- addition of server runtime environments and Web and
- J2EE development artifacts such as HTML, CSS,
- Javascript, JSP, XML, WSDL, J2EE Deployment
- Descriptors, etc. The WTP user interface will extend
- all the standard Eclipse Platform functions such as
- content assist, quick fixes, refactoring, and
- semantic search to these new artifacts in a
- seamless, consistent fashion.
- </p>
- </li>
- <li>
- <strong>WTP API Definition</strong>
- <p>
- A key goal of the WTP project is the definition of a
- stable, robust, functional API that add-in providers
- can build on. Our objective is ensure that plug-ins
- that use WTP APIs will run without recompilation on
- future WTP releases. Plug-ins that use internal WTP
- code may require modification to run in future
- releases. The definition of APIs for the initial
- code base will take several releases to complete,
- and new APIs will continue to be introduced as the
- project grows.
- </p>
- </li>
- <li>
- <strong>Web and J2EE Standards Currency</strong>
- <p>
- The scope of the WTP project includes Web and J2EE
- standards, and these standards are currently
- undergoing rapid evolution, especially in the area
- of XML and Web services. Each release of WTP will
- both upgrade support for exisiting key standards and
- introduce new support for industrially relevant
- emerging standards.
- </p>
- </li>
- </ul>
- <h2>Development Process</h2>
- <p>The WTP project uses the following development process:</p>
- <ul>
- <li>
- <strong>Milestone Process</strong>
- <p>
- The overall release content is staged into a
- sequence of milestones. The detailed content of each
- milestone is defined by a planning process. Each
- milestone contains a subset of stable function that
- supports a set of development scenarios. Milestone
- builds are suitable for end user testing and
- feedback. Milestones are scheduled bimonthly, but
- are not defined by the schedule. The milestone
- release is declared when all the high priority
- functions are complete.
- </p>
- </li>
- <li>
- <strong>Continuous Integration</strong>
- <p>
- The WTP project practices continuous integration.
- The complete product is built nightly. The build
- process include the execution of unit tests,
- performance tests, and API violation and breakage
- scans. Nightly builds may be unstable and are mainly
- of interest to WTP developers.
- </p>
- <p>
- Once a week, the code base base is stabilized in an
- integration build. Integration builds are suitable
- for testing and for evaluation by other projects
- that use WTP.
- </p>
- <p>
- Approximately bimonthly, a milestone build is
- declared. As mentioned above, milestone builds are
- declared when the high priority items are complete.
- Milestone builds are of interest to WTP users.
- </p>
- <p>
- WTP product releases occur approximately annually in
- conjunction with Eclipse product releases. Our goal
- is to follow Eclipse releases as soon as possible so
- that other projects can move to new Eclipse and WTP
- releases at the same time. In practice, we
- anticipate a two to four week period between Eclipse
- and WTP releases, during which time WTP will perform
- testing on the final Eclipse release.
- </p>
- </li>
- </ul>
- <h2>WTP 0.7, 3Q2005</h2>
- <p>
- WTP 0.7 is the initial release. The goal of this release is
- to integrate the initial code contributions and define an
- initial API. The high priority APIs are the Server Tools and
- Flexible Project Layout. Other API will be defined on a best
- effort basis, as permitted by the available resource and
- schedule. Most elements of the API will be defered to WTP
- 1.0.
- </p>
- <p>
- This release was previously called WTP 1.0, but it was
- decided to renumber it to WTP 0.7 since the APIs were too
- new to be finalized. Most documents have been updated to
- reflect this new numbering scheme. One exception is Bugzilla
- which still refers to the following milestones as being part
- of WTP 1.0. To avoid confusion, we have skipped M7 and
- started the real WTP 1.0 milestones at M8.
- </p>
- <p>
- WTP 0.7 is based on Eclipse 3.1. See
- <a
- href="../milestone_plans/reports/report-milestone-overview.html">
- Eclipse WTP 0.7 Milestone Plan
- </a>
- for details. The milestone plan summary for WTP 0.7 is as
- follows:
- </p>
- <ul>
- <li>
- <strong>M1: October 15, 2004.</strong>
- <p>Server Tools. Based on Eclipse 3.1 M3.</p>
- </li>
- <li>
- <strong>M2: December 24, 2004.</strong>
- <p>
- Web Tools, XML Tools, SSE Framework. Based on
- Eclipse 3.1 M4.
- </p>
- </li>
- <li>
- <strong>M3: February 25, 2005.</strong>
- <p>
- EJB Tools, Web Service Tools, Data Tools, Flexible
- Project Layout. Based on Eclipse 3.1 M5.
- </p>
- </li>
- <li>
- <strong>M4: April 29, 2005.</strong>
- <p>
- WTP 0.7 API Definition Complete. Based on Eclipse
- 3.1 M6.
- </p>
- </li>
- <li>
- <strong>M5: July 1, 2005.</strong>
- <p>
- WTP 0.7 API Implementation Complete. Based on
- Eclipse 3.1 M7.
- </p>
- </li>
- <li>
- <strong>M6 Final: July 29, 2005.</strong>
- <p>Stabilization. Based on Eclipse 3.1 Final.</p>
- </li>
- </ul>
- <h2>WTP 1.0, 4Q2005</h2>
- <p>
- WTP 1.0 will be based on a
- <a
- href="http://www.eclipse.org/eclipse/development/eclipse_maintenance_schedule_3_1_x.html">
- maintenance release of Eclipse 3.1
- </a>
- . Based on the current plan, WTP 1.0 will pick up Eclipse
- 3.1.1, which is scheduled for Fall, 2005, probably in
- September. The purpose of this release is to upgrade WTP 0.7
- to a state that is suitable for adoption by tool vendors.
- The main work items are stabilization of APIs and resolution
- of outstanding NL and Accessibility bugs.
- </p>
- <ul>
- <li>
- Promote selected provisional APIs to platform status
- based on vendor requirements.
- </li>
- <li>
- Componentize WTP into Features to enable adopters to
- select subsets of function.
- </li>
- <li>Fix National Language bugs.</li>
- <li>Fix Accessibility bugs.</li>
- <li>
- Fix other important bugs, with high priority given to
- those required by adopters.
- </li>
- <li>Upgrade Help system content.</li>
- </ul>
- <p>The following milestones are planned:</p>
- <ul>
- <li>
- <strong>1.0 M8: September 23, 2005</strong>
- </li>
- <li>
- <strong>1.0 M9: November 18, 2005</strong>
- </li>
- <li>
- <strong>1.0 M10 Final: December 16, 2005</strong>
- </li>
- </ul>
- <p>
- Since we anticipate that vendors will adopt WTP 1.0, we will
- also have a maintenance stream. The current Eclipse 3.1 plan
- is to have an Eclipse 3.1.2 maintenance release in Winter
- 2006, probably early January. We should therefore plan to
- move to that version, and to fix critical bugs in a WTP
- 1.0.1 maintenance release in late January, 2006. This
- maintenance plan needs to be ratified by the WTP PMC.
- </p>
- <h2>WTP 1.5, 2Q2006</h2>
- <p>
- WTP 1.5 is based on
- <a
- href="http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_2.html">
- Eclipse 3.2
- </a>
- . Detailed WTP 1.5 planning has not been performed, but the
- following list gives some candidate items:
- </p>
- <ul>
- <li>Exploitation of Eclipse 3.2 innovations.</li>
- <li>Improvements to user interface consistency.</li>
- <li>Further elaboration of the WTP platform API.</li>
- <li>Exploitation of JDK 1.5.</li>
- <li>
- Support for new Web standards as as SOAP 1.2, WSDL 2.0,
- and their reference implementations, Axis 2 and Woden.
- </li>
- <li>Support for JEE 5.0 including:</li>
- <ul>
- <li>JSR 175: Code Annotations</li>
- <li>JSR 181: Code Annontations for Web Services</li>
- <li>
- JSR 127: JSF Tools, based on the
- <a target="_top"
- href="http://www.eclipse.org/proposals/eclipse-jsf/">
- JavaServer Faces Tooling Project
- </a>
- proposal from Oracle.
- </li>
- <li>
- JSR 220: EJB 3.0 Entity Bean ORM Tools, based on the
- <a target="_top"
- href="http://www.eclipse.org/proposals/eclipse-jsr220-orm/index.html">
- JSR220-ORM Project
- </a>
- proposal from Versant and the
- <a target="_top"
- href="http://www.eclipse.org/proposals/eclipse-ejb30-orm/index.html">
- EJB 3.0 Object-Relational Mapping Project
- </a>
- proposal from Oracle
- </li>
- </ul>
- <li>
- JSR 88: JMX Server Control, based on proposed
- <a target="_top"
- href="http://labs.jboss.com/portal/index.html?ctrl:id=page.default.info&project=jsr88ide">
- JSR88 Plugin by The JBossIDE Team
- </a>
- contribution
-
-
- </li>
- <li>
- Migration of WTP Data Tools to the
- <a target="_top" href="http://eclipse.org/datatools/">
- Data Tools Platform Project
- </a>
- (DTP)
- </li>
- <li>
- Architectural harmonization with other Eclipse projects
- such as the Eclipse Platform and TPTP.
- </li>
- <li>DITA based XML Help.</li>
- </ul>
- <p>
- The following dates have been adjusted to
- reflect the Eclipse 3.2 plan. The latest plan for Eclipse
- 3.2 is to have a concurrent release of the platform and all
- major projects, including WTP, on June 30, 2006.
- </p>
- <ul>
- <li>
- <strong>
- 1.5 M1: February 10, 2006
- </strong>
- </li>
- <li>
- <strong>
- 1.5 M2: April 7, 2006
- </strong>
- </li>
- <li>
- <strong>
- 1.5 M3: June 2, 2006
- </strong>
- </li>
- <li>
- <strong>
- 1.5 M4 Final: June 30, 2006
- </strong>
- </li>
- </ul>
- <h2>WTP 2.0, 3Q2007</h2>
- <p>
- WTP 2.0 is based on Eclipse 4.0, which we assume will be
- released in 2Q2007.
- </p>
- </body>
-</html>
\ No newline at end of file
diff --git a/development/planning/wtp-ptp.html b/development/planning/wtp-ptp.html
deleted file mode 100644
index 0697829..0000000
--- a/development/planning/wtp-ptp.html
+++ /dev/null
@@ -1,106 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
-<meta name="Author" content="Eclipse WTP PMC">
-<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<title>Eclipse Web Tools Project Plan Plan</title>
-<link rel="stylesheet" href="default_style.css" type="text/css">
-
-</head>
-
-<body>
-
-<h1>Eclipse Web Tools
- Project Plan Summary</h1>
-<p>Last revised February 16, 2005</p>
-<h2>Executive Summary of Current Plan</h2>
-<p>The Web Tools Platform top-level project is currently working on the 1.0
-release. The Web Tools Platform is currently in process of its first major
-release and thus is concentrating on completing, formalizing, and stabilizing
-the initial frameworks and APIs. The project is not planning major new
-functionality at this time. The framework and exemplary tools include server
-tools, web tools, XML tools, structure source editing, EJB tools, web service
-tools, data tools, and vendor neutral flexible project layouts.</p>
-<p>The Web Tools Platform project is tracking the Eclipse Platform closely and
-is taking advantage of the latest Platform innovations to provide user interface
-consistency and seamless integration. The Web Tools milestone releases are
-hosted on the very latest Platform milestone release at all times. The R1.0
-final release is planned for late July 2005 on top of the Platform 3.1 final
-release.</p>
-<p>Details on the current plan(s) can be found at:</p>
-<ul>
- <li> WTP 1.0 release
- <a href="http://eclipse.org/webtools/development/planning/roadmap.html">
- roadmap</a>,
- <a href="http://www.eclipse.org/webtools/development/eclipse_WTP_project_plan_1_0.html">
- project plan</a>, general milestone
- <a href="http://www.eclipse.org/webtools/development/planning/milestone_plan_1_0.html">
- plan</a>, and
- <a href="http://www.eclipse.org/webtools/development/milestone_plans/reports/report-milestone-overview.html">
- detailed milestone plan</a></li>
-</ul>
-<h2>Forward Looking Statement</h2>
-<p>The <a href="http://www.eclipse.org/org/councils/themes.html">Eclipse Themes
-and Priorities</a> are one of the guiding focus areas for the features and
-enhancements in Web Tools Platform Project. Overall, Web Tools is an
-initial-phase project and thus our focus is on a stable, robust, functional API
-that add-in providers can build upon, rather than on adding new features.
-Because of this focus, we are more driven by our Architecture Plan and less by
-the community feedback of new features (through Bugzilla).</p>
-<ul>
- <li><b>Scaling Up</b> - During release 1.0, we are not planning any work on
- handling very large websites. The project anticipates working on those issues
- during release 2.0 while utilizing the features of the Platform releases 3.1
- and 3.2.</li>
- <li><b>Enterprise Ready</b> - We do not have any plans for supporting specific
- enterprise development features. The Web Tools Platform project already
- supports a set of vendor neutral APIs for connecting to web servers and
- databases to enable development across a wide variety of enterprise
- configurations.</li>
- <li><b>Design for Extensibility: Be a Better Platform</b> - During release
- 1.0, we are not planning any work on being a platform for other projects. We
- anticipate working with the Test & Performance Tooling Platform as well as the
- Business Intelligence and Reporting Project in the release 1.1 and release 2.0
- time frame to support their requirements in our tools.</li>
- <li><b>Embedded Development </b>- We do not have any specific plans for
- supporting embedded development.</li>
- <li><b>Rich Client Platform</b> - We do not have any specific plans for
- supporting the Rich Client Platform.</li>
- <li><b>Simple to Use</b> - During release 1.0, the project is concentrating on
- creating a very solid base of well designed and excellently implemented APIs.
- Thus we are not allocating any release 1.0 effort to improving the user
- interface. However, the project intends to allocate significant resources to
- the user interface and user experience during releases 1.1 and 2.0. For
- example, the project plans to provide Darwin Information Typing Architecture
- based XML help.</li>
- <li><b>Enable Consistent Multi-language Support</b> - The WTP project will
- support Java-JSP dual-language development, but we do not have plans to
- support or enabling any other multi-language development.</li>
- <li><b>Appealing to Broader Community</b> - In the WTP 1.1 and 2.0 releases,
- we will continue to track the appropriate Web and J2EE standards. These
- standards are undergoing rapid evolution, especially in the area of XML and
- Web services. Each release of WTP will both upgrade support for existing key
- standards and introduce new support for industrially relevant emerging
- standards.<ul>
- <li>The WTP project will exploit J2SE Java 5.</li>
- <li>The WTP project will support SOAP 1.2, WSDL 2.0, and their reference
- implementations.</li>
- <li>The WTP project will support JSRs 175 and 181.</li>
- <li>The WTP project will support J2EE 1.5.</li>
- <li><i>What other standards?</i></li>
- </ul>
- </li>
-</ul>
-<p><i>Are there any known unresolved issues? Are we not testing on enough
-platforms? Under resourced in certain areas?</i></p>
-<p><i>It would be good to have "candidate work areas" in each of these themes,
-or at least in the themes that are relevant to WTP.</i></p>
-<p><i>This forward looking statement is somewhat minimal and it would be nice if
-someone could make some strengthening comments.</i></p>
-</body>
-
-</html>
\ No newline at end of file
diff --git a/development/pmc_call_notes.html b/development/pmc_call_notes.html
deleted file mode 100644
index 9c2716f..0000000
--- a/development/pmc_call_notes.html
+++ /dev/null
@@ -1,344 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html><head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"><title>Eclipse Web Tools Platform Project Development</title>
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"></head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td align="left" width="60%"><font class="indextop">eclipse web tools platform
- project development</font><br>
- <font class="indexsub">pmc conference calls.</font></td>
-
- <td width="40%"><img src="../../images/Idea.jpg" align="middle" height="86" hspace="50" width="120"></td>
- </tr>
-</tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Calls</font></b></td>
- </tr>
- </tbody></table>
-
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
-
- <tbody>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-10-18.html">October 18, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-10-11.html">October 11, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-10-04.html">October 4, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-09-27.html">September 27, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-09-20.html">September 20, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-09-13.html">September 13, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-09-06.html">September 6, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-08-30.html">August 30, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-08-23.html">August 23, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>8/16 Vacation; no meeting</td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>8/9 Vacation; no meeting</td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>8/2 Vacation; no meeting</td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-07-26.html">July 26, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-07-19.html">July 19, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-07-12.html">July 12, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-07-05.html">July 05, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-06-28.html">June 28, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-06-21.html">June 21, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-06-14.html">June 14, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-06-07.html">June 7, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-05-31.html">May 31, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-05-24.html">May 24, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-05-17.html">May 17, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-05-10.html">May 10, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-05-03.html">May 3, 2005</a></td>
- </tr> <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-04-26.html">April 26, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-04-12.html">April 12, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-04-05.html">April 5, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-03-29.html">March 29, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-03-22.html">March 22, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-03-15.html">March 15, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-03-08.html">March 8, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-02-21.html">February 21, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-02-15.html">February 15, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-02-08.html">February 8, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-02-01.html">February 1, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2005-01-04.html">January 4, 2005</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2004-12-21.html">December 21, 2004</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2004-12-14.html">December 14, 2004</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2004-11-30.html">November 30, 2004</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
-
- <td>
- <a href="pmc_call_notes/2004-11-23.html">November 23, 2004</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2004-11-16.html">November 16, 2004</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
-
- <td>
- <a href="pmc_call_notes/2004-11-09.html">November 9, 2004</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2004-11-02.html">November 2, 2004</a></td>
-
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
-
- <td>
- <a href="pmc_call_notes/2004-10-26.html">October 26, 2004</a></td>
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2004-10-19.html">October 19, 2004</a></td>
-
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
-
- <td>
- <a href="pmc_call_notes/2004-10-12.html">October 12, 2004</a></td>
-
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2004-10-05.html">October 5, 2004</a></td>
-
- </tr>
-
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2004-09-27.html">September 27, 2004</a></td>
-
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2004-09-22.html">September 22, 2004</a></td>
-
- </tr>
-
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2004-09-13.html">September 13, 2004</a></td>
-
- </tr>
-
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
-
- <td>
- <a href="pmc_call_notes/2004-09-06.html">September 06, 2004</a></td>
-
- </tr>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <a href="pmc_call_notes/2004-08-16.html">August 16, 2004</a></td>
-
- </tr>
-
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
- <td>
- <p><a href="pmc_call_notes/2004-08-09.html">August 9, 2004</a></p>
-
- </td>
- </tr>
-
-
-
- </tbody></table>
- <table border="0" cellpadding="2" cellspacing="5" width="100%">
-
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font face="Arial,Helvetica" color="#FFFFFF">Quarterly Planning Updates</font></b></td>
- </tr>
-
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody>
- <tr>
- <td align="right" valign="top"><img src="../../images/Adarrow.gif" border="0" height="16" width="16"></td>
-
- <td>
- <a href="pmc_call_notes/2004Q4-plan-update.html">
-
- 2004 Q4</a></td>
- </tr>
-
-
-
-
- </tbody></table>
-
-
-</body></html>
\ No newline at end of file
diff --git a/development/pmc_call_notes/2004-08-09.html b/development/pmc_call_notes/2004-08-09.html
deleted file mode 100644
index 81a020d..0000000
--- a/development/pmc_call_notes/2004-08-09.html
+++ /dev/null
@@ -1,72 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
-<title>Project Documentation</title>
-</head>
-<body text="#000000" bgcolor="#ffffff" link="#0000ee" vlink="#551a8b" alink="#ff0000">
-<table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
- <tr>
- <td ALIGN=LEFT VALIGN=TOP COLSPAN="2" BGCOLOR="#0080C0"><b>
- <font face="Arial,Helvetica" color="#FFFFFF">PMC Conference Call - August 9,
- 2004</font></b></td>
- </tr>
- </table>
-<table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
- <tr>
- <td>
- <p>Attending: Christophe Ney, Jochen Krause, David Williams, Bjorn
- Freeman-Benson, Naci Dai, Arthur Rhyman</p>
- <p>Requirements Group report from Jochen</p>
- <ul>
- <li>Requirements group has been functioning for one week</li>
- <li>Using a wiki to gather their thoughts</li>
- <li>Will publish a draft of requirements on the website next week
- (August 16th)</li>
- <li>Should we use 3.0 or the latest 3.1 milestone? Consensus was that we
- should track the latest milestone.</li>
- </ul>
- <p>Planning Group report by Christophe</p>
- <ul>
- <li>One response to the email asking for help with reviewing the initial
- contributions.</li>
- <li>Code camp is being considered but nothing definite yet</li>
- <li>Planning document similar to the
- <a href="http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_1.html">
- Eclipse platform plan</a> is a good idea, but there is no commitment to
- produce one.</li>
- </ul>
- <p>Architecture Group report by David</p>
- <ul>
- <li>Rough draft of the architecture document on the website by the end
- of the week</li>
- <li>There was a lot of discussion about perhaps people have too high of
- expectations for the document?</li>
- <li>Conclusion: earlier and incomplete better than later and perfect</li>
- </ul>
- <p>Web Standard Tools by Naci</p>
- <ul>
- <li>M0: the first public build - should be available via the website by
- next week. Including the Cruise Control build status page, etc.</li>
- <li>Further discussion of the build process, what to do when builds
- break, etc. will take place on the wtp-dev mailing list.</li>
- </ul>
- <p>Postponed by Bjorn</p>
- <ul>
- <li>We'll talk about scope expansion/reduction/etc next week.</li>
- <li>We also need to get an M0, M1, M2 plan onto the website so that
- everyone knows our dates and goals. The Planning Group should put this
- together or else we'll have to find an alternative solution next week.</li>
- </ul>
- <p><font size=-1><i>Minutes posted by Bjorn Freeman-Benson, August 9 2004</i></font></p>
- </td>
- </tr>
- </table>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/development/pmc_call_notes/2004-08-16.html b/development/pmc_call_notes/2004-08-16.html
deleted file mode 100644
index 6affbb6..0000000
--- a/development/pmc_call_notes/2004-08-16.html
+++ /dev/null
@@ -1,88 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
-<title>Project Documentation</title>
-</head>
-<body text="#000000" bgcolor="#ffffff" link="#0000ee" vlink="#551a8b" alink="#ff0000">
-<table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
- <tr>
- <td ALIGN=LEFT VALIGN=TOP COLSPAN="2" BGCOLOR="#0080C0"><b>
- <font face="Arial,Helvetica" color="#FFFFFF">PMC Conference Call - August 16,
- 2004</font></b></td>
- </tr>
- </table>
-<table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
- <tr>
- <td>
- <p>Attending: Dominique de Vito, Jochen Krause, David Williams, Bjorn
- Freeman-Benson, Arthur Ryman, Mitch Sonies</p>
- <p>Requirements Group report from Jochen</p>
- <ul>
- <li>Requirements group has a draft of the requirements. It will be put
- on the website before the end of the week.</li>
- <li>The flexible project structure requirements that Todd Williams is
- writing are going to be late - perhaps as much as a week late.</li>
- <li>Jochen has been attending the weekly Pollinate call to gather
- requirements.</li>
- </ul>
- <p>Architecture Group report by David</p>
- <ul>
- <li>The rough draft of the architecture document is ready and will be
- posted on the website today.</li>
- <li>The draft follows the "better earlier and incomplete than later and
- perfect" - we expect it to be a living document.</li>
- </ul>
- <p>Wed Standard Tools by Arthur</p>
- <ul>
- <li>The team will be creating the top-level CVS structure this week.</li>
- <li>The team will then check-in the initial server tools code, also this
- week.</li>
- <li>Arthur will post the milestone plan that he and Naci have worked out
- to the website this week.</li>
- <li>The build servers are working, although they exist behind a
- firewall, so the outputs (builds, logs, stats, etc) will be uploaded to
- the website after each build. The server tools code check-in will be the
- first test of the builds.</li>
- <li>Thanks to the EMF project for all their help setting up our build
- servers.</li>
- </ul>
- <p>Planning Group report by Dominique</p>
- <ul>
- <li>Dominique is just back from vacation.</li>
- <li>He will be collecting code reviews from contributors and making
- notes about which contributors are actually contributing.</li>
- <li>He will work with the IBM webmaster to get the correct set of
- committers (right now there are some who should be there who are not and
- some who are there who should not be).</li>
- <li>He will work with the IBM webmaster to get the correct set of WebDAV
- committers (same problem). Also, we need an automated script that gens
- the WebDAV committer names the way it does for committers.</li>
- <li>The planning group will work on the themes document a la the
- <a href="http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_1.html">
- Eclipse platform plan</a> - although there is still no committed
- delivery date.</li>
- </ul>
- <p>Publicity by Mitch</p>
- <ul>
- <li>Mitch is forming a working group to brainstorm about how to generate
- the appropriate publicity and knowledge about the project in spite of
- the lack of resources from Eclipse.org</li>
- </ul>
- <p>Misc Business by Bjorn</p>
- <ul>
- <li>The PMC voted to, at Henrik's request, replace Henrik with David
- Williams as the Architecture Group representative on the PMC.</li>
- </ul>
- <p><font size=-1><i>Minutes posted by Bjorn Freeman-Benson, August 16 2004</i></font></p>
- </td>
- </tr>
- </table>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/development/pmc_call_notes/2004-09-06.html b/development/pmc_call_notes/2004-09-06.html
deleted file mode 100644
index f973cb7..0000000
--- a/development/pmc_call_notes/2004-09-06.html
+++ /dev/null
@@ -1,103 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html><head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"></head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - September 6,
- 2004</font></b></td>
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <p>Attending: Naci Dai, Dominique de Vito, Jochen Krause, Christophe Ney.
- </p>
-
-
- <p>Code base status</p>
- <ul>
- <li>Build is now available => should promoted for public download</li>
- <ul>
- <li>CVS includes initial server tools, tomcat support, TCP/IP monitor</li>
- </ul>
- <li>Eteration working on extension of server support (IBM) to generic XML configuration (Lomboz)</li>
- <ul>
- <li>Architecture document for more flexible server tools (adaptator) will be made available on Wednesday by Naci</li>
- <li>Naci looking for support to get BULL involved in server tools (architecture review, validation with JOnAS)</li>
- <li>Naci exploring contribution of SAP/JBoss</li>
- </ul>
- <li>Proposal is to concentrate effort on server tools and extensible editor</li>
- </ul>
-
-
-
-
- <p>Planning committee report</p>
- <ul>
- <li>A few calls have taken place to bring everybody up to speed</li>
- <ul>
- <li>So far positive answers from</li>
- <ul>
- <li>Vladislav (Openwide) => code review of extensible editor</li>
- <li>Thomas (Frameworxs) => design of generic project support</li>
- </ul>
- <li>Still trying to get in touch with Together and Librados</li>
- </ul>
- <li>PMC looking for contribution on code review for</li>
- <ul>
- <li>Extensible editor (Jens Lukowski, Innoopract, OpenWide, Exadel)</li>
- </ul>
-
-
- <li>PMC accepting contributions on code review for</li>
- <ul>
- <li>Data tools (Exadel - Xquark - Librados - Together)</li>
- </ul>
- <li>Draft of themes document has been made available to PMC for review before publishing</li>
- <li>Difficulties experienced to get any commitment on dates by participants for milestone plan</li>
- <li>Proposal is to move forward with following milestone plan (due next monday)</li>
-
-
- <li>October 15 - M1 (server tools)</li>
- <ul>
- <li>build infrastructure</li>
- <li>server support for tomcat</li>
- <li>servlet debugging</li>
- <li>integrated lomboz generic xml server support</li>
- <li>display in browser</li>
- </ul>
- <li>December 17 - M2 (extensible editor)</li>
- <ul>
- <li>project layout for web modules</li>
- <li>structured source code editor</li>
- <li>JSP editor </li>
- </ul>
-
-
- </ul>
-
-
-
- <p>Misc.</p>
- <ul>
- <li>EclipseCon CFP open. WTP contributors are encouraged to submit talks (please notify pmc)</li>
- <li>Jochen participating to Pollinate project</li>
-</ul>
-
-
-
- <p><font size="-1"><i>Minutes taken by Christophe Ney and posted by Dominique De Vito, September 30 2004</i></font></p>
- </td>
- </tr>
- </tbody></table>
-
-</body></html>
\ No newline at end of file
diff --git a/development/pmc_call_notes/2004-09-13.html b/development/pmc_call_notes/2004-09-13.html
deleted file mode 100644
index f05b8ef..0000000
--- a/development/pmc_call_notes/2004-09-13.html
+++ /dev/null
@@ -1,83 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html><head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"></head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - September 13,
- 2004</font></b></td>
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <p>Attending: Naci Dai, Dominique de Vito, Jochen Krause, Christophe Ney,
- David Williams, Arthur Ryman, Mitch Sonies</p>
-
- <p>Project promotion by Mitch</p>
- <ul>
- <li>Mitch working on project Press Release & exposure</li>
- <li>The proposed objectives are:</li>
- <ul>
- <li>Make people aware that the project exists</li>
- <li>Convince the world that project is community driven, not IBM</li>
- </ul>
- <li>Should be able to get support from Beth</li>
- <li>Comments by Jochen that communication should wait for first milestones to be released. </li>
- </ul>
-
-
- <p>Code base progress report</p>
- <ul>
- <li>Code review of structured code editor is been conducted.
- If positive, initial code could be moved to CVS next week</li>
- <li>Review of server tools architecture is been conducted</li>
- <ul>
- <li>Feedback by Joachim, SAP on current server tool API</li>
- </ul>
- <li>XML based configuration been included to IBM server tools</li>
- <ul>
- <li>Compatibility problem of IBM contribution with Eclipse 3.1 to be resolved </li>
- </ul>
-
- </ul>
-
- <p>Milestone planning</p>
- <ul>
- <li>Draft of milestone planning document is in circulation</li>
- <li>Final version is due by next week, as result of code review
- may impact M3</li>
- <li>Naci confident that M1, M2 can be reached according to the plan,
- but for flexible project structure manager (M3)</li>
- </ul>
-
- <p>Resources availability</p>
- <ul>
- <li>Eteration, Innoopract, Exadel, Thales, INRIA ressources are now fully engaged</li>
- <li>OpenWide, Together Teamlosungen resources should be engaged by the end of the week</li>
- <li>Participation of BULL and Librados to be consolidated</li>
- <li>More ressources should be available from SAP (Web Services) and JBoss</li>
- <li>Contribution from B.C. Holmes to be investigated by Arthur</li>
- </ul>
-
- <p>Misc.</p>
- <ul>
- <li>EclipseCon CFP open. WTP contributors are encouraged to submit talks (please notify PMC)</li>
- </ul>
-
-
-
- <p><font size="-1"><i>Minutes taken by Christophe Ney and posted by Dominique De Vito, September 30 2004</i></font></p>
- </td>
- </tr>
- </tbody></table>
-
-</body></html>
\ No newline at end of file
diff --git a/development/pmc_call_notes/2004-09-22.html b/development/pmc_call_notes/2004-09-22.html
deleted file mode 100644
index 42bd018..0000000
--- a/development/pmc_call_notes/2004-09-22.html
+++ /dev/null
@@ -1,83 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html><head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"></head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - September 22,
- 2004</font></b></td>
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <p>Attending: Naci Dai, Dominique de Vito, Christophe Ney,
- David Williams, Mitch Sonies</p>
-
-
- <p>Code base progress report by Naci and David</p>
- <ul>
- <li>JST subproject on M1</li>
- <ul>
- <li>Usefull conference call last week on generic server API</li>
- <li>Progress made on generic server code</li>
- <li>How to contribute a server tool document draft to be published today</li>
- </ul>
- <li>JST subproject on M2</li>
- <ul>
- <li>JBoss will be contributing EJB Wizards</li>
- <li>BULL will be contributing mapping tools</li>
- </ul>
- <li>Structured Source Editor</li>
- <ul>
- <li>API clean up on going</li>
- <li>Usefull conference call last week on Structured Source Editor</li>
- </ul>
- </ul>
- <p>Planning Group report by Dominique & Christophe</p>
- <ul>
- <li>Some report is missing for vision of progress been made. Need reports on the following:</li>
- <ul>
- <li>Arthur on WST subproject (structured source code editor, data tools)</li>
- <li>Jochen on requirements</li>
- </ul>
- <li>New resource commitments from JBoss and SAP. Currently investigate engagement of those resources</li>
- <li>Difficulties to engage resources with Librados (no response) and XQuark (very limited at this point)</li>
- <li>New contacts : Orbeon, Sysdeo, Thales TRT</li>
- </ul>
-
-
-
- <p>Publicity by Mitch</p>
- <ul>
- <li>Mitch will expose next Monday a draft plan</li>
- <li>Mitch will need very focused articles: </li>
- <ul>
- <li>typically of interest to small companies</li>
- <li>for publication on IBMs dev. corner - works, Java development journal</li>
- </ul>
- <li>Press release opportunity at IBM software group press event, November 1 - decision for Press Release postponed </li>
- </ul>
-
-
- <p>Architecture Group report by David</p>
- <ul>
- <li>No progress to report</li>
- </ul>
-
-
-
- <p><font size="-1"><i>Minutes taken by Christophe Ney and posted by Dominique De Vito, September 30 2004</i></font></p>
- </td>
- </tr>
- </tbody></table>
-
-</body></html>
\ No newline at end of file
diff --git a/development/pmc_call_notes/2004-09-27.html b/development/pmc_call_notes/2004-09-27.html
deleted file mode 100644
index ed91c27..0000000
--- a/development/pmc_call_notes/2004-09-27.html
+++ /dev/null
@@ -1,96 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html><head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"></head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - September 27,
- 2004</font></b></td>
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <p>Attending: Dominique de Vito, Jochen Krause, Christophe Ney,
- David Williams, Arthur Ryman, Mitch Sonies</p>
-
-
- <p>WST subproject report by Arthur</p>
- <ul>
- <li>Structured Source Code Editor</li>
- <ul>
- <li>Weekly calls are performed between teams on this topic</li>
- <li>The first target is to review and select code pieces and to put selected pieces into CVS</li>
- <li>The working group is doing OK according to the plan</li>
- </ul>
- <li>Data Tools</li>
- <ul>
- <li>Exadel is working on that topic : contribution to come</li>
- <li>B.C. Holmes, from the 'Quantum Database Utility' OSS project, has joined Eclipse WTP - Welcome !</li>
- <li>Arthur has a contact with Apache Derby project - Derby integration into Eclipse WTP is targeted (one Apache contributor foreseen)</li>
- <li>Follow-up with Actuate is needed - may contribute to Eclipse WTP</li>
- <li>Synergies with BIRT have to be explored</li>
- </ul>
- </ul>
-
- <p>J2EE subproject report by Christophe</p>
- <ul>
- <li>Bull working on JOnAS server tool implementation</li>
- <li>Bull to contribute EJB wizard work done on top of JOnAS</li>
- <li>Plan for EJB wizards document description </li>
- </ul>
-
- <p>Architecture Committee report by David</p>
- <ul>
- <li>Continuing with server tool meetings</li>
- <li>By the end of September, a list of requirements is due</li>
- <li>The group is planning to organize enhancements/bug reports in BugZilla.</li>
- <li>A project overview is due.</li>
- </ul>
-
-
-
- <p>Requirements Group report from Jochen</p>
- <ul>
- <li>The projet needs to deliver code to increase interest.</li>
- </ul>
-
-
- <p>Planning Group report by Dominique</p>
- <ul>
- <li>The milestone M3-M5 plan is expected for the end of October</li>
- <li>The complete milestone plan is expected for the end of November</li>
- <li>Need to check Eclipse Platform plan</li>
- <li>Themes page and current milestone page to be published tomorrow</li>
- <li>New contacts : Orbeon, Sysdeo, Air France</li>
- <li>Thales TRT might be contributing to Eclipse WTP - description of Thales TRT Eclipse work to be posted on wtp list</li>
- </ul>
-
- <p>Marketing progress report by Mitch</p>
- <ul>
- <li>Promotion plan is still due, will be sent by next Monday </li>
- </ul>
-
-
-
-
-
-
-
-
-
-
- <p><font size="-1"><i>Minutes taken by Christophe Ney and posted by Dominique De Vito, September 30 2004</i></font></p>
- </td>
- </tr>
- </tbody></table>
-
-</body></html>
\ No newline at end of file
diff --git a/development/pmc_call_notes/2004-10-05.html b/development/pmc_call_notes/2004-10-05.html
deleted file mode 100644
index a52525c..0000000
--- a/development/pmc_call_notes/2004-10-05.html
+++ /dev/null
@@ -1,110 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html><head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"></head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - October 5,
- 2004</font></b></td>
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <p>Attending: Dominique de Vito, Jochen Krause, David Williams, Mitch Sonies,
- Bjorn Freeman-Benson</p>
-
-
- <p>PMC Call Schedule</p>
- <ul>
- <li>Tuesdays at 4pm (Paris), 10am (USA, Eastern), 7am (USA, Western)</li>
- <li>We will start on time and we will try to restrict ourselves to no
- more than an hour.</li>
- </ul>
-
-
- <p>Code Camps</p>
- <ul>
- <li>We are considering a Code Camp at
- <a href="http://www.eclipsecon.org/">EclipseCon</a> (Feb-Mar) and at the
- <a href="http://wiki.objectweb.org/ObjectWebCon05/">ObjectWebCon</a>
- (Jan-Feb). Contact <a href="mailto:dominique.devito@objectweb.org">
- Dominique</a> to express your interest.</li>
- </ul>
-
-
- <p>Structured Source Editor</p>
- <ul>
- <li>Jochen and Jens and others have been working on the code and it is
- ready to checkin to CVS. Bjorn will be checking it in.</li>
- <li>The next steps are to extend the code with tutorials and examples
- for understanding.</li>
- <li>They propose a small "Team Camp" in late December - early January.</li>
- </ul>
-
-
- <p>Ordering of Work</p>
- <ul>
- <li>We discussed how much work should be done before IBM refreshes their
- code contribution, which turned into...</li>
- <li>...a philosophic discussion of "what is an API" and "how much code
- should we adopt how quickly". This topic requires more discussion to
- arrive at a consensus, but in the meantime...</li>
- <li>...we agreed to "adopt/commit code as the community can understand
- the architecture, the design, and the code".<ul>
- <li>We are aware that there are people in the community who feel that
- the project is adopting code too slowly. Our answer is "you could help
- us adopt it more quickly by helping with architecture and design
- documentation, examples and executable use-cases that will allow the
- community as a whole to understand the code base we have been so
- generously given".</li>
- </ul>
- </li>
- </ul>
-
-
- <p>Becoming a Committer</p>
- <ul>
- <li>We discussed the process to follow for new committers. Bjorn agreed
- to update the website with a clearer description of what is required.</li>
- </ul>
-
-
- <p>Cross Product Requirements List</p>
- <ul>
- <li>David gave us an update on his Architecture Council action item to
- help coordinate WTP with other Eclipse projects.</li>
- </ul>
-
-
- <p>On the Queue for Next Week</p>
- <ul>
- <li>Discussion the WebDAV component</li>
- <li>Marketing group report</li>
- <li>Planning group report</li>
- </ul>
-
-
-
-
-
-
-
-
-
-
- <p><font size="-1"><i>Minutes taken by Bjorn Freeman-Benson and posted by
- Bjorn Freeman-Benson, October 5, 2004</i></font></p>
- </td>
- </tr>
- </tbody></table>
-
-</body></html>
\ No newline at end of file
diff --git a/development/pmc_call_notes/2004-10-12.html b/development/pmc_call_notes/2004-10-12.html
deleted file mode 100644
index 2da9006..0000000
--- a/development/pmc_call_notes/2004-10-12.html
+++ /dev/null
@@ -1,105 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html><head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"></head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - October
- 12,
- 2004</font></b></td>
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <p>Attending: Arthur Ryman, Bjorn Freeman-Benson, Christophe Ney, David
- Williams, Dominique de Vito, Jochen Krause, Mitch Sonies, Naci Dai</p>
-
-
- <p><b>Personnel </b>by Bjorn and Dominique</p>
- <ul>
- <li>The committers have voted to promote Gorkem Ercan to Committer. The
- PMC concurred and has informed the EMO.</li>
- <li>The PMC appointed Dominique de Vito to the PMC.</li>
- <li>Panagiotis Korros has contributed a number of project files to help
- developers and will soon be listed on the <a href="../../people/contributors.html">
- contributors page</a>.</li>
- <li>Thanks to both Gorkem, Dominique, and Panagiotis for their positive
- contributions so far and we look forward to more of the same.</li>
- </ul>
-
-
- <p><b>IBM Update</b> by Arthur</p>
- <ul>
- <li>The IBM Team is soon coming off their internal product push and will
- be refreshing the IBM code contribution in a couple weeks.</li>
- <li>In the meantime, they are going to rename their existing code from
- com.ibm to org.eclipse and commit it to CVS so that people can start to
- work on it.</li>
- <li>Integrate the Exadel enhancements to the SQL scrapbook and begin
- working on an improved SQL source editor</li>
- </ul>
-
-
- <p><b>Derby</b> by Arthur</p>
- <ul>
- <li>Suggestion that we include the
- <a href="http://incubator.apache.org/derby/">Apache Derby</a> binary in
- the WTP distro. Pros and cons were discussed; there are many issues
- involved, more than can be summarized quickly. We decided not to include
- the binary currently and instead to convince the Apache group to host an
- Eclipse updates site.</li>
- </ul>
- <p><b>M1</b> by Naci</p>
- <ul>
- <li>We are on target to produce M1 on October 15th.</li>
- <li>We are going to rename the CVS directories as per the Eclipse
- standards before the M1 build.</li>
- <li>M1 has not been extensively tested, but we decided it is better to
- get an M1 out for feedback from the community than it is to achieve
- perfection. We will schedule a longer test pass for M2.</li>
- <li>Action item (Dominique): expose our integration builds on the
- website. The builds are on the download server, but there is no link.</li>
- <li>Action item (Bjorn): write up the New & Noteworthy.</li>
- </ul>
-
-
- <p><b>Marketing Group Update</b> by Mitch</p>
- <ul>
- <li>We are putting together an initial marketing plan, but we
- acknowledge that we are different than other Eclipse top-level projects
- because we don't have a dedicated corporate marketing team.</li>
- </ul>
-
-
- <p><b>On the Queue for Next Week</b></p>
- <ul>
- <li>Discussion the WebDAV component</li>
- <li>Planning group report</li>
- <li>Discussion of changes to Charter</li>
- </ul>
-
-
-
-
-
-
-
-
-
-
- <p><font size="-1"><i>Minutes taken by Bjorn Freeman-Benson and posted by
- Bjorn Freeman-Benson, October 12, 2004</i></font></p>
- </td>
- </tr>
- </tbody></table>
-
-</body></html>
\ No newline at end of file
diff --git a/development/pmc_call_notes/2004-10-19.html b/development/pmc_call_notes/2004-10-19.html
deleted file mode 100644
index 4d2b7ef..0000000
--- a/development/pmc_call_notes/2004-10-19.html
+++ /dev/null
@@ -1,134 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html><head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"></head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - October
- 19,
- 2004</font></b></td>
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <p>Attending: Bjorn Freeman-Benson, David Williams, Jochen Krause, Mitch Sonies, Naci Dai</p>
-
-
- <p><b>Flexible Project Support Working Group</b> by David</p>
-
-
- <ul>
- <li>Who is on this working group?</li>
- </ul>
- <p><b>Charter</b> by Bjorn</p>
-
-
- <ul>
- <li>To resolve a potential ambiguity in the charter about voting, we
- propose to vote next week to propose to the Eclipse Board the following
- changes (highlighted) to the <a href="../../project-charter.html">WTP
- Project Charter</a>:<br>
- "Once a Developer is nominated, the Committers for the Project (or
- component) will vote. <span style="background-color: #FFFF00">Voting
- will remain open for one week (seven calendar days).</span> If there are
- at least 3 positive votes and no negative votes
- <span style="background-color: #FFFF00">in that period</span>, the
- Developer is recommended to the PMC for commit privileges."</li>
- </ul>
- <p><b>Milestone Dates</b> by David and Naci</p>
-
-
- <ul>
- <li>We have changed <a href="../planning/milestone_plan_1_0.html">our
- milestone dates</a> to be one week after the corresponding Eclipse
- Platform milestone dates and have annotated our milestones with the
- Platform milestone version they will be built upon.</li>
- </ul>
- <p><b>FAQ</b> by Bjorn</p>
-
-
- <ul>
- <li>We don't have a FAQ yet, but we need one. We decided the best
- process to create the FAQ is to have a Bugzilla component for the FAQ
- and use that to drive the FAQ creation. We have requested the Eclipse
- infrastructure person to create the FAQ component.</li>
- </ul>
- <p><b>Adoption Rate of Contributed Code</b> by Jochen</p>
-
-
- <ul>
- <li>Continued discussion of how quickly to put the contributed code into
- CVS; whether the code should be put in CVS before being reviewed, after
- being reviewed but before being refactored, etc. The issue remains open.</li>
- </ul>
- <p><b>M1 How Did We Do?</b> by David and Naci</p>
-
-
- <ul>
- <li>A series of measures of our progress:<ul>
- <li>Made the M1 date: <b><font color="#00CC66"><i>yes</i></font></b></li>
- <li>Promised function: <i><b><font color="#00CC66">mostly</font></b></i></li>
- <li>Unit tests complete and running as "passed": <font color="#FF0000">
- <i>no</i></font></li>
- <li>Test plan with use cases: <i><font color="#FF0000">no</font></i></li>
- <li>Function available one week before milestone: <i>
- <font color="#FF0000">no</font></i></li>
- <li>Design and APIs reviewed and issues answered before milestone: <i>
- <font color="#FF0000">no</font></i></li>
- <li>Community-users buy-in and/or excitement: <i>
- <font color="#FF0000">no - no announcement, no link to download page,
- no tutorials/examples/where to start, no new/noteworthy</font></i></li>
- <li>Included community contributed code: <i><b><font color="#00CC66">
- yes</font></b></i></li>
- </ul>
- </li>
- <li>For the M2 release, we need to behave more like a real software
- project including:<ul>
- <li>A development process document including the freeze-build-test
- cycle and when to freeze, when to provide the first integration build,
- testing, fixing, labeling in CVS, how to notify the world, etc.
- Include the list of tasks that committers must complete to be part of
- the M-Build (no more last minute dependency errors).</li>
- <li>A list of the built packages: WTP binary, WST binary, WTP SDK, WST
- SDK, Tests. Not that JST requires WST, so there is no separate JST
- binary or JST SDK.</li>
- <li>A requirement that no component be included in the release if
- there are no tests. The lack of unit tests and a test platform is our
- single biggest deficiency.</li>
- </ul>
- </li>
- </ul>
-
-
- <p><b>On the Queue for Next Week</b></p>
- <ul>
- <li>Discussion the WebDAV component</li>
- <li>Planning group report</li>
- <li>Milestone planning for M2</li>
- </ul>
-
-
-
-
-
-
-
-
-
-
- <p><font size="-1"><i>Minutes taken by Bjorn Freeman-Benson and posted by
- Bjorn Freeman-Benson, October 19, 2004</i></font></p>
- </td>
- </tr>
- </tbody></table>
-
-</body></html>
\ No newline at end of file
diff --git a/development/pmc_call_notes/2004-10-26.html b/development/pmc_call_notes/2004-10-26.html
deleted file mode 100644
index ebf10c0..0000000
--- a/development/pmc_call_notes/2004-10-26.html
+++ /dev/null
@@ -1,96 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html><head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"></head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - October
- 26,
- 2004</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <p>Attending: David Williams, Mitch Sonies, Naci Dai, Christophe Ney, Dominique De Vito</p>
-
-
- <p><b>Planning Comittee Status</b> by Dominique</p>
-
- <ul>
-
- <li>Good news about the new infrastructure: the new webmaster is very helpful and quick to reply !</li>
- <li>Our 2 new committers, Valeriy Pelyushenko and Gorkem Ercan, have now their committer rights</li>
- <li>According to email exchanges with some OSS Eclipse plugins' teams, the WTP project appears now more attractive to new contributors</li>
- <li>We are waiting the Bjorn's return about the contact with Alex Fitzpatrick from the OSS <a href="http://sourceforge.net/projects/jseditor/">JSEditor</a> Eclipse plugin</li>
- <li>Uwe Voigt, of the <a href="http://sourceforge.net/projects/dbedit">DbEdit</a> plugin, would be interested in bringing
-his experience and knowledge into the WTP project</li>
- <li>Ed Merks, from the <a href="http://www.eclipse.org/xsd/">XSD</a> Eclipse technology project, seems interested to work on WTP schema capabilities. To confirm.</li>
- <li>Exchange of emails with <a href="http://www.eclipse.org/pollinate/">Pollinate</a> for a better WTP/Pollinate synchronization and a better WTP milestones planification. In short term, Pollinate
- is interested in JSP editor and flexible project layout. In a longer term, Pollinate is interested in
- Web Services support (not before Q2 2005).</li>
- <li>Dominique to post M4-M5 draft, this evening, on wtp-pmc, for first comments and then, on eclipse.org for community comments</li>
- </ul>
-
-
- <p><b>Charter</b> by Christophe</p>
-
- <ul>
- <li>To resolve a potential ambiguity in the charter about committer vote approval, we have voted
- 'yes' for the <a href="./2004-10-19.html">charter change proposal</a> of the previous week.</li>
- <li>The committer vote approval for Jens Lukowski is still on-going. Due to the charter change, the time counter is reset
- to zero and this vote process will last no more than 7 days, starting from now</li>
- </ul>
-
-
- <p><b>Milestone Dates</b> by David </p>
-
- <ul>
- <li>David mentionned WTP M2 should be based on Eclipse 3.1M4, not on 3.1M3 as stated by the current milestone plan. Everyone agrees.
- <li>Dominique to do the correction of that mistake on eclipse.org</li>
- </ul>
-
-
-
- <p><b>Adoption Rate of Contributed Code</b> by Naci</p>
-
- <ul>
- <li>Continued discussion of how quickly to put the contributed code into CVS.</li>
- <li>Naci brings the idea of an incubator, a space for code under review, before putting it into CVS.</li>
- <li>Should we define a workflow for acceptation of code in main stream WTP codebase !?</li>
- <li>David proposed the idea to put code into CVS, that may be, or not upon status, part of the builds.</li>
- <li>We need to formalize better, to write down somes notes about the review process and the CVS acceptance</li>
- <li>David is going to check the Eclipse development process and to highlight that process to look for guidelines</li>
- </ul>
-
-
-
- <p><b>On the Queue for Next Week</b></p>
-
- <ul>
- <li>Discussion the WebDAV component (reflexion in progress)</li>
- <li>'Making noise' by Mitch</li>
- </ul>
-
-
-
-
-
-
- <p><font size="-1"><i>Minutes taken by Christophe Ney, October 26, 2004, and posted by
- Dominique De Vito, the following day</i></font></p>
- </td>
-
- </tr>
- </tbody></table>
-
-</body></html>
\ No newline at end of file
diff --git a/development/pmc_call_notes/2004-11-02.html b/development/pmc_call_notes/2004-11-02.html
deleted file mode 100644
index 9d11c02..0000000
--- a/development/pmc_call_notes/2004-11-02.html
+++ /dev/null
@@ -1,144 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html><head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"></head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - November
- 2,
- 2004</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <p>Attending: Naci Dai, Dominique De Vito, Bjorn Freeman-Benson, Jochen
- Krause, Mitch Sonies, David Williams<br>
- Regrets: Christophe Ney</p>
-
-
- <p><b>Meeting Time</b> by Bjorn</p>
-
- <ul>
- <li>The conference call has, by consensus, been moved earlier by one
- hour.</li>
- </ul>
-
-
- <p><b>Jens Lukowksi Committer Vote</b> by Dominique</p>
-
- <ul>
- <li>More than ten positive votes and on negative votes were received.
- The PMC agreed with the committers that Jens should be elevated to
- committer status.</li>
- </ul>
-
-
- <p><b>Server Adapters</b> by Naci</p>
-
- <ul>
-
- <li>We will host adapters for commercial servers as long as the adapter
- is open source and there is a developer attached to the project for
- maintenance.</li>
-
- <li>We will encourage companies to host their own update site for their
- adapter so that the company can make changes, point releases, etc.
- without being tied to the WTP release cycle.</li>
-
- <li>Rationale: we will define a stable API for adapters, but the
- companies should do their own builds of their own adapters.</li>
-
- <li>We are considering an extension point that allows advertising of
- adapter update sites. This would provide a scheme for third-parties to
- have adapters hosted elsewhere but still easily usable from within the
- WTP tools. Naci and Arthur will create a feature request in
- Bugzilla.</li>
- </ul>
-
-
- <p><b>Pagnagotis's patches and the wtp-dev mailing list</b> by Bjorn</p>
- <ul>
- <li>We must be more responsive to community input. We all agreed to
- this.</li>
- <li>We also suggest that patches be submitted via bugzilla for ease of
- tracking.</li>
- </ul>
- <p><b>WST Components and Leads</b> by Arthur</p>
- <ul>
- <li><a href="http://www.eclipse.org/webtools/wst/components.html">
- Reviewed</a> and approved with minor changes.</li>
- </ul>
- <p><b>JST Components and Leads</b> by Naci</p>
- <ul>
- <li><a href="http://www.eclipse.org/webtools/jst/components.html">
- Reviewed</a> and approved with minor changes.</li>
- </ul>
- <p><b>WTP Contributors Page</b> by Bjorn</p>
- <ul>
- <li>Everyone's job to keep
- <a href="http://www.eclipse.org/webtools/people/contributors.html">
- this page</a> current.</li>
- </ul>
- <p><b>CVS and Website</b> by Bjorn</p>
- <ul>
- <li>Simple single CVS project that can be edited with Eclipse</li>
- <li>Server-side script will copy the HEAD of the CVS tree to the website
- whenever the HEAD changes</li>
- </ul>
-
-
-
- <p><b>On the Queue for Next Week</b></p>
-
- <ul>
- <li>Discussion the WebDAV component (reflexion in progress)</li>
- <li>'Making noise' by Mitch</li>
- <li>M2 Milestone planning by Bjorn<ul>
- <li>Features; schedule; testing; releasing</li>
- </ul>
-
-
-
-
-
-
- </li>
- <li>WTP recontribution plan by Arthur</li>
- <li>Planning group by Dominiqie<ul>
- <li>PHP Editor; M4-M5 milestone plan</li>
- </ul>
-
-
-
-
-
-
- </li>
- <li>Bug validation by Bjorn</li>
- <li>Technology PMC SOA proposal - what to do? by Bjorn</li>
- <li>Project granularity by Arthur</li>
- </ul>
-
-
-
-
-
-
- <p><font size="-1"><i>Minutes taken by, and posted by, Bjorn
- Freeman-Benson, November 2, 2004</i></font></p>
- </td>
-
- </tr>
- </tbody></table>
-
-</body></html>
\ No newline at end of file
diff --git a/development/pmc_call_notes/2004-11-09.html b/development/pmc_call_notes/2004-11-09.html
deleted file mode 100644
index 2c03a25..0000000
--- a/development/pmc_call_notes/2004-11-09.html
+++ /dev/null
@@ -1,126 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html><head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"></head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - November
- 9,
- 2004</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <p>Attending: Naci Dai, Dominique De Vito, Bjorn Freeman-Benson, David Williams,
- Christophe Ney<br>
- Regrets: Arthur Ryman</p>
-
-
- <p><b>Meeting Time</b> by Bjorn</p>
-
- <ul>
- <li>Promptness would be appreciated.</li>
- </ul>
-
-
- <p><b>JBoss Contribution Status</b> by Naci</p>
-
- <ul>
- <li>Should we include their binary library; decision is yes if EPL'd</li>
- <li>Need to review their code based on the guidelines</li>
- </ul>
-
-
- <p><b>PHP Project</b> by Dominique</p>
-
- <ul>
- <li>Are looking to see if someone wants to start a PHP project under
- Technology so that we can use it as an example of how to extend our
- code, etc. <a href="http://www.phpeclipse.de/">www.phpeclipse.de</a>
- looks to have a CPL license - wonder if he is interested in an Eclipse
- project - one that fits well with WTP?</li>
- </ul>
-
-
- <p><b>M4-M5 Milestones and Planning Group </b>by Dominique </p>
-
- <ul>
- <li>limited feedback so far </li>
- <li>in order to sync up with the 3.1 releases, M4 should be our last
- milestone </li>
- <li>telling people to stay tuned and waiting for refresh</li>
- </ul>
-
-
- <p><b>Help Wanted Page</b> by Dominique</p>
-
- <ul>
- <li>bug filtering, validation, and prioritization</li>
- <li>website restructuring</li>
- <li>each component should eventually have their own list bugzilla and
- inbox email aliases</li>
- </ul>
-
-
- <p><b>Technology PMC SOA Proposal</b> by Bjorn</p>
-
- <ul>
- <li>reviewed the proposal</li>
- <li>concluded that if tools for existing specs, it should be part of WTP
- </li>
- <li>if exploratory, it should be based on WTP </li>
- <li>perhaps start as a Technology project and then join WTP as a
- third-sub-project</li>
- <li>timing not so critical; 3-4 months</li>
- </ul>
-
-
- <p><b>EclipseCon WTP Tutorial</b> by Naci</p>
-
- <ul>
-
- <li>will look around for a speaker</li>
- </ul>
-
-
-
- <p><b>On the Queue for Next Week</b></p>
-
- <ul>
- <li>'Making noise' by Mitch</li>
- <li>M2 Milestone planning by Bjorn<ul>
- <li>Features; schedule; testing; releasing</li>
- </ul>
-
-
-
-
-
-
- </li>
- <li>Project granularity by Arthur</li>
- </ul>
-
-
-
-
-
-
- <p><font size="-1"><i>Minutes taken by, and posted by, Bjorn
- Freeman-Benson, November 15, 2004</i></font></p>
- </td>
-
- </tr>
- </tbody></table>
-
-</body></html>
\ No newline at end of file
diff --git a/development/pmc_call_notes/2004-11-16.html b/development/pmc_call_notes/2004-11-16.html
deleted file mode 100644
index ad1df9a..0000000
--- a/development/pmc_call_notes/2004-11-16.html
+++ /dev/null
@@ -1,135 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html><head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"></head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - November
- 16,
- 2004</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <p>Attending: Jochen Krause, David Williams,
- Dominique De Vito<br>
- Regrets: Arthur Ryman, Bjorn Freeman-Benson, Christophe Ney</p>
-
-
-
- <p><b>PHP Project</b> by Dominique</p>
-
- <ul>
- <li>Contact with the <a href="http://www.phpeclipse.de/">PHPEclipse</a> project.
- This project already uses some WTP components and is expected to follow WTP components
- evolution. Discussion on-going to see if the team is interested in an Eclipse
- project - one that fits well with WTP?</li>
-
- </ul>
-
-
- <p><b>Planning Group and M4-M5 Milestones </b>by Dominique </p>
-
- <ul>
- <li>Planning Group a bit late : feedback from Naci is not yet taken into account, the same for work on bugs into BugZilla </li>
- <li>A page 'help wanted' for calling external help, in specific area, has yet to be defined</li>
- <li>Component leaders will be helpful to finalize of the milestone plan</li>
- </ul>
-
-
-
- <p><b>EclipseCon and ObjectWebCon events about WTP</b> by David, Jochen</p>
-
- <ul>
-
- <li>WTP tutorials will be presented during EclipseCon, technical details will be given during the code camp</li>
- <li>ObjectWebCon will host also WTP presentations, for example, a SSE presentation by Innoopract/Jochen</li>
- </ul>
-
-
-
-
-
- <p><b>Talk about M2</b></p>
-
- <ul>
- <li>David plan for WTP M2 testing has got positive feedback, looks OK</li>
- <ul>
- <li>
-12/10 (Friday) -
-candidate build for M2 (on Eclipse M3),
-component, test plans complete, component
-teams (and community) begins "milestone
-testing". (typically, there might be 2 to 3
-days of "formal testing" but its up to each
-component team, to satisfy their test plan,
-plus, hopefully, the community will pick up
-builds and find some bugs for us).</li>
- <li>12/20 (Friday) -
-upgrade build for final candidate build (include
-Eclipse M4, and "most recent" versions of pre-req
-projects).</li>
- <li>
-12/20 to 12/22, "regression tests" with new base/pre-reqs.</li>
- <li>
- 12/22 (Wednesday) milestone M2 declared and promoted.</li>
- </ul>
- </li>
- <li>M2 content: all items with high and medium priority should be ready with M2, we have to check with Naci about EJB Wizard</li>
- <li>M2 content may be modified depending on component leaders feedback</li>
- </ul>
-
-
-
-
-
-
- <p><b>Code refresh and build process</b> by David</p>
-
- <ul>
-
- <li>Code refresh still ongoing into CVS, end expected next week</li>
- <li>Build process has yet to be fixed as soon as possible</li>
-
- </ul>
-
-
- <p><b>On the Queue for Next Week</b></p>
-
- <ul>
- <li>'Making noise' by Mitch</li>
- <li>M2 Milestone planning by Bjorn<ul>
- <li>Features; schedule; testing; releasing</li>
-
- </ul>
-
-
- </li>
- <li>Project granularity by Arthur</li>
- <li>Requirements</li>
- </ul>
-
-
-
-
-
-
- <p><font size="-1"><i>Minutes taken by Jochen Krause and Dominique De Vito, and posted by, Dominique De Vito
- , November 16, 2004</i></font></p>
- </td>
-
- </tr>
-
- </tbody></table>
-
-</body></html>
\ No newline at end of file
diff --git a/development/pmc_call_notes/2004-11-23.html b/development/pmc_call_notes/2004-11-23.html
deleted file mode 100644
index 0856443..0000000
--- a/development/pmc_call_notes/2004-11-23.html
+++ /dev/null
@@ -1,119 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html><head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"></head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - November
- 23,
- 2004</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <p>Attending: Jochen Krause, David Williams,
- Dominique De Vito, Arthur Ryman, Bjorn Freeman-Benson, Christophe Ney</p>
-
-
-
- <p><b>M2 Status</b> by David </p>
-
-
-
- <ul>
- <li>
- The test plans should be published by 12/10; component leads should
- write them
- <ul>
- <li>12/10 (Friday) - candidate build for M2 (on Eclipse M3),
- component test plans complete, component teams (and community)
- begins "milestone testing". </li>
- <li>12/20 (Friday) - upgrade build for final candidate build
- (include Eclipse M4, and "most recent" versions of pre-req
- projects). </li>
- <li>12/20 to 12/22, "regression tests" with new base/pre-reqs. </li>
- <li>12/22 (Wednesday) milestone M2 declared and promoted.</li>
- </ul>
- </li>
- <li>
- Naci will remove the unspec'ed items from the features (e.g., web services), but they can stay in CVS
- </li>
- <li>
- We seem
- to be on track for <a href="../planning/milestone_plan_1_0.html"> our high priority M2 items and some medium M2 items</a>
- </li>
- </ul>
-
-
-
- <p><b>Code Refresh </b>by Arthur </p>
- <ul>
- <li>Target completion is the end of the next week</li>
- <li>Main work items for future milestones: API definitions, automated
- tests, performance tests</li>
- </ul>
-
-
-
- <p><b>EPL/CPL Licensing </b>by Bjorn </p>
-
- <ul>
- <li>Dominique is working on gathering the information about all our
- contributors</li>
- </ul>
- <p><b>Binary Distribution of Jars</b> by Bjorn and Arthur </p>
- <ul>
- <li>Plan is to gather all the third-party content; will be review with
- PMC; target for completion - 12/12</li>
- </ul>
- <p><b>Marketing</b> by Mitch </p>
- <ul>
- <li>The Eclipse PR/marcom has seemed disbanded </li>
- <li>We're going to focus on the fact that WTP is compelling to
- users </li>
- <li>We need to create the presentations of things to talk about and we
- need people who go around to talk to media channels</li>
- <li>Less bizdev and more talking about what we are doing</li>
- <li>Look at the project website as a primary exposure vehicle - use our
- own site as a marketing channel; better than the awkward site we have
- now </li>
- <li>We need an organized way to collect these opportunities and have a
- mechanism to represent ourselves at them</li>
- <li>Now that we are about to release something worthwhile (M2), we
- should ramp up our marketing to users.</li>
- </ul>
-
-
- <p><b>On the Queue for Next Week</b></p>
-
- <ul>
- <li>Discussion of how the Requirements, Planning, and Architecture
- groups are functioning</li>
- <li>Project granularity by Arthur</li>
- <li>Requirements</li>
- </ul>
-
-
-
-
-
-
- <p><font size="-1"><i>Minutes taken and posted by Bjorn Freeman-Benson,, November
- 24, 2004</i></font></p>
- </td>
-
- </tr>
-
- </tbody></table>
-
-</body></html>
\ No newline at end of file
diff --git a/development/pmc_call_notes/2004-11-30.html b/development/pmc_call_notes/2004-11-30.html
deleted file mode 100644
index 02cc1fd..0000000
--- a/development/pmc_call_notes/2004-11-30.html
+++ /dev/null
@@ -1,169 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html><head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"></head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - November
- 30,
- 2004</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <p>Attending: Jochen Krause, David Williams,
- Dominique De Vito, Arthur Ryman, Bjorn Freeman-Benson, Christophe Ney</p>
-
-
-
- <p><b>Committer Inventory</b> by Bjorn</p>
-
-
-
- <ul>
- <li>Dominique and Bjorn are puzzled about what we are supposed to be
- doing. Action item: Bjorn will ask Mike exactly what we need to do for
- this.</li>
- </ul>
-
-
-
- <p><b>Code Contribution Inventory</b> by Bjorn</p>
-
-
-
- <ul>
- <li>The work is distributed between Arthur and Naci; IBM has done
- theirs; Dec 2 for the redistribution inventory from IBM</li>
- </ul>
-
-
-
- <p><b>Marshall Culpepper Committer Vote</b> by Dominique</p>
-
-
-
- <ul>
- <li>Positive vote = welcome to Marshall as a committer</li>
- </ul>
-
-
-
- <p><b>CVS and Website</b> by Arthur and Bjorn</p>
-
-
-
- <ul>
- <li>Denis has prototyped the "website in CVS but served via Apache"
- scheme</li>
- <li>Arthur will do the work of moving the website to CVS and then send
- Denis an email to ask him to make the process change</li>
- <li>The people with WebDAV write access will become committers</li>
- </ul>
-
-
-
- <p><b>M2 Shutdown</b> by David </p>
-
-
-
- <ul>
- <li>David will post plan to website</li>
- <li>component leads will write new & noteworthy</li>
- <li>new & noteworthy consolidation will be done by Jochen</li>
- <li>discussion of how to build and what plugins to load and why it won't
- build</li>
- <li>we need more documentation about how to build the system and how to
- develop the system</li>
- <li>who is creating the tutorial? what's the plan? who is creating the
- development test plan? who is creating the build tutorial? what are the
- features?</li>
- <li>We should not end M2 until we meet the exit criteria = "builds
- correctly; has tutorial?"</li>
- <li>simulate what a contributor would be doing.</li>
- </ul>
-
-
-
- <p><b>M2 Status</b> by David </p>
-
-
-
- <ul>
- <li>
- The test plans should be published by 12/10; component leads should
- write them
- <ul>
- <li>12/10 (Friday) - candidate build for M2 (on Eclipse M3),
- component test plans complete, component teams (and community)
- begins "milestone testing". </li>
- <li>12/20 (Friday) - upgrade build for final candidate build
- (include Eclipse M4, and "most recent" versions of pre-req
- projects). </li>
- <li>12/20 to 12/22, "regression tests" with new base/pre-reqs. </li>
- <li>12/22 (Wednesday) milestone M2 declared and promoted.</li>
- </ul>
- </li>
- <li>
- Naci will remove the unspec'ed items from the features (e.g., web services), but they can stay in CVS
- </li>
- <li>
- We seem
- to be on track for <a href="../planning/milestone_plan_1_0.html"> our high priority M2 items and some medium M2 items</a>
- </li>
- </ul>
-
-
-
- <p><b>Help Wanted List</b></p>
- <ul>
- <li>Bugzilla filtering is Bjorn's top desire</li>
- <li>The idea is to have a list of things that the project needs help
- with, tasks ranging from a couple hours here and there up through major
- efforts</li>
- <li>Dominique will write it up and circulate a proposal to PMC</li>
- <li>Then we'll put in on the newsgroup and the website</li>
- </ul>
- <p><b>Project Granularity</b> by Arthur</p>
- <ul>
- <li>Which Eclipse features should we distribute</li>
- <li>We should host an update site as well as the straight binary
- download (in fact, one might argue that we should only have the update
- site)</li>
- </ul>
-
-
- <p><b>On the Queue for Next Week</b></p>
-
- <ul>
- <li>Discussion of how the Requirements, Planning, and Architecture
- groups are functioning</li>
- <li>Requirements</li>
- <li>M2 Shutdown Plan</li>
- <li>Report from the Planning Council</li>
- </ul>
-
-
-
-
-
-
- <p><font size="-1"><i>Minutes taken and posted by Bjorn Freeman-Benson,,
- December 4, 2004</i></font></p>
- </td>
-
- </tr>
-
- </tbody></table>
-
-</body></html>
\ No newline at end of file
diff --git a/development/pmc_call_notes/2004-12-14.html b/development/pmc_call_notes/2004-12-14.html
deleted file mode 100644
index 50bd9ba..0000000
--- a/development/pmc_call_notes/2004-12-14.html
+++ /dev/null
@@ -1,144 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html><head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"></head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call -
- December 14,
- 2004</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <p>Attending: David Williams,
- Dominique De Vito, Arthur Ryman, Ivelin Ivanov, Jochen Krause</p>
-
-
-
- <p><b>Code Contribution Inventory</b> by Arthur</p>
-
-
-
- <ul>
- <li>3 rd party content that may not be compatible with EPL has been
- removed (M2 is only affected with regard to validation - Xerces parser)</li>
- <li>Eclipse PMC will decide on including 3 rd party libraries</li>
- <li>DTDs are not shipped anymore - first time access of these DTDs will
- require online internet access (DTDs remain cached afterwards)</li>
- <li>Initial IBM code contribution (zip) has been removed as it is
- obsolete</li>
- </ul>
-
-
-
-
- <p><b>Contribution questionaire for significant contributions </b>by
- Dominique</p>
- <ul>
- <li>Arthur (IBM), Naci (Eteration) and Ivelin (JBoss) are in process
- preparing the questionaire (Dec 21)</li>
- </ul>
-
-
-
-
- <p><b>Committer status of Deniz</b> by Naci</p>
-
-
-
- <ul>
- <li>Deniz has changed jobs and does not have resources anymore to work
- on WTP</li>
- <li>Naci will ask him to request the PMC to remove him as a committer</li>
- </ul>
-
-
-
- <p><b>M2 Status</b> by David, Naci</p>
-
-
-
-
- <ul>
- <li>establish fallback-Plan for M2 with respect to moving up to Eclipse
- M4</li>
- <li>create an integration build with M4 - if we detect problems we will
- declare the last build with Eclipse M3 as Web Tools M2</li>
- <li>Naci will publish the build schedule for M2</li>
- <li>Problems with build machine led to gaps in the build cycle, there
- are work arounds for finalizing M2, build scripts will be updated after
- M2 (Naci)</li>
- </ul>
-
-
-
- <p><b>Web Tools Download server</b> by Arthur</p>
-
-
-
-
- <ul>
- <li>Web Tools download space is exhausted</li>
- <li>Need to delete old builds - keep nightly builds for 2 weeks and all
- integration builds since the last milestone release (Naci)</li>
- </ul>
-
-
-
- <p><b>JBoss Server Integration</b> by Ivelin</p>
-
- <ul>
- <li>Naci and David gave feedback</li>
- <li>Marshall is working to adapt the API changes for JBoss support</li>
- <li>The contribution will not make it into M2, but will be ready soon
- afterwards</li>
- <li>Integration testing support for JBoss shall become part of the
- builds (Ivelin)</li>
- </ul>
-
-
- <p><b>EclipseCon</b> by Jochen</p>
-
- <ul>
- <li>Code camps are no longer planned for EclipseCon</li>
- <li>WTP will do a project sprint, open to all interested developers</li>
- <li>We may want to organize a project meeting at EclipseCon</li>
- </ul>
-
-
- <p> </p>
-
-
- <p><b>On the Queue for Next Week</b></p>
-
- <ul>
- <li>Discussion of how the Requirements, Planning, and Architecture
- groups are functioning</li>
- <li>M2</li>
- </ul>
-
-
-
-
-
-
- <p><font size="-1"><i>Minutes taken by Jochen Krause and posted by Bjorn Freeman-Benson,,
- December 20, 2004</i></font></p>
- </td>
-
- </tr>
-
- </tbody></table>
-
-</body></html>
\ No newline at end of file
diff --git a/development/pmc_call_notes/2004-12-21.html b/development/pmc_call_notes/2004-12-21.html
deleted file mode 100644
index cddd47f..0000000
--- a/development/pmc_call_notes/2004-12-21.html
+++ /dev/null
@@ -1,72 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html><head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"></head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - December 21, 2004</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <p>Attending: David Williams, Christophe Ney, Arthur Ryman, Mitch Sonies,
- Naci Dai, Dominique de Vito </p>
- <p>Excused: Jochen Krause, Bjorn Freeman-Benson </p>
- <p><b>Topic Discussed</b></p>
- <ul>
- <li>Proposal for web site structure enhancement should be ready by tomorrow</li>
- <ul>
- <li>will post the url to pmc for comment tomorrow</li>
- </ul>
- <li>M2 readiness</li>
- <ul>
- <li>some problem with server tools seems to be resolved</li>
- <li>a lot of anoying little problem make this release not very high quality but no show stopper</li>
- </ul>
- <li>plan for releade build</li>
- <ul>
- <li>Naci to post a note on the dav list with the plan</li>
- </ul>
- <li>Third party jars</li>
- <ul>
- <li>Adrian Cho (lawyer at IBM) to work with Dominique on resolving this legal issue</li>
- </ul>
- <li>Proposal to evaluate the TCP-IP sniffer (Test Tools)</li>
- <ul>
- <li>David Lauzon to open feature request on this</li>
- </ul>
- <li>For information</li>
- <li>Arthur suggest to Announce ObjectWebCon on WTP project web site and to announce this event on the newsgroup</li>
- <li>Mitch and Arthur to discuss web site content and make a proposal</li>
- <ul>
- <li>Putz together a press release for all WTP related events at EclipseCon</li>
- </ul>
- <li>EclipseConference</li>
- <ul>
- <li>3talks, a poster, a panel, a BOF and the code camp</li>
- <li>Lawrence Mandel will be working with Arthur as Ecosystem evangelist, he will help organizing</li>
- </ul>
- </ul>
-<p><b>Next Call</b></p>
-<p>No call next week, next call an January, 4th</p>
-<p>HAPPY HOLIDAYS!</p>
-<p><b><font size="-1"><i>Minutes taken by Christophe Ney and posted by Jochen Krause,
- February 8, 2005</i></font></td>
- </tr>
-
- <tr>
- <td> </td>
-
- </tr>
-
- </tbody></table>
-
-</body></html>
\ No newline at end of file
diff --git a/development/pmc_call_notes/2004Q4-plan-update.html b/development/pmc_call_notes/2004Q4-plan-update.html
deleted file mode 100644
index b5ef87c..0000000
--- a/development/pmc_call_notes/2004Q4-plan-update.html
+++ /dev/null
@@ -1,87 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html><head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"></head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font face="Arial,Helvetica" color="#FFFFFF">2004 Q4 WTP Quarterly Plan
- Update</font></b></td>
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <b>Project Name:</b> Web Tools Platform Project
- <p><b>Project Leaders:</b> Bjorn Freeman-Benson, Christophe Ney, Dominique
- de Vito, Arthur Ryman, Naci Dai, Jochen Krause, David Williams, Mitch
- Sonies </p>
- <p><b>Project Description:</b>
- <a href="http://www.eclipse.org/webtools/project-scope.html">
- http://www.eclipse.org/webtools/project-scope.html </a></p>
- <p><b>Executive Summary: <br>
- </b>Effectively, the project did not start until September due to the
- combination of vacation schedules, the commercial commitments of a major
- contributor, and other factors. However, the project is now starting and
- we are taking the first steps in the right directions. Our biggest problem
- is turning resource contribution commitments into actions, however we do
- have a number of new active non-IBM committers, and we have formed working
- group to gather in more people. </p>
- <p>The first chunks of code have been evaluated, revamped, and moved from
- the initial contributions into the CVS repository. We expect the pace of
- this movement to accelerate in the next quarter. We are committed to
- committing [sic] as fast as the community can understand the architecture,
- design, and code. We are working on the pieces on the critical path to a
- larger framework, e.g., structured source editing which is a prerequisite
- for JSP editing, etc. </p>
- <p>We have found starting this project to be harder that we anticipated
- given its unique situation of being (a) the first time such a diverse team
- has been tried from day one, and (b) the first time a project has started
- with a large code contribution that many contributors must become familiar
- with. </p>
- <p><b>Acknowledgements:</b> <br>
- We thank the Eclipse Platform build team for helping with our build
- system, and Jim des Rivieres for help with our APIs and naming schemes.
- </p>
- <p><b>List of currently shipping software distributions (if more than one,
- please list by component name):</b> <br>
- Nothing is shipping, but then we hadn't planned to ship anything yet. </p>
- <p><b>Key Release Dates:</b> </p>
- <ul>
- <li>M1 - October 15, 2004 - Finalize build infrastructure and server
- tools. </li>
- <li>M2 - December 15, 2004 - Flexible project layout. Initial structure
- source editing and EJB tools. </li>
- <li>M3 - February 15, 2005 - Improved structured source editing and EJB
- tools. Database tools and initial Web Services. </li>
- </ul>
- <p><b>URL to current planning document:</b> <br>
- <a href="http://www.eclipse.org/webtools/development/planning/milestone_plan_1_0.html">
- http://www.eclipse.org/webtools/development/planning/milestone_plan_1_0.html</a>
- and
- <a href="http://www.eclipse.org/webtools/development/eclipse_WTP_project_plan_1_0.html">
- http://www.eclipse.org/webtools/development/eclipse_WTP_project_plan_1_0.html
- </a></p>
-
-
-
-
-
-
-
-
-
-
- <p><font size="-1"><i>Secretary: Bjorn Freeman-Benson, October 12, 2004</i></font></p>
- </td>
- </tr>
- </tbody></table>
-
-</body></html>
\ No newline at end of file
diff --git a/development/pmc_call_notes/2005-01-04.html b/development/pmc_call_notes/2005-01-04.html
deleted file mode 100644
index eb44d17..0000000
--- a/development/pmc_call_notes/2005-01-04.html
+++ /dev/null
@@ -1,93 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html><head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"></head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - January 4, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <p>Attending: David Williams, Christophe Ney, Arthur Ryman, Mitch Sonies,
- Naci Dai, Jochen Krause</p>
-
-
-<p><b>Tracking code contributions</b></p>
-<ul>
-<li>Adrian Cho currently designing the form for contributors</li>
-<li>Size of a contribution is as small as 2 lines of code to correct a bug</li>
-</ul>
-
-<p><b>M2 post-mortem</b></p>
-<ul>
-<li>Was released on time with expected features - BRAVO!</li>
-<li>Licensing information is missing (Action item: Jochen to resolve this (P1))</li>
-<li>Documentation is still poor
-<ul>
-<li><font size="2">Documentation to be high priority for M3</font></li>
-<li><font size="2">IBM will contribute online help (but links to commerial
-product need to be reworked)</font></li>
-</ul>
-
-</li>
-<li>build process to be improved<ul>
-<li><font size="2">Several problems identified with existing Eclipse Build tools</font></li>
-<li><font SIZE="2">strategy is to submit bug report to them and develop
-alternative tools with Ant task (Naci)</font></li>
-<li><font SIZE="2">should automate the process of promoting the build to a
-milestone release</li>
-</ul>
-
-</li>
-</font>
-<li>Missing update Manager<font SIZE="2"><ul>
-<li>test going on with the Derby team</li>
-<li>open discussion when some feedback available from Derby experience</li>
-<li>Jeff Lou to look at the process for WTP to use Eclipse Update Site</li>
-<li> </li>
-</ul>
-
-</font></li>
-</ul>
-
- <p><b>Milestone plans for M3-M4</b></p>
-<ul>
-<li>target for component leads to provide milestone plan within 15 days</li>
-<li>arthur team looking at automation of milestone plan compilation</li>
-</ul>
-
- <p><b>Misc.</b></p>
-<ul>
-<li>Arthur to send a note to wtp list for cvs access on web site</li>
-<li>Jochen to design a "new and noteworthy" page</li>
-<li>Material used during conferences to be published after the events</li>
-<li>Upcoming event page to be created (ObjectWebCon, EclipseCon)</li>
-<li>Next Meeting on Tuesday (Jochen and Christophe will not attend)</li>
-</ul>
-
- <p> </p>
-
- <p><font size="-1"><i>Minutes taken by Christophe Ney and posted by Jochen Krause,
- February 7, 2005</i></font></p>
- </td>
-
- </tr>
-
- <tr>
- <td>
- </td>
-
- </tr>
-
- </tbody></table>
-
-</body></html>
\ No newline at end of file
diff --git a/development/pmc_call_notes/2005-02-01.html b/development/pmc_call_notes/2005-02-01.html
deleted file mode 100644
index 28d7049..0000000
--- a/development/pmc_call_notes/2005-02-01.html
+++ /dev/null
@@ -1,72 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html><head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"></head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call -
- Februar 1, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <p>Attending: David Williams,
- Dominique De Vito, Arthur Ryman, Mitch Sonies, Marshall Culpepper, Jochen Krause</p>
-
-
-<p><b>Licensing Issues</b></p>
-<ul>
-<li>Contribution form not required for JBoss, since all code was developed as part of the WTP project </li>
-<li>Final form of committer questionnaire awaiting completion by the Eclipse parent </li>
-<li>Action items: None </li>
-</ul>
-
-<p><b>Marketing Track</b></p>
-<ul>
-<li>Set up analyst presentations in conjunction with EclipseCon</li>
-<li>Calendar conflict between JBoss & W3C events noted </li>
-<li>Lawrence Mandel will present marketing activity summary at start of weekly PMC calls </li>
-<li>Action items: Mitch Sonies to coordinate with Ian Skerrett at Eclipse </li>
-</ul>
-
-<p><b>Requirements Track</b></p>
-<ul>
-<li>Functionality now substantially set for 1.0 release</li>
-<li>Action items: Jochen Krause to collect additional requirements </li>
-</ul>
-
-<p><b>Web Site</b></p>
-<ul>
-<li>New site content has been posted </li>
-<li>WTP now a top-level site (not pages within Eclipse.org) </li>
-<li>Moving site to XML/XSLT stylesheets and eliminating use of frames </li>
-<li>ANT scripts developed </li>
-<li>Action items: Arthur Ryman: post site editing FAQ. All: please report any broken links. </li>
-</ul>
-
-<p><b>M3 Update</b></p>
-<ul>
-<li>Proceeding on course. Next step will be Feb10 interim build of M5 of base. (Will provide support for Web services and Axis.)</li>
-<li>Third-party code is being factored out as plug-ins to simplify hosting & licensing issues </li>
-<li>Action items: none </li>
-</ul>
-
- <p><font size="-1"><i>Minutes taken by Mitch Sonies and posted by Jochen Krause,
- February 3, 2005</i></font></p>
- </td>
-
- </tr>
-
- </tbody></table>
-
-</body></html>
\ No newline at end of file
diff --git a/development/pmc_call_notes/2005-02-08.html b/development/pmc_call_notes/2005-02-08.html
deleted file mode 100644
index f532b72..0000000
--- a/development/pmc_call_notes/2005-02-08.html
+++ /dev/null
@@ -1,81 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html><head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - Februar 8, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <p>Attending: David Williams,
- Christophe Ney, Arthur Ryman, Jochen Krause</p>
-
-
-<p><b>Web Site</b></p>
-<ul>
-<li>Merge mileston planning into one document (add a topic to the plan items) -
-Arthur</li>
-<li>Update development conventions and guidelines, merge with WTP development
-practices - David </li>
-<li>Create howto for checking out projects from map files - David</li>
-<li>Remove links to obsolete info (project sets) - Arthur</li>
-<li>Update link to working groups with info about components - Jochen</li>
-</ul>
-
-<p><b>Requirements Track</b></p>
-<ul>
-<li>APIs should be defined by M4 and freezed by M5 (Arthur to check with Jim for
-"freeze" details)
-<ul>
-<li>A tool (API Scanning Tool) for checking the API has been developed with
-support from Jim de Rivieres<br>
-<font face="Arial" size="2">
-<span lang="EN-GB" style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">
-<a href="http://www.eclipse.org/webtools/development/apiscanner/apiscanner.html" style="color: blue; text-decoration: underline">
-http://www.eclipse.org/webtools/development/apiscanner/apiscanner.html</a></span></font></li>
-<li>The Tool will help to uncover API violations and in future to track changes
-in the API</li>
-</ul>
-
-</li>
-</ul>
-
-<p><b>M3 Update</b></p>
-<ul>
-<li>Publish dates relevant to the M3 release with regard to testing, builds, ...
-- David</li>
-</ul>
-
- <p><b>Misc</b></p>
- <ul>
- <li>Congratulations to ObjectWeb for obtaining the J2EE 1.4
- certification for Jonas</li>
- <li>Foster further adoption of Eclipse within ObjectWeb (e.g. Workshop
- at the next ObjectWeb architecture meeting) - Christophe</li>
- <li>Conference call notes will be published directly to the webtools
- website and copied to the pmc mailing list</li>
- </ul>
-
- <p><font size="-1"><i>Minutes taken and posted by Jochen Krause,
- February 8, 2005</i></font></p>
- </td>
-
- </tr>
-
- <tr>
- <td>
- </td>
-
- </tr>
-
- </tbody></table>
-
-</body></html>
\ No newline at end of file
diff --git a/development/pmc_call_notes/2005-02-15.html b/development/pmc_call_notes/2005-02-15.html
deleted file mode 100644
index 3efef23..0000000
--- a/development/pmc_call_notes/2005-02-15.html
+++ /dev/null
@@ -1,95 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html><head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - Februar
- 15, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <p>Attending: Dominique De Vito, David Williams, Arthur Ryman, Jochen Krause,
- Naci Dai, Bjorn Freeman-Benson, Mitch Sonies, Lawrence Mandel<br>
- Regrets: Christophe Ney</p>
-
-
-<p><b>EclipseCon </b>by Lawrence</p>
-<ul>
-<li>Summary of what's going on at EclipseCon for the WTP project including the
-project sprint, code camp, and the WTP "track"</li>
-<li>People who want to submit ideas for the Project Sprint on Monday evening
-should do so by the end of the week</li>
-<li>Jochen was chosen as our press spokesperson for EclipseCon</li>
-</ul>
-
-<p><b>WTP Day in Europe</b> by Christophe (via Bjorn)</p>
-<ul>
-<li>There was lots of positive feedback from the ObjectWeb members about having
-a WTP Workshop Day in 4Q2005. ObjectWeb is going to organize, support, and
-promote this.</li>
-</ul>
-
-<p><b>Architecture and Requirements Groups</b> by Arthur and David and Jochen</p>
-<ul>
-<li>Erich Gamma was removed from the Architecture Group. Kevin Haaland was
-added. David will update <a href="../../pmc.html">the website list</a>.</li>
-<li>The Requirements Group has been changed but the website not updated. Jochen
-will update the website.</li>
-<li>Also, the website list is not linked from the home page, so Arthur will fix
-that.</li>
-<li>The PMC agreed that in the future the Groups can change on their own, but
-that the PMC needs to be informed of such changes.</li>
-</ul>
-
- <p><b>Committers</b> by Arthur</p>
- <ul>
- <li>We removed two inactive committers: Deniz Seçilir and Valeriy
- Pelyushenko.</li>
- </ul>
-
- <p><b>Roadmap</b> by Arthur and Bjorn</p>
- <ul>
- <li>M4 is going to be the API Freeze milestone. Arthur will put his nice
- "what API Freeze means" document on the website.</li>
- <li>We are careful to acknowledge that we are going to violate our own
- APIs in our R1.0 - we do not have enough time to solidify <i>all</i> the
- APIs before our R1.0. We will distinguish between "official API" and
- "internal non-API that is currently used as API but will change in the
- future and cannot be relied on".</li>
- <li>As part of this freeze, we will be putting in place a process to
- control API changes. We anticipate that this process will consist of
- having the Planning Group review any API changes. Arthur is going to
- draft the process and distribute for comments. Part of the process will
- include the kind of justification that supplicants will be required to
- provide when requesting a variance from the freeze.</li>
- <li>Dominique will enhance the Planning Group to accommodate this new
- workload. He will review the membership, add people as necessary, etc.</li>
- <li>It is very important for us to have a Roadmap document contribution
- this week. The Roadmap will be published at EclipseCon and if we're the
- only project with no input, that would be awkward. Arthur will draft
- something by Wednesday.</li>
- </ul>
-
- <p><font size="-1"><i>Minutes taken and posted by Bjorn Freeman-Benson,
- February 15, 2005</i></font></p>
- </td>
-
- </tr>
-
- <tr>
- <td>
- </td>
-
- </tr>
-
- </tbody></table>
-
-</body></html>
\ No newline at end of file
diff --git a/development/pmc_call_notes/2005-02-21.html b/development/pmc_call_notes/2005-02-21.html
deleted file mode 100644
index 7883d25..0000000
--- a/development/pmc_call_notes/2005-02-21.html
+++ /dev/null
@@ -1,118 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html><head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - February
- 21, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <p>Attending: Dominique De Vito, David Williams, Arthur Ryman, Jochen Krause,
- Naci Dai, Bjorn Freeman-Benson, Tim Wagner, Lawrence Mandel, Christophe
- Ney</p>
-
-
-<p><b>Community </b>by Lawrence</p>
-<ul>
-<li>All is well</li>
-<li>The PMC thanks Lawrence for making our website good again. Thanks!</li>
-</ul>
-
-<p><b>BEA</b> by Tim</p>
- <ul>
- <li>BEA has joined Eclipse as a Strategic Developer and plans to
- contribute in at least two places: WTP and LDT. Tim gave a presentation
- about BEA's involvement including this statement "<i>As part of the
- Eclipse communitys acceptance of BEAs request to join as a strategic
- developer, we would like to formally request a leadership role in the
- Web Tools Project. </i>
- <p></p>
- <p><i>BEA brings a long history of experience with J2EE standards and
- server technologies, as well as award-winning tools for J2EE developers
- with its Workshop IDE. BEAs IDE technologies focus on open web
- standards and span a variety of use cases, including web applications
- and services, Java and JSP development, XML and XSD editing, data
- integration, portal development, and more. With a large installed base
- among the Fortune 500, BEA brings not only development resources but
- also a deep appreciation for the complexities of real world use cases to
- the Web Tools Project team. </i></p>
- <p></p>
- <p><i>As manager for both the compiler/languages team and the Workshop
- IDE core team within BEA, my background in J2EE tooling and
- language-based IDE services provides a useful reference point for
- participating in the leadership of this project. I have been an internal
- advocate for migrating to Eclipse as a tooling platform, and also for
- adopting the 1.0 GA of WTP as a product dependency for BEA. My top
- priority for the next several months is to ensure that WTPs scheduled
- milestones continue to be met without disruption. </i></p>
- <p></p>
- <p><i>In addition to my full time involvement in Eclipse project
- management, I would like to also introduce other BEA employees we have
- identified as being Eclipse committers.</i>"</li>
- <li>Tim identified BEA's #1 concern as driving WTP R1.0 to successful
- conclusion because BEA now has a product dependency on WTP (just like
- IBM does).</li>
- </ul>
- <p><b>PMC</b> by Bjorn</p>
- <ul>
- <li>After a long Q&A, the PMC voted to make the following changes to the
- PMC:<ul>
- <li>Tim Wagner to join as a co-lead</li>
- <li>Bjorn Freeman-Benson to step down as co-lead, but to remain on the
- PMC</li>
- <li>Mitch Sonies resigned from the PMC. The entire PMC expressed our
- regrets to Mitch and thanked him for helping to make WTP what it is
- today.</li>
- </ul>
- </li>
- </ul>
-
-<p><b>Committers</b> by Arthur</p>
-<ul>
-<li>The IBM team has identified five new committer candidates amongst its team.
-These candidates will need to be proposed and voted in by the existing
-committers, but everyone agreed that this was a good thing.</li>
-<li>In addition, the WSVT Technology sub-project is being rolled up into the WTP
-WST sub-project, and thus will bring two more new committers. Again, the WTP
-committers will need to vote them in, but otherwise the PMC agrees that these
-people are good.</li>
-</ul>
-
-<p><b>Requirements Groups</b> by Jochen</p>
-<ul>
-<li>The requirements group has deteriorated to just two people: Jochen and
-Arthur, so Jochen has requested that we reboot the group. Jochen will create the
-new membership list for the next PMC call.</li>
-<li>They plan to use Bugzilla to gather and discuss requirements.</li>
-</ul>
-
- <p><b>M3</b> by everyone</p>
- <ul>
- <li>We agreed that our schedule is in danger of slipping, but that we
- will choose quality over the date for M3.</li>
- </ul>
-
- <p><font size="-1"><i>Minutes taken and posted by Bjorn Freeman-Benson,
- February 21, 2005</i></font></p>
- </td>
-
- </tr>
-
- <tr>
- <td>
- </td>
-
- </tr>
-
- </tbody></table>
-
-</body></html>
\ No newline at end of file
diff --git a/development/pmc_call_notes/2005-03-08.html b/development/pmc_call_notes/2005-03-08.html
deleted file mode 100644
index 02c3bce..0000000
--- a/development/pmc_call_notes/2005-03-08.html
+++ /dev/null
@@ -1,132 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for March 8, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - March 8, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
-Attending: Tim Wagner [TW], Arthur Ryman [AR], David Williams [DW], Dominique De Vito [DV], Jochen Krause [JK], Naci Dai [ND]
-Others: Lawrence Mandel (representing WTP community) [LM]
-
-<h2>Procedural matters time and administration of PMC conference call</h2>
-<ul>
-<li>PMC agreed to continue meeting on a weekly basis to ensure timely review of all WTP matters
-<li>Meeting will commence one hour later (7am PST), starting next week
-<li>Meeting will move to a US conference service: 1-888-722-7907 (alt: 1-816-650-0713), passcode 9262945. Note that there are no local numbers outside the US with the Sprint service (let me know if this is an issue).
-</ul>
-
-<h2>Community from Lawrence Mandel</h2>
-<ul>
-<li>WTP help system initial content should be available by next week
-<li>Conference response: generally good, although code clinic was not advertised sufficiently (and far enough in advance); this was a general conference issue, and not specific to WTPs use of it
-Some general discussion around whether a code clinic was helpful given the prerelease state of WTP (DW), and whether condensing it to fewer hours in the future would be an improvement (JK). Whether code clinics should overlay the conference at all, or whether there simply isnt enough time for them to be useful was also raised as an issue (ND).
-<li>EclipseCorner looking for contributions from WTP. This would also help communicate to the wider community what WTP has made available so far and possibly help drive adoption. Publishing in broader forums (JDJ, e.g.) would also be helpful, and contributions here are actively solicited; talk to Lawrence if youre interested.
-</ul>
-
-[PMC members only for the remaining portion of the meeting]
-
-<h2>Requirements group reboot [JK] </h2>
-<ul>
-<li>Requirements group is currently composed of Jochen and Arthur.
-<li>BEA will appoint someone (either Tim or a WTP dev or pgm) to this group to participate as well.
-<li>Process: Group will reconstitute and meet; mechanism to solicit requirements from WTP consumers and possibly additional members to be its first order of business
-<li>Community is actively encouraged to participate at multiple levels, and committers or consumers of WTP interested in membership should identify themselves to JK or TW
-</ul>
-
-<h2>EclipseCon Debrief </h2>
-<ul>
-<li>General consensus that WTPs presence and message at conference was successful
-<li>Web Services generated interest from the press and several articles [JK]
-<li>WTP not on high download list; needs improved stability to drive adoption and more advertising of available features [ND]
-</ul>
-
-
-<h2>M3 Release Debrief</h2>
-<ul>
-<li>Significant improvements in process and code quality w.r.t. previous milestones, but more work on stability is needed to reach production quality and enable widespread adoption [ND]
-<li>Demos at conference generally went well and succeeded at illustrating new functionality
-</ul>
-
-<h2>Packaging Issues </h2>
-<ul>
-<li>Arthur noted that packaging is problematic too many loose files, too many 3rd party downloads (14!), etc.
-<li>Licensing issues affecting 3rd party redistribution rights are being worked through with the EMO, but it will take time.
-<li>WTP investigating the use of Eclipse update sites as a distribution mechanism for milestone releases; will require 4th component to version numbering (Jeffrey Liu working on this already)
-<li>Two ZIPped bundles proposed: all WTP, and all WTP + Eclipse platform; should ease installation hassles
-<li>Request to maintain some useful editing features (XML, e.g.) as separable from the entirety of WTP [JK]
-<li>New and Noteworthy isnt on the download page [JK].
-Should add link to upper right box in WTP home page.
-Main Eclipse page downloads reference is still to M2, and needs to be updated.
-</ul>
-
-<h2>New Committers </h2>
-The PMC reviewed the community voting results and accepted the following WTP committers: Jeffrey Liu, Kathy Chan, Keith Chong, Vijay Bhadriraju, Lawrence Dunnell
-
-<h2>1.0 Rampdown / GA Process Description </h2>
-<ul>
-<li>Between M5 and GA, WTP will be in rampdown mode, and some description of the process and the release criteria is needed [TW].
-<li>Existing documentation for milestone builds and exit criteria to be reviewed [DW, TW] in preparation for this.
-<li>In general, following the platform seems reasonable, and we also need to respect documentation and help file status [ND].
-<li>On a related topic, integration builds will move from Thursday to Tuesday to allow for two days to address problems if the test status is not green [ND].
-API discussion
-<li>Process surrounding the definition and freezing of APIs; see http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg00705.html [AR]. David Williams agreed that the architecture group would play a significant role in reviewing and admitting APIs for WTP as a whole.
-<li>Finalized process should be posted to the website [DV]
-<li>Platform tool to analyze component metadata (component.xml) and scan for API violations was described [AR]; we are not yet compliant in many areas.
-<li>Discussed nomenclature surrounding provisional APIs; a significant percentage of WTPs APIs may be in this category for 1.0
-<li>WTP to have standing agenda item until 1.0 GA to review status of component.xmls / API conformance metrics
-<li>Release-to-release API change process: PMC will adopt some combination of its own policies and the platforms approach to managing and communicating the change; details TBD.
-</ul>
-
-<h2>Clarifying JST Use of Standards vs. Tooling Technologies</h2>
-Discussed use of xdoclet by WTP, since questions were raised about its non-J2EE standardness at the EclipseCon project sprint. PMC clarified that tooling of any form xdoclet, ant, editors, etc. is acceptable for project use, but that *runtime* infrastructure and platforms targeted by JST will be limited to J2EE standards.
-
-<h2>Data Tools Project and Future of WTP RDB Component </h2>
-Arthur provided a description of meetings between IBM and Exadel with Sybase over the charters of the WTP RDB component and the newly proposed toplevel Data Tools Project (DTP)
-WTP PMC agreed that 1.0 release, and currently planned requirements for it, will not be affected apart from API definitions in this arena, which require either renaming or provisional status (outcome TBD based on subsequent discussions with Sybase/DTP representatives)
-RDB EMF models will continue to exist, and WTP consumers can continue to rely on them; Sybase is planning to contribute upgraded SQL editing and debugging capabilities as well as technology that expands on the RDB component scope into administration and DB design
-
-<h2>Help System </h2>
-<ul>
-<li>Help content was not included in original IBM contribution, but will be made available shortly
-<li>Lawrence Mandel will be technical contact for help build system and tools
-<li>Help system is XML based (DITA), with open source processors on SourceForge
-<li>IBM may be contributing a writer as well; first priority is correcting/augmenting content to match current WTP APIs and architecture; subsequent work would probably include some localization effort, at least for major languages
-<li>Other companies may be able to contribute once infrastructure and content is present
- </ul>
-
-<h2>Action Items:</h2>
-<ul>
-<li>[TW] By 3/15: Identify BEA employee to serve on WTP requirements group
-<li>[TW/JK] By 3/15: Reconstitute requirements group and set date for initial meeting.
-<li>[AI] Bundled M3 releases (see minutes)
-<li>[JK] Add new and noteworthy link and correct main Eclipse download page reference to be M3 instead of M2
-<li>[TW] Draft language for endgame / rampdown based on Davids milestone release document; will circulate to PMC when ready.
-<li>[TW] Pending community feedback on Arthurs API adoption process, post it to the website.
-<li>[TW] Update website to clarify that tool (not runtime) technologies are admissible in JST and unrelated to the JCP requirement
-<li>[AR] Manage ongoing conversation with Sybase surrounding the RDB/DTP merge/migration.
-</ul>
-
-
-<small>Minutes taken by Tim Wagner, March 8, 2005</small>
- </td>
-
- </tr>
-
- <tr>
- <td>
- </td>
-
- </tr>
-
- </tbody></table>
-</html>
-
diff --git a/development/pmc_call_notes/2005-03-15.html b/development/pmc_call_notes/2005-03-15.html
deleted file mode 100644
index e9afbdb..0000000
--- a/development/pmc_call_notes/2005-03-15.html
+++ /dev/null
@@ -1,195 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for March 15, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - March 15, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
-Attending: Tim Wagner [TW], Arthur Ryman [AR], David Williams [DW], Dominique De Vito [DV], Jochen Krause [JK]
-
-Others: Lawrence Mandel (representing WTP community) [LM]
-
-
-
-<h2>Procedural matters none</h2>
-
-<h2>Community from Lawrence Mandel</h2>
-
-<ul>
-
-<li>W-S validation project approved to move into WTP; code will be merged this week (includes the SOAP monitor)
-
-<li>Help system work in flight; hoping to have it up this week
-
-<li>External communications OOPSLA coming up. LM will be submitting a tutorial, demo, and possibly a panel session; theme will be Using WTP for teaching J2EE.
-
-<li>For this and any other external communication, please let LM know so that he can post events to the community page, and also serve as a clearing house for slide decks and other shareable material.
-
-<li>Download statistics. These are tracked when downloads are performed through the correct PHP script. JK pointed out that we want to track our download frequency so that we can monitor overall use as well as changes w.r.t. WTP events. Download statistics can be tracked at
-
-<a href="http://www.eclipse.org/downloads/stats.php?filename=wtp-"> www.eclipse.org/downloads/stats.php?filename=wtp-</a>. DW reported that were around 20K downloads for M3. LM will periodically report on changes in download frequency.
-
-</ul>
-
-
-
-[PMC members only for the remaining portion of the meeting]
-
-
-
-
-
-<h2>Requirements group [JK] </h2>
-
-<ul>
-
-<li>BEA nominated Paul Meijer to work with Jochen
-
-<li>Jochen working independently for past week; will set date for initial meeting with Paul and other interested parties this week
-
-</ul>
-
-
-
-<h2>Architecture Group [DW]</h2>
-
-<ul>
-
-<li>Kevin Haaland and Ted Bashor joined the group
-
-<li>Spent a significant amount of time discussing operations, and the differing frameworks for them. Kevin reported that platform is attempting to drive adoption of a single solution.
-
-<li>Other issues included an edit model in EMF and moving the extensible navigator to the platform from WTP.
-
-<li>Process involves weekly conference calls for the group, community review of proposals (see below), and architectural reviews with component leads. Individuals will be selected to drive cross-project or cross-component (within WTP) architectural challenges.
-
-<li>Bugzilla entries filed by architecture group for changes that need to be made or issues being tracked can be found at
- <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=%5Barch%5D&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">this
- URL</a>.
-
-</ul>
-
-
-
-
-
-<h2>Bundled WTP Downloads [AR]</h2>
-
-<ul>
-
-<li>Two bundled packages available: one with eclipse, wtp, emf, gef, jem, and xerces, another with all of that <em>but</em>eclipse
-
-<li>Plan is to do this for each milestone; Jeffrey Liu owns updating build scripts to do this automatically.
-
-</ul>
-
-
-
-<h2>wtp-pmc mailing list</h2>
-
-<ul>
-
-<li>For maximum transparency of our operations, the WTP PMC agreed to disband the ObjectWeb-hosted mailing list and recreate one of the same name hosted on Eclipse. It would continue to be used for administrative purposes, and we would discourage threads better expressed on wtp-dev.
-
-</ul>
-
-
-
-<h2>APIs</h2>
-
-<ul>
-
-<li>Jeffrey Liu handling the scanning process.
-
-<li>component.xml updates are in flight; would like to see this finished quickly, but DW reports that not all component teams can complete the work this week; this will be the first step in distinguishing our true API
-
-<li>renaming non-API public methods to
internal is in flight
-
-<li>use of the internal.provisional naming scheme ratified
-
-<li>rdb will be entirely internal; whether we will pre-name components for their post migration location is still TBD [next meeting is 3/17]
-
-<li>M4 process will be (in order): define component.xml files, drive for javadoc and junit coverage, correct naming conventions, work on implementation
-
-<li>PMC will review component.xml progress next week and will review statistics on an ongoing basis as part of our weekly call agenda; component leads should be prepared for PMC review starting next week
-
-<li>Currently have ~14K APIs without JUnit tests; number needs to drop through additional tests and by interning unintentional APIs
-
-</ul>
-
-
-
-<h2>Plans for integrating BEA developers</h2>
-
-<ul>
-
-<li>IBM sites will host immersion days for BEA developers to help them ramp up on technology, people, and processes
-
-</ul>
-
-
-
-<h2>Maintenance Releases</h2>
-
-Both BEA and IBM will be basing products on WTP 1.0, so we need to plan for a 1.0.x maintenance stream. This will need to be coordinated with the platform maintenance stream. Planning should begin now to ensure that this is handled smoothly; a single release manager would be ideal. Since Nacis team currently handles build, well revisit this next week when hes present.
-
-
-
-<h2>Handling Third Party Content</h2>
-
-[quoted from Arthurs notes]
-
-<em>
-
-<p>
-
-I have been working with Janet Campbell, the Eclipse Foundation IP lawyer, to get permission to redistribute some 3PC (from Apache, W3C, etc). This is going to be a slow process. Also, our policy to to not reship runtimes. These two considerations combine to produce a difficult situation for our users who have to namually download and install many pieces.
-<p>
-I'd like to suggest an alternative. I'm calling these "Wormholes". The idea is to create Update Manager sites at Apache, W3C, ObjectWeb, SourceForge, etc. We would create a project at each of those sites and package the code we need. We would create extension points for this content, e.g. a Server Runtine extension point and the Jonas, Tomcat, Geronimo, Jigsaw, etc. runtimes could be packaged to extend that runtime. We would preload the URLs to these sites in WTP. Then the user could easily download and install the 3PC. This fineses the installation, configuration, legal, and maintenance problems.
-<p>
-To start, we could create an "ObjectWeb-Eclipse Wormhole" for Jonas. Next would be an "Apache-Eclipse Wormhole".for Tomcat, Axis, etc. We need to propose an Apache project for that, and the more companies who could participate, the stronger our proposal is. I've already run this by Mike Milinkovich and he likes the idea.
-
-</em>
-
-<p>
-
-This would be targeted for M5. JK noted that placing, e.g., JBoss in the plugins directory is not ideal for everyone, so this would have to be optional. If ObjectWeb cannot host, then BEA and IBM could work on a joint Apache proposal.
-
-
-
-<h2>Action Items:</h2>
-
-<ul>
-
-<li>[JK] Call requirements group meeting.
-
-<li>[TW] Disband existing wtp-pmc distribution list and recreate it on Eclipse.
-
-<li>[AR] Proposal for 3PC downloads.
-
-</ul>
-
-
-
-<small>Minutes taken by Tim Wagner, March 15, 2005</small> </td>
-
- </tr>
-
- <tr>
- <td>
- </td>
-
- </tr>
-
- </tbody></table>
-</html>
-
diff --git a/development/pmc_call_notes/2005-03-22.html b/development/pmc_call_notes/2005-03-22.html
deleted file mode 100644
index 049a229..0000000
--- a/development/pmc_call_notes/2005-03-22.html
+++ /dev/null
@@ -1,213 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for March 22, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - March 22, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <title>WTP PMC Minutes for March 22, 2005 Conference Call</title
-
-
-Attending: Tim Wagner [TW], Arthur Ryman [AR], David Williams [DW], Dominique De Vito [DV], Jochen Krause [JK], Naci Dai [ND], Bjorn Freeman-Benson [BB], Christophe Ney [CN]
-
-Others: Lawrence Mandel (representing WTP community) [LM]
-
-
-
-<h2>Procedural matters </h2>
-
-<ul>
-
-<li>TW: Reminder that private mailing list (wtp-pmc@objectweb.org) has been decommissioned and all PMC members and other interested parties should subscribe to the Eclipse-hosted one (wtp-pmc@eclipse.org).
-
-<li>AR: Requested that EMO investigate IRC server for telecon use.
-
-</ul>
-
-
-
-<h2>Community [LM]</h2>
-
-<ul>
-
-<li>OOPSLA submissions for tutorial and panel completed
-
-<li>JK and DV also presenting at conferences; will update Lawrence with info
-
-<li>Messaging: no response yet from WTP community; LM requested that PMC members appeal to their respective organizations for support in writing articles and communicating WTP info; EclipseCorner in particular is easy to publish to and eager for material
-
-<li>TW: BEA eWorld, dev2dev interview, and JavaOne conference are likely candidates for WTP presentations; more as the event dates/agendas crystallize
-
-<li>CN: ObjectWeb hosting conference in Viet Nam at which WTP information will be presented
-
-<li>WTP help system initial content should be available by next week (delayed from previous estimate); currently working towards stable local builds
-
-</ul>
-
-
-
-<h2>Documentation Strategy</h2>
-
-<ul>
-
-<li>PMC discussed the likelihood of a lag between code GA and documentation readiness, especially in light of the limited resources and the size of the initial documentation content drop from IBM. If we ship in July, a September doc release, with subsequent quarterly updates, might be a tractable schedule. Expect to use professional writers (devs may author initial content or edit subsequently). Initial code release will contain samples, JavaDocs, and anything else thats ready at that point.
-
-<li>Documentation will have a separate build process/schedule. LM/AR to pursue offline.
-
-<li>AR: IBM has product documentation resources that will contribute to this effort
-
-<li>TW: BEA probably in similar state; some fraction of a doc resource likely available to help post (BEAs) 9.0 delivery
-
-</ul>
-
-
-
-[PMC members only for the remaining portion of the meeting]
-
-
-
-<h2>Requirements Group Report [JK] </h2>
-
-<ul>
-
-<li>Requirements group composition:
-
- <ul>
-
- <li>Paul Meijer (BEA)
-
- <li>Todd Williams (Genuitec)
-
- <li>Arthur Ryman (IBM)
-
- <li>Jochen Krause (Innoopract, chair)
-
- <li>Ivelin Ivanov (JBoss)
-
- </ul>
-
-<li>First meeting will follow next weeks PMC call
-
-<li>Version numbering PMC discussed merits of next version being 1.1 (historical consistency, description of maturity of project) versus 3.2 (alignment with platform, less confusion for users). Tabled final decision pending feedback from Eclipse Councils next month.
-
-</ul>
-
-
-
-<h2>Architecture Group Report [DW]</h2>
-
-<ul>
-
-<li>Several new bugs posted [see query string in last weeks minutes tw]
-
-<li>Thursday call agenda: Browser resolution (move to platform?), tabbed property page (same question)
-
-<li>TW: What role is Architecture Group playing in API review? DW: Focusing on WTP vs. platform and cross component issues as detected by themselves, component leads, or members of the community.
-
-<li>TW: Suggested that a community review of the APIs in the form of 1-2 hour presentations by each component lead would be a forum for API commentary. Architecture Group could help structure the review, but the community at large would own the outcome. AR noted that timeframe must be post M4 to allow API definition process to complete.
-
-</ul>
-
-
-
-<h2>Disk Quota/Build Issues [AR]</h2>
-
-<ul>
-
-<li>Problem is not so much disk quota on our main server as the load we place on mirrors; if we trim down the nightly size, that will have the biggest impact
-
-<li>Three suggestions
-
- <ol>
-
- <li>Dont retain nightly builds beyond the next integration build
-
- <li>Dont publish non-SDK bundle in nightlies (theyre only for dev use)
-
- <li>Dont publish WST-only bundle in nightlies (same reason)
-
- </ol>
-
-PMC resolved to adopt all three changes to the process, and that warmup (pre-final) I-builds need not be kept after the next successful I-build.
-
-</ul>
-
-
-
-<h2>Integration Builds [ND]</h2>
-
-<ul>
-
-<li> Platform insists that test failure implies the result is not an I-build; weve lacked that level of quality in our I-builds
-
-<li>Our previous milestone releases have been stressful because of accumulated test failure debt
-
-<li>Current (updated) process is to attempt the I-build on Tuesday, focus on build or test failures midweek attempting to produce a successful build on Thursday. Expectation is that there are no large changes between Tuesday and Thursday; changes can be released to head, just not included in the I-build candidate.
-
-<li>Biggest remaining problem is getting people to focus on tests; will now <em>require</em> tests to pass to release the I-build (otherwise we fail for the week and try again the following week rather than posting the failure).
-
-<li>[AR] For m4 we have two buckets: real tests, and API tests that do not yet have backing implementation and will therefore fail. For the duration of m4, we need to manually differentiate in declaring the I-build green.
-
-<li>[ND] Also, Linux machine should be up this weekend, so we will start having parallel builds on Linux as well as Windows.
-
-</ul>
-
-
-
-<h2>API Review</h2>
-
-<ul>
-
-<li>PMC reviewed initial API statistics; will track component convergence over time to help drive process.
-
-</ul>
-
-
-
-<h2>RDB / DTP Issues [AR]</h2>
-
-Arthur posted minutes of previous meeting to mailing list. Components would likely move in August (pending proposal approval); still considering whether to rename them in advance to limit later churn on other WTP components that are downstream.
-
-
-
-<h2>Action Items:</h2>
-
-<ul>
-
-<li>[JK/DV/CN] update Lawrence with info on upcoming conference presentations of WTP info
-
-<li>[TW/DW] work on scheduling API review by component leads
-
-<li>[ND] update build scripts based on the Quota resolutions (see above)
-
-<li>[ND] update build page with process change (test pass requirement) for I-builds
-
-<li>[AR] ask Jeffrey to add time series tracking to API statistics pages so we can track trends at the component level
-
-</ul>
-
-
-
-
-
-<small>Minutes taken by Tim Wagner, March 22, 2005</small>
- </tr>
-
- <tr>
- <td>
- </td>
-
- </tr>
-
- </tbody></table>
-</html>
-
diff --git a/development/pmc_call_notes/2005-03-29.html b/development/pmc_call_notes/2005-03-29.html
deleted file mode 100644
index 4b36dc7..0000000
--- a/development/pmc_call_notes/2005-03-29.html
+++ /dev/null
@@ -1,186 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for March 29, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - March 29, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
-
-Attending:
-
-Tim Wagner [TW],
-
-David Williams [DW],
-
-Dominique De Vito [DV],
-
-Arthur Ryman [AR],
-
-Bjorn Freeman-Benson [BB],
-
-Jochen Krause [JK],
-
-Naci Dai [ND]
-
-Others: Lawrence Mandel (representing WTP community) [LM]
-
-
-
-
-<h2>Procedural matters </h2>
-
-<ul>
-
-<li>Update on last weeks request that EMO investigate IRC server for telecon use: will be delayed for several months.
-
-</ul>
-
-
-
-<h2>Community [LM]</h2>
-
-<ul>
-
-<li>EclipseWorld submissions: tutorial would be good [AR], target audience is end users rather than plug-in developers could reuse material from EclipseCon overview (plus updates from 1.0 release). AR, TW, and Tim deBoer may all be submitting talks.
-
-<li>Help system build working, will push out to public machine this week. General convention in Eclipse is to ship help <em>with</em> the download. While we will have something ready by 1.0 ship, concern is that we will not have enough manpower to have this ready in time; if we have a quarterly maintenance release, may need to use that as the documentation release vehicle. Doc build <em>is</em> separate from code, so we will need to use a later (1.0.1) release vehicle the first time around to complete documentation. One suggestion is to have developers try to update some of the areas of significant change (like flexible project model). Build periodicity: part of N-builds for simplicity. (Requires 2-3 minutes to run, produces about 3M of output.) Currently a separate feature.
-
-<li>(External) Link breakage / Cross Project Coordination: (M3 separate download no longer works because of broken links.) Two options asking other teams to keep the links alive, or maintaining local copies of the material we need. I-builds from other projects are needed for fixes or platform milestone compatibility, but if another team deletes an I-build, we should no longer be relying on it. Resolved to copy I-builds from other projects (not platform, where we use only milestone builds).
-
-</ul>
-
-
-
- [PMC members only for the remaining portion of the meeting]
-
-
-
-<h2>Requirements Group Report [JK] </h2>
-
-<ul>
-
-<li>Will be discussing themes this week, and will send out results to wtp-pmc mailing list.
-
-<li>Still have two milestone plans linked on our website; see AIs.
-
-</ul>
-
-
-
-<h2>Architecture Group Report [DW]</h2>
-
-<ul>
-
-<li>WTP Browser support migrated to platform
-
-<li>Tabbed property sheet migrated to platform
-
-<li>(See A-G notes for further details.)
-
-<li>Component open house scheduling will be open to any interested parties as well as WTP devs. Format: telecon + eMeeting. Proposed agenda: One hour apiece, six meetings, one meeting per week, component leads would be presenters.
-
-</ul>
-
-
-
-<h2>AXE Proposal [AR]</h2>
-
-<ul>
-
-<li>Form-based UI for XML documents, proposed by Anywhere, based on Jelly (an Apache project).
-
-<li>Arthur sent a follow-up requesting an example and some exploration of the ease of use.
-
-<li>Too late for 1.0; discussion is whether this should be a 1.1 feature.
-
-<li>Since they appear inclined to proposing a technology project, well evaluate that when/if it occurs.
-
-</ul>
-
-
-
-<h2>DTP Update</h2>
-
-<ul>
-
-<li>Technical meetings getting started.
-
-<li>Proposal timeframe: June; component move targeted for August
-
-<li>Package prenaming: low confidence that this will happen in time for WTP 1.0
-
-</ul>
-
-
-
-<h2>Release Review [BB]</h2>
-
-<ul>
-
-<li>Precedes each major release (WTPs 1.0)
-
-<li>Scheduled for early in endgame
-
-<li>Purposes: verify no outstanding IP issues, set of released features vs. roadmap, verify that API is appropriate quality, defect status.
-
-</ul>
-
-
-
-<h2>API Review</h2>
-
-<ul>
-
-<li>PMC reviewed API statistics
-
-<li>Time series / convergence tracking not yet available
-
-<li>Down to ~6K APIs (still high, but substantial progress versus starting point)
-
-<li>SSE and other components will have trouble meeting M4 exit criteria [DW], resolution is to defer API definition where necessary to meet quality goals
-
-</ul>
-
-
-
-<h2>Action Items:</h2>
-
-<ul>
-
-<li>ND: copy I-builds referenced from other projects.
-
-<li>AR: update milestone plan on website
-
-<li>TW: finalize dates for release reviews with EMO
-
-<li>TW/AR/DW: finalize trip logistics for BEA visits
-
-<li> LM: coordinate EclipseWorld submissions with AR, TW
-
-</ul>
-
-
-
-
-
-<small>Minutes taken by Tim Wagner, March 29, 2005</small>
- </tr>
-
- <tr>
- <td>
- </td>
-
- </tr>
-
- </tbody></table>
-</html>
-
diff --git a/development/pmc_call_notes/2005-04-05.html b/development/pmc_call_notes/2005-04-05.html
deleted file mode 100644
index 422c36c..0000000
--- a/development/pmc_call_notes/2005-04-05.html
+++ /dev/null
@@ -1,163 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for April 5, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - April 5, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <title>WTP PMC Minutes for April 5, 2005 Conference Call</title>
-
-
-
-Attending:
-
-Tim Wagner [TW],
-
-David Williams [DW],
-
-Jochen Krause [JK]
-
-Others: Lawrence Mandel (representing WTP community) [LM]
-
-
-
-
-<h2>Procedural matters </h2>
-
-<ul>
-
-<li>Please note that US is now on daylight savings times; the PMC calls will occur at 7am PDT.
-
-</ul>
-
-
-
-<h2>Community [LM] </h2>
-
-<ul>
-
-<li>Internal build working, more help files done, migrated to M6. Still working on releasing to WTP build process.
-
-<li>No new conference notices.
-
-<li>Greater dev involvement in newsgroup answering questions (increased responsiveness to user community).
-
-</ul>
-
-
-
-[PMC members only for the remaining portion of the meeting]
-
-
-
-<h2>API Review</h2>
-
-<ul>
-
-<li>PMC reviewed API statistics
-
-<li>Time series / convergence tracking not yet available.
-
-<li>Bulk of APIs are in the j2ee.core component.
-
-<li>Good progress on removing unintended APIs: dropped roughly 30% from previous week; overall metric is 48/100.
-
-<li>Summary from April 1st I-build report: 4,326 APIs, 26% JUnit coverage, 77% JavaDoc coverage, 0% overview coverage (this is a reporting bug).
-
-See <a href="http://download.eclipse.org/webtools/downloads/drops/I-I20050331-200503312230/apitools/api-progress.html">
-
-http://download.eclipse.org/webtools/downloads/drops/I-I20050331-200503312230/apitools/api-progress.html</a>.
-
-</ul>
-
-
-
-<h2>Requirements Group Report [JK] </h2>
-
-<ul>
-
-<li>Minutes from last weeks meeting available at: <a href=http://www.eclipse.org/webtools/development/requirements_call_notes/2005-03-30.html>http://www.eclipse.org/webtools/development/requirements_call_notes/2005-03-30.html</a>.
-
-<li>Group deciding on forum for community feedback on draft requirements/specification (existing newsgroup may be too noisy for this purpose).
-
-</ul>
-
-
-
-<h2>Architecture Group Report [DW] </h2>
-
-<ul>
-
-<li>Ted Bashor and Chuck Bridgham volunteered to update the architectural overview document.
-
-<li>XSL contribution under review; may need to create new component as a home for it.
-
-<li>M6 migration resulted in a variety of build problems; platform ripple effect was severe (see bug #90231).
-
-</ul>
-
-
-
-<h2>XPDL Proposal [JK]</h2>
-
-<ul>
-
-<li> From JK email:
-
-OpenWide is planning to work on an XPDL editor that integrates with web tools and they would be interested in contributing to the project. Does the PMC consider XPDL to be a de jure standard?
-
-<a href="http://www.wfmc.org/standards/XPDL.htm"> http://www.wfmc.org/standards/XPDL.htm</a>
-
-<li> JK: We are not precise about which standards bodies we admit to WTP; need to clarify our position. Agreed to table this until next meeting (need quorum).
-
-</ul>
-
-
-
-<h2>Action Items:</h2>
-
-<ul>
-
-<li>TW: finalize dates for release reviews with EMO
-
-<li>TW: provide LM with BEA conference information related to WTP
-
-</ul>
-
-
-
-<h2>Tabled Items for Next Weeks Agenda</h2>
-
-<ul>
-
-<li>Refining list of standards bodies admissible for WTP use.
-
-<li>XPDL proposal.
-
-<li>Product-facing forum(s) for WTP 1.0 features (suggested by JK).
-
-</ul>
-
-
-
-<small>Minutes taken by Tim Wagner, April 5, 2005</small>
- </tr>
-
- <tr>
- <td>
- </td>
-
- </tr>
-
- </tbody></table>
-</html>
-
diff --git a/development/pmc_call_notes/2005-04-12.html b/development/pmc_call_notes/2005-04-12.html
deleted file mode 100644
index e0ff45c..0000000
--- a/development/pmc_call_notes/2005-04-12.html
+++ /dev/null
@@ -1,135 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for April 12, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - April 12, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <title>WTP PMC Minutes for April 12, 2005 Conference Call</title>
-
-
-Attending:
-Tim Wagner [TW],
-David Williams [DW],
-Arthur Ryman [AR],
-Dominique De Vito [DD],
-Christophe Ney [CN],
-Jochen Krause [JK],
-Naci Dai [ND]
-Others: Lawrence Mandel (representing WTP community) [LM]
-
-<h1>WTP PMC Minutes for April 12, 2005 Conference Call</h1>
-
-<h2>Procedural matters - None</h2>
-
-<h2>Community [LM] </h2>
-<ul>
-<li>EclipseWorld tutorial proposal in flight.
-<li>AR created presentation archive see email on WTP list. This is intended to be a repository for presentation materials.
-<li>AR talking at Colorado Software Summit on Web Services development in Eclipse and WSDL 2.0.
-<li>Help system: successful internal build; should be incorporated into this weeks I-build. Requested Bugzilla documentation component (PMC approved request). Will be contacting BEA for help with documentation content work.
-</ul>
-
-[PMC members only for the remaining portion of the meeting]
-
-<h2>API Review</h2>
-<ul>
-<li>PMC reviewed API statistics
-<li>j2ee.core component identified as not making sufficient progress; the bulk of its models will need to be turned provisional. Potential migration of flexible project model to platform in 3.2 is a possible stumbling block in finalizing API in that area.
-<li>Clarified renaming/repackaging strategy to be complete by end of M4.
-<li>Continued progress on removing unintended APIs: dropped from 4,326 to 3,349. Overall metric for 4/11 build is 59.
-<li>Summary from April 11th build report: 35% JUnit coverage, 95% JavaDoc coverage, 9/14 overview docs.
-See <a href='http://download.eclipse.org/webtools/downloads/drops/N-N20050411-200504111848/apitools/api-progress.html'>
-http://download.eclipse.org/webtools/downloads/drops/N-N20050411-200504111848/apitools/api-progress.html</a>.
-</ul>
-
-<h2>Requirements Group Report [JK] </h2>
-<ul>
-<li>No news to report; will begin including this in the agenda on a bi-weekly basis.
-</ul>
-
-<h2>Architecture Group Report [DW] </h2>
-<ul>
-<li>Validation framework API deferred.
-<li>XML resolver/catalog API deferred.
-<li>See flexible project model notes above.
-<li>Separate XERCES plugin build likely this week.
-<li>XML and WSDL dependency on JDT should be removed this week.
-<li>GEMs M6 readiness is late; may cause us to introduce a late dependency change into our own build.
-</ul>
-
-<h2>XPDL Proposal and Discussion of WTP Criteria for Submissions [JK] </h2>
-<ul>
-<li>AR: standard body must be recognized, but standard must also be popular and open source runtime available, and standard must be in scope.
-<li>AR: Criteria for standards body: open to new members, broad industry participation, established/history.
-<li>CN: Maturity and adoption of standard should be part of our criteria.
-<li>ND: XPDL and BPEL would be better placed in a technology project; too far from general audience of WTP.
-<li>PMC resolved to suggest a technology project, but agreed to review the proposal when written to review vis-à-vis WTP charter.
-</ul>
-
-<h2>WTP 1.0 Product Forums [JK] </h2>
-<ul>
-<li>Idea would be to get interested parties to build on WTP 1.0, drive adoption, and gather requirements for 1.1.
-<li>Timeframe: post 1.0 ship (easier to do once churn stops).
-<li>Requirements group will take this on and report back to the PMC when proposal is complete.
-</ul>
-
-<h2>Eclipse Booth at JavaOne [TW] </h2>
-<ul>
-<li>CN, DD, and TW will assist with staffing the booth; TW to respond to Ian.
-</ul>
-
-<h2>Creation of XSL Component [DW] </h2>
-<ul>
-<li>Discussed contribution request (for 1.1; not on table for 1.0 release).
-<li>Normal committership process must be followed, despite size of contribution.
-<li>Can be made part of build so that its available for evaluation by committers and rest of community.
-</ul>
-
-<h2>Upcoming Milestone Build Process Ownership [DW] </h2>
-<ul>
-<li>Setting dates / versions for upstream components, driving test plans with component leads, evaluation of candidates and convergence toward acceptance.
-<li>AR offered to support DW in this effort.
-</ul>
-
-<h2>Build Status Reports [ND] </h2>
-<ul>
-<li>New distribution list will be set up for build reports.
-<li>Progress on build status/result reporting compile failures now attached to email.
-<li>Will increase number of warmup builds.
-</ul>
-
-<h2>Status Update on Ongoing Projects [AR] </h2>
-<ul>
-<li>Janet making progress on 3rd party content agreements; ETA is M4.
-<li>AXE will be going into the Lepido technology project.
-<li>DTP: Sybase and others meeting with IBM to go over code and make progress (see email to PMC).
-</ul>
-
-<h2>Action Items:</h2>
-<ul>
-<li>TW: finalize dates for release reviews with EMO (week of June 20th being discussed)
-</ul>
-
-
-<small>Minutes taken by Tim Wagner, April 12, 2005</small>
- </tr>
-
- <tr>
- <td>
- </td>
-
- </tr>
-
- </tbody></table>
-</html>
-
diff --git a/development/pmc_call_notes/2005-04-19.html b/development/pmc_call_notes/2005-04-19.html
deleted file mode 100644
index e1f703c..0000000
--- a/development/pmc_call_notes/2005-04-19.html
+++ /dev/null
@@ -1,131 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for April 19, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - April 19, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <title>WTP PMC Minutes for April 19, 2005 Conference Call</title>
-
-
-Attending:
-Tim Wagner [TW],
-David Williams [DW],
-Arthur Ryman [AR],
-Dominique De Vito [DD],
-Jochen Krause [JK],
-Naci Dai [ND]
-Others: Lawrence Mandel (representing WTP community) [LM]
-
-<h1>WTP PMC Minutes for April 19, 2005 Conference Call</h1>
-
-<h2>Procedural matters</h2>
-<ul>
-<li>[TW] Bjorn Freeman-Benson has requested that the WTP PMC accept his resignation;
-due to his other EMO commitments, he can no longer continue to participate in this forum.
-The PMC gratefully acknowledges Bjorn's contributions and thanks him for his work
-on the WTP's behalf.
-</ul>
-
-<h2>Community [AR/LM] </h2>
-<ul>
-<li>Help system update: IBM docs team unable to contribute user documentation. WTP will need to
-resource its help needs, prioritizing scenarios first, followed by reference information.
-Starting from scratch will enable us to exploit dynamic (context-sensitive) help from 3.1 platform.
-<li>Lawrence Mandel will be taking on the role of user documentation editor.
-<li>Upcoming events: Colorado Software Summit, EclipseWorld
-</ul>
-
-[PMC members only for the remaining portion of the meeting]
-
-<h2>API Review</h2>
-<ul>
-<li>PMC reviewed API statistics
-<li>Issue: J2EE model (1,581 APIs) consists of generated models. Reported test coverage is low (22%); actual coverage
-is higher -- many APIs are hit via reflection. Jeffrey Liu will be investigating more accurate analysis of its
-test coverage this week (via tracing). Discussed whether "raw" EMF model should be exposed as WTP API versus wrapping
-this in public facade (we cannot prevent generated public methods from leaking into our API). M5 will provide a
-public review period in which we can assess whether the community is content with WTP committing to EMF in its
-API.
-<li>Issue: JST Server component tests at 39% (only other non-green component); remaining tests are due to
-generic server (however, substantial use of this area has occurred).
-<li>Issue: Data tools has not completed internal naming convention change due to product interaction (requesting
-delay until early May to achieve renaming).
-<li>WTP extension points must be clearly documented as in/out of public API.
-<li>Continued progress on eliminating APIs: total number of APIs dropped from 3,349 to 2,583.
-Overall metric for 4/19 build is 66.
-<li>Summary from April 19th build report: 45% JUnit coverage, 97% JavaDoc coverage, 2/9 overview docs.
-See <a href='http://download.eclipse.org/webtools/downloads/drops/I-I20050419-200504190713/apitools/api-progress.html'>
-http://download.eclipse.org/webtools/downloads/drops/I-I20050419-200504190713/apitools/api-progress.html</a>.
-</ul>
-
-<h2>M4 Readiness</h2>
-<ul>
-<li>Build created, although there were some failing tests in server connectivity (will require rebuild).
-<li><b><font color="#ff0000">Schedule will be slipped one week; M4 now targeted for 4/29.</font></b>
-<li>Delay will enable integration of 3PC into download to improve user experience.
-<li>We are already on milestone builds for all prerequisites that provide them (EMF and JEM do not);
-we are also copying them to ensure integrity of our own downloads.
-<li>Bundled ZIP of WTP and its transitive prerequisites will be available for milestone build (already
-there in build system).
-<li>Discussed creating a release engineering distribution list for WTP to separate out the build
-and test notification traffic.
-</ul>
-
-<h2>Requirements Group Report [JK] </h2>
-<ul>
-<li>Discussed process of getting to themes and priorities; plan to use Bugzilla, but
-feel that a better requirements tracking tool/reporting solution is needed.
-<li>We may need to change our milestone tracking methodology slightly to conform to
-Bugzilla; will report back on this as more info emerges.
-</ul>
-
-<h2>Architecture Group Report [DW] </h2>
-<ul>
-<li>No meeting last week; nothing new to report. Still looking for overview documents from component leads.
-<li>Concerns about flexible project model: ultimately belongs in base, and team proposing API is also primary
-consumer; may not have sufficient community validation in terms of process.
-</ul>
-
-<h2>EJB 3.0 Interaction with WTP [DD] </h2>
-<ul>
-<li>Planning problems in terms of interaction with other EJB 3.0 projects and WTP 1.1 schedule.
-<li>Questions raised about the rules for when technologies incubate separately versus inside an
-established project (need to be addressed by the EMO).
-<li>Ivelin and Jochen can be points of contact within WTP.
-</ul>
-
-<h2>Backport of WTP M3 to 3.0.2 by Innoopract. [JK] </h2>
-<ul>
-<li>Makes several features available to users who cannot move to 3.1.
-<li>Excludes web services and RDB.
-</ul>
-
-<h2>Action Items:</h2>
-<ul>
-<li>ND: Create new mail list for release engineering traffic and update our mail page and EMO mail page with addition.
-<li>AR: Notify mailing list and newsgroup of schedule slip.
-<li>TW: Notify EMO of schedule slip.
-</ul>
-
-
-<small>Minutes taken by Tim Wagner, April 19, 2005</small>
- </tr>
-
- <tr>
- <td>
- </td>
-
- </tr>
-
- </tbody></table>
-</html>
diff --git a/development/pmc_call_notes/2005-04-26.html b/development/pmc_call_notes/2005-04-26.html
deleted file mode 100644
index 2cb6ed2..0000000
--- a/development/pmc_call_notes/2005-04-26.html
+++ /dev/null
@@ -1,79 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for April 26, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - April 26, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <title>WTP PMC Minutes for April 26, 2005 Conference Call</title>
-
-
-Attending:
-Tim Wagner [TW],
-David Williams [DW],
-Arthur Ryman [AR],
-Dominique De Vito [DD],
-Jochen Krause [JK]
-
-<h1>WTP PMC Minutes for April 26, 2005 Conference Call</h1>
-
-<h2>No procedural matters</h2>
-
-<h2>No community update this week</h2>
-
-<h2>M4 Readiness</h2>
-<ul>
-<li>Tuesday build should include at least 5 of the 12 remaining unresolved blocking-or-critical issues
-<li>Non-trivial churn occurring, but still appear to be on track for a Friday milestone release
-<li>No 3PC issues known at this time (although some non-blocking 3PC, such as DTDs, still need to be added)
-</ul>
-
-<h2>API Review</h2>
-<ul>
-<li>Summary: 52% JUnit coverage, 96% JavaDoc coverage on 2,674 APIs.
-<li>Dynamic tracing of project model APIs raised measured coverage from 25% to 35%; more testing (on full suite) still pending and delayed on other bugs
-</ul>
-
-<h2>Architecture Group Report [DW] </h2>
-<ul>
-<li>Component meetings are scheduled for six weeks on Thursdays, starting in May; interested consumer of WTP and others are invited (meetings are open to the public)
-<li>"State of the Architecture" Report as of M4:
- <ul>
- <li>Too many plugins; some consolidation is warranted
- <li>Feature split-up, based on user expectations/scenarios into functional areas being considered in M5
- </ul>
-<li>M4 exit: need to issue a clear statement that "internal provisional" APIs means that we're interested in feedback, but that these <em>are still internal and not API quality</em>
-<li>No "friend" APIs will be defined in 1.0; will look into this in subsequent releases
-<li>During M5 we need to review the number of violations of platform APIs
-<li>State of APIs on M4 exit: "ready for review" means that community feedback is being sought
-<li>EMF models: need to clarify which parts are in/out of the API; see AG notes (ongoing issue, AG working with component leads on this)
-</ul>
-
-<h2>Discussion of Possible Hardening Release [JK] </h2>
-<ul>
-<li>Discussed a possible hardening release, circa 12/15/2005, focusing on APIs, performance, and usability
-<li>Would advance ability of ISV's to build on WTP
-<li>Likely numbered "1.1"; work on next major release (2.0?) could occur in parallel on a separate branch
-<li>Issues - coordination with WTP prereqs (EMF, GEF, etc.); believe these should be tractable
-</ul>
-
-<small>Minutes taken by Tim Wagner, April 26, 2005</small>
- </tr>
-
- <tr>
- <td>
- </td>
-
- </tr>
-
- </tbody></table>
-</html>
diff --git a/development/pmc_call_notes/2005-05-03.html b/development/pmc_call_notes/2005-05-03.html
deleted file mode 100644
index 6cdaaf0..0000000
--- a/development/pmc_call_notes/2005-05-03.html
+++ /dev/null
@@ -1,88 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for May 3, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - May 3, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <title>WTP PMC Minutes for May 3, 2005 Conference Call</title>
-
-
-Attending:
-Tim Wagner [TW],
-David Williams [DW],
-Arthur Ryman [AR],
-Dominique De Vito [DD],
-Naci Dai [ND]
-
-<h1>WTP PMC Minutes for May 3, 2005 Conference Call</h1>
-
-<h2>No procedural matters</h2>
-
-<h2>Community Update [LM]</h2>
-<ul>
-<li>Just over 8K downloads of M4 to date
-<li>Working with Ian Skerrett (EMO) and Pieter Humphrey (BEA) on WTP 1.0 press release
-<li>Articles in technical journals need to be written to build awareness of WTP; see Lawrence or Ian to participate
-<li>Arthur, Jochen writing for JDJ
-</ul>
-
-<h2>M4 API and Release Debrief</h2>
-<ul>
-<li>All APIs met exit criteria except the (EMF-generated) J2EE model; dynamic tracing
-coverage of that is now over 50%, but we will still likely have a testing shortfall.
-Mitigation: Early in M5, close on 100% coverage for this component.
-<li>API violations: Our API violates its own requirements (e.g., return types that are
-not in the API). Need to address this, including defining exactly what constitutes
-a violation (subclassing non-API classes/interfaces?).
-<li>[AR] Suggest starting shutdown sequence a week early to increase M5 ship date reliability.
-Need to limit destabilizing changes in shutdown sequence; a lightweight approval process
-may need to be in place for M5, which will serve as a rehearsal for GA convergence.
-<li>[ND] I-builds not getting to sufficient quality; creates drag on M-builds. May have
-a better chance with M5 since APIs are in place. Some tutorials/examples out of date with
-respect to M4 codeline. (Lawrence Mandel is organizing the effort to correct them.)
-</ul>
-
-<h2>Date And Release Changes</h2>
-<ul>
-<li>M5 moved to 7/1 to enable sufficient time for development and convergence.
-<li>PMC approved requirements group provision of a Dec. 15, 2005 hardening release plan (to be numbered 1.1)
-</ul>
-
-<h2>No Architecture Group Report this week </h2>
-<h2>No Requirements Group Report this week </h2>
-
-<h2>Performance Testing Server Support</h2>
-<ul>
-<li>Need JSP and Derby on server to enable WTP performance testing
-<li>PMC approved making request of the EMO
-</ul>
-
-<h2>Action Items</h2>
-<ul>
-<li>TW: work with Paul Meijer on Dr. Dobbs or other WTP article
-<li>AR: additional detail around performance testing infrastructure requests
-<li>AR: conversation with Roel Stalman regarding Oracle's EJB 3.0 plans and future integration with WTP
-<li>TW: conversation with Steve Todd regarding Borland's use of WTP and possible seat on WTP requirements group
-</ul>
-
-<small>Minutes taken by Tim Wagner, May 3, 2005</small>
- </tr>
-
- <tr>
- <td>
- </td>
-
- </tr>
-
- </tbody></table>
-</html>
diff --git a/development/pmc_call_notes/2005-05-10.html b/development/pmc_call_notes/2005-05-10.html
deleted file mode 100644
index 0d0b784..0000000
--- a/development/pmc_call_notes/2005-05-10.html
+++ /dev/null
@@ -1,81 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for May 10, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - May 10, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <title>WTP PMC Minutes for May 10, 2005 Conference Call</title>
-
-
-Attending:
-Tim Wagner [TW],
-Christophe Ney [CN],
-David Williams [DW],
-Arthur Ryman [AR],
-Dominique De Vito [DD],
-Naci Dai [ND]
-
-<h1>WTP PMC Minutes for May 10, 2005 Conference Call</h1>
-
-<h2>No procedural matters</h2>
-<h2>No community update [LM]</h2>
-<h2>M5 Planning</h2>
-<ul>
-<li>Continuing with provisional naming scheme where appropriate
-<li>Geronimo adapter added
-</ul>
-
-<h2>Architecture Group Report this week </h2>
-<ul>
-<li>See email posting for full group status
-<li>Component open houses begin 5/19
-<li>Kevin Haaland (platform team) asked to provide contact for working on 3.2
-project model issues (w.r.t. platform integration)
-</ul>
-
-<h2>No Requirements Group Report this week </h2>
-
-<h2>Performance Testing Server Support</h2>
-<ul>
-<li>Arthur and Jeffrey Liu providing detailed written requirements for
-transmission to the EMO
-</ul>
-
-<h2>Release Review</h2>
-<ul>
-<li>BIRT review occurred; AR, TW, and others participated in process
-<li>EMO communicated that provisional naming scheme is desired for WTP
-</ul>
-
-<h2>Clarifying API Conformance Rules</h2>
-<ul>
-<li>PMC voted to allow non-API base classes where warranted, with the understanding
-that the public facade created is still the responsibility of the provider
-<li>AR to check with Jim diRiviera on platform's perspective
-</ul>
-
-<h2>Action Items</h2>
-<ul>AR: talk to jeem about non-API base class "rule" in platform
-</ul>
-
-<small>Minutes taken by Tim Wagner, May 10, 2005</small>
- </tr>
-
- <tr>
- <td>
- </td>
-
- </tr>
-
- </tbody></table>
-</html>
diff --git a/development/pmc_call_notes/2005-05-17.html b/development/pmc_call_notes/2005-05-17.html
deleted file mode 100644
index 2588c97..0000000
--- a/development/pmc_call_notes/2005-05-17.html
+++ /dev/null
@@ -1,69 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for May 17, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - May 17, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- <title>WTP PMC Minutes for May 17, 2005 Conference Call</title>
-
-
-Attending:
-Tim Wagner [TW],
-Christophe Ney [CN],
-David Williams [DW],
-Arthur Ryman [AR],
-Lawrence Mandel [LM]
-
-<h1>WTP PMC Minutes for May 17, 2005 Conference Call</h1>
-
-<h2>No procedural matters</h2>
-<h2>Community Update [AR]</h2>
-<ul><li>People pages up now, sorted by contribution</ul>
-
-<h2>Decision on Flexible Project and Server Feature Request</h2>
-Because of the need to ship in a timely manner, we have decided to postpone suggested enhancements to the
-flexible project model/server APIs. Although these are important pieces of the WTP framework, scheduling
-constraints and incipient change in this area in the platform itself have caused us to defer those
-investigations until 1.1. The PMC resolved to
-<ul>
-<li>Maintain the current shipping schedule
-<li>Make the quality of user tools the focus of the 1.0 release
-<li>Make the framework (APIs) the focus of the 1.1 release, including finalizing the project and server models
-</ul>
-One natural fallout of this decision is that the server and project APIs must be provisional in 1.0,
-given that they are almost certain to change for the reasons cited.
-WTP will document them as such (JavaDoc, component.xml, release documentation) but is not currently planning on
-altering the packaging because of the delays involved and the shortness of the remaining schedule.
-
-
-<h2>No Architecture Group Report this week (but note that open houses begin Thursday) </h2>
-<h2>No Requirements Group Report this week </h2>
-
-<h2>Action Items</h2>
-<ul>
-<li>[TW] Communicate disposition of feature request to BEA.
-<li>[TW] Communicate decision on feature request to WTP community and EMO.
-<li>[TW] Verify status of performance testing infrastructure request with EMO.
-</ul>
-
-<small>Minutes taken by Tim Wagner, May 17, 2005</small>
- </tr>
-
- <tr>
- <td>
- </td>
-
- </tr>
-
- </tbody></table>
-</html>
diff --git a/development/pmc_call_notes/2005-05-24.html b/development/pmc_call_notes/2005-05-24.html
deleted file mode 100644
index 5d8ce3a..0000000
--- a/development/pmc_call_notes/2005-05-24.html
+++ /dev/null
@@ -1,86 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for May 24, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - May 24, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- Attending:
- Tim Wagner [TW],
- David Williams [DW],
- Lawrence Mandel [LM],
- Jochen Krause [JK],
- Arthur Ryman [AR],
- Naci Dai [ND],
- Dominique De Vito [DD],
- Christophe Ney [CN]
-
-<h1>WTP PMC Minutes for May 24, 2005 Conference Call</h1>
-
-<h2>No procedural matters</h2>
-
-<h2>Community Update [AR] </h2>
-<ul>
- <li>Help system now available (two plugins, split along JST and WST lines, 12-15 documents)
- <li>Component leads prioritizing help needs, which will be routed to developers
- <li>Newsgroup posts need to be read to provide community feedback and support
-</ul>
-
-<h2>Council Meeting Report [DW, TW] </h2>
-<ul>
- <li>[see email to <code>wtp-pmc@eclipse.org</code> for complete summary]
-</ul>
-
-<h2>Architecture Group Report [DW] </h2>
-<ul>
- <li>Component team reviews ("open houses") have begun; last Thursday was server and RDB tools,
- this week is web services
-</ul>
-
-<h2>Requirements Group Report [JK] </h2>
-<ul>
- <li>Draft of 1.1 discussed, preview will be released shortly
- <li>Discussing enhancements tracking
-</ul>
-
-<h2>Release Numbering</h2>
-<ul>
- <li>PMC is renumbering July 2005 release to 0.7
- <li>December release is planned to be 1.0
- <li>PMC will request more precise description of 1.0 release criteria from EMO
- <li>Technical issues: plugin numbers must be modified, Bugzilla categories should
- reflect release numbering, @since tags are now out of date, next week's I-build will
- be first under new numbering scheme
-</ul>
-
-<h2>Oracle's JSF Proposal [AR] </h2>
-<ul>
- <li>WTP supports the proposal
- <li>JSF would become a new component of the JST subproject
-</ul>
-
-<h2>Action Items</h2>
-<ul>
-<li>[TW] Communicate question to EMO regarding 1.0 release criteria
-<li>[TW] Clarify WTP charter documents with respect to JSF
-<li>[TW] Communicate PMC's support of Oracle JSF project to EMO
-<li>[DW] Bugzilla category rename
-</ul>
-
-<small>Minutes taken by Tim Wagner, May 24, 2005</small>
-
-</tr>
-<tr>
- <td> </td>
-</tr>
-</tbody></table>
-</html>
diff --git a/development/pmc_call_notes/2005-05-31.html b/development/pmc_call_notes/2005-05-31.html
deleted file mode 100644
index fb1cbac..0000000
--- a/development/pmc_call_notes/2005-05-31.html
+++ /dev/null
@@ -1,61 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for May 31, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - May 31, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- Attending:
- Tim Wagner [TW],
- David Williams [DW],
- Lawrence Mandel [LM],
- Jochen Krause [JK]]
-
-<h1>WTP PMC Minutes for May 31, 2005 Conference Call</h1>
-
-<h2>No procedural matters</h2>
-
-<h2>Community Update [LM] </h2>
-<ul>
- <li>Clarified that help component is part of the WST feature, included
- in nightly and integration builds, named "Web Application Development
- Guide"
-</ul>
-
-<h2>Architecture Group Report [DW] </h2>
-<ul>
- <li>Last week's open house was focused on web services;
- this week is the common subsystem
-</ul>
-
-<h2>December Release Planning [JK] </h2>
-<ul>
- <li>Will continue milestone numbering (beginning with M7).
- <li>Will clarify wording regarding interaction with platform planning
- for components with overlap issues.
-</ul>
-
-<h2>Action Items</h2>
-<ul>
- <li>[DW] Create Bugzilla category for 0.7 release
- <li>[TW] Announce release renumbering
- <li>[JK] Update website w.r.t. release renumbering
-</ul>
-
-<small>Minutes taken by Tim Wagner, May 31, 2005</small>
-
-</tr>
-<tr>
- <td> </td>
-</tr>
-</tbody></table>
-</html>
diff --git a/development/pmc_call_notes/2005-06-07.html b/development/pmc_call_notes/2005-06-07.html
deleted file mode 100644
index 9273299..0000000
--- a/development/pmc_call_notes/2005-06-07.html
+++ /dev/null
@@ -1,89 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for June 07, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - June 07, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- Attending:
- Tim Wagner [TW],
- David Williams [DW],
- Jochen Krause [JK],
- Arthur Ryman [AR],
- Dominique De Vito [DD],
- Lawrence Mandel [LM],
- Naci Dai [ND],
- Christophe Ney [CN]
-
-
-<h1>WTP PMC Minutes for June 07, 2005 Conference Call</h1>
-
-<h2>No procedural matters</h2>
-
-<h2>Community Update [LM] </h2>
-<ul>
- <li>Community feedback from 0.7 renumbering via newsgroup; PMC needs to help clarify.
- <li>Help system - each component lead has prioritized requirements, and these are being
- delegated. Volume of requirements versus resources will mean that we cannot accomplish
- all high priority requests.
- <li>ND reported on Holland Open conference
-</ul>
-
-<h2>Architecture Group Report [DW] </h2>
-<ul>
- <li>Open houses proceeding
- <li>Feature split still being investigated for 0.7 release; will have updated report
- next week on viability. Will review download packaging and udpate site plans
- post this split.
-</ul>
-
-<h2>0.7 Release Status and Endgame Planning [TW] </h2>
-<ul>
- <li>Current status by priorities: 5/23/785/2/0
- <li>Endgame proposal being reviewed by PMC.
-</ul>
-
-<h2>1.0 Release Planning [JK] </h2>
-<ul>
- <li>Requirements group released 1.0 themes and priorities document.
- <li>Backward compatibility requirement between 0.7 and 1.0 clarified to
- be (user) project layout compatibility.
- <li>EJB 3.0 interaction with WTP will be the subject of a conf call tomorrow
- with Oracle, Versant, and WTP representatives
- <li>Planning group needs to be rebooted to handle planning and scheduling.
- TW and AR will reboot this group and report back to the PMC.
-</ul>
-
-<h2>New Committer Review [AR] </h2>
-<ul>
- <li>Larry Isaacs proposed as committer by Tim de Boer, received four
- positive votes and no negative votes. PMC voted to grant him
- committership.
-</ul>
-
-<h2>Action Items</h2>
-<ul>
- <li>[DW] continue investigating feature split
- <li>[TW] update and circulate endgame plant
- <li>[TW/AR] reboot planning group
- <li>[JK] will talk to EMO regarding WTP IP issues surrounding caching of
- Sun-licensed DTDs and schemas
-</ul>
-
-<small>Minutes taken by Tim Wagner, June 07, 2005</small>
-
-</tr>
-<tr>
- <td> </td>
-</tr>
-</tbody></table>
-</html>
diff --git a/development/pmc_call_notes/2005-06-14.html b/development/pmc_call_notes/2005-06-14.html
deleted file mode 100644
index bfbb7d0..0000000
--- a/development/pmc_call_notes/2005-06-14.html
+++ /dev/null
@@ -1,77 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for June 14, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - June 14, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- Attending:
- Tim Wagner [TW],
- Arthur Ryman [AR],
- Lawrence Mandel [LM],
- Naci Dai [ND]
-
-
-<h1>WTP PMC Minutes for June 14, 2005 Conference Call</h1>
-
-<h2>No procedural matters</h2>
-
-<h2>Community Update [LM] </h2>
-<ul>
- <li>Help system proposal from IBM reviewed.
- <li>Three stage approach:
- <ol>
- <li>0.7 release: HTML-based, content contribution
- <li>1.0 release: begin DITA conversion; joint representation
- <li>post 1.0 release: fully DITA based, XML authoring tools available
- </ol>
- <li>IBM will contribute content and one additional committer
-</ul>
-
-<h2>0.7 Release Status and Endgame Planning </h2>
-<ul>
- <li>Current status by priorities (excluding enhancements): 4/19/691/1/0
- <li>Weekly status telecons will be used to review component-level defect tracking
- <li>Agreed to re-version non-enhancement entries in Bugzilla to 0.7 version
- <li>Plugins to be re-versioned to 0.7 this week
-</ul>
-
-<h2>Future Release Planning </h2>
-<ul>
- <li>Approved milestone dates for 1.0 release:
- <ol>
- <li>M8: September 23
- <li>M9: November 18
- <li>M10 (ship): December 16
- </ol>
- M9-M10 is the four week rampdown period.
- <li>Approved release numbering for 2006 release (synchronized with 3.2
- platform) to be 1.5.
-</ul>
-
-<h2>Action Items</h2>
-<ul>
- <li>[TW] announce planning dates (see above)
- <li>[TW/AR] committer access for IBM doc writer
- <li>[TW/AR] reboot planning group (held over)
- <li>[JK] will talk to EMO regarding WTP IP issues surrounding caching of
- Sun-licensed DTDs and schemas (held over)
-</ul>
-
-<small>Minutes taken by Tim Wagner, June 14, 2005</small>
-
-</tr>
-<tr>
- <td> </td>
-</tr>
-</tbody></table>
-</html>
diff --git a/development/pmc_call_notes/2005-06-21.html b/development/pmc_call_notes/2005-06-21.html
deleted file mode 100644
index b3bfe9f..0000000
--- a/development/pmc_call_notes/2005-06-21.html
+++ /dev/null
@@ -1,72 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for June 21, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - June 21, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- Attending:
- Tim Wagner [TW],
- Arthur Ryman [AR],
- David Williams [DW],
- Jochen Krause [JK],
- Dominique de Vito [DV]
-
-<h1>WTP PMC Minutes for June 21, 2005 Conference Call</h1>
-
-<h2>Procedural matters</h2>
-<ul>
- <li>Approved use of Bugzilla for action item tracking in PMC and dev telecons.
- Process: use "[action]" as the summary prefix. Any component
- (including "website") can be used, as appropriate.
- Entries can be either bugs or enhancements.
-</ul>
-
-<h2>No community update this week (Lawrence on vacation) </h2>
-
-<h2>Architecture Group Report [DW] </h2>
-<ul>
- <li>Open houses have completed
- <li>Progress on consolidating plugins and reducing dependencies
- <li>M5 architecture overview to be produced
-</ul>
-
-<h2>Sun DTD licensing for release </h2>
-JK working with EMO to determine legality of DTD caching vis a vis our
-user experience. Jochen to continue owning topic; goal is to enable
-0.7 release plan ASAP. Topic will be raised in release review.
-
-<h2>0.7 Release Status and Endgame Planning [TW] </h2>
-<ul>
- <li>Component leads need to review version for open bugs
- <li>Plugins to be re-versioned to 0.7 this week have completed
- <li>Rampdown process approved; see posting to WTP mailing list
-</ul>
-
-<h2>Susan Yeshin Committer Status [AR] </h2>
-Committership conditionally approved pending no negative votes between now and
-voting period completion.
-
-<h2>Action Items</h2>
-<ul>
- <li>[JK] Follow up on DTD licensing / legal issues
- <li>[DV] Follup up on SVG proposal and WTP requirements
-</ul>
-
-<small>Minutes taken by Tim Wagner, June 21, 2005</small>
-
-</tr>
-<tr>
- <td> </td>
-</tr>
-</tbody></table>
-</html>
diff --git a/development/pmc_call_notes/2005-06-28.html b/development/pmc_call_notes/2005-06-28.html
deleted file mode 100644
index 915c49f..0000000
--- a/development/pmc_call_notes/2005-06-28.html
+++ /dev/null
@@ -1,86 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for June 28, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - June 28, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- Attending:
- Tim Wagner [TW],
- David Williams [DW],
- Lawrence Mandel [LM],
- Arthur Ryman [AR],
- Naci Dai [ND],
- Christophe Ney [CN]
-
-<h1>WTP PMC Minutes for June 28, 2005 Conference Call</h1>
-
-<h2>Procedural matters</h2>
-No procedural matters to report.
-
-<h2>Community Update (LM] </h2>
-<ul>
- <li>Launch page will go live this week.
- <li>Web services screen cast will be removed; not sufficiently usable as-is.
- <li>Other screen casts will be incrementally replaced to update them to M5,
- capture the correct release numbering, and improve the illustration of
- current features.
- <li>Documentation contributions still planned for 0.7. Additions will be
- permitted to the documentation until late in the 0.7 release cycle.
-</ul>
-
-<h2>Sun DTD licensing for Release </h2>
- Licenses are now prompted for when retrieval happens, and caching is only
- performed once the license has been accepted. Also discussed moving our
- persistent record from workspace to a more permanent (cross workspace) spot.
- W3C schema redistribution has been approved by the EMO.
-
-<h2>0.7 Release Status </h2>
-<ul>
- <li>July 1st (Friday) is technically the M5 release date, but it's a
- national holiday in Canada. Will attempt to wrap the build on Thursday
- if possible. Four "Blocking" bugs currently; will ask community to
- review severity settings and pursue resolving these before declaring M5.
- <li>md5 signing to convert an I-build to an M-build is complicated; will
- instead begin generating M-build candidates that are not officially shown
- prior to being blessed.
- <li>Test plans need to be published by component teams.
- <li>New and Noteworthy must be updated prior to Thursday.
-</ul>
-
-<h2>0.7 Release Review </h2>
-<ul>
- <li>Reminder that the release review is next week, 7am PDT Wednesday. All PMC members
- should plan to attend the telecon.
-</ul>
-
-<h2>JSF Proposal Status </h2>
-<ul>
- <li>Review by Arthur of the initial call reviewing the Oracle proposal.
- <li>PMC suggests that a new component within WTP would be reasonable to
- contain this proposed technology.
-</ul>
-
-<h2>Action Items</h2>
-<ul>
- <li>[TW] Follow up on DTD licensing / legal issues with Mike Milinkovich
- <li>[DV] Follup up on SVG proposal and WTP requirements (held over)
-</ul>
-
-<small>Minutes taken by Tim Wagner, June 28, 2005</small>
-
-</tr>
-<tr>
- <td> </td>
-</tr>
-</tbody></table>
-</html>
diff --git a/development/pmc_call_notes/2005-07-05.html b/development/pmc_call_notes/2005-07-05.html
deleted file mode 100644
index c7b03ca..0000000
--- a/development/pmc_call_notes/2005-07-05.html
+++ /dev/null
@@ -1,73 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for July 05, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - July 05, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- Attending:
- Tim Wagner [TW],
- David Williams [DW],
- Lawrence Mandel [LM],
- Jochen Krause [JK],
- Arthur Ryman [AR]
-
-<h1>WTP PMC Minutes for July 05, 2005 Conference Call</h1>
-
-<h2>Procedural matters</h2>
-No procedural matters to report.
-
-<h2>JavaOne Conference Report [TW] </h2>
-Impressions of conference and Eclipse buzz / presence.
-
-<h2>Community Update [LM] </h2>
-<ul>
- <li>Susan Yeshin has been working with writers and component leads to get help system ready.
- "Books" (top-level items in help system) in flight -
- WST dev, JST dev, and overall WTP help (user focused) should be available this week.
- Website material will also go up coincident with the contribution.
- Dynamic ("popup") help will be the next priority. Christophe (from Innoopract) has been
- helping with this as well.
-</ul>
-
-<h2>Requirements Update [JK] </h2>
-<ul>
- <li>Will target late July for a "PM open house" - designed to solicit requirements and describe the
- status/content of WTP
-</ul>
-
-<h2>0.7 Release Status </h2>
-<ul>
- <li>Bug count by priority: 0 / 14 / 298 / 3 (315 total)
-</ul>
-
-<h2>0.7 Release Review </h2>
-<ul>
- <li>Reminder that the release review is tomorrow, 7am PDT Wednesday. All PMC members
- should plan to attend the telecon.
- <li>Updated draft version of slides sent to PMC mailing list.
-</ul>
-
-<h2>Action Items</h2>
-<ul>
- <li>[LM] Add boilerplate "about.html"s where missing
- <li>[DV] Follow up up on SVG proposal and WTP requirements (held over)
-</ul>
-
-<small>Minutes taken by Tim Wagner, July 05, 2005</small>
-
-</tr>
-<tr>
- <td> </td>
-</tr>
-</tbody></table>
-</html>
diff --git a/development/pmc_call_notes/2005-07-12.html b/development/pmc_call_notes/2005-07-12.html
deleted file mode 100644
index 53de3c6..0000000
--- a/development/pmc_call_notes/2005-07-12.html
+++ /dev/null
@@ -1,96 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for July 12, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - July 12, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- Attending:
- Tim Wagner [TW],
- Naci Dai [ND],
- Lawrence Mandel [LM],
- David Williams [DW],
- Jochen Krause [JK],
- Arthur Ryman [AR]
-
-<h1>WTP PMC Minutes for July 12, 2005 Conference Call</h1>
-
-<h2>Procedural matters</h2>
-<ul>
- <li>WTP accepts Dominique de Vito's resignation and offers its thanks for his contributions.
- <li>Dirk Le Roux's committership vote accepted.
- <li>WTP 0.7 release review has been accepted by the EMO.
- <li>EMO charter clarification. We need to clarify that the Java EE portion of our charter covers
- current and future versions of Java EE, including JCP standards in pre-acceptance stages and
- standards that are applicable to Web or Java application development that are not specifically
- targeted for Java EE.
-</ul>
-
-<h2>Community Update [LM] </h2>
-<ul>
- <li>Short delay in help content; should be ready within the next few days. This will be the bulk of the
- contribution.
- <li>Christophe making progress on ISV documentation; first version be available toward the end of this week.
- <li>Looking at decoupling the help build from the dev build.
-</ul>
-
-<h2>Architecture Update [DW] </h2>
-<ul>
- <li>Chuck planning to work with Kevin Haaland (platform base) w.r.t. flexible project migration; no update yet.
-</ul>
-
-<h2>0.7 Release Status </h2>
-<ul>
- <li>First RC scheduled for Wednesday, July 13th
- <li>Bug count by priority: 1 / 29 / 300 / 12 (342 total)
- <li>Component leads will be polled; Arthur and Naci will make final call on RC viability during
- the day Wednesday. Cutoff on fixes Tuesday is 8pm EDT; build will be ready by midnight EDT.
- (CC will be suspended after the build.)
- Component leads should vote by 4pm EDT. If vote fails we spin another release with additional
- fixes; otherwise Arthur and Naci make final determination.
-</ul>
-
-<h2>JSF Incubation </h2>
-<ul>
- <li>Webpage (peer to WST/JST within the existing website)
- <li>Separate mailing list (wtp-jsf-dev@eclipse.org)
- <li>Will prefer org.eclipse.jst.jsf as packaging, not incubator packaging
- <li>PMC position
-</ul>
-
-<h2>Summary of Remote Server Call (JMX deployment / JSR 88) </h2>
-<ul>
- <li>See JST email list for meeting minutes.
-</ul>
-
-<h2>Action Items</h2>
-<ul>
- <li>[TW] Committership paperwork for Dirk Le Roux filed
- <li>[TW] Offer thanks from PMC to Domninique de Vito
- <li>[JK] Select date for PM open houses
- <li>[TW] Draft language for charter revision with the EMO
- <li>[AR] Update charter diagram
- <li>[LM / ND] Help build system decoupling
- <li>[TW] Inform EMO and Oracle of invitation to Oracle to join the WTP PMC
- <li>[TW / AR] Follow up with Oracle on timing, plans, and project scope/wording finalization for
- JSF (sub) project within WTP. Updated proposal language should seed the WTP subproject
- website. Publicize on the website, newsgroup, etc.
-</ul>
-
-<small>Minutes taken by Tim Wagner, July 12, 2005</small>
-
-</tr>
-<tr>
- <td> </td>
-</tr>
-</tbody></table>
-</html>
diff --git a/development/pmc_call_notes/2005-07-19.html b/development/pmc_call_notes/2005-07-19.html
deleted file mode 100644
index 02c3b14..0000000
--- a/development/pmc_call_notes/2005-07-19.html
+++ /dev/null
@@ -1,94 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for July 19, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - July 19, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- Attending:
- Tim Wagner [TW],
- Lawrence Mandel [LM],
- David Williams [DW],
- Arthur Ryman [AR],
- Christophe Ney [CN],
- Jochen Krause [JK]
-
-<h1>WTP PMC Minutes for July 19, 2005 Conference Call</h1>
-
-<h2>Community Update [LM] </h2>
-<ul>
- <li>Docs are ready to go for server tools, XML, SSE, J2EE; Web Services and data tools will not make 0.7
- <li>waiting on legal clearance
- <li>Discussion about separating help build in flight (looks reasonably straightforward)
- <li>Jeffrey researching update manager site (Eclipse hosted/communal)
- <li>WTP articles solicited
- <li>Screencasts need to be updated for 0.7 GA and refined. Jochen and Lawrence will start with the
- Web Services topic.
- <li>FAQ needs updating (LM).
-</ul>
-
-<h2>Procedural matters</h2>
-<ul>
- <li>Charter revision in progress; working on the "draft standards" portion. Targeting next month's board call.
-</ul>
-
-<h2>Requirements Update [JK] </h2>
-<ul>
- <li>Product management open house planned for after 0.7 release.
- <li>Using Bugzilla enhancements as foundation for call.
-</ul>
-
-<h2>Architecture Update [DW] </h2>
-<ul>
- <li>No new issues; ramping up 3.2 planning.
-</ul>
-
-<h2>0.7 Release Status </h2>
-<ul>
- <li>Second RC scheduled for Friday, July 22nd; slight complication w.r.t. release of JEM (same day).
- We will attempt to incorporate their final driver. Build will be targeted for Friday evening.
- <li>Bug count by priority: 1 / 28 / 297 / 38 (364 total)
- <li>Cutoff on fixes: Thursday 8pm EDT. Build will be done overnight (US) and ready by 9am Friday.
- JEM update on Friday will require a respin during the day Friday, but WTP bits can be tested in
- parallel.
- (CC will be suspended after the build.)
- <li>Axis 1.2.1 update - legal review will cause this to slip to 1.0
- <li>J2EE schemas/DTDs update - some of these reference IBM material, and these can be redistributed
- by WTP in principle; Janet reviewing
-</ul>
-
-<h2>JSF Incubation </h2>
-<ul>
- <li>Waiting on EMO to run release review.
- <li>Mike Milinkovich discussing resource levels with Oracle w.r.t. scope of project.
-</ul>
-
-
-<h2>Action Items</h2>
-<ul>
- <li>[JK] Publicize PM open houses
- <li>[AR] Update charter diagram
- <li>[LM / ND] Help build system decoupling
- <li>[LM / JK] Update Web Service webcast
- <li>[TW] Send process update to dev list
- <li>[TW] Draft response on legal process
- <li>[TW] Attend Versant ORM creation review to address any WTP-related issues
-</ul>
-
-<small>Minutes taken by Tim Wagner, July 19, 2005</small>
-
-</tr>
-<tr>
- <td> </td>
-</tr>
-</tbody></table>
-</html>
diff --git a/development/pmc_call_notes/2005-07-26.html b/development/pmc_call_notes/2005-07-26.html
deleted file mode 100644
index 8663cb5..0000000
--- a/development/pmc_call_notes/2005-07-26.html
+++ /dev/null
@@ -1,82 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for July 26, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - July 26, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- Attending:
- Tim Wagner [TW],
- Lawrence Mandel [LM],
- David Williams [DW],
- Arthur Ryman [AR],
- Jochen Krause [JK]
- Naci Dai [ND]
-
-<h1>WTP PMC Minutes for July 26, 2005 Conference Call</h1>
-
-<h2>Community Update [LM] </h2>
-<ul>
- <li>Help will be ready to go (books and infopop) with 0.7 at the end of the week.
- <li>Webservice screencast update expected this week.
- <li>FAQ update will happen next week.
-</ul>
-
-<h2>Procedural matters</h2>
-<ul>
- <li>Final charter modifications reviewed; TW to produce "diff" version for PMC and Board.
- <li>Post 0.7 vacation: telecons and status calls will be suspended for three weeks. Use the
- mailing list and convene ad hoc meetings as needed.
- <li>WTP committers and PMC members should be especially aware of newsgroup activity following the
- 0.7 release to provide adequate post-release community support.
-</ul>
-
-<h2>JSF Update </h2>
-<ul>
- <li>Will be sub-project while in incubation mode; post incubation the expectation is that it will become
- one or more components within JST.
- <li>Targeting WTP 1.5 release as first coordinated JSF delivery.
- <li>Oracle planning creation review for end of August, soliciting additional contributors.
-</ul>
-
-<h2>Requirements Update [JK] </h2>
-<ul>
- <li>Product open houses: request sent to requirements mailing list and requirements group members,
- also soliciting specific companies known to be interested.
- <li>Call scheduled for August 9th; may have second call during September due to vacation schedules.
-</ul>
-
-<h2>Architecture Update [DW] </h2>
-<ul>
- <li>No new issues; ramping up 3.2 planning.
-</ul>
-
-<h2>0.7 Release Status </h2>
-<ul>
- <li>Defects 104563, 104413, 103306 accepted for inclusion (in addition to the four previously voted on).
- <li>RC4 build should start within a few hours of the completion of this call.
-</ul>
-
-<h2>Maintenance Stream (0.7.1) </h2>
-<ul>
- <li>Will enable WTP to get processes in place for multi-stream development and release
- <li>Primarily targeting NL fixes in 0.7; PMC triage will remain in place
- <li>Will add fixes proactively, but will target release for platform 3.1.1
-</ul>
-
-<h2>Action Items</h2>
-No action items recorded.
-
-<small>Minutes taken by Tim Wagner, July 26, 2005</small>
-</tr>
-</tbody></table>
-</html>
diff --git a/development/pmc_call_notes/2005-08-23.html b/development/pmc_call_notes/2005-08-23.html
deleted file mode 100644
index 8bef654..0000000
--- a/development/pmc_call_notes/2005-08-23.html
+++ /dev/null
@@ -1,130 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for August 23, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - August 23, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- Attending:
- David Williams [DW],
- Arthur Ryman [AR],
- Naci Dai [ND]
-
-<h1>WTP PMC Minutes for August 23, 2005 Conference Call</h1>
-<pre>
-1. Ecosystem Update
-
-Lawrence:
- - the FAQ page has been updated
- - tte Community page will be updated soon
- - most tutorials have been updated to reflect WTP 0.7 content
- - there has been great feedback on WTP 0.7 in the newsgroup, frequent posts, good discussions, problem reports captured as bugs
- - Help system contributions have been received from Christoph Krawczyk and Christopher Judd
- - EclipseWorld is being held in New York next week and there are many WTP presentations
- - EclipseCon 2006 has issued a call for submissions, please ask your colleagues to contribute abstracts
-
-2. WTP 0.7.1 Release Status
-
-David - the NL fixes have been made
-Naci - looks like non-NL fixes have also been committed
-Arthur - we need to limit fixes to NL and sever problems
- - we have not formally committed to a 0.7.1 release
- - we need to establish the demand from adapters and end users
- - if we do have a formal 0.7.1 release, we should synchronize it with Eclipse 3.1.1
-
-[action] Arthur to followup on demand for a 0.7.1 release [1]
-
-3. WTP 1.0 Release Planning
-
-Arthur - we need to firm up our plans and establish the API set we will release
- - see the roadmap for 1.0 priorities [2]:
-
- * Promote selected provisional APIs to platform status based on vendor requirements.
- * Componentize WTP into Features to enable adopters to select subsets of function.
- * Fix National Language bugs.
- * Fix Accessibility bugs.
- * Fix other important bugs, with high priority given to those required by adopters.
- * Upgrade Help system content.
-
-David - agreed, with the understanding that performance problems are included under "other important bugs"
- - I've been working on the Feature definition
-Naci - agreed
-Arthur - any planned enhancements in addition to bugs?
-Naci - possibly a CMP EJB creation wizard
- - some Web service enhancements are being planned
-David - possibly spell checking and folding, subject to sizing and resource
-
-[action] Arthur to send out note requesting component leads to update their milestone plans and to map APIs to milestones
-
-David - the recent build breaks have been mainly caused by JUnit timeouts, but are otherwise stable
- - the builds may destabilize as more code gets committed
-
-4. Release Engineering
-
-David - we resolved the treatment of maintenance (M) builds
- - they are treated like integration builds
-
-Naci - I've need refactoring the build scripts and and documenting the process
- - we need to have reproducible builds that can be run locally
- - I am restructuring the tasks so they are more modular
- - I've been assessing Maven, which is widely used at Apache, as a way to simplify our build scripts
-
-5. Charter Revisions
-
-Arthur - Mike proposal a delta to our revisions in the area of working on draft standards
- - the terms of use of the draft standards must be consistent with our use in Eclipse
-Naci - agreed
-David - agreed
-
-[action] Tim to make the change and resubmit to Mike for approval
-
-6. WTP 1.5 Planning
-
-Arthur - see roadmap [2]
- - Eclipse 3.2 is proposing a train
- - projects can opt in to a coordinated release
- - recommend we opt in
- - to catch the train we need to move up our milestone dates by 2 weeks
-David - agree
-Naci - agree
-Arthur - I'll update the roadmap now, but we should wait for a PMC quorum to formally opt it
-
-[action] Tim to review Eclipse 3.2 planning with PMC and hold vote on opting in
-
-[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=107743
-[2] http://www.eclipse.org/webtools/development/planning/roadmap.html
-
-7. Architecture Update
-
-David - I am working on a proposal for Feature definition in WTP 1.0 and will post it soon
-Arthur - can we target this for 1.0 M8?
-David - yes, but not completely due to some additional refactoring work
-
-8. Other Business
-
-Naci - Gorkem has developed a PDE tool to aid ISVs in creating server adapters
-David - has the PMC agreed to support this type of tool
-Arthur - this will help promote the adoption of WTP APIs and extension points
- - we should encourage this type of tool for all of our extension points
-David - I suggest we start by packaging this type of tool in the SDK examples directory of each component
-
-David - should be be providing zips for each Feature?
- - if so, can we use CVS to host them?
-Arthur - CVS is not good for binaries since it can't diff them and the server isn't mirrored
- - why not have a single binary zip and let adopters extract binaries from it?
-David - OK, we won't build mulriple zips for now
-</pre>
-
-<small>Minutes taken by Arthur Ryman, August 23, 2005</small>
-</tr>
-</tbody></table>
-</html>
diff --git a/development/pmc_call_notes/2005-08-30.html b/development/pmc_call_notes/2005-08-30.html
deleted file mode 100644
index c826015..0000000
--- a/development/pmc_call_notes/2005-08-30.html
+++ /dev/null
@@ -1,91 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for August 30, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - August 30, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- Attending:
- Tim Wagner [TW],
- David Williams [DW],
- Jochen Krause [JK]
- Christophe Ney [CN]
-
-<!--PMC MEMBERS NOT PRESENT ON THIS CALL:
- Lawrence Mandel [LM],
- Naci Dai [ND],
- Raghunathan Srinivasan [RS]
- Arthur Ryman [AR],
--->
-
-<h1>WTP PMC Minutes for August 30, 2005 Conference Call</h1>
-
-<h2>Community Update [LM] </h2>
-<ul>
- <li>LinuxWorld had an Eclipse presence (report from CN)
- <li>EclipseWorld in progress; more updates next week (TW, AR, LM attending)
-</ul>
-
-<h2>Procedural matters</h2>
-<ul>
- <li>Christophe Ney is resigning as co-lead, to remain on the PMC as a member. The PMC thanks him for his
- many project contributions as project lead.
-</ul>
-
-<h2>Council Update</h2>
-<ul>
- <li>Architecture council discussed its role, also spent time reviewing "flexible project model" as lead by David
- <li>Planning council discussed release train issues (including milestone pile-on), IP log requirement for all projects,
- and project info XML file format
-</ul>
-
-<h2>JSF Update </h2>
-<ul>
- <li>JSF creation review has been passed by the EMO, and the project is now being provisioned into WTP as a sub project (peer
- of WST and JST).
-</ul>
-
-<h2>Requirements Update [JK] </h2>
-<ul>
- <li>Product management informational call - did not receive sufficient interest to hold this event in August, will
- wait until September when more people are back from vacation (next Thursday is target date).
- <li>Borland expressed interest during council meetings in getting more involved with WTP development; will attempt to
- connect JK and Richard Gronback to make progress on this front
- <li>Exit criteria for 1.0 must include extension point documentation [JK]
- <li>API definition should be targeted for our first 1.0 milestone, 9/23 [DW]
-</ul>
-
-<h2>Architecture Update [DW] </h2>
-<ul>
- <li>Discussion of feature includes and the current problems surrounding them; David will pursue as part of a general
- feature revision proposal
-</ul>
-
-<h2>0.7.1 (Maintenance Stream) Status </h2>
-<ul>
- <li>Most NL fixes are complete
- <li>Several blocking bugs remain open as of today
- <li>Would adopt 3.1.1 rev of platfrom (currently slated for end of September)
-</ul>
-
-<h2>1.0 Planning </h2>
-No further work on 1.0 planning; limited PMC attendance.
-
-<h2>Action Items</h2>
-<ul>
- <li>TW to follow up with Charter revisions approved in last meeting (held over).
-</ul>
-
-<small>Minutes taken by Tim Wagner, August 30, 2005</small>
-</tr>
-</tbody></table>
-</html>
diff --git a/development/pmc_call_notes/2005-09-06.html b/development/pmc_call_notes/2005-09-06.html
deleted file mode 100644
index da845f1..0000000
--- a/development/pmc_call_notes/2005-09-06.html
+++ /dev/null
@@ -1,100 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for September 6, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - September 6, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- Attending:
- Tim Wagner [TW],
- Naci Dai [ND],
- Raghunathan Srinivasan [RS]
- David Williams [DW],
- Lawrence Mandel [LM],
- Arthur Ryman [AR],
- Jochen Krause [JK]
-
-<!--PMC MEMBERS NOT PRESENT ON THIS CALL:
- Christophe Ney [CN],
--->
-
-<h1>WTP PMC Minutes for September 6, 2005 Conference Call</h1>
-
-<h2>Community Update [LM] </h2>
-<ul>
- <li>EclipseWorld - many WTP presentations from both inside and outside the WTP dev community, all talks well attended and
- received
- <li>Website content still in flux; component leads are working on project plans
- <li>Arthur suggested factoring the website content so that component leads can update the relevant portion quickly
- <li>Phoenix not ready yet; we will try to be early adopters when they're ready
- <li>DW suggested making "audience organization" (users, extenders, devs) more obvious
- <li>EclipseCon program committee has set aside two technical and one tutorial slots per top-level project; projects
- still need to go through the proposal process (and can submit additional talks, of course)
-</ul>
-
-<h2>Procedural matters</h2>
-<ul>
- <li>No procedural matters to report.
-</ul>
-
-<h2>0.7.1 (Maintenance Stream) Status </h2>
-<ul>
- <li>Using Thursday status/component lead meeting for triage; PMC members are invited to attend that.
- <li>Arthur researching SOAP schema IP issues; may need to re-vet in 0.7.1 with Foundation legal.
-</ul>
-
-<h2>1.0 and 1.5 Planning </h2>
-<ul>
- <li>WTP joining the 1.5 release train; will need to join train ASAP to improve likelihood of final ship.
- <li>We are using many internal APIs from the platform; any drift caused by this reliance on platform internals
- could be mitigated in either the 1.0 line or the (not yet created) 1.5 line. Split point will be late October/early
- November (roughly the M9 milestone).
- <li>We need to create the 1.5 line at least in time to handle new feature work that cannot go into the 1.0 codebase.
- <li>Once we move to 1.5 (and join the Zebra train), we will need to migrate to a 6 week release cycle in order to
- synchronize. (DW: suggesting our M9 timeframe).
- <li>1.0 will remain on its existing (8 week milestones) schedule.
- <li>For 1.5, we would need to begin synchronizing with platform I-builds (not an immediate requirement).
- <li>Chuck will be presenting a proposal soon on project-related APIs.
-</ul>
-
-<h2>Requirements Update [JK] </h2>
-<ul>
- <li>Open requirements call will be held this Thursday. Oracle, BEA, and others are planning to participate;
- IBM has conflict with internal planning meetings. Will attempt to solicit feedback on 1.5 plan and any
- additional requirements.
-</ul>
-
-<h2>Architecture Update [DW] </h2>
-<ul>
- <li>Weekly call will resume this week.
- <li>Feature split up will proceed as proposed (little feedback received so far). Will start with the low-hanging fruit;
- some of the more difficult divisions may extend beyond 1.0 release.
- <li>Feature split up will be important to build / releng restructuring as well. Might be able to use Buckminster's tools
- to view the dependency arcs.
-</ul>
-
-<h2>JSF Update [RS] </h2>
-<ul>
- <li>Legal process moving forward within Oracle (committer agreement, etc.)
-</ul>
-
-<h2>Action Items</h2>
-<ul>
- <li>[RS] Will investigate EclipseCon presentation topics.
- <li>[TW] Get platform dates and drive process of setting 2006 WTP milestone dates.
- <li>[JK] Follow up with SAS and SAP w.r.t. requirements call (Th).
-</ul>
-
-<small>Minutes taken by Tim Wagner, September 6, 2005</small>
-</tr>
-</tbody></table>
-</html>
diff --git a/development/pmc_call_notes/2005-09-13.html b/development/pmc_call_notes/2005-09-13.html
deleted file mode 100644
index c0b10ba..0000000
--- a/development/pmc_call_notes/2005-09-13.html
+++ /dev/null
@@ -1,114 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for September 13, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - September 13, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- Attending:
- Naci Dai [ND],
- Jochen Krause [JK]
- Lawrence Mandel [LM],
- Christophe Ney [CN],
- Arthur Ryman [AR],
- Raghunathan Srinivasan [RS],
- Tim Wagner [TW],
- David Williams [DW]
-
-<!--PMC MEMBERS NOT PRESENT ON THIS CALL:
-
--->
-
-<h1>WTP PMC Minutes for September 13, 2005 Conference Call</h1>
-
-<h2>Community Update [LM] </h2>
-<ul>
- <li>Website changes to simplify updates to frequent content. Will create a separate directory structure organized
- around specific components within specific releases, to constrain the amount of code that needs to be checked out
- for the bulk of developers. Tutorials, design documents, and models will remain in the existing directory
- structure and be updated in place (these updates occur less frequently). JavaDocs will be removed; these are now
- available through the help system. Implementation will likely start after M8 is complete.
- <li>Discussion of automatic harvesting system that would enable Bugzilla to be used in lieu of separate component
- plans. Because all impact to the product must be described via Bugzilla, feature work should be trackable
- through it. [JK] However, component leads are able to describe milestone plans in more readable terms than reading
- a Bugzilla report [AR]. Two problems that come up are the desire to describe finer granularity steps than the
- feature request as a whole and the inability to edit the title of a Bugzilla entry once created.
- <li>Link to "current plan" should always be valid [DW]; would be nice to treat this like API and ensure that it
- always functions as a reference.
- <li>EclipseCon presentation suggestions:
- <ul>
- <li>Architecture and API/extension point overview
- <li>JSF project introduction
- </ul>Will continue discussing this next week.
-</ul>
-
-<h2>Procedural matters</h2>
-<ul>
- <li>No procedural matters to report.
-</ul>
-
-<h2>Requirements Update [JK] </h2>
-<ul>
- <li>Product manager requirements call held last Thursday. Participants included BEA, JBoss, Borland, Oracle,
- Sybase, and Parasoft in addition to WTP PMC representation. Focus was requirements gathering for 1.0 and 1.5.
- Benefit was primarily outbound.
- <li>Need to begin working on 1.5 requirements between now and end of year. JK will join the weekly Thursday status
- call to initiate 1.5 requirements gathering.
- <li>Eclipse requirements council has decided to use Bugzilla for requirements tracking purposes.
- <li>Non-API to API transition policy. We're essentially forcing our adopters to use non-API code because we
- won't have a full-featured surface area in 1.0. So even though we're technically permitted to make changes,
- we want to support client migration as smoothly as possible onto post-1.0 versions of WTP.
- One suggestion is to enable clients to use API scanning and inform us of internal APIs that they're using so
- we have more information. We can also attempt to treat our important internal methods as "pseudo API",
- attempting to keep it live for another release to decrease the migration burden.
-</ul>
-
-<h2>Architecture Update [DW] </h2>
-<ul>
- <li>No meeting last week due to scheduling conflicts. Sub-system definition, feature split-up,
- flexible project, and 1.0 API definition are the top agenda items.
-</ul>
-
-<h2>0.7.1 (Maintenance Stream) Status </h2>
-<ul>
- <li>Arthur researching SOAP schema IP issues; may need to re-vet in 0.7.1 with Foundation legal.
- <li>Platform 3.1.1 RCs have begun. We will make the transition to 3.1.1 for 0.7.1 builds in preparation
- for our ship.
- <li>Freeze on 0.7.1 additions (apart from platform integration issues) is 9/23. Release is scheduled for early October
- (after 3.1.1 is gold and any remaining issues have been resolved).
-</ul>
-
-<h2>Updates on related Projects </h2>
-<ul>
- <li>Iona announced "STP", a SOA tools project. There are some areas of overlap with WTP, including some areas with
- potential for joint development as well as normal dependencies on WTP APIs and extension points.
- Since Christophe is on both PMCs, he can serve to coordinate areas of overlap and serve as a liaison
- between the teams.
- <li>Buckminster Technology Project: Sort of a "super update manager" - it assists with setting up workspaces, including
- potentially third party software. There might be some synergy between our build process, with its map files, and
- the dependency metadata created by the Buckminster project. Buckminster team is working on making a build system
- compatible with PDE builds; once it reaches that stage, we will evaluate for use in production WTP builds.
- <li>JSR 220: see summary of EclipseWorld meetings on "jst-dev". Tomorrow at 15:00 UTC there will be a meeting to
- make the first step in getting to a combined model.
-</ul>
-
-<h2>Action Items</h2>
-<ul>
- <li>[TW] Get platform dates and drive process of setting 2006 WTP milestone dates.
- <li>[JK] Follow up with SAS and SAP w.r.t. 1.0 requirements.
- <li>[AR] 0.7.1 Schema/IP issue.
-</ul>
-
-<small>Minutes taken by Tim Wagner, September 13, 2005</small>
-</tr>
-</tbody></table>
-</html>
diff --git a/development/pmc_call_notes/2005-09-20.html b/development/pmc_call_notes/2005-09-20.html
deleted file mode 100644
index e1da9f6..0000000
--- a/development/pmc_call_notes/2005-09-20.html
+++ /dev/null
@@ -1,89 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for September 20, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - September 20, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- Attending:
- Arthur Ryman [AR],
- Raghunathan Srinivasan [RS],
- David Williams [DW],
- Lawrence Mandel [LM],
- Tim Wagner [TW],
- Naci Dai [ND],
- Jochen Krause [JK]
-
-<!--PMC MEMBERS NOT PRESENT ON THIS CALL:
- Christophe Ney [CN],
--->
-
-<h1>WTP PMC Minutes for September 20, 2005 Conference Call</h1>
-
-<h2>Community Update [LM] </h2>
-<ul>
- <li>Documentation for 0.7.1 will be released as a separate ZIP file on the update/download sites. Docs are in good shape
- and current effort is expected to complete on time.
- <li>Website update (partitioning) has begun; Arthur and Lawrence are in flight on this project.
-</ul>
-
-<h2>Procedural matters</h2>
-<ul>
- <li>Konstantin Komissarchik committer vote accepted.
- <li>Tim will bring WTP Charter mods before the Eclipse Board on Wednesday.
- <li>Contribution questionnaire policy clarified: 3rd contributions must come in via Bugzilla patches, and
- require a questionnaire if they are over 100 lines or represent non EPL-licensed IP.
- See <a href="http://www.eclipse.org/org/processes/Guidelines_for_Eclipse_Development_Process/project-log.html">
- The Eclipse Process</a> for more details.
- <li>Scanning tool for Bugzilla patches would be helpful to meet IP due diligence requirements.
- <li>Tim to start working on IP log.
-
-</ul>
-
-<h2>Architecture Update [DW] </h2>
-<ul>
- <li>Open house held on "feature" feature last week.
- <li>Progress on flexible project planning and alignment with platform plans, led by Chuck.
-</ul>
-
-<h2>0.7.1 (Maintenance Stream) Status </h2>
-<ul>
- <li>Arthur and Tim researching SOAP schema IP issues; four of the five W3C schemas are unclear on their usage restrictions.
- <li>Planning for code complete this Friday (9/23).
-</ul>
-
-<h2>1.0 Status </h2>
-<ul>
- <li>On track to release on schedule (9/23)
-</ul>
-
-<h2>JSF Status </h2>
-<ul>
- <li>Paperwork planned to complete by this Friday, followed by EMO provisioning.
- <li>Working on milestone planning; will publish information when paperwork completes.
-</ul>
-
-<h2>API Migration Policy </h2>
-<ul>
- <li>Discussion of internal promotion, deprecation, and communication with adopters;
- Arthur revising proposal based on feedback.
-</ul>
-
-<h2>Action Items</h2>
-<ul>
- <li>[TW] Get platform dates and drive process of setting 2006 WTP milestone dates (help up on planning info from platform).
-</ul>
-
-<small>Minutes taken by Tim Wagner, September 20, 2005</small>
-</tr>
-</tbody></table>
-</html>
diff --git a/development/pmc_call_notes/2005-09-27.html b/development/pmc_call_notes/2005-09-27.html
deleted file mode 100644
index 342fc30..0000000
--- a/development/pmc_call_notes/2005-09-27.html
+++ /dev/null
@@ -1,97 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for September 27, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - September 27, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- Attending:
- Raghunathan Srinivasan [RS],
- Arthur Ryman [AR],
- David Williams [DW],
- Lawrence Mandel [LM],
- Tim Wagner [TW]
-
-<!--PMC MEMBERS NOT PRESENT ON THIS CALL:
- Christophe Ney [CN],
- Jochen Krause [JK]
- Naci Dai [ND],
--->
-
-<h1>WTP PMC Minutes for September 27, 2005 Conference Call</h1>
-
-<h2>Community Update [LM] </h2>
-<ul>
- <li>Website partitioning update: Reorg mostly complete - 1.0 plans have been moved, need
- some existing link fixup from old summary plans. Also need to generate reports from
- Bugzilla and make them look like milestone plan (Arthur). Tutorial cleanup complete;
- tutorials are now each self contained. Next step is to reorganize subproject pages
- (groups by component).
- <li>EclipseCon - WTP slot use. Raghu: Oracle preparing submissions for EJB 3.0 and JSF (the
- latter could use one of the WTP reserved slots). AR: One of our slots should be the
- overview presentation, and we should submit as many additional abstracts as we can
- for deep dives on specific topics.
-</ul>
-
-<h2>Procedural matters [TW] </h2>
-<ul>
- <li>Mike Milinkovich did not include the WTP charter modifications in the pre-meeting materials for the Board face-to-face
- in Chicago last week, so the vote will occur on the next board call. I presented the changes, and all but the "emerging
- specs" part were considered acceptable. The Board suggested an amendment of that one to use the following language:
- "...new revisions of existing standards..." to constrain pre-release tooling work.
-</ul>
-
-<h2>Architecture Update [DW] </h2>
-<ul>
- <li>Progress on flexible project planning and alignment with platform plans, led by Chuck
- (call to occur Wednesday). Discussed approach of having a wizard that would migrate
- a multi-module app to multiple projects.
- <li>Feature reorg in flight; partial progress will be made in 1.0, with the remainder
- going into 1.5.
- <li>"Aspects" went into the (M9) build; integration will proceed this week.
- <li>Migration of code to base in time for joining the train is a current risk factor
- (tabbed properties, extensible navigator, Internet proxy settings).
- <li>Need to resurrect API scanning tool to enable PMC progress review.
-</ul>
-
-<h2>0.7.1 (Maintenance Stream) Status </h2>
-<ul>
- <li>Currently reviewing/testing release candidate. Each team is being asked to spend one
- day to run through use cases/scenarios.
- <li>Looking to declare publically Friday if all goes well.
-</ul>
-
-<h2>1.0 Status </h2>
-<ul>
- <li>New and Noteworthy - need to ensure that Oracle adapter is described.
- <li>M9 component plans complete.
- <li>Risk analysis: facet integration, multi-module migration, performance problems
-</ul>
-
-<h2>JSF Status </h2>
-<ul>
- <li>Paperwork complete! JSF devs are now committers (3 from Oracle, one from Exadel)!
- <li>Planning update: Talking to other companies interested in project,
- Website milestone being updated, Exadel will not be making a code contribution
- (starting from scratch).
-</ul>
-
-<h2>Action Items</h2>
-<ul>
- <li>[TW] Get platform dates and drive process of setting 2006 WTP milestone dates (help up on planning info from platform).
- <li>[TW] Work with Board on charter modification vote (October call).
-</ul>
-
-<small>Minutes taken by Tim Wagner, September 27, 2005</small>
-</tr>
-</tbody></table>
-</html>
diff --git a/development/pmc_call_notes/2005-10-04.html b/development/pmc_call_notes/2005-10-04.html
deleted file mode 100644
index a39ca50..0000000
--- a/development/pmc_call_notes/2005-10-04.html
+++ /dev/null
@@ -1,75 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for October 4, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - October 4, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- Attending:
- Tim Wagner [TW],
- Raghunathan Srinivasan [RS],
- David Williams [DW],
- Jochen Krause [JK]
-
-<!--PMC MEMBERS NOT PRESENT ON THIS CALL:
- Arthur Ryman [AR],
- Lawrence Mandel [LM],
- Christophe Ney [CN],
- Naci Dai [ND],
--->
-
-<h1>WTP PMC Minutes for October 4, 2005 Conference Call</h1>
-
-<h2>Single Component Decision [Chuck Bridgham] </h2>
-<ul>
- <li>Review/recap of multi-component approach and single-component architecture discussions.
- <li>Rationale for decision timing.
- <li>PMC voted to proceed with this plan.
-</ul>
-
-<h2>Requirements Update [JK] </h2>
-<ul>
- <li>Major bugs for tracking WST and JST API rollup are not complete; need to push component teams to
- keep up with this part of the development process.
- <li>Discussed compiler warnings; will attempt to make progress as part of normal process - if that
- fails, will consider adding this to 1.0 exit criteria.
-</ul>
-
-<h2>Architecture Update [DW] </h2>
-<ul>
- <li>API scanning tool update: Jeffrey still working on revising this tool (and also as the base for the 3rd party
- "API reliance" standalone tool).
- <li>Last week's meeting included an update from the platform PMC: tabbed properties and extensible navigator
- being considered; answer should be available in (platform) M3 timeframe. Proxy settings were rejected
- for the 3.2 timeframe due to resource constraints; unclear whether WTP has any resources who can handle
- the platform base submission.
- <li>Joining the train includes having a good capabilities story and requires attention from WTP on this point;
- Lawrence suggested as a possible resource (and not being on the call, was unable to dispute this claim).
-</ul>
-
-<h2>JSF Status </h2>
-<ul>
- <li>Milestone 1 planned for end of December - use cases covered by this milestone will be published on the web site
- by the end of this week.
- <li>Subsequent milestones will be coordinated with WTP 1.5 milestone dates.
-</ul>
-
-<h2>Action Items</h2>
-<ul>
- <li>[TW/AR] Work with Board on charter modification vote (October call) - still in flight.
- <li>[TW] Schedule Carl (SOA project lead) for upcoming PMC call.
-</ul>
-
-<small>Minutes taken by Tim Wagner, October 4, 2005</small>
-</tr>
-</tbody></table>
-</html>
diff --git a/development/pmc_call_notes/2005-10-11.html b/development/pmc_call_notes/2005-10-11.html
deleted file mode 100644
index c9c8fb4..0000000
--- a/development/pmc_call_notes/2005-10-11.html
+++ /dev/null
@@ -1,103 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for October 11, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - October 11, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- Attending:
- Tim Wagner [TW],
- Lawrence Mandel [LM],
- Christophe Ney [CN],
- Arthur Ryman [AR],
- Raghunathan Srinivasan [RS],
- Jochen Krause [JK]
- David Williams [DW],
-
-<!--PMC MEMBERS NOT PRESENT ON THIS CALL:
- Naci Dai [ND],
--->
-
-<h1>WTP PMC Minutes for October 11, 2005 Conference Call</h1>
-
-<h2>Community Update [LM] </h2>
-<ul>
- <li>Two articles published last week, several blog postings
- <li>Lawrence has an OOPSLA presentation coming up next week; several other
- presentations coming up (BEAWorld, Colorado Software Summit)
- <li>"PRO JST" (Chris Judd) on bookshelves now
- <li>EclipseCon - two tutorial submissions (Naci/Arthur/Lawrence) and Gorkem (server tools);
- also checking with David on SSE editor creation.
- For presentations, we have JSF planned (Raghu), an overview (Arthur), and one or more
- detailed topics (Web Services?).
- <li>Capabilities: Lawrence will own this for 1.5.
-</ul>
-
-<h2>Procedural </h2>
-<ul>
- <li>Carl Trieloff invite sent - will hope to discuss areas of overlap next week on this call
- <li>Charter revision
- <li>Jeffrey's request for a "test build" against 3.2 platform - will defer this until
- later
-</ul>
-
-<h2>Requirements Update [JK] </h2>
-<ul>
- <li>Major bugs for tracking WST and JST API rollup: still outstanding
- <li>Making progress on compiler warnings - will continue to work on this with goal of reaching
- zero by 1.0 release.
- <li>[AR] Now generating web pages from Bugzilla. Currently requires a build; Arthur investigating
- PHP as solution for running and styling query during page fetch. Requires minor tweak
- in PHP settings from Eclipse webmaster.
-</ul>
-
-<h2>Architecture Update [DW] </h2>
-<ul>
- <li>Features/dependencies document updated - see email thread and spec
- <li>API scanning tool and "reliance" tools update: Will revive tool against current
- component.xml files; also need to update the component files themselves for accuracy.
- (There is also a project going forward with the platform to investigate inline
- (source) annotations to replace component.xml.) Will look to work on reliance tool
- immediately post 1.0.
-<!--
- <li>Last week's meeting included an update from the platform PMC: tabbed properties and extensible navigator
- being considered; answer should be available in (platform) M3 timeframe. Proxy settings were rejected
- for the 3.2 timeframe due to resource constraints; unclear whether WTP has any resources who can handle
- the platform base submission.
--->
-</ul>
-
-<h2>JSF Status </h2>
-<ul>
- <li>Milestone 1 draft now public; looking for feedback.
- <li>Status call this afternoon, and open to everyone.
-</ul>
-
-<h2>Confirming 1.5 / 3.2 / "Zebra" DTP Migration Plan</h2>
-<ul>
- <li>Current WTP plan is to move all data tools permanently into DTP in the 1.5 timeframe.
- <li>Will request "contract" from DTP to provide our current data tools back to us,
- modulo package renaming, in the "Zebra" release.
- <li>Should do a scheduling checkup in early January on execution of this plan.
-</ul>
-
-<h2>Action Items</h2>
-<ul>
- <li>[TW] Submit revised charter mods to Board.
- <li>[TW] Follow up with Carl's invite to next week's meeting.
- <li>[TW] Follow up with John Graham on DTP issues (see above) - look for invite (not Th).
-</ul>
-
-<small>Minutes taken by Tim Wagner, October 11, 2005</small>
-</tr>
-</tbody></table>
-</html>
diff --git a/development/pmc_call_notes/2005-10-18.html b/development/pmc_call_notes/2005-10-18.html
deleted file mode 100644
index 5848a33..0000000
--- a/development/pmc_call_notes/2005-10-18.html
+++ /dev/null
@@ -1,100 +0,0 @@
-<html>
-<head>
-<title>WTP PMC Minutes for October 18, 2005 Conference Call</title>
-</head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
- <font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - October 18, 2005</font></b></td>
-
- </tr>
- </tbody></table>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody><tr>
- <td>
- Attending:
- Tim Wagner [TW],
- Jochen Krause [JK]
- Raghunathan Srinivasan [RS],
- Lawrence Mandel [LM],
- David Williams [DW],
- Arthur Ryman [AR],
-
-<!--PMC MEMBERS NOT PRESENT ON THIS CALL:
- Naci Dai [ND],
-
- Christophe Ney [CN],
--->
-
-<h1>WTP PMC Minutes for October 18, 2005 Conference Call</h1>
-
-<h2>Community Update [LM] </h2>
-<ul>
- <li>OOPSLA report: Lawrence at conference; several Eclipse-related events still to come
- <li>CASCON: Web Services and WTP tutorials and talk (double session), demo still to come
- at WTP booth
- <li>Jochen representing WTP at JavaPolis (plug-in event, "IDE shootout" discussion)
- <li>EclipseCon submission summary:
- <ul>
- <li>Tutorial: Implementing the Web Tools Server SPI (Marshall)
- <li>Tutorial: Overview tutorial (Naci/Arthur/Lawrence)
- <li>Tutorial: Extending Web Tools for your Server (Gorkem)
- <li>Tutorial: Extending Web Tools through Project Facets (Konstantin)
- <li>Tutorial: Extending SSE (David - TBD)
- <li>TALK: JSF (Oracle)
- <li>TALK: Extending Web Tools through Project Facets (Konstantin)
- <li>TALK: Overview (Arthur)
- <li>Other talk ideas: adopter/API overview, SSE, Web Services
- <li>PMC will advocate the WTP overview tutorial for our guaranteed tutorial slot;
- more talk abstracts needed (and slot selection TBD)
- </ul>
- <li>Usage study (Findlater, UBC) recruiting participants for Eclipse and WTP interaction
-</ul>
-
-<h2>Procedural </h2>
-<ul>
- <li>Carl Trieloff planning to join us next week (conflict for this morning's call).
- <li>Time to start working on the IP log / license tracking again. I've started this with
- Bjorn, but will need to pull in others.
- <li>Followup from last week's AI: mail sent to John Graham to clarify DTP migration plan
- (and support in "Comet" time frame)
- <li>Charter mods will be presented at tomorrow's Board call
-</ul>
-
-<h2>Requirements Update </h2>
-<ul>
- <li>Bugzilla-based milestone plans are now live on our website
- <li>Still TBD: enabling dynamic report generation to eliminate build step (via PHP - needs to be enabled)
-</ul>
-
-<h2>1.0 Planning </h2>
-<ul>
- <li>Plugin version numbers need to be bumped to 1.0.
- <li>I-builds are being produced late; will discuss during the status meeting this week.
- <li>New feature breakdown should complete for WST next week.
-</ul>
-
-<h2>1.5 Planning </h2>
-<ul>
- <li>Will attempt build on 3.2 M3 after our M9.
- <li>Will plan to join train officially with M4 after our 12/16 ship (should be easy if M3 build
- has already succeeded).
- <li>Will return to requirements and milestone planning when we hit rampdown.
-</ul>
-
-<h2>JSF Status </h2>
-<ul>
- <li>Sybase interested in joining project, currently working on internal approval.
-</ul>
-
-<h2>Action Items</h2>
-<ul>
- <li>[TW] Track charter mods with Board (Wed call).
-</ul>
-
-<small>Minutes taken by Tim Wagner, October 18, 2005</small>
-</tr>
-</tbody></table>
-</html>
diff --git a/development/project_set_instructions/authenticate.gif b/development/project_set_instructions/authenticate.gif
deleted file mode 100644
index d3fff08..0000000
--- a/development/project_set_instructions/authenticate.gif
+++ /dev/null
Binary files differ
diff --git a/development/project_set_instructions/book.css b/development/project_set_instructions/book.css
deleted file mode 100644
index 139eb28..0000000
--- a/development/project_set_instructions/book.css
+++ /dev/null
Binary files differ
diff --git a/development/project_set_instructions/checkout.gif b/development/project_set_instructions/checkout.gif
deleted file mode 100644
index 57c03c4..0000000
--- a/development/project_set_instructions/checkout.gif
+++ /dev/null
Binary files differ
diff --git a/development/project_set_instructions/import_project_set.html b/development/project_set_instructions/import_project_set.html
deleted file mode 100644
index 0b406f7..0000000
--- a/development/project_set_instructions/import_project_set.html
+++ /dev/null
@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="book.css" charset="ISO-8859-1" type="text/css">
-<title>Import Project Set wizard</title>
-</head>
-<body bgcolor="#ffffff">
-<h3>Import team project set wizard</h3>
-<p class="Para"> The Import team project set wizard can be used to import a set of projects shared in the repository into the Workbench.</p>
-<ol>
- <li>
- <p class="Para"> Select <b>File</b> <b>Import</b> from menu.</p>
- </li>
- <li>
- <p class="Para"> In the Import wizard, select <b>Team Project Set</b>, then click
- <b>Next</b>.</p>
- <p class="Para"> <img src="import_team_project_set.gif" alt="Import Wizard. A wizard that imports a team project set." border="0" height="550" width="470"></p>
- </li>
- <li>
- <p class="Para"> In the <b>File name</b> field, type or browse to select
- the team project set file (.psf), then click <b>Finish</b>.</p>
- <p class="Para"> <img src="select_team_project_set_file.gif" alt="Import Wizard. From directory field." border="0" height="550" width="470"></p>
- </li>
- <li>
- <p class="Para">The web tools project CVS server may prompt you to enter your password.</p>
- <p class="Para">Enter the password, then click <b>OK</b></p>
- <p class="Para"><img src="authenticate.gif" alt="Enter CVS password." border="0"></p>
- </li>
- <li>
- <p class="Para">The Team Project Set Wizard will checkout the Web Tools Projects into your workspace</p>
- <p class="Para"> <img src="checkout.gif" alt="Import Team Project Set Wizard. Checkout files from CVS." border="0"></p>
- </li>
- <li>
- <p class="Para"> When the wizard completes the project import, the imported projects will show in the Navigator/Package Explorer.</p>
- <p class="Para"> <img src="package_explorer.gif" alt="Import Team Project Set Completed. Package explorer." border="0"></p>
- </li>
-</ol>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/development/project_set_instructions/import_team_project_set.gif b/development/project_set_instructions/import_team_project_set.gif
deleted file mode 100644
index bff7f06..0000000
--- a/development/project_set_instructions/import_team_project_set.gif
+++ /dev/null
Binary files differ
diff --git a/development/project_set_instructions/package_explorer.gif b/development/project_set_instructions/package_explorer.gif
deleted file mode 100644
index 1775d6d..0000000
--- a/development/project_set_instructions/package_explorer.gif
+++ /dev/null
Binary files differ
diff --git a/development/project_set_instructions/select_team_project_set_file.gif b/development/project_set_instructions/select_team_project_set_file.gif
deleted file mode 100644
index f6f84ff..0000000
--- a/development/project_set_instructions/select_team_project_set_file.gif
+++ /dev/null
Binary files differ
diff --git a/development/proposals/Component_Feature_Proposal.html b/development/proposals/Component_Feature_Proposal.html
deleted file mode 100644
index f6253b2..0000000
--- a/development/proposals/Component_Feature_Proposal.html
+++ /dev/null
@@ -1,10 +0,0 @@
-<html>
-
-<head>
-<title>Features Framework Specification</title>
-<meta http-equiv="refresh" content="5;url=http://www.eclipse.org/webtools/development/proposals/Features%20Framework%20Specification.htm">
-</head>
-
-<body>
-The document you are trying to access has moved. If you browser does not automatically redirect, use this <a href="http://www.eclipse.org/webtools/development/proposals/Features%20Framework%20Specification.htm">link</a>.
-</body>
\ No newline at end of file
diff --git a/development/proposals/Features Framework Specification.htm b/development/proposals/Features Framework Specification.htm
deleted file mode 100644
index ba830d7..0000000
--- a/development/proposals/Features Framework Specification.htm
+++ /dev/null
@@ -1,451 +0,0 @@
-<html>
-<head><title>Features Framework Specification</title></head>
-<body>
-<font face="Arial" size="-1">
-
-<center>
-
- <font size="+0"><b>Features Framework Specification</b></font><br/><br/>
-
- <b><i>initial design by</i></b><br/>
- Ted Bashor [<a href="mailto:tbashor@bea.com"><i>tbashor@bea.com</i></a>],
- Chuck Bridgham [<a href="mailto:cbridgha@us.ibm.com"><i>cbridgha@us.ibm.com</i></a>],<br/>
- Tim Deboer [<a href="mailto:deboer@ca.ibm.com"><i>deboer@ca.ibm.com</i></a>],
- Michael Elder [<a href="mailto:mdelder@us.ibm.com"><i>mdelder@us.ibm.com</i></a>],<br/>
- Konstantin Komissarchik [<a href="mailto:kosta@bea.com"><i>kosta@bea.com</i></a>],
- Jason Sholl [<a href="mailto:jsholl@us.ibm.com"><i>jsholl@us.ibm.com</i></a>],<br/>
- Thomas Yip [<a href="mailto:tyip@bea.com"><i>tyip@bea.com</i></a>],
- Elson Yuen [<a href="mailto:eyuen@ca.ibm.com"><i>eyuen@ca.ibm.com</i></a>]
- <br/><br/>
-
- <b><i>written by</i></b><br/>
- Konstantin Komissarchik [<a href="mailto:kosta@bea.com"><i>kosta@bea.com</i></a>]
- <br/></br/>
-
- <b><i>revision date</i></b><br/>
- 2005-08-29
- <br/><br/>
-
-</center>
-
-<b>Summary</b>
-<hr/>
-
-<p>This framework provides a common mechanism and ui for adding and
-removing units of functionality from a project. A unit of functionality (or a
-"feature") is a marker that can be used, for instance, to enable
-feature-specific UI. A feature also has a great deal of flexibility to
-manipulate the project when it's being installed. It can add natures, builders,
-and classpath entries. It can also lay down feature-specific metadata files
-and other resources into the project directory.</p>
-
-<b>Feature vs. Nature</b>
-<hr/>
-
-<p>A feature is similar to a nature, but it's scope is much wider.</p>
-
-<ol>
- <li>
- Features are designed to be added and removed by the end user, while natures are an
- implementation detail. A feature can, if necessary, add a nature to the project as
- part of it's installation logic. Not all features will use natures.
- </li>
- <li>
- Features can be versioned. Feature A can declare that it depends on feature B version
- 1.2 or newer. Upgrade handling can be associated with moving from version 1.2 to 1.3.
- </li>
- <li>
- Features support a richer constraint expression language than natures.
- </i>
- <li>
- It would be difficult to add additional lifecycle event methods to the
- IProjectNature interface, because doing so will break all of the existing
- implementations. The feature framework, on the other hand, uses a delegate
- mechanism where every event method is represented by a separate interface.
- This makes it very easy to add support for new lifecycle events without
- effecting existing code. See the <a href="#delegates">Delegates</a>
- section for more information.
- </li>
- <li>
- The IProjectNature's configure and deconfigure methods do not take any
- parameters. This makes them of limited use in situations where input from
- UI needs to be taken into account and has resulted in a situation where
- most of the necessary work happens in the wizards. This makes it quite
- difficult for someone to say add java functionality to a project at the
- API level. The features framework addresses this problem by allowing the
- install and uninstall delegates to take a configuration object. The
- configuration object can either be filled out by the UI or someone working
- at the API level.
- </li>
-</ol>
-
-<b>Version Support</b>
-<hr/>
-
-<p>The framework supports defining multiple versions of the same feature. This
-makes it possible to, for example, express that feature A depends on version
-1.3 or newer of feature B. There are no limitations placed on the format of the
-version string. The feature author is responsible for providing an
-implementation of a version comparator. If one is not provided, a default
-implementation will be used.</p>
-
-<b>Constraints</b>
-<hr/>
-
-<p>Each feature version can declaratively specify what constraints must be
-satisfied before the feature can be installed. Four operators are supported:
-and, or, requires, and oneof.<p>
-
-<font size="+0"><pre>
-<requires feature="<i>string</i>" version="<i>string</i>" allow-newer="<i>boolean</i>" soft="<i>boolean</i>"/>
-</pre></font>
-
-<p>The <i>feature</i> and <i>version</i> attributes are required. The
-<i>allow-newer</i> and <i>soft</i> attributes are optional and both are
-defaulted to <i>false</i>. The <i>soft</i> attribute is used to indicate that
-the feature is allowed to be installed even if the required feature is missing,
-but if the required feature is selected, this feature should be installed after
-it.</p>
-
-<font size="+0"><pre>
-<oneof set="<i>string</i>"/>
-</pre></font>
-
-<p>The <i>set</i> attribute is required. This constraint is used to indicate
-that the feature conflicts with members of the specified set.</p>
-
-<font size="+0"><pre>
-<and>...</and>, <or>...</or>
-</pre></font>
-
-<p>Both of these operators work with two or more sub-constraints.</p>
-
-<table cellpadding="10"><tr><td bgcolor="#C0C0C0">
-<font size="-1" face="Arial"><p><b>Example:</b></p></font>
-<font size="+0"><pre>
-<extension point="...core.features">
- <feature-version id="web" version="1.0">
- ...
- <constraint>
- <and>
- <requires feature="java" version="5.0"/>
- <requires feature="flexible.project" version="1.0"/>
- <oneof set="modules"/>
- </and>
- </constraint>
- ...
- </feature-version>
-</extension>
-</pre></font>
-</td></tr></table>
-
-<p><b><a name="delegates">Delegates</a></b><hr/></p>
-
-<p>Each feature version can implement any number of the supported delegate
-interfaces to be given a chance to do some work during some event in a feature's
-life cycle. Six delegates are supported: <i>install</i>, <i>uninstall</i>,
-<i>update</i>, <i>upgrade</i>, <i>activate</i>, and <i>deactivate</i>. Most, if
-not all, features will implement at least the <i>install</i> delegate.</p>
-
-<p><i>install</i> - Invoked when the feature is being added to a project. This
-can happen either during project creation or when the user chooses to add a
-feature to an existing project. This delegate will be invoked after all the
-features that this feature depends on are installed. This delegate can take
-input from UI through a config object. See the <a href="#wizard">Wizard
-Framework</a> section for more information.</p>
-
-<p><i>uninstall</i> - Invoked when the feature is being removed from a project.
-This delegate can take input from UI through a config object. See the
-<a href="#wizard">Wizard Framework</a> section for more information.</p>
-
-<p><i>update</i> - Invoked on an installed feature when there is significant
-change to some of the feature's dependencies. Some examples of a signficiant
-change include: installing or installing a soft dependency, upgrading of a
-dependent feature, and installing or uninstalling a hard dependency where an
-"OR" constraint is involved.
-</p>
-
-<p><i>upgrade</i> - Invoked when the user changes the version of a feature
-that's already installed.</p>
-
-<p><i>activate</i> - Invoked when a project containing this feature is loaded.
-The feature's author should use caution when taking advantage of this delegate,
-since this will cause the plugin that contains the delegate to be loaded every
-time any project containing this feature is loaded.</p>
-
-<p><i>deactivate</i> - Invoked when a project containing this feature is closed.
-The feature's author should use caution when taking advantage of this delegate,
-since this will cause the plugin that contains the delegate to be loaded every
-time any project containing this feature is closed.</p>
-
-<table cellpadding="10"><tr><td bgcolor="#C0C0C0">
-<font size="-1" face="Arial"><p><b>Example:</b></p></font>
-<font size="+0"><pre>
-<extension point="...core.features">
- <feature-version id="web" version="1.0">
- ...
- <delegate type="install" class="...WebFeatureInstallDelegate"/>
- <delegate type="uninstall" class="...WebFeatureUninstallDelegate"/>
- ...
- </feature-version>
-</extension>
-</pre></font>
-</td></tr></table>
-
-<p><b>Categories</b><hr/></p>
-
-<p>A category is a grouping of several related features that would frequently
-be added to a project as a set. Categories allow the feature author to provide a
-fine-grained feature breakdown for an expert user wihout complicating matters
-for a novice. A feature can belong to at most one category.</p>
-
-<p><b>Presets</b><hr/></p>
-
-<p>A preset is a user convenience mechanism for quickly selecting a set of
-features. Presets are intended as a quick starting point for doing a certain
-type of development. For instance a server vendor might create a preset that can
-be used when developing exclusively for that server platform or there might
-be presets for doing webservice development vs. web ui development. After
-applying a preset, the user can further tweak the set of selected features and
-change their configurations.</p>
-
-<p>A user can also define custom presets, which are stored in workspace
-metadata. Once a custom preset is created it can be used just like a preset
-defined through the extension point.</p>
-
-<p>Presets would manifest in the UI as a drop-down above the feature selection
-panel. The list of presets will be filtered to only show presets that would
-not conflict with fixed features. A preset is allowed to change the version of
-a fixed feature, but not deselect it.</p>
-
-<table cellpadding="10"><tr><td bgcolor="#C0C0C0">
-<font size="-1" face="Arial"><p><b>Example:</b></p></font>
-<font size="+0"><pre>
-<extension point="...core.features">
- ...
- <preset id="wls.web.preset">
- <label>WebLogic Web App</label>
- <feature id="java" version="5.0"/>
- <feature id="wtp.framework" version="1.0"/>
- <feature id="web" version="1.0"/>
- <feature id="wls.web" version="9.0"
- <feature id="struts" version="1.1"/>
- <feature id="wls.struts" version="9.0"/>
- </preset>
- ...
-</extension>
-</pre></font>
-</td></tr></table>
-
-<p><b>Runtime Modeling</b><hr/></p>
-
-<p>A runtime is a container or an environment that projects will execute within.
-Sun Java VM and Apache Tomcat are both examples of a runtime. Some features can
-only run on specific types of runtimes. For instance, a Web Module feature
-cannot run on a base Sun Java VM runtime. It needs a J2EE server such as Apache
-Tomcat. A vendor-specific feature might only run on that vendor's runtime.</p>
-
-<p>The framework provides a way to declare runtime types and to map features to
-them. The runtimes are versioned and features can be mapped to either a specific
-version, specific version or newer, or all versions. It is not necessary to map
-all features to all runtimes that they will run on. If feature x depends on
-feature y and feature x will run on all runtimes that y will run on, it is not
-necessary to provide mappings for x. In fact, a feature will run on all runtimes
-unless it is explicitly restricted by runtime mappings or features it depends
-on.</p>
-
-<p>If the set of features that a runtime supports varries based on it's
-configuration, the "runtime extension" concept can help in modeling these
-situations. A feature can be mapped to either a runtime or a runtime extension.
-A runtime can have any number of extensions.</p>
-
-<table cellpadding="10"><tr><td bgcolor="#C0C0C0">
-<font size="-1" face="Arial"><p><b>Example:</b></p></font>
-<font size="+0"><pre>
-<extension point="...core.runtime">
- ...
- <runtime id="sun.vm" version="1.4"/>
- <runtime id="sun.vm" version="5.0"/>
- <runtime id="apache.tomcat" version="4.0"/>
- <runtime id="apache.tomcat" version="5.0"/>
- <runtime id="jboss" version="1.0"/>
- <runtime-extension id="jboss.ejb.extension" version="1.0"/>
- ...
- <runtime-mapping>
- <feature id="java" version="1.4"/>
- <runtime id="sun.vm" version="1.4" allow-newer="true"/>
- </runtime-mapping>
- <runtime-mapping>
- <feature id="java" version="5.0"/>
- <runtime id="sun.vm" version="5.0" allow-newer="true"/>
- </runtime-mapping>
- <runtime-mapping>
- <feature id="web" version="1.0"/>
- <runtime id="apache.tomcat" version="4.0" allow-newer="true"/>
- </runtime-mapping>
- <runtime-mapping>
- <feature id="web" version="1.0"/>
- <runtime id="jboss" version="1.0"/>
- </runtime-mapping>
- <runtime-mapping>
- <feature id="ejb" version="1.0"/>
- <runtime-extension id="jboss.ejb.extension" version="1.0"/>
- </runtime-mapping>
- ...
-</extension>
-</pre></font>
-</td></tr></table>
-
-<p>A runtime instance is formed by taking a particular version of the runtime
-type and combining it with any applicable extensions. A runtime instance can
-also "build-on" another runtime instance. For example, one can create "My JBoss"
-runtime that's an instance of "jboss v.1.0" with "jboss.ejb.extension v.1.0"
-installed and that builds on "My JVM Install" runtime instance. The framework
-provides a way to register runtime instance, but tooling is left to runtime
-vendors.</p>
-
-<p>A user can choose to associate the project with a particular runtime at the
-time of creation. If the user chooses to do that, the selected runtime instance
-is available to feature wizard pages and the delegates. The features can adjust
-their behavior based on the selected runtime. One common use of this is for
-classpath setup. A feature can ask the runtime if it can provide classpath
-entries for it. If the runtime is unable to provide classpath entries for a
-particular feature, or if no runtime is selected, the feature is responsible for
-setting up the classpath on it's own. This might mean gathering additional
-input from the user. When the user changes the runtime associated with a
-project, all of the installed features are notified so that they can adjust
-the classpath accordingly.</p>
-
-<b>Fixed Features</b>
-<hr/>
-
-<p>While it would be possible to allow the user to pick from the complete list
-of available features when creating a project, the generality of that would
-likely lead to user confusion. As such, certain features can be "fixed" at
-project creation to define a "project type". Any features that conflict with
-the fixed features are not displayed to the user. The user cannot de-select a
-fixed feature, but can change it's version.</p>
-
-<b><a name="wizard">Wizard Framework</a></b>
-<hr/>
-
-<p>Part of the features framework is a wizard that provides a common way to add
-and remove features. The wizard consists of a feature selection page followed
-by pages associated with actions that the user takes in the feature selection
-page (such as install feature or uninstall feature). The feature action pages are
-displayed in dependency order. The wizard can either be used stand-alone on an
-existing project or as part of a project creation wizard. In fact the framework
-provides an abstract project creation wizard that prepends a page that allows
-the user to specify project name and location. The abstract project creation
-wizard is subclassed to specify the set of fixed features and which preset to
-start with.</p>
-
-<p>Feature authors can register pages and the config objects through the
-provided extension point. The config object will be instantiated and passed to
-all of the pages. The same config object will then be passed to the delegate
-implementing the action. The framework places only one restriction on the config
-object: it has to have a zero-argument constructor.</p>
-
-<p>Wizard pages associated with particular feature can peek at the config of the
-other features currently being operated on. That's done through the wizard
-context that's available to all of the pages.</p>
-
-<table cellpadding="10"><tr><td bgcolor="#C0C0C0">
-<font size="-1" face="Arial"><p><b>Example:</b></p></font>
-<font size="+0"><pre>
-<extension point="...ui.wizard">
- ...
- <wizard-pages feature="web" version="1.0">
- <install>
- <config class="...WebFeatureInstallConfig"/>
- <page class="...WebFeatureInstallPage1"/>
- <page class="...WebFeatureInstallPage2"/>
- </install>
- <wizard-pages>
- ...
-</extension>
-</pre></font>
-</td></tr></table>
-
-<p/>
-
-<b>Open Issues</b>
-<hr/>
-
-<ol>
- <li>
- Should this be kept inside WTP or contributed to eclipse core?
- </li>
- <li>
- Are features a property of a project or of a component?
- </li>
-</ol>
-
-<b>Apendix A: Extension Points</b>
-<hr/>
-
-<font size="+0"><pre>
-<extension point="...core.features">
- <feature id=""> <i>(0 or more)</i>
- <label>...</label>
- <description>...</description> <i>(optional)</i>
- <icon>...</icon> <i>(optional)</i>
- <version-comparator class=""/> <i>(optional)</i>
- <category>...</category> <i>(optional)</i>
- </feature>
- <feature-version feature="" version=""> <i>(0 or more)</i>
- <constraint> <i>(optional)</i>
- <i>[choice]</i>
- <and>
- ...
- </and>
- <or>
- ...
- </or>
- <requires feature="" version="" allow-newer="" soft=""/>
- <one-of set=""/>
- <i>[/choice]</i>
- </constraint>
- <set-member id=""/> <i>(0 or more)</i>
- <delegate type="" class=""/> <i>(0 or more)</i>
- </feature-version>
- <category name=""> <i>(0 or more)</i>
- <label>...</label>
- <description>...</description> <i>(optional)</i>
- <icon>...</icon> <i>(optional)</i>
- </category>
- <preset id=""> <i>(0 or more)</i>
- <label>...</label>
- <feature id="" version=""/> <i>(1 or more)</i>
- </preset>
-</extension>
-
-<extension point="...core.runtime">
- <runtime id="" version=""/> <i>(0 or more)</i>
- <runtime-extension id="" version=""/> <i>(0 or more)</i>
- <runtime-mapping> <i>(0 or more)</i>
- <feature id="" version=""/>
- <i>[choice]</i>
- <runtime id="" version="" allow-newer=""/>
- <runtime-extension id="" version="" allow-newer=""/>
- <i>[/choice]</i>
- </runtime-mapping>
-</extension>
-
-<extension point="...ui.wizard">
- <wizard-pages feature="" version=""> <i>(1 or more)</i>
- <install> <i>(optional)</i>
- <config class=""/>
- <page class=""/> <i>(1 or more)</i>
- </install>
- <uninstall> <i>(optional)</i>
- <config class=""/>
- <page class=""/> <i>(1 or more)</i>
- </uninstall>
- <wizard-pages>
-</extension>
-</pre></font>
-
-</font>
-</body>
-</html>
\ No newline at end of file
diff --git a/development/proposals/FlexibleProjectConcepts.html b/development/proposals/FlexibleProjectConcepts.html
deleted file mode 100644
index e2049d5..0000000
--- a/development/proposals/FlexibleProjectConcepts.html
+++ /dev/null
@@ -1,499 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../webtools/wtp.css" type="text/css">
-<title>flexible project concepts</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">jst j2ee</font>
-<br>
-<font class="indexsub">flexible project concepts</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><a name="top"></a></td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Introduction</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The goal of this document is to share some initial ideas that will help
- shape the Eclipse Web Tools (WTP) J2EE project application model and its
- implementation. We initially planned to pursue this effort as a formal
- requirements gathering and documentation process. But once we began
- analyzing the problem space it was clear that there is no common J2EE
- project model used within the J2EE development community. Stated another
- way, all current J2EE project models are ad hoc. At most, the J2EE
- application deployment model, defined in the J2EE specification, is the
- only common reference structure and it only specifies to the runtime
- archive form of valid J2EE applications. With that as our starting point,
- we concluded that rather than attempt to draft a conventional
- requirements document, it would be more beneficial to initiate a
- discussion of ideas among the key WTP participants that can serve as the
- catalyst for a J2EE application project requirements and subsequent
- architecture and implementation.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The contents of this document are representative of the future direction.
- However, some of this functionality described is representative of our
- current state.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- There are several use cases described in the Use Case Scenario Powerpoint
- Slides. Where relevant, the relationship of the concepts described in
- this document and the scenario slides are highlighted.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- A
- <b>project</b>
- is a type of resource which groups resources into buildable, reusable
- units - Java project resources are defined in terms of Java elements such
- as package fragments, types, methods and fields.
-
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>The scenario slides highlight the following types of use cases:</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>
-
-<p>Simple Project (contains one module and one Deploy Scheme)</p>
-
-</li>
-
-<li>
-
-<p>
- Simple Container Project (contains one or more modules, possibly
- multiple Deploy Schemes)
- </p>
-
-</li>
-
-<li>
-
-<p>
- Application Project (application and modules contained in the
- same Simple Container project)
- </p>
-
-</li>
-
-<li>
-
-<p>
- Application Project Variation (application in one Simple
- Container Project modules may be in other Simple Container
- projects)
- </p>
-
-</li>
-
-<li>
-
-<p>Composed Modules (stay tuned (bum bum bum))</p>
-
-</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The J2EE module definitions build on the use case concepts. As discussed
- in the use cases, a module is a collection of files in a project.
- However, for the remainder of this document, the term abstract module
- will refer to an intangible concept (to be defined more explicitly later
- on). The abstract module concept represents the abstraction of a physical
- module in terms that can be understood programmatically. The specifics of
- how these projects are constructed is not important to the discussion of
- modules.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- A
- <b>resource</b>
- is a abstraction which contains model elements. A
- <b>resource set</b>
- is a collection of related persistent resources. The resource set manages
- the collection of resources and produces notifications for changes to
- that collection. A
- <b>project resource set</b>
- is a resource set defined at the project level, meaning the project
- resource set manages the collection of resources for that project. There
- is only one project resource set per project, ensuring each resource is
- only loaded once within the workspace. Each resource contained in the
- project resource set has a
- <b>relative URI</b>
- , which is a partial URI with respect to or relative to the project. A
- <b>WTP project resource set</b>
- is defined in terms of module resources, which contain abstract module
- models (defined later).
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- A
- <b>URI converter</b>
- may be configured on a resource set to normalize relative URIs for
- comparison and to monitor access to the backing store. The resource set
- will use this converter to produce an input or output stream for a URI,
- during serialization or deserialization of a resource, and during a load
- to check for a resource URI match to one of its known resources.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- An
- <b>abstract module</b>
- is a logical, abstracted, first-class model of a deployable artifact. The
- initial assumption will be that abstract modules must be contained within
- one project and thus use one project resource set. However, a project and
- the associated project resource set may contain more than one abstract
- module.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- A
- <b>J2EE abstract module</b>
- is a collection of one or more components, organized by a standard
- layout, targeted for the same container upon deployment, and which can be
- archived conforming to the J2EE specification. Modules always contain a
- set of files, but all J2EE modules also contain specialized files called
- <b>deployment descriptors</b>
- . Deployment descriptors describe the contents of deployment units and
- configure components and applications to their environment. They also
- externalize the relationships between components, so those relationships
- can be managed without writing or changing program code. There are five
- core types of J2EE deployment descriptors, each of which corresponds to a
- type of J2EE deployment unit:
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>
-
-<p>Application</p>
-
-</li>
-
-<li>
-
-<p>Application Client</p>
-
-</li>
-
-<li>
-
-<p>EJB</p>
-
-</li>
-
-<li>
-
-<p>Web</p>
-
-</li>
-
-<li>
-
-<p>Resource Adapter for Java Connector</p>
-
-</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Vendor-specific deployment descriptors may be defined for different
- Enterprise application containers to provide additional information.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Each deployment descriptor describes a set of contained objects which are
- represented through
- <b>module models</b>
- . The root abstract module model object for the deployment descriptor is
- the associated J2EE abstract module type object.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>
-
-<p>
- The
- <b>Application</b>
- is the root object for an EAR module.
- </p>
-
-</li>
-
-<li>
-
-<p>
- The
- <b>EJBJar</b>
- is the root object for an EJB module.
- </p>
-
-</li>
-
-<li>
-
-<p>
- The
- <b>WebApp</b>
- is the root object for a Web module
- </p>
-
-</li>
-
-<li>
-
-<p>
- The
- <b>ApplicationClient</b>
- is the root object for an Application Client module.
- </p>
-
-</li>
-
-<li>
-
-<p>
- The
- <b>Connector</b>
- is the root object for a JCA Connector module.
- </p>
-
-</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Before proceeding, it should be noted that there are two distinct
- metamodels in the tooling environment. First, J2EE abstract models allow
- framework clients to understand the J2EE-specific deployment descriptors
- and their third-party extensions. The tooling frameworks are built
- primarily to modify and update these models. There is also a separate
- model for understanding how modules and their contained resources can be
- constructed for deploying to server environments, which is referred to as
- <b>ModuleCore</b>
- .
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<b>ModuleCore</b>
- can be used to acquire, create, and destroy
- <b>abstract module contexts</b>
- . An
- <b>abstract module context</b>
- is used to manage multiple abstract modules per project. In the first
- implementation, an abstract module context will not span multiple
- projects. Each abstract module context identifies a unique custom defined
- abstract module using a module handle (see Server Tooling), server target
- type (see Server Tooling), an edit model (to be discussed later).
-
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<table cellspacing="10" cellpadding="10">
-
-<tr>
-
-<td>
-
-<p>
-
-
-</p>
-
-</td>
-
-</tr>
-
-<tr>
-
-<td>
-
-<p>
-
-<i>
- Figure 1: Overview of ModuleCore, ModuleContext, and
- Abstract Module relationships.
- </i>
-
-</p>
-
-</td>
-
-</tr>
-
-</table>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Meanwhile,
- <b>edit models</b>
- provide a shared, reference counted, read/write controlled amalgamation
- of a related set of resources. Primarily, resources and Java working
- copies are wrapped by an Edit Model in order to represent a coherent and
- consistent view for clients. Managing these resources as a group, allows
- changes to be committed or rolled back as a consistent unit of work.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Typically, specialized types of edit models have aforementioned knowledge
- of their expected or required resources for a given type of abstracted
- module. Not surprisingly, clients may wish to add capabilities and
- additional known resources to existing edit model. The edit model will
- attempt to load these resources so that they may be managed with the
- existing, known resources.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Edit models are created via an extension which defines the
- <b>edit model factory</b>
- . The lifecycle of how edit models are created and destroyed will be
- covered in the API Concepts document.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Typically, J2EE components are built on a regular schedule (e.g. daily)
- and packaged as Enterprise Archives (EARs). Collaboration between teams
- and individual members is facilitated by these build artifacts which are
- used to back current development. These are referred to as
- <b>target EARs</b>
- . Developers set up their development environments so the components they
- are actively working on are loaded directly from a source repository and
- the other components are loaded from the Target EARs.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The use of target EARs is analogous to self-hosting in Eclipse. The idea
- is to only have abstract modules that are currently being developed in
- the workspace. All other dependencies will be loaded from a target EAR.
- Changing target EARs would simply be a matter of adjusting some abstract
- module property (just like PDE). Loading projects from the repository, or
- deleting them from the workspace would change where they were loaded from
- as well (also like PDE).
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Rather than using target EARs, EAR files may be extracted to a structure
- which represents its contained abstract modules. The remaining non-module
- jar archives are called
- <b>utility jars</b>
- . Utility jars are regular jars which the various abstract modules can
- depend on. Utility jars may exist as jar files within the EAR abstract
- module which is useful when a developer is not currently working on the
- contents of the utility jar. All abstract module archives must (utility
- jars have the option) be handled in separate abstract modules.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- An <b>extracted module</b> or <b>utility jar module</b> is simply a module containing
- the extracted contents of the archive. The benefit of using extracted
- modules is all the artifacts can be modified. This would be useful if a
- developer did not have access to the source repository. Typically,
- however, instead of using extracted modules, a developer would connect to
- a source repository. Jars within WARs can be extracted as modules within
- Eclipse projects (like utility jar modules) or can remain in the WAR in
- binary form.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-<i>Last updated 11/11/04</i>
-</p>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/development/proposals/FlexibleProjectConcepts.xml b/development/proposals/FlexibleProjectConcepts.xml
deleted file mode 100644
index d305905..0000000
--- a/development/proposals/FlexibleProjectConcepts.xml
+++ /dev/null
@@ -1,321 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?xml-stylesheet type="text/xsl" href="../../wtp.xsl"?>
-<html>
- <head>
- <meta
- name="root"
- content="../../.." />
- <title>flexible project concepts</title>
- </head>
-
- <body>
- <a name="top" />
-
- <h1>jst j2ee</h1>
-
- <h2>Introduction</h2>
- <p>
- The goal of this document is to share some initial ideas that will help
- shape the Eclipse Web Tools (WTP) J2EE project application model and its
- implementation. We initially planned to pursue this effort as a formal
- requirements gathering and documentation process. But once we began
- analyzing the problem space it was clear that there is no common J2EE
- project model used within the J2EE development community. Stated another
- way, all current J2EE project models are ad hoc. At most, the J2EE
- application deployment model, defined in the J2EE specification, is the
- only common reference structure and it only specifies to the runtime
- archive form of valid J2EE applications. With that as our starting point,
- we concluded that rather than attempt to draft a conventional
- requirements document, it would be more beneficial to initiate a
- discussion of ideas among the key WTP participants that can serve as the
- catalyst for a J2EE application project requirements and subsequent
- architecture and implementation.
- </p>
- <p>
- The contents of this document are representative of the future direction.
- However, some of this functionality described is representative of our
- current state.
- </p>
- <p>
- There are several use cases described in the Use Case Scenario Powerpoint
- Slides. Where relevant, the relationship of the concepts described in
- this document and the scenario slides are highlighted.
- </p>
- <p>
- A
- <b>project</b>
- is a type of resource which groups resources into buildable, reusable
- units - Java project resources are defined in terms of Java elements such
- as package fragments, types, methods and fields.
-
- </p>
- <p>The scenario slides highlight the following types of use cases:</p>
- <ul>
- <li>
- <p>Simple Project (contains one module and one Deploy Scheme)</p>
- </li>
- <li>
- <p>
- Simple Container Project (contains one or more modules, possibly
- multiple Deploy Schemes)
- </p>
- </li>
- <li>
- <p>
- Application Project (application and modules contained in the
- same Simple Container project)
- </p>
- </li>
- <li>
- <p>
- Application Project Variation (application in one Simple
- Container Project modules may be in other Simple Container
- projects)
- </p>
- </li>
- <li>
- <p>Composed Modules (stay tuned (bum bum bum))</p>
- </li>
- </ul>
- <p>
- The J2EE module definitions build on the use case concepts. As discussed
- in the use cases, a module is a collection of files in a project.
- However, for the remainder of this document, the term abstract module
- will refer to an intangible concept (to be defined more explicitly later
- on). The abstract module concept represents the abstraction of a physical
- module in terms that can be understood programmatically. The specifics of
- how these projects are constructed is not important to the discussion of
- modules.
- </p>
- <p>
- A
- <b>resource</b>
- is a abstraction which contains model elements. A
- <b>resource set</b>
- is a collection of related persistent resources. The resource set manages
- the collection of resources and produces notifications for changes to
- that collection. A
- <b>project resource set</b>
- is a resource set defined at the project level, meaning the project
- resource set manages the collection of resources for that project. There
- is only one project resource set per project, ensuring each resource is
- only loaded once within the workspace. Each resource contained in the
- project resource set has a
- <b>relative URI</b>
- , which is a partial URI with respect to or relative to the project. A
- <b>WTP project resource set</b>
- is defined in terms of module resources, which contain abstract module
- models (defined later).
- </p>
- <p>
- A
- <b>URI converter</b>
- may be configured on a resource set to normalize relative URIs for
- comparison and to monitor access to the backing store. The resource set
- will use this converter to produce an input or output stream for a URI,
- during serialization or deserialization of a resource, and during a load
- to check for a resource URI match to one of its known resources.
- </p>
- <p>
- An
- <b>abstract module</b>
- is a logical, abstracted, first-class model of a deployable artifact. The
- initial assumption will be that abstract modules must be contained within
- one project and thus use one project resource set. However, a project and
- the associated project resource set may contain more than one abstract
- module.
- </p>
- <p>
- A
- <b>J2EE abstract module</b>
- is a collection of one or more components, organized by a standard
- layout, targeted for the same container upon deployment, and which can be
- archived conforming to the J2EE specification. Modules always contain a
- set of files, but all J2EE modules also contain specialized files called
- <b>deployment descriptors</b>
- . Deployment descriptors describe the contents of deployment units and
- configure components and applications to their environment. They also
- externalize the relationships between components, so those relationships
- can be managed without writing or changing program code. There are five
- core types of J2EE deployment descriptors, each of which corresponds to a
- type of J2EE deployment unit:
- </p>
- <ul>
- <li>
- <p>Application</p>
- </li>
- <li>
- <p>Application Client</p>
- </li>
- <li>
- <p>EJB</p>
- </li>
- <li>
- <p>Web</p>
- </li>
- <li>
- <p>Resource Adapter for Java Connector</p>
- </li>
- </ul>
- <p>
- Vendor-specific deployment descriptors may be defined for different
- Enterprise application containers to provide additional information.
- </p>
- <p>
- Each deployment descriptor describes a set of contained objects which are
- represented through
- <b>module models</b>
- . The root abstract module model object for the deployment descriptor is
- the associated J2EE abstract module type object.
- </p>
- <ul>
- <li>
- <p>
- The
- <b>Application</b>
- is the root object for an EAR module.
- </p>
- </li>
- <li>
- <p>
- The
- <b>EJBJar</b>
- is the root object for an EJB module.
- </p>
- </li>
- <li>
- <p>
- The
- <b>WebApp</b>
- is the root object for a Web module
- </p>
- </li>
- <li>
- <p>
- The
- <b>ApplicationClient</b>
- is the root object for an Application Client module.
- </p>
- </li>
- <li>
- <p>
- The
- <b>Connector</b>
- is the root object for a JCA Connector module.
- </p>
- </li>
- </ul>
- <p>
- Before proceeding, it should be noted that there are two distinct
- metamodels in the tooling environment. First, J2EE abstract models allow
- framework clients to understand the J2EE-specific deployment descriptors
- and their third-party extensions. The tooling frameworks are built
- primarily to modify and update these models. There is also a separate
- model for understanding how modules and their contained resources can be
- constructed for deploying to server environments, which is referred to as
- <b>ModuleCore</b>
- .
- </p>
- <p>
- <b>ModuleCore</b>
- can be used to acquire, create, and destroy
- <b>abstract module contexts</b>
- . An
- <b>abstract module context</b>
- is used to manage multiple abstract modules per project. In the first
- implementation, an abstract module context will not span multiple
- projects. Each abstract module context identifies a unique custom defined
- abstract module using a module handle (see Server Tooling), server target
- type (see Server Tooling), an edit model (to be discussed later).
-
- </p>
-
- <table
- cellspacing="10"
- cellpadding="10">
- <tr>
- <td>
- <p>
- <!-- Image does not exist.
- <img src="../images/modulecore_concepts.jpg" />
- -->
- </p>
- </td>
- </tr>
- <tr>
- <td>
- <p>
- <i>
- Figure 1: Overview of ModuleCore, ModuleContext, and
- Abstract Module relationships.
- </i>
- </p>
- </td>
- </tr>
- </table>
- <p>
- Meanwhile,
- <b>edit models</b>
- provide a shared, reference counted, read/write controlled amalgamation
- of a related set of resources. Primarily, resources and Java working
- copies are wrapped by an Edit Model in order to represent a coherent and
- consistent view for clients. Managing these resources as a group, allows
- changes to be committed or rolled back as a consistent unit of work.
- </p>
- <p>
- Typically, specialized types of edit models have aforementioned knowledge
- of their expected or required resources for a given type of abstracted
- module. Not surprisingly, clients may wish to add capabilities and
- additional known resources to existing edit model. The edit model will
- attempt to load these resources so that they may be managed with the
- existing, known resources.
- </p>
- <p>
- Edit models are created via an extension which defines the
- <b>edit model factory</b>
- . The lifecycle of how edit models are created and destroyed will be
- covered in the API Concepts document.
- </p>
- <p>
- Typically, J2EE components are built on a regular schedule (e.g. daily)
- and packaged as Enterprise Archives (EARs). Collaboration between teams
- and individual members is facilitated by these build artifacts which are
- used to back current development. These are referred to as
- <b>target EARs</b>
- . Developers set up their development environments so the components they
- are actively working on are loaded directly from a source repository and
- the other components are loaded from the Target EARs.
- </p>
- <p>
- The use of target EARs is analogous to self-hosting in Eclipse. The idea
- is to only have abstract modules that are currently being developed in
- the workspace. All other dependencies will be loaded from a target EAR.
- Changing target EARs would simply be a matter of adjusting some abstract
- module property (just like PDE). Loading projects from the repository, or
- deleting them from the workspace would change where they were loaded from
- as well (also like PDE).
- </p>
- <p>
- Rather than using target EARs, EAR files may be extracted to a structure
- which represents its contained abstract modules. The remaining non-module
- jar archives are called
- <b>utility jars</b>
- . Utility jars are regular jars which the various abstract modules can
- depend on. Utility jars may exist as jar files within the EAR abstract
- module which is useful when a developer is not currently working on the
- contents of the utility jar. All abstract module archives must (utility
- jars have the option) be handled in separate abstract modules.
- </p>
- <p>
- An <b>extracted module</b> or <b>utility jar module</b> is simply a module containing
- the extracted contents of the archive. The benefit of using extracted
- modules is all the artifacts can be modified. This would be useful if a
- developer did not have access to the source repository. Typically,
- however, instead of using extracted modules, a developer would connect to
- a source repository. Jars within WARs can be extracted as modules within
- Eclipse projects (like utility jar modules) or can remain in the WAR in
- binary form.
- </p>
- <p><i>Last updated 11/11/04</i></p>
- </body>
-</html>
diff --git a/development/proposals/FlexibleProjectConcepts_files/filelist.xml b/development/proposals/FlexibleProjectConcepts_files/filelist.xml
deleted file mode 100644
index 8cc6128..0000000
--- a/development/proposals/FlexibleProjectConcepts_files/filelist.xml
+++ /dev/null
@@ -1,5 +0,0 @@
-<xml xmlns:o="urn:schemas-microsoft-com:office:office">
- <o:MainFile HRef="../FlexibleProjectConcepts.htm"/>
- <o:File HRef="image001.gif"/>
- <o:File HRef="filelist.xml"/>
-</xml>
\ No newline at end of file
diff --git a/development/proposals/FlexibleProjectConcepts_files/image001.gif b/development/proposals/FlexibleProjectConcepts_files/image001.gif
deleted file mode 100644
index f2962db..0000000
--- a/development/proposals/FlexibleProjectConcepts_files/image001.gif
+++ /dev/null
Binary files differ
diff --git a/development/proposals/FlexibleProjectStructureDesignOverview.html b/development/proposals/FlexibleProjectStructureDesignOverview.html
deleted file mode 100644
index 26a2228..0000000
--- a/development/proposals/FlexibleProjectStructureDesignOverview.html
+++ /dev/null
@@ -1,818 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../webtools/wtp.css" type="text/css">
-<title>flexible project concepts</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">jst j2ee</font>
-<br>
-<font class="indexsub">flexible project concepts</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top"><a name="top"></a></td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Introduction</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The following document provides an overview of the direction that the
- J2EE Tools team is going with the design and implementation of the
- Flexible Project Structure support and API. The document will discuss the
- following:
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>
-
-<p>the metamodel used to understand project structures,</p>
-
-</li>
-
-<li>
-
-<p>the XML format used to store the model within each project,</p>
-
-</li>
-
-<li>
-
-<p>a high level overview of the important components in the API,</p>
-
-</li>
-
-<li>
-
-<p>how the modules are prepared for deployment, and</p>
-
-</li>
-
-<li>
-
-<p>how modules are announced to the server.</p>
-
-</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The design of the flexible project structure as enumerated by this
- document does not meet some of the initial suggestions due to constraints
- within the base Eclipse platform. For instance, only one server target is
- supported at a time (but users may switch the server target easily and
- recompile). Also, the resources which compose a module must be wholly
- contained under a single project, but of course modules may reference
- modules in other projects.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Project Structural Model</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The EMF structural model allows the tooling to understand various layouts
- for projects. Each logical module contained in the project is represented
- by a WorkbenchModule element. The WorkbenchModule defines information
- about the type of module, the resources consumed by the module from the
- project, and the dependent modules. The WorkbenchModule is abstract, and
- as modeled, does not necessarily correspond to only J2EE artifacts.
-
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<table cellspacing="10" cellpadding="10">
-
-<tr>
-
-<td>
-
-<p>
-<!-- Image does not exist.
-<img src="../images/module_structural_metamodel_rose.png">
--->
- </p>
-
-</td>
-
-</tr>
-
-<tr>
-
-<td>
-
-<p>
-
-<i>Figure 1: The Module Structural Metamodel.</i>
-
-</p>
-
-</td>
-
-</tr>
-
-</table>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The WorkbenchModule defines its deployedName, which is the name that will
- be used when the deployable form of the module is constructed. For a web
- application, the deployedName might be “MyWebApplication.war”. The
- WorkbenchModule may be uniquely referenced by a URI (stored on the
- WorkbenchModule as the “handle”). The fully qualified URI to any module
- must begin with the module protocol (“module:”), specify a subprotocol
- (“resource|classpath”) and then a path to the referenced module. A
- WorkbenchModule with the deplyedName “MyWebApplication.war” defined in a
- project named “MyWebModulesProject” would be referenced by the following
- URI: “module:/resource/MyWebModulesProject/MyWebApplication.war”.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Each WorkbenchModule defines a ModuleType. The ModuleType defines a
- moduleTypeId, which indicates the specific kind of module. The Web Tools
- Platform uses the moduleTypeId to determine how to handle the
- WorkbenchModule. The ModuleType may also define the runtime-paths of
- special metadata resources which are important to the WorkbenchModule.
- “Metadata” refers to resources which explain the details of the specific
- modules. An example of such a file would be the “WEB-INF/web.xml”
- deployment descriptor for Web Applications.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Each WorkbenchModule defines a list of WorkbenchModuleResources. Each
- WorkbenchModuleResource provides “sourcePath” and the corresponding
- “deployedPath”. The “sourcePath” can reference either a file or folder,
- but must reference a resource in the same project. The “deployedPath”
- will specify a location relative to the deployed structure of the
- WorbenchModule.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Each WorkbenchModule defines a list of DependentModules. Each
- DependentModule provides a handle which must resolve to another
- WorkbenchModule, a deployedPath that defines where the constructed module
- will be placed within the context of the deployed WorkbenchModule, and a
- dependencyType that can be either “consume” or “use” to indicate how the
- contents of that DependentModule should be absorbed by the
- WorkbenchModule.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">XML Format for WorkbenchModules</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The EMF model is stored as an XML model on disk. A full schema of this
- format will follow. The example below defines two modules in a single
- project. The first module (named: “MyWebModule.war”) defines two
- resources – each containers – that should be included in the deployed
- module. Three dependent modules are referenced, demonstrating the various
- ways that module URIs may be used. The first reference points to a local
- module, defined in the same project. The second reference
- (“module:/resource/AnotherProject/MyWebModuleLib2.jar”) uses a fully
- qualified URI that points to a module in another project. The last
- reference points to a module which is already in a deployable form and
- available on the classpath
- (“module:/classpath/AnotherTeamsUtilities.jar”). The second module
- defined by the XML sample (“MyWebModuleLib.jar”) defines a
- WorkbenchModule of the type “jst.utility”, which would be a simple Java
- library that could be used as a Utility Jar in a *.ear module or a Web
- Library in a *.war module.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<table cellspacing="10" cellpadding="10">
-
-<tr>
-
-<td>
-
-<pre>
-
-<project-modules id="moduleCoreId">
- <wb-module
- deploy-name="MyWebModule.war">
- <wb-module
- module-type-id="jst.web" />
- <wb-resource
- deploy-path="WEB-INF/"
- source- path="/MyModulesProject/MyWebModule/WebContent/WEB-INF" />
- <wb-resource
- deploy-path="jsps/"
- source- path="/MyModulesProject/MyWebModule/WebContent/myjsps" />
- <dependent-module
- deploy-path="WEB-INF/lib"
- handle="MyWebModuleLib.jar" />
- <dependent-module
- deploy-path="WEB-INF/lib"
- handle="module:/resource/AnotherProject/MyWebModuleLib2.jar" />
- <dependent-module
- deploy-path="WEB-INF/lib"
- handle="module:/classpath/AnotherTeamsUtilities.jar" />
- </wb-module>
- <wb-module
- deploy-name="MyWebModuleLib.jar">
- <wb-module
- module-type-id="jst.utility" />
- <wb-resource
- deploy-path="/"
- source-path="/MyModulesProject/lib-src"/>
- </wb-module>
-</project-modules>
- </pre>
-
-</td>
-
-</tr>
-
-<tr>
-
-<td>
-
-<p>
-
-<i>Figure 2: Sample metamodel XML format</i>
-
-</p>
-
-</td>
-
-</tr>
-
-</table>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Constraints enforced by the current solution</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ol>
-
-<li>
-
-<p>
- The solution will not check dependencies for modules that are
- contained in the same project. To get the full benefits of
- inter-module dependency checking, modules must be separated into
- different projects. We do not have the necessary flexibility in
- constructing and scoping classpaths on a level more granular than
- the project level, which would be needed to support this
- functionality.
- </p>
-
-</li>
-
-<li>
-
-<p>
- The solution will not allow a single module to span more than one
- project. Within that project, we will have fairly broad
- flexibility to specify which resources map to which modules. Each
- module within a project must have its own source folder, but a
- module may contain more than one source folder. It would be
- discouraged or completely disallowed for a single source folder
- to be contained by more than one module. Modules may reference
- dependent modules in other projects (so a Web Application may
- reference a Web Library outside of the project that contains the
- Web Application).
- </p>
-
-</li>
-
-<li>
-
-<p>
- The solution will not allow more than one server target per
- module (and really per-project) at a time. The ability to switch
- this server target (via some action or property setting) will
- continue to be possible. Users that need the capability to
- develop for multiple server targets will need to manually switch
- and test as necessary.
- </p>
-
-</li>
-
-<li>
-
-<p>
- Each module in a project will have its own output folder
- structure automatically constructed for it. The output structure
- will match the J2EE-spec output structure required for the module
- type (for J2EE modules). A new builder will handle this
- responsibility and work cooperatively with the Java builder to
- construct a deployable, on-disk representation of the module
- structure. The necessity for this on-disk structure to match a
- J2EE-compliant layout is motivated by the requirement to have
- in-workbench testing, so that users will not have to deal with a
- deployer actually constructing a deployable module and shipping
- it off to a server to test their code. This approach is
- consistent with existing Ant-based approaches and Application
- Servers which can run in a "debug" mode on disk. Our value-add
- will be greater automation and integration with the workbench --
- particularly for incremental based support. The specialized
- module builder would not be necessary if the source was already
- in the appropriate J2EE-spec compliant structure. The default
- creation will still encourage a single module per project, which
- conforms to the correct J2EE structure.
- </p>
-
-</li>
-
-<li>
-
-<p>
- Modules will be described using a simple XML format, and each
- project will contain one .wtpmodules file that will describe all
- of the modules for that project. The level of tooling to help
- users create these files is yet to be determined for WTP M4. This
- would be a great area for other interested developers to suggest
- and provide tooling (e.g. a Wizard or Editor) to create these
- files from existing structures.
- </p>
-
-</li>
-
-</ol>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Interaction Diagram for Important Components</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The follow diagram highlights the important relationships between the
- components in the Flexible Project API. Each project that supports a
- flexible project structure has a ModuleCoreNature associated with it. The
- ModuleCoreNature is used to manage the WTP Modules Structural Model and
- used to access the Artifact Edit Models. A project has exactly one
- Structural Model that defines all of the modules contained by the
- project. A project may have multiple Artifact Edit Models. Each Artifact
- Edit Model represents the pieces of a module that an operation or editor
- would want to modify, and are loaded and saved as a single unit.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<table cellspacing="10" cellpadding="10">
-
-<tr>
-
-<td><!-- Image does not exist.
- <img src="../images/modulecore_interaction_diagram_rose.jpg">
- -->
- </td>
-
-</tr>
-
-<tr>
-
-<td>
-
-<p>
-
-<i>Figure 3: Interaction diagram of the ModuleCore components</i>
-
-</p>
-
-</td>
-
-</tr>
-
-</table>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The complexity of accessing the models is hidden from clients by the use
- of an Adapter pattern. When a client needs to read or modify a deployment
- descriptor model, the client may adapt the ArtifactEditModel to return an
- instance of the ArtifactEdit adapter or even request a specific subclass
- of ArtifactEdit with API which is targeted to the specific type of
- Deployment Descriptor. Clients that need to edit or understand the
- structural model of the modules in the project may use a similar pattern
- by adapting the ModuleStructuralModel to a ModuleCore adapter, which will
- then have the necessary API to focus on the module structural model.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The ArtifactEditModel and ModuleStructuralModel are each a subclass of
- the EditModel object. Edit models have a life cycle that requires them to
- be notified when clients are using them and notified when clients have
- completed their tasks. The ModuleCore and ArtifactEdit adapters will wrap
- the specific instances of the edit models they originally adapted. At the
- end of the client’s usage, the edit model must still be released.
- Releasing the edit model allows the framework to maintain an accurate
- reference count so that when the edit model is no longer in use by any
- client, the resources that it references may be unloaded.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">ArtifactEdit: Working with the Module Content Metamodel</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The ArtifactEdit adapter pattern is used to facilitate access to the
- modules resources, and provide API for specific module types. Clients
- must adapt the ArtifactEditModel to an ArtifactEdit adapter, which will
- operate in the context of the ArtifactEditModel that created it. An
- ArtifactEditModel may be acquired from the ModuleCoreNature using the
- specific WorkbenchModule the client is interested in.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<pre>
- public ArtifactEditModel getModuleEditModelForRead(WorkbenchModule wbModule, Object anAccessorKey)
- </pre>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Each module type will register an ArtifactEditAdapterFactory that creates
- a corresponding ArtifactEdit instance or subclass. For instance, a module
- of type “jst.web” would register the WebAppEditAdapterFactory.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<pre>
- IAdapterManager manager = Platform.getAdapterManager();
- manager.registerAdapters(new WebAppEditAdapterFactory(), ArtifactEditModel.class);
- </pre>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Web Tools Platform contributors may use SPI as above to expand the types
- of ArtifactEdit adapters available to clients.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>The following line would return the specific ArtifactEdit instance:</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<pre>
- WebAppEdit util = (WebAppEdit)moduleEditModel.getAdapter(WebAppEdit.class);
- </pre>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The WebAppEdit class would have some of the specific module API
- previously found on the WebNature and WebEditModel. Type specific API
- would be found here:
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<pre>
- public WebApp getWebApp();
- public int getServletVersion();
- </pre>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>Additionally, API is inherited from a common superclass:</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<pre>
- public int getJ2EEVersion();
- public createDeploymentDescriptorWithRoot();
- public EObject getRootObject();
- </pre>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The API that will be provided to consumers is still under development,
- and suggestions for the kinds of API that are required are always
- welcome.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Deployable Module Builder</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The Deployable Module Builder extends the Eclipse Incremental Builder
- framework in order to create and maintain a deployable module output
- structure for flexible module projects, which are now supported by the
- Web Tools Platform. The builder is added to any project which contains
- the Module Core Nature indicating that a given project is flexible. The
- can construct appropriate deploy structures for multiple modules of
- possibly varying types within the same project. The deploy structure for
- each J2EE module will be the corresponding J2EE-compliant runtime
- structure, but the builder may be extended to handle other types of
- modules that are not J2EE-specific. The deploy structures created by the
- builder may then be used to run on a server.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The Deployable Module Builder is scoped to the project level, as all
- Eclipse builders are, however this specific builder is more concerned
- about the individual modules within a given project. The design of the
- builder focuses on these individual modules, rather than a project-level
- artifact. The builder uses the WorkbenchModule definitions from the
- Modules Structural Model to understand what structures need to be
- created. Each operation arranges the deployable structure according to
- J2EE specifications by processing each of the WorkbenchModuleResources
- contained in its WorkbenchModule. The deployable structure is created in
- the project using the format “RootProject/.deployables/module_name”. The
- builder also manages all module dependencies making sure dependent
- modules are handled appropriately. Once all WorkbenchModules for the
- given project have been constructed, the Java builder will then compile
- all source code and the *.class files will be pushed into the predefined
- output locations within their corresponding WorkbenchModule deployed
- structure. The API defined by the Server Tools component will then be
- used to correctly adapt a WorkbenchModule to an IModule in order to run
- the modules on the server.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Each module type (EJB, Web App, App Client, Connector) must register its
- own type of deployable module builder. The registration mechanism is not
- yet complete, but will allow for total extensibility within the framework
- in how deployable modules are constructed. (Note: Currently in the M3
- initial implementation, the only module which contributes a deployable
- module builder is Web Application, which means only a Web Application
- project can support flexible project structures.)
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The following screen shots show a flexible Web Module project before and
- after the Deployable Module Builder has run.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<table cellspacing="10" cellpadding="10">
-
-<tr>
-
-<td><!-- Image does not exist.
- <img src="../images/flexibleproject_screenshot1.png">
- -->
- </td>
-
-</tr>
-
-<tr>
-
-<td>
-
-<p>
-
-<i>Figure 4: A flexible project before a build.</i>
-
-</p>
-
-</td>
-
-</tr>
-
-</table>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<table cellspacing="10" cellpadding="10">
-
-<tr>
-
-<td><!-- Image does not exist.
- <img src="../images/flexibleproject_screenshot2.png">
- -->
- </td>
-
-</tr>
-
-<tr>
-
-<td>
-
-<p>
-
-<i>
- Figure 5: A flexible project after a build with 3 web
- modules defined within the project.
- </i>
-
-</p>
-
-</td>
-
-</tr>
-
-</table>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<table cellspacing="10" cellpadding="10">
-
-<tr>
-
-<td><!-- Image does not exist.
- <img src="../images/flexibleproject_screenshot3.png">
- -->
- </td>
-
-</tr>
-
-<tr>
-
-<td>
-
-<p>
-
-<i>
- Figure 6: The individual output module J2EE compliant
- contents.
- </i>
-
-</p>
-
-</td>
-
-</tr>
-
-</table>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Server Integration</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The contents of the “.deployables” folder are represented as IModules to
- the Server Tooling, which is a model format that the server can deploy.
- The Server API contains a ServerUtil object that listens for project
- changes. A project change occurs after the deploy builder creates a
- “.deployables” folder. After the project change, ServerUtil will query
- for a DeployableFactory via an extension point. Currently, Server Tools
- assigns a single DeployableFactory per project, which must be expanded to
- allow multiple modules and modules types per project. The
- DeployableFactory will create multiple J2EE ModuleDelegates depending on
- the WorkbenchModules defined for the project (see ModuleCore API). Each
- J2EE ModuleDelegate will set its context and metadata location based on
- the location of the deployable structure created for the WorkbenchModule.
- Next, the DeployableFactory creates an IModule (as defined by the Server
- Tools API) caches the IModule by the project. As already stated, single
- module per project approach must change to support multiple modules per
- project.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Once the Run on server action is invoked by the user, the WorkbenchModule
- will be adapted to an IModule, which the Server Tools understand and can
- deploy.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<table cellspacing="10" cellpadding="10">
-
-<tr>
-
-<td><!-- Image does not exist.
- <img src="../images/deployable_module_builder_overview.jpg">
- -->
- </td>
-
-</tr>
-
-<tr>
-
-<td>
-
-<p>
-
-<i>
- Figure 6: Interaction diagram of the Server Integration components
- </i>
-
-</p>
-
-</td>
-
-</tr>
-
-</table>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p></p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-
-<i>Last updated Feb 16 2004</i>
-
-</p>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/development/proposals/FlexibleProjectStructureDesignOverview.xml b/development/proposals/FlexibleProjectStructureDesignOverview.xml
deleted file mode 100644
index 3e41f07..0000000
--- a/development/proposals/FlexibleProjectStructureDesignOverview.xml
+++ /dev/null
@@ -1,514 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?xml-stylesheet type="text/xsl" href="../../wtp.xsl"?>
-<html>
- <head>
- <meta
- name="root"
- content="../../.." />
- <title>flexible project concepts</title>
- </head>
-
- <body>
- <a name="top" />
-
- <h1>jst j2ee</h1>
-
- <h2>Introduction</h2>
- <p>
- The following document provides an overview of the direction that the
- J2EE Tools team is going with the design and implementation of the
- Flexible Project Structure support and API. The document will discuss the
- following:
- </p>
-
- <ul>
- <li>
- <p>the metamodel used to understand project structures,</p>
- </li>
- <li>
- <p>the XML format used to store the model within each project,</p>
- </li>
- <li>
- <p>a high level overview of the important components in the API,</p>
- </li>
- <li>
- <p>how the modules are prepared for deployment, and</p>
- </li>
- <li>
- <p>how modules are announced to the server.</p>
- </li>
- </ul>
- <p>
- The design of the flexible project structure as enumerated by this
- document does not meet some of the initial suggestions due to constraints
- within the base Eclipse platform. For instance, only one server target is
- supported at a time (but users may switch the server target easily and
- recompile). Also, the resources which compose a module must be wholly
- contained under a single project, but of course modules may reference
- modules in other projects.
- </p>
- <h2>Project Structural Model</h2>
- <p>
- The EMF structural model allows the tooling to understand various layouts
- for projects. Each logical module contained in the project is represented
- by a WorkbenchModule element. The WorkbenchModule defines information
- about the type of module, the resources consumed by the module from the
- project, and the dependent modules. The WorkbenchModule is abstract, and
- as modeled, does not necessarily correspond to only J2EE artifacts.
-
- </p>
- <table
- cellspacing="10"
- cellpadding="10">
- <tr>
- <td>
- <p>
- <img src="../images/module_structural_metamodel_rose.png" />
- </p>
- </td>
- </tr>
- <tr>
- <td>
- <p>
- <i>Figure 1: The Module Structural Metamodel.</i>
- </p>
- </td>
- </tr>
- </table>
- <p>
- The WorkbenchModule defines its deployedName, which is the name that will
- be used when the deployable form of the module is constructed. For a web
- application, the deployedName might be “MyWebApplication.war”. The
- WorkbenchModule may be uniquely referenced by a URI (stored on the
- WorkbenchModule as the “handle”). The fully qualified URI to any module
- must begin with the module protocol (“module:”), specify a subprotocol
- (“resource|classpath”) and then a path to the referenced module. A
- WorkbenchModule with the deplyedName “MyWebApplication.war” defined in a
- project named “MyWebModulesProject” would be referenced by the following
- URI: “module:/resource/MyWebModulesProject/MyWebApplication.war”.
- </p>
- <p>
- Each WorkbenchModule defines a ModuleType. The ModuleType defines a
- moduleTypeId, which indicates the specific kind of module. The Web Tools
- Platform uses the moduleTypeId to determine how to handle the
- WorkbenchModule. The ModuleType may also define the runtime-paths of
- special metadata resources which are important to the WorkbenchModule.
- “Metadata” refers to resources which explain the details of the specific
- modules. An example of such a file would be the “WEB-INF/web.xml”
- deployment descriptor for Web Applications.
- </p>
- <p>
- Each WorkbenchModule defines a list of WorkbenchModuleResources. Each
- WorkbenchModuleResource provides “sourcePath” and the corresponding
- “deployedPath”. The “sourcePath” can reference either a file or folder,
- but must reference a resource in the same project. The “deployedPath”
- will specify a location relative to the deployed structure of the
- WorbenchModule.
- </p>
- <p>
- Each WorkbenchModule defines a list of DependentModules. Each
- DependentModule provides a handle which must resolve to another
- WorkbenchModule, a deployedPath that defines where the constructed module
- will be placed within the context of the deployed WorkbenchModule, and a
- dependencyType that can be either “consume” or “use” to indicate how the
- contents of that DependentModule should be absorbed by the
- WorkbenchModule.
- </p>
- <h2>XML Format for WorkbenchModules</h2>
- <p>
- The EMF model is stored as an XML model on disk. A full schema of this
- format will follow. The example below defines two modules in a single
- project. The first module (named: “MyWebModule.war”) defines two
- resources – each containers – that should be included in the deployed
- module. Three dependent modules are referenced, demonstrating the various
- ways that module URIs may be used. The first reference points to a local
- module, defined in the same project. The second reference
- (“module:/resource/AnotherProject/MyWebModuleLib2.jar”) uses a fully
- qualified URI that points to a module in another project. The last
- reference points to a module which is already in a deployable form and
- available on the classpath
- (“module:/classpath/AnotherTeamsUtilities.jar”). The second module
- defined by the XML sample (“MyWebModuleLib.jar”) defines a
- WorkbenchModule of the type “jst.utility”, which would be a simple Java
- library that could be used as a Utility Jar in a *.ear module or a Web
- Library in a *.war module.
- </p>
-
- <table
- cellspacing="10"
- cellpadding="10">
- <tr>
- <td>
- <pre>
-
-<project-modules id="moduleCoreId">
- <wb-module
- deploy-name="MyWebModule.war">
- <wb-module
- module-type-id="jst.web" />
- <wb-resource
- deploy-path="WEB-INF/"
- source- path="/MyModulesProject/MyWebModule/WebContent/WEB-INF" />
- <wb-resource
- deploy-path="jsps/"
- source- path="/MyModulesProject/MyWebModule/WebContent/myjsps" />
- <dependent-module
- deploy-path="WEB-INF/lib"
- handle="MyWebModuleLib.jar" />
- <dependent-module
- deploy-path="WEB-INF/lib"
- handle="module:/resource/AnotherProject/MyWebModuleLib2.jar" />
- <dependent-module
- deploy-path="WEB-INF/lib"
- handle="module:/classpath/AnotherTeamsUtilities.jar" />
- </wb-module>
- <wb-module
- deploy-name="MyWebModuleLib.jar">
- <wb-module
- module-type-id="jst.utility" />
- <wb-resource
- deploy-path="/"
- source-path="/MyModulesProject/lib-src"/>
- </wb-module>
-</project-modules>
- </pre>
- </td>
- </tr>
- <tr>
- <td>
- <p>
- <i>Figure 2: Sample metamodel XML format</i>
- </p>
- </td>
- </tr>
- </table>
- <h2>Constraints enforced by the current solution</h2>
- <ol>
- <li>
- <p>
- The solution will not check dependencies for modules that are
- contained in the same project. To get the full benefits of
- inter-module dependency checking, modules must be separated into
- different projects. We do not have the necessary flexibility in
- constructing and scoping classpaths on a level more granular than
- the project level, which would be needed to support this
- functionality.
- </p>
- </li>
- <li>
- <p>
- The solution will not allow a single module to span more than one
- project. Within that project, we will have fairly broad
- flexibility to specify which resources map to which modules. Each
- module within a project must have its own source folder, but a
- module may contain more than one source folder. It would be
- discouraged or completely disallowed for a single source folder
- to be contained by more than one module. Modules may reference
- dependent modules in other projects (so a Web Application may
- reference a Web Library outside of the project that contains the
- Web Application).
- </p>
- </li>
- <li>
- <p>
- The solution will not allow more than one server target per
- module (and really per-project) at a time. The ability to switch
- this server target (via some action or property setting) will
- continue to be possible. Users that need the capability to
- develop for multiple server targets will need to manually switch
- and test as necessary.
- </p>
- </li>
- <li>
- <p>
- Each module in a project will have its own output folder
- structure automatically constructed for it. The output structure
- will match the J2EE-spec output structure required for the module
- type (for J2EE modules). A new builder will handle this
- responsibility and work cooperatively with the Java builder to
- construct a deployable, on-disk representation of the module
- structure. The necessity for this on-disk structure to match a
- J2EE-compliant layout is motivated by the requirement to have
- in-workbench testing, so that users will not have to deal with a
- deployer actually constructing a deployable module and shipping
- it off to a server to test their code. This approach is
- consistent with existing Ant-based approaches and Application
- Servers which can run in a "debug" mode on disk. Our value-add
- will be greater automation and integration with the workbench --
- particularly for incremental based support. The specialized
- module builder would not be necessary if the source was already
- in the appropriate J2EE-spec compliant structure. The default
- creation will still encourage a single module per project, which
- conforms to the correct J2EE structure.
- </p>
- </li>
- <li>
- <p>
- Modules will be described using a simple XML format, and each
- project will contain one .wtpmodules file that will describe all
- of the modules for that project. The level of tooling to help
- users create these files is yet to be determined for WTP M4. This
- would be a great area for other interested developers to suggest
- and provide tooling (e.g. a Wizard or Editor) to create these
- files from existing structures.
- </p>
- </li>
- </ol>
- <h2>Interaction Diagram for Important Components</h2>
- <p>
- The follow diagram highlights the important relationships between the
- components in the Flexible Project API. Each project that supports a
- flexible project structure has a ModuleCoreNature associated with it. The
- ModuleCoreNature is used to manage the WTP Modules Structural Model and
- used to access the Artifact Edit Models. A project has exactly one
- Structural Model that defines all of the modules contained by the
- project. A project may have multiple Artifact Edit Models. Each Artifact
- Edit Model represents the pieces of a module that an operation or editor
- would want to modify, and are loaded and saved as a single unit.
- </p>
- <table
- cellspacing="10"
- cellpadding="10">
- <tr>
- <td>
- <img src="../images/modulecore_interaction_diagram_rose.jpg" />
- </td>
- </tr>
- <tr>
- <td>
- <p>
- <i>Figure 3: Interaction diagram of the ModuleCore components</i>
- </p>
- </td>
- </tr>
- </table>
- <p>
- The complexity of accessing the models is hidden from clients by the use
- of an Adapter pattern. When a client needs to read or modify a deployment
- descriptor model, the client may adapt the ArtifactEditModel to return an
- instance of the ArtifactEdit adapter or even request a specific subclass
- of ArtifactEdit with API which is targeted to the specific type of
- Deployment Descriptor. Clients that need to edit or understand the
- structural model of the modules in the project may use a similar pattern
- by adapting the ModuleStructuralModel to a ModuleCore adapter, which will
- then have the necessary API to focus on the module structural model.
- </p>
- <p>
- The ArtifactEditModel and ModuleStructuralModel are each a subclass of
- the EditModel object. Edit models have a life cycle that requires them to
- be notified when clients are using them and notified when clients have
- completed their tasks. The ModuleCore and ArtifactEdit adapters will wrap
- the specific instances of the edit models they originally adapted. At the
- end of the client’s usage, the edit model must still be released.
- Releasing the edit model allows the framework to maintain an accurate
- reference count so that when the edit model is no longer in use by any
- client, the resources that it references may be unloaded.
- </p>
- <h2>ArtifactEdit: Working with the Module Content Metamodel</h2>
- <p>
- The ArtifactEdit adapter pattern is used to facilitate access to the
- modules resources, and provide API for specific module types. Clients
- must adapt the ArtifactEditModel to an ArtifactEdit adapter, which will
- operate in the context of the ArtifactEditModel that created it. An
- ArtifactEditModel may be acquired from the ModuleCoreNature using the
- specific WorkbenchModule the client is interested in.
- </p>
- <p>
- <pre>
- public ArtifactEditModel getModuleEditModelForRead(WorkbenchModule wbModule, Object anAccessorKey)
- </pre>
- </p>
- <p>
- Each module type will register an ArtifactEditAdapterFactory that creates
- a corresponding ArtifactEdit instance or subclass. For instance, a module
- of type “jst.web” would register the WebAppEditAdapterFactory.
- </p>
- <p>
- <pre>
- IAdapterManager manager = Platform.getAdapterManager();
- manager.registerAdapters(new WebAppEditAdapterFactory(), ArtifactEditModel.class);
- </pre>
- </p>
- <p>
- Web Tools Platform contributors may use SPI as above to expand the types
- of ArtifactEdit adapters available to clients.
- </p>
- <p>The following line would return the specific ArtifactEdit instance:</p>
- <p>
- <pre>
- WebAppEdit util = (WebAppEdit)moduleEditModel.getAdapter(WebAppEdit.class);
- </pre>
- </p>
- <p>
- The WebAppEdit class would have some of the specific module API
- previously found on the WebNature and WebEditModel. Type specific API
- would be found here:
- </p>
- <p>
- <pre>
- public WebApp getWebApp();
- public int getServletVersion();
- </pre>
- </p>
- <p>Additionally, API is inherited from a common superclass:</p>
- <p>
- <pre>
- public int getJ2EEVersion();
- public createDeploymentDescriptorWithRoot();
- public EObject getRootObject();
- </pre>
- </p>
- <p>
- The API that will be provided to consumers is still under development,
- and suggestions for the kinds of API that are required are always
- welcome.
- </p>
- <h2>Deployable Module Builder</h2>
- <p>
- The Deployable Module Builder extends the Eclipse Incremental Builder
- framework in order to create and maintain a deployable module output
- structure for flexible module projects, which are now supported by the
- Web Tools Platform. The builder is added to any project which contains
- the Module Core Nature indicating that a given project is flexible. The
- can construct appropriate deploy structures for multiple modules of
- possibly varying types within the same project. The deploy structure for
- each J2EE module will be the corresponding J2EE-compliant runtime
- structure, but the builder may be extended to handle other types of
- modules that are not J2EE-specific. The deploy structures created by the
- builder may then be used to run on a server.
- </p>
- <p>
- The Deployable Module Builder is scoped to the project level, as all
- Eclipse builders are, however this specific builder is more concerned
- about the individual modules within a given project. The design of the
- builder focuses on these individual modules, rather than a project-level
- artifact. The builder uses the WorkbenchModule definitions from the
- Modules Structural Model to understand what structures need to be
- created. Each operation arranges the deployable structure according to
- J2EE specifications by processing each of the WorkbenchModuleResources
- contained in its WorkbenchModule. The deployable structure is created in
- the project using the format “RootProject/.deployables/module_name”. The
- builder also manages all module dependencies making sure dependent
- modules are handled appropriately. Once all WorkbenchModules for the
- given project have been constructed, the Java builder will then compile
- all source code and the *.class files will be pushed into the predefined
- output locations within their corresponding WorkbenchModule deployed
- structure. The API defined by the Server Tools component will then be
- used to correctly adapt a WorkbenchModule to an IModule in order to run
- the modules on the server.
- </p>
- <p>
- Each module type (EJB, Web App, App Client, Connector) must register its
- own type of deployable module builder. The registration mechanism is not
- yet complete, but will allow for total extensibility within the framework
- in how deployable modules are constructed. (Note: Currently in the M3
- initial implementation, the only module which contributes a deployable
- module builder is Web Application, which means only a Web Application
- project can support flexible project structures.)
- </p>
- <p>
- The following screen shots show a flexible Web Module project before and
- after the Deployable Module Builder has run.
- </p>
- <table
- cellspacing="10"
- cellpadding="10">
- <tr>
- <td>
- <img src="../images/flexibleproject_screenshot1.png" />
- </td>
- </tr>
- <tr>
- <td>
- <p>
- <i>Figure 4: A flexible project before a build.</i>
- </p>
- </td>
- </tr>
- </table>
- <table
- cellspacing="10"
- cellpadding="10">
- <tr>
- <td>
- <img src="../images/flexibleproject_screenshot2.png" />
- </td>
- </tr>
- <tr>
- <td>
- <p>
- <i>
- Figure 5: A flexible project after a build with 3 web
- modules defined within the project.
- </i>
- </p>
- </td>
- </tr>
- </table>
- <table
- cellspacing="10"
- cellpadding="10">
- <tr>
- <td>
- <img src="../images/flexibleproject_screenshot3.png" />
- </td>
- </tr>
- <tr>
- <td>
- <p>
- <i>
- Figure 6: The individual output module J2EE compliant
- contents.
- </i>
- </p>
- </td>
- </tr>
- </table>
- <h2>Server Integration</h2>
- <p>
- The contents of the “.deployables” folder are represented as IModules to
- the Server Tooling, which is a model format that the server can deploy.
- The Server API contains a ServerUtil object that listens for project
- changes. A project change occurs after the deploy builder creates a
- “.deployables” folder. After the project change, ServerUtil will query
- for a DeployableFactory via an extension point. Currently, Server Tools
- assigns a single DeployableFactory per project, which must be expanded to
- allow multiple modules and modules types per project. The
- DeployableFactory will create multiple J2EE ModuleDelegates depending on
- the WorkbenchModules defined for the project (see ModuleCore API). Each
- J2EE ModuleDelegate will set its context and metadata location based on
- the location of the deployable structure created for the WorkbenchModule.
- Next, the DeployableFactory creates an IModule (as defined by the Server
- Tools API) caches the IModule by the project. As already stated, single
- module per project approach must change to support multiple modules per
- project.
- </p>
- <p>
- Once the Run on server action is invoked by the user, the WorkbenchModule
- will be adapted to an IModule, which the Server Tools understand and can
- deploy.
- </p>
- <table
- cellspacing="10"
- cellpadding="10">
- <tr>
- <td>
- <img src="../images/deployable_module_builder_overview.jpg" />
- </td>
- </tr>
- <tr>
- <td>
- <p>
- <i>
- Figure 6: Interaction diagram of the Server Integration components
- </i>
- </p>
- </td>
- </tr>
- </table>
- <p></p>
- <p>
- <i>Last updated Feb 16 2004</i>
- </p>
- </body>
-</html>
diff --git a/development/proposals/FlexibleProjectStructureDesignOverview_files/filelist.xml b/development/proposals/FlexibleProjectStructureDesignOverview_files/filelist.xml
deleted file mode 100644
index 579f3c3..0000000
--- a/development/proposals/FlexibleProjectStructureDesignOverview_files/filelist.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-<xml xmlns:o="urn:schemas-microsoft-com:office:office">
- <o:MainFile HRef="../FlexibleProjectStructureDesignOverview.html"/>
- <o:File HRef="image001.png"/>
- <o:File HRef="image011.jpg"/>
- <o:File HRef="oledata.mso"/>
- <o:File HRef="image003.png"/>
- <o:File HRef="image012.jpg"/>
- <o:File HRef="image005.jpg"/>
- <o:File HRef="image006.jpg"/>
- <o:File HRef="image007.jpg"/>
- <o:File HRef="image008.jpg"/>
- <o:File HRef="image009.png"/>
- <o:File HRef="image013.jpg"/>
- <o:File HRef="header.html"/>
- <o:File HRef="filelist.xml"/>
-</xml>
\ No newline at end of file
diff --git a/development/proposals/FlexibleProjectStructureDesignOverview_files/header.html b/development/proposals/FlexibleProjectStructureDesignOverview_files/header.html
deleted file mode 100644
index 016c3fa..0000000
--- a/development/proposals/FlexibleProjectStructureDesignOverview_files/header.html
+++ /dev/null
@@ -1,31 +0,0 @@
-<html xmlns:v="urn:schemas-microsoft-com:vml"
-xmlns:o="urn:schemas-microsoft-com:office:office"
-xmlns:w="urn:schemas-microsoft-com:office:word"
-xmlns="http://www.w3.org/TR/REC-html40">
-
-<head>
-<meta http-equiv=Content-Type content="text/html; charset=windows-1252">
-<meta name=ProgId content=Word.Document>
-<meta name=Generator content="Microsoft Word 10">
-<meta name=Originator content="Microsoft Word 10">
-<link id=Main-File rel=Main-File
-href="../FlexibleProjectStructureDesignOverview.html">
-</head>
-
-<body lang=EN-US link=blue vlink=purple>
-
-<div style='mso-element:header' id=h1>
-
-<p class=MsoHeader><font size=1 face=Arial><span style='font-size:8.0pt;
-font-family:Arial'>Web Tools Platform <span style='mso-tab-count:2'> </span>Page
-<span style='mso-field-code:" PAGE "'><span style='mso-no-proof:yes'>1</span></span>
-of <span style='mso-field-code:" NUMPAGES "'><span style='mso-no-proof:yes'>8</span></span><o:p></o:p></span></font></p>
-
-<p class=MsoHeader><font size=1 face=Arial><span style='font-size:8.0pt;
-font-family:Arial'>Flexible Project Structure: Concepts and Direction<o:p></o:p></span></font></p>
-
-</div>
-
-</body>
-
-</html>
diff --git a/development/proposals/FlexibleProjectStructureDesignOverview_files/image001.png b/development/proposals/FlexibleProjectStructureDesignOverview_files/image001.png
deleted file mode 100644
index dcd8397..0000000
--- a/development/proposals/FlexibleProjectStructureDesignOverview_files/image001.png
+++ /dev/null
Binary files differ
diff --git a/development/proposals/FlexibleProjectStructureDesignOverview_files/image003.png b/development/proposals/FlexibleProjectStructureDesignOverview_files/image003.png
deleted file mode 100644
index 5c2fe42..0000000
--- a/development/proposals/FlexibleProjectStructureDesignOverview_files/image003.png
+++ /dev/null
Binary files differ
diff --git a/development/proposals/FlexibleProjectStructureDesignOverview_files/image005.jpg b/development/proposals/FlexibleProjectStructureDesignOverview_files/image005.jpg
deleted file mode 100644
index f6bbc87..0000000
--- a/development/proposals/FlexibleProjectStructureDesignOverview_files/image005.jpg
+++ /dev/null
Binary files differ
diff --git a/development/proposals/FlexibleProjectStructureDesignOverview_files/image009.png b/development/proposals/FlexibleProjectStructureDesignOverview_files/image009.png
deleted file mode 100644
index d47fbce..0000000
--- a/development/proposals/FlexibleProjectStructureDesignOverview_files/image009.png
+++ /dev/null
Binary files differ
diff --git a/development/proposals/FlexibleProjectStructureDesignOverview_files/image011.jpg b/development/proposals/FlexibleProjectStructureDesignOverview_files/image011.jpg
deleted file mode 100644
index 5fc0f58..0000000
--- a/development/proposals/FlexibleProjectStructureDesignOverview_files/image011.jpg
+++ /dev/null
Binary files differ
diff --git a/development/proposals/FlexibleProjectStructureDesignOverview_files/image012.jpg b/development/proposals/FlexibleProjectStructureDesignOverview_files/image012.jpg
deleted file mode 100644
index b339a5e..0000000
--- a/development/proposals/FlexibleProjectStructureDesignOverview_files/image012.jpg
+++ /dev/null
Binary files differ
diff --git a/development/proposals/index.html b/development/proposals/index.html
deleted file mode 100644
index 7fcfad7..0000000
--- a/development/proposals/index.html
+++ /dev/null
@@ -1,94 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../webtools/wtp.css" type="text/css">
-<title>Proposals</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">web tools platform</font>
-<br>
-<font class="indexsub">Proposals</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Introduction</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Proposals allow technical contributors in the community to outline
- requests for new functionality or to provide initial suggestions
- for new functionality to the community in a persistable, open manner.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Feedback on these proposals is encouraged by adding comments
- to referenced bugs or via the mailing list
- (<a href="https://dev.eclipse.org/mailman/listinfo/wtp-dev">wtp-dev</a>
- unless otherwise specified). Please include a reference (URL) to the
- proposal that you are providing feedback for any e-mails to the
- mailing list.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Proposals</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>
- <a href="../../jst/components/j2ee/proposals/WTPFlexibleProjectProposals.html">
- New WTP Flexible Project Proposals
- </a>
- : Provides an overview of the proposed features from the platform. <i>Added (09/07/05).</i>
- </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>
- <a href="Features Framework Specification.htm">
- Feature Framework Specification Proposal
- </a>
- : A proposal to introduce a concept of a "feature" for the Virtual components.
- Component Features would replace the existing concept of a single component type
- identifier and would provide a way to specify the precise functionality that should
- be enabled for a component. <i>Added (05/10/05).</i>
- </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>
- <a href="FlexibleProjectConcepts.html">
- Flexible Project Concepts
- </a>
- : Defines terminology and concepts for the Flexible Project
- Structure design. <i>Added (02/19/05).</i>
- </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>
- <a href="FlexibleProjectStructureDesignOverview.html">
- Flexible Project Design Overview
- </a>
- : Provides an overview of the current design solution. <i>Added (02/19/05).</i>
- </td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/development/proposals/index.xml b/development/proposals/index.xml
deleted file mode 100644
index 783887f..0000000
--- a/development/proposals/index.xml
+++ /dev/null
@@ -1,55 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?xml-stylesheet type="text/xsl" href="../../wtp.xsl"?>
-<html>
- <head>
- <meta name="root" content="../../.." />
- <title>Proposals</title>
- </head>
- <body>
- <h1>web tools platform</h1>
- <h2>Introduction</h2>
- <p>
- Proposals allow technical contributors in the community to outline
- requests for new functionality or to provide initial suggestions
- for new functionality to the community in a persistable, open manner.
- </p>
- <p>
- Feedback on these proposals is encouraged by adding comments
- to referenced bugs or via the mailing list
- (<a href="https://dev.eclipse.org/mailman/listinfo/wtp-dev">wtp-dev</a>
- unless otherwise specified). Please include a reference (URL) to the
- proposal that you are providing feedback for any e-mails to the
- mailing list.
- </p>
- <h2>Proposals</h2>
- <h3>
- <a href="../../jst/components/j2ee/proposals/WTPFlexibleProjectProposals.html">
- New WTP Flexible Project Proposals
- </a>
- : Provides an overview of the proposed features from the platform. <i>Added (09/07/05).</i>
- </h3>
- <h3>
- <a href="Features Framework Specification.htm">
- Feature Framework Specification Proposal
- </a>
- : A proposal to introduce a concept of a "feature" for the Virtual components.
- Component Features would replace the existing concept of a single component type
- identifier and would provide a way to specify the precise functionality that should
- be enabled for a component. <i>Added (05/10/05).</i>
- </h3>
- <h3>
- <a href="FlexibleProjectConcepts.html">
- Flexible Project Concepts
- </a>
- : Defines terminology and concepts for the Flexible Project
- Structure design. <i>Added (02/19/05).</i>
- </h3>
- <h3>
- <a href="FlexibleProjectStructureDesignOverview.html">
- Flexible Project Design Overview
- </a>
- : Provides an overview of the current design solution. <i>Added (02/19/05).</i>
- </h3>
- <br />
- </body>
-</html>
\ No newline at end of file
diff --git a/development/requirements/build.xml b/development/requirements/build.xml
deleted file mode 100644
index 9930802..0000000
--- a/development/requirements/build.xml
+++ /dev/null
@@ -1,26 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!--
-
- Change Log:
-
- 2005-06-22 Arthur Ryman <ryman@ca.ibm.com>
- - created rdf task to query Bugzilla via Ant get task
-
--->
-
-
-
-<project name="requirements" default="main" basedir=".">
-
- <target name="main" depends="rdf, milestone-plan" description="Builds XML file" />
-
- <target name="rdf" description="Gets bugs from Bugzilla in RDF format.">
- <get dest="enhancements.rdf" src="https://bugs.eclipse.org/bugs/buglist.cgi?product=Web+Tools&bug_status=NEW&bug_severity=enhancement&ctype=rdf&columnlist=target_milestone,priority,short_short_desc,component" />
- </target>
-
- <target name="milestone-plan" depends="rdf" description="Transforms RDF into Milestone Plan format.">
- <xslt style="rdf2milestone.xsl" in="enhancements.rdf" out="enhancement_overview.xml" force="yes"/>
- </target>
-
-</project>
\ No newline at end of file
diff --git a/development/requirements/enhancement_overview.html b/development/requirements/enhancement_overview.html
deleted file mode 100644
index d5e2975..0000000
--- a/development/requirements/enhancement_overview.html
+++ /dev/null
@@ -1,956 +0,0 @@
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
-<head>
-<title>WTP bugzilla enhancement backlog - ordered by target milestone, priority, component</title>
-<link rel="stylesheet" type="text/css" href="../milestone_plans/stylesheets/images/default_style.css"/>
-<script src="../../popup.js" type="text/javascript">
- // script is linked
- </script>
-</head>
-<body>
-<table border="0" width="100%" cellPadding="2" cellSpacing="5">
-<tr>
-<td>
-<font class="indextop">WTP bugzilla enhancement backlog <br> - ordered by target milestone, priority, component</font>
-<br/>
-<font class="indexsub"/>
-</td>
-<td>
-<br/>
-</td>
-<td width="28%">
-<img height="86" width="120" src="../milestone_plans/stylesheets/images/Idea.jpe"/>
-</td>
-</tr>
-</table>
-<table border="0" width="100%" cellPadding="2" cellSpacing="5">
-<tr>
-<a name="Overall_Planning">
-<td rowspan="3" colSpan="2" bgColor="#0080c0" width="100%" align="left" valign="top">
-<b>
-<font face="Arial,Helvetica">
-<font color="#ffffff">All Milestones</font>
-</font>
-</b>
-</td>
-</a>
-</tr>
-</table>
-<table width="100%" cellspacing="5">
-<tr>
-<td/>
-</tr>
-</table>
-<tr>
-<td>
-<table>
-<tr>
-<td valign="top">
-<img height="16" border="0" nosave="" src="../milestone_plans/stylesheets/images/Adarrow.gif"/>
-</td>
-<td>
-<b>---</b>
-<ul>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=92603"><description>[jst.ws] Support deployment of Axis Web services with JDK 1.5</description>
-</a>
-<font color="8080FF"> [high]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> I get the following message when running a bottom up Web service creation scenario with Axis 1.1 and Tomcat 5.0 using the Sun JDK_1.5. IWAB0489E Error when deploying Web service to Axis runtime java.lang.NullPointerException --- Nested Exception --- java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:396) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.setProperty(SAX ParserImpl.java:395) at org.apache.axis.encoding.DeserializationContextImpl.parse(Deserializa tionContextImpl.java:246) at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:538) at org.apache.axis.Message.getSOAPEnvelope(Message.java:376) at org.apache.axis.client.Call.invokeEngine(Call.java:2583) at org.apache.axis.client.Call.invoke(Call.java:2553) at org.apache.axis.client.Call.invoke(Call.java:1672) at org.apache.axis.client.AdminClient.process(AdminClient.java:355) at org.apache.axis.client.AdminClient.process(AdminClient.java:334) at org.apache.axis.client.AdminClient.process(AdminClient.java:341) at org.apache.axis.client.AdminClient.process(AdminClient.java:292) at org.apache.axis.tools.ant.axis.AdminClientTask.execute(AdminClientTas k.java:308) at org.eclipse.jst.ws.internal.axis.consumption.core.command.AxisDeployC ommand.executeAntTask(AxisDeployCommand.java:111) Here is the java full version: java full version '1.5.0_01-b08' From the stack trace, it appears that Sun's Xerces is not compatible with Axis 1.1. The workaround would be to use JDK 1.4.x. (I'm running with '1.4.2'.) (sengpl@ca.ibm.com @ 2005-04-25 12:08) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=95452">
-<description>[jst.jsp] add JSP "batch" validator to WTP</description>
-</a>
-<font color="8080FF"> [medium]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> There is currently as-you-type source validation for JSP, but no batch validator (that adds problem markers to the problems view). Details need to be figured out to decide if we should be using a JSP compiler such as Jasper for more exact validation, or if our as-you-type approach would be sufficient for batch validation as well (which may be faster than using a JSP compiler...) If the batch validator is in place for JSP, we will get the desired 'gray' icons when a problem from the problems view is fixed in the live editor. (pavery@us.ibm.com @ 2005-05-16 16:30) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=95454">
-<description>[jst.jsp] JSP should support variables declared by custom tags</description>
-</a>
-<font color="8080FF"> [medium]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Variables declared by a custom tag as defined in a TagExtraInfo class should be honored by the JSP editor. This either requires prereq-ing servlet.jar to get Taglib TagExtraInfo... APIs, or some kind of smart reflection to create these API classes at runtime. One problem w/ the prereq-ing approach is that the version of the APIs might not be the correct version that the user is actually running with... One problem I've run into with the reflection approach is that TagLibraryInfo is an abstract class, so I'm not able to reflect it (in any way that I know of). Need to resolve this stuff by M5. (pavery@us.ibm.com @ 2005-05-16 16:37) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=91866">
-<description>[wst.xml] Schema-based Content Assist should be stricter</description>
-</a>
-<font color="8080FF"> [medium]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The content assist in the XML editor makes many more suggestions than might be expected, e.g. for a content model with a sequence (A?, B?, C?), the content assist will always suggest A, B and C regardless of the existing content (e.g. B and C may already be present). This means you can create invalid documents in no time at all. This turns out to be partly because AbstractContentAssistProcessor:1593 (in o.e.wst.xml.ui.internal.contentassist) hardcodes the value ModelQuery.EDIT_MODE_UNCONSTRAINED in all calls to getInsertActions, which returns actions for the legal completions. Setting the value to EDIT_MODE_CONSTRAINED_STRICT is better, but runs into a bug: the text used for starting the completion ('<') is erroneously considered #PCDATA, and so all suggestions are evaluated as invalid by the schema validator used to sieve away illegal suggestions (this happens in DOMValidator.createContentSpecification:144, in xml.core.internal.contentmodel.internal.util). Further, it seems that the DOMValidator determines if something is a valid insert by inserting it and validating the result. This is a problem if the content model requires a sequence of elements (e.g. (A, B, C)?). You will never be allowed to insert 'A' by the validator since A by itself is invalid. So this is really one enhancement request (stricter validation) and, should that suggestion be accepted, two bug reports. (slehmann@novell.com @ 2005-04-19 07:12) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=92551">
-<description>[wst.xml] Allow extension or usage of XMLMultiPageEditor</description>
-</a>
-<font color="8080FF"> [medium]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Today XMLMultiPageEditor and all its 'relatives' are marked as internal API + not very much suited for extension. Thus its not possible to add pages to this editor nor redo what the XMLMultiPageEditorPart does since all its editors also are internal. My usecase is I want to add a multipageeditor like PDE has for plugin.xml and use the WTP xml editor in it - but this is not possible with any public API. (max.andersen@jboss.com @ 2005-04-25 03:55) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=77344">
-<description>[FAQ] List plug-in prereqs for using WTP</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> (bnfb@superboy.org @ 2004-10-30 18:17) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=93543">
-<description>[J2EE Standard Tools] struts-config.xml should support code navigation</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> I don't know which component this belongs so please forgive if it is in a bad component... The editor should of struts-config.xml should allow the navigation to the code through Ctrl+Click as in the Java editor. It should be possible to: - Ctrl+Click on an action type value and open the selected Action - Ctrl+Click on an action name value and open the selected class for the form (or jump to its definition and from there Ctrl+Click on the form-bean type value open the selected class) - Ctrl+Click on a forward path value and open the selected file (ric.almeida@gmail.com @ 2005-05-03 11:16) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=96594">
-<description>[J2EE Standard Tools] Websphere server support</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> I would like to have more application servers supported on 1.0 final version, in special Websphere 5-6. (luctor@gmail.com @ 2005-05-25 08:20) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=77568">
-<description>[Web Standard Tools] Update Management Extension</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> WTP should have a feature that allows tool/server-runtime developers to advertise their wtp-related software maintained outside the eclipse foundation. This feature should follow the 'plugin' pattern; it should be a extension that provides the URL of the updatable software and a list of WTP extension-points that it is related to. This will allow WTP tools to discover external software in a consistent and simple manner WTP can use this feature to provide users for clickable convenient access/installation of external software with minimal discovery effort. The feature would also allow tool providers to maintain their point releases without strong ties to WTP release process. (naci.dai@eteration.com @ 2004-11-03 02:36) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=85251">
-<description>[Web Standard Tools] plugin documentation is missing</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Is it okay, that WebTools plugin doesn't contain no documentation? Or is it just not merged with Eclipse documentation yet? WebTools 1.0M2 (tomasz@rtsoftware.com @ 2005-02-15 08:22) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=90728">
-<description>[Web Standard Tools] Investigate: Use single jar packaging</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-core- home/documents/3.1/run_from_jars.html Eclipse 3.0 and previous was shipped such that each plug-in was a directory that contained code in a JAR, along with multiple other files. In order to improve the number of files that we ship along with the size of the Eclipse distributions, we would like to be able to ship each plug-in as a single JAR file containing its code and other resources. (jeffliu@ca.ibm.com @ 2005-04-07 17:34) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=90730">
-<description>[Web Standard Tools] Investigate: Improve the performance of our resource bundles</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-core- home/documents/3.1/message_bundles.html Standard Java ResourceBundles have quite inefficient space characteristics. Since a running Eclipse tends to have many externalized messages we have implemented a new message bundle story to be used in Eclipse. (jeffliu@ca.ibm.com @ 2005-04-07 17:37) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=92587">
-<description>[Web Standard Tools] Performance Logs collected from WTP M4 Scenerios</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> This is a meta-bug for gathering information about performance failures using the performance instrumentation. Attach your performance.log files to this bug. (david_williams@us.ibm.com @ 2005-04-25 10:55) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=93328">
-<description>[Web Standard Tools] Set the "derived" file attribute for copied resources</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> WTP copies over all resources to the .deployables directory. Unfortunately, this causes them to be doubled in the 'Open Resource' view (Ctrl-Shift-R). It is easy to edit the wrong version (happened to me dozends of times), which means that your changes will never make it to version control (but they will appear in your development web server, which makes issue very nasty). If WTP would set the 'derived' file attribute on all copied resources, they would not appear doubled (except if the user checks 'show derived resources'). What do you think? (andreas@schildbach.de @ 2005-04-29 18:06) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=96848">
-<description>[Web Standard Tools] Bundles, jarring, messages</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Very few plugins in WTP make use of performance and memory improvements in Eclipse v3.0 and v3.1: * Switch to pure bundles (manifest.mf) instead of plugins to save Eclipse startup and management overhead. * Jar up plugins to save disk footprint and install time. * Switch to Messages.properties to lower memory use and improve startup time. We need to slowly start doing each one of these across WTP to improve our performance and memory use. (deboer@ca.ibm.com @ 2005-05-26 14:58) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=91792">
-<description>[documentation] separate jovadoc download</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Jeff, Currently, to see the javadoc in progress, we need to download the SDK build. It will be great if we can download javadoc in a separate zip file to see the document work in progress. (kboo@ca.ibm.com @ 2005-04-18 16:32) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=81771">
-<description>[jst.jsp] Java templates not shown in scriptlet Content Assist</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> wtp-sdk-I20041221.zip Inside of a scriptlet: <% String foo = '5'; foo.toString(); int a[]; if| %> At the '|', I should see Java templates proposed. (nitind@us.ibm.com @ 2004-12-22 03:42) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=81772">
-<description>[jst.jsp] Italic settings not honored in Java code sections</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> wtp-sdk-I20041221.zip Inside of a scriptlet: <% String foo = '5'; foo.toString(); int a[]; if| %> If I've set 'keywords excluding 'return'' to be italicized in the Java Syntax Coloring preferences, the JSP editor does not reflect this nor does it change colors immediately. (nitind@us.ibm.com @ 2004-12-22 03:43) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=82308">
-<description>[jst.jsp] JSP scriplet sections should use Java preferences</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The edition of java code in jsp scriplet gives some useful functionalities, like compilation or code assists. But it seems to do not reuse the java editor preferences. I would like to have the same functionnalities and same comportement that I have when I edit a classic Java class. For example, keeping 'completion overwrites' or the 'automatically insert on correct position' the semicolon and braces would be more comfortable. It would be great if the java formatter could also work on java code in scriplets. In other words, the WTP project should integrate with existing functionality in the Eclipse base :) (chabert@fimasys.fr @ 2005-01-06 04:44) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=82537">
-<description>[jst.jsp] It should be possible to define a style for the content of jsp delimeters too</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> In Window > Preferences > Web and XML > JSP Files > JSP Styles it is not possible to define style for the content of scriptlets e.g. <% this text here %> to make it possible to set it visually appart from other (html) content of a .jsp page for instance by choosing a background color. Currently it is only possible to define a style for Attribute Names, Attribute Values, Comment Content, Comment Delimiters, JSP Delimiters, Tag Delimiters and Tag Names. Missing are JSP Content (the stuff inside scriptlets, e.g. inside JSP Delimiters and inside Scriptlet Tags) and Tag Content (see the equal signs?). See attached screenshot. regards, Lars (lars.sonchocky-helldorf@interone.de @ 2005-01-11 05:42) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=86169">
-<description>[jst.jsp] [ca] JSP Java content assist should auto-import necessary class</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> JSP Java content assist should auto-import a necessary package/class if a class is selected from content assist who is not imported already. In regular JSP syntax it would insert <%@page import='org.foo.Class'%> in XML-JSP syntax it would <jsp:directive.page import='org.foo.Class'/> These would probably be inserted at the top of the file (if that's convention) and under <jsp:root> if it's XML-JSP. (pavery@us.ibm.com @ 2005-02-22 12:57) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=86656">
-<description>[jst.jsp] content assist for <%@page import=""%> would be nice</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> It would be nice to have conent assist for <%@page import='|'%>, similar to what we have for <jsp:useBean class='|'>. (pavery@us.ibm.com @ 2005-02-25 11:49) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=86841">
-<description>[jst.jsp] RFE: generate error on missing taglib-directive</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> When I delete the <%@ taglib...> directives of a JSP-document JST does not generate on error. Expected/recommended behaviour: E.g. with no taglib-directive in the page I would expect jst to generate an error if <bean:write name='item' property='yardProject' /> is used. Current behaviour: No error / warning is generated and the Tomcat servlet container throws a NullPointerException in _jspService() (holbitlan@gmx.de @ 2005-02-28 10:27) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=88389">
-<description>[jst.jsp] Improve cursor position after inserting tag with required attirbute and no default value</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> 1. Create J2EE Web Project. 2. Place files from attachment to correspond project's folders. 3. Open index.jsp file, place cursor into body tag and ask for completion proposals by CTRL+SPACE. 4. Select a:tagName1 from list, so <a:tagName |action=''></a:tagName> is inserted. This is Ok, but cursor is located just before 'action' attribute. It's supposed to be inside 'action' attribute value. (dgolovin@exadel.com @ 2005-03-17 17:07) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=95237">
-<description>[jst.jsp] add EL support for the JSP editor</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> This bug is to track progress for initial EL support in the JSP Editor planned for M5. This will include: - syntax highlihting - content assist - error reporting - (some) auto edit More details to come. (pavery@us.ibm.com @ 2005-05-13 17:41) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=95450">
-<description>[jst.jsp] add extract include file for JSP source refactoring</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> It would be cool to have source 'refactoring' for extracting includes. It could work by: - highlighting desired text - possibly check if selection is valid - extract to the contents to another file - add static or dynamic include tag (pavery@us.ibm.com @ 2005-05-16 16:23) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=96769">
-<description>[jst.jsp] Extendible content assist in JSP editor</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> There are a lot of framevorks that require additional proposals are showed in proposal list for JSP tag attribute. For example, if JSF is used to build WEB application. There is a JSP page looks like: <!-- JSP begin --> <%@ taglib uri='http://java.sun.com/jsf/html' prefix='h' %> <%@ taglib uri='http://java.sun.com/jsf/core' prefix='f' %> <f:loadBundle basename='demo.bundle.Messages' var='Message'/> <HTML> <HEAD> <title>Input Name Page</title> </HEAD> <body bgcolor='white'> <f:view> <h1><h:outputText value='#{Message.inputname_header}'/></h1> <h:messages style='color: red'/> <h:form id='helloForm'> <h:outputText value='#{Message.prompt}'/> <h:inputText id='userName' value='|' required='true'> <f:validateLength minimum='2' maximum='20'/> </h:inputText> <h:commandButton id='submit' action='sayhello' value='Say Hello' /> </h:form> </f:view> </body> </HTML> <!-- JSP end --> Now if user is asking by CTRL+Space for proposal list in attribute value (position marked as | in line below) <h:inputText id='userName' value='|' required='true'> proposal list contains only implicit objects, but for this use-case, I'd like to add some managed beans from JSF configuration file and demo.bundle.Messages resource bundle keys to the proposal list. Now I can do this only using the internal API. This would be more convenient to use extension point or public API for this matter, so third-party vendors can use it. (dgolovin@exadel.com @ 2005-05-26 08:42) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=97089">
-<description>[jst.jsp] Add support for tagx extension.</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> jsp, jspx, jspf, tag, tag are supported and resolve to the JSAP editor. tagx -a tag file in jsp 2.0 xml syntax- is not part of the file associations. I would suggest to add it. There are the natural (pombredanne@nexb.com @ 2005-05-27 17:47) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=82920">
-<description>[jst.server] Deployments don't support dependent projects</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> BAD: Auto server deployments don't support dependent projects. I wonder why JST can't support such a simple but important feature! (caozj@sunline.cn @ 2005-01-15 21:54) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=88045">
-<description>[jst.server] Launching server with specific user</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> I'm working on a linux OS, and I use JBoss as application server. Eclipse is running with my own user, as jboss runs with a specific jboss user (in order to be run by other user on my computer). The fact is that when I launch jboss with eclipse web tool server tools, it try to launch eclipse with my user. I would like to specify the user which launch the server (eg jboss user). A solution may be to add a parameter in front of the launching command line. In my case, it would be a 'sudo -u jboss' to execute the server with my jboss user. (chabert@fimasys.fr @ 2005-03-15 08:41) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=90100">
-<description>[jst.server] JBoss 4.0.1 support</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> It would be nice to be able to start and stop JBoss 4.0.1 from with in web tools. So, I created a server definition for it. Please see attachements. (eclipse@juddsolutions.com @ 2005-04-02 22:35) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=96438">
-<description>[jst.server] Generic Server Support for WebLogic Server 9.0</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Patch org.eclipse.jst.server.generic.serverdefinitions plugin to include support for WebLogic Server 9.0 (rfrost@bea.com @ 2005-05-24 11:10) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=88627">
-<description>[jst.ws] Webservice Explorer does not support Cookies</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> I´ve tried to use the Webservice Explorer from WTP M3 with a Webservice that uses two cookies to work properly. At the first request (which is a login) the load balancing server sets a cookie with the server used for communication and a second cookie is set after I logged in at the webservice successfully. By using the TCP/IP Monitor I figured out that the Webservice Explorer ignores the cookies set by the webservice provider. (klaus.kierer@tiscover.com @ 2005-03-21 06:53) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89102">
-<description>[jst.ws] Plug Web service wizards into Web Service Consumer framework</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The Web Service client and skeleton wizards should be plugged into the Web service consumer framework (89085) so that the wizards can be launched from the Web Services Explorer. Detailed requirements and design are forthcoming in a design document, a link to which will be appended to this defect. [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=89085 (cbrealey@ca.ibm.com @ 2005-03-25 10:30) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89103">
-<description>[jst.ws] Exploit Web Service Finder framework from WSDL selection page</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The WSDL selection page (page 2) of the Web Service wizard client and skeleton wizards should be updated to exploit the Web service finder framework (89084) to simplify the process of finding and selecting WSDL. Detailed requirements and design are forthcoming in a design document, a link to which will be appended to this defect. [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=89084 (cbrealey@ca.ibm.com @ 2005-03-25 10:33) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89922">
-<description>[jst.ws] Support Axis Web service creation from EJBs</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Apache Axis supports the creation of Web services bottom-up from EJBs. The tools in WTP for Apache Axis should support this as well. Further details are forthcoming in a design document, a link to which will be added to this bug. (cbrealey@ca.ibm.com @ 2005-04-01 00:00) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89923">
-<description>[jst.ws] Support Axis JUnit testcase generation</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Apache Axis' WSDL2Java tool has support for generating JUnit tests via its '-t' or '-testcase' options. This should be plugged into the Web services framework as a kind of test facility, along side the Sample JSP generator and the Web services explorer. (cbrealey@ca.ibm.com @ 2005-04-01 00:04) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89924">
-<description>[jst.ws] Support generation of Axis clients to non-Web projects</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The current tools in WTP for generating Axis clients restricts their generation to Web projects/modules. The tools should allow the generation of Axis clients to other module types like EJB, Client-Application and plain Java. (cbrealey@ca.ibm.com @ 2005-04-01 00:06) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=92294">
-<description>[jst.ws] Web Service creation wizard does not return newly created web service</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Web Service creation wizard does not return the newly created web service after clicking Finish button (because it does not use any data model but the dynamic wizard/WizardPageManager unlike EJB creation wizard). Hence there is no way to get the newly created web service from the wizard. For example, I want get the ServiceImplBean object reference from the wizard after creating java bean web service. Here is the snippet of code: DynamicWizard wizard = new DynamicWizard(); wizard.setInitialData('org.eclipse.jst.ws.creation.ui.wizard.serverwizard'); wizard.init( PlatformUI.getWorkbench(), new StructuredSelection(service)); WizardDialog dialog= new WizardDialog(PlatformUI.getWorkbench ().getActiveWorkbenchWindow().getShell(), wizard); dialog.create(); dialog.open(); //when user click the finish button I want to get the newly created ServiceImplBean from the wizard. (sdatta@ca.ibm.com @ 2005-04-21 17:08) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=92828">
-<description>[jst.ws] Enhance Web service Server selection dialog/wizard ui</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> This is in response to a comment. The server selection on page 3 should appear similarly in look and feel to the server tools' server selection/targeting UI. (sengpl@ca.ibm.com @ 2005-04-26 16:51) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=93111">
-<description>[jst.ws] Performance: Use the Eclipse 3.1 message bundle facility</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Eclipse has created a new and more efficient message bundling mechanism. Here is a brief description: Standard Java ResourceBundles have quite inefficient space characteristics. Since a running Eclipse tends to have many externalized messages we have implemented a new message bundle story to be used in Eclipse. The mechanism is quite simple and completely generic - it can be used anywhere. Summary of the new approach: -vmessages.properties - this file is same as before except all keys need to be valid Java identifiers. -Each message file has a corresponding Java class. -Each key/value pair in the file has a public static String field whose name is the same as the message key. -When message bundles are loaded, the values of the fields are set to be the values from the messages.properties files. -The message properties files are purged from memory. -When creating a new message: create a field in your Messages.java file create a key/value pair in your messages.properties file where the key name matches the field name to reference the message, simply reference the field (e.g. Messages.my_key) rather than the standard lookup More info at: http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform- core-home/documents/3.1/message_bundles.html (sengpl@ca.ibm.com @ 2005-04-28 08:46) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=96812">
-<description>[jst.ws] Enhance Web service wizard to determine supported servers based on spec levels</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Currently Web service runtime extensions need to explicitly identify their supported servers by listing the server type ids. This means that when a new server is in the picture, the extension XML for the Web service has to be modified to include the new server's type id if the WS runtime wants to expose support for that server. This enhancement would allow to WS runtime to simply spec levels (servlet, JSP, ejb, J2EE) . The wizard would expose support for all servers that support those spec levels. The WS runtime would still be able use server type ids to state support for only certain servers or to exclude specific servers. Determining whether this enhancement is feasible for M5 requires a discussion with server tools team about whether they have (or could provide) API that lets us ask questions about whether a certain server type supported a certain spec. level. (rsinha@ca.ibm.com @ 2005-05-26 11:29) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=82185">
-<description>[releng] map files should be automatically tagged each build</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> As long as we're discussing improving the build process ... I think the map files should be tagged with the build identifier for each build. Well, obviously more important for Milestones, less so for Integration builds, and not important for nightlies ... but if easier to do automatically each time, then I'd suggest tagging each automatically is better than not tagging any automatically, since the later is subject to someone remembering to do it for the important cases. (david_williams@us.ibm.com @ 2005-01-04 16:03) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=82434">
-<description>[releng] Include Base Eclipse automated unit tests in WebTools unit tests</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Seems it would be 'good practice' to run base eclipse unit tests and performance tests, and, I guess pre-reqs automated tests (eventually) at the same time we run the webtools automated tests. I thought of this since there's been a few other bugs that apparently only happen 'in combination' with base things (e.g. conflicts between ant documents, and xml documents). I'm not sure the current tests would have caught those particular problems, but just seems like a good idea. The automated base performance tests, in particular, would be interesting to make sure base function runs at same rate whether or not WTP is added. (david_williams@us.ibm.com @ 2005-01-08 20:21) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=82851">
-<description>[releng] Test scripts should be versioned/in map file</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Currently, the org.eclipse.wtp.releng/testScripts folder is not versioned. Whenever someone creates a new JUnit test and checks it into the HEAD stream, adding it to the test.xml file will cause it to show up in all builds, including the integration build. We need to have a way to allow JUnit plugins to be checked in or modified in the nightly builds, so that they can be tested and only moved to the integration build along with the corresponding code plugins. (deboer@ca.ibm.com @ 2005-01-14 11:11) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89366">
-<description>[releng] Add "extension point capabilities" to the Eclipse API scanner</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Here's a thread that discuss this issue: I think extension points and their related schemas should be part of the API definition. Component.xml does not cover them except in the case that you need to access a Java class or implement a Java interface. I agree that we need to expand our tool coverage to include extension points. Of course, there is still flexibility in declaring an extension point as API. Same goes for any resource that's included in a plug-in. For example, there may be a set of standard icons that we want people to use. Clearly we can't just delete those since it would break clients. Concerning our implementations of other APIs, I think we don't have to do anything since our implementations are already constrained by the semantics of the APIs they implement. We need to preserve that. I think there is a simple way to determine what we need to document as part of our 'API'. Just ask yourself, 'If I change this can I break clients?' If the answer is 'Yes' then we need to document how clients are allowed to use it, and we need to add tool support if possible to help us manage it. To get this process going, I'd like to ask Jeffrey to extend component.xml to include the declaration of extension points (and their schemas), and resources that we are proposing as API. Jeffrey, pls come up with a proposal and post it for review. Arthur Ryman, Rational Desktop Tools Development phone: +1-905-413-3077, TL 969-3077 assistant: +1-905-413-2411, TL 969-2411 fax: +1-905-413-4920, TL 969-4920 mobile: +1-416-939-5063, text: 4169395063@fido.ca intranet: http://labweb.torolab.ibm.com/DRY6/ David M Williams <david_williams@us.ibm.com> Sent by: wtp-dev-admin@eclipse.org 03/17/2005 01:27 PM Please respond to wtp-dev To wtp-dev@eclipse.org cc Subject [wtp-dev] Questions on component.xml There's probably already been discussion and answers provided for some questions that immediately came to my mind while starting (and just staring, mind you :) to define our component.xml files .... but figured if I didn't know the answer, perhaps it might be worth asking here so the answers would be repeated for everyone. One part of our API that gets focus in our component.xml files are classes or interfaces we implement that we want docs, junits, and java doc. That's clear enough. But what about extension points? That's a critical part of a specified API ... how are they represented in component.xml files? A more minor case is 'ids' ... there's some strings defined via plugins or extensions that we expect others to use as API (editor IDs, content menuIDs, are obvious cases). While these can sometimes be redundantly specified in JavaCode to be used as constants (eg. we've done that for our contentTypeIds) there's no hard and fast rule that it has to be, or that it is even always desirable. Its there a suggested way to capture these IDs which are not defined in Java Code? Lastly, the hardest, what about our implementations of other's interfaces? These may be some critical areas to have JUnit test coverage for, but as far as I can tell, that's a whole other problem not related to component.xml and our measurements? But in some cases we may need some amount of doc for? I see this strongly in org.w3c.dom API's ... since we have our own DOM implementation ... we don't expose our implementation as API per se, but we do expose it through the org.w3c.dom interface ... that is, obviously, we expect clients to write code to the org.w3c.dom interface which uses our implementation (our instance being obtained from one API, naturally). If this one is carried to extreme, I think we'd find thousands of cases where we implement base eclipse APIs (either interfaces, or subclassing such popular classes as 'Plugin', 'ITextEditor', etc). Are any of these 'implementations of others APIs' part of the component.xml files? [I don't think so, but its a pretty fine line, sometimes, or gives a distorted picture of 'coverage' if not]. Thanks for any advice. (jeffliu@ca.ibm.com @ 2005-03-29 11:14) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=91587">
-<description>[releng] Component tool could check naming conventions too</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> It would be a nice extra check on 'Eclipse quality code' if the component tool could check for some naming convention violations. For example, if component tool had a list of 'API Classes', then all other classes should have 'internal' in their name, or be default (package) access protected, or marked private. There might be other rules that could be checked, but thought I'd post this here as a general enhancement to consider. (david_williams@us.ibm.com @ 2005-04-15 14:49) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=91599">
-<description>[releng] Best to have "X build declared" flag on webpage</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> This was discussed on wtp-dev, and I see similar confusion on newsgroup, because we do I-build 'warm-ups' many people get an I-build as soon as its on download page, even though we haven't yet determined its suitability. Would be best to have some 'status' on build page, such as 'doing I-build warm-ups', which eventually changes to 'xxx build declared I-build', which would be 'manually' set by one of the project leaders. (david_williams@us.ibm.com @ 2005-04-15 15:50) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=96465">
-<description>[releng] Performance: Pre-build help indexes to improve the performance of the help system</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Pre-build help indexes to improve the performance of the help system. Here's an example: https://bugs.eclipse.org/bugs/show_bug.cgi?id=91695 (jeffliu@ca.ibm.com @ 2005-05-24 13:18) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=96874">
-<description>[releng] API Tool "component" should be seperate from releng component</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Just thought I'd suggest, the API checking tools in releng could (probably) be put in its own component and then 'pulled' into the build, based on version in some map file, like we do other components. This has the advantage 1) that changes released to head would not effect I-build (until 'released'). 2) it would be a more re-usable tool for other teams that might want to make it part of their build process. (david_williams@us.ibm.com @ 2005-05-26 16:56) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=74782">
-<description>[website] Most wanted enhancements / most hated bugs</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> I'd like to see two top lists either easily accessible from or placed directly on http://bugs.eclipse.org/bugs/. One should list the top N (20?) most voted for non-fixed enhancement requests. One should list the top N (20?) most voted for non-fixed bug reports. The point would be to make information about what's bothering people more accessible. (walles@mailblocks.com @ 2004-09-23 11:01) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89081">
-<description>[wst.command] Design a unified wizard/model/command framework</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> There are currently two frameworks in WTP designed to help extenders of the platform create dynamic and extensible wizards, models and commands/operations. An effort is already underway to converge these frameworks, developed under the J2EE and Web services components, into one. This enhancement is being opened to track this work. A design document will be drafted and a link to it appended to this bug. (cbrealey@ca.ibm.com @ 2005-03-25 00:48) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=93869">
-<description>[wst.common] Add a WTP startup performance test</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Add a WTP startup performance test (jeffliu@ca.ibm.com @ 2005-05-05 22:50) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=86437">
-<description>[wst.css] RFE: Add captilization preference for selectors</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> (nitind@us.ibm.com @ 2005-02-24 02:09) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=93445">
-<description>[wst.css] RFE: Add Template support to Content Assist and New Wizard</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The HTML component has support for Templates in its editor's Content Assist and in its New wizard. Could the same kind of support be added for CSS? (nitind@us.ibm.com @ 2005-05-02 15:41) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=93446">
-<description>[wst.dtd] RFE: Add Template support to New DTD Wizard</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The HTML component has support for Templates in its editor's Content Assist and in its New wizard. Could the same kind of support be added at least in the New DTD wizard? (nitind@us.ibm.com @ 2005-05-02 15:42) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=88442">
-<description>[wst.html] WYSIWYG HTML Editor</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Besides the structural HTML editor that already exists, it would be great to have a WYSIWYG (X)HTML editor. This editor could help in quickly designing (X)HTML documents from within Eclipse. The WYSIWYG HTML editing component could also be used in Rich Client applications that are Eclipse-based and thus would benefit a broad user base. There exists a WYSIWYG editing feature (work still in progress) in the GEF subproject (http://www.eclipse.org/gef/team/wysiwyg.html?cvsroot=Tools_Project) that could be used as a basis here. (tderflinger@gmx.net @ 2005-03-18 07:58) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=94283">
-<description>[wst.internet] v1.1/2: TCP/IP monitor</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The TCP/IP monitor is similar to function provided by TPTP. I'm opening this bug to look at ways to make this function common in future releases - do we rely on TPTP, provide simple function in WTP that is extended by TPTP, or are there other options? We'll investigate post v1.0. (deboer@ca.ibm.com @ 2005-05-10 08:32) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=86434">
-<description>[wst.javascript] RFE: Add Show In... target for Outline view</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> M3 test builds Show In... Outline is useful if Link with Editor is disabled. (nitind@us.ibm.com @ 2005-02-24 01:54) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=88902">
-<description>[wst.javascript] Feature Request: More intelligent JS code outlining</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> As it stands, the Javascript editor (while useful) cannot properly outline OO-style javascript, e.g.: function foo(bar) { this.baz = bar; } foo.prototype.buz(bletch) { alert(this.baz + ': ' + bletch); } The current JS outliner doesn't see much - it recognizes foo as a global function, but does not show any of the arguments, members, or methods added to that function's prototype or instance. The Sourceforge JS editor (https://sourceforge.net/projects/jseditor/) actually has a fairly good outlining system which includes some (not all) of this desired functionality, but it would be really excellent to see this kind of thing make it into the WTE. (ctembreull@gmail.com @ 2005-03-23 13:42) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=92331">
-<description>[wst.javascript] Need to document JavaScript parser generator procedure</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> In the interest of 'open' development, we should improve and better document parser generation procedure for java script. What's there now is some heavily hand tweaked code originally generated by sablecc. We should move to more consistent/standard/ non-hand-tweaked methods (and perhaps move to JFlex methodology used elsewhere). (david_williams@us.ibm.com @ 2005-04-22 00:43) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=79045">
-<description>[wst.rdb] Execute single SQL statement in Scrapbook</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Using the execute in the Scrapbook should only execute the currently selected SQL code. If nothing is selected it should then execute the whole thing. (eclipse@juddsolutions.com @ 2004-11-18 20:48) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=79046">
-<description>[wst.rdb] SQL Execute</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The SQL Execute should have a key like ctrl+e for quick execution. Using the menu takes to much time. (eclipse@juddsolutions.com @ 2004-11-18 20:53) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=81035">
-<description>[wst.rdb] DB Qutput SQL History pane should be enhanced</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The pane of the DB Output that should the SQL history need to broken out into its own window. This window should be tied to the SQL Editor windows. This history should be kept from one session to the next. Currently, if you close Eclipse all the history is lost. Error should either be in sent to the Eclipse Error Log or the Console view. This view should just be a history of SQL command executed. Double Clicking on a query should either open a new SQL Editor or load the query in the current SQL Editor. This option should be configurable. (jeff@duska.com @ 2004-12-14 18:45) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=81036">
-<description>[wst.rdb] SQL Editor/ SQL Scrapbook should include its own toolbar</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The SQL Editor could use a handy toolbar on the top of eidt view. I would move the select connection to this toolbar. Here are the buttons I would suggestion * An execute query * An execute selected SQL * Convert to Uppercase * Convert to Lowercase * Standard cut, copy and paste * Convert to langauge - this would take the SQL turn it into the string for Java. This should extendable, so other the community could add other lanaguages. * Cancel for a runnaway query. I would also change it to a dropdown list. We have no need to display a new dialog for such a simple bit of information. I think the execute button would be here. (jeff@duska.com @ 2004-12-14 18:54) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=84858">
-<description>[wst.rdb] The Database connection.</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The available options for the DB is the tied to a DB. I was wondering if we can have a generic category where the end users can try to connect to other databases as their needs specify. e.g. I work with the open source or inmemory DBs like the HSQL and others to get the basic functionality up and then migrate to other DBs. I find it difficult to corelate the DBs at different categories when I am not working with the same. If there is a generic environment which can make the connection based on the driver and classes i link to the connection. (tjmaven@yahoo.com @ 2005-02-09 21:51) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=85094">
-<description>[wst.rdb] SQL Scrapbook editor should provide standard text editing facilities</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Currently the scrapbook editor directly extends the abstract editor which provides none of the standard text editing capabilities such as hyperlinking, hovers, and quickdiff. These are the changes i made to get it going: - SQLScrapbookEditor should extend TextEditor - Use a combined preference store when creating the source viewer (SQLScrapbookEditor constructor) new ChainedPreferenceStore(new IPreferenceStore[] { SqlscrapbookPlugin.getDefault().getPreferenceStore(), EditorsUI.getPreferenceStore()}) - SQLSourceViewerConfiguration should extend TextSourceViewerConfiguration More changes may be required but this gives you basic functionality (brockj@tpg.com.au @ 2005-02-12 19:38) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=85099">
-<description>[wst.rdb] Enable syntax colouring of multiline comments</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Currently only single line comments are hilighted in the SQL scrapbook editor. It would be nice if multiline comments (/* */) were hilighted too. - Add a multiline rule in SQLSourceScanner and SQLCommentScanner for the multiline comment rules.add(new MultiLineRule('/*', '*/', comment)); - Uncomment the multiline rule for multiline comments in SQLPartitionScanner (brockj@tpg.com.au @ 2005-02-12 22:19) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=87488">
-<description>[wst.rdb] Data and Schema Export</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> There should a the possibility to export data from individual tables or from the whole database. Important export formats would be XML (dbunit compatible) or CSV. Also, the generation of a 'create table' schema file would be useful to export the database schema. (tderflinger@gmx.net @ 2005-03-09 08:26) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=90376">
-<description>[wst.rdb] Flexibility to customize SQL keywords by User.</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> There should be a flexibility to customize the keyword list for the SQL or PL/SQL. This gives the user the flexibility to include the keywords which is available in some of the database which may not be included in the default list of the editor. One possible approach would be allow the user to associate a syntax file with a specific structure as define by the editor to the sql editor. As in Textpad. (tjmaven@yahoo.com @ 2005-04-05 16:54) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=94068">
-<description>[wst.server] Action to move servers between workspace and metadata</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> By default, servers (the files containing server definitions) are stored in metadata. There is a preference that allows future servers to be created in the workspace instead, but it is clunky and does not allow existing servers to be moved into the workspace. This feature request is to add an action that allows servers to be moved between workspace and metadata. This will make it easier to share servers across a team. (deboer@ca.ibm.com @ 2005-05-08 16:19) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=73271">
-<description>[wst.sse] Folding for XML/HTML family languages editors</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> It would be very useful to have folding functionality for XML type elements in editors like JEdit does. (eclipse-dev@telus.net @ 2004-09-03 16:02) </detail>")"/>
-</li>
-<ul>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=85776">
-<description href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=85776">depends on 85776</description>
-</a>
-</li>
-</ul>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=82119">
-<description>[wst.sse] ReadOnly state in DOM should be "pay as you go"</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Currently the read-only controller in XMLNode's *always* traverses nodes to keep read-only state accurate. See for example syncChildEditableState(Node child) in NodeContainer If there is never any read-only nodes in document, this can cause *lots* of extra DOM traversals. While these ultimately result in 'no-ops', so not too expensive, for large documents, with lots of elements, can result in a million 'no-ops' for no good reason. A better design would be to quickly decide to do nothing, until at least one node was set to be read-only. (david_williams@us.ibm.com @ 2005-01-03 22:14) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=83449">
-<description>[wst.sse] Put the snippets view into the platform project</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Hello, The snippets view is very useful. It would be good to migrate this plugin from the wst project to the platform project as a basic plugin which can be used for everything else than web projects too... best regards Xavier (xavier.mehaut@free.fr @ 2005-01-21 15:19) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89085">
-<description>[wst.ws] Design Web Services Consumer framework</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> This enhancement is being opened to track work in progress on the definition of a Web Services Consumer framework that, initially, will allow the Web services wizards to add themselves as launchable tools from Web services discovered in the Web Services Explorer, however, the framework will also allow other extenders to contribute tools that eat WSDL to the Web Services Explorer. Further details are forthcoming in a design document, a link to which will be appended to this enhancement. (cbrealey@ca.ibm.com @ 2005-03-25 01:06) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89086">
-<description>[wst.ws] Design extensible Web services validation profile framework</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> This enhancement is being opened to track work in progress on the definition of an extensible preference page and related plumbing that allows the plugging-in of WSDL/XSD conformance or 'ruleset' profiles, initially to be exemplified by the WS-I SSBP and AP profiles. Further details are forthcoming in a design document, a link to which will be appended to this enhancement. (cbrealey@ca.ibm.com @ 2005-03-25 01:10) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89100">
-<description>[wst.ws] Web Services Explorer should use WSFinder framework</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The Web Services Explorer should exploit the WSFinder framework to drive its 'Browse WSDL' feature. Detailed requirements and design are forthcoming in a design document, a link to which will be appended to this defect. (cbrealey@ca.ibm.com @ 2005-03-25 10:22) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=82569">
-<description>[wst.wsdl] Need a WSDL 1.1 to WSDL 2.0 converter</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> As the WSDL 2.0 specification is almost final, we need to prepare a WSDL 1.1 to WSDL 2.0 converter so that already existing WSDL 1.1 document assets can be reused. (kboo@ca.ibm.com @ 2005-01-11 11:09) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=82595">
-<description>[wst.wsdl] Need a JUnit test plugin</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> We need a JUnit test plugin for testing the WSDL model and its bindings. (kboo@ca.ibm.com @ 2005-01-11 14:03) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=90895">
-<description>[wst.wsdl] Enhancement to the WSDL validator</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> We would like the WSDL validator to provide a reporter mechanism that provides error keys. Thanks much -Chida (chidan@us.ibm.com @ 2005-04-09 02:14) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=91288">
-<description>[wst.wsdl] Resizing of WSDL-Graph View</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The current WSDL-Graph Editorview cannot be resized. I am often working on a 1280x1024 display (i.e. 90deg rotated) when editing documents/sources. The current WSDL-editorview items have a fixed size and only use the upper third part of my screen. This is very annoying when the WSDL has a lot of Ports/Messages. Possible enhancements: * Resize the selection-boxes(service/bindings/ports/..) according the current windowsize. Horizontally the itemnamelengths could also be a measure. * Hide/Collapse options for all boxes (currently there is only a hide-button for the 'Bindings') * Graph-Display properties/preferences: Sizes, Fonts, ... Regards, Guus (ggerrits@mtg.de @ 2005-04-13 11:38) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=78369">
-<description>[wst.xml] Selection dtd files in Xml Catalog</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> In Xml catalog make a ability to select dtd file from anywhere in filesystem because very offen we donn't need dtd files in project, but need Tag Completion while edit xml file. (yatsuk@ua.fm @ 2004-11-11 03:57) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=79627">
-<description>[wst.xml] pluggable validator using "services" pattern</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> [this is a captured requirement from news:eclipse.technology.wsvt] > The default validators should probably be registered automatically. I would like to suggest that you employ the Service Discovery pattern made famous by JavaMail and embodied in the commons-discovery framework (although commons-discovery is certainly NOT a prerequisite for this pattern). The short version (for those not familiar) is that your delegate is an interface and you discover (at runtime) those who provide such an interface by asking the ClassLoader for /META-INF/services/${fq_javaInterfaceName} which is a Properties file whose keys are a (possibly singular) list of the concrete implementing class(es) that should be instantiated and used. I have seen this used more and more (I believe wsdl4j uses it also) and I am really sold on its usefulness. (eclipse@mdaniel.scdi.com @ 2004-11-27 15:00) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=81925">
-<description>[wst.xml] add nodes' XPath</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> add a node's XPath to its properties (david_fire4@hotmail.com @ 2004-12-27 05:41) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=81955">
-<description>[wst.xml] add XML graph view</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Add an XML view which is similar to xsd's 'graph' view. (david_fire4@hotmail.com @ 2004-12-28 02:01) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=83071">
-<description>[wst.xml] Make elements/attribute/etc. names in design view editable</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> I would find it very useful to be able to edit an XML document using just the design view. For this to be really feasible, I should be able to change an element(/attribute/etc.) name on the fly, without inserting a new element, preferably by just clicking on the name (lorenzo.donati.bz@tiscali.it @ 2005-01-18 05:19) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=83073">
-<description>[wst.xml] allow word-wrap in design view content column </description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> In order to work on XML files just using the design view, I would find very useful to have the right-hand column of the design view supporting a 'word-wrapping' mode. This would allow to see and edit, in particular, the whole text content of an element without resorting to scrollbars or the like. This will, I think, really speed up editing without messing up the source (important when editing is done by non-developer people) (lorenzo.donati.bz@tiscali.it @ 2005-01-18 05:27) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=83074">
-<description>[wst.xml] Define views to edit attributes and to show text content</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> I would find very useful a view that allows editing of all the attributes of an element selected in the design view of the editor. In some kind of jobs I find myself changing lots of attributes, and having a separate view (maybe together with an option to filter them out of the editor design view, to reduce clutter) would speed things up. For the same reasons, a view allowing editing of just the text content of a node would be great. Some other hints for improving the user interaction could be taken from the xmlshell editor (from www.softgauge.com), which seems to be discontinued (I tried to get a license for it, but that company never replied to me), I used a demo for a while and I really miss many of those features in eclipse. (lorenzo.donati.bz@tiscali.it @ 2005-01-18 05:39) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=84671">
-<description>[wst.xml] Allow copy/paste on XML nodes also between different editors</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> I would find very useful if the design view in XML editor allowed to use copy/cut/paste on nodes. More specifically, I'd like to cut/copy a node and paste it somewhere else, in the same tree or even in a tree in a different XML editor. This would allow quick editing of XML documents as trees. I could, for example, move/copy an entire subtree from an XML file to another without messing with the source view, which would require a lot of error-prone text selection if the subtree to be copied/moved were too big. This would also facilitate insertion of the subtree in the right place, because it would be done looking at the tree model and not at the raw XML source text. If all these operations were supported also through drag and drop, this would be great, but I don't really know if D&D support in eclipse would easily allow a node to be dragged from an open editor to another one. Thanks. (lorenzo.donati.bz@tiscali.it @ 2005-02-08 08:44) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=85348">
-<description>[wst.xml] Need a way to extend schema-derived content assist</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> I need a way to add additional content assist proposals to those generated from the schema in an XML file. On the newsgroup, Nitin wrote: >> For .xml files, we haven't yet defined a way to contribute proposals to our existing Content Assist. and the behavior with conflicting org.eclipse.wst.sse.ui.extendedconfiguration extensions is undefined. << (rrodseth@mac.com @ 2005-02-15 17:53) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=87465">
-<description>[wst.xml] honor system XML Catalogs, please!</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> At the moment, it is quite annoying and a lot of work to add all catalog entries to the XML Catalog Preferences. Also on almost any *x OS/developer machine, there is already an or more system xml catalog[s] with appropriate mappings for the most common doctypes. So it would be very useful, to be able to tell the XML editor, that it should lookup and use DTDs via one or more user specified catalogs (e.g. file:///etc/xml/catalog). BTW: Those catalogs have of course the format specified in http://www.oasis-open.org/committees/entity/spec.html - see also http://xml.apache.org/commons/components/resolver/ (elkner@linofee.org @ 2005-03-08 22:29) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=88444">
-<description>[wst.xml] XML Editor: Display first attribute for an element in design / outline views</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Using 1.0M3 with Eclipse 3.1M5a. Both the outline view and the design editor for XML documents show the tree of XML elements. It would be nice if the first attribute of the element is also displayed, as shown below: - classes - class name='SomeClass' - properties - property name='name' - property name='length' - class name='SomeClassA' - class name='SomeClassB' When you have a lot of similar elements, this little thing makes it very quick to navigate XML documents. Right now I find myself clicking element after element in the outline view until I find the one I want. (cw_murray@yahoo.com @ 2005-03-18 08:14) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=88445">
-<description>[wst.xml] XML Editor: Display first attribute for an element in design / outline views</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Using 1.0M3 with Eclipse 3.1M5a. Both the outline view and the design editor for XML documents show the tree of XML elements. It would be nice if the first attribute of the element is also displayed, as shown below: - classes - class name='SomeClass' - properties - property name='name' - property name='length' - class name='SomeClassA' - class name='SomeClassB' When you have a lot of similar elements, this little thing makes it very quick to navigate XML documents. Right now I find myself clicking element after element in the outline view until I find the one I want. (cw_murray@yahoo.com @ 2005-03-18 08:15) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89392">
-<description>[wst.xml] Customizable keyboard shortcuts for jumping to and selecting matching items in xml.</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> It would be nice to be able to jump to the matching item (quote, bracket, close tag) within an xml document. Also it would be nice to select those things using customizable keyboard shortcuts. I believe you can already select tag contents and contents of parent tags, etc with a keyboard shortcut, but I don't think it is customizable, and was awkward to use. (mbditt@plauditdesign.com @ 2005-03-29 14:35) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89469">
-<description>[wst.xml] [Contribution] XSLT Support, Configurable XML Outline</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Attached is a zip containing my initial contribution of XSLT support for the Eclipse Platform. the archive contains source, class files and documentation(html). the documentation including screenshots is also online at http://eclipsexslt.sourceforge.net/ Features: - Some useful editor extensions making XML/XSLT editing more comfortable. - Configurable XML editor outline - XSLT Launch Configuration. XSLT transformations files can be started immediately via Run/Run As/Orangevolt XSLT , using the Run action in the toolbar or by using the Resource Navigator context menu. - The XSLT process console provides syntax colored XSLT process output supporting hyperlinks for error messages/warnings ( For example if an error occures in file foo.xsl, line 138 you can move the mouse over this the error line and after clicking it the XSLT process console opens/acitvates the file in the editor and jumps to the right line). - XSLT Processor Preferences for controlling/tuning the processor behaviour. - Pluggable XSLT processor support. Use the XSLT processor you want. - XPATH Navigator View. This view is used to execute XPATH expressions against a XML document (or XML selection) opened in Eclipse (see XPATH Navigator). (lars.gersmann@orangevolt.com @ 2005-03-30 03:21) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=91628">
-<description>[wst.xml] Should XML Examples be converted to Eclipse Samples?</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Seems it might be more consistent 'face', more of an 'Eclipse citizen' for WTP. See Help, Welcome for other cases. I'm not positive what the 'platform strategy' is, but writing this up not to forget to investigate. (david_williams@us.ibm.com @ 2005-04-15 21:35) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=92503">
-<description>[wst.xml] xerces config conflicts not well handled.</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Greetings: Im thinking the JKD im using must be missing the parser eclipse is looking for. I had this exception when attempting to open an htm file in the eclipse editor. I believe I'm running the latest builds for everything. I'll attach my configuration as a .txt file. Let me know what else I can do to help here. javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:113) at org.eclipse.wst.xml.uriresolver.internal.XMLCatalogPersistence.load(XMLCatalogPersistence.java:93) at org.eclipse.wst.xml.uriresolver.internal.XMLCatalogPersistence.load(XMLCatalogPersistence.java:64) at org.eclipse.wst.xml.uriresolver.internal.XMLCatalogPersistence.load(XMLCatalogPersistence.java:56) at org.eclipse.wst.xml.uriresolver.internal.DefaultCatalogImpl.<init>(DefaultCatalogImpl.java:33) at org.eclipse.wst.xml.uriresolver.XMLCatalogPlugin.getDefaultXMLCatalog(XMLCatalogPlugin.java:42) at org.eclipse.wst.xml.core.modelquery.XMLCatalogIdResolver.resolveId(XMLCatalogIdResolver.java:62) at org.eclipse.wst.xml.core.modelquery.XMLCatalogIdResolver.resolveId(XMLCatalogIdResolver.java:55) at org.eclipse.wst.html.core.modelquery.XHTMLAssociationProvider.getXHTMLCMDocument(XHTMLAssociationProvider.java:59) at org.eclipse.wst.html.core.modelquery.HTMLModelQueryCMProvider.getCorrespondingCMDocument(HTMLModelQueryCMProvider.java:65) at org.eclipse.wst.common.contentmodel.modelqueryimpl.SimpleAssociationProvider.getCorrespondingCMDocument(SimpleAssociationProvider.java:36) at org.eclipse.wst.common.contentmodel.modelqueryimpl.ModelQueryImpl.getCorrespondingCMDocument(ModelQueryImpl.java:96) at org.eclipse.wst.html.core.commentelement.handlers.CommentElementHandlerForSSI.createElement(CommentElementHandlerForSSI.java:41) at org.eclipse.wst.xml.core.commentelement.impl.CommentElementConfiguration.createElement(CommentElementConfiguration.java:77) at org.eclipse.wst.xml.core.internal.document.XMLModelParser.createCommentElement(XMLModelParser.java:718) at org.eclipse.wst.xml.core.internal.document.XMLModelParser.insertComment(XMLModelParser.java:917) at org.eclipse.wst.xml.core.internal.document.XMLModelParser.insertStructuredDocumentRegion(XMLModelParser.java:1517) at org.eclipse.wst.xml.core.internal.document.XMLModelParser.replaceStructuredDocumentRegions(XMLModelParser.java:2300) at org.eclipse.wst.xml.core.internal.document.XMLModelImpl.newModel(XMLModelImpl.java:575) at org.eclipse.wst.xml.core.internal.document.XMLModelImpl.setStructuredDocument(XMLModelImpl.java:838) at org.eclipse.wst.sse.core.AbstractModelLoader.createModel(AbstractModelLoader.java:115) at org.eclipse.wst.sse.core.internal.FileBufferModelManager.getModel(FileBufferModelManager.java:444) at org.eclipse.wst.sse.core.ModelManagerImpl._getModelFor(ModelManagerImpl.java:400) at org.eclipse.wst.sse.core.ModelManagerImpl.getModelForEdit(ModelManagerImpl.java:1163) at org.eclipse.wst.sse.ui.StructuredTextEditor.doSetInput(StructuredTextEditor.java:1294) at org.eclipse.ui.texteditor.AbstractTextEditor$16.run(AbstractTextEditor.java:2345) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:346) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:291) at org.eclipse.jface.window.ApplicationWindow$1.run(ApplicationWindow.java:624) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69) at org.eclipse.jface.window.ApplicationWindow.run(ApplicationWindow.java:621) at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:1975) at org.eclipse.ui.texteditor.AbstractTextEditor.internalInit(AbstractTextEditor.java:2363) at org.eclipse.ui.texteditor.AbstractTextEditor.init(AbstractTextEditor.java:2390) at org.eclipse.wst.sse.ui.StructuredTextEditor.init(StructuredTextEditor.java:1924) at org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:857) at org.eclipse.ui.internal.EditorManager.busyRestoreEditorHelper(EditorManager.java:1223) at org.eclipse.ui.internal.EditorManager.busyRestoreEditor(EditorManager.java:1102) at org.eclipse.ui.internal.EditorManager$7.run(EditorManager.java:1064) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69) at org.eclipse.ui.internal.EditorManager.restoreEditor(EditorManager.java:1062) at org.eclipse.ui.internal.EditorManager$Editor.getEditor(EditorManager.java:1648) at org.eclipse.ui.internal.EditorManager$Editor.getPart(EditorManager.java:1639) at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:260) at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:126) at org.eclipse.ui.internal.presentations.newapi.PresentablePartFolder.select(PresentablePartFolder.java:268) at org.eclipse.ui.internal.presentations.newapi.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65) at org.eclipse.ui.internal.presentations.newapi.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:391) at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1070) at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1019) at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1223) at org.eclipse.ui.internal.PartStack.add(PartStack.java:406) at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:109) at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:63) at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:267) at org.eclipse.ui.internal.EditorManager$4.run(EditorManager.java:829) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69) at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:809) at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:697) at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:660) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2236) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2165) at org.eclipse.ui.internal.WorkbenchPage.access$7(WorkbenchPage.java:2157) at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2143) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2138) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2123) at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:278) at org.eclipse.ui.actions.OpenWithMenu.access$0(OpenWithMenu.java:270) at org.eclipse.ui.actions.OpenWithMenu$2.handleEvent(OpenWithMenu.java:177) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1012) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2778) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2472) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1570) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1534) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:306) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:228) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:156) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:315) at org.eclipse.core.launcher.Main.basicRun(Main.java:268) at org.eclipse.core.launcher.Main.run(Main.java:942) at org.eclipse.core.launcher.Main.main(Main.java:926) (wbrown@colorfulsoftware.com @ 2005-04-23 16:55) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=93150">
-<description>[wst.xml] Sax content extension point for XML Validator</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> This extension point allows users to implement their own content handlers to the XML Validator so they can add their own validation checking. Using this extension users would add custom validation messages. A patch for the cheat sheet editor plugin will be attached as an example. The extended cheat sheet validator will check to see that the pluginid attribute value in the cheat sheet is valid. (mhutchin@ca.ibm.com @ 2005-04-28 13:43) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=95903">
-<description>[wst.xml] Allow jar: uri's in mappinginfo</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> It would be valuable to be able to refer to DTD/XSD's inside a jar file inside a plugin and not just as now a concrete file. something like: jar:platform:/plugin/my.plugin.id/xsd/schemas.jar!/myschema.xsd (max.andersen@jboss.com @ 2005-05-19 03:49) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=86595">
-<description>[wst.xsd] Export XSD graph view as graphic</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> It would be real nice to be able to export the xsd graph view as some sort of graphics file, for instance jpg or tiff. (vredeveld@imst.de @ 2005-02-25 02:56) </detail>")"/>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-</td>
-</tr>
-<tr>
-<td>
-<table>
-<tr>
-<td valign="top">
-<img height="16" border="0" nosave="" src="../milestone_plans/stylesheets/images/Adarrow.gif"/>
-</td>
-<td>
-<b>1.0 M4</b>
-<ul>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=79655">
-<description>[jst.ejb] Provide for generation of CMP/CMR via JDBC</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> I have some code that may be used as a basis for writing CMP Beans with CMR directly from any existing database schema available via JDBC. It currently works with Oracle 9i and automatically generates LomBoz-style CMP beans complete with XDoclet directives for JBOSS 4.0. It also generates: An XMI file suitable for importing into Poseidon UML and Argo UML. Local and Remote J2EE Service Locators compliant with the Service Locator J2EE Pattern XDoclet code for CMR based on the Fireign Constraints defined in the DB Schema XDoclet code for extra finder methods defined in a supplemental text file An SQL script for regenerating the original schema on other servers I couldn't see any other plans for this, so do you think it would be useful? (matthew@robinsonfamily-au.org @ 2004-11-29 05:23) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=85175">
-<description>[jst.jsp] Access to external Javadoc in JSP pages</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> When coding Java methods within files in the JSP editor (for example, in scriptlets), users should be able to access external Javadoc just like they can in Java files (using Navigate > Open External Javadoc (Shift+F2). (stevebang@gmail.com @ 2005-02-14 14:27) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=81026">
-<description>[wst.rdb] RDB SQL Editor as a replace for SQL Scrapbook</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The SQL Scrapbook UI is nothing like any SQL tool I've used. I would like to see a SQL Editor window. When I do this, I don't expect a wizard to start. Nor do I expect to be saving the query. Most of the time I'm looking for data, I'm not writing SQL that I want to keep. I should be able to save the query, but it should not be forced on me. I would also like to have the multi-pane approach. The user can select what panes are show, but I would expect the top to be a SQL pane, the bottom to be the results grid. (jeff@duska.com @ 2004-12-14 18:11) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=84413">
-<description>[wst.rdb] db output limits row size</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> when accessing an oracle d/b using jdbc and the view server explorer category. the db output when viewing the actual data in table is limited to a fixed number of rows. this ideally would be configurable. i couldn't find a place in the jdbc connection that would cause the rows size to be limited, so it must be in eclipse. eclipse Version: 3.1.0 webtools M2 (stuart_mellanby@hotmail.com @ 2005-02-04 03:54) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89084">
-<description>[wst.ws] Design Web Service Finder framework</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> This enhancement is being opened to track work in progress on the definition of a Web Services Finder framework that will allow extenders to plug-in mechanisms for locating Web services and callers to perform basic lookups. Amongst other things, this will lead to the appearance of Apache Axis Web services in the Project Explorer. Further details are forthcoming in a design document, a link to which will be appended to this enhancement. (cbrealey@ca.ibm.com @ 2005-03-25 01:03) </detail>")"/>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-</td>
-</tr>
-<tr>
-<td>
-<table>
-<tr>
-<td valign="top">
-<img height="16" border="0" nosave="" src="../milestone_plans/stylesheets/images/Adarrow.gif"/>
-</td>
-<td>
-<b>1.0 M5</b>
-<ul>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=82261">
-<description>[J2EE Standard Tools] F: Inlcude standard schemas</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> I understand standard schemas like J2EE Deployment Descriptor ones should be included with WTP so you don't need to be connected to Internet to get some features like Code Assist editing the deployment descriptors. Regards, Chemi. (ordax@es.ibm.com @ 2005-01-05 12:24) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=83459">
-<description>[jst.j2ee] J2EE Project Explorer should be a superset of Package Explorer</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Project Explorer should be a superset of Package Explorer. Here are some things that are missing in Project Explorer * Working Sets * The New History Working Set view * Filters should be a superset of the Java filters dialog. * Go into * Back and Forward history (jeff@duska.com @ 2005-01-21 16:57) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=83530">
-<description>[jst.j2ee] Web-app directory option</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Give the end-user the option to change the web-app-directory for each project (guilherme.silveira@caelum.com.br @ 2005-01-24 09:00) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=85114">
-<description>[jst.j2ee] No progress on WAR import</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> There is no progress monitor on the WAR import wizard. When importing large WAR files, it's annoying because there's no way to tell how long it is going to take. (deboer@ca.ibm.com @ 2005-02-13 15:21) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=85252">
-<description>[jst.j2ee] import an existing project or allow to change its nature</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> While there are many things that can be imported into a new J2EE project, one that is not possible is to import an existing workspace project, that has been created as non-J2EE project. Import is probably a wrong notion for this action, I guess being able to change the project nature of an existing project would be enough. (tomasz@rtsoftware.com @ 2005-02-15 08:27) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=92861">
-<description>[jst.j2ee] add an extension point for constributing a new appserver to "window->preferences->XDoclet->ejbdoclet"</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> ... (navy@shekou.com @ 2005-04-26 23:13) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=86389">
-<description>[wst.common] Change presentation of filtering items in Project Navigator filter dialog [CommonNavigator]</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Currently, the Project Navigator’s filter dialog uses a table to display items that can be individually filtered. This approach is not visually scalable. Using a tree structure to visually organize individual filter contributions by group is more practical. This would allow clients to create filter groups and specify contributions to those groups. The tree items should also support icons. (jcorchis@ca.ibm.com @ 2005-02-23 17:19) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=86391">
-<description>[wst.common] Add support for TabbedPropertyViewer [CommonNavigator]</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Add CommonNavigator support for the TabbedPropertyViewer. Support would include a set of default categories (say general, core, appearance, advanced) for clients contributions. (jcorchis@ca.ibm.com @ 2005-02-23 17:27) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=86385">
-<description>[wst.validation] validation framework should utilize content type</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Validation framework should utilize content type instead of the object filter class for IFile. eg. <filter objectClass='org.eclipse.core.resources.IFile' nameFilter='*.jspf'> </filter> Since content type is more robust, it handles (multiple) file extensions among other things. Also on a side note, it seems that the 'caseSensitive' attribute default value should be 'false', since it doesn't seem likely that someone will NOT want to validate a file if it has an uppcase extension. (pavery@us.ibm.com @ 2005-02-23 17:07) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=86810">
-<description>[wst.validation] Allow exclusions of paths during validation</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> It should be possible to specify exclude settings for the validators. For example, I have a project with a folder where I put all 3-party libs and docs into. If I enable HTML validation this folder should not be scanned. Currently a lot errors and warnings are generated for 3 party docs. (gunnar@wagenknecht.org @ 2005-02-28 04:13) </detail>")"/>
-</li>
-<li>
-<a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=90565">
-<description>[wst.validation] Add lightbulb help when validate on save is greyed out</description>
-</a>
-<font color="8080FF"> [low]</font>
-<img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The validate on save option on the validation preferences page will be greyed out if auto build is not enabled. While this function makes sense it is confusing for users as they do not know how to enable this function. I suggest that a lightbulb help item be placed next to the validate on save preference when it is greyed out informing the user that they must enable auto build to enable this preference. (lmandel@ca.ibm.com @ 2005-04-07 01:55) </detail>")"/>
-</li>
-</ul>
-</td>
-</tr>
-</table>
-</td>
-</tr>
-<table border="0" width="100%" cellpadding="2" cellspacing="5">
-<tbody>
-<tr>
-<td colspan="4" bgcolor="#0080c0" width="100%" align="left" valign="top">
-<b>
-<font face="Arial,Helvetica">
-<font color="#ffffff">Legend</font>
-</font>
-</b>
-</td>
-</tr>
-<tr>
-<td valign="top">
-<img width="14" height="5" src="../milestone_plans/stylesheets/images/progress.gif"/>
-</td>
-<td width="50%">item is under development.</td>
-<td valign="top">
-<img width="10" height="10" src="../milestone_plans/stylesheets/images/glass.gif"/>
-</td>
-<td width="50%">item is under investigation.</td>
-</tr>
-<tr>
-<td valign="top">
-<img width="10" height="10" src="../milestone_plans/stylesheets/images/ok.gif"/>
-</td>
-<td width="50%">item is finished.</td>
-<td valign="top">
-<img width="40" height="12" src="../milestone_plans/stylesheets/images/help.gif"/>
-</td>
-<td width="50%">help wanted</td>
-</tr>
-<tr>
-<td valign="top">
-<img width="10" height="10" src="../milestone_plans/stylesheets/images/defer.gif"/>
-</td>
-<td width="50%">item is deferred.</td>
-<td valign="top">
-<font class="indexsub">
-<img src="../milestone_plans/stylesheets/images/new.gif"/>
-</font>
-</td>
-<td width="50%">new</td>
-</tr>
-</tbody>
-</table>
-<br/>
-</body>
-</html>
diff --git a/development/requirements/index.html b/development/requirements/index.html
deleted file mode 100644
index 7412ed0..0000000
--- a/development/requirements/index.html
+++ /dev/null
@@ -1,256 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../webtools/wtp.css" type="text/css">
-<title>Eclipse Web Tools Platform Project Requirements</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">wtp requirements</font>
-<br>
-<font class="indexsub">Eclipse Web Tools Platform Project Requirements</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The WTP project uses an open process to establish
- requirements. The process is run by the Requirements Group
- who report to the WTP PMC. The Requirements Group gathers
- requirements from all stakeholders, including users,
- developers, vendors, and the Eclipse Foundation, using a
- variety of sources such as newsgroups, mailing lists,
- Bugzilla, and conference calls.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Requirements are summarized in documents that are published
- on this Web site for public review, and then submitted to
- the WTP PMC as input to the release planning process.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Requirements Group</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The requirements process for the WTP project is run by the
- Requirements Group. The current members of this group are:
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ul>
-
-<li>
-
-<a href="../../people/krause.html">Jochen Krause</a>
- - Chair
- </li>
-
-<li>
-
-<a href="../../people/ivanov.html">Ivelin Ivanov</a>
-
-</li>
-
-<li>
-
-<a href="../../people/meijer.html">Paul Meijer</a>
-
-</li>
-
-<li>
-
-<a href="../../people/ryman.html">Arthur Ryman</a>
-
-</li>
-
-<li>
-
-<a href="../../people/williamsT.html">Todd Williams</a>
-
-</li>
-
-</ul>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The Requirements Group holds periodic conference calls. The
- minutes of these calls are listed in the Requirements
- Conference Calls page.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>
- <a href="../requirements_call_notes.html">
- Requirements Conference Calls
- </a>
- </td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">WTP Requirements Documents</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- WTP requirements are described in the following documents:
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>
- <a href="wtp_1_0_plan.html">
- Eclipse Web Tools Project DRAFT 1.0 Plan
- </a>
- </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>
- <a href="wtp_1_5_plan.html">
- Eclipse Web Tools Project DRAFT 1.5 Plan
- </a>
- </td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Web Tools Bugzilla</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Requirements are recorded in Bugzilla using the Request for
- Enhancement (RFE) mechanism. You create a Web Tools RFE by
- entering a new bug and setting its fields as follows:
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<table>
-
-<tr>
-
-<th>Product:</th>
- <td>
- <code>Web Tools</code>
- </td>
-
-</tr>
-
-<tr>
-
-<th>Severity:</th>
- <td>
- <code>enhancement</code>
- </td>
-
-</tr>
-
-</table>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The current list of RFEs is given by a live Bug List query.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>
- <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Web%20Tools&bug_severity=enhancement" target="_top">
- Enter a New Web Tools RFE
- </a>
- </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>
- <a target="_top" href="https://bugs.eclipse.org/bugs/buglist.cgi?product=Web+Tools&bug_status=NEW&bug_severity=enhancement&columnlist=target_milestone,priority,short_short_desc,component">
- Web Tools RFE List
- </a>
- </td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">wtp-requirements Mailing List</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The wtp-requirements mailing list is now available for
- discussions about project requirements. Members of the
- community can raise requirements in the mailing list and
- members of the requirements group will monitor the list and
- create Bugzilla RFEs. Members of the community may also
- create Bugzilla RFEs themselves.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>
- <a href="mailto:wtp-requirements@eclipse.org">
- Post a message to wtp-requirements
- </a>
- </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>
- <a target="_top" href="http://dev.eclipse.org/mhonarc/lists/wtp-requirements/maillist.html">
- wtp-requirements Archives
- </a>
- </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>
- <a href="http://dev.eclipse.org/mailman/listinfo/wtp-requirements" target="_top">
- wtp-requirements Information
- </a>
- </td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Archived Web Tools Requirements</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Initial requirements for WTP were captured on a wiki. New
- requirements should be discussed in the mailing list and
- recorded in Bugzilla.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>
- <a target="_top" href="https://wiki.objectweb.org/eclipse-webtools/Wiki.jsp?page=WebToolsRequirements">
- Web Tools Requirements Wiki
- </a>
- </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>
- <a href="requirements.html">
- Web Tools Project requirements and use cases for Release 0.7
- </a>
- </td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/development/requirements/index.xml b/development/requirements/index.xml
deleted file mode 100644
index cd38eff..0000000
--- a/development/requirements/index.xml
+++ /dev/null
@@ -1,153 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?xml-stylesheet type="text/xsl" href="../../wtp.xsl"?>
-<html>
- <head>
- <meta name="root" content="../../.." />
- <title>Eclipse Web Tools Platform Project Requirements</title>
- </head>
- <body>
- <h1>wtp requirements</h1>
- <p>
- The WTP project uses an open process to establish
- requirements. The process is run by the Requirements Group
- who report to the WTP PMC. The Requirements Group gathers
- requirements from all stakeholders, including users,
- developers, vendors, and the Eclipse Foundation, using a
- variety of sources such as newsgroups, mailing lists,
- Bugzilla, and conference calls.
- </p>
- <p>
- Requirements are summarized in documents that are published
- on this Web site for public review, and then submitted to
- the WTP PMC as input to the release planning process.
- </p>
- <h2>Requirements Group</h2>
- <p>
- The requirements process for the WTP project is run by the
- Requirements Group. The current members of this group are:
- </p>
- <ul>
- <li>
- <a href="../../people/krause.html">Jochen Krause</a>
- - Chair
- </li>
- <li>
- <a href="../../people/ivanov.html">Ivelin Ivanov</a>
- </li>
- <li>
- <a href="../../people/meijer.html">Paul Meijer</a>
- </li>
- <li>
- <a href="../../people/ryman.html">Arthur Ryman</a>
- </li>
- <li>
- <a href="../../people/williamsT.html">Todd Williams</a>
- </li>
- </ul>
- <p>
- The Requirements Group holds periodic conference calls. The
- minutes of these calls are listed in the Requirements
- Conference Calls page.
- </p>
- <h3>
- <a href="../requirements_call_notes.html">
- Requirements Conference Calls
- </a>
- </h3>
- <h2>WTP Requirements Documents</h2>
- <p>
- WTP requirements are described in the following documents:
- </p>
- <h3>
- <a href="wtp_1_0_plan.html">
- Eclipse Web Tools Project DRAFT 1.0 Plan
- </a>
- </h3>
- <h3>
- <a href="wtp_1_5_plan.html">
- Eclipse Web Tools Project DRAFT 1.5 Plan
- </a>
- </h3>
- <h2>Web Tools Bugzilla</h2>
- <p>
- Requirements are recorded in Bugzilla using the Request for
- Enhancement (RFE) mechanism. You create a Web Tools RFE by
- entering a new bug and setting its fields as follows:
- </p>
- <table>
- <tr>
- <th>Product:</th>
- <td>
- <code>Web Tools</code>
- </td>
- </tr>
- <tr>
- <th>Severity:</th>
- <td>
- <code>enhancement</code>
- </td>
- </tr>
- </table>
- <p>
- The current list of RFEs is given by a live Bug List query.
- </p>
- <h3>
- <a
- href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Web%20Tools&bug_severity=enhancement"
- target="_top">
- Enter a New Web Tools RFE
- </a>
- </h3>
- <h3>
- <a target="_top"
- href="https://bugs.eclipse.org/bugs/buglist.cgi?product=Web+Tools&bug_status=NEW&bug_severity=enhancement&columnlist=target_milestone,priority,short_short_desc,component">
- Web Tools RFE List
- </a>
- </h3>
- <h2>wtp-requirements Mailing List</h2>
- <p>
- The wtp-requirements mailing list is now available for
- discussions about project requirements. Members of the
- community can raise requirements in the mailing list and
- members of the requirements group will monitor the list and
- create Bugzilla RFEs. Members of the community may also
- create Bugzilla RFEs themselves.
- </p>
- <h3>
- <a href="mailto:wtp-requirements@eclipse.org">
- Post a message to wtp-requirements
- </a>
- </h3>
- <h3>
- <a target="_top"
- href="http://dev.eclipse.org/mhonarc/lists/wtp-requirements/maillist.html">
- wtp-requirements Archives
- </a>
- </h3>
- <h3>
- <a
- href="http://dev.eclipse.org/mailman/listinfo/wtp-requirements"
- target="_top">
- wtp-requirements Information
- </a>
- </h3>
- <h2>Archived Web Tools Requirements</h2>
- <p>
- Initial requirements for WTP were captured on a wiki. New
- requirements should be discussed in the mailing list and
- recorded in Bugzilla.
- </p>
- <h3>
- <a target="_top"
- href="https://wiki.objectweb.org/eclipse-webtools/Wiki.jsp?page=WebToolsRequirements">
- Web Tools Requirements Wiki
- </a>
- </h3>
- <h3>
- <a href="requirements.html">
- Web Tools Project requirements and use cases for Release 0.7
- </a>
- </h3>
-
- </body>
-</html>
diff --git a/development/requirements/rdf2milestone.xsl b/development/requirements/rdf2milestone.xsl
deleted file mode 100644
index 76829d5..0000000
--- a/development/requirements/rdf2milestone.xsl
+++ /dev/null
@@ -1,81 +0,0 @@
-<?xml version="1.0"?>
-<!--
-
- Transforms Bugzilla RDF report into milestone format.
-
- Change Log:
-
- 2005-06-16: Arthur Ryman <ryman@ca.ibm.com>
- - created
-
--->
-<xsl:stylesheet version="1.0"
- xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
- xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
- xmlns:bz="http://www.bugzilla.org/rdf#"
- xmlns:nc="http://home.netscape.com/NC-rdf#" exclude-result-prefixes="rdf bz nc" >
-
- <xsl:output method="xml" indent="yes" />
-
- <xsl:key name="target_milestones" match="//bz:target_milestone"
- use="." />
-
- <xsl:template match="/">
-
- <plan xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:noNamespaceSchemaLocation="../../../../development/milestone_plans/milestonePlan.xsd">
- <component name="Overview of" subproject="any">
- <milestone name="Milestones">
- <title>
- <xsl:text>All Milestones - </xsl:text>
- <xsl:value-of select="count(//bz:bug)" />
- <xsl:text> Enhancement Requests</xsl:text>
- </title>
- <xsl:call-template name="categories" />
- </milestone>
- </component>
- </plan>
-
- </xsl:template>
-
- <xsl:template name="categories">
- <xsl:for-each select="//bz:target_milestone">
- <xsl:sort select="." />
- <xsl:if
- test="generate-id(.)=generate-id(key('target_milestones',.)[1])">
- <category name="{.}">
- <xsl:variable name="target_milestone" select="." />
- <xsl:for-each
- select="//bz:bug[bz:target_milestone=$target_milestone]">
- <xsl:sort select="bz:component" />
- <xsl:sort select="bz:id" />
- <xsl:variable name="priority">
- <xsl:choose>
- <xsl:when test="bz:priority='P1'">
- <xsl:text>high</xsl:text>
- </xsl:when>
- <xsl:when test="bz:priority='P2'">
- <xsl:text>medium</xsl:text>
- </xsl:when>
- <xsl:otherwise>
- <xsl:text>low</xsl:text>
- </xsl:otherwise>
- </xsl:choose>
- </xsl:variable>
- <item priority="{$priority}" status="new">
- <description>
- <xsl:text>[</xsl:text>
- <xsl:value-of select="bz:component" />
- <xsl:text>] </xsl:text>
- <xsl:value-of
- select="bz:short_short_desc" />
- </description>
- <bugzilla link="{@rdf:about}" />
- </item>
- </xsl:for-each>
- </category>
- </xsl:if>
- </xsl:for-each>
- </xsl:template>
-
-</xsl:stylesheet>
diff --git a/development/requirements/requirements.html b/development/requirements/requirements.html
deleted file mode 100644
index 6690bea..0000000
--- a/development/requirements/requirements.html
+++ /dev/null
@@ -1,429 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head>
-
- <title>Eclipse Webtools Project Wiki: Web Tools Requirements</title><link rel="stylesheet" href="http://www.eclipse.org/default_style.css">
- <style type="text/css">h3 {font-family: arial, helvetica, geneva; font-size: 10pt; font-weight: bold ; color: #ffffff; background-color: #0080c0; border: 2px solid #0080c0; } </style>
-</head>
-
-<body>
-
-<table border="0" cellspacing="5" cellpadding="2" width="100%">
- <tbody><tr>
- <td align="left" width="60%"><font class="indextop">eclipse web tools<br>platform project</font><br><font class="indexsub">Web Tools Requirements</font></td>
- <td width="40%"> </td>
- </tr>
-</tbody></table>
-
-
-<table border="0" cellspacing="5" cellpadding="2" width="100%">
- <tbody><tr>
- <td valign="top">
-
-
-<h3>Web Tools Project requirements and use cases</h3>
-<p>
-</p><h4>This is a draft document intended to get community feedback - gathering,
-structuring and prioritizing requirements is work in progress! A document
-incorporating your feedback and more details on requirements / use cases will be
-published here on August, 24th. </h4>
-<p>Please provide feedback to this document via the newsgroup:
-<a href="news://news.eclipse.org:119/eclipse.webtools">
-news://news.eclipse.org/eclipse.webtools</a> </p>
-<h4>The listed requirements are centered around three themes that
-we plan to concentrate on for the first milestones:</h4>
-<p>
-<a class="wikipage" href="#StructuredEditor">structuredEditor </a>
-</p><p>
-<a class="wikipage" href="#ServerTooling">serverTooling </a>
-</p><p>
-<a class="wikipage" href="#ProjectLayout">projectLayout</a> (a more extensive
-document is work in progress and will be published with the next revision of
-this document on
-August, 24th)</p><p>
-</p><h4>Overall goals / requirements from the original project proposal</h4>
-<ul>
-<li> Seamlessly extend the eclipse user experience
-</li>
-<li> provide an exstensible framework - not end user tools only</li>
-<li> Provide modular design of tools for enabling separate tool deliveries for
-various groups of developers</li>
-</ul>
-<h4>General comments</h4>
-<ul>
-<li> UI scalability needs some love early on. It feels like the size of
-context sensitive menus in the Package explorer doubled in size after I
-installed the IBM contribution, even when I'm just doing desktop Java
-apps. Many of the plug-ins instantiate themselves at startup time too.
-WTP should be there when you need it but out of the way when you don't.
-<a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01125.html">Ed Burnette</a><!-- Image does not exist. <img class="outlink" src="requirements_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> track 3.1 development, "take advantage of every new feature" -
-consider that any WTP early adopters and testers are more than likely
-going to be 3.1 early adopters and testers too. <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01125.html">Ed Burnette</a><!-- Image does not exist. <img class="outlink" src="requirements_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> Pushing down features into the platform: the Internet prefernce
-page - that should just replace the setting in Install/Update because
-they interfere with each other. Another example would be the new
-content type framework. Maybe that nice web browser window too, so
-everybody can stop reinventing it. <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01125.html">Ed Burnette</a><!-- Image does not exist. <img class="outlink" src="requirements_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> Beginners have problems with configuration issues
-</li>
-</ul>
-<p>
-</p><hr>
-<p>
-</p><h4>Requirements that will become relevant for future milestones</h4>
-<a class="wikipage" href="#FutureRequirements">Future Requirements</a>
-<p>
-</p><h4>Frequently requested requirements / features that are out of scope of this project</h4>
-<a class="wikipage" href="#OutOfScope">outOfScope</a>
-<hr size="1" noshade="noshade">
-
- </td>
- </tr>
-
-</tbody></table>
-
-<h3> S<a name="StructuredEditor">tructured Editor</a></h3>
-<p>
-</p><h4>Community Input</h4>
-<p>
-</p><ul>
-<li> HTML, XML, and JSP are the top three in importance <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01125.html">Ed Burnette</a><!-- Image does not exist. <img class="outlink" src="structured_editor_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> support for JSP 2.0 <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01013.html">Martin Kuhn</a><!-- Image does not exist. <img class="outlink" src="structured_editor_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> debug of jsp tags(files) and EL <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01122.html">Rui Figueira</a><!-- Image does not exist. <img class="outlink" src="structured_editor_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> Highlighting corrently and content assist will be enough <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01127.html">Stephen Duncan Jr</a><!-- Image does not exist. <img class="outlink" src="structured_editor_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> use JDT preferences for syntax highlighting <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01127.html">Stephen Duncan Jr</a><!-- Image does not exist. <img class="outlink" src="structured_editor_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> handle file includes of other JSP files (e.g. shared import
-statements, multiple includes, as well as useBean statements should not
-lead to error markers if they are no real problems) <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01127.html">Stephen Duncan Jr</a><!-- Image does not exist. <img class="outlink" src="structured_editor_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> xml editor <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01123.html">Haris Peco</a><!-- Image does not exist. <img class="outlink" src="structured_editor_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> Content assist for Java scriptlets should be at the same level as the JDT <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01127.html">Stephen Duncan Jr</a><!-- Image does not exist. <img class="outlink" src="structured_editor_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> HTML, CSS, JavaScript basic syntax highlighting is a necessity <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01127.html">Stephen Duncan Jr</a><!-- Image does not exist. <img class="outlink" src="structured_editor_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> support for jsp-document (xml-syntax) <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg00825.html">Nicolas Youna</a><!-- Image does not exist. <img class="outlink" src="structured_editor_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> let DHTML resources coexist (leading to errors with ibm contribution as they are recognized as xml) <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01103.html">David Williams</a><!-- Image does not exist. <img class="outlink" src="structured_editor_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> support for Java refactorings (e.g. method rename or signature
-changes) should work as if JSPs were Java classes - no need for
-additional checks <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01157.html">Richard Nemec</a><!-- Image does not exist. <img class="outlink" src="structured_editor_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> recognition and code assist for locally defined (e.g. by custom tags) JavaBeans <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01157.html">Richard Nemec</a><!-- Image does not exist. <img class="outlink" src="structured_editor_files/out.png" alt="" width="6" height="6">-->
-</li>
-</ul>
-<p>
-</p><h4>From the proposal</h4>
-<ul>
-<li> Quick Fixes
-</li>
-<li> Refactoring support
-</li>
-<li> Enable hybrid source editing (HTML in Java, SQL in Java)
-</li>
-<li> Extensibility with visual editors, form based views</li>
-<li> Develop Web pages based on JavaScript and CSS</li>
-</ul>
-<p>
-</p><h4>Other</h4>
-<p>
-</p><ul>
-<li> underlying platform shall be extensible for future additions of other languages <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01127.html">Stephen Duncan Jr</a><!-- Image does not exist. <img class="outlink" src="structured_editor_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> jsp editor, xml editor to work independently of eclipse project
-settings (e.g. with setting tablibs as properties in the project)<a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01124.html">Pak, Young-rok</a><!-- Image does not exist. <img class="outlink" src="structured_editor_files/out.png" alt="" width="6" height="6">-->
-</li>
-</ul>
-<p>
-</p><ul>
-<li> Handy tools for HTML, CSS, and Javascript are nice bonuses. <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01127.html">Stephen Duncan Jr</a><!-- Image does not exist. <img class="outlink" src="structured_editor_files/out.png" alt="" width="6" height="6">-->
-</li>
-</ul>
-<p>
-</p><p>
-</p><ul>
-<li> javascript debugging (maybe a first implementation could wrap the venkman debugger or something like that) <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01122.html">Rui Figueira</a><!-- Image does not exist. <img class="outlink" src="structured_editor_files/out.png" alt="" width="6" height="6">-->
-</li>
-</ul>
-<p>
-</p><p>
-</p><h4>Comments</h4>
-<p>I don't think jsp preview is useful.
-
-<br clear="all">
-
-</p>
-<p> </p>
-
-
-<h3><a name="ServerTooling">Server Tooling</a></h3>
-<p>
-</p><h4>Community Input</h4>
-<p>
-</p><ul>
-<li> Anything you can do with the old Sysdeo plug-in, you want the
-first version of Web Tools to be able to do, only better (frequent
-request, take a closer look at sysdeo) <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01125.html">Ed Burnette</a><!-- Image does not exist. <img class="outlink" src="server_tooling_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> JSP debugging is needed
-</li>
-<li> debug of jsp tags(files) and EL <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01122.html">Rui Figueira</a><!-- Image does not exist. <img class="outlink" src="server_tooling_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> "generic server tooling" like in Lomboz <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg00978.html">Gorkem Ercan</a><!-- Image does not exist. <img class="outlink" src="server_tooling_files/out.png" alt="" width="6" height="6">-->
-</li>
-</ul>
-<p>
-</p><h4>From the proposal</h4>
-<ul>
-<li> Develop and publish a static HTML site
-</li>
-<li> Deploy an applet on a given HTTP server
-</li>
-<li> Provide Exemplar Server Tools for open-technology server runtimes such as Apache Tomcat, JOnAS, JBoss, J2EE 1.4 SDK and others
-</li>
-</ul>
-<p>
-</p><h4>Comments</h4>
-<p>
-Server tool is not esential. Most WAS servers provide convenient tool
-to deploy, start, stop. And by just using eclipse run setting, that
-tools can be used. Priority of this job should be lower. </p><p>
-Don't really have a strong interest in this at the moment. Generally
-we're fine with using ANT to push our files to our development Tomcat
-server for testing, and using the Tomcat provided tools for the
-redeploying when necessary, etc. I don't really have a need for Eclipse
-support for servers.
-<a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01127.html">Stephen Duncan Jr</a><!-- Image does not exist. <img class="outlink" src="server_tooling_files/out.png" alt="" width="6" height="6">-->
-
-
-</p>
-<p> </p>
-
-
-<h3><a name="ProjectLayout">Project layout</a></h3>
-<p>
-</p>
-<p>
-</p><p><b>A more extensive
-definition of requirements for the project layout is work in progress and will be published with the next revision of
-this document on August, 24th</b></p>
-<h4>Community Input</h4>
-<p>
-</p><ul>
-<li> multiple sourcepath <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01124.html">Pak, Young-rok</a><!-- Image does not exist. <img class="outlink" src="project_layout_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> flexible name of web content directory, document files directory, etc.<a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01124.html">Pak, Young-rok</a><!-- Image does not exist. <img class="outlink" src="project_layout_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> possibility to divide source path into three parts: src/java for java source, src/conf for resources, src/test for test classes<a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01124.html">Pak, Young-rok</a><!-- Image does not exist. <img class="outlink" src="project_layout_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> multiple projects to be assebmled to one J2EE application <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01088.html">Rocky Burt</a><!-- Image does not exist. <img class="outlink" src="project_layout_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> dependencies to standard java projects and automatic packaging for deployment
-</li>
-<li> clearly separate the project source structure from the build and deploy structure and artifacts. <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg00811.html">Gabriele Garuglieri</a><!-- Image does not exist. <img class="outlink" src="project_layout_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> possibility of changing the WebContent src folder name on one
-single Web project. (ibm contribution only offers a global action to
-rename the WebContent folder name for all web projects in the
-workspace) <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg00964.html">Vijay Bhadriraju</a><!-- Image does not exist. <img class="outlink" src="project_layout_files/out.png" alt="" width="6" height="6">-->
-</li>
-</ul>
-<p>
-</p><p>
-</p><ul>
-<li> specifying taglibs as a property of project (like jars for java
-compiling) would be a very interessting feature (enabling editor to
-work with jsp pages without depending on typical web project
-structures) <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg00825.html">Nicolas Youna</a><!-- Image does not exist. <img class="outlink" src="project_layout_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> name with a period (ie demo.war) as the base directory (helps to avoid deploy step on jboss) <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg00987.html">Tony BenBrahim</a><!-- Image does not exist. <img class="outlink" src="project_layout_files/out.png" alt="" width="6" height="6">-->
-</li>
-</ul>
-<p>
-</p><p>
-</p><h4>Example project structures</h4>
-<p>
-</p><p>
-Project
-</p><p>
-...src<br>
-.....packages<br>
-...site<br>
-.....meta-inf<br>
-.....web-inf<br>
-.....supt<br>
-.......css<br>
-.......imgs<br>
-.......inc<br>
-.......js<br>
-</p><p>
-<a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01127.html">Stephen Duncan Jr</a><!-- Image does not exist. <img class="outlink" src="project_layout_files/out.png" alt="" width="6" height="6">-->
-</p><p>
-So for war file:
-</p><ul>
-<li> project1/src/java/package/goes/Here.java
-</li>
-<li> project1/src/webapp/index.html
-</li>
-<li> project1/src/webapp/WEB-INF/web.xml
-</li>
-</ul>
-<p>
-For ejb jar file:
-</p><ul>
-<li> project2/src/java/package/goes/Here.java
-</li>
-<li> project2/src/ejb/META-INF/ejb-jar.xml
-</li>
-</ul>
-<p>
-For J2EE ear packages:
-</p><ul>
-<li> project3/src/application/META-INF/application.xml
-</li>
-</ul>
-<p>
-Note, that ear module is separate from war/ejbjar modules.
-It just assembles war/ejbjars created in separate modules.
-</p><p>
-<a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01126.html">Tomasz Pik</a><!-- Image does not exist. <img class="outlink" src="project_layout_files/out.png" alt="" width="6" height="6">-->
-</p><p>
-</p><ul>
-<li> another suggestion
-</li>
-</ul>
-<p>
-/myProjet<br>
-.../src : java sources<br>
-.../env : environment specific folder<br>
-....../env1 : contains env1 environment files<br>
-....../env2 : contains env2 environment files<br>
-.../etc : other files (.properties .xml ...)<br>
-.../web : web root (without a WEB-INF folder)<br>
-.../lib : lib required for the project<br>
-</p><p>
-<a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg00827.html">Nicolas Youna</a><!-- Image does not exist. <img class="outlink" src="project_layout_files/out.png" alt="" width="6" height="6">-->
-
-
-</p>
-<p> </p>
-
-
-<h3><a name="FutureRequirements">Requirements that will become relevant for
-future milestones</a></h3>
-<p>
-</p><h4>From the community</h4>
-<p>
-</p><ul>
-<li> database explorer (better) <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01123.html">Haris Peco</a><!-- Image does not exist. <img class="outlink" src="other_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> java server faces <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01123.html">Haris Peco</a><!-- Image does not exist. <img class="outlink" src="other_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> ant based build files <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg00978.html">Gorkem Ercan</a><!-- Image does not exist. <img class="outlink" src="other_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> The tools must allow to export their configured actions as Ant
-files that can be saved with projects, run separately and/or reimported
-by others developers reobtaining the original configuration. <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg00811.html">Gabriele Garuglieri</a><!-- Image does not exist. <img class="outlink" src="other_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> annotations based EJB tools like in Lomboz <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg00978.html">Gorkem Ercan</a><!-- Image does not exist. <img class="outlink" src="other_files/out.png" alt="" width="6" height="6">-->
-</li>
-</ul>
-<p>
-</p><ul>
-<li> Web Services Explorer implemented in SWT as a regular Eclipse view <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg00971.html">Ed Burnette</a><!-- Image does not exist. <img class="outlink" src="other_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> Mac OS X support, JSP debugging on OS X <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg00974.html">Rob Williams</a><!-- Image does not exist. <img class="outlink" src="other_files/out.png" alt="" width="6" height="6">-->
-</li>
-</ul>
-<p>
-</p><ul>
-<li> XSLT Editing and debugging <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01023.html">Igor Malinin</a><!-- Image does not exist. <img class="outlink" src="other_files/out.png" alt="" width="6" height="6">-->
-</li>
-</ul>
-
-
-
-
-<h4>From the proposal</h4>
-<p>
-</p><ul>
-<li>Develop SQL statements and generate static Web pages from database queries
-</li>
-<li>Develop XSD and XSLT for XML based Web pages and Web services </li>
-<li>Develop and publish WSDL schema on UDDI registries </li>
-<li>Explore UDDI registries and dynamically test Web services via WSDL </li>
-<li>Test Web services for WS-I compliance</li>
-<li>Develop a J2EE Web Application
-<ul>
- <li>Develop tag libraries </li>
- <li>Develop Servlet Filters </li>
- <li>Package the contents of war files </li>
- <li>Edit deployment descriptors </li>
-</ul>
-</li>
-<li>Develop an EJB Application
-<ul>
- <li>Add an EJB </li>
- <li>Add methods/fields/relationships/mappings to an EJB </li>
- <li>Edit the deployment descriptors </li>
- <li>Package the contents of an EJB-JAR
- <ul>
- <li>Generate necessary classes </li>
- <li>Run, Test, Debug EJBs </li>
- </ul>
- </li>
-</ul>
-</li>
-<li>Develop an Enterprise Application
-<ul>
- <li>Assemble an enterprise application
- <ul>
- <li>Add, remove Web Applications, EJBs </li>
- <li>Add, remove client applications </li>
- </ul>
- </li>
- <li>Package the contents of an ear </li>
- <li>Edit the deployment descriptors </li>
- <li>Run, Test, Debug an Enterprise Applications </li>
-</ul>
-</li>
-<li>Import existing Web applications, EJBs, and ears into a project
-<ul>
- <li>Enhance the "PetStore" blue-print application </li>
-</ul>
-</li>
-<li>Develop Java Web Services
-<ul>
- <li>Develop a Web Service based on Session Beans </li>
- <li>Develop a Web Service based on JavaBeans </li>
- <li>Create Web Service Clients </li>
-</ul>
-</li>
-</ul>
-<p> </p>
-
-<h3><a name="OutOfScope">Frequently requested features that are out of scope of this project</a></h3>
-<p>
-</p><ul>
-<li> Struts support
-</li>
-<li> hibernate support <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01123.html">Haris Peco</a><!-- Image does not exist. <img class="outlink" src="outOfScope_files/out.png" alt="" width="6" height="6">-->
-</li>
-<li> spring support <a class="external" href="http://dev.eclipse.org/newslists/news.eclipse.webtools/msg01123.html">Haris Peco</a><!-- Image does not exist. <img class="outlink" src="outOfScope_files/out.png" alt="" width="6" height="6">-->
-</li>
-</ul>
-
-<p>For more information about what is "in scope" versus "out of scope" please
-see our <a href="http://www.eclipse.org/webtools/project-scope.html">project
-scope</a>.</p>
-
-</body></html>
\ No newline at end of file
diff --git a/development/requirements/wtp_1_0_plan.html b/development/requirements/wtp_1_0_plan.html
deleted file mode 100644
index bd7be50..0000000
--- a/development/requirements/wtp_1_0_plan.html
+++ /dev/null
@@ -1,337 +0,0 @@
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
-<title>Eclipse Web Tools Project DRAFT 1.0 Plan</title>
-</head>
-
-<body>
-
-<h1>Eclipse Web Tools Project DRAFT 1.0 Plan</h1>
-
-<p><b>Initial draft</b> Mai 25, 2005 (by Jochen Krause / WTP Requirements Group
-based on WTP Project 0.7 Plan and Eclipse Project DRAFT 3.2 Plan)</p>
-<p><i>
-Please send comments about this <b>draft plan</b> to the </i>wtp-requirements@eclipse.org
-<i>mailing list.</i></p>
-
-<p>This document lays out the feature and API set for the next feature release
-of Eclipse Web Tools after 0.7, designated release 1.0. This document is a draft
-and is subject to change, we welcome all feedback. </p>
-<p>Web Tools 1.0 will be compatible with Eclipse 3.1 Releases.</p>
-<p>Plans do not materialize out of nowhere, nor are they entirely static. To
-ensure the planning process is transparent and open to the entire Eclipse
-community, we (the Eclipse Web Tools Requirement Group & the Web Tools PMC) post
-plans in an embryonic form and revise them throughout the release cycle. </p>
-<p>The first part of the plan deals with the important matters of release
-deliverables, release milestones, target operating environments, and
-release-to-release compatibility. These are all things that need to be clear for
-any release, even if no features were to change. </p>
-<p>The remainder of the plan consists of plan items for the two subprojects
-under the Eclipse Web Tools top-level project. Each plan item covers a feature
-or API that is to be added to Web Tools, or some aspect of Web Tools that is to
-be improved. Each plan item will have its own entry in the Eclipse bugzilla
-database, with a title and a concise summary (usually a single paragraph) that
-explains the work item at a suitably high enough level so that everyone can
-readily understand what the work item is without having to understand the
-nitty-gritty detail. </p>
-<p>Not all plan items represent the same amount of work; some may be quite
-large, others, quite small. Some plan items may involve work that is localized
-to a single Platform component; others may involve coordinated changes to
-several components; other may pervade the entire Platform. Although some plan
-items are for work that is more pressing that others, the plan items appear in
-no particular order. </p>
-<p>With the previous release as the starting point, this is the plan for how we
-will enhance and improve it. Fixing bugs, improving test coverage,
-documentation, examples, performance tuning, usability, etc. are considered
-routine ongoing maintenance activities and are not included in this plan unless
-they would also involve a significant change to the API or feature set, or
-involve a significant amount of work. The intent of the plan is to account for
-all interesting feature work. </p>
-<p> </p>
-<p>The current status of each plan item is noted: </p>
-
- <p><b>High Priority</b> plan item - A
- high priority plan item is one that we have decided to address for the
- release (committed).</p>
- <p><b>Medium Priority</b> plan item -
- A medium priority plan item is one that we are considering addressing for
- the release. Although we are actively investigating it, we are not yet in a
- position to commit to it, or to say that we won't be able to address it. </p>
- <p><b>Low Priority </b>plan item A
- low priority plan item is one that we addressed for a release we will only
- address that item if one component has addressed all high and medium
- priority items </p>
- <p><b>Deferred</b> plan item - A
- reasonable proposal that will not make it in to this release for some reason
- is marked as deferred with a brief note as to why it was deferred. Deferred
- plan items may resurface as committed plan items at a later point.</p>
-
-<h2>Release deliverables</h2>
-<p>The release deliverables have the same form as previous releases, namely: </p>
-<ul>
- <li>Source code release for Eclipse WTP
- Project, available as versions tagged "R1_0" in the Eclipse WTP Project
- </li>
- <li>CVS repository</li>
- <li>Eclipse WTP runtime binary and SDK
- download with all Eclipse pre-reqs (downloadable).</li>
- <li>Eclipse WTP runtime binary and SDK
- download (downloadable).</li>
-</ul>
-
-<h2>Release milestones</h2>
-
-<p>Release milestone occurring at roughly 6 week intervals and will be
-compatible with Eclipse 3.1 releases. Compatibility with Eclipse 3.2 milestone
-builds is not covered during the 1.0 release cycle. Eclipse 3.2 compatibility
-will be achieved with the Web Tools release following the 1.0 release, targeted
-for summer 2006. </p>
-<p>The milestones are:</p>
-<ul>
- <li>Friday September 23, 2005 - Milestone 8
- (1.0 M8) - stable build</li>
- <li>Friday Nov. 18, 2005 - Milestone 9
- (1.0 M9) - stable build</li>
- <li>Friday Dec. 16, 2005 Release 1.0
- - release build</li>
-</ul>
-
-<h2>Target Operating Environments</h2>
-
-<p>Eclipse WTP is built on the Eclipse platform itself. </p>
-<p>Most of the Eclipse WTP is "pure" Java code and has no direct dependence on
-the underlying operating system. The chief dependence is therefore on Eclipse.
-The 1.0 release of the Eclipse WTP Project is written and compiled against
-version 1.4 of the Java 2 Platform APIs, and targeted to run on version 1.4 and
-5.0 (1.5) of the Java 2 Runtime Environment, Standard Edition.</p>
-<p>Eclipse WTP is tested and validated on the following reference platforms
-(this list is updated over the course of the release cycle):</p>
-
-<table BORDER CELLSPACING="1" CELLPADDING="2" WIDTH="821">
- <tr>
- <td VALIGN="MIDDLE" COLSPAN="4" BGCOLOR="#cccccc">
-
- <p ALIGN="CENTER"><b>Eclipse WTP Reference Platforms</b><font FACE="Times New Roman" COLOR="#000080">
- </font></td>
- </tr>
- <tr>
- <td WIDTH="24%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080"><b>Operating system</b></font></td>
- <td WIDTH="14%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080"><b>Processor architecture</b></font></td>
- <td WIDTH="10%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080"><b>Window system</b></font></td>
- <td WIDTH="52%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080"><b>Java 2 Platform</b></font></td>
- </tr>
- <tr>
- <td WIDTH="24%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Microsoft Windows XP</font></td>
- <td WIDTH="14%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Intel x86</font></td>
- <td WIDTH="10%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Win32</font></td>
- <td WIDTH="52%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Sun Java 2 SDK, Standard
- Edition, version 1.4.2_06 for Microsoft Windows</font></td>
- </tr>
- <tr>
- <td WIDTH="24%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Microsoft Windows XP</font></td>
- <td WIDTH="14%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Intel x86</font></td>
- <td WIDTH="10%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Win32</font></td>
- <td WIDTH="52%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">IBM 32-bit SDK for Windows,
- Java 2 Technology Edition, Version 1.4.1</font></td>
- </tr>
- <tr>
- <td WIDTH="24%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Red Hat Enterprise Linux WS 3</font></td>
- <td WIDTH="14%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Intel x86</font></td>
- <td WIDTH="10%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">GTK</font></td>
- <td WIDTH="52%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Sun Java 2 SDK, Standard
- Edition, 1.4.2_05 for Linux x86</font></td>
- </tr>
- <tr>
- <td WIDTH="24%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Red Hat Enterprise Linux WS 3</font></td>
- <td WIDTH="14%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Intel x86</font></td>
- <td WIDTH="10%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">GTK</font></td>
- <td WIDTH="52%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">IBM 32-bit SDK for Linux on
- Intel architecture, Java 2 Technology Edition, Version 1.4.2</font></td>
- </tr>
- <tr>
- <td WIDTH="24%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">SuSE Linux 8.3</font></td>
- <td WIDTH="14%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Intel x86</font></td>
- <td WIDTH="10%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">GTK</font></td>
- <td WIDTH="52%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Sun Java 2 SDK, Standard
- Edition, 1.4.2_06 for Linux x86</font></td>
- </tr>
- <tr>
- <td WIDTH="24%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">SuSE Linux 8.3</font></td>
- <td WIDTH="14%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Intel x86</font></td>
- <td WIDTH="10%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">GTK</font></td>
- <td WIDTH="52%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">IBM 32-bit SDK for Linux on
- Intel architecture, Java 2 Technology Edition, Version 1.4.2</font></td>
- </tr>
-</table>
-
-<p>Although untested, Eclipse WTP should work fine on other OSes that support
-the same window system. See also
-<a HREF="http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_1.html/lTargetOperatingEnvironments">
-<u>Eclipse Target Operating
-Environments</u></a>
-</p>
-<p>Eclipse WTP is planned to support models for projects, editors, web and J2EE
-artefacts, servers. Whereas Eclipse WTP would not add OS dependencies to support
-the first three, projects, editors and artefacts, integrating servers to Eclipse
-WTP would imply some OS dependencies. Eclipse WTP is targeted to be OS
-independent through a modular conception. So, components for servers integration
-will be available out of Eclipse WTP Web, or J2EE, Standard Tools runtime binary
-distributions.</p>
-<p>Servers integrated into Eclipse WTP deliverables will be tested and validated
-on the same platforms listed above. Tests for other platforms will be relying on
-the community support.</p>
-
-<h3>Internationalization</h3>
-
-<p>The Eclipse WTP is designed as the basis for internationalized products. The
-user interface elements provided by the Eclipse SDK components, including
-dialogs and error messages, are externalized. The English strings are provided
-as the default resource bundles. Other language support, if any, will rely on
-the community support.</p>
-<h2>Compatibility with Other WTP Releases</h2>
-<p>Project Compatibility:</p>
-<ul> <li>support for 0.7 projects </li>
-</ul>
-<p>Eclipse WTP deliverables will be compatible with Eclipse 3.1. No special
-attention will give for being compatible with previous Eclipse versions.</p>
-
-<h2>Eclipse WTP Subprojects</h2>
-
-<p>The Eclipse WTP consists of 2 subprojects. Each subproject is covered in its
-own section: </p>
-
-<a HREF="http://eclipse.org/webtools/wst/index.html">
- Web Standard Tools</a>
-
- <a HREF="http://eclipse.org/webtools/jst/index.html">
- J2EE Standard Tools</a>
-<p>For each subproject, the items listed reflect new features of the Web Tools
-Platform, or areas where existing features will be significantly reworked.
-Common goals are listed in the Common goals area.</p>
-<p>TBD [Each item indicates the components likely affected by that work item
-(many items involve coordinated changes to several components). Numbers in
-parentheses link to bugzilla problem reports for that plan item]</p>
-
-<h2>Common goals:</h2>
-<h3>Built to last</h3>
-<ul>
-<li>Platform
-
-<ul><li>Evolve available APIs and promote
- provisional APIs to platform APIs as appropriate (provisional APIs may
- disappear without replacement or be moved to other layers of the eclipse platform)
- </li>
- <li>Resolve API
- violations </li>
- <li><span >Extensibility (provide API to extend WTP
- with other specifications, e.g. JSF) </span></li>
-</ul></li>
-
-<li>Performance
-<ul> <li>Memory Footprint </li>
- <li>Startup time</li>
- <li>Zero performance regression compared to 0.7</li>
- <li>Eliminating all critical performance
- problems (please report bugs)</li>
-</ul></li>
-
-<li>UI Consitency / Scalability
-<ul><li>Enforcement of
- Eclipse Guidelines </li>
- <li>Ease of use </li>
- <li>Common undo / redo in visual and text
- editors </li>
- </ul></li>
- <li>Online Help
- <ul><li>Providing more content</li>
- <li><span >Use dynamic system</span></li>
- <li>Fix National Language bugs.</li>
- <li>Fix Accessibility bugs</li>
- </ul></li>
-
- <li>Improve feature split
- <ul>
- <li>Componentize WTP into Features to enable adopters to select subsets of function</li>
- <li>Community feedback welcome</li>
- </ul></li>
-</ul>
-
-
-<h2><span >Web Standard Tools
-subproject</span></h2>
-
-
-<h3><span >Built to last</span></h3>
-
-
-<p><span >Evolve
-available APIs and promote provisional APIs to platform APIs for the following
-components (provisional APIs may disappear without replacement or be moved to
-other layers of the eclipse platform)</span></p>
-
-
-<ul type="disc">
-<li><span >Command </span></li><li><span >Navigator</span></li><li><span >Snippets</span></li><li><span >SSE (CSS, DTD, HTML, XML)</span></li><li><span >Web Services</span></li>
-</ul>
-
-
-<h2><span >J2EE Standard Tools</span></h2>
-
-
-<h3><span >Built to last</span></h3>
-
-
-<p><span>Evolve
-available APIs and promote provisional APIs to platform APIs for the following
-components (provisional APIs may disappear without replacement or be moved to
-other layers of the eclipse platform)</span></p>
-
-
-<ul type="disc">
-<li><span >JSP</span></li>
-<li><span >Flexible Project Structure </span></li>
-<li><span >Component Features</span></li>
-<li><span >Server</span></li>
-</ul>
-
-
-<h3>Server Runtime</h3>
-
-
-<ul type="disc">
-<li><span >Support for JBoss, WebSphere, WebLogic</span></li>
-</ul>
-
-
-</body>
-
-</html>
\ No newline at end of file
diff --git a/development/requirements/wtp_1_5_plan.html b/development/requirements/wtp_1_5_plan.html
deleted file mode 100644
index 38b261a..0000000
--- a/development/requirements/wtp_1_5_plan.html
+++ /dev/null
@@ -1,368 +0,0 @@
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
-<title>Eclipse Web Tools Project DRAFT 1.5 Plan</title>
-</head>
-
-<body>
-
-<h1>Eclipse Web Tools Project DRAFT 1.5 Plan</h1>
-
-<p><b>Initial draft</b> September 8, 2005 (by Jochen Krause / WTP Requirements Group
-based on WTP Project 1.0 Plan and Eclipse Project DRAFT 3.2 Plan)</p>
-<p><i>
-Please send comments about this <b>draft plan</b> to the </i>wtp-requirements@eclipse.org
-<i>mailing list.</i></p>
-
-<p>This document lays out the feature and API set for the next feature release
-of Eclipse Web Tools after 1.0, designated release 1.5. This document is a draft
-and is subject to change, we welcome all feedback. </p>
-<p>Web Tools 1.5 will be compatible with Eclipse 3.2 Releases.</p>
-<p>Plans do not materialize out of nowhere, nor are they entirely static. To
-ensure the planning process is transparent and open to the entire Eclipse
-community, we (the Eclipse Web Tools Requirement Group & the Web Tools PMC) post
-plans in an embryonic form and revise them throughout the release cycle. </p>
-<p>The first part of the plan deals with the important matters of release
-deliverables, release milestones, target operating environments, and
-release-to-release compatibility. These are all things that need to be clear for
-any release, even if no features were to change. </p>
-<p>The remainder of the plan consists of plan items for the two subprojects
-under the Eclipse Web Tools top-level project. Each plan item covers a feature
-or API that is to be added to Web Tools, or some aspect of Web Tools that is to
-be improved. Each plan item will have its own entry in the Eclipse bugzilla
-database, with a title and a concise summary (usually a single paragraph) that
-explains the work item at a suitably high enough level so that everyone can
-readily understand what the work item is without having to understand the
-nitty-gritty detail. </p>
-<p>Not all plan items represent the same amount of work; some may be quite
-large, others, quite small. Some plan items may involve work that is localized
-to a single Platform component; others may involve coordinated changes to
-several components; other may pervade the entire Platform. Although some plan
-items are for work that is more pressing that others, the plan items appear in
-no particular order. </p>
-<p>With the previous release as the starting point, this is the plan for how we
-will enhance and improve it. Fixing bugs, improving test coverage,
-documentation, examples, performance tuning, usability, etc. are considered
-routine ongoing maintenance activities and are not included in this plan unless
-they would also involve a significant change to the API or feature set, or
-involve a significant amount of work. The intent of the plan is to account for
-all interesting feature work. </p>
-<p> </p>
-<p>The current status of each plan item is noted: </p>
-
- <p><b>High Priority</b> plan item - A
- high priority plan item is one that we have decided to address for the
- release (committed).</p>
- <p><b>Medium Priority</b> plan item -
- A medium priority plan item is one that we are considering addressing for
- the release. Although we are actively investigating it, we are not yet in a
- position to commit to it, or to say that we won't be able to address it. </p>
- <p><b>Low Priority </b>plan item A
- low priority plan item is one that we addressed for a release we will only
- address that item if one component has addressed all high and medium
- priority items </p>
- <p><b>Deferred</b> plan item - A
- reasonable proposal that will not make it in to this release for some reason
- is marked as deferred with a brief note as to why it was deferred. Deferred
- plan items may resurface as committed plan items at a later point.</p>
-
-<h2>Release deliverables</h2>
-<p>The release deliverables have the same form as previous releases, namely: </p>
-<ul>
- <li>Source code release for Eclipse WTP
- Project, available as versions tagged "R1_0" in the Eclipse WTP Project
- </li>
- <li>CVS repository</li>
- <li>Eclipse WTP runtime binary and SDK
- download with all Eclipse pre-reqs (downloadable).</li>
- <li>Eclipse WTP runtime binary and SDK
- download (downloadable).</li>
-</ul>
-
-<h2>Release milestones</h2>
-
-<p>Release milestone occurring at roughly 6 week intervals in synchronisation
-with the Eclipse Platform milestone releases (starting early 2006 latest) and will be
-compatible with Eclipse 3.2 releases.</p>
-<p>The milestones are:</p>
-<ul>
- <li>TBD</li>
-</ul>
-
-<h2>Target Operating Environments</h2>
-
-<p>Eclipse WTP is built on the Eclipse platform itself. </p>
-<p>Most of the Eclipse WTP is "pure" Java code and has no direct dependence on
-the underlying operating system. The chief dependence is therefore on Eclipse.
-The 1.0 release of the Eclipse WTP Project is written and compiled against
-version 1.4 of the Java 2 Platform APIs, and targeted to run on version 1.4 and
-5.0 (1.5) of the Java 2 Runtime Environment, Standard Edition.</p>
-<p>Eclipse WTP is tested and validated on the following reference platforms
-(this list is updated over the course of the release cycle):</p>
-
-<table BORDER CELLSPACING="1" CELLPADDING="2" WIDTH="821">
- <tr>
- <td VALIGN="MIDDLE" COLSPAN="4" BGCOLOR="#cccccc">
-
- <p ALIGN="CENTER"><b>Eclipse WTP Reference Platforms</b><font FACE="Times New Roman" COLOR="#000080">
- </font></td>
- </tr>
- <tr>
- <td WIDTH="24%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080"><b>Operating system</b></font></td>
- <td WIDTH="14%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080"><b>Processor architecture</b></font></td>
- <td WIDTH="10%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080"><b>Window system</b></font></td>
- <td WIDTH="52%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080"><b>Java Platform</b></font></td>
- </tr>
- <tr>
- <td WIDTH="24%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Microsoft Windows XP</font></td>
- <td WIDTH="14%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Intel x86</font></td>
- <td WIDTH="10%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Win32</font></td>
- <td WIDTH="52%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Sun ... TBD</font></td>
- </tr>
- <tr>
- <td WIDTH="24%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Microsoft Windows XP</font></td>
- <td WIDTH="14%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Intel x86</font></td>
- <td WIDTH="10%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Win32</font></td>
- <td WIDTH="52%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">IBM ... TBD</font></td>
- </tr>
- <tr>
- <td WIDTH="24%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Red Hat Enterprise Linux ... TBD</font></td>
- <td WIDTH="14%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Intel x86</font></td>
- <td WIDTH="10%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">GTK</font></td>
- <td WIDTH="52%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Sun ... TBD</font></td>
- </tr>
- <tr>
- <td WIDTH="24%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Red Hat Enterprise Linux ... TBD</font></td>
- <td WIDTH="14%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Intel x86</font></td>
- <td WIDTH="10%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">GTK</font></td>
- <td WIDTH="52%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">IBM ... TBD</font></td>
- </tr>
- <tr>
- <td WIDTH="24%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">SuSE Linux ... TBD</font></td>
- <td WIDTH="14%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Intel x86</font></td>
- <td WIDTH="10%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">GTK</font></td>
- <td WIDTH="52%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Sun ... TBD</font></td>
- </tr>
- <tr>
- <td WIDTH="24%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">SuSE Linux ... TBD/font></td>
- <td WIDTH="14%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">Intel x86</font></td>
- <td WIDTH="10%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">GTK</font></td>
- <td WIDTH="52%" VALIGN="MIDDLE">
- <font FACE="Times New Roman" COLOR="#000080">IBM ... TBD</font></td>
- </tr>
-</table>
-
-<p>Although untested, Eclipse WTP should work fine on other OSes that support
-the same window system. See also
-<a HREF="http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_1.html/lTargetOperatingEnvironments">
-<u>Eclipse Target Operating
-Environments</u></a>
-</p>
-<p>Eclipse WTP is planned to support models for projects, editors, web and J2EE
-artefacts, servers. Whereas Eclipse WTP would not add OS dependencies to support
-the first three, projects, editors and artefacts, integrating servers to Eclipse
-WTP would imply some OS dependencies. Eclipse WTP is targeted to be OS
-independent through a modular conception. So, components for servers integration
-will be available out of Eclipse WTP Web, or J2EE, Standard Tools runtime binary
-distributions.</p>
-<p>Servers integrated into Eclipse WTP deliverables will be tested and validated
-on the same platforms listed above. Tests for other platforms will be relying on
-the community support.</p>
-
-<h3>Internationalization</h3>
-
-<p>The Eclipse WTP is designed as the basis for internationalized products. The
-user interface elements provided by the Eclipse SDK components, including
-dialogs and error messages, are externalized. The English strings are provided
-as the default resource bundles. Other language support, if any, will rely on
-the community support.</p>
-<h2>Compatibility with Other WTP Releases</h2>
-<p>Project Compatibility:</p>
-<ul> <li>Full compatibility with 1.0 projects </li>
-<li><b>TBD</b></li>
-</ul>
-<p>Eclipse WTP deliverables will be compatible with Eclipse 3.2. No special
-attention will give for being compatible with previous Eclipse versions.</p>
-
-<h2>Eclipse WTP Subprojects</h2>
-
-<p>The Eclipse WTP consists of 2 subprojects. Each subproject is covered in its
-own section: </p>
-
-<a HREF="http://eclipse.org/webtools/wst/index.html">
- Web Standard Tools</a>
-
- <a HREF="http://eclipse.org/webtools/jst/index.html">
- J2EE Standard Tools</a>
-<p>For each subproject, the items listed reflect new features of the Web Tools
-Platform, or areas where existing features will be significantly reworked.
-Common goals are listed in the Common goals area.</p>
-<p>TBD [Each item indicates the components likely affected by that work item
-(many items involve coordinated changes to several components). Numbers in
-parentheses link to bugzilla problem reports for that plan item]</p>
-
-
-<h2><span >Web Standard Tools
-subproject</span></h2>
-
-
-<h3><span >Architectural harmonization</span></h3>
-<ul type="disc">
-<li>DTP (data tools)</li>
-<li>Moving generic components to platform (like the browser to 3.1)</li>
-<li>TPTP Validation (elaborate correction framework part of validation), TCP/IP sniffer (tcp/ip monitor)</li>
-<li>EJB3</li>
-<li>Lipido (AXE Cocoon tooling)</li>
-</ul>
-
-<h3><span >Web Services Support</span></h3>
-<ul type="disc">
-<li>Soap 1.2 Support</li>
-<li>WSDL 2.0 Support</li>
-<li>New WS-I profiles</li>
-<li>WS Security</li>
-<li>Axis 2.0 Support</li>
-</ul>
-
-<h2><span >J2EE Standard Tools</span></h2>
-
-
-<h3><span >Architectural harmonization</span></h3>
-<ul type="disc">
-<li>EJB3 Projects</li>
-</ul>
-
-<h3><span >J2EE 1.5 Support</span></h3>
-<ul type="disc">
-<li>EJB3</li>
-<li>JSR 175 (Metadata) Support</li>
-<li>JSF Support</li>
-</ul>
-
-<h3><span >Web Services Support</span></h3>
-<ul type="disc">
-<li>JSR 181 (Web Services)</li>
-</ul>
-
-<h3><span >Server Runtime</span></h3>
-<ul type="disc">
-<li>JSR 88 Support, Advanced Server Support for one/multiple open source J2EE server</li>
-<li>Support for incremental deploy</li>
-</ul>
-
-<br/>
-<p>
-The following shall serve as an example how the community can help to provide input for their desired use cases, this details the EJB 3.0 support of our top level item J2EE 1.5 Support:
-</p>
-
-
-<h3>EJB3.0 Use cases proposed by Ivelin Ivanov (JBoss)</h3>
-<br>
-</p>
-<p>1) Wizards for Stateless and Stateful Session Beans that follow J2EE naming
-conventions and generate both the bean implementation class and the remote /
-local (or both) interfaces </p>
-<p>a) The user will be able to invoke the Session bean wizard through the File >
-New > Other.. menu of eclipse. If the user has right clicked on any package or
-source directory, the wizard should auto-fill the pertinent information. </p>
-<p>b) The wizard should give the user an option to either<br>
-"Follow J2EE Naming Standards", and enter a simple bean name, or to "Customize
-Type Names", and manually enter the bean implementation class, and remote and/or
-local interfaces. </p>
-<p>c) The user should have the ability to generate Local, and Remote interfaces
-for the bean. It is not required to generate either. The generated bean
-implementation class should implement all generated business interfaces. </p>
-<p>d) The user should have the option to make the Session bean either Stateful,
-or Stateless. </p>
-<p>e) There should be an option for generating either annotated POJOs (default)
-or XML descriptors for all bean meta-data. </p>
-<p>2) An EJB3 Project Nature Wizard and related Classpath Containers for
-automated EJB3 API code completion and compilation </p>
-<p>a) The EJB3 project nature wizard should have all the options and steps the
-standard Java project wizard does. </p>
-<p>b) The wizard will create classpath containers for the generated project that
-will contain all the classes necessary for compilation of EJB3 APIs </p>
-<p>3) Table and column meta-data completion for common entity annotations such
-as @Table, @Column, @JoinColumn, and @Id. This could be a possible integration
-point with the Data Tools Project. </p>
-<p>a) when defining the EJB3 project there should be away to associate the
-project with a db-server in the DTP project </p>
-<p>b) Using the catalog/schema/table/column/etc information found in the DTP
-project<br>
-we should provide seamless content-assitance inside the related java annotations
-</p>
-<p>Note: This will require support from the JDT to allow non-JDT plugins to
-provide content assistance on annotations values. </p>
-<p>4) Message Driven Bean wizards that provide stub methods for the
-MessageListener interface, and use server tools to find JMS Topics / Queues. </p>
-<p>a) Similar to the Session Bean wizard, but without remote/local interface
-generation. </p>
-<p>b) User should have the option to either "implement MessageListener"
-explicity, or simply implement the "onMessage" method without the container
-contract. </p>
-<p>c) Possible integration point w/ Server Tools: Locate Active JMS Queues and
-Topics for this MDB to subscribe to. </p>
-<p>d) There should be an option for generating either annotated POJOs (default)
-or XML descriptors for all bean meta-data.<br>
-<br>
-</p>
-<h3>JSR 88 Use Cases proposed by Ivelin Ivanov (JBoss), edited by Jochen Krause
-</h3>
-<p>1) A method to deploy a packaged j2ee application, war, ear, etc through the
-jsr-88 API. </p>
-<p>a) Provide a packaged jsr-88 deployment action </p>
-<p>b) If the deployable package's descriptors all match the requirements, the
-user should be able to select a target from those listed in preferences and
-deployment should begin. </p>
-<p>c) If the deployable package is missing information, the missing information
-should be matched with the unpackaged descriptor and the user should be able to
-fill in missing data( e.g. with a tabbed dialog, with different tabs for each
-descriptor that is missing elements) </p>
-<p>d) The user shall be able to manually add missing information on the fly,
-rather than through the above mentioned method. It should be possible to persist
-the information that was added on the fly to the appropriate descriptor file.<br>
-<br>
-</p>
-<p>2) Find out about missing deployment descriptor items for an unpackaged j2ee
-application </p>
-<p>a) Enable user to discover missing descriptor elements </p>
-<p>b) If the project has an associated packaging configuration (project
-preferences), the tool will generate the model using the packaging configuration
-as a guide. Otherwise it will suggest / redirect to the packaging configuration
-preference page. </p>
-<p>c) See Use Case 1 b) d) </p>
-<p>d) If there are no missing required xpaths for deployment, the user shall be
-able to package and deploy</p>
-
-
-</body>
-
-</html>
\ No newline at end of file
diff --git a/development/requirements_call_notes.html b/development/requirements_call_notes.html
deleted file mode 100644
index 0dd2388..0000000
--- a/development/requirements_call_notes.html
+++ /dev/null
@@ -1,63 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-<link rel="stylesheet" href="../../default_style.css" type="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
-<title>Project Documentation</title>
-</head>
-<body text="#000000" bgcolor="#ffffff" link="#0000ee" vlink="#551a8b" alink="#ff0000">
-<table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
- <tr>
- <td ALIGN=LEFT width="60%"><font class=indextop>eclipse web tools platform
- project development</font><br>
-
- <font class=indexsub>requirements conference calls.</font></td>
- <td WIDTH="40%"><img SRC="../../images/Idea.jpg" HSPACE=50 height=86 width=120 align=CENTER></td>
- </tr>
-</table>
-<table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
- <tr>
- <td ALIGN=LEFT VALIGN=TOP COLSPAN="2" BGCOLOR="#0080C0"><b>
- <font face="Arial,Helvetica" color="#FFFFFF">Requirements Conference Calls</font></b></td>
- </tr>
-
- </table>
-<table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
- <tr>
- <td align=right valign=top><img src="../../images/Adarrow.gif" border=0 height=16 width=16></td>
- <td>
- <p><a href="requirements_call_notes/2004-08-23.html">August 23, 2004</a></p>
- </td>
- </tr>
- <tr>
- <td align=right valign=top><img src="../../images/Adarrow.gif" border=0 height=16 width=16></td>
- <td>
- <p><a href="requirements_call_notes/2004-08-30.html">August 30, 2004</a></p>
- </td>
- </tr>
- <tr>
- <td align=right valign=top><img src="../../images/Adarrow.gif" border=0 height=16 width=16></td>
- <td>
- <p><a href="requirements_call_notes/2004-09-13.html">September 13, 2004</a></p>
- </td>
- </tr>
- <tr>
- <td align=right valign=top><img src="../../images/Adarrow.gif" border=0 height=16 width=16></td>
- <td>
- <p><a href="requirements_call_notes/2005-03-30.html">March 30, 2005</a></p>
- </td>
- </tr>
- <tr>
- <td align=right valign=top><img src="../../images/Adarrow.gif" border=0 height=16 width=16></td>
- <td>
- <p><a href="requirements_call_notes/2005-04-12.html">April 12, 2005</a></p>
- </td>
- </tr>
- </table>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/development/requirements_call_notes/2004-08-23.html b/development/requirements_call_notes/2004-08-23.html
deleted file mode 100644
index 39dfddd..0000000
--- a/development/requirements_call_notes/2004-08-23.html
+++ /dev/null
@@ -1,50 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
-<title>Project Documentation</title>
-</head>
-<body text="#000000" bgcolor="#ffffff" link="#0000ee" vlink="#551a8b" alink="#ff0000">
-<table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
- <tr>
- <td ALIGN=LEFT VALIGN=TOP COLSPAN="2" BGCOLOR="#0080C0"><b>
-
- <font face="Arial,Helvetica" color="#FFFFFF">Requirements Conference Call - August 23,
- 2004</font></b></td>
- </tr>
- </table>
- <table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
- <tr>
- <td>
- <p>Finalize priorities </p>
- <ul>
- <li>priorities have been discussed in the group and added to the requirements document (see attachment)</li>
- <li>we need to add context to some of the requirements - plan: use an xml template</li>
- <li>Priorities for the flexible project layout have been omittted, we will wait for Todds draft</li>
- <li>Decision if the first draft of the flexible project layout will be published directly to be discussed with Bjorn (Jochen)</li>
- </ul>
-
- <p> Eclipse development process - Requirements council</p>
- <ul>
- <li>Requirements group is not envisioned for the projects, but only for the Eclipse organisation. Bring that subject up at the next PMC call</li>
- </ul>
-
- <p>Distribution of minutes</p>
- <ul>
- <li>send a last information about the mailing list, talk to Bjorn if we should publish the minutes the same way as the PMC notes (Jochen)</li>
- </ul>
-
- <p>Use case template</p>
- <ul>
- <li>needs to be adjusted to our requirements (self explanatory, extend with catgory, priority) (Jochen and Arthur)</li>
- </ul>
- </td>
- </tr>
- </table>
- </body>
-</html>
diff --git a/development/requirements_call_notes/2004-08-30.html b/development/requirements_call_notes/2004-08-30.html
deleted file mode 100644
index a71fd9e..0000000
--- a/development/requirements_call_notes/2004-08-30.html
+++ /dev/null
@@ -1,55 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
-<title>Project Documentation</title>
-</head>
-<body text="#000000" bgcolor="#ffffff" link="#0000ee" vlink="#551a8b" alink="#ff0000">
-<table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
- <tr>
- <td ALIGN=LEFT VALIGN=TOP COLSPAN="2" BGCOLOR="#0080C0"><b> <font face="Arial,Helvetica" color="#FFFFFF">Requirements
- Conference Call - August 30, 2004</font></b></td>
- </tr>
-</table>
-<table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
- <tr>
- <td bgcolor="#FFFFFF"><p>Agenda:</p>
- <ul>
- <li>Flexible Project Structure</li>
- <li>Requirement Priorities</li>
- </ul>
- <p>Attending: Arthur Ryman, Vladislav Pernin, Todd Williams, Jochen Krause</p>
- <P>General</P>
- <li>With regard to publishing documents we follow the principle early and often, not perfect but late </li>
- <p>Flexible project model</p>
- <li>We will make initial requirements document available on a wiki, as well
- as Nacis and Thomas notes. The wiki will become publicly usable.</li>
- <li>Request making the wiki public from Dominique / Christophe</li>
- <li>Objection: This will make it much harder to read to document / follow the
- main ideas (but a revision system is available - make that more visible
- (Jochen) )</li>
- <br>
- <li>Flexible project structure, scope is wider than stated, valid as well
- for WST, we have to specify the requirements for WST only</li>
- <li>We should make sure that our needs are heard by the platform team (specifically
- links). David Williams will go to the EMO meeting.</li><br>
- <li>Use exploded archives as default layouts</li>
- <blockquote>One use case:
- <li>Import a project from CVS and be able to adapt the Web Project Structure
- to the one in cvs.</li></blockquote>
- <li>Provide comments to the requirements document in the wiki to get a discussion
- going</li>
- <p>Requirements Priorities</p>
- <li>Priorities as agreed during the last conf call will be published
- on the webtools web site</li>
- <p>Use cases</p>
- <li>Find a way to combine Bugzilla with a better structured method
- of specifying requirements suggest a template (Arthur / Jochen)</li></td>
- </tr>
-</table>
-</body>
-</html>
diff --git a/development/requirements_call_notes/2004-09-13.html b/development/requirements_call_notes/2004-09-13.html
deleted file mode 100644
index 3caa6ab..0000000
--- a/development/requirements_call_notes/2004-09-13.html
+++ /dev/null
@@ -1,38 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project Development</title>
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
-<title>Project Documentation</title>
-</head>
-<body text="#000000" bgcolor="#ffffff" link="#0000ee" vlink="#551a8b" alink="#ff0000">
-<table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
- <tr>
- <td ALIGN=LEFT VALIGN=TOP COLSPAN="2" BGCOLOR="#0080C0"><b> <font face="Arial,Helvetica" color="#FFFFFF">Requirements
- Conference Call - September 13, 2004</font></b></td>
- </tr>
-</table>
-<table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
- <tr>
- <td bgcolor="#FFFFFF">
- <p>Attending: Arthur Ryman, Jochen Krause</p>
- <p>Agenda:</p>
- <ul>
- <li>flexible project model</li>
- <li>finalizing priorities for server tooling, structured editor</li>
- <li>capturing requirements with use cases</li>
- </ul>
- <p>flexible project model and finalizing priorities - postponed</p>
- <P>capturing requirements with use cases should be discussed with the Eclipse Requirements Council,
- to see how they capture and process input and if they use other tools than bugzilla. Query other Eclipse projects for
- their experience / tools.</P>
- <p>Requirements for the 1.0 release of web tools should be finalized by the end of October. Define themes (with PMC) and query
- the community for input.</p>
- </td>
- </tr>
-</table>
-</body>
-</html>
diff --git a/development/requirements_call_notes/2005-03-30.html b/development/requirements_call_notes/2005-03-30.html
deleted file mode 100644
index 9863d0c..0000000
--- a/development/requirements_call_notes/2005-03-30.html
+++ /dev/null
@@ -1,108 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
- <TITLE>Eclipse Web Tools Platform Project Development</TITLE>
-
- <STYLE>
- <!--
- @page { size: 21cm 29.7cm; margin: 2cm }
- TD P { margin-bottom: 0cm }
- H1.western { font-family: "Times New Roman", serif }
- H1.cjk { font-family: "Lucida Sans Unicode" }
- H1.ctl { font-family: "Tahoma" }
- P { margin-bottom: 0.21cm }
- -->
- </STYLE>
-</HEAD>
-<BODY LANG="de-DE" DIR="LTR">
-<P STYLE="margin-bottom: 0cm"><BR>
-</P>
-<TABLE WIDTH=100% BORDER=0 CELLPADDING=2 CELLSPACING=0 STYLE="page-break-before: always">
- <COL WIDTH=256*>
- <TR>
- <TD WIDTH=100% VALIGN=TOP BGCOLOR="#0080c0">
- <P ALIGN=LEFT><FONT COLOR="#ffffff"><FONT FACE="Arial, Helvetica"><B>Requirements Group Conference
- Call - March 30, 2005</B></FONT></FONT></P>
- </TD>
- </TR>
-</TABLE>
-<TABLE WIDTH=100% BORDER=0 CELLPADDING=2 CELLSPACING=0>
- <COL WIDTH=256*>
- <TR>
- <TD WIDTH=100%>
- <P STYLE="margin-bottom: 0.5cm">Attending: Paul Meijer, Jochen
- Krause, Arthur Ryman</P>
- <H1 CLASS="western">Initial topics for requirements gathering</H1>
- <H2>Architectural harmonization</H2>
- <UL>
- <LI>DTP (data tools)LDT (SSE)
- <LI>Moving generic components to platform (browser as an example)
- <LI>TPTP Validation (elaborate correction framework part of validation), TCP/IP sniffer (tcp/ip
- monitor)
- </UL>
- <H2>Built to last</H2>
- <UL>
- <LI>Platform
- <UL>
- <LI>API (resolve API violations)
- <LI>Extensibility (other languages, e.g. PHP)
- </UL>
- <LI>Performance
- <UL>
- <LI>Memory Footprint
- <LI>Startup time for editors
- </UL>
- <LI>UI Consitency / Scalability
- <UL>
- <LI>Enforcement of Eclipse Guidelines
- <LI>Ease of use
- <LI>Common undo / redo in visual and text editors
- </UL>
- </UL>
- <H2>J2EE 1.5 Support</H2>
- <UL>
- <LI>EJB 3.0 Support
- <LI>JSR 175 (Metadata) Support
- <LI>JSF Support
- </UL>
- <H2>Web Services Support</H2>
- <UL>
- <LI>Soap 1.2 Support
- <LI>WSDL 2.0 Support
- <LI>JSR 181 (Web Services)
- <LI>New WS-I profiles
- <LI>WS Security
- <LI>Axis 2.0 Support
- </UL>
- <H2>Server Runtime</H2>
- <UL>
- <LI>JSR 88 Support, Server Support for an open source J2EE server
- <LI>Support for Jboss, WebSphere, WebLogic (requested by end users)
- <LI>Support for incremental deploy
- </UL>
- <H2>Requirements
- gathering process</H2>
- <P>Write
- up a draft document - post message on website, mailing list and
- newsgroup</P>
- <P>At W3C they set up a public
- mailing list for draft specifications - public comment mailing
- list</P>
- <P STYLE="margin-bottom: 0.5cm">Action item (JK): Ask Bjorn if setting up a mailing list for this purpose is adaquate</P>
- <P STYLE="margin-bottom: 0.5cm">Next call in two weeks</P>
- </TD>
- </TR>
- <TR>
- <TD WIDTH=100%>
- <P><BR>
- </P>
- </TD>
- </TR>
-</TABLE>
-<P><BR><BR>
-</P>
-<P STYLE="margin-bottom: 0cm"><BR>
-</P>
-</BODY>
-</HTML>
\ No newline at end of file
diff --git a/development/requirements_call_notes/2005-04-12.html b/development/requirements_call_notes/2005-04-12.html
deleted file mode 100644
index 2761327..0000000
--- a/development/requirements_call_notes/2005-04-12.html
+++ /dev/null
@@ -1,78 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
- <TITLE>Eclipse Web Tools Platform Project Development</TITLE>
-
- <STYLE>
-
- </STYLE>
-</HEAD>
-<BODY LANG="de-DE" DIR="LTR">
-<P STYLE="margin-bottom: 0cm"><BR>
-</P>
-<TABLE WIDTH=100% BORDER=0 CELLPADDING=2 CELLSPACING=0 STYLE="page-break-before: always">
- <COL WIDTH=256*>
- <TR>
- <TD WIDTH=100% VALIGN=TOP BGCOLOR="#0080c0">
- <P ALIGN=LEFT><FONT COLOR="#ffffff"><FONT FACE="Arial, Helvetica"><B>Requirements Group Conference
- Call - <span lang="de">April 12</span>, 2005</B></FONT></FONT></P>
- </TD>
- </TR>
-</TABLE>
-<TABLE WIDTH=100% BORDER=0 CELLPADDING=2 CELLSPACING=0>
- <COL WIDTH=256*>
- <TR>
- <TD WIDTH=100%>
- <P STYLE="margin-bottom: 0.5cm">Attending: Jochen
- Krause<span lang="de"> (JK)</span>, Arthur Ryman<span lang="de">
- (AR), </span>Paul Meijer<span lang="de"> (PM)</span>,
- <span lang="de">Ivelin Ivanov (II), Todd Williams (TW)</span></P>
- <H2>Draft requirements document</H2>
- <UL>
- <li><span lang="de">draft not yet ready - item deferred to next
- week</span></li>
- </UL>
- <H2>Requirements
- gathering process</H2>
- <ul>
- <li><span lang="de">JBoss way: Jboss providers roadmap, end users
- comment on that roadmap (using JIRA - as JIRA is not open source
- this is probably not the way WTP can go)</span></li>
- <li><span lang="de">Using Bugzilla for feedback does not seem to
- be very attractive while in the process of developing a initial version of themes
- and priorities, but is useful for evolving an existing plan</span></li>
- <li><span lang="de">Requirements group will explore ways to
- provide a more user friendly user interface to requirements /
- feature requests (Action item JK)</span></li>
- <li><span lang="de">Requirements mailing list has been requested (JK)</span></li>
- </ul>
- <H2><span lang="de">Use cases</span></H2>
- <ul>
- <li><span lang="de">Use cases are a "standard way" to describe
- featues, but they are pretty heavy weight. We want to explore if
- we can provide a template to the community that is useful but
- simple (Action item II, TW, JK)</span></li>
- </ul>
- <H2><span lang="de">Current feature requests on Bugzilla</span></H2>
- <ul>
- <li><span lang="de">deferred to next week</span></li>
- </ul>
- <P STYLE="margin-bottom: 0.5cm"> </P>
- <P STYLE="margin-bottom: 0.5cm">Next call <span lang="de">on April
- 19</span></P>
- </TD>
- </TR>
- <TR>
- <TD WIDTH=100%>
- <P><BR>
- </P>
- </TD>
- </TR>
-</TABLE>
-<P><BR><BR>
-</P>
-<P STYLE="margin-bottom: 0cm"><BR>
-</P>
-</BODY>
-</HTML>
\ No newline at end of file
diff --git a/development/status-telecons/index.html b/development/status-telecons/index.html
deleted file mode 100644
index 7cb033b..0000000
--- a/development/status-telecons/index.html
+++ /dev/null
@@ -1,440 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../webtools/wtp.css" type="text/css">
-<title>
- Eclipse Web Tools Platform Project Status Telecons
- </title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">wtp status telecons</font>
-<br>
-<font class="indexsub">
- Eclipse Web Tools Platform Project Status Telecons
- </font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Introduction</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The WTP project holds weekly development telecons to review
- status and discuss issues. The meetings are open to all
- members of the development community.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Logistics</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<table cellspacing="4">
-
-<tr>
-
-<th align="right">Day:</th>
- <td>Thursday</td>
-
-</tr>
-
-<tr>
-
-<th align="right">
- <a target="_top" href="http://www.timeanddate.com/worldclock/">
- UTC
- </a>
- :
- </th>
- <td>16:00</td>
-
-</tr>
-
-<tr>
-
-<th align="right">Istanbul Time:</th>
- <td>9:00 PM</td>
-
-</tr>
-
-<tr>
-
-<th align="right">Raleigh Time:</th>
- <td>2:00 PM</td>
-
-</tr>
-
-<tr>
-
-<th align="right">Seattle Time:</th>
- <td>11:00 AM</td>
-
-</tr>
-
-<tr>
-
-<th align="right">Toronto Time:</th>
- <td>2:00 PM</td>
-
-</tr>
-
-<tr>
-
-<th align="right">Conference ID:</th>
- <td>9976929</td>
-
-</tr>
-
-<tr>
-
-<th align="right">Toronto Dial-in:</th>
- <td>416 343-2604</td>
-
-</tr>
-
-<tr>
-
-<th align="right">Toll-free Dial-in:</th>
- <td>1 866 576-2504</td>
-
-</tr>
-
-<tr>
-
-<th align="right">Global Toll-free Dial-in:</th>
- <td>800 4444-3030</td>
-
-</tr>
-
-<tr>
-
-<th align="right">Information:</th>
- <td>1 800 667-3678</td>
-
-</tr>
-
-</table>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Action Items</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Action items that arise in the telecons are tracked in
- <a target="_top" href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Web%20Tools">
- Bugzilla
- </a>
- . Action items are distinguished from other bugs by having a
- summary that begins with the text:
- <code>[action]</code>
-
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The following Bug Lists show the current and all action
- items:
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>
- <a target="_top" href="https://bugs.eclipse.org/bugs/buglist.cgi?short_desc_type=casesubstring&short_desc=%5Baction%5D&product=Web+Tools&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED">
- Current Action Items
- </a>
- </td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>
- <a target="_top" href="https://bugs.eclipse.org/bugs/buglist.cgi?short_desc_type=casesubstring&short_desc=%5Baction%5D&product=Web+Tools">
- All Action Items
- </a>
- </td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Agenda and Minutes</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- The agenda and minutes are posted to the
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/maillist.html">
- wtp-dev
- </a>
- mailing list. The following tables summarizes the past
- meetings:
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>WTP 1.0</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<table cellspacing="4">
-
-<tr>
-
-<th>Date</th>
- <th>Agenda</th>
- <th>Minutes</th>
-
-</tr>
-
-<tr>
-
-<td>2005-09-29</td>
- <td>
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02578.html">
- Agenda
- </a>
- </td>
- <td>
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02586.html">
- Minutes
- </a>
- </td>
-
-</tr>
-
-<tr>
-
-<td>2005-09-22</td>
- <td>
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02536.html">
- Agenda
- </a>
- </td>
- <td>
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02547.html">
- Minutes
- </a>
- </td>
-
-</tr>
-
-<tr>
-
-<td>2005-09-15</td>
- <td>
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02479.html">
- Agenda
- </a>
- </td>
- <td>
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02526.html">
- Minutes
- </a>
- </td>
-
-</tr>
-
-<tr>
-
-<td>2005-09-08</td>
- <td>
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02443.html">
- Agenda
- </a>
- </td>
- <td>
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02472.html">
- Minutes
- </a>
- </td>
-
-</tr>
-
-<tr>
-
-<td>2005-09-01</td>
- <td>
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02412.html">
- Agenda
- </a>
- </td>
- <td>
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02434.html">
- Minutes
- </a>
- </td>
-
-</tr>
-
-</table>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
- Regular telecons were suspended for the month of August,
- 2005.
- </p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../images/Adarrow.gif"></td><td>WTP 0.7</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<table cellspacing="4">
-
-<tr>
-
-<th>Date</th>
- <th>Agenda</th>
- <th>Minutes</th>
-
-</tr>
-
-<tr>
-
-<td>2005-07-28</td>
- <td>
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02157.html">
- Agenda
- </a>
- </td>
- <td>
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02172.html">
- Minutes
- </a>
- </td>
-
-</tr>
-
-<tr>
-
-<td>2005-07-21</td>
- <td>
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02117.html">
- Agenda
- </a>
- </td>
- <td>
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02144.html">
- Minutes
- </a>
- </td>
-
-</tr>
-
-<tr>
-
-<td>2005-07-14</td>
- <td>
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02089.html">
- Agenda
- </a>
- </td>
- <td>
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02145.html">
- Minutes
- </a>
- </td>
-
-</tr>
-
-<tr>
-
-<td>2005-07-07</td>
- <td>
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02043.html">
- Agenda
- </a>
- </td>
- <td>
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02053.html">
- Minutes
- </a>
- </td>
-
-</tr>
-
-<tr>
-
-<td>2005-06-30</td>
- <td>
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg01984.html">
- Agenda
- </a>
- </td>
- <td>
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02006.html">
- Minutes
- </a>
- </td>
-
-</tr>
-
-<tr>
-
-<td>2005-06-23</td>
- <td>
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg01928.html">
- Agenda
- </a>
- </td>
- <td>
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg01932.html">
- Minutes
- </a>
- </td>
-
-</tr>
-
-<tr>
-
-<td>2005-06-16</td>
- <td>
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg01875.html">
- Agenda
- </a>
- </td>
- <td>
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg01905.html">
- Minutes
- </a>
- </td>
-
-</tr>
-
-<tr>
-
-<td>2005-06-09</td>
- <td>
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg01830.html">
- Agenda
- </a>
- </td>
- <td>
- <a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg01834.html">
- Minutes
- </a>
- </td>
-
-</tr>
-
-</table>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/development/status-telecons/index.xml b/development/status-telecons/index.xml
deleted file mode 100644
index 084907c..0000000
--- a/development/status-telecons/index.xml
+++ /dev/null
@@ -1,327 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?xml-stylesheet type="text/xsl" href="../../wtp.xsl"?>
-<html>
- <head>
- <meta name="root" content="../../.." />
- <title>
- Eclipse Web Tools Platform Project Status Telecons
- </title>
- </head>
- <body>
- <h1>wtp status telecons</h1>
- <h2>Introduction</h2>
- <p>
- The WTP project holds weekly development telecons to review
- status and discuss issues. The meetings are open to all
- members of the development community.
- </p>
- <h2>Logistics</h2>
- <table cellspacing="4">
- <tr>
- <th align="right">Day:</th>
- <td>Thursday</td>
- </tr>
- <tr>
- <th align="right">
- <a target="_top"
- href="http://www.timeanddate.com/worldclock/">
- UTC
- </a>
- :
- </th>
- <td>16:00</td>
- </tr>
- <tr>
- <th align="right">Istanbul Time:</th>
- <td>9:00 PM</td>
- </tr>
- <tr>
- <th align="right">Raleigh Time:</th>
- <td>2:00 PM</td>
- </tr>
- <tr>
- <th align="right">Seattle Time:</th>
- <td>11:00 AM</td>
- </tr>
- <tr>
- <th align="right">Toronto Time:</th>
- <td>2:00 PM</td>
- </tr>
- <tr>
- <th align="right">Conference ID:</th>
- <td>9976929</td>
- </tr>
- <tr>
- <th align="right">Toronto Dial-in:</th>
- <td>416 343-2604</td>
- </tr>
- <tr>
- <th align="right">Toll-free Dial-in:</th>
- <td>1 866 576-2504</td>
- </tr>
- <tr>
- <th align="right">Global Toll-free Dial-in:</th>
- <td>800 4444-3030</td>
- </tr>
- <tr>
- <th align="right">Information:</th>
- <td>1 800 667-3678</td>
- </tr>
- </table>
- <h2>Action Items</h2>
- <p>
- Action items that arise in the telecons are tracked in
- <a target="_top"
- href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Web%20Tools">
- Bugzilla
- </a>
- . Action items are distinguished from other bugs by having a
- summary that begins with the text:
- <code>[action]</code>
- </p>
- <p>
- The following Bug Lists show the current and all action
- items:
- </p>
- <h3>
- <a target="_top"
- href="https://bugs.eclipse.org/bugs/buglist.cgi?short_desc_type=casesubstring&short_desc=%5Baction%5D&product=Web+Tools&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED">
- Current Action Items
- </a>
- </h3>
- <h3>
- <a target="_top"
- href="https://bugs.eclipse.org/bugs/buglist.cgi?short_desc_type=casesubstring&short_desc=%5Baction%5D&product=Web+Tools">
- All Action Items
- </a>
- </h3>
- <h2>Agenda and Minutes</h2>
- <p>
- The agenda and minutes are posted to the
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/maillist.html">
- wtp-dev
- </a>
- mailing list. The following tables summarizes the past
- meetings:
- </p>
-
- <h3>WTP 1.0</h3>
- <table cellspacing="4">
- <tr>
- <th>Date</th>
- <th>Agenda</th>
- <th>Minutes</th>
- </tr>
- <tr>
- <td>2005-09-29</td>
- <td>
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02578.html">
- Agenda
- </a>
- </td>
- <td>
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02586.html">
- Minutes
- </a>
- </td>
- </tr>
- <tr>
- <td>2005-09-22</td>
- <td>
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02536.html">
- Agenda
- </a>
- </td>
- <td>
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02547.html">
- Minutes
- </a>
- </td>
- </tr>
- <tr>
- <td>2005-09-15</td>
- <td>
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02479.html">
- Agenda
- </a>
- </td>
- <td>
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02526.html">
- Minutes
- </a>
- </td>
- </tr>
- <tr>
- <td>2005-09-08</td>
- <td>
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02443.html">
- Agenda
- </a>
- </td>
- <td>
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02472.html">
- Minutes
- </a>
- </td>
- </tr>
- <tr>
- <td>2005-09-01</td>
- <td>
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02412.html">
- Agenda
- </a>
- </td>
- <td>
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02434.html">
- Minutes
- </a>
- </td>
- </tr>
- </table>
-
- <p>
- Regular telecons were suspended for the month of August,
- 2005.
- </p>
-
- <h3>WTP 0.7</h3>
- <table cellspacing="4">
- <tr>
- <th>Date</th>
- <th>Agenda</th>
- <th>Minutes</th>
- </tr>
- <tr>
- <td>2005-07-28</td>
- <td>
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02157.html">
- Agenda
- </a>
- </td>
- <td>
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02172.html">
- Minutes
- </a>
- </td>
- </tr>
- <tr>
- <td>2005-07-21</td>
- <td>
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02117.html">
- Agenda
- </a>
- </td>
- <td>
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02144.html">
- Minutes
- </a>
- </td>
- </tr>
- <tr>
- <td>2005-07-14</td>
- <td>
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02089.html">
- Agenda
- </a>
- </td>
- <td>
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02145.html">
- Minutes
- </a>
- </td>
- </tr>
- <tr>
- <td>2005-07-07</td>
- <td>
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02043.html">
- Agenda
- </a>
- </td>
- <td>
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02053.html">
- Minutes
- </a>
- </td>
- </tr>
- <tr>
- <td>2005-06-30</td>
- <td>
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg01984.html">
- Agenda
- </a>
- </td>
- <td>
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02006.html">
- Minutes
- </a>
- </td>
- </tr>
- <tr>
- <td>2005-06-23</td>
- <td>
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg01928.html">
- Agenda
- </a>
- </td>
- <td>
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg01932.html">
- Minutes
- </a>
- </td>
- </tr>
- <tr>
- <td>2005-06-16</td>
- <td>
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg01875.html">
- Agenda
- </a>
- </td>
- <td>
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg01905.html">
- Minutes
- </a>
- </td>
- </tr>
- <tr>
- <td>2005-06-09</td>
- <td>
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg01830.html">
- Agenda
- </a>
- </td>
- <td>
- <a
- href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg01834.html">
- Minutes
- </a>
- </td>
- </tr>
- </table>
- </body>
-</html>
diff --git a/development/tests.html b/development/tests.html
deleted file mode 100644
index dcba37f..0000000
--- a/development/tests.html
+++ /dev/null
@@ -1,147 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="http://dev.eclipse.org/default_style.css" type="text/css">
-<title>WTP automated testing</title>
-</head>
-
-<body>
-<table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
- <tr>
- <td ALIGN=LEFT width="80%">
- <p><b><font face="Verdana" size="+3">WTP automated testing</font></b><br>
- Last Updated: Nov. 29, 2004</p>
- <p>This document outlines the principles of WTP automated testing. It also provides some guidelines
- for creating and running test cases. If anyone has suggestions for this document,
- please post a message to the wtp-dev mailing list.</p>
- </td>
- </tr>
-</table>
-
-<table border=0 cellspacing=5 cellpadding=2 width="100%" >
- <tr>
- <td align=LEFT valign=TOP colspan="3" bgcolor="#0080C0"> <b><font face="Arial,Helvetica" color="#FFFFFF">Testing</font></b></td>
- </tr>
- <TR>
- <TD align="LEFT" valign="TOP">
- <p>The goal of unit testing is to achieve:
- <ol>
- <li>Continuous integration. Unit tests are run as part of the WTP builds. They give an early indication on
- what is failing. Unit test failures should be fixed as soon as possible (before the next integration build).</li>
- <li>API compatibility. Component teams should provide unit tests for their public APIs. This ensures developers
- do not break existing clients.</li>
- </ol>
- </p>
- <P>The goal of performance testing is to achieve uniform or better performance as WTP moves
- forwards. As a developer, your dedication to WTP performance is strongly desired. To ensure the
- performance of WTP does not regress over time, developers should provide performance test cases
- along side with their features, etc. Developers are also expected to verify their
- bug fixes and features contribution against existing performance test cases. If something is not performing
- well, open a bug. Use performance as the keyword. Click <a href="https://bugs.eclipse.org/bugs/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=performance&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">here</a> to see a list of all the
- currently open performance bugs in WTP.</P>
- <p>Eclipse has a <a href="http://www.eclipse.org/test-and-performance/index.html">performance infrastructure</a> in place for measuring and tracking
- performance. The performance processes described in this document are modeled around the same
- infrastructure. To create and run tests under this infrastructure, please refer to the
- <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.test.performance/doc/Performance%20Tests%20HowTo.html">Eclipse Tests How-To document</a>.
- Eclipse also has tips and tools to aid developers to debug
- and track down performance problems. They are listed here:
- <ol>
- <li><a href="http://www.eclipse.org/eclipse/development/performance/bloopers.html">Performance bloopers</a></li>
- <li><a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-core-home/dev.html#tools">Core tools</a></li>
- <li><a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-swt-home/dev.html#tools">SWT tools</a></li>
- </ol>
- </p>
- <p>Components may have their own testing requirements. For example,
- the server tools framework often call APIs on server extensions to retrieve data about the
- extension. Some of these APIs must be short running as they are called from the UI. The server
- tools framework provides abstract performance test cases that extensions should extend to verify
- that code contributed by the extension does not regress performance in the base framework.
- Performance requirements from component teams are listed in a document which is located in that
- components development directory in CVS. Please refer to the <a href="http://www.eclipse.org/webtools/development/WTPDevelopmentPractice.html">WTP Development Practices</a>
- document regarding any development related issues.
- </p>
- </TD>
- </TR>
-</table>
-
-<table border=0 cellspacing=5 cellpadding=2 width="100%" >
- <tr>
- <td align=LEFT valign=TOP colspan="3" bgcolor="#0080C0"> <b><font face="Arial,Helvetica" color="#FFFFFF"><a name="policy"></a>Creating junit test cases</font></b></td>
- </tr>
- <tr>
- <td align="LEFT" valign="TOP">
- <p>Here's a laundry list for integrating test plugins into the WTP build:
- <ol>
- <li>Commit the plugin into CVS, use the component's "performance-tests" folder. For example,
- the org.eclipse.wst.wsdl.tests.performance plugin should be placed into
- /home/webtools/wst/components/wsdl/performance-tests.</li>
- <li>Add the plugin to the component's tests map file. This map file can be found inside
- the /home/webtools/org.eclipse.wtp.releng/maps directory.</li>
- <li>Add the plugin to the feature.xml file. This file can be found inside the
- /home/webtools/<sub-project>/assembly/features/<performance feature> directory.</li>
- <li>Update test.properties and test.xml inside /home/webtools/org.eclipse.wtp.releng/testScripts to include
- the new performance plugins.</li>
- </ol>
- The <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.test.performance/doc/Performance%20Tests%20HowTo.html">Eclipse Tests How-To document</a>
- has a very thorough explaination on how to create and run performance test cases using the Eclipse
- performance infrastructure.
- </p>
- </td>
- </tr>
-</table>
-
-<table border=0 cellspacing=5 cellpadding=2 width="100%" >
- <tr>
- <td align=LEFT valign=TOP colspan="3" bgcolor="#0080C0"> <b><font face="Arial,Helvetica" color="#FFFFFF">WTP performance process</font></b></td>
- </tr>
- <tr>
- <td align="LEFT" valign="TOP">
- <p>This section describes the process for tracking performance in WTP. It is based on the
- process used by the Eclipse Platform Project. All performance tests must be automated.
- Performance tests are run every week using Thursday's
- integration builds. Performance tests should:
- <ol>
- <li>never have compile errors</li>
- <li>always run to completion</li>
- </ol>
- </p>
- <p>If either condition fails, failures should be handled immediately according to the
- <a href="http://www.eclipse.org/webtools/development/WTPDevelopmentPractice.html">WTP Development Practices document</a>.
- Performance results are store in a Cloudscape database and are compared against results from
- the previous release. In case of a regression, a note will be posted to the mailing list
- indicating the problem.
- <ol>
- <li>the developer who introduced the regression should fix the performance problem</li>
- <li>if the regression can be justified by a new feature, then the PMC must get involved
- and decide how important that feature is (ex. any competition, etc). Solutions may
- include, but not limited to, making the feature optional (ex. create a preference and turn
- it off by default), so only users who wish to use it have to pay for it.</li>
- </ol>
- </p>
- <p>Performance results from the weekly integration build are rendered into a graph, and is
- linked to on the build page. This graph provides a simple comparison between the integration
- build and the reference build.
- </p>
- <p>To run performance tests for a build that's available from the Eclipse download Web site:
- <ol>
- <li>Check out /home/webtools/org.eclipse.wtp.releng</li>
- <li>Change the properties files to fit your system (buildAll.properties, tests.properties, build.cfg and etc)</li>
- <li>Open a command prompt and navigate to the org.eclipse.wtp.releng directory</li>
- <li>Run the following command:
- <p>ant -f cruise.xml -DbuildType=<buildType> -DbuildId=<buildId> -Dtimestamp=<timestamp> performance</p>
- <p>For example:</p>
- <p>ant -f cruise.xml -DbuildType=N -DbuildId=N20041127 -Dtimestamp=200411271458 performance</p>
- </li>
- </ol>
- Running performance tests for a local build is similar. Go to your ${buildDirectory} directory and check the
- buildType, buildId and timestamp for your local build. Go through the same steps as above. If you have a Cloudscape
- database setup (refer to the <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.test.performance/doc/Performance%20Tests%20HowTo.html">Eclipse Tests How-To document</a>),
- then the performance results will be written to the ${testDir}/results directory, else the performance results
- will be displayed in the console.
- </p>
- </td>
- </tr>
-</table>
-
-</html>
diff --git a/development/updatesite/figure1.gif b/development/updatesite/figure1.gif
deleted file mode 100644
index 5b4a6aa..0000000
--- a/development/updatesite/figure1.gif
+++ /dev/null
Binary files differ
diff --git a/development/updatesite/figure1.jpg b/development/updatesite/figure1.jpg
deleted file mode 100644
index 5e44057..0000000
--- a/development/updatesite/figure1.jpg
+++ /dev/null
Binary files differ
diff --git a/development/updatesite/updatesite.html b/development/updatesite/updatesite.html
deleted file mode 100644
index 400defd..0000000
--- a/development/updatesite/updatesite.html
+++ /dev/null
@@ -1,83 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../../default_style.css" type="text/css">
-<link rel="stylesheet" href="../../../webtools/wtp.css" type="text/css">
-<title>Web Tools Platform Update Site</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">WTP Update Site</font>
-<br>
-<font class="indexsub">Web Tools Platform Update Site</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<col width="16">
-<col width="*">
-<tbody>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p align="right">
-<em>Updated 2005-08-11</em>
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Known issues</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>
-Currently you must install WTP and its required features/plug-ins into the default location (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=103064">103064</a>).
-</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<br>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Using the Update Site</font></b></td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<p>The Web Tools Platform is now available from the Eclipse.org Update Site. To install the Web Tools Platform using Eclipse's built-in update manager, follow the instructions below:</p>
-</td>
-</tr>
-<tr>
-<td valign="top" align="right"> </td><td valign="top">
-<ol>
-
-<li>Click on the <b>Help</b> menu, and then <b>Software Updates</b> > <b>Find and Install...</b> to open the Install/Update wizard.</li>
-
-<li>Select <b>Search for new features to install</b> and click <b>Next</b>.</li>
-
-<li>By default, the Eclipse.org update site should already be available. Enable the <b>Eclipse.org update site</b> checkbox and click <b>Finish</b>. </li>
-
-<li>You can choose a mirror site, however, not all mirror sites have WTP and its required features (EMF, GEF and JEM). Click <b>OK</b>.</li>
-
-<li>After the update manager finishes searching for available updates, the following dialog will open:
-<br>
-<img src="figure1.jpg" border="0" alt="Update Feature selection dialog"></li>
-
-<li>Expand the <b>Eclipse.org update site</b> node and enable the <b>WTP 0.7</b> checkbox. Click the <b>Select Required</b> button to enable the features required by WTP which are not already installed. Click <b>Next</b> to continue.</li>
-
-<li>Review and accept the license agreements for each Feature and click <b>Next</b>, then <b>Finish</b>.</li>
-
-<li>The update manager will take some time to download all of the Features. Many of the downloads are not <em>signed</em>, so you may wish to click the <b>Install All</b> button if the <b>Feature Verification</b> dialog opens.</li>
-
-<li>After Eclipse verifies and installs the downloaded Features, it is recommended that you restart Eclipse.</li>
-
-</ol>
-</td>
-</tr>
-</tbody>
-</table>
-</body>
-</html>
diff --git a/development/updatesite/updatesite.xml b/development/updatesite/updatesite.xml
deleted file mode 100644
index fae5b2e..0000000
--- a/development/updatesite/updatesite.xml
+++ /dev/null
@@ -1,33 +0,0 @@
-<?xml-stylesheet type="text/xsl" href="../../wtphome.xsl"?>
-<html>
-<head>
- <title>Web Tools Platform Update Site</title>
- <meta name="root" content="../../.." />
-</head>
-<body>
-
-<h1>WTP Update Site</h1>
-<p align="right"><em>Updated 2005-08-11</em></p>
-
-<h2>Known issues</h2>
-<p>
-Currently you must install WTP and its required features/plug-ins into the default location (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=103064">103064</a>).
-</p>
-<br/>
-<h2>Using the Update Site</h2>
-<p>The Web Tools Platform is now available from the Eclipse.org Update Site. To install the Web Tools Platform using Eclipse's built-in update manager, follow the instructions below:</p>
-<ol>
-<li>Click on the <b>Help</b> menu, and then <b>Software Updates</b> > <b>Find and Install...</b> to open the Install/Update wizard.</li>
-<li>Select <b>Search for new features to install</b> and click <b>Next</b>.</li>
-<li>By default, the Eclipse.org update site should already be available. Enable the <b>Eclipse.org update site</b> checkbox and click <b>Finish</b>. </li>
-<li>You can choose a mirror site, however, not all mirror sites have WTP and its required features (EMF, GEF and JEM). Click <b>OK</b>.</li>
-<li>After the update manager finishes searching for available updates, the following dialog will open:
-<br/><img src="figure1.jpg" border="0" alt="Update Feature selection dialog" /></li>
-<li>Expand the <b>Eclipse.org update site</b> node and enable the <b>WTP 0.7</b> checkbox. Click the <b>Select Required</b> button to enable the features required by WTP which are not already installed. Click <b>Next</b> to continue.</li>
-<li>Review and accept the license agreements for each Feature and click <b>Next</b>, then <b>Finish</b>.</li>
-<li>The update manager will take some time to download all of the Features. Many of the downloads are not <em>signed</em>, so you may wish to click the <b>Install All</b> button if the <b>Feature Verification</b> dialog opens.</li>
-<li>After Eclipse verifies and installs the downloaded Features, it is recommended that you restart Eclipse.</li>
-</ol>
-
-</body>
-</html>
diff --git a/development/working_groups.html b/development/working_groups.html
deleted file mode 100644
index c5c3d70..0000000
--- a/development/working_groups.html
+++ /dev/null
@@ -1,384 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta http-equiv="CONTENT-TYPE" content="text/html; charset=UTF-8" />
-<title>Eclipse WTP working groups</title>
-<link rel="stylesheet" href="../wtp.css" type="text/css" />
-</head>
-<body lang="fr-FR" text="#000000" link="#0000ee" vlink="#551a8b"
- bgcolor="#ffffff" dir="LTR">
-<table width="100%" border="0" cellpadding="2" cellspacing="5"
- style="page-break-before: always">
- <tr>
- <td width="60%">
- <p align="LEFT"><b><font face="sans-serif" size="6">Eclipse WTP
- working groups</font></b><br />
- <font size="1" face="sans-serif" color="#8080ff">The Eclipse Web Tools
- Platform project</font></p>
- </td>
- <td width="40%">
- <p><img src="http://www.eclipse.org/images/Idea.jpg" name="Image1"
- align="MIDDLE" hspace="50" width="120" height="86" border="0"
- alt="Idea.jpg" /></p>
- </td>
- </tr>
-</table>
-
-<table width="100%" border="0" cellpadding="2" cellspacing="0">
- <col width="7*" />
- <col width="249*" />
- <tr>
- <td colspan="2" width="100%" valign="TOP" bgcolor="#0080c0"
- align="left"><b><font face="sans-serif" color="#ffffff">Goal of this
- document (last update: October 20, 2004)</font></b></td>
- </tr>
-
- <tr>
- <td width="3%" valign="TOP">
- <p align="RIGHT"> </p>
- </td>
- <td width="97%">
- <p>This is an evolving document with two goals in mind:</p>
- <p></p>
- <ul>
- <li>The first goal is to present existing Eclipse WTP working groups,
- and the organizations and people working in that groups on a regular
- basis</li>
- <li>The second goal is to give (hopefully) accurate information about
- these groups; directions of the working groups and major news will
- take place here.</li>
- </ul>
- <p></p>
- </td>
- </tr>
- <tr>
- <td width="3%" valign="top" align="right"><img
- src="http://www.eclipse.org/images/Adarrow.gif" alt="arrow" /></td>
- <td width="97%"><a href="#SERVER_TOOLING"><b>Server tooling</b></a></td>
- </tr>
-
- <tr>
- <td width="3%" valign="top" align="right"><img
- src="http://www.eclipse.org/images/Adarrow.gif" alt="arrow" /></td>
- <td width="97%"><a href="#FLEXIBLE_PROJECT_LAYOUT"><b>Flexible project
- layout</b></a></td>
- </tr>
-
- <tr>
- <td width="3%" valign="top" align="right"><img
- src="http://www.eclipse.org/images/Adarrow.gif" alt="arrow" /></td>
- <td width="97%"><a href="#SSE"><b>Structured Source Editing</b></a></td>
- </tr>
-
- <tr>
- <td width="3%" valign="top" align="right"><img
- src="http://www.eclipse.org/images/Adarrow.gif" alt="arrow" /></td>
- <td width="97%"><a href="#DATA_TOOLS"><b>Data tools</b></a></td>
- </tr>
-
- <tr>
- <td width="3%" valign="top" align="right"><img
- src="http://www.eclipse.org/images/Adarrow.gif" alt="arrow" /></td>
- <td width="97%"><a href="#OTHER_GROUPS"><b>Other groups</b></a></td>
- </tr>
-
- <tr>
- <td width="3%"></td>
- <td width="97%">
- <p><b>Groups' contact</b> : You want to join ? contact the WTP team
- through the eclipse.webtools newsgroup! See <a
- href="http://www.eclipse.org/newsgroups/index.html"> Eclipse
- newsgroups</a>.</p>
- </td>
- </tr>
-
- <tr>
- <td colspan="2" width="100%" valign="top" align="left"
- bgcolor="#0080c0"><a name="SERVER_TOOLING" /> <font color="#ffffff"
- face="sans-serif"> <b>Server tooling</b></font></td>
- </tr>
-
- <tr>
- <td width="3%"></td>
- <td width="97%">
- <table border="0" cellpadding="0" style="border-collapse: collapse"
- bordercolor="#111111" width="100%" id="AutoNumber1" cellspacing="0">
- <tr>
- <td width="50%" align="left" valign="top"><b>News</b>
- <ul>
- <li>Requirement gathered for server tooling are <a
- href="http://wiki.objectweb.org/eclipse-webtools/Wiki.jsp?page=ServerTooling">here</a></li>
- <li>Initial code drop, in August/September, for support of Web
- browsers, TCP/IP monitor, Java & J2EE servers, Tomcat. See <a
- href="http://www.eclipse.org/newsportal/article.php?id=1315&group=eclipse.webtools">drop
- announcement</a> (no additional requirement for this code - just
- the Eclipse 3.0 platform).</li>
- <li>Review of server tools architecture is been conducted</li>
- <li>XML based configuration been included to IBM server tools</li>
- <li>Progress made on generic server code</li>
- <li>How to contribute a server tool document draft to be published</li>
- <li>Bull working on JOnAS server tool implementation</li>
- <li>JBoss working on JBoss server tool implementation</li>
- </ul>
-
- <b>Milestones</b>
- <ul>
- <li>Milestone <a
- href="http://www.eclipse.org/webtools/development/planning/milestone_plan_1_0.html#M1">M1</a>
- (<a href="http://download.eclipse.org/webtools/downloads/">released
- October 15</a>) and <a
- href="http://www.eclipse.org/webtools/development/planning/milestone_plan_1_0.html#M2">M2</a>
- (December 15)</li>
- </ul>
- </td>
- <td width="50%" align="left" valign="top"><b>Group composition</b>
- <ul>
- <li>BULL, Gorkem Ercan, Eteration, IBM, JBoss, SAP<br />
- <br />
- </li>
- <li>Someone forgotten ? tell us: <a
- href="mailto:wtp-web-site@objectweb.org">wtp-web-site@objectweb.org</a></li>
- </ul>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%"> </td>
- </tr>
- <tr>
- <td colspan="2" width="100%" valign="top" bgcolor="#0080c0"
- align="left"><a name="FLEXIBLE_PROJECT_LAYOUT" /><font
- color="#ffffff"><font face="sans-serif"><b>Flexible project layout</b></font>
- </font></td>
- </tr>
-
- <tr>
-
- <td width="3%">
- <p> </p>
- </td>
-
- <td width="97%">
- <table border="0" cellpadding="0" style="border-collapse: collapse"
- bordercolor="#111111" width="100%" id="AutoNumber1" cellspacing="0">
- <tr>
- <td width="50%" align="left" valign="top"><b>News</b>
- <ul>
-
- <li>Requirement gathered for project layout are <a
- href="http://wiki.objectweb.org/eclipse-webtools/Wiki.jsp?page=ProjectLayout">here</a></li>
-
- </ul>
-
- <b>Milestones</b>
- <ul>
- <li>Milestone <a
- href="http://www.eclipse.org/webtools/development/planning/milestone_plan_1_0.html#M2">M2</a>
- (December 15) and <a
- href="http://www.eclipse.org/webtools/development/planning/milestone_plan_1_0.html#M3">M3</a>
- (February 15)</li>
-
- </ul>
- </td>
-
- <td width="50%" align="left" valign="top"><b>Group composition</b>
- <ul>
- <li>Gorkem Ercan, Eteration, Frameworx, Genuitec<br />
- <br />
- </li>
-
- <li>Someone forgotten ? tell us: <a
- href="mailto:wtp-web-site@objectweb.org">wtp-web-site@objectweb.org</a></li>
-
-
-
- </ul>
-
-
- </td>
- </tr>
- <tr>
-
- <td width="100%" colspan="3" align="left" valign="top"></td>
- </tr>
-
- </table>
-
- </td>
-
- </tr>
-
- <tr>
-
- <td width="3%">
-
- <p> </p>
- </td>
-
- <td width="97%"> </td>
-
- </tr>
-
- <tr>
- <td colspan="2" width="100%" valign="top" bgcolor="#0080c0"
- align="left"><a name="SSE" /><font color="#ffffff" face="sans-serif">
- <b>Structured Source Editing (SSE)</b></font></td>
- </tr>
-
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <table border="0" cellpadding="0" style="border-collapse: collapse"
- bordercolor="#111111" width="100%" id="AutoNumber1" cellspacing="0">
- <tr>
- <td width="50%" align="left" valign="top"><b>News</b>
- <ul>
- <li>Requirement gathered for SSE are <a
- href="http://wiki.objectweb.org/eclipse-webtools/Wiki.jsp?page=StructuredEditor">here</a></li>
- <li>Weekly calls are performed between teams on this topic</li>
- <li>After a code review, some SSE parts are in preparation for
- moving into CVS</li>
-
- <li>API clean up on going</li>
-
- </ul>
- <b>Milestones</b>
- <ul>
- <li>Milestone <a
- href="http://www.eclipse.org/webtools/development/planning/milestone_plan_1_0.html#M2">M2</a>
- (December 15) and <a
- href="http://www.eclipse.org/webtools/development/planning/milestone_plan_1_0.html#M3">M3</a>
- (February 15)</li>
-
- </ul>
- </td>
- <td width="50%" align="left" valign="top"><b>Group composition</b>
- <ul>
- <li>IBM, Innoopract, Jens Lukowski, OpenWide<br />
- <br />
- </li>
-
- <li>Someone forgotten ? tell us: <a
- href="mailto:wtp-web-site@objectweb.org">wtp-web-site@objectweb.org</a></li>
- </ul>
- </td>
- </tr>
- <tr>
- <td width="100%" colspan="3" align="left" valign="top"></td>
- </tr>
- </table>
- </td>
-
- </tr>
-
-
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%"> </td>
-
- </tr>
- <tr>
-
- <td colspan="2" width="100%" align="left" valign="top"
- bgcolor="#0080c0"><a name="DATA_TOOLS" /><font color="#ffffff"
- face="sans-serif"> <b>Data tools</b></font></td>
- </tr>
-
-
-
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">
- <table border="0" cellpadding="0" style="border-collapse: collapse"
- bordercolor="#111111" width="100%" id="AutoNumber1" cellspacing="0">
- <tr>
- <td width="50%" align="left" valign="top"><b>News</b>
- <ul>
- <li>Exadel is working on that topic : contribution to come</li>
- <li>B.C. Holmes, from the 'Quantum Database Utility' OSS project,
- has joined Eclipse WTP - Welcome !</li>
- <li>Contact with Apache <a
- href="http://incubator.apache.org/projects/derby.html">Derby</a>
- project - Derby integration into Eclipse WTP is targeted (one
- Apache contributor foreseen)</li>
- </ul>
-
- <b>Milestones</b>
- <ul>
- <li>Milestone <a
- href="http://www.eclipse.org/webtools/development/planning/milestone_plan_1_0.html#M2">M2</a>
- (December 15) and <a
- href="http://www.eclipse.org/webtools/development/planning/milestone_plan_1_0.html#M3">M3</a>
- (February 15)</li>
- </ul>
-
- </td>
- <td width="50%" align="left" valign="top"><b>Group composition</b>
- <ul>
- <li>Apache, Exadel, B. C. Holmes, IBM, JBoss (starting
- mid-October), Together Teamlösungen (soon)<br />
- <br />
- </li>
- <li>Someone forgotten ? tell us: <a
- href="mailto:wtp-web-site@objectweb.org">wtp-web-site@objectweb.org</a></li>
- </ul>
- </td>
- </tr>
- <tr>
- <td width="100%" colspan="3" align="left" valign="top"></td>
- </tr>
- </table>
- </td>
- </tr>
-
-
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%"> </td>
- </tr>
-
- <tr>
- <td colspan="2" width="100%" align="left" valign="top"
- bgcolor="#0080c0"><a name="OTHER_GROUPS" /> <font color="#ffffff"><font
- face="sans-serif"> <b>Other groups</b></font></font></td>
- </tr>
- <tr>
- <td width="3%">
- <p> </p>
- </td>
- <td width="97%">This page is mainly related to groups working on code.
- So, these groups are detailled here. But there are other groups just
- like, the architecture group, the marketing group...</td>
- </tr>
- <tr></tr>
-
-
-
-</table>
-<p style="margin-top: 0.5cm; margin-bottom: 0cm"><br />
-</p>
-<p>Please see our <a href="http://eclipse.org/legal/privacy.html">privacy
-policy</a> and website <a
- href="http://eclipse.org/legal/termsofuse.html">terms of use</a>. For
-problems with the eclipse.org site, please contact the <a
- href="mailto:webmaster@eclipse.org">webmaster</a> or read the <a
- href="http://eclipse.org/webmaster/index.html">webmaster FAQ</a> for
-answers to common questions!</p>
-</body>
-
-</html>
diff --git a/downloads.html b/downloads.html
deleted file mode 100644
index 93d3988..0000000
--- a/downloads.html
+++ /dev/null
@@ -1,293 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
-<title>Eclipse Web Tools Platform Project</title>
-<link rel="stylesheet" href="../default_style.css" type="text/css"/>
-</head>
-<body>
-<table border="0" cellspacing="5" cellpadding="2" width="100%">
- <tr>
- <td align="left" valign="top" colspan="2" bgcolor="#0080C0"><b><font
- face="Arial,Helvetica" color="#FFFFFF">Eclipse Web Tools Platform PMC
- Downloads</font></b></td>
- </tr>
- <tr>
- <td height="150">
- <p><b>Getting the latest Downloads </b><br/>
-
- On this page you can find the links to the latest builds produced by
- the <a href="main.html">Eclipse Web Tools Platform</a>
- Project. All downloads are provided under the terms and conditions
- of the Eclipse.org Software User Agreement unless otherwise specified.
- </p>
- <p>If this is your first time visiting eclipse.org, you need to make sure that
- you install a Eclipse Platform SDK before you install the Web Tools Platform. Please note that every
- Web Tools Platform build requires a <i>specific</i> "Stable" or "Release" version
- of the Eclipse Platform and other prerequisite projects as mentioned on its download page.
- Eclipse Platform SDK downloads can be found on
- <a href="http://download.eclipse.org/downloads/index.php" target="_top">Eclipse
- Platform download page</a>. You can read more about the Eclipse
- Platform by visiting the <a href="../eclipse/index.html" target="_top">Eclipse
- Platform</a> main page and reading the Eclipse Platform <a
- href="../eclipse/faq/eclipse-faq.html">FAQ</a>.</p>
- </td>
- </tr>
-</table>
-<hr/>
-<table border="0" cellspacing="5" cellpadding="2" width="100%">
- <tr bgcolor="#0080C0">
- <td align="left" valign="top" >
- <font color="#ffffff"><b>Web Tools Platform Resources</b></font>
- </td>
- </tr>
- <tr><td>
- Please make sure to look at our <a href="main.html">project home page</a> for a wealth of
- information about this project, including the
- <a href="http://www.eclipse.org/webtools/testtutorials/gettingstarted/GettingStarted.html">Getting Started</a>
- guide and <a href ="http://www.eclipse.org/webtools/community/community.html#tutorials">Tutorials</a>.
- </td></tr>
-</table>
-
-
-<hr/>
-<table border="0" cellspacing="5" cellpadding="2" width="100%">
- <tr bgcolor="#0080C0">
- <td align="left" valign="top" colspan="2">
- <font color="#ffffff"><b>Build Notes</b></font>
- </td>
- </tr>
-</table>
-
-<table width="80%" cellspacing="0" cellpadding="3" height="124" border="1">
- <tr>
- <td width="30%"><b>Build</b></td>
- <td width="70%"><b>Notes</b></td>
- </tr>
-
-<tr>
- <td width="30%" valign="top"><a target="_top"
- href="http://download.eclipse.org/webtools/downloads/drops/R-0.7-200507290654/">0.7 Release</a>
- <br />
- Available July 29, 2005<br /></td>
-
- <td width="70%"><p>This is the official WTP 0.7 Release build. The
- focusses since M5 have been increasing stability, polishing the UI,
- and applying critical bug fixes. There were many <a
- href="https://bugs.eclipse.org/bugs/buglist.cgi?product=Web+Tools&resolution=FIXED&chfieldfrom=2005-07-01&chfieldto=2005-07-28&chfield=resolution&order=bugs.bug_id,bugs.bug_severity">bugs
- fixed</a> for this release but don't let that stop you from reporting
- more -- if it isn't in Bugzilla it's not a bug!
- </p>
- <p>And remember to please <a
- href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=reporter&z_axis_field=&query_format=report-table&product=Web+Tools&bug_status=RESOLVED&format=table&action=wrap">
- verify the fixes</a> for the bugs you've reported.</p>
- </td>
- </tr>
-<!--
-<tr>
- <td width="30%" valign="top"><a target="_top"
- href="http://download.eclipse.org/webtools/downloads/drops/S-0.7RC5-200507280540/">0.7RC5</a>
- <br />
- Available July 28, 2005<br /></td>
-
- <td width="70%">
- This is the fifth Release Candidate for WTP 0.7.
- </td>
-</tr>
-<tr>
- <td width="30%" valign="top"><a target="_top"
- href="http://download.eclipse.org/webtools/downloads/drops/S-0.7RC4-200507270811/">0.7RC4</a>
- <br />
- Available July 27, 2005<br /></td>
-
- <td width="70%">
- This is the fourth Release Candidate for WTP 0.7.
- </td>
-</tr>
-<tr>
- <td width="30%" valign="top"><a target="_top"
- href="http://download.eclipse.org/webtools/downloads/drops/S-0.7RC3-200507250308/">0.7RC3</a>
- <br />
- Available July 25, 2005<br /></td>
-
- <td width="70%">
- This is the third Release Candidate for WTP 0.7, differing primarily by being built against the JEM 1.1 Release. The dependencies for WTP are now all Release builds.
- </td>
-</tr>
-<tr>
- <td width="30%" valign="top"><a target="_top"
- href="http://download.eclipse.org/webtools/downloads/drops/S-0.7RC2-200507221429/">0.7RC2</a>
- <br />
- Available July 22, 2005<br /></td>
-
- <td width="70%">
-
- <p>This is the second Release Candidate produced for WTP 0.7. The main focusses have been increased stability and critical bug fixes.
-
- <p>There were many bugs fixed for this second release candidate but only a few more will be fixed before the 0.7 release.
- Don't let that stop you from reporting many more, though - - if it isn't in Bugzilla it's not a bug!</p><p>And remember to please
- <a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=reporter&z_axis_field=&query_format=report-table&product=Web+Tools&bug_status=RESOLVED&format=table&action=wrap">
- verify the fixes</a> for the bugs you've reported.</p>
- </td>
- </tr>
-<tr>
- <td width="30%" valign="top"><a target="_top"
- href="http://download.eclipse.org/webtools/downloads/drops/S-0.7RC1-200507150303/">0.7RC1</a>
- <br />
- Available July 15, 2005<br /></td>
-
- <td width="70%">
-
- <p>This is the first Release Candidate produced for WTP 0.7. The main focusses have been increased stability and improved user interfaces.
-
- <p>There were <a
- href="https://bugs.eclipse.org/bugs/buglist.cgi?product=Web+Tools&resolution=FIXED&chfieldfrom=2005-07-01&chfieldto=2005-07-14&chfield=resolution&order=bugs.bug_id,bugs.bug_severity">
- 201 bugs</a> fixed for this first release candidate. Bug fixing will continue but it slow down through RC2 to provide greater stability for testing while ramping down for the 0.7 release.
- Don't let that stop you from reporting many more, though -- only reported bugs can be fixed!</p><p>And remember to please
- <a href="https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=reporter&z_axis_field=&query_format=report-table&product=Web+Tools&bug_status=RESOLVED&format=table&action=wrap">
- verify the fixes</a> for the bugs you've reported.</p>
- </td>
- </tr>
- -->
-<tr>
- <td width="30%" valign="top"><a target="_top"
- href="http://download.eclipse.org/webtools/downloads/drops/S-1.0M5-200506302219/">0.7M5</a>
- <br />
- Available July 1, 2005<br /></td>
-
- <td width="70%">
-
- <p>This milestone focussed on code cleanup and stability, especially for the Server Tools and Flexible Projects.
- Please see our the <a href="http://www.eclipse.org/webtools/development/news/0.7M5.html">New and Noteworthy</a>
- for any new features that were still added ;-)
- </p>
- <p>There were <a
- href="https://bugs.eclipse.org/bugs/buglist.cgi?product=Web+Tools&resolution=FIXED&chfieldfrom=2005-04-30&chfieldto=2005-06-30&chfield=resolution&order=bugs.bug_severity,bugs.bug_id">
- 652 bugs</a> fixed for this milestone. But, there are still <a
- href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&bug_severity=major&bugidtype=include&chfieldfrom=&chfieldto=Now&cmdtype=doit&order=bugs.bug_severity,bugs.bug_id">
- some serious bugs </a> to be aware of. And, we hope you
- report many more -- show interest by heavy use!</p>
- </td>
- </tr>
-
-<tr>
- <td width="30%" valign="top"><a target="_top"
- href="http://download.eclipse.org/webtools/downloads/drops/S-1.0M4-200504292037/">1.0M4</a>
- <br />
- Available April 29, 2005 <br /></td>
-
- <td width="70%">
-
- <p>This milestone focussed on API definition and cleanup, especially for the Server Tools and Flexible Projects.
- Please see our the <a href="http://www.eclipse.org/webtools/development/news/1.0M4.html">New and Noteworthy</a>
- for any new features that were still added ;-) </p>
-
- <p>There were <a
- href="https://bugs.eclipse.org/bugs/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&chfieldfrom=2005-02-27&chfieldto=2005-04-29&cmdtype=doit&order=bugs.bug_severity,bugs.bug_id">
- 405 bugs</a> fixed for this milestone. But, there are still <a
- href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&bug_severity=major&bugidtype=include&chfieldfrom=&chfieldto=Now&cmdtype=doit&order=bugs.bug_severity,bugs.bug_id">
- some serious bugs </a> to be aware of. And, we hope you
- report many more -- show interest by heavy use!</p>
- </td>
- </tr>
-<tr>
- <td width="30%" valign="top"><a target="_top"
- href="http://download.eclipse.org/webtools/downloads/drops/S-1.0M3-200502260707/index.html">1.0M3</a>
- <br />
- Available February 26, 2005 <br /></td>
-
- <td width="70%">
-
-
- <p>This milestone offers an significant enhancement in functionality to WTP, mainly in the following areas:</p>
- <ul>
- <li>J2EE and Validation</li>
- <li>Structured Source Editing</li>
- <li>Server Tools</li>
- <li>XML, XSD, and WSDL</li>
- <li>Web Services Tools</li>
- </ul>
-
- <p>Please see our the <a href="http://www.eclipse.org/webtools/development/news/1.0M3.html">New and Noteworthy</a> page
- and read our <a href="http://www.eclipse.org/org/press-release/20050301wtprelease.htm">press release</a> ;-)</p>
-
- <p>There were <a
- href="https://bugs.eclipse.org/bugs/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=2004-12-24&chfieldto=2005-02-26&chfieldvalue=&cmdtype=doit&namedcmd=ALL+WTP&newqueryname=&order=Importance&field0-0-0=noop&type0-0-0=noop&value0-0-0=">
- 187 bugs</a> fixed for this milestone. But, there are still <a
- href="https://bugs.eclipse.org/bugs/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=80811%2C81031%2C71994%2C81030%2C81394%2C81687%2C81710%2C81714%2C81716&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&namedcmd=ALL+WTP&newqueryname=&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">
- some known bugs marked 'major' </a> to be aware of. And, we hope you
- report many more -- show interest by heavy use!</p>
- </td>
- </tr>
- <tr>
- <td width="30%" valign="top"><a target="_top"
- href="http://download.eclipse.org/webtools/downloads/drops/S-1.0M2-200412230036/index.html">1.0M2</a>
- <br />
- Available December 22, 2004 (22:00 EST)<br />
- (same as I20041223 build)</td>
-
- <td width="70%">
-
-
-
- <p>This was a significant milestone accomplishing all our <b>High
- Priority</b> items:</p>
- <ul>
- <li>Project Layouts for Web/J2EE Modules (Simple Web/J2EE project
- layouts)</li>
- <li>XML Editing and Validation</li>
- <li>Database Table content browsing</li>
- </ul>
-
- <p>as well as our <b>Medium Priority</b> items:</p>
- <ul>
-
- <li>JSP Editing and debugging</li>
- <li>XML creation wizards (creates skeleton XML given DTD or XML
- Schema)</li>
- <li>Graphical XML Schema editor</li>
- <li>XML catalog support</li>
- <li>Validation for XML Schema and DTD</li>
- <li>XML example project to jump start users</li>
-
-
- <li>Simple EJB Wizards</li>
- </ul>
- <p>And even one <b>Low Priority</b> item:</p>
-
- <ul>
- <li>Snippets View (but many changes still planned)</li>
- </ul>
-
-
- <p>There were <a
- href="https://bugs.eclipse.org/bugs/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=2004-10-15&chfieldto=2004-12-23&chfieldvalue=&cmdtype=doit&namedcmd=ALL+WTP&newqueryname=&order=Importance&field0-0-0=noop&type0-0-0=noop&value0-0-0=">
- 107 bugs</a> fixed for this milestone. But, there are still <a
- href="https://bugs.eclipse.org/bugs/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=80811%2C81031%2C71994%2C81030%2C81394%2C81687%2C81710%2C81714%2C81716&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&namedcmd=ALL+WTP&newqueryname=&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">
- some known bugs marked 'major' </a> to be aware of. And, we hope you
- report many more -- show interest by heavy use!</p>
- <p>Be sure to check out the <a
- href="http://www.eclipse.org/webtools/wst/components.html">WST</a> and
- <a href="http://www.eclipse.org/webtools/jst/components.html">JST</a>
- components for details on plans, designs, overviews, and test cases.
- There's a nice <a
- href="http://www.eclipse.org/webtools/testtutorials/M2/tutorial1/wtp-tutorial-I.html">mini-test-tutorial</a>
- that describes how to get started and creating a very small web
- application of one servlet and one JSP. As well as overviews of <a
- href="http://www.eclipse.org/webtools/wst/components/sse/m2/m2.html">editing</a>
- and much much more.</p>
- </td>
- </tr>
- <tr>
- <td width="20%"><a target="_top"
- href="http://download.eclipse.org/webtools/downloads/drops/S-1.0M1-200410152212/index.html">1.0M1</a>
- <br />
- Available October 16, 2004</td>
- <td width="80%">Our first milestone (but, sorry, we weren't keeping
- notes then).</td>
-
- </tr>
-</table>
-<p>A more complete list of builds can be found <a href="http://download.eclipse.org/webtools/downloads/">here</a>.</p>
-</body>
-</html>
diff --git a/eclipse_nav.html b/eclipse_nav.html
deleted file mode 100644
index 68c5e1f..0000000
--- a/eclipse_nav.html
+++ /dev/null
@@ -1,65 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Home Navigator</title>
-<base target="main">
-<link rel="stylesheet" href="../nav_style.css" type="text/css">
-</head>
-<body text="#000000" bgcolor="#6699CC" link="#FFFFCC" vlink="#551A8B" alink="#FF0000">
-<table BORDER=0 CELLSPACING=0 CELLPADDING=0 COLS=1 WIDTH="100%" BGCOLOR="#90C8FF" >
- <tr>
- <td VALIGN=CENTER HEIGHT="21" BGCOLOR="#0080C0"> <a href="http://www.eclipse.org" target="_top" class="navhead">
- eclipse home</a></td>
- </tr>
- <tr VALIGN=CENTER>
- <td HEIGHT="21"> <a href="http://eclipse.org/org/index.html" class="nav" target="_top">about us</a></td>
- </tr>
- <tr>
- <td BGCOLOR="#CFFFFF"><img SRC="../images/c.gif" height=1 width=1></td>
- </tr>
- <tr VALIGN=CENTER>
- <td HEIGHT="21"> <a href="http://eclipse.org/projects/index.html" class="nav" target="_top">projects</a></td>
- </tr>
- <tr>
- <td BGCOLOR="#CFFFFF"><img SRC="../images/c.gif" height=1 width=1></td>
- </tr>
- <tr VALIGN=CENTER>
- <td HEIGHT="21"> <a href="http://eclipse.org/downloads/index.php" class="nav" target="_top">downloads</a></td>
- </tr>
- <tr>
- <td BGCOLOR="#CFFFFF"><img SRC="../images/c.gif" height=1 width=1></td>
- </tr>
- <tr VALIGN=CENTER>
- <td HEIGHT="21"> <a href="http://eclipse.org/articles/index.html" class="nav" target="_top">articles</a></td>
- </tr>
- <tr>
- <td BGCOLOR="#CFFFFF"><img SRC="../images/c.gif" height=1 width=1></td>
- </tr>
- <tr VALIGN=CENTER>
- <td HEIGHT="21"> <a href="http://eclipse.org/newsgroups/index.html" class="nav" target="_top">newsgroups</a></td>
- </tr>
- <tr>
- <td BGCOLOR="#CFFFFF"><img SRC="../images/c.gif" height=1 width=1></td>
- </tr>
- <tr valign=CENTER>
- <td valign=CENTER height="21"> <a href="http://eclipse.org/community/index.html" class="nav" target="_top">community</a></td>
- </tr>
- <tr>
- <td bgcolor="#CFFFFF"><img src="../images/c.gif" height=1 width=1></td>
- </tr>
- <tr VALIGN=CENTER>
- <td HEIGHT="21"> <a href="http://eclipse.org/search/search.cgi" class="nav">search</a></td>
- </tr>
- <tr>
- <td BGCOLOR="#CFFFFF"><img SRC="../images/c.gif" height=1 width=1></td>
- </tr>
- <tr VALIGN=CENTER>
- <td HEIGHT="21"> <a href="https://bugs.eclipse.org/bugs/" class="nav">bugs</a></td>
- </tr>
- <tr>
- <td BGCOLOR="#CFFFFF"><img SRC="../images/c.gif" height=1 width=1></td>
- </tr>
-</table>
-</body>
-</html>
diff --git a/eproject-banner.html b/eproject-banner.html
deleted file mode 100644
index d0b1303..0000000
--- a/eproject-banner.html
+++ /dev/null
@@ -1,41 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
- <title>Eclipse Banner</title>
- <meta http-equiv="Content-Type"
- content="text/html; charset=iso-8859-1">
- <style type="text/css">
-.input {background: "#ffffcc";color: "#000000" ;font-weight: normal;}
-a.nav:link { text-decoration: none; color: "#000000"; }
-a.nav:visited { text-decoration: none; color: "#000000"; }
-a.nav:hover { text-decoration: underline; color: "#000000"; }
- </style>
-</head>
-<body text="#ffffcc" bgcolor="#ffffff" link="#0000ee" vlink="#551a8b"
- alink="#ff0000">
-<table border="0" cellspacing="0" cellpadding="0" width="100%">
- <tbody>
- <tr>
- <td width="100%">
- <table border="0" cellspacing="0" cellpadding="0" width="100%"
- bgcolor="#006699">
- <tbody>
- <tr>
- <td bgcolor="#000000" width="116"><a href="http://www.eclipse.org" target="_top">
- <img src="../images/EclipseBannerPic.jpg" width="115" height="50" border="0"></a>
- </td>
- <td width="637">
- <img src="../images/gradient.jpg" border="0" height="50" width="282">
- </td>
- <td width="250">
- <img src="../images/eproject-simple.GIF" width="250" height="48">
- </td>
- </tr>
- </tbody>
- </table>
- </td>
- </tr>
- </tbody>
-</table>
-</body>
-</html>
diff --git a/faq/.project b/faq/.project
deleted file mode 100644
index 4fc4177..0000000
--- a/faq/.project
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
- <name>faq</name>
- <comment></comment>
- <projects>
- </projects>
- <buildSpec>
- </buildSpec>
- <natures>
- </natures>
-</projectDescription>
diff --git a/faq/CommitterFAQ.html b/faq/CommitterFAQ.html
deleted file mode 100644
index 2701b84..0000000
--- a/faq/CommitterFAQ.html
+++ /dev/null
@@ -1,570 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../default_style.css" type="text/css">
-<link rel="stylesheet" href="../../webtools/wtp.css" type="text/css">
-<title>wtp committer faq</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">wtp committer faq</font>
-<br>
-<font class="indexsub">frequently asked questions and answers</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#cccccc">
-<tbody>
-<tr>
-<td width="90%"><b><font size="+1" face="Arial,Helvetica" color="#000000"><a name="">About the FAQ</a></font></b></td><td align="right" width="10%"></td>
-</tr>
-</tbody>
-</table>
-<br>
- Last updated: October 14, 2005<br>
-<br>
-<p>For problems with this FAQ please open a <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Web%20Tools&component=FAQ">bug report</a>.</p>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#cccccc">
-<tbody>
-<tr>
-<td width="90%"><b><font size="+1" face="Arial,Helvetica" color="#000000"><a name="toc">Table of Contents</a></font></b></td><td align="right" width="10%"></td>
-</tr>
-</tbody>
-</table>
-<ul>
-<li>
-<b>General</b>
-<ol>
-<li>
-<a href="#general_1">Who do we contact in order to get commiter passwords reset?</a>
-</li>
-<li>
-<a href="#general_2">How do I change my dev.eclipse.org password?</a>
-</li>
-</ol>
-<br>
-</li>
-<li>
-<b>Build/CVS</b>
-<ol>
-<li>
-<a href="#cvs_1">What is the CVS info for the webtools project?</a>
-</li>
-<li>
-<a href="#cvs_2">How do I add my plugin to the WTP CVS repository?</a>
-</li>
-<li>
-<a href="#cvs_3">Where can I find more information about CVS?</a>
-</li>
-<li>
-<a href="#cvs_4">Is there a tool for releasing changes?</a>
-</li>
-<li>
-<a href="#cvs_5">How do I release my changes?</a>
-</li>
-<li>
-<a href="#cvs_6">What do I need to do before releasing changes?</a>
-</li>
-<li>
-<a href="#cvs_7">How do I add a new plugin to WTP?</a>
-</li>
-<li>
-<a href="#cvs_8">How do I jar my plug-in?</a>
-</li>
-</ol>
-<br>
-</li>
-<li>
-<b>Source Code</b>
-<ol>
-<li>
-<a href="#source_1">What copyrights should we use? </a>
-</li>
-<li>
-<a href="#source_2">Is there a tool to update the copyright?</a>
-</li>
-<li>
-<a href="#source_3">What are the package naming conventions?</a>
-</li>
-<li>
-<a href="#source_4">What comment should I use when declaring public provisional API?</a>
-</li>
-</ol>
-<br>
-</li>
-<li>
-<b>Website</b>
-<ol>
-<li>
-<a href="#website_1">Who maintains the WTP website?</a>
-</li>
-<li>
-<a href="#website_2">How do I update the WTP website?</a>
-</li>
-<li>
-<a href="#website_3">What is the CVS info for the webtools website?</a>
-</li>
-</ol>
-<br>
-</li>
-</ul>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#cccccc">
-<tbody>
-<tr>
-<td width="90%"><b><font size="+1" face="Arial,Helvetica" color="#000000"><a name="General">General</a></font></b></td><td align="right" width="10%"><a href="#toc">top</a></td>
-</tr>
-</tbody>
-</table>
-<ol>
-<li>
-<a name="general_1"><b>Who do we contact in order to get commiter passwords reset?</b></a>
-<br>
-<br>
- You need to contact the Eclipse webmaster at <a xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" href="mailto:webmaster@eclipse.org">webmaster@eclipse.org</a>.
- <br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="general_2"><b>How do I change my dev.eclipse.org password?</b></a>
-<br>
-<br>
- You can change your password using the committer tools available at <a xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" href="https://dev.eclipse.org/committers/">https://dev.eclipse.org/committers/</a>.
- <br>
-<br>
-<hr>
-<br>
-</li>
-</ol>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#cccccc">
-<tbody>
-<tr>
-<td width="90%"><b><font size="+1" face="Arial,Helvetica" color="#000000"><a name="Build/CVS">Build/CVS</a></font></b></td><td align="right" width="10%"><a href="#toc">top</a></td>
-</tr>
-</tbody>
-</table>
-<ol>
-<li>
-<a name="cvs_1"><b>What is the CVS info for the webtools project?</b></a>
-<br>
-<br>
- server : dev.eclipse.org<br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
- path : /cvsroot/webtools
- <br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="cvs_2"><b>How do I add my plugin to the WTP CVS repository?</b></a>
-<br>
-<br>
- <ol xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <li>On your plugin project select <B>Team->Share Project...</B> context menu.</li>
- <li>Choose existing repository location (or create a new one if you haven't) for
- <B>dev.eclipse.org:/home/webtools</B>
- </li>
- <li>On the next page, if you know exactly where the plugin should be located in the
- repository, then select the "Use specified module name" radio button and
- type in the full path. However, to be safe, it's recommended browsing the repository
- to obtain the correct path, and then adding the module name. Here is an example:<br/>
- <br/>
- Select the "Use an existing module".<br/>
- Browse and then select the folder where you want your new plugin to reside.<br/>
- <br/>
- <img border="0" src="images/shareProject1.gif" width="485" height="602"/>
-<br/>
- <br/>
- Notice that the text field is filled in with the path. Reselect the "Use
- specified module name:" radio button, and append your plugin's name.<br/>
- <br/>
- <img border="0" src="images/shareProject2.gif" width="486" height="602"/>
- </li>
- </ol>
-
-<br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="cvs_3"><b>Where can I find more information about CVS?</b></a>
-<br>
-<br>
- The <a xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" href="http://dev.eclipse.org/viewcvs/index.cgi/?cvsroot=WebTools_Project">WTP
- CVS respository page</a> contains links to useful CVS documentation including how to
- use Eclipse with CVS.
- <br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="cvs_4"><b>Is there a tool for releasing changes?</b></a>
-<br>
-<br>
- Yes. The releng tool plugin is available from the <a xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" href="http://www.eclipse.org/downloads" target="_top">Eclipse download page</a>. Each version
- of Eclipse contains its own releng tool plugin. Select the version of Eclipse you're
- using. The releng tool plugin is found at the bottom of the page.
- <br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="cvs_5"><b>How do I release my changes?</b></a>
-<br>
-<br>
- <ol xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <li>
- Commit your changes to the CVS repository. (For information about
- CVS and committing see the FAQ entry <a href="#cvs_3">Where can I find more information about CVS?</a>)
- </li>
- <li>
- Extract the releng project from the CVS repository. This project contains the
- map files.
- </li>
- <li>
- <b>
- *note: It is strongly recommended that you use the releng tool to release
- your changes.
- </b>
- <p>
- You now have to tag your source files and update the corresponding map entries.
- Although you can do this manually it is much easier and less error prone to use
- the releng tool. (See FAQ entry <a href="#cvs_4">Is there a tool for releasing
- changes?</a>)
- </p>
- <ol>
- <li>
- Select the plug-in you want to release, right click on it and select Team->Release as shown below.<br/>
-<br/>
- <img src="images/releasemenu.gif"/>
- </li>
- <li>
- Select the releng project as the map project. Click Next.
- </li>
- <li>
- If not already selected, select the plug-ins you want to release. Click Next.
- </li>
- <li>
- The page displays the changes between the last released version of the plug-in
- and what is in HEAD. Review the changes. If everything is correct, click Next.
- </li>
- <li>
- Enter the tag you want to use to release the changes. WTP uses tags of the form
- vYYYYMMDD_HHMM. Click Next.
- </li>
- <li>
- The page displays the changes to the map files. Review the changes. If everything
- is correct, click Next.
- </li>
- <li>
- Enter a comment for the release operation and click Finish.
- </li>
- </ol>
- </li>
- </ol>
-
-<br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="cvs_6"><b>What do I need to do before releasing changes?</b></a>
-<br>
-<br>
- <p xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- It depends. If you're releasing an isolated fix, you're probably safe to run the
- JUnit tests for the plugin and, if all pass, release your fix. If you're making
- a breaking provisional API change (remember, you cannot make breaking API changes)
- you should announce the change to the WTP dev list advising
- what has changed, why, and how existing consumers of the provisional API can
- adapt their plugins to the change.
- </p>
- <p xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- It is also good practice to use a current WTP development driver when making
- changes so as not to cause a break in your plugin due to changes in other
- plugins.
- </p>
-
-<br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="cvs_7"><b>How do I add a new plugin to WTP?</b></a>
-<br>
-<br>
- <p xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <b>Follow this proceduce closely. Mistakes will likely cause a build breakage.</b>
-<br/>
- There are three tasks to add a new plugin to WTP:
- <ol>
- <li>
- Commit your new plug-in to the CVS repository. See <a href="#cvs_2">How do I add my plugin to the WTP CVS repository?</a>
- </li>
- <li>
- <p>
- Add your plugin to the appropriate feature. Features are located under the
- subproject's assembly component. For example, for WST you can find features
- at wst/components/assembly/features.
- </p>
- <p>
- A feature entry will look like the following:<br/>
- <br/>
- <plugin<br/>
- id="org.eclipse.wst.common.uriresolver"<br/>
- download-size="0"<br/>
- install-size="0"<br/>
- version="0.0.0"/><br/>
- </p>
- <p>
- After you've added your plugin to the feature, commit the changes
- and release the feature.
- </p>
- </li>
- <li>
- Add your plugin to the appropriate map file. Map files are located in the
- releng component. A map file entry will look like the following:<br/>
- <br/>
- plugin@org.eclipse.wst=v20050718_2336,:pserver:anonymous@dev.eclipse.org:/home/webtools,,wst/components/assembly/plugins/org.eclipse.wst<br/>
- <br/>
- After updating the map file commit it to the repository.
- </li>
- <li>
- <p>
- Your plugin is now in the repository, included in a feature, and included
- in a map. Now release your plugin.
- </p>
- </li>
- </ol>
- </p>
-
-<br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="cvs_8"><b>How do I jar my plug-in?</b></a>
-<br>
-<br>
- <p xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- First of all, jarring is not an option for every plug-in. If your plugin contains
- multiple jars you can't jar your plug-in.
- </p>
- <p xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- There are a three steps to jarring your plugin:
- <ol>
- <li>
- Update your plug-in's build.properties file to include the source.. and
- output.. keys as well as "." for bin.includes and src.includes as follows:<br/>
- <br/>
- source.. = src/<br/>
- output.. = bin/<br/>
- bin.includes = plugin.xml,\<br/>
- META-INF/,\<br/>
- .,\<br/>
- plugin.properties,\<br/>
- about.html<br/>
- src.includes = exsd/,\<br/>
- .,\<br/>
- build.properties<br/>
- </li>
- <li>
- Update your plug-in's manifest (MANIFEST.MF) by removing the line beginning with "Bundle-ClassPath".
- </li>
- <li>
- Update the feature entry for your plugin to include the unpack=false attribute.<br/>
- <br/>
- <plugin<br/>
- id="org.eclipse.wst.common.uriresolver"<br/>
- download-size="0"<br/>
- install-size="0"<br/>
- version="0.0.0"<br/>
- unpack="false"/>
- </li>
- </ol>
- </p>
-
-<br>
-<br>
-<hr>
-<br>
-</li>
-</ol>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#cccccc">
-<tbody>
-<tr>
-<td width="90%"><b><font size="+1" face="Arial,Helvetica" color="#000000"><a name="Source Code">Source Code</a></font></b></td><td align="right" width="10%"><a href="#toc">top</a></td>
-</tr>
-</tbody>
-</table>
-<ol>
-<li>
-<a name="source_1"><b>What copyrights should we use? </b></a>
-<br>
-<br>
- <p xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">The copyright statement takes one of these two forms, differing only in the year stated on the first line of text.<br/>
- IBM copyrights below are examples only and won't apply to everyone in the community.</p>
- <ul xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <li>If the file's year of invention and last year of modification are the same.<br/>
- Example:<br/>
- /*******************************************************************************<br/>
- * Copyright (c) 2005 IBM Corporation and others.<br/>
- * All rights reserved. This program and the accompanying materials<br/>
- * are made available under the terms of the Eclipse Public License v1.0<br/>
- * which accompanies this distribution, and is available at<br/>
- * http://www.eclipse.org/legal/epl-v10.html<br/>
- *<br/>
- * Contributors:<br/>
- * IBM Corporation - initial API and implementation<br/>
- *******************************************************************************/
- </li>
- <li>If the file's year of invention and last year of modification are
- different...<br/>
- Example:<br/>
- /*******************************************************************************<br/>
- * Copyright (c) 2001,2005 IBM Corporation and others.<br/>
- * All rights reserved. This program and the accompanying materials<br/>
- * are made available under the terms of the Eclipse Public License v1.0<br/>
- * which accompanies this distribution, and is available at<br/>
- * http://www.eclipse.org/legal/epl-v10.html<br/>
- * <br/>
- * Contributors:<br/>
- * IBM Corporation - initial API and implementation<br/>
- *******************************************************************************/
- </li>
- </ul>
-
-<br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="source_2"><b>Is there a tool to update the copyright?</b></a>
-<br>
-<br>
- <B xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">org.eclipse.releng.tools </B>plugin from
- <a xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" href="http://www.eclipse.org/downloads/index.php">Eclipse download site</a>
- allows you to fix copyrights.
- <br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="source_3"><b>What are the package naming conventions?</b></a>
-<br>
-<br>
- See the <a xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" href="../development/guidelines/naming-conventions.html">WTP project naming
- conventions</a>
-
-<br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="source_4"><b>What comment should I use when declaring public provisional API?</b></a>
-<br>
-<br>
- <p xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- The following comment should be placed in each provisional API class description:<br/>
- <br/>
- * <p><br/>
- * <b>Note:</b> This class/interface is part of an interim API that is still under development and expected to<br/>
- * change significantly before reaching stability. It is being made available at this early stage to solicit feedback<br/>
- * from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken<br/>
- * (repeatedly) as the API evolves.<br/>
- * </p>
- </p>
- <p xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- See the WST <a href="http://dev.eclipse.org/viewcvs/index.cgi/wst/components/server/plugins/org.eclipse.wst.server.core/servercore/org/eclipse/wst/server/core/IModule.java?rev=1.12&cvsroot=WebTools_Project&content-type=text/vnd.viewcvs-markup" target="_top">Server core plugin</a> for an example.
- </p>
-
-<br>
-<br>
-<hr>
-<br>
-</li>
-</ol>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#cccccc">
-<tbody>
-<tr>
-<td width="90%"><b><font size="+1" face="Arial,Helvetica" color="#000000"><a name="Website">Website</a></font></b></td><td align="right" width="10%"><a href="#toc">top</a></td>
-</tr>
-</tbody>
-</table>
-<ol>
-<li>
-<a name="website_1"><b>Who maintains the WTP website?</b></a>
-<br>
-<br>
- The WTP website is maintained by the WTP committers.<br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
- <br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
- Problems and requests should be submitted by opening a <a xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Web%20Tools&component=website">bug report</a>.
- <br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="website_2"><b>How do I update the WTP website?</b></a>
-<br>
-<br>
- <p xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- There are two ways:
- <ol>
- <li>
- Extract the whole website (www/webtools), make your changes, and run
- the website build script (build.xml) in the webtools folder. This will
- build the whole site and is useful if you need to make changes in more than
- one module (see below). The downside is the website is big and can take
- a while to extract.
- </li>
- <li>
- The website is broken up into self contained modules such as community, faq, people,
- and plans. Extract the module you want to make changes to (such as www/webtools/plans), make your changes,
- run the build script (build.xml) included in the module, and commit your changes.
- </li>
- </ol>
- </p>
-
-<br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="website_3"><b>What is the CVS info for the webtools website?</b></a>
-<br>
-<br>
- The WTP website is located in the cvs root for the Eclipse website in
- the www/webtools folder.<br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
-<br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
- server : dev.eclipse.org<br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
- path : /cvsroot/org.eclipse
- <br>
-<br>
-<hr>
-<br>
-</li>
-</ol>
-<br>
-<p></p>
-<p>Please see our <a href="http://www.eclipse.org/legal/privacy.html">privacy
- policy</a> and website <a href="http://www.eclipse.org/legal/termsofuse.html">terms
- of use</a>. For problems with the eclipse.org site, please contact the
- <a href="mailto:webmaster@eclipse.org">webmaster</a> or read the
- <a href="../../../webmaster/index.html">webmaster FAQ</a> for answers to common questions!</p>
-</body>
-</html>
diff --git a/faq/CommitterFAQ.xml b/faq/CommitterFAQ.xml
deleted file mode 100644
index 0c38ded..0000000
--- a/faq/CommitterFAQ.xml
+++ /dev/null
@@ -1,341 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<faq xmlns="http://www.eclipse.org/webtools/faq"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://www.eclipse.org/webtools/faq schemas/faq.xsd"
- name="wtp committer faq">
- <category name="General"/>
- <category name="Build/CVS"/>
- <category name="Source Code"/>
- <category name="Website"/>
- <entry id="cvs_1" category="Build/CVS">
- <question>What is the CVS info for the webtools project?</question>
- <answer>
- server : dev.eclipse.org<br/>
- path : /cvsroot/webtools
- </answer>
- </entry>
- <entry id="website_1" category="Website">
- <question>Who maintains the WTP website?</question>
- <answer>
- The WTP website is maintained by the WTP committers.<br/>
- <br/>
- Problems and requests should be submitted by opening a <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Web%20Tools&component=website">bug report</a>.
- </answer>
- </entry>
- <entry id="website_2" category="Website">
- <question>How do I update the WTP website?</question>
- <answer>
- <p>
- There are two ways:
- <ol>
- <li>
- Extract the whole website (www/webtools), make your changes, and run
- the website build script (build.xml) in the webtools folder. This will
- build the whole site and is useful if you need to make changes in more than
- one module (see below). The downside is the website is big and can take
- a while to extract.
- </li>
- <li>
- The website is broken up into self contained modules such as community, faq, people,
- and plans. Extract the module you want to make changes to (such as www/webtools/plans), make your changes,
- run the build script (build.xml) included in the module, and commit your changes.
- </li>
- </ol>
- </p>
- </answer>
- </entry>
- <entry id="website_3" category="Website">
- <question>What is the CVS info for the webtools website?</question>
- <answer>
- The WTP website is located in the cvs root for the Eclipse website in
- the www/webtools folder.<br /><br />
- server : dev.eclipse.org<br/>
- path : /cvsroot/org.eclipse
- </answer>
- </entry>
- <entry id="general_1" category="General">
- <question>Who do we contact in order to get commiter passwords reset?</question>
- <answer>
- You need to contact the Eclipse webmaster at <a href="mailto:webmaster@eclipse.org">webmaster@eclipse.org</a>.
- </answer>
- </entry>
- <entry id="general_2" category="General">
- <question>How do I change my dev.eclipse.org password?</question>
- <answer>
- You can change your password using the committer tools available at <a href="https://dev.eclipse.org/committers/">https://dev.eclipse.org/committers/</a>.
- </answer>
- </entry>
- <entry id="source_1" category="Source Code">
- <question>What copyrights should we use? </question>
- <answer>
- <p>The copyright statement takes one of these two forms, differing only in the year stated on the first line of text.<br/>
- IBM copyrights below are examples only and won't apply to everyone in the community.</p>
- <ul>
- <li>If the file's year of invention and last year of modification are the same.<br/>
- Example:<br/>
- /*******************************************************************************<br/>
- * Copyright (c) 2005 IBM Corporation and others.<br/>
- * All rights reserved. This program and the accompanying materials<br/>
- * are made available under the terms of the Eclipse Public License v1.0<br/>
- * which accompanies this distribution, and is available at<br/>
- * http://www.eclipse.org/legal/epl-v10.html<br/>
- *<br/>
- * Contributors:<br/>
- * IBM Corporation - initial API and implementation<br/>
- *******************************************************************************/
- </li>
- <li>If the file's year of invention and last year of modification are
- different...<br/>
- Example:<br/>
- /*******************************************************************************<br/>
- * Copyright (c) 2001,2005 IBM Corporation and others.<br/>
- * All rights reserved. This program and the accompanying materials<br/>
- * are made available under the terms of the Eclipse Public License v1.0<br/>
- * which accompanies this distribution, and is available at<br/>
- * http://www.eclipse.org/legal/epl-v10.html<br/>
- * <br/>
- * Contributors:<br/>
- * IBM Corporation - initial API and implementation<br/>
- *******************************************************************************/
- </li>
- </ul>
- </answer>
- </entry>
- <entry id="source_2" category="Source Code">
- <question>Is there a tool to update the copyright?</question>
- <answer>
- <B>org.eclipse.releng.tools </B>plugin from
- <a href="http://www.eclipse.org/downloads/index.php">Eclipse download site</a>
- allows you to fix copyrights.
- </answer>
- </entry>
- <entry id="source_3" category="Source Code">
- <question>What are the package naming conventions?</question>
- <answer>
- See the <a href="../development/guidelines/naming-conventions.html">WTP project naming
- conventions</a>
- </answer>
- </entry>
- <entry id="cvs_2" category="Build/CVS">
- <question>How do I add my plugin to the WTP CVS repository?</question>
- <answer>
- <ol>
- <li>On your plugin project select <B>Team->Share Project...</B> context menu.</li>
- <li>Choose existing repository location (or create a new one if you haven't) for
- <B>dev.eclipse.org:/home/webtools</B>
- </li>
- <li>On the next page, if you know exactly where the plugin should be located in the
- repository, then select the "Use specified module name" radio button and
- type in the full path. However, to be safe, it's recommended browsing the repository
- to obtain the correct path, and then adding the module name. Here is an example:<br/>
- <br/>
- Select the "Use an existing module".<br/>
- Browse and then select the folder where you want your new plugin to reside.<br/>
- <br/>
- <img border="0" src="images/shareProject1.gif" width="485" height="602"/><br/>
- <br/>
- Notice that the text field is filled in with the path. Reselect the "Use
- specified module name:" radio button, and append your plugin's name.<br/>
- <br/>
- <img border="0" src="images/shareProject2.gif" width="486" height="602"/>
- </li>
- </ol>
- </answer>
- </entry>
- <entry id="cvs_3" category="Build/CVS">
- <question>Where can I find more information about CVS?</question>
- <answer>
- The <a href="http://dev.eclipse.org/viewcvs/index.cgi/?cvsroot=WebTools_Project">WTP
- CVS respository page</a> contains links to useful CVS documentation including how to
- use Eclipse with CVS.
- </answer>
- </entry>
- <entry id="cvs_4" category="Build/CVS">
- <question>Is there a tool for releasing changes?</question>
- <answer>
- Yes. The releng tool plugin is available from the <a href="http://www.eclipse.org/downloads" target="_top">Eclipse download page</a>. Each version
- of Eclipse contains its own releng tool plugin. Select the version of Eclipse you're
- using. The releng tool plugin is found at the bottom of the page.
- </answer>
- </entry>
- <entry id="cvs_5" category="Build/CVS">
- <question>How do I release my changes?</question>
- <answer>
- <ol>
- <li>
- Commit your changes to the CVS repository. (For information about
- CVS and committing see the FAQ entry <a href="#cvs_3">Where can I find more information about CVS?</a>)
- </li>
- <li>
- Extract the releng project from the CVS repository. This project contains the
- map files.
- </li>
- <li>
- <b>
- *note: It is strongly recommended that you use the releng tool to release
- your changes.
- </b>
- <p>
- You now have to tag your source files and update the corresponding map entries.
- Although you can do this manually it is much easier and less error prone to use
- the releng tool. (See FAQ entry <a href="#cvs_4">Is there a tool for releasing
- changes?</a>)
- </p>
- <ol>
- <li>
- Select the plug-in you want to release, right click on it and select Team->Release as shown below.<br /><br />
- <img src="images/releasemenu.gif"/>
- </li>
- <li>
- Select the releng project as the map project. Click Next.
- </li>
- <li>
- If not already selected, select the plug-ins you want to release. Click Next.
- </li>
- <li>
- The page displays the changes between the last released version of the plug-in
- and what is in HEAD. Review the changes. If everything is correct, click Next.
- </li>
- <li>
- Enter the tag you want to use to release the changes. WTP uses tags of the form
- vYYYYMMDD_HHMM. Click Next.
- </li>
- <li>
- The page displays the changes to the map files. Review the changes. If everything
- is correct, click Next.
- </li>
- <li>
- Enter a comment for the release operation and click Finish.
- </li>
- </ol>
- </li>
- </ol>
- </answer>
- </entry>
- <entry id="cvs_6" category="Build/CVS">
- <question>What do I need to do before releasing changes?</question>
- <answer>
- <p>
- It depends. If you're releasing an isolated fix, you're probably safe to run the
- JUnit tests for the plugin and, if all pass, release your fix. If you're making
- a breaking provisional API change (remember, you cannot make breaking API changes)
- you should announce the change to the WTP dev list advising
- what has changed, why, and how existing consumers of the provisional API can
- adapt their plugins to the change.
- </p>
- <p>
- It is also good practice to use a current WTP development driver when making
- changes so as not to cause a break in your plugin due to changes in other
- plugins.
- </p>
- </answer>
- </entry>
- <entry id="cvs_7" category="Build/CVS">
- <question>How do I add a new plugin to WTP?</question>
- <answer>
- <p>
- <b>Follow this proceduce closely. Mistakes will likely cause a build breakage.</b><br/>
- There are three tasks to add a new plugin to WTP:
- <ol>
- <li>
- Commit your new plug-in to the CVS repository. See <a href="#cvs_2">How do I add my plugin to the WTP CVS repository?</a>
- </li>
- <li>
- <p>
- Add your plugin to the appropriate feature. Features are located under the
- subproject's assembly component. For example, for WST you can find features
- at wst/components/assembly/features.
- </p>
- <p>
- A feature entry will look like the following:<br />
- <br />
- <plugin<br />
-     id="org.eclipse.wst.common.uriresolver"<br />
-     download-size="0"<br />
-     install-size="0"<br />
-     version="0.0.0"/><br />
- </p>
- <p>
- After you've added your plugin to the feature, commit the changes
- and release the feature.
- </p>
- </li>
- <li>
- Add your plugin to the appropriate map file. Map files are located in the
- releng component. A map file entry will look like the following:<br />
- <br/>
- plugin@org.eclipse.wst=v20050718_2336,:pserver:anonymous@dev.eclipse.org:/home/webtools,,wst/components/assembly/plugins/org.eclipse.wst<br />
- <br />
- After updating the map file commit it to the repository.
- </li>
- <li>
- <p>
- Your plugin is now in the repository, included in a feature, and included
- in a map. Now release your plugin.
- </p>
- </li>
- </ol>
- </p>
- </answer>
- </entry>
- <entry id="cvs_8" category="Build/CVS">
- <question>How do I jar my plug-in?</question>
- <answer>
- <p>
- First of all, jarring is not an option for every plug-in. If your plugin contains
- multiple jars you can't jar your plug-in.
- </p>
- <p>
- There are a three steps to jarring your plugin:
- <ol>
- <li>
- Update your plug-in's build.properties file to include the source.. and
- output.. keys as well as "." for bin.includes and src.includes as follows:<br />
- <br />
- source.. = src/<br />
- output.. = bin/<br />
- bin.includes = plugin.xml,\<br />
-                META-INF/,\<br />
-                .,\<br />
-                plugin.properties,\<br />
-                about.html<br />
- src.includes = exsd/,\<br />
-                .,\<br />
-                build.properties<br />
- </li>
- <li>
- Update your plug-in's manifest (MANIFEST.MF) by removing the line beginning with "Bundle-ClassPath".
- </li>
- <li>
- Update the feature entry for your plugin to include the unpack=false attribute.<br />
- <br />
- <plugin<br />
-     id="org.eclipse.wst.common.uriresolver"<br />
-     download-size="0"<br />
-     install-size="0"<br />
-     version="0.0.0"<br />
-     unpack="false"/>
- </li>
- </ol>
- </p>
- </answer>
- </entry>
- <entry id="source_4" category="Source Code">
- <question>What comment should I use when declaring public provisional API?</question>
- <answer>
- <p>
- The following comment should be placed in each provisional API class description:<br />
- <br />
- * <p><br />
- * <b>Note:</b> This class/interface is part of an interim API that is still under development and expected to<br />
- * change significantly before reaching stability. It is being made available at this early stage to solicit feedback<br />
- * from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken<br />
- * (repeatedly) as the API evolves.<br />
- * </p>
- </p>
- <p>
- See the WST <a href="http://dev.eclipse.org/viewcvs/index.cgi/wst/components/server/plugins/org.eclipse.wst.server.core/servercore/org/eclipse/wst/server/core/IModule.java?rev=1.12&cvsroot=WebTools_Project&content-type=text/vnd.viewcvs-markup" target="_top">Server core plugin</a> for an example.
- </p>
- </answer>
- </entry>
-</faq>
diff --git a/faq/build.xml b/faq/build.xml
deleted file mode 100644
index dca243d..0000000
--- a/faq/build.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-<project name="faq" default="main" basedir=".">
-
- <target name="main" depends="validate, faq" description="Builds WTP FAQ."/>
-
- <!-- Builds the WTP FAQ pages -->
- <target name="faq" description="Transforms FAQ XML to HTML">
- <xslt in="main.xml" out="main.html" style="stylesheets/faq.xsl" />
- <xslt in="CommitterFAQ.xml" out="CommitterFAQ.html" style="stylesheets/faq.xsl" />
- </target>
-
- <target name="validate" description="Validate XML files">
- <xmlvalidate failonerror="yes" lenient="true" warn="yes">
- <fileset dir="." includes="*.xml, *.xsl, *.xsd, *.data" excludes="build.xml" />
- <attribute name="http://xml.org/sax/features/namespaces" value="true" />
- <!--
- <attribute name="http://xml.org/sax/features/validation" value="true" />
-
- <attribute name="http://apache.org/xml/features/validation/schema" value="true" />
- <attribute name="http://apache.org/xml/features/validation/schema-full-checking" value="true" />
- -->
- </xmlvalidate>
- </target>
-
-</project>
\ No newline at end of file
diff --git a/faq/images/releasemenu.gif b/faq/images/releasemenu.gif
deleted file mode 100644
index 4bf9372..0000000
--- a/faq/images/releasemenu.gif
+++ /dev/null
Binary files differ
diff --git a/faq/images/shareProject1.gif b/faq/images/shareProject1.gif
deleted file mode 100644
index 88e48f0..0000000
--- a/faq/images/shareProject1.gif
+++ /dev/null
Binary files differ
diff --git a/faq/images/shareProject2.gif b/faq/images/shareProject2.gif
deleted file mode 100644
index d9dd970..0000000
--- a/faq/images/shareProject2.gif
+++ /dev/null
Binary files differ
diff --git a/faq/main.html b/faq/main.html
deleted file mode 100644
index eb3e2e2..0000000
--- a/faq/main.html
+++ /dev/null
@@ -1,580 +0,0 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="../../default_style.css" type="text/css">
-<link rel="stylesheet" href="../../webtools/wtp.css" type="text/css">
-<title>eclipse web tools platform faq</title>
-</head>
-<body>
-<table width="100%" cellspacing="5" cellpadding="2" border="0">
-<tbody>
-<tr>
-<td width="60%" align="left"><font class="indextop">eclipse web tools platform faq</font>
-<br>
-<font class="indexsub">frequently asked questions and answers</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../images/Idea.jpg"></td>
-</tr>
-</tbody>
-</table>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#cccccc">
-<tbody>
-<tr>
-<td width="90%"><b><font size="+1" face="Arial,Helvetica" color="#000000"><a name="">About the FAQ</a></font></b></td><td align="right" width="10%"></td>
-</tr>
-</tbody>
-</table>
-<br>
- Last updated: October 14, 2005<br>
-<br>
-<p>
-<about xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- Many of the FAQ's found on this page have been pulled from the <a href="../community/community.html#help">WTP newsgroup</a>. Thank you to everyone that took
- the time to answer these questions.
- </about>
-</p>
-<p>For problems with this FAQ please open a <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Web%20Tools&component=FAQ">bug report</a>.</p>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#cccccc">
-<tbody>
-<tr>
-<td width="90%"><b><font size="+1" face="Arial,Helvetica" color="#000000"><a name="toc">Table of Contents</a></font></b></td><td align="right" width="10%"></td>
-</tr>
-</tbody>
-</table>
-<ul>
-<li>
-<b>General</b>
-<ol>
-<li>
-<a href="#about_1">How is the Eclipse Web Tools Platform licensed?</a>
-</li>
-<li>
-<a href="#about_2">Who are the contributors to the Eclipse Web Tools Platform Project?</a>
-</li>
-<li>
-<a href="#about_3">What version of Eclipse does WTP work with?</a>
-</li>
-<li>
-<a href="#about_5">Which zip file should I download?</a>
-</li>
-<li>
-<a href="#about_6">How do I install WTP?</a>
-</li>
-<li>
-<a href="#about_7">Are there any WTP tutorials available?</a>
-</li>
-<li>
-<a href="#about_8">What is New and Noteworthy in WTP 0.7?</a>
-</li>
-<li>
-<a href="#about_9">Where can I find a list of known problems for WTP 0.7?</a>
-</li>
-</ol>
-<br>
-</li>
-<li>
-<b>Data Tools</b>
-<ol>
-<li>
-<a href="#data_1">Where can I find the WTP Data Tools?</a>
-</li>
-</ol>
-<br>
-</li>
-<li>
-<b>J2EE</b>
-<ol>
-<li>
-<a href="#j2ee_1">Where can I find the New J2EE Web Module wizard?</a>
-</li>
-<li>
-<a href="#j2ee_2">Does the WTP include a visual JSP editor?</a>
-</li>
-<li>
-<a href="#j2ee_3">How do I install XDoclet in WTP?</a>
-</li>
-</ol>
-<br>
-</li>
-<li>
-<b>Server/Internet</b>
-<ol>
-<li>
-<a href="#server_1">Where are cached files located?</a>
-</li>
-<li>
-<a href="#server_2">How do I debug JSPs with BEA WebLogic Server 8.x?</a>
-</li>
-<li>
-<a href="#server_3">How do I debug JSPs with Apache Tomcat 4.x?</a>
-</li>
-</ol>
-<br>
-</li>
-<li>
-<b>Web</b>
-<ol>
-<li>
-<a href="#web_1">Why does the HTML editor show a validation error if I don't use closing </p> or </br> tags?</a>
-</li>
-<li>
-<a href="#web_2">Does WTP's JavaScript editor report syntax errors?</a>
-</li>
-</ol>
-<br>
-</li>
-<li>
-<b>Web Services</b>
-<ol>
-<li>
-<a href="#ws_1">Can the WSDL validator be extended to validate extension elements, for example partnerLinks and properties from the WS-BPEL specification?</a>
-</li>
-<li>
-<a href="#ws_2">Why does WTP produce errors for multiple import statements for the same namespace in WSDL 1.1?</a>
-</li>
-</ol>
-<br>
-</li>
-<li>
-<b>XML</b>
-<ol>
-<li>
-<a href="#xml_1">How do I use my own filename extensions in the XML editor? It only works correctly if a file ends with .xml.</a>
-</li>
-<li>
-<a href="#xml_2">How do I programmatically add entries to the XML catalog?</a>
-</li>
-<li>
-<a href="#xml_3">Why does the XML catalog preference dialog only show URI Key type entry when no file is selected?</a>
-</li>
-</ol>
-<br>
-</li>
-</ul>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#cccccc">
-<tbody>
-<tr>
-<td width="90%"><b><font size="+1" face="Arial,Helvetica" color="#000000"><a name="General">General</a></font></b></td><td align="right" width="10%"><a href="#toc">top</a></td>
-</tr>
-</tbody>
-</table>
-<ol>
-<li>
-<a name="about_1"><b>How is the Eclipse Web Tools Platform licensed?</b></a>
-<br>
-<br>
- The Eclipse Web Tools Platform consists of software produced by the
- Eclipse Project combined with third party software from other open
- source projects. The software produced by the Eclipse Project is made
- available under the <a xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" href="http://www.eclipse.org/legal/epl-v10.html">Eclipse
- Public License</a>. Third party components are made available under
- their own licenses. The detailed licensing information can be found in
- the <a xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" href="http://www.eclipse.org/legal/epl/notice.html">Eclipse.org
- Software User Agreement</a> (notice.html) file in the root directory of
- the SDK download. Licensing for third party components is described in
- about.html files in the respective subdirectories.
- <br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="about_2"><b>Who are the contributors to the Eclipse Web Tools Platform Project?</b></a>
-<br>
-<br>
- We have a <a xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" href="../people/contributors.html">whole page</a>
- listing the hard working contributors to this project. See the
- <a xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" href="CommitterFAQ.html">Committer FAQ</a> if you are a committer.
- <br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="about_3"><b>What version of Eclipse does WTP work with?</b></a>
-<br>
-<br>
- WTP 0.7 works with Eclipse 3.1.<br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
- WTP 1.0 currently plans to support Eclipse 3.1.x.<br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
- To use WTP with Eclipse 2.1.x see the alphaWorks project <a xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" href="http://www.alphaworks.ibm.com/tech/webtools" target="_top">IBM Web Tools for Eclipse</a>.
- <br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="about_5"><b>Which zip file should I download?</b></a>
-<br>
-<br>
- The WTP SDK (wtp-sdk-*.zip) includes both the <a xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" href="http://eclipse.org/webtools/wst/main.html">Web Standard Tools</a>
- and <a xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" href="http://eclipse.org/webtools/jst/main.html">J2EE Standard Tools</a>,
- including source and both user and programmer documentation. <b xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">If you
- aren't sure which download you need, you should probably get this one.</b>
-<br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
-<br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
- The software development kit (SDK) downloads are for developers
- wishing to build solutions on top of the Web Tools Platform, while the
- non-SDK (e.g.: wtp-0.7.zip) downloads are suitable for everyone else's use. The
- project also provides separate builds of the
- <a xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" href="http://eclipse.org/webtools/wst/main.html">Web Standard Tools</a>
- (wtp-wst-*.zip) by themselves for those uninterested in the tooling for J2EE standards.
- <br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="about_6"><b>How do I install WTP?</b></a>
-<br>
-<br>
- <ul xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <li>
-<a href="http://www.eclipse.org/webtools/development/updatesite/updatesite.html">Automatic installation using the Update Manager in Eclipse 3.1</a>
-</li>
- <br/>
-<br/>
- <li>Manual installation<br/>
- The Web Tools Platform has several required projects that must all be
- installed for proper operation. Each WTP
- <a href="http://download.eclipse.org/webtools/downloads/" target="_top">build</a> is
- built and tested with specific versions of these "prereqs" (the
- <i>Requirements</i> section) and it's
- recommended that only those versions be installed and active when used
- with a particular WTP build. The WTP download page for each build
- details the complete list of requirements and provides links to download the
- supported versions. Downloading and unpacking each should place
- its contents into a folder named <b>eclipse</b>.
- <ol>
- <li>Unpack the Eclipse SDK</li>
- <li>Unzip the Graphical Editor Framework (GEF)</li>
- <li>Unzip the Eclipse Modeling Framework (EMF) / XML Schema Infoset Model (XSD) / Service Data Objects (SDO)</li>
- <li>Unzip the Java EMF Model (JEM) from the Visual Editor Project</li>
- <li>Unzip the Web Tools Platform build into the same location</li>
- </ol>
- WTP should now be installed. Launch Eclipse with the <i>-clean</i>
- option one time to ensure all plugins are detected properly.<br/>
-<br/>
- <i>The identical version of the full
- VE-SDK may be substituted for the listed JEM-SDK version if you wish to
- use the Visual Editor and the Web Tools Platform at the same time.
- </i>
-<br/>
-<br/>
-
- A <a href="http://www.eclipse.org/org/june05release/screencasts/5-webToolsInstallation/webToolsInstallation.html" target="_top">
- screencast</a> that includes setting up Xdoclet and a JBoss 3.x test server is also
- available.
- </li>
- </ul>
-
-<br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="about_7"><b>Are there any WTP tutorials available?</b></a>
-<br>
-<br>
- Yes! See the <a xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" href="../community/community.html#tutorials">WTP community page</a>.
- <br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="about_8"><b>What is New and Noteworthy in WTP 0.7?</b></a>
-<br>
-<br>
- <p xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Refer to the <a href="../development/news/0.7.html">WTP 0.7 - New and Noteworthy</a> document
- for what is new in WTP 0.7.</p>
-
-<br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="about_9"><b>Where can I find a list of known problems for WTP 0.7?</b></a>
-<br>
-<br>
- <p xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Refer to the <a href="../development/news/0.7.html">WTP 0.7 - New and Noteworthy</a> document
- for the list of known problems for WTP 0.7.</p>
-
-<br>
-<br>
-<hr>
-<br>
-</li>
-</ol>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#cccccc">
-<tbody>
-<tr>
-<td width="90%"><b><font size="+1" face="Arial,Helvetica" color="#000000"><a name="Data Tools">Data Tools</a></font></b></td><td align="right" width="10%"><a href="#toc">top</a></td>
-</tr>
-</tbody>
-</table>
-<ol>
-<li>
-<a name="data_1"><b>Where can I find the WTP Data Tools?</b></a>
-<br>
-<br>
- Select Window->Show View->Other...->Data. You can then open the Database Explorer and Data Output views.
- <br>
-<br>
-<hr>
-<br>
-</li>
-</ol>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#cccccc">
-<tbody>
-<tr>
-<td width="90%"><b><font size="+1" face="Arial,Helvetica" color="#000000"><a name="J2EE">J2EE</a></font></b></td><td align="right" width="10%"><a href="#toc">top</a></td>
-</tr>
-</tbody>
-</table>
-<ol>
-<li>
-<a name="j2ee_1"><b>Where can I find the New J2EE Web Module wizard?</b></a>
-<br>
-<br>
- J2EE Web Module has been renamed Dynamic Web Project.
- <br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="j2ee_2"><b>Does the WTP include a visual JSP editor?</b></a>
-<br>
-<br>
- There is no visual JSP editor today, although it's a frequently
- requested enhancement. It's not currently in the plan for the 1.5
- release, but if someone wants to donate code or development time we'd
- certainly be happy to take the contribution.
- <br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="j2ee_3"><b>How do I install XDoclet in WTP?</b></a>
-<br>
-<br>
- To install XDoclet:
- <ol xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <li>Download XDoctlet from <a href="http://sourceforge.net/project/showfiles.php?group_id=31602" target="_top">
- http://sourceforge.net/project/showfiles.php?group_id=31602</a>.
- </li>
- <li>Unzip XDoclet to a directory on your machine such as C:\XDoclet
- </li>
- <li>Specify the directory in which XDoclet is located in Window->Preferences->J2EE Annotations->XDoclet.
- </li>
- </ol>
-
-<br>
-<br>
-<hr>
-<br>
-</li>
-</ol>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#cccccc">
-<tbody>
-<tr>
-<td width="90%"><b><font size="+1" face="Arial,Helvetica" color="#000000"><a name="Server/Internet">Server/Internet</a></font></b></td><td align="right" width="10%"><a href="#toc">top</a></td>
-</tr>
-</tbody>
-</table>
-<ol>
-<li>
-<a name="server_1"><b>Where are cached files located?</b></a>
-<br>
-<br>
- The cached files are located in WORKSPACE_DIR/.metadata/.plugins/org.eclipse.wst.internet.cache.
- The entries are all named with numbers but you can see the mappings in the
- cache.xml file located in the same directory.
- <br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="server_2"><b>How do I debug JSPs with BEA WebLogic Server 8.x?</b></a>
-<br>
-<br>
- BEA WebLogic Server 8.x and earlier do not support JSR-45; WebLogic Server 9.x and later
- do support JSR-45 so you can debug JSP files with them using WTP (note: there are outstanding issues with JSP
- source lookup for the WLS Generic adapter in 0.7 - see
- <a xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=104401" target="_top">bug 104401</a>).
- <br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="server_3"><b>How do I debug JSPs with Apache Tomcat 4.x?</b></a>
-<br>
-<br>
- Apache Tomcat 4.x and earlier do not support JSR-45; Tomcat 5.x and later
- do support JSR-45 so you can debug JSP files with them using WTP.
- <br>
-<br>
-<hr>
-<br>
-</li>
-</ol>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#cccccc">
-<tbody>
-<tr>
-<td width="90%"><b><font size="+1" face="Arial,Helvetica" color="#000000"><a name="Web">Web</a></font></b></td><td align="right" width="10%"><a href="#toc">top</a></td>
-</tr>
-</tbody>
-</table>
-<ol>
-<li>
-<a name="web_1"><b>Why does the HTML editor show a validation error if I don't use closing </p> or </br> tags?</b></a>
-<br>
-<br>
- You're likely editing an XHTML file which requires that the file be well formed XML.
- <br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="web_2"><b>Does WTP's JavaScript editor report syntax errors?</b></a>
-<br>
-<br>
- The JavaScript editor does not report syntax errors and the core teams have
- no plans to add this for JavaScript. However, contributions are always welcome.
- <br>
-<br>
-<hr>
-<br>
-</li>
-</ol>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#cccccc">
-<tbody>
-<tr>
-<td width="90%"><b><font size="+1" face="Arial,Helvetica" color="#000000"><a name="Web Services">Web Services</a></font></b></td><td align="right" width="10%"><a href="#toc">top</a></td>
-</tr>
-</tbody>
-</table>
-<ol>
-<li>
-<a name="ws_1"><b>Can the WSDL validator be extended to validate extension elements, for example partnerLinks and properties from the WS-BPEL specification?</b></a>
-<br>
-<br>
- Yes! The WSDL validator has extension points (which should all be
- considered internal, non-API at this point) which allow you to plug your
- own extension validator for a given namespace into the WSDL validator.<br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
- <br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
- In this case, you can create a validator for the WS-BPEL namespace and
- plug-it into the WSDL validator. Your validator will get called any time
- an element from the WS-BPEL namespace is encountered.<br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
- <br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
- The WSDL <a xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" href="http://dev.eclipse.org/viewcvs/index.cgi/wst/components/wsdl/plugins/org.eclipse.wst.wsdl.validation/src/wsdlvalidate/org/eclipse/wst/wsdl/validation/internal/wsdl11/http/HTTPValidator.java?rev=1.2&cvsroot=WebTools_Project&content-type=text/vnd.viewcvs-markup" target="_top">HTTP validator</a>
- and <a xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" href="http://dev.eclipse.org/viewcvs/index.cgi/wst/components/wsdl/plugins/org.eclipse.wst.wsdl.validation/src/wsdlvalidate/org/eclipse/wst/wsdl/validation/internal/wsdl11/soap/SOAPValidator.java?rev=1.2&cvsroot=WebTools_Project&content-type=text/vnd.viewcvs-markup" target="_top">SOAP validator</a> both use this extension mechanism.
- To contribute your validator to the WSDL validator you need to specify an entry
- in your plugin manifest as follows:<br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
- (I'm assuming http://schemas.xmlsoap.org/ws/2004/03/business-process/ is the BPEL namespace.)<br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
- <br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
- <extension point="org.eclipse.wst.wsdl.validation.wsdl11validator"><br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
- <wsdl11validator<br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
- class="org.example.WSBPELValidator"<br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
- namespace="http://schemas.xmlsoap.org/ws/2004/03/business-process/"<br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
- resourcebundle="wsbpelvalidator"/><br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
- </extension>
- <br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="ws_2"><b>Why does WTP produce errors for multiple import statements for the same namespace in WSDL 1.1?</b></a>
-<br>
-<br>
- The <a xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" href="http://schemas.xmlsoap.org/wsdl/" target="_top">WSDL 1.1 schema</a> restricts
- wsdl:import statements by specifying that they must contain unique
- namespaces. This means one import per namespace per WSDL document.
- <br>
-<br>
-<hr>
-<br>
-</li>
-</ol>
-<table width="100%" cellspacing="0" cellpadding="2" border="0" bgcolor="#cccccc">
-<tbody>
-<tr>
-<td width="90%"><b><font size="+1" face="Arial,Helvetica" color="#000000"><a name="XML">XML</a></font></b></td><td align="right" width="10%"><a href="#toc">top</a></td>
-</tr>
-</tbody>
-</table>
-<ol>
-<li>
-<a name="xml_1"><b>How do I use my own filename extensions in the XML editor? It only works correctly if a file ends with .xml.</b></a>
-<br>
-<br>
- <i xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Note: this also applies to the JSP and HTML editors and others in WTP</i>
-<br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
-<br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
- Earlier versions of Eclipse only allowed users to associated editors
- with custom file names using the <i xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">File Associations</i> preference page.
- Eclipse 3.1 supports a more flexible notion of <i xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Content
- Types</i> that allows more than just editors to treat custom-named files
- as XML, for example. Instead of using the <i xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">File Associations</i> preference page,
- add the filename extension to the new <i xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Content Types</i> preference page.
- Doing so "teaches" Eclipse about that filename extension so that features
- such as Validation and Task Tag detection also support those files correctly.<br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
-<br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
- See the
- <a xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" href="http://download.eclipse.org/eclipse/downloads/drops/R-3.1-200506271435/eclipse-news-part1.html" target="_top">
- Eclipse 3.1 New and Noteworthy</a> section regarding <i xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Editor lookup
- based on content type</i> for more information.
- <br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="xml_2"><b>How do I programmatically add entries to the XML catalog?</b></a>
-<br>
-<br>
- The XML catalog extension point schema contains specific definitions of
- how to use the extension point. You can view the schema <a xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" href="http://dev.eclipse.org/viewcvs/index.cgi/wst/components/xml/plugins/org.eclipse.wst.xml.core/schema/catalogContributions.exsd?rev=1.4&cvsroot=WebTools_Project&content-type=text/vnd.viewcvs-markup" target="_top">here</a>.<br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
- <br xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
- For easier viewing, checkout the org.eclipse.wst.xml.core plugin from the
- repository and view this file with the Eclipse extension schema editor.
- <br>
-<br>
-<hr>
-<br>
-</li>
-<li>
-<a name="xml_3"><b>Why does the XML catalog preference dialog only show URI Key type entry when no file is selected?</b></a>
-<br>
-<br>
- <p xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- As Public ID and System ID are only applicable to DTD entity resolution in
- order to see these options in addition to URI for the Key Type choice you must
- first select a DTD file.
- </p>
- <p xmlns="http://www.eclipse.org/webtools/faq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- When you select an XSD file you will see Namespace Name and Schema Location for
- the Key Type selection.
- </p>
-
-<br>
-<br>
-<hr>
-<br>
-</li>
-</ol>
-<br>
-<p></p>
-<p>Please see our <a href="http://www.eclipse.org/legal/privacy.html">privacy
- policy</a> and website <a href="http://www.eclipse.org/legal/termsofuse.html">terms
- of use</a>. For problems with the eclipse.org site, please contact the
- <a href="mailto:webmaster@eclipse.org">webmaster</a> or read the
- <a href="../../../webmaster/index.html">webmaster FAQ</a> for answers to common questions!</p>
-</body>
-</html>
diff --git a/faq/main.xml b/faq/main.xml
deleted file mode 100644
index 7697d70..0000000
--- a/faq/main.xml
+++ /dev/null
@@ -1,270 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<faq xmlns="http://www.eclipse.org/webtools/faq"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://www.eclipse.org/webtools/faq schemas/faq.xsd"
- name="eclipse web tools platform faq">
- <about>
- Many of the FAQ's found on this page have been pulled from the <a href="../community/community.html#help">WTP newsgroup</a>. Thank you to everyone that took
- the time to answer these questions.
- </about>
- <category name="General" />
- <category name="Data Tools" />
- <category name="J2EE"/>
- <category name="Server/Internet" />
- <category name="Web"/>
- <category name="Web Services"/>
- <category name="XML" />
- <entry category="General" id="about_1">
- <question>How is the Eclipse Web Tools Platform licensed?</question>
- <answer>
- The Eclipse Web Tools Platform consists of software produced by the
- Eclipse Project combined with third party software from other open
- source projects. The software produced by the Eclipse Project is made
- available under the <a href="http://www.eclipse.org/legal/epl-v10.html">Eclipse
- Public License</a>. Third party components are made available under
- their own licenses. The detailed licensing information can be found in
- the <a href="http://www.eclipse.org/legal/epl/notice.html">Eclipse.org
- Software User Agreement</a> (notice.html) file in the root directory of
- the SDK download. Licensing for third party components is described in
- about.html files in the respective subdirectories.
- </answer>
- </entry>
- <entry id="about_2" category="General">
- <question >Who are the contributors to the Eclipse Web Tools Platform Project?</question>
- <answer>
- We have a <a href="../people/contributors.html">whole page</a>
- listing the hard working contributors to this project. See the
- <a href="CommitterFAQ.html">Committer FAQ</a> if you are a committer.
- </answer>
- </entry>
- <entry id="about_3" category="General">
- <question>What version of Eclipse does WTP work with?</question>
- <answer>
- WTP 0.7 works with Eclipse 3.1.<br/>
- WTP 1.0 currently plans to support Eclipse 3.1.x.<br/>
- To use WTP with Eclipse 2.1.x see the alphaWorks project <a href="http://www.alphaworks.ibm.com/tech/webtools" target="_top">IBM Web Tools for Eclipse</a>.
- </answer>
- </entry>
- <entry id="about_5" category="General">
- <question>Which zip file should I download?</question>
- <answer>
- The WTP SDK (wtp-sdk-*.zip) includes both the <a href="http://eclipse.org/webtools/wst/main.html">Web Standard Tools</a>
- and <a href="http://eclipse.org/webtools/jst/main.html">J2EE Standard Tools</a>,
- including source and both user and programmer documentation. <b>If you
- aren't sure which download you need, you should probably get this one.</b><br/><br/>
- The software development kit (SDK) downloads are for developers
- wishing to build solutions on top of the Web Tools Platform, while the
- non-SDK (e.g.: wtp-0.7.zip) downloads are suitable for everyone else's use. The
- project also provides separate builds of the
- <a href="http://eclipse.org/webtools/wst/main.html">Web Standard Tools</a>
- (wtp-wst-*.zip) by themselves for those uninterested in the tooling for J2EE standards.
- </answer>
- </entry>
- <entry id="about_6" category="General">
- <question>How do I install WTP?</question>
- <answer>
- <ul>
- <li><a href="http://www.eclipse.org/webtools/development/updatesite/updatesite.html">Automatic installation using the Update Manager in Eclipse 3.1</a></li>
- <br/><br/>
- <li>Manual installation<br/>
- The Web Tools Platform has several required projects that must all be
- installed for proper operation. Each WTP
- <a href="http://download.eclipse.org/webtools/downloads/" target="_top">build</a> is
- built and tested with specific versions of these "prereqs" (the
- <i>Requirements</i> section) and it's
- recommended that only those versions be installed and active when used
- with a particular WTP build. The WTP download page for each build
- details the complete list of requirements and provides links to download the
- supported versions. Downloading and unpacking each should place
- its contents into a folder named <b>eclipse</b>.
- <ol>
- <li>Unpack the Eclipse SDK</li>
- <li>Unzip the Graphical Editor Framework (GEF)</li>
- <li>Unzip the Eclipse Modeling Framework (EMF) / XML Schema Infoset Model (XSD) / Service Data Objects (SDO)</li>
- <li>Unzip the Java EMF Model (JEM) from the Visual Editor Project</li>
- <li>Unzip the Web Tools Platform build into the same location</li>
- </ol>
- WTP should now be installed. Launch Eclipse with the <i>-clean</i>
- option one time to ensure all plugins are detected properly.<br/><br/>
- <i>The identical version of the full
- VE-SDK may be substituted for the listed JEM-SDK version if you wish to
- use the Visual Editor and the Web Tools Platform at the same time.
- </i><br/><br/>
-
- A <a href="http://www.eclipse.org/org/june05release/screencasts/5-webToolsInstallation/webToolsInstallation.html" target="_top">
- screencast</a> that includes setting up Xdoclet and a JBoss 3.x test server is also
- available.
- </li>
- </ul>
- </answer>
- </entry>
- <entry id="xml_1" category="XML">
- <question>How do I use my own filename extensions in the XML editor? It only works correctly if a file ends with .xml.</question>
- <answer>
- <i>Note: this also applies to the JSP and HTML editors and others in WTP</i><br/><br/>
- Earlier versions of Eclipse only allowed users to associated editors
- with custom file names using the <i>File Associations</i> preference page.
- Eclipse 3.1 supports a more flexible notion of <i>Content
- Types</i> that allows more than just editors to treat custom-named files
- as XML, for example. Instead of using the <i>File Associations</i> preference page,
- add the filename extension to the new <i>Content Types</i> preference page.
- Doing so "teaches" Eclipse about that filename extension so that features
- such as Validation and Task Tag detection also support those files correctly.<br/><br/>
- See the
- <a href="http://download.eclipse.org/eclipse/downloads/drops/R-3.1-200506271435/eclipse-news-part1.html" target="_top">
- Eclipse 3.1 New and Noteworthy</a> section regarding <i>Editor lookup
- based on content type</i> for more information.
- </answer>
- </entry>
- <entry category="Server/Internet" id="server_1">
- <question>Where are cached files located?</question>
- <answer>
- The cached files are located in WORKSPACE_DIR/.metadata/.plugins/org.eclipse.wst.internet.cache.
- The entries are all named with numbers but you can see the mappings in the
- cache.xml file located in the same directory.
- </answer>
- </entry>
- <entry category="Server/Internet" id="server_2">
- <question>How do I debug JSPs with BEA WebLogic Server 8.x?</question>
- <answer>
- BEA WebLogic Server 8.x and earlier do not support JSR-45; WebLogic Server 9.x and later
- do support JSR-45 so you can debug JSP files with them using WTP (note: there are outstanding issues with JSP
- source lookup for the WLS Generic adapter in 0.7 - see
- <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=104401" target="_top">bug 104401</a>).
- </answer>
- </entry>
- <entry category="J2EE" id="j2ee_1">
- <question>Where can I find the New J2EE Web Module wizard?</question>
- <answer>
- J2EE Web Module has been renamed Dynamic Web Project.
- </answer>
- </entry>
- <entry category="Web" id="web_1">
- <question>Why does the HTML editor show a validation error if I don't use closing </p> or </br> tags?</question>
- <answer>
- You're likely editing an XHTML file which requires that the file be well formed XML.
- </answer>
- </entry>
- <entry category="XML" id="xml_2">
- <question>How do I programmatically add entries to the XML catalog?</question>
- <answer>
- The XML catalog extension point schema contains specific definitions of
- how to use the extension point. You can view the schema <a href="http://dev.eclipse.org/viewcvs/index.cgi/wst/components/xml/plugins/org.eclipse.wst.xml.core/schema/catalogContributions.exsd?rev=1.4&cvsroot=WebTools_Project&content-type=text/vnd.viewcvs-markup" target="_top">here</a>.<br/>
- <br/>
- For easier viewing, checkout the org.eclipse.wst.xml.core plugin from the
- repository and view this file with the Eclipse extension schema editor.
- </answer>
- </entry>
- <entry category="J2EE" id="j2ee_2">
- <question>Does the WTP include a visual JSP editor?</question>
- <answer>
- There is no visual JSP editor today, although it's a frequently
- requested enhancement. It's not currently in the plan for the 1.5
- release, but if someone wants to donate code or development time we'd
- certainly be happy to take the contribution.
- </answer>
- </entry>
- <entry category="Web Services" id="ws_1">
- <question>Can the WSDL validator be extended to validate extension elements, for example partnerLinks and properties from the WS-BPEL specification?</question>
- <answer>
- Yes! The WSDL validator has extension points (which should all be
- considered internal, non-API at this point) which allow you to plug your
- own extension validator for a given namespace into the WSDL validator.<br/>
- <br/>
- In this case, you can create a validator for the WS-BPEL namespace and
- plug-it into the WSDL validator. Your validator will get called any time
- an element from the WS-BPEL namespace is encountered.<br/>
- <br/>
- The WSDL <a href="http://dev.eclipse.org/viewcvs/index.cgi/wst/components/wsdl/plugins/org.eclipse.wst.wsdl.validation/src/wsdlvalidate/org/eclipse/wst/wsdl/validation/internal/wsdl11/http/HTTPValidator.java?rev=1.2&cvsroot=WebTools_Project&content-type=text/vnd.viewcvs-markup" target="_top">HTTP validator</a>
- and <a href="http://dev.eclipse.org/viewcvs/index.cgi/wst/components/wsdl/plugins/org.eclipse.wst.wsdl.validation/src/wsdlvalidate/org/eclipse/wst/wsdl/validation/internal/wsdl11/soap/SOAPValidator.java?rev=1.2&cvsroot=WebTools_Project&content-type=text/vnd.viewcvs-markup" target="_top">SOAP validator</a> both use this extension mechanism.
- To contribute your validator to the WSDL validator you need to specify an entry
- in your plugin manifest as follows:<br/>
- (I'm assuming http://schemas.xmlsoap.org/ws/2004/03/business-process/ is the BPEL namespace.)<br/>
- <br/>
- <extension point="org.eclipse.wst.wsdl.validation.wsdl11validator"><br/>
-     <wsdl11validator<br/>
-         class="org.example.WSBPELValidator"<br/>
-         namespace="http://schemas.xmlsoap.org/ws/2004/03/business-process/"<br/>
-         resourcebundle="wsbpelvalidator"/><br/>
- </extension>
- </answer>
- </entry>
- <entry id="data_1" category="Data Tools">
- <question>Where can I find the WTP Data Tools?</question>
- <answer>
- Select Window->Show View->Other...->Data. You can then open the Database Explorer and Data Output views.
- </answer>
- </entry>
- <entry id="ws_2" category="Web Services">
- <question>Why does WTP produce errors for multiple import statements for the same namespace in WSDL 1.1?</question>
- <answer>
- The <a href="http://schemas.xmlsoap.org/wsdl/" target="_top">WSDL 1.1 schema</a> restricts
- wsdl:import statements by specifying that they must contain unique
- namespaces. This means one import per namespace per WSDL document.
- </answer>
- </entry>
- <entry id="server_3" category="Server/Internet">
- <question>How do I debug JSPs with Apache Tomcat 4.x?</question>
- <answer>
- Apache Tomcat 4.x and earlier do not support JSR-45; Tomcat 5.x and later
- do support JSR-45 so you can debug JSP files with them using WTP.
- </answer>
- </entry>
- <entry id="web_2" category="Web">
- <question>Does WTP's JavaScript editor report syntax errors?</question>
- <answer>
- The JavaScript editor does not report syntax errors and the core teams have
- no plans to add this for JavaScript. However, contributions are always welcome.
- </answer>
- </entry>
- <entry id="j2ee_3" category="J2EE">
- <question>How do I install XDoclet in WTP?</question>
- <answer>
- To install XDoclet:
- <ol>
- <li>Download XDoctlet from <a href="http://sourceforge.net/project/showfiles.php?group_id=31602" target="_top">
- http://sourceforge.net/project/showfiles.php?group_id=31602</a>.
- </li>
- <li>Unzip XDoclet to a directory on your machine such as C:\XDoclet
- </li>
- <li>Specify the directory in which XDoclet is located in Window->Preferences->J2EE Annotations->XDoclet.
- </li>
- </ol>
- </answer>
- </entry>
- <entry id="about_7" category="General">
- <question>Are there any WTP tutorials available?</question>
- <answer>
- Yes! See the <a href="../community/community.html#tutorials">WTP community page</a>.
- </answer>
- </entry>
- <entry id="about_8" category="General">
- <question>What is New and Noteworthy in WTP 0.7?</question>
- <answer>
- <p>Refer to the <a href="../development/news/0.7.html">WTP 0.7 - New and Noteworthy</a> document
- for what is new in WTP 0.7.</p>
- </answer>
- </entry>
- <entry id="about_9" category="General">
- <question>Where can I find a list of known problems for WTP 0.7?</question>
- <answer>
- <p>Refer to the <a href="../development/news/0.7.html">WTP 0.7 - New and Noteworthy</a> document
- for the list of known problems for WTP 0.7.</p>
- </answer>
- </entry>
- <entry id="xml_3" category="XML">
- <question>Why does the XML catalog preference dialog only show URI Key type entry when no file is selected?</question>
- <answer>
- <p>
- As Public ID and System ID are only applicable to DTD entity resolution in
- order to see these options in addition to URI for the Key Type choice you must
- first select a DTD file.
- </p>
- <p>
- When you select an XSD file you will see Namespace Name and Schema Location for
- the Key Type selection.
- </p>
- </answer>
- </entry>
-
-</faq>
diff --git a/faq/schemas/faq.xsd b/faq/schemas/faq.xsd
deleted file mode 100644
index 08fdd54..0000000
--- a/faq/schemas/faq.xsd
+++ /dev/null
@@ -1,50 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.eclipse.org/webtools/faq" xmlns:tns="http://www.eclipse.org/webtools/faq">
- <element name="faq" type="tns:faq">
- <key name="entry">
- <selector xpath="tns:entry"/>
- <field xpath="@id"/>
- </key>
- <key name="category">
- <selector xpath="tns:category"/>
- <field xpath="@name"/>
- </key>
- </element>
- <element name="question" type="anyType">
- </element>
-
- <element name="answer" type="anyType">
- </element>
-
- <element name="entry">
- <complexType>
- <sequence>
- <element ref="tns:question"></element>
- <element ref="tns:answer"></element>
- </sequence>
- <attribute name="id" type="string" use="required"></attribute>
- <attribute name="category" type="string" use="optional" default="General"></attribute>
- </complexType>
- </element>
-
- <complexType name="faq">
- <sequence>
- <element ref="tns:about" minOccurs="0" maxOccurs="1"></element>
- <element ref="tns:category" minOccurs="1" maxOccurs="unbounded"></element>
- <element ref="tns:entry" minOccurs="0"
- maxOccurs="unbounded">
- </element>
- </sequence>
- <attribute name="name" type="string" use="required"></attribute>
- </complexType>
-
- <element name="about" type="anyType">
- </element>
-
- <element name="category">
- <complexType>
- <attribute name="name" type="string" use="required"></attribute>
- </complexType>
- </element>
-
-</schema>
\ No newline at end of file
diff --git a/faq/stylesheets/faq.xsl b/faq/stylesheets/faq.xsl
deleted file mode 100644
index a7bae37..0000000
--- a/faq/stylesheets/faq.xsl
+++ /dev/null
@@ -1,147 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
- version="1.0"
- xmlns:xalan="http://xml.apache.org/xslt"
- xmlns:faq="http://www.eclipse.org/webtools/faq"
- xmlns:date="http://exslt.org/dates-and-times"
- exclude-result-prefixes="date faq xalan xsl">
- <xsl:include href="wtp-common.xsl" />
- <xsl:template match="/">
- <xsl:apply-templates mode="faqpage"/>
- </xsl:template>
-
- <xsl:template match="faq:faq" mode="faqpage">
- <xsl:param name="title" select="@name"/>
- <xsl:param name="subtitle" select="'frequently asked questions and answers'"/>
- <xsl:param name="root" select="'../..'"/>
- <xsl:call-template name="page">
- <xsl:with-param name="element" select="."/>
- <xsl:with-param name="title" select="$title"/>
- <xsl:with-param name="subtitle" select="$subtitle"/>
- <xsl:with-param name="root" select="$root"/>
- </xsl:call-template>
- </xsl:template>
-
- <xsl:template name="aboutFAQ">
- <xsl:call-template name="heading">
- <xsl:with-param name="title" select="'About the FAQ'"/>
- <xsl:with-param name="alink" select="''"/>
- </xsl:call-template>
- <br/>
- Last updated: <xsl:value-of select="date:month-name()"/> <xsl:value-of select="date:day-in-month()"/>, <xsl:value-of select="date:year()"/><br/>
- <br/>
- <xsl:if test="/faq:faq/faq:about">
- <p>
- <xsl:apply-templates select="/faq:faq/faq:about" mode="body"/>
- </p>
- </xsl:if>
-
- <p>For problems with this FAQ please open a <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Web%20Tools&component=FAQ">bug report</a>.</p>
- </xsl:template>
-
- <xsl:template name="endpage">
- <xsl:param name="root"/>
- <p></p>
- <p>Please see our <a href="http://www.eclipse.org/legal/privacy.html">privacy
- policy</a> and website <a href="http://www.eclipse.org/legal/termsofuse.html">terms
- of use</a>. For problems with the eclipse.org site, please contact the
- <a href="mailto:webmaster@eclipse.org">webmaster</a> or read the
- <a href="{$root}/../webmaster/index.html">webmaster FAQ</a> for answers to common questions!</p>
- </xsl:template>
-
- <xsl:template name="heading">
- <xsl:param name="alink"/>
- <xsl:param name="title"/>
- <xsl:param name="toplink"/>
- <table bgcolor="#cccccc" border="0" cellpadding="2" cellspacing="0" width="100%">
- <tbody>
- <tr>
- <td width="90%">
- <b>
- <font color="#000000" face="Arial,Helvetica" size="+1">
- <a name="{$alink}"><xsl:value-of select="$title"/></a>
- </font>
- </b>
- </td>
- <td width="10%" align="right">
- <xsl:if test="$toplink != ''">
- <a href="{$toplink}">top</a>
- </xsl:if>
- </td>
- </tr>
- </tbody>
- </table>
- </xsl:template>
-
- <xsl:template match="faq:faq">
- <xsl:param name="root"/>
- <xsl:call-template name="aboutFAQ"/>
- <!-- Create the TOC. -->
- <xsl:call-template name="heading">
- <xsl:with-param name="title" select="'Table of Contents'"/>
- <xsl:with-param name="alink" select="'toc'"/>
- </xsl:call-template>
- <ul>
- <xsl:for-each select="faq:category">
- <li>
- <b><xsl:value-of select="@name"/></b>
- <xsl:variable name="catname" select="@name"/>
- <ol>
- <xsl:for-each select="../faq:entry[@category=$catname]">
- <xsl:sort select="@id" data-type="text" order="ascending"/>
- <li>
- <a href="#{@id}"><xsl:value-of select="faq:question"/></a>
- </li>
- </xsl:for-each>
- </ol>
- <br/>
- </li>
- </xsl:for-each>
- </ul>
-
- <!-- Create the answer sections. -->
- <xsl:for-each select="faq:category">
- <xsl:call-template name="heading">
- <xsl:with-param name="title" select="@name"/>
- <xsl:with-param name="alink" select="@name"/>
- <xsl:with-param name="toplink" select="'#toc'"/>
- </xsl:call-template>
- <xsl:variable name="catname" select="@name"/>
- <ol>
- <xsl:for-each select="../faq:entry[@category=$catname]">
- <xsl:sort select="@id"/>
- <li>
- <a name="{@id}"><b><xsl:value-of select="faq:question"/></b></a><br/><br/>
- <xsl:apply-templates select="faq:answer"/><br/><br/>
- <hr/><br/>
- </li>
- </xsl:for-each>
- </ol>
- </xsl:for-each>
-
- <br/>
- <!--
- <table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody>
- <xsl:apply-templates select="." mode="body"/>
- </tbody>
- </table>
- -->
- <xsl:call-template name="endpage">
- <xsl:with-param name="root" select="$root"/>
- </xsl:call-template>
-
- </xsl:template>
-
- <xsl:template match="faq:answer">
- <xsl:apply-templates select="*|@*|text()" mode="body"/>
- </xsl:template>
-
- <xsl:template match="*|@*|text()" mode="faqpage">
- </xsl:template>
-
- <xsl:template match="*|@*|text()">
- </xsl:template>
-
-
-</xsl:stylesheet>
diff --git a/faq/stylesheets/wtp-common.xsl b/faq/stylesheets/wtp-common.xsl
deleted file mode 100644
index 178f9b3..0000000
--- a/faq/stylesheets/wtp-common.xsl
+++ /dev/null
@@ -1,159 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
-<xsl:template name="infobox">
-<xsl:param name="root"/>
-<xsl:param name="title" />
-<xsl:param name="icon" />
-<xsl:param name="description" />
-<xsl:param name="items" />
-<TABLE cellspacing="0" cellpadding="0" width="275" border="0">
- <TR>
- <TD rowspan="3" height="15" bgcolor="#0080C0" style="padding-top: 5px; padding-bottom: 5px;"><center><SPAN
- style="color: #ffffff; font-weight:bold; font-size: 11px; font-family: Verdana,Arial,Helvetica; padding-left: 5px; padding-right: 5px;"><xsl:value-of select="$title"/></SPAN></center></TD>
- <TD rowspan="1" height="13" width="57%"></TD>
- </TR>
- <TR>
- <TD height="3" bgcolor="#0080C0"><IMG
- src="{$root}/images/c.gif"
- width="1" height="10"/></TD>
- </TR>
-</TABLE>
-<TABLE cellspacing="0" cellpadding="0" width="275" border="0">
- <TR>
- <TD bgcolor="#0080C0"><IMG
- src="{$root}/images/c.gif"
- width="2" height="1"/></TD>
- <TD bgcolor="white"><IMG
- src="{$root}/images/c.gif"
- width="5" height="1"/></TD>
- <TD width="100%">
- <xsl:if test="$icon != ''">
- <img border="0" align="right">
- <xsl:attribute name="src">
- <xsl:value-of select="$icon"/>
- </xsl:attribute>
- </img>
- </xsl:if>
- <xsl:if test="$description">
- <xsl:apply-templates select="$description/*|$description/@*|$description/text()" mode="body"/>
- </xsl:if>
- <TABLE border="0" cellspacing="2">
- <TBODY>
- <!-- xsl:value-of select="$items/*"/-->
- <xsl:for-each select="$items">
-
- <TR>
-
- <!-- TD valign="top">
- <xsl:if test="attribute::icon">
- <img border="0">
- <xsl:attribute name="src">
- <xsl:value-of select="attribute::icon"/>
- </xsl:attribute>
- </img>
- </xsl:if>
- </TD-->
- <TD>
- <xsl:if test="count(child::item) > 0">
-
- <xsl:for-each select="item">
- <xsl:choose>
- <xsl:when test="@link and @title">
- <a>
- <xsl:attribute name="href">
- <xsl:value-of select="attribute::link"/>
- </xsl:attribute>
- <b><xsl:value-of select="attribute::title"/></b>
- </a>
-
- </xsl:when>
- <xsl:otherwise>
- <xsl:if test="@title">
- <b>
- <xsl:value-of select="attribute::title"/>
- </b>
- </xsl:if>
- </xsl:otherwise>
- </xsl:choose>
- <table border="0">
- <tr>
- <xsl:if test="count(child::*) > 0 or child::text()">
- <td valign="top">
- <img src="{$root}/images/Adarrow.gif"/>
- </td>
- <td valign="top">
- <xsl:apply-templates select="*|@*|text()" mode="infobox"/>
- </td>
- </xsl:if>
- </tr>
- </table>
- </xsl:for-each>
- </xsl:if>
- </TD>
- </TR>
-
-
-
- </xsl:for-each>
- </TBODY>
- </TABLE>
-
-</TD>
- <TD bgcolor="white"><IMG
- src="{$root}/images/c.gif"
- width="5" height="1"/></TD>
- <TD bgcolor="#0080C0"><IMG
- src="{$root}/images/c.gif"
- width="2" height="1"/></TD>
- </TR>
- <TR>
- <TD bgcolor="#0080C0" colspan="5"><!--IMG
- src="{$root}/images/c.gif"
- width="1" height="2"/--></TD>
- </TR>
-</TABLE>
-</xsl:template>
-
-<xsl:template name="page">
-<xsl:param name="element"/>
-<xsl:param name="title"/>
-<xsl:param name="subtitle"/>
-<xsl:param name="root"/>
-<html>
- <head>
- <meta content="text/html; charset=iso-8859-1" http-equiv="Content-Type" />
- <link type="text/css" href="{$root}/default_style.css" rel="stylesheet" />
- <link type="text/css" href="{$root}/webtools/wtp.css" rel="stylesheet" />
- <title><xsl:value-of select="$title"/></title>
- </head>
-<body>
-<table border="0" cellpadding="2" cellspacing="5" width="100%">
- <tbody>
- <tr>
- <td align="left" width="60%"><font class="indextop"><xsl:value-of select="$title"/></font><br />
- <font class="indexsub"><xsl:value-of select="$subtitle"/></font></td>
- <td width="40%"> <img src="{$root}/images/Idea.jpg" align="middle" height="86" hspace="50" width="120" /></td>
- </tr>
- </tbody>
- </table>
-<xsl:apply-templates select="$element">
- <xsl:with-param name="root" select="$root"/>
-</xsl:apply-templates>
-</body>
-</html>
-</xsl:template>
-
-
-<xsl:template match="*|@*|text()" mode="infobox">
- <xsl:copy>
- <xsl:apply-templates select="*|@*|text()" mode="infobox"/>
- </xsl:copy>
-</xsl:template>
-
-<xsl:template match="*|@*|text()" mode="body">
- <xsl:copy>
- <xsl:apply-templates select="*|@*|text()" mode="body"/>
- </xsl:copy>
-</xsl:template>
-
-</xsl:stylesheet>
\ No newline at end of file
diff --git a/images/charter.gif b/images/charter.gif
deleted file mode 100644
index 2f56273..0000000
--- a/images/charter.gif
+++ /dev/null
Binary files differ
diff --git a/images/dev.gif b/images/dev.gif
deleted file mode 100644
index 7252b8b..0000000
--- a/images/dev.gif
+++ /dev/null
Binary files differ
diff --git a/images/download.gif b/images/download.gif
deleted file mode 100644
index 69eede7..0000000
--- a/images/download.gif
+++ /dev/null
Binary files differ
diff --git a/images/help.gif b/images/help.gif
deleted file mode 100644
index 4346543..0000000
--- a/images/help.gif
+++ /dev/null
Binary files differ
diff --git a/images/subprojects.gif b/images/subprojects.gif
deleted file mode 100644
index ad04533..0000000
--- a/images/subprojects.gif
+++ /dev/null
Binary files differ
diff --git a/index.html b/index.html
deleted file mode 100644
index a2b9e3f..0000000
--- a/index.html
+++ /dev/null
@@ -1,26 +0,0 @@
-
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Web Tools Platform Project</title>
-<LINK REL="shortcut icon" HREF="http://www.eclipse.org/images/eclipse.ico" TYPE="image/x-icon">
-</head>
-<frameset rows="48,*" frameborder=0 framespacing=0 border="0">
- <frame name="banner" scrolling="no" noresize target="home"
- src="eproject-banner.html" marginwidth="0" marginheight="0" frameborder="NO">
- <frameset cols="126,*" frameborder=0 framespacing=0 border="0">
- <frameset rows="175,*" frameborder=0 framespacing=0 border="0">
- <frame name="nav" scrolling="no" noresize target="main"
- src="nav.html" marginwidth="0" marginheight="0" frameborder="NO">
- <frame name="home_nav" scrolling="no" noresize target="main"
- src="eclipse_nav.html" marginwidth="0" marginheight="0" frameborder="NO">
- </frameset>
- <frame name="main" marginwidth=10 marginheight=10 noresize frameborder="NO" src="main.html">
- </frameset>
- <noframes>
- <body>
- <p>This page uses frames, but your browser doesn't support them.</p>
- </body>
- </noframes> </frameset>
-</html>
\ No newline at end of file
diff --git a/initial-contribution/IBM/Getting Started.html b/initial-contribution/IBM/Getting Started.html
deleted file mode 100644
index 9af067f..0000000
--- a/initial-contribution/IBM/Getting Started.html
+++ /dev/null
@@ -1,107 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
- <meta http-equiv="Content-Type" content="text/html; charset=Cp1252">
- <meta http-equiv="Content-Style-Type" content="text/css">
- <link href="theme/Master.css" rel="stylesheet" type="text/css">
- <title>Getting Started.html</title>
-</head>
-<body>
-<h1>Eclipse Web Tooling Platform Contribution - IBM</h1>
-<p>
-<strong>NOTE:
-This initial contribution has been removed since it is out of date and no longer needed.
-Please obtain WTP builds from the project <a href="http://download.eclipse.org/webtools/downloads/">download</a> page.
-Although the following guide is obsolete, you may still find it of use in evaluating the WTP builds.
-This guide will eventually be superceded by WTP tutorials.
-</strong>
-</p>
-<h2>1.0 Introduction</h2>
-<p>Welcome to IBM's contribution to the Eclipse Web Tooling Platform
-(WTP). The purpose of this document is to guide you through initial
-setup of the code including any prerequisites and a high level tour
-through each of the components which are being contributed for
-evaluation. Before starting, please take note of <a
- href="#TermsAndConditions">Section 5, The Terms and Conditions</a> of
-this contribution.</p>
-<h2>2.0 Getting Started</h2>
-<h3>2.1 Prerequisites</h3>
-<p>Here are the prerequisites you need to download and extract to your
-system:</p>
-<ul>
- <li><a
- href="http://download.eclipse.org/downloads/drops/R-3.0-200406251208/eclipse-SDK-3.0-win32.zip">Eclipse
-Release 3.0 SDK</a> </li>
- <li><a
- href="http://download.eclipse.org/tools/emf/downloads/drops/2.0/R200406280827/emf-sdo-SDK-2.0.0.zip">EMF
-2.0.0 SDK</a> </li>
- <li><a
- href="http://download.eclipse.org/tools/gef/downloads/drops/R-3.0-200406251257/GEF-ALL-3.0.zip">GEF
-3.0.0 SDK</a> </li>
- <li><!-- Arthur Ryman 2004-09-29: Corrected broken link to JEM by copying zip to Web site -->
-<!-- Ernest Mah 2004-09-30: Pointed to fixed link on the VE downloads -->
-<a
- href="http://download.eclipse.org/tools/ve/downloads/wtpdrops/JEM-SDK-I20040728.zip">JEM
-SDK</a>
-
-Jave Edit Model SDK (shared with VE)</li>
- <li><a
- href="http://download.eclipse.org/tools/emf/downloads/drops/2.0/R200406280827/xsd-SDK-2.0.0.zip">XSD
-2.0.0 SDK</a> </li>
- <li>1.4.2 JRE. We've focused most of our testing on Windows using the
- <a href="http://java.sun.com/j2se/1.4.2/download.html">Sun 1.4.2 JRE</a>
- </li>
-</ul>
-<p>Once you've unzipped/installed all of the above, download the ibm.zip
-and extract it. It contains an a copy of this "Getting Started" guide
-and the com.ibm.wtp.sdk zip file. Unzip this SDK into the same location
-as the above SDKs. The zip extracts with 'eclipse' as the root
-directory.</p>
-<h3>2.2 Launching Eclipse</h3>
-<p>Note that if you installing into an existing Eclipse 3.0
-environment, you'll need to launch eclipse with the -clean flag to
-allow the environment to detect the new plugins. Subsequent launching
-of eclipse won't require the -clean flag.</p>
-<pre wrap="">eclipse -clean -vmargs -Xmx256m</pre>
-<p>The VM arguments are required for indexing and java searching.</p>
-<h2>3.0 Explore Various Components</h2>
-<p>If you've made it thus far here's where the real fun begins! Walk
-through the evaluation guides for the components that you're interested
-in. Don't forget to provide feedback to us as described in <a
- href="#Feedback">Section 4.0</a>.</p>
-<ul>
- <li><a href="evalGuides/DataToolsEval.html?p=1">Data Tools</a></li>
- <li><a href="evalGuides/J2EEToolsEval.html?p=1">J2EE Tools</a></li>
- <li><a href="evalGuides/ServerToolsEval.html?p=1">Server Tools</a></li>
- <li><a href="evalGuides/SSEEval.html?p=1">Structured Source Editing</a></li>
- <li><a href="evalGuides/TabbedPropertyEval.html?p=1">Tabbed Property
-View</a></li>
- <li><a href="evalGuides/XMLToolsEval.html?p=1">XML Tools</a></li>
- <li><a href="evalGuides/WebServicesToolsEval.html?p=1">Web Services
-Tools</a></li>
-</ul>
-<h2><a name="Feedback">4.0 Provide Feedback to Us</a></h2>
-<p>We encourage development/design feed back on the <a
- href="https://dev.eclipse.org/mailman/listinfo/wtp-dev">wtp-dev</a>
-mailing list. You can subscribe to the list via <a
- href="https://dev.eclipse.org/mailman/listinfo/wtp-dev">this link</a>.<br>
-<br>
-For usage questions, discussion of bugs, and strange behaviour please
-post to the eclipse.webtools newsgroup. Information on the Web Tools
-Platform newsgroup can be found <a
- href="http://www.eclipse.org/newsgroups/index.html">here</a>.</p>
-<h2><a name="TermsAndConditions">5.0 Terms and Conditions</a></h2>
-<h3>5.1 Licensing</h3>
-<p>IBM's Eclipse WTP SDK Contribution (the Content) is distributed
-under the <a href="http://www.eclipse.org/legal/epl-v10.html">EPL</a>
-and <a href="http://www.eclipse.org/legal/cpl-v10.html">CPL</a>. This
-applies to all files distributed under this contribution. All
-intellectual property remains under the ownership of IBM Corporation. </p>
-<h3>5.1 Disclaimers</h3>
-<p>The Content is provided as is for <b>evaluation purposes only</b>.
-The Content can and will most likely change before appearing in the
-Eclipse CVS repository. The APIs and packages will be reworked once the
-contribution is accepted. The code has not been extensively tested and
-should be considered a snapshot in time of ongoing development.</p>
-</body>
-</html>
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval.html b/initial-contribution/IBM/evalGuides/DataToolsEval.html
deleted file mode 100644
index bb083c4..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval.html
+++ /dev/null
@@ -1,535 +0,0 @@
-<html xmlns:v="urn:schemas-microsoft-com:vml"
-xmlns:o="urn:schemas-microsoft-com:office:office"
-xmlns:w="urn:schemas-microsoft-com:office:word"
-xmlns="http://www.w3.org/TR/REC-html40">
-
-<head>
-<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
-<meta name=ProgId content=Word.Document>
-<meta name=Generator content="Microsoft Word 10">
-<meta name=Originator content="Microsoft Word 10">
-<link rel=File-List href="DataToolsEval_files/filelist.xml">
-<link rel=Edit-Time-Data href="DataToolsEval_files/editdata.mso">
-<!--[if !mso]>
-<style>
-v\:* {behavior:url(#default#VML);}
-o\:* {behavior:url(#default#VML);}
-w\:* {behavior:url(#default#VML);}
-.shape {behavior:url(#default#VML);}
-</style>
-<![endif]-->
-<title>Getting Started.html</title>
-<!--[if gte mso 9]><xml>
- <o:DocumentProperties>
- <o:Author>Der Ping Chou</o:Author>
- <o:LastAuthor>Der Ping Chou</o:LastAuthor>
- <o:Revision>2</o:Revision>
- <o:TotalTime>348</o:TotalTime>
- <o:Created>2004-07-13T00:46:00Z</o:Created>
- <o:LastSaved>2004-07-13T00:46:00Z</o:LastSaved>
- <o:Pages>1</o:Pages>
- <o:Words>634</o:Words>
- <o:Characters>3618</o:Characters>
- <o:Company>IBM</o:Company>
- <o:Lines>30</o:Lines>
- <o:Paragraphs>8</o:Paragraphs>
- <o:CharactersWithSpaces>4244</o:CharactersWithSpaces>
- <o:Version>10.2625</o:Version>
- </o:DocumentProperties>
-</xml><![endif]--><!--[if gte mso 9]><xml>
- <w:WordDocument>
- <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
- </w:WordDocument>
-</xml><![endif]-->
-<link rel=Stylesheet type="text/css" media=all href="../theme/Master.css">
-<style>
-<!--
- /* Style Definitions */
- p.MsoNormal, li.MsoNormal, div.MsoNormal
- {mso-style-parent:"";
- margin:0in;
- margin-bottom:.0001pt;
- mso-pagination:widow-orphan;
- font-size:12.0pt;
- font-family:"Times New Roman";
- mso-fareast-font-family:"Times New Roman";}
-h1
- {mso-margin-top-alt:auto;
- margin-right:0in;
- mso-margin-bottom-alt:auto;
- margin-left:0in;
- mso-pagination:widow-orphan;
- mso-outline-level:1;
- font-size:24.0pt;
- font-family:"Times New Roman";
- font-weight:bold;}
-h2
- {mso-margin-top-alt:auto;
- margin-right:0in;
- mso-margin-bottom-alt:auto;
- margin-left:0in;
- mso-pagination:widow-orphan;
- mso-outline-level:2;
- font-size:18.0pt;
- font-family:"Times New Roman";
- font-weight:bold;}
-h3
- {mso-margin-top-alt:auto;
- margin-right:0in;
- mso-margin-bottom-alt:auto;
- margin-left:0in;
- mso-pagination:widow-orphan;
- mso-outline-level:3;
- font-size:13.5pt;
- font-family:"Times New Roman";
- font-weight:bold;}
-p
- {mso-margin-top-alt:auto;
- margin-right:0in;
- mso-margin-bottom-alt:auto;
- margin-left:0in;
- mso-pagination:widow-orphan;
- font-size:12.0pt;
- font-family:"Times New Roman";
- mso-fareast-font-family:"Times New Roman";}
-@page Section1
- {size:8.5in 11.0in;
- margin:1.0in 1.25in 1.0in 1.25in;
- mso-header-margin:.5in;
- mso-footer-margin:.5in;
- mso-paper-source:0;}
-div.Section1
- {page:Section1;}
- /* List Definitions */
- @list l0
- {mso-list-id:216820099;
- mso-list-template-ids:1277307288;}
-@list l0:level1
- {mso-level-start-at:4;
- mso-level-tab-stop:.5in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-@list l1
- {mso-list-id:347800264;
- mso-list-template-ids:-978969588;}
-@list l1:level1
- {mso-level-start-at:2;
- mso-level-tab-stop:.5in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-@list l2
- {mso-list-id:628972938;
- mso-list-template-ids:-1929337976;}
-@list l3
- {mso-list-id:925764890;
- mso-list-template-ids:-1763424008;}
-@list l3:level1
- {mso-level-start-at:3;
- mso-level-tab-stop:.5in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-@list l4
- {mso-list-id:926772034;
- mso-list-template-ids:35409304;}
-@list l4:level1
- {mso-level-number-format:bullet;
- mso-level-text:\F0B7;
- mso-level-tab-stop:.5in;
- mso-level-number-position:left;
- text-indent:-.25in;
- mso-ansi-font-size:10.0pt;
- font-family:Symbol;}
-@list l4:level2
- {mso-level-tab-stop:1.0in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-@list l4:level3
- {mso-level-tab-stop:1.5in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-@list l4:level4
- {mso-level-tab-stop:2.0in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-@list l4:level5
- {mso-level-tab-stop:2.5in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-@list l4:level6
- {mso-level-tab-stop:3.0in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-@list l4:level7
- {mso-level-tab-stop:3.5in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-@list l4:level8
- {mso-level-tab-stop:4.0in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-@list l4:level9
- {mso-level-tab-stop:4.5in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-@list l5
- {mso-list-id:1310207450;
- mso-list-template-ids:2115414768;}
-@list l5:level1
- {mso-level-start-at:6;
- mso-level-tab-stop:.5in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-@list l6
- {mso-list-id:1334600384;
- mso-list-template-ids:1188730944;}
-@list l6:level1
- {mso-level-tab-stop:.5in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-@list l6:level2
- {mso-level-tab-stop:1.0in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-@list l6:level3
- {mso-level-tab-stop:1.5in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-@list l6:level4
- {mso-level-tab-stop:2.0in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-@list l6:level5
- {mso-level-tab-stop:2.5in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-@list l6:level6
- {mso-level-tab-stop:3.0in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-@list l6:level7
- {mso-level-tab-stop:3.5in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-@list l6:level8
- {mso-level-tab-stop:4.0in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-@list l6:level9
- {mso-level-tab-stop:4.5in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-@list l7
- {mso-list-id:1546019837;
- mso-list-template-ids:1367504666;}
-@list l7:level1
- {mso-level-number-format:bullet;
- mso-level-text:\F0B7;
- mso-level-tab-stop:.5in;
- mso-level-number-position:left;
- text-indent:-.25in;
- mso-ansi-font-size:10.0pt;
- font-family:Symbol;}
-@list l8
- {mso-list-id:2048412170;
- mso-list-template-ids:1579335996;}
-@list l8:level1
- {mso-level-start-at:5;
- mso-level-tab-stop:.5in;
- mso-level-number-position:left;
- text-indent:-.25in;}
-ol
- {margin-bottom:0in;}
-ul
- {margin-bottom:0in;}
--->
-</style>
-<!--[if gte mso 10]>
-<style>
- /* Style Definitions */
- table.MsoNormalTable
- {mso-style-name:"Table Normal";
- mso-tstyle-rowband-size:0;
- mso-tstyle-colband-size:0;
- mso-style-noshow:yes;
- mso-style-parent:"";
- mso-padding-alt:0in 5.4pt 0in 5.4pt;
- mso-para-margin:0in;
- mso-para-margin-bottom:.0001pt;
- mso-pagination:widow-orphan;
- font-size:10.0pt;
- font-family:"Times New Roman";}
-</style>
-<![endif]-->
-<meta http-equiv=Content-Style-Type content="text/css">
-<!--[if gte mso 9]><xml>
- <o:shapedefaults v:ext="edit" spidmax="2050"/>
-</xml><![endif]--><!--[if gte mso 9]><xml>
- <o:shapelayout v:ext="edit">
- <o:idmap v:ext="edit" data="1"/>
- </o:shapelayout></xml><![endif]-->
-</head>
-
-<body lang=EN-US style='tab-interval:.5in'>
-
-<div class=Section1>
-
-<h1>Data Tools Evaluation Guide</h1>
-
-<h2>1.0 Introduction</h2>
-
-<p>The Data Tools contribution offers features to allow you to work with a
-variety of databases.<br>
-<br>
-You can connect to the database, load and view database objects, sample the contents
-of tables, and execute SQL statements and commands.<br>
-<br>
-This information will get you started using these features.</p>
-
-<h2>2.0 Getting Started</h2>
-
-<p>Before using the Data Tools components, you will need to have access to a
-supported database and the information required to connect to it. </p>
-
-<h2>3.0 Quick Tour</h2>
-
-<p>The following sections give step-by-step instructions on how to use the Data
-Tools functions.</p>
-
-<h3>3.1 Opening the Data Views</h3>
-
-<p>The Data Tools provides two views: the Database Explorer view and the DB
-Output view. </p>
-
-<p>The Database Explorer view is where you will create connections, view your
-database objects and launch actions from those objects. The DB Output view is
-where query results and messages are displayed.<br>
-<br>
-To open the Database Explorer view, select Window->Show view->Other->Data->
-Database Explorer.<br>
-To open the DB Output view, select Window->Show view->Other->Data->
-DB Output view.<br>
-Rearrange the views as follows:<br style='mso-special-character:line-break'>
-<![if !supportLineBreakNewLine]><br style='mso-special-character:line-break'>
-<![endif]></p>
-
-<p><!--[if gte vml 1]><v:shapetype id="_x0000_t75" coordsize="21600,21600"
- o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe" filled="f"
- stroked="f">
- <v:stroke joinstyle="miter"/>
- <v:formulas>
- <v:f eqn="if lineDrawn pixelLineWidth 0"/>
- <v:f eqn="sum @0 1 0"/>
- <v:f eqn="sum 0 0 @1"/>
- <v:f eqn="prod @2 1 2"/>
- <v:f eqn="prod @3 21600 pixelWidth"/>
- <v:f eqn="prod @3 21600 pixelHeight"/>
- <v:f eqn="sum @0 0 1"/>
- <v:f eqn="prod @6 1 2"/>
- <v:f eqn="prod @7 21600 pixelWidth"/>
- <v:f eqn="sum @8 21600 0"/>
- <v:f eqn="prod @7 21600 pixelHeight"/>
- <v:f eqn="sum @10 21600 0"/>
- </v:formulas>
- <v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect"/>
- <o:lock v:ext="edit" aspectratio="t"/>
-</v:shapetype><v:shape id="_x0000_i1025" type="#_x0000_t75" style='width:221.25pt;
- height:315pt'>
- <v:imagedata src="DataToolsEval_files/image001.png" o:title=""/>
-</v:shape><![endif]--><![if !vml]><img width=295 height=420
-src="DataToolsEval_files/image002.jpg" v:shapes="_x0000_i1025"><![endif]></p>
-
-<h3>3.2 Connecting to a Database</h3>
-
-<p><span style='color:red'>{Can add Connection screencaps in this section}</span><br>
-You can connect to a variety of database systems using the Connection Wizard.
-Once connected, the database metadata is loaded, allowing you to view the
-schemas, tables, columns and their data types.<br>
-<br>
-For example, if you have DB2 UDB v8.1 installed and the SAMPLE database
-created, you can follow these steps to connect and load its database metadata:</p>
-
-<ol start=1 type=1>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
- mso-list:l6 level1 lfo3;tab-stops:list .5in'>Launch the Connection Wizard<br>
- The Connection Wizard can be launched from the New Connection item in the
- context menu of the Database Explorer (right mouse click on Database
- Explorer View). </li>
-</ol>
-
-<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
-margin-left:.25in'><!--[if gte vml 1]><v:shape id="_x0000_i1026" type="#_x0000_t75"
- style='width:491.25pt;height:136.5pt'>
- <v:imagedata src="DataToolsEval_files/image003.png" o:title=""/>
-</v:shape><![endif]--><![if !vml]><img width=655 height=182
-src="DataToolsEval_files/image004.jpg" v:shapes="_x0000_i1026"><![endif]></p>
-
-<ol start=2 type=1>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
- mso-list:l6 level1 lfo3;tab-stops:list .5in'>Establish a Connection to a
- Database Page<br>
- Ensure the "Choose a database manager and JDBC driver" radio
- button is selected and press Next. </li>
-</ol>
-
-<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
-margin-left:.25in'><!--[if gte vml 1]><v:shape id="_x0000_i1027" type="#_x0000_t75"
- style='width:479.25pt;height:436.5pt'>
- <v:imagedata src="DataToolsEval_files/image005.png" o:title=""/>
-</v:shape><![endif]--><![if !vml]><img width=639 height=582
-src="DataToolsEval_files/image006.jpg" v:shapes="_x0000_i1027"><![endif]></p>
-
-<ol start=3 type=1>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
- mso-list:l6 level1 lfo3;tab-stops:list .5in'>Specify Connection Parameters
- Page<br>
- In the Select a Database Manager tree, expand the DB2 Universal Database
- node and select V8.1. In the Alias field, type "SAMPLE". Press
- the Test Connection button. After a successful connection, press Next.</li>
-</ol>
-
-<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
-margin-left:.25in'><!--[if gte vml 1]><v:shape id="_x0000_i1028" type="#_x0000_t75"
- style='width:479.25pt;height:436.5pt'>
- <v:imagedata src="DataToolsEval_files/image007.png" o:title=""/>
-</v:shape><![endif]--><![if !vml]><img width=639 height=582
-src="DataToolsEval_files/image008.jpg" v:shapes="_x0000_i1028"><![endif]></p>
-
-<ol start=4 type=1>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
- mso-list:l6 level1 lfo3;tab-stops:list .5in'>Limit the Objects Retrieved
- from the Database catalog loading<br>
- On this page you can filter the database objects that are retrieved. To
- add a filter which excludes tables that start with "C", press
- the Add button to the right of the Table and Routine filter grid. In the
- Add Object Filter dialog, select Table for the Target field, select NOT LIKE
- for the Predicate field and type "C%" (without the quotes) in
- the Predicate field, then press OK. Back in the main wizard page, click
- Next.<br>
- Note: If you are connecting to a database with a large number of database
- objects, it is important to filter appropriately to reduce the number of
- tables returned. </li>
-</ol>
-
-<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
-margin-left:.25in'><!--[if gte vml 1]><v:shape id="_x0000_i1029" type="#_x0000_t75"
- style='width:353.25pt;height:135pt'>
- <v:imagedata src="DataToolsEval_files/image009.png" o:title=""/>
-</v:shape><![endif]--><![if !vml]><img width=471 height=180
-src="DataToolsEval_files/image010.jpg" v:shapes="_x0000_i1029"><![endif]></p>
-
-<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
-margin-left:.25in'><!--[if gte vml 1]><v:shape id="_x0000_i1030" type="#_x0000_t75"
- style='width:479.25pt;height:436.5pt'>
- <v:imagedata src="DataToolsEval_files/image011.png" o:title=""/>
-</v:shape><![endif]--><![if !vml]><img width=639 height=582
-src="DataToolsEval_files/image012.jpg" v:shapes="_x0000_i1030"><![endif]></p>
-
-<ol start=5 type=1>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
- mso-list:l6 level1 lfo3;tab-stops:list .5in'>Specify Connection Parameters
- Page <span style='color:red'>{Q: same name as a previous page? or is it
- because I'm on an older driver?}</span> <br>
- Press Next. </li>
-</ol>
-
-<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
-margin-left:.25in'><!--[if gte vml 1]><v:shape id="_x0000_i1031" type="#_x0000_t75"
- style='width:479.25pt;height:436.5pt'>
- <v:imagedata src="DataToolsEval_files/image013.png" o:title=""/>
-</v:shape><![endif]--><![if !vml]><img width=639 height=582
-src="DataToolsEval_files/image014.jpg" v:shapes="_x0000_i1031"><![endif]></p>
-
-<ol start=6 type=1>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
- mso-list:l6 level1 lfo3;tab-stops:list .5in'>Summary Page<br>
- Review your settings and press Finish. The database metadata will load. </li>
-</ol>
-
-<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
-margin-left:.25in'><!--[if gte vml 1]><v:shape id="_x0000_i1032" type="#_x0000_t75"
- style='width:479.25pt;height:436.5pt'>
- <v:imagedata src="DataToolsEval_files/image015.png" o:title=""/>
-</v:shape><![endif]--><![if !vml]><img width=639 height=582
-src="DataToolsEval_files/image016.jpg" v:shapes="_x0000_i1032"><![endif]></p>
-
-<p>In the Database Explorer, you will see a tree structure representing your
-connection and the database objects retrieved. <br>
-<br>
-<!--[if gte vml 1]><v:shape id="_x0000_i1033" type="#_x0000_t75" style='width:483.75pt;
- height:318pt'>
- <v:imagedata src="DataToolsEval_files/image017.png" o:title=""/>
-</v:shape><![endif]--><![if !vml]><img width=645 height=424
-src="DataToolsEval_files/image018.jpg" v:shapes="_x0000_i1033"><![endif]><span
-style='mso-spacerun:yes'> </span></p>
-
-<h3>3.3 Sampling Contents of a Table</h3>
-
-<p>You can sample the contents of a table and see its data appear in the DB
-Output view.</p>
-
-<p>To sample the data from a table, expand the connection, database, schema and
-Tables nodes in the Database Explorer. Using a table's context menu, select
-Sample Contents. This displays the table's data in the Results tab of the DB
-Output view.<br>
-<br>
-<!--[if gte vml 1]><v:shape id="_x0000_i1034" type="#_x0000_t75" style='width:488.25pt;
- height:320.25pt'>
- <v:imagedata src="DataToolsEval_files/image019.png" o:title=""/>
-</v:shape><![endif]--><![if !vml]><img width=651 height=427
-src="DataToolsEval_files/image020.jpg" v:shapes="_x0000_i1034"><![endif]></p>
-
-<p><span style='color:red'><!--[if gte vml 1]><v:shape id="_x0000_i1035"
- type="#_x0000_t75" style='width:489.75pt;height:318pt'>
- <v:imagedata src="DataToolsEval_files/image021.png" o:title=""/>
-</v:shape><![endif]--><![if !vml]><img width=653 height=424
-src="DataToolsEval_files/image022.jpg" v:shapes="_x0000_i1035"><![endif]><span
-style='mso-spacerun:yes'> </span></span></p>
-
-<h3>3.4 Executing SQL Statements and Commands</h3>
-
-<p>The Data Tools offer a way to execute SQL statements and commands through
-its SQL Scrapbook editor. <br>
-<br>
-To invoke the SQL Scrapbook, select Open SQL Scrapbook from the connection node
-context menu in the Database Explorer. The SQL Scrapbook opens in the editor
-area. Type a SQL statement or command then execute it by selecting Execute from
-the SQL menu or by selecting the Execute icon in the toolbar. <br>
-<br>
-<!--[if gte vml 1]><v:shape id="_x0000_i1036" type="#_x0000_t75" style='width:489.75pt;
- height:159.75pt'>
- <v:imagedata src="DataToolsEval_files/image023.png" o:title=""/>
-</v:shape><![endif]--><![if !vml]><img width=653 height=213
-src="DataToolsEval_files/image024.jpg" v:shapes="_x0000_i1036"><![endif]><span
-style='color:red'><br style='mso-special-character:line-break'>
-<![if !supportLineBreakNewLine]><br style='mso-special-character:line-break'>
-<![endif]><o:p></o:p></span></p>
-
-<p><!--[if gte vml 1]><v:shape id="_x0000_i1037" type="#_x0000_t75" style='width:489.75pt;
- height:479.25pt'>
- <v:imagedata src="DataToolsEval_files/image025.png" o:title=""/>
-</v:shape><![endif]--><![if !vml]><img width=653 height=639
-src="DataToolsEval_files/image026.jpg" v:shapes="_x0000_i1037"><![endif]></p>
-
-<h2>4.0 Known Problems</h2>
-
-<ul type=disc>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
- mso-list:l4 level1 lfo11;tab-stops:list .5in'>CLOB and BLOB data types do
- not display well in the DB Output view.</li>
-</ul>
-
-<h2>5.0 Provide Feedback to Us</h2>
-
-<P>We encourage development/design feed back on the <A
- href="https://dev.eclipse.org/mailman/listinfo/wtp-dev">wtp-dev</A> mailing list. You can subscribe to the list via <A
- href="https://dev.eclipse.org/mailman/listinfo/wtp-dev">this link</A>.<BR>
-<BR>
-For usage questions, discussion of bugs, and strange behaviour please post to the eclipse.webtools newsgroup. Information on the Web Tools Platform newsgroup can be found <A
- href="http://www.eclipse.org/newsgroups/index.html">here</A>.</P>
-
-
-</div>
-
-</body>
-
-</html>
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/filelist.html b/initial-contribution/IBM/evalGuides/DataToolsEval_files/filelist.html
deleted file mode 100644
index 7295203..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/filelist.html
+++ /dev/null
@@ -1,31 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xml xmlns:o="urn:schemas-microsoft-com:office:office">
- <o:MainFile HRef="../DataToolsEval.html"/>
- <o:File HRef="image001.png"/>
- <o:File HRef="image002.jpg"/>
- <o:File HRef="image003.png"/>
- <o:File HRef="image004.jpg"/>
- <o:File HRef="image005.png"/>
- <o:File HRef="image006.jpg"/>
- <o:File HRef="image007.png"/>
- <o:File HRef="image008.jpg"/>
- <o:File HRef="image009.png"/>
- <o:File HRef="image010.jpg"/>
- <o:File HRef="image011.png"/>
- <o:File HRef="image012.jpg"/>
- <o:File HRef="image013.png"/>
- <o:File HRef="image014.jpg"/>
- <o:File HRef="image015.png"/>
- <o:File HRef="image016.jpg"/>
- <o:File HRef="image017.png"/>
- <o:File HRef="image018.jpg"/>
- <o:File HRef="image019.png"/>
- <o:File HRef="image020.jpg"/>
- <o:File HRef="image021.png"/>
- <o:File HRef="image022.jpg"/>
- <o:File HRef="image023.png"/>
- <o:File HRef="image024.jpg"/>
- <o:File HRef="image025.png"/>
- <o:File HRef="image026.jpg"/>
- <o:File HRef="filelist.xml"/>
-</xml>
\ No newline at end of file
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/filelist.xml b/initial-contribution/IBM/evalGuides/DataToolsEval_files/filelist.xml
deleted file mode 100644
index 6aeec8c..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/filelist.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-<xml xmlns:o="urn:schemas-microsoft-com:office:office">
- <o:MainFile HRef="../DataToolsEval.html"/>
- <o:File HRef="image001.png"/>
- <o:File HRef="image002.jpg"/>
- <o:File HRef="image003.png"/>
- <o:File HRef="image004.jpg"/>
- <o:File HRef="image005.png"/>
- <o:File HRef="image006.jpg"/>
- <o:File HRef="image007.png"/>
- <o:File HRef="image008.jpg"/>
- <o:File HRef="image009.png"/>
- <o:File HRef="image010.jpg"/>
- <o:File HRef="image011.png"/>
- <o:File HRef="image012.jpg"/>
- <o:File HRef="image013.png"/>
- <o:File HRef="image014.jpg"/>
- <o:File HRef="image015.png"/>
- <o:File HRef="image016.jpg"/>
- <o:File HRef="image017.png"/>
- <o:File HRef="image018.jpg"/>
- <o:File HRef="image019.png"/>
- <o:File HRef="image020.jpg"/>
- <o:File HRef="image021.png"/>
- <o:File HRef="image022.jpg"/>
- <o:File HRef="image023.png"/>
- <o:File HRef="image024.jpg"/>
- <o:File HRef="image025.png"/>
- <o:File HRef="image026.jpg"/>
- <o:File HRef="filelist.xml"/>
-</xml>
\ No newline at end of file
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image001.png b/initial-contribution/IBM/evalGuides/DataToolsEval_files/image001.png
deleted file mode 100644
index d2078f4..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image001.png
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image002.jpg b/initial-contribution/IBM/evalGuides/DataToolsEval_files/image002.jpg
deleted file mode 100644
index dce6f45..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image002.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image003.png b/initial-contribution/IBM/evalGuides/DataToolsEval_files/image003.png
deleted file mode 100644
index 1eaebcf..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image003.png
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image004.jpg b/initial-contribution/IBM/evalGuides/DataToolsEval_files/image004.jpg
deleted file mode 100644
index 99739d6..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image004.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image005.png b/initial-contribution/IBM/evalGuides/DataToolsEval_files/image005.png
deleted file mode 100644
index 1f18208..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image005.png
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image006.jpg b/initial-contribution/IBM/evalGuides/DataToolsEval_files/image006.jpg
deleted file mode 100644
index fb2d90c..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image006.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image007.png b/initial-contribution/IBM/evalGuides/DataToolsEval_files/image007.png
deleted file mode 100644
index 4e50dac..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image007.png
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image008.jpg b/initial-contribution/IBM/evalGuides/DataToolsEval_files/image008.jpg
deleted file mode 100644
index 03490d0..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image008.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image009.png b/initial-contribution/IBM/evalGuides/DataToolsEval_files/image009.png
deleted file mode 100644
index 61d48e2..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image009.png
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image010.jpg b/initial-contribution/IBM/evalGuides/DataToolsEval_files/image010.jpg
deleted file mode 100644
index 2a6ffb1..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image010.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image011.png b/initial-contribution/IBM/evalGuides/DataToolsEval_files/image011.png
deleted file mode 100644
index d7415b6..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image011.png
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image012.jpg b/initial-contribution/IBM/evalGuides/DataToolsEval_files/image012.jpg
deleted file mode 100644
index 23d7d7d..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image012.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image013.png b/initial-contribution/IBM/evalGuides/DataToolsEval_files/image013.png
deleted file mode 100644
index 995e1e4..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image013.png
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image014.jpg b/initial-contribution/IBM/evalGuides/DataToolsEval_files/image014.jpg
deleted file mode 100644
index d6ddae2..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image014.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image015.png b/initial-contribution/IBM/evalGuides/DataToolsEval_files/image015.png
deleted file mode 100644
index 07fe698..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image015.png
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image016.jpg b/initial-contribution/IBM/evalGuides/DataToolsEval_files/image016.jpg
deleted file mode 100644
index f2ef76b..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image016.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image017.png b/initial-contribution/IBM/evalGuides/DataToolsEval_files/image017.png
deleted file mode 100644
index 0a53b9e..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image017.png
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image018.jpg b/initial-contribution/IBM/evalGuides/DataToolsEval_files/image018.jpg
deleted file mode 100644
index 04f84e1..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image018.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image019.png b/initial-contribution/IBM/evalGuides/DataToolsEval_files/image019.png
deleted file mode 100644
index a735692..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image019.png
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image020.jpg b/initial-contribution/IBM/evalGuides/DataToolsEval_files/image020.jpg
deleted file mode 100644
index db9e0ee..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image020.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image021.png b/initial-contribution/IBM/evalGuides/DataToolsEval_files/image021.png
deleted file mode 100644
index 0d65dff..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image021.png
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image022.jpg b/initial-contribution/IBM/evalGuides/DataToolsEval_files/image022.jpg
deleted file mode 100644
index a94938f..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image022.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image023.png b/initial-contribution/IBM/evalGuides/DataToolsEval_files/image023.png
deleted file mode 100644
index 31c37d1..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image023.png
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image024.jpg b/initial-contribution/IBM/evalGuides/DataToolsEval_files/image024.jpg
deleted file mode 100644
index 16bd76c..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image024.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image025.png b/initial-contribution/IBM/evalGuides/DataToolsEval_files/image025.png
deleted file mode 100644
index 5cce5cd..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image025.png
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image026.jpg b/initial-contribution/IBM/evalGuides/DataToolsEval_files/image026.jpg
deleted file mode 100644
index 3a2b61a..0000000
--- a/initial-contribution/IBM/evalGuides/DataToolsEval_files/image026.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/J2EEToolsEval.html b/initial-contribution/IBM/evalGuides/J2EEToolsEval.html
deleted file mode 100644
index 98b25b1..0000000
--- a/initial-contribution/IBM/evalGuides/J2EEToolsEval.html
+++ /dev/null
@@ -1,78 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=Cp1252">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link href="../theme/Master.css" rel="stylesheet" type="text/css">
-<title>Getting Started.html</title>
-</head>
-<body>
-<H1>J2EE Tools Evaluation Guide</H1>
-<H2>1.0 Introduction</H2>
-<P>The J2EE tools contribution offers tools to create, import, export and exploration thru J2EE modules including EAR, Application Client, Connector, EJB and Web projects. <BR>The following document contains information to get you started using the J2EE tools features
-</P>
-<H2>2.0 Getting Started</H2>
-<P>This document can be used as reference for a user with a new workspace or an existing workspace.<H2>3.0 Quick Tour</H2>
-<P>In the following bullet points various simple tasks within the J2EE tools will be explained. The sections themselves are not inter-related and can be run independent of the others.</P>
-<H3>3.1 Project Creation</H3>
-<P>The J2EE tools Project Creation wizards allow developers to create basic J2EE projects including EAR, Application Client, Connector, EJB and Web projects. Each Project Creation wizard can be launched by selecting File->Import->Module type (Note: Module type depends on which type of J2EE project you are going to create. EJB Project is shown below, however, EAR, Application Client, Connector can be found under the J2EE folder, and Web Project be found in the Web folder with in this wizard.)<BR>
-<IMG src="J2EEToolsEval_files/1480_5053.jpg" align="baseline"><BR>Each module has its own wizard; however, for usability reasons they are all very similar. Because of this only the EJB Project Creation will be covered in detail in this document, but the same principles apply for all modules.<BR>Once you have selected EJB Project from the basic Project
-Creation Wizard hitting "Next" will take you to the EJB Project Creation Wizard. This wizard pictured below allows the developer to enter a "Project Name" as well as a variety of other J2EE specific information including possible EAR which will contain the EJB as well as a target server.<BR>
-<IMG src="J2EEToolsEval_files/1480_6255.jpg" align="baseline"><BR>
-The user can now create the project by selecting "Finish".<BR>
-</P>
-<H3>3.2 Import</H3>
-<P><SPAN
- style='font-size: 12.0pt; font-family: "Times New Roman"; mso-fareast-font-family: "Times New Roman"; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA'>J2EE
-Tools provide import of EJB modules in form of .jar files. The import wizard can
-be invoked from two places. The user can access the wizard from File -> Import -> EJB Jar file<BR>
-<IMG src="J2EEToolsEval_files/1480_25186.jpg" align="baseline">
-</SPAN><BR>or right click on the EJB modules group in the Project Explorer and select Import -> EJB JAR File<BR>
-<IMG src="J2EEToolsEval_files/1480_25434.jpg" align="baseline"><BR>
-<SPAN
- style='font-size: 12.0pt; font-family: "Times New Roman"; mso-fareast-font-family: "Times New Roman"; color: black; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA'>The EJB
-Import wizard comes up as shown in the figure below. Select the <B
- style="mso-bidi-font-weight: normal">EJB JAR file</B> by using the <B
- style="mso-bidi-font-weight: normal">Browse</B> button and navigating to the JAR file to be imported.<BR>
-<IMG src="J2EEToolsEval_files/1480_26923.jpg" align="baseline"><BR>
-<BR>
-To complete the import simple press "<B>Finish</B>". Import of other modules like EAR, Application Client, Web and Connector
-projects is also supported and can be done in a similar way, as a wizard is available for each module type
-<BR>
-</SPAN></P>
-<H3>3.3 Export</H3>
-<P><SPAN
- style='font-size: 12.0pt; font-family: "Times New Roman"; mso-fareast-font-family: "Times New Roman"; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA'>J2EE
-Tools provide exporting of EJB modules in form of .jar files. The export wizard can be invoked from two places. First the user can access the wizard from either File -> Export -> EJB Jar file<BR>
-<IMG src="J2EEToolsEval_files/1480_23732.jpg" align="baseline"><BR>
-</SPAN>or right click on the EJB project to be exported under the EJB modules in the Project Explorer and select Export -> EJB JAR file.<BR>
-<IMG src="J2EEToolsEval_files/1480_23804.jpg" align="baseline"><BR>
-<SPAN
- style='font-size: 12.0pt; font-family: "Times New Roman"; mso-fareast-font-family: "Times New Roman"; color: black; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA'>EJB
-Export wizard comes up as shown in the figure below. Select the <B
- style="mso-bidi-font-weight: normal">Destination</B> by using the <B
- style="mso-bidi-font-weight: normal">Browse</B> button. You are also able to change the project which you want to export by selecting on the drop down combo box under the "<B>Project:</B>" heading.</SPAN><BR>
-<IMG src="J2EEToolsEval_files/1480_24007.jpg" align="baseline"><BR>To complete the export simple press finish. <SPAN
- style='font-size: 12.0pt; font-family: "Times New Roman"; mso-fareast-font-family: "Times New Roman"; color: black; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA'>Export
-of other modules like EAR, Application Client, Web and Connector
-projects is also supported and can be done in a similar way</SPAN>, as a wizard is available for each module type.<BR>
-</P>
-<H3>3.4 Project Explorer</H3>
-<P>The Project Explorer is useful J2EE group navigation view. The view can be launched by selecting Windows->Show View->Others->J2EE -> Project Explorer. The Project Explorer has two basic layouts determined by selection of the folder grouping button located at the top of the view <IMG
- src="J2EEToolsEval_files/1480_31986.jpg" align="baseline">. When selected, as seen below, the J2EE projects in your workspace will be group under their appropriate J2EE modules. Simple Java Projects and other non-J2EE projects will be found under the "Other Projects" group.<BR>
-<IMG src="J2EEToolsEval_files/1480_30115.jpg" align="baseline"><BR>If a user would like to see all project ungrouped simply deselecting the <IMG
- src="J2EEToolsEval_files/1480_31986.jpg" align="baseline"> will show a view seen below.<BR>
-<IMG src="J2EEToolsEval_files/1480_32577.jpg" align="baseline"><BR>
-<BR>The Project Explorer also provides a framework of actions which are contributed from the individual objects to perform operations, open editors and do a variety of other work on the projects and their contents as seen by the example implementation below.<BR>
-.<IMG
- src="J2EEToolsEval_files/1480_589.jpg" align="baseline"><BR></P>
-<H2>4.0 Provide Feedback to Us</H2>
-
-<P>We encourage development/design feed back on the <A
- href="https://dev.eclipse.org/mailman/listinfo/wtp-dev">wtp-dev</A> mailing list. You can subscribe to the list via <A
- href="https://dev.eclipse.org/mailman/listinfo/wtp-dev">this link</A>.<BR>
-<BR>
-For usage questions, discussion of bugs, and strange behaviour please post to the eclipse.webtools newsgroup. Information on the Web Tools Platform newsgroup can be found <A
- href="http://www.eclipse.org/newsgroups/index.html">here</A>.</P>
-</P>
-</body>
-</html>
diff --git a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_23732.jpg b/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_23732.jpg
deleted file mode 100644
index 1c5f77a..0000000
--- a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_23732.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_23804.jpg b/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_23804.jpg
deleted file mode 100644
index 34a725d..0000000
--- a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_23804.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_23928.jpg b/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_23928.jpg
deleted file mode 100644
index ec72ecb..0000000
--- a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_23928.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_24007.jpg b/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_24007.jpg
deleted file mode 100644
index de8f217..0000000
--- a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_24007.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_25186.jpg b/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_25186.jpg
deleted file mode 100644
index 718ecd1..0000000
--- a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_25186.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_25434.jpg b/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_25434.jpg
deleted file mode 100644
index fe6143d..0000000
--- a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_25434.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_26923.jpg b/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_26923.jpg
deleted file mode 100644
index da0a706..0000000
--- a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_26923.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_30115.jpg b/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_30115.jpg
deleted file mode 100644
index 7ce2925..0000000
--- a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_30115.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_31986.jpg b/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_31986.jpg
deleted file mode 100644
index 7652809..0000000
--- a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_31986.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_32577.jpg b/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_32577.jpg
deleted file mode 100644
index 7668f04..0000000
--- a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_32577.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_4044.jpg b/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_4044.jpg
deleted file mode 100644
index 1508821..0000000
--- a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_4044.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_5053.jpg b/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_5053.jpg
deleted file mode 100644
index a02e41d..0000000
--- a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_5053.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_589.jpg b/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_589.jpg
deleted file mode 100644
index a942c8e..0000000
--- a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_589.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_6255.jpg b/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_6255.jpg
deleted file mode 100644
index 721e79f..0000000
--- a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/1480_6255.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image001.jpg b/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image001.jpg
deleted file mode 100644
index 5db40f8..0000000
--- a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image001.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image001_.jpg b/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image001_.jpg
deleted file mode 100644
index c5c593c..0000000
--- a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image001_.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image001__.jpg b/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image001__.jpg
deleted file mode 100644
index c5c593c..0000000
--- a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image001__.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image001___.jpg b/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image001___.jpg
deleted file mode 100644
index c5c593c..0000000
--- a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image001___.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image002.jpg b/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image002.jpg
deleted file mode 100644
index c5c593c..0000000
--- a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image002.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image002_.jpg b/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image002_.jpg
deleted file mode 100644
index 12e0156..0000000
--- a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image002_.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image002__.jpg b/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image002__.jpg
deleted file mode 100644
index 12e0156..0000000
--- a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image002__.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image002___.jpg b/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image002___.jpg
deleted file mode 100644
index 12e0156..0000000
--- a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image002___.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image004.jpg b/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image004.jpg
deleted file mode 100644
index bbebe1d..0000000
--- a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/clip_image004.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/hfedit9394.gif b/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/hfedit9394.gif
deleted file mode 100644
index 3a864e1..0000000
--- a/initial-contribution/IBM/evalGuides/J2EEToolsEval_files/hfedit9394.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/SSEEval.html b/initial-contribution/IBM/evalGuides/SSEEval.html
deleted file mode 100644
index bf403a2..0000000
--- a/initial-contribution/IBM/evalGuides/SSEEval.html
+++ /dev/null
@@ -1,1269 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
-<html>
-<head>
-<meta
- http-equiv="Content-Type"
- content="text/html; charset=Cp1252" />
-<meta
- http-equiv="Content-Style-Type"
- content="text/css" />
-<meta
- name="Generator"
- content="WTP HTML Source Page Editor" />
-<link
- href="../theme/Master.css"
- rel="stylesheet"
- type="text/css" />
-<title>Structured Source Editing Evaluation Guide</title>
-</head>
-<body>
-<h1>Structured Source Editing Evaluation Guide</h1>
-<h2>1.0 Introduction</h2>
-<p>Structured Source Editors (SSE) can be used to edit XML, HTML, XHTML,
-CSS, DTD, client-side JavaScript, and JSP 1.1, 1.2, and 2.0 with Java or
-server-side JavaScript. They are intended to provide all of the advanced
-features that Eclipse users appreciate in their editors: content assist,
-customizable highlighting, as-you-type validation, smart editing,
-integration with outline and property views and much much more.</p>
-<p>In addition to the end-user features, the SSE editors are intended to
-be easy for others to re-use as the source page in multipage editors.
-One obvious example is as the source page of a WYSIWYG HTML editor.
-Programmatic interaction with the text model can be accomplished with
-standard Eclipse text document APIs (e.g. replace) or through standard
-DOM APIs. We provide a custom DOM implementation that tolerates
-ill-formed text and that allows for easy integration with other models.</p>
-<p>An additional component provided is the Snippets view. This provides
-a type of "clip book" where plug-in providers and end-users can store
-their favorite bits of code to drag-and-drop into an editor.</p>
-<p>The code in this initial proposed contribution is a snapshot
-"midstream" of our move to Eclipse 3.0. There are many bugs and much
-more to be done integrating with functionality provided in the base
-Eclipse text infrastructure. However, there's plenty to try out already.
-So give it a spin, and let us know what you like and don't like.</p>
-<h2>2.0 Getting Started</h2>
-<p>Nothing special is needed to get started, just start editing an XML,
-HTML, CSS, DTD, JavaScript, or JSP file. Referenced DTDs, Schemas, and
-tag libraries will be loaded and used to provide content assist and fill
-the Properties view. Note that to enjoy the Java editing integration
-while editing JSPs, the JSP file will need to be in a Web project or a
-Java project with the Build Path properly set with a server's library
-jars.</p>
-<h2>3.0 Quick Tour</h2>
-<p>Hopefully all the introductory "standard" editing features would be
-discoverable by anyone familiar with Eclipse's other editors. Therefore,
-we've just listed basic features in the following tables. Later in this
-section we've collected some "new and noteworthy" notes we've written
-while moving to Eclipse 3.0.</p>
-<p>Overview of editing features, compared with Eclipse 3.0's Java
-Editor:<br />
-</p>
-<table
- border="1"
- cellpadding="4"
- cellspacing="0">
- <tbody>
- <tr align="center">
- <th></th>
- <th>Java</th>
- <th>XML</th>
- <th>JSP</th>
- <th>HTML &<br />
- XHTML</th>
- <th>CSS</th>
- <th>DTD</th>
- <th>JavaScript</th>
- </tr>
- <tr>
- <td>Highlighting</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- </tr>
- <tr>
- <td>Content Assist</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">N</td>
- <td align="center">Y</td>
- </tr>
- <tr>
- <td>Parameter/Attribute Hints</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">N</td>
- <td align="center">-</td>
- <td align="center">N</td>
- </tr>
- <tr>
- <td>Formatter</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">N</td>
- <td align="center">N</td>
- </tr>
- <tr>
- <td>Structured Selection</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">N</td>
- </tr>
- <tr>
- <td>Hover Info</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">N</td>
- <td align="center">N</td>
- <td align="center">Y</td>
- </tr>
- <tr>
- <td>Smart Insert</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">N</td>
- <td align="center">N</td>
- <td align="center">N</td>
- </tr>
- <tr>
- <td>Open Selection</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">N</td>
- <td align="center">N</td>
- <td align="center">N</td>
- </tr>
- <tr>
- <td>Find Element</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">N</td>
- <td align="center">N</td>
- <td align="center">N</td>
- </tr>
- <tr>
- <td>Validating as-you-type</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">P?</td>
- <td align="center">N</td>
- <td align="center">N</td>
- </tr>
- <tr>
- <td>Delimiter Matching</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- </tr>
- <tr>
- <td>Refactoring Participation</td>
- <td align="center">Y</td>
- <td align="center">-</td>
- <td align="center">Y</td>
- <td align="center">P?</td>
- <td align="center">-</td>
- <td align="center">-</td>
- <td align="center">N</td>
- </tr>
- <tr>
- <td>Search Participation</td>
- <td align="center">Y</td>
- <td align="center">P?</td>
- <td align="center">Y</td>
- <td align="center">P?</td>
- <td align="center">N</td>
- <td align="center">N</td>
- <td align="center">N</td>
- </tr>
- <tr>
- <td>Quick Fix & Quick Assist</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">N?</td>
- <td align="center">N</td>
- <td align="center">N</td>
- </tr>
- <tr>
- <td>Property Sheet</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">N</td>
- <td align="center">N</td>
- </tr>
- <tr>
- <td>Outline View</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- </tr>
- <tr>
- <td>Quick Outline</td>
- <td align="center">Y</td>
- <td align="center">N</td>
- <td align="center">N</td>
- <td align="center">N</td>
- <td align="center">N</td>
- <td align="center">N</td>
- <td align="center">N</td>
- </tr>
- <tr>
- <td>Text Folding</td>
- <td align="center">Y</td>
- <td align="center">P</td>
- <td align="center">P</td>
- <td align="center">P</td>
- <td align="center">N</td>
- <td align="center">N</td>
- <td align="center">N</td>
- </tr>
- <tr>
- <td>Task Tags</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">N</td>
- </tr>
- </tbody>
-</table>
-<p>Editing features within the mixed content of JSP files:<br />
-</p>
-<table
- border="1"
- cellpadding="4"
- cellspacing="0">
- <tbody>
- <tr align="center">
- <th></th>
- <th>JSP</th>
- <th>Custom Tags</th>
- <th>HTML&XML</th>
- <th>Client-side JavaScript</th>
- <th>CSS</th>
- <th>Server-side Java</th>
- <th>Server-side JavaScript</th>
- <th>JSP Expression Language (EL)</th>
- </tr>
- <tr>
- <td>Highlighting</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">P</td>
- </tr>
- <tr>
- <td>Content Assist</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">P</td>
- </tr>
- <tr>
- <td>Validating as-you-type</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">Y</td>
- <td align="center">N</td>
- <td align="center">N</td>
- <td align="center">Y</td>
- <td align="center">N</td>
- <td align="center">?</td>
- </tr>
- </tbody>
-</table>
-<p></p>
-<h2>Recently added editing functions, views, and JDT integration</h2>
-<table
- border="0"
- cellpadding="10"
- cellspacing="0"
- width="85%">
- <tbody>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>Configurable Go To Next/Previous Annotation</b></td>
- <td
- align="left"
- valign="top"
- width="85%">The source editor's Go To Next / Previous Error tool bar
- buttons have been replaced by configurable Go To Next / Previous
- Annotation drop-down style buttons where you can choose which
- annotations are considered while stepping:
- <p><img src="StructuredSourceEditors/annotation1.bmp.jpg" /></p>
- <p>These actions are also present on the Navigate menu</p>
- </td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>Outline view can <i>not</i> follow caret</b></td>
- <td
- align="left"
- valign="top"
- width="85%">The Outline views now have a toggle option on their
- toolbars to control synchronization with the cursor in the source
- editors:
- <p><img src="StructuredSourceEditors/outlinelink1.bmp.jpg" /></p>
- </td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>Context information for attributes</b></td>
- <td
- align="left"
- valign="top"
- width="85%">A popup with information about attributes for an element is now
- available (invoked via ctrl+shift+space). The attributes which are
- already there show up in <b>bold</b>, and required attributes show
- up with an <b>*</b>:
- <p><img src="StructuredSourceEditors/attrusage1.bmp.jpg" /></p>
- </td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>Background Jobs and Progress View</b></td>
- <td
- align="left"
- valign="top"
- width="85%">For a consistent "look and feel" we are taking advantage
- of the new-to-R3 background "Job" class and Progress View for loading
- content models (instead of having our own thread, and using status
- indicator as we did previously).
- <p><img src="StructuredSourceEditors/ProgressView.gif" /></p>
- </td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>Java HoverInfo</b></td>
- <td
- align="left"
- valign="top"
- width="85%">Information about symbols within Java code sections will
- be shown in its HoverInfo.
- <p><img src="StructuredSourceEditors/jsphoverinfo1.bmp.jpg" /></p>
- </td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>Java code as-you-type validation</b></td>
- <td
- align="left"
- valign="top"
- width="85%">The JSP editor now provides for dynamic syntax checking
- of Java code sections.
- <p><img src="StructuredSourceEditors/jspcodeerror1.bmp.jpg" /></p>
- </td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>Improved debugging support (JSR-045)</b></td>
- <td
- align="left"
- valign="top"
- width="85%">Breakpoints set within the JSP editor can now be
- triggered in JSR-045 compatible servers. Apache Tomcat versions
- 5.0.2, 5.0.12, 5.0.16, and 5.0.25 have been successfully tested.
- Details are discussed <a href="javafamily-relnotes-short.html?p=1">here</a>.
- <p><img src="StructuredSourceEditors/breakpoints1.bmp.jpg" /></p>
- <p>This makes use of the SSE Breakpoint Provider extension API
- allowing for the setting of breakpoints for use in other scenarios
- such as client-side JavaScript and XSL transformation debugging.</p>
- </td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>Conditional breakpoints with JSR-045 debugging</b></td>
- <td
- align="left"
- valign="top"
- width="85%">
- <p>The JSP editor supports setting conditional breakpoints with
- JSR-045 compatible servers. This is done using the vertical ruler's
- context menu.</p>
- <p><img
- src="StructuredSourceEditors/2/editbreakpoints.jpg"
- alt="JSP editor ruler context menu" /></p>
- <p>Note: this requires additional entries to be made on the JSP
- project's classpath. See Eclipse bug <a
- href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=51348#c3">51348</a>
- for details.</p>
- <p><img
- src="StructuredSourceEditors/2/editbreakpoints2.jpg"
- alt="breakpoint properties dialog" /></p>
- </td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>XML Comment and Uncomment</b></td>
- <td
- align="left"
- valign="top"
- width="85%">
- <p>Comment and Uncomment from the Editor pulldown menu can be used to
- comment each line in a block of selected text in the XML Editor. If
- no text is selected, the current line is commented.</p>
- <p><img
- border="0"
- src="StructuredSourceEditors/commentMenu.jpg" /></p>
- <p><img
- border="0"
- src="StructuredSourceEditors/commentEditor.jpg" /></p>
- </td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>XML Add Block Comment and Remove Block Comment</b></td>
- <td
- align="left"
- valign="top"
- width="85%">
- <p>Add Block Comment and Remove Block Comment from the Editor
- pulldown menu can be used to comment all elements in a block of
- selected text in the XML Editor. If no text is selected, the current
- element is commented.</p>
- <p><img
- border="0"
- src="StructuredSourceEditors/addBlockCommentMenu.jpg" /></p>
- <p><img
- border="0"
- src="StructuredSourceEditors/addBlockCommentEditor.jpg" /></p>
- </td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>Quick Fix and Quick Assist</b></td>
- <td
- align="left"
- valign="top"
- width="85%">Quick Fix provides proposals for fixing validation
- errors and warnings. Quick Assist provides proposals for common
- tasks.<br />
- <br />
- Here is a list of Quick Fix proposals currently available. More
- proposals will be added in future milestones.
- <table border="1">
- <tbody>
- <tr>
- <th>Validation Error or Warning</th>
- <th>Quick Fix Proposals</th>
- </tr>
- <tr>
- <td>EmptyTag</td>
- <td>
- <ul>
- <li>remove this tag</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>MissingEndTag</td>
- <td>
- <ul>
- <li>convert to self-ending tag</li>
- <li>insert end tag</li>
- <li>remove this tag</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>AttrsInEndTag</td>
- <td>
- <ul>
- <li>remove all attributes in end tag</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>MissingAttrValue</td>
- <td>
- <ul>
- <li>insert default attribute value from content model</li>
- <li>remove this attribute</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>NoAttrValue</td>
- <td>
- <ul>
- <li>insert default attribute value from content model</li>
- <li>remove this attribute</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>SpacesBeforeTagName</td>
- <td>
- <ul>
- <li>remove spaces before tag name</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>SpacesBeforePI</td>
- <td>
- <ul>
- <li>remove spaces before processing instruction</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>NamespaceInPI</td>
- <td>
- <ul>
- <li>remove namespace in processing instruction</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>UnknownElement</td>
- <td>
- <ul>
- <li>remove this element</li>
- <li>local rename</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>UnknownAttr</td>
- <td>
- <ul>
- <li>remove this attribute</li>
- <li>local rename</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>InvalidAttrValue</td>
- <td>
- <ul>
- <li>replace with default attribute value from content model</li>
- <li>remove this attribute value</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>MissingRequiredAttr</td>
- <td>
- <ul>
- <li>insert required attribute and default value from content
- model</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>AttrValueNotQuoted</td>
- <td>
- <ul>
- <li>quote attribute value</li>
- </ul>
- </td>
- </tr>
- </tbody>
- </table>
- <p><img
- border="0"
- src="StructuredSourceEditors/quickFix.jpg"
- width="563"
- height="331" /></p>
- <p>Local Rename is the only Quick Assist proposal in this milestone.
- More proposals will be added in future milestones.</p>
- </td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>Open on Hyperlink Support</b></td>
- <td
- align="left"
- valign="top"
- width="85%">
- <p>In previous versions, users were able to open on/navigate to the
- source/declaration/referred to file of certain tag attributes by
- using the Open Selection menu item (shortcut key F3 by default). This
- support has been extended so that in addition to selecting the tag
- attribute and pressing F3, users are able to use a combination of
- pressing a modifier key (the Ctrl key by default) and their mouse to
- hover over the tag users want to open selection on. A hyperlink will
- then appear for users to click on to Open Selection.</p>
- <table border="BORDER">
- <tbody>
- <tr>
- <th width="50%">Tag</th>
- <th width="50%">File opened</th>
- </tr>
- <tr>
- <td>any HTML tag that contains a URI attribute (as defined by the
- HTML 4.01 DTD) such as the Anchor tag</td>
- <td>the file located in the URI attribute value</td>
- </tr>
- <tr>
- <td>any JSP tag that contains a URI attribute (as defined by the
- JSP 1.2 Specification) such as the jsp:forward tag</td>
- <td>the file located in the URI attribute value</td>
- </tr>
- <tr>
- <td>jsp:useBean</td>
- <td>the class referenced by the useBean action</td>
- </tr>
- <tr>
- <td>JSP Scriptlets</td>
- <td>selected Java element's declaration</td>
- </tr>
- <tr>
- <td>DOCTYPE Declaration</td>
- <td>the file referenced by the public/system ID</td>
- </tr>
- <tr>
- <td>Schema location attribute</td>
- <td>the file referenced by the schema location attribute</td>
- </tr>
- </tbody>
- </table>
- <p><img
- border="0"
- src="StructuredSourceEditors/1/hyperlink1.jpg" /></p>
- <br />
- <p><img
- border="0"
- src="StructuredSourceEditors/1/hyperlink2.jpg" /></p>
- </td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>Quick Diff Support</b></td>
- <td
- align="left"
- valign="top"
- width="85%">
- <p>The Source editors are now tied into the base Quick Diff support,
- allowing users to see the difference between their current changes in
- the file from either the latest version on CVS or version on disk.</p>
- <p><img
- border="0"
- src="StructuredSourceEditors/1/quickdiff1.jpg" /></p>
- <br />
- <p><img
- border="0"
- src="StructuredSourceEditors/1/quickdiff2.jpg" /></p></td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>Find Occurrences <br />
- (Ctrl+Shift+A)</b></td>
- <td
- align="left"
- valign="top"
- width="85%">
- <p>Source Editors now have the ability to find occurrences of a
- language element in a file.</p>
- <p>A user can now search for an element name, attribute name,
- attribute value, or a Java element (in the JSP Editor). To do so,
- press Ctrl+Shift+A or use the menu "Source > Occurrences in File".
- Results will appear in the Search results view.</p>
- <p align="center"><img
- src="StructuredSourceEditors/1/occurrences_menuaction.jpg" /> <br />
- <b>Find Occurrences Action</b></p>
- <br />
- <p align="center"><img
- src="StructuredSourceEditors/1/occurrences_results.jpg" /> <br />
- <b>Find Occurrences Results</b></p>
- <hr />
- <br />
- <p align="center"><img src="StructuredSourceEditors/1/findAll.jpg" />
- <br />
- <b>XML Example of "Find Occurrences"</b></p>
- </td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="left"
- valign="top"
- width="15%">
- <p align="right"><b>Highlighting of matching delimiters</b></p>
- </td>
- <td
- valign="top"
- width="85%">In addition to the previous support for highlighting
- matching delimiters in server-side Java code snippets and JavaScript
- code, delimiters can now be highlighted in XML, HTML, JSP, DTD, and
- CSS files.
- <p><img
- border="0"
- src="StructuredSourceEditors/1/brackets2.jpg" /></p>
- <br />
- <p><img
- border="0"
- src="StructuredSourceEditors/1/brackets.jpg" /></p>
- </td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>JSP Search Support</b></td>
- <td
- align="left"
- valign="top"
- width="85%">
- <p>JSP files now integrate with the Java Search functionality.</p>
- <p>Users can now search for uses of Types, Methods, Fields, etc. in
- their JSP files via the Java Search Dialog. Search results show up in the
- Search Results view together with Java search results.
- <!-- CURRENTLY BROKEN
- Double clicking on the
- result will open the appropriate file and jump the cursor to the
- first occurrence in the file.
- -->
- </p>
- <p align="center"><img src="StructuredSourceEditors/2/jsp_search.jpg" /><br />
- <b>JSP Search Dialog</b></p>
- <br />
- <p align="center"><img
- src="StructuredSourceEditors/2/jsp_searchresults.jpg" /><br />
- <b>JSP Search Results</b></p>
- </td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>Quick Fix and Quick Assist<br />
- (Ctrl+1)</b></td>
- <td
- align="left"
- valign="top"
- width="85%">
- <p>The JSP Editor now has offers Quick Fix and Quick Assist support.
- </p>
- <p>When the editor cursor is in a JSP Java partition and assistance
- is available, you may press Ctrl+1 to launch Quick Fix and Quick
- Assist.</p>
- <p align="center"><img
- src="StructuredSourceEditors/2/launchQuickAssist.jpg"
- border="1" /> <br />
- <b>Launch Quick Assist</b></p>
- <p><b>Local Rename</b> is one of the Quick Assist proposals which
- lets you rename a Java variable across multiple JSP Java partitions.
- </p>
- <p align="center"><img
- src="StructuredSourceEditors/2/localRename.jpg"
- border="1" /> <br />
- <b>Local Rename</b></p>
- </td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>Task Tags</b></td>
- <td
- align="left"
- valign="top"
- width="85%">
- <p>When a file of a supported content type is built, its comments
- will be searched for Task Tags and corresponding tasks in the Tasks
- view automatically created.</p>
- <img
- border="0"
- src="StructuredSourceEditors/3/tasktags1.jpg" /></td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>Add more to Snippets</b></td>
- <td
- align="left"
- valign="top"
- width="85%">
- <p>The <b>Add to Snippets</b> context menu action previously
- available only in the SSE editors is now available from the Java and
- Default Text Editors</p>
- <img
- border="0"
- src="StructuredSourceEditors/3/javaaddtosnippets1.jpg" /></td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>Source menu on Navigator Views</b></td>
- <td
- align="left"
- valign="top"
- width="85%">
- <p>The <b>Source</b> context menu, which contains <b>Format Document</b>
- and <b>Convert Line Delimiters</b> actions, has been added to the
- Navigator View. The actions can be used on a project, a folder, or a
- document. When the action is used on a project or a folder, the
- action will be applied to all documents and sub-folders in the
- project or folder.</p>
- <p>In this milestone, the Source actions only supports content types
- supported by the Source Editor (including XML, HTML, JSP, and CSS).
- Documents of unsupported content type (for example, bitmaps) will be
- ignored. In the future, other plug-ins may specify formatters for
- other content types via an extension point.</p>
- <p align="center"><img
- src="StructuredSourceEditors/3/sourceMenu.jpg"
- border="0" /> <br />
- <b>Source Menu</b></p>
- <p>The Source action progress dialog is cancellable, in case a large
- folder is selected by accident, or the action is taking too long. The
- progress dialog also shows you any exceptions the Source action
- encountered.</p>
- <p align="center"><img
- src="StructuredSourceEditors/3/formatDocProgressDialog.jpg"
- border="0" /> <br />
- <b>Format Document Progress Dialog</b> <br />
- <font size="-2">Note: The UI for the Format Document Progress Dialog
- will change in a future milestone.</font></p>
- </td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>In-editor preferences</b></td>
- <td
- align="left"
- valign="top"
- width="85%">
- <p>The source editor context menu now contains a menu item to change
- preferences relative to the current editor.</p>
- <img
- border="0"
- src="StructuredSourceEditors/1/editorprefsmenu.gif"
- alt="In editor preferences menu" />
- <p>This allows users to change
- editor preferences easily and immediately without having to navigate
- the entire preferences dialog.</p>
- <img
- border="0"
- src="StructuredSourceEditors/1/editorprefs.gif"
- alt="In editor preferences" /></td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>New Cleanup options</b></td>
- <td
- align="left"
- valign="top"
- width="85%">
- <p>Two new options have been added to Cleanup:</p>
- <ul>
- <li><b>Compress empty element tags</b> - compresses empty element
- tags into the form <tag /></li>
- <li><b>Insert required attributes</b> - inserts missing required
- attributes according to the content model</li>
- </ul>
- <img
- border="0"
- src="StructuredSourceEditors/1/cleanupDialog.gif" /></td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>New QuickAssist proposals</b></td>
- <td
- align="left"
- valign="top"
- width="85%">
- <p>New useful QuickAssist proposals have been added:</p>
- <ul>
- <li><b>Surround with new element</b> - surrounds the element at the
- cursor with a new element. You will enter the linked edit mode after
- the new element is inserted. You can rename the default start tag
- name and end tag name at the same time. While in the linked edit
- mode, Content Assist is available for selecting the element name.</li>
- <li><b>Insert required attributes</b> - inserts missing required
- attributes according to the content model for the element at the
- cursor</li>
- </ul>
- <img
- border="0"
- src="StructuredSourceEditors/1/newQuickAssistProposals.gif"
- alt="New QuickAssist Proposals" /></td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>New QuickFix proposals</b></td>
- <td
- align="left"
- valign="top"
- width="85%">
- <p>More smarter QuickFix proposals for common validation errors. For
- example, when a missing end tag is detected, the following QuickFix
- proposals are available:</p>
- <ul>
- <li><b>Change to empty-element tag</b> - changes this tag into the
- form <tag /></li>
- <li><b>Remove this tag</b> - removes this problem tag</li>
- <li><b>Insert end tag before first child element</b> - closes this
- tag before the first child element</li>
- <li><b>Insert end tag at end of element</b> - closes this tag at the
- end of this element</li>
- </ul>
- <img
- border="0"
- src="StructuredSourceEditors/1/newQuickFixProposals.gif"
- alt="New QuickFix Proposals" /></td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>Expand Selection To</b></td>
- <td
- align="left"
- valign="top"
- width="85%">
- <p>The Expand Selection To actions can be used to select elements in
- the document easily:</p>
- <ul>
- <li><b>Enclosing Element</b> - selects the element at the cursor</li>
- <li><b>Next Element</b> - expands the selection to the next element</li>
- <li><b>Previous Element</b> - expands the selection to the previous
- element</li>
- <li><b>Restore Last Selection</b> - undoes last selection expansion</li>
- </ul>
- <img
- border="0"
- src="StructuredSourceEditors/1/expandSelectionToMenu.gif"
- alt="Expand Selection To Menu" /></td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>Rename Refactoring</b></td>
- <td
- align="left"
- valign="top"
- width="85%">
- <p>JSP files now participate in the refactoring of Java elements.
- Renaming a Type, Method, or Package will update the references within
- JSP files (jsp:useBean tags, import statements, scriptlets, etc.) as
- well. The necessary changes for JSP files will be computed
- automatically</p>
- <p><img
- border="0"
- src="StructuredSourceEditors/2/rename1.gif"
- alt="Java editor Refactor menu" /></p>
- <p><img
- border="0"
- src="StructuredSourceEditors/2/rename2.gif"
- alt="Refactor results dialog" /></p>
- <p>This can be also invoked directly from the JSP source editor. For
- example, with a class in a <b>jsp:useBean</b> tag selected, choosing
- Refactor...Rename from the context menu will launch the familiar Java
- Refactoring dialog.</p>
- <p><img
- border="0"
- src="StructuredSourceEditors/2/rename3.gif"
- alt="Refactor menu in JSP source editor" /></p>
- </td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>Move Refactoring</b></td>
- <td
- align="left"
- valign="top"
- width="85%">
- <p>JSP files also participate in the moving of Java source files.
- After dragging a class <b>MyDate</b> from "one.two.three" into the
- package "one.two.three.four", when dropped, the user will be prompted
- to update the affected JSP files.</p>
- <img
- border="0"
- src="StructuredSourceEditors/2/rename4.gif"
- alt="dialog presented when moving Java sources" />
- <p>This type of refactoring can also be invoked via the editor
- context menu if a Java element is selected.</p>
- </td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>Automatic Snippets management by content-type</b></td>
- <td
- align="left"
- valign="top"
- width="85%">
- <p>The Customizer's Show/Hide functionality from earlier releases has
- been augmented with more fine-grained controls for visibility.</p>
- <p><img
- border="0"
- src="StructuredSourceEditors/3/customizer1.gif"
- alt="customizer dialog" /></p>
- <p>Users may now select which content-types a drawer applies to. When
- editing files those content-types, that drawer will be shown. Drawers
- configured for per-content-type management but not enabled for that
- content type will be hidden.</p>
- <p><img
- border="0"
- src="StructuredSourceEditors/3/customizer2.gif"
- alt="content type dialog" /></p>
- </td>
- </tr>
- <tr>
- <td colspan="2">
- <hr />
- </td>
- </tr>
- <tr>
- <td
- align="right"
- valign="top"
- width="15%"><b>Configurable Hover Help</b></td>
- <td
- align="left"
- valign="top"
- width="85%">
- <p>Users can configure the type of hover help displayed, and the
- keystrokes used to display hover help in Source Editors.</p>
- <p><img
- border="0"
- src="StructuredSourceEditors/hoverspref.jpg"
- alt="hover help preferences" /></p>
- </td>
- </tr>
- </tbody>
-</table>
-<h2>4.0 Provide Feedback to Us</h2>
-<p>We encourage development/design feed back on the <a
- href="https://dev.eclipse.org/mailman/listinfo/wtp-dev">wtp-dev</a> mailing list. You can subscribe to the list via <a
- href="https://dev.eclipse.org/mailman/listinfo/wtp-dev">this link</a>.<br>
-</br>
-<br> For usage questions, discussion of bugs, and strange behaviour
-please post to the eclipse.webtools newsgroup. Information on the Web
-Tools Platform newsgroup can be found </br>
-<a href="http://www.eclipse.org/newsgroups/index.html">here</a>.</p>
-
-<p></p><hr width="80%"/>
-<p align="center"><font size="-2"><font color="#808080">Return to the <b>Eclipse Web Tooling Platform Contribution - IBM</b> <a
- href="../Getting Started.html?p=1">Getting Started Guide</a></font></font></p>
-</body>
-</html>
diff --git a/initial-contribution/IBM/evalGuides/ServerToolsEval.html b/initial-contribution/IBM/evalGuides/ServerToolsEval.html
deleted file mode 100644
index cf77c49..0000000
--- a/initial-contribution/IBM/evalGuides/ServerToolsEval.html
+++ /dev/null
@@ -1,225 +0,0 @@
-<html>
-
-<head>
- <meta http-equiv="Content-Type" content="text/html; charset=Cp1252">
- <meta http-equiv="Content-Style-Type" content="text/css">
- <link href="../theme/Master.css" rel="stylesheet" type="text/css">
- <title>Server Tools Evaluation Guide</title>
-</head>
-
-<body>
-<H1>Server Tools Evaluation Guide</H1>
-
-<H2>1.0 Introduction</H2>
-<p>The Server Tools component provides a comprehensive framework for supporting servers within Eclipse,
-as well as a number of supporting tools. The initial contribution contains support for several versions
-of Apache Tomcat, an internal Web browser for viewing Web pages inside the IDE, and a TCP/IP monitor
-for observing data flow between a client and a server.</p>
-
-<p>The Server Tools contribution consists of four separate components:</p>
-
-<ul>
-<li>Web Browser - Support for an internal (hosted within the IDE) Web browser and launching external browsers.</li>
-<li>TCP/IP Monitor - A TCP/IP "tunnel" that sits between a client and server and allows you to monitor
- the traffic between them. The TCP/IP Monitor is also the basis for the WS-I SOAP monitor.</li>
-<li>Server Tools framework - A generic framework for adding server support to Eclipse. Provides a set of common actions
- and wizards, and a Servers view and preferences to manage servers. It provides a number of extension points that
- allow developers to extend the servers that are supported, and API to allow other plugins to access server
- information and control servers.</li>
-<li>Apache Tomcat server support - Support for running and debugging on Tomcat v3.2, v4.0, v4.1, and v5.0.</li>
-</ul>
-
-<p>
-This guide will step you through each one of these components and point out many of the useful features along the way.
-There are two scenarios - the first scenario will highlight the TCP/IP Monitor and the Web Browser support, and the
-second scenario will involve debugging a JSP file on Tomcat v5.0.
-</p>
-
-
-<H2>2.0 Getting Started</H2>
-
-<p>There is no setup required to run the first scenario. To run the second scenario,
-you will need to install two things before you begin:</p>
-
-<ul>
-<li>To run a Web project on Apache Tomcat, you'll need to download and unzip a copy of the Tomcat server.
- You can download Tomcat from <a href="http://jakarta.apache.org">http://jakarta.apache.org</a>.
- Click on Downloads > Binaries on the left hand side and download any version of Tomcat v3.2.x, v4.0.x,
- v4.1.x, or v5.0.x. For JSP debugging support, choose Tomcat v5.0.x.</li>
-
-<li>To run JavaServer Pages on Tomcat, you will need a full JDK (not just a JRE). If you do not already use a
- JDK to run Eclipse, you will need to download and install one separately.</li>
-
-</ul>
-
-<H2>3.0 Quick Tour</H2>
-
-<H3>3.1 Scenario 1 - TCP/IP Monitor and Web Browser</H3>
-
-<p>In this scenario, we'll take a look at the TCP/IP Monitor and Web Browser
-support, and then use the monitor to inspect traffic between the Web browser
-and an external Web site.
-</p>
-
-<ol>
-<li>Go to Window > Preferences and then select Web Browser.</li>
-
-<li>This page displays the Web browsers that have been found on
- your machine, and allows you to add and remove them from the list.
- The checked Web browser is the one that will be used by the tools.
- On most operating systems "Internal Web browser" will be checked
- by default.</li>
-
- <p><img src="ServerToolsEval_files/browserPrefs.gif" width="635" height="539"/></p>
-
-<li>Using this page, you can edit the settings for each browser (see below), add new
- browsers, or do a search through a particular directory.</li>
-
- <p><img src="ServerToolsEval_files/editBrowser.gif" width="432" height="176"/></p>
-
-<li>Select the TCP/IP Monitor preferences on the left.</li>
-
-<li>Click Add to add a new monitor. Type "www.eclipse.org" in the Host name: field and click OK.</li>
-
- <p><img src="ServerToolsEval_files/monitorPrefs.gif" width="635" height="539"/></p>
-
-<li>Click Start and then OK to exit the preferences dialog.</li>
-
-<li>Switch to the Server perspective. Note the Servers view (a server has been installed here to show
- the menu actions) that shows the status of all installed servers and allows you to start, stop, and
- publish to any server.</li>
-
- <p><img src="ServerToolsEval_files/serversView.gif" width="875" height="657"/></p>
-
-<li>Click on the "world" icon (<img src="ServerToolsEval_files/internal_browser.gif" width="16" height="16"/>)
- on the toolbar. This will open your preferred Web browser. If the Internal Web Browser was checked in
- the preferences, it will open. Take this opportunity to get familiar with the internal browser.</li>
-
-<li>Type in "http://localhost/" in the location field and hit Enter.</li>
-
-<li>The TCP/IP monitor view should appear below, and fill up with the traffic between your
- Web browser and Eclipse.org. When you select each request in the tree at the top left,
- information about the request/response is shown, the bottom left of the view will display
- the HTTP request that was made to www.eclipse.org, and the bottom right will show each
- response.</li>
-
- <p><img src="ServerToolsEval_files/monitorBrowser.gif" width="875" height="657"/></p>
-
-<li>Select /images/EclipseBannerPic.jpg from the tree. The response output isn't very useful
- in this case because the content is a JPG image. In the response section (bottom right),
- select Image View from the combo box. The JPG should now be visible.</li>
-
-<li>Close the Web browser and the TCP/IP monitor views.</li>
-
-</ol>
-
-
-<H3>3.2 Scenario 2 - Debugging a JSP on Tomcat v5.0</H3>
-
-<p>In this scenario, we'll create a new Web project and JSP file, and then debug the JSP on Tomcat v5.0.
-If you are using another version of Tomcat, you can follow along with all of the steps, but the debugger
-will not stop at the breakpoint in the JSP.</p>
-
-<ol>
-<li>Go to create a new project and select Web > Dynamic Web Project. Click Next.</li>
-
- <p><img src="ServerToolsEval_files/newProject.gif" width="500" height="500"/></p>
-
-<li>Type My Web as the Web project name. If you want to use an older version of
- Tomcat, select a supported J2EE Web version for your version of Tomcat. If in
- doubt as to what version(s) your Tomcat server supports, choose 2.2.</li>
-
-<li>The target server field is blank if you have not used this workspace before.
- Click New... to create a new server runtime.</li>
-
-<li>Select your version of Tomcat from the list, and click Next.</li>
-
- <p><img src="ServerToolsEval_files/newRuntime.gif" width="438" height="422"/></p>
-
-<li>Use the Browse... button to locate the Tomcat installation directory (the directory
- in which you unzipped Tomcat).</li>
-
-<li>Tomcat requires a JDK to be able to compile JSP files. If you are using a JRE to
- run Eclipse, you'll need to install a JDK now. Click Installed JREs...</li>
-
-<li>Click Add... to create a new Installed JRE. Type MyJDK in the JRE Name: field
- and use the first Browse... button to choose the directory in which you have a JDK.
- The default system libraries list at the bottom of the dialog should automatically
- fill up.</li>
-
-<li>If you are using an IBM JDK, type -Xj9 in the Default VM Arguments: field to
- allow JSP debugging. (In either case, JSP debugging is only supported by Tomcat v5.0)</li>
-
- <p><img src="ServerToolsEval_files/JDKSettings.gif" width="486" height="443"/></p>
-
-<li>Click OK to get back to the Installed JRE preferences. Your new JDK should now
- be listed. You do not need to check the JDK to have the Web project compile against
- the Tomcat JDK - when the project is created it will automatically be set to compile
- against the correct JDK and Tomcat libraries.</li>
-
- <p><img src="ServerToolsEval_files/installedJREs.gif" width="635" height="539"/></p>
-
-<li>Click OK again, and make sure that MyJDK is selected in the JRE: field. Click Finish.</li>
-
- <p><img src="ServerToolsEval_files/tomcatRuntime.gif" width="438" height="422"/></p>
-
-<li>You should now be back at the Web project wizard. Uncheck the <b>Add module to an EAR
- project</b> checkbox, since Tomcat does not support EAR projects. The wizard should
- now look like this:</li>
-
- <p><img src="ServerToolsEval_files/newWebProject.gif" width="503" height="504"/></p>
-
-<li>Click Finish. The new Web project will be created in the workspace.</li>
-
-<li>Create a new file, called today.jsp. The JSP editor will be automatically opened up.</li>
-
-<li>Type
- <pre>Today is: <%= new java.util.Date().toString() %></pre>
- in the editor and save.</li>
-
-<li>Double click in the margin by the text you just entered to set a breakpoint.</li>
-
- <p><img src="ServerToolsEval_files/JSP.gif" width="875" height="657"/></p>
-
-<li>Close the editor.</li>
-
-<li>Right click on the today.jsp file in the Navigator and choose Debug > Debug on Server.</li>
-
- <p><img src="ServerToolsEval_files/debugOnServer.gif" width="875" height="657"/></p>
-
-<li>The server selection wizard is empty because there are no servers defined. Click
- New Server... and select your version of Tomcat. Click Finish.</li>
-
- <p><img src="ServerToolsEval_files/newServer.gif" width="508" height="521"/></p>
-
-<li>Ensure that the server is selected and click Finish.</li>
-
- <p><img src="ServerToolsEval_files/serverSelection.gif" width="438" height="517"/></p>
-
-<li>When Eclipse prompts you to switch to the Debug perspective, click Yes.</li>
-
-<li>In a few seconds, the JSP file will stop in the debugger and the JSP editor
- will be opened. From here, you can inspect the variables and make changes to the
- JSP file. Click on the Resume button in the Debug view to run the JSP file.</li>
-
- <p><img src="ServerToolsEval_files/debugJSP.gif" width="875" height="657"/></p>
-
-<li>The Web browser will open, displaying the results of the JSP page:</li>
-
- <p><img src="ServerToolsEval_files/browserJSP.gif" width="875" height="657"/></p>
-
-</ol>
-
-
-<H2>4.0 Provide Feedback to Us</H2>
-
-<P>We encourage development/design feed back on the <A
- href="https://dev.eclipse.org/mailman/listinfo/wtp-dev">wtp-dev</A> mailing list. You can subscribe to the list via <A
- href="https://dev.eclipse.org/mailman/listinfo/wtp-dev">this link</A>.<BR>
-<BR>
-For usage questions, discussion of bugs, and strange behaviour please post to the eclipse.webtools newsgroup. Information on the Web Tools Platform newsgroup can be found <A
- href="http://www.eclipse.org/newsgroups/index.html">here</A>.</P>
-</p>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/JDKSettings.gif b/initial-contribution/IBM/evalGuides/ServerToolsEval_files/JDKSettings.gif
deleted file mode 100644
index 394f6dd..0000000
--- a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/JDKSettings.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/JSP.gif b/initial-contribution/IBM/evalGuides/ServerToolsEval_files/JSP.gif
deleted file mode 100644
index 67abdb0..0000000
--- a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/JSP.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/browserJSP.gif b/initial-contribution/IBM/evalGuides/ServerToolsEval_files/browserJSP.gif
deleted file mode 100644
index f92b8d4..0000000
--- a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/browserJSP.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/browserPrefs.gif b/initial-contribution/IBM/evalGuides/ServerToolsEval_files/browserPrefs.gif
deleted file mode 100644
index e9fedb5..0000000
--- a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/browserPrefs.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/debugJSP.gif b/initial-contribution/IBM/evalGuides/ServerToolsEval_files/debugJSP.gif
deleted file mode 100644
index 41aa17c..0000000
--- a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/debugJSP.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/debugOnServer.gif b/initial-contribution/IBM/evalGuides/ServerToolsEval_files/debugOnServer.gif
deleted file mode 100644
index 303a10c..0000000
--- a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/debugOnServer.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/editBrowser.gif b/initial-contribution/IBM/evalGuides/ServerToolsEval_files/editBrowser.gif
deleted file mode 100644
index 3cfb5fd..0000000
--- a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/editBrowser.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/installedJREs.gif b/initial-contribution/IBM/evalGuides/ServerToolsEval_files/installedJREs.gif
deleted file mode 100644
index 08b2efa..0000000
--- a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/installedJREs.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/internal_browser.gif b/initial-contribution/IBM/evalGuides/ServerToolsEval_files/internal_browser.gif
deleted file mode 100644
index 09f609d..0000000
--- a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/internal_browser.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/monitorBrowser.gif b/initial-contribution/IBM/evalGuides/ServerToolsEval_files/monitorBrowser.gif
deleted file mode 100644
index c21fce3..0000000
--- a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/monitorBrowser.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/monitorPrefs.gif b/initial-contribution/IBM/evalGuides/ServerToolsEval_files/monitorPrefs.gif
deleted file mode 100644
index 1b618e1..0000000
--- a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/monitorPrefs.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/newProject.gif b/initial-contribution/IBM/evalGuides/ServerToolsEval_files/newProject.gif
deleted file mode 100644
index 9cf6c81..0000000
--- a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/newProject.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/newRuntime.gif b/initial-contribution/IBM/evalGuides/ServerToolsEval_files/newRuntime.gif
deleted file mode 100644
index 1aeee2d..0000000
--- a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/newRuntime.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/newServer.gif b/initial-contribution/IBM/evalGuides/ServerToolsEval_files/newServer.gif
deleted file mode 100644
index 3505041..0000000
--- a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/newServer.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/newWebProject.gif b/initial-contribution/IBM/evalGuides/ServerToolsEval_files/newWebProject.gif
deleted file mode 100644
index 98d6e89..0000000
--- a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/newWebProject.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/serverSelection.gif b/initial-contribution/IBM/evalGuides/ServerToolsEval_files/serverSelection.gif
deleted file mode 100644
index a5995ab..0000000
--- a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/serverSelection.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/serversView.gif b/initial-contribution/IBM/evalGuides/ServerToolsEval_files/serversView.gif
deleted file mode 100644
index f698a49..0000000
--- a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/serversView.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/tomcatRuntime.gif b/initial-contribution/IBM/evalGuides/ServerToolsEval_files/tomcatRuntime.gif
deleted file mode 100644
index 85f7542..0000000
--- a/initial-contribution/IBM/evalGuides/ServerToolsEval_files/tomcatRuntime.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/brackets.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/brackets.jpg
deleted file mode 100644
index 16a099a..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/brackets.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/brackets2.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/brackets2.jpg
deleted file mode 100644
index 8213182..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/brackets2.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/cleanupDialog.gif b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/cleanupDialog.gif
deleted file mode 100644
index 41af040..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/cleanupDialog.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/dtdprefs.gif b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/dtdprefs.gif
deleted file mode 100644
index 7d50178..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/dtdprefs.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/editorprefs.gif b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/editorprefs.gif
deleted file mode 100644
index aac9154..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/editorprefs.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/editorprefsmenu.gif b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/editorprefsmenu.gif
deleted file mode 100644
index b34f731..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/editorprefsmenu.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/expandSelectionToMenu.gif b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/expandSelectionToMenu.gif
deleted file mode 100644
index 7e2a9ff..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/expandSelectionToMenu.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/findAll.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/findAll.jpg
deleted file mode 100644
index fd15000..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/findAll.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/hyperlink1.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/hyperlink1.jpg
deleted file mode 100644
index 7871c4a..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/hyperlink1.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/hyperlink2.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/hyperlink2.jpg
deleted file mode 100644
index 87d645d..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/hyperlink2.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/newQuickAssistProposals.gif b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/newQuickAssistProposals.gif
deleted file mode 100644
index 45efa7a..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/newQuickAssistProposals.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/newQuickFixProposals.gif b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/newQuickFixProposals.gif
deleted file mode 100644
index f025e35..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/newQuickFixProposals.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/occurrences_menuaction.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/occurrences_menuaction.jpg
deleted file mode 100644
index 9235576..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/occurrences_menuaction.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/occurrences_results.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/occurrences_results.jpg
deleted file mode 100644
index 0d57435..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/occurrences_results.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/quickdiff1.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/quickdiff1.jpg
deleted file mode 100644
index 8cd83a9..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/quickdiff1.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/quickdiff2.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/quickdiff2.jpg
deleted file mode 100644
index 343820a..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/1/quickdiff2.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/editbreakpoints.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/editbreakpoints.jpg
deleted file mode 100644
index c85b371..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/editbreakpoints.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/editbreakpoints2.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/editbreakpoints2.jpg
deleted file mode 100644
index d84d275..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/editbreakpoints2.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/jsp_search.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/jsp_search.jpg
deleted file mode 100644
index 283a9d1..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/jsp_search.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/jsp_searchresults.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/jsp_searchresults.jpg
deleted file mode 100644
index 2bd6619..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/jsp_searchresults.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/launchQuickAssist.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/launchQuickAssist.jpg
deleted file mode 100644
index ba2622f..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/launchQuickAssist.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/localRename.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/localRename.jpg
deleted file mode 100644
index 793e677..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/localRename.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/rename1.gif b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/rename1.gif
deleted file mode 100644
index 4d520b3..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/rename1.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/rename2.gif b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/rename2.gif
deleted file mode 100644
index afdc631..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/rename2.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/rename3.gif b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/rename3.gif
deleted file mode 100644
index 3d4e958..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/rename3.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/rename4.gif b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/rename4.gif
deleted file mode 100644
index e6ec730..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/2/rename4.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/3/customizer1.gif b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/3/customizer1.gif
deleted file mode 100644
index ba26920..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/3/customizer1.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/3/customizer2.gif b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/3/customizer2.gif
deleted file mode 100644
index 57ed2c3..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/3/customizer2.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/3/formatDocProgressDialog.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/3/formatDocProgressDialog.jpg
deleted file mode 100644
index 4c125da..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/3/formatDocProgressDialog.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/3/javaaddtosnippets1.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/3/javaaddtosnippets1.jpg
deleted file mode 100644
index 066d815..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/3/javaaddtosnippets1.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/3/sourceMenu.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/3/sourceMenu.jpg
deleted file mode 100644
index 4b1ca65..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/3/sourceMenu.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/3/tasktags1.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/3/tasktags1.jpg
deleted file mode 100644
index 76c9551..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/3/tasktags1.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/ProgressView.gif b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/ProgressView.gif
deleted file mode 100644
index 7c9527d..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/ProgressView.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/addBlockCommentEditor.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/addBlockCommentEditor.jpg
deleted file mode 100644
index 07fcc84..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/addBlockCommentEditor.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/addBlockCommentMenu.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/addBlockCommentMenu.jpg
deleted file mode 100644
index e8738c1..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/addBlockCommentMenu.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/annotation1.bmp.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/annotation1.bmp.jpg
deleted file mode 100644
index cd0227e..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/annotation1.bmp.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/attrusage1.bmp.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/attrusage1.bmp.jpg
deleted file mode 100644
index 69faada..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/attrusage1.bmp.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/breakpoints1.bmp.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/breakpoints1.bmp.jpg
deleted file mode 100644
index f995cc8..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/breakpoints1.bmp.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/commentEditor.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/commentEditor.jpg
deleted file mode 100644
index a27da29..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/commentEditor.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/commentMenu.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/commentMenu.jpg
deleted file mode 100644
index 5c54bfd..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/commentMenu.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/default_style.css b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/default_style.css
deleted file mode 100644
index 217167f..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/default_style.css
+++ /dev/null
@@ -1,15 +0,0 @@
-p, table, td, th { font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre { font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code { font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup { font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 { font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li { font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 { font-family: verdana, arial, helvetica, geneva; font-size: 28px; font-weight: bold}
-body { font-family: verdana, arial, helvetica, geneva; font-size: 10pt; clip: rect( ); margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large;; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small;; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link { text-decoration: none; color: #FFFFFF}
-a.bar:visited { color: #FFFFFF; text-decoration: none}
-a.bar:hover { color: #FFFFFF; text-decoration: underline}
-a.bar { color: #FFFFFF}
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/featuretable1.html b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/featuretable1.html
deleted file mode 100644
index f8c6f3f..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/featuretable1.html
+++ /dev/null
@@ -1,958 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=CP1252">
-<title>featuretable1.html</title>
-</head>
-<body>
-<p></p>
-<p:colorscheme
- colors="#000000,#FFFFFF,#808080,#CCCCFF,#7889FB,#DFFF66,#C0C0C0,#D18213" />
-
-<TABLE width="446" height="239" cellpadding="0" cellspacing="0">
- <TR>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <P> </P>
- </TD>
- <TD width="56" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='mso-line-spacing:"100 35 15";mso-char-wrap:1;mso-kinsoku-overflow:
- 1'><SPAN
- style='mso-bidi-font-family:Arial;mso-hansi-font-family:"Times New Roman";
- font-size:9pt'><B>Java</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='mso-line-spacing:"100 35 15";mso-char-wrap:1;mso-kinsoku-overflow:
- 1'><SPAN
- style='mso-bidi-font-family:Arial;mso-hansi-font-family:"Times New Roman";
- font-size:9pt'><B>XML</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='mso-line-spacing:"100 35 15";mso-char-wrap:1;mso-kinsoku-overflow:
- 1'><SPAN
- style='mso-bidi-font-family:Arial;mso-hansi-font-family:"Times New Roman";
- font-size:9pt'><B>JSP</B></SPAN></DIV>
- </TD>
- <TD width="56" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='mso-line-spacing:"100 35 15";mso-char-wrap:1;mso-kinsoku-overflow:
- 1'><SPAN
- style='mso-bidi-font-family:Arial;mso-hansi-font-family:"Times New Roman";
- font-size:9pt'><B>HTML
- & </B></SPAN><SPAN
- style='mso-bidi-font-family:
- Arial;mso-hansi-font-family:"Times New Roman";font-size:9pt'><B>XHTML</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='mso-line-spacing:"100 35 15";mso-char-wrap:1;mso-kinsoku-overflow:
- 1'><SPAN
- style='mso-bidi-font-family:Arial;mso-hansi-font-family:"Times New Roman";
- font-size:9pt'><B>CSS</B></SPAN></DIV>
- </TD>
- <TD width="56" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='mso-line-spacing:"100 35 15";mso-char-wrap:1;mso-kinsoku-overflow:
- 1'><SPAN
- style='mso-bidi-font-family:Arial;mso-hansi-font-family:"Times New Roman";
- font-size:9pt'><B>DTD</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='mso-line-spacing:"100 35 15";mso-char-wrap:1;mso-kinsoku-overflow:
- 1'><SPAN
- style='mso-bidi-font-family:Arial;mso-hansi-font-family:"Times New Roman";
- font-size:9pt'><B>Java
- Script</B></SPAN></DIV>
- </TD>
- </TR>
- <TR>
- <TD width="57" height="25"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='mso-line-spacing:"100 35 15";mso-char-wrap:1;mso-kinsoku-overflow:
- 1'><SPAN
- style='mso-bidi-font-family:Arial;mso-hansi-font-family:"Times New Roman";
- font-size:9pt'><B>Highlighting</B></SPAN></DIV>
- </TD>
- <TD width="56" height="25"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="25"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="25"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="56" height="25"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="25"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="56" height="25"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="25"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- </TR>
- <TR>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='mso-line-spacing:"100 35 15";mso-char-wrap:1;mso-kinsoku-overflow:
- 1'><SPAN
- style='mso-bidi-font-family:Arial;mso-hansi-font-family:"Times New Roman";
- font-size:9pt'><B>Content
- </B></SPAN><SPAN
- style='mso-bidi-font-family:Arial;
- mso-hansi-font-family:"Times New Roman";font-size:9pt'><B>Assist</B></SPAN></DIV>
- </TD>
- <TD width="56" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="56" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="56" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt"><B>N</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- </TR>
- <TR>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='mso-line-spacing:"100 35 15";mso-char-wrap:1;mso-kinsoku-overflow:
- 1'><SPAN
- style='mso-bidi-font-family:Arial;mso-hansi-font-family:"Times New Roman";
- font-size:9pt'><B>Parameter/At</B></SPAN><SPAN
- style='mso-bidi-font-family:
- Arial;mso-hansi-font-family:"Times New Roman";font-size:9pt'><B>tribute
- Hints</B></SPAN></DIV>
- </TD>
- <TD width="56" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="56" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <P> </P>
- </TD>
- <TD width="56" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <P> </P>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <P> </P>
- </TD>
- </TR>
- <TR>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='mso-line-spacing:"100 35 15";mso-char-wrap:1;mso-kinsoku-overflow:
- 1'><SPAN
- style='mso-bidi-font-family:Arial;mso-hansi-font-family:"Times New Roman";
- font-size:9pt'><B>Formatting</B></SPAN></DIV>
- </TD>
- <TD width="56" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="56" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="56" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt"><B>N</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <P> </P>
- </TD>
- </TR>
- <TR>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='mso-line-spacing:"100 35 15";mso-char-wrap:1;mso-kinsoku-overflow:
- 1'><SPAN
- style='mso-bidi-font-family:Arial;mso-hansi-font-family:"Times New Roman";
- font-size:9pt'><B>Structured
- </B></SPAN><SPAN
- style='mso-bidi-font-family:
- Arial;mso-hansi-font-family:"Times New Roman";font-size:9pt'><B>Selection</B></SPAN></DIV>
- </TD>
- <TD width="56" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="56" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>?</B></SPAN></DIV>
- </TD>
- <TD width="56" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>?</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <P> </P>
- </TD>
- </TR>
- <TR>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='mso-line-spacing:"100 35 15";mso-char-wrap:1;mso-kinsoku-overflow:
- 1'><SPAN
- style='mso-bidi-font-family:Arial;mso-hansi-font-family:"Times New Roman";
- font-size:9pt'><B>Hover
- Info</B></SPAN></DIV>
- </TD>
- <TD width="56" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="56" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <P> </P>
- </TD>
- <TD width="56" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <P> </P>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <P> </P>
- </TD>
- </TR>
- <TR>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='mso-line-spacing:"100 35 15";mso-char-wrap:1;mso-kinsoku-overflow:
- 1'><SPAN
- style='mso-bidi-font-family:Arial;mso-hansi-font-family:"Times New Roman";
- font-size:9pt'><B>Smart
- Edit</B></SPAN></DIV>
- </TD>
- <TD width="56" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="56" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <P> </P>
- </TD>
- <TD width="56" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <P> </P>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <P> </P>
- </TD>
- </TR>
- <TR>
- <TD width="57" height="27"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='mso-line-spacing:"100 35 15";mso-char-wrap:1;mso-kinsoku-overflow:
- 1'><SPAN
- style='font-family:"Times New Roman";mso-bidi-font-family:Arial;
- mso-hansi-font-family:"Times New Roman";font-size:9pt'><B></B></SPAN><SPAN
- style='mso-bidi-font-family:Arial;mso-hansi-font-family:"Times New Roman";
- font-size:9pt'><B>Open
- On</B></SPAN><SPAN
- style='font-family:"Times New Roman";
- mso-bidi-font-family:Arial;mso-hansi-font-family:"Times New Roman";
- font-size:9pt'><B></B></SPAN><SPAN
- style='font-family:Arial;mso-bidi-font-family:
- Arial;mso-hansi-font-family:"Times New Roman";font-size:9pt'><B> </B></SPAN></DIV>
- <DIV
- style='mso-line-spacing:"100 35 15";mso-char-wrap:1;mso-kinsoku-overflow:
- 1'><SPAN
- style='mso-bidi-font-family:Arial;mso-hansi-font-family:"Times New Roman";
- font-size:9pt'><B>(hyperlinks)</B></SPAN></DIV>
- </TD>
- <TD width="56" height="27"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="27"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="27"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="56" height="27"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="27"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="56" height="27"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <P> </P>
- </TD>
- <TD width="57" height="27"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <P> </P>
- </TD>
- </TR>
- <TR>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='mso-line-spacing:"100 35 15";mso-char-wrap:1;mso-kinsoku-overflow:
- 1'><SPAN
- style='mso-bidi-font-family:Arial;mso-hansi-font-family:"Times New Roman";
- font-size:9pt'><B>Find
- Element </B></SPAN><SPAN
- style='mso-bidi-font-family:
- Arial;mso-hansi-font-family:"Times New Roman";font-size:9pt'><B>Occurrences</B></SPAN></DIV>
- </TD>
- <TD width="56" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="56" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <DIV
- style='text-align:center;mso-line-spacing:"100 35 15";mso-char-wrap:
- 1;mso-kinsoku-overflow:1'><SPAN
- style="mso-bidi-font-family:Arial;mso-hansi-font-family:
- Arial;font-size:10pt;color:#66FF66"><B>Y</B></SPAN></DIV>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <P> </P>
- </TD>
- <TD width="56" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <P> </P>
- </TD>
- <TD width="57" height="24"
- style="vertical-align:top;border-left-style:solid;
- border-left-width:1px;border-left-color:white;border-top-style:solid;
- border-top-width:1px;border-top-color:white;border-bottom-style:solid;
- border-bottom-width:1px;border-bottom-color:white;border-right-style:solid;
- border-right-width:1px;border-right-color:white">
- <P> </P>
- </TD>
- </TR>
-</TABLE>
-
-</body>
-</html>
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/hoverspref.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/hoverspref.jpg
deleted file mode 100644
index 375f331..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/hoverspref.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/jspcodeerror1.bmp.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/jspcodeerror1.bmp.jpg
deleted file mode 100644
index d62afbf..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/jspcodeerror1.bmp.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/jsphoverinfo1.bmp.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/jsphoverinfo1.bmp.jpg
deleted file mode 100644
index 847fcbf..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/jsphoverinfo1.bmp.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/outlinelink1.bmp.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/outlinelink1.bmp.jpg
deleted file mode 100644
index ffff217..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/outlinelink1.bmp.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/quickFix.jpg b/initial-contribution/IBM/evalGuides/StructuredSourceEditors/quickFix.jpg
deleted file mode 100644
index 7d53aad..0000000
--- a/initial-contribution/IBM/evalGuides/StructuredSourceEditors/quickFix.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/TabbedPropertyEval.html b/initial-contribution/IBM/evalGuides/TabbedPropertyEval.html
deleted file mode 100644
index 2cbf3f4..0000000
--- a/initial-contribution/IBM/evalGuides/TabbedPropertyEval.html
+++ /dev/null
@@ -1,31 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=Cp1252">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link href="../theme/Master.css" rel="stylesheet" type="text/css">
-<title>Getting Started.html</title>
-</head>
-<body>
-<H1>Tabbed Property View Evaluation Guide</H1>
-<H2>1.0 Introduction</H2>
-<P>The Common UI Properties feature provides a set of extension points and supporting framework to implement a tabbed UI for the Eclipse properties view.</p>
-<H2>2.0 Getting Started</H2>
-<p>The com.ibm.xtools.common.ui.properties plug-in defines the following three extension points:</p>
-<ul><li>The property contributor extension point describes a set of workbench parts that are contributors of properties to be displayed within tabs in the properties view. <br><br>
-<li>The property tabs extension point describes a list of tabs that will be contributed to the properties view.<br><br>
-<li>The property sections extension point describes a list of sections to be displayed within tabs that will be contributed to the property view. A section is a class that adds a set of widgets to a tab based on element selection and filtering. The sections are created using the Eclipse UI forms toolkit.<br><br>
-</ul>
-<H2>3.0 Example</H2>
-<p>Below is an example snapshot of a usage of the tabbed properties view. The properties view is displaying four tabs based on the selected element. The General tab is currently selected. This implementation has provided a standard label provider so that a title bar is displayed with the element icon and text. </p>
-<img border=0 height=229 width=760 src="TabbedPropertyEval_files/properties_view.jpg">
-<H2>4.0 Provide Feedback to Us</H2>
-<P>We encourage development/design feed back on the <A
- href="https://dev.eclipse.org/mailman/listinfo/wtp-dev">wtp-dev</A> mailing list. You can subscribe to the list via <A
- href="https://dev.eclipse.org/mailman/listinfo/wtp-dev">this link</A>.<BR>
-<BR>
-For usage questions, discussion of bugs, and strange behaviour please post to the eclipse.webtools newsgroup. Information on the Web Tools Platform newsgroup can be found <A
- href="http://www.eclipse.org/newsgroups/index.html">here</A>.</P>
-
-</P>
-</body>
-</html>
\ No newline at end of file
diff --git a/initial-contribution/IBM/evalGuides/TabbedPropertyEval_files/properties_view.jpg b/initial-contribution/IBM/evalGuides/TabbedPropertyEval_files/properties_view.jpg
deleted file mode 100644
index 156b952..0000000
--- a/initial-contribution/IBM/evalGuides/TabbedPropertyEval_files/properties_view.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval.html b/initial-contribution/IBM/evalGuides/WebServicesToolsEval.html
deleted file mode 100644
index f1f9fc4..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval.html
+++ /dev/null
@@ -1,833 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
- <meta http-equiv="Content-Style-Type" content="text/css">
- <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
- <title>Getting Started.html</title>
-<link href="../theme/Master.css" rel="stylesheet" type="text/css">
-</head>
-<body>
-
-<h1>
-Web Services Tools Evaluation Guide</h1>
-
-<h2>
-<a NAME="intro"></a>1.0 Introduction</h2>
-The Web Services Tools contribution provides an extensible framework of
-wizards, actions, preferences, code generators and Web applications to
-help Eclipse users create, publish, discover, consume and test Web Services
-chiefly for, but not limited to, the Java programming language and the
-J2EE platform. Included in the contribution are tools for building Apache
-Axis Web services and Web service clients on Apache Tomcat.
-<p>The design and capabilities of the tools, both internally and visually,
-are anchored to a small but significant set of public specifications and
-consortiums, including:
-<ul>
-<li>
-<a href="http://www.w3c.org/XML/Schema">XML Schema 1.0</a>.</li>
-
-<li>
-<a href="http://www.w3c.org/TR/2000/NOTE-SOAP-20000508/">SOAP 1.1</a>.</li>
-
-<li>
-<a href="http://www.w3c.org/TR/wsdl">WSDL 1.1</a>.</li>
-
-<li>
-<a href="http://www.uddi.org/">UDDI v2</a>.</li>
-
-<li>
-<a href="http://www.ws-i.org/">WS-I</a>.</li>
-
-<li>
-<a href="http://www.jcp.org/en/jsr/detail?id=101">JSR-101</a>.</li>
-
-<li>
-<a href="http://www.jcp.org/en/jsr/detail?id=109">JSR-109</a>.</li>
-
-<li>
-<a href="http://java.sun.com/j2ee/index.jsp">J2EE 1.4</a>.</li>
-
-<li>
-<a href="http://ws.apache.org/axis/">Apache Axis</a>.</li>
-
-<li>
-<a href="http://jakarta.apache.org/tomcat/">Apache Tomcat</a>.</li>
-</ul>
-Included in the Web Services Tools contribution are:
-<ul>
-<li>
-An embedded Web application for publishing, discovering and invoking Web
-services.</li>
-
-<li>
-Extensible Wizards for creating Web Services from existing Java classes
-(these are called "bottom up" scenarios).</li>
-
-<li>
-Extensible Wizards for creating Web services from existing WSDL (these
-are called "top down" scenarios).</li>
-
-<li>
-Extensible Wizards for creating Web service clients from WSDL.</li>
-
-<li>
-Extensions in support of Apache Axis and Apache Tomcat.</li>
-
-<li>
-Wizards for integrating with public and private UDDI registries.</li>
-
-<li>
-Wizards for configuring Web service and Web service client JAX-RPC handlers.</li>
-
-<li>
-Popup actions.</li>
-
-<li>
-Web Service scenario preference pages.</li>
-
-<li>
-Internet proxy firewall preference page.</li>
-
-<li>
-The Environment Command Framework, used to organize UI-agnostic engine
-code into dynamic trees of executable commands.</li>
-
-<li>
-The Dynamic Wizard Framework, used to build wizards with highly dynamic
-page flows.</li>
-
-<li>
-Models, parsers and code generators.</li>
-</ul>
-<b>Note:</b> The <a href="J2EEToolsEval.html">J2EE Tools</a> and <a href="XMLToolsEval.html">XML
-Tools</a> contributions also contain tools for Web services, such as the
-WSDL Editor, the WSDL and WS-I validators, and the J2EE Project Explorer.
-<h2>
-<a NAME="getstart"></a>2.0 Getting Started</h2>
-Of all the Web services tools included in this contribution, three of them
-stand out as the primary means to developing and working with Web services:
-<ul>
-<li>
-The <b>Web Services Explorer</b> for publishing, discovering and invoking
-Web services.</li>
-
-<li>
-The <b>Web Service</b> wizard for creating new Web services bottom-up from
-Java or top-down from WSDL.</li>
-
-<li>
-The <b>Web Service Client</b> wizard for creating Web service client proxies
-and sample JSP clients from WSDL.</li>
-</ul>
-If you have a connection to the internet, then the easiest way to get started
-with the tools and learn a bit about Web services is to run the Web Services
-Explorer and play with some Web services on the internet. You don't need
-anything in your workspace, and you don't need any installed servers. Follow
-the instructions in <a href="#tour-wse">Chapter 3.1</a> to use the Web
-Services Explorer to invoke an operation on a Web service available via
-<a href="http://www.xmethods.net">XMethods</a>.
-<p>If you do not have a connection to the internet, then the next easiest
-way to get started is to create your own Web service. The Web Service wizard
-will help you do this, however, there are a couple of prerequisites. First,
-you will need to download a version of <a href="http://jakarta.apache.org/tomcat/">Apache
-Tomcat</a> and install it into Eclipse WTP using the Installed Runtimes
-preference page. Second, you will need to create a Web project and create
-a basic Java class within it. Follow the instructions in <a href="#tour-bu">Chapter
-3.2</a> to create a Web service and Web service client bottom-up from a
-simple Java class.
-<h2>
-<a NAME="tour"></a>3.0 Quick Tour</h2>
-The following chapters will guide you through a few of the more prominent
-tools in this contribution:
-<ol>
-<li>
-<a href="#tour-wse">Using the Web Services Explorer to test a Web service</a></li>
-
-<li>
-<a href="#tour-bu">Using the Web Service wizard to build a Web service
-bottom-up from Java</a></li>
-
-<li>
-<a href="#tour-prefs">Exploring the Preferences</a></li>
-
-<li>
-<a href="#tour-wizards">Exploring the Wizards</a></li>
-
-<li>
-<a href="#tour-popups">Exploring the Popup Actions</a></li>
-
-<li>
-<a href="#tour-frameworks">Behind the Scenes</a></li>
-</ol>
-
-<h3>
-<a NAME="tour-wse"></a>3.1 Using the Web Services Explorer to test a Web
-service</h3>
-This scenario is very simple. It demonstrates how to use the Web Services
-Explorer to invoke operations on a Web service named "<a href="http://www.xmethods.net/ve2/ViewListing.po;jsessionid=TZdF2D6E_KB9KKIY5_DG4FJw(QHyMHiRM)?key=uuid:477CEED8-1EDD-89FA-1070-6C2DBE1685F8">Temperature
-- Weather</a>" as available from <a href="http://www.xmethods.net/">XMethods</a>
-on the internet. The only prerequisite is that you be connected to the
-internet. If you are connected via a firewall, you can use the Internet
-preferences page (choose <b>Preferences -> Internet</b> from the main menu).
-Other than that, you can begin with a completely fresh workspace and no
-installed servers.
-<ol>
-<li>
-Launch the Eclipse WTP workbench.</li>
-
-<li>
-From the main menu bar, select <b>Run -> Launch the Web Services Explorer</b>.
-This will take a few moments the first time while Eclipse's internal Tomcat
-server starts up and loads the Web Services Explorer application. After
-the Web Browser view opens, maximize it. Result:</li>
-
-<br><img SRC="WebServicesToolsEval_files/image0BJ.JPG" NOSAVE height=544 width=738>
-<li>
-In the Web Service Explorer's toolbar (top-right), click on the <b>WSDL
-Page</b> icon, <img SRC="WebServicesToolsEval_files/wsdl.gif" NOSAVE height=16 width=16>.
-Result:</li>
-
-<br><img SRC="WebServicesToolsEval_files/image7DI.JPG" NOSAVE height=544 width=738>
-<li>
-Click on <img SRC="WebServicesToolsEval_files/wsdl_main.gif" NOSAVE height=16 width=16><b>WSDL
-Main</b>. Result:</li>
-
-<br><img SRC="WebServicesToolsEval_files/imageN5S.JPG" NOSAVE height=544 width=738>
-<li>
-In the <b>WSDL URL</b> field, enter the URL <tt>http://www.xmethods.net/sd/2001/TemperatureService.wsdl</tt>,
-then click on <b>Go</b>. Result:</li>
-
-<br><img SRC="WebServicesToolsEval_files/imagePK7.JPG" NOSAVE height=544 width=738>
-<li>
-Under <b>Operations</b> in the right hand pane, click on <b>getTemp</b>.
-Result:</li>
-
-<br><img SRC="WebServicesToolsEval_files/image9TE.JPG" NOSAVE height=544 width=738>
-<li>
-In the <b>zipcode string</b> entry field, enter <tt>90210</tt>, then click
-on <b>Go</b>. In the <b>Status</b> pane, you should see an answer like
-this:</li>
-
-<br><b>return (float): 67.0</b>
-<br>You may need to move the horizontal bar separating the <b>Actions</b>
-and <b>Status</b> panes upwards a bit to get a better view. Result:<img SRC="WebServicesToolsEval_files/imageTVQ.JPG" NOSAVE BORDER=0 height=544 width=738></ol>
-<b>Explanation</b>
-<p>The Web Services Explorer is a JSP Web application hosted on the Apache
-Tomcat servlet engine contained within Eclipse. It is integrated into Eclipse
-on two levels: visually by virtue of it running in the embedded browser,
-and logically by virtue of it running as a thread in the Eclipse JRE. Though
-not demonstrated in this scenario, this latter type of integration allows
-the Web Services Explorer to access resources in the workspace, write resources
-into the workspace, and launch various Web services wizards.
-<p>The Web Services Explorer provides three key services to the user:
-<ol>
-<li>
-Comprehensive support for discovering Web services in WS-Inspection 1.0
-documents, and in UDDI v2 or v3 registries using the UDDI v2 protocol.</li>
-
-<li>
-Comprehensive support for publishing Web services to UDDI v2 or v3 registries
-using the UDDI v2 protocol.</li>
-
-<li>
-Comprehensive support for browsing and invoking Web services natively<b>*</b>
-via their WSDL and XSD.</li>
-</ol>
-<b>*</b> A key point of the scenario above is that no code was generated
-and no servers were required in order to invoke operations on the WSDL.
-<h3>
-<a NAME="tour-bu"></a>3.2 Using the Web Service wizard to build a Web service
-bottom-up from Java</h3>
-This scenario shows how to create a simple Web service and Web service
-client from a Java class. The Java class in this scenario converts between
-the Celsius and Farenheit temperature scales. Before creating the Web service,
-there are three prerequisites:
-<ol>
-<li>
-<a href="#tour-bu-prereqtomcat">Install Apache Tomcat</a></li>
-
-<li>
-<a href="#tour-bu-prereqwsi">Turn off WS-I compliance checking</a></li>
-
-<li>
-<a href="#tour-bu-prereqweb">Create a Web project</a></li>
-</ol>
-If you have completed these prerequisites, carry on with the scenario at
-chapter <a href="#tour-bu-main">3.2.4</a>.
-<h4>
-<a NAME="tour-bu-prereqtomcat"></a>3.2.1 Install Apache Tomcat</h4>
-
-<ol>
-<li>
-Download and unzip <a href="http://jakarta.apache.org/tomcat/">Apache Tomcat</a>
-(this scenario was written using Apache Tomcat version 4.1.30, but other
-versions can be substituted).</li>
-
-<li>
-Start the Eclipse WTP workbench.</li>
-
-<li>
-Open <b>Window -> Preferences -> Server -> Installed Runtimes</b> to create
-a Tomcat installed runtime.</li>
-
-<br><img SRC="WebServicesToolsEval_files/imageOJG.JPG" NOSAVE height=532 width=634>
-<li>
-Click on <b>Add...</b> to open the <b>New Server Runtime</b> dialog, then
-select your runtime under <b>Apache</b> (Apache Tomcat v4.1 in this example):</li>
-
-<br><img SRC="WebServicesToolsEval_files/imageD3M.JPG" NOSAVE height=415 width=438>
-<li>
-Click <b>Next</b>, and fill in your <b>Tomcat installation directory</b>:</li>
-
-<br><img SRC="WebServicesToolsEval_files/image849.JPG" NOSAVE height=415 width=438>
-<li>
-Ensure the selected <b>JRE</b> is a full JDK and is of a version that will
-satisfy Apache Tomcat (this scenario was written using SUN JDK 1.4.2_05).
-If necessary, you can click on <b>Installed JREs...</b> to add JDKs to
-Eclipse.</li>
-
-<li>
-Click <b>Finish</b>.</li>
-</ol>
-<b>Note:</b> Further details on installing and using servers can be found
-in the <a href="ServerToolsEval.html">Server Tools</a> contribution.
-<h4>
-<a NAME="tour-bu-prereqwsi"></a>3.2.2 Turn off WS-I compliance checking</h4>
-
-<ol>
-<li>
-Open <b>Window -> Preferences -> Web Services -> WS-I Compliance</b>.</li>
-
-<li>
-Change both compliance levels from <b>Suggest compliance</b> to <b>Ignore
-compliance</b> since Apache Axis 1.0 does not lend itself to WS-I compliant
-Web services in general. Note that this prerequisite is not critical. If
-you leave the compliance level set to <b>Suggest compliance</b>, then the
-Web service wizards and the WSDL validator will simply produce warning
-messages telling you that your Web service will not be, or is not, WS-I
-compliant.</li>
-
-<br><img SRC="WebServicesToolsEval_files/imageDQC.JPG" NOSAVE height=433 width=634>
-<li>
-Click <b>OK</b>.</li>
-</ol>
-
-<h4>
-<a NAME="tour-bu-prereqweb"></a>3.2.3 Create a Web project</h4>
-
-<ol>
-<li>
-Open <b>File -> New -> Other... -> Web -> Dynamic Web Project</b> to create
-a new Web project named <tt>Converter</tt>.</li>
-
-<li>
-Enter <tt>Converter</tt> into the <b>Name</b> field.</li>
-
-<li>
-Choose a <b>Web version</b> of <b>2.3</b>.</li>
-
-<li>
-Choose a <b>Target server</b> of <b>Apache Tomcat v4.1</b>.</li>
-
-<li>
-Deselect <b>Add module to an EAR project</b>. Result:</li>
-
-<br><img SRC="WebServicesToolsEval_files/imageNQC.JPG" NOSAVE height=497 width=503>
-<li>
-Click <b>Finish</b>.</li>
-</ol>
-
-<h4>
-<a NAME="tour-bu-main"></a>3.2.4 Create a Web service and Web service client</h4>
-
-<ol>
-<li>
-Import the <a href="WebServicesToolsEval_files/wtp/Converter.java">wtp/Converter.java</a>
-class into Converter/JavaSource (be sure to preserve the package).</li>
-
-<li>
-Select the file.</li>
-
-<li>
-Open File -> New -> Other... -> Web Services -> Web Service.</li>
-
-<li>
-Select <b>Generate a proxy</b>.</li>
-
-<li>
-Select <b>Test the Web service</b>.</li>
-
-<li>
-Select <b>Overwrite files without warning</b>. Result:</li>
-
-<br><img SRC="WebServicesToolsEval_files/imageTEP.JPG" NOSAVE height=565 width=500>
-<li>
-Click <b>Finish</b>.</li>
-
-<li>
-It will take about one minute for the wizard to assemble the Web service
-and Web service client Web projects, start Apache Tomcat, and deploy the
-projects to Tomcat. Once finished, the generated Sample JSP Web application
-will appear in the browser view, maximized here for clarity:</li>
-
-<br><img SRC="WebServicesToolsEval_files/imageJN6.JPG" NOSAVE height=505 width=694>
-<li>
-Under <b>Methods</b>, click on <b>celsiusToFarenheit(float)</b>.</li>
-
-<li>
-Under <b>Inputs</b>, enter <tt>37</tt> into the <b>celsius</b> entry field.</li>
-
-<li>
-Click on <b>Invoke</b>. In the Result view, you should get a response of
-<b>98.6</b>.</li>
-
-<br><img SRC="WebServicesToolsEval_files/imageG73.JPG" NOSAVE height=505 width=694></ol>
-<b>Explanation</b>
-<p>The Web Service wizard is orchestrating the end-to-end generation, assembly,
-deployment, installation and execution of the Web service, Web service
-client, and sample JSPs. In this scenario we clicked Finish on page one.
-In effect, this is allowing the wizard to pick reasonable defaults according
-to the basic high-level choices made on the first page. If you repeat this
-scenario, but use the Next button to work thru the wizard, you will learn
-more about the kinds of choices that are available and the kinds of defaults
-being assumed.
-<p>Note that this evaluation guide does not include a Web Service Client
-wizard scenario. This is mainly because the above Web service creation
-scenario includes all the logical features and most of the visual features
-of the Web Service Client wizard. Also, note that the process of using
-the Web service creation wizard to create a Web service top-down is largely
-the same as for bottom-up. The only major difference is that the top-down
-scenario generates a skeletal Java class which you must implement in order
-to get any kind of useful response from the service.
-<p>After completing this scenario, the WSDL for the Converter Web service
-can be found in Converter/WebContent/wsdl/Converter.wsdl. Now that your
-Web service is running, there are a few interesting things you can do with
-this WSDL file. Examples:
-<ol>
-<li>
-You can double-click on the WSDL to open the WSDL graphical editor.</li>
-
-<li>
-You can right-click on the WSDL and choose <b>Web Services -> Test with
-Web Services Explorer</b> to test the service (as similar to <a href="#tour-wse">scenario
-3.1</a> above).</li>
-
-<li>
-You can right-click on the WSDL and choose <b>Web Services -> Publish WSDL
-file</b> to publish the service to a public UDDI registry.</li>
-
-<li>
-You can click on the WSDL and choose <b>File -> New -> Other... -> Web
-Services -> Web Service Client</b> to generate a Web service client. Note,
-however, that we have already witnessed the internal and visual features
-of the Web Service Client wizard since, in addition to being its own wizard,
-it is quite literally embedded within the larger Web Service wizard.</li>
-</ol>
-
-<h3>
-<a NAME="tour-prefs"></a>3.3 Exploring the Preferences</h3>
-This contribution includes a number of preference pages to help govern
-the default behaviour of the Web services tools in the Web Services Tools
-and <a href="XMLToolsEval.html">XML Tools</a> contributions.
-<p>The <b>Internet</b> preferences page found under <b>Window -> Preferences
--> Internet</b> lets you configure regular and basic-authenticating firewall
-proxies for any plugin in Eclipse that opens HTTP connections to the outside
-world. Because of the proliferation of WSDL documents, Schema, Web services,
-UDDI registries and similar resources on the internet, the Web services
-tools are frequently called upon to load resources from the internet. For
-users running on the protected side of a firewall, the Internet preferences
-page is essential. The settings made on this page apply to all plugins
-running in the Eclipse JRE, not just to the Web service plugins.
-<blockquote><img SRC="WebServicesToolsEval_files/imageV5J.JPG" NOSAVE height=454 width=684></blockquote>
-All the other preference pages reviewed below can be found under
-<b>Window
--> Preferences -> Web Services</b>.
-<p>The <b>Popup Dialog Selection</b> page lets you enable or disable the
-wizards associated with specific Web service popup actions. Most of the
-Web services popup (or context menu) actions are equipped with wizards
-which are visually enabled by default. Each of these wizards has a checkbox
-entitled "Do not show me this dialog box again." If you select this, then
-Finish the wizard, the next time you run the same popup action the wizard
-will be disabled, meaning the action will simply run with whatever default
-values are in effect. You can use the Popup Dialog Selection preferences
-page to re-enable the wizards for the various popup actions.
-<blockquote><img SRC="WebServicesToolsEval_files/imageS25.JPG" NOSAVE height=454 width=684></blockquote>
-The <b>Project Topology</b> page controls the default J2EE project layout
-built by the Web service wizards for your Web services and clients. Using
-this page, you can choose your favourite J2SE or J2EE project type for
-Web service clients, and you can control whether your service and client
-projects get assembled into the same EAR or into different EARs. Note:
-It is recommended that you choose different EARs for services and clients.
-Because of the symmetry of the package-to-namespace and namespace-to-package
-mappings when generating Web services and Web service clients, it is common
-for classes of identical qualified names to appear in the service and client
-projects. If both projects are assembled into the same EAR, J2EE classloaders
-can end up loading the wrong classes.
-<blockquote><img SRC="WebServicesToolsEval_files/imageOUN.JPG" NOSAVE height=454 width=684></blockquote>
-The <b>Resource Management</b> page specifies the file overwrite, folder
-creation, and file checkout policies for the wizards.
-<blockquote><img SRC="WebServicesToolsEval_files/image14L.JPG" NOSAVE height=454 width=684></blockquote>
-The <b>Scenario Defaults</b> page controls the default choices that appear
-on the first page of the Web Service and Web Service Client wizards.
-<blockquote><img SRC="WebServicesToolsEval_files/imageV0H.JPG" NOSAVE height=454 width=684></blockquote>
-The <b>Server and Runtime</b> page lets you choose your favourite server,
-Web service runtime and J2EE level.
-<blockquote><img SRC="WebServicesToolsEval_files/imageTKB.JPG" NOSAVE height=454 width=684></blockquote>
-The <b>Test Facility Defaults</b> page lets you customize the preferred
-order of the available Web service test facilities in the tools. In the
-WTP, there are two, and in this default order: 1. The Web service sample
-JSPs (seen in <a href="#tour-bu">scenario 3.2</a> above) and the Web Services
-Explorer (seen in <a href="#tour-wse">scenario 3.1</a> above). The wizards
-will choose the first test facility in the list that is compatible with
-the scenario. For example, if you run the Web Service wizard with <b>Generate
-a Proxy</b> deselected and <b>Test the Web service</b> selected on page
-one, then the wizard will launch the Web Services Explorer. Although the
-Sample JSP test facility appears first in the list, the wizard will not
-choose it since the Sample JSPs require a generated Java proxy.
-<blockquote><img SRC="WebServicesToolsEval_files/imageQMH.JPG" NOSAVE height=454 width=684></blockquote>
-The <b>Web Services Explorer</b> page includes a couple of preferences
-that control how the Explorer talks to UDDI registries and to Web services.
-In general you will not need to visit this page.
-<blockquote><img SRC="WebServicesToolsEval_files/imageJ5D.JPG" NOSAVE height=454 width=684></blockquote>
-The <b>WSDL Files</b> page lets you pick a default namespace for WSDL editing.
-<blockquote><img SRC="WebServicesToolsEval_files/imageAUK.JPG" NOSAVE height=454 width=684></blockquote>
-The <b>WS-I Compliance</b> page was visited in the prerequisites of <a href="#tour-bu-prereqwsi">scenario
-3.2</a> above. It controls the degree to which the tools expect adherence
-to various WS-I Profiles.
-<blockquote><img SRC="WebServicesToolsEval_files/imageMOB.JPG" NOSAVE height=454 width=684></blockquote>
-
-<h3>
-<a NAME="tour-wizards"></a>3.4 Exploring the Wizards</h3>
-In addition to the Web Service and Web Service Client wizards discussed
-above, there are a couple of other wizards in this contribution.
-<p>The <b>Import WSIL</b> wizard (<b>File -> Import... -> WSIL</b>) is
-used to create WS-Inspection documents in the workspace containing a list
-of one or more WSDL document URLs. The Web Services Explorer and some of
-the other wizards can also create WS-Inspection documents in the workspace.
-In all these cases, the purpose is to keep references to WSDL documents
-(via WSIL) in the workspace instead of copies of WSDL documents (which
-can become stale).
-<blockquote><img SRC="WebServicesToolsEval_files/imageNQD.JPG" NOSAVE height=550 width=470></blockquote>
-
-<p><br>The <b>Unit Test UDDI Registry Configuration</b> wizard (<b>File
--> New -> Other... -> Web Services -> Unit Test UDDI</b>) is the extension
-point for plugging in providers of UDDI registries. There are no UDDI registries
-included in the current WTP contribution, so the wizard will come up with
-no registries to choose from.
-<blockquote><img SRC="WebServicesToolsEval_files/image76L.JPG" NOSAVE height=500 width=500></blockquote>
-The <b>Web Service Import</b> wizard (<b>File -> Import... -> Web Service</b>)
-launches a wizard that helps you choose a UDDI Registry and then launches
-the Web Services Explorer so that you can begin searching for the Web service
-you are interested in.
-<blockquote><img SRC="WebServicesToolsEval_files/imageRMO.JPG" NOSAVE height=550 width=479></blockquote>
-The <b>Web Service Export</b> wizard (<b>File -> Export... -> Web Service</b>)
-launches a wizard similar to the aforementioned Web Service Import wizard
-that helps you choose a UDDI Registry and then launches the Web Services
-Explorer so that you can publish your Web service to the registry.
-<blockquote><img SRC="WebServicesToolsEval_files/imageI2V.JPG" NOSAVE height=550 width=493></blockquote>
-The <b>Configure Handlers</b> wizard is available from the context menu
-for certain WSDL documents and J2EE descriptors. It simplifies the process
-of developing and configuring JAX-RPC handlers into a JSR-109 compliant
-Web service or Web service client. Since Apache Axis is not a JSR-109 Web
-service runtime, the Configure Handlers wizard is of limited use unless
-a third party extends the WTP platform with a JSR-109 compliant Web service
-runtime.
-<blockquote><img SRC="WebServicesToolsEval_files/image5CS.JPG" NOSAVE height=682 width=438></blockquote>
-
-<h3>
-<a NAME="tour-popups"></a>3.5 Exploring the Popup Actions</h3>
-The Web Services Tools contribution includes a handful of popup actions
-available on key resources, including:
-<ul>
-<li>
-Projects.</li>
-
-<li>
-WSDL documents.</li>
-
-<li>
-WS-Inspection documents.</li>
-
-<li>
-Java classes.</li>
-
-<li>
-EJBs.</li>
-
-<li>
-J2EE deployment descriptors.</li>
-</ul>
-Popup actions available:
-<blockquote>
-<table BORDER BGCOLOR="#CCFFFF" >
-<tr>
-<td><b>Action</b></td>
-
-<td><b>Remarks</b></td>
-</tr>
-
-<tr>
-<td>Test with Web Services Explorer</td>
-
-<td>Launches the Web Services Explorer to invoke operations on a given
-WSDL document.</td>
-</tr>
-
-<tr>
-<td>Publish WSDL file</td>
-
-<td>Launches the Web Services Explorer to publish WSDL to a UDDI registry.</td>
-</tr>
-
-<tr>
-<td>Generate WSIL</td>
-
-<td>Launches a wizard that generates a WS-Inspection document from a given
-WSDL document.</td>
-</tr>
-
-<tr>
-<td>Generate Client</td>
-
-<td>Equivalent to File -> New -> Other... -> Web Services -> Web Service
-Client.</td>
-</tr>
-
-<tr>
-<td>Create Web service</td>
-
-<td>Equivalent to File -> New -> Other... -> Web Services -> Web Service
-for a bottom-up scenario.</td>
-</tr>
-
-<tr>
-<td>Generate Java bean skeleton</td>
-
-<td>Equivalent to File -> New -> Other... -> Web Services -> Web Service
-for a top-down scenario.</td>
-</tr>
-
-<tr>
-<td>Configure Handlers</td>
-
-<td>Launches the Configure Handlers wizard.</td>
-</tr>
-
-<tr>
-<td>Generate Sample JSPs</td>
-
-<td>Launches that subset of the Web Service Client wizard that generates
-Sample JSPs from a Java proxy.</td>
-</tr>
-</table>
-</blockquote>
-
-<h3>
-<a NAME="tour-frameworks"></a>3.6 Behind the Scenes</h3>
-There are several extension points and frameworks, and several examples
-of their use, incorporated into the Web services tools. This chapter provides
-a glimpse of the key extension points and a couple of significant frameworks.
-<h4>
-<a NAME="tour-frameworks-ep"></a>3.6.1 Extension Points</h4>
-
-<blockquote>
-<table BORDER BGCOLOR="#CCFFFF" >
-<tr>
-<td><b>Plugin</b></td>
-
-<td><b>Extension Point</b></td>
-
-<td><b>Remarks</b></td>
-</tr>
-
-<tr>
-<td>com.ibm.env</td>
-
-<td>DynamicWizard</td>
-
-<td>Used to define dynamic wizards and, optionally, couple them to newWizards,
-importWizards, exportWizards and popupMenus extensions.</td>
-</tr>
-
-<tr>
-<td>com.ibm.env</td>
-
-<td>actionDialogPreferenceType</td>
-
-<td>Used by dynamic wizards to enable or disable the "do not show me this
-dialog box again", and to control their appearance in the Popup Dialog
-Selection preference page.</td>
-</tr>
-
-<tr>
-<td>com.ibm.etools.webservice.consumption</td>
-
-<td>wsfinder</td>
-
-<td>Used to plug in objects that help to locate Web services in the workspace
-by looking for specific patterns (WSDL files, deployment descriptors, etc).
-Not yet used within WTP.</td>
-</tr>
-
-<tr>
-<td>com.ibm.etools.webservice.consumption</td>
-
-<td>WebServiceStartServerType</td>
-
-<td>Used to plug in objects that manage startup details specific to different
-kinds of servers. Though currently used within WTP, this extension point
-is likely to be removed.</td>
-</tr>
-
-<tr>
-<td>com.ibm.etools.webservice.consumption</td>
-
-<td>serverDefaulter</td>
-
-<td>Used to plug in algorithms to compute a reasonable runtime target for
-projects that do not have a runtime target.</td>
-</tr>
-
-<tr>
-<td>com.ibm.etools.webservice.consumption.ui</td>
-
-<td>objectSelectionWidget</td>
-
-<td>The second page of the Web service wizard is where the user selects
-the object from which they will build their Web service. Since the selection
-controls differ from object type to object type (eg. Java, EJB, WSDL...),
-the selection controls are contributed to the page via this extension point.
-Extensions for Java and EJB selection are included in the WTP.</td>
-</tr>
-
-<tr>
-<td>com.ibm.etools.webservice.consumption.ui</td>
-
-<td>publicUDDIRegistryType</td>
-
-<td>Used to declare known public (internet) UDDI registries to the wizards
-and the Web Services Explorer.</td>
-</tr>
-
-<tr>
-<td>com.ibm.etools.webservice.consumption.ui</td>
-
-<td>privateUDDIRegistryType</td>
-
-<td>The com.ibm.etools.webservice.uddi.registry plugin uses this extension
-point to contribute its private registry configuration page to the end
-of the Web service wizards. This extension point is likely to be removed,
-with the contents of the com.ibm.etools.webservice.uddi.registry plugin
-being pulled right into this plugin.</td>
-</tr>
-
-<tr>
-<td>com.ibm.etools.webservice.consumption.ui</td>
-
-<td>webServiceServerRuntimeType</td>
-
-<td>Used to extend the Web service (creation) wizard with pages and logic
-that handle the development, assembly, deployment and installation tasks
-for Web services of a specific Web service implementation type, using a
-specific Web service runtime, and for execution on a specific runtime target
-(server).</td>
-</tr>
-
-<tr>
-<td>com.ibm.etools.webservice.consumption.ui</td>
-
-<td>webServiceClientType</td>
-
-<td>Used to extend the Web service (creation) and Web service client wizards
-with pages and logic that handle the development, assembly, deployment
-and installation tasks for Web service clients of a specific Web service
-implementation type, using a specific Web service runtime, and for execution
-on a specific runtime target (server or client container).</td>
-</tr>
-
-<tr>
-<td>com.ibm.etools.webservice.consumption.ui</td>
-
-<td>webServiceTest</td>
-
-<td>Used to plug Web service test facilities into the Web service tools.</td>
-</tr>
-
-<tr>
-<td>com.ibm.etools.webservice.consumption.ui</td>
-
-<td>clientProjectType</td>
-
-<td>Used to plug in project types that can accept a JAX-RPC Web service
-client and that would appear in the Project Topology preference page.</td>
-</tr>
-
-<tr>
-<td>com.ibm.etools.webservice.explorer</td>
-
-<td>wsexplorerType</td>
-
-<td>Used to plug in alternative WSDL/UDDI exploration tools to the Web
-Services Explorer.</td>
-</tr>
-
-<tr>
-<td>com.ibm.etools.webservice.uddi.registry</td>
-
-<td>privateUDDIRegistryType</td>
-
-<td>Used by providers of specific private UDDI registries to add their
-registries to the private registry configuration page (which is in turn
-extended into the wizard using com.ibm.etools.webservice.consumption.ui's
-privateUDDIRegistryType extension point).</td>
-</tr>
-</table>
-</blockquote>
-There are also two frameworks that help address two key requirements of
-the Web services tools. One requirement is that all the work done by the
-Web services tools be accomplished, where possible, in a variety of user
-interface environments including, but not limited to, Eclipse. The other
-requirements is that the Web services wizards in Eclipse exhibit page sequences
-that are highly dynamic and extensible.
-<h4>
-<a NAME="tour-frameworks-ecf"></a>3.6.2 The Environment Command Framework</h4>
-The Environment Command Framework or <b>ECF</b> provides the means for
-encapsulating and coordinating the execution of the maximum amount of tools
-code in the form of reusable, stateful Command objects that are not tied
-to any particular user interface environment. The ECF defines Command
-Fragments as a means for organizing Commands into a tree that is progressively
-flattened and executed for a given scenario. The ECF manages the flow of
-state between Command objects, and manages the execution, undoing, and
-redoing of Commands. The ECF makes heavy use of URIs to manipulate resources
-regardless of their location in an Eclipse workspace, a filesystem, an
-HTTP server, or so forth. Examples of user interface environments are Eclipse
-SWT dialogs and wizards, Eclipse headless commands, Java command line tools,
-ANT tasks, JUnit testcases, Web services and batch processes.
-<p>The framework, as well as a command line implementation of it, can be
-found in <b>com.ibm.env.core</b>. An Eclipse implementation of the framework
-can be found in <b>com.ibm.env</b>.
-<h4>
-<a NAME="tour-frameworks-dwf"></a>3.6.3 The Dynamic Wizard Framework</h4>
-The Dynamic Wizard Framework or <b>DWF</b> provides for the assembly of
-highly dynamic and extensible wizards. It also provides boilerplate extensions
-to the Eclipse newWizards, importWizards, exportWizards and popupMenus
-extension points to permit DWF wizards to be plugged into these Eclipse
-extension points with no adapter code and only a small amount of extension
-XML. The sequence of pages in a DWF wizard is not fixed. Rather, the determination
-of the next page is made on demand based upon up-to-the-minute state
-and/or known extensions to DWF extension points. The DWF provides for the
-abstract binding of (non-visual) ECF Command objects and Command state
-data to (visual) SWT Widgets and Widget state. In this manner, a DWF wizard
-becomes an overlay over a Command Fragment tree.
-<p>The framework can be found in <b>com.ibm.env</b>.
-<h2>
-<a NAME="feedback"></a>4.0 Provide Feedback to Us</h2>
-<P>We encourage development/design feed back on the <A
- href="https://dev.eclipse.org/mailman/listinfo/wtp-dev">wtp-dev</A> mailing list. You can subscribe to the list via <A
- href="https://dev.eclipse.org/mailman/listinfo/wtp-dev">this link</A>.<BR>
-<BR>
-For usage questions, discussion of bugs, and strange behaviour please post to the eclipse.webtools newsgroup. Information on the Web Tools Platform newsgroup can be found <A
- href="http://www.eclipse.org/newsgroups/index.html">here</A>.</P>
-</body>
-</html>
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/image0BJ.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/image0BJ.JPG
deleted file mode 100644
index 8bfc825..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/image0BJ.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/image14L.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/image14L.JPG
deleted file mode 100644
index 0a539d5..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/image14L.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/image3D9.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/image3D9.JPG
deleted file mode 100644
index d479f57..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/image3D9.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/image5CS.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/image5CS.JPG
deleted file mode 100644
index 4fb3eb7..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/image5CS.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/image76L.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/image76L.JPG
deleted file mode 100644
index 72d2fb6..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/image76L.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/image7DI.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/image7DI.JPG
deleted file mode 100644
index 3bfd6f9..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/image7DI.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/image849.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/image849.JPG
deleted file mode 100644
index 4ad1005..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/image849.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/image9TE.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/image9TE.JPG
deleted file mode 100644
index c0a4b11..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/image9TE.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageAUK.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageAUK.JPG
deleted file mode 100644
index ca338a7..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageAUK.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageD3M.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageD3M.JPG
deleted file mode 100644
index 1bb86cc..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageD3M.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageDQC.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageDQC.JPG
deleted file mode 100644
index 157809c..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageDQC.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageG73.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageG73.JPG
deleted file mode 100644
index c46a0cd..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageG73.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageI2V.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageI2V.JPG
deleted file mode 100644
index 2590618..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageI2V.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageJ5D.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageJ5D.JPG
deleted file mode 100644
index be9bd64..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageJ5D.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageJN6.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageJN6.JPG
deleted file mode 100644
index af7b417..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageJN6.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageMOB.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageMOB.JPG
deleted file mode 100644
index 4bf1b9a..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageMOB.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageN5S.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageN5S.JPG
deleted file mode 100644
index a0adf78..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageN5S.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageNQC.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageNQC.JPG
deleted file mode 100644
index 90e5c52..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageNQC.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageNQD.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageNQD.JPG
deleted file mode 100644
index c7374f1..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageNQD.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageOJG.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageOJG.JPG
deleted file mode 100644
index 12f2d8c..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageOJG.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageOUN.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageOUN.JPG
deleted file mode 100644
index 2a45c0b..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageOUN.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imagePK7.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imagePK7.JPG
deleted file mode 100644
index 1859cb7..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imagePK7.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageQMH.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageQMH.JPG
deleted file mode 100644
index 407bc31..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageQMH.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageRMO.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageRMO.JPG
deleted file mode 100644
index 81019dd..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageRMO.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageS25.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageS25.JPG
deleted file mode 100644
index 68e24af..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageS25.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageTEP.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageTEP.JPG
deleted file mode 100644
index 97f9c9b..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageTEP.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageTKB.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageTKB.JPG
deleted file mode 100644
index bc0dff8..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageTKB.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageTVQ.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageTVQ.JPG
deleted file mode 100644
index 8e54e9d..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageTVQ.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageV0H.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageV0H.JPG
deleted file mode 100644
index 08f9310..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageV0H.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageV5J.JPG b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageV5J.JPG
deleted file mode 100644
index d479f57..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/imageV5J.JPG
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/wsdl.gif b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/wsdl.gif
deleted file mode 100644
index de3b52a..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/wsdl.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/wsdl_main.gif b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/wsdl_main.gif
deleted file mode 100644
index 9f074e8..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/wsdl_main.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/wtp/Converter.java b/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/wtp/Converter.java
deleted file mode 100644
index 3902400..0000000
--- a/initial-contribution/IBM/evalGuides/WebServicesToolsEval_files/wtp/Converter.java
+++ /dev/null
@@ -1,14 +0,0 @@
-package wtp;
-
-public class Converter
-{
- public float celsiusToFarenheit ( float celsius )
- {
- return (celsius * 9 / 5) + 32;
- }
-
- public float farenheitToCelsius ( float farenheit )
- {
- return (farenheit - 32) * 5 / 9;
- }
-}
diff --git a/initial-contribution/IBM/evalGuides/XMLToolsEval.html b/initial-contribution/IBM/evalGuides/XMLToolsEval.html
deleted file mode 100644
index bb0263c..0000000
--- a/initial-contribution/IBM/evalGuides/XMLToolsEval.html
+++ /dev/null
@@ -1,187 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=Cp1252">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link href="../theme/Master.css" rel="stylesheet" type="text/css">
-<title>Getting Started.html</title>
-</head>
-<body>
-<H1>XML Tools Evaluation Guide</H1>
-<H2>1.0 Introduction</H2>
-<P>The XML Tools contribution consists of the following components</P>
-<UL>
- <LI><A href="#3.1">XML example wizards</A></LI>
- <LI><A href="#3.2">XML Schema editor</A></LI>
- <LI><A href="#3.3">WSDL editor and 'New WSDL' wizard'</A></LI>
- <LI><A href="#3.4">Validators for various XML artifacts</A>
- <UL>
- <LI>XML</LI>
- <LI>XML Schema</LI>
- <LI>DTD</LI>
- <LI>WSDL with optional WS-I validation*</LI>
- </UL>
- <LI><A href="#3.5">New XML wizard and XML generators </A></LI>
- <LI><A href="#3.6">XML catalog support</A></LI>
-</UL>
-<P>* These components are pulled in from the eclipse WSVT project</P>
-<H2>2.0 Getting Started</H2>
-<P>The easiest way to get started using the XML tools is to use the New Example wizard to create the example 'Editing and Validating XML files' project. This wizard will create a 'simple' project and populate it with some XML artifacts that you can use to experiment with the editors and validators. See section 3.1 for more details. Although the XML tools are designed to work in various perspectives, we'll choose to use the resource perspective to explore the tools.<H2>3.0 Quick Tour</H2><H3><A
- name="3.1">3.1 XML example wizards</A></H3>
-<P>The XML Example wizard is a very simple component that provides a sample project that is pre-populated with some example files. From the main menu select File->New -> Example to invoke the dialog shown below. Currently there is only one example project named 'Editing and validating XML files'. This sample project is a handy way to populate your workspace with some XML files so that you can try out the XML Tools.<BR>
-<IMG border="0" src="XMLToolsEval_files/New_Example.gif" width="501"
- height="429">
-</P>
-<H3><A name="3.2">3.2 XML Schema editor</A></H3>
-<P>Under the PurchaseOrder folder, locate the PurchaseOrder.xsd file and double click the file to open it in the XML Schema Editor. As shown below, an Outline and Properties view is provided in addition to the editor pane. At the bottom of the editor area you'll see that there is a 'Source' and a 'Graph' tab at the bottom of the editor area. The 'Source' tab is used for basic XML source editing. The 'Graph' tab is used for higher level graphical editing. Select the 'Graph' tab so that you're looking at the Graph view. As shown below you should see a 'top level' view of the XML Schema that summarizes all of the components (e.g. elements and types) that are defined in the schema.<BR>
-<IMG border="0" src="XMLToolsEval_files/XSD_Editor_top_level_view.gif"
- width="867" height="718">
-</P>
-<P>In order to see these components in detail you can 'drill down' on a component of interest by double clicking on it. For example, if we double click on the 'purchaseOrder' component, the editor will display the structure of the 'purchaseOrder' element as shown below. Notice that the +/- controls can be used to navigate into an element's containment structure. To return to the 'top level' view, press the back button <IMG
- border="0" src="XMLToolsEval_files/XSD_Editor_back.gif" width="26"
- height="21"> at the top left of the editor, or right clicking within the editor and selecting 'Back to Schema' from the context menu.<BR>
-</P>
-<P><IMG border="0" src="XMLToolsEval_files/XSD_Editor_purchaseOrder.gif"
- width="587" height="475"></P><P>Editing the schema is acheived by invoking context menu actions on selected objects in the Graph view and using the properties view to modify the properties of the selected object. Follow the steps below to create a new element declaration and define its content.</P>
-<OL>
- <LI>right click within the 'Elements' section of the top level schema and choose 'Add Global Element'</LI>
- <LI>use the properties view to change the name of the element to 'purchaseOrderList'
-<IMG border="0" src="XMLToolsEval_files/XSD_Editor_properties.gif"
- width="516" height="178">
- </LI>
- <LI>right click within the 'Elements' section of the top level schema and choose 'Add Global Element'</LI>
- <LI>use the properties view to change the name of the element to 'purchaseOrderList'</LI>
- <LI>now double click on the element in the editor to drill down on the element so that we can edit its structure</LI>
- <LI>right click on the purchaseOrderList and select 'Add Sequence' to specify that the element will contain a sequence of child elements.<BR>
- <IMG
- border="0" src="XMLToolsEval_files/XSDEditor_purchaseOrderList.gif"
- width="377" height="136" align="top"> <BR>
- </LI>
- <LI>right click on the sequence to specify a child element, in this case we want to reference an existing element so we'll add an element reference as shown below.<BR>
- <IMG
- border="0" src="XMLToolsEval_files/XSDEditor_addElementRef.gif"
- width="384" height="179" align="top"><BR>
- </LI>
- <LI>Notice that editor automatically selected the 'PurchaseOrderElement' (as shown below). Luckily this happens to be the element we'd like to reference. If we wanted to specify a different element we could click on the label to invoke a combo box to select an alternative element. In the properties view modify the element reference's minOccurs and maxOccurs to be 0 and undbounded respectively. This specifies that the purchaseOrderList element will contain zero or more purchaseOrder elements.<IMG
- border="0" src="XMLToolsEval_files/XSDSchema_minmax.gif" width="441"
- height="119"><br/></LI>
- <LI>Right click again on the sequence node and add an element. Rename NewElement to retailerInfo. Now in the properties view, switch to the 'Attributes' tab so that we can define some attributes for the retailerInfo element. Right click in the empty box on the left to add attribute use the table on the right to name the attribute 'retailerName' with a type of 'string'. Add another attribute and give it the name 'dateSubmitted' and give it the type 'date'. Your editor should appear as shown below. <BR><IMG
- border="0" src="XMLToolsEval_files/XSDEditor_attributes.gif"
- width="755" height="498"><br/></LI>
- <LI>Now that we've finished editing the XML Schema you can save the file. If you'd like to validate the schema or create an XML instance from the schema continue to sections 3.4 and 3.5 for more details.</LI>
-</OL>
-<H3><A name="3.3">3.3 WSDL Editor and 'New WSDL' wizard</A></H3>
-<P>In this section we will explore the new WSDL wizard and WSDL Editor by creating a completely new WSDL file. The WSDL file we will be creating is
-TemperatureService.wsdl. We will go through adding Operations, deleting Operations, generating our binding, and simple editing using the editor.
-</P>
-
-1. New WSDL Wizard
- <UL>
- <LI>From the main menu, select File->New->XML->WSDL to launch the New WSDL Wizard.</LI>
- <LI>Select a project and enter the filename "TemperatureService.wsdl". Click Next.</LI>
- <LI>In the next dialog, there is a "Create WSDL Skeleton" checkbox. This option is used to create a skeleton (sample) WSDL file. This allows
-the user the ability to quickly modify and edit this skeleton for their own purposes. Select this checkbox and the SOAP rpc encoded option and
-click Finish.
-<BR><IMG border="0" src="XMLToolsEval_files/WSDLEditor_NewWSDLWizard.jpg" align="top"><BR><BR></LI>
- </UL>
-
-2. Exploring and editing the newly created WSDL file
- <UL>
- <LI>The newly created WSDL file will open in the editor. Explore the WSDL using the Graph view ("Graph" tab), Source view ("Source" tab), outline
-view, and the properties view.</LI>
- <LI>In the Graph View, rename the Port under the "TemperatureService" Service to "GetTemperatureInfoSOAP".</LI>
- <LI>Rename the Port Type to "GetTemperatureInfoSOAP".</LI>
- <LI>Rename the Operation to "GetTemperatureForZipCode". The rename will rename the Operation and it's associated elements. For example, it will rename the
-Operation, Messages, Parts, and Elements.The rename will only rename associated elements if the name of the element is a generated name. For instance, if the
-Message "NewOperationRequest" was renamed to "NewMessageName" before the Operation rename was done, the Message will not be renamed.</LI>
- <LI>Rename the Message "GetTemperatureForZipCodeRequest" to "GetTemperatureInput". Notice the Part is also renamed because the Part is a generated name.</LI>
- <LI>Rename the Part "GetTemperatureInput" to "ZipCode".</LI>
- <LI>Rename the Part "GetTemperatureForZipCodeResponse" to "Temperature".</LI>
- <LI>Rename the Message "GetTemperatureForZipCodeResponse" to "GetTemperatureOutput". Notice the Part is not renamed.</LI>
- <LI>Select the Part "Temperature" and change the type to "xsd:float" using the properties view.<BR><BR></LI>
- </UL>
-
-3. Adding a new Operation
- <UL>
- <LI>Right click on the PortType "GetTemperatureInfoSOAP" and select "Add Operation". The Add Operation Dialog will appear with a "Create default messages"
-checkbox. Selecting this checkbox will create two default Messages. One for Input and one for Output. If this checkbox is not selected, only an
-Input and Output will be created.</LI>
- <LI>Create the Operation with this option selected and the filename "GetTemperatureForDate".
-<BR><IMG border="0" src="XMLToolsEval_files/WSDLEditor_AddOperationDialog.jpg" align="top"></LI>
- <LI>Rename the Message "GetTemperatureForDateRequest" to "GetTemperatureForDateInput".</LI>
- <LI>Rename the Part "GetTemperatureforDateInput" to "Date".</LI>
- <LI>Rename the Message "GetTemperatureForDateResponse to "GetTemperatureForDateOutput".</LI>
- <LI>Rename the Part "GetTemperatureForDateOutput" to "Temperature".</LI>
- <LI>Select the Part "Date" and change the type to "xsd:date" using the properties view.</LI>
- <LI>Select the Part "Temperature" and change the type from "xsd:string" to "xsd:float" by right-clicking on the Part and selecting "Set Type..."<BR><BR></LI>
- </UL>
-
-4. Adding an Operation by copying an existing Operation
- <UL>
- <LI>Copy the "Operation by right-clicking on the Operation "GetTemperatureForZipCode" and select "Copy".</LI>
- <LI>Right-click on the Operation again and select "Paste".</LI>
- <LI>A copy of "GetTemperatureForZipCode" is created with the name "GetTemperatureForZipCode1". Notice the Input, Output, Messages, and Parts are also copied.</LI>
- <LI>Rename the Operation "GetTemperatureForZipCode1" to "GetTemperatureForCity".</LI>
- <LI>Rename the Message "GetTemperatureInput1" to "GetTemperatureForCityInput"</LI>
- <LI>Rename the Part "ZipCode" to "City".</LI>
- <LI>Select the Part "City" and change the type to "xsd:string".</LI>
- <LI>Rename the Message "GetTemperatureForCityResponse" to "GetTemperatureForCityOutput".<BR><BR></LI>
- </UL>
-
-5. Editing an 'embedded' schema
- <UL>
- <LI>Select the Part "City" and in the properties view, change the "Reference Kind" to "element".</LI>
- <LI>In the Graph view, select the Part "City", do a right-click, and select "Set Element...". A dialog will appear with an option
-to create a new element. Select this option and use the element name "City". Click "Finish"</LI>
- <LI>In the top right of the Graph View, the newly created type will appear (currently there is a small bug. Only the arrow and the schema icon
-appears at this point. However, the targetnamespace should also appear). Double clicking on the arrow will open the 'embedded' schema editor. From here,
-the user can edit as if it were the XML Schema editor.
-<BR><IMG border="0" src="XMLToolsEval_files/WSDLEditor_EmbeddedSchemaEditor.jpg" align="top"></LI>
- <LI>Click on the "Back to Previous view" button located on the top left corner of the editor to move back to the WSDL view.<BR><BR></LI>
- </UL>
-
-6. Deleting an Operation
- <UL>
- <LI>Right-click on the Operation "GetTemperatureForCity" and select "Delete".</LI>
- <LI>A dialog will appear with a "Delete associated Messages and Parts". Having this checkbox selected will delete the Operation's associated
-Messages and Parts only if the Messages are not referenced by other Operations.</LI>
- <LI>Select this option and Click "Ok".
-<BR><IMG border="0" src="XMLToolsEval_files/WSDLEditor_DeleteOperationDialog.jpg" align="top"><BR><BR></LI>
- </UL>
-
-7. Regenerate Binding
- <UL>
- <LI>Right-click on the Binding "NewWSDLFileSOAP" and select "Generate Binding Content...".</LI>
- <LI>Select the "Overwrite existing binding information" and click "Finish". Notice there is now a Binding Operation for each Operation.
-<BR><IMG border="0" src="XMLToolsEval_files/WSDLEditor_GenerateBindingDialog.jpg" align="top"><BR><BR></LI>
- </UL>
-
-8. Now that we've finished editing the WSDL you can save the file. If you'd like to validate the WSDL continue to section 3.4
-
-<H3><A name="3.4">3.4 Validators for XML artifacts</A></H3>
-<P>There are several ways to inoke the validators. The most direct way is to right click on a file (for example purchaseOrder.xsd) and select 'Validate XML Schema' from the context menu. A dialog message will pop up to inform you if the file is valid or not. If the file is invalid errors will be shown in the Problems view. Using the project's preferences, you can also configure the validators to be invoked automatically when a resource is saved. With this setting enabled the validator is automatically invoked and the Problems view is updated when a file is saved. In order to validate an entire project right click on the project and select 'Run Validation'.</P>
-<H3><A name="3.5">3.5 New XML wizard and XML generators</A></H3>
-<P>The capability to create an XML instance from a DTD or XML Schema is provided via a 'Generate->XML' menu option and via a 'New XML File' Wizard. Follow the steps below to generate an XML file from an XML Schema. The 'New Wizard' dialog works bery much the same but is invoked from the File->New->Other menu action.<BR>
-</P>
-<OL>
- <LI>In the naviagor view, select the file PurchaseOrder.xsd under the PurchaseOrder directory</LI>
- <LI>Right click on the file and select 'Generate -> XML File...'</LI>
- <LI>Accept the default name PurchaseOrder1.xml, press Next</LI>
- <LI>In the 'Root Element' combo select the 'PurchaseOrder' (or 'PurchaseOrderList' element if you've completed section 3.2). </LI>
- <LI>Check the the 'Create Optional elements' box, press Finish</LI>
- <LI>The XML file will now open up in the XML Editor. Notice that the file's content has been generated according to the structure defined in the XML Schema.</LI>
-</OL>
-<H3><A name="3.6">3.6 XML catalog</A> support</H3>
-<P>The XML Catalog provides a way to redirect references to XML artifacts (specified by URI locations and namespace names) to an alternate location. Typically this mechanism is used to redirect remote refereces to resources out on the web to a local copy. The user can manually edit the XML Catalog entries via the preferences page (select Window->Preferences->Web and XML->XML Catalog. By pressing the 'New..' button the user can populat the 'User Specified Entries' section of the catalog with a new catalog entry. </P><H3><IMG
- border="0" src="XMLToolsEval_files/XMLCatalog.gif" width="503"
- height="358"></H3>
-<P>You'll notice that the 'Plugin Specified Entries' section of the catalog contains a lot of entries. These entries are contributed by serverl plugins via extension point defined in plugin.xml files. Generally if a plugins requires access to an XML resources that is officially available on the web it will ship a local copy of that XML resource and contribute a catalog entry to redirect remote references to the local copy.</P>
-<H2>4.0 Provide Feedback to Us</H2>
-<P>We encourage development/design feed back on the <A
- href="https://dev.eclipse.org/mailman/listinfo/wtp-dev">wtp-dev</A> mailing list. You can subscribe to the list via <A
- href="https://dev.eclipse.org/mailman/listinfo/wtp-dev">this link</A>.<BR>
-<BR>
-For usage questions, discussion of bugs, and strange behaviour please post to the eclipse.webtools newsgroup. Information on the Web Tools Platform newsgroup can be found <A
- href="http://www.eclipse.org/newsgroups/index.html">here</A>.</P>
-</P>
-</body>
-</html>
diff --git a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/New_Example.gif b/initial-contribution/IBM/evalGuides/XMLToolsEval_files/New_Example.gif
deleted file mode 100644
index 7c8a076..0000000
--- a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/New_Example.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/WSDLEditor_AddOperationDialog.jpg b/initial-contribution/IBM/evalGuides/XMLToolsEval_files/WSDLEditor_AddOperationDialog.jpg
deleted file mode 100644
index 2c8d1af..0000000
--- a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/WSDLEditor_AddOperationDialog.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/WSDLEditor_DeleteOperationDialog.jpg b/initial-contribution/IBM/evalGuides/XMLToolsEval_files/WSDLEditor_DeleteOperationDialog.jpg
deleted file mode 100644
index d02f6b9..0000000
--- a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/WSDLEditor_DeleteOperationDialog.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/WSDLEditor_EmbeddedSchemaEditor.jpg b/initial-contribution/IBM/evalGuides/XMLToolsEval_files/WSDLEditor_EmbeddedSchemaEditor.jpg
deleted file mode 100644
index 67354cd..0000000
--- a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/WSDLEditor_EmbeddedSchemaEditor.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/WSDLEditor_GenerateBindingDialog.jpg b/initial-contribution/IBM/evalGuides/XMLToolsEval_files/WSDLEditor_GenerateBindingDialog.jpg
deleted file mode 100644
index 26d93f2..0000000
--- a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/WSDLEditor_GenerateBindingDialog.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/WSDLEditor_NewWSDLWizard.jpg b/initial-contribution/IBM/evalGuides/XMLToolsEval_files/WSDLEditor_NewWSDLWizard.jpg
deleted file mode 100644
index 3f4f60e..0000000
--- a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/WSDLEditor_NewWSDLWizard.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/WSDLEditor_RenameOperationResult.jpg b/initial-contribution/IBM/evalGuides/XMLToolsEval_files/WSDLEditor_RenameOperationResult.jpg
deleted file mode 100644
index 22874f4..0000000
--- a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/WSDLEditor_RenameOperationResult.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XMLCatalog.gif b/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XMLCatalog.gif
deleted file mode 100644
index 869d25a..0000000
--- a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XMLCatalog.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XSDEditor_addElementRef.gif b/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XSDEditor_addElementRef.gif
deleted file mode 100644
index c9b9b2b..0000000
--- a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XSDEditor_addElementRef.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XSDEditor_attributes.gif b/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XSDEditor_attributes.gif
deleted file mode 100644
index 132fb36..0000000
--- a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XSDEditor_attributes.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XSDEditor_purchaseOrderList.gif b/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XSDEditor_purchaseOrderList.gif
deleted file mode 100644
index b528096..0000000
--- a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XSDEditor_purchaseOrderList.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XSDSchema_minmax.gif b/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XSDSchema_minmax.gif
deleted file mode 100644
index aa657be..0000000
--- a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XSDSchema_minmax.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XSD_Editor_back.gif b/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XSD_Editor_back.gif
deleted file mode 100644
index c4e2191..0000000
--- a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XSD_Editor_back.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XSD_Editor_properties.gif b/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XSD_Editor_properties.gif
deleted file mode 100644
index f0b0cbd..0000000
--- a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XSD_Editor_properties.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XSD_Editor_purchaseOrder.gif b/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XSD_Editor_purchaseOrder.gif
deleted file mode 100644
index 530fb9e..0000000
--- a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XSD_Editor_purchaseOrder.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XSD_Editor_top_level_view.gif b/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XSD_Editor_top_level_view.gif
deleted file mode 100644
index 1beb7de..0000000
--- a/initial-contribution/IBM/evalGuides/XMLToolsEval_files/XSD_Editor_top_level_view.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/IBM/theme/Master.css b/initial-contribution/IBM/theme/Master.css
deleted file mode 100644
index ea1c4eb..0000000
--- a/initial-contribution/IBM/theme/Master.css
+++ /dev/null
@@ -1,45 +0,0 @@
-P {
- FONT-SIZE: 10pt; FONT-FAMILY: arial, helvetica, geneva
-}
-TABLE {
- FONT-SIZE: 10pt; FONT-FAMILY: arial, helvetica, geneva
-}
-TD {
- FONT-SIZE: 10pt; FONT-FAMILY: arial, helvetica, geneva
-}
-TH {
- FONT-SIZE: 10pt; FONT-FAMILY: arial, helvetica, geneva
-}
-PRE {
- FONT-SIZE: 10pt; FONT-FAMILY: "Courier New", Courier, mono
-}
-H2 {
- FONT-WEIGHT: bold; FONT-SIZE: 18pt; LINE-HEIGHT: 14px; FONT-FAMILY: arial, helvetica, geneva
-}
-CODE {
- FONT-SIZE: 10pt; FONT-FAMILY: "Courier New", Courier, mono
-}
-SUP {
- FONT-SIZE: 10px; FONT-FAMILY: arial,helvetica,geneva
-}
-H3 {
- FONT-WEIGHT: bold; FONT-SIZE: 14pt; FONT-FAMILY: arial, helvetica, geneva
-}
-LI {
- FONT-SIZE: 10pt; FONT-FAMILY: arial, helvetica, geneva
-}
-H1 {
- FONT-WEIGHT: bold; FONT-SIZE: 28px; FONT-FAMILY: arial, helvetica, geneva
-}
-BODY {
- MARGIN-TOP: 5mm; FONT-SIZE: 10pt; MARGIN-LEFT: 3mm; FONT-FAMILY: arial, helvetica, geneva
-}
-.indextop {
- FONT-WEIGHT: bold; FONT-SIZE: x-large; FONT-FAMILY: Verdana, Arial, Helvetica, sans-serif
-}
-.indexsub {
- FONT-SIZE: xx-small; COLOR: #8080ff; FONT-FAMILY: Arial, Helvetica, sans-serif
-}
-.section {
- PADDING-RIGHT: 1px; PADDING-LEFT: 1px; FONT-WEIGHT: bold; FONT-SIZE: 11pt; PADDING-BOTTOM: 1px; WIDTH: 100%; COLOR: white; PADDING-TOP: 1px; FONT-FAMILY: Arial, Helvetica; BACKGROUND-COLOR: #0099CC
-}
diff --git a/initial-contribution/OBJECTWEB/Getting Started.html b/initial-contribution/OBJECTWEB/Getting Started.html
deleted file mode 100644
index 7e248c7..0000000
--- a/initial-contribution/OBJECTWEB/Getting Started.html
+++ /dev/null
@@ -1,102 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=Cp1252">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link href="theme/Master.css" rel="stylesheet" type="text/css">
-<title>Getting Started.html</title>
-</head>
-<body>
-<H1>Eclipse Web Tooling Platform Contribution - LOMBOZ</H1>
-<p>
-<strong>NOTE:
-This initial contribution has been removed since it is out of date and no longer needed.
-Please obtain WTP builds from the project <a href="http://download.eclipse.org/webtools/downloads/">download</a> page.
-Although the following guide is obsolete, you may still find it of use in evaluating the WTP builds.
-This guide will eventually be superceded by WTP tutorials.
-</strong>
-</p>
-<H2>1.0 Introduction</H2>
-<P>Welcome to Eteration's contribution to the Eclipse Web Tooling Platform
-(WTP), ObjectWeb Lomboz. The purpose of this document is to guide you through
- initial
-setup of the code including any prerequisites and a high level tour
-through each of the components which are being contributed for
-evaluation. Before starting, please take note of <A
- href="#TermsAndConditions">Section 5, The Terms and Conditions</A> of this contribution.
-
-<a href="http://www.eteration.com" target="lomboz" >Eteration</a> is a member of the <a href="http://www.objectweb.org" target="lomboz" >ObjectWeb</a> consortium, and <a href="http://lomboz.objectweb.org" target="lomboz" >Lomboz</a> is an open source
-project hosted by ObjectWeb.</P>
-<H2>2.0 Getting Started</H2>
-<p>Here are the prerequisites you need to download and extract to your system:
-<ul>
-<li><a href='http://download.eclipse.org/downloads/drops/R-3.0-200406251208/eclipse-SDK-3.0-win32.zip'>Eclipse Release 3.0 SDK</a>
-<li><a href='http://download.eclipse.org/tools/emf/downloads/drops/2.0/R200406280827/emf-sdo-runtime-2.0.0.zip'>EMF,
- SDO 2.0.0 Runtime</a>
-
-<li><a href='http://java.sun.com/j2se/1.4.2/download.html'>Sun
- 1.4.2 JSDK</a>
-</ul>
-<P>Once you've unzipped/installed all of the above, download the
-<a href="http://download.eclipse.org/webtools/downloads/initial-contributions/objectweb.zip">
-objectweb.zip</a> and
- extract it. Unzip this SDK into the same location as the above SDKs. The zip
-extracts with 'eclipse' as the root directory.</P>
-<P>Follow the <a href="setup/setup.html">setup instructions</a> to complete the installation.</P>
-<H2>3.0 Lomboz Tutorial</H2>
-<P>Once the installation is complete. Walk
-through the lomboz <a href="http://www.objectlearn.com/support/docs/index.jsp" target="lomboz" >evaluation tutorial</a> for the components that you're interested
-in. Don't forget to provide feedback to us as described in <A
- href="#Feedback">Section 4.0</A>.</P>
-
-<P> </P>
-<H2><A name="Feedback">4.0 Provide Feedback to Us</A></H2>
-
-<p>We encourage development/design feed back on the <a
- href="https://dev.eclipse.org/mailman/listinfo/wtp-dev">wtp-dev</a>
-mailing list. You can subscribe to the list via <a
- href="https://dev.eclipse.org/mailman/listinfo/wtp-dev">this link</a>.<br>
-
-<br>
-For usage questions, discussion of bugs, and strange behaviour please
-post to the eclipse.webtools newsgroup. Information on the Web Tools
-Platform newsgroup can be found <a
- href="http://www.eclipse.org/newsgroups/index.html">here</a>.</p>
-
-<H2><A name="TermsAndConditions">5.0 Terms and Conditions</A></H2>
-<H3>5.1 Licensing</H3>
-<P>Eteration's Eclipse WTP Contribution Lomboz (the Content) is distributed under
- the <A
- href="http://www.eclipse.org/legal/epl-v10.html">EPL</A> and <A
- href="http://www.eclipse.org/legal/cpl-v10.html">CPL</A>. This applies to all
- files distributed under this contribution. All intellectual property remains
- under the ownership of Eteration A.S. and others
- as indicated
- in the
- contents
-of the with respective files where it applies.</P>
-
-<P>The Content includes items that
- have been sourced from
- third parties as follows: JSP Parser is based on software developed by The
- Apache Software Foundation as part of the Jakarta project. The content in the
- com.objectlearn.jasper package and com\objectlearn\jdt\j2ee\ui\editor\partitioner\JspNonXmlParser.java
- is based on code in the org/apache/jasper/compiler package of Tomcat and is
- therefore
- Copyright (c) 1999 The Apache Software Foundation. All rights reserved. Your
- use of JSP Parser is subject to the terms and conditions of the <a href="http://jakarta.apache.org/ant/manual/LICENSE">Apache
- Software License 1.1.</a> The content includes the following software in binary
- format included as is. These software can be downloaded from their own
- sites and subject
- to their licensing terms. From the Apache Software Foundation as part of the
- Jakarta project: <a href="http://jakarta.apache.org/commons/index.html">Commons
- Libraries</a>,
- <a href="http://ws.apache.org/axis/index.html">Axis</a>, <a href="http://logging.apache.org/log4j/docs/">Log4j</a> Your
- use of these software is subject to the terms and conditions of the <a href="http://jakarta.apache.org/ant/manual/LICENSE">Apache
- Software License 1.1.</a> And from sourceforge: <a href="http://sourceforge.net/projects/xdoclet">XDoclet</a>.
- Your use of xdoclet is subject to the terms and conditions of the <a href="http://www.opensource.org/licenses/bsd-license.php">BSD</a> license.</P>
-
-<H3>5.1 Disclaimers</H3>
-<P>The Content is provided as is for <B>evaluation purposes only</B>. The Content can and will most likely change before appearing in the Eclipse CVS repository. The APIs and packages will be reworked once the contribution is accepted. The code has not been extensively tested and should be considered a snapshot in time of ongoing development.</P>
-</P>
-</body>
-</html>
\ No newline at end of file
diff --git a/initial-contribution/OBJECTWEB/setup/customize.jpg b/initial-contribution/OBJECTWEB/setup/customize.jpg
deleted file mode 100644
index 968a904..0000000
--- a/initial-contribution/OBJECTWEB/setup/customize.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/OBJECTWEB/setup/plugins.gif b/initial-contribution/OBJECTWEB/setup/plugins.gif
deleted file mode 100644
index 000dcaa..0000000
--- a/initial-contribution/OBJECTWEB/setup/plugins.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/OBJECTWEB/setup/prefs1.jpg b/initial-contribution/OBJECTWEB/setup/prefs1.jpg
deleted file mode 100644
index 04fecb9..0000000
--- a/initial-contribution/OBJECTWEB/setup/prefs1.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/OBJECTWEB/setup/prefs2.jpg b/initial-contribution/OBJECTWEB/setup/prefs2.jpg
deleted file mode 100644
index 5d6b788..0000000
--- a/initial-contribution/OBJECTWEB/setup/prefs2.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/OBJECTWEB/setup/prefs3.jpg b/initial-contribution/OBJECTWEB/setup/prefs3.jpg
deleted file mode 100644
index c017056..0000000
--- a/initial-contribution/OBJECTWEB/setup/prefs3.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/OBJECTWEB/setup/prefs4.gif b/initial-contribution/OBJECTWEB/setup/prefs4.gif
deleted file mode 100644
index d5541cf..0000000
--- a/initial-contribution/OBJECTWEB/setup/prefs4.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/OBJECTWEB/setup/prefs4.jpg b/initial-contribution/OBJECTWEB/setup/prefs4.jpg
deleted file mode 100644
index c017056..0000000
--- a/initial-contribution/OBJECTWEB/setup/prefs4.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/OBJECTWEB/setup/serverruntime1.gif b/initial-contribution/OBJECTWEB/setup/serverruntime1.gif
deleted file mode 100644
index 8d6284f..0000000
--- a/initial-contribution/OBJECTWEB/setup/serverruntime1.gif
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/OBJECTWEB/setup/serverruntime2.jpg b/initial-contribution/OBJECTWEB/setup/serverruntime2.jpg
deleted file mode 100644
index 1cc129a..0000000
--- a/initial-contribution/OBJECTWEB/setup/serverruntime2.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/OBJECTWEB/setup/serverruntime3.jpg b/initial-contribution/OBJECTWEB/setup/serverruntime3.jpg
deleted file mode 100644
index 23c916b..0000000
--- a/initial-contribution/OBJECTWEB/setup/serverruntime3.jpg
+++ /dev/null
Binary files differ
diff --git a/initial-contribution/OBJECTWEB/setup/setup.html b/initial-contribution/OBJECTWEB/setup/setup.html
deleted file mode 100644
index bc1bc3a..0000000
--- a/initial-contribution/OBJECTWEB/setup/setup.html
+++ /dev/null
@@ -1,126 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=Cp1252">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link href="file:///C|/Documents%20and%20Settings/naci.PEPE/Desktop/OBJECTWEB/theme/Master.css" rel="stylesheet" type="text/css">
-<title>Getting Started.html</title>
-</head>
-<body>
-<H1>Setup and Configuration</H1>
-<H2>1.0 Introduction</H2>
-<P>The plugin is distributed in ZIP format, therefore, using your ZIP file utility,
- unzip lomboz.zip file into the Eclipse_Home directory. This will create a set
-of new plugin directories as follows:</P>
-<P><img src="plugins.gif" width="306" height="240"></P>
-<H2>2.0 Customizing Java Perspective</H2>
-<P>Select menu Window>Customize Perspective..., in the Shortcuts tab choose 'Submenus: New'
-
-check all Lomboz related items.
-
- Select menu Window>Customize Perspective...', in the Shortcuts tab choose 'Submenus: Show View'
-
-check Lomboz Views', J2EE View.
-
-Select menu Window>Customize Perspective...', in the Commands tab in the availabe commands tab, check Lomboz Actions.
-<P><img src="customize.jpg" width="642" height="491">
-<P>
-<H2>3.0 Lomboz Preferences</H2>
-<P>Select menu Window>Preferences', in the Workbench->Label Decorations, check
- Lomboz J2EE Decorators.</P>
-<P><img src="prefs1.jpg" width="506" height="390"></P>
-<P>To use Lomboz, Java projects need to have separate source and binary
- folders. Open the preferences dialog from Workbench -Preferences menu and Expand
- the Java item, New Project. Make sure that the ‘Use folders for source
- and output location as default for newly created Java projects’ check
- box is ticked. Finally enter ‘src’ and ‘bin’ for the
- names of these folders, which are the defaults. Please do not modify these
-names as they are required by some of the Lomboz tasks.</P>
-<p><img src="prefs2.jpg">
-</p>
-<p>Most application servers use the standard Java compiler (javac) to compile JSP files. Javac is found in the tools.jar distributed with standard Java JDKs (NOT JREs).
-You must select the tools.jar that will be used by the application servers here. It is normally found inside the lib folder under the JDK installation.
-</p>
-<p><img src="prefs3.jpg" width="632" height="344"></p>
-<p><strong>Enable JSP Syntax</strong> checking enables or disables JSP compilation. This is useful if you have very large JSP files and you do not want to check the syntax everytime you save the file. By default it is enabled. If you disable it Lomboz will not perform any syntax checking and you will not get any feedback about the potential problems in JSP files.
- <strong>Server restart</strong> is useful if your application server does not automatically reload a web/ejb module after it has been reployed. If this option is enabled, Lomboz will restart the server after a module is redeployed. This option maybe useful if you are working with Tomcat.<strong> Update
- server classpath</strong> and deployment parameters tells Lomboz to check and fix the Project classpath and deployment properties of a selected module everytime you Launch the targeted server of an ejb or web module. This is very useful if you make a change to the server definition after you create the module. By default it is enabled. If you disable this option, you have to make sure that you fix the project classpath and deployment properties everytime you make such changes.
-<strong>Use application server classpath</strong>, tell Lomboz to use the classpath that you will define in the next step when it launches an application server. It will NOT use the classpath of the Java Projects you will create. If you do not enable this feature, Lomboz will use the classpth of the Java project to launch a server. The disadvantage of this will be that all edployde web and ejb modules will appear twice on the classpath: Once from the eclipse java project and once from the ejb jar or web .war. This can cause unexpected class loader problems. If you are experiencing these problems make sure that you enable this feature.
-
-The reverse side of the coin is you will loose your acapability for dynamically modifying your Java code in a debugger (JDK 1.4 feature).
-
-Some application servers are more sophisticated about how they manage class loaders and they will allow you to use the project classpath, however most will not (i.e. JBoss, Tomcat, etc.)
-
-</p>
-<p><img src="prefs4.gif"></p>
