Oh, does more than one module need access to foo.jar?  If not, put foo.jar
and foo.properties in the module that needs it and your life will be easier.

Mike
> -----Original Message-----
> From: tclug-devel-admin at mn-linux.org
> [mailto:tclug-devel-admin at mn-linux.org]On Behalf Of Mike Bresnahan
> Sent: Friday, October 17, 2003 11:00 AM
> To: tclug-devel at mn-linux.org
> Subject: RE: [TCLUG-DEVEL] Java properties file question
>
>
> > Root or top directory.
>
> I do not believe that the root directory of the EAR is in the classpath.
> You can add a JAR file to the classpath of dependent modules by editing
> their manifest files, but I don't think you can add property
> files this way.
> You can solve your problem by putting the properties file inside
> a JAR file
> and adding the JAR file to the classpath via manifest entries.
>
> I am assuming you are searching for the properties file on the classpath.
> Is this assumption true?  If so, which function are you using to do the
> search.  They don't all work the same and the behavior varies if
> the EAR is
> expanded or not expanded.
>
> Mike
>
>
> _______________________________________________
> tclug-devel mailing list
> tclug-devel at mn-linux.org
> https://mailman.real-time.com/mailman/listinfo/tclug-devel


_______________________________________________
tclug-devel mailing list
tclug-devel at mn-linux.org
https://mailman.real-time.com/mailman/listinfo/tclug-devel