I did some work to make xmime work in Aegis, and I hit one bug in JAXB. Certainly your fragment is wrong isofar as it uses xmime:expectedContentTypes without including that schema. Have you tried just using JAXB tools and seeing what you get for generated code?
On Thu, Jun 18, 2009 at 2:26 PM, bharath thippireddy<[email protected]> wrote: > In our wsdl files for services which use MTOM we have the following element > declaration. > > > > <xsd:element name="AppData" type="xsd:base64Binary" > xmime:expectedContentTypes="application/xml,application/zip,application/x-gzip"/> > > > > When we run the WS-I validation against the wsdl it fails with the following > exception > > > > Assertion: BP2122 > > > > Result > > failed > > Failure Message > > A wsdl:types element contained a data type definition that is not an XML > schema definition. > > Failure Detail Message > > Schema is structurally invalid. > > Fatal error: The prefix "xmime" for attribute "xmime:expectedContentTypes" > associated with an element type "xsd:element" is not bound. > > > > > > The validation passes if we change the type to type="xmime:base64Binary".This > requires a new xmime schema to be imported. > > But the code that gets generated uses byte[] instead of DataHandlers.Looks > like the wsdl2java ignores the xmime:expectedContentTypes if the type is not > xsd:base64Binary .Is this a bug in CXF? > > > > What is the recommended approach? > > > > Thanks and regards, > > Bharath > >
