Michele, can you post your entire stacktrace please? I can't match the
error you get with current svn. The error you are getting indicates no
soapmonitorPhase in inflow, yet your axis2.xml does have it.  So
sorry, no clear indication of the problem yet.  You could try putting
axis2 in debug to see the phases loaded, which may flush out the error
by confirming the phase isn't loaded.

Alternatively, try out tcpmon ;-) .

Good luck,
Robert

On Jan 4, 2008 10:11 AM, Michele Mazzucco <[EMAIL PROTECTED]> wrote:
> Robert,
>
> if the module is globally engaged I get the error I mentioned in my
> previous email. The same happens also if I "dynamically" engage the
> module.
>
> Michele
>
>
> On 4 Jan 2008, at 12:01, robert lazarski wrote:
>
> > You need to engage the module. Search for:
> >
> > <module ref="addressing"/>
> >
> > Then in the same place, add:
> >
> > <module ref="soapmonitor"/>
> >
> > HTH,
> > Robert
> >
> > On Jan 4, 2008 8:44 AM, Michele Mazzucco
> > <[EMAIL PROTECTED]> wrote:
> >> Robert,
> >>
> >> in axis2 1.3 all the phases needed by the soap monitor module are
> >> already included.
> >>
> >>
> >>
> >>
> >> Michele
> >>
> >> On 4 Jan 2008, at 11:07, robert lazarski wrote:
> >>
> >>> The exception is pretty self descriptive... show us the entire
> >>> axis2.xml and maybe we can help.
> >>>
> >>> Robert
> >>>
> >>> On Jan 4, 2008 7:39 AM, Michele Mazzucco
> >>> <[EMAIL PROTECTED]> wrote:
> >>>> Hi all,
> >>>>
> >>>> I can't enage the soapmonitor module under Axis2 1.3 because of the
> >>>> following error
> >>>>   org.apache.axis2.phaseresolver.PhaseException: Did not find the
> >>>> desired phase 'soapmonitorPhase' while deploying handler
> >>>> 'InFlowSOAPMonitorHandler'.
> >>>>
> >>>> My axis2.xml differs from the default one only because of the NIO
> >>>> transport listener.
> >>>>
> >>>>
> >>>> Any idea?
> >>>>
> >>>> Thanks,
> >>>> Michele
> >>>>
> >>>>
> >>>> -------------------------------------------------------------------
> >>>> --
> >>>> 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]
>
>

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

Reply via email to