...
- #18166 - Batch processing of POST/Create requests. JDBC inserts are now batched instead of performing individual inserts.
- Logging improvements
- KIOSK mode - when no configuration.xml is defined, the KIOSK mode kicks in pre-loading BIRT (ClassicModels?) and myStore QuerySets? with with in-memory Derby databases. This will make it very easy to try out the DBConnector.
- #19243 - JSON payload now supported from business rules when performing POSTs and PUTs.
- #20546 - Query statements are validated when the DB Connector starts instead of when used.
- Console prints the DB Connector version and revision number.
- #18620 - Generating max-length for SQL Server NVARCHAR
- #20532 - Ability to disable QuerySets and/or Querys while developing your integration.
- #18708, #18676 - Returns blank or null in the JSON results for columns that have blank or null values..
- The WAR is now executable - there is the option to either deploy the WAR in an existing Servlet Container or simply run the WAR in standalone mode (with java -jar dbconnector.war).
- The SQL Server JDBC driver is now open source and included in the WAR
- QuerySet and Query names only allow alphanumeric, dot, dash, and underline characters and it can only start with letters - this makes sure that they are automatically XML and JSON friendly.
- The driver and validationQuery attributes in <resource-def> are now optional: they will be properly inferred based on the current database.
- The configuration.xml file is automatically picked up from the current directory where the DB Connector was launched or from ./config/configuration.xml. It can be manually set by using the frevvo.connectors.database.configuration property as before. This is specially useful when running the DB Connector standalone.
- #9564 - Ability to generate schemas for all queries in a queryset. This makes it possible to download a single XSD for all queries at once.
...