Releases: Novartis/YADA
8.4.0 HyperSQL support
This release includes a HyperSQL adaptor, and an updated installer which deploys HyperSQL, rather than SQLite. Additionally, jdbc connection pools are now closed when apps (data sources) are deactivated through the yada-admin ui.
8.3.0: Ease of Use
new YADA-Quickstart installer executable jar
Validated on Java 8
Validated on Tomcat 8
Patched security hole created by saving a default plugin without a plugin class name
Automated test db drop/reload using exec-maven-plugin
Log verbosity reduction (moved some WARN level statements to DEBUG)
Addtional code style fixes and minor refactoring
Many bug fixes and improvements in yada-admin including:
- broke out menu bar into separate flightjs component
- added handlers for enabling/disabling each menu including unbinding of click handlers and removal of href attributes (formerly, "disabled" buttons with links were still clickable)
- added static backdrop attribute to all modals to prevent errant dismissal
Automated UI testing of yada-admin using Selenium including:
- Firefox and Chrome (OS X)
- login with known credentials
- create multiple apps
- validate menubar functionality
- create query and cancel
- create query and save
- edit query: mark query as protected
- edit query: add security config
Bug Fixes:
- Fixed bug preventing multiple default (query-level) plugins from being attached to a query and executed
- Fixed bug failing to update server cache after change to security property settings (i.e., mark this query as secure checkbox)
- Fixed bug which removed security policy UI and never restored it when a query creation task was cancelled prior to saving or editing any query
- Fixed bug causing server cache updates to fail when passing param properties as targets (e.g., FOO qname-1)
See the Deployment Guide and the Admin Guide for more info.
8.2.1
- Fixed bug requiring server restart to establish connection pool for newly created app. Connection pools should now be instantiated upon first qname request for new app.
- Enabled comments in JDBC datasource configs
- This release tested successfully on Tomcat 8.x as well.
8.2.0
8.1.1
8.1.0 yada-admin tool security
8.1.0 builds upon the previous release by attaching YADA security configurations to all YADA queries utilized by the yada-admin webapp.
Additionally, dependency injection is now supported for Execution Policies, enabling arbitrary server-originating values to be used as gatekeeping criteria for query execution authorization. Previously, only the validated token could be used as criteria. Now, for example, a secure user id, validated header or cookie, or token, could be used. Plus, a value passed to a protected query can be assigned to a differently named field used by its protector.
8.0.0 Container-independent, Dynamic Connection Pools
YADA 8.0.0 represents a major leap forward.
YADA now supports container-independent, dynamically configured JDBC connection pools.
Previously, YADA required Tomcat. It required static configuration of datasources using Tomcat's JNDI implementation, and it required Tomcat to be restarted when adding a new datasource.
Those days are over.
With HakariCP and a new user interface in the yada-admin web app, YADA now enables the creation of connection pools at runtime without restarting your container-or as I like to put it, YADA now supports no-bounce mounts!
For more details about how to utilize this feature, see the documentation, in particular, the Admin Guide.
7.1.4
7.1.3
7.1.2
Restores fallback functionality for some unparsable queries. Specifically, when JSqlParser fails to parse a query (as it can with some uncommon or convoluted nesting and join strategies,) YADA will fallback to setting JDBC positional parameters by analyzing the data passed in the request.