Awake SQL 1.3.1 released: now shipping with an embedded web server
The Awake SQL Web Server is a version of Awake SQL that embeds it's own JavaEE servlet container in order to run Awake SQL
Community Edition and Awake SQL Enterprise Edition server side without any
JavaEE servlet container. Awake SQL Web Server consists of one unique Java jar.
- Fast Awake SQL installation on the server side with one unique jar to deploy.
- Fast environment setup: there is no need to setup a dedicated Tomcat or JavaEE container to run Awake SQL on the server side. Only Java is required.
- Easy setup of new Awake SQL server instances: just run the Awake SQL Web Server jar with another port and new configuration file and the new instance is up.
The embedded Java EE servlet container is Tomcat 7 and we allow all configuration options. No Tomcat expertise is required in order to configure and use the Awake SQL Web Server. In some cases you may be required to read portions of the Tomcat 7 user documentation.
Other new feature in v1.3.1: Tomcat JDBC Connection Pool
The default connection pool implementation is now the Tomcat JDBC Connection Pool. It's embedded in Awake SQL and works with other non-Tomcat servlet containers. (Our previous home made connection pool implementation has now been deprecated.)
About Awake SQL
Awake SQL combines a virtual JDBC Driver and a framework to enable remote JDBC access over HTTP. Android and Java Desktop application developers can easily access remote SQL databases in the cloud just by including standard JDBC calls in their code, just like they would for a locally hosted database. Awake SQL comes with a complete set of features: main data types are implemented, including BLOBs/CLOBs, and transactions are supported.
Fore more info, please visit http://www.awake-sql.org.
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)