On 31/03/2009 09:48, "Andreas Veithen" <andreas.veit...@gmail.com> wrote:
> Frank,
>
> MTOM is a _transparent_ way of optimizing messages. Why does the WSDL
> explicitly reference xop:Include?
That is a very good question... And not one I can answer immediatly.
I am 'new' to MTOM, that is, I learned it about 2 months ago, and I learned
it through gSOAP. At the level of gSOAP (in C++), it is not transparent... I
think I see at that level the 'processed' message with it's attachments.
What you are saying is that the WSDL should in fact contain a binary blob
there, with mime type attribute, instead of the xop:Include object.
Makes sense, but then I have to investigate how I can make such a setup with
gSAOP (where I start from C++ classes...)
Thanks for the input
Frank
>
> Andreas
>
> On Mon, Mar 30, 2009 at 18:18, Frank Vyncke <frank.vyn...@esko.com> wrote:
>> I,
>>
>> Am starting to develop a 'client' for a gSOAP based server, using MTOM
>> attachments.
>>
>> I have a wsdl file, but when I try to compile the wsdl file, I get an
>> exception with the following message:
>>
>> Caused by: org.apache.axis2.schema.SchemaCompilationException: can not find
>> the element {http://www.w3.org/2004/08/xop/include}Include from the parent
>> schema http://www.genivia.com/schemas/mtom_stream_test.xsd
>>
>> Can anyone tell me where this error comes from, because the wsdl file does
>> import the http://www.w3.org/2004/08/xop/include schema correctly (I think,
>> there is no way I can check if it really imported the schema or not).
>>
>> Thanks
>> Frank
>>
>>
