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

Q. Once in the java element named send-verification-email, jBPM will invoke the method:-

View solution

Q. Inside authorizeCustomer, the service queries the server for the any processes waiting at the:-

View solution

Q. The authorizeCustomer method also updates the Customer entity, marking it as authorized. From there, execution proceeds to the send-welcome-email java element.

View solution

Q. OSGi—which was formerly known as the:-

View solution

Q. OSGi provides a layer on top of the JVM’s default class loader.

View solution

Q. On top of Spring Dynamic Modules, SpringSource built SpringSource dm Server, which is a server wired from top to bottom with OSGi and Spring.

View solution

Q. OSGi is a framework.

View solution

Q. User component models are:-

View solution

Q. In OSGi, anything used by something else is a state.

View solution