TJWS Changelog

What's new in TJWS 1.1111

Mar 20, 2015
  • nohup option
  • getSession() never null fix pointed by Warren E. Downs
  • messed sessions fix when browser sends more than one session cookies
  • session persistence between server re-runs (here are some issues when classes loaded under WEB-INF/..)
  • fixes realm not got applied to servlets, hanging when accessed reserved device, like con:, prt: pointed by users (Niel Markwick, and others)
  • added J2EE web app deployment and JSP support (JASPER) as a separate module
  • support of filters and listeners, requested by Argan
  • keep-alive support, requested by Torben Bruun
  • err option to keep System.err unchanged or customize it, requested by Xavier
  • many keep-alive fixes came from Martin Egholm Nielsen
  • fixes in web app servlet most reported by Nicolas Prochazka
  • supporting HTTP and HTTPS transports in the same instance
  • exit out of serve() by Andr� Kischkel
  • thread pooling for servicing requests
  • unavailable, and path pattern related fixes
  • web app launcher including embedded .war
  • JSP engine with spec 2.0/2.1 support as Japser
  • filter for include, forward, and error. Multiple URL patterns
  • HTTP Range request support for file servlet
  • added Response Buffer and Request Dispatcher support in base server
  • flexible support of server sockets including Selector based
  • default log directory by Italia Roberto
  • compression of text content by file servlet
  • stronger security for session id
  • fix: not eating unconsumed part of input stream for keep-alive connection (reported by Bill Burke@redhat)
  • dynamic redeploy advised by poll results
  • data sources and connection pooling advised by poll results
  • missed processing of charset in POST request pointed by Jack
  • virtual host by ganesan
  • closing all connections at stop requestedd by Weinan Li@redhat
  • JSR 315 Comet support requested by Ivan Voronov
  • Base server vulnerability related directory transversal using '..' pointed by Jo�o Sampaio
  • Android compatibility of war deployment requested by Alex Xin
  • Adjustung behavior matching to servlet specification done by Andreas
  • Using servlets mapping URL patterns matching to servlet specification including extensions mapping, by Bruno B
  • Accurate handling keep allive by Andreas
  • Proper freeing resources in CGI servlet by Frank
  • SSL handler default class updated by Jan
  • Reliable detection of chunked encoding by Darren
  • JSR 356 (websocket) by Robert

New in TJWS 1.109 (Feb 20, 2015)

  • JSR (websocket) by Robert

New in TJWS 1.107 (Dec 6, 2014)

  • nohup option
  • getSession() never null fix pointed by Warren E. Downs
  • messed sessions fix when browser sends more than one session cookies
  • session persistence between server re-runs (here are some issues when classes loaded under WEB-INF/..)
  • fixes realm not got applied to servlets, hanging when accessed reserved device, like con:, prt: pointed by users (Niel Markwick, and others)
  • added J2EE web app deployment and JSP support (JASPER) as a separate module
  • support of filters and listeners, requested by Argan
  • keep-alive support, requested by Torben Bruun
  • err option to keep System.err unchanged or customize it, requested by Xavier
  • many keep-alive fixes came from Martin Egholm Nielsen
  • fixes in web app servlet most reported by Nicolas Prochazka
  • supporting HTTP and HTTPS transports in the same instance
  • exit out of serve() by Andr� Kischkel
  • thread pooling for servicing requests
  • unavailable, and path pattern related fixes
  • web app launcher including embedded .war
  • JSP engine with spec 2.0/2.1 support as Japser
  • filter for include, forward, and error. Multiple URL patterns
  • HTTP Range request support for file servlet
  • added Response Buffer and Request Dispatcher support in base server
  • flexible support of server sockets including Selector based
  • default log directory by Italia Roberto
  • compression of text content by file servlet
  • stronger security for session id
  • fix: not eating unconsumed part of input stream for keep-alive connection (reported by Bill Burke@redhat)
  • dynamic redeploy advised by poll results
  • data sources and connection pooling advised by poll results
  • missed processing of charset in POST request pointed by Jack
  • virtual host by ganesan
  • closing all connections at stop requestedd by Weinan Li@redhat
  • JSR 315 Comet support requested by Ivan Voronov
  • Base server vulnerability related directory transversal using '..' pointed by Jo�o Sampaio
  • Android compatibility of war deployment requested by Alex Xin
  • Adjustung behavior matching to servlet specification done by Andreas
  • Using servlets mapping URL patterns matching to servlet specification including extensions mapping, by Bruno B
  • Accurate handling keep allive by Andreas
  • Proper freeing resources in CGI servlet by Frank
  • SSL handler default class updated by Jan
  • Reliable detection of chunked encoding by Darren

New in TJWS 1.106 (May 22, 2014)

  • Several bugs and security improvements.

New in TJWS 1.102 (Apr 6, 2013)

  • Updated SSL acceptor to use newer JSSE spec
  • Updated Jasper patch to 7.0.37
  • JDBC driver can be loaded from application class path
  • More robust way to close connections at destroying app connection pool
  • Added DLNA headers processing in file servlet
  • Added log rolling feature
  • If async request get closed in starting thread, no new thread spawn

New in TJWS 1.100 (Jan 3, 2013)

  • Reordered operations at destroy
  • Added change port in launcher

New in TJWS 1.99 (Sep 17, 2012)

  • Consider all attributes of context.xml as optional but url
  • Freeing resources in CGI servlet after processing
  • Corrected CGI servlet mapping
  • Added session tracking parameters and nodes for JSS 3.0
  • Added secure only session cookie option
  • Auto deploy directory location can be customized by overriding
  • WarRoller method
  • Fixed problem preventing using javamelody monitoring filter
  • Fixed regression issued by session listeners cleanup

New in TJWS 1.93 (Sep 30, 2011)

  • GNU JSP provider is now default JSP provider and any version of Jasper from 5 to 7 can be used for excessive JSP support.

New in TJWS 1.83 (Jul 23, 2011)

  • This release includes about 10 bug fixes and enhancements provided by individual contributors.
  • Another set of changes includes adopting Android platform and discarding GJT JSP engine Although it was small and working, it was generally not useful, so didn't bring any value to TJWS.
  • GNU JSP provider is now default JSP provider and any version of Jasper from 5 to 7 can be used for excessive JSP support.
  • Service support for Windows obtains 64-bit version.

New in TJWS 1.81 (Oct 26, 2010)

  • The release contains minor code improvement.
  • Perhaps next release will be greater and introduces clustering configuration.

New in TJWS 1.80a (Jul 29, 2010)

  • Among other changes are security updates and code refactoring.
  • The release also contains resource clean up at exit requested my JBOSS QA team.

New in TJWS 1.80 (Jul 27, 2010)

  • This release adds some valuable features from servlet specification 3.0.
  • Core TJWS still keeps compatibility with servlet specification 2.3 and JDK 1.4.2
  • or personal profile 1.1. However J2EE extension utilizes most of JSR 315.
  • Asynchronous requests handling and multi pats processing are major supported
  • items of the new specification.
  • Among other changes are security updates and code refactoring.
  • The release also contains resource clean up at exit requested my JBOSS QA team.

New in TJWS 1.71 (Mar 24, 2010)

  • Usage of TJWS in data center environment for SaS.
  • Service usage under Windows system was improved, however the service executable
  • lost capability to run under Windows 2000. It is still 32bit version, since I have
  • no access to 64 bit systems.
  • Added virtual hosting support.

New in TJWS 1.60 (Sep 10, 2009)

  • Accurate determination post form content type when charset is used
  • Applied context path to session cookie
  • Added define to specify an application deployed in root context