Dear Robert,

I have made sure that axis2-soapmonitor*.mar was in my modules folder as well as axis2-soapmonitor*.jar in WEB-INF/lib.

so, should i try it with the latest nightly build or is there any other possibility that i might do something wrong? Please comment..

     Thank you,
     Wan

From: "robert lazarski" <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: [Axis2 v1.0] soapmonitor, how to use
Date: Wed, 5 Jul 2006 10:56:42 -0300

Looks fine to me. And I just gave the soapmonitor a spin on a recent
nightly build and its running fine. My guess, however, is either you
don't have the axis2-soapmonitor*.mar in modules or
axis2-soapmonitor*.jar in WEB-INF/lib .

If all else fails, but axis2 in debug via
WEB-INF/classes/log4j.properties , etc,  and send the ouput to the
list.

HTH,
Robert
http://www.braziloutsource.com/

On 7/5/06, Wan Kaveevivitchai <[EMAIL PROTECTED]> wrote:
can you see what is wrong with my axis2.xml?
i have tried so many different configuration.

<axisconfig name="AxisJava2.0">
    <!-- ================================================= -->
    <!-- Parameters -->
    <!-- ================================================= -->
    <parameter name="hotdeployment" locked="false">true</parameter>
    <parameter name="hotupdate" locked="false">false</parameter>
    <parameter name="enableMTOM" locked="false">true</parameter>

    <parameter name="cacheAttachments" locked="false">true</parameter>
    <parameter name="attachmentDIR"
locked="false">/users/alice3/home/</parameter>
    <parameter name="sizeThreshold" locked="false">4000</parameter>

    <!--This will give out the timout of the configuration contexts, in
seconds-->
    <parameter name="ConfigContextTimeoutInterval"
locked="false">30</parameter>

<!--During a fault, stacktrace can be sent with the fault message. The
following flag will control -->
    <!--that behaviour.-->
    <parameter name="sendStacktraceDetailsWithFaults"
locked="false">true</parameter>

    <!--If there aren't any information available to find out the fault
reason, we set the message of the expcetion-->
<!--as the faultreason/Reason. But when a fault is thrown from a service
or some where, it will be -->
    <!--wrapped by different levels. Due to this the initial exception
message can be lost. If this flag-->
    <!--is set then, Axis2 tries to get the first exception and set its
message as the faultreason/Reason.-->
    <parameter name="DrillDownToRootCauseForFaultReason"
locked="false">false</parameter>

    <parameter name="userName" locked="false">admin</parameter>
    <parameter name="password" locked="false">axis2</parameter>

    <!--<parameter name="contextPath" locked="false">axis2</parameter>-->
<!--<parameter name="servicePath" locked="false">services</parameter>--> <!--Set the flag to true if you want to enable transport level session
mangment-->
    <parameter name="manageTransportSession"
locked="false">false</parameter>

<!-- If you have a frontend host which exposes this webservice using a
different public URL  -->
    <!-- use this parameter to override autodetected url -->
    <!--<parameter name="httpFrontendHostUrl"
locked="false">https://someotherhost/context</parameter>-->


    <!--    The way of adding listener to the system-->
    <!--    <listener class="org.apache.axis2.ObserverIMPL">-->
    <!--        <parameter name="RSS_URL"
locked="false">http://127.0.0.1/rss</parameter>-->
    <!--    </listener>-->

    <!-- ================================================= -->
    <!-- Message Receivers -->
    <!-- ================================================= -->
<!--This is the Deafult Message Receiver for the system , if you want to
have MessageReceivers for -->
<!--all the other MEP implement it and add the correct entry to here ,
so that you can refer from-->
    <!--any operation -->
<!--Note : You can ovride this for particular service by adding the same
element with your requirement-->
    <messageReceivers>
        <messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-only";

class="org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver"/>
        <messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-out";

class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>
    </messageReceivers>
    <!-- ================================================= -->
    <!-- Transport Ins -->
    <!-- ================================================= -->
    <transportReceiver name="http"

class="org.apache.axis2.transport.http.SimpleHTTPServer">
        <parameter name="port" locked="false">6060</parameter>
        <parameter name="CONNECTION_TIMEOUT" locked="false">0</parameter>
        <parameter name="SO_TIMEOUT" locked="false">0</parameter>
    <!-- Here is the complete list of supported parameters (see example
settings further below):
        port: the port to listen on (default 6060)
        hostname:  if non-null, url prefix used in reply-to endpoint
