Meanwhile, I found a workaround: unpack the .properties file into the
/WEB-INF/classes directory.
Looks like a bug to me.
-----Original Message-----
From: Christian Sell <[EMAIL PROTECTED]>
To: Orion-Interest <[EMAIL PROTECTED]>
Date: Donnerstag, 15. Juni 2000 07:10
Subject: urgent: error accessing jar file
>Hello,
>
>Q1:
>I have a JSP tag library which uses the ECS library from apache. Both my
tag
>library and ECS reside as *.jar files in /WEB-INF/lib. When my test page is
>loaded, the initialization code of ECS reads a property file from the jar
>with the following statement:
>
>static {
> try
>
>
> resource = ResourceBundle.getBundle("org.apache.ecs.ecs");
> }
> catch(Exception e)
> {
> System.err.println("Cannot find org.apache.ecs.ecs.properties.");
> }
> }
>
>Even though the file org.apache.ecs.ecs.properties is in the jar file, the
>error message is printed out, the resource variable is not set, and I get a
>NullPointerException later on. I have this very same configuration running
>under Tomcat. However, I have seen previous versions of Tomcat having
>problems accessing implicitly (through placement in /WEB-INF/lib) mapped
jar
>files via getClassForName() and getResource(). Could it be that Orion has a
>similar problem? If not, why is ECS unable to read the properties file from
>its own jar under Orion?
>
>Q2:
>Do I get any further docs when I buy the product? If not, when is the
>documentation going to be improved?
>
>thanks, Christian Sell
>
>
