[JBoss JIRA] Created: (GTNPORTAL-1909) adding a null as an argument to EventListeners in Organization Service API should be forbidden
by Viliam Rockai (JIRA)
adding a null as an argument to EventListeners in Organization Service API should be forbidden
----------------------------------------------------------------------------------------------
Key: GTNPORTAL-1909
URL: https://issues.jboss.org/browse/GTNPORTAL-1909
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Identity integration
Reporter: Viliam Rockai
Assignee: Boleslaw Dawidowicz
you can add a null object through add*EventListener(*EventListener e) in nearly all handlers:
userHandler_ = service_.getUserHandler();
profileHandler_ = service_.getUserProfileHandler();
groupHandler_ = service_.getGroupHandler();
membershipHandler_ = service_.getMembershipHandler();
and that will mess the code later by throwing NullPointerException, when calling other methods from the API - I think it should throw NullPointerException right away.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (GTNPORTAL-1866) Issue with picketlink cache - cached items are never evicted
by Marek Posolda (JIRA)
Issue with picketlink cache - cached items are never evicted
------------------------------------------------------------
Key: GTNPORTAL-1866
URL: https://issues.jboss.org/browse/GTNPORTAL-1866
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: EPP 5.1.0.GA, Picketlink version is 1.1.7.GA
Reporter: Marek Posolda
Assignee: Boleslaw Dawidowicz
I think there is issue related to expiration of JBoss cache entries, which are used for picketlink cache. Right now, JBoss cache in server/default/deploy/gatein.ear/02portal.war/WEB-INF/organization/picketlink-idm/jboss-cache.xml and jboss-cache-cluster.xml is configured to use Expiration algorithm:
<eviction wakeUpInterval="5000">
<default algorithmClass="org.jboss.cache.eviction.ExpirationAlgorithm"
eventQueueSize="1000000">
<property name="maxNodes" value="100000" />
<property name="timeToLive" value="120000" />
<property name="warnNoExpirationKey" value="false" />
</default>
</eviction>
Problem is that ExpirationAlgorithm requires support in Java code for eviction, which is mentioned in http://docs.jboss.org/jbosscache/3.1.0.CR1/userguide_en/html/eviction_pol... . There is need to call something like:
// sets the expiry time for a node
cache.getRoot().addChild(fqn1).put(ExpirationConfiguration.EXPIRATION_KEY, future);
otherwise node is never evicted periodically. And I am seeing that this is not called in Picketlink code and GateIn+Picketlink integration code. And I am seeing in JMX that nodes are never evicted automatically after some time. Fact is that entries are cleared from cache only by trigger of some events (For example after update of some user are entries for this user evicted from cache).
Last week I was working on application for adding users into GateIn IDM database only with plain SQL. And when I create users, I am not seeing them in organization management portlet because query for get all users is never evicted from cache. I need to restart my GateIn portal or trigger JMX eviction of picketlink cache (Operation "invalidateAll" on MBean exo:name=plidmcache,portal="portal",service=PicketLinkIDMCacheService .
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (GTNPORTAL-1824) We should implement all Unsupported method in UserHandler interface
by Khoi Nguyen (JIRA)
We should implement all Unsupported method in UserHandler interface
-------------------------------------------------------------------
Key: GTNPORTAL-1824
URL: https://issues.jboss.org/browse/GTNPORTAL-1824
Project: GateIn Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Khoi Nguyen
Currently, some methods in UserHandler have been deprecated and suggested to use other method such as
* getUserPageList -> findAllUsers
* findUsers -> findUsersByQuery
* findUsersByGroup -> findUsersByGroupId
Unfortunately, these methods haven't been implemented yet and throw UnsupportedOperationException, there're very confusing for developer who want to use this API, so we must implement them as soon as possible.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months