You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Glen Daniels <gl...@thoughtcraft.com> on 2007/06/07 03:00:13 UTC
[axis2] Module-specified phases - one more comment
Hi all!
I'm just in the midst of trying out the Axis2 SOAPMonitor. Cool stuff.
If you would allow me to quote from our own SOAPMonitor documentation
(http://ws.apache.org/axis2/1_2/soapmonitor-module.html):
-- begin quote --
In the axis2.xml file, define your phase orders for the
'soapmonitorPhase' referenced in the module.xml of soapmonitor.mars.
Below is an example which should NOT be copied exactly, since the
default phases change occasionally. The important point here is that
'soapmonitorPhase' should be placed under the 'user can add his own
phases to this area' comment in the 'inflow', 'outflow', 'INfaultflow',
and 'Outfaultflow' sections.
-- end quote --
Consider what we're saying here. "Do not copy this config exactly,
because the default phases change". "Please place soapmonitorPhase
AFTER PostDispatch..." Oh - hm, I guess we mean RMPhase now. (should we
perhaps update the comment in axis2.xml?) Doesn't that seem like
something you could capture in software?
Now I'm not really going to spend any time on the fact that the first
quoted sentence is hard to understand, that "soapmonitor.mars" should be
"soapmonitor.mar", or that "soapmonitorPhase" should really be
capitalized in some way that makes sense (SoapMonitorPhase, maybe?), or
even that the phase the user is being asked to add has already been
present in the default axis2.xml since before 1.2.
I will however ask that you note that the user is being asked to add a
phase to FOUR separate places in a configuration file. So that they can
use an "easy to use" debugging tool. Now it's true that we've added the
soapmonitorPhase already and this documentation should change anyway,
but the point would be the same for any third party Module that might
need it's own phases that are NOT yet in our default config.
If Modules could simply express Phases and constraints for deploying
them, all this would boil down to <module ref="soapmonitor"/>. That is all.
Thanks,
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [axis2] Module-specified phases - one more comment
Posted by David Illsley <da...@gmail.com>.
You've persuaded me, but then I agreed with your position beforehand ;-)
David
On 07/06/07, Glen Daniels <gl...@thoughtcraft.com> wrote:
> Hi all!
>
> I'm just in the midst of trying out the Axis2 SOAPMonitor. Cool stuff.
> If you would allow me to quote from our own SOAPMonitor documentation
> (http://ws.apache.org/axis2/1_2/soapmonitor-module.html):
>
> -- begin quote --
> In the axis2.xml file, define your phase orders for the
> 'soapmonitorPhase' referenced in the module.xml of soapmonitor.mars.
> Below is an example which should NOT be copied exactly, since the
> default phases change occasionally. The important point here is that
> 'soapmonitorPhase' should be placed under the 'user can add his own
> phases to this area' comment in the 'inflow', 'outflow', 'INfaultflow',
> and 'Outfaultflow' sections.
> -- end quote --
>
> Consider what we're saying here. "Do not copy this config exactly,
> because the default phases change". "Please place soapmonitorPhase
> AFTER PostDispatch..." Oh - hm, I guess we mean RMPhase now. (should we
> perhaps update the comment in axis2.xml?) Doesn't that seem like
> something you could capture in software?
>
> Now I'm not really going to spend any time on the fact that the first
> quoted sentence is hard to understand, that "soapmonitor.mars" should be
> "soapmonitor.mar", or that "soapmonitorPhase" should really be
> capitalized in some way that makes sense (SoapMonitorPhase, maybe?), or
> even that the phase the user is being asked to add has already been
> present in the default axis2.xml since before 1.2.
>
> I will however ask that you note that the user is being asked to add a
> phase to FOUR separate places in a configuration file. So that they can
> use an "easy to use" debugging tool. Now it's true that we've added the
> soapmonitorPhase already and this documentation should change anyway,
> but the point would be the same for any third party Module that might
> need it's own phases that are NOT yet in our default config.
>
> If Modules could simply express Phases and constraints for deploying
> them, all this would boil down to <module ref="soapmonitor"/>. That is all.
>
> Thanks,
> --Glen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
David Illsley - IBM Web Services Development
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org