jruaux 2003/03/12 01:37:30
Modified: documentation/docs/xdocs/participating todo.xml
Log:
Updated eclipse todos
Revision Changes Path
1.14 +210 -209 jakarta-cactus/documentation/docs/xdocs/participating/todo.xml
Index: todo.xml
===================================================================
RCS file: /home/cvs/jakarta-cactus/documentation/docs/xdocs/participating/todo.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- todo.xml 3 Mar 2003 08:29:03 -0000 1.13
+++ todo.xml 12 Mar 2003 09:37:30 -0000 1.14
@@ -5,7 +5,7 @@
<properties>
<title>Roadmap/Todo for Cactus</title>
<authors>
- <author name="Vincent Massol" email="[EMAIL PROTECTED]"/>
+ <author name="Vincent Massol" email="[EMAIL PROTECTED]" />
</authors>
</properties>
@@ -13,224 +13,225 @@
<section title="Forewords">
<p>
- As is stated on the Cactus <link href="site:goals">goals</link> page,
- the intention is to explore as much as possible in the realm of unit
- testing of server side java code ...
+ As is stated on the Cactus
+ <link href="site:goals">goals</link>
+ page, the intention is to explore as much as possible in the realm
+ of unit testing of server side java code ...
</p>
<p>
- This brings a bad news and a good one ... The
- bad one is that the TODO list is likely to keep growing or at least
- have a respectable size ... The good one
- is that there will be work for everyone ... :-)
+ This brings a bad news and a good one ... The bad one is that the
+ TODO list is likely to keep growing or at least have a respectable size
+ ... The good one is that there will be work for everyone ... :-)
</p>
<p>
- If you are interested in participating, send an email on the Cactus
- mailing list stating your interest and you'll be enrolled right
- away ... We're always looking for help ! Don't be put off if in the
- "Volunteer" column there is already a person listed. On the contrary,
- the more person that participate in a given task, the better (like in
- pair programming, several sets of eyes are always better than one!).
- However you'll need to sync. with these others persons but this is
+ If you are interested in participating, send an email on the Cactus
+ mailing list stating your interest and you'll be enrolled right away
+ ... We're always looking for help ! Don't be put off if in the
+ "Volunteer" column there is already a person listed. On the contrary,
+ the more person that participate in a given task, the better (like in
+ pair programming, several sets of eyes are always better than one!).
+ However you'll need to sync. with these others persons but this is
easily done by posting to the mailing-list.
</p>
- <p>
- The game has just begun ... !
- </p>
+ <p>The game has just begun ... !</p>
</section>
- <version title="Version 1.5">
+ <version title="Version 1.5">
- <category title="Documentation">
- <action>
- Add doc for the new feature to run JUnit Test Case without modifying
- them on the server side.
- </action>
- <action>
- Modify the web site presentation: start by introducing the Cactus
- Ecosystem: framework + front ends.
- </action>
- <action assigned-to="Christopher Lenz">
- Add a web site sitemap.
- </action>
- <action>
- Update web site for new <code>begin()</code> and <code>end()</code>
- methods.
- </action>
- <action>
- Add documentation for the new Initializer feature.
- </action>
- <action>
- Add documentation for a new way to start Cactus tests by using the
- Jetty Initializer.
- </action>
- <action assigned-to="Jason Robertson, Vincent Massol">
- Add documentation for form-based authentication.
- </action>
- </category>
-
- <category title="Design/Code">
- <action assigned-to="Vincent Massol">
- In the Ant Integration, support merging of user web.xml with Cactus
- provided web.xml.
- </action>
- </category>
-
- <category title="Eclipse Plugin">
- <action assigned-to="Julien Ruaux">
- Changed directory structure to
- <code>integration/eclipse/org.apache.cactus.eclipse/</code>, in order
- to allow for several other Eclipse plugins, Eclipse features and
- Eclipse sites. And this is the standard directory structure for Eclipse
- plugins.
- </action>
- <action assigned-to="Julien Ruaux">
- Add an Eclipse Feature to distribute our Eclipse plugin.
- </action>
- <action assigned-to="Julien Ruaux">
- Add an Eclipse Site to distribute our Eclipse plugin.
- </action>
- </category>
-
- </version>
-
- <version title="Undefined">
-
- <category title="Documentation">
- <action>
- Improve the documentation CheckSitemap Ant task to check external URLs
- (when online).
- </action>
- </category>
-
- <category title="Build Process">
- <action assigned-to="Jason Van Zyl">
- Move Cactus to Maven.
- </action>
- <action>
- Add Ant scripts for JBoss/Tomcat.
- </action>
- <action>
- Add Ant scripts for the J2EE RI.
- </action>
- </category>
-
- <category title="Design/Code">
- <action assigned-to="Hudson Wong, Vincent Massol">
- Add an EJB sample application to demonstrate how to perform EJB
- unit testing.
- </action>
- <action assigned-to="Jason Robertson, Vincent Massol">
- Add test case for form-based authentication.
- </action>
- <action assigned-to="Christopher Lenz">
- Improve the ServletTestRunner: look at ways to make it run without the
- permission to set system properties.
- Potentially look at replacing it by the JUnitEE test runner.
- </action>
- <action>
- Continue the JMS Redirector/Client to test Message Driven Beans.
- </action>
- <action>
- Add support for Servlet API 2.4/JSP 2.0 (by using Resin 3, Tomcat 5).
- </action>
- <action>
- Potentially replace access to instance variables of redirectors by
- method calls. For example, replace "request.xxx()" by
- "getHttpServletRequest().xxx()". Deprecate the direct access. Needs
- to be discussed on cactus-dev.
- </action>
- <action>
- Add support for multi-concurrent Cactus tests. This involves storing
- each test result under a unique key in the application scope.
- </action>
- <action>
- Improve support for the JUnitReport XML format so that the Ant-provided
- <code>junit-noframes.xsl</code> XSL is completely supported. ATM, some
- sections appear blank.
- </action>
- <action>
- Add EJB Redirectors so that unit testing of code that require an EJB
- is facilitated. For example, let's imagine you need to test that an
- object that has been put in the JNDI tree by a servlet can be retrieved
- by an EJB. These are not unit tests per see but rather integration
- tests, which is Cactus favorite domain. Also these redirectors could be
- used to directly unit tests EJB whithout requiring a servlet
- environment (at the current time, you need to call your EJB from a
- Servlet/JSP/Filter Redirector, which is fine for certain tests but not
- needed for others.
- </action>
- <action assigned-to="Vincent Massol">
- In the Ant Integration, add support for EARs (used for EJB unit
- testing).
- </action>
- </category>
+ <category title="Documentation">
+ <action>
+ Add doc for the new feature to run JUnit Test Case without
+ modifying them on the server side.
+ </action>
+ <action>
+ Modify the web site presentation: start by introducing the
+ Cactus Ecosystem: framework + front ends.
+ </action>
+ <action assigned-to="Christopher Lenz">Add a web site sitemap.</action>
+ <action>
+ Update web site for new
+ <code>begin()</code>
+ and
+ <code>end()</code>
+ methods.
+ </action>
+ <action>Add documentation for the new Initializer feature.</action>
+ <action>
+ Add documentation for a new way to start Cactus tests by using the
+ Jetty Initializer.
+ </action>
+ <action assigned-to="Jason Robertson, Vincent Massol">Add documentation for
form-based authentication.</action>
+ </category>
+
+ <category title="Design/Code">
+ <action assigned-to="Vincent Massol">
+ In the Ant Integration, support merging of user web.xml with Cactus
+ provided web.xml.
+ </action>
+ </category>
+
+ <category title="Eclipse Plugin">
+ <action assigned-to="Julien Ruaux">
+ Changed directory structure to
+ <code>integration/eclipse/org.apache.cactus.eclipse/</code>
+ , in order to allow for several other Eclipse plugins, Eclipse
+ features and Eclipse sites. And this is the standard directory
+ structure for Eclipse plugins.
+ </action>
+ <action assigned-to="Julien Ruaux">Add an Eclipse Feature to distribute our
Eclipse plugin.</action>
+ <action assigned-to="Julien Ruaux">Add an Eclipse Site to distribute our
Eclipse plugin.</action>
+ </category>
+
+ </version>
+
+ <version title="Undefined">
+
+ <category title="Documentation">
+ <action>
+ Improve the documentation CheckSitemap Ant task to check
+ external URLs (when online).
+ </action>
+ </category>
+
+ <category title="Build Process">
+ <action assigned-to="Jason Van Zyl">Move Cactus to Maven.</action>
+ <action>Add Ant scripts for JBoss/Tomcat.</action>
+ <action>Add Ant scripts for the J2EE RI.</action>
+ </category>
+
+ <category title="Design/Code">
+ <action assigned-to="Hudson Wong, Vincent Massol">
+ Add an EJB sample application to demonstrate how to perform EJB
+ unit testing.
+ </action>
+ <action assigned-to="Jason Robertson, Vincent Massol">Add test case for
form-based authentication.</action>
+ <action assigned-to="Christopher Lenz">
+ Improve the ServletTestRunner: look at ways to make it run
+ without the permission to set system properties. Potentially look at
+ replacing it by the JUnitEE test runner.
+ </action>
+ <action>
+ Continue the JMS Redirector/Client to test Message Driven
+ Beans.
+ </action>
+ <action>
+ Add support for Servlet API 2.4/JSP 2.0 (by using Resin 3, Tomcat
+ 5).
+ </action>
+ <action>
+ Potentially replace access to instance variables of
+ redirectors by method calls. For example, replace "request.xxx()" by
+ "getHttpServletRequest().xxx()". Deprecate the direct access. Needs
+ to be discussed on cactus-dev.
+ </action>
+ <action>
+ Add support for multi-concurrent Cactus tests. This involves
+ storing each test result under a unique key in the application scope.
+ </action>
+ <action>
+ Improve support for the JUnitReport XML format so that the
+ Ant-provided
+ <code>junit-noframes.xsl</code>
+ XSL is completely supported. ATM, some sections appear blank.
+ </action>
+ <action>
+ Add EJB Redirectors so that unit testing of code that require an
+ EJB is facilitated. For example, let's imagine you need to test that
+ an object that has been put in the JNDI tree by a servlet can be
+ retrieved by an EJB. These are not unit tests per see but rather
+ integration tests, which is Cactus favorite domain. Also these
+ redirectors could be used to directly unit tests EJB whithout
+ requiring a servlet environment (at the current time, you need to
+ call your EJB from a Servlet/JSP/Filter Redirector, which is fine for
+ certain tests but not needed for others.
+ </action>
+ <action assigned-to="Vincent Massol">
+ In the Ant Integration, add support for EARs (used for EJB unit
+ testing).
+ </action>
+ </category>
+
+ <category title="Ideas">
+ <p>Ideas to explore ...</p>
+ <action>Potential bundling of JUnitEE.</action>
+ <action>
+ Add performance extensions to be able to test each single method in
+ performance: response time. Need to add notion of server time in
+ cactus XML response. And need extensions (probably TestSuite
+ extensions to repeat each test or start several threads). Idea
+ initially suggested by
+ <link href="mailto:[EMAIL PROTECTED]">Michael Rimov</link>
+ . Integrate JUnitPerf.
+ </action>
+ <action>
+ Use
+ <link href="http://xdoclet.sourceforge.net/docs/";>XDoclet</link>
+ with Cactus to better provide continuous integration. It could be
+ used to automatically generate
+ <code>web.xml</code>
+ files, automatically generating test cases from methods to test,
+ ...
+ </action>
+ <action assigned-to="Nicholas Lesiecki, Vincent Massol">
+ Add tutorial on AspectJ testing (using AspectJ with Cactus testing
+ in order to easily intercept method calls and relace them by the
+ needed behavior for the test). Research adding a Cactus Aspect
+ extension to allow writing test cases as Aspects (this would allow to
+ remove the need for Cactus redirectors in most cases).
+ </action>
+ <action>
+ Help Cactus users test multipart/form-data. At least explain how
+ to do it. Some idea: use cos.jar (from
+ <link
+
href="http://www.servlets.com/cos/index.html";>http://www.servlets.com/cos/index.html</link>
+ ) to read multipart/form-data on the server side. Now we still need
+ to provide a mechanism to easily send multipart/form-data on the
+ Cactus client side. The best solution would be to use HttpClient but
+ we need to check if it has this feature or if it can be added.
+ Submitted by
+ <link href="mailto:[EMAIL PROTECTED]">Gunnar Ole Skogen</link>
+ .
+ </action>
+ <action>
+ Provide a full servlet container test suite a la Watchdog using
+ Cactus
+ </action>
+ </category>
+
+ <category title="Eclipse Plugin">
+ <action>
+ Ability to leave the server running after the test is finished
+ so that we don't need to start it again for the next test (needs hot
+ redeploy)
+ </action>
+ <action>
+ Add client jars in the user's project classpath (popup menu to
+ Cactify the project)
+ </action>
+ <action>Add a log view a la Ant plugin</action>
+ <action>Separate the war creation in a war plugin</action>
+ <action>
+ Separate the container start/stop/deploy feature in a separate
+ plugin
+ </action>
+ <action>
+ Ability to Cactify a Java project :
+ <ul>
+ <li>
+ add the client-side jars to the project's build path
+ </li>
+ <li>
+ create a web application folder structure
+ </li>
+ </ul>
+ </action>
+ <action>Automate tests on the plugin</action>
+ <action>Add support for the embedded Jetty container</action>
- <category title="Ideas">
- <p>
- Ideas to explore ...
- </p>
- <action>
- Potential bundling of JUnitEE.
- </action>
- <action>
- Add performance extensions to be able to test each single method in
- performance: response time. Need to add notion of server time in
- cactus XML response. And need extensions (probably TestSuite
- extensions to repeat each test or start several threads). Idea
- initially suggested by
- <link href="mailto:[EMAIL PROTECTED]">Michael Rimov</link>.
- Integrate JUnitPerf.
- </action>
- <action>
- Use <link href="http://xdoclet.sourceforge.net/docs/";>XDoclet</link>
- with Cactus to better provide continuous integration. It could be
- used to automatically generate <code>web.xml</code> files,
- automatically generating test cases from methods to test, ...
- </action>
- <action assigned-to="Nicholas Lesiecki, Vincent Massol">
- Add tutorial on AspectJ testing (using AspectJ with Cactus testing
- in order to easily intercept method calls and relace them by the
- needed behavior for the test). Research adding a Cactus Aspect
- extension to allow writing test cases as Aspects (this would allow to
- remove the need for Cactus redirectors in most cases).
- </action>
- <action>
- Help Cactus users test multipart/form-data. At least explain how to do
- it. Some idea: use cos.jar (from
- <link
href="http://www.servlets.com/cos/index.html";>http://www.servlets.com/cos/index.html</link>)
- to read multipart/form-data on the server side. Now we still need to
- provide a mechanism to easily send multipart/form-data on the Cactus
- client side. The best solution would be to use HttpClient but we need
- to check if it has this feature or if it can be added. Submitted by
- <link href="mailto:[EMAIL PROTECTED]">Gunnar Ole Skogen</link>.
- </action>
- <action>
- Provide a full servlet container test suite a la Watchdog using Cactus
- </action>
- </category>
-
- <category title="Eclipse Plugin">
- <action>
- Ability to leave the server running after the test is
- finished so that we don't need to start it again for the next
- test (needs hot redeploy)
- </action>
- <action>
- Add client jars in the user's project classpath (popup menu to Cactify the
project)
- </action>
- <action>
- Add a log view a la Ant plugin
- </action>
- <action>
- Separate the war creation in a war plugin
- </action>
- <action>
- Separate the container start/stop/deploy feature in a separate plugin
- </action>
- </category>
-
- </version>
+ </category>
+
+ </version>
</body>
-
+
</document>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
