Deploying State Transition Predicates
To deploy your custom predicates, the Java code must be compiled and the resulting *.class file must be uploaded to the appropriate sub-directory under ~/CB-.../tomcat/webapps/cb/WEB-INF/classes/..., where the sub-directory is the equivalent of the predicates's package name.
If you have multiple custom predicates (along with custom workflow actions, Wiki Plugins, etc.), you may choose to pack all your custom classes (along with your custom language resource files) into one Java archive (*.jar) and put that into ~/CB-.../tomcat/webapps/cb/WEB-INF/lib.
For actions not under com.intland.codebeamer, or not annotated as @Component
, you must also provide extra <bean> configurations in
, you must also provide extra <bean> configurations in~/CB-../tomcat/webapps/cb/WEB-INF/classes/my-ApplicationContext.xml
Finally you have to restart Codebeamer, for your newly deployed predicates to get loaded.
 | Old pre-CB-7.8 state transition predicates implementing StateTransitionPredicate or derived from DefaultStateTransitionPredicate are not longer supported in CB-7.8 or newer! |
Any attempt to deploy such old predicates via ~/CB-.../tomcat/webapps/cb/WEB-INF/classes/my-applicationContext.xml will cause the Codebeamer startup to fail.
If you had developed custom predicates, you should first check, whether the default Expression predicate can now be used for this task. Only if that is not possible, you should try to migrate your custom predicate.