Bug 779619 (SOA-1989) - missing jbpm process def fails quietly
Summary: missing jbpm process def fails quietly
Keywords:
Status: CLOSED WONTFIX
Alias: SOA-1989
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB
Version: 5.0.0 GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-15 12:46 UTC by Burr Sutter
Modified: 2010-09-21 20:34 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-09-21 20:34:14 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1989 0 None None None Never

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


Note You need to log in before you can comment on or make changes to this bug.