Hi
I am wandering if Axis2 library could be able to send multiple SOAP
requests from a client in a thread-safe way.
I have seen that using axutil_env_create_all I could have a system
environment and with axutil_init_thread_env and
axutil_free_thread_env I could handle something like
On Fri, Feb 20, 2009 at 1:37 PM, Jorge Nevado jorge.nev...@ericsson.comwrote:
Hi there,
Axis2/C's client APIs are not thoroughly test for thread safeness. It's said
that svc client API is not good to use in a mult-threaded environment. I
think you can create your own threads and test some random
Hello Jorge, welcome
I believe Manjula posted some good info on how to use then clean up
calls from multiple threads.
It is better to use Guththila as your parser with more than one thread.
It should be your default now after 1.5.0.
Axis handles internal management of threads so you only need
We want to post the webservice request to JMS Queue. I found samples only
exposing the service over JMS. How would we get access to connection
instance in skeleton or receiverInout if we configure JMS parameters in
axis2.xml?
Thanks in advance.
faultcode and faultstring are not in the right namespace. They should
have the same namespace as the SOAP envelope.
Andreas
On Fri, Feb 20, 2009 at 06:36, Rahul Kulkarni
rahul.kulkar...@symphonysv.com wrote:
Actually, the SOAP Fault is getting mapped to the AxisFault exception, but
doesn't
Hi Prasuna,
Once you have exposed your web service over JMS , you can use
WSDL2JAVA to generate client side Stub and it is possible to use this
Stub to post a request to a JMS Queue . Further you can find URL for
the JMS endpoint on generated WSDL document.
// JMS Endpoit
Hi;
This[1] may be helpful.
Thanks regards.
-Prabath
[1]:http://blog.facilelogin.com/2008/12/enabling-jms-transport-for-axis2.html
Prasuna Lanka wrote:
We want to post the webservice request to JMS Queue. I found samples
only exposing the service over JMS. How would we get access to
But from the SOAP 1.1 primer, it looks like that it has been supported.
Has it to do anything with #AXIS-2394 ticket? Link:
(http://issues.apache.org/jira/browse/AXIS-2394)
Thanks and Regards,
// Rahul
-Original Message-
From: Andreas Veithen [mailto:andreas.veit...@gmail.com]
Sent:
contentType is set for the each element in your XSD e.g.
xsd:element maxOccurs=1 minOccurs=1 name=binaryData
nillable=true
type=xmime:base64Binary
xmime:expectedContentTypes=application/octet-stream
I am new to Axis2; i am using ADB.
I'd like to skip namespace prefixes in XML response. For example if the
client receive
name xsi:type=xsd:stringJohn/name
or receive
s:name xsi:type=xsd:stringJohn/s:name
it must work in both case. At the moment only the second case work, because
in xsd
You could have elementFormDefault=unqualified in the schema of the WSDL.
This instructs the user not to care about the namespaces.
Thanks,
Keith.
On Fri, Feb 20, 2009 at 7:39 PM, durbans m34890...@yahoo.it wrote:
I am new to Axis2; i am using ADB.
I'd like to skip namespace prefixes in XML
Hi Martin,
I test with a very simple service which is deployed as a POJO. Following is
the WSDL generated by Axis2 for the service.
?xml version=1.0 encoding=UTF-8?
wsdl:definitions xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:mime=
http://schemas.xmlsoap.org/wsdl/mime/; xmlns:soap12=
Hi,
It seems like you have a version mismatch problem with Axiom, it may
refer to a incompatible Axiom.jar file from somewhere, pleases use the
Jar files available on you axis2 1.4.1 lib directory to compile your
services and also to run your web service client. Since you haven't
mention when
Hi Appasamy ,
try use following code segment on current MeaasgeContext .
String clientIp = (String)messageContext.getProperty(REMOTE_ADDR);
Thanks ,
On Fri, Feb 20, 2009 at 3:41 AM, RickCromer
rick.cro...@stratustelecom.com wrote:
I get it from Axis v1 using the following code, but I don't
Hi Nandana,
sorry for the late answer. Here is attached the wsdl I used.
And the code to create the AxisService is here [1]
[1]
http://github.com/matthieu/apache-ode/blob/085025ab3639c7aa0255bbb9b905210ff6caf295/axis2/src/main/java/org/apache/ode/axis2/hooks/ODEAxisService.java#L80
Thanks a lot
The wsdl is also available here : http://gist.github.com/67691
Just in case the attachement did not make it through.
Alexis
On Fri, Feb 20, 2009 at 1:02 PM, Alexis Midon mi...@intalio.com wrote:
Hi Nandana,
sorry for the late answer. Here is attached the wsdl I used.
And the code to create
I'm trying to debug my application on the server and can't figure out how to
hook the debugger into an JAX-WS Axis2 *.aar to Tomcat 6 deployment. Can
someone help me with this?
I've hooked into my SOAP services using Axis1 many times so I understand about
setting up the debug connection.
Using Eclipse Ganymede (though it should work for most flavors of eclipse)
1. In the Debug view, go to Debug Configurations... it'll be in the
tool bar near the top of eclipse
2. In the Debug Configurations popup, select Remote Java Application
from the list on the left and then click the
Steve, I did this and now I'm able to connect, thanks.
Regards,
Rick Cromer
-Original Message-
From: Steve Hall [mailto:sh...@starmountsystems.com]
Sent: Friday, February 20, 2009 4:27 PM
To: axis-user@ws.apache.org
Subject: Re: Axis2 - How to hook Eclipse Debugger into aar on Tomcat
19 matches
Mail list logo