Mantis - Resin
|
|||||
Viewing Issue Advanced Details | |||||
|
|||||
ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
2391 | minor | always | 02-01-08 21:28 | 02-13-08 11:56 | |
|
|||||
Reporter: | ckchris | Platform: | |||
Assigned To: | ferg | OS: | |||
Priority: | normal | OS Version: | |||
Status: | closed | Product Version: | 3.1.3 | ||
Product Build: | Resolution: | fixed | |||
Projection: | none | ||||
ETA: | none | Fixed in Version: | 3.1.5 | ||
|
|||||
Summary: | 0002391: Ability to specify a config parameter that will ignore unknown servlets in web.xml | ||||
Description: |
Some webapps come with extraneous servlet mapping definitions that somehow do not have the proper classes included in the classes/ or lib/ (ie. OpenBravo or Confluence, etc). These extraneous mapping definitions are normally for development or testing purposes so when a production WAR is created, the relevant classes no longer exist. Currently, Resin will not start up a webapp if it finds unknown servlets. In order to continue, one must manually remove each offending entry. This is ok if there is only 1 or 2 or 3. But if there are over 50 of them, the process is quite tedious. I propose an additional config parameter under <web-app> where one can specify to bypass/ignore unknown servlet. Something like <web-app> <ignore-unknown-servlets>true</ignore-unknown_servlets> </web-app> |
||||
Steps To Reproduce: | |||||
Additional Information: | |||||
Relationships | |||||
Attached Files: |
Notes | |||||
|
|||||
|
|