If you edit and unintentionally corrupt the Reusable Assets Specifications (RAS) manifest file (for example, you set the pattern to an invalid type), the Pattern Authoring view does not display patterns and a null pointer exception is recorded in the PDE Runtime Error Log.
To avoid permission issues when you install deployable plug-ins from RAS assets into the Eclipse plug-ins area, the RAS importer first checks if the area has write permissions. If it does, the plug-ins are extracted into the plug-ins area. However, if the users cannot modify the plug-ins area, the deployable plug-ins are installed in the user's configuration area under com.ibm.xtools.ras.import/plugins.
When deployable plug-ins are installed into Rational Software Modeler by the RAS Import Engine, the Eclipse update configurator reports an error that states that the new plug-in could not be installed because it is already installed. The errors appear after you restart Rational Software Modeler. Note that the newly installed plug-ins deploy correctly and that you can ignore these error messages.
Reusable Assets Specifications (RAS) manifest files for patterns are modified when you create or delete patterns, add or delete parameters, or change the properties of patterns or parameters.
When you work with a pattern in a configuration management system, the system does not detect changes to the RAS manifest, and you are not given the option to check out the RAS manifest file after it changes.
To work around this issue, check out the RAS manifest file before you modify a pattern.
When you download a Reusable Assets Specifications (RAS) asset by using the RAS Asset Explorer, in the Save window, you must type the name of the RAS asset, including the .ras file extension. The RAS asset file name does not load automatically.
When you initiate a RAS Export of a pattern library as a deployable plug-in, you must remain within the 256-character limit for computed path names. If you exceed the limit, some class files might be missing from the JAR file in the exported asset. The missing class files have long names, such as DirectedAssociationPattern$DirectingClassParameter$AssociationClassDependency.
To work around this issue, initiate the RAS Export from a workspace with a short path name. In some rare cases, you might also have to rename the nested classes of a pattern with shorter names.
When you perform a search on a Rational XDE™ repository using a query, the NOT, AND, and OR search options are ignored. Your search string is treated as a keyword.
Return to the main readme file