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 Michele Mazzucco <Mi...@ncl.ac.uk> on 2008/01/04 10:39:41 UTC
[Axis2] Unable to engage the soap monitor module (axis2 1.3)
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: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
Posted by Nandana Mihindukulasooriya <na...@gmail.com>.
Hi,
> I'm not completely clear on your setup but it seems to me you are
> creating a ConfigurationContext yourself or are not loading the same
> axis2.xml as you showed me
If you create a ConfigurationContext without specifying an axis2.xml,
axis2_default.xml [1] will be used and this will cause problems as the
user defined phases are not present there. Anyway Axis2 is going to
have dynamic phase support very soon, so these kind of problems will
not occur as the modules them selves will be able to define the phases
which they require to register their handlers.
[1] - http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/axis2_default.xml?view=markup
thanks,
Nandana
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
On 4 Jan 2008, at 16:00, robert lazarski wrote:
> I'm not completely clear on your setup but it seems to me you are
> creating a ConfigurationContext yourself or are not loading the same
> axis2.xml as you showed me - which is why putting axis2 in debug would
> help as it would confirm the soapmonitorPhase is being loaded in
> inflow.
The two configuration files (embedded and inside tomcat) are the
indeed the same.
>
> Anywhich way though, what you are lacking is getting the
> soapmonitorPhase configured in inflow - be it via axis2.xml,
> ConfigurationContext etc. Are you able to engage and run the other
> modules like logging and ping ok in your embedded setup?
Not the logging (it throws an exception saying it's not valid), but I
can successfully deploy a module of mine.
> Can you load
> the phases programtically in your embedded setup?
Yes.
> See the unit tests
> in the src tree for how to do phase loading programtically - sorry for
> being a bit vague here but looking at the source is the quickest way
> to tackle advance cases like this.
>
> HTH,
> Robert
Michele
>
> On Jan 4, 2008 12:39 PM, Michele Mazzucco
> <Mi...@ncl.ac.uk> wrote:
>> Robert,
>>
>> I get that error if I run an embedded version of axis2. If I deploy
>> it to tomcat (clean setup) it works fine.
>>
>> Jan 4, 2008 3:36:45 PM org.apache.coyote.http11.Http11Protocol init
>> INFO: Initializing Coyote HTTP/1.1 on http-8080
>> Jan 4, 2008 3:36:45 PM org.apache.catalina.startup.Catalina load
>> INFO: Initialization processed in 1011 ms
>> Jan 4, 2008 3:36:46 PM org.apache.catalina.core.StandardService start
>> INFO: Starting service Catalina
>> Jan 4, 2008 3:36:46 PM org.apache.catalina.core.StandardEngine start
>> INFO: Starting Servlet Engine: Apache Tomcat/6.0.14
>> Jan 4, 2008 3:36:46 PM org.apache.catalina.startup.HostConfig
>> deployWAR
>> INFO: Deploying web application archive axis2.war
>> [INFO] Deploying module: addressing-1.3
>> [INFO] Deploying module: metadataExchange-1.3
>> [INFO] Deploying module: ping-1.3
>> [INFO] Deploying module: script-1.3
>> [INFO] Deploying module: soapmonitor-1.3
>> [INFO] script module activated
>> [INFO] HTTP Sender starting
>> [INFO] Deploying Web service: version.aar
>> Jan 4, 2008 3:36:50 PM org.apache.coyote.http11.Http11Protocol start
>> INFO: Starting Coyote HTTP/1.1 on http-8080
>> Jan 4, 2008 3:36:50 PM org.apache.jk.common.ChannelSocket init
>> INFO: JK: ajp13 listening on /0.0.0.0:8009
>> Jan 4, 2008 3:36:50 PM org.apache.jk.server.JkMain start
>> INFO: Jk running ID=0 time=0/52 config=null
>> Jan 4, 2008 3:36:50 PM org.apache.catalina.startup.Catalina start
>> INFO: Server startup in 5161 ms
>>
>>
>> Any idea?
>> Michele
>>
>>
>> On 4 Jan 2008, at 14:50, robert lazarski wrote:
>>
>>> 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
>>> <Mi...@ncl.ac.uk> 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
>>>>> <Mi...@ncl.ac.uk> 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
>>>>>>> <Mi...@ncl.ac.uk> 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: 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
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> -----------------------------------------------------------------
>>>>>> --
>>>>>> --
>>>>>> 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
>>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> 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
>>>
>>
>>
>> ---------------------------------------------------------------------
>> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
Posted by robert lazarski <ro...@gmail.com>.
I'm not completely clear on your setup but it seems to me you are
creating a ConfigurationContext yourself or are not loading the same
axis2.xml as you showed me - which is why putting axis2 in debug would
help as it would confirm the soapmonitorPhase is being loaded in
inflow.
Anywhich way though, what you are lacking is getting the
soapmonitorPhase configured in inflow - be it via axis2.xml,
ConfigurationContext etc. Are you able to engage and run the other
modules like logging and ping ok in your embedded setup? Can you load
the phases programtically in your embedded setup? See the unit tests
in the src tree for how to do phase loading programtically - sorry for
being a bit vague here but looking at the source is the quickest way
to tackle advance cases like this.
HTH,
Robert
On Jan 4, 2008 12:39 PM, Michele Mazzucco <Mi...@ncl.ac.uk> wrote:
> Robert,
>
> I get that error if I run an embedded version of axis2. If I deploy
> it to tomcat (clean setup) it works fine.
>
> Jan 4, 2008 3:36:45 PM org.apache.coyote.http11.Http11Protocol init
> INFO: Initializing Coyote HTTP/1.1 on http-8080
> Jan 4, 2008 3:36:45 PM org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 1011 ms
> Jan 4, 2008 3:36:46 PM org.apache.catalina.core.StandardService start
> INFO: Starting service Catalina
> Jan 4, 2008 3:36:46 PM org.apache.catalina.core.StandardEngine start
> INFO: Starting Servlet Engine: Apache Tomcat/6.0.14
> Jan 4, 2008 3:36:46 PM org.apache.catalina.startup.HostConfig deployWAR
> INFO: Deploying web application archive axis2.war
> [INFO] Deploying module: addressing-1.3
> [INFO] Deploying module: metadataExchange-1.3
> [INFO] Deploying module: ping-1.3
> [INFO] Deploying module: script-1.3
> [INFO] Deploying module: soapmonitor-1.3
> [INFO] script module activated
> [INFO] HTTP Sender starting
> [INFO] Deploying Web service: version.aar
> Jan 4, 2008 3:36:50 PM org.apache.coyote.http11.Http11Protocol start
> INFO: Starting Coyote HTTP/1.1 on http-8080
> Jan 4, 2008 3:36:50 PM org.apache.jk.common.ChannelSocket init
> INFO: JK: ajp13 listening on /0.0.0.0:8009
> Jan 4, 2008 3:36:50 PM org.apache.jk.server.JkMain start
> INFO: Jk running ID=0 time=0/52 config=null
> Jan 4, 2008 3:36:50 PM org.apache.catalina.startup.Catalina start
> INFO: Server startup in 5161 ms
>
>
> Any idea?
> Michele
>
>
> On 4 Jan 2008, at 14:50, robert lazarski wrote:
>
> > 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
> > <Mi...@ncl.ac.uk> 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
> >>> <Mi...@ncl.ac.uk> 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
> >>>>> <Mi...@ncl.ac.uk> 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: 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
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> -------------------------------------------------------------------
> >>>> --
> >>>> 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
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> 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
> >
>
>
> ---------------------------------------------------------------------
> 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: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
Robert,
I get that error if I run an embedded version of axis2. If I deploy
it to tomcat (clean setup) it works fine.
Jan 4, 2008 3:36:45 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Jan 4, 2008 3:36:45 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1011 ms
Jan 4, 2008 3:36:46 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Jan 4, 2008 3:36:46 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.14
Jan 4, 2008 3:36:46 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive axis2.war
[INFO] Deploying module: addressing-1.3
[INFO] Deploying module: metadataExchange-1.3
[INFO] Deploying module: ping-1.3
[INFO] Deploying module: script-1.3
[INFO] Deploying module: soapmonitor-1.3
[INFO] script module activated
[INFO] HTTP Sender starting
[INFO] Deploying Web service: version.aar
Jan 4, 2008 3:36:50 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Jan 4, 2008 3:36:50 PM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
Jan 4, 2008 3:36:50 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/52 config=null
Jan 4, 2008 3:36:50 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 5161 ms
Any idea?
Michele
On 4 Jan 2008, at 14:50, robert lazarski wrote:
> 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
> <Mi...@ncl.ac.uk> 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
>>> <Mi...@ncl.ac.uk> 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
>>>>> <Mi...@ncl.ac.uk> 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: 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
>>>>>
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> 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
>>>
>>
>>
>> ---------------------------------------------------------------------
>> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
Posted by robert lazarski <ro...@gmail.com>.
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 <Mi...@ncl.ac.uk> 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
> > <Mi...@ncl.ac.uk> 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
> >>> <Mi...@ncl.ac.uk> 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: 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
> >>>
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> 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
> >
>
>
> ---------------------------------------------------------------------
> 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: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
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
> <Mi...@ncl.ac.uk> 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
>>> <Mi...@ncl.ac.uk> 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: 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
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
Posted by robert lazarski <ro...@gmail.com>.
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 <Mi...@ncl.ac.uk> 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
> > <Mi...@ncl.ac.uk> 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: 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
> >
>
>
>
> ---------------------------------------------------------------------
> 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: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
Robert,
in axis2 1.3 all the phases needed by the soap monitor module are
already included.
Re: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
Posted by robert lazarski <ro...@gmail.com>.
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 <Mi...@ncl.ac.uk> 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: 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: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
Posted by Nandana Mihindukulasooriya <na...@gmail.com>.
Hi Michele,
You have to add the soapmonitorPhase ( at the moment )
to the
axis2.xml to use soap monitor module. You can find the details here [1].
Thanks,
Nandana
[1] - http://ws.apache.org/axis2/1_3/soapmonitor-module.html
On Jan 4, 2008 3:09 PM, Michele Mazzucco <Mi...@ncl.ac.uk> 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: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>