Qwicap / News: Recent posts

Qwicap is a Java web application development API that discards the traditional hit-run-exit CGI model, automatically and transparently provides rich state, and supplies a powerful, extremely easy-to-use XML engine for "templating" tasks in order to avoid mixing code and content. It builds on Servlet, XHTML and CSS technologies. 

Qwicap version 1.4b25 adds new methods to the Form and FormDataSet classes, and updates the internal Table library.

Qwicap is a Java web application development API that discards the traditional hit-run-exit CGI model, automatically and transparently provides rich state, and supplies a powerful, extremely easy-to-use XML engine for "templating" tasks in order to avoid mixing code and content. It builds on Servlet, XHTML and CSS technologies. 

Qwicap version 1.4b24 upgrades the Table library; adds missing Javadocs; adds the FormControlValue.setValues, FormDataSet.setData, and Form.getDataSet methods; and modifies the code to make more efficient use of the Table library.... read more

Qwicap is a Java web application development API that discards the traditional hit-run-exit CGI model, automatically and transparently provides rich state, and supplies a powerful, extremely easy-to-use XML engine for "templating" tasks in order to avoid mixing code and content. It builds on Servlet, XHTML and CSS technologies. 

Qwicap version 1.4b23 corrects a bug that could prevent some form data sets from being read completely, corrects floating-point precision related bugs in the Qwicap.getFloat and Qwicap.getDouble methods, replaces most internal uses of CSS pattern strings with pre-compiled, static CSSPatterns objects, adds the missing Match.get(CSSPatterns) method, removes some obsolete code, and improves some logging messages.

Qwicap is a Java web application development API that discards the traditional hit-run-exit CGI model, automatically and transparently provides rich state, and supplies a powerful, extremely easy-to-use XML engine for "templating" tasks in order to avoid mixing code and content. It builds on Servlet, XHTML and CSS technologies. 

Qwicap version 1.4b22 corrects bugs related to handling XML markup in a namespace-aware manner, improves handling of namespaces in CSS selectors, allows CSS attribute selectors to be namespace-aware, removes an obscure bug that could produce a NullPointerException when the "Match.getText" method was invoked, adds new Javadocs and improves existing Javadocs, and adds more unit tests.

Qwicap is a Java web application development API that discards the traditional hit-run-exit CGI model, automatically and transparently provides rich state, and supplies a powerful, extremely easy-to-use XML engine for "templating" tasks in order to avoid mixing code and content. It builds on Servlet, XHTML and CSS technologies. 

Qwicap version 1.4b21 deals with two issues that caused memory leaks, two issues that caused problems when rejecting bad user input, and makes a few small improvements.

Qwicap is a Java web application development API that discards the traditional hit-run-exit CGI model, automatically and transparently provides rich state, and supplies a powerful, extremely easy-to-use XML engine for "templating" tasks in order to avoid mixing code and content. It builds on Servlet, XHTML and CSS technologies.

Qwicap 1.4b20 avoids some potential errors in the class pre-loading process, improves the implementation of the private geti18nServices method in the Results and SmartStringConverter classes, and makes minor improvements to some log messages and Javadoc.... read more

Qwicap is a Java web application development API that discards the traditional hit-run-exit CGI model, automatically and transparently provides rich state, and supplies a powerful, extremely easy-to-use XML engine for "templating" tasks in order to avoid mixing code and content. It builds on Servlet, XHTML and CSS technologies.

Qwicap 1.4b18 corrects a bug in the status reports returned by the Qwicap.getStatusReport method.

Qwicap is a Java web application development API that discards the traditional hit-run-exit CGI model, automatically and transparently provides rich state, and supplies a powerful, extremely easy-to-use XML engine for "templating" tasks in order to avoid mixing code and content. It builds on Servlet, XHTML and CSS technologies.

Qwicap 1.4b17 better handles IOExceptions when transmitting pages to clients, ensures that AJAX commands are not processed when AJAX support is disabled, supplies the missing Results.getDeclarations method, adds implementation of the Iterable interface to all classes that supported enumeration, upgrades the Table library, improves the formatting of status reports, improves the Javadocs, makes the Ant build script more generic, and includes Eclipse project files.

