On 7/13/02 5:20 PM, "Stephen Haberman" <[EMAIL PROTECTED]> wrote:
> Hello, > > Torque uses Texen's PropertiesUtil object and it was giving us problems > in how it guessed where to load files from (e.g. relying on just > templatePath being null to insinuate that useClasspath=false). > > So, instead of relying on ad hoc mechanisms for guessing where to load a > properties file from, I updated PropertiesUtil to instead call > RuntimeSingleton.getContent and put the resulting text into a Properties > object. > > The patched PropertiesUtil passes all of the unit tests (test-texen and > test-texen-classpath) along with correctly handling for the deprecated > $generator.templatePath being in the propertiesFile parameter. And it > also gets rid of the messy logic on guessing where to load the file from > and instead relies on Velocity's existing resource management > infrastructure. > > Does this look okay to commit? I think it works great, and it passes the > tests, but if there are any objections or changes I should make, just > let me know. I didn't look at the patch - but doesn't this mean you'll have to put the properties file in path accessible to the resource loader? -- Geir Magnusson Jr. Research & Development, Adeptra Inc. [EMAIL PROTECTED] +1-203-247-1713 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
