Comments for OcpSoft

Comment on Improving Community – The power of good, centralized documentation. by Dominik

Dominik — Sat, 13 Mar 2010 17:57:39 +0000

Modularize JBOSS Seam and provide Maven poms for the various parts.

E.g. I really want to use JBoss Seams Mail component with JSF2/JavaEE6 (glassfish) but don’t want to go for the whole framework just because of this.

Comment on Persist and pass FacesMessages over multiple page redirects by Lincoln

Lincoln — Wed, 10 Mar 2010 15:23:38 +0000

You could add a check to see if the message already exists. Only add the message if it is not already present in the list.

Comment on Persist and pass FacesMessages over multiple page redirects by Kaja

Kaja — Wed, 10 Mar 2010 08:49:04 +0000

for (Iterator iter = facesContext.getMessages(null); iter.hasNext();) {
messages.add(iter.next());
iter.remove();
}

iter.remove(); doesn’t work on MyFaces, it’s probably because MyFaces return copy of collection so you remove item from copy not from orginal collection.

First message is saved in INVOKE_APPLICATION, second in RENDER_RESPONSE and also there is orginal message in facesContext so I get 3 same messages on page after all.

Comment on Spring Security – What happens after /you/ log in? by Pamela

Pamela — Tue, 09 Mar 2010 23:22:35 +0000

Do you think it’s possible to utilize taglibs/tld file in order to create URL protection?

I’m currently using JSF 1.2 so I can utilize a tld file that would have security tag defined.

If you could give me a quick example, that’d really be fabulous.

Thanks~!

Comment on Spring Security – What happens after /you/ log in? by Lincoln

Lincoln — Fri, 05 Mar 2010 19:29:40 +0000

Unfortunately, there is no example, sorry. This was all taken out of:

http://ocpsoft.com/scrumshark/ , but you can download the sources for that and take a look.

http://code.google.com/p/ocpsoft-tools/

Comment on Spring Security – What happens after /you/ log in? by Pamela

Pamela — Fri, 05 Mar 2010 13:41:09 +0000

By Hello World, I meant your Basic Login example presented in this article and the previous one.

Sorry if I confused you in any way.

Thanks!

Comment on Spring Security – What happens after /you/ log in? by Pamela

Pamela — Thu, 04 Mar 2010 21:12:10 +0000

BTW where can I download your HelloWorld example?

Comment on Spring Security – What happens after /you/ log in? by Lincoln

Lincoln — Thu, 04 Mar 2010 17:07:35 +0000

No problem. You’d do something very similar. You’d want to create a JSF Action Method in a JSF Managed Bean – something like:

public class MyBean {
public boolean isUserGrantedAccess()
{…}
}

This method would check the logged in user’s preferences, permissions, the state of the system or whatever logic needed.

Then you would disable or render the link by referencing that action method in your Facelet view.

Notice the “is” should be omitted. See “JEE Unified Expression Language Syntax” for more details on that.

Comment on Spring Security – What happens after /you/ log in? by Pamela

Pamela — Thu, 04 Mar 2010 15:37:36 +0000

How about when I want to hide certain links/buttons for certain users? Would I go thru a similar process, or something different.

Sorry, I’m fairly new to this whole programming in Spring Security.

Thanks for your response, Lincoln.

Comment on Spring Security – What happens after /you/ log in? by Lincoln

Lincoln — Thu, 04 Mar 2010 15:29:40 +0000

I usually defer to the non-filter security mechanisms for such use-cases. PrettyFaces allows you to do just that with URL actions. In the action you would check the user’s credentials / business scenario and decide whether or not to continue to process and render, or redirect to a different page. There are other ways, but… this is one.

http://ocpsoft.com/prettyfaces/