Re: Axis2 Release Date (again)

Sanjiva Weerawarana wrote: How does April 1st sound? 6 weeks from today. Its April fool's day ;-) Anyway, lets lay down some realistic requirements for Axis2 1.0. I set up a wiki page for those requirements here (http://wiki.apache.org/ws/FrontPage/Axis2/releases/1.0). Please help

Re: Axis2 Release Date (again)

Thanks, Sanjiva. :) On 2/13/06, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: On Mon, 2006-02-13 at 10:40 +0800, Juanda Zeng wrote:> Hi. I know this has been asked before, but the last time I checked, I > couldn't find the answer. So here it is again...>> Our company plans to incorporate Axis2 int

Re: Axis2 Release Date (again)

On Mon, 2006-02-13 at 10:40 +0800, Juanda Zeng wrote: > Hi. I know this has been asked before, but the last time I checked, I > couldn't find the answer. So here it is again... > > Our company plans to incorporate Axis2 into one of our products. But > we would be more comfortable in adopting Axis

Please revert this (Re: svn commit: r377293 - in /webservices/axis/trunk/java: src/org/apache/axis/client/ src/org/apache/axis/security/ src/org/apache/axis/server/ src/org/apache/axis/transport/http/

Dug, Making general changes is ok. But adding specific interfaces like the one you are adding is not ok. Especially since they are not in tune with existing projects like WSS4J or Sandesha. So, please consider this as a -1. Please stick to well known handler interfaces and revert these specific

Axis2 Release Date (again)

Hi. I know this has been asked before, but the last time I checked, I couldn't find the answer. So here it is again...   Our company plans to incorporate Axis2 into one of our products. But we would be more comfortable in adopting Axis2 if we know the release date, so that we can better plan our p

Re: Axis 1.X HEAD broken

I'd appreciate your great (and fast :-) work on that. Meanwhile, currently build fails due to unavailability of http:// soapinterop.java.sun.com/round3/groupd/import1?WSDL . Cheers, Ias 2006. 02. 11, 오전 3:10, David Blevins 작성: On Feb 10, 2006, at 7:24 AM, Rick McGuire wrote: David Blevi

[jira] Updated: (AXIS-2403) Deserialization of document/literal response fails in BeanPropertyTarget.java with java.lang.IllegalArgumentException: argument type mismatch

[ http://issues.apache.org/jira/browse/AXIS-2403?page=all ] Arthur Ryman updated AXIS-2403: --- Attachment: response.xml > Deserialization of document/literal response fails in BeanPropertyTarget.java > with java.lang.IllegalArgumentException: argument type

[jira] Updated: (AXIS-2403) Deserialization of document/literal response fails in BeanPropertyTarget.java with java.lang.IllegalArgumentException: argument type mismatch

[ http://issues.apache.org/jira/browse/AXIS-2403?page=all ] Arthur Ryman updated AXIS-2403: --- Attachment: schedule.xsd > Deserialization of document/literal response fails in BeanPropertyTarget.java > with java.lang.IllegalArgumentException: argument type

[jira] Updated: (AXIS-2403) Deserialization of document/literal response fails in BeanPropertyTarget.java with java.lang.IllegalArgumentException: argument type mismatch

[ http://issues.apache.org/jira/browse/AXIS-2403?page=all ] Arthur Ryman updated AXIS-2403: --- Attachment: Query.wsdl BTW, this looks very similar to bug AXIS-1761 buts its difference. That bug was caused by some case problems in field names and it failed i

[jira] Created: (AXIS-2403) Deserialization of document/literal response fails in BeanPropertyTarget.java with java.lang.IllegalArgumentException: argument type mismatch

Deserialization of document/literal response fails in BeanPropertyTarget.java with java.lang.IllegalArgumentException: argument type mismatch - Key:

[jira] Resolved: (AXIS2-447) setText() in OMElement adds the Text node twice

[ http://issues.apache.org/jira/browse/AXIS2-447?page=all ] Eran Chinthaka resolved AXIS2-447: -- Fix Version: 0.95 Resolution: Fixed This is fixed in the current svn by Ruchith. > setText() in OMElement adds the Text node twice > -