This whole question turns out to be the following: Is it a valid JAX-WS/JAX-B thing to annotate a plain old String bean property for MTOM, and expect MTOM to happen? If so, then I need to determine if the failure to do so is us or JAX-B, and if the latter we have to decide if we care enough to contemplate some sort of workaround.
On Mon, Aug 25, 2008 at 10:17 AM, Daniel Kulp <[EMAIL PROTECTED]> wrote: > > I don't think there is a way to set the threshold in the wsdl. You can turn > it on with a ws-policy fragment, but you cannot set the threshold that way. > > If it's jaxws, the easiest way to go about it would be to add a: > @MTOM(enabled = true, threshold = 1000) > annotation onto the interface/impl. > > You can enable mtom via configuration. Just set mtom-enabled property on the > bean. systests/src/test/resources/mtomTestBeans.xml > I don't think you can control the threshold that way. To control that, you > probably need to create a JAXBDataBinding object and set the mtomThreshold > property on that and set that into the service. > > > Dan > > > On Sunday 24 August 2008 10:03:20 pm Benson Margulies wrote: >> What does one put in a WSDL to mark a service as MTOM and to set the >> threshold? Or, if there isn't any, how does one push a relevant >> property onto a CXF client proxy? >> >> I'm trying to mop of CXF-1395, and I think that the problem is that >> the client isn't bothering to use MTOM at all, presumably because >> there isn't 4K of text. > > > > -- > Daniel Kulp > [EMAIL PROTECTED] > http://www.dankulp.com/blog >
