RE: SQL STatements in a Properties file.

recompilation. There may be a better approach, but this one has worked for me so far. robert > -Original Message- > From: Vikram Goyal01 [mailto:[EMAIL PROTECTED]] > Sent: Monday, June 10, 2002 8:43 AM > To: Struts Users Mailing List > Subject: RE: SQL STatements in a

RE: SQL STatements in a Properties file.

[mailto:[EMAIL PROTECTED]] Sent: Monday, June 10, 2002 5:29 PM To: Struts Users Mailing List Subject: RE: SQL STatements in a Properties file. The reason for putting your SQL in a properties files is so that you or whomever is doing research or maintenance on the code can find all of the SQL in one pl

RE: SQL STatements in a Properties file.

Vikram -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED]] Sent: Friday, June 07, 2002 4:44 AM To: Struts Users Mailing List Subject: RE: SQL STatements in a Properties file. The framework knows nothing of sql. However, I have also pondered the using the message resources

Re: SQL STatements in a Properties file.

- Original Message - From: "James Mitchell" <[EMAIL PROTECTED]> > The framework knows nothing of sql. > > However, I have also pondered the using the message resources for something > like this. > I guess if your data layer had access to the message resourcesyou could > do something li

RE: SQL STatements in a Properties file.

eries and data access. Having another level of abstraction is IMHO pointless. Rgs Vikram -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED]] Sent: Friday, June 07, 2002 4:44 AM To: Struts Users Mailing List Subject: RE: SQL STatements in a Properties file. The framework knows

RE: SQL STatements in a Properties file.

The framework knows nothing of sql. However, I have also pondered the using the message resources for something like this. I guess if your data layer had access to the message resourcesyou could do something like this. sql.customers.get=Select * from customers sql.customer.get=Select * from