[Axis2][Patch] Whitespace bug Makefile.am

Hi all, There is a whitespace charactor in modules/xml/om/src/Makefile.am after a \. As a result Makefile.in and Makefile doesn't get generated properlly. Attached patch fixed that problem. Please apply. Sanjaya Index: modules/xml/om/src/Makefile.am

[Axis2] Pathced header file replaced

Hi all, There was a problem when compiling axis2 on powerpc. In include/axis2_defines.h calling convention wanted to define only for _GNUC_ on _i386_. The patched axis2_defines.h was there and somebody has replaced it. Please apply the patch or restore the correct file again. Thanks

[Axis2] Pathced header file replaced

Hi all, There was a problem when compiling axis2 on powerpc. In include/axis2_defines.h calling convention cdecl' wanted to define only for _GNUC_ on _i386_. The patched axis2_defines.h was there and somebody has replaced it. Please apply the patch or restore the correct file again.

[Axis2] Added string concatenate function

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I have added axis2_stracat(const axis2_char_t *s1, const axis2_char_t *s2, axis2_env_t **env) function. Please apply the patch and commit the code. - - Sahan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG

[jira] Created: (AXIS-2341) Error in SOAP message when using 2D-Arrays

Error in SOAP message when using 2D-Arrays --- Key: AXIS-2341 URL: http://issues.apache.org/jira/browse/AXIS-2341 Project: Apache Axis Type: Bug Components: Serialization/Deserialization Versions: 1.3

Re: [VOTE] David Blevins as Axis committer (Re: Axis 1.4 FinalBranch)

+1 ~Thilina On 12/14/05, jayachandra [EMAIL PROTECTED] wrote: Here is my +1 Jaya On 12/14/05, Tom Jordahl [EMAIL PROTECTED] wrote: +1 to David.All help with Axis 1.x appreciated!--Tom Jordahl -Original Message- From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED]] Sent: Tuesday,

RE: Bug in beandeserializer??

Title: Bug in beandeserializer?? Hi Everone, It seems like either noone know what is going on here or noone wants to offer help. I really think this is a bug, but don't know much about it to figure it out. Can anyone please help me with this??? Thanks, Parikh, Pratik | Software Engineer

Re: [Axis2] Possible bug in the AxisEngine.resume() method

Hi Chamikara: +1 and -1 to parts of this patch. :) First, I agree about merging the chains (op-specifc and global) into one - that was the intent (a single EC) from the first Axis2 meetings. The problem with doing it here is that I think this method might get called before operation dispatching

[jira] Created: (AXIS-2342) Reopen issue: Character entities are escaped too aggressively

Reopen issue: Character entities are escaped too aggressively - Key: AXIS-2342 URL: http://issues.apache.org/jira/browse/AXIS-2342 Project: Apache Axis Type: Bug Components: Serialization/Deserialization

[jira] Commented: (AXIS-2342) Reopen issue: Character entities are escaped too aggressively

[ http://issues.apache.org/jira/browse/AXIS-2342?page=comments#action_12360513 ] Thiago Jung Bauermann commented on AXIS-2342: - I am opening this issue again because it appears that the fix to this problem was removed from the source code. From

Re: [Axis2] Possible bug in the AxisEngine.resume() method

Hi Glen, Please see my comments below.On 12/15/05, Glen Daniels [EMAIL PROTECTED] wrote: Hi Chamikara:+1 and -1 to parts of this patch. :)First, I agree about merging the chains (op-specifc and global) into one- that was the intent (a single EC) from the first Axis2 meetings.Theproblem with doing

Re: [VOTE] David Blevins as Axis committer (Re: Axis 1.4 FinalBranch)

+ for David. Jaliya - Original Message - From: Thilina Gunarathne To: axis-dev@ws.apache.org Sent: Thursday, December 15, 2005 6:03 AM Subject: Re: [VOTE] David Blevins as Axis committer (Re: Axis 1.4 FinalBranch) +1 ~Thilina On 12/14/05,

Re: [Axis2] Possible bug in the AxisEngine.resume() method

Hi Chamikara! Actually what I merged was the AxisEngine.send() method (not receive() ). Shouldn't both chains be available by the time this get called by the MessageReceiver ? If so merging in the begining should not be a problem. Woops, my bad - I misinterpreted the patch. Yes, you're

RE: Clustering Axis2

On Wed, 2005-12-14 at 14:07 -0500, Rajith Attapattu wrote: http://wadi.codehaus.org/ Fankly I am no expert either, I am actually working on (discussion stage) adding HA-JNDI to WADI. Jeff Geneder and Jules Gosnel are the experts and according to Jeff the web session clustering works well

[axis2] MessageContext IDs

Is there any reason why we can't make it so that every message context has an id when its created? I'm fine with having getId() and setId() so that the default ID can be changed but it seems to me that we never use a message context without setting the ID. This avoids repeated code fragments like:

[jira] Commented: (AXIS-2272) Duplicated operation names

[ http://issues.apache.org/jira/browse/AXIS-2272?page=comments#action_12360554 ] Jason Weiss commented on AXIS-2272: --- We've run into this exact same issue on multiple projects. We've wasted more time wondering what was going on until we actually looked

Re: [Axis2] Possible bug in the AxisEngine.resume() method

Hi Glen, Since TransportSender already extend the Handler interface it can be easily attached to the end of the handler chain. But MessageReceiver is a seperate interface and this does not extend Handler. Are you suggesting that the MessageReceiver should extend the Handler interface. (also this