> "Sriram Narayan (CTS)" wrote:
> >
> > Hi
> > Could u pls share ur opinions on placing all the queries that an ejb fires
> > inside the ejb-jar.xml as env entries.
> > We could then retrive them as required using context.lookup...
> >
> > This helps in cleaning the code from the clutter of sql.
> > But is it costly in any way? Are jndi lookups for env entries cached?
This general approach isn't bad. We used it with the Enterprise Tool Kit. SQL
statements were stored in XML files, which were bundled into the entity bean
jars. It really cleaned up the BMP code that programmers wrote. They didn't
have to write any JDBC, and it was easy to update the SQL that they executed.
-david
--
David Sims [EMAIL PROTECTED]
Sims Computing, Inc. www.simscomputing.com
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
