Ajith, we can't override what they generate, i just want us to note which elements are marked by the xmime stuff and do the needful at runtime (extract the contents that are base64'ed and then MTOM-it)
-- dims On 9/1/05, Ajith Ranabahu <[EMAIL PROTECTED]> wrote: > Hi Dims, > This is exactly the approach that I have taken. I never call 'scomp' :) . > Instead the schema DOM element is fed into the XMLBeans.CompileXMLBeans() > method to generate a schema type system and then from that I take the > Document types (schemas) and a make a mapping. > Have a look at the XMLBeansExtension class and you'll see how Axis2 > interacts with XMLBeans. > > But I don't think this approach will solve our problem. I mean the real > problem seems to be that XMLBeans does not realize the semantics of the > xmime extension. We may be able to extract which elements are base64 (I have > to check that !) but still the root problem remains. We should get our feet > wet and dig into XMLBeans to solve it :) (Unless the XMLbeans guys have > already done something to make it easy for us :))) > > On 9/2/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > > Ajith, > > > > Could you walk the schema stuff as mentioned here: > > > http://mail-archives.apache.org/mod_mbox/xmlbeans-dev/200508.mbox/[EMAIL > PROTECTED] > > > > "The way I would do it is: compile the schemas using the API > > (XmlBeans.compileXmlBeans ()) instead of using "scomp", get a > > SchemaTypeSystem back and call .globalElements() and .globalTypes() on > > it." > > > > If we can extract enough info from the SchemaTypeSystem, we can store > > it somehow and use it when we have to do MTOM. > > > > thanks, > > dims > > > > > > > > > > -- > Ajith Ranabahu -- Davanum Srinivas : http://wso2.com/ - Oxygenating The Web Service Platform
