It did help on that issue, and shrunk the war by 2 megs.
Now it just fails to start with a generic ServletException with no
explaining message, and no clue in the log as to why.
Wonderful. This codebase just don't like people. :)
2007/5/8, Geert Bevin [EMAIL PROTECTED]:
You probably have
Hi Christian,
what is the stacktrace? Are sure that you didn't remove the xml
parser that your servlet container needs to parse its xml files.
Might be that this is bound to a particular version.
Take care,
Geert
On 09 May 2007, at 02:10, Christian Vest Hansen wrote:
It did help on
