Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Message-ID: <31632490.1185774893080.JavaMail.jira@brutus>
Date: Sun, 29 Jul 2007 22:54:53 -0700 (PDT)
From: "Damitha Kumarage (JIRA)" <jira@apache.org>
To: axis-c-dev@ws.apache.org
Subject: [jira] Commented: (AXIS2C-624) module handlers are invoked for
 service even when module is not engaged for the serivce
In-Reply-To: <32450615.1182506440119.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AXIS2C-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516281 ] 

Damitha Kumarage commented on AXIS2C-624:
-----------------------------------------

The problem is that phases are shared between operations and owner of phase is phases_info.
So if I refer to the example I mentioned in my previous comment when service X is loaded if handler H is added to the Module M specifc phase, then when service Y is loaded since the same phase is used the the previously added H handler is also availble for this service operation too.
To avoid this I make the operation the owner of the phases and avoid reusing the phases.
This is done by following change

Before
            phase = axutil_hash_get(phases_info->op_in_phases, phase_name,
                AXIS2_HASH_KEY_STRING);
            if(!phase)
            {
                phase = axis2_phase_create(env, phase_name);
                axutil_hash_set(phases_info->op_in_phases, phase_name,
                    AXIS2_HASH_KEY_STRING, phase);
            }
            status = axutil_array_list_add(op_in_phases, env, phase);
Now
           phase = axis2_phase_create(env, phase_name);
            status = axutil_array_list_add(op_in_phases, env, phase);

I'll commit this code if no side effects are reported

> module handlers are invoked for service even when module is not engaged for the serivce
> ---------------------------------------------------------------------------------------
>
>                 Key: AXIS2C-624
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-624
>             Project: Axis2-C
>          Issue Type: Bug
>            Reporter: Damitha Kumarage
>            Priority: Blocker
>
> I can see that even when a module is not engaged to a service(globally or service wise) handlers of that module is invoked
> for that service. This happens both for in and out path.
> This must be due to a change done to the engine very recently. I can cleary remember this was working correctly when I was testing sandesha2/C for release 0.90

-- 
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