Originally by
We have done quite a lot of changes to servlet level recently so there may be some incompatibilities. Jani did this extensively last spring, but it ought to be done again before release.
See for example
http://forum.itmill.com/posts/list/591.page
The issue discussed there fixed in [6240], but there may be different problems!
Test list (from earlier compatibility list:
- Apache Tomcat, version 5.0 and later
- OK with common developer testing
- Version 4.1 also works, supports servlet spec 2.3 and java5
- BEA WebLogic Server, version 8.1 and later
- 8.x not working as tested earlier (java 1.4)
- 9.2 and 10.3 tested to work on testserver
- IBM WebSphere Application Server, version 5.1 and later
- Toolkit 5.3 only works 6.1 onwards (java 1.5 support)
- the war built by project ant script fails to load to webSphere due dual jar files exists.
- verified to work with AddressBook war (from the tutorial project)
- JBoss Application Server, version 3.2.7 and later
- 3.2.8.SP1 works ok
- couldn't launch 3.2.7 (server desc files missing in the downloaded package)
- Jetty, version 5 and later
- OK with common developer testing
- Oracle Application Server, since version 9i
- oracle application server as this is discontinued, so dropping from list is not that bad option ?
- couldn't start installation on test server. Would need an older test server.
- Sun Java Systems Application Server, since version 7
- couldn't easily find any demo/trial version (bundled with IDEs dl list) In our test server (debian) it is hard to install those due unmet library dependencies. Would need an older RedHat or something.
- Glassfish 2.1 ~ application server 9, so we can fairly safe assume that Toolkit works at least version 9 and up
- also the commercial version is nowdays branded glassfish
- Suggestion: drop official support for all non Glassfish branded sun application servers.
- Glassfish 3
- tested with demo package war on rnd test server, works flawlessly
- Glassfish 2
- works ok
该提问来源于开源项目：vaadin/framework
