In the case of composites, where you can import using namespace, there is a CompositeModelResolver that handles the specific delegation to others resolvers (e.g CompositeModelResolver). We would need to enhance BPEL processor/resolver to delegate the resolution to model resolvers and then import/export from sca-contribution.xml would work.
On Mon, Jan 26, 2009 at 2:06 AM, Simon Laws <[email protected]> wrote: > 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 > -- Luciano Resende Apache Tuscany, Apache PhotArk http://people.apache.org/~lresende http://lresende.blogspot.com/
