First off, you probably want the xalan-dev list, not this xerces-j-dev list.
Secondly, the behavior is as designed. When you get the newTransformer(...), the stylesheet is parsed, the xsl:include, etc. are resolved, and the Transformer is built into memory. *Then* you set the URIResolver into the already-built Transformer - but the stylesheet has already been fully processed into memory. As you discovered, if you set the URIResolver into the factory instead, it is used to resolve the xsl:include, etc. because the factory is what's building the transformer. Make sense? - Shane ---- you "Domingo, John" <[EMAIL PROTECTED]> wrote ---- Basically, my URI Resolver implementation's resolve() method NEVER gets called when trying to resolve an xsl:include statement in my transformation stylesheet. Now the funny thing here is that I tried setting the URI Resolver via the TransformerFactory, and it works fine!!!!!!!! My URI Resolver implementation's resolve() method is called fine. Here's what that code looks like: ===== <eof aka="mailto:[EMAIL PROTECTED]"; quote="A mirror is like a window on the other side of behind you."/> __________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
