Unsurprisingly, the new deployer breaks the axis tests that attempt to
set up a web application in code. On the other hand, the new deployer
should make it possible to directly deploy axis servlet(s) for pojo web
services.
should I:
1. merge to trunk now and disable axis tests
2. rewrite the axis deployment code on the branch and then merge
thanks
david jencks
On Dec 6, 2004, at 10:22 PM, David Jencks wrote:
The djencks/jetty-deployer1/trunk branch is basically working
perfectly so I plan to merge it back to trunk shortly.
missing features:
1. default locale configs. These can be specified in web.xml but
there aren't any defaults like jetty has in default-web.xml yet. Are
these actually useful?
2. default filters work but they are automatically mapped to /*. The
default filter mapping isn't quite done.
could be improved:
I think we should merge JettyWebAppJACCContext into JettyWebAppContext
and make whether the security interceptors are added dependent on
configuration.
thanks
david jencks
