FYI:  I messed around with some of these jar files and was unsuccessful. I 
then upgraded to Tomcat 4.0 and it seemed to work perfectly (along with a 
myriad other problems I was having).






Santiago Gala <[EMAIL PROTECTED]>
10/03/01 06:21 AM
Please respond to jetspeed-user

 
        To:     [EMAIL PROTECTED]
        cc: 
        Subject:        Re: XSL Portlet:  SAXException - Namespace not supported



[EMAIL PROTECTED] wrote:

>I have tried to move a very simple XSL portlet example into version 
1.3a2. 
> This example worked fine in version 1.3a1, but now I get the error 
>message shown below in both the portlet and in the log.  I don't 
>understand what namespace it is referring to.  Has anyone had similar 
>problems?  Has anyone been able to deploy XSL portlets in version 1.3a2?
>
You are probably using a XML parser (coming from tomcat) that is not 
namespace aware. One possibility is to remove crimson.jar or parser.jar 
from the tomcat/lib directory or classpath, and put there the 
xerces-xxx.jar that comes with jetspeed. It will replace the parser 
coming with tomcat and it is namespace aware. Also, it can happen that 
you have a parser around in the classpath that gets configured by the 
JAXP api.

>
>I'm using the 9/21 build under NT for development.
>
>Thanks.
>Jim
>
>[Tue Oct 02 14:21:44 EDT 2001] -- INFO -- SimpleTransform:  transforming 
>url: 
>file:D:\javadev\install\tomcat\webapps\jetspeed\portlets\sphinxcatalog\menuitems.xml 

>with stylesheet: /portlets/sphinxcatalog/menus.xsl
>[Tue Oct 02 14:21:44 EDT 2001] -- ERROR -- Invalid SAX Transformer: 
>javax.xml.transform.TransformerException: Namespace not supported by 
>SAXParser
>[Tue Oct 02 14:21:44 EDT 2001] -- ERROR -- 
>        Exception:  org.xml.sax.SAXException: problem in SAX transform: 
>javax.xml.transform.TransformerException: Namespace not supported by 
>SAXParser
>        Stack Trace follows:
>        org.xml.sax.SAXException: problem in SAX transform: 
>javax.xml.transform.TransformerException: Namespace not supported by 
>SAXParser
>
>




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to