Hi, Edward.
"Edward L. Knoll" <[EMAIL PROTECTED]> wrote on 2004-12-20 11:55:43
AM:
> If I'd stopped to think about it, I would not have expected to be able
> to change a result-tree-fragement into a number/integer, but the logic
> appears to work (outside the threading issues). I've included s
Empirical evidence now seems to be pointing at another possible
explanation. The Java function we are calling takes several parameters
which are either integers or strings. Template scope XSL variables
were being used to establish the values of these parameters and then
these local variable
Hi, Edward
You can open a bug in the JIRA database
(http://nagoya.apache.org/jira/secure/Dashboard.jspa).
Please attach the description here in the bug report. It might be difficult
to diagnose the problem without a testcase. If possible, please also
describe the types of the parameters, in
Spoke to soon. The incident rate dropped a lot, but the problem still
persistes.
Edward L. Knoll wrote:
Context: Xalan-J, 2.6.0; SAX transformation chain.
We were having a concurrency operation associated with a call to a
static Java method we were making from an XSL stylesheet. We
restructur
