[JBoss Portal] - Themes - Region interceptor override
by lucboudreau
Hi, I'm developing a theme/layout for JBoss portal 2.6.2 and my objective is to change the HTML code generated for the tab navigation. Instead of ULs, I want simple As. But there is a catche... I want to change the associated JSP for my custom themes only. I don't want to change it for all themes, since this would break the other themes that come with JBoss portal.
I don't want my theme to have any impact whatsoever on the default theme because I want to keep the Admin portal isolated in it's own theme. This way, If i break something, I can always go back. Also, this gives me much more flexibility.
What are my options ?
- Use a different RenderSet ? (would that even work ?)
- Override the MBean where JSPs are defined with a custom subclass ? (this is too complicated for nothing, let's keep it simple.)
The way I understood, the MBean is an interceptor which gets called when we call the taglib for region render and it overrides the output by code from the JSP.
One solution I thought of is this. Use a different tag for navigation generation. In order to do this, I need to find hot to access PortalAuthorizationManagerFactory from a JSP or taglib. Any insights ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123166#4123166
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123166
18 years, 4 months
[JBoss Seam] - Re: Setting Authorization Roles
by asookazian
"shane.bryzak(a)jboss.com" wrote : You can place a element within a element inside pages.xml, like this:
|
| <page view-id="/orderDetail.xhtml">
| | <restrict>#{s:hasRole('admin')}</restrict>
| | </page>
What is the recommended alternative implementation strategy to hard-coding the role(s) like above in pages.xml? for example, storing the role information in a RDBMS table so that we can update role data real-time and users are granted roles when they begin a new session.
Is it even necessary to do this? the argument bein that roles for page level access do not change frequently enough to need real-time updates?
Also, is it sufficient in most cases to use s:hasRole for component level restriction on JSF's instead of using s:hasPermission?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123159#4123159
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123159
18 years, 4 months