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 "Samisa Abeysinghe (JIRA)" <ji...@apache.org> on 2006/01/22 16:41:15 UTC

[jira] Commented: (AXIS2C-22) Dispatchers do not get loaded properly

    [ http://issues.apache.org/jira/browse/AXIS2C-22?page=comments#action_12363571 ] 

Samisa Abeysinghe commented on AXIS2C-22:
-----------------------------------------

Diff with the previous rivision shows me the following. Should we not have this code? Whay was it removed?

--- conf_builder.c      (revision 370104)
+++ conf_builder.c      (working copy)
@@ -228,25 +228,7 @@
         AXIS2_CONF_ADD_MSG_RECV(builder_impl->conf, env, att_value, msg_recv);
         AXIS2_QNAME_FREE(qmep, env);
     }
-
-    /* processing Dispatching Order */
-    qdisporder = axis2_qname_create(env, AXIS2_DISPATCH_ORDER, NULL, NULL);
-    disp_order_element = AXIS2_OM_ELEMENT_GET_FIRST_CHILD_WITH_QNAME(
-        conf_element, env, qdisporder, conf_node, &disp_order_node);
-    AXIS2_QNAME_FREE(qdisporder, env);
-    if(NULL != disp_order_element)
-    {
-        axis2_conf_builder_process_disp_order(conf_builder, env, disp_order_node);
-        /*log.info("found the custom disptaching order and continue with that order");*/
-    } else
-    {
-        status = AXIS2_CONF_SET_DEFAULT_DISPATCHERS(builder_impl->conf, env);
-        if(AXIS2_SUCCESS != status)
-        {
-            return AXIS2_FAILURE;
-        }
-        /*log.info("no custom diaptching order found continue with default dispatcing order");*/
-    }


> Dispatchers do not get loaded properly
> --------------------------------------
>
>          Key: AXIS2C-22
>          URL: http://issues.apache.org/jira/browse/AXIS2C-22
>      Project: Axis2-C
>         Type: Bug
>   Components: core/deployment
>     Reporter: Samisa Abeysinghe
>     Priority: Blocker
>      Fix For: M0.3

>
> There seem to be some problem in loading the dispatchers.
> As I remember this was working last Thursday. But some change has caused the addressing despathcer not to load :(

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