Hi, A "shim DOM" is a DOM implementation on top of OM. This means that we will be able to build a DOM tree (DOM refers to w3c standard DOM) from a previously built OM tree. The reason for having such a shim DOM is to facilitate features such as WSS4J (which are written on pure DOM) About spec compliance. Well I do believe that specifications are important which ultimately allow our client/server to be interoperable. Just as you mentioned there will be lot of people who wish to try out axis using there own clients and spec compliance is specially important in this sense (to some level beyond the wire down to the API as well) We at Axis2 are not against specs at all :).What we believe is that the core needs to be "spec-neutral". No specification is assumed in the core. this is exactly what has been done in Geronimo which has a "non-J2EE-aware" core. So similarly we are developing a simple and fast core which has no built in support for any of the specifications, but such specification support can easily be layered upon.
Hope this gives you some insight to the Axis2 way of looking at things :) On Fri, 11 Mar 2005 12:44:40 +0530, jayachandra <[EMAIL PROTECTED]> wrote: > Sry, forgot the [Axis2] prefix in the subject. > Resending with [Axis2] prefixed in the subject. > > -- Ajith Ranabahu
