Hi,
I'm not the best person to answer 1. So I'll be leaving it out.
Regarding 2....
An OMText can be used to hold binary data. (isBinary flag is used to track this). A MTOM message can contain Base64 encoded strings together with MTOM optimised parts.Binary data stored in OMText can be serialised either as Base64encoded Strings or as MTOM optimised parts. "optimized" property is used to track whether this binary OMText node will be serialized as Base64 or MTOM. "isOptimized" and "setOptimized" are for the users. Users can use them to decide on the fly whether to optimize or not. Axis2 gives user the full flexibility in choosing :).
You can see the usage of the above methodes in integration/test/o.a.a.mtom.EchoService.
Regards,
~Thilina
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.
--
"May the SourcE be with u"
http://www.bloglines.com/blog/thilina http://webservices.apache.org/~thilina/
