May 2012 - esb-issues - Jboss List Archives

[JBoss JIRA] (JBESB-3792) Bpm5Processor does not map BPM parameters on SIGNAL_EVENT.

by Marek Baluch (JIRA)

Marek Baluch created JBESB-3792: ----------------------------------- Summary: Bpm5Processor does not map BPM parameters on SIGNAL_EVENT. Key: JBESB-3792 URL: https://issues.jboss.org/browse/JBESB-3792 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.11 Reporter: Marek Baluch Bpm5Processor does not map BPM parameters on SIGNAL_EVENT. This means that settings like: {code} <action name="jbpm5-2" class="org.jboss.soa.esb.services.jbpm5.actions.Bpm5Processor"> <property name="process-definition-name" value="Evaluation.bpmn"/> <property name="process-id" value="com.sample.evaluation"/> <property name="process-action" value="signalEvent|abortProcessInstance"/> <property name="esbToBpmParams"> <mapping esb="employee" bpm="employee" value="krisv"/> <mapping esb="reason" bpm="reason" value="Yearly performance review"/> </property> </action> {code} have no effect. IMO mapping BPM parameters does not make much sense for the abortProcessInstance (as used in the bpm5processor sample) event but it makes sence for signalEvent. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

3
7
0 / 0

[JBoss JIRA] (JBESB-3811) Add ESBWorkItemHandler

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3811: ------------------------------------- Summary: Add ESBWorkItemHandler Key: JBESB-3811 URL: https://issues.jboss.org/browse/JBESB-3811 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.11 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 CP1 Add the ESBWorkItemHandler to jbpm5 so that we we compile it into jbossesb-jbpm5.jar and have it available as a JBPM Service. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
2
0 / 0

[JBoss JIRA] (JBESB-3810) BusinessRulesProcessor action does not provide an option to set-up value of PSEUDO time

by Musharraf Hussain (JIRA)

Musharraf Hussain created JBESB-3810: ---------------------------------------- Summary: BusinessRulesProcessor action does not provide an option to set-up value of PSEUDO time Key: JBESB-3810 URL: https://issues.jboss.org/browse/JBESB-3810 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.10 Environment: Red Hat Enterprise Linux 6.x JBoss Enterprise SOA Platform 5.2.0 Reporter: Musharraf Hussain - Currently there is no way to get SessionPseudoClock from BusinessRulesProcessor action to call SessionPseudoClock.advanceTime() . Thus, BusinessRulesProcessor action [1] does not provide an option to set-up value of PSEUDO time. [1] http://anonsvn.jboss.org/repos/labs/labs/jbossesb/tags/JBESB_4_10/product... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
1
0 / 0

[JBoss JIRA] (JBESB-3803) org.jboss.soa.esb.listeners.gateway.SqlTableGatewayListener class needs to log DEBUG statements

by Rick Wagner (JIRA)

Rick Wagner created JBESB-3803: ---------------------------------- Summary: org.jboss.soa.esb.listeners.gateway.SqlTableGatewayListener class needs to log DEBUG statements Key: JBESB-3803 URL: https://issues.jboss.org/browse/JBESB-3803 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.11 Environment: ESB as used by SOA-P. Reporter: Rick Wagner Priority: Minor Description of problem: SqlTableGatewayListener class in general has virtually not enough debug statements for trouble shooting when a problem arises. Recently we ran into an issue with the SQL that was built by SqlTableGatewayListener. Since there was no debug logging on the sql that got built, we had to use byteman scripts to figure out the SQL. The following three methods should at least log the SQL that it built before returning from the method. protected String scanStatement(); protected String updateStatement(); protected String deleteStatement(); Version-Release number of selected component (if applicable): JBossESB 4.10 How reproducible: Does not apply. Steps to Reproduce: Does not apply. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

3
4
0 / 0

[JBoss JIRA] (JBESB-3743) Transactional improvement for invm resources

by Kevin Conner (JIRA)

Kevin Conner created JBESB-3743: ----------------------------------- Summary: Transactional improvement for invm resources Key: JBESB-3743 URL: https://issues.jboss.org/browse/JBESB-3743 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.10 CP1 Reporter: Kevin Conner The transactional behaviour of InVM resources associates a single message with each XAResource. If multiple InVM operations occur within the same transaction then multiple XAResources will be enlisted into the transaction, causing the transaction manager to do more work than is necessary. The code needs to change so that there is a single XAResource enlisted with each transaction, representing multiple operations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

3
5
0 / 0

[JBoss JIRA] (JBESB-3808) Switch jbpm5 ESB persistence to use HSQLDialect

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3808: ------------------------------------- Summary: Switch jbpm5 ESB persistence to use HSQLDialect Key: JBESB-3808 URL: https://issues.jboss.org/browse/JBESB-3808 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.11 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 CP1 Switch jbpm5 ESB persistence to use HSQLDialect from H2Dialect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
2
0 / 0

[JBoss JIRA] (JBESB-3806) Need a ModelSchemaParser for 1.3.1 jbossesb schema

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3806: ------------------------------------- Summary: Need a ModelSchemaParser for 1.3.1 jbossesb schema Key: JBESB-3806 URL: https://issues.jboss.org/browse/JBESB-3806 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.11 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 CP1 Missing a schema parser for 1.3.1 bananastand:rosetta tcunning$ find . | grep Model | grep SchemaParser | grep -v svn ./src/org/jboss/soa/esb/listeners/config/model/Model101SchemaParser.java ./src/org/jboss/soa/esb/listeners/config/model/Model110SchemaParser.java ./src/org/jboss/soa/esb/listeners/config/model/Model120SchemaParser.java ./src/org/jboss/soa/esb/listeners/config/model/Model130SchemaParser.java bananastand:rosetta tcunning$ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
2
0 / 0

[JBoss JIRA] (JBESB-3807) jbpm5 failing tests because DefaultDS not found

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3807: ------------------------------------- Summary: jbpm5 failing tests because DefaultDS not found Key: JBESB-3807 URL: https://issues.jboss.org/browse/JBESB-3807 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.11 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 CP1 Make sure we use DefaultDS as our test datasource for the tests in jbpm5 to match the persistence.xml. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
4
0 / 0

[JBoss JIRA] (JBESB-3786) Enable configuration and propagation of the JMS priority through the ESB aware servicestr

by Kevin Conner (JIRA)

Kevin Conner created JBESB-3786: ----------------------------------- Summary: Enable configuration and propagation of the JMS priority through the ESB aware servicestr Key: JBESB-3786 URL: https://issues.jboss.org/browse/JBESB-3786 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.11 Reporter: Kevin Conner The feature request is to have a priority configured on a gateway and then have that propagate through the ESB services which are invoked as a result. The priority should be applied to any JMS transports which are used to communicate with ESB services, using the JMS message setJMSPriorty, and propagated through those services to subsequent ESB service invocations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
7
0 / 0

[JBoss JIRA] (JBESB-3805) Camel Gateway configuration ignores properties set on provider and bus

by Kevin Conner (JIRA)

Kevin Conner created JBESB-3805: ----------------------------------- Summary: Camel Gateway configuration ignores properties set on provider and bus Key: JBESB-3805 URL: https://issues.jboss.org/browse/JBESB-3805 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.11 Reporter: Kevin Conner The camel gateway only maps properties from the camel-gateway element, ignoring those on the camel-bus and camel-provider elements. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues May 2012