AUTO: Hyen V Chung/Austin/IBM is out of the office until 07/19/2002. (returning 07/13/2011)

2011-07-01 Thread Hyen V Chung
I am out of the office until 07/13/2011. Note: This is an automated response to your message "RE: Identify IP address of the source request" sent on 7/1/2011 9:04:40 PM. This is the only notification you will receive while this person is away. --

Problem creating Axis2 Rampart Client

2011-07-01 Thread Louis Amstutz
I'm creating a web service using Axis2 which uses Rampart for authentication. In all the samples for Rampart, the client needs to have a client side repository for Axis2. Rampart is started on the client as follows: ConfigurationContext ctx = ConfigurationContextFactory.createConfigurationContextF

Re: Identify IP address of the source request

2011-07-01 Thread Deepal jayasinghe
> A little more detail: > > The message context is set as a thread-local variable in the thread > executing Servlet.service(ServletRequest,ServletResponse) or its > specializations. A request must have been received. We set the thread local variable just before we call the service, to be exact in

Re: Identify IP address of the source request

2011-07-01 Thread Jeff Greif
A little more detail: The message context is set as a thread-local variable in the thread executing Servlet.service(ServletRequest,ServletResponse) or its specializations. A request must have been received. Even if the servlet is being constructed on each request, Servlet.init may be called befo

RE: Identify IP address of the source request

2011-07-01 Thread Afkham Azeez
The MessageContext is set as a thread local variable when a request is received. In fact, for a msg context to be created, either a message should be received or sent. A valid msg context will be accessible in your operation implementation methods. On Jul 1, 2011 2:23 AM, "Matta, Geethamadhurima" <

Re: version 1.5.5 or 1.6.0

2011-07-01 Thread Andreas Veithen
The answer to your question is given on the Axis2 home page [1]: "1.5.5 is a maintenance release that contains fixes for several issues in the sample projects included with the binary distribution as well as a couple of other issues. If possible users should upgrade to Axis2 1.6.0 (see below). Th

RE: Identify IP address of the source request

2011-07-01 Thread Tony HEDOUX
Hi, You should try the same syntax but in your calling method (not in the init() ). package myWebService; import org.apache.axis2.context.MessageContext; public class MyService { public String giveYourIp(){ MessageContext msgCtx = MessageContext.getCurrentMessageContext(); return (St

RE: Identify IP address of the source request

2011-07-01 Thread Matta, Geethamadhurima
Nadir, How to get msgContext obj. I am using: MessageContext msgCtx = MessageContext.getCurrentMessageContext(); But msgCtx is null. From: Nadir Amra [mailto:[email protected]] Sent: 30 June 2011 21:59 To: [email protected] Cc: '[email protected]' S

Axis2 Server side asynchronous callback/ws-addressing help

2011-07-01 Thread BalajiG
We currently use Axis2 (1.5) for our synchronous service calls. We have a requirement where BPEL process written in another language need to invoke an asynchronous java web service which will give a call-back using ws-addressing. After reading through the various user guide and posts, I’m still no