[
http://jira.jboss.com/jira/browse/JBRULES-1284?page=comments#action_12383469 ]
Justin Wick commented on JBRULES-1284:
--------------------------------------
IMHO, if this is known to be a "bad" thing to do, the compiler should at least
throw a warning saying so, if not a straight-out error. Unless, of course, the runtime
coercian could be made better.
Is there a reason runtime type coercion cannot say that literals are whatever type they
would be in Java? i.e. 50 is an integer, 50l is a long, 50.0 is a double, "50"
is a String, etc?
ClassCastException when using "<" constraint on field of
type java.lang.Object containing data of type java.lang.Integer
------------------------------------------------------------------------------------------------------------------------
Key: JBRULES-1284
URL:
http://jira.jboss.com/jira/browse/JBRULES-1284
Project: JBoss Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0.2
Environment: Windows XP, Eclipse 3.2
Reporter: Justin Wick
Assigned To: Mark Proctor
Attachments: DroolsTest.zip
If I'm doing a pattern constraint, say "< 50" on a field, and that field
is type java.lang.Object, with a value of type java.lang.Integer, a ClassCastException is
generated at run time, although there is no compile-time error saying that this is an
illegal constraint.
See attached files for an example
--
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