Andrea Spinelli-2 wrote: > > 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 >
Thank you very much for your reply, Andrea. Yes, this is a really bad problem that should be fixed, mainly because this kind of problem is not like a "common bug", or a "little mistake". It is a kind of bug that can make something completely unreliable. I do not rely on ADB, and I will never use it until they fix the problem. And I will recommend everybody to not use ADB as well. I simply do not rely on ADB anymore. That´s sad. Fortunately, using a XML Beans webservice this problem doesn´t happen. Well, at least until now this didn´t happen to me. -- View this message in context: http://www.nabble.com/Problem-related-to-ADB-when-transferring-a-byte-array-tp20607870p20801565.html Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
