Sort of. I mean any java class which saves, loads, or gets data from
somewhere and thus requires configuration at some time. Using IOC you
can hand wave around those configuration issues and having one "smarter"
class dependent on the servlet api which configures the rest of your
beans is OK.
-Tim
Brian Munroe wrote:
On 8/31/07, Tim Funk <[EMAIL PROTECTED]> wrote:
Do you really want code that has nothing to do with the servlet api
dependent on ServletContext? Plugging in a new jndi lookup for testing
is much easier.
Forgive my ignorance here, but do you mean, say, in a bean? That
doesn't inherit the servlet's scope? I've never tried it because I
always use JNDI :)
---------------------------------------------------------------------
To start a new topic, e-mail: [email protected]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
