[jira] Created: (AXIS2C-99) mod_axis2 crashes in Win32

mod_axis2 crashes in Win32 -- Key: AXIS2C-99 URL: http://issues.apache.org/jira/browse/AXIS2C-99 Project: Axis2-C Type: Bug Components: transport/http Versions: Current (Nightly) Reporter: Sahan Gamage Axis2 Apache2

RE: [AXIS2] soapFault question

And additionally, how to get rid of the faultactor element? Yves On Mon, 2006-03-13 at 11:15 -0500, Tony Dean wrote: Chinthaka, After retrying this just now, it almost works but not quite. The results follow: ?xml version=1.0 encoding=UTF-8 ? - soapenv:Envelope

Re: [axis2] Gump ws-commons-axiom

Hi Steve: I've been trying to get axis2 to build on gump. primarily to stop anyone making changes incompatible with my project. It will also catch out problems nobody has missed, and that includes tests that fail. +1! There are currently three tests failing on axiom. Unless/until they are

RE: documentation

Mylene, You can open a Jira bug with the diffs to the docs. Someone (and I don't know if it will be me) should be able to apply the patches. -- Tom Jordahl Adobe ColdFusion Team -Original Message- From: mylene [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 14, 2006 12:58 AM To: Tom

SimpleSession destroy

Hello all. When a SimpleSession object expires (timeout ended), the hashtable inside this object is detroyed but not this object. So, the garbage collector cannot suppress this object in the memory. Is it normal ? Don't I understand something? If it's a known bug, is a correction planned?

[Axis2] REMINDER : Axis IRC chat TOMORROW

Hi folks! This is an automatic reminder that the weekly Axis2 developer chat will be occurring tomorrow, March 15, at: 7PM PST, 10PM EST, 3AM GMT, 9AM (next day) SLT, 2PM (next day) AEST The chat takes place on the freenode IRC network, (use server irc.freenode.net), on channel #apache-axis,

Re: [Axis2] A question about asynchronous services and message queue

Maybe I should clarify my point here: A service can support asynchronous communication with a message queue stands before it, no matter whether or not this service is able to support asynchronous messaging by nature. It is hard for an asynchronous service to handle long-run service requests

Re: [axis2] Gump ws-commons-axiom

Glen Daniels wrote: Hi Steve: I've been trying to get axis2 to build on gump. primarily to stop anyone making changes incompatible with my project. It will also catch out problems nobody has missed, and that includes tests that fail. +1! There are currently three tests failing on axiom.

[jira] Commented: (AXIS2-488) UnsignedLong would be improved by implementing the Comparable interface

[ http://issues.apache.org/jira/browse/AXIS2-488?page=comments#action_12370372 ] Alan M. Feldstein commented on AXIS2-488: - Index: modules/adb/src/org/apache/axis2/databinding/types/UnsignedLong.java

[jira] Created: (AXIS2-490) Arrays are not handled correctly by org.apache.axis2.databinding.utils.BeanUtil.deserialize

Arrays are not handled correctly by org.apache.axis2.databinding.utils.BeanUtil.deserialize --- Key: AXIS2-490 URL: http://issues.apache.org/jira/browse/AXIS2-490 Project: Apache Axis

[jira] Created: (AXIS2-491) Arrays are not handled correctly by org.apache.axis2.databinding.utils.BeanUtil.deserialize

Arrays are not handled correctly by org.apache.axis2.databinding.utils.BeanUtil.deserialize --- Key: AXIS2-491 URL: http://issues.apache.org/jira/browse/AXIS2-491 Project: Apache Axis

[jira] Updated: (AXIS2-491) Arrays are not handled correctly by org.apache.axis2.databinding.utils.BeanUtil.deserialize

[ http://issues.apache.org/jira/browse/AXIS2-491?page=all ] Chad Brandon updated AXIS2-491: --- Attachment: patch.txt Here's the patch. Arrays are not handled correctly by org.apache.axis2.databinding.utils.BeanUtil.deserialize

[jira] Commented: (AXIS2-490) Arrays are not handled correctly by org.apache.axis2.databinding.utils.BeanUtil.deserialize

[ http://issues.apache.org/jira/browse/AXIS2-490?page=comments#action_12370384 ] Chad Brandon commented on AXIS2-490: Can someone please delete this issue? I accidently hit submit twice and it created duplicate issues. Sorry about that. Thanks.

[jira] Deleted: (AXIS2-491) Arrays are not handled correctly by org.apache.axis2.databinding.utils.BeanUtil.deserialize

[ http://issues.apache.org/jira/browse/AXIS2-491?page=all ] Davanum Srinivas deleted AXIS2-491: --- Arrays are not handled correctly by org.apache.axis2.databinding.utils.BeanUtil.deserialize

[jira] Updated: (AXIS2-490) Arrays are not handled correctly by org.apache.axis2.databinding.utils.BeanUtil.deserialize

[ http://issues.apache.org/jira/browse/AXIS2-490?page=all ] Chad Brandon updated AXIS2-490: --- Attachment: patch.txt Attaching the patch to this issue (since AXIS-491) was the one that was deleted. Arrays are not handled correctly by

[jira] Created: (AXIS2-492) new UnsignedLong( 0xffffffffffffffffL ) should not throw a NumberFormatException

new UnsignedLong( 0xL ) should not throw a NumberFormatException Key: AXIS2-492 URL: http://issues.apache.org/jira/browse/AXIS2-492 Project: Apache Axis 2.0 (Axis2)

Axis 1.1 Final

Title: Axis 1.1 Final Hello, The link to Axis 1.1 (Final Version) is no longer valid. Can you please update the link and also provide a location where it can be downloaded from? We have a live product that was tested against the 1.1 version and we don't have the manpower to retest with a

Re: Axis 1.1 Final

Please check the archives: http://archive.apache.org/ -- dims On 3/14/06, Rudy Tibuni [EMAIL PROTECTED] wrote: Hello, The link to Axis 1.1 (Final Version) is no longer valid. Can you please update the link and also provide a location where it can be downloaded from? We have a live

Re: [Axis2] JAX-WS as another WSDL2Code/Java language option?

Looking at WSDL - Java work required by JAX-WS, and one way that occurred to me to do this was to define another language (jax-ws) as a peer to java and csharp, for which there would be an emitter associated templates/writer classes. This implies that the java language option is really the

[Axis2] Interface vs Binding vs Automatic code gen

Is org.apache.axis2.wsdl.codegen.CodeGenConfiguration.codeGenerationStyle actually user configurable at this point? This comment in CodeGenConfiguration.java suggests it is: /* Code generation style means whether to use the binding or the interface for code generation. * the default is

[jira] Created: (AXIS2-493) When using BeanUtil at the RPCMessageReceiver(i.e.), axis2 gets NullPointerException using java styled propert names such as contextType(setContextType/getContextType)

When using BeanUtil at the RPCMessageReceiver(i.e.), axis2 gets NullPointerException using java styled propert names such as contextType(setContextType/getContextType)

[jira] Updated: (AXIS2-493) When using BeanUtil at the RPCMessageReceiver(i.e.), axis2 gets NullPointerException using java styled propert names such as contextType(setContextType/getContextType)

[ http://issues.apache.org/jira/browse/AXIS2-493?page=all ] Fabio Costa updated AXIS2-493: -- Attachment: Mail.java Mail class used by the issue I presented. When using BeanUtil at the RPCMessageReceiver(i.e.), axis2 gets NullPointerException using java

Re: [Axis2] JAX-WS as another WSDL2Code/Java language option?

Hi all, Exactly. You can reuse most of the writer/emitter stuff but essentially what you'll have to implement is an emitter and a bunch of templates. jax-ws is fine for the lang name. Ajith On 3/15/06, Kenneth Tam [EMAIL PROTECTED] wrote: Looking at WSDL - Java work required by JAX-WS, and one

Re: [axis2] WSDL 2.0 CR work

Hi Glen and all, We are quite happy to see the woden people making progress and yes, we are surely looking forward to a solid piece of woden code which we can integrate to Axis2. Here is what I think of the situation right now. 1. WOM is somewhat deeply hooked into Axis2 right now and replacing