Re: unsubscribe
Please send a mail to axis-user-unsubscr...@ws.apache.org On Fri, Oct 9, 2009 at 06:10, Gudikoti, Rajesh rajesh.gudik...@logica.com wrote: Please help Logica to respect the environment by not printing this email / Pour contribuer comme Logica au respect de l'environnement, merci de ne pas imprimer ce mail / Bitte drucken Sie diese Nachricht nicht aus und helfen Sie so Logica dabei, die Umwelt zu schützen. / Por favor ajude a Logica a respeitar o ambiente não imprimindo este correio electrónico. This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
Async Web service with two port types
Hi all, I'm explaoring the async field of web services and have developed one using ws-addressing, and have my service when a request comes in, reply with HTTP 202 message, and the sending the actual result to a new endpoint, this works fine. In the end I maybe want to compose a BPEL process with these services and in BPEL examples and sites I looked at all talk about a service with two port types, on for kicking of the service and the other one for a call back, I've not grasped this fully so was wondering if anyone have done something similar before and/or can provide an example. In the BPEL world I typically see something like this portType name=LoanService operation name=initiate input message=tns:LoanServiceRequestMessage/ /operation /portType !-- portType implemented by the requester of LoanService BPEL process for asynchronous callback purposes -- portType name=LoanServiceCallback operation name=onResult input message=tns:LoanServiceResultMessage/ /operation /portType Also not entierly sure how the service then should be implemented. Any tips or hint on this matter?? cheers, Håkon -- Håkon Sagehaug, Scientific Programmer Parallab, Bergen Center for Computational Science (BCCS) UNIFOB AS (University of Bergen Research Company)
RE: Cannot load SchemaTypeSystem
Ouuh sorry I missed that single .class file... but anyway, if all of the xsb stuff is on the runtime class path (i. e. the directories containing it all) this is OK. I preferred to pack this all together as a JAR and add it to the JAR zoo of the application. But that problem solved, now the constructors. The generated XyzStub class is the user-friendly frontend of all generated stuff. For standard scenarios this will do, and it has some additional constructors allowing you to add additional configuration besides the endpoint. I think this is merely a guess what may be needed in usual scenarios -- but in the simplest cases, you should be done simply using the constructor taking the endpoint only. In my case I needed additional configuration, and that forced me to use a neighbour class of XyzStub -- Xyz. This class provides some additional functionality to set up Options. I needed this to prevent the generated code to use chunked transfer, which usually is allowed to use, but was not in ma case. Not that helpful maybe, but the existing constructors should work if provided with useful non-null arguments. (but whats useful at the end...) hth, --cg -Original Message- From: sch...@afrigis.co.za [mailto:sch...@afrigis.co.za] Sent: Friday, October 09, 2009 7:31 AM To: axis-user@ws.apache.org; fryar...@gmail.com Subject: RE: Cannot load SchemaTypeSystem Awesome Michael, That did the job, in my case I had to copy it to the build directory as it is a web app but it worked perfectly. Now though I encountered a lovely surprise, a NullPointerException thrown by one of the generated stubs, specifically this line: _messageContext.getTransportOut().getSender().cleanup(_messageContext); I will add some log statements in here but I am guessing it is _messageContext. I now the stub had various constructors and for some of these if you only provide the end point it sets the other, which I believe is this _messageContext to null, not sure why those constructors exist then if you should not really be using them, or am I missing something? -- Kind Regards Schalk Neethling -Original Message- From: FRYARS, Michael [mailto:fryar...@gmail.com] Sent: 08 October 2009 10:06 PM To: axis-user@ws.apache.org Subject: Re: Cannot load SchemaTypeSystem In among all those .xsb files you'll find a single .class file, and this .class must be available at runtime. [Note: XMLBeans generates the .class directly, it doesn't generate a .java and then have it compiled] I saw the problem you describe when running JUnit tests which used an axis2-generated SOAP client. The AAR deployed in the axis2 WAR was fine. But the (eclipse) project that held the tests didn't have this XMLBeans .class file in the 'bin' directory. It was present in the 'resource' directory, which was the target directory for XMLBeans generated source, but it wasn't copied to the bin directory and so wasn't available to the test client at runtime. Simply copying it across to the bin directory solved the problem. Regards, Michael sch...@afrigis.co.za a écrit : Hi there Christian, I did find the resource folder with stacks of .xsb files on. I added this to the sources in the build path in Eclipse as well as to the Output... tab. However, I still get the problem, any ideas as to where else I need to set something? Maybe something to do with Tomcat? Thanks for your help. -- Kind Regards Schalk Neethling -Original Message- From: Christian Gosch [mailto:christian.go...@inovex.de] Sent: 08 October 2009 02:13 PM To: axis-user Subject: RE: Cannot load SchemaTypeSystem XMLbeans does not only generate classes, but lots of additional binaries, which must be presesnt on the classpath. Look through your output folder, and you will find an additional folder with this stuff. Add it to your runtime classpath, and you may be done :-) --cg -Original Message- From: sch...@afrigis.co.za [mailto:sch...@afrigis.co.za] Sent: Thursday, October 08, 2009 12:29 PM To: axis-user@ws.apache.org Subject: Cannot load SchemaTypeSystem Hi there, I finally got Axis2 to generate the appropriate stubs etc for me, finally having to use the command line tool, and I chose XMLBeans as my data binding solution as I have worked with it before and found it real easy to use. After having to hunt around for some jar files I can finally run a servlet to test out the generated code. I start of the servlet with the following: GetPointsByRadiusDocumentImpl pointsByRadius = new GetPointsByRadiusDocumentImpl(GetPointsByRadiusDocument.type); However, when running the servlet I get the exception mentioned above i.e. java.lang.RuntimeException: Cannot load SchemaTypeSystem. Unable to load class with name
RE: Cannot load SchemaTypeSystem
General observation on NPE. Might apply to your case, Shalk, or it might not. I sometimes found NPEs in the execution of generated code when I wasn't careful to exactly match the axis2 version used for generation with the version used at runtime. (missing/renamed member variables, missing/renamed methods, etc) Regards, Michael Christian Gosch-2 wrote: Ouuh sorry I missed that single .class file... but anyway, if all of the xsb stuff is on the runtime class path (i. e. the directories containing it all) this is OK. I preferred to pack this all together as a JAR and add it to the JAR zoo of the application. But that problem solved, now the constructors. The generated XyzStub class is the user-friendly frontend of all generated stuff. For standard scenarios this will do, and it has some additional constructors allowing you to add additional configuration besides the endpoint. I think this is merely a guess what may be needed in usual scenarios -- but in the simplest cases, you should be done simply using the constructor taking the endpoint only. In my case I needed additional configuration, and that forced me to use a neighbour class of XyzStub -- Xyz. This class provides some additional functionality to set up Options. I needed this to prevent the generated code to use chunked transfer, which usually is allowed to use, but was not in ma case. Not that helpful maybe, but the existing constructors should work if provided with useful non-null arguments. (but whats useful at the end...) hth, --cg -Original Message- From: sch...@afrigis.co.za [mailto:sch...@afrigis.co.za] Sent: Friday, October 09, 2009 7:31 AM To: axis-user@ws.apache.org; fryar...@gmail.com Subject: RE: Cannot load SchemaTypeSystem Awesome Michael, That did the job, in my case I had to copy it to the build directory as it is a web app but it worked perfectly. Now though I encountered a lovely surprise, a NullPointerException thrown by one of the generated stubs, specifically this line: _messageContext.getTransportOut().getSender().cleanup(_messageContext); I will add some log statements in here but I am guessing it is _messageContext. I now the stub had various constructors and for some of these if you only provide the end point it sets the other, which I believe is this _messageContext to null, not sure why those constructors exist then if you should not really be using them, or am I missing something? -- Kind Regards Schalk Neethling -- View this message in context: http://www.nabble.com/Cannot-load-SchemaTypeSystem-tp25801609p25819161.html Sent from the Axis - User mailing list archive at Nabble.com.
Increase performance using axis 2 client stubs
hi all,
In our project we've got a web portal that uses web services, that we call
by generating stubs using axis2 lib, as the back bone. I'm looking for ways
to improve the performance in the calling bit now I've stated reusing the
HttpClient object that is used, we have a Util class that wrappes the logic
of calliing all the services so for now we're interacting with three, and
all uses the same HttpClient object. Should every call be inside a
syncronized block?like this
synchronized(httpClient){
call service
}
Or is it a better way to do this?Could the http clients be in a pool managed
by tomcat in some way?
Also if there is any other tricks on how to increase performace on client
side axis2 calls, please say how
cheers, Håkon
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
Re: Increase performance using axis 2 client stubs
Hi
One more thing I create the HttpClient object like this
MultiThreadedHttpConnectionManager conMrg = new
MultiThreadedHttpConnectionManager();
conMrg.getParams().setDefaultMaxConnectionsPerHost(10);
httpClient = new HttpClient(conMrg);
cheers, Håkon
2009/10/9 Håkon Sagehaug hakon.sageh...@bccs.uib.no
hi all,
In our project we've got a web portal that uses web services, that we call
by generating stubs using axis2 lib, as the back bone. I'm looking for ways
to improve the performance in the calling bit now I've stated reusing the
HttpClient object that is used, we have a Util class that wrappes the logic
of calliing all the services so for now we're interacting with three, and
all uses the same HttpClient object. Should every call be inside a
syncronized block?like this
synchronized(httpClient){
call service
}
Or is it a better way to do this?Could the http clients be in a pool
managed by tomcat in some way?
Also if there is any other tricks on how to increase performace on client
side axis2 calls, please say how
cheers, Håkon
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
[Axis2] attribute name in xs:element
Hi, I deploy my web service with Axis2 and weblogic 10 and I have a question about parameter name in wsdl... Why are they specified param0 for the name? For example : xs:element minOccurs=0 name=param0 nillable=true type=ns1:DonneesWS/ instead of xs:element minOccurs=0 name=donnees nillable=true type=ns1:DonneesWS/ What is the solution to have donnees instead fo param0? Thanks a lot, David
RE: Increase performance using axis 2 client stubs
Here is some code we use. Basically it uses commons pooling and creates a
pool of stubs. The expensive operation of creating the axis2 configuration
etc is only done once.
It would be simple to wrap it as a proxy of your stub interface and put the
attached code in the proxy and so the implementation details hidden from the
caller.
Hope it helps.
P
_
From: hakon.sageh...@googlemail.com [mailto:hakon.sageh...@googlemail.com]
On Behalf Of Håkon Sagehaug
Sent: 09 October 2009 12:02
To: axis-user@ws.apache.org
Subject: Increase performance using axis 2 client stubs
hi all,
In our project we've got a web portal that uses web services, that we call
by generating stubs using axis2 lib, as the back bone. I'm looking for ways
to improve the performance in the calling bit now I've stated reusing the
HttpClient object that is used, we have a Util class that wrappes the logic
of calliing all the services so for now we're interacting with three, and
all uses the same HttpClient object. Should every call be inside a
syncronized block?like this
synchronized(httpClient){
call service
}
Or is it a better way to do this?Could the http clients be in a pool managed
by tomcat in some way?
Also if there is any other tricks on how to increase performace on client
side axis2 calls, please say how
cheers, Håkon
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
Axis2ClientWebService1.java
Description: Binary data
Re: Increase performance using axis 2 client stubs
From memory (apologies in advance if this is off the mark), I think it's the
axis2 client stub that will serialize multiple calls - i.e. will finish one
request/response before beginning another. So if you want to parallelize the
calls, what's needed is multiple client stubs, and multiple threads to run
them in.
[I used java.util.concurrent.ThreadPoolExecutor, one stub object per thread,
to do some basic load testing of a service.]
Regards,
Michael
Håkon Sagehaug wrote:
Hi
One more thing I create the HttpClient object like this
MultiThreadedHttpConnectionManager conMrg = new
MultiThreadedHttpConnectionManager();
conMrg.getParams().setDefaultMaxConnectionsPerHost(10);
httpClient = new HttpClient(conMrg);
cheers, Håkon
2009/10/9 Håkon Sagehaug hakon.sageh...@bccs.uib.no
hi all,
In our project we've got a web portal that uses web services, that we
call
by generating stubs using axis2 lib, as the back bone. I'm looking for
ways
to improve the performance in the calling bit now I've stated reusing
the
HttpClient object that is used, we have a Util class that wrappes the
logic
of calliing all the services so for now we're interacting with three,
and
all uses the same HttpClient object. Should every call be inside a
syncronized block?like this
synchronized(httpClient){
call service
}
Or is it a better way to do this?Could the http clients be in a pool
managed by tomcat in some way?
Also if there is any other tricks on how to increase performace on client
side axis2 calls, please say how
cheers, Håkon
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
--
View this message in context:
http://www.nabble.com/Increase-performance-using-axis-2-client-stubs-tp25819232p25819536.html
Sent from the Axis - User mailing list archive at Nabble.com.
Re: Increase performance using axis 2 client stubs
Hi
Thanks for the replys,
I could tell little more about my setup perhaps. I've got on
eConfigurationContext that is shared between the stubs, each service has one
stub connecte to it. Thw web app is running inside tomcat, so the util
class that is responsible for calling managing the stubs, is I guess on
instance per thread, if on erequest to the web app equals one thread. Hence
one stub per service per thread.
One way to go is a pool of stunbs I guess shared by the web application.
cheers, Håkon
2009/10/9 mfr fryar...@gmail.com
From memory (apologies in advance if this is off the mark), I think it's
the
axis2 client stub that will serialize multiple calls - i.e. will finish one
request/response before beginning another. So if you want to parallelize
the
calls, what's needed is multiple client stubs, and multiple threads to run
them in.
[I used java.util.concurrent.ThreadPoolExecutor, one stub object per
thread,
to do some basic load testing of a service.]
Regards,
Michael
Håkon Sagehaug wrote:
Hi
One more thing I create the HttpClient object like this
MultiThreadedHttpConnectionManager conMrg = new
MultiThreadedHttpConnectionManager();
conMrg.getParams().setDefaultMaxConnectionsPerHost(10);
httpClient = new HttpClient(conMrg);
cheers, Håkon
2009/10/9 Håkon Sagehaug hakon.sageh...@bccs.uib.no
hi all,
In our project we've got a web portal that uses web services, that we
call
by generating stubs using axis2 lib, as the back bone. I'm looking for
ways
to improve the performance in the calling bit now I've stated reusing
the
HttpClient object that is used, we have a Util class that wrappes the
logic
of calliing all the services so for now we're interacting with three,
and
all uses the same HttpClient object. Should every call be inside a
syncronized block?like this
synchronized(httpClient){
call service
}
Or is it a better way to do this?Could the http clients be in a pool
managed by tomcat in some way?
Also if there is any other tricks on how to increase performace on
client
side axis2 calls, please say how
cheers, Håkon
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
--
View this message in context:
http://www.nabble.com/Increase-performance-using-axis-2-client-stubs-tp25819232p25819536.html
Sent from the Axis - User mailing list archive at Nabble.com.
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
[Axis2] Pb with xs:element name?
Hi, I deploy my web service with Axis2-1.3 and weblogic 10 and I have a question about parameter name in wsdl... Why are they specified param0 for the name of the tag xs:element? For example : xs:element minOccurs=0 name=param0 nillable=true type=ns1:DonneesWS/ instead of xs:element minOccurs=0 name=donnees nillable=true type=ns1:DonneesWS/ Thanks a lot, David _ A la recherche de bons plans pour une rentrée pas chère ? Bing ! Trouvez ! http://www.bing.com/search?q=bons+plans+rentr%C3%A9eform=MVDE6
HTTP Works, but Axis Fails
We have a Java application that can connect to a PHP-based server from
California (C) but not from India(I). Besides geographic location, the only
known difference between C and I is that I accesses the Internet via a proxy
server. We believe we have worked out the proxy issues in that I can reach and
receive correct data from the server via HTTP. However, an attempt to access
the same data using Axis/SOAP leads to a 'SocketException: connection Reset'
(output attached).
We have boiled this all down to a JUnit test (attached) that connects to the
same server via HTTP and Axis. This test completely works from C whereas only
the HTTP test works from I. Both tests obtain a list of organism names by going
to the webpage
http://137.120.14.24/wikipathways-test/wpi/webservice/webservice.php/listOrganisms.
Does anyone know the cause to this problem or have any suggestions on how to
debug it (we don't run the web service but can communicate with those that do)?
System Info
---
Server: wso2 wsf/php v.2.0
Clients: OS: Windows-XP, JVM: 1.6
Libraries Used to Run the Test
--
Junit.jar
Axis.jar
jaxrpc.jar
commons-logging-1.0.4.jar
commons-discovery-0.2jar
wsdl4j-1.5.1.jar
Failed Client (I) Output
PROXY SETTINGS BEFORE TEST:
http.proxyHost= 'ptproxy.persistent.co.in'
http.proxyHost= 'null'
http.proxyPort= '8080'
http.proxyUser= 'null'
http.proxyPassword= 'null'
socksProxyHost= 'null'
socksProxyPort= 'null'
java.net.socks.username= 'null'
java.net.socks.password= 'null'
testListOrganismsUsingHTTP organisms:
ns1:listOrganismsResponse
xmlns:ns1=http://www.wso2.org/php/xsd;ns1:organismsAnopheles
gambiae/ns1:organismsns1:organismsArabidopsis
thaliana/ns1:organismsns1:organismsBos
taurus/ns1:organismsns1:organismsBacillus
subtilis/ns1:organismsns1:organismsCaenorhabditis
elegans/ns1:organismsns1:organismsCanis
familiaris/ns1:organismsns1:organismsDanio
rerio/ns1:organismsns1:organismsDrosophila
melanogaster/ns1:organismsns1:organismsEscherichia
coli/ns1:organismsns1:organismsEquus
caballus/ns1:organismsns1:organismsGallus
gallus/ns1:organismsns1:organismsHomo
sapiens/ns1:organismsns1:organismsMus
musculus/ns1:organismsns1:organismsOryza
sativa/ns1:organismsns1:organismsPan
troglodytes/ns1:organismsns1:organismsRattus
norvegicus/ns1:organismsns1:organismsSaccharomyces
cerevisiae/ns1:organismsns1:organismsXenopus
tropicalis/ns1:organisms/ns1:listOrganismsResponse
testListOrganismsUsingHTTP test PASSED
PROXY SETTINGS BEFORE TEST:
http.proxyHost= 'ptproxy.persistent.co.in'
http.proxyHost= 'null'
http.proxyPort= '8080'
http.proxyUser= 'null'
http.proxyPassword= 'null'
socksProxyHost= 'null'
socksProxyPort= 'null'
java.net.socks.username= 'null'
java.net.socks.password= 'null'
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.net.SocketException: Connection reset
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.net.SocketException:
Connection reset
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at
org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:739)
at
org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
com.agilent.pwdemo.unittest.NetworkTests$TestStub.listOrganisms(NetworkTests.java:329)
at
com.agilent.pwdemo.unittest.NetworkTests.testListOrganismsUsingAxis(NetworkTests.java:167)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at
Re : [Axis2] Pb with xs:element name?
Okthe answer is to compile the procjet in debug to have the attribute name donnee in the class file De : Didav Didav dida...@hotmail.fr À : axis-user@ws.apache.org Envoyé le : Ven 9 Octobre 2009, 14 h 41 min 17 s Objet : [Axis2] Pb with xs:element name? Hi, I deploy my web service with Axis2-1.3 and weblogic 10 and I have a question about parameter name in wsdl... Why are they specified param0 for the name of the tag xs:element? For example : xs:element minOccurs=0 name=param0 nillable=true type=ns1:DonneesWS/ instead of xs:element minOccurs=0 name=donnees nillable=true type=ns1:DonneesWS/ Thanks a lot, David Gratuit : Hotmail plus rapide avec Internet Explorer 8 ! Cliquez ici !
xmlns
Hello, When i have in a wsdl: xmlns:ax23=http://vo.coaching.de/xsd; or xmlns:ax24=http://vo.coaching.de/xsd; ax23 or ax24 specify the version of axis2 ?? so axis2 1.3 and axis2 1.4 ??? Thank you David Achetez un nouveau PC et bénéficiez de Windows 7 dès sa sortie ! En savoir plus _ A la recherche de bons plans pour une rentrée pas chère ? Bing ! Trouvez ! http://www.bing.com/search?q=bons+plans+rentr%C3%A9eform=MVDE6
Re: Increase performance using axis 2 client stubs
Again apologies in advance if I've misunderstood. You talked of a util that encapsulates three WS client stub calls (all calls on the same HttpClient object). This util executes in a web container thread triggered by a request to your portal app. You want to speed up the execution of the util. My observation/suggestion is that, assuming the WS calls don't *need* to be consecutive, you can speed things up by making all of the WS calls simultaneously. As it stands, it sounds to me like all of the action happens in the single web container thread allocated to the request. The util executes in this thread, the util makes calls to each of the stubs it holds, also in this single thread. It's with multiple threads (and stubs), not a pool of connections, that you can make the stub calls simultaneous. (although pooling the stubs/connections should certainly help performance too) To do this your util must create the extra threads it needs, or take them from a threadpool, or whatever. In any case it needs to call each stub in a separate thread, not just in the single thread allocated to the request. Regards, Michael Håkon Sagehaug wrote: Hi Thanks for the replys, I could tell little more about my setup perhaps. I've got on eConfigurationContext that is shared between the stubs, each service has one stub connecte to it. Thw web app is running inside tomcat, so the util class that is responsible for calling managing the stubs, is I guess on instance per thread, if on erequest to the web app equals one thread. Hence one stub per service per thread. One way to go is a pool of stunbs I guess shared by the web application. cheers, Håkon 2009/10/9 mfr fryar...@gmail.com From memory (apologies in advance if this is off the mark), I think it's the axis2 client stub that will serialize multiple calls - i.e. will finish one request/response before beginning another. So if you want to parallelize the calls, what's needed is multiple client stubs, and multiple threads to run them in. [I used java.util.concurrent.ThreadPoolExecutor, one stub object per thread, to do some basic load testing of a service.] Regards, Michael -- View this message in context: http://www.nabble.com/Increase-performance-using-axis-2-client-stubs-tp25819232p25822510.html Sent from the Axis - User mailing list archive at Nabble.com.
RE: xmlns
to understand namespace assignments for your XML messages please reference http://wso2.org/library/articles/differentiating-between-soap-versions-looking-soap-message hth Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. From: dida...@hotmail.fr To: axis-user@ws.apache.org Subject: xmlns Date: Fri, 9 Oct 2009 14:37:15 + Hello, When i have in a wsdl: xmlns:ax23=http://vo.coaching.de/xsd; or xmlns:ax24=http://vo.coaching.de/xsd; ax23 or ax24 specify the version of axis2 ?? so axis2 1.3 and axis2 1.4 ??? Thank you David Achetez un nouveau PC et bénéficiez de Windows 7 dès sa sortie ! En savoir plus Gratuit : Hotmail plus rapide avec Internet Explorer 8 ! Cliquez ici ! _ Hotmail: Trusted email with powerful SPAM protection. http://clk.atdmt.com/GBL/go/177141665/direct/01/
RE: [Axis2] Pb with xs:element name?
Is that a POJO service or what? And what JDK are you using. From: Didav Didav [mailto:dida...@hotmail.fr] Sent: Friday, October 09, 2009 8:41 AM To: axis-user@ws.apache.org Subject: [Axis2] Pb with xs:element name? Hi, I deploy my web service with Axis2-1.3 and weblogic 10 and I have a question about parameter name in wsdl... Why are they specified param0 for the name of the tag xs:element? For example : xs:element minOccurs=0 name=param0 nillable=true type=ns1:DonneesWS/ instead of xs:element minOccurs=0 name=donnees nillable=true type=ns1:DonneesWS/ Thanks a lot, David Gratuit : Hotmail plus rapide avec Internet Explorer 8 ! Cliquez ici ! http://www.microsoft.com/france/windows/products/winfamily/ie/ie8/msn/d efault.aspx
Re : [Axis2] Pb with xs:element name?
Yes POJO Service. I m using JDK 1.5 De : David Hesson dhes...@rjlg.com À : axis-user@ws.apache.org Envoyé le : Ven 9 Octobre 2009, 17 h 41 min 43 s Objet : RE: [Axis2] Pb with xs:element name? Is that a POJO service or what? And what JDK are you using. From:Didav Didav [mailto:dida...@hotmail.fr] Sent: Friday, October 09, 2009 8:41 AM To: axis-user@ws.apache.org Subject: [Axis2] Pb with xs:element name? Hi, I deploy my web service with Axis2-1.3 and weblogic 10 and I have a question about parameter name in wsdl... Why are they specified param0 for the name of the tag xs:element? For example : xs:element minOccurs=0 name=param0 nillable=true type=ns1:DonneesWS/ instead of xs:element minOccurs=0 name=donnees nillable=true type=ns1:DonneesWS/ Thanks a lot, David Gratuit : Hotmail plus rapide avec Internet Explorer 8 ! Cliquez ici !
RE: HTTP Works, but Axis Fails
I forgot to attach the test program (now attached).
-Original Message-
From: CREECH,MIKE (Non-A-Labs,ex1)
Sent: Friday, October 09, 2009 7:18 AM
To: axis-user@ws.apache.org
Cc: CREECH,MIKE (Non-A-Labs,ex1)
Subject: HTTP Works, but Axis Fails
We have a Java application that can connect to a PHP-based server from
California (C) but not from India(I). Besides geographic location, the only
known difference between C and I is that I accesses the Internet via a proxy
server. We believe we have worked out the proxy issues in that I can reach and
receive correct data from the server via HTTP. However, an attempt to access
the same data using Axis/SOAP leads to a 'SocketException: connection Reset'
(output attached).
We have boiled this all down to a JUnit test (attached) that connects to the
same server via HTTP and Axis. This test completely works from C whereas only
the HTTP test works from I. Both tests obtain a list of organism names by going
to the webpage
http://137.120.14.24/wikipathways-test/wpi/webservice/webservice.php/listOrganisms.
Does anyone know the cause to this problem or have any suggestions on how to
debug it (we don't run the web service but can communicate with those that do)?
System Info
---
Server: wso2 wsf/php v.2.0
Clients: OS: Windows-XP, JVM: 1.6
Libraries Used to Run the Test
--
Junit.jar
Axis.jar
jaxrpc.jar
commons-logging-1.0.4.jar
commons-discovery-0.2jar
wsdl4j-1.5.1.jar
Failed Client (I) Output
PROXY SETTINGS BEFORE TEST:
http.proxyHost= 'ptproxy.persistent.co.in'
http.proxyHost= 'null'
http.proxyPort= '8080'
http.proxyUser= 'null'
http.proxyPassword= 'null'
socksProxyHost= 'null'
socksProxyPort= 'null'
java.net.socks.username= 'null'
java.net.socks.password= 'null'
testListOrganismsUsingHTTP organisms:
ns1:listOrganismsResponse
xmlns:ns1=http://www.wso2.org/php/xsd;ns1:organismsAnopheles
gambiae/ns1:organismsns1:organismsArabidopsis
thaliana/ns1:organismsns1:organismsBos
taurus/ns1:organismsns1:organismsBacillus
subtilis/ns1:organismsns1:organismsCaenorhabditis
elegans/ns1:organismsns1:organismsCanis
familiaris/ns1:organismsns1:organismsDanio
rerio/ns1:organismsns1:organismsDrosophila
melanogaster/ns1:organismsns1:organismsEscherichia
coli/ns1:organismsns1:organismsEquus
caballus/ns1:organismsns1:organismsGallus
gallus/ns1:organismsns1:organismsHomo
sapiens/ns1:organismsns1:organismsMus
musculus/ns1:organismsns1:organismsOryza
sativa/ns1:organismsns1:organismsPan
troglodytes/ns1:organismsns1:organismsRattus
norvegicus/ns1:organismsns1:organismsSaccharomyces
cerevisiae/ns1:organismsns1:organismsXenopus
tropicalis/ns1:organisms/ns1:listOrganismsResponse
testListOrganismsUsingHTTP test PASSED
PROXY SETTINGS BEFORE TEST:
http.proxyHost= 'ptproxy.persistent.co.in'
http.proxyHost= 'null'
http.proxyPort= '8080'
http.proxyUser= 'null'
http.proxyPassword= 'null'
socksProxyHost= 'null'
socksProxyPort= 'null'
java.net.socks.username= 'null'
java.net.socks.password= 'null'
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.net.SocketException: Connection reset
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.net.SocketException:
Connection reset
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at
org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:739)
at
org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
com.agilent.pwdemo.unittest.NetworkTests$TestStub.listOrganisms(NetworkTests.java:329)
at
com.agilent.pwdemo.unittest.NetworkTests.testListOrganismsUsingAxis(NetworkTests.java:167)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
simpleType vs. no type in XSD
I don't see any benefit to define SimpleType. Instead, ADB bean generates 2 classes for each SimpleType element that brings in unnecessary complicity. I would just define such basic restrictions in attribute as 'type' and 'maxLength' . Any thought about this? This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http://www.jpmorgan.com/pages/disclosures/email.
RE: xmlns
Thank you... I have an another question : Is it possible to set the namespace prefix in a wsdl? I have in my wsdl: xs:schema xmlns:ax24=http://language.webservice.releve.efluidpub.efluid.com/xsd; attributeFormDefault=qualified elementFormDefault=qualified targetNamespace=http://language.webservice.releve.efluidpub.efluid.com/xsd; but I want xs:schema xmlns:ax23=http://language.webservice.releve.efluidpub.efluid.com/xsd; attributeFormDefault=qualified elementFormDefault=qualified targetNamespace=http://language.webservice.releve.efluidpub.efluid.com/xsd; Thanks, David From: mgai...@hotmail.com To: axis-user@ws.apache.org Subject: RE: xmlns Date: Fri, 9 Oct 2009 11:19:52 -0400 to understand namespace assignments for your XML messages please reference http://wso2.org/library/articles/differentiating-between-soap-versions-looking-soap-message hth Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. From: dida...@hotmail.fr To: axis-user@ws.apache.org Subject: xmlns Date: Fri, 9 Oct 2009 14:37:15 + Hello, When i have in a wsdl: xmlns:ax23=http://vo.coaching.de/xsd; or xmlns:ax24=http://vo.coaching.de/xsd; ax23 or ax24 specify the version of axis2 ?? so axis2 1.3 and axis2 1.4 ??? Thank you David Achetez un nouveau PC et bénéficiez de Windows 7 dès sa sortie ! En savoir plus Gratuit : Hotmail plus rapide avec Internet Explorer 8 ! Cliquez ici ! Hotmail: Trusted email with powerful SPAM protection. Sign up now. _ A la recherche de bons plans pour une rentrée pas chère ? Bing ! Trouvez ! http://www.bing.com/search?q=bons+plans+rentr%C3%A9eform=MVDE6
AbstractMethodError in simple Rampart client
I have created a simple Axis2 echo service and client and am now trying to add Rampart security, starting with a simple UsernameToken and plain text Password. The secured service is running and it rejects client calls that are missing the required SOAP header. I set up the client to add the username and password, but I get an AbstractMethodError on the client side. Am I missing a configuration step or an overlooked dependency? Any help would be greatly appreciated!! I'm using Axis2 1.5 and Rampart 1.4. The rahas-1.4 and rampart-1.4 modules *do* get deployed from the client repo. Brief code snippet: ConfigurationContext ctx = //snip: Factory.create(repo) SecureServiceStub stub = new SecureServiceStub(ctx); // configure rampart security ServiceClient sc = stub._getServiceClient(); sc.engageModule(rampart); Options options = sc.getOptions(); options.setUserName(guest); options.setPassword(pass); stub.echo(hello); Exception in thread main java.lang.AbstractMethodError org.apache.axiom.om.impl.builder.StAXBuilder.processAttributes(StAXBuilder.java:230) org.apache.axiom.om.impl.builder.StAXOMBuilder.populateOMElement(StAXOMBuilder.java:396) org.apache.axiom.om.impl.builder.StAXOMBuilder.createOMElement(StAXOMBuilder.java:425) org.apache.axiom.om.impl.builder.StAXOMBuilder.createNextOMElement(StAXOMBuilder.java:282) org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:207) org.apache.axiom.om.impl.dom.DocumentImpl.getOMDocumentElement(DocumentImpl.java:443) org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:502) org.apache.rahas.Token.init(Token.java:141) org.apache.rampart.builder.BindingBuilder.handleSupportingTokens(BindingBuilder.java:388) ...
RE: Re : [Axis2] Pb with xs:element name?
Can I please see the signature of the POJO method? I'm not sure if it's related to having a complex object as the input argument, or maybe a property needs set in the Axis2 config. From: David [mailto:tida...@yahoo.fr] Sent: Friday, October 09, 2009 11:51 AM To: axis-user@ws.apache.org Subject: Re : [Axis2] Pb with xs:element name? Yes POJO Service. I m using JDK 1.5 De : David Hesson dhes...@rjlg.com À : axis-user@ws.apache.org Envoyé le : Ven 9 Octobre 2009, 17 h 41 min 43 s Objet : RE: [Axis2] Pb with xs:element name? Is that a POJO service or what? And what JDK are you using. From: Didav Didav [mailto:dida...@hotmail.fr] Sent: Friday, October 09, 2009 8:41 AM To: axis-user@ws.apache.org Subject: [Axis2] Pb with xs:element name? Hi, I deploy my web service with Axis2-1.3 and weblogic 10 and I have a question about parameter name in wsdl... Why are they specified param0 for the name of the tag xs:element? For example : xs:element minOccurs=0 name=param0 nillable=true type=ns1:DonneesWS/ instead of xs:element minOccurs=0 name=donnees nillable=true type=ns1:DonneesWS/ Thanks a lot, David Gratuit : Hotmail plus rapide avec Internet Explorer 8 ! Cliquez ici ! http://www.microsoft.com/france/windows/products/winfamily/ie/ie8/msn/default.aspx
Re: Axis 1 (1.4) - Simple proof of concept client not working - SAXParserException: Content is not allowed in prolog
I needed to add WEB-INF\server-config.wsdd and add my custom services in that
file. After that, I was able to see my custom service. I was able to create
custom client and successfully returned the results.
There is so much emphasis on deploying using JWS, Admin Console etc. and a
lot of emphasis on Tomcat. I wish there were more documentations on steps
needed to be taken for app servers other than Tomcat.
mule_user wrote:
I am new to Axis. I am using Axis 1 (not Axis2). I am trying to make a
simple app work. I created a web project called Axis1 which has two modles
namely Axis1(which only has META-INF\application.xml) and Axis1Web.
Axis1Web has the source code.
Axis1Web
|
---META-INF
|
application.xml
?xml version=1.0 encoding=UTF-8?
application id=Application_ID version=1.4
xmlns=http://java.sun.com/xml/ns/j2ee;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/application_1_4.xsd;
display-name
Axis1/display-name
module id=WebModule_1255025189235
web
web-uriAxis1Web.war/web-uri
context-rootAxis1Web/context-root
/web
/module
/application
Axis1Web
|
src
|
-org.ncc.server
| |
| Calculator
| |
| SimpleCalculator
|
-org.ncc.client (contains code geberated by WSDL2Java)
|
Axis1WebSoapBindingStub
|
Calculator
|
CalculatorService
|
CalculatorServiceLocator
|
CalcCleint (written by me, not generated by WSDl2Java)
Axis1Web project's WEB-INF\lib contains all the jar files from lib
directory of Axis 1 (version 1.4). That is why wsdl2Java generated classes
comiple successfully.
Axis1Web\WebContent\WEB-INF\web.xml
?xml version=1.0 encoding=UTF-8?
web-app id=WebApp_ID version=2.4
xmlns=http://java.sun.com/xml/ns/j2ee;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd;
display-name
Axis1Web/display-name
/web-app
/
Interface in server package:
/
package org.ncc.server;
public interface Calculator {
int add (int x, int y);
}
/
Implementation in server package:
package org.ncc.server;
public class SimpleCalculator {
public int add(int a, int b) {
return a + b;
}
}
/
I copied Calculator.class to C:\Axis. Then I ran the following to generate
Java2WSDL.
C:\Axisset
CLASSPATH=%AXIS_CLASSPATH%;C:\workspace-7.5\Axis1Web\WebContent\WEB-
INF\classes
C:\Axisjava -classpath %CLASSPATH% org.apache.axis.wsdl.Java2WSDL -o
calculator
.wsdl -n urn:org.ncc.calculator -l http://localhost:9081/Axis1Web
org.ncc.server
.Calculator
Generated C:\Axis\claculator.wsdl is:
/
?xml version=1.0 encoding=UTF-8?
wsdl:definitions targetNamespace=urn:org.ncc.calculator
xmlns:apachesoap=http://xml.apache.org/xml-soap;
xmlns:impl=urn:org.ncc.calculator xmlns:intf=urn:org.ncc.calculator
xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
!--WSDL created by Apache Axis version: 1.4
Built on Apr 22, 2006 (06:55:48 PDT)--
wsdl:message name=addResponse
wsdl:part name=addReturn type=xsd:int/
/wsdl:message
wsdl:message name=addRequest
wsdl:part name=in0 type=xsd:int/
wsdl:part name=in1 type=xsd:int/
/wsdl:message
wsdl:portType name=Calculator
wsdl:operation name=add parameterOrder=in0 in1
wsdl:input message=impl:addRequest name=addRequest/
wsdl:output message=impl:addResponse name=addResponse/
/wsdl:operation
/wsdl:portType
wsdl:binding name=Axis1WebSoapBinding type=impl:Calculator
wsdlsoap:binding style=rpc
transport=http://schemas.xmlsoap.org/soap/http/
wsdl:operation name=add
wsdlsoap:operation soapAction=/
wsdl:input name=addRequest
wsdlsoap:body
encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;
namespace=urn:org.ncc.calculator use=encoded/
/wsdl:input
wsdl:output name=addResponse
wsdlsoap:body
encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;
namespace=urn:org.ncc.calculator use=encoded/
/wsdl:output
/wsdl:operation
/wsdl:binding
wsdl:service
Re: [Axis2] AbstractMethodError in simple Rampart client
David Dearing wrote: I have created a simple Axis2 echo service and client and am now trying to add Rampart security, starting with a simple UsernameToken and plain text Password. The secured service is running and it rejects client calls that are missing the required SOAP header. I set up the client to add the username and password, but I get an AbstractMethodError on the client side. Am I missing a configuration step or an overlooked dependency? Any help would be greatly appreciated!! I'm using Axis2 1.5 and Rampart 1.4. The rahas-1.4 and rampart-1.4 modules *do* get deployed from the client repo. Brief code snippet: ConfigurationContext ctx = //snip: Factory.create(repo) SecureServiceStub stub = new SecureServiceStub(ctx); // configure rampart security ServiceClient sc = stub._getServiceClient(); sc.engageModule(rampart); Options options = sc.getOptions(); options.setUserName(guest); options.setPassword(pass); stub.echo(hello); Exception in thread main java.lang.AbstractMethodError org.apache.axiom.om.impl.builder.StAXBuilder.processAttributes(StAXBuilder.java:230) org.apache.axiom.om.impl.builder.StAXOMBuilder.populateOMElement(StAXOMBuilder.java:396) org.apache.axiom.om.impl.builder.StAXOMBuilder.createOMElement(StAXOMBuilder.java:425) org.apache.axiom.om.impl.builder.StAXOMBuilder.createNextOMElement(StAXOMBuilder.java:282) org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:207) org.apache.axiom.om.impl.dom.DocumentImpl.getOMDocumentElement(DocumentImpl.java:443) org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:502) org.apache.rahas.Token.init(Token.java:141) org.apache.rampart.builder.BindingBuilder.handleSupportingTokens(BindingBuilder.java:388) ... Some additional investigation led me to find the error being generated from a line in StAXBuilder that attempts to call OMAttribute.setAttributeType with a null type. The OMAttribute appears to be wsu:Id for the wsse:UsernameToken element. I think this type should be xsd:ID, but I'm not sure where/how to change this on the client.
