Re: Throwing EvaluationException slows down evaluation, proposed change: not fill stack trace

2019-01-04 Thread kiwiwings
Based on my experience, that setting system properties in web applications involves discussions with the web admins, I don't like system properties at all. Although [1] says the opposite, I guess (but haven't tried) that context-param aren't automatically set as system properties. Is [1] true

Re: Throwing EvaluationException slows down evaluation, proposed change: not fill stack trace

2019-01-04 Thread Dominik Stadler
Hi, I would stick to system properties, it is the easiest to implement and as the feature is something that only few will be concerned with, it can be non-obvious that this is possible. Dominik. On Mon, Dec 17, 2018 at 3:48 PM pj.fanning wrote: > For me, this kind of optimisation needs to be

Re: Throwing EvaluationException slows down evaluation, proposed change: not fill stack trace

2018-12-17 Thread pj.fanning
For me, this kind of optimisation needs to be configurable. Most users would not need this performance optimisation and would be better off to get the full stack trace. I would pitch that something like XmlOptions in the XMLBeans project is a useful model. This allows users to choose to override

Re: Throwing EvaluationException slows down evaluation, proposed change: not fill stack trace

2018-12-17 Thread gallon . fizik
fixes: 1. *6+ times higer 2. Perhaps even the error message can be omitted because one can get it from the stored ErrorEval. - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: