[x3d-public] Side effects of X3DExecutionContext.removeImportedNode and updateImportedNode?

[Bradley Vender <bradley.vender@ndsu.nodak.edu>]

When user code calls removeImportedNode or updateImportedNode, what 
effect does this have on routes to and from the formerly imported node?

Say I have
  DEF A Inline { .... }
  DEF B Inline { .... }
  DEF X NotImportant { ... }
  IMPORT A.SOMENODE AS ANode
  ROUTE X.someField TO ANode.someOtherField
and then in the SAI I call
  updateImportedNode("BNode","ANode",B);
which should have the effect of changing the IMPORT to
  IMPORT B.BNode AS ANode
.  What happens to the ROUTE?  Does it remain unchanged, still 
effectively (in psuedo-X3D)
  ROUTE X.someField TO A.SOMENODE.someOtherField
or does it essentially become like so
  ROUTE X.someField TO B.BNode.someOtherField
?

If there are side effects for changing or removing imports, are there 
similar side effects for changing or removing EXPORT's from inside the 
scene?

My apologies for the above punctuation, but I was trying to keep code on 
seperate lines from text and English got in the way.

--Brad
-------------------------------------------------------------------------
for list subscription/unsubscription,
go to http://www.web3d.org/cgi-bin/public_list_signup/lwgate/listsavail.html