axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Gainty" <>
Subject Re: Help with SwA
Date Sun, 29 Apr 2007 18:09:30 GMT

Appears you may have discovered a bug as the as there appears
to not be ability to deal with any buffer over 64k (the native datatypes appear to be all
integer instead of long)
Looking at the source
I find length assignments of variables to int (max +- 64k) but no mention of lengths to long
or unsigned long datatypes
Do you know if there a JIRA ???

Saludos Cordiales!
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.

  ----- Original Message ----- 
  From: Jorge Fernandez 
  To: ; 
  Sent: Sunday, April 29, 2007 11:23 AM
  Subject: Re: Help with SwA

  Hi Thilina,

  With the new release that seems to work fine. But sadly :( , now I'm getting the following
exception when trying to access the attachments with both MTOM or SwA at the client: javax.mail.MessagingException: Error reading input stream;
    nested exception is: End of Stream, but boundary not found
      at org.apache.axiom.attachments.Attachments.getPart(
      at org.apache.axiom.attachments.Attachments.getNextPartDataHandler(
      at org.apache.axiom.attachments.Attachments.getContentIDSet(
      at org.apache.axiom.attachments.Attachments.getAllContentIDs(
      at client.Medici_LinkSOAP12PortStub.getAttachment(
      at client.ClientUtilities.mtomTest(
      at client.Client.main(
  Caused by: javax.mail.MessagingException: Error reading input stream;
    nested exception is: End of Stream, but boundary not found
      at javax.mail.internet.MimeBodyPart.<init>(
      at org.apache.axiom.attachments.PartOnMemory.<init>(
      at org.apache.axiom.attachments.Attachments.getPart(
      ... 6 more
  Caused by: End of Stream, but boundary not found
      at Source)
      at Source)
      at Source)
      at com.sun.mail.util.ASCIIUtility.getBytes(
      at javax.mail.internet.MimeBodyPart.<init>(
      ... 8 more

  I can see with TCPMon this:

  HTTP/1.1 200 OK
  Server: Apache-Coyote/1.1
  Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_2B201ECB17F697F7391177859246638;
type="application/soap+xml"; start="<>";
action="urn:validateUser";charset=UTF-8Transfer-Encoding: chunkedDate: Sun, 29 Apr 2007 15:07:26
GMT423--MIMEBoundaryurn_uuid_2B201ECB17F697F7391177859246638Content-Type: application/soap+xml;
charset=UTF-8Content-Transfer-Encoding: 8bitContent-ID: 
        <?xml version='1.0' encoding='UTF-8'?>
           <soapenv:Envelope xmlns:wsa="" xmlns:soapenv="">
                       <axis2:ServiceGroupId xmlns:axis2="">urn:uuid:2B201ECB17F697F7391177859246088</axis2:ServiceGroupId>
                 <ns3:validateUserResponse xmlns:ns3="http://op_messages.medici_link/xsd">


  Content-Type: application/octet-stream
  Content-Transfer-Encoding: binary

  And this is the last line I can see with TCPMon

  I'm sending a 11'8KB picture. 
  With axis2 1.1.1 I had no problem with sending a picture that was about 24 KB. If I sent
a larger one, I received it with errors and I couldn't see it correctly in the client but
the response message seemed to be well formed.

  Could you tell me, please if I have to do something else to send attachments in the service??

  Thilina Gunarathne <> escribió:
    > org.apache.axis2.AxisFault: Invalid Application type. Support available for
    > MTOM & SwA/SOAP 1.l only.; nested exception is:
    > Invalid Application type. Support
    > available for MTOM & SwA/SOAP 1.l only.
    You seem to be usign a old version of the axis2.. Please try the
    latest 1.2 release..

    > But I don't know if this is right. Do I have to specify something in the
    > wsdl like I do when I use MTOM so the client could expect any attachment
    > when parsing the response message.
    MTOM is much better than SwA.. You can specify the type of the element
    containing the binary data as base64Binary...

    Seems like you already have it in your WSDL, since you seem to be able
    to succesfully generate skeletons with MTOM suppport...

    See for more data...

    Thilina Gunarathne - -

    To unsubscribe, e-mail:
    For additional commands, e-mail:


  LLama Gratis a cualquier PC del Mundo.
  Llamadas a fijos y móviles desde 1 céntimo por minuto.
View raw message