You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Alessandro Adamou (JIRA)" <ji...@apache.org> on 2011/07/05 14:22:16 UTC

[jira] [Updated] (STANBOL-247) More robust OntoNet session management

     [ https://issues.apache.org/jira/browse/STANBOL-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alessandro Adamou updated STANBOL-247:
--------------------------------------

    Description: 
CRUD methods (both Java and RESTful) on OntoNet Sessions must improve the concurrent management of sessions and associated resources:

- If a session is destroyed (e.g. by the deactivate() method of a component), when other components try to destroy it they throw exceptions. They should instead log warnings, as it is generally safe to destroy an already destroyed session.

- Session methods should be synchronized on the shared resources (e..g ontologies) they use.

  was:
Session CRUD methods should be synchronized and resistant to null sessions.

RESTful API should encompass the whole session lifecycle management. Also, destructive operations over SSL should be considered.


> More robust OntoNet session management
> --------------------------------------
>
>                 Key: STANBOL-247
>                 URL: https://issues.apache.org/jira/browse/STANBOL-247
>             Project: Stanbol
>          Issue Type: Improvement
>          Components: KReS
>            Reporter: Alessandro Adamou
>            Assignee: Alessandro Adamou
>            Priority: Minor
>
> CRUD methods (both Java and RESTful) on OntoNet Sessions must improve the concurrent management of sessions and associated resources:
> - If a session is destroyed (e.g. by the deactivate() method of a component), when other components try to destroy it they throw exceptions. They should instead log warnings, as it is generally safe to destroy an already destroyed session.
> - Session methods should be synchronized on the shared resources (e..g ontologies) they use.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Re: [jira] [Updated] (STANBOL-247) More robust OntoNet session management

Posted by Enrico Daga <en...@gmail.com>.
Thank you Alessandro, now I understand :)
Enrico

On 5 July 2011 14:22, Alessandro Adamou (JIRA) <ji...@apache.org> wrote:
>
>     [ https://issues.apache.org/jira/browse/STANBOL-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Alessandro Adamou updated STANBOL-247:
> --------------------------------------
>
>    Description:
> CRUD methods (both Java and RESTful) on OntoNet Sessions must improve the concurrent management of sessions and associated resources:
>
> - If a session is destroyed (e.g. by the deactivate() method of a component), when other components try to destroy it they throw exceptions. They should instead log warnings, as it is generally safe to destroy an already destroyed session.
>
> - Session methods should be synchronized on the shared resources (e..g ontologies) they use.
>
>  was:
> Session CRUD methods should be synchronized and resistant to null sessions.
>
> RESTful API should encompass the whole session lifecycle management. Also, destructive operations over SSL should be considered.
>
>
>> More robust OntoNet session management
>> --------------------------------------
>>
>>                 Key: STANBOL-247
>>                 URL: https://issues.apache.org/jira/browse/STANBOL-247
>>             Project: Stanbol
>>          Issue Type: Improvement
>>          Components: KReS
>>            Reporter: Alessandro Adamou
>>            Assignee: Alessandro Adamou
>>            Priority: Minor
>>
>> CRUD methods (both Java and RESTful) on OntoNet Sessions must improve the concurrent management of sessions and associated resources:
>> - If a session is destroyed (e.g. by the deactivate() method of a component), when other components try to destroy it they throw exceptions. They should instead log warnings, as it is generally safe to destroy an already destroyed session.
>> - Session methods should be synchronized on the shared resources (e..g ontologies) they use.
>
> --
> This message is automatically generated by JIRA.
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>



-- 
Enrico Daga

--
http://www.enridaga.net
skype: enri-pan