APAR status
Closed as program error.
Error description
If importing a project (which contains no custom plug-in JARs) into Studio then the Plug-in JARs folder and default JAR are not present after profile generation. This means that new custom JARs cannot be added to the profile and once this profile is active in WSRR governance policy validation messages will not contain their full descriptive text.
Local fix
Problem summary
A project with no custom plugin JARs does not have a Plug-in JARs folder once exported. Therefore when the project is imported into Studio, no Plug-in JARs folder or default JAR are created.
Problem conclusion
A project imported into Studio will always contain the Plug-in JARs folder and (at least) the default JAR. This fix is targeted at Studio v7.5.0.2.
Temporary fix
Comments
APAR Information
APAR number
IV10510
Reported component name
SERV REG STUDIO
Reported component ID
5724N7202
Reported release
750
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-11-11
Closed date
2011-11-11
Last modified date
2011-11-11
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
SERV REG STUDIO
Fixed component ID
5724N7202
Applicable component levels
R750 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSWLGF","label":"WebSphere Service Registry and Repository"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
11 November 2011