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 "Chamikara Jayalath (JIRA)" <ji...@apache.org> on 2005/10/05 05:43:50 UTC
[jira] Created: (AXIS2-268) Modules need the configurationContext object(s) in initialization
Modules need the configurationContext object(s) in initialization
-----------------------------------------------------------------
Key: AXIS2-268
URL: http://issues.apache.org/jira/browse/AXIS2-268
Project: Apache Axis 2.0 (Axis2)
Type: Improvement
Components: deployment
Reporter: Chamikara Jayalath
We found the scnario of Modules needing the cofigurationContext object in initialization, currently the method module.init (axisConfiguration) is available, but there is no way to access the configurationContext object (s).
Scenario:
Sandesha2 uses context hierarcy serialization feature of axis2 to provide true persistance. Everything belong to Axis2 is saved in the configurationContext and we asks the axis2 system to save the state time to time (and it get saved nicely). But in a restart of the system, we need the configurationContext object again to continue the work from where it stopped. But currently there is no way to access it.
Chamikara
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-268) Modules need the configurationContext object(s) in initialization
Posted by "Chamikara Jayalath (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-268?page=comments#action_12331350 ]
Chamikara Jayalath commented on AXIS2-268:
------------------------------------------
This is needed only in system restoring. This is not needed in the first startup. (and may not be possible due to the unavailability of configurationContext object(s) )
> Modules need the configurationContext object(s) in initialization
> -----------------------------------------------------------------
>
> Key: AXIS2-268
> URL: http://issues.apache.org/jira/browse/AXIS2-268
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: deployment
> Reporter: Chamikara Jayalath
>
> We found the scnario of Modules needing the cofigurationContext object in initialization, currently the method module.init (axisConfiguration) is available, but there is no way to access the configurationContext object (s).
> Scenario:
> Sandesha2 uses context hierarcy serialization feature of axis2 to provide true persistance. Everything belong to Axis2 is saved in the configurationContext and we asks the axis2 system to save the state time to time (and it get saved nicely). But in a restart of the system, we need the configurationContext object again to continue the work from where it stopped. But currently there is no way to access it.
> Chamikara
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (AXIS2-268) Modules need the configurationContext
object(s) in initialization
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-268?page=all ]
Deepal Jayasinghe resolved AXIS2-268:
-------------------------------------
Resolution: Fixed
now the init method is as follows
init(ConfigurationContext configContext, AxisModule module)
> Modules need the configurationContext object(s) in initialization
> -----------------------------------------------------------------
>
> Key: AXIS2-268
> URL: http://issues.apache.org/jira/browse/AXIS2-268
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: deployment
> Reporter: Chamikara Jayalath
> Assignee: Deepal Jayasinghe
>
> We found the scnario of Modules needing the cofigurationContext object in initialization, currently the method module.init (axisConfiguration) is available, but there is no way to access the configurationContext object (s).
> Scenario:
> Sandesha2 uses context hierarcy serialization feature of axis2 to provide true persistance. Everything belong to Axis2 is saved in the configurationContext and we asks the axis2 system to save the state time to time (and it get saved nicely). But in a restart of the system, we need the configurationContext object again to continue the work from where it stopped. But currently there is no way to access it.
> Chamikara
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (AXIS2-268) Modules need the configurationContext
object(s) in initialization
Posted by "Eran Chinthaka (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-268?page=all ]
Eran Chinthaka reassigned AXIS2-268:
------------------------------------
Assign To: Deepal Jayasinghe
> Modules need the configurationContext object(s) in initialization
> -----------------------------------------------------------------
>
> Key: AXIS2-268
> URL: http://issues.apache.org/jira/browse/AXIS2-268
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: deployment
> Reporter: Chamikara Jayalath
> Assignee: Deepal Jayasinghe
>
> We found the scnario of Modules needing the cofigurationContext object in initialization, currently the method module.init (axisConfiguration) is available, but there is no way to access the configurationContext object (s).
> Scenario:
> Sandesha2 uses context hierarcy serialization feature of axis2 to provide true persistance. Everything belong to Axis2 is saved in the configurationContext and we asks the axis2 system to save the state time to time (and it get saved nicely). But in a restart of the system, we need the configurationContext object again to continue the work from where it stopped. But currently there is no way to access it.
> Chamikara
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira