I'm sure this can be figured out - maybe someone more knowledgable can give
you some help. The ACEGI interfaces need to be implemented correctly and
this is all setup to use username. The bottom of this page spells out pretty
clearly what needs to be left alone:
http://www.appfuse.org/display/APF/AppFuse+Core+Classes
But you might consider just keeping the username field an d just storing
email address in both the email field and the username field (only have one
field on the signup/edit screen of course). With just a bit more work and a
lot less fragile would be to eliminate the email field and change the
methods that actually send emails to the user to use username instead of the
email field..
Its not super elegant, but IMHO you lose a lot of the boost that appfuse
gives when you have to start tinkering with basics like this. Just my two
cents.
> From: Harsha Ch <[EMAIL PROTECTED]>
> Reply-To: <[email protected]>
> Date: Tue, 20 May 2008 23:48:50 -0700
> To: <[email protected]>
> Subject: [appfuse-user] regarding request.getRemoteUser()
>
> HI,
> I did some changes to the appfuse ( appfuse2 struts basic ), I
> discarded the username instead i am using email as login id, every
> thing else working fine , but the getRemoteUser() is returning null
> must be because there is no username for the logged in user, how
> should i change it to return logged in user email address.
>
> thanks,
> harsha
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
