You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Antonio Manuel Muñiz Martín <am...@gmail.com> on 2007/10/09 13:22:53 UTC
SOAPMonitor Problem
Ok. Thanks.
I extract the soapmonitor.jar file in root directory (/axis2) and I
configured the axis2.xml and web.xml in axis2 distribution.
When I put the URL localhost:8080/axis2/SOAPMonitor in the browser the
response is "The requested resource is not available".
I forgot anything?
Thanks a lot for your effort.
Regards,
Antonio.
>axis2-soapmonitor.jar got renamed to soapmonitor.jar during the conversion
to maven2 for the 1.3 release. Thanks for pointing that out, I'll update the
docs.
>
>HTH,
>Robert
>
>On 10/9/07, Antonio Manuel Muñiz Martín <am...@gmv.com> wrote:
>
>
>
> Hi.
>
> Where is axis2-soapmonitor.jar? This file appears in the doc but I do
> not find it.
> The command javac -classpath axis2-soapmonitor.jar
> SOAPMonitorApplet-java uses it.
>
> Regards.
>
>
>
> ________________________________
> Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede
> contener información clasificada por su emisor como confidencial en el
> marco de su Sistema de Gestión de Seguridad de la Información siendo
> para uso exclusivo del destinatario, quedando prohibida su divulgación
> copia o distribución a terceros sin la autorización expresa del
> remitente. Si Vd. ha recibido este mensaje erróneamente, se ruega lo
> notifique al remitente y proceda a su borrado. Gracias por su
colaboración.
> ________________________________
> This message including any attachments may contain confidential
> information, according to our Information Security Management System,
> and intended solely for a specific individual to whom they are
> addressed. Any unauthorised copy, disclosure or distribution of this
> message is strictly forbidden. If you have received this transmission
> in error, please notify the sender immediately and delete it.
> ________________________________
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: SOAPMonitor Problem
Posted by Todd Allen <tb...@copart.com>.
This can also be done in the services.xml file (instead of axis2.xml).
robert lazarski wrote:
> In your axis2.xml , you need to have:
>
> <module ref="addressing"/>
> <module ref="soapmonitor"/>
>
> As the docs say, don't copy and paste the phases. In fact, you
> shouldn't need to change those at all.
>
> HTH,
> Robert
>
> On 10/9/07, Antonio Manuel Muñiz Martín <am...@gmail.com> wrote:
>
>> I do all steps in documentation. I don´t modify phaseOrder content, because
>> the phase soapmonitorPhase already exists.
>> Perhaps I don´t understand the phase filosofy.
>>
>> In my axis2.xml I have:
>>
>> ...
>> <module ref="soapmonitor"/>
>> ...
>> <phaseOrder type="InFlow">
>> <!-- System predefined phases -->
>> <phase name="Transport">
>> <handler name="RequestURIBasedDispatcher"
>>
>> class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher">
>> <order phase="Transport"/>
>> </handler>
>> <handler name="SOAPActionBasedDispatcher"
>>
>> class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher">
>> <order phase="Transport"/>
>> </handler>
>> </phase>
>> <phase name="Addressing">
>> <handler name="AddressingBasedDispatcher"
>>
>> class="org.apache.axis2.dispatchers.AddressingBasedDispatcher">
>> <order phase="Addressing"/>
>> </handler>
>> </phase>
>> <phase name="Security"/>
>> <phase name="PreDispatch"/>
>> <phase name="Dispatch"
>> class="org.apache.axis2.engine.DispatchPhase">
>> <handler name="RequestURIBasedDispatcher"
>>
>> class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher
>> "/>
>> <handler name="SOAPActionBasedDispatcher"
>>
>> class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>
>> <handler name="RequestURIOperationDispatcher"
>>
>> class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>
>> <handler name="SOAPMessageBodyBasedDispatcher"
>>
>> class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher
>> "/>
>>
>> <handler name="HTTPLocationBasedDispatcher"
>>
>> class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/>
>> </phase>
>> <phase name="RMPhase"/>
>> <!-- System predefined phases -->
>> <!-- After Postdispatch phase module author 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="soapmonitorPhase"/>
>> <phase name="OperationOutPhase"/>
>> <!--system predefined phase-->
>> <!--these phase will run irrespective of the service-->
>> <phase name="RMPhase"/>
>> <phase name="PolicyDetermination"/>
>> <phase name="MessageOut"/>
>> <phase name="Security"/>
>> </phaseOrder>
>> <phaseOrder type="InFaultFlow">
>> <phase name="Addressing">
>> <handler name="AddressingBasedDispatcher"
>> class="
>> org.apache.axis2.dispatchers.AddressingBasedDispatcher">
>> <order phase="Addressing"/>
>> </handler>
>> </phase>
>> <phase name="Security"/>
>> <phase name="PreDispatch"/>
>> <phase name="Dispatch"
>> class="org.apache.axis2.engine.DispatchPhase">
>> <handler name="RequestURIBasedDispatcher"
>>
>> class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>
>> <handler name="SOAPActionBasedDispatcher"
>>
>> class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher
>> "/>
>> <handler name="RequestURIOperationDispatcher"
>>
>> class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>
>> <handler name="SOAPMessageBodyBasedDispatcher"
>>
>> class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/>
>>
>> <handler name="HTTPLocationBasedDispatcher"
>>
>> class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher
>> "/>
>> </phase>
>> <phase name="RMPhase"/>
>> <!-- 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="soapmonitorPhase"/>
>> <phase name="OperationOutFaultPhase"/>
>> <phase name="RMPhase"/>
>> <phase name="PolicyDetermination"/>
>> <phase name="MessageOut"/>
>> </phaseOrder>
>>
>> 2007/10/9, robert lazarski <ro...@gmail.com>:
>>
>>> On 10/9/07, Fátima Milla Olaya <fa...@evidian.com> wrote:
>>>
>>>> robert lazarski a écrit :
>>>>
>>>>> Did you edit the web.xml ? Please read the docs carefully - the
>>>>> required info is all there.
>>>>>
>>>>> HTH,
>>>>> Robert
>>>>>
>>>>>
>>>> FaultFlow">
>>>> <phase name="Addressing">
>>>> <handler name="AddressingBasedDispatcher"
>>>>
>>>>
>>>>
>> class="org.apache.axis2.dispatchers.AddressingBasedDispatcher">
>>
>>>> <order phase="Addressing"/>
>>>> </handler>
>>>> </phase>
>>>> <phase name="Security"/>
>>>> <phase name="PreDispatch"/>
>>>> <phase name="Dispatch"
>>>> class="org.apache.axis2.engine.DispatchPhase ">
>>>> <handler name="RequestURIBasedDispatcher"
>>>>
>>>>
>>>>
>> class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>
>>
>>>> <handler name="SOAPActionBasedDispatcher"
>>>>
>>>>
>>>>
>> class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>
>>
>>>> <handler
>>>>
>> name="RequestURIOperationDispatcher"
>>
>>>>
>> class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher
>> "/>
>>
>>>> <handler
>>>>
>> name="SOAPMessageBodyBasedDispatcher"
>>
>>>>
>> class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/>
>>
>>>> <handler name="HTTPLocationBasedDispatcher"
>>>>
>>>>
>>>>
>> class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/>
>>
>>>> </phase>
>>>> <phase name="RMPhase"/>
>>>> <!-- user can add his own phases to this area -->
>>>> <phase name="userphase1"/>
>>>> <phase name="OperationInFaultPhase"/>
>>>> <phase name="soapmonitorPhase"/>
>>>> </phaseOrder>
>>>> <phaseOrder type="OutFaultFlow">
>>>> <!-- user can add his own phases to this area -->
>>>> <phase name="userphase1"/>
>>>> <phase name="soapmonitorPhase"/>
>>>> <phase name="OperationOutFaultPhase"/>
>>>> <phase name="RMPhase"/>
>>>> <phase name="PolicyDetermination"/>
>>>> <phase name="MessageOut"/>
>>>> </phaseOrder>
>>>> </axisconfig>
>>>>
>>>>
>>> Where in the axis2.xml are you engaging the module ?
>>>
>>> HTH,
>>> Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: SOAPMonitor Problem
Posted by Antonio Manuel Muñiz Martín <am...@gmail.com>.
Problem solved.
SOAPMonitor not runs on Glassfish.
I have do the same on Tomcat and it runs.
Thaks for all.
2007/10/9, Antonio Manuel Muñiz Martín <am...@gmail.com>:
>
> Mmm, I´m using axis distribution deployed on Glassfish server. ¿Is this a
> problem?
> I think that axis is independent of the servlet container.
>
> 2007/10/9, robert lazarski < robertlazarski@gmail.com>:
> >
> > Ehh, looks like you are already engaging the module.
> >
> > "The requested resource is not available".
> >
> > Where do you see that, in the browser? I think that's a tomcat error.
> > So you've edited web.xml, engaged the module, you have expanded the
> > soapmonitor.jar to webapps/axis2 and there is a module under
> > WEB-INF/modules ? Hmm, this does work in 1.3 because I use it.
> >
> > Try looking in the tomcat logs for some clues - you might be getting
> > an error somewhere. Also verify you are in fact binding to port 5001
> > and some other program has stolen the port - you should get lots of
> > error messages in the logs if that happens.
> >
> > If all else fails, put axis2 in debug mode via the log4j.properties.
> >
> > HTH,
> > Robert
> >
> > On 10/9/07, robert lazarski <ro...@gmail.com> wrote:
> > > In your axis2.xml , you need to have:
> > >
> > > <module ref="addressing"/>
> > > <module ref="soapmonitor"/>
> > >
> > > As the docs say, don't copy and paste the phases. In fact, you
> > > shouldn't need to change those at all.
> > >
> > > HTH,
> > > Robert
> > >
> > > On 10/9/07, Antonio Manuel Muñiz Martín <am...@gmail.com>
> > wrote:
> > > > I do all steps in documentation. I don´t modify phaseOrder content,
> > because
> > > > the phase soapmonitorPhase already exists.
> > > > Perhaps I don´t understand the phase filosofy.
> > > >
> > > > In my axis2.xml I have:
> > > >
> > > > ...
> > > > <module ref="soapmonitor"/>
> > > > ...
> > > > <phaseOrder type="InFlow">
> > > > <!-- System predefined phases -->
> > > > <phase name="Transport">
> > > > <handler name="RequestURIBasedDispatcher"
> > > >
> > > > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher">
> > > > <order phase="Transport"/>
> > > > </handler>
> > > > <handler name="SOAPActionBasedDispatcher"
> > > >
> > > > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher">
> > > > <order phase="Transport"/>
> > > > </handler>
> > > > </phase>
> > > > <phase name="Addressing">
> > > > <handler name="AddressingBasedDispatcher"
> > > >
> > > > class="org.apache.axis2.dispatchers.AddressingBasedDispatcher">
> > > > <order phase="Addressing"/>
> > > > </handler>
> > > > </phase>
> > > > <phase name="Security"/>
> > > > <phase name="PreDispatch"/>
> > > > <phase name="Dispatch"
> > > > class=" org.apache.axis2.engine.DispatchPhase">
> > > > <handler name="RequestURIBasedDispatcher"
> > > >
> > > > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher
> > > > "/>
> > > > <handler name="SOAPActionBasedDispatcher"
> > > >
> > > > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>
> > > > <handler name="RequestURIOperationDispatcher"
> > > >
> > > > class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>
> > > > <handler name="SOAPMessageBodyBasedDispatcher"
> > > >
> > > > class=" org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher
> > > > "/>
> > > >
> > > > <handler name="HTTPLocationBasedDispatcher"
> > > >
> > > > class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher "/>
> > > > </phase>
> > > > <phase name="RMPhase"/>
> > > > <!-- System predefined phases -->
> > > > <!-- After Postdispatch phase module author 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="soapmonitorPhase"/>
> > > > <phase name="OperationOutPhase"/>
> > > > <!--system predefined phase-->
> > > > <!--these phase will run irrespective of the service-->
> > > > <phase name="RMPhase"/>
> > > > <phase name="PolicyDetermination"/>
> > > > <phase name="MessageOut"/>
> > > > <phase name="Security"/>
> > > > </phaseOrder>
> > > > <phaseOrder type="InFaultFlow">
> > > > <phase name="Addressing">
> > > > <handler name="AddressingBasedDispatcher"
> > > > class="
> > > > org.apache.axis2.dispatchers.AddressingBasedDispatcher ">
> > > > <order phase="Addressing"/>
> > > > </handler>
> > > > </phase>
> > > > <phase name="Security"/>
> > > > <phase name="PreDispatch"/>
> > > > <phase name="Dispatch"
> > > > class="org.apache.axis2.engine.DispatchPhase">
> > > > <handler name="RequestURIBasedDispatcher"
> > > >
> > > > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>
> > > > <handler name="SOAPActionBasedDispatcher"
> > > >
> > > > class=" org.apache.axis2.dispatchers.SOAPActionBasedDispatcher
> > > > "/>
> > > > <handler name="RequestURIOperationDispatcher"
> > > >
> > > > class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>
> > > > <handler name="SOAPMessageBodyBasedDispatcher"
> > > >
> > > > class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher
> > "/>
> > > >
> > > > <handler name="HTTPLocationBasedDispatcher"
> > > >
> > > > class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher
> > > > "/>
> > > > </phase>
> > > > <phase name="RMPhase"/>
> > > > <!-- 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="soapmonitorPhase"/>
> > > > <phase name="OperationOutFaultPhase"/>
> > > > <phase name="RMPhase"/>
> > > > <phase name="PolicyDetermination"/>
> > > > <phase name="MessageOut"/>
> > > > </phaseOrder>
> > > >
> > > > 2007/10/9, robert lazarski <robertlazarski@gmail.com >:
> > > > > On 10/9/07, Fátima Milla Olaya <fa...@evidian.com>
> > wrote:
> > > > > > robert lazarski a écrit :
> > > > > > > Did you edit the web.xml ? Please read the docs carefully -
> > the
> > > > > > > required info is all there.
> > > > > > >
> > > > > > > HTH,
> > > > > > > Robert
> > > > > > >
> > > > > > FaultFlow">
> > > > > > <phase name="Addressing">
> > > > > > <handler name="AddressingBasedDispatcher"
> > > > > >
> > > > > >
> > > > class="org.apache.axis2.dispatchers.AddressingBasedDispatcher">
> > > > > > <order phase="Addressing"/>
> > > > > > </handler>
> > > > > > </phase>
> > > > > > <phase name="Security"/>
> > > > > > <phase name="PreDispatch"/>
> > > > > > <phase name="Dispatch"
> > > > > > class="org.apache.axis2.engine.DispatchPhase ">
> > > > > > <handler name="RequestURIBasedDispatcher"
> > > > > >
> > > > > >
> > > > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>
> > > > > > <handler name="SOAPActionBasedDispatcher"
> > > > > >
> > > > > >
> > > > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>
> > > > > > <handler
> > > > name="RequestURIOperationDispatcher"
> > > > > >
> > > > > >
> > > > class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher
> > > > "/>
> > > > > > <handler
> > > > name="SOAPMessageBodyBasedDispatcher"
> > > > > >
> > > > > >
> > > > class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher
> > "/>
> > > > > >
> > > > > > <handler name="HTTPLocationBasedDispatcher"
> > > > > >
> > > > > >
> > > > class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/>
> > > > > > </phase>
> > > > > > <phase name="RMPhase"/>
> > > > > > <!-- user can add his own phases to this area -->
> > > > > > <phase name="userphase1"/>
> > > > > > <phase name="OperationInFaultPhase"/>
> > > > > > <phase name="soapmonitorPhase"/>
> > > > > > </phaseOrder>
> > > > > > <phaseOrder type="OutFaultFlow">
> > > > > > <!-- user can add his own phases to this area -->
> > > > > > <phase name="userphase1"/>
> > > > > > <phase name="soapmonitorPhase"/>
> > > > > > <phase name="OperationOutFaultPhase"/>
> > > > > > <phase name="RMPhase"/>
> > > > > > <phase name="PolicyDetermination"/>
> > > > > > <phase name="MessageOut"/>
> > > > > > </phaseOrder>
> > > > > > </axisconfig>
> > > > > >
> > > > >
> > > > > Where in the axis2.xml are you engaging the module ?
> > > > >
> > > > > HTH,
> > > > > Robert
> > > > >
> > > > >
> > > >
> > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail:
> > > > axis-user-unsubscribe@ws.apache.org
> > > > > For additional commands, e-mail: axis-user-help@ws.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
>
Re: SOAPMonitor Problem
Posted by Antonio Manuel Muñiz Martín <am...@gmail.com>.
Mmm, I´m using axis distribution deployed on Glassfish server. ¿Is this a
problem?
I think that axis is independent of the servlet container.
2007/10/9, robert lazarski <ro...@gmail.com>:
>
> Ehh, looks like you are already engaging the module.
>
> "The requested resource is not available".
>
> Where do you see that, in the browser? I think that's a tomcat error.
> So you've edited web.xml, engaged the module, you have expanded the
> soapmonitor.jar to webapps/axis2 and there is a module under
> WEB-INF/modules ? Hmm, this does work in 1.3 because I use it.
>
> Try looking in the tomcat logs for some clues - you might be getting
> an error somewhere. Also verify you are in fact binding to port 5001
> and some other program has stolen the port - you should get lots of
> error messages in the logs if that happens.
>
> If all else fails, put axis2 in debug mode via the log4j.properties.
>
> HTH,
> Robert
>
> On 10/9/07, robert lazarski <ro...@gmail.com> wrote:
> > In your axis2.xml , you need to have:
> >
> > <module ref="addressing"/>
> > <module ref="soapmonitor"/>
> >
> > As the docs say, don't copy and paste the phases. In fact, you
> > shouldn't need to change those at all.
> >
> > HTH,
> > Robert
> >
> > On 10/9/07, Antonio Manuel Muñiz Martín <am...@gmail.com>
> wrote:
> > > I do all steps in documentation. I don´t modify phaseOrder content,
> because
> > > the phase soapmonitorPhase already exists.
> > > Perhaps I don´t understand the phase filosofy.
> > >
> > > In my axis2.xml I have:
> > >
> > > ...
> > > <module ref="soapmonitor"/>
> > > ...
> > > <phaseOrder type="InFlow">
> > > <!-- System predefined phases -->
> > > <phase name="Transport">
> > > <handler name="RequestURIBasedDispatcher"
> > >
> > > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher">
> > > <order phase="Transport"/>
> > > </handler>
> > > <handler name="SOAPActionBasedDispatcher"
> > >
> > > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher">
> > > <order phase="Transport"/>
> > > </handler>
> > > </phase>
> > > <phase name="Addressing">
> > > <handler name="AddressingBasedDispatcher"
> > >
> > > class="org.apache.axis2.dispatchers.AddressingBasedDispatcher">
> > > <order phase="Addressing"/>
> > > </handler>
> > > </phase>
> > > <phase name="Security"/>
> > > <phase name="PreDispatch"/>
> > > <phase name="Dispatch"
> > > class="org.apache.axis2.engine.DispatchPhase">
> > > <handler name="RequestURIBasedDispatcher"
> > >
> > > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher
> > > "/>
> > > <handler name="SOAPActionBasedDispatcher"
> > >
> > > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>
> > > <handler name="RequestURIOperationDispatcher"
> > >
> > > class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>
> > > <handler name="SOAPMessageBodyBasedDispatcher"
> > >
> > > class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher
> > > "/>
> > >
> > > <handler name="HTTPLocationBasedDispatcher"
> > >
> > > class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/>
> > > </phase>
> > > <phase name="RMPhase"/>
> > > <!-- System predefined phases -->
> > > <!-- After Postdispatch phase module author 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="soapmonitorPhase"/>
> > > <phase name="OperationOutPhase"/>
> > > <!--system predefined phase-->
> > > <!--these phase will run irrespective of the service-->
> > > <phase name="RMPhase"/>
> > > <phase name="PolicyDetermination"/>
> > > <phase name="MessageOut"/>
> > > <phase name="Security"/>
> > > </phaseOrder>
> > > <phaseOrder type="InFaultFlow">
> > > <phase name="Addressing">
> > > <handler name="AddressingBasedDispatcher"
> > > class="
> > > org.apache.axis2.dispatchers.AddressingBasedDispatcher">
> > > <order phase="Addressing"/>
> > > </handler>
> > > </phase>
> > > <phase name="Security"/>
> > > <phase name="PreDispatch"/>
> > > <phase name="Dispatch"
> > > class="org.apache.axis2.engine.DispatchPhase">
> > > <handler name="RequestURIBasedDispatcher"
> > >
> > > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>
> > > <handler name="SOAPActionBasedDispatcher"
> > >
> > > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher
> > > "/>
> > > <handler name="RequestURIOperationDispatcher"
> > >
> > > class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>
> > > <handler name="SOAPMessageBodyBasedDispatcher"
> > >
> > > class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/>
> > >
> > > <handler name="HTTPLocationBasedDispatcher"
> > >
> > > class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher
> > > "/>
> > > </phase>
> > > <phase name="RMPhase"/>
> > > <!-- 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="soapmonitorPhase"/>
> > > <phase name="OperationOutFaultPhase"/>
> > > <phase name="RMPhase"/>
> > > <phase name="PolicyDetermination"/>
> > > <phase name="MessageOut"/>
> > > </phaseOrder>
> > >
> > > 2007/10/9, robert lazarski <ro...@gmail.com>:
> > > > On 10/9/07, Fátima Milla Olaya <fa...@evidian.com>
> wrote:
> > > > > robert lazarski a écrit :
> > > > > > Did you edit the web.xml ? Please read the docs carefully - the
> > > > > > required info is all there.
> > > > > >
> > > > > > HTH,
> > > > > > Robert
> > > > > >
> > > > > FaultFlow">
> > > > > <phase name="Addressing">
> > > > > <handler name="AddressingBasedDispatcher"
> > > > >
> > > > >
> > > class="org.apache.axis2.dispatchers.AddressingBasedDispatcher">
> > > > > <order phase="Addressing"/>
> > > > > </handler>
> > > > > </phase>
> > > > > <phase name="Security"/>
> > > > > <phase name="PreDispatch"/>
> > > > > <phase name="Dispatch"
> > > > > class="org.apache.axis2.engine.DispatchPhase ">
> > > > > <handler name="RequestURIBasedDispatcher"
> > > > >
> > > > >
> > > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>
> > > > > <handler name="SOAPActionBasedDispatcher"
> > > > >
> > > > >
> > > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>
> > > > > <handler
> > > name="RequestURIOperationDispatcher"
> > > > >
> > > > >
> > > class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher
> > > "/>
> > > > > <handler
> > > name="SOAPMessageBodyBasedDispatcher"
> > > > >
> > > > >
> > > class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/>
> > > > >
> > > > > <handler name="HTTPLocationBasedDispatcher"
> > > > >
> > > > >
> > > class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/>
> > > > > </phase>
> > > > > <phase name="RMPhase"/>
> > > > > <!-- user can add his own phases to this area -->
> > > > > <phase name="userphase1"/>
> > > > > <phase name="OperationInFaultPhase"/>
> > > > > <phase name="soapmonitorPhase"/>
> > > > > </phaseOrder>
> > > > > <phaseOrder type="OutFaultFlow">
> > > > > <!-- user can add his own phases to this area -->
> > > > > <phase name="userphase1"/>
> > > > > <phase name="soapmonitorPhase"/>
> > > > > <phase name="OperationOutFaultPhase"/>
> > > > > <phase name="RMPhase"/>
> > > > > <phase name="PolicyDetermination"/>
> > > > > <phase name="MessageOut"/>
> > > > > </phaseOrder>
> > > > > </axisconfig>
> > > > >
> > > >
> > > > Where in the axis2.xml are you engaging the module ?
> > > >
> > > > HTH,
> > > > Robert
> > > >
> > > >
> > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail:
> > > axis-user-unsubscribe@ws.apache.org
> > > > For additional commands, e-mail: axis-user-help@ws.apache.org
> > > >
> > > >
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
Re: SOAPMonitor Problem
Posted by robert lazarski <ro...@gmail.com>.
Ehh, looks like you are already engaging the module.
"The requested resource is not available".
Where do you see that, in the browser? I think that's a tomcat error.
So you've edited web.xml, engaged the module, you have expanded the
soapmonitor.jar to webapps/axis2 and there is a module under
WEB-INF/modules ? Hmm, this does work in 1.3 because I use it.
Try looking in the tomcat logs for some clues - you might be getting
an error somewhere. Also verify you are in fact binding to port 5001
and some other program has stolen the port - you should get lots of
error messages in the logs if that happens.
If all else fails, put axis2 in debug mode via the log4j.properties.
HTH,
Robert
On 10/9/07, robert lazarski <ro...@gmail.com> wrote:
> In your axis2.xml , you need to have:
>
> <module ref="addressing"/>
> <module ref="soapmonitor"/>
>
> As the docs say, don't copy and paste the phases. In fact, you
> shouldn't need to change those at all.
>
> HTH,
> Robert
>
> On 10/9/07, Antonio Manuel Muñiz Martín <am...@gmail.com> wrote:
> > I do all steps in documentation. I don´t modify phaseOrder content, because
> > the phase soapmonitorPhase already exists.
> > Perhaps I don´t understand the phase filosofy.
> >
> > In my axis2.xml I have:
> >
> > ...
> > <module ref="soapmonitor"/>
> > ...
> > <phaseOrder type="InFlow">
> > <!-- System predefined phases -->
> > <phase name="Transport">
> > <handler name="RequestURIBasedDispatcher"
> >
> > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher">
> > <order phase="Transport"/>
> > </handler>
> > <handler name="SOAPActionBasedDispatcher"
> >
> > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher">
> > <order phase="Transport"/>
> > </handler>
> > </phase>
> > <phase name="Addressing">
> > <handler name="AddressingBasedDispatcher"
> >
> > class="org.apache.axis2.dispatchers.AddressingBasedDispatcher">
> > <order phase="Addressing"/>
> > </handler>
> > </phase>
> > <phase name="Security"/>
> > <phase name="PreDispatch"/>
> > <phase name="Dispatch"
> > class="org.apache.axis2.engine.DispatchPhase">
> > <handler name="RequestURIBasedDispatcher"
> >
> > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher
> > "/>
> > <handler name="SOAPActionBasedDispatcher"
> >
> > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>
> > <handler name="RequestURIOperationDispatcher"
> >
> > class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>
> > <handler name="SOAPMessageBodyBasedDispatcher"
> >
> > class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher
> > "/>
> >
> > <handler name="HTTPLocationBasedDispatcher"
> >
> > class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/>
> > </phase>
> > <phase name="RMPhase"/>
> > <!-- System predefined phases -->
> > <!-- After Postdispatch phase module author 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="soapmonitorPhase"/>
> > <phase name="OperationOutPhase"/>
> > <!--system predefined phase-->
> > <!--these phase will run irrespective of the service-->
> > <phase name="RMPhase"/>
> > <phase name="PolicyDetermination"/>
> > <phase name="MessageOut"/>
> > <phase name="Security"/>
> > </phaseOrder>
> > <phaseOrder type="InFaultFlow">
> > <phase name="Addressing">
> > <handler name="AddressingBasedDispatcher"
> > class="
> > org.apache.axis2.dispatchers.AddressingBasedDispatcher">
> > <order phase="Addressing"/>
> > </handler>
> > </phase>
> > <phase name="Security"/>
> > <phase name="PreDispatch"/>
> > <phase name="Dispatch"
> > class="org.apache.axis2.engine.DispatchPhase">
> > <handler name="RequestURIBasedDispatcher"
> >
> > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>
> > <handler name="SOAPActionBasedDispatcher"
> >
> > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher
> > "/>
> > <handler name="RequestURIOperationDispatcher"
> >
> > class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>
> > <handler name="SOAPMessageBodyBasedDispatcher"
> >
> > class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/>
> >
> > <handler name="HTTPLocationBasedDispatcher"
> >
> > class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher
> > "/>
> > </phase>
> > <phase name="RMPhase"/>
> > <!-- 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="soapmonitorPhase"/>
> > <phase name="OperationOutFaultPhase"/>
> > <phase name="RMPhase"/>
> > <phase name="PolicyDetermination"/>
> > <phase name="MessageOut"/>
> > </phaseOrder>
> >
> > 2007/10/9, robert lazarski <ro...@gmail.com>:
> > > On 10/9/07, Fátima Milla Olaya <fa...@evidian.com> wrote:
> > > > robert lazarski a écrit :
> > > > > Did you edit the web.xml ? Please read the docs carefully - the
> > > > > required info is all there.
> > > > >
> > > > > HTH,
> > > > > Robert
> > > > >
> > > > FaultFlow">
> > > > <phase name="Addressing">
> > > > <handler name="AddressingBasedDispatcher"
> > > >
> > > >
> > class="org.apache.axis2.dispatchers.AddressingBasedDispatcher">
> > > > <order phase="Addressing"/>
> > > > </handler>
> > > > </phase>
> > > > <phase name="Security"/>
> > > > <phase name="PreDispatch"/>
> > > > <phase name="Dispatch"
> > > > class="org.apache.axis2.engine.DispatchPhase ">
> > > > <handler name="RequestURIBasedDispatcher"
> > > >
> > > >
> > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>
> > > > <handler name="SOAPActionBasedDispatcher"
> > > >
> > > >
> > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>
> > > > <handler
> > name="RequestURIOperationDispatcher"
> > > >
> > > >
> > class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher
> > "/>
> > > > <handler
> > name="SOAPMessageBodyBasedDispatcher"
> > > >
> > > >
> > class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/>
> > > >
> > > > <handler name="HTTPLocationBasedDispatcher"
> > > >
> > > >
> > class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/>
> > > > </phase>
> > > > <phase name="RMPhase"/>
> > > > <!-- user can add his own phases to this area -->
> > > > <phase name="userphase1"/>
> > > > <phase name="OperationInFaultPhase"/>
> > > > <phase name="soapmonitorPhase"/>
> > > > </phaseOrder>
> > > > <phaseOrder type="OutFaultFlow">
> > > > <!-- user can add his own phases to this area -->
> > > > <phase name="userphase1"/>
> > > > <phase name="soapmonitorPhase"/>
> > > > <phase name="OperationOutFaultPhase"/>
> > > > <phase name="RMPhase"/>
> > > > <phase name="PolicyDetermination"/>
> > > > <phase name="MessageOut"/>
> > > > </phaseOrder>
> > > > </axisconfig>
> > > >
> > >
> > > Where in the axis2.xml are you engaging the module ?
> > >
> > > HTH,
> > > Robert
> > >
> > >
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > axis-user-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-user-help@ws.apache.org
> > >
> > >
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: SOAPMonitor Problem
Posted by robert lazarski <ro...@gmail.com>.
In your axis2.xml , you need to have:
<module ref="addressing"/>
<module ref="soapmonitor"/>
As the docs say, don't copy and paste the phases. In fact, you
shouldn't need to change those at all.
HTH,
Robert
On 10/9/07, Antonio Manuel Muñiz Martín <am...@gmail.com> wrote:
> I do all steps in documentation. I don´t modify phaseOrder content, because
> the phase soapmonitorPhase already exists.
> Perhaps I don´t understand the phase filosofy.
>
> In my axis2.xml I have:
>
> ...
> <module ref="soapmonitor"/>
> ...
> <phaseOrder type="InFlow">
> <!-- System predefined phases -->
> <phase name="Transport">
> <handler name="RequestURIBasedDispatcher"
>
> class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher">
> <order phase="Transport"/>
> </handler>
> <handler name="SOAPActionBasedDispatcher"
>
> class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher">
> <order phase="Transport"/>
> </handler>
> </phase>
> <phase name="Addressing">
> <handler name="AddressingBasedDispatcher"
>
> class="org.apache.axis2.dispatchers.AddressingBasedDispatcher">
> <order phase="Addressing"/>
> </handler>
> </phase>
> <phase name="Security"/>
> <phase name="PreDispatch"/>
> <phase name="Dispatch"
> class="org.apache.axis2.engine.DispatchPhase">
> <handler name="RequestURIBasedDispatcher"
>
> class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher
> "/>
> <handler name="SOAPActionBasedDispatcher"
>
> class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>
> <handler name="RequestURIOperationDispatcher"
>
> class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>
> <handler name="SOAPMessageBodyBasedDispatcher"
>
> class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher
> "/>
>
> <handler name="HTTPLocationBasedDispatcher"
>
> class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/>
> </phase>
> <phase name="RMPhase"/>
> <!-- System predefined phases -->
> <!-- After Postdispatch phase module author 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="soapmonitorPhase"/>
> <phase name="OperationOutPhase"/>
> <!--system predefined phase-->
> <!--these phase will run irrespective of the service-->
> <phase name="RMPhase"/>
> <phase name="PolicyDetermination"/>
> <phase name="MessageOut"/>
> <phase name="Security"/>
> </phaseOrder>
> <phaseOrder type="InFaultFlow">
> <phase name="Addressing">
> <handler name="AddressingBasedDispatcher"
> class="
> org.apache.axis2.dispatchers.AddressingBasedDispatcher">
> <order phase="Addressing"/>
> </handler>
> </phase>
> <phase name="Security"/>
> <phase name="PreDispatch"/>
> <phase name="Dispatch"
> class="org.apache.axis2.engine.DispatchPhase">
> <handler name="RequestURIBasedDispatcher"
>
> class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>
> <handler name="SOAPActionBasedDispatcher"
>
> class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher
> "/>
> <handler name="RequestURIOperationDispatcher"
>
> class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>
> <handler name="SOAPMessageBodyBasedDispatcher"
>
> class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/>
>
> <handler name="HTTPLocationBasedDispatcher"
>
> class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher
> "/>
> </phase>
> <phase name="RMPhase"/>
> <!-- 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="soapmonitorPhase"/>
> <phase name="OperationOutFaultPhase"/>
> <phase name="RMPhase"/>
> <phase name="PolicyDetermination"/>
> <phase name="MessageOut"/>
> </phaseOrder>
>
> 2007/10/9, robert lazarski <ro...@gmail.com>:
> > On 10/9/07, Fátima Milla Olaya <fa...@evidian.com> wrote:
> > > robert lazarski a écrit :
> > > > Did you edit the web.xml ? Please read the docs carefully - the
> > > > required info is all there.
> > > >
> > > > HTH,
> > > > Robert
> > > >
> > > FaultFlow">
> > > <phase name="Addressing">
> > > <handler name="AddressingBasedDispatcher"
> > >
> > >
> class="org.apache.axis2.dispatchers.AddressingBasedDispatcher">
> > > <order phase="Addressing"/>
> > > </handler>
> > > </phase>
> > > <phase name="Security"/>
> > > <phase name="PreDispatch"/>
> > > <phase name="Dispatch"
> > > class="org.apache.axis2.engine.DispatchPhase ">
> > > <handler name="RequestURIBasedDispatcher"
> > >
> > >
> class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>
> > > <handler name="SOAPActionBasedDispatcher"
> > >
> > >
> class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>
> > > <handler
> name="RequestURIOperationDispatcher"
> > >
> > >
> class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher
> "/>
> > > <handler
> name="SOAPMessageBodyBasedDispatcher"
> > >
> > >
> class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/>
> > >
> > > <handler name="HTTPLocationBasedDispatcher"
> > >
> > >
> class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/>
> > > </phase>
> > > <phase name="RMPhase"/>
> > > <!-- user can add his own phases to this area -->
> > > <phase name="userphase1"/>
> > > <phase name="OperationInFaultPhase"/>
> > > <phase name="soapmonitorPhase"/>
> > > </phaseOrder>
> > > <phaseOrder type="OutFaultFlow">
> > > <!-- user can add his own phases to this area -->
> > > <phase name="userphase1"/>
> > > <phase name="soapmonitorPhase"/>
> > > <phase name="OperationOutFaultPhase"/>
> > > <phase name="RMPhase"/>
> > > <phase name="PolicyDetermination"/>
> > > <phase name="MessageOut"/>
> > > </phaseOrder>
> > > </axisconfig>
> > >
> >
> > Where in the axis2.xml are you engaging the module ?
> >
> > HTH,
> > Robert
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: SOAPMonitor Problem
Posted by Antonio Manuel Muñiz Martín <am...@gmail.com>.
I do all steps in documentation. I don´t modify phaseOrder content, because
the phase soapmonitorPhase already exists.
Perhaps I don´t understand the phase filosofy.
In my axis2.xml I have:
...
<module ref="soapmonitor"/>
...
<phaseOrder type="InFlow">
<!-- System predefined phases -->
<phase name="Transport">
<handler name="RequestURIBasedDispatcher"
class="
org.apache.axis2.dispatchers.RequestURIBasedDispatcher">
<order phase="Transport"/>
</handler>
<handler name="SOAPActionBasedDispatcher"
class="
org.apache.axis2.dispatchers.SOAPActionBasedDispatcher">
<order phase="Transport"/>
</handler>
</phase>
<phase name="Addressing">
<handler name="AddressingBasedDispatcher"
class="
org.apache.axis2.dispatchers.AddressingBasedDispatcher">
<order phase="Addressing"/>
</handler>
</phase>
<phase name="Security"/>
<phase name="PreDispatch"/>
<phase name="Dispatch" class="org.apache.axis2.engine.DispatchPhase
">
<handler name="RequestURIBasedDispatcher"
class="
org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>
<handler name="SOAPActionBasedDispatcher"
class="
org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>
<handler name="RequestURIOperationDispatcher"
class="
org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>
<handler name="SOAPMessageBodyBasedDispatcher"
class="
org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/>
<handler name="HTTPLocationBasedDispatcher"
class="
org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/>
</phase>
<phase name="RMPhase"/>
<!-- System predefined phases -->
<!-- After Postdispatch phase module author 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="soapmonitorPhase"/>
<phase name="OperationOutPhase"/>
<!--system predefined phase-->
<!--these phase will run irrespective of the service-->
<phase name="RMPhase"/>
<phase name="PolicyDetermination"/>
<phase name="MessageOut"/>
<phase name="Security"/>
</phaseOrder>
<phaseOrder type="InFaultFlow">
<phase name="Addressing">
<handler name="AddressingBasedDispatcher"
class="
org.apache.axis2.dispatchers.AddressingBasedDispatcher">
<order phase="Addressing"/>
</handler>
</phase>
<phase name="Security"/>
<phase name="PreDispatch"/>
<phase name="Dispatch" class="org.apache.axis2.engine.DispatchPhase
">
<handler name="RequestURIBasedDispatcher"
class="
org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>
<handler name="SOAPActionBasedDispatcher"
class="
org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>
<handler name="RequestURIOperationDispatcher"
class="
org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>
<handler name="SOAPMessageBodyBasedDispatcher"
class="
org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/>
<handler name="HTTPLocationBasedDispatcher"
class="
org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/>
</phase>
<phase name="RMPhase"/>
<!-- 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="soapmonitorPhase"/>
<phase name="OperationOutFaultPhase"/>
<phase name="RMPhase"/>
<phase name="PolicyDetermination"/>
<phase name="MessageOut"/>
</phaseOrder>
2007/10/9, robert lazarski <ro...@gmail.com>:
>
> On 10/9/07, Fátima Milla Olaya <fa...@evidian.com> wrote:
> > robert lazarski a écrit :
> > > Did you edit the web.xml ? Please read the docs carefully - the
> > > required info is all there.
> > >
> > > HTH,
> > > Robert
> > >
> > FaultFlow">
> > <phase name="Addressing">
> > <handler name="AddressingBasedDispatcher"
> >
> > class="org.apache.axis2.dispatchers.AddressingBasedDispatcher">
> > <order phase="Addressing"/>
> > </handler>
> > </phase>
> > <phase name="Security"/>
> > <phase name="PreDispatch"/>
> > <phase name="Dispatch"
> > class="org.apache.axis2.engine.DispatchPhase">
> > <handler name="RequestURIBasedDispatcher"
> >
> > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>
> > <handler name="SOAPActionBasedDispatcher"
> >
> > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>
> > <handler name="RequestURIOperationDispatcher"
> >
> > class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>
> > <handler name="SOAPMessageBodyBasedDispatcher"
> >
> > class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/>
> >
> > <handler name="HTTPLocationBasedDispatcher"
> >
> > class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/>
> > </phase>
> > <phase name="RMPhase"/>
> > <!-- user can add his own phases to this area -->
> > <phase name="userphase1"/>
> > <phase name="OperationInFaultPhase"/>
> > <phase name="soapmonitorPhase"/>
> > </phaseOrder>
> > <phaseOrder type="OutFaultFlow">
> > <!-- user can add his own phases to this area -->
> > <phase name="userphase1"/>
> > <phase name="soapmonitorPhase"/>
> > <phase name="OperationOutFaultPhase"/>
> > <phase name="RMPhase"/>
> > <phase name="PolicyDetermination"/>
> > <phase name="MessageOut"/>
> > </phaseOrder>
> > </axisconfig>
> >
>
> Where in the axis2.xml are you engaging the module ?
>
> HTH,
> Robert
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
Re: SOAPMonitor Problem
Posted by robert lazarski <ro...@gmail.com>.
On 10/9/07, Fátima Milla Olaya <fa...@evidian.com> wrote:
> robert lazarski a écrit :
> > Did you edit the web.xml ? Please read the docs carefully - the
> > required info is all there.
> >
> > HTH,
> > Robert
> >
> FaultFlow">
> <phase name="Addressing">
> <handler name="AddressingBasedDispatcher"
>
> class="org.apache.axis2.dispatchers.AddressingBasedDispatcher">
> <order phase="Addressing"/>
> </handler>
> </phase>
> <phase name="Security"/>
> <phase name="PreDispatch"/>
> <phase name="Dispatch"
> class="org.apache.axis2.engine.DispatchPhase">
> <handler name="RequestURIBasedDispatcher"
>
> class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>
> <handler name="SOAPActionBasedDispatcher"
>
> class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>
> <handler name="RequestURIOperationDispatcher"
>
> class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>
> <handler name="SOAPMessageBodyBasedDispatcher"
>
> class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/>
>
> <handler name="HTTPLocationBasedDispatcher"
>
> class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/>
> </phase>
> <phase name="RMPhase"/>
> <!-- user can add his own phases to this area -->
> <phase name="userphase1"/>
> <phase name="OperationInFaultPhase"/>
> <phase name="soapmonitorPhase"/>
> </phaseOrder>
> <phaseOrder type="OutFaultFlow">
> <!-- user can add his own phases to this area -->
> <phase name="userphase1"/>
> <phase name="soapmonitorPhase"/>
> <phase name="OperationOutFaultPhase"/>
> <phase name="RMPhase"/>
> <phase name="PolicyDetermination"/>
> <phase name="MessageOut"/>
> </phaseOrder>
> </axisconfig>
>
Where in the axis2.xml are you engaging the module ?
HTH,
Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: SOAPMonitor Problem
Posted by Fátima Milla Olaya <fa...@evidian.com>.
robert lazarski a écrit :
> Did you edit the web.xml ? Please read the docs carefully - the
> required info is all there.
>
> HTH,
> Robert
>
> On 10/9/07, Antonio Manuel Muñiz Martín <am...@gmail.com> wrote:
>
>> This is exactly what I do. And the response is "The requested resource is
>> not available" when I try /axis2/SOAPMonitor
>> Another idea?
>> Thanks.
>>
>>
>> 2007/10/9, Fátima Milla Olaya < fatima.milla-olaya@evidian.com>:
>>
>>> Unzip the applet classes and place them at the root of the war - for
>>> example axis2/SOAPMonitorApplet*.class
>>>
>>> Suerte!
>>>
>>> Antonio Manuel Muñiz Martín a écrit :
>>>
>>>> Ok. Thanks.
>>>>
>>>> I extract the soapmonitor.jar file in root directory (/axis2) and I
>>>> configured the axis2.xml and web.xml in axis2 distribution.
>>>> When I put the URL localhost:8080/axis2/SOAPMonitor in
>>>>
>> the browser the
>>
>>>> response is "The requested resource is not available".
>>>> I forgot anything?
>>>>
>>>> Thanks a lot for your effort.
>>>> Regards,
>>>> Antonio.
>>>>
>>>>
>>>>> axis2-soapmonitor.jar got renamed to soapmonitor.jar during the
>>>>>
>>>> conversion to maven2 for the 1.3 release. Thanks for pointing that
>>>> out, I'll update the docs.
>>>>
>>>>> HTH,
>>>>> Robert
>>>>>
>>>>> On 10/9/07, Antonio Manuel Muñiz Martín < ammuniz@gmv.com
>>>>>
>>>> <ma...@gmv.com>> wrote:
>>>>
>>>>>
>>>>> Hi.
>>>>>
>>>>> Where is axis2-soapmonitor.jar ? This file appears in the doc but I
>>>>>
>> do
>>
>>>>> not find it.
>>>>> The command javac -classpath axis2-soapmonitor.jar
>>>>> SOAPMonitorApplet-java uses it.
>>>>>
>>>>> Regards.
>>>>>
>>>>>
>>>>>
>>>>> ________________________________
>>>>> Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede
>>>>> contener información clasificada por su emisor como confidencial en el
>>>>> marco de su Sistema de Gestión de Seguridad de la Información siendo
>>>>> para uso exclusivo del destinatario, quedando prohibida su divulgación
>>>>> copia o distribución a terceros sin la autorización expresa del
>>>>> remitente. Si Vd. ha recibido este mensaje erróneamente, se ruega lo
>>>>> notifique al remitente y proceda a su borrado. Gracias por su
>>>>>
>>>> colaboración.
>>>>
>>>>> ________________________________
>>>>> This message including any attachments may contain confidential
>>>>> information, according to our Information Security Management System,
>>>>> and intended solely for a specific individual to whom they are
>>>>> addressed. Any unauthorised copy, disclosure or distribution of this
>>>>> message is strictly forbidden. If you have received this transmission
>>>>> in error, please notify the sender immediately and delete it.
>>>>> ________________________________
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>> ---------------------------------------------------------------------
>>
>>>> To unsubscribe, e-mail:
>>>>
>> axis-user-unsubscribe@ws.apache.org
>>
>>>> <ma...@ws.apache.org>
>>>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>>> <ma...@ws.apache.org>
>>>>
>>>
>>>
>> ---------------------------------------------------------------------
>>
>>> To unsubscribe, e-mail:
>>>
>> axis-user-unsubscribe@ws.apache.org
>>
>>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>>
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
These are the two files that I have written. Take a look or copy them. Bye
*Web.xml*
<?xml version="1.0" encoding="ISO-8859-1"?>
<!--
~ Licensed to the Apache Software Foundation (ASF) under one
~ or more contributor license agreements. See the NOTICE file
~ distributed with this work for additional information
~ regarding copyright ownership. The ASF licenses this file
~ to you under the Apache License, Version 2.0 (the
~ "License"); you may not use this file except in compliance
~ with the License. You may obtain a copy of the License at
~
~ http://www.apache.org/licenses/LICENSE-2.0
~
~ Unless required by applicable law or agreed to in writing,
~ software distributed under the License is distributed on an
~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
~ KIND, either express or implied. See the License for the
~ specific language governing permissions and limitations
~ under the License.
-->
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application
2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
<display-name>Apache-Axis2</display-name>
<servlet>
<servlet-name>AxisServlet</servlet-name>
<display-name>Apache-Axis Servlet</display-name>
<servlet-class>org.apache.axis2.transport.http.AxisServlet</servlet-class>
<!--<init-param>-->
<!--<param-name>axis2.xml.path</param-name>-->
<!--<param-value>/WEB-INF/conf/axis2.xml</param-value>-->
<!--<param-name>axis2.xml.url</param-name>-->
<!--<param-value>http://localhot/myrepo/axis2.xml</param-value>-->
<!--<param-name>axis2.repository.path</param-name>-->
<!--<param-value>/WEB-INF</param-value>-->
<!--<param-name>axis2.repository.url</param-name>-->
<!--<param-value>http://localhot/myrepo</param-value>-->
<!--</init-param>-->
<load-on-startup>1</load-on-startup>
</servlet>
<servlet>
<servlet-name>AxisAdminServlet</servlet-name>
<display-name>Apache-Axis AxisAdmin Servlet (Web
Admin)</display-name>
<servlet-class>
org.apache.axis2.transport.http.AxisAdminServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>SOAPMonitorService</servlet-name>
<display-name>SOAPMonitorService</display-name>
<servlet-class>
org.apache.axis2.soapmonitor.servlet.SOAPMonitorService
</servlet-class>
<init-param>
<param-name>SOAPMonitorPort</param-name>
<param-value>5001</param-value>
</init-param>
<load-on-startup>100</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>SOAPMonitorService</servlet-name>
<url-pattern>/SOAPMonitor</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>AxisServlet</servlet-name>
<url-pattern>/servlet/AxisServlet</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>AxisServlet</servlet-name>
<url-pattern>*.jws</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>AxisServlet</servlet-name>
<url-pattern>/services/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>AxisAdminServlet</servlet-name>
<url-pattern>/axis2-admin/*</url-pattern>
</servlet-mapping>
<mime-mapping>
<extension>inc</extension>
<mime-type>text/plain</mime-type>
</mime-mapping>
<welcome-file-list>
<welcome-file>index.jsp</welcome-file>
<welcome-file>index.html</welcome-file>
<welcome-file>/axis2-web/index.jsp</welcome-file>
</welcome-file-list>
<error-page>
<error-code>404</error-code>
<location>/axis2-web/Error/error404.jsp</location>
</error-page>
<error-page>
<error-code>500</error-code>
<location>/axis2-web/Error/error500.jsp</location>
</error-page>
</web-app>
*Axis2.xml*
FaultFlow">
<phase name="Addressing">
<handler name="AddressingBasedDispatcher"
class="org.apache.axis2.dispatchers.AddressingBasedDispatcher">
<order phase="Addressing"/>
</handler>
</phase>
<phase name="Security"/>
<phase name="PreDispatch"/>
<phase name="Dispatch"
class="org.apache.axis2.engine.DispatchPhase">
<handler name="RequestURIBasedDispatcher"
class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>
<handler name="SOAPActionBasedDispatcher"
class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>
<handler name="RequestURIOperationDispatcher"
class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>
<handler name="SOAPMessageBodyBasedDispatcher"
class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/>
<handler name="HTTPLocationBasedDispatcher"
class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/>
</phase>
<phase name="RMPhase"/>
<!-- user can add his own phases to this area -->
<phase name="userphase1"/>
<phase name="OperationInFaultPhase"/>
<phase name="soapmonitorPhase"/>
</phaseOrder>
<phaseOrder type="OutFaultFlow">
<!-- user can add his own phases to this area -->
<phase name="userphase1"/>
<phase name="soapmonitorPhase"/>
<phase name="OperationOutFaultPhase"/>
<phase name="RMPhase"/>
<phase name="PolicyDetermination"/>
<phase name="MessageOut"/>
</phaseOrder>
</axisconfig>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: SOAPMonitor Problem
Posted by robert lazarski <ro...@gmail.com>.
Did you edit the web.xml ? Please read the docs carefully - the
required info is all there.
HTH,
Robert
On 10/9/07, Antonio Manuel Muñiz Martín <am...@gmail.com> wrote:
> This is exactly what I do. And the response is "The requested resource is
> not available" when I try /axis2/SOAPMonitor
> Another idea?
> Thanks.
>
>
> 2007/10/9, Fátima Milla Olaya < fatima.milla-olaya@evidian.com>:
> >Unzip the applet classes and place them at the root of the war - for
> >example axis2/SOAPMonitorApplet*.class
> >
> >Suerte!
> >
> > Antonio Manuel Muñiz Martín a écrit :
> > > Ok. Thanks.
> > >
> > > I extract the soapmonitor.jar file in root directory (/axis2) and I
> > > configured the axis2.xml and web.xml in axis2 distribution.
> > > When I put the URL localhost:8080/axis2/SOAPMonitor in
> the browser the
> > > response is "The requested resource is not available".
> > > I forgot anything?
> > >
> > > Thanks a lot for your effort.
> > > Regards,
> > > Antonio.
> > >
> > > >axis2-soapmonitor.jar got renamed to soapmonitor.jar during the
> > > conversion to maven2 for the 1.3 release. Thanks for pointing that
> > > out, I'll update the docs.
> > > >
> > > >HTH,
> > > >Robert
> > > >
> > > >On 10/9/07, Antonio Manuel Muñiz Martín < ammuniz@gmv.com
> > > <ma...@gmv.com>> wrote:
> > > >
> > > >
> > > >
> > > > Hi.
> > > >
> > > > Where is axis2-soapmonitor.jar ? This file appears in the doc but I
> do
> > > > not find it.
> > > > The command javac -classpath axis2-soapmonitor.jar
> > > > SOAPMonitorApplet-java uses it.
> > > >
> > > > Regards.
> > > >
> > > >
> > > >
> > > > ________________________________
> > > > Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede
> > > > contener información clasificada por su emisor como confidencial en el
> > > > marco de su Sistema de Gestión de Seguridad de la Información siendo
> > > > para uso exclusivo del destinatario, quedando prohibida su divulgación
> > > > copia o distribución a terceros sin la autorización expresa del
> > > > remitente. Si Vd. ha recibido este mensaje erróneamente, se ruega lo
> > > > notifique al remitente y proceda a su borrado. Gracias por su
> > > colaboración.
> > > > ________________________________
> > > > This message including any attachments may contain confidential
> > > > information, according to our Information Security Management System,
> > > > and intended solely for a specific individual to whom they are
> > > > addressed. Any unauthorised copy, disclosure or distribution of this
> > > > message is strictly forbidden. If you have received this transmission
> > > > in error, please notify the sender immediately and delete it.
> > > > ________________________________
> > > >
> > > >
> > > >
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> axis-user-unsubscribe@ws.apache.org
> > > <ma...@ws.apache.org>
> > > For additional commands, e-mail: axis-user-help@ws.apache.org
> > > <ma...@ws.apache.org>
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: SOAPMonitor Problem
Posted by Antonio Manuel Muñiz Martín <am...@gmail.com>.
This is exactly what I do. And the response is "The requested resource is
not available" when I try /axis2/SOAPMonitor
Another idea?
Thanks.
2007/10/9, Fátima Milla Olaya <fa...@evidian.com>:
>Unzip the applet classes and place them at the root of the war - for
>example axis2/SOAPMonitorApplet*.class
>
>Suerte!
> Antonio Manuel Muñiz Martín a écrit :
> > Ok. Thanks.
> >
> > I extract the soapmonitor.jar file in root directory (/axis2) and I
> > configured the axis2.xml and web.xml in axis2 distribution.
> > When I put the URL localhost:8080/axis2/SOAPMonitor in the browser the
> > response is "The requested resource is not available".
> > I forgot anything?
> >
> > Thanks a lot for your effort.
> > Regards,
> > Antonio.
> >
> > >axis2-soapmonitor.jar got renamed to soapmonitor.jar during the
> > conversion to maven2 for the 1.3 release. Thanks for pointing that
> > out, I'll update the docs.
> > >
> > >HTH,
> > >Robert
> > >
> > >On 10/9/07, Antonio Manuel Muñiz Martín <ammuniz@gmv.com
> > <ma...@gmv.com>> wrote:
> > >
> > >
> > >
> > > Hi.
> > >
> > > Where is axis2-soapmonitor.jar ? This file appears in the doc but I
> do
> > > not find it.
> > > The command javac -classpath axis2-soapmonitor.jar
> > > SOAPMonitorApplet-java uses it.
> > >
> > > Regards.
> > >
> > >
> > >
> > > ________________________________
> > > Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede
> > > contener información clasificada por su emisor como confidencial en el
> > > marco de su Sistema de Gestión de Seguridad de la Información siendo
> > > para uso exclusivo del destinatario, quedando prohibida su divulgación
> > > copia o distribución a terceros sin la autorización expresa del
> > > remitente. Si Vd. ha recibido este mensaje erróneamente, se ruega lo
> > > notifique al remitente y proceda a su borrado. Gracias por su
> > colaboración.
> > > ________________________________
> > > This message including any attachments may contain confidential
> > > information, according to our Information Security Management System,
> > > and intended solely for a specific individual to whom they are
> > > addressed. Any unauthorised copy, disclosure or distribution of this
> > > message is strictly forbidden. If you have received this transmission
> > > in error, please notify the sender immediately and delete it.
> > > ________________________________
> > >
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > <ma...@ws.apache.org>
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> > <ma...@ws.apache.org>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
Re: SOAPMonitor Problem
Posted by Fátima Milla Olaya <fa...@evidian.com>.
Antonio Manuel Muñiz Martín a écrit :
> Ok. Thanks.
>
> I extract the soapmonitor.jar file in root directory (/axis2) and I
> configured the axis2.xml and web.xml in axis2 distribution.
> When I put the URL localhost:8080/axis2/SOAPMonitor in the browser the
> response is "The requested resource is not available".
> I forgot anything?
>
> Thanks a lot for your effort.
> Regards,
> Antonio.
>
> >axis2-soapmonitor.jar got renamed to soapmonitor.jar during the
> conversion to maven2 for the 1.3 release. Thanks for pointing that
> out, I'll update the docs.
> >
> >HTH,
> >Robert
> >
> >On 10/9/07, Antonio Manuel Muñiz Martín <ammuniz@gmv.com
> <ma...@gmv.com>> wrote:
> >
> >
> >
> > Hi.
> >
> > Where is axis2-soapmonitor.jar ? This file appears in the doc but I do
> > not find it.
> > The command javac -classpath axis2-soapmonitor.jar
> > SOAPMonitorApplet-java uses it.
> >
> > Regards.
> >
> >
> >
> > ________________________________
> > Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede
> > contener información clasificada por su emisor como confidencial en el
> > marco de su Sistema de Gestión de Seguridad de la Información siendo
> > para uso exclusivo del destinatario, quedando prohibida su divulgación
> > copia o distribución a terceros sin la autorización expresa del
> > remitente. Si Vd. ha recibido este mensaje erróneamente, se ruega lo
> > notifique al remitente y proceda a su borrado. Gracias por su
> colaboración.
> > ________________________________
> > This message including any attachments may contain confidential
> > information, according to our Information Security Management System,
> > and intended solely for a specific individual to whom they are
> > addressed. Any unauthorised copy, disclosure or distribution of this
> > message is strictly forbidden. If you have received this transmission
> > in error, please notify the sender immediately and delete it.
> > ________________________________
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-user-help@ws.apache.org
> <ma...@ws.apache.org>
Unzip the applet classes and place them at the root of the war - for
example axis2/SOAPMonitorApplet*.class
Suerte!
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org