Yes, it will be tricky, to say the least! I'll do what I can to try to isolate it. It calls custom Java extension functions that wouldn't be useful (or executable) outside of our environment, as they make calls to local web services. If we can narrow it down to something specific, I'll pass on any additional information. In the interim, I think you're on the right track in that *something* changed since 2.3.1 in the caching/iterator behavior, perhaps as part of some of the DTM optimization attempts?
Rick Bullotta CTO Lighthammer Software (www.lighthammer.com) -----Original Message----- From: Joseph Kesselman/CAM/Lotus [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 10, 2002 2:08 PM To: [EMAIL PROTECTED] Subject: Re: Critical Xalan 2.3.X Error in testing... First thought: Hard to diagnose without seeing a sample of the problem. Can you come up with a minimal set of sample files that provokes this error, and post a bugzilla report?
