This week's book giveaway is in the Clojure forum.
We're giving away four copies of Clojure in Action and have Amit Rathore and Francis Avila on-line!
See this thread for details.
Win a copy of Clojure in Action this week in the Clojure forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

SAXException: Namespace not supported by SAXParser

 
Jane Cheeney
Greenhorn
Posts: 1
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
After loading iPlanet on my Windows machines, I have built and deployed a java based application that was originally built on Solaris. This app uses xsl on the frontend. I have modified the configurations/classpaths for Windows, and successfuly connecting to the database, but now I find that we still cannot display any of the xsl pages. We are beginning by just trying to invoke an existing servlet that does nothing but display a simple page. This xsl pages does not pull any data from the database; it only uses existing xml files on the system to populate the page.
We receive the following error:
javax.xml.transform.TransformerConfigurationException: javax.xml.transform.TransformerException: org.xml.sax.SAXException: Namespace not supported by SAXParser
javax.xml.transform.TransformerConfigurationException: javax.xml.transform.TransformerException: org.xml.sax.SAXException: Namespace not supported by SAXParser at org.apache.xalan.processor.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:946) at com.gm.ilocate.infra.StylesheetCache.fillAllFromList(StylesheetCache.java:113) at com.gm.ilocate.infra.StylesheetCache.getTransformer(StylesheetCache.java:151) at com.gm.ilocate.infra.IlocateTransformXMLtoXSL.showPage(IlocateTransformXMLtoXSL.java:192) at com.gm.ilocate.infra.IlocateTransformXMLtoXSL.showPage(IlocateTransformXMLtoXSL.java:90) at com.gm.ilocate.servlet.DealerLocateServlet.displayEmailUpdate(DealerLocateServlet.java:48) at com.gm.ilocate.servlet.DealerLocateServlet.performTask(DealerLocateServlet.java:768) at com.gm.ilocate.servlet.DealerLocateServlet.service(DealerLocateServlet.java:829) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.netscape.server.servlet.servletrunner.ServletInfo.service(Unknown Source) at com.netscape.server.servlet.servletrunner.ServletRunner.execute(Unknown Source) at com.kivasoft.applogic.AppLogic.execute(Unknown Source) at com.kivasoft.applogic.AppLogic.execute(Unknown Source) at com.kivasoft.thread.ThreadBasic.run(Native Method) at java.lang.Thread.run(Thread.java:484) --------- javax.xml.transform.TransformerException: org.xml.sax.SAXException: Namespace not supported by SAXParser at org.apache.xalan.processor.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:942) at com.gm.ilocate.infra.StylesheetCache.fillAllFromList(StylesheetCache.java:113) at com.gm.ilocate.infra.StylesheetCache.getTransformer(StylesheetCache.java:151) at com.gm.ilocate.infra.IlocateTransformXMLtoXSL.showPage(IlocateTransformXMLtoXSL.java:192) at com.gm.ilocate.infra.IlocateTransformXMLtoXSL.showPage(IlocateTransformXMLtoXSL.java:90) at com.gm.ilocate.servlet.DealerLocateServlet.displayEmailUpdate(DealerLocateServlet.java:48) at com.gm.ilocate.servlet.DealerLocateServlet.performTask(DealerLocateServlet.java:768) at com.gm.ilocate.servlet.DealerLocateServlet.service(DealerLocateServlet.java:829) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.netscape.server.servlet.servletrunner.ServletInfo.service(Unknown Source) at com.netscape.server.servlet.servletrunner.ServletRunner.execute(Unknown Source) at com.kivasoft.applogic.AppLogic.execute(Unknown Source) at com.kivasoft.applogic.AppLogic.execute(Unknown Source) at com.kivasoft.thread.ThreadBasic.run(Native Method) at java.lang.Thread.run

We have already tried to re-build and deploy with different versions of xml-apis.jar (the standard jar file containing the javax.xml classes) and SAX Parser classes, too see if this was a version incompatibility issue. We have also placed the xml classes/jar files at the front of our classpaths.
any ideas?
Thanks in advance!!!
 
Anonymous
Ranch Hand
Posts: 18944
  • 0
  • send pies
  • Quote
  • Report post to moderator
Jane,
Moving your xml libraries in front of the classpath won't help if iPlanet uses different xml libraries in the boot classpath.
It looks like Xalan is using the SAXParser that comes with iPlanet, which may not support certain features.
The override this, set the system property "javax.xml.parsers.SAXParserFactory" to the name of the SAXParser you want to use, which in Xalan's case should be "org.apache.xerces.jaxp.SAXParserFactoryImpl"
Cheers
[ December 20, 2002: Message edited by: Beno�t d'Oncieu ]
 
I agree. Here's the link: http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic