Q. JBPM supports databases such as:-

View solution

Q. To make use of jBPM from within a Spring application context.

View solution

Q. To use jBPM as a stand-alone process server:-

View solution

Q. It’s not too difficult to get jBPM working on JBoss EJB environment.

View solution

Q. JBoss itself supports deploying processes to a directory and loading those, with some configuration.

View solution

Q. jBPM is, fundamentally, a runtime that stores its state and jobs in a database. It uses:-

View solution

Q. To have an annotated class be registered as a Hibernate entity, it needs to be registered with the:-

View solution

Q. Because our jBPM configuration uses Hibernate, we have to configure the :-

View solution

Q. The next bean—the dataSource—is configured entirely at your discretion. The properties are set using properties in the properties file :-

View solution

Q. When we’re integrating with Spring, we modify the transaction-context element and the command-service element.

View solution

Q. The hibernate-session element tells jBPM to reuse an existing Hibernate session:-

View solution

Q. The spring-transaction-interceptor element is a special element to enable jBPM to defer to the TransactionManager defined in our application context.

View solution

Q. jBPM will expose beans using the:-

View solution

Q. jBPM, and indeed most workflow engines, passivate state for you, allowing a process to wait on external events :-

View solution

Q. The method annotated with @PostConstruct will be run after the bean’s been configured to let the user inject custom initialization logic.

View solution

Q. The business process file’s name needs to end in :-

View solution

Q. At the top, we’ve injected some dependencies:

View solution

Q. In the bean, setupProcessDefinitions is run when the bean is created.

View solution

Q. Process definition will reference Spring beans using the JBoss expression language.

View solution

Q. In jBPM, a business process is built using jPDL.

View solution