----- Original Message -----
From: "Peter Donald" <[EMAIL PROTECTED]>
> So in that way EJB has an inviolatable policy for somethings. Im not sure
if
> we should have the same though.
My point was that EJB is not a requirement to use a J2EE container, but if
you use them then there are "rules" (loosely speaking, actually better
titled "best practices" in most cases) that you should adhere to.
So, if you use a certain facility of the container, you should do it the
"standard" way, but if you want to go outside the box you can and you'll be
told that you'll pay a penalty if you aren't careful.
> I hope so ;) If you are interested in the supporting theory there is a
> relatively easy-to-read set of info on the Avalon web pages about
"Inversion
> of Control" and "Separation of Concerns". Avalon hasn't put up any
literature
> on "located" or "contextualization" APIs/Frameworks (which is the other
part
> of the container theory). However I think I have some references if you
want
> ;)
Sure, fire some URL's my way. I'm interested, but certainly more from a
very keenly interested bystander perspective at this point, so I probably
won't digest them very deeply just yet.
Erik
