Well I am not sure I understand the question fully - I am using this piece
of code to do the transform:
          TransformerFactory tFactory = TransformerFactory.newInstance();
          Templates templates = tFactory.newTemplates(new
StreamSource(is));
          Transformer transformer = templates.newTransformer();
          transformer.transform(source,new StreamResult(bo));

And I have the xalan.jar and the xerces.jar in my path. I am loading the
base xsl file in the StreamSource - and I expected the StremSource to find
the include xsl file in the same directory - but thats not happening - is
this a bug??
TIA
Anamitra



                                                                                
                                        
                    "Joseph                                                     
                                        
                    Kesselman/CAM/Lotus       To:     [EMAIL PROTECTED]         
                           
                    "                         cc:     [EMAIL PROTECTED]         
                             
                    <[EMAIL PROTECTED]       Subject:     Re: include path 
problem in Xalan                            
                    s.ibm.com>                                                  
                                        
                                                                                
                                        
                    04/09/2002 06:02 PM                                         
                                        
                                                                                
                                        
                                                                                
                                        





Sanity check: Are you experiencing this problem when using XSLTC, or
interpretive Xalan? We haven't yet moved to a shared representation for
parsing and optimizing stylesheets, so there are separate implementations
of the include code and a bug in one may or may not be present in the
other.






Reply via email to