Enterprise Client Community

Many of you have never been in touch with selecting the right parser on server side... this information for these ones who are.

By default CaptainCasa uses the crimson-SAX-parser even though the default parser of the java environment is another one. This is the reason why there is a crimson.jar delivered in WEB-INF/lib.

Why don't we use the default parser which is part of the java runtime from 1.5 on? ...because it has a severe bug! We could not believe it ourselves, but the result of parsing does sometimes not reflect the document that is parsed. We did isolate the error into a mini-Java program and published a message within the Xerces forums - getting back a response 3 hours after posting (!!), that Sun branched from the Xerces parsers some years ago. And: in the repsonse they did test against Xerces and checked that Xerces does not have this error. So we posted a message to Sun (3 months ago), ...well, no repsonse yet.

We also tested with crimson, which is smaller than Xerces, and crimson also is fine. So we decided for crimson.

Now, in some situations you want to explicitly define the parser on your own. We know some users who have problems with crimson.jar being around when using Spring. In this case you need to specify the parser in the configuration file /eclntjsfserver/config/system.xml. But: pay attention - do not specify the defaulf parser of the java runtime (com.sun.xerces....), this is the one with the bug. You may also remove crimson.jar completely when specifying to use an other parser.

A "nice" symptom that a wrong parser is used on server side is, that popups are shown with wrong dimensions (very small height). So, check the parser settings in this case!

Björn

...just one comment: from Release 2.5 we use Xerces as default parser, no crimson anymore...
Björn