Thanks. The following line you suggested solved my problem.
outMessageContext.setProperty(Constants.Configuration.ENABLE_MTOM,Constants.VALUE_TRUE);
Great...
I am curious about the meanings and effects of the following two lines:
outMessageContext.setDoingSwA(true);
outMessageContext.setServerS
Hi Thilina,
Thanks. The following line you suggested solved my problem.
outMessageContext.setProperty(Constants.Configuration.ENABLE_MTOM,
Constants.VALUE_TRUE);
I am curious about the meanings and effects of the following two lines:
outMessageContext.setDoingSwA(true);
outMessageContext.setServ
Hi Thilina,
Thanks. The following line you suggested solved my problem.
outMessageContext.setProperty(Constants.Configuration.ENABLE_MTOM,
Constants.VALUE_TRUE);
I am curious about the meanings and effects of the following two lines:
outMessageContext.setDoingSwA(true);
outMessageContext.setServ
I use some proprietary information. From the request url my custom message
receiver can decide which service should be invoked.
I mean how you specify that a request message needs to be directed to
your custom message receiver. May be you are using a custom deployer
to bypass the services.xml.
T
I use some proprietary information. From the request url my custom message
receiver can decide which service should be invoked.
Regards,
Xinjun
On 5/26/07, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:
try this...
outMessageContext.setProperty(Constants.Configuration.ENABLE_MTOM,
Constants.VAL
try this...
outMessageContext.setProperty(Constants.Configuration.ENABLE_MTOM,Constants.VALUE_TRUE);
I don't have service.xml. I write a custom MessageReceiver to process the
request and response MessageContext
Curious to know how you are specifying your custom message receiver to
the services.
I don't have service.xml. I write a custom MessageReceiver to process the
request and response MessageContext. In this way, is the way you suggested
still workable?
Regards,
Xinjun
On 5/25/07, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:
> The following is the code snippet where I try to enab
The following is the code snippet where I try to enable SwA only for one
service.
/** in axis2.xml, enableSwA is set to false **/
Please add the enableSwA parameter to your services.xml to enable SwA
only for that service. Also you can add it under a respective
operation element in the services.
I have a related question regarding SwA support.
In the axis2.xml, if I set enableSwA to true, my response can arrive at the
client with attachment, but then all the requests (no matter there is
any attachment) are considered as multipart requests and I get "Bad Request"
error. The "Bad Request" e
> DataHandler(byte_data,"application/octet-stream");
You may use the ByteArrayDataSource for this purpose.. Alternatively
you can try using "binary" instead of the
"application/octet-stream"...
HTH,
Thilina
> BinaryData binaryData =new BinaryData();
> binaryData.setBase64Binary(dataHandler);
>
I attach the response message
Thilina Gunarathne <[EMAIL PROTECTED]> escribió: Messsage traces please..:)
On 5/1/07, Jorge Fernandez wrote:
> Hi Thilina,
>
> You were right. The problem was in TCPMon. Without using TCPMon, I don't
> even have the problem sending big files. Thanks a lot.
>
> I ha
Messsage traces please..:)
On 5/1/07, Jorge Fernandez <[EMAIL PROTECTED]> wrote:
Hi Thilina,
You were right. The problem was in TCPMon. Without using TCPMon, I don't
even have the problem sending big files. Thanks a lot.
I have one more question now that this problem was fixed: Is there any
sa
age without making a copy. Thank you.
- Original Message -
From: "Thilina Gunarathne"
To: ;
Sent: Sunday, April 29, 2007 11:19 PM
Subject: Re: Help with SwA
There was a known bug in Axis2 1.1.1 which prevented the last boundary
being written to the wire in the case of runn
t; <[EMAIL PROTECTED]>
To: ; <[EMAIL PROTECTED]>
Sent: Sunday, April 29, 2007 11:19 PM
Subject: Re: Help with SwA
There was a known bug in Axis2 1.1.1 which prevented the last boundary
being written to the wire in the case of running Axis2 in Tomcat ...
This was fixed in the latest 1.2
Hmm.. Then this might be something else...
Have you tried this without TCPMON...
~Thilina
On 4/30/07, Jorge Fernandez <[EMAIL PROTECTED]> wrote:
Hi Thilina,
I didn't have that problem in axis2 1.1.1 but now I'm using the last 1.2
release and I'm having that problem.
Regards,
--
Thilina Gu
tely by telephone or email and destroy the original
> > message without making a copy. Thank you.
> >
> > - Original Message -
> > *From:* Jorge Fernandez
> > *To:* axis-user@ws.apache.org ;
> > [EMAIL PROTECTED]
> > *Sent:* Su
rge Fernandez <mailto:[EMAIL PROTECTED]>
> *To:* axis-user@ws.apache.org <mailto:axis-user@ws.apache.org> ;
> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
> *Sent:* Sunday, April 29, 2007 11:23 AM
> *Subject:* Re: Help with SwA
>
> Hi Thilina,
>
>
ECTED] <mailto:[EMAIL PROTECTED]>
*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
attac
Thank you.
- Original Message -
From: Jorge Fernandez
To: Martin Gainty ; axis-user
Sent: Sunday, April 29, 2007 5:52 PM
Subject: Re: Help with SwA
Hola Martin,
Thank you for the information. I don't know if there is a JIRA. But I think
it's strange this bug when in the pr
original
message without making a copy. Thank you.
- Original Message -
From:Jorge Fernandez
To: axis-user@ws.apache.org ; [EMAIL PROTECTED]
Sent: Sunday, April 29, 2007 11:23 AM
Subject: Re: Help with SwA
Hi Thilina,
With the new release that seems to work
troy the original
message without making a copy. Thank you.
- Original Message -
From: Jorge Fernandez
To: axis-user@ws.apache.org ; [EMAIL PROTECTED]
Sent: Sunday, April 29, 2007 11:23 AM
Subject: Re: Help with SwA
Hi Thilina,
With the new release that seems to work
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:
org.apache.axiom.om.OMException: javax.mail.MessagingException: Error reading
input stream;
nested excep
org.apache.axis2.AxisFault: Invalid Application type. Support available for
MTOM & SwA/SOAP 1.l only.; nested exception is:
org.apache.axiom.om.OMException: 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 t
Hi,
I'm trying to send a file with SwA from the service to the client and I'm not
sure how to do it. When I set enableSwA parameter to true in the operation in
the service.xml I get the exception:
org.apache.axis2.AxisFault: Invalid Application type. Support available for
MTOM & SwA/SOAP 1.l o
Hi,
See my comments inline
On 7/19/06, Ben Malek, Hamid <[EMAIL PROTECTED]> wrote:
I have a big problem making Axis2 work fine with SwA.
1.The first problem is that I could not find any documentation on how to
programmatically construct a SwA SOAP message using AXIOM API only. You can
o
I have a big problem making Axis2 work fine with SwA.
1.
The first problem is
that I could not find any documentation on how to programmatically construct a
SwA SOAP message using AXIOM API only. You can only construct MTOM SOAP
messages with Axiom but not SwA. The example of SwA given
26 matches
Mail list logo