Fixes are available
APAR status
Closed as program error.
Error description
Links to requrement attached to Java classes (not the files) are not refactored after a rename of the project. The links to requ irements attached to the Java Class files are refactored. Steps to reproduce: Create a requirements project in ReqPro 7.0.1 Create 2 TYPE requirements Open RSA Create a Java project called project1 Create a package Create 2 Java Class files Class1.java and Class2.java Open the requirements explorer and then open the ReqPro project Drag Class1.java onto requirement 1 Drag the Java class Class2 onto requirement 2 Save everything Right click on the top level of the project and select Refactor? Rename Change the name to project1a Open the Requirement Link Problems view In the Requirements Explorer right click on the Opaque Element P roxies and select Organise Proxies Expand the branch of the Opaque Element Proxies relating to the old (before rename) project A red 'x' appears on requirement 2 and an error message appears in the Requirement Link Problems Related information: First enable the visibilty of the AssociatedElementUri in ReqPro by selecting File?Project Administration?Properties and click o n Attributes tab. Then select the Requirement type 'TYPE' then highlight the Associated ElementUri and click on edit. Uncheck the hide checkbox. In RSA if you look at the properties tab of the requirements you will see that the file link has a type res: whereas the Java cl ass itself has a URI of type j2se: Workaround: Link requirements at the file level. Note that this is not an option for this customer who requires t he link to be at the class level and anyway has thousands of req uirements.
Local fix
Problem summary
There are 2 listeners to refactoring. one for resource changes (updates links to files, folders, etc.) and one for java element changes (renaming packages, classes, methods). The Java Refactoring listener was not treating the JavaProject as a JavaElement, so no code was there to update java elements upon JavaProject rename.
Problem conclusion
Implemented 2 functions that notifies all linked JavaElements below the JavaProject upon JavaProject rename
Temporary fix
Comments
APAR Information
APAR number
PM03230
Reported component name
SW ARCHITECT WI
Reported component ID
5724I7001
Reported release
754
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-12-10
Closed date
2010-04-01
Last modified date
2010-04-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
SW ARCHITECT WI
Fixed component ID
5724I7001
Applicable component levels
R754 PSN
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYKBQ","label":"Rational Software Architect Designer for WebSphere Software"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"754","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS4JCV","label":"Rational Software Architect for WebSphere Software"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"754","Edition":"","Line of Business":{"code":"LOB15","label":"Integration"}}]
Document Information
Modified date:
01 April 2010