Hello all,
for using WS-Security functionality with rampart modul in Axis2, we have
written a CallbackHandler class, simliar too the one explained here,
http://wso2.org/library/3733.
Question: Is there any way to get access to ServiceContext or AxisService
in CallbackHandler class???
Thanks so m
On Fri, Jan 13, 2012 at 9:33 PM, André Spielmann wrote:
> Hello all,
>
> for using WS-Security functionality with rampart modul in Axis2, we have
> written a CallbackHandler class, simliar too the one explained here,
> http://wso2.org/library/3733.
>
> Question: Is there any way to get access to
Andre,
I agree with Sagara regarding the purpose of CallbackHandler ,
http://wso2.org/library/3733
But I would think that line below should give you the configurationContext.
org.apache.axis2.context.ConfigurationContext configurationContext =
MessageContext.getCurrentMessageCont
Hi All,
I have two questions on attachments in Axis2 - would appreciate any
thoughts/pointers/answers.
1. Until recently our Axis based service implementation was not
supporting attachments. We now enabled attachments support by enabling
MTOM/SwA in our service.xml. After this we see tha
Dear all,
thanks .. I already tried to get the MessageContext as well. Does not work,
it's null.
Any other idea?
Any other way to get access to some objects which are set
by ServiceLifeCycle at startup?
Thank
Andre
On Fri, Jan 13, 2012 at 5:28 PM, wrote:
> Andre,
>
> ** **
>
> I agree
Hi, search for my last Post in the archive. (MessageContext null) There you
will find the solution.. Tom
Für's private
http://toms-toy.de/thomas%20grabietz%20...@toms-toy.de%20(0xE43515AC)%20pub.asc
"André Spielmann" schrieb:
Dear all,
thanks .. I already tried to get the MessageContext as
Hi all,
I'm performing a stress test on AXIS2C, sending multiple Asynchronous
request from a client to a service.
I'm using an instance of svc_client to send multiple non_blocking requests
to a service, but after the request I lock the thread to wait for the
callback on complete to finish
Not exactly correct. The article you are citing is quite old and
assumes that class loaders always use a parent-first delegation
policy. With that policy you would not get this ClassCastException.
That follows from what they call the Uniqueness Principle. However, in
Tomcat a webapp class loader us
You are in a wrong mailing list, please find correct list here[1].
[1] - http://axis.apache.org/axis2/c/core/lists_issues.html
Thanks !
On Sat, Jan 14, 2012 at 1:59 AM, Alex Mantaut wrote:
>
> Hi all,
> I'm performing a stress test on AXIS2C, sending multiple Asynchronous
> request from a
