It sounds plausible that ARIES-361 introduced this. I haven't looked at
earlier versions to determine if is something new.
Joe
On 9/27/10 2:22 PM, Lin Sun wrote:
Hi
Is this behavior only existing in trunk?
My guess is that this is introduced by
ARIES-361 which includes extensions to OBR
that enable the OBRAriesResolver to provision against service dependencies
inferred from individual bundles'<service> and<reference> blueprint
elements.
Lin
On Mon, Sep 27, 2010 at 2:02 PM, Joe Bohn<[email protected]> wrote:
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
--
Joe
