Thanks for your time, the comments are very helpful
Just to clarify, you suggested that changing the Axis2.xml is not needed when
writing modules but the first guide is doing thatIf possible, I would like the
module to activate on a single service
So far this is what I have,
the SimpleModule.java which I assume is mostly default
package abd;
import org.apache.axis2.AxisFault;import
org.apache.axis2.context.ConfigurationContext;import
org.apache.axis2.description.AxisDescription;import
org.apache.axis2.description.AxisModule;import
org.apache.axis2.modules.Module;import org.apache.neethi.Assertion;import
org.apache.neethi.Policy;
public class SimpleModule implements Module{
public void init(ConfigurationContext configContext, AxisModule module)
throws AxisFault { }
public void engageNotify(AxisDescription axisDescription) throws AxisFault
{ }
public void shutdown(ConfigurationContext configurationContext) throws
AxisFault { } public String[] getPolicyNamespaces() { return
null; }
public void applyPolicy(Policy policy, AxisDescription axisDescription)
throws AxisFault { } public boolean
canSupportAssertion(Assertion assertion) { return true; }}
The SimpleHandler.java which I pasted before and the module.xml
<module name="SimpleModule" class="abd.SimpleModule"> <InFlow>
<handler name="InFlowLogHandler" class="abd.SimpleHandler"> <order
phase="TestPhase"/> </handler> </InFlow>
<OutFlow> <handler name="OutFlowLogHandler"
class="abd.SimpleHandler"> <order phase="TestPhase"/>
</handler> </OutFlow>
<OutFaultFlow> <handler name="FaultOutFlowLogHandler"
class="abd.SimpleHandler"> <order phase="TestPhase"/>
</handler> </OutFaultFlow>
<InFaultFlow> <handler name="FaultInFlowLogHandler"
class="abd.SimpleHandler"> <order phase="TestPhase"/>
</handler> </InFaultFlow></module>
The contents of the bin folder are
abd > .class filesMETA-INF > module.xml
Date: Tue, 28 May 2013 14:41:40 -0400
From: deep...@gmail.com
To: java-dev@axis.apache.org
Subject: Re: Deploying a handler
What is confusing ?
You can add handlers either using modules or by editing axis2.xml,
however we do not recommend changes to axis2.xml. That is why we
introduced the concepts of modules, where user can deploy customs
handlers without changing any global configurations.
Deepal
This is confusing now so, I
will test the previous method tomorrow just for testing, but
I will give the modules a more detailed look for the final
deployment
Date: Tue, 28 May 2013 11:24:27 -0400
From: deep...@gmail.com
To: java-dev@axis.apache.org
Subject: Re: Deploying a handler
NOPE, you do not need to
modify axis2.xml.
Deepal
yes it will work and you need to modify the
axis2.xml as well
On Tue, May 28, 2013 at 6:36
PM, Deepal jayasinghe <deep...@gmail.com>
wrote:
The way you deploy handlers in Axis2 is using
the concept call Module. Please follow following
tutorial to get a good understanding how to do
that.
http://axis.apache.org/axis2/java/core/docs/modules.html
http://www.packtpub.com/article/apache-axis2-web-services-writing-module
Deepal
Hello,
I wrote my own simple handler which I
want to deploy. This handler is the
first to work on inflowing SOAP messages
and as such I modified the configuration
to have it in the inflow section.
My question is, how do I build and
deploy this handler?
Thanks
