Hi, Mike -- What version of XalanJ are you using? What is your JDK version? Can you include the full stack trace of the MissingResourceException, please (you may need to include the -edump command line switch).
Also, if you're executing XalanJ from the command line, can you please type java org.apache.xalan.xslt.EnvironmentCheck and include the output? Thanks, Gary > -----Original Message----- > From: Michael Engelhart [mailto:[EMAIL PROTECTED] > Sent: Friday, March 01, 2002 1:16 PM > To: [EMAIL PROTECTED] > Subject: xalan extensions classpath > > > Hi, > > I have a stylesheet with the following in it: > > <xsl:variable name="language" select="/Document/@Language" /> > <xsl:variable name="country" select="/Document/@Country" /> > <xsl:variable name="locale" > select="java:java.util.Locale.new($language, > $country)" /> > <xsl:variable name="i18nBundle" > select="java:java.util.ResourceBundle.getBundle('clients.somec > lient.i18n', > $locale)" /> > > > This standalone application has the directory that contains > "clients/someclient" in the classpath and I can easily call: > ResourceBundle bundle = > ResourceBundle.getBundle("clients.someclient.i18n"); > without throwing a MissingResourceException from anywhere in my java > class files. I can also do transforms with Xalan as well but when I > include the above XSL extension code I get a MissingResourceException > thrown. > > So my question is how come Xalan isn't using the applications > classpath > in it's extension mechanism? Also I tried jarring up that clients > directory and sticking it my Java Extensions directory (which > on Mac OS > X gets added to the classpath automatically) and it found the file > fine. But I want these properties files to be editable and not > wrapped up in a jar. The clients directory is to sit in the > applications top level directory. > > Any help/advice would be apprectiated. > > Thanks > Mike >
