HI all,
do standalone instances of Axis2 deal with the same origin scenarios?
If a remote client is running Ajax/XHR on a browser, there are cases taht
that the browser will send a preflight OPTIONS request to the server before
it can send the request. Does Axis2 deal with such a request or does
According to the following thread:
http://www.mail-archive.com/[email protected]/msg44983.html
If calling a WSDL2Java generated client stub within a multithreaded framework
such as a Struts servlet, the recommended approach is to create a new client
stub per thread but have a cached or si
The problem is not sending the servicegroupID or the session related
information. When you keep sending request it always create a new
instances, only way to stop is to copy the servicegroupID from the
previous request and send it alone with the next request.
One another way to get this work is tr
Hi Deepal,
The article describes how to keep session, without needing to reuse the same
ServiceClient object. I.e. keep session using different ServiceClient objects.
My question was, why is the web service class being re-instantiated for each
web
service invocation for ALL scopes except applica
Now, I got the point. For that you need to try the following.
http://wso2.org/library/3184
Deepal
> Hi Deepal,
>
> I have tried all scopes. In client side I have set manage session to true.
> For instance. I set the session scope in services.xml to
> "transportsession".
> In the web service I use
Hi Deepal,
I have tried all scopes. In client side I have set manage session to true.
For instance. I set the session scope in services.xml to "transportsession".
In the web service I use
MessageContext messageContext = MessageContext.getCurrentMessageContext();
ServiceContext scontext = messageC
On 1/23/2011 7:11 AM, am am wrote:
> I am starting on axis2 (1.5.4).
> I am looking into the various session scopes for web services
> (request, soapsession etc).
> By experimenting, I notice that in all scopes except the application
> scope, there is a new instance of my web service being create
I am starting on axis2 (1.5.4).
I am looking into the various session scopes for web services (request,
soapsession etc).
By experimenting, I notice that in all scopes except the application scope,
there is a new instance of my web service being created per service call.
Only by setting the scope
See AXIS2-4640 for a discussion about this.
Andreas
On Sun, Jan 23, 2011 at 10:37, am am wrote:
> Hi,
>
> I am starting on axis2 (1.5.4). After doing a wsdl2java code generation, I
> was looking into the artifacts.
> For a service that accepts a String and returns a String an ADBean was
> genera
Hi,
I am starting on axis2 (1.5.4). After doing a wsdl2java code generation, I was
looking into the artifacts.
For a service that accepts a String and returns a String an ADBean was
generated
for the in-out params. The bean has some fields and booleans to indicate if the
value has been set f
10 matches
Mail list logo