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 Edward Bush <Bu...@crlcorp.com> on 2007/07/05 22:06:10 UTC
[Axis2] v1.2 - Handler not firing after Module engaged
I'm creating a Module/Handler combination. The module.xml declares the
Handler to be invoked during multiple phases (OperationInPhase,
OperationOutPhase, OperationInFaultPhase, OperationOutFaultPhase), which
I chose by inspecting the chain for the operation(s) I'm running.
I can deploy the Module/Handler fine, but after engaging the Module for
a service, the Handler's invoke method never seems to be called. My
inference is that - somehow - the association that should be made
between the Handler and the phase is never made. I did discover that
the Handler's name doesn't appear to be set, at least, not prior to the
Handler's init method being called. Likewise, the HandlerDescription's
handler property is not set. Rationalizing that this might perhaps be
the cause of my woes, I took to setting each of them, but to no avail.
Yes, I called super.init(desc) first.
I've followed the userguide/logging sample very closely, so I'm somewhat
surprised to find that this isn't working. The one thing I did not do
(and have no desire to do) is to introduce a custom phase into the
axis2.xml configuration. My primary reason for wanting to avoid this
approach is that I have not been able to successfully get that file to
be loaded (I'm "embedding" Axis2 into an application).
Any suggestions at all?
Thanks in Advance!
Eddie Bush
Software Analyst
Clinical Reference Laboratory
913-693-1519
bushe@crlcorp.com
RE: [Axis2] v1.2 - Handler not firing after Module engaged
Posted by Edward Bush <Bu...@crlcorp.com>.
A more recent GA release than 1.2, I meant to say :-)
-----Original Message-----
From: Edward Bush [mailto:BushE@crlcorp.com]
Sent: Friday, July 06, 2007 2:15 PM
To: axis-user@ws.apache.org
Subject: RE: [Axis2] v1.2 - Handler not firing after Module engaged
Deepal,
Is <module ref="my-module" /> intended to refer to a module's NAME or
the name of the module's FILE?
It would appear that, upon really tracing this through and mucking
around with things, the name I specify for my module in the module.xml
is not being honored! Rather, the name seems to be set to a partial
substring of the module's MAR file.
Ex: client-srvcs-mar-1.0-SNAPSHOT.mar, whose module.xml gives it the
name 'soapLogger' must instead be referenced as 'client-srvcs-mar-1.0'.
This isn't the expected behavior, is it?
This has been my entire problem with this. I'm running Axis 1.2 GA
release. I believe that's the most recent. If there is a GA release
available, that may be used as a Maven2 dependency, I would love to know
it.
Thanks for your patience and assistance!
Eddie Bush
Software Analyst
Clinical Reference Laboratory
bushe at crlcorp dot com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: [Axis2] v1.2 - Handler not firing after Module engaged
Posted by Edward Bush <Bu...@crlcorp.com>.
Deepal,
Is <module ref="my-module" /> intended to refer to a module's NAME or
the name of the module's FILE?
It would appear that, upon really tracing this through and mucking
around with things, the name I specify for my module in the module.xml
is not being honored! Rather, the name seems to be set to a partial
substring of the module's MAR file.
Ex: client-srvcs-mar-1.0-SNAPSHOT.mar, whose module.xml gives it the
name 'soapLogger' must instead be referenced as 'client-srvcs-mar-1.0'.
This isn't the expected behavior, is it?
This has been my entire problem with this. I'm running Axis 1.2 GA
release. I believe that's the most recent. If there is a GA release
available, that may be used as a Maven2 dependency, I would love to know
it.
Thanks for your patience and assistance!
Eddie Bush
Software Analyst
Clinical Reference Laboratory
bushe at crlcorp dot com
-----Original Message-----
From: Deepal Jayasinghe [mailto:deepal@opensource.lk]
Sent: Friday, July 06, 2007 12:21 AM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] v1.2 - Handler not firing after Module engaged
Hi Edward ,
Could you please create a JIRA and attach your module.mar file , then we
can help you to fix you problem.
Thanks
Deepal
> I'm creating a Module/Handler combination. The module.xml declares
> the Handler to be invoked during multiple phases (OperationInPhase,
> OperationOutPhase, OperationInFaultPhase, OperationOutFaultPhase),
> which I chose by inspecting the chain for the operation(s) I'm
running.
>
> I can deploy the Module/Handler fine, but after engaging the Module
> for a service, the Handler's invoke method never seems to be called.
> My inference is that - somehow - the association that should be made
> between the Handler and the phase is never made. I did discover that
> the Handler's name doesn't appear to be set, at least, not prior to
> the Handler's init method being called. Likewise, the
> HandlerDescription's handler property is not set. Rationalizing that
> this might perhaps be the cause of my woes, I took to setting each of
> them, but to no avail. Yes, I called super.init(desc) first.
>
> I've followed the userguide/logging sample very closely, so I'm
> somewhat surprised to find that this isn't working. The one thing I
> did not do (and have no desire to do) is to introduce a custom phase
> into the axis2.xml configuration. My primary reason for wanting to
> avoid this approach is that I have not been able to successfully get
> that file to be loaded (I'm "embedding" Axis2 into an application).
>
> Any suggestions at all?
>
> Thanks in Advance!
>
> Eddie Bush
> Software Analyst
> Clinical Reference Laboratory
> bushe at crlcorp dot com
--
Thanks,
Deepal
................................................................
"The highest tower is built one brick at a time"
---------------------------------------------------------------------
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] v1.2 - Handler not firing after Module engaged
Posted by Deepal Jayasinghe <de...@opensource.lk>.
Hi Edward ,
Could you please create a JIRA and attach your module.mar file , then we
can help you to fix you problem.
Thanks
Deepal
> I'm creating a Module/Handler combination. The module.xml declares
> the Handler to be invoked during multiple phases (OperationInPhase,
> OperationOutPhase, OperationInFaultPhase, OperationOutFaultPhase),
> which I chose by inspecting the chain for the operation(s) I'm running.
>
> I can deploy the Module/Handler fine, but after engaging the Module
> for a service, the Handler's invoke method never seems to be called.
> My inference is that - somehow - the association that should be made
> between the Handler and the phase is never made. I did discover that
> the Handler's name doesn't appear to be set, at least, not prior to
> the Handler's init method being called. Likewise, the
> HandlerDescription's handler property is not set. Rationalizing that
> this might perhaps be the cause of my woes, I took to setting each of
> them, but to no avail. Yes, I called super.init(desc) first.
>
> I've followed the userguide/logging sample very closely, so I'm
> somewhat surprised to find that this isn't working. The one thing I
> did not do (and have no desire to do) is to introduce a custom phase
> into the axis2.xml configuration. My primary reason for wanting to
> avoid this approach is that I have not been able to successfully get
> that file to be loaded (I'm "embedding" Axis2 into an application).
>
> Any suggestions at all?
>
> Thanks in Advance!
>
> *Eddie Bush*
> Software Analyst
> Clinical Reference Laboratory
> 913-693-1519
> bushe@crlcorp.com <ma...@crlcorp.com>
>
--
Thanks,
Deepal
................................................................
"The highest tower is built one brick at a time"
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org