Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1058304 - Error when opening guided rule with DSL using regex with predefined character classes or {n,m} quantifiers
Summary: Error when opening guided rule with DSL using regex with predefined character...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ER1
: 6.0.1
Assignee: manstis
QA Contact: Jiri Locker
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-27 13:43 UTC by Jiri Locker
Modified: 2014-08-06 19:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 19:58:15 UTC
Type: Bug


Attachments (Terms of Use)

Description Jiri Locker 2014-01-27 13:43:01 UTC
Description of problem:
I have added this DSL to ApplicantDsl in mortgages:

>[then]Set applicant name to {name:\w+ \w+} = applicant.setName("{name}")

When I use it in guided rule it works fine. I can added, name validation works as expected. When I save the rule, close it and reopen, I get an error message saying:

Unable to complete your request. The following exception occurred: Illegal repetition near index 21 Set applicant name to {name:\w+ \w+} ^.

Version-Release number of selected component (if applicable):
CR2

How reproducible:
-

Steps to Reproduce:
1. open ApplicantDsl in mortgages, add the sentence in description, save
2. open RegexDslRule, use the sentence with any valid name string, save and close
3. reopen RegexDslRule

Actual results:
Error message.

Expected results:
The rule should open.

Additional info:


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