Hey All,
I just committed my improvements to the JavaClassWorkspaceMapManager. I wanted to get this change into the daily build for a couple days before our next soft release of Hackystat. Of course all the test cases pass on my local machine and I've gone through many manual tests. However, if you spot anything weird with coverage or unit test data (in your local versions) immediately send me an email.
The improvements to this mechanism include: 1) fixes to the review issues generated in Sept 2004
2) added persistency to the mappings using the UserData Partition mechanism. This new feature saves (on my CSDL machine) more that 2 minutes and 600 MB when reading in FileMetric data from users in hacky2004-all.
3) added a new admin command (it works, but I need to add a little bit more to it). here is the doc for that command
This administrator command allows you to manually refresh and persist the JavaClassWorkspaceMapManager caches. In normal operations persistence will occur (1) if a user has a JavaClassWorkspace cache instantiated in the manager and (2) at 2:00 am via a DailyTimer Task. In addition, in normal operations, due to the persistence mechanism a user's JavaClassWorkspace cache will never be generated from the default start day. This command provides a manual override to generate the cache from the default start day and create a new persistent version of that cache.
The User Email selector allows you to select the users who you wish to refresh and persist. In other words, when selecting a user you will read in all their FileMetric data from January 1, 2003. So, be wary of selecting all the users.
In addition, the execution speed of this command depends on how many users you select and the amount of FileMetric data each user has. In other words, this command is slow and it is also memory intensive.
thanks, aaron
