RE: [axis1] more stable version of axis
thanks for all, it help us a lot Michel Lequim -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cyrille Le Clerc Sent: Monday, June 19, 2006 1:41 PM To: axis-user@ws.apache.org Subject: Re: [axis1] more stable version of axis Hello Michel, I confirm you client side timeouts work as expected in Axis 1.4 . To set client side socket timeouts, you have to invoke "myStub.setTimeout(x)" (in millis). Note that you retrieve your stub calling MyServiceLocator.getMyBinding() and note that setTimeout(x) is implemented by (org.apache.axis.client.Stub). This stub.setTimeout(millis) is used to both set the socket.setSotimeout(x) and the socket.connect (endpoint, timeoutInMillis) The default sender (HTTPSender) implements the previously described configuration settings. The CommonsHTTPSender (based on Jakarta Commons HTTP Client) implements the previous confiiguration settings but you can also globally define timeouts as defined on the wiki : http://wiki.apache.org/ws/FrontPage/Axis/AxisCommonsHTTP . Sample : HelloWorldBindingStub binding = (HelloWorldBindingStub) new HelloWorldServiceLocator().gethelloWorldBinding(); // Time out after a minute binding.setTimeout(6); Hope this helps, Cyrille -- Cyrille Le Clerc [EMAIL PROTECTED] [EMAIL PROTECTED] +33 6.61.33.69.86 On 6/19/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > thanks, > > I think I will use the 1.4 then, > I need just to be sure that the time out configuration works for client, > could you please confirm ? > > Michel Lequim > > > > From: > [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > On Behalf Of Anne Thomas Manes > Sent: Friday, June 16, 2006 7:11 PM > To: axis-user@ws.apache.org > Subject: Re: [axis1] more stable version of axis > > > The formal release came out quite recently, but the build was produced quite > a while ago, and it's the one used in Geronimo. > > > On 6/16/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > > > > > yes but axis 1.4 was released very recently, in april 2006, it is not too > risky to use it in production ? > > > > > > Michel Lequim > > > > > > > From: > [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > ] On Behalf Of Anne Thomas Manes > > Sent: Friday, June 16, 2006 2:22 AM > > To: axis-user@ws.apache.org > > Subject: Re: [axis1] more stable version of axis > > > > > > > > Axis 1.4 fixes a number of array bugs. I recommend it over 1.2. > > > > > > On 6/15/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > Dear axis users, > > > > > > we are to plan here to use axis in production but we are not sure about > the version we will use, I hope > > > someone can help us. We think axis 2 is not enough stable, too recent > release and some bugs are still found (by example > > > for the timeout configuration which is a feature we really need). We > then hesitate between axis 1.2 to 1.4, > > > axis 1.4 seems to be also very recent so we plan to use axis 1.3. > > > > > > Do you think it is a good choice ? > > > > > > thanks in advance > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] = = = = = = = = = = = = = = = = = = = = = = = = = Fortis Bank disclaimer : http://www.fortisbank.be/legal/disclaimer.htm Fortis Bank privacy policy : http://www.fortisbank.be/legal/privacy_policy.htm = = = = = = = = = = = = = = = = = = = = = = = = = - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [axis1] more stable version of axis
thanks, I think I will use the 1.4 then, I need just to be sure that the time out configuration works for client, could you please confirm ? Michel Lequim From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anne Thomas ManesSent: Friday, June 16, 2006 7:11 PMTo: axis-user@ws.apache.orgSubject: Re: [axis1] more stable version of axis The formal release came out quite recently, but the build was produced quite a while ago, and it's the one used in Geronimo. On 6/16/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: yes but axis 1.4 was released very recently, in april 2006, it is not too risky to use it in production ? Michel Lequim From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] ] On Behalf Of Anne Thomas ManesSent: Friday, June 16, 2006 2:22 AMTo: axis-user@ws.apache.orgSubject: Re: [axis1] more stable version of axis Axis 1.4 fixes a number of array bugs. I recommend it over 1.2. On 6/15/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: Dear axis users, we are to plan here to use axis in production but we are not sure about the version we will use, I hope someone can help us. We think axis 2 is not enough stable, too recent release and some bugs are still found (by example for the timeout configuration which is a feature we really need). We then hesitate between axis 1.2 to 1.4, axis 1.4 seems to be also very recent so we plan to use axis 1.3. Do you think it is a good choice ? thanks in advance -To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] = = = = = = = = = = = = = = = = = = = = = = = = = Fortis Bank disclaimer : http://www.fortisbank.be/legal/disclaimer.htm Fortis Bank privacy policy : http://www.fortisbank.be/legal/privacy_policy.htm = = = = = = = = = = = = = = = = = = = = = = = = = - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
why the axis website has only documentation for axis 1.2 ?
Hi ! why the official documentation is about axis 1.2 and the last release is 1.4 ? Is it because the axis 1.2 version is considered by developpers as the only one stable ? Where can I then find the documentation for the 1.4 version ? kind regards, Michel Michel Lequim -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Seak, Teng-Fong Sent: Friday, June 16, 2006 2:47 PM To: axis-user@ws.apache.org Subject: Re: How to make Axis use Tomcat's compiler? Eclipse's compiler, called JDT. Quoted from Tomcat's release notes: In addition, Tomcat 5.5 uses the Eclipse JDT Java compiler for compiling JSP pages. This means you no longer need to have the complete Java Development Kit (JDK) to run Tomcat, but a Java Runtime Environment (JRE) is sufficient. The Eclipse JDT Java compiler is bundled with the binary Tomcat distributions. .. cf "Dependency Changes" in: http://apache.crihan.fr/dist/tomcat/tomcat-5/v5.5.17/RELEASE-NOTES STF Dhakshinamoorthy, Hariharasudhan wrote: > what is Tomcat Compiler ? > > -Original Message- > From: Seak, Teng-Fong [mailto:[EMAIL PROTECTED] > Sent: Friday, June 16, 2006 2:11 PM > To: axis-user@ws.apache.org > Subject: Re: How to make Axis use Tomcat's compiler? > > > Still no answer? Are Axis's developers reading this mailing-list? > > Seak, Teng-Fong wrote: > >> Hello everybody, >> >> I don't know if this post would be considered off-topic; I've posted >> it to Tomcat several days ago but without any answer. >> >> I'm trying to use Web service in Tomcat, ie with Axis. I've read >> and followed the install guide and user guide: >> http://ws.apache.org/axis/java/install.html >> http://ws.apache.org/axis/java/user-guide.html >> >> Everything's OK, except one thing: >> Axis needs tools.jar to compile JWS on the fly. For the moment, I've >> got the tools.jar from a JDK 1.5 and put it in the library folder to >> make Axis compile. So, anyone knows if it's possible to make Axis use >> Tomcat's compiler (ie the one used in Eclipse, if I'm not mistaken) >> and how? >> >> By the way, the docs for Axis are too old; they're still using >> Tomcat 4 as reference! Furthermore, the docs just say Axis needs >> Java2, but no clear mention if JRE is enough. I mean, Tomcat only >> needs JRE whereas tools.jar could only be found in JDK. So, JRE or JDK? >> >> TIA >> >> STF >> - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] = = = = = = = = = = = = = = = = = = = = = = = = = Fortis Bank disclaimer : http://www.fortisbank.be/legal/disclaimer.htm Fortis Bank privacy policy : http://www.fortisbank.be/legal/privacy_policy.htm = = = = = = = = = = = = = = = = = = = = = = = = = - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [AXIS2] J2EE Support
Hi, axis 1 & 2 work in a J2EE environment Michel Lequim -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Lindley Sent: Friday, June 16, 2006 11:54 AM To: axis-user@ws.apache.org Subject: [AXIS2] J2EE Support I was just wondering, why neither AXIS, nor AXIS2 do support J2EE - is this correct? JBoss e.g. has this feature. Is this information correct? thanks, -- --- Mag. Andrew Lindley ARC Seibersdorf research GmbH Research Studios Austria Studio Digital Memory Engineering Thurngasse 8/20, A-1090 Wien T. +43.1.585-0537 F. +43.1.585-3741 <[EMAIL PROTECTED]> www.arcs.ac.at - dme.researchstudio.at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] = = = = = = = = = = = = = = = = = = = = = = = = = Fortis Bank disclaimer : http://www.fortisbank.be/legal/disclaimer.htm Fortis Bank privacy policy : http://www.fortisbank.be/legal/privacy_policy.htm = = = = = = = = = = = = = = = = = = = = = = = = = - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [AXis2] best version to be on production
sorry, I made a mistake in the last mail, here is what I wanted to say: Hi, we have the same problem of choosing a version of axis. the timeout setting that does not work is one of our main reason to not choose axis 2, the second is that we fear that more bugs will be discovered in the future because it is rather new. have you find a way to make the time out working ? Michel Lequim Michel Lequim -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lequim Michel Sent: Friday, June 16, 2006 9:26 AM To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: RE: [AXis2] best version to be on production Hi, we have the same problem of choosing a version of axis for axis 2. the timeout setting that does not work is one of our main reason to not choose axis 2, the second is that we fear that more bugs will be discovered in the future because it is rather new. have you find a way to make the time out working ? Michel Lequim -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Ashton Sent: Friday, June 16, 2006 1:46 AM To: axis-user@ws.apache.org Subject: Re: [AXis2] best version to be on production Nicolas Guaneme wrote: > kavithaa Rajavenkateshwaran wrote: > >> Hi, >> >> We are thinking about using axis in production. I tried with the >> latest release in axis1.x and axis2. >> Axis1.x seems to be much more stable. But not sure.Can some suggest >> me which version to go with. >> >> Thanks, >> Kavithaa >> > Hi, I prefer Axis 1 beacause you can find more doc and examples for > develop and support... I work with Axis 1 in production easy and > stable. Our experience late last year was that Axis 1.3 performance was unacceptable under load (too much CPU and memory usage). We switched to Axis 2 (0.92) which performed a lot better for us (and 1.0 performs better again). The lack of the ability to set the client timeout in the current 1.0 release is also causing us pain. Cheers, Paul. -- Paul Ashton iCom Project Leader Tourplan Christchurch, New Zealand Phone: +64 3 3669669 Fax: +64 3 3791091 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] = = = = = = = = = = = = = = = = = = = = = = = = = Fortis Bank disclaimer : http://www.fortisbank.be/legal/disclaimer.htm Fortis Bank privacy policy : http://www.fortisbank.be/legal/privacy_policy.htm = = = = = = = = = = = = = = = = = = = = = = = = = - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] = = = = = = = = = = = = = = = = = = = = = = = = = Fortis Bank disclaimer : http://www.fortisbank.be/legal/disclaimer.htm Fortis Bank privacy policy : http://www.fortisbank.be/legal/privacy_policy.htm = = = = = = = = = = = = = = = = = = = = = = = = = - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [axis1] more stable version of axis
yes but axis 1.4 was released very recently, in april 2006, it is not too risky to use it in production ? Michel Lequim From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anne Thomas ManesSent: Friday, June 16, 2006 2:22 AMTo: axis-user@ws.apache.orgSubject: Re: [axis1] more stable version of axis Axis 1.4 fixes a number of array bugs. I recommend it over 1.2. On 6/15/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: Dear axis users, we are to plan here to use axis in production but we are not sure about the version we will use, I hope someone can help us. We think axis 2 is not enough stable, too recent release and some bugs are still found (by example for the timeout configuration which is a feature we really need). We then hesitate between axis 1.2 to 1.4, axis 1.4 seems to be also very recent so we plan to use axis 1.3. Do you think it is a good choice ? thanks in advance -To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] = = = = = = = = = = = = = = = = = = = = = = = = = Fortis Bank disclaimer : http://www.fortisbank.be/legal/disclaimer.htm Fortis Bank privacy policy : http://www.fortisbank.be/legal/privacy_policy.htm = = = = = = = = = = = = = = = = = = = = = = = = = - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [AXis2] best version to be on production
Hi, we have the same problem of choosing a version of axis for axis 2. the timeout setting that does not work is one of our main reason to not choose axis 2, the second is that we fear that more bugs will be discovered in the future because it is rather new. have you find a way to make the time out working ? Michel Lequim -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Ashton Sent: Friday, June 16, 2006 1:46 AM To: axis-user@ws.apache.org Subject: Re: [AXis2] best version to be on production Nicolas Guaneme wrote: > kavithaa Rajavenkateshwaran wrote: > >> Hi, >> >> We are thinking about using axis in production. I tried with the >> latest release in axis1.x and axis2. >> Axis1.x seems to be much more stable. But not sure.Can some suggest >> me which version to go with. >> >> Thanks, >> Kavithaa >> > Hi, I prefer Axis 1 beacause you can find more doc and examples for > develop and support... I work with Axis 1 in production easy and > stable. Our experience late last year was that Axis 1.3 performance was unacceptable under load (too much CPU and memory usage). We switched to Axis 2 (0.92) which performed a lot better for us (and 1.0 performs better again). The lack of the ability to set the client timeout in the current 1.0 release is also causing us pain. Cheers, Paul. -- Paul Ashton iCom Project Leader Tourplan Christchurch, New Zealand Phone: +64 3 3669669 Fax: +64 3 3791091 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] = = = = = = = = = = = = = = = = = = = = = = = = = Fortis Bank disclaimer : http://www.fortisbank.be/legal/disclaimer.htm Fortis Bank privacy policy : http://www.fortisbank.be/legal/privacy_policy.htm = = = = = = = = = = = = = = = = = = = = = = = = = - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[axis1] more stable version of axis
Title: [axis1] more stable version of axis Dear axis users, we are to plan here to use axis in production but we are not sure about the version we will use, I hope someone can help us. We think axis 2 is not enough stable, too recent release and some bugs are still found (by example for the timeout configuration which is a feature we really need). We then hesitate between axis 1.2 to 1.4, axis 1.4 seems to be also very recent so we plan to use axis 1.3. Do you think it is a good choice ? thanks in advance = = = = = = = = = = = = = = = = = = = = = = = = = Fortis Bank disclaimer : http://www.fortisbank.be/legal/disclaimer.htm Fortis Bank privacy policy : http://www.fortisbank.be/legal/privacy_policy.htm = = = = = = = = = = = = = = = = = = = = = = = = = - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [axis 2][sandesha] The responses concatenate with echostring example
Title: [axis 2][sandesha] The responses concatenate with echostring example I forgot to precise that I get the following warning message when running the JSP : [29/05/06 13:46:07:810 CEST] 65a8aac1 TraceNLS u No message text associated with key WARNING:.Cannot.set.header..Response.already.committed. in bundle com.ibm.ejs.resources.seriousMessages [29/05/06 13:46:07:810 CEST] 65a8aac1 SRTServletRes W WARNING: Cannot set header. Response already committed. I don't know if this warning is important for my problem, can please someone help me ? kinds regards, Michel From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lequim MichelSent: Monday, May 29, 2006 10:22 AMTo: axis-user@ws.apache.orgSubject: [axis 2][sandesha] The responses concatenate with echostring example Hi everybody ! I am a beginner with axis 2.0, I have tried to run the example echostring with WS-ReliableMessaging (module sandesha) in a JSP page but I got some problems,... When I run the example I got as response the following string : "echo1echo2echo3". But if I run it again, even from another computer, I got the response "echo1echo2echo3echo1echo2echo3" ! Is it normal ? What should I do to avoid this ? I have added "serviceClient.finalizeInvoke();" at the end to release resources. Here is the code I am using : DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <%@ page language="java" contentType="text/html; charset=ISO-8859-1" pageEncoding="ISO-8859-1"%> <%@ page import="java.io.File"%> <%@ page import="javax.xml.namespace.QName"%> <%@ page import="org.apache.axiom.om.OMAbstractFactory"%> <%@ page import="org.apache.axiom.om.OMElement"%> <%@ page import="org.apache.axiom.om.OMFactory"%> <%@ page import="org.apache.axiom.om.OMNamespace"%> <%@ page import="org.apache.axiom.soap.SOAPBody"%> <%@ page import="org.apache.axis2.Constants"%> <%@ page import="org.apache.axis2.addressing.EndpointReference"%> <%@ page import="org.apache.axis2.client.Options"%> <%@ page import="org.apache.axis2.client.ServiceClient"%> <%@ page import="org.apache.axis2.client.async.AsyncResult"%> <%@ page import="org.apache.axis2.client.async.Callback"%> <%@ page import="org.apache.axis2.context.ConfigurationContext"%> <%@ page import="org.apache.axis2.context.ConfigurationContextFactory"%> <%@ page import="org.apache.sandesha2.client.SandeshaClientConstants"%>index.jspTITLE> HEAD> Test Technique Web Servicesh1>
AXIS 2.0 Web Service Reliable Messaging Clienth2>
Placez le contenu ici.P> <%! private final static String applicationNamespaceName = "http://tempuri.org/"; private final static String echoString = "echoString"; private final static String Text = "Text"; private final static String Sequence = "Sequence"; private final static String echoStringResponse = "echoStringResponse"; private final static String EchoStringReturn = "EchoStringReturn"; private static String toEPR = "http://127.0.0.1:9080/axis2/services/RMSampleService"; private static String CLIENT_REPO_PATH = "c:\\Winprog\\WorkspacesRSA\\WSRMClient"; %> <%! private static OMElement getEchoOMBlock(String text, String sequenceKey) { OMFactory fac = OMAbstractFactory.getOMFactory(); OMNamespace applicationNamespace = fac.createOMNamespace(applicationNamespaceName,"ns1"); OMElement echoStringElement = fac.createOMElement(echoString, applicationNamespace); OMElement textElem = fac.createOMElement(Text,applicationNamespace); OMElement sequenceElem = fac.createOMElement(Sequence,applicationNamespace); textElem.setText(text); sequenceElem.setText(sequenceKey); echoStringElement.addChild(textElem); echoStringElement.addChild(sequenceElem); return echoStringElement; } static class TestCallback extends Callback { String name = null; public TestCallback (String name) { this.name = name; } public void onComplete(AsyncResult result) { SOAPBody body = result.getResponseEnvelope().getBody(); OMElement echoStringResponseElem = body.getFirstChildWithName(new QName (applicationNamespaceName,echoStringResponse)); OMElement echoStringReturnElem = echoStringResponseElem.getFirstChildWithName(new QName (applicationNamespaceName,EchoStringReturn)); String resultStr = echoStringReturnElem.getText(); System.out.println("Callback '" + name + "' got result:" + resultStr); } public void onError (Exception e) { System.out.println("Error reported for
[axis 2][sandesha] The responses concatenate with echostring example
Title: [axis 2][sandesha] The responses concatenate with echostring example Hi everybody ! I am a beginner with axis 2.0, I have tried to run the example echostring with WS-ReliableMessaging (module sandesha) in a JSP page but I got some problems,... When I run the example I got as response the following string : "echo1echo2echo3". But if I run it again, even from another computer, I got the response "echo1echo2echo3echo1echo2echo3" ! Is it normal ? What should I do to avoid this ? I have added "serviceClient.finalizeInvoke();" at the end to release resources. Here is the code I am using : DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <%@ page language="java" contentType="text/html; charset=ISO-8859-1" pageEncoding="ISO-8859-1"%> <%@ page import="java.io.File"%> <%@ page import="javax.xml.namespace.QName"%> <%@ page import="org.apache.axiom.om.OMAbstractFactory"%> <%@ page import="org.apache.axiom.om.OMElement"%> <%@ page import="org.apache.axiom.om.OMFactory"%> <%@ page import="org.apache.axiom.om.OMNamespace"%> <%@ page import="org.apache.axiom.soap.SOAPBody"%> <%@ page import="org.apache.axis2.Constants"%> <%@ page import="org.apache.axis2.addressing.EndpointReference"%> <%@ page import="org.apache.axis2.client.Options"%> <%@ page import="org.apache.axis2.client.ServiceClient"%> <%@ page import="org.apache.axis2.client.async.AsyncResult"%> <%@ page import="org.apache.axis2.client.async.Callback"%> <%@ page import="org.apache.axis2.context.ConfigurationContext"%> <%@ page import="org.apache.axis2.context.ConfigurationContextFactory"%> <%@ page import="org.apache.sandesha2.client.SandeshaClientConstants"%>index.jspTITLE> HEAD> Test Technique Web Servicesh1>
AXIS 2.0 Web Service Reliable Messaging Clienth2>
Placez le contenu ici.P> <%! private final static String applicationNamespaceName = "http://tempuri.org/"; private final static String echoString = "echoString"; private final static String Text = "Text"; private final static String Sequence = "Sequence"; private final static String echoStringResponse = "echoStringResponse"; private final static String EchoStringReturn = "EchoStringReturn"; private static String toEPR = "http://127.0.0.1:9080/axis2/services/RMSampleService"; private static String CLIENT_REPO_PATH = "c:\\Winprog\\WorkspacesRSA\\WSRMClient"; %> <%! private static OMElement getEchoOMBlock(String text, String sequenceKey) { OMFactory fac = OMAbstractFactory.getOMFactory(); OMNamespace applicationNamespace = fac.createOMNamespace(applicationNamespaceName,"ns1"); OMElement echoStringElement = fac.createOMElement(echoString, applicationNamespace); OMElement textElem = fac.createOMElement(Text,applicationNamespace); OMElement sequenceElem = fac.createOMElement(Sequence,applicationNamespace); textElem.setText(text); sequenceElem.setText(sequenceKey); echoStringElement.addChild(textElem); echoStringElement.addChild(sequenceElem); return echoStringElement; } static class TestCallback extends Callback { String name = null; public TestCallback (String name) { this.name = name; } public void onComplete(AsyncResult result) { SOAPBody body = result.getResponseEnvelope().getBody(); OMElement echoStringResponseElem = body.getFirstChildWithName(new QName (applicationNamespaceName,echoStringResponse)); OMElement echoStringReturnElem = echoStringResponseElem.getFirstChildWithName(new QName (applicationNamespaceName,EchoStringReturn)); String resultStr = echoStringReturnElem.getText(); System.out.println("Callback '" + name + "' got result:" + resultStr); } public void onError (Exception e) { System.out.println("Error reported for test call back"); e.printStackTrace(); } } %> <% String axis2_xml = CLIENT_REPO_PATH + File.separator +"client_axis2.xml"; try{ System.out.println("-- Creation of context"); ConfigurationContext configContext = org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(CLIENT_REPO_PATH,axis2_xml); System.out.println("-- Service client"); ServiceClient serviceClient = new ServiceClient (configContext,null); System.out.println("Options"); Options clientOptions = new Options (); System.out.println("-- YOP
problem installing sample one with IBM Websphere Application Server 5.1 and IBM Rational Software Architect
Title: problem installing sample one with IBM Websphere Application Server 5.1 and IBM Rational Software Architect Dear, I have tried to work with axis 2.0 in a WebSphere environment and I get some trouble. Could you please help me to find what's happening ? Here is my problem: I have tried to install axis 2 in a servlet contained like explained in the installation guide. I use Rational Software Architect to deploy on a test WebSphere application Server 5.1. Like usual I have imported the war file and encapsulated in an ear, then I have published it to the WAS 5.1. Then I have typed the url to see if all is working, in the validate screen all is correct except this: >Examining Version Service >There was a problem of examine Version service , may be the service not available or some thing has gone wrong. >But this does not mean system does not working ! Try to upload a some other service >and check to see whether it is working. I have also tried to test the version webservice but I got: >Available services >Faulty Services >C:\Winprog\IBM\Rational\SDP\6.0\runtimes\base_v51\installedApps\localhost\axis2EAR.ear\axis2.war\WEB-INF\services\version.aar and when clicking I got: Error: java.lang.NoSuchMethodError: javax.xml.namespace.QName: method (Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)V not found at org.apache.ws.java2wsdl.utils.TypeTable.populateSimpleTypes(TypeTable.java:38) at org.apache.ws.java2wsdl.utils.TypeTable.(TypeTable.java:33) at org.apache.ws.java2wsdl.SchemaGenerator.(SchemaGenerator.java:48) at org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:209) at org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:149) at org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:76) at org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:118) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:620) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:195) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:207) at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:155) at org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:91) at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:142) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:42) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:213) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:182) at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doInit(StrictServletInstance.java:82) at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._init(StrictLifecycleServlet.java:147) at com.ibm.ws.webcontainer.servlet.PreInitializedServletState.init(StrictLifecycleServlet.java:270) at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.init(StrictLifecycleServlet.java:113) at com.ibm.ws.webcontainer.servlet.ServletInstance.init(ServletInstance.java:189) at javax.servlet.GenericServlet.init(GenericServlet.java:258) at com.ibm.ws.webcontainer.webapp.WebAppServletManager.addServlet(WebAppServletManager.java:876) at com.ibm.ws.webcontainer.webapp.WebAppServletManager.loadServlet(WebAppServletManager.java:224) at com.ibm.ws.webcontainer.webapp.WebAppServletManager.loadAutoLoadServlets(WebAppServletManager.java:542) at com.ibm.ws.webcontainer.webapp.WebApp.loadServletManager(WebApp.java:1279) at com.ibm.ws.webcontainer.webapp.WebApp.init(WebApp.java:283) at com.ibm.ws.webcontainer.srt.WebGroup.loadWebApp(WebGroup.java:392) at com.ibm.ws.webcontainer.srt.WebGroup.init(WebGroup.java:211) at com.ibm.ws.webcontainer.WebContainer.addWebApplication(WebContainer.java:1005) at com.ibm.ws.runtime.component.WebContainerImpl.install(WebContainerImpl.java:136) at com.ibm.ws.runtime.component.WebContainerImpl.start(WebContainerImpl.java:356) at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:505) at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:808) at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:354) at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:578) at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:299) at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:256) at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536) at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413) at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:152) at com.ibm.ws.runtime.component.ContainerImpl.startCompon