It really depends on what you are more familiar with. I generally prefer Tomcat's realms, both because they take less programming and also because I can easily write a custom realm when I need to (and I have had to before). Although you can use a Realm to protect an entire Cocoon webapp, you can also use it to protect specific URI patterns as well. For one client, I used a custom realm to protect one particular subdirectory.
On the other hand, Cocoon authentication is great for protected specific pipelines under specific situations. The fine-grained control you have with Cocoon will fit some projects better.
Regards,
Lajos
SAXESS - Hussayn Dabbous wrote:
Hy,
while browsing through the cocoon docs, i realised, that
cocoon offers an authentication mechanism on it's own.
Since i'm developing webapplications using tomcat i
naturally use the authentication Realms provided by tomcat.
But when i want to use cocoon on top of tomcat, what shall i do:
Either drop the cocoon authentication in favour of the tomcat auth. or vice versa ?
Where can i find hints about advantages/disadvantages
concerning the two approaches?
any pointers or explanations are welcome ;-)
regards, hussayn
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
-- galatea.com Cocoon training, consulting & support
--------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
