Re: Axis C++ clien not working: HTTPTransportException Channel error: connection timed out before receiving

I would suggest building Axis C++ from latest code in SVN and trying again. There are numerous fixes in the transport that is not in 1.6b. Nadir K. Amra Илья Велесевич [EMAIL PROTECTED] wrote on 08/10/2007 06:09:25 AM: Hi all!!! I'm user Axis C++ 1.6b not long ago; I have web service

WS-Addressing : Adding reference parameters?

Hi, Is there anything special you need to do to add a reference parameter other than what's contained in the following block? axiom_node_t* node = NULL; axiom_namespace_t* namespace = axiom_namespace_create( this-axisEnv, http://url/;, prefix ); axiom_element_t*

Axis C++ clien not working: HTTPTransportException Channel error: connection timed out before receiving

Hi all!!! I'm user Axis C++ 1.6b not long ago; I have web service written on C# and located on my localhost (Windows XP Pro, IIS server) (localhost - turn on) I've generate proxy classes(using WSDL2Ws tool): Service1Soap.cpp Service1Soap.hpp And my client don't working I try run this code:

Axis C++ not working: HTTPTransportException Channel error: connection timed out before receiving

Hi all!!! I'm user Axis C++ 1.6b not long ago; I have web service written on C# and located on my localhost (Windows XP Pro, IIS server) (localhost - turn on) I've generate proxy classes(using WSDL2Ws tool): Service1Soap.cpp Service1Soap.hpp And my client don't working I try run this code:

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

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

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

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?

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

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

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

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

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

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

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: !-- Define a non-SSL

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

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

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

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

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 .

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,

SoapEnvelope toStringWithConsume()

Hi I have the following issue with SoapEnvelope toStringWithConsume() it returns the following incorrect string to me: ?xml version='1.0' encoding='utf-8'?soap-env:Envelope xmlns:soap-env=http://schemas.xmlsoap.org/soap/envelope/;soap-env:HeaderTransactionID

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

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

[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

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

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.

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

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

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

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. ?xml version=1.0 encoding=UTF-8?SOAP-ENV:Envelope

XSD Schema default value behaviour

Hi, In my schema I have defined an element as xsd:element name=discountAmount type=xsd:decimal default=0/ 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

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

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:

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

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