Task List

why this document

this is the primary coordination document for tasks that need to happen to support GlassFish in NetBeans. The list isn't tied to a release, so this can grow.

I want this to be fairly light weight and still useful as a reference for communication.

Since I want to keep this list as a reference point for discussions, I want to make sure that edits happen in a way that preserve the identifiers across updates.

Editing Rules

There are a couple simple rules that folks need to follow to make this possible:

1. Add items at the 'end' of list or sub-list... not in the middle. So, if you add a 'top level item' do it at the end of the document. The same holds true for adding a sub-item... Adding sublists is an easy way to avoid breaking this rule...
2. No items are to be deleted. If you need to delete an item use the strikethrough ccs directive. And put a note about why the item is struck through... There is an exception to this rule... you can delete an item from the list if it does not affect the numbering of items that follow it. This basically means the last item in a list or sub-list.
3. Use the ccs directive to color text as green when you consider the item to be done/ready for testing by QA. %_{%(color: green text that needs to be colored%}% Please add a link to any 'cross reference' that makes sense for an item when you mark it as completed. An obvious cross reference would be a link to the commit/commits that you think 'close' this item.
4. I expect folks to edit this list to communicate the work that they are doing or think they will be doing to support Glassfish in NB. If you are working on a task and think of subtasks that aren't called out, take the minute to add them to the document. That way folks can get a feel for the status by comparing green to black elements in the list. By the end of milestone three, we want to have a list that is 'mostly' green.

The List

1. extend v3 integration to support remote domains
   Vince
   1. change the registration wizard
      1. UI design design document
   2. enable archive deployment with POST
2. support only v3 'final'
   Vince the commit%%
   1. remove Prelude from user visible labels
   2. switch the 'source' of the bits that get used by 'Download v3 Now' button
   3. ping RE to shift to using v3 promoted bits
3. extend v3 with settable deployment timeout
   1. UI design for server properties panels
4. remove enable/disable functionality from 'deployed apps' under v2 domain (bug fix) issue
5. make sure starting v3 can trigger the start of Java DB (or other registered DB like MySQL) Jav db only at this point%%
   1. include user control to disable automatic start-up of the DB (on server properties page)
   2. base start-up processing on better 'trigger', like presence of a jdbc resource in the app or on the server that is being started.
6. user and password properties for v3 domains
   1. use to create authenticated admin requests
   2. UI design for registration wizard
   3. UI design for server properties
7. allow user to change the ports for a server on the properties page
   1. UI design for server properties
8. allow user to specify the transport details for debugging (shmem vs strike host/port

   )

   ---

   Jspwiki style: socket

   1. UI design for server properties
9. allow user to change the java strike platform

   used to start v3

   ---

   Jspwiki style: executable

   1. UI design for server properties
10. allow user to control whether the server uses the IDE's proxy settings when started from the IDE
    1. UI design for server properties
11. extend personal domain processing to allow user to define ports and auth info
    1. -ports
    2. username and password-
    3. UI design for registration wizard
12. allow user to associate username and password with a domain at registration time
    1. UI design for registration wizard
13. prep javadb when v3 is registered
    Nitya
    1. create databases that have the data to support samples
    2. register connections with the IDE
    3. add jdbc resource/connection pool info to v3 domain
14. extend v3's download now button to be more tweakable and informative but with decent defaults
15. add menu item to edit domain.xml in xml editor
16. extend runtime tree
    Nitya
    1. partition module types
    2. allow user to view/edit properties of deployed modules
    3. expose API to extend the v3 run-time tree
    4. partition JDBC resources
    5. add nodes and folders for resources that are 'new in v3' (compared to v3 Prelude)
    6. Currently Connector Resource are added. Other resources will be added as commands become available in v3
    7. UI to edit domain properties... that ends up in
17. ejb jar project deployment
    1. directory
    2. archive – for remote domains
18. ear project deployment
    1. directory
    2. archive – for remote domains
19. web app deployment
    1. directory
    2. archive – for remote deployment
20. Support 'Use database'
    Nitya
    1. fix issues for servlet
    2. fix issues related to ejbs
       1. in ejb jar project
       2. in web app project
21. Support 'Call EJB'
    1. web-app code calling ejb from ejb-jar project
    2. web app code calling ejb from inside the web app project
       1. servlet
       2. ejb
    3. ejb-jar code call ejb from ejb-jar project
22. Support 'Send Mail'
    Nitya
    1. this depends on the IDE
    2. api's nned to be added
23. Support 'Use JMS'
    Nitya
24. register xml schemas and dtds
    Rochelle
    1. commit1
    2. commit2
    3. commit3
    4. commit4
    5. commit5
    6. internal link to test instructions
25. Resource wizards
    Nitya
    1. fix bugs
26. extend v3 plugin to deal with complex tasks better
    1. http monitor bug fixes
    2. jdbc driver deployment fixes
    3. profiler and start issues
27. j2eeserver api changes to support Java EE 6 development
    1. need way to identify which features are available from a server
    2. need way to identify which features are used by a project
28. app client project deployment
    1. archive – local
    2. archive – remote
29. support v3 Prelude in main
    1. roll-back changes that implemented item 2 in 'main'
    2. refactor code to create two plugins one for v3 and one for v3 Prelude
30. read/write AS_JAVA into asenv.conf and asenv.bat or domain.xml for v3
31. migration issues
    1. users turn off v3 support
    2. users turn off v3 Prelude support