Hi Dan
If that's the case then agreed. I misunderstood the original usecase. My point is that such a great CXF feature as its
policy-awareness should be utilized more when feasible...but yes, in this case it wouldn't help. Policy expressions don't have to
live in wsdls but it's only (?) when they do can they help client to avoid duplicating the configuration...
Remember, the world doesn't have to revolve around wsdl and stuff stuck
in wsdl.
Agreed. Reality check :-)
Cheers, Sergey
Sergey,
On Tuesday 21 August 2007, Sergey Beryozkin wrote:
I'm wondering, why there's a need to configure MTOM explicitly on the
client side ? CXF is policy-aware, so if the service' WSDL contains a
non-optional MTOM WS-Policy assertion then the client runtime should
consume it and do MTOM. The thing is, the server has already expressed
a requirement to have messages MTOMed, so this should be sufficient.
One of the purposes of WS-Policy expressions is to mimimize the need
for a client-side configuration.
Well, if you are doing complete code first development (no wsdl involved
at all), there currently isn't an easy way to enforce WS-Policy
expressions or to add the ws-policy stuff to the wsdl generated with
the ?wsdl call. The client may not even be using a WSDL. It could
be just using the interface and and endpoint URL. It doesn't have to
query for a wsdl if it doesn't want too.
Remember, the world doesn't have to revolve around wsdl and stuff stuck
in wsdl.
Dan
Cheers, Serge
----- Original Message -----
From: "Willem Jiang" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, August 21, 2007 9:33 AM
Subject: Re: enable MTOM client
> Hi,
>
> You can take [1]'s inlineSoapBinding bean as a example to configure
> the MTOM on the client side.
> [1]https://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/frontend/
>jaxws/src/test/java/org/apache/cxf/jaxws/spring/clients.xml
>
> Willem.
>
> nuka wrote:
>> I didn't configure MTOM on the client side. The only configuration
>> I've made is
>> - jaxws endpoint configuration for MTOM (beans.xml)
>> - MIMEType annotation application/octet-stream for the binary data
>>
>>
>> I don't know how to configure the client via xml (or by code). I
>> use jaxws as frontend. I saw that the client can be configured by
>> xml (in the beans.xml file ) but I don't know how. I would
>> appreciate if you can show me a sample.
>>
>> thanks in advance
>>
>> Nuka
>>
>> Dan Diephouse wrote:
>>> What does your client code look like? You probably aren't
>>> configuring MTOM right on the client side.
>>>
>>> Cheers,
>>> - Dan
>>>
>>> On 8/20/07, nuka <[EMAIL PROTECTED]> wrote:
>>>> Hello,
>>>>
>>>> I have some problems when enabling MTOM for CXF generated client.
>>>> I've made the configuration for MTOM as suggested in the user
>>>> guide for both
>>>> client and server side.
>>>>
>>>> - jaxws endpoint configuration for MTOM (beans.xml)
>>>> - MIMEType annotation application/octet-stream for the binary
>>>> data
>>>>
>>>>
>>>> The server is ok, its responses support MTOM. But the client
>>>> requests are not MTOM based. The binary data is embedded in the
>>>> SOAP body.
>>>>
>>>> I believe I've missed something on the client side configuration
>>>> but I don't
>>>> know what.
>>>>
>>>> Thanks in advance
>>>> Nuka
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://www.nabble.com/enable-MTOM-client-tf4300910.html#a12242043
>>>> Sent from the cxf-user mailing list archive at Nabble.com.
>>>
>>> --
>>> Dan Diephouse
>>> Envoi Solutions
>>> http://envoisolutions.com | http://netzooid.com/blog
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4,
Ireland
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194
[EMAIL PROTECTED]
http://www.dankulp.com/blog
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
