You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Suat Gonul (Resolved) (JIRA)" <ji...@apache.org> on 2011/12/16 14:56:30 UTC
[jira] [Resolved] (STANBOL-434) Add session management for not
using a new session in each operation
[ https://issues.apache.org/jira/browse/STANBOL-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suat Gonul resolved STANBOL-434.
--------------------------------
Resolution: Fixed
Implemented in revision 1215106
> Add session management for not using a new session in each operation
> --------------------------------------------------------------------
>
> Key: STANBOL-434
> URL: https://issues.apache.org/jira/browse/STANBOL-434
> Project: Stanbol
> Issue Type: Improvement
> Components: CMS Adaptor
> Reporter: Suat Gonul
>
> Currently, for each operation in CMS Adapter, a new session is obtained with the provided connection parameters. Instead of doing this, newly created sessions would be cached and they can be used later on. Furthermore, already available sessions can be used. This would make OSGI based integration easier as in sling-stanbol case.
> When using REST services, first a session would be created and cached and this same session is used in subsequent operations by a session key corresponding to the cached session.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira