[
http://jira.jboss.com/jira/browse/JBRULES-1284?page=comments#action_12386768 ]
Michael Neale commented on JBRULES-1284:
----------------------------------------
As discussed - we should treat object fields as an unknown type, no hashing, just evaluate
it as needed. This will mean a performance penalty, but the only other alternative is to
defer any sort of hashing decision until we see an object, work out its type, but that is
not rigorous. If people want to use Object, they have to understand, that there is price
to pay at runtime.
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: Edson Tirelli
Priority: Blocker
Fix For: 4.0.4, 4.1.0
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