Hehehe...i asked the same question #1 last week when i met Eran in Synapse F2F. Eran, Please check if my understanding below is correct.
Suppose you are building an om structure by reading stuff from a stream and you are half-way through it you want to serialize everything (including the stuff for which OM has not been built in memory) then you can call serialize. So AFTER you serialize you lose the info for which om was not built already. So if you want to build the OM *AND* serialize the input to output, then you call serializeWithCache. Need to check on #2 -- dims On 9/30/05, Eric Johnson <[EMAIL PROTECTED]> wrote: > I've got two OM questions at the moment: > > 1) What the heck does "OMNode.serializeWithCache()" mean? How is it > different from "OMNode.serialize()"? I was hoping to put some Javadoc > on the function(s) but couldn't figure out from inspection what the > substantive difference was. > > 2) What is the OMText "optimized" property? It is never set via > "setOptimized", and never inspected via "isOptimized." I'm guessing > that this was meant to be the "optimized" part of MTOM, but since it is > never set or used, is it worth keeping? > > -Eric. > > -- Davanum Srinivas : http://wso2.com/ - Oxygenating The Web Service Platform
