CA Software 5.1.1 WSAD Plugin 2.0 PATCH 006 - CA Technologies
{{search ? 'Close':'Search'}}

****************************************************************

CA Software 5.1.1 WSAD Plugin 2.0 PATCH 006

****************************************************************


****************************************************************
Contents
****************************************************************

1.0 Welcome

2.0 Fix Alerts

3.0 Installation Considerations

4.0 Patch installation
4.1 WINDOWS Installation

5.0 Problems corrected
5.1 Problems fixed in PATCH 001
5.2 Problems fixed in PATCH 002
5.3 Problems fixed in PATCH 003
5.4 Problems fixed in PATCH 004
5.5 Problems fixed in PATCH 005
5.6 Problems fixed in PATCH 006

6.0 Additional information on problems corrected

7.0 Contacting Technical Support


****************************************************************
1.0 Welcome
****************************************************************

This Readme file contains installation considerations as
well as patch installation instructions, problems
corrected, known issues, and contacting Technical Support.


****************************************************************
2.0 Fix Alerts
****************************************************************

For each fix listed, you should view the information listed in
Section 6.0 for additional information.

--none


****************************************************************
3.0 Installation Considerations
****************************************************************

* In addition to its WSAD Plugin PATCH, the Harvest 5.1.1 WSAD Plugin 2.0
also requires the installation of the following patches:

- HARVEST 5.1.1 PATCH.
- HARVEST 5.1.1 HSDK for WSAD 2.0 PATCH.
- HARWEB 3.1 PATCH.

* Please refer to the README.TXT of HARVEST 5.1.1 PATCH,
the HARVEST 5.1.1 HSDK for WSAD 2.0 PATCH, and the
HARWEB 3.1 PATCH for installation instructions.

* The minimum patch level requirements for this WSAD plugin PATCH are:

- HARVEST 5.1.1 PATCH 017.
- HARVEST 5.1.1 HSDK for WSAD 2.0 PATCH 017.
- HARWEB 3.1 PATCH 011.

* Please apply this PATCH/FIX to the corresponding WSAD installation.

* The PATCH files are cumulative; in other words, applying the latest
PATCH file provides all fixes.

For example: HAR511WSAD2PATCH005 contains all fixes from
HAR511WSAD2PATCH001 to HAR511WSAD2PATCH005.

* To apply a patch/fix go to the APPLY PATCH/FIX section.

* The difference between HAR511WSAD2PATCH005 and HAR511WSAD2PATCH005FIX,
is that the first refers to a publicly available PATCH (patch 5),
and the second refers to a set of intermediate FIXES available after
the PATCH (patch 5).

* Intermediate FIXES are usually included in the next publicly
available PATCH.


****************************************************************
4.0 Patch installation
****************************************************************

________________________________________________________________
4.2 WINDOWS Installation
________________________________________________________________

To apply the PATCH/FIX, perform the following steps:

1.- Shutdown Websphere.

2.- Copy the "<patch>.zip" file to the Websphere directory where
the plugins are installed (this should be the "plugins" directory,
which contains the directories "com.ca.harvest.<component name>.<version>").

3.- Decompress "<patch>.zip" file into this directory. This will
place the "com.ca.harvest.<component name>.<version>.zip" files
within the "plugins" directory.

4.- Decompress each "com.ca.harvest.<component name>.<version>.zip" file
into the "plugins" directory. This will create the additional directories
within the "plugins" directory, which contain the updated versions.

5.- Modify file: .harcontext located within: .metadata.pluginscom.ca.harvest.core
and change the version number to the new version number of com.ca.harvest.core.
For example, if the version is 2.0.3, then modify the following line:
<!DOCTYPE harvest SYSTEM 'platform:/plugin/com.ca.harvest.core_2.0.3/dtd/harContext.dtd'>

6.- Start Websphere.


****************************************************************
5.0 Problems corrected
****************************************************************

Note: An asterisk (*) indicates to refer to the section
"6.0 Additional information on problems corrected"

________________________________________________________________
5.1 Problems fixed in PATCH 001
________________________________________________________________

1262 - RESOURCE OUT SYNC ERROR IN WSAD
(*) 1646 - REPLACE WITH LATEST TRUNK VERSION FAILS WITH NO MEANINGFUL MESSAGE
(*) 1648 - REFRACTOR/ RENAME FILE NOT RENAMED
1656 - SYNCHRONISATION INCORRECT WHEN D TAGS EXIST
(*) 1675 - DISABLE SHYNCHRONIZE OPTION WHEN MORE THAN ONE RESOURCE IS SELECTED
(*) 1707 - INVALID VIEWPATH ERROR WHEN SYNCHRONIZING SUBDIRECTORY
1723 - DECORATOR MARKED INCORRECTLY WHEN FILE IS ALREADY CHECKED OUT
1730 - RECEIVED .PROJECT OUT OF SYNC ERROR WHEN UPDATING PROJECT PROPERTIES
1761 - DECORATOR MARKED INCORRECTLY WHEN CHECKIN FAILS FOR SOME FILES
1781 - WSAD 5 HANGS WHEN RENAMING A FILE IN A WEB PROJECT

