[JBoss JIRA] Created: (JBPORTAL-1488) Session Invalidation issue when Tomcat SSO is turned on
by Sohil Shah (JIRA)
Session Invalidation issue when Tomcat SSO is turned on
-------------------------------------------------------
Key: JBPORTAL-1488
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1488
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Server
Affects Versions: 2.6.CR2, 2.4.1 SP1
Reporter: Sohil Shah
Assigned To: Sohil Shah
Priority: Minor
Fix For: 2.6 Final, 2.4.2 Final
It turns out that when Tomcat SSO is turned on, when a user's session is invalidated,
as the portal server iterates through all the active war sessions and invalidates them, the main portal session is invalidated as well.
The code calls session.invalidate on the main portal session after that and gets and IllegalStateException because the session is already invalidated.
This exception needs to be handled smoothly so that user does not see a failure upon logout
Note: This issue surfaces only when Tomcat SSO is actiavted.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 5 months
[JBoss JIRA] Created: (JBPORTAL-1730) IdentityServiceControllerImpl : unregister existing MBean service before to re register them
by Antoine Herzog (JIRA)
IdentityServiceControllerImpl : unregister existing MBean service before to re register them
--------------------------------------------------------------------------------------------
Key: JBPORTAL-1730
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1730
Project: JBoss Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Portal Identity
Affects Versions: 2.6.1 Final
Reporter: Antoine Herzog
Priority: Optional
Fix For: 2.6.3 Final
In IdentityServiceControllerImpl (service name="portal:service=Module,type=IdentityServiceController")
the Identity Beans are registered as JMX MBeans.
When redeploying the service, an exception is thrown, as the services are yet deployed.
javax.management.InstanceAlreadyExistsException: portal:service=Module,type=User already registered.
Let's put this code before to register the bean, at line 378 of IdentityServiceControllerImpl.java
// Unregister the former service is if it is yet there.
// This to avoid the exception when redeploying this service
if (getServer().isRegistered(
new ObjectName(module.getServiceName()))) {
getServer().unregisterMBean(
new ObjectName(module.getServiceName()));
}
Thanks,
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 5 months
[JBoss JIRA] Created: (JBPORTAL-1724) portlet lib for clustering tests
by Prabhat Jha (JIRA)
portlet lib for clustering tests
--------------------------------
Key: JBPORTAL-1724
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1724
Project: JBoss Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Portal Portlet, Portal QA
Affects Versions: 2.6.2 Final
Reporter: Prabhat Jha
Assigned To: Julien Viet
Fix For: 2.6.3 Final
For clustering tests, from portlet modules, we need
portal-portlet-lib.jar
portal-portlet-test-framework-lib.jar
test-info.war
In thirdparty/jboss-portal/portlet, test jars are not available. We need to make this available. I think better place will be to put all test related binaries in test module or build them in portlet module but upload to repository under test module.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 5 months
[JBoss JIRA] Created: (JBPORTAL-1874) Default installation of JBoss Portal 2.6.3 does not validate as correct XHTML and CSS
by Piotr Kubowicz (JIRA)
Default installation of JBoss Portal 2.6.3 does not validate as correct XHTML and CSS
-------------------------------------------------------------------------------------
Key: JBPORTAL-1874
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1874
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Core
Affects Versions: 2.6.3 Final
Environment: Windows XP SP 2, Java 6u3, JBoss 4.2.2 GA
Reporter: Piotr Kubowicz
Assigned To: Julien Viet
After deploying downloaded JBoss Portal 2.6.3, the main page does not pass validation with http://validator.w3.org/ and http://jigsaw.w3.org/css-validator/. As result, some browsers may not display parts of pages (since they are invalid). Also other themes and layouts provided by default suffer from incompatibility with XHTML and CSS standards.
Anyone can see this running the validator on public portal demo (there are more error messages when you log in and then run the validation).
There are too many reasons to enumerate, but some of them include:
- index.jsp in generic layout includes "/layouts/common/modal.jsp", which causes CSS stylesheet usage declaration (<link rel="stylesheet") being pasted inside <body> tag (sic!!!)
- in URLs there are plain ampersand signs (IdentityUserPortletWindow?action=1&org.apache.myfaces), whilst all of them should be changed to & entities
- omitting alt attribute and closing / in <img> element in standard portlets
- duplicate id attribute inserted by one of portlets on the main page (not visible in the demo)
In default Renaissance theme CSS (http://skocz.pl/jbosscsserrors):
- using "font: 11px" instead of "font-size: 11px"
- illegal combination "background-color: none"
I suggest including phase of XHTML and CSS validation in JBoss Portal development lifecycle because you will encounter such problems with every new release as good Java programmers need not to be good web designers. Besides W3C validators, watch output of the error console in your browser (Opera and Firefox do their job well), since it displays errors in all CSS files used on page, not only in the main CSS, as well as JavaScript errors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 5 months