references                                 (default null)
        originServer:  value of http Server header in outgoing messages
                                    (default "Simple-Server/1.1")
requestTimeout: value in millis of time that requests can wait for
data                                (default 20000)
        requestTcpNoDelay:  true to maximize performance and minimize
latency                                   (default true)
                            false to minimize bandwidth consumption by
combining segments
requestCoreThreadPoolSize: number of threads available for request
processing (unless queue fills up)  (default 25)
requestMaxThreadPoolSize: number of threads available for request
processing if queue fills us         (default 150)
note that default queue never fills up:
see HttpFactory
        threadKeepAliveTime:  time to keep threads in excess of core size
alive while inactive                  (default 180)
                              note that no such threads can exist with
default unbounded request queue
threadKeepAliveTimeUnit: TimeUnit of value in threadKeepAliveTime
(default SECONDS)                    (default SECONDS)
    -->
        <!-- <parameter name="hostname"
locked="false">http://www.myApp.com/ws</parameter> -->
        <!-- <parameter name="originServer"
locked="false">My-Server/1.1</parameter>           -->
        <!-- <parameter name="requestTimeout"
locked="false">10000</parameter>                   -->
        <!-- <parameter name="requestTcpNoDelay"
locked="false">false</parameter>                   -->
        <!-- <parameter name="requestCoreThreadPoolSize"
locked="false">50</parameter>                      -->
        <!-- <parameter name="RequestMaxThreadPoolSize"
locked="false">100</parameter>                     -->
        <!-- <parameter name="threadKeepAliveTime"
locked="false">240000</parameter>                  -->
        <!-- <parameter name="threadKeepAliveTimeUnit"
locked="false">MILLISECONDS</parameter>            -->
    </transportReceiver>

    <!--Uncomment if you want to have SMTP transport support-->
    <!--<transportReceiver name="mail"
class="org.apache.axis2.transport.mail.SimpleMailListener">-->
    <!--<parameter name="transport.mail.pop3.host"
locked="false">127.0.0.1</parameter>-->
    <!--<parameter name="transport.mail.pop3.user"
locked="false">axis2</parameter>-->
    <!--<parameter name="transport.mail.pop3.password"
locked="false">axis2</parameter>-->
    <!--<parameter name="transport.mail.pop3.port"
locked="false">110</parameter>-->
    <!--<parameter name="transport.mail.replyToAddress"
locked="false">[EMAIL PROTECTED]</parameter>-->
    <!--</transportReceiver>-->

    <transportReceiver name="tcp"
                       class="org.apache.axis2.transport.tcp.TCPServer">
        <parameter name="port" locked="false">6060</parameter>
<!--If you want to give your own host address for EPR generation-->
        <!--uncommet following paramter , and set as you required.-->
        <!--<parameter name="hostname"
locked="false">tcp://myApp.com/ws</parameter>-->
    </transportReceiver>

    <!--Uncomment this if you want JMS transport support-->
    <!--<transportReceiver name="jms"
class="org.apache.axis2.transport.jms.SimpleJMSListener">-->
    <!--<parameter name="transport.jms.Destination"
locked="false">dynamicQueues/FOO</parameter>-->
    <!--<parameter name="java.naming.factory.initial" locked="false">-->
    <!--org.activemq.jndi.ActiveMQInitialContextFactory</parameter>-->
    <!--<parameter name="java.naming.provider.url"
locked="false">tcp://localhost:61616</parameter>-->
    <!--</transportReceiver>-->

    <!-- ================================================= -->
    <!-- Transport Outs -->
    <!-- ================================================= -->

    <transportSender name="tcp"

class="org.apache.axis2.transport.tcp.TCPTransportSender"/>
    <transportSender name="local"

class="org.apache.axis2.transport.local.LocalTransportSender"/>
    <transportSender name="jms"
                     class="org.apache.axis2.transport.jms.JMSSender"/>
    <transportSender name="http"

class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
        <parameter name="PROTOCOL" locked="false">HTTP/1.1</parameter>
        <parameter name="Transfer-Encoding"
locked="false">chunked</parameter>
    </transportSender>
    <transportSender name="https"

class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
        <parameter name="PROTOCOL" locked="false">HTTP/1.1</parameter>
        <parameter name="Transfer-Encoding"
locked="false">chunked</parameter>
    </transportSender>

    <!-- Uncomment this one with the appropriate papameters to enable the
SMTP transport Receiver
   <transportSender name="mailto"
