07-10-2009 10:50 AM
RIM was able to reproduce the issue based on my sample code and confirmed that this is a problem caused by distribution of classes within sibling COD files and Application Control checks for protected APIs.
In a third-party application, if a class name (including the package name) sorts after "com.rim." then the compiled class gets put into the higher-numbered COD files. Class names that sort before "com.rim." go in lower-numbered COD files. My application has seven sibling COD files and because my class names were all "com.z...." my code always ended up in the higher-numbered COD files and my resource files were in the lower-numbered COD files.
In 4.6.1 and 5.0, the Application Control checks perform slowly for classes in higher-numbered CODs. The recommended workaround from RIM was to use class names that sort before "com.rim." RIM also logged an issue and will make changes in the future to avoid this behavior.
07-13-2009 05:08 PM
07-14-2009 03:20 AM