If the issue occurs on the client side, it could somehow be related to FILE_SIZE_THRESHOLD, but that is not the most probable explanation. I remember fixing several issues in Axiom with code that incorrectly assumed that InputStream#available always returns the remaining number of bytes in the stream. This is true for ByteArrayInputStream, but not for FileInputStream. The code was related to MTOM or base64 handling and chances are high that these fixes resolve the problem seen by Massimiliano. Hence my request to test with the latest Axiom version.
Andreas On Thu, May 21, 2009 at 13:59, Chinmoy Chakraborty <[email protected]> wrote: > Hi, > > Just curious..is there anything to do with 'FILE_SIZE_THRESHOLD'? > > Chinmoy > > On Thu, May 21, 2009 at 3:01 PM, Massimiliano Ziccardi > <[email protected]> wrote: >> >> TO Andreas: I tried with the latest snapshot, but even after replacing >> both axis and axiom, I always get: >> >> The type org.apache.axiom.om.impl.OMStAXWrapper cannot be resolved. It is >> indirectly referenced from required .class files WStestImplStub.java >> TEST_CLIENT/src/it/test/ws/impl >> >> I've searched through the jars, and I found OMStAXWrapper inside another >> package... >> >> Did I make something wrong? >> >> TO Sanjay: I read the topic you talk about. I've autogenerated the client >> starting from the wsdl: should I rewrite the stub using the logic described >> there? >> >> At the moment, I simply call the getFile(GetFile).get_return methods of my >> stub to get the DataHandler >> >> Thanks, >> Massimiliano >> >> On Wed, May 20, 2009 at 6:26 PM, Sanjay Gupta >> <[email protected]> wrote: >>> >>> I had the exact same issue few weeks back and martin gainty helped me. I >>> haven't tried his solution yet. I have been so busy with other things. See >>> the thread "Sending binary data(not using MTOM) using DataHandler". >>> Thanks >>> Sanjay >>> >>> -----Original Message----- >>> From: Andreas Veithen [mailto:[email protected]] >>> Sent: Wednesday, May 20, 2009 8:46 AM >>> To: [email protected] >>> Subject: Re: Problem with MTOM >>> >>> Massimiliano, >>> >>> Can you check whether replacing the Axiom JARs with version >>> 1.2.9-SNAPSHOT fixes this issue? You can download them from [1]. If >>> that doesn't help, can you try to use tcpmon or Wireshark to determine >>> whether the content is truncated on the server or client side? >>> >>> Andreas >>> >>> [1] >>> http://people.apache.org/repo/m2-snapshot-repository/org/apache/ws/commons/axiom/ >>> >>> On Wed, May 20, 2009 at 17:25, Massimiliano Ziccardi >>> <[email protected]> wrote: >>> >>Which version of Axis2 >>> > >>> > I'm using AXIS2 1.4.1. >>> > >>> >>and Axiom do you use? >>> > >>> > All the jars I use are from the AXIS2 1.4.1 package. >>> > >>> >>Is the client also Axis2 based? >>> > >>> > Both client and server are AXIS2 1.4.1 >>> > >>> > Thank you very much for you prompt help! >>> > >>> > Massimiliano >>> > >>> > >>> > On Wed, May 20, 2009 at 5:22 PM, Andreas Veithen >>> > <[email protected]> >>> > wrote: >>> >> >>> >> Massimiliano, >>> >> >>> >> Which version of Axis2 and Axiom do you use? >>> >> Is the client also Axis2 based? >>> >> >>> >> Andreas >>> >> >>> >> On Wed, May 20, 2009 at 17:17, Massimiliano Ziccardi >>> >> <[email protected]> wrote: >>> >> > Hi all. >>> >> > >>> >> > I've a simlpe pojo class: >>> >> > >>> >> > public class MyClass >>> >> > { >>> >> > public DataHandler getFile() >>> >> > { >>> >> > return new DataHandler(new FileDataSource(new >>> >> > File("/tmp/myfile"))); >>> >> > } >>> >> > } >>> >> > >>> >> > I've published that pojo as a WebService. >>> >> > >>> >> > The problem is that, on the client side, the file is always >>> >> > truncated at >>> >> > 12123 bytes. >>> >> > >>> >> > How can I solve this issue? >>> >> > >>> >> > Thanks, >>> >> > Massimiliano >>> >> > >>> > >>> > >> > >
