Pass Strings from JSF page to method in Security backing bean

["Zohner, Michael" <Mi...@dkib.com>]

Hiu,

I developed a SecurityBacking bean, where I manage user roles etc.

In the jsf pages I now want to hide elements (links, buttons etc.)

In the backing, I have a method, which is like:

	public boolean isUserInGroup(List<String> userGroups){
		return isUserInGroup(getCurrentUser(), userGroups);
	}

In the jsf page I now want to do that:

<h:outputText value="TEST!!!"
rendered="#{securityBacking.userInGroup['userGroup1','userGroup2']}"></h
:outputText>

But this leads to an error.

I think the el is wrong here.

What I am doing wrong ?

The method to check whether the user in one of these user groups expects
a list of strings (one or more Strings).

Regards
Michael


________________
Dresdner Bank AG
Sitz/Registered Office: Frankfurt am Main, Handelsregister/Commercial Register: Amtsgericht/Local Court, Frankfurt am Main, HRB 14000 
Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Michael Diekmann 
Vorstand/Board of Managing Directors: Herbert Walter (Vorsitzender/Chairman), Andreas Georgi, Stefan Jentzsch, Wulf Meier, Andree Moschner, Klaus Rosenfeld, Otto Steinmetz, Friedrich Woebking 

This e-mail is confidential and the information contained in it may be privileged.  It should not be read, copied or used by anyone other than the intended recipient.  If you have received it in error, please contact the sender immediately by telephoning +44 (0)20 7623 8000 or by return email, and delete the e-mail and do not disclose its contents to any person.  We believe, but do not warrant, that this e-mail and any attachments are virus free, but you must take full responsibility for virus checking.  Please refer to http://www.dresdnerkleinwort.com/disc/email/ and read our e-mail disclaimer statement and monitoring policy.
________________

Re: Pass Strings from JSF page to method in Security backing bean

[Mike Kienenberger <mk...@gmail.com>]

Read through this page for general questions about el function support:
http://wiki.apache.org/myfaces/Parameters_In_EL_Functions

However, your best bet is to use the SecurityContext feature of Tomahawk:
http://wiki.apache.org/myfaces/SecurityContext

On 4/20/07, Zohner, Michael <Mi...@dkib.com> wrote:
> Hiu,
>
> I developed a SecurityBacking bean, where I manage user roles etc.
>
> In the jsf pages I now want to hide elements (links, buttons etc.)
>
> In the backing, I have a method, which is like:
>
>         public boolean isUserInGroup(List<String> userGroups){
>                 return isUserInGroup(getCurrentUser(), userGroups);
>         }
>
> In the jsf page I now want to do that:
>
> <h:outputText value="TEST!!!"
> rendered="#{securityBacking.userInGroup['userGroup1','userGroup2']}"></h
> :outputText>
>
> But this leads to an error.
>
> I think the el is wrong here.
>
> What I am doing wrong ?
>
> The method to check whether the user in one of these user groups expects
> a list of strings (one or more Strings).
>
> Regards
> Michael
>
>
> ________________
> Dresdner Bank AG
> Sitz/Registered Office: Frankfurt am Main, Handelsregister/Commercial Register: Amtsgericht/Local Court, Frankfurt am Main, HRB 14000
> Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Michael Diekmann
> Vorstand/Board of Managing Directors: Herbert Walter (Vorsitzender/Chairman), Andreas Georgi, Stefan Jentzsch, Wulf Meier, Andree Moschner, Klaus Rosenfeld, Otto Steinmetz, Friedrich Woebking
>
> This e-mail is confidential and the information contained in it may be privileged.  It should not be read, copied or used by anyone other than the intended recipient.  If you have received it in error, please contact the sender immediately by telephoning +44 (0)20 7623 8000 or by return email, and delete the e-mail and do not disclose its contents to any person.  We believe, but do not warrant, that this e-mail and any attachments are virus free, but you must take full responsibility for virus checking.  Please refer to http://www.dresdnerkleinwort.com/disc/email/ and read our e-mail disclaimer statement and monitoring policy.
> ________________
>
>