[ 
https://issues.apache.org/jira/browse/AXIS2C-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569733#action_12569733
 ] 

Senaka Fernando commented on AXIS2C-645:
----------------------------------------

Hi Sahan,

OK, I agree with you. But, we have another problem.

What seems to be happening is that the configuration does not know about the 
configuration context and the configuration context not knowing about the 
modules, but the modules knowing about the configuration context. Of course 
there seems to be a better "hack", which is that the module keeping a reference 
to the conf_ctx. Which will get your problem solved in no time. But, you are 
not supposed to do that. It is because the core will have no idea that the 
module is sharing its responsibilities.

* According to the current layout, a configuration context has a configuration. 
A configuration would know about modules. But, a configuration would 
necessarily not know about the configuration context.

* And, we have a configuration initializer that knows about all these 
components. It is rather a builder, and that may delegate resources to the 
conf, modules etc.

* For the shutdown process, we don't have a manager. It is merely a freeing of 
resources that lead into calling the shutdown method.

Thus, to facilitate your requirement, Sahan, it seems that we will have to 
introduce a manager to oversee the shutdown process, which AFAIK is not 
possible in C, as there is no way to free the manager. Thus, we'll have to 
introduce an overall manager for the whole core plus modules etc, to manage the 
entire engine (similar to a runtime).

If you simply think about this issue in a C programmer's perspective I believe 
this can be achieved, but, thinking in an OO perspective it requires an 
architectural level change.

> Need to pass configuration context to axis2_module_shutdown()
> -------------------------------------------------------------
>
>                 Key: AXIS2C-645
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-645
>             Project: Axis2-C
>          Issue Type: Improvement
>          Components: core/description
>    Affects Versions: Current (Nightly)
>            Reporter: Sahan Gamage
>            Priority: Minor
>
> We need to pass configuration context to module shutdown function since 
> modules might have pushed module specific data as parameters to configuration 
> context. Cleaning module specific data by the module itself and not by the 
> axis2 core is the most suitable way I believe.

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to