PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3261
*** shadow/3261 Mon Aug 27 07:09:06 2001
--- shadow/3261.tmp.28297 Mon Aug 27 08:47:29 2001
***************
*** 227,230 ****
The only other suggestion I have is for you to put some debugging printfs in
XSLTEngine::getStylesheetFromPIURL(). Most importantly, see what the variable
! localXSLURLString contains when the stylesheet is parsed.
--- 227,257 ----
The only other suggestion I have is for you to put some debugging printfs in
XSLTEngine::getStylesheetFromPIURL(). Most importantly, see what the variable
! localXSLURLString contains when the stylesheet is parsed.
!
! ------- Additional Comments From [EMAIL PROTECTED] 2001-08-27 08:47 -------
! After I put some reporting code to XSLTEngineImpl::getStylesheetFromPIURL() I've
! come to a conclusion (correct me if i'm wrong) that
! XalanTransformer::transform(const XSLTInputSource& theInputSource, const
! XSLTResultTarget& theResultTarget) does not use getStylesheetFromPIURL() at all.
! It's body looks like the following:
! -----------
! // Do the transformation...
! return transform(
! theInputSource,
! XSLTInputSource(),
! theResultTarget);
! -----------
!
! Then I took a look at the XSLTInputSource::XSLTInputSource(). It's pretty
! straightforward too:
! ----------
! XSLTInputSource::XSLTInputSource() :
! InputSource(),
! m_stream(0),
! m_node(0)
! {
! }
! -----------
! Eh... I'm not an experienced C++ programmer. Correct me if I'm wrong. But looks
! like XSLTInputSource() does NOTHING...
