Bug 779619 (SOA-1989)

Summary: missing jbpm process def fails quietly
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Burr Sutter <burr.sutter>
Component: JBossESBAssignee: Default User <jbpapp-maint>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.0.0 GA   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1989
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-21 20:34:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Burr Sutter 2010-03-15 12:46:04 UTC 
project_key: SOA

This could be user error but it could require a tweak in the logging.

If I forget to deploy bpm5_ESBOrderProcess to jBPM and then use the following action, no message is shown in the console.  Nothing happens.

    <action class="org.jboss.soa.esb.services.jbpm.actions.BpmProcessor" name="start_a_new_order_process">
     <property name="command" value="StartProcessInstanceCommand"/>
     <property name="process-definition-name" value="bpm5_ESBOrderProcess"/>
     <property name="key" value="body.businessKey"/>
     <property name="esbToBpmVars">
      <mapping bpm="entireOrderAsXML" esb="BODY_CONTENT"/>
     </property>     
    </action>

I think there may be a similar problem with Smooks logging level as well - errors are not shown in the console.

Note: I am running SOA inside of JBDS 3.
Comment 1 Anne-Louise Tangring 2010-09-21 20:34:14 UTC 
This can be achieved through Log4j