[Axis2] Adding new build script

Hi, I would like to have current build.sh renamed to build_all.sh and keep the original build.sh(before the project moves and folder structure changes) as it is. thanks damitha - To unsubscribe, e-mail: [EMAIL PROTECTED] For

[jira] Closed: (AXIS2C-162) Support C code generation using WSDLs using Axis2/Java codegen tool

[ http://issues.apache.org/jira/browse/AXIS2C-162?page=all ] Samisa Abeysinghe closed AXIS2C-162: Resolution: Fixed Assign To: Samisa Abeysinghe This code by Dimuthu to generate C code was commited into Java svn, after discusing over the

Re: [Axis2] Adding new build script

Samisa Abeysinghe wrote: Damitha Kumarage wrote: Hi, I would like to have current build.sh renamed to build_all.sh and keep the original build.sh(before the project moves and folder structure changes) as it is. +1. This will ease the build process, when it comes to build all and build

[Axis2] Moving tests into respective projects-Done

Hi all, I have moved util and axiom tests from the main project into respective projects. thanks damitha - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

[axis2] fixes for occurring multiple definitions when building firefox extension

Hi, I got an error some symbols ( transport_out, transport_in, axis2_stack_ops )defines twise, while I m building the firefox extension. The fixes are attached with the mail. Regards Dimuthu Index: modules/core/engine/conf.c

Re: [axis2] fixes for occurring multiple definitions when building firefox extension

Hi Dimuthu I applied the patch. Thanks nandikaOn 5/19/06, Dimuthu Gamage [EMAIL PROTECTED] wrote: Hi, I got an errorsome symbols ( transport_out, transport_in,axis2_stack_ops )defines twise, while I m building the firefoxextension. The fixes are attached with the mail.RegardsDimuthu Index:

[jira] Created: (AXISCPP-970) axis-c engine: nillable problem: when minOccurs=0 and nillable=false, the serailization does NOT follow W3C schema standard

axis-c engine: nillable problem: when minOccurs=0 and nillable=false, the serailization does NOT follow W3C schema standard --- Key: AXISCPP-970 URL:

[jira] Resolved: (AXIS2C-53) Enable setting proxy in client transport

[ http://issues.apache.org/jira/browse/AXIS2C-53?page=all ] Sahan Gamage resolved AXIS2C-53: Fix Version: Current (Nightly) (was: 0.92) Resolution: Fixed Added proxy supprt. Proxies will be enabled by setting following

[jira] Commented: (AXISCPP-970) axis-c engine: nillable problem: when minOccurs=0 and nillable=false, the serailization does NOT follow W3C schema standard

[ http://issues.apache.org/jira/browse/AXISCPP-970?page=comments#action_12412617 ] Michael Xiong commented on AXISCPP-970: --- //Sorry, there're some poinnts in-corrent in above content, so I'd like to rewite it as the below(would you like to help me

[Axis2] Why does org.apache.axis2.engine.Handler extend Serializable interface

Hi Folks, Is there any particular reason that the org.apache.axis2.engine.Handler interface extends Serializable interface. -- Thanks Afkham Azeez - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail:

Re: [Axis2] C code generation using codegen tool - whre to put the code?

Done. Samisa... Davanum Srinivas wrote: Samisa, You have commit privs...So please go ahead and commit the changes. thanks, dims On 5/19/06, Samisa Abeysinghe [EMAIL PROTECTED] wrote: Here is the Axis2/C Jira that has the source attachment: http://issues.apache.org/jira/browse/AXIS2C-162

Re: [Axis2] Why does org.apache.axis2.engine.Handler extend Serializable interface

Done ! Thanks, Ruchith On 5/19/06, Sanjiva Weerawarana [EMAIL PROTECTED] wrote: On Fri, 2006-05-19 at 13:06 +0600, Afkham Azeez wrote: Hi Folks, Is there any particular reason that the org.apache.axis2.engine.Handler interface extends Serializable interface. None that I can think of!

[jira] Created: (AXIS2-750) Extract and support wsaw:Action (or Default Action Pattern) on service side. WSDL 1.1 Only

Extract and support wsaw:Action (or Default Action Pattern) on service side. WSDL 1.1 Only -- Key: AXIS2-750 URL: http://issues.apache.org/jira/browse/AXIS2-750 Project: Apache Axis 2.0

[jira] Updated: (AXIS2-750) Extract and support wsaw:Action (or Default Action Pattern) on service side. WSDL 1.1 Only

[ http://issues.apache.org/jira/browse/AXIS2-750?page=all ] David Illsley updated AXIS2-750: Attachment: patch.txt Patch implementing the above with some relevant unit tests. NB. Treats the 'input' action as the output when !serverSide in the

Re: [Axis2] C code generation using codegen tool - whre to put the code?

On Fri, 2006-05-19 at 10:25 +0530, Ajith Ranabahu wrote: As for moving the codegen tool out, I'm not really sure we should be doing that right now. One issue I see in that is the use of core Axis2 components inside the codegen module where there is a tight dependency on Axis2 components such

[VOTE] David Illsley for committer

When people suffer from daily merge conflicts problem. I know they are ready :) I'd like to nominate David for committer status in Axis2 based on his consistent stream of patches, Hopefully more to come :) Here's my vote: +1. Thanks, dims On 5/19/06, David Illsley (JIRA) [EMAIL PROTECTED]

Re: [VOTE] David Illsley for committer

+1 indeed. Davanum Srinivas wrote: When people suffer from daily merge conflicts problem. I know they are ready :) I'd like to nominate David for committer status in Axis2 based on his consistent stream of patches, Hopefully more to come :) Here's my vote: +1. Thanks, dims On

Re: [VOTE] David Illsley for committer

+1, welcome aboard, David. Robert http://www.braziloutsource.com/On 5/19/06, Deepal Jayasinghe [EMAIL PROTECTED] wrote:+1 indeed.Davanum Srinivas wrote: When peoplesuffer from daily merge conflicts problem. I know they are ready :) I'd like to nominate David for committer status in Axis2 based

Re: [VOTE] David Illsley for committer

+1 and Welcome !! Davanum Srinivas wrote: When people suffer from daily merge conflicts problem. I know they are ready :) I'd like to nominate David for committer status in Axis2 based on his consistent stream of patches, Hopefully more to come :) Here's my vote: +1. Thanks, dims

Re: [Axis 2] Woden maven repo Location

Thanks Dims! I've been meaning to do this for a while. Lawrence Davanum Srinivas [EMAIL PROTECTED] 05/19/2006 12:14 AM Please respond to axis-dev@ws.apache.org To Chathura Herath [EMAIL PROTECTED] cc axis-dev@ws.apache.org, woden-dev@ws.apache.org Subject Re: [Axis 2] Woden

[jira] Created: (AXIS2-751) Easier customization of message receivers needed

Easier customization of message receivers needed Key: AXIS2-751 URL: http://issues.apache.org/jira/browse/AXIS2-751 Project: Apache Axis 2.0 (Axis2) Type: Wish Components: core Versions: 1.0 Reporter:

[jira] Commented: (AXIS-2479) cannot deserialize exception with null non-nillable attributes (premature end of file)

[ http://issues.apache.org/jira/browse/AXIS-2479?page=comments#action_12412545 ] Bjorn Townsend commented on AXIS-2479: -- Nikolay, Can you provide code with which to reproduce this issue? I'm also a bit confused as to why you'd want to throw an

RE: [Axis2] Axis2 and Woden

+1 Way to early to branch 1.1 and 1.0.1. -- Tom Jordahl Adobe ColdFusion Team -Original Message- From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED] Sent: Thursday, May 18, 2006 1:10 PM To: axis-dev@ws.apache.org Cc: woden-dev@ws.apache.org Subject: Re: [Axis2] Axis2 and Woden On Thu,

[jira] Created: (AXIS2-752) Problem handling multiple binary MTOM attachments

Problem handling multiple binary MTOM attachments - Key: AXIS2-752 URL: http://issues.apache.org/jira/browse/AXIS2-752 Project: Apache Axis 2.0 (Axis2) Type: Bug Versions: 1.0 Environment: Windows XP, Tomcat

[jira] Updated: (AXIS2-752) Problem handling multiple binary MTOM attachments

[ http://issues.apache.org/jira/browse/AXIS2-752?page=all ] Timo Ahokas updated AXIS2-752: -- Attachment: TestCode.zip Testcase code (client, server + service description/wsdl) + example SOAP messages. Problem handling multiple binary MTOM attachments

[jira] Created: (AXIS2-753) Setting SOAP Version URI to type 1.2 creates invalid Content-Type that fails during parsing

Setting SOAP Version URI to type 1.2 creates invalid Content-Type that fails during parsing --- Key: AXIS2-753 URL: http://issues.apache.org/jira/browse/AXIS2-753 Project: Apache Axis

[jira] Updated: (AXIS2-753) Setting SOAP Version URI to type 1.2 creates invalid Content-Type that fails during parsing

[ http://issues.apache.org/jira/browse/AXIS2-753?page=all ] Timo Ahokas updated AXIS2-753: -- Attachment: TestCode2.zip Test client for reproducing the issue. It will fail the call - comment out the line with sets the SOAP version and no exception will be

[jira] Commented: (AXIS2-753) Setting SOAP Version URI to type 1.2 creates invalid Content-Type that fails during parsing

[ http://issues.apache.org/jira/browse/AXIS2-753?page=comments#action_12412572 ] Timo Ahokas commented on AXIS2-753: --- The server reports this: 2006-05-19 19:30:02,973

[jira] Commented: (AXIS2-753) Setting SOAP Version URI to type 1.2 creates invalid Content-Type that fails during parsing

[ http://issues.apache.org/jira/browse/AXIS2-753?page=comments#action_12412575 ] Timo Ahokas commented on AXIS2-753: --- Seems to only occur when ENABLE_MTOM is also set to true (only setting the SOAP 1.2 version doesn't cause this error). Setting SOAP

Re: [Axis2] C code generation using codegen tool - whre to put the code?

Sanjiva Weerawarana wrote: On Fri, 2006-05-19 at 10:25 +0530, Ajith Ranabahu wrote: As for moving the codegen tool out, I'm not really sure we should be doing that right now. One issue I see in that is the use of core Axis2 components inside the codegen module where there is a tight

Re: [Axis2] C code generation using codegen tool - whre to put the code?

Dennis Sosnoski wrote: Sanjiva Weerawarana wrote: On Fri, 2006-05-19 at 10:25 +0530, Ajith Ranabahu wrote: As for moving the codegen tool out, I'm not really sure we should be doing that right now. One issue I see in that is the use of core Axis2 components inside the codegen module where

Help Me!!

Hello All, I have this WSDL service ?xml version=1.0 encoding=UTF-8? wsdl:definitions xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:tns=http://co.com.www.avisortech/MPPWebServices/; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:xsd=http://www.w3.org/2001/XMLSchema;