[JBoss JIRA] Created: (GTNPORTAL-1851) Upgrade (or better, remove) JUEL
by Chris Laprun (JIRA)
Upgrade (or better, remove) JUEL
--------------------------------
Key: GTNPORTAL-1851
URL: https://issues.jboss.org/browse/GTNPORTAL-1851
Project: GateIn Portal
Issue Type: Component Upgrade
Security Level: Public (Everyone can see)
Components: Shindig
Affects Versions: 3.1.0-GA
Reporter: Chris Laprun
Priority: Critical
Fix For: 3.2.0-GA
First, why is JUEL needed? Could it be removed?
If not, the JUEL version we're currently using (2.1.2) is not conform to the EL specification and, associated with how things are packaged for AS 6, causes EL issues in JSF applications.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (GTNPORTAL-1941) Different portlet names for remote portlets added in "Portlet" menu
by Michal Vanco (JIRA)
Different portlet names for remote portlets added in "Portlet" menu
-------------------------------------------------------------------
Key: GTNPORTAL-1941
URL: https://issues.jboss.org/browse/GTNPORTAL-1941
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: WSRP integration
Affects Versions: 3.1.0-GA
Environment: EPP5.1.1 DEV02 or GateIn trunk (11/06/20)
Reporter: Michal Vanco
Assignee: Chris Laprun
Fix For: 3.2.0-GA
There are 3 options how can be remote portlets added in category in App.registry:
1) auto import - id is: selfv2._richFacesPortlet.richFacesPortlet
2) Add application in category (in Categories menu) - id is: /richFacesPortlet.richFacesPortlet
3) "Click here to add into categories" in "Portlet" menu - Remote portlets, id is: richFacesPortlet.richFacesPortlet
When you add remote portlet on page 1) and 2) works fine.
But for third option gives you:
org.gatein.pc.api.NoSuchPortletException: No such portlet /richFacesPortlet.richFacesPortlet.richFacesPortlet
and portlet isn't rendered on page.
Is there some way how to unify portlet names on different places and fix remote portlet added in Portlet menu?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (GTNWSRP-234) NotSerializableException: com.sun.faces.renderkit.RenderKitFactoryImpl
by Michal Vanco (JIRA)
NotSerializableException: com.sun.faces.renderkit.RenderKitFactoryImpl
----------------------------------------------------------------------
Key: GTNWSRP-234
URL: https://issues.jboss.org/browse/GTNWSRP-234
Project: GateIn WSRP
Issue Type: Bug
Affects Versions: 2.0.0-GA
Environment: EPP5.1.1 DEV01, wsrp 2.0.1-epp51-Beta02
Reporter: Michal Vanco
Assignee: Chris Laprun
Fix For: 2.0.1-GA
Attachments: wsrp_cluster_NSE.txt
I'm getting this error when session is replicated in wsrp-admin-gui.
The scenario was:
- start two EPP5.1.1 instances in cluster
- open loadbalancer and sign in as root, go to WSRP admin portlet
- stop one EPP instance and start it again
- refresh WSRP admin page -> error appears (attached log) and I can't access WSRP portlet anymore
java.lang.IllegalStateException: Cannot reset a commited stream
(even after restart of both instances and deleting cookie)
Note: I've added <distributable /> element in both wsrp-admin-gui.war and wsrp-producer.war web.xml files.
And uriworkermap.properties contains:
/wsrp-admin-gui=loadbalancer
/wsrp-admin-gui/*=loadbalancer
/wsrp-producer=loadbalancer
/wsrp-producer/*=loadbalancer
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (GTNWSRP-236) WSRP Admin portlet doesn't work with distributable element (Non-serializable attribute)
by Michal Vanco (JIRA)
WSRP Admin portlet doesn't work with distributable element (Non-serializable attribute)
---------------------------------------------------------------------------------------
Key: GTNWSRP-236
URL: https://issues.jboss.org/browse/GTNWSRP-236
Project: GateIn WSRP
Issue Type: Bug
Environment: EPP5.1.1 DEV01 (cluster) with <distributable /> element added at wsrp-admin-gui.war
Reporter: Michal Vanco
Assignee: Chris Laprun
Attachments: wsrp-distributable.txt
When you add distributable element in wsrp-admin-gui.war, portlet isn't displayed at all when rendering view (/jsf/consumers/consumers.xhtml).
Full log attached.
Result is that without distributable element, operations in admin portlet aren't replicated on other nodes. (for example consumer is present only on original node)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (GTNPORTAL-1610) Cache portal config for the scope of the request
by Marek Posolda (JIRA)
Cache portal config for the scope of the request
------------------------------------------------
Key: GTNPORTAL-1610
URL: https://jira.jboss.org/browse/GTNPORTAL-1610
Project: GateIn Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Performance
Affects Versions: 3.1.0-GA
Environment: EPP 5.1.0 ER3
Reporter: Marek Posolda
Assignee: Julien Viet
I found another thing for logged user case performance, which can be improved. Issue is that method UserPortalConfigService.getUserPortalConfig() is called two times during HTTP request of logged user. And this method is expensive, because it performs other calls to IDM and DataStorage. So it should be possible to call it only once per HTTP request.
Now it's called from:
1. LocalizationLifecycle.onStartRequest()
2. PortalStateManager.restoreUIRootComponent() . After this call is obtained UserPortalConfig saved as attribute into PortalRequestContext.
It should be possible to save it into PortalRequestContext after LocalizationLifecycle.onStartRequest(), so that PortalStateManager.restoreUIRootComponent() can read it from PortalRequestContext. Or create another Lifecycle class for this purpose (Something similar to UserProfileLifecycle, which is doing similar thing for obtain UserProfile) ?
--
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
14 years, 8 months
[JBoss JIRA] Created: (GTNPORTAL-1912) User Management - Delete user is invalid in special case
by Nguyen Thanh Cong (JIRA)
User Management - Delete user is invalid in special case
--------------------------------------------------------
Key: GTNPORTAL-1912
URL: https://issues.jboss.org/browse/GTNPORTAL-1912
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Nguyen Thanh Cong
r6550
- Go to User Managemnet
- Search a user such as demo
- Delete demo >> successfully. However, demo is still displayed.
- Enter the other keyword to search >> error
Exception:
as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
java.lang.IllegalStateException
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1402)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1361)
at sun.misc.Unsafe.defineClass(Native Method)
at sun.reflect.ClassDefiner.defineClass(ClassDefiner.java:45)
at sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:381)
at java.security.AccessController.doPrivileged(Native Method)
at sun.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:377)
at sun.reflect.MethodAccessorGenerator.generateSerializationConstructor(MethodAccessorGenerator.java:95)
at sun.reflect.ReflectionFactory.newConstructorForSerialization(ReflectionFactory.java:313)
at java.io.ObjectStreamClass.getSerializableConstructor(ObjectStreamClass.java:1327)
at java.io.ObjectStreamClass.access$1500(ObjectStreamClass.java:52)
at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:437)
at java.security.AccessController.doPrivileged(Native Method)
at java.io.ObjectStreamClass.<init>(ObjectStreamClass.java:413)
at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:310)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1106)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
at org.exoplatform.commons.serialization.serial.DataContainer.writeExternal(DataContainer.java:68)
at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1421)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1390)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
at org.exoplatform.commons.serialization.serial.DataContainer.writeExternal(DataContainer.java:68)
at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1421)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1390)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
at org.exoplatform.commons.serialization.serial.DataContainer.writeExternal(DataContainer.java:68)
at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1421)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1390)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
at java.util.ArrayList.writeObject(ArrayList.java:570)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
at org.exoplatform.commons.serialization.serial.DataContainer.writeExternal(DataContainer.java:68)
at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1421)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1390)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
at java.util.ArrayList.writeObject(ArrayList.java:570)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
at org.exoplatform.commons.serialization.serial.DataContainer.writeExternal(DataContainer.java:68)
at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1421)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1390)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
at org.exoplatform.commons.serialization.SerializationContext.write(SerializationContext.java:105)
at org.exoplatform.portal.application.replication.ApplicationState.writeObject(ApplicationState.java:95)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
at org.apache.catalina.session.StandardSession.writeObject(StandardSession.java:1546)
at org.apache.catalina.session.StandardSession.writeObjectData(StandardSession.java:989)
at org.apache.catalina.session.StandardManager.doUnload(StandardManager.java:517)
at org.apache.catalina.session.StandardManager.unload(StandardManager.java:463)
at org.apache.catalina.session.StandardManager.stop(StandardManager.java:667)
at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4611)
at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:924)
at org.apache.catalina.startup.HostConfig.undeployApps(HostConfig.java:1319)
at org.apache.catalina.startup.HostConfig.stop(HostConfig.java:1290)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:323)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1086)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1098)
at org.apache.catalina.core.StandardEngine.stop(StandardEngine.java:448)
at org.apache.catalina.core.StandardService.stop(StandardService.java:587)
at org.apache.catalina.core.StandardServer.stop(StandardServer.java:744)
at org.apache.catalina.startup.Catalina.stop(Catalina.java:648)
at org.apache.catalina.startup.Catalina$CatalinaShutdownHook.run(Catalina.java:692)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Created: (GTNPORTAL-1886) Disabling option "associationMembershipType" in idm-configuration.xml when only DB (Hibernate) is used as identity store
by Marek Posolda (JIRA)
Disabling option "associationMembershipType" in idm-configuration.xml when only DB (Hibernate) is used as identity store
------------------------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-1886
URL: https://issues.jboss.org/browse/GTNPORTAL-1886
Project: GateIn Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Identity integration
Affects Versions: 3.1.0-GA
Environment: EPP 5.1.0.GA
Reporter: Marek Posolda
Assignee: Boleslaw Dawidowicz
Priority: Minor
Fix For: 3.2.0-GA
Right now, this option is enabled in idm-configuration.xml with value "member" . It means that when we are creating new membership with type "member", we need to call two picketlink API operations:
1) getIdentitySession().getRoleManager().createRole(mt.getName(), user.getUserName(), groupId)
2) getIdentitySession().getRelationshipManager().associateUserByKeys(groupId, user.getUserName())
I think that second call to relationshipManager is redundant and it does not make much sense. We don't need unnamed relationship when we already have named relationship with type "member" created by RoleManager.
Right now, with option enabled, there are more necessary calls to Picketlink API and also more records in DB. Especially we have 2 records in DB in table "jbid_io_rel" for each membership of type "member" . One with NAME=NULL and one with NAME=2 (member)
For example:
mysql> select jbid_io_rel.* from jbid_io_rel inner join jbid_io on jbid_io.ID=jbid_io_rel.TO_IDENTITY where jbid_io.name like "john";
+----+---------------+------+-------------+----------+
| ID | FROM_IDENTITY | NAME | TO_IDENTITY | REL_TYPE |
+----+---------------+------+-------------+----------+
| 22 | 3 | NULL | 19 | 1 |
| 23 | 3 | 2 | 19 | 2 |
| 24 | 4 | NULL | 19 | 1 |
| 25 | 4 | 2 | 19 | 2 |
| 26 | 8 | 1 | 19 | 2 |
+----+---------------+------+-------------+----------+
5 rows in set (0,00 sec)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months