2009/5/5 Daniel Kulp :
>
> OK. That kind of make sense (along with what Eoghan said).
>
> However, I really think there needs to at least be a "README" in the
> distributions that describes a little what it is along with pointers to the
> walkthroughs and such on the website.
I've added a READM
Hi
I think MTOM message should have the attachment info, we could check
that for it. We have some trouble to send the MTOM message if we send
the message in Text model, and Liu Cong is working on the patch.
Willem
Daniel Kulp wrote:
> Doesn't it already support MTOM?
>
> Basically, it provides
Pretty close. Just mentioned on IRC that the source distro needs the
LICENSE/NOTICE things. Other than that, looks much better.
Thanks!
Dan
On Wed May 6 2009 9:10:18 am Eoghan Glynn wrote:
> 2009/5/5 Daniel Kulp :
> > OK. That kind of make sense (along with what Eoghan said).
> >
> > Ho
Thanks Dan, should be sorted in this latest commit:
http://svn.apache.org/viewvc?rev=772302&view=rev
/Eoghan
2009/5/6 Daniel Kulp :
>
>
> Pretty close. Just mentioned on IRC that the source distro needs the
> LICENSE/NOTICE things. Other than that, looks much better.
>
> Thanks!
> Dan
>
>
>
On Wed May 6 2009 9:15:54 am Willem Jiang wrote:
> Hi
>
> I think MTOM message should have the attachment info, we could check
> that for it. We have some trouble to send the MTOM message if we send
> the message in Text model, and Liu Cong is working on the patch.
Hmmthe message won't hav
Hi,
It already supports MTOM. But there may be a bug for the MTOM.
The current implementation send all the messages as TextMessage because
jmsConfig variable in JMSConduit is not initialized according to the
MessageType of SOAPMessage. So it is wrong when the message has an
attachment.
Sorry, I us
Bharath,
Did you get this working?
Basically, the Conduit extends Observable and the client registers a
MessageObserver with the conduit via the setMessageObserver call. On the
incoming message, you would need to setup a Message and just call the
onMessage call of that observer.That sho
Hi,
If we defer the creation of JMS Message until we know the Content-Type
for the client, we still need to flight with the miss configuration of
MTOM with TextMessage on the server side.
Current solution , I discussed with Liu Cong is if the MTOM is enabled,
CXF JMS transport will check the conf
After digging the code, I found we could know if the Message has
attachments by looking the message in the JMSConduit.sendExchange()
method. We can tell if the message is MTOM enabled and has the
attachement message, then we just make sure the JMS Message type is
BytesMessage that should be OK.
BT
If the config doesn't appear in the
WSDL of the service. The current implementation of JMS Transport will
send MTOM message as TextMessage. So in current implementation, if one
wants to use JMS MTOM-support, the config must be set, then the MTOM message will be sent as
ByteMessage.
Willem Jiang
Yes, I confirmed that.
Please feel free to add your comments and patch on the JIRA CXF-1760.
We can add a check point in the JMSConduit.sendExchange() to show some
warning or throw the exception if the user forget to add the messageType
configuration.
Willem
liucong wrote:
> If the config does
11 matches
Mail list logo
