Hmm... I think I see what you mean. According to jaxb pdf spec, the text/plain should be mapped to a DataHandler, not a String. Although: http://fisheye5.cenqua.com/browse/~raw,r=1.2/jax-ws-sources/jaxws-ri/docs/mtom-swaref.html seems to imply otherwise.
In anycase, the 2.1 runtime seems to not handle String as mimes at all, always outputting them inline as string. Sounds like another JAXB bug. :-( Dan On Thursday 17 January 2008, Daniel Kulp wrote: > On Thursday 17 January 2008, Benson Margulies wrote: > > Thanks. > > > > Relatedly, if wsdl2java produces 'the wrong thing' in terms of field > > type, is there some wsdl extension to shake it by the lapels? > > I guess the question is: what do you mean by "wrong thing"? > > Dan > > > On Thu, 2008-01-17 at 16:17 -0500, Daniel Kulp wrote: > > > On Thursday 17 January 2008, Benson Margulies wrote: > > > > There is a wsdl for MtoM. It seems to have a fairly simple > > > > structure of types and elements. > > > > > > > > Yet the wsdl2java for it concocts these complex INOUT holders. > > > > > > > > Why? > > > > > > Because the names (and types) of parameters for the INs match the > > > names of the OUTS. Thus, the spec state that those are to be > > > considered INOUT parameters which thus require Holders. -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog
