if ws-sec is turned on, then we force a build of the om tree...just like we do now.
-- dims On 3/31/06, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: > On Fri, 2006-03-31 at 10:55 -0500, Davanum Srinivas wrote: > > Let me try again...The DB framework will build the java objects > > directly from the MIME root part (this is the first step always!) and > > *then* accesses the other mime parts and sticks them where it is > > needed (or adds a reference) on the java objects that it already > > created. Except that OM tree is *never* built. > > Ah but that's inconsistent with XOP .. if you do XOP, then when you look > at the XML at the Infoset level (which is what you do when you look at > the root part thru Axiom) then you have to un-XOPify it and just see the > XML Infoset. There's no halfway point. > > What you're looking at is SwA .. MTOM is not that IMO. > > I guess we could put a flag saying "don't unXOPify" but that seems like > a hack. > > > And on the sending > > side, it generates stax events directly from the the java objects into > > the MIME root part and adds the attachments into a bag while it is > > doing so...again no OM tree in the picture at all. > > Again, you're thinking like SwA and not like a single unified Infoset > that has the binary parts logically in it. Think of WS-Security- how > will your model work with WS-Sec turned on to sign the whole shebang? > > Sanjiva. > > -- Davanum Srinivas : http://wso2.com/blogs/
