Check D:\Hyperion\Essbase61p3a\java\jre\lib\ext for .jar files that
contain other versions of the DOM classes which are not DOM Level 2
compliant.  It appears that your java.exe is in
D:\Hyperion\Essbase61p3a\java\bin.  If that is the case, java.ext.dirs
is set correctly.  Why do you want to change it?

Gary

> -----Original Message-----
> From: Jason Rizer [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, January 30, 2002 8:56 AM
> To: [EMAIL PROTECTED]
> Subject: SAXException: Namespace not supported by SAXParser?
> 
> 
> Hello.  I've written an application which utilizes
> Xalan.  It works correctly everywhere but on one
> specific machine.  The machine in question is running
> Win2000.  When we run the application on this machine
> the following stack trace is produced:
> 
> 7 XMIObject CWM:Multiplicity
> DCE:[EMAIL PROTECTED]:1
> javax.xml.transform.TransformerConfigurationException:
> javax.xml.transform.Trans
> formerConfigurationException:
> javax.xml.transform.TransformerException: org.xml.
> sax.SAXException: Namespace not supported by SAXParser
>         at 
> org.apache.xalan.processor.TransformerFactoryImpl.newTransformer(Tran
> sformerFactoryImpl.java:767)
>         at 
> com.hyperion.mda.javax.jmi.xmi.XmiWriterImpl.persistObjects(XmiWriter
> Impl.java:126)
>         at 
> com.hyperion.mda.javax.jmi.xmi.XmiWriterImpl.write(XmiWriterImpl.java
> :60)
>         at 
> com.hyperion.mda.metadriver.ADMExportToXMIVisitorImpl.finish(ADMExpor
> tToXMIVisitorImpl.java:321)
>         at
> com.hyperion.mda.metadriver.ADMToXMI.execute(ADMToXMI.java:86)
>         at 
> com.hyperion.mda.metadriver.MetaDriverImpl.execute(MetaDriverImpl.jav
> a:53)
>         at 
> com.hyperion.mda.metadriverclient.MDGUIClient$RunInterchange.run(MDGU
> IClient.java:2309)
>         at java.lang.Thread.run(Unknown Source)
> ---------
> 
> When I run EnvironmentCheck on the machine these are
> the results:
> 
> D:\HAB\jars>java
> org.apache.xalan.xslt.EnvironmentCheck
> #---- BEGIN writeEnvironmentReport($Revision: 1.9 $):
> Useful stuff found: ---- 
> java.class.path=.;;d:\HAB\lib;;d:\HAB\lib\adm.jar;;d:\HAB\lib\
> ap.jar;;d:\HAB\jar
> s\xmitool.jar;d:\HAB\lib\xerces.jar;;d:\HAB\jars;;d:\HAB\jars\
> metadriver.jar;;d:
> \HAB\jars\metadriverclient.jar;d:\HAB\jars\cwmframework.jar;;d
> :\HAB\jars\xalan.j
> ar;;d:\HAB\jars\xml-apis.jar; 
> java.ext.dirs=D:\Hyperion\Essbase61p3a\java\jre\lib\ext
> version.xerces2=not-present
> version.xerces1=Xerces 1.2.1
> version.xalan2_2=Xalan Java 2.2.D14
> ERROR.=At least one error was found!
> version.xalan1=not-present
> version.ant=not-present
> ERROR.version.JAXP=1.0.1
> java.version=1.3.0
> version.crimson=not-present 
> sun.boot.class.path=D:\Hyperion\Essbase61p3a\java\jre\lib\rt.j
> ar;D:\Hyperion\Ess
> base61p3a\java\jre\lib\i18n.jar;D:\Hyperion\Essbase61p3a\java\
> jre\lib\sunrsasign
> .jar;D:\Hyperion\Essbase61p3a\java\jre\classes
> #---- BEGIN Listing XML-related jars in: 
> foundclasses.java.class.path ---- 
> xerces.jar-path=d:\hab\lib\xerces.jar
> xerces.jar-apparent.version=xerces.jar from
> lotusxsl-j_2_0_0 from XML4J-3_1_1 xalan.jar-apparent.version=xalan.jar
> WARNING.present-unknown-version xalan.jar-path=d:\hab\jars\xalan.jar
> xml-apis.jar-apparent.version=xml-apis.jar
> present-unknown-version xml-apis.jar-path=d:\hab\jars\xml-apis.jar
> #----- END Listing XML-related jars in: 
> foundclasses.java.class.path ----- version.SAX=2.0 
> ERROR.version.DOM=ERROR attempting to load DOM level 2
> class: java.lang.NoSuchMe
> thodException
> version.xalan2x=Xalan Java 2.2.D14
> #----- END writeEnvironmentReport: Useful properties
> found: -----
> # WARNING: Potential problems found in your
> environment!
> #    Check any 'ERROR' items above against the Xalan
> FAQs
> #    to correct potential problems with your
> classes/jars
> #    http://xml.apache.org/xalan-j/faq.html
> 
> 
> Two questions:  First, obviously, does anyone have any
> idea what the problem is?  Second, does anyone know
> how to change the values of the variable
> java.ext.dirs?  I can't figure out how to change this 
> permanently to point to the jdk.  Thanks in advance for any 
> advice anyone may have!
> 
> -Jason

Reply via email to