Problem by BPEL process compilation with JDeveloper

Question

Hi,
I don't quite know whether my problem is in the JDeveloper forum or Oracle Process Manager one.
I am currently trying to execute a process, with dynamic invocation and dynamic management capabilities, but I won't go into technical details. In the WSDL Definition for the process I have defined 2 partnerLinkTypes - one for the standard synchronous request/response (receive-reply) and one for my management port (asynchronous receive).
The end of the WSDL Definition is as follows:
<portType name="ConfigurationPort">
<operation name="ConfigurationChanged">
<input message="client:ConfigMessage"/>
</operation>
</portType>
<portType name="DynamicDBServiceProcess">
<operation name="process">
<input message="client:DynamicDBServiceProcessRequestMessage"/>
<output message="client:DynamicDBServiceProcessResponseMessage"/>
</operation>
</portType>
<plnk:partnerLinkType name="DynamicDBServiceProcess">
<plnk:role name="DynamicDBServiceProcessProvider">
<plnk:portType name="client:DynamicDBServiceProcess"/>
</plnk:role>
</plnk:partnerLinkType>
<plnk:partnerLinkType name="ConfigPartner">
<plnk:role name="Reconfigure">
<plnk:portType name="client:ConfigurationPort"/>
</plnk:role>
<plnk:role name="ReconfigureResponse">
<plnk:portType name="client:ConfigurationPort"/>
</plnk:role>
</plnk:partnerLinkType>
The JDeveloper BPEL compiler is supposed to generate the binding and service tags for my abstract portTypes, but the binding and service for my ConfigurationPort are somehow wrong generated:
<binding name="DynamicDBServiceProcessBinding" type="tns:DynamicDBServiceProcess">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="process">
<soap:operation style="document" soapAction="process"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
</binding>
<binding name="ConfigurationPortBinding" type="tns:ConfigurationPort">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="ConfigurationChanged">
<soap:operation style="document" soapAction="ConfigurationChanged"/>
<input>
<soap:header message="tns:WSARelatesToHeader" part="RelatesTo" use="literal" encodingStyle=""/>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="DynamicDBServiceProcess">
<port name="DynamicDBServiceProcessPort" binding="tns:DynamicDBServiceProcessBinding">
<soap:address location="http://I71NB60:9700/orabpel/default/DynamicDBServiceProcess/2.4"/>
</port>
</service>
<service name="ConfigurationPortService">
<port name="ConfigurationPortPort" binding="tns:ConfigurationPortBinding">
<soap:address location="http://set.by.caller"/>
</port>
</service>
I tried to find some configuration property for the project in order to properly modify the generation of my soap:address location (it surely isn't http://set.by.caller/). Nevertheless the process compiles fine and is successfully deployed, but at runtime an exception is generated because of "java.sql.SQLException: [POL-3221] Null-Schl?ssel in prim?rem Index" (trying to insert a NULL key in the primary Index). Has anyone know how to tune my project (or compiler) settings in order to generate a proper binding and service?
Best regards,
Genadi Genov

Answer 1

Try posting on the BPEL forum BPEL