[
https://jira.jboss.org/browse/GTNPORTAL-1510?page=com.atlassian.jira.plug...
]
Michael Schuetz commented on GTNPORTAL-1510:
--------------------------------------------
OK, I got it now!
I disabled ServiceEngineerPortlet first, without success. This was quite strange cause the
portlet page was physically not available anymore and still being displayed. So I kept
searching and found the reason:
In home.xhtml i did use same content of ServiceEngineerPortlet for demo purposes. I did
not use this for quite a while now.
This was my global Seam pages.xml:
###
<?xml version="1.0" encoding="UTF-8"?>
<pages
xmlns="http://jboss.com/products/seam/pages"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://jboss.com/products/seam/pages
http://jboss.com/products/seam/pages-2.0.xsd"
no-conversation-view-id="/portlets/testportlet/home.xhtml"
login-view-id="/portlets/testportlet/home.xhtml">
<exception class="org.jboss.seam.security.NotLoggedInException">
<redirect view-id="/portlets/testportlet/home.xhtml">
<message severity="warn">You must be logged in to use this
feature</message>
</redirect>
</exception>
<!-- HERE -->
<exception>
<redirect view-id="/portlets/testportlet/home.xhtml"/>
</exception>
</pages>
###
Interesting: home.xhtml is not part of a portlet, although name suggests it.
Actually, the configuration of global exception handling was the root cause. When
exception occurs, the redirect take place. For some reason the redirect happens within
current portlet, not at page level.
So, is this a bug in communication between GateIn and Seam or just misconfiguration of
Seam? Is it recommended to not use Seam global pages configuration as this is
responsibility of portal platform?
When one portlet crashes, a different one well be displayed
-----------------------------------------------------------
Key: GTNPORTAL-1510
URL:
https://jira.jboss.org/browse/GTNPORTAL-1510
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.1.0-GA
Environment: * GateIn 3.1/JBoss AS 5.1
* Seam 2
* JSF 2
Reporter: Michael Schuetz
Assignee: kien nguyen
Fix For: 3.2.0-GA
Attachments: bug_1.png, bug_2.png, bug_3.png, bug_4.png
Original Estimate: 4 hours
Remaining Estimate: 4 hours
What I did:
* starting portal
* logging in with specific role
* access portlet
* perform portlet actions
* let the portlet crash (in mny use case this portlet need special VPN access to external
system. So i just cut VPN access.)
* try to redo portlet actions
* another portlet appears
Strange thing: the logged in user does not have the permissions to view this portlet.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira