Date: 2004-04-03T10:15:43 Editor: JeremyBoynes <[EMAIL PROTECTED]> Wiki: Apache Geronimo Wiki Page: TODO URL: http://wiki.apache.org/geronimo/TODO
no comment Change Log: ------------------------------------------------------------------------------ @@ -1,71 +1,27 @@ This is the TODO list for the project. '''Note:''' Tasks should eventually make their way into the IssueTracking system. +This list includes things that we need to happen from affiliate projects as well. + '''Contents''' [[TableOfContents]] -= General Tasks = - - * Generally hanging out on the mail list & answering questions - * Documentation - early days I know but reviewing all the javadoc & helping document stuff or contributing to the website, wiki, FAQ - * Specify initial set of requirements before defining architecture - * Define high-level architecture - * Get a daily build of the website & source & binary distribution working somewhere - * Document how to run PetStore Sample - * Update "maven dist" target to generate a ZIP/tar that can be used to deploy geronimo on another machine - -= General Development Tasks = - - * JUnit test cases - we need to get 90%+ test coverage. Its a great way for folks to learn & understand the current codebase while not really messing stuff up. Also by writing test cases we can find holes and you learn the APIs and how the system hangs together. A great way to get your feet wet by writing code. - * Thread based unit tests - e.g. using something like JUnitPerf might be handy for writing thread-ed tests. - * Download the code & take a look - what do you think? - * Performance testing (bit too early for this) - -= J2EE Development Tasks = - - * Find a complete list of all the JSRs we need to implement as part of J2EE so that we can add them all to this to do list and start implementing them! (See [wiki:J2EESpecs J2EE Specifications]) - * A J2EE deployment verifier. This requires a close reading of the J2EE specifications, so it will also be a learning project. - * Implement JSR 77 (J2EE Application Management) - * Implement JSR 88 (J2EE Application Deployment) [underway] - * A servlet that can satisfy the RMI remote class loading calls. - * A JSR 88 deployer client gui. A server side implementation is required, but I don't think it is needed to start on the client code. [command-line client underway] - * A new JNDI implementation. (See the [[ApacheJ2EE/FAQ]] - we could try use the JNDI inside Tomcat CVS as a base - maybe moving it into Jakarta Commons so we can all work on it & reuse it. There's also talk of using [http://ldapd.sf.net LDAPd] - * A nice web based management console. There is already one for Tomcat thats based on Structs http://cvs.apache.org/viewcvs/jakarta-tomcat-4.0/webapps/admin/ so maybe we could just extend that to add the various J2EE and Geronimo features? - * JCA implementation. There's a JCA 1.5 JMS RA available for [http://www.swiftmq.com SwiftMQ]. Contact [mailto:[EMAIL PROTECTED] Andreas Mueller]. - * Complete EJB container - * MDB implementation - * JavaMail - * API imported (Done) - * API classes implemented (Alex Blewitt) - * POP/SMTP/IMAP providers - * Activation Framework - * API imported (Done) - * Any other implementation relating to Activation framework? - -= Integration Tasks = - -Various projects need to be integrated. Here's a sample list (in no particular order): - - * Tomcat / Jetty - * Axis Web Services - * OpenJMS - * Tyrex - * James - * JNDI implementation - * OJB - * Quartz for scheduler? - * Avalon Containers integration with Geronimo so any Avalon specific components can be deployed easily inside Geronimo (or vice versa) - -= Testing Tasks = - - * Hitting 100% coverage on the Clover report of the JUnit tests - * After you build Geronimo go to a module's directory - * Run maven clover:html-report - * Open target/docs/clover/index.html file in your prefered browser - * The greener the better - * Create a number of use case unit tests testing the expected functionality of the whole J2EE container - * Create some J2EE compliance unit tests - similar to the above but using references to the relevant J2EE specification parts - * Integration testing plan & implementation += For Milestone 1 Release = -= Comments = +Tasks that we need to do to get an M1 Milestone Release out -''How about using Cactus for integration unit testing?'' --VincentMassol + * Release Build and Packaging + * EAR Module + * EAR Deployer + * EJB Deployer (OpenEJB) + * CMP Multi-Valued Relations (OpenEJB) + += General Todo's = + +Tasks that are not associated with a particular release + + * JSR77 support for Jetty components + * DConfigBeans + * Tomcat integration + * JMS integration + * WebServices integration + * EJB Timer Service
