Hi, Im still not sure I am comfortable with doing the mergin this way rather than through utlity methods. The main reason is there are different strategies to use when merging consider the following
Source: <a/> Default: <a><b/></a> The result will most likely be equal to the "Default" tree. But what happens in the following cases Source: <a><b/></a> Default: <a><b/></a> Do we double the B or replace it? Source: <a><b x="1"/></a> Default: <a><b/></a> Do we double the B or replace it? Source: <a><b x="1"/></a> Default: <a><b y="2"/></a> Do we double the B or replace it or merge it? Source: <a><b x="1"/></a> Default: <a><b x="2" y="2"/></a> Do we double the B or replace it or merge it? etc. Mergin attributes is simple and well understood but the ability of merging trees is less so - which is why we should keep it in a utility method and keep that in excalibur until we are more certain of it. -- Cheers, Pete -------------------------------- My opinions may have changed, but not the fact that I am right -------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
