If you want to change the theme for the dashboard page, change this section to
use your custom theme and layout:
| deployment
| if-existskeep/if-exists
| context
| context-namedashboard/context-name
| properties
|
| !--
| |
http://repository.jboss.org/maven2/
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4255357#4255357
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4255357
___
jboss-user mailing list
We are running a number of Struts apps in Portal and do not have any
significant problems. We stick to using the Struts tag libraries however and
do not use code directly in the JSPs. If you are under time constraints,
converting this app to a portlet shouldn't be too difficult. If you have
We have a similar setup with AD authentication and DB as a backup. I have the
DBIdentityLoginModule configured with the options of:
module-option name=hashAlgorithmMD5/module-option
| module-option name=hashEncodingHEX/module-option
I believe these are the defaults for this module.
View the
I think the problem here is that JBoss expects there to be a single default
portal for all users. Although a role can give a user access to a portal
(admin user, for instance), it cannot determine which portal will be the user's
default when they login. I have not found a way to do this but
You can drop your jboss portal database schema and then recreate it. When you
restart the server, the tables will be recreated and you will have the default
page.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4249929#4249929
Reply to the post :
Yes.
You will need the Struts portlet bridge:
http://portals.apache.org/bridges/multiproject/portals-bridges-struts/index.html
In your portlet.xml, you will need to define you portlet-class as:
org.apache.portals.bridges.struts.StrutsPortlet
And in web.xml your action servlet class will be:
