Orbeon Forms Java stack traces are very long. Does that mean that performance is necessarily bad?
Java stack traces are indeed very long in Orbeon Forms. This is due mainly to the nature of XPL pipelines, which are implemented on top of the event-based SAX API.In reality you cannot make any reasonable conclusion about performance just by looking at the length of a typical stack trace: you would have in addition to that to look at the pattern of execution of those methods. For example, if every top-level method call was going through, say, 300 levels of method calls, this would likely be an issue, but it is not the case in Orbeon Forms. The bottom line is that no, the length of a stack trace does not directly correlate with poor performance.To reach valid conclusions about performance, run a tool like Apache JMeter on your application.
Java stack traces are indeed very long in Orbeon Forms. This is due mainly to the nature of XPL pipelines, which are implemented on top of the event-based SAX API. In reality you cannot make any reasonable conclusion about performance just by looking at the length of a typical stack trace: you would have in addition to that to look at the pattern of execution of those methods. For example, if every top-level method call was going through, say, 300 levels of method calls, this would likely be an issue, but it is not the case in Orbeon Forms. The bottom line is that no, the length of a stack trace does not directly correlate with poor performance. To reach valid conclusions about performance, run a tool like Apache JMeter on your application.
