I'm not sure how children is implemented in the engine but I do know
that olap4j offers selection modes (including children, member... etc)
that are the same as all the one implemented in the halogen gui. So
you wouldn't have to directly parse the MDX and (in the case of
children) iterate all the children of a given member. olap4j will do
that for you. In other words once you've parsed a member selection
and found that it's children then you just need to select children on
that member in olap4j.
Bill