My Oracle Support Banner

JDeveloper Compile Errors After Adding A Component To A SOA Suite Composite (Doc ID 2948693.1)

Last updated on MAY 22, 2023

Applies to:

Oracle SOA Suite - Version and later
Information in this document applies to any platform.


On : version, Deployment

JDeveloper compile errors after adding a new component to a SOA Suite composite

Using JDeveloper a composite is being extended. Currently the composite consists of 46 components: 12 mediators, 27 bpel processes and 7 bpel subprocesses.
It is possible to add 1 component (bpel process or mediator) without compile errors. After adding a second component (bpel process or mediator) a compile results in these errors for another already present component that has not been changed:
Error(168): Parameter "v_input" (by-value) type mismatch in call to "{}DeltaVoegDeelnemerToeInternSubproces" (type "ns1:VoegDeelnemerToeInternRequest", expecting "ns1:VoegDeelnemerToeInternRequest").
Error(169): Parameter "v_output" (by-reference) type mismatch in call to "{}DeltaVoegDeelnemerToeInternSubproces" (type "ns2:VoegDeelnemerToeDeelMutaties", expecting "ns2:VoegDeelnemerToeDeelMutaties"). We cannot extend the compositie as expected. Are we facing limits for the number of components in a SOA Suite composite?


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.