Re: Soap Stub generation using ADB in Axis2-1.3
You can use the -pn option to specify the portName that the code should be generated for. Or you can use the -ap option which will genarate code for all ports. Thanks, Keith. On 8/10/07, Shalab Goel <[EMAIL PROTECTED]> wrote: > > > In Axis2, the Soap stubs for SOAP 1.1 and Soap 1.2 were automatically > generated. In Axis 1.3, only soap 1.2 Stubs are generated by default. > Is there an argument that can be fed to wsdl2java to say I want Soap > 1.1compatible stubs? > > The following is my command line for generating stub class using ADB. > > %AXIS2_HOME%\bin\wsdl2java -uri MyWS.wsdl -d adb -p com.myws.client > > Is MTOM functionality for Axis2 1.3 tested with both Soap 1.1 and Soap > 1.2generated stubs? > > The .NET service, against which I am writing an Axis client, generates a > Soap 1.1 response. And it clashes if I try to use Soap1.2 Stub. Is there > an Axis client configuration setting (like CUSTOM_SESSION_ID setting for > sessions) to overcome this issue? > > Thanks > Shalab > > > -Original Message- > From: Davanum Srinivas [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 09, 2007 6:11 PM > To: axis-user@ws.apache.org; [EMAIL PROTECTED] > Subject: Re: Is this regression for MTOM functionality in Axis2 1.3 > > Shalab, > > Not a known issue, please log a bug with some way for us to recreate the > issue. > > thanks, > dims > > On 8/9/07, Shalab Goel <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Hello, > > > > > > > > I have a .NET service for which I am writing an Axis2 client. One of the > > operations streams MTOM content to the client. > > > > This works with Axis2 -1.2 but does not work with RC candidate build > > location for Axis 2-1.3 referenced in Deepal's message from two days > ago? > > > > > > > > Wondering if this is a regression, and is it a known issue? Appreciate > your > > response. > > > > > > > > Thanks > > > > Shalab Goel > > > > > > > > > > > > > > > -- > Davanum Srinivas :: http://davanum.wordpress.com > > - > 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] > > -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/
Re: [axis2] rest question
This is not the case now. text/xml contentType is used for SOAP 1.1 request, the way we figure out whether a request is REST is based on the contentType. Obviously If the HTTPMethod is PUT, GET or DELETE then this is treated as REST automatically. From 1.2 onwards we hace the notion of messageBuilders and Message Formatters who are called upon to build request messages and to format response messages (This mapping is in the axis2 xml). So if the contentType is text/xml then the SOAP builder will take control. If the content Type is application/xml then the ApplicationXMLBuilder (RESP POST style) will take over. The GET is processed by XFormURLEncodedBuilder and so on. These mappings can be changed in your axis2.xml. Thanks, Keith. On 8/11/07, Mark Thompson <[EMAIL PROTECTED]> wrote: > > The axis2/1_2/rest.ws.html documentation indicates that if the content > type is text/xml and the SOAPAction Header is missing that the message > is treated as a restful message. > > If that is the case should the AxisServlet code be changed to check if > the request.getHeader(HTTPConstants.HEADER_SOAP_ACTION) value is not > empty in addition to checking if !isRESTRequest(contentTYpe) near the > top of the doPost(...) method? > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/
Re: [Axis2][VOTE]Axis2 1.3 release artifacts (#take3)
+ 1 Thanks, Keith. On 8/10/07, Deepal jayasinghe <[EMAIL PROTECTED]> wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi all, > > I have uploaded Axis2 1.3 (take3) into my Apache home location [1] > again . As a result of we found a few issues in 1.3 take2 I had to > upload the artifacts again and call for a new vote. I will keep open > the vote for 72 hrs from now and will do the Axis2 1.3 release on > Monday 13th Aug 2007. > > You can find both IntelliJ idea and Eclipse plugin artifacts in the > tools folder [2] > > Please try to cover the following areas when testing. > - - Code generation > - - Sessions > - - Web application > - - In different application servers > - - Both JDK 1.5 and JDK 1.4 > - - Java2WSDL > - - POJOs > - - And whatever the JIRA we have marked as fixed. > > You can find maven2 repository under my home directory as well [3]. I > have host the web site for 1.3 in [4] please have a look at that as well > > I will do the final release on Friday (10th Aug 2007), here is my +1 > for the release date as well as for release artifacts. > > > [1] : http://people.apache.org/~deepal/axis2/1.3-take3/ > [2] : http://www-lk.wso2.com/~deepal/1.3-tools/ > [3] : http://people.apache.org/~deepal/axis2/1.3-take3/m2-repo/ > [4] : http://www-lk.wso2.com/~deepal/axis2/ > > > P.S : Please note that I need to have two more PMC vote to go ahead > with the release, so please give us the support by voting for the release. > > > Thanks > Deepal > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.2 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFGvFhvjOGcXNDx0CARAh+4AJ49M1d86/v39C6Z0WnMcxsK5RgF3QCdGD8d > 43gXJ+tvuyHhc/nI1t1u1fw= > =sqos > -END PGP SIGNATURE- > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/
Re: Java2WSDL Method translation issue?
Glenn, Is your problem similar to this one? http://issues.apache.org/jira/browse/AXIS2-3017 thanks, dims On 8/10/07, Glenn Williams <[EMAIL PROTECTED]> wrote: > > > > > Hello, > > > > I have a Java method ( public double getFICO() ) who's body is upper case. > When converted in the WSDL it looks like this: fICO. When running a query > against Axis this method cannot be found. If I change the WSDL to this: > FICO, it works fine. Any ideas on what the problem might be? > > > > glw -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is this regression for MTOM functionality in Axis2 1.3
there is an option in wsdl2java to generate all stubs.. -ap Generate code for all ports On 8/10/07, Shalab Goel <[EMAIL PROTECTED]> wrote: > > Thanks Dims for your response. > > I tried take3 today. I am still seeing the same problem. > MTOM streaming works if using same client code and .NET webservice with Axis2 > 1.2, but does not work with Axis2-1.3. > > I am using ADB generated stubs in both cases. > > Noticed that in Axis1.3 only Soap12 stubs are generated. Is there an argument > to wsdl2java to generate Soap11 compliant ADB stubs? > > Will appreciate a response. > > Thanks > Shalab Goel > > -Original Message- > From: Davanum Srinivas [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 09, 2007 6:11 PM > To: axis-user@ws.apache.org; [EMAIL PROTECTED] > Subject: Re: Is this regression for MTOM functionality in Axis2 1.3 > > Shalab, > > Not a known issue, please log a bug with some way for us to recreate the > issue. > > thanks, > dims > > On 8/9/07, Shalab Goel <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Hello, > > > > > > > > I have a .NET service for which I am writing an Axis2 client. One of the > > operations streams MTOM content to the client. > > > > This works with Axis2 -1.2 but does not work with RC candidate build > > location for Axis 2-1.3 referenced in Deepal's message from two days ago? > > > > > > > > Wondering if this is a regression, and is it a known issue? Appreciate your > > response. > > > > > > > > Thanks > > > > Shalab Goel > > > > > > > > > > > > > > > -- > Davanum Srinivas :: http://davanum.wordpress.com > > - > 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] > > -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
XSD Schema default value behaviour
Hi, In my schema I have defined an element as What is the expected behaviour? A) If the application doesn't set any value then the webservice client should send the value 0 B) Webservice client won't be sending the value since its default value is 0, webservice should assume the value as 0 and should not expect it from the client. Which of the above statement is correct? BTW Axis2 doesn't handle default value and I have filed a JIRA for this. .NET client refuses to send default value, so I'm not sure who should handle the default value. Server or client? Thanks, Haneef -Original Message- From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 08, 2007 11:54 PM To: axis-user@ws.apache.org Subject: Re: Axis 2 https port address Hi Ali, Did you try with Axis2 1.3 take2 ? , please test with that and if the issue is there then please create a JIRA. Thanks Deepal Thanks Deepal > Hi, > > I have deployed a service in weblogic which listens at both http and > https addresses. My service is build using "useOriginalWsdl=true" > option. I'm giving the wsdl and asking Axis to just change the port > address. Also I haven't changed any options in axis.xml. Everything > is default. > > Here is my problem. I'm able to get wsdl using both http and https > addresses. But If I get the wsdl using https, then the port address > is "http". I believe it should be https. Am I missing something? Is > there any configuration for this in axis.xml? > > > Thanks, > Haneef > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > -- Thanks, Deepal "The highest tower is built one brick at a time" - 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]
axis2 - returning a hashmap
Im writing a java client that has to work against a perl (soap::lite) server.
Watching the output of 'tcpmonitor' shows that the data is being sent over
the wire but when I try to deserialize it Im getting a null.
http://xml.apache.org/xml-soap";
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance";
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/";
xmlns:xsd="http://www.w3.org/1999/XMLSchema";
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";>http://kopernik/auth";>1700avguard.exe524mdm.exe3816issch.exe1728mainserv.exe1648sched.exe1964DWRCS.EXE200... and so on.
QName opClientData =new QName("http://kopernik/auth";,
"getTaskInfo");
Object[] obArgs = new Object[] { };
Class[] returnTypes = new Class[] { HashMap.class };
Object[] response = serviceClient.invokeBlocking(opClientData,
obArgs, returnTypes);
response[0] == null when this returns. What am I doing wrong? Ive tried
setting the 'returnTypes' to Object[] with the same result.
--
View this message in context:
http://www.nabble.com/axis2---returning-a-hashmap-tf4251711.html#a12100654
Sent from the Axis - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Axis2 Spring Question
I currently have my web services running with axis2 (1.1) and spring running inside the aar. Recently I have discovered a need for servlets and/or web pages to get access to the objects that are in the spring context. If I move spring to the WEB-INF/lib, can I do this? The Axis2-Spring integration docs don't go into much detail here. I guess what I am wondering is whether or not the aar files are available at the time the Spring ContextLoaderListener starts up. If so, this should work. Thanks, John
RE: Overloaded methods
I think it depends of the wsdl style. Maybe this can be helpful: http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/ "Bhojraj, Santosh" <[EMAIL PROTECTED]> escribió: I was able to do it with Axis 1.1. Please see the attachment. - From: keith chapman [mailto:[EMAIL PROTECTED] Sent: Friday, August 10, 2007 12:13 AM To: axis-user@ws.apache.org Subject: Re: Overloaded methods I believe WSDL 1.1 does not support method overloading. Certainly WSDL 2.0 does not support it. That may b the issue. Thanks, Keith. On 8/9/07, Bhojraj, Santosh <[EMAIL PROTECTED]> wrote: Hi: I have a java interface with several service APIs defined,some of which are overloaded. How do I use Axis 2 to generate a WSDL for it ?I got an error when trying to run the Ant task. Please see theattachment. Thanx!! Santosh - Tounsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
RE: returning complex object with Axis2
Hi Feh, Here is how you return complex object with Axis2 (I'm showing this in WSDL 1.1 version). For Example: Say you have the following method. public Employee findEmployee (long empId); This method is returning an Employee object which is a complex object. The Employee object looks like this. Employee String empName; String empDesignation; intempAge String empDepartmentName In your WSDL you represent this as follows (I'm showing the WSDL in document/literal style and I'm showing only the schema definition part, not the message, portType, binding & service parts, I hope you can handle those). http://schemas.xmlsoap.org/wsdl/"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:tns="your namespace"> http://www.w3.org/2001/XMLSchema"; targetNamespace="your namespace"> ... message ... ... portType ... ... binding ... ... service ... Thanks Raghu -Original Message- From: feh [mailto:[EMAIL PROTECTED] Sent: Thursday, August 09, 2007 1:58 PM To: axis-user@ws.apache.org Subject: returning complex object with Axis2 Please bear with me...it's been a few months since I've worked with Axis 2, so my description of the situation may not be very clear... I've learned just enough about Axis 2 to write a soap service. It is a little bit unusual, in that the soap service was added to an existing web application, running under Tomcat. From what I remember, Axis 2 was designed to be its own container, so I had to find instructions somewhere on the net (where, I don't remember), which outlined how to incorporate Axis2 into an existing web app. Needless to say, this is probably not a "standard" installation. Anyway, all my services currently return primitive values (String, int, int[], etc). I'm wondering how to return complex objects, if it's possible. Is there documentation or a howto that covers this situation? In all the examples I've looked at so far, the service methods all return primitives. Thanks. -- View this message in context: http://www.nabble.com/returning-complex-object-with-Axis2-tf4245196.html #a12080657 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Is this regression for MTOM functionality in Axis2 1.3
Thanks Dims for your response. I tried take3 today. I am still seeing the same problem. MTOM streaming works if using same client code and .NET webservice with Axis2 1.2, but does not work with Axis2-1.3. I am using ADB generated stubs in both cases. Noticed that in Axis1.3 only Soap12 stubs are generated. Is there an argument to wsdl2java to generate Soap11 compliant ADB stubs? Will appreciate a response. Thanks Shalab Goel -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Thursday, August 09, 2007 6:11 PM To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: Re: Is this regression for MTOM functionality in Axis2 1.3 Shalab, Not a known issue, please log a bug with some way for us to recreate the issue. thanks, dims On 8/9/07, Shalab Goel <[EMAIL PROTECTED]> wrote: > > > > > Hello, > > > > I have a .NET service for which I am writing an Axis2 client. One of the > operations streams MTOM content to the client. > > This works with Axis2 -1.2 but does not work with RC candidate build > location for Axis 2-1.3 referenced in Deepal's message from two days ago? > > > > Wondering if this is a regression, and is it a known issue? Appreciate your > response. > > > > Thanks > > Shalab Goel > > > > > > -- Davanum Srinivas :: http://davanum.wordpress.com - 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]
RE: Improved Error Response for Bad Requests on ADB
This is a known bug in Axis2 1.2 but seems to be resolved in 1.3. Regards, Jorge Fernández Geoff Peart <[EMAIL PROTECTED]> escribió: Using the default Data Binding, a badly formed request gets meaningless runtime exceptions making it difficult for a client to develop and debug their application. Is there a way to either override this behaviour, or plug-in better error handling? I don't want to get in and edit the generated code, but even if the runtime errors held more information like why its failing would be a step in the right direction? Any help would be great. Thanks G - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
Which axis 1.3 jars to bundle
I am migrating my tomcat based axis1 service to axis2. The axis1 service used the minimal axis content in an exploded format. So we just had the axis.jar and axis-ant jars and any dependent jars in the classpath with the requisite servlet definitions in the web.xml file. With axis2, I see a whole lot of additional jars. Some of those I can easily discard - but others are questionable. What is the minimal set of jars to include for migrating the older service and adding MTOM functionality in the newer service after migration. Is there an axis dependencies list somewhere that will help me figure out the dependent jars for my usage?
[axis2] rest question
The axis2/1_2/rest.ws.html documentation indicates that if the content type is text/xml and the SOAPAction Header is missing that the message is treated as a restful message. If that is the case should the AxisServlet code be changed to check if the request.getHeader(HTTPConstants.HEADER_SOAP_ACTION) value is not empty in addition to checking if !isRESTRequest(contentTYpe) near the top of the doPost(...) method? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
OMElement Vs java.lang.Object for (xsd:anyType) - Axis 1.3 Vs Axis 2 code generation
Hi, In my webservices, I have a method which has a parameter defined as type="xsd:anyType" in the WSDL. In Axis 1.3, when I did WSDL2Java for my WSDL that parameter got converted to java.lang.Object. But in Axis2 1.2, when I did WSDL2Java for the same WSDL, that parameter got converted to org.apache.axiom.om.OMElement. My question is, if I need to pass a Java Object to my webservice method, how do I convert it to OMElement and pass it to the method from the client code & how do I convert OMElement back to java.lang.Object in my server code? Thanks Raghu
Java2WSDL Method translation issue?
Hello, I have a Java method ( public double getFICO() ) who's body is upper case. When converted in the WSDL it looks like this: fICO. When running a query against Axis this method cannot be found. If I change the WSDL to this: FICO, it works fine. Any ideas on what the problem might be? glw
Soap Stub generation using ADB in Axis2-1.3
In Axis2, the Soap stubs for SOAP 1.1 and Soap 1.2 were automatically generated. In Axis 1.3, only soap 1.2 Stubs are generated by default. Is there an argument that can be fed to wsdl2java to say I want Soap 1.1 compatible stubs? The following is my command line for generating stub class using ADB. %AXIS2_HOME%\bin\wsdl2java -uri MyWS.wsdl -d adb -p com.myws.client Is MTOM functionality for Axis2 1.3 tested with both Soap 1.1 and Soap 1.2 generated stubs? The .NET service, against which I am writing an Axis client, generates a Soap 1.1 response. And it clashes if I try to use Soap1.2 Stub. Is there an Axis client configuration setting (like CUSTOM_SESSION_ID setting for sessions) to overcome this issue? Thanks Shalab -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Thursday, August 09, 2007 6:11 PM To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: Re: Is this regression for MTOM functionality in Axis2 1.3 Shalab, Not a known issue, please log a bug with some way for us to recreate the issue. thanks, dims On 8/9/07, Shalab Goel <[EMAIL PROTECTED]> wrote: > > > > > Hello, > > > > I have a .NET service for which I am writing an Axis2 client. One of the > operations streams MTOM content to the client. > > This works with Axis2 -1.2 but does not work with RC candidate build > location for Axis 2-1.3 referenced in Deepal's message from two days ago? > > > > Wondering if this is a regression, and is it a known issue? Appreciate your > response. > > > > Thanks > > Shalab Goel > > > > > > -- Davanum Srinivas :: http://davanum.wordpress.com - 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]
RE: OutOfMemoryError - Large Attachments
What about chunking? Is that turned on by MTOM automatically? -jeff -Original Message- From: Charitha Kankanamge [mailto:[EMAIL PROTECTED] Sent: Friday, August 10, 2007 1:21 PM To: axis-user@ws.apache.org Subject: Re: OutOfMemoryError - Large Attachments Hi Greg, Axis2 mtom sample demonstrates transfering a file to a web service. I just checked it with the latest axis2-1.3(#take3) [1] and was able to transfer ~20MB file using the mtom sample. If you send large attachements using that sample, increase timeout value in client (serviceStub._getServiceClient().getOptions().setTimeOutInMilliSeconds(1 000);). [1]http://people.apache.org/~deepal/axis2/1.3-take3/ regards Charitha Skinner, Gregory W. wrote: > Hi All- > > I am getting an OutOfMemoryError when I try to send attachments larger > than 1M to my Axis2 service. Anything less works just fine. I looked > at the posts from a while ago regarding this issue, but have not been > able to succeed in getting it to work. > > I am using ADB for the service and have MTOM enable as well as file > caching. Does anyone have any idea how I can deal with this? > > Thanks, > Greg - 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]
Re: OutOfMemoryError - Large Attachments
Hi Greg, Axis2 mtom sample demonstrates transfering a file to a web service. I just checked it with the latest axis2-1.3(#take3) [1] and was able to transfer ~20MB file using the mtom sample. If you send large attachements using that sample, increase timeout value in client (serviceStub._getServiceClient().getOptions().setTimeOutInMilliSeconds(1000);). [1]http://people.apache.org/~deepal/axis2/1.3-take3/ regards Charitha Skinner, Gregory W. wrote: Hi All- I am getting an OutOfMemoryError when I try to send attachments larger than 1M to my Axis2 service. Anything less works just fine. I looked at the posts from a while ago regarding this issue, but have not been able to succeed in getting it to work. I am using ADB for the service and have MTOM enable as well as file caching. Does anyone have any idea how I can deal with this? Thanks, Greg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
WSDL2Java -generates multiple requests/response classes
Hi all, I am using Axis 2.1.2 and I am trying to generate the stub classes for both the service and client code with WSDL2Java. My problem is that it generates multiple request/response object such as HelloWorldReply, HelloWorldReply1 etc which I assume has to do with my WSDL. I get multiple request/reply classes when I use the Axis2 codegen plugin (Eclipse 3.3), if I run it from the command line I get three request objects and one reply object. The WSDL validates correctly with the WSDL editor in Eclipse 3.3, as far as I know it's pretty standard type of WSDL, we use it across our company. The commandline parameters looks like this: %AXIS2_HOME%\bin\WSDL2Java -uri HelloWorld.wsdl -p com.acme.ws -d adb -s -wv 1.1 -ss -sd -ssi I would appreciate if anyone has any ideas. I have also included the WSDL I am using below. TIA, Magnus http://schemas.xmlsoap.org/wsdl/"; xmlns:ns=" http://acme.com/ws/helloworld"; xmlns:s1=" http://schemas.xmlsoap.org/wsdl/soap/"; targetNamespace=" http://acme.com/ws/helloworld"; name="HelloWorldServiceDefinitions"> http://acme.com/ws/helloworld"; xmlns:xs="http://www.w3.org/2001/XMLSchema";> Stuff in request that needs to be set. Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). Identifies the name of the guy. Optional message sent in. Stuff in reply that client will see. Message from the web service.. http://schemas.xmlsoap.org/soap/http"/> http://localhost:7001/helloworld"/>
Re: [Axis2][VOTE]Axis2 1.3 release artifacts (#take3)
Here is my +1 for 1.3 release. All samples worked out of the box in Winxp/jdk15 environment. When running userguide samples, users may need to go through the associated xdocs (eg:- modules.html) to configure logging module. regards Charitha Deepal jayasinghe wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I have uploaded Axis2 1.3 (take3) into my Apache home location [1] again . As a result of we found a few issues in 1.3 take2 I had to upload the artifacts again and call for a new vote. I will keep open the vote for 72 hrs from now and will do the Axis2 1.3 release on Monday 13th Aug 2007. You can find both IntelliJ idea and Eclipse plugin artifacts in the tools folder [2] Please try to cover the following areas when testing. - - Code generation - - Sessions - - Web application - - In different application servers - - Both JDK 1.5 and JDK 1.4 - - Java2WSDL - - POJOs - - And whatever the JIRA we have marked as fixed. You can find maven2 repository under my home directory as well [3]. I have host the web site for 1.3 in [4] please have a look at that as well I will do the final release on Friday (10th Aug 2007), here is my +1 for the release date as well as for release artifacts. [1] : http://people.apache.org/~deepal/axis2/1.3-take3/ [2] : http://www-lk.wso2.com/~deepal/1.3-tools/ [3] : http://people.apache.org/~deepal/axis2/1.3-take3/m2-repo/ [4] : http://www-lk.wso2.com/~deepal/axis2/ P.S : Please note that I need to have two more PMC vote to go ahead with the release, so please give us the support by voting for the release. Thanks Deepal -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGvFhvjOGcXNDx0CARAh+4AJ49M1d86/v39C6Z0WnMcxsK5RgF3QCdGD8d 43gXJ+tvuyHhc/nI1t1u1fw= =sqos -END PGP SIGNATURE- - 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]
Re: Axis2 HttpCoreNIOSSLSender Chunked Transfer Encoding
Short term fix, You can configure Axis1 to work with chunked by using CommonsHTTPSender. thanks, dims On 8/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hi, > > I am trying to configure the new Axis2 HttpCoreNIOSSLSender TransportSender > with axis2-1.3-RC3: chunked transfer encoding is the default. > So far I haven't found a way to disable it, and axis1 on the other end can't > parse the messages. > > Is it possible to send messages without transfer encoding? > Or is there any other way to get the SimpleAxisServer to send messages with > SSL encryption? > > Thanks in advance, > > Vadim Chubarov > -- > Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! > Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Improved Error Response for Bad Requests on ADB
Using the default Data Binding, a badly formed request gets meaningless runtime exceptions making it difficult for a client to develop and debug their application. Is there a way to either override this behaviour, or plug-in better error handling? I don't want to get in and edit the generated code, but even if the runtime errors held more information like why its failing would be a step in the right direction? Any help would be great. Thanks G - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Axis2 HttpCoreNIOSSLSender Chunked Transfer Encoding
Hi, I am trying to configure the new Axis2 HttpCoreNIOSSLSender TransportSender with axis2-1.3-RC3: chunked transfer encoding is the default. So far I haven't found a way to disable it, and axis1 on the other end can't parse the messages. Is it possible to send messages without transfer encoding? Or is there any other way to get the SimpleAxisServer to send messages with SSL encryption? Thanks in advance, Vadim Chubarov -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
OutOfMemoryError - Large Attachments
Hi All- I am getting an OutOfMemoryError when I try to send attachments larger than 1M to my Axis2 service. Anything less works just fine. I looked at the posts from a while ago regarding this issue, but have not been able to succeed in getting it to work. I am using ADB for the service and have MTOM enable as well as file caching. Does anyone have any idea how I can deal with this? Thanks, Greg smime.p7s Description: S/MIME cryptographic signature
Re: [Axis2][VOTE]Axis2 1.3 release artifacts (#take3)
Ranjan, that web site is not the final destination. it's only for preview...it will work when we move the web site to the final location. thanks, dims On 8/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hi Deepal/Srinivas, > > If I click the 'version 1.2' link on the left navbar on the link > http://www-lk.wso2.com/~deepal/axis2/ > it results in 404 - page not found. Same with almost all the links apart > from version 1.3 > > Thanks, > Madhav > > -Original Message- > From: Glen Daniels [mailto:[EMAIL PROTECTED] > Sent: Friday, August 10, 2007 2:35 PM > To: axis-user@ws.apache.org > Cc: [EMAIL PROTECTED] > Subject: Re: [Axis2][VOTE]Axis2 1.3 release artifacts (#take3) > > +1... ship it! (and let's get to work on 1.4 :)) > > --Glen > > Davanum Srinivas wrote: > > +1 from me. > > > > thanks, > > dims > > > > On 8/10/07, Deepal jayasinghe <[EMAIL PROTECTED]> wrote: > >> -BEGIN PGP SIGNED MESSAGE- > >> Hash: SHA1 > >> > >> Hi all, > >> > >> I have uploaded Axis2 1.3 (take3) into my Apache home location [1] > >> again . As a result of we found a few issues in 1.3 take2 I had to > >> upload the artifacts again and call for a new vote. I will keep open > >> the vote for 72 hrs from now and will do the Axis2 1.3 release on > >> Monday 13th Aug 2007. > >> > >> You can find both IntelliJ idea and Eclipse plugin artifacts in the > >> tools folder [2] > >> > >> Please try to cover the following areas when testing. > >> - - Code generation > >> - - Sessions > >> - - Web application > >> - - In different application servers > >> - - Both JDK 1.5 and JDK 1.4 > >> - - Java2WSDL > >> - - POJOs > >> - - And whatever the JIRA we have marked as fixed. > >> > >> You can find maven2 repository under my home directory as well [3]. I > > >> have host the web site for 1.3 in [4] please have a look at that as > >> well > >> > >> I will do the final release on Friday (10th Aug 2007), here is my +1 > >> for the release date as well as for release artifacts. > >> > >> > >> [1] : http://people.apache.org/~deepal/axis2/1.3-take3/ > >> [2] : http://www-lk.wso2.com/~deepal/1.3-tools/ > >> [3] : http://people.apache.org/~deepal/axis2/1.3-take3/m2-repo/ > >> [4] : http://www-lk.wso2.com/~deepal/axis2/ > >> > >> > >> P.S : Please note that I need to have two more PMC vote to go ahead > >> with the release, so please give us the support by voting for the > release. > >> > >> > >> Thanks > >> Deepal > >> -BEGIN PGP SIGNATURE- > >> Version: GnuPG v1.4.2 (MingW32) > >> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > >> > >> iD8DBQFGvFhvjOGcXNDx0CARAh+4AJ49M1d86/v39C6Z0WnMcxsK5RgF3QCdGD8d > >> 43gXJ+tvuyHhc/nI1t1u1fw= > >> =sqos > >> -END PGP SIGNATURE- > >> > >> > >> - > >> 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] > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2][VOTE]Axis2 1.3 release artifacts (#take3)
Hi Deepal/Srinivas, If I click the 'version 1.2' link on the left navbar on the link http://www-lk.wso2.com/~deepal/axis2/ it results in 404 - page not found. Same with almost all the links apart from version 1.3 Thanks, Madhav -Original Message- From: Glen Daniels [mailto:[EMAIL PROTECTED] Sent: Friday, August 10, 2007 2:35 PM To: axis-user@ws.apache.org Cc: [EMAIL PROTECTED] Subject: Re: [Axis2][VOTE]Axis2 1.3 release artifacts (#take3) +1... ship it! (and let's get to work on 1.4 :)) --Glen Davanum Srinivas wrote: > +1 from me. > > thanks, > dims > > On 8/10/07, Deepal jayasinghe <[EMAIL PROTECTED]> wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Hi all, >> >> I have uploaded Axis2 1.3 (take3) into my Apache home location [1] >> again . As a result of we found a few issues in 1.3 take2 I had to >> upload the artifacts again and call for a new vote. I will keep open >> the vote for 72 hrs from now and will do the Axis2 1.3 release on >> Monday 13th Aug 2007. >> >> You can find both IntelliJ idea and Eclipse plugin artifacts in the >> tools folder [2] >> >> Please try to cover the following areas when testing. >> - - Code generation >> - - Sessions >> - - Web application >> - - In different application servers >> - - Both JDK 1.5 and JDK 1.4 >> - - Java2WSDL >> - - POJOs >> - - And whatever the JIRA we have marked as fixed. >> >> You can find maven2 repository under my home directory as well [3]. I >> have host the web site for 1.3 in [4] please have a look at that as >> well >> >> I will do the final release on Friday (10th Aug 2007), here is my +1 >> for the release date as well as for release artifacts. >> >> >> [1] : http://people.apache.org/~deepal/axis2/1.3-take3/ >> [2] : http://www-lk.wso2.com/~deepal/1.3-tools/ >> [3] : http://people.apache.org/~deepal/axis2/1.3-take3/m2-repo/ >> [4] : http://www-lk.wso2.com/~deepal/axis2/ >> >> >> P.S : Please note that I need to have two more PMC vote to go ahead >> with the release, so please give us the support by voting for the release. >> >> >> Thanks >> Deepal >> -BEGIN PGP SIGNATURE- >> Version: GnuPG v1.4.2 (MingW32) >> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org >> >> iD8DBQFGvFhvjOGcXNDx0CARAh+4AJ49M1d86/v39C6Z0WnMcxsK5RgF3QCdGD8d >> 43gXJ+tvuyHhc/nI1t1u1fw= >> =sqos >> -END PGP SIGNATURE- >> >> >> - >> 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2][VOTE]Axis2 1.3 release artifacts (#take3)
+1... ship it! (and let's get to work on 1.4 :)) --Glen Davanum Srinivas wrote: +1 from me. thanks, dims On 8/10/07, Deepal jayasinghe <[EMAIL PROTECTED]> wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I have uploaded Axis2 1.3 (take3) into my Apache home location [1] again . As a result of we found a few issues in 1.3 take2 I had to upload the artifacts again and call for a new vote. I will keep open the vote for 72 hrs from now and will do the Axis2 1.3 release on Monday 13th Aug 2007. You can find both IntelliJ idea and Eclipse plugin artifacts in the tools folder [2] Please try to cover the following areas when testing. - - Code generation - - Sessions - - Web application - - In different application servers - - Both JDK 1.5 and JDK 1.4 - - Java2WSDL - - POJOs - - And whatever the JIRA we have marked as fixed. You can find maven2 repository under my home directory as well [3]. I have host the web site for 1.3 in [4] please have a look at that as well I will do the final release on Friday (10th Aug 2007), here is my +1 for the release date as well as for release artifacts. [1] : http://people.apache.org/~deepal/axis2/1.3-take3/ [2] : http://www-lk.wso2.com/~deepal/1.3-tools/ [3] : http://people.apache.org/~deepal/axis2/1.3-take3/m2-repo/ [4] : http://www-lk.wso2.com/~deepal/axis2/ P.S : Please note that I need to have two more PMC vote to go ahead with the release, so please give us the support by voting for the release. Thanks Deepal -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGvFhvjOGcXNDx0CARAh+4AJ49M1d86/v39C6Z0WnMcxsK5RgF3QCdGD8d 43gXJ+tvuyHhc/nI1t1u1fw= =sqos -END PGP SIGNATURE- - 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]
RE: Overloaded methods
I was able to do it with Axis 1.1. Please see the attachment. From: keith chapman [mailto:[EMAIL PROTECTED] Sent: Friday, August 10, 2007 12:13 AM To: axis-user@ws.apache.org Subject: Re: Overloaded methods I believe WSDL 1.1 does not support method overloading. Certainly WSDL 2.0 does not support it. That may b the issue. Thanks, Keith. On 8/9/07, Bhojraj, Santosh <[EMAIL PROTECTED]> wrote: Hi: I have a java interface with several service APIs defined, some of which are overloaded. How do I use Axis 2 to generate a WSDL for it ? I got an error when trying to run the Ant task. Please see the attachment. Thanx!! Santosh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/ CommonBPMService.wsdl Description: CommonBPMService.wsdl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2][VOTE]Axis2 1.3 release artifacts (#take3)
+1 from me. thanks, dims On 8/10/07, Deepal jayasinghe <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi all, > > I have uploaded Axis2 1.3 (take3) into my Apache home location [1] > again . As a result of we found a few issues in 1.3 take2 I had to > upload the artifacts again and call for a new vote. I will keep open > the vote for 72 hrs from now and will do the Axis2 1.3 release on > Monday 13th Aug 2007. > > You can find both IntelliJ idea and Eclipse plugin artifacts in the > tools folder [2] > > Please try to cover the following areas when testing. > - - Code generation > - - Sessions > - - Web application > - - In different application servers > - - Both JDK 1.5 and JDK 1.4 > - - Java2WSDL > - - POJOs > - - And whatever the JIRA we have marked as fixed. > > You can find maven2 repository under my home directory as well [3]. I > have host the web site for 1.3 in [4] please have a look at that as well > > I will do the final release on Friday (10th Aug 2007), here is my +1 > for the release date as well as for release artifacts. > > > [1] : http://people.apache.org/~deepal/axis2/1.3-take3/ > [2] : http://www-lk.wso2.com/~deepal/1.3-tools/ > [3] : http://people.apache.org/~deepal/axis2/1.3-take3/m2-repo/ > [4] : http://www-lk.wso2.com/~deepal/axis2/ > > > P.S : Please note that I need to have two more PMC vote to go ahead > with the release, so please give us the support by voting for the release. > > > Thanks > Deepal > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.2 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFGvFhvjOGcXNDx0CARAh+4AJ49M1d86/v39C6Z0WnMcxsK5RgF3QCdGD8d > 43gXJ+tvuyHhc/nI1t1u1fw= > =sqos > -END PGP SIGNATURE- > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: {Disarmed} Re: soap over jms
Asankha, maybe I didn't get your point. I've added the needed libs and configured the embedded axis engine. What else shall I do? Michele On Fri, 2007-08-10 at 17:55 +0530, Asankha C. Perera wrote: > Michele > > ok, but it does not work :( > > > Yes.. not with a default SVN download or with the 1.0 release.. thats > why I said that: > > > > Yes, you could. But we haven't done it since it would increase the > > > size of the Synapse core download. > > > > asankha > > - > 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]
Re: {Disarmed} Re: soap over jms
Michele ok, but it does not work :( Yes.. not with a default SVN download or with the 1.0 release.. thats why I said that: Yes, you could. But we haven't done it since it would increase the size of the Synapse core download. asankha - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2][VOTE]Axis2 1.3 release artifacts (#take3)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I have uploaded Axis2 1.3 (take3) into my Apache home location [1] again . As a result of we found a few issues in 1.3 take2 I had to upload the artifacts again and call for a new vote. I will keep open the vote for 72 hrs from now and will do the Axis2 1.3 release on Monday 13th Aug 2007. You can find both IntelliJ idea and Eclipse plugin artifacts in the tools folder [2] Please try to cover the following areas when testing. - - Code generation - - Sessions - - Web application - - In different application servers - - Both JDK 1.5 and JDK 1.4 - - Java2WSDL - - POJOs - - And whatever the JIRA we have marked as fixed. You can find maven2 repository under my home directory as well [3]. I have host the web site for 1.3 in [4] please have a look at that as well I will do the final release on Friday (10th Aug 2007), here is my +1 for the release date as well as for release artifacts. [1] : http://people.apache.org/~deepal/axis2/1.3-take3/ [2] : http://www-lk.wso2.com/~deepal/1.3-tools/ [3] : http://people.apache.org/~deepal/axis2/1.3-take3/m2-repo/ [4] : http://www-lk.wso2.com/~deepal/axis2/ P.S : Please note that I need to have two more PMC vote to go ahead with the release, so please give us the support by voting for the release. Thanks Deepal -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGvFhvjOGcXNDx0CARAh+4AJ49M1d86/v39C6Z0WnMcxsK5RgF3QCdGD8d 43gXJ+tvuyHhc/nI1t1u1fw= =sqos -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: {Disarmed} Re: soap over jms
ok, but it does not work :( ./synapse.sh Starting Synapse/Java ... Using SYNAPSE_HOME:/home/nmm42/devel/apps/synapse-1.0 Using JAVA_HOME: /usr/java/jdk1.6.0_01 Using SYNAPSE_XML: -Dsynapse.xml=/home/nmm42/devel/apps/synapse-1.0/repository/conf/synapse.xml [SynapseServer] Using the Axis2 Repository /home/nmm42/devel/apps/synapse-1.0/repository [main] INFO SynapseModule - Initializing the Synapse configuration ... [main] INFO XMLConfigurationBuilder - Generating the Synapse configuration model by parsing the XML configuration [main] INFO SynapseConfigurationBuilder - Loaded Synapse configuration from : /home/nmm42/devel/apps/synapse-1.0/repository/conf/synapse.xml [main] INFO SynapseModule - Deploying the Synapse service.. [main] INFO SynapseModule - Initializing Sandesha 2... [main] INFO SynapseModule - Deploying Proxy services... [main] INFO SynapseModule - Synapse initialized successfully...! [main] INFO HttpCoreNIOSender - HTTPS Sender starting [main] INFO HttpCoreNIOSender - HTTP Sender starting [main] INFO HttpCoreNIOListener - HTTPS Listener starting on port : 8443 [SynapseServer] Starting transport https on port 8443 [main] INFO HttpCoreNIOListener - HTTP Listener starting on port : 8080 [SynapseServer] Starting transport http on port 8080 [main] ERROR JMSConnectionFactory - Error creating a JMS connection using the factory : QueueConnectionFactory javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:33) at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:280) at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:214) at org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:161) at org.apache.axis2.transport.jms.JMSConnectionFactory.listen(JMSConnectionFactory.java:308) at org.apache.axis2.transport.jms.JMSListener.start(JMSListener.java:300) at org.apache.axis2.engine.ListenerManager.addListener(ListenerManager.java:209) at org.apache.synapse.SynapseServer.main(SynapseServer.java:78) Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:519) at org.apache.activemq.transport.tcp.TcpTransport.connect(TcpTransport.java:335) at org.apache.activemq.transport.tcp.TcpTransport.doStart(TcpTransport.java:303) at org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:49) at org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:54) at org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:54) at org.apache.activemq.transport.WireFormatNegotiator.start(WireFormatNegotiator.java:66) at org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:54) at org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:54) at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:265) ... 6 more org.apache.axis2.transport.jms.AxisJMSException: Error creating a JMS connection using the factory : QueueConnectionFactory at org.apache.axis2.transport.jms.JMSConnectionFactory.handleException(JMSConnectionFactory.java:449) at org.apache.axis2.transport.jms.JMSConnectionFactory.listen(JMSConnectionFactory.java:310) at org.apache.axis2.transport.jms.JMSListener.start(JMSListener.java:300) at org.apache.axis2.engine.ListenerManager.addListener(ListenerManager.java:209) at org.apache.synapse.SynapseServer.main(SynapseServer.java:78) Caused by: javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:33) at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:280) at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:214) at org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:161) at org.apache.axis2.transport.jms.JMSConnectionFactory.listen(JMSConnectionFactory.java:308) ... 3 more Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl
Re: soap over jms
Michele Yes, you could. But we haven't done it since it would increase the size of the Synapse core download. asankha Michele Mazzucco wrote: Paul, thanks very much for your explanation. Just a quick question now. Can I embed ActiveMQ into Synapse? Thanks, Michele On Thu, 2007-08-09 at 18:35 +0100, Paul Fremantle wrote: Michele So the JMS transport supports SOAP/JMS, I believe this uses the standard (which was posted to axis-dev a while back by Glen Daniels), also XML/JMS, text and binary too. Synapse can switch between these. Basically it represents text and binary using special wrapper elements in the message "http://ws.apache.org/commons/ns/payload">. The samples show how to switch from a SOAP/HTTP to XML/JMS message. http://ws.apache.org/synapse/Synapse_Samples.html#Transport Paul On 8/9/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Ok, sorry Paul :). I simply meant if there's anything special I should know in order to use pure JMS inside my web service running on top of axis2/synapse, i.e. I guess I should use a TextMessage if I want to forward a message somewhere. What shall the it include?, just the SOAP body or the full envelope? Does it make sense to mix pure JMS and SOAP or it's better to split these tasks? If I split them, what about inter-leavings and other time related problems? Thanks, Michele On Thu, 2007-08-09 at 14:55 +0100, Paul Fremantle wrote: I didn't understand part two of question #1 Synapse can also do load-balancing based on Axis2 sessions with affinity, so each request goes to the server that initiated the session. Paul On 8/9/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Paul, thanks very much for the quick answer. However my idea about the proxy was a bit different, that is the proxy is used to address fault tolerance issues (at least at this stage), not for performance reasons. The rationale is that my web service is statefull and it looks to me that keeping the replica in sync would be very messy as the load increases (and beyond a certain point it would be infeasible). I've notice you didn't reply to the second part of question #1, so I guess I can do it the usual way (i.e. via MessageListener on the receiver side for async processing). Thanks, Michele On Thu, 2007-08-09 at 13:47 +0100, Paul Fremantle wrote: Michele You could use Apache Synapse (ws.apache.org/synapse). It can take XML/SOAP over HTTP requests and forward them to JMS. No coding required. It can also perform load-balancing. You could do round-robin DNS to Synapse to spread the load to a pair of Synapse servers or just have one. It can handle fairly high loads on its own. Paul On 8/9/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Hi all, I want use both SOAP over HTTP and SOAP over JMS (topic with multiple subscribers) but it's not very clear how to achieve my goal. I want to put a sort of proxy/load balancer in front of my distributed app to receive HTTP requests and forward them via JMS to a replicated web service. Here are my questions: 1 - How do I configure axis2 assuming it runs inside tomcat? I guess the transport is completely transparent to my app, but what about if I want to use JMS to accomplish other tasks? 2 - What do you suggest to use as proxy (I'll eventually need to modify it in order to detect and react to node crashes). Thanks, Michele - 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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SoapEnvelope toStringWithConsume()
Hi I have the following issue with SoapEnvelope toStringWithConsume() it returns the following incorrect string to me: http://schemas.xmlsoap.org/soap/envelope/";>http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2"; soap-env:mustUnderstand="1" />Server.ServiceServer Errorhttp://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0";>4004Validation ErrorValidation violation: TransactionID (MM7Schema) validation failed Which is incorrect as it should end with . Below is the original string for reference : http://schemas.xmlsoap.org/soap/envelope/";>http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2"; soap-env:mustUnderstand="1">Server.ServiceServer Errorhttp://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0";>4004Validation ErrorValidation violation: TransactionID (MM7Schema) validation failed I must say I am stumped any ideas ? Kind regards Stefan Kok. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: soap over jms
Paul, thanks very much for your explanation. Just a quick question now. Can I embed ActiveMQ into Synapse? Thanks, Michele On Thu, 2007-08-09 at 18:35 +0100, Paul Fremantle wrote: > Michele > > So the JMS transport supports SOAP/JMS, I believe this uses the > standard (which was posted to axis-dev a while back by Glen Daniels), > also XML/JMS, text and binary too. > > Synapse can switch between these. Basically it represents text and > binary using special wrapper elements in the message xmlns="http://ws.apache.org/commons/ns/payload";>. > > The samples show how to switch from a SOAP/HTTP to XML/JMS message. > http://ws.apache.org/synapse/Synapse_Samples.html#Transport > > Paul > > On 8/9/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote: > > Ok, sorry Paul :). > > I simply meant if there's anything special I should know in order to use > > pure JMS inside my web service running on top of axis2/synapse, i.e. I > > guess I should use a TextMessage if I want to forward a message > > somewhere. What shall the it include?, just the SOAP body or the full > > envelope? > > Does it make sense to mix pure JMS and SOAP or it's better to split > > these tasks? If I split them, what about inter-leavings and other time > > related problems? > > > > Thanks, > > Michele > > > > On Thu, 2007-08-09 at 14:55 +0100, Paul Fremantle wrote: > > > I didn't understand part two of question #1 > > > > > > Synapse can also do load-balancing based on Axis2 sessions with > > > affinity, so each request goes to the server that initiated the > > > session. > > > > > > Paul > > > > > > On 8/9/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote: > > > > Paul, > > > > > > > > thanks very much for the quick answer. However my idea about the proxy > > > > was a bit different, that is the proxy is used to address fault > > > > tolerance issues (at least at this stage), not for performance reasons. > > > > The rationale is that my web service is statefull and it looks to me > > > > that keeping the replica in sync would be very messy as the load > > > > increases (and beyond a certain point it would be infeasible). > > > > I've notice you didn't reply to the second part of question #1, so I > > > > guess I can do it the usual way (i.e. via MessageListener on the > > > > receiver side for async processing). > > > > > > > > Thanks, > > > > Michele > > > > > > > > > > > > On Thu, 2007-08-09 at 13:47 +0100, Paul Fremantle wrote: > > > > > Michele > > > > > > > > > > You could use Apache Synapse (ws.apache.org/synapse). It can take > > > > > XML/SOAP over HTTP requests and forward them to JMS. No coding > > > > > required. It can also perform load-balancing. You could do round-robin > > > > > DNS to Synapse to spread the load to a pair of Synapse servers or just > > > > > have one. It can handle fairly high loads on its own. > > > > > > > > > > Paul > > > > > > > > > > On 8/9/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote: > > > > > > Hi all, > > > > > > > > > > > > I want use both SOAP over HTTP and SOAP over JMS (topic with > > > > > > multiple > > > > > > subscribers) but it's not very clear how to achieve my goal. > > > > > > I want to put a sort of proxy/load balancer in front of my > > > > > > distributed > > > > > > app to receive HTTP requests and forward them via JMS to a > > > > > > replicated > > > > > > web service. > > > > > > Here are my questions: > > > > > > 1 - How do I configure axis2 assuming it runs inside tomcat? I > > > > > > guess the > > > > > > transport is completely transparent to my app, but what about if I > > > > > > want > > > > > > to use JMS to accomplish other tasks? > > > > > > 2 - What do you suggest to use as proxy (I'll eventually need to > > > > > > modify > > > > > > it in order to detect and react to node crashes). > > > > > > > > > > > > > > > > > > Thanks, > > > > > > Michele > > > > > > > > > > > > > > > > > > - > > > > > > 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] > > > > > > > > > > > > > > > > > > > > - > > 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]
Re: Tomcat 5.5.23 and Axis2 1.3-RC2 configuration
Try to use the NIO based transport receiver / sender and if possible switch to tomcat 6.* and enable the NIO connector (or the APR -- which is available also for tomcat 5.5.23). Michele On Fri, 2007-08-10 at 11:15 +0200, PXr Malmqvist wrote: > Hello! > > I have a service deployed on Axis2 1.3-RC2 and Tomcat 5.5.23. > I start with default configurations for both Tomcat and Axis2 and I > want to change configuration for the http connection to my service to > avoid exception at heavy load. > > The Tomcats server.xml file includes: > > > port="8080" maxHttpHeaderSize="8192" >maxThreads="150" minSpareThreads="25" > maxSpareThreads="75" >enableLookups="false" redirectPort="8443" > acceptCount="100" >connectionTimeout="2" disableUploadTimeout="true" >maxKeepAliveRequests="1" /> > > where I have added maxKeepAliveRequests="1" and it really improved my > service. > > > > The axis2.xml includes: > > > > > > > class="org.apache.axis2.transport.http.SimpleHTTPServer"> > 8080 > > . > > . > > > but I dont se any affection on my system when I change any parameter > for the transportReceiver. (requestCoreThreadPoolSize, ...) > > So do anyone knows how it works? Isn't the transportReciver used at > all in this case? > > > > Please, help! > > /Pr > > > > > > > > > > > > > > > > __ > FREE pop-up blocking with the new MSN Toolbar MSN Toolbar Get it now! > - > 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]
Tomcat 5.5.23 and Axis2 1.3-RC2 configuration
Hello!I have a service deployed on Axis2 1.3-RC2 and Tomcat 5.5.23.I start with default configurations for both Tomcat and Axis2 and I want to change configuration for the http connection to my service to avoid exception at heavy load. The Tomcats server.xml file includes: port="8080" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="2" disableUploadTimeout="true" maxKeepAliveRequests="1" /> where I have added maxKeepAliveRequests="1" and it really improved my service. The axis2.xml includes: class="org.apache.axis2.transport.http.SimpleHTTPServer"> 8080 . . but I dont se any affection on my system when I change any parameter for the transportReceiver. (requestCoreThreadPoolSize, ...) So do anyone knows how it works? Isn't the transportReciver used at all in this case? Please, help! /Pär FREE pop-up blocking with the new MSN Toolbar MSN Toolbar Get it now! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [axis2] jms configuration how to
More details here http://mail-archives.apache.org/mod_mbox/activemq-users/200703.mbox/% [EMAIL PROTECTED] Michele On Fri, 2007-08-10 at 09:38 +0100, Michele Mazzucco wrote: > Lizhao, > > from http://activemq.apache.org/containers.html it looks like it should > work. > > Michele > > On Fri, 2007-08-10 at 13:26 +0800, Chen, Lizhao wrote: > > Hi, Michele, > > > > I don't think it runs embedded ActiveMQ in Tomcat which described in > > http://activemq.apache.org/tomcat.html, you should have to run > > standalone ActiveMQ else. > > > > Best Regards! > > > > > > > > Lizhao Chen > > > > > > > > 86-021-50800850-8395 > > > > -Original Message- > > From: Michele Mazzucco [mailto:[EMAIL PROTECTED] > > Sent: Friday, August 10, 2007 1:26 AM > > To: axis-user@ws.apache.org > > Subject: Re: [axis2] jms configuration how to > > > > Asankha, > > > > thanks for the quick reply. I'm quite familiar with Joram > > (standalone) but not with ActiveMQ so I did what is described here > > [1] (second option) > > > > > > Michele > > > > [1] http://activemq.apache.org/tomcat.html > > > > On 9 Aug 2007, at 17:47, Asankha C. Perera wrote: > > > > > Michele > > >> > >> class="org.apache.axis2.transport.jms.JMSListener"> > > >> > > >>> >> name="java.naming.factory.initial">org.apache.activemq.jndi.ActiveMQI > > > > >> nitialContextFactory > > >>> >> name="java.naming.provider.url">tcp://localhost:61616 > > >>> >> name="transport.jms.ConnectionFactoryJNDIName">QueueConnectionFactory > > > > >> > > >> > > >> > > >> > > > You have specified that the JMS connection factory found when a > > > JNDI lookup is performed for "QueueConnectionFactory" using the > > > initial context factory > > > "org.apache.activemq.jndi.ActiveMQInitialContextFactory" and the > > > url "tcp://localhost:61616" should be used by the Axis2 JMS > > > listener. Note that the above sample configuration is the default > > > configuration for a standalone ActiveMQ release - and not for an > > > ActiveMQ instance embedded into Tomcat. > > >> [ERROR] Error creating a JMS connection using the factory : > > >> QueueConnectionFactory > > >> javax.jms.JMSException: Could not create Transport. Reason: > > >> java.io.IOException: Transport scheme NOT recognized: [tcp] > > >> > > > Here the JNDI lookup has failed when trying to access the JNDI > > > context using the above IC factory and URL. Probably this is due to > > > an issue in embedding ActiveMQ into Tomcat - which I am not > > > familiar with. You could refer to the ActiveMQ documentation, and > > > supply the correct parameters for Axis2 to use to acquire the JNDI > > > context and things will work > > > > > > asankha > > > > > > - > > > 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] > > > > The information contained in this message may be privileged > > and confidential and protected from disclosure. If the reader > > of this message is not the intended recipient, or an employee > > or agent responsible for delivering this message to the > > intended recipient, you are hereby notified that any reproduction, > > dissemination or distribution of this communication is strictly > > prohibited. If you have received this communication in error, > > please notify us immediately by replying to the message and > > deleting it from your computer. Thank you. Tellabs > > > > > > - > > 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] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [axis2] jms configuration how to
Lizhao, from http://activemq.apache.org/containers.html it looks like it should work. Michele On Fri, 2007-08-10 at 13:26 +0800, Chen, Lizhao wrote: > Hi, Michele, > > I don't think it runs embedded ActiveMQ in Tomcat which described in > http://activemq.apache.org/tomcat.html, you should have to run > standalone ActiveMQ else. > > Best Regards! > > > > Lizhao Chen > > > > 86-021-50800850-8395 > > -Original Message- > From: Michele Mazzucco [mailto:[EMAIL PROTECTED] > Sent: Friday, August 10, 2007 1:26 AM > To: axis-user@ws.apache.org > Subject: Re: [axis2] jms configuration how to > > Asankha, > > thanks for the quick reply. I'm quite familiar with Joram > (standalone) but not with ActiveMQ so I did what is described here > [1] (second option) > > > Michele > > [1] http://activemq.apache.org/tomcat.html > > On 9 Aug 2007, at 17:47, Asankha C. Perera wrote: > > > Michele > >> >> class="org.apache.axis2.transport.jms.JMSListener"> > >> > >>>> name="java.naming.factory.initial">org.apache.activemq.jndi.ActiveMQI > > >> nitialContextFactory > >>>> name="java.naming.provider.url">tcp://localhost:61616 > >>>> name="transport.jms.ConnectionFactoryJNDIName">QueueConnectionFactory > > >> > >> > >> > >> > > You have specified that the JMS connection factory found when a > > JNDI lookup is performed for "QueueConnectionFactory" using the > > initial context factory > > "org.apache.activemq.jndi.ActiveMQInitialContextFactory" and the > > url "tcp://localhost:61616" should be used by the Axis2 JMS > > listener. Note that the above sample configuration is the default > > configuration for a standalone ActiveMQ release - and not for an > > ActiveMQ instance embedded into Tomcat. > >> [ERROR] Error creating a JMS connection using the factory : > >> QueueConnectionFactory > >> javax.jms.JMSException: Could not create Transport. Reason: > >> java.io.IOException: Transport scheme NOT recognized: [tcp] > >> > > Here the JNDI lookup has failed when trying to access the JNDI > > context using the above IC factory and URL. Probably this is due to > > an issue in embedding ActiveMQ into Tomcat - which I am not > > familiar with. You could refer to the ActiveMQ documentation, and > > supply the correct parameters for Axis2 to use to acquire the JNDI > > context and things will work > > > > asankha > > > > - > > 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] > > The information contained in this message may be privileged > and confidential and protected from disclosure. If the reader > of this message is not the intended recipient, or an employee > or agent responsible for delivering this message to the > intended recipient, you are hereby notified that any reproduction, > dissemination or distribution of this communication is strictly > prohibited. If you have received this communication in error, > please notify us immediately by replying to the message and > deleting it from your computer. Thank you. Tellabs > > > - > 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]