________________________________________________________________
5.2 Problems fixed in PATCH 002
________________________________________________________________

1727 - IMAGE RESOURCE LEAK CAUSES IDE TO CRASH
1759 - DRAG AND DROP CAUSES A RESOURCE OUT-OF-SYNCH ERROR
1805 - REMOVING ONE PROJECT FROM A HARVEST CONNECTION CLOSES THE CONNECTION
1861 - CANNOT RESIZE PATH COLUMN WITHIN VERSION LIST WINDOW

________________________________________________________________
5.3 Problems fixed in PATCH 003
________________________________________________________________

1782 - CHECKIN FAILS FOR FILES RENAMED FROM UPPER CASE TO LOWER CASE OR VICE VERSA
(*) 1859 - "Replace with" OPTION DISPLAYS BOTH VERSIONS IN WORKSPACE RATHER THAN LATEST VERSION FOR RENAMED FILES
1868 - CANNOT CHECKIN A FILE CONTAINING NON-ENGLISH CHARACTERS

________________________________________________________________
5.4 Problems fixed in PATCH 004
________________________________________________________________

(*) 1727 - WSAD SHUTDOWN BY IMAGE LIMIT

________________________________________________________________
5.5 Problems fixed in PATCH 005
________________________________________________________________

(*) 1846 - UDP OUTPUT IN THE HARVEST LOG IN WSAD IS TRUNCATED
(*) 1964 - REMOVE ITEM CAUSES PROBLEM DURING SYNCHRONIZATION
(*) 2092 - CANNOT UNDO CHECKOUT IN WSAD IF RESERVED VERSION IS DELETED
(*) 2180 - CHANGE MESSAGE WHEN RENAME ITEM PROCESS IS NOT DEFINED
(*) 2262 - CANNOT UNDO CHECKOUT IN WSAD IF RESERVED VERSION IS DELETED BY ANOTHER USER
(*) 2293 - RENAMING AN ITEM CURRENTLY CHECKED OUT INCORRECTLY CREATES NEW ITEM

________________________________________________________________
5.6 Problems fixed in PATCH 006
________________________________________________________________

(*) 2264 - DELETING AN ITEM CURRENTLY CHECKED OUT REMOVES ITEM FROM WORKSPACE
(*) 2663 - SYNCHRONIZE OF WSAD IS SLOWER IN SP2


****************************************************************
6.0 Additional information on problems corrected
****************************************************************

1646 - REPLACE WITH LATEST TRUNK VERSION FAILS WITH NO MEANINGFUL MESSAGE

The following Error Message has been changed:

FROM: CAHReplateWithLatestAction.coMsg2

TO: One or more children of - %7B0%7D - is checked out.


1648 - REFRACTOR/ RENAME FILE NOT RENAMED

The following dialog has been changed:

FROM: "The file cannot be renamed unless it is checked in, Do you want to check it in ?"

TO: "File will not be replaced. Only references within this file will be renamed "


1675 - DISABLE SHYNCHRONIZE OPTION WHEN MORE THAN ONE RESOURCE IS SELECTED

Harvest WSDA plugin does not support synchronisation of multiple packages at a time.
Therefore, this option will now be disabled when more than one package/file is selected.


1707 - INVALID VIEWPATH ERROR WHEN SYNCHRONIZING SUBDIRECTORY

A user cannot synchronize a view path if that view path does not exist in the Repository.
The following message will be displayed if a user attempts to do so:

"Cannot synchronize view path which does not exist in repository"


1727 - WSAD SHUTDOWN BY IMAGE LIMIT

The CA Software CM WebSphere Studio Integration now allows you to customize the label
decorations used on projects managed by Harvest. Go to Window, Preferences, Team, AllFusion
Harvest CM to update the decorator preferences. From this preference page, you have the
ability to enable/disable image decorations, as well as customize the text decorations.


1846 - UDP OUTPUT IN THE HARVEST LOG IN WSAD IS TRUNCATED

UDP output will still appear truncated in the log. Users will have to double click on the entry in the
log and a dialog box will appear showing the whole text.


1859 - "Replace with" OPTION DISPLAYS BOTH VERSIONS IN WORKSPACE RATHER THAN LATEST VERSION FOR RENAMED FILES

Rename a file in the WSAD Workspace, and then check into harvest to create a new version. Then
click "Replace with -> version in Harvest " and get the version compare window. Click this file's
previous version with its original name and perform "Get". Both of the files will incorrectly appear
in the workspace, rather than just the latest version.

1964 - REMOVE ITEM CAUSES PROBLEM DURING SYNCHRONIZATION

If a file is removed from workspace and synchronize with harvest, the file will be deleted. There is no
option to get back this file later on, even if other people checkin the same file or remove the "D" tag
from harvest.

