Re: AXIS2 V1.2; Rampart 1.2: Error msg: The "Dispatch" phase is not found on the global "InFlow" phase of the axis2.xml file

[Amila Suriarachchi]

why you have given the Dispatch phase in Transport phase handlers

<phase name="Transport">
           <handler name="RequestURIBasedDispatcher"
                    class="
org.apache.axis2.engine.RequestURIBasedDispatcher">
               <order phase="Dispatch"/>
           </handler>
           <handler name="SOAPActionBasedDispatcher"
                    class="
org.apache.axis2.engine.SOAPActionBasedDispatcher">
               <order phase="Dispatch"/>
           </handler>
       </phase>

try changing the
<order phase="Dispatch"/>
to
<order phase="Transport"/>

But anyway this could be a phase rule excecution problem.


On 7/20/07, Par Nagi <[EMAIL PROTECTED]> wrote:

Hi,

I am getting: The "Dispatch" phase is not found on the global "InFlow"
phase of the axis2.xml file when running a simple client. The failure
happens at:

     ConfigurationContext configContext =
ConfigurationContextFactory
.createConfigurationContextFromFileSystem("../../client_repo",
"../../client_repo/conf/client.axis2.xml" );

I tried this with a client.axis2.xml file that is listed below.

The classpath for the executing client contains the following libraries:

xmlsec-1.4.0.jar;wss4j-1.5.2.jar;axiom-api-1.2.4.jar;axiom-impl-1.2.4.jar
;axis2-adb-1.2.jar;axis2-kernel-1.2.jar;stax-api-1.0.1.jar;.;rampart-
policy-1.2.jar;XmlSchema-1.3.1.jar;commons-httpclient-3.0.1.jar;commons-
codec-1.3.jar;rampart-1.2\lib\xmlsec-1.4.0.jar;axis2-dom-1.2.4.jar;wsdl4j-
1.6.2.jar;activation-1.1.jar;wstx-asl-3.2.1.jar;rampart-trust-1.2.jar;rampart-
core-1.2.jar;commons-logging-1.1.jar;

Appreciate any info on what might be causing this.

- Nagi

=== client.axis2.xml ===
<axisconfig name="AxisJava2.0">

    <module ref="rampart" />

    <parameter name="hotdeployment" locked="false">true</parameter>
    <parameter name="hotupdate" locked="false">true</parameter>

    <parameter name="OutflowSecurity">
      <action>
        <items>UsernameToken</items>
         <user>wss4j</user>
     <passwordCallbackClass>ClientPWCallback</passwordCallbackClass>
      </action>
    </parameter>

    <messageReceiver mep="INOUT" class="
org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>

    <transportSender name="http" class="
org.apache.axis2.transport.http.CommonsHTTPTransportSender">
        <parameter name="PROTOCOL" locked="false">HTTP/1.0</parameter>
    </transportSender>

   <phaseOrder type="inflow">
        <!--  System pre defined phases       -->
         <phase name="Transport">
            <handler name="RequestURIBasedDispatcher"
                     class="
org.apache.axis2.engine.RequestURIBasedDispatcher">
                <order phase="Dispatch"/>
            </handler>
            <handler name="SOAPActionBasedDispatcher"
                     class="
org.apache.axis2.engine.SOAPActionBasedDispatcher">
                <order phase="Dispatch"/>
            </handler>
        </phase>
        <phase name="Security"/>
        <phase name="PreDispatch"/>
        <phase name="Dispatch" class="
org.apache.axis2.engine.DispatchPhase">
            <handler name="AddressingBasedDispatcher"
                     class="
org.apache.axis2.engine.AddressingBasedDispatcher">
                <order phase="Dispatch"/>
            </handler>

            <handler name="SOAPMessageBodyBasedDispatcher"
                     class="
org.apache.axis2.engine.SOAPMessageBodyBasedDispatcher">
                <order phase="Dispatch"/>
            </handler>
            <handler name="InstanceDispatcher"
                     class="org.apache.axis2.engine.InstanceDispatcher">
                <order phase="PostDispatch"/>
            </handler>
        </phase>
        <!--  System pre defined phases       -->
        <!--   After Postdispatch phase module author or or service author
can add any phase he want      -->
        <phase name="OperationInPhase"/>
    </phaseOrder>
    <phaseOrder type="outflow">
        <!--      user can add his own phases to this area  -->
        <phase name="OperationOutPhase"/>
        <!--system predefined phase-->
        <!--these phase will run irrespective of the service-->
        <phase name="PolicyDetermination"/>
        <phase name="MessageOut"/>
    </phaseOrder>
    <phaseOrder type="INfaultflow">
        <phase name="PreDispatch"/>
        <phase name="Dispatch" class="
org.apache.axis2.engine.DispatchPhase">
            <handler name="RequestURIBasedDispatcher"
                     class="
org.apache.axis2.engine.RequestURIBasedDispatcher">
                <order phase="Dispatch"/>
            </handler>

            <handler name="SOAPActionBasedDispatcher"
                     class="
org.apache.axis2.engine.SOAPActionBasedDispatcher">
                <order phase="Dispatch"/>
            </handler>

            <handler name="AddressingBasedDispatcher"
                     class="
org.apache.axis2.engine.AddressingBasedDispatcher">
                <order phase="Dispatch"/>
            </handler>

            <handler name="SOAPMessageBodyBasedDispatcher"
                     class="
org.apache.axis2.engine.SOAPMessageBodyBasedDispatcher">
                <order phase="Dispatch"/>
            </handler>
            <handler name="InstanceDispatcher"
                     class="org.apache.axis2.engine.InstanceDispatcher">
                <order phase="PostDispatch"/>
            </handler>
        </phase>
        <!--      user can add his own phases to this area  -->
        <phase name="OperationInFaultPhase"/>
    </phaseOrder>
    <phaseOrder type="Outfaultflow">
        <!--      user can add his own phases to this area  -->
        <phase name="OperationOutFaultPhase"/>
        <phase name="PolicyDetermination"/>
        <phase name="MessageOut"/>
    </phaseOrder>

</axisconfig>

--
Amila Suriarachchi,
WSO2 Inc.