TP2 Tasks

Task list

The dates and tasks could still change based on the new information. Need to check with other teams which have dependencies on the dates.

ID Task Owner(s) Date Dependency Notes DONE
D1 deploy/deploydir/undeploy/redeploy Jane March 5 2008   Yes
D2 enable/disable Hong Feb 13 2008   Yes
D3 list-components (list-applications) Jane March 26 2008   Yes
D4 provide common deployment client interface Tim Feb 27 2008 dependency from admin gui team Yes
D5 support autodeploy Tim Feb 13 2008   Yes
D6 add security support in deployment Hong Feb 20 2008 dependency with security team Yes
D7 switch to domain.xml to store application information Hong March 12 2008   Yes
D8 start/deployment performance Tim March 26 2008   On-going
D9 application management Hong/Tim March 19 2008   Dropped
D10 workspace reorgnization for web distribution Hong March 26 2008   Yes

Details of the tasks and dependencies

  • Support cli commands:
    • deploy/deploydir/undeploy/redeploy: Need to support additional deployment options: --virtualservers, --contextroot and --precompilejsp. Need to look at redeployment and deploy --force scenario.
    • enable/disable
    • get-client-stubs: not planned, confirmed with webservices team this is not needed by war webservices
  • Support deployment for deployment clients
    • Make the common deployment client interface ready for admin-gui to use
      • Dependency from admin-gui team
    • Implement JSR88 on top of new client interface (NTH)
  • Support auto directory deployment (for MyEclipse plugin)
  • Support security
    • Separate out security related deployment logic in SecurityDeployer
      • Dependency from security team
  • Use domain.xml to store application information
    • Dependency on admin infrastructure team
      • Complete domain.xml implementation, so the domain.xml can be persisted.
      • New element represent the applications element.
applications = (application)*
application = (engine+, name, location, context-root?, object-type, enabled, libraries, availability-enabled, 
    directory-deployed, property*)
engine = (sniffer, property*)
  • Start up/ Deployment performance (with performance team)
  • Application Management (NTH)
    • In recent discussion for this feature, it seems there are some requirements for this feature that we did not originally capture. And the new requirements (customize configurations per instance) will affect the design and the implementation of the feature. The current plan is to get the one-pager design document ready by TP2 release.