I have  a contribution that contains a composite with a component with
implementation.bpel. The actual .bpel file is in a separate contribution.
I've been getting an error reported telling me that the system can't find
the BPEL implement file referenced by the implementation.bpel element.

The bpel file itself is found correctly by contribution processing and is
added to the ExtensibleModelResolver. When the implementation.bpel artifact,
in a separate contribution, is resolved it can't find the bpel artifact to
which it refers as each contribution has a separate ExtensibleModelResolver.

Can someone explain to me how the namespace import/export function is
intended to be invoked in this situation? Do we need a bpel model resolver
that is able to extract the required namespace from the bpel script and make
it available for other contributions to import?

Simon

Reply via email to