My Oracle Support Banner

BPEL PM throws Errors when Omitting Revision Number in Endpoint Url (Doc ID 428999.1)

Last updated on APRIL 23, 2019

Applies to:

Oracle(R) BPEL Process Manager 10g - Version 10.1.3.1 and later
Information in this document applies to any platform.

Symptoms

Deployed the BPEL project and run the end point url.

This would end successfully, producing the output shown below :

soap length=379 
Process Initialisation ---> SUCCESS! 
<env:Envelope 


xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Header/><env:Body>< 

TestProcessResponse 
xmlns="http://xmlns.oracle.com/Test"><result 

xmlns="http://xmlns.oracle.com/Test">Test 

PARTNER!</result></TestProcessResponse></env:Body></env:Envelope> 

Later, removed the revision version /1.0 from the 'Test' project directory and then run the project using Ant in JDeveloper . This displays the following errors :

soap length=379 
Process Initialisation ---> ERROR! 
<env:Envelope 


xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Header/><env:Body>< 

env:Fault 


xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>env:Server</f 

aultcode><faultstring> 


java.lang.NullPointerException</faultstring><faultactor></faultactor></env:Fau 

lt></env:Body></env:Envelope> 


This means that the BPEL PM refuses to use default revision when omitting revision number in endpoint url.




Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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