Steps to Reproduce:
1. User1 and User2 do an "Add to workspace" of the same project in WSAD
2. User1 deletes version0 of a file1 & synchronizes with Harvest
-> D-tag with version1 is present in Harvest
3. User2 synchronizes with Harvest and file1 is deleted in his workspace
4. User1 creates a new file, calling it file1, which was previously deleted & synchronizes with Harvest
-> Version2 is created
5. User2 synchronizes with Harvest
-> A new delete tag Version3 is created
-> file1 does not appear
6. User1 synchronizes with Harvest
-> file1 does not appear anymore

2092 - CANNOT UNDO CHECKOUT IN WSAD IF RESERVED VERSION IS DELETED

If an item is checked out for update in a WSAD workspace, and if the reserved version is deleted from the
Harvest perspective, then the checkout cannot be undone.

Steps to Reproduce:
1. Perform a check-out of a file
2. Go to harvest repositories perspective and delete the reserve tag
3. Go back to the navigator and try to synchronize the project or undo checkout.
4. Get an error: version not reserved for file: %7Bfile name%7D

2180 - CHANGE MESSAGE WHEN RENAME ITEM PROCESS IS NOT DEFINED

When trying to rename a file and no rename item process is defined in that state, the error message is misleading.

Current Error Message:
There is no rename item process in the current context.

New Error Message:
There is no rename item process defined in the current harvest state.

2262 - CANNOT UNDO CHECKOUT IN WSAD IF RESERVED VERSION IS DELETED BY ANOTHER USER

After aN "R" tag version is deleted by another user, the first users cannot synchronize, checkin, or
undo checkout for this item.

Steps to Reproduce:
1. UserA adds a project into workspace.
2. Checkout a item for update.
3. Another uesrB adds this project into his workspace also.
4. UserB deletes the "R" tag version from the versoin list in Harvest Repositories field.
5. UserA trys to do Synchronize/checkin/undo check, He will always get error:
version not reserved for file : ....., checkin failed.

With this fix, if a user has checkout ">" mark on an item and the "R" tag version is deleted by another user, the
user can use "undo checkout" to remove the checkout ">" mark, so that the status of the item can be restored back.

2264 - DELETING AN ITEM CURRENTLY CHECKED OUT REMOVES ITEM FROM WORKSPACE

When a user receives the message "Cannot Delete File. Please check-in or undo check-out first."
Selecting OK will remove the file from the workspace instead of letting you checkin or
undo the checkout.

Steps to Reproduce:
1. Add a project into worksapce.
2. Checkout a item for update.
3. Delete this item in the workspace. Will get the message: "Are you sure want to delete the item?"
4. Click yes, Will get the error message: "File is checked out. Please check-in or undo check-out first."
5. Click ok, the file is removed from the workspace.

2293 - RENAMING AN ITEM CURRENTLY CHECKED OUT INCORRECTLY CREATES NEW ITEM

In wsad workspace, there is a project being managed by harvest. User checks out a file for update, makes changes
to this file, and saves it. If there is no rename process defined, then after the rename process fails, a new
version is created for this file in harvest.

Steps to Reproduce:
1. Add a project to WSAD project. There is no rename process defined.
2. Checkout a file for update and make some changes to it, then save it.
3. Right click item and select "rename" to rename the file to a new file.
4. The rename process fails, but a new version is created in harvest.

2663 - SYNCHRONIZE OF WSAD IS SLOWER IN SP2

When comparing synchronization of WSAD between SP2 and Harvest511 PATCH016, sync in SP2 takes
longer time than in PATCH016.

Steps to Reproduce:
1. Apply Harvest 5.1.1 Patch 16 (and the appropriate HSDK & Wsad Patches).
2. Time the Wsad Synchronize
3. Apply Harvest 5.1.1 SP2 (and the appropriate HSDK & Wsad Service Packs).
4. Time the Wsad Synchronize

For example: Synchronize 561 files in a wsad project:
Harvest 5.1.1 patch 16 - 45 sec.
Harvest 5.1.1 SP2 GA - 1 min 30 sec.

Download:

Operating System File Size
Windows 623 KB

Chat with CA

Just give us some brief information and we'll connect you to the right CA Expert.

Our hours of availability are 8AM - 5PM CST.

All Fields Required

connecting

We're matching your request.

Unfortunately, we can't connect you to an agent. If you are not automatically redirected please click here.

  • {{message.agentProfile.name}} will be helping you today.

    View Profile


  • Transfered to {{message.agentProfile.name}}

    {{message.agentProfile.name}} joined the conversation

    {{message.agentProfile.name}} left the conversation

  • Your chat with {{$storage.chatSession.messages[$index - 1].agentProfile.name}} has ended.
    Thank you for your interest in CA.


    How Did We Do?
    Let us know how we did so that we can maintain a quality experience.

    Take Our Survey >

    Rate Your Chat Experience.

    {{chat.statusMsg}}

agent is typing