You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Damitha Kumarage (JIRA)" <ji...@apache.org> on 2008/06/26 08:24:45 UTC
[jira] Resolved: (AXIS2C-1202) Loading modules in alphabetical
order has a problem when using module operation level "module ref"
[ https://issues.apache.org/jira/browse/AXIS2C-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Damitha Kumarage resolved AXIS2C-1202.
--------------------------------------
Resolution: Fixed
Assignee: Damitha Kumarage (was: S.Uthaiyashankar)
This problem currenlty occurs if your modules A and B are engaged to a perticular service say S. If both are engaged globally by adding module refs to axis2.xml then this problem should not occur. I have fixed this and see below for information of my fix.
The problem you face is due to this reason. Currently when adding a module operation to a perticular service it retrieve all engaged modules to the axis2_conf and add handlers of those modules into the operations exection chain.
Now suppose your module A is engaged first to the service. Then it is added to the services engaged modules list only, not to the conf's engageed module list.
Now suppose your module B has a module operation. When this module is engaged to the service it add that module operation to the service. At that time it retrieve all the engaged modules to the conf and add their handlers to the operation's execution chain. The handlers of module A is not added to this execution chain because it is engaged to the service S only. My fix is to retrieve the modules engaged to the service as well and add their handlers to the module operation's execution chain.
This shoud fix your problem.
> Loading modules in alphabetical order has a problem when using module operation level "module ref"
> --------------------------------------------------------------------------------------------------
>
> Key: AXIS2C-1202
> URL: https://issues.apache.org/jira/browse/AXIS2C-1202
> Project: Axis2-C
> Issue Type: Bug
> Components: core/deployment
> Affects Versions: Current (Nightly)
> Reporter: S.Uthaiyashankar
> Assignee: Damitha Kumarage
>
> Axis2/C loads modules in alphabetical order. Suppose we have module 'A' and module 'B' then A will be loaded before B. If A is having an operation defined in module level, which is having a "module ref" to 'B', then deployment engine cannot resolve it.
--
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org