Qwicap is a Java web application development API that discards the traditional hit-run-exit CGI model, automatically and transparently provides rich state, and supplies a powerful, extremely easy-to-use XML engine for "templating" tasks in order to avoid mixing code and content. It builds on Servlet, XHTML and CSS technologies.

Qwicap 1.4b16 corrects bugs in the file upload code, incorporates the Apache Commons File Upload library (version 1.2.1) as a JAR, and updates the associated Apache Commons I/O library JAR to version 1.4.... read more

Qwicap is a Java web application development API that discards the traditional hit-run-exit CGI model, automatically and transparently provides rich state, and supplies a powerful, extremely easy-to-use XML engine for "templating" tasks in order to avoid mixing code and content. It builds on Servlet, XHTML and CSS technologies. 

Qwicap 1.4b15 further fine-tunes the log messages associated with thread pool destruction, including the addition of a final report of any daemon threads that have resisted Qwicap's effort to persuade them to exit; and modifies the method "QwicapAbandonmentException.rethrowIfThisPageWasAbandoned(Throwable)" such that it will rethrow QwicapSessionDeathException and QwicapSessionWillNotDieError, in addition to the various "abandonment" exceptions that it has always rethrown (when appropriate).

Qwicap is a Java web application development API that discards the traditional hit-run-exit CGI model, automatically and transparently provides rich state, and supplies a powerful, extremely easy-to-use XML engine for "templating" tasks in order to avoid mixing code and content. It builds on Servlet, XHTML and CSS technologies.

Qwicap 1.4b14 modifies the MutableMarkup class to omit redundant XML declarations from insert operations; improves a number of logging operations; and interrupts any lingering threads in a Qwicap application's thread group after its thread pool is destroyed.... read more

Qwicap is a Java web application development API that discards the traditional hit-run-exit CGI model, automatically and transparently provides rich state, and supplies a powerful, extremely easy-to-use XML engine for "templating" tasks in order to avoid mixing code and content. It builds on Servlet, XHTML and CSS technologies.   

Qwicap version 1.4b13 addresses bugs in the servlet destruction process; works-around ClassLoader bugs during application redeployment in Tomcat; brings Qwicap into full compliance with the OWASP Top 10 security guidelines (2007 edition); transparently handles redundant form data set submissions caused by users double-clicking "submit" buttons; automatically provides user-friendly notification of attempts to interact with expired sessions, and of the abnormal termination of sessions; extends the XML engine to allow the manipulation of the contents of comments, declarations and CDATA sections; improves the functionality and compatibility of the experimental, AJAX-based page navigation features; increases logging; provides new build features; improves and extends the Javadocs; and provides a host of other improvements.

Qwicap is a Java web application development API that discards the traditional hit-run-exit CGI model, automatically provides rich state, and supplies a powerful, extremely easy-to-use XML "templating" engine to avoid mixing code and content. It builds on Servlet, XHTML and CSS technologies.  

Qwicap version 1.4b12 of 20-Nov-2007 restores the status report functionality that 1.4b11 disabled, and also corrects a bug in the Results and MutableMarkup classes that would cause an exception to be thrown in some cases when they were used outside of the context of a Qwicap web application.... read more

Qwicap is a Java web application development API that discards the traditional hit-run-exit CGI model, automatically provides rich state, and supplies a powerful, extremely easy-to-use XML "templating" engine to avoid mixing code and content. It builds on Servlet, XHTML and CSS technologies.

Qwicap version 1.4b11 of 12-Nov-2007 embraces Java 1.5, provides Qwicap's first support for internationalization and localization, and makes Qwicap applications able to run both directly from their WARs, and within the default constraints of the Security Manager.... read more

Qwicap is a Java web application development API that discards the traditional hit-run-exit CGI model, automatically provides rich state, and supplies a powerful, extremely easy-to-use XML "templating" engine to avoid mixing code and content. It builds on Servlet, XHTML and CSS technologies.  

Qwicap version 1.4b10 of 15-June-2007 expands the functionality of, and corrects bugs in, the automatic character set detection features added in version 1.04b9. It also corrects a bug in the new "destroy this session" feature of the authentication & authorization interface. Also, the amount of information logged for each hit has been greatly increased.

