Hi, I was actually going to write a long explanation for this but I see Anne has done it (quite completely I should say) some time back. Thanks Robert for pulling it out from the archives. in the Axis2 setting, If you use XMLBeans, it'll actually correctly mark the OM elements for optimization. So if you've codegned for the optimized schema you should automatically get the optimized wire message.
Ajith On 3/23/06, Michael Meire <[EMAIL PROTECTED]> wrote: > Dear, > > I guess my question is related. > > The problem I'm facing is the following: I am creating a webservice, > starting from a WSDL file. I need file attachments, and therefore I want to > use MTOM. > I also need some kind of "inheritance" and therefore I'm creating complex > types that are extensions of other types. Concretely I include something > like the following: > > <xsd:complexType name="abc"> > <xsd:complexContent> > <xsd:extension base="xyz"> > <xsd:sequence> > <xsd:element name="loFileZipped" > type="xsd:base64Binary"/> > </xsd:sequence> > </xsd:extension> > </xsd:complexContent> > </xsd:complexType> > > > My experiences so far with Axis2 v0.94 are the following: > > > when using wsdl2java using ADB, the abc-type is not taken into account ==> > no java class corresponding to this type is generated > when using wsdl2java using xmlbeans, an abc-javaclass is generated, > including a variable byte[] getLoFileZipped() > So this option seems to do the trick for me. However, in this case, I can't > get MTOM working. The byte array is sent as inline xml within the SOAP > message. > I have (as far as I know) followed the instructions for using MTOM. I also > successfully tested the MTOM sample that is included in the Axis2 > distribution. > I think basically my question comes down to: > how can I use extension-complextypes in my wsdl, and still be able to use > MTOM... > > Any hints or suggestions on this are of course welcome... > > thanks very much in advance, > best, > Michael... > -- Ajith Ranabahu
