Changes in Implicit Java Classpath

Implicit directories added into Studio's Java "classpath" have changed in version 6.0.

Version 5.x of ALBPM Studio loaded Java classes and resources from the studio/ext/ directory. This allowed your project code to load any resources (like property or configuration files) placed in this directory.

On ALBPM Studio version 6.0, directory studio/ext/ was removed. You should place your resource files on your project's lib/ directory instead. This is a cleaner solution, since each project has its own lib/ directory and you don't need to modify your Studio installation directories anymore.

On ALBPM Enterprise, the same resource files should be placed in the <engine_home_dir>/lib directory, where <engine_home_dir> is the ALBPM Engines' Home directory, configured via Process Administrator.

On ALBPM Enterprise for J2EE, the resource files should be placed in a directory loaded by your application server's class loaders. For the case WebLogic, refer to http://edocs.bea.com/wls/docs92/programming/classloading.html#wp1096756.

Important: When exporting a project from ALBPM Studio for deployment on ALBPM Enterprise, you should select option Include Versionable Libraries Only. This prevents non-versionable libraries and resource files from being included in the exported project file. If you don't select this option, resource files included in the project may be loaded before the files placed in <engine_home_dir>/lib.