on 2/2/00 4:54 PM, Mike Cannon-Brookes <[EMAIL PROTECTED]> wrote:
> This is where JetSpeed / Turbine have problems IMHO, why add your own login
> system when J2EE has a comprehensive login system? Caching is handled by the
> J2EE server usually?
Why is it that there are always these people out there that can't understand
*why* we do things? Gawd, I need to sit down and document this stuff.
<answer>
Because I don't want to use J2EE's login system. I want the source and the
ability to modify things myself. If I wanted closed source, I would buy a
commercial product.
Also, J2EE is just a collection of technologies. It isn't an implementation.
It is up to you to implement the login system based on those technologies.
This is something that Turbine is essentially already doing. It is a login
system implemented within a Servlet (J2EE technology) environment. The same
with the caching systems. We are just making the code available for you to
take advantage of instead of re-doing the wheel. Can't you just appreciate
that?
Also, Turbine's login system is essentially an interface with a default
implementation. You have all the options you want on how to implement it
yourself on the back end. It is totally customizable.
For example, you can simply override a couple of classes, write your code to
pull username/passwords out of an LDAP database and you are done. If J2EE
already has a feature for pulling usernames/passwords out of an LDAP
database, there is no problem with using that within Turbine.
</answer >
I hope that clarifies things.
-jon
--
Come to the first official Apache Software Foundation
Conference! <http://ApacheCon.Com/>
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
