parsing blueprint elements on EBA install

[Joe Bohn]

When processing an application (EBA) we parse all of the blueprint.xml 
(including custom namespaces) as part of the application processing for 
all bundles within the EBA.  The net result is that we do all of this 
parsing twice because we also must parse and processes the information 
in the BlueprintContainer.

Why is it necessary to parse the blueprint.xml during EBA installation 
in the application module?

I stumbled on this because I was making some modifications to a custom 
namespace handler and noticed that it was being invoked twice for the 
same elements.  It seems that this is not desirable.  Should all 
namespace handlers be coded in such a way that they can be invoked 
multiple times for the exact same elements?

--
Joe