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

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

Hi Sahan,

I'll try to contact the sandesha folks first. And, well, I guess the dependency 
is not library/code wise, but execution logic wise. The core is told what to do 
and simply does it. But, no other module shares responsibility in  doing any 
core tasks. But, this fix would violate that. That's what I meant by violation 
of abstraction. It is because you are asking for control over resources 
delegated beyond the interface boundary, for which you didn't retain ownership.

Therefore, we should rather maintain a table of references, with appropriate 
cleanup procedures. These can be called at module_shutdown(). This will rather 
not affect the abstraction as mentioned in the Axis2 architecture. This is 
because this table will lie in the module side of the interface boundary and 
thus would act as a certification of ownership. Thus, the module will gain 
control over module specific detail.

Obviously the core would have more control over cleaning up module data. And, 
the module specific cleanup would be an assert to the existing logic rather 
than a replacement. Thus, you'll have to be certain on whether you let the core 
do the cleanup or you do the cleanup. This can and should be controlled within 
the module_init() function.

Regards,
Senaka

> 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