Hi,
I'm using version 1.3 of Axis2 to generate a java client (using
wsdl2java tool) from wsdl(which is written in .net /C#).
It is working fine if the size of the input is small. But get following
error once the message size is bigger.
org.apache.axis2.AxisFault: The input stream for an incoming message is
null.
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUti
ls.java:71)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(Out
InAxisOperation.java:326)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper
ation.java:389)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInA
xisOperation.java:211)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163
)
at
sophis.client.scenariorequestservice.ScenarioRequestServiceStub.Scenario
ApiRequest(ScenarioRequestServiceStub.java:486)
I'll give and example. The object I'm sending to the service is a Job.
It contains number of job items. If the number of job items exceeds 100,
I'm getting the above error.
I suspect something to do with SOAP message size. But I did not figure
out anything to set to Options to fix the size of SOAP message.
Any help will be appreciated.
Regards,
Anil
________________________________
From: [email protected] [mailto:[email protected]]
Sent: Friday, August 28, 2009 3:44 PM
To: [email protected]
Subject: Re: send soap attachment via AXIS2
What do you mean by "1".
Come on man, I don't want to sound like a troll, but this is the whole
problem with AXIS2. I'm not a lazy programmer. I gave you a very
specific question. My problem is, all the documentation --including "1"
on this page-- has such concise snippets, it assumes I know how to load
the implied objects, that I don't.
Am I asking a question that's more complex than I realize? I just want
the code snippet for sending an attachment, but I feel like every time I
see such info online (including your "1") it's a three line snapshot of
a huge program that seems to have nothing in common with my code (e.g.
its always some heavy awt client preparing stuff; why can't I just find
how to send a jpg or text file via AXIS2?).
I don't feel I know enough about AXIS2 to realize the pertinent parts
about "1". And, by the way, I saw "1" when I did a google search.
Are there no new users to AXIS2?
prabath <[email protected]>
08/27/2009 09:42 PM
Please respond to
[email protected]
To
[email protected]
cc
Subject
Re: send soap attachment via AXIS2
Please have a look at [1].
Thanks & regards.
-Prabath
[1]:https://svn.apache.org/repos/asf/webservices/axis2/site/1_1/mtom-gui
de.html
[email protected] wrote:
>
> Hello,
>
> I'm struggling to send a soap attachment with AXIS2.
>
> Most of the documentation I'm finding online is on receiving, rather
than
> sending attachments. Here's the closest I've gathered to what the
code
> should sort of look like (which is surely wrong):
>
>
>
stub._getServiceClient().getOptions().setProperty(Constants.Configuratio
n.ENABLE_MTOM,
> Constants.VALUE_TRUE);
>
> FileDataSource dataSource =
> new FileDataSource("c:\\myImageAttachment.jpg");
> DataHandler dataHandler = new DataHandler(dataSource);
>
> MessageContext.getCurrentMessageContext().addAttachment(dataHandler);
>
>
> stub.CreateIncident();
>
>
> But that code does not work since getCurrentMessageContext returns
null.
>
> Outside of attachments, the rest of the functionality works fine.
>
> It looks, to me, like the old version of Axis had an addAttachment
> method on the stub API, but I don't see anything comparable in 2.
>
>
> Any help would be appreciated. Thanks.
>
> Sean
>
> This transmission is intended solely for the person or organization to
> whom it is addressed and it may contain privileged and cofidential
> information. If you are not the intended recipient you should not
> copy, distribute or take any action in reliance on it. If you believe
> you received this transmission in error please notify the sender.
> 222 Merchandise Mart Plaza, Suite 250, Chicago, IL 60654, USA
>
This transmission is intended solely for the person or organization to
whom it is addressed and it may contain privileged and cofidential
information. If you are not the intended recipient you should not copy,
distribute or take any action in reliance on it. If you believe you
received this transmission in error please notify the sender.
222 Merchandise Mart Plaza, Suite 250, Chicago, IL 60654, USA
This email and any attachments are confidential and may also be privileged. If
you are not the addressee, do not disclose, copy, circulate or in any other way
use or rely on the information contained in this email or any attachments. If
received in error, notify the sender immediately and delete this email and any
attachments from your system. Emails cannot be guaranteed to be secure or
error free as the message and any attachments could be intercepted, corrupted,
lost, delayed, incomplete or amended. Standard Chartered PLC and its
subsidiaries do not accept liability for damage caused by this email or any
attachments and may monitor email traffic.
Standard Chartered PLC is incorporated in England with limited liability under
company number 966425 and has its registered office at 1 Aldermanbury Square,
London, EC2V 7SB.
Standard Chartered Bank ("SCB") is incorporated in England with limited
liability by Royal Charter 1853, under reference ZC18. The Principal Office of
SCB is situated in England at 1 Aldermanbury Square, London EC2V 7SB. In the
United Kingdom, SCB is authorised and regulated by the Financial Services
Authority under FSA register number 114276.
If you are receiving this email from SCB outside the UK, please click
http://www.standardchartered.com/global/email_disclaimer.html to refer to the
information on other jurisdictions.