class="org.apache.axis2.transport.mail.MailTransportSender">
       <parameter name="transport.mail.smtp.host"
locked="false">127.0.0.1</parameter>
       <parameter name="transport.mail.smtp.user"
locked="false">axis2</parameter>
       <parameter name="transport.mail.smtp.password"
locked="false">axis2</parameter>
       <parameter name="transport.mail.smtp.port"
locked="false">25</parameter>
   </transportSender>
   -->

    <!-- ================================================= -->
    <!-- Global Modules  -->
    <!-- ================================================= -->
    <!-- Comment this to disable Addressing -->
    <module ref="addressing"/>
    <module ref="rampart"/>
    <module ref="soapmonitor"/>


<!--Configuring module , providing parameters for modules whether they
refer or not-->
    <!--<moduleConfig name="addressing">-->
<!--<parameter name="addressingPara" locked="false">N/A</parameter>-->
    <!--</moduleConfig>-->

    <!-- ================================================= -->
    <!-- Phases  -->
    <!-- ================================================= -->

    <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"/>
        <phase name="soapmonitorPhase"/>
    </phaseOrder>
    <phaseOrder type="outflow">
        <!--      user can add his own phases to this area  -->
        <phase name="OperationOutPhase"/>
        <phase name="soapmonitorPhase"/>
        <!--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"/>
        <phase name="soapmonitorPhase"/>
    </phaseOrder>
    <phaseOrder type="Outfaultflow">
        <!--      user can add his own phases to this area  -->

        <phase name="OperationOutFaultPhase"/>
        <phase name="soapmonitorPhase"/>
        <phase name="PolicyDetermination"/>
        <phase name="MessageOut"/>
    </phaseOrder>
</axisconfig>

Thank you,
Sathita


>From: "robert lazarski" <[EMAIL PROTECTED]>
>Reply-To: [email protected]
>To: [email protected]
>Subject: Re: [Axis2 v1.0] soapmonitor, how to use
>Date: Wed, 5 Jul 2006 09:21:56 -0300
>
>You need to have the following in the four phases, inflow, outflow,
>INfaultflow, Outfaultflow :
>
><phase name="soapmonitorPhase"/>
>
>Ordering is important, it should be the last entry in the phase.
>Reference the docs to see the example.
>
>Also, make sure you have the  <module ref="soapmonitor"/> either in
>the axis2.xml file next to the addressing ref, or alternatively, in
>your services.xml .
>
>HTH,
>Robert
>http://www.braziloutsource.com/
>
>On 7/5/06, Wan Kaveevivitchai <[EMAIL PROTECTED]> wrote:
>>
>>thank you, i have been follow all of them, before sending the first
>>message.
>>But i don't quite understand where should i make change in axis2.xml?
>>
>>Best regards,
>>Sathita
>>
>> >From: [EMAIL PROTECTED]
>> >Reply-To: [email protected]
>> >To: [email protected]
>> >Subject: Re: [Axis2 v1.0] soapmonitor, how to use
>> >Date: Wed, 05 Jul 2006 13:54:04 +0200
>> >
>> >Hi,
>> >have a look at this:
>>http://ws.apache.org/axis2/1_0/soapmonitor-module.html
>> >
>> >HTH Bille
>> >
>> > > -----Urspr�ngliche Nachricht-----
>> > > Von: [email protected]
>> > > Gesendet: 05.07.06 13:21:15
>> > > An: [email protected]
>> > > Betreff: [Axis2 v1.0] soapmonitor, how to use
>> >
>> >
>> > > Dear All,
>> > >
>> > > I did deploy soapmonitor module, and i now can see the Applet
>>but
>> > > it's actually cannot catch any soap passed. i think it's probably
>>need
>> >to
>> > > validate or do some proper deployment. I went to administration page
>>of
>> > > axis2 try to engage module globally, and it gave me this:
>> > >
>> > > Invalid phases please recheck axis2.xml soapmonitorPhase for the
>>handler
>> > > InFlowSOAPMonitorHandler
>> > >
>> > > what should i do? and how i suppose to configure axis2.xml?
>> > > there is nothing clear in the documentation.
>> > >
>> > > Thank you, really appreciate
>> > >
>> > > Sathita
>> > >
>> > >
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > > For additional commands, e-mail: [EMAIL PROTECTED]
>> > >
>> >
>> >
>> >______________________________________________________________
>> >Verschicken Sie romantische, coole und witzige Bilder per SMS!
>> >Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
>> >
>> >
>> >---------------------------------------------------------------------
>> >To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to