Some 'more, in-depth' information on Oracle BPEL PM, ESB and other SOA, day2day things

Wednesday, May 31, 2006

BPEL 10.1.2.0.2: Dynamic Endpoints cause NPE

On the forums there was a long discussion on Dynamic Partner links, and after all Koen has found the solution, that represents another impact of a know bug.

In some cases IDE adds whitespaces to entries (breaks before and after the value), and at some points this proves to be specially enoying. One is in the setText() XPath function within a stylesheet transformation (XSL) - especially here a develper usually want to make sure that the exact amount of digits is set. Another one that showed up is when using dynamic partnerlinks.

Quoted is his answer, also to be found here

In the literal xml fragment in the copy-statement, JDeveloper generates whitespaces and newlines, every time you use the designer, even without actually editing the bpel.

Example:

<copy>
<from>
<EndpointReference
xmlns="http://schemas.xmlsoap.org/ws/2003/03/addressing">
<Address>
http://localhost/broker/Repository/MailStorage.asmx
</Address>
<ServiceName
xmlns:ns7="http://coplintho.ibbt.be/broker/repository/">
ns7:MailStorage
</ServiceName>
</EndpointReference>
</from>
<to variable="partnerReference"/>
</copy>
One must delete these whitespaces and newlines manually every time before building the process.


I guess this is a great example of collaboration on our BPEL forums, and something we are very proud of..

An a public thanks you to all our fellows anserwing questions.

1 Comments:

Anonymous Sean Carey said...

Clemens, there's a way to modify this example such that this bug will not occur with each deployment of the process. See my article here: http://www.oracle.com/technology/pub/articles/bpel_cookbook/carey.html in the section "Creating a Dynamic BPEL Process", step 7.

1:25 AM

 

Post a Comment

<< Home