Qwicap is a Java web application development API that discards the traditional hit-run-exit CGI model, automatically provides rich state, and supplies a powerful, extremely easy-to-use XML "templating" engine to avoid mixing code and content. It builds on Servlet, XHTML and CSS technologies.  

Qwicap version 1.4b9 adds character-set awareness to the classes that read and write XML and XHTML. Because no announcements of the releases of versions 1.4b7 and 1.4b8 were made, it is also worth noting that logging has been added to the Qwicap.reportException method, so you can learn about an exception even if it incapacitates the web application, and the messages in exceptions thrown by the MutableMarkup class have been made more informative.

Qwicap is a Java web application development API that discards the traditional hit-run-exit CGI model, automatically provides rich state, and supplies a powerful, extremely easy-to-use XML "templating" engine to avoid mixing code and content. It builds on Servlet, XHTML and CSS technologies.

Qwicap 1.4b6 fixes no bugs that impact Qwicap, but does fix one bug in code which Qwicap doesn't use, and makes some very minor adjustments to the web pages of the example applications.

Qwicap is a Java web application development API that discards the traditional hit-run-exit CGI model, automatically provides rich state, and supplies a powerful, extremely easy-to-use XML "templating" engine to avoid mixing code and content. It builds on Servlet, XHTML and CSS technologies.

Qwicap 1.4b5 eliminates a case in which the QwicapServlet class could generate an IllegalArgumentException by invoking the HttpSerlvetResponse.sendError method.

Qwicap is a Java web application development API that discards the traditional hit-run-exit CGI model, automatically provides rich state, and supplies a powerful, extremely easy-to-use XML "templating" engine to avoid mixing code and content. It builds on Servlet, XHTML and CSS technologies. 

Qwicap 1.4b4 corrects a stupid bug that prevented Qwicap's SecureRandom service provider from being accessed. It also corrects a related mistake in the associated Javadocs.

Qwicap is a Java web application development API that discards the traditional hit-run-exit CGI model, automatically provides rich state, and supplies a powerful, extremely easy-to-use XML "templating" engine to avoid mixing code and content. It builds on Servlet, XHTML and CSS technologies.

Qwicap version 1.4b3 corrects a NullPointerException that was introduced in version 1.4b2, and allows the creation of SecureRandom instances based on Qwicap's internal "Rule 30" pseudo-random number generator.

Qwicap is a Java web application development API that discards the traditional hit-run-exit CGI model, provides rich state, and a powerful, extremely easy-to-use XML "templating" engine to avoid mixing code and content. It builds on Servlet, XHTML and CSS technologies.

Qwicap 1.4b2 allows application servers to use Qwicap as a shared library, improves the FormDataSetFilter and BlockingListener systems, adds a backup mechanism for forcing uncooperative client applications to die, removes some deprecated antiques, deprecates some sub-optimal hold-overs from old versions, replaces the Qwicap.prompt(MutableMarkup, PromptFlags) method with the more elegant Qwicap.prompt method, adds the Qwicap.showPage method, corrects a bug that could cause "bad input" loops, corrects a number of other bugs, adds convenience methods to various classes, and improves the Javadoc.

Qwicap version 1.4b1 includes a more flexible, rearchitected authentication and authorization system, includes cleaner core code wherever the code became involved with Servlet life-cycles, futher simplifies web application deployment descriptors, adds three convenience methods to the Results class, and includes numerous improvements to the Javadocs.

Qwicap 1.4b0 corrects a bug that may have interfered with Tomcat shutdown, and a bug that caused newline characters within HTML "textarea" tags to be encoded. In addition, it simplifies web application setup by eliminating the requirement to include the "qwicap.css" style sheet in web applications, and, for convenience, it provides access to Qwicap's internal pseudo-random number generator.

Qwicap 1.4a42 fixes a thread synchronization bug, adds a thread pool, adds a status reporting system, adds "blocking listeners", and includes various internal improvements.

Qwicap 1.4a37 fixes a bug associated with clients prematurely closing their HTTP connections, corrects a synchronization problem, and provides a more flexible means of specifying the details of page behavior to the "Qwicap.prompt" method.