The attached patch is sub-optimal. In AXIS2-3765 (wasn't aware that it is 
the same bug when i created the issue since we only have one byte[])  i 
proposed a patch which does not need the extra loop.
Nevertheless it works both ways..

I also patched it locally and we are going live with this patch, even 
though i am not really happy about this.






"Afkham Azeez" <[EMAIL PROTECTED]> 
03.12.2008 01:27
Bitte antworten an
[email protected]


An
[email protected]
Kopie

Thema
Re: Problem related to ADB when transferring a byte array [== AXIS2-3538]






Have you submitted this patch? Is this the same patch that is attached to 
JIRA issue AXIS2-3538? 

Thanks
Azeez

On Tue, Dec 2, 2008 at 2:07 PM, Andrea Spinelli <[EMAIL PROTECTED]
> wrote:

Marc F. wrote:
 
To demonstrate a possible bug in ADB Webservice I attached a zip file,
containing two aar files, and the source code as well.

 

Alas, I think this is a well-known issue:

 https://issues.apache.org/jira/browse/AXIS2-3538

I had an exchange of e-mails with Deepal, but it ended in nothing.

The issue was submitted on 24/Feb/08 09:13 AM and a suggestion for a patch 
is available from June 2008, but it is currently unassigned. It is marked 
as "critical".

In our organisation we wrote a patch, recompiled axis2, and we are using 
the patch (with success).  I can send the patch to anyone interested, but 
I think this is a REALLY BAD problem and should be fixed as soon as 
possible by the axis2 development team.

Is anyone in the axis2 team listening?

Hi
 Andrea

-- 
dott. Andrea Spinelli - IMTeam
e-mail: andrea dot spinelli at imteam dot it
phone: +39-035-636029
fax: +39-035-638129
www: http://www.imteam.it/
IANA enterprise number: 1.3.6.1.4.1.30916


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-- 
Thanks
Afkham Azeez

Blog: http://afkham.org
Developer Portal: http://www.wso2.org
WSAS Blog: http://wso2wsas.blogspot.com
Company: http://wso2.com
GPG Fingerprint: 643F C2AF EB78 F886 40C9  B2A2 4AE2 C887 665E 0760

Reply via email to