Bug 778944 (SOA-1378) - Rules: MVELSalienceExpression not thread-safe
Summary: Rules: MVELSalienceExpression not thread-safe
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1378
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBoss Rules
Version: 4.3 CP01
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3 CP02
Assignee: Julian Coleman
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks: SOA-1379
TreeView+ depends on / blocked
 
Reported: 2009-06-19 10:11 UTC by Julian Coleman
Modified: 2009-09-22 08:32 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-22 08:32:07 UTC
Type: Bug


Attachments (Terms of Use)


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

Description Julian Coleman 2009-06-19 10:11:16 UTC
Affects: Release Notes
Date of First Response: 2009-07-22 23:00:56
project_key: SOA

See   JBRULES-1991.
Summary: MVELSalienceExpression not thread-safe

Comment 1 Julian Coleman 2009-06-19 11:41:44 UTC
Link: Added: This issue depends JBRULES-1991


Comment 2 Julian Coleman 2009-06-19 11:46:32 UTC
Fixes pulled across to new Drools SOA branch (soa_branches/SOA_JDK6) in revision
27023 of:
  drools-compiler/src/test/java/org/drools/rule/builder/dialect/mvel/MVELSalienceBuilderTest.java  drools-core/src/main/java/org/drools/base/mvel/MVELSalienceExpression.java

Commit message:
  Pull across revision 25600 from branches/Branch_4_0_2_SOA_4_2.
  JBRULES-1991: 
  SOA-1286:
  MVELSalienceExpression not thread-safe

Drools tag (soa_tags/4.3.0.CP02) created in revision 27025.


Comment 3 Julian Coleman 2009-06-19 11:50:52 UTC
Link: Added: This issue is a dependency of SOA-1379


Comment 4 Dana Mison 2009-07-23 03:00:56 UTC
Added to 4.3.CP02 Release Notes as resolved:

JBRULES-1991 - MVELSalienceExpression is now thread-safe

Comment 5 Jiri Pechanec 2009-09-22 08:32:07 UTC
Verified in CR4


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