Issue 8 in expressionoasis: Support for Integer Type Operand in GTEExpression

[express...@googlecode.com]

Status: New
Owner: mohit.gu...@vedantatree.com
Labels: Type-Defect Priority-Medium

New issue 8 by mohit.gu...@vedantatree.com: Support for Integer Type
Operand in GTEExpression
http://code.google.com/p/expressionoasis/issues/detail?id=8

What steps will reproduce the problem?
1. Use case involve an expression, with Property Expression where property
is of Integer type
2. As GTEExpression is currently working for Long only, it is failing here
3. What is the solution, should user extend the GTEExpression and use it in
config.xml?



--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[express...@googlecode.com]

Comment #1 on issue 8 by mohit.gu...@vedantatree.com: Support for Integer

Type Operand in GTEExpression
http://code.google.com/p/expressionoasis/issues/detail?id=8

This case can happen only in case of PropertyExpression evaluation where
any Property can be of Integer, Short etc. In normal expression string
parsing, the number will always be taken as of Long type.

Now, although extending the class and specify extended class in config is
one possible solution.

Another solution could be to modify Property Expression to upgrade the type
to widest type in same category, i.e.

Byte, Short, Integer, Long > Long
Character, String > Character

Adding more type mappings in expression is feasible, but implementation
would be same for these different types, with the addition of few more
checks

Any inputs, any impact on result..?

[express...@googlecode.com]

Updates:
Status: Done

Comment #2 on issue 8 by mohitgupta.ynr: Support for Integer Type Operand
in GTEExpression
http://code.google.com/p/expressionoasis/issues/detail?id=8

No code change was required. Decision was that expression can be extended
for any new desired type mapping.