[Portfolio] OSP SiteEventListener.java
holladay at longsight.com
Fri Oct 26 13:39:42 PDT 2012
I've resolved this jira. My local tests show no negative effect.
Could someone from OSP verify this on the sakai nightly build?
On Thu, Sep 20, 2012 at 3:23 PM, Bryan Holladay <holladay at longsight.com> wrote:
> I created the jira here: https://jira.sakaiproject.org/browse/SAK-22653
> On Thu, Sep 20, 2012 at 3:19 PM, Bryan Holladay <holladay at longsight.com> wrote:
>> I removed the listened locally and created a new site without any
>> tools. Then added all OSP tools, checked permissions and they were
>> all there. Then removed and re-added the tools again and still there.
>> This makes sense since OSP used to have a different permission
>> handling system and now that its on Sakai's it should behave the same.
>> I can commit this to trunk if everyone else agrees (let me know).
>> Also, I think this should go into 2.9.x since it's a huge slowdown for
>> On Wed, Sep 19, 2012 at 10:48 PM, Maurer, Christopher Wayne
>> <chmaurer at iupui.edu> wrote:
>>> I believe that's the listener that allowed osp tools to get default
>>> permissions after adding a tool to the site. I know that it was used back
>>> in the day before we integrated with the normal sakai template permission
>>> stuff, so it's possible that it isn't necessary anymore. Might try not
>>> registering it and see if tool permissions still look right when
>>> adding/removing tools.
>>> On 9/19/12 4:15 PM, "Bryan Holladay" <holladay at longsight.com> wrote:
>>>>What does this class do?
>>>>I am running Yourkit and this stood out as 79% of the load when
>>>>SiteService.save(Site) is called. I've attached a screen shot. Is it
>>>>ok to turn off or disable w/sakai.property?
More information about the portfolio