You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Luciana Moreira (JIRA)" <ji...@apache.org> on 2010/11/11 17:52:14 UTC
[jira] Created: (AXIS2-4879) Enable setting
ConfigContextTimeoutInterval OR LastTouchedTime to 0 programmatically
Enable setting ConfigContextTimeoutInterval OR LastTouchedTime to 0 programmatically
------------------------------------------------------------------------------------
Key: AXIS2-4879
URL: https://issues.apache.org/jira/browse/AXIS2-4879
Project: Axis2
Issue Type: Improvement
Affects Versions: 1.5
Reporter: Luciana Moreira
We would like to be able to have a better control over the soap sessions. More specifically we would like to be able to clean the soap session when at the application level we are aware that this session with the client should no longer exist.
This issue has been posted in the mailing list. But due to the lack of responses I concluded that this is currently not existing. Therefore this is my request for improvement.
http://markmail.org/message/xa4ljqjp6bud6old
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Assigned: (AXIS2-4879) Enable setting
ConfigContextTimeoutInterval OR LastTouchedTime to 0 programmatically
Posted by "Afkham Azeez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Afkham Azeez reassigned AXIS2-4879:
-----------------------------------
Assignee: Afkham Azeez
> Enable setting ConfigContextTimeoutInterval OR LastTouchedTime to 0 programmatically
> ------------------------------------------------------------------------------------
>
> Key: AXIS2-4879
> URL: https://issues.apache.org/jira/browse/AXIS2-4879
> Project: Axis2
> Issue Type: Improvement
> Affects Versions: 1.5
> Reporter: Luciana Moreira
> Assignee: Afkham Azeez
>
> We would like to be able to have a better control over the soap sessions. More specifically we would like to be able to clean the soap session when at the application level we are aware that this session with the client should no longer exist.
> This issue has been posted in the mailing list. But due to the lack of responses I concluded that this is currently not existing. Therefore this is my request for improvement.
> http://markmail.org/message/xa4ljqjp6bud6old
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4879) Enable setting
ConfigContextTimeoutInterval OR LastTouchedTime to 0 programmatically
Posted by "Ralf Hauser (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931140#action_12931140 ]
Ralf Hauser commented on AXIS2-4879:
------------------------------------
and AXIS2-3699
> Enable setting ConfigContextTimeoutInterval OR LastTouchedTime to 0 programmatically
> ------------------------------------------------------------------------------------
>
> Key: AXIS2-4879
> URL: https://issues.apache.org/jira/browse/AXIS2-4879
> Project: Axis2
> Issue Type: Improvement
> Affects Versions: 1.5
> Reporter: Luciana Moreira
>
> We would like to be able to have a better control over the soap sessions. More specifically we would like to be able to clean the soap session when at the application level we are aware that this session with the client should no longer exist.
> This issue has been posted in the mailing list. But due to the lack of responses I concluded that this is currently not existing. Therefore this is my request for improvement.
> http://markmail.org/message/xa4ljqjp6bud6old
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4879) Enable setting
ConfigContextTimeoutInterval OR LastTouchedTime to 0 programmatically
Posted by "Ralf Hauser (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931139#action_12931139 ]
Ralf Hauser commented on AXIS2-4879:
------------------------------------
see also AXIS2-2956
> Enable setting ConfigContextTimeoutInterval OR LastTouchedTime to 0 programmatically
> ------------------------------------------------------------------------------------
>
> Key: AXIS2-4879
> URL: https://issues.apache.org/jira/browse/AXIS2-4879
> Project: Axis2
> Issue Type: Improvement
> Affects Versions: 1.5
> Reporter: Luciana Moreira
>
> We would like to be able to have a better control over the soap sessions. More specifically we would like to be able to clean the soap session when at the application level we are aware that this session with the client should no longer exist.
> This issue has been posted in the mailing list. But due to the lack of responses I concluded that this is currently not existing. Therefore this is my request for improvement.
> http://markmail.org/message/xa4ljqjp6bud6old
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org