Changelog1_4_x

1.4.3 - August 30, 2014

• Add a no-op marker interface (ch.ralscha.extdirectspring.ExtDirectSpring) to introduce a type-safe way to configure an extdirectspring application with ComponentScan#basePackageClasses
  Example with Spring Boot

@Configuration @ComponentScan(basePackageClasses = { ExtDirectSpring.class, Main.class }) @EnableAutoConfiguration public class Main {

 
- Support for @CookieValue method parameter annotation. The library extracts the cookie value and sets the parameter value. Behaves the same way as in spring-mvc

- Add a getOperator() method to the Filter class. In Ext JS 5 _comparison_ is now called _operator_.

- Add a new field _rawConversion_ to the filter classes. 
This field contains the raw value of the comparison (extjs4) / operator (extjs5) property from the request. The _conversion_ field still contains 
the mapped Conversion enum value. But the library no longer throws an exception when the client sends an unknown operation/conversion parameter. 
In this case _rawConversion_ contains the value the client sent and _conversion_ is null.

- Filter changes for Ext JS 5. This version no longer sends a type information. So we have to rely on type autodetection to figure out which Filter 
instance to create. This was already implemented for String-, Boolean- and NumericFilter. This change adds support for the missing ListFilter. When the value is of type List a ListFilter is created. The ListFilter is now generic and is no longer limited to String elements. For instance it's now possible to send a list of numbers


## 1.4.2 - July 20, 2014
- [Issue #128](https://github.com/ralscha/extdirectspring/issues/128)  
Convert MethodInfoCache and ApiCache singleton classes to Spring beans
 
- [Issue #129](https://github.com/ralscha/extdirectspring/issues/129)  
Add support for 'number' in Filter.createFilter

- [Issue #130](https://github.com/ralscha/extdirectspring/issues/130)  
Move getComparison() method to the base Filter class

- [Issue #131](https://github.com/ralscha/extdirectspring/issues/131)  
Support null values in BooleanFilter


## 1.4.1 - March 31, 2014
- [Issue #123](https://github.com/ralscha/extdirectspring/issues/123)
- [Issue #99](https://github.com/ralscha/extdirectspring/issues/99)

## 1.4.0 - December 31, 2013

- [Issue #119](https://github.com/ralscha/extdirectspring/issues/119)   
Extracted the Ext Model Generator and moved the code into it's own project https://github.com/ralscha/extclassgenerator.    
  See also the corresponding issue [Issue #65](https://github.com/ralscha/extdirectspring/issues/65)
  and the [migration guide](https://github.com/ralscha/extclassgenerator/wiki/Migration)

- [Issue #117](https://github.com/ralscha/extdirectspring/issues/117)   
Removed deprecated classes

- [Issue #118](https://github.com/ralscha/extdirectspring/issues/118)  
Minimum requirement for version 1.4.x are Spring 4, Servlet 3 (JEE 6) and Java 6

- [Issue #120](https://github.com/ralscha/extdirectspring/issues/120)   
When the client sends a filter request that only contains a property but no value (`{filter:[{property:"name"}]}`) the library now creates 
a StringFilter instance with a null value. In older versions a null element was added to the filters collection.  

- [Issue #121](https://github.com/ralscha/extdirectspring/issues/121)  
Removed Vary header in the ExtDirectSpringUtils.addCacheHeaders method

- [Issue #122](https://github.com/ralscha/extdirectspring/issues/122)  
Added apiNS, actionNs, remotingApiVar, pollingUrlsVar, sseVar, fullRouterUrl and baseRouterUrl to the [Configuration](http://rasc.ch/eds/apidocs/ch/ralscha/extdirectspring/controller/Configuration.html) class.