You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-dev@axis.apache.org by Eran Chinthaka <ch...@opensource.lk> on 2004/10/28 06:52:08 UTC

[Axis2] - OM and MTOM

Can we introduce a OMBinaryNode to OM to represent the base64 which are MTOM
compliant.

 

But I have a problem of identifying optimized and un-optimized data in the
parser level. Can we represent everything as Strings, whether optimized or
unoptimized. The Element having the base64 data *may* have some information
in its attributes to identify. But do we have to check all the elements for
this, and what if the element do not have those info, but contains base64
data.

 

Thoughts & Comments .. ??

 

  _____  

Eran Chinthaka

Lanka Software Foundation