[
http://jira.jboss.com/jira/browse/JBRULES-261?page=comments#action_12352810 ]
Michael Neale commented on JBRULES-261:
---------------------------------------
defaintely automatic. We don't want to be as rigid with types as java is.
Of course, if there is any "loss" of data resolution, that is a problem, but if
there is not, then automatic is good.
Mismatched types in field constraints
-------------------------------------
Key: JBRULES-261
URL:
http://jira.jboss.com/jira/browse/JBRULES-261
Project: JBoss Rules
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rule Assemply/SPI
Affects Versions: 3.0.1
Reporter: Michael Neale
Assigned To: Mark Proctor
Priority: Minor
Fix For: 3.1-m2
Problem: If a rule compares two fields and one of them is a char and the
other one is a String, the match is always negative. No type-mismatch error
or warning is displayed. This can be quite confusing. The attached Eclipse
project illustrates this problem.
Suggested Solution: If all information is available at compile-time an error
should be generated on type mismatches. Otherwise there should be a warning
during run-time and maybe a type conversion attempt.
--
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