[
http://jira.jboss.com/jira/browse/JBRULES-717?page=all ]
Edson Tirelli resolved JBRULES-717.
-----------------------------------
Fix Version/s: 3.1-m2
(was: 3.1-m1)
Resolution: Rejected
Assignee: Edson Tirelli (was: Mark Proctor)
Thomas,
Not sure if you got my mail in the mail list. The DSL functionality didn't made the
cut out date for M1. It is included in M2 (trunk). So, if you can try out trunk, let me
know if you have any problem.
M2 shall be out soon.
Thank you,
Edson
Drools 3.1.0-M1 dsl compatibility problems with 3.0.4
-----------------------------------------------------
Key: JBRULES-717
URL:
http://jira.jboss.com/jira/browse/JBRULES-717
Project: JBoss Rules
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Drl Parser/Builder
Affects Versions: 3.1-m1
Environment: windows 2k
Reporter: Thomas Gonzalez
Assigned To: Edson Tirelli
Priority: Critical
Fix For: 3.1-m2
Tom - there was some MAJOR re-work for 3.1m1 - could you put this in a JIRA - that
example, perhaps with the test code, but at least the example.
Its probably some regex-foo stuffing up and choking on the \n, no doubt. That would be
great.
On 3/2/07, Tom Gonzalez <tomgon(a)nortel.com> wrote:
We are in the process of converting from 3.0.4 to 3.1.0-M1 and having problems building
rules with a dsl that built in 3.0.4 with no problems.
We are getting rule compilation errors reporting:
String literal is not properly closed by a double-quote
The problem was isolated to the following, a dsl mapping that works in 3.0.4
[then]Log : {level} , {message}=logUtil.log ( {level} , "{message}\n"
);
We had to change it to the following to get past the compile error.
[then]Log : {level} , {message}=logUtil.log ( {level} , "{message}");
Tried to get the lf in various ways but no luck. Only way would be to modify every
message and add a LF
[then]Log : {level} , {message}=logUtil.log ( {level} , "{message}" +
"\n"); -- no good got same error.
This was not easy to find either. The error message above was not of much use.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira