Gringinho schrieb:
Another thought:
with the ac.login usecase, is the "correct way" now to add a ac.mylogin
usecase
and set a configuration of:
modules-core/acusecases/config/cocoon-xconf/usecase-ac-*mylogin*.xconf
Yes, though I'd rather place it in a custom module and call it e.g.
"ac.loginWithoutForm".
*without a component view?*
Yes. But if you want to show an error message if the login failed, you
have to take care of this yourself.
One option would be to override the Login class and attach the error
message to the session so that it can be displayed on the subsequent
page. It's a bit tricky, though, since you have to delete the message
from the session as soon as you fetch it (e.g. using a custom
SessionInputModule).
Another option would be to override getExitQueryString() and attach a
request parameter containing the error message. I guess this would be
more convenient.
Will this effectively rid the displaying of the intermittent login-screen?
Yes, it should. If not, you can file a bug :)
And the same approach for an immediate logout URL using a
"?lenya.usecase=ac.mylogout" ?
Yes.
Further on, having a (as a blatant copy or slightly modified version of
Login.java):
modules-core/acusecases/java/src/org/apache/lenya/cms/ac/usecases/*Mylogin*.java
You need this only if you want to alter the error handling (see above).
Otherwise, you can just reference the Login class from the acusecases
module.
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
