[EMAIL PROTECTED] wrote: > I have a Java extension element that pipes a number of documents through a > series of transformations. All is working fine as long as I don't create a > constructor for this Java class. I wanted a constructor so I could > instantiate an object from main() and use this facility standalone without > making the worker routine static. I discovered that as soon as I introduce > a constructor, even an empty constructor, the implementation breaks. When > the extension element is called, it reports the stylesheet line number > where it was called and DOES NOTHING. Any ideas? > Don -- I'm a little confused here. I don't understand what's happening when you add your constructor. you said "... the implementation breaks. When the extension element is called, it reports the stylesheet line number where it was called and DOES NOTHING." Who is reporting the stylesheet line number? Do you get a stack trace? Can you include it? If you include a no-argument constructor, we will use it to create an instance of the extension element that we use to invoke it. If you don't want that to happen, make your constructor have an argument. But, I'd like to get to the bottom of what's happening with this. Does your constructor report the line number from which it was called or does the pipeDocument method or is it coming from Xalan or what? Gary
