If you are into BPEL programming

Tools are to make your life easier. In BPEL programming tooling is very important, as BPEL can be categorized as a visual programming language, thouhg there’s no such standard on visual notations like in BPMN.
Recently I used Carbon studio on Eclipse Galelio which made it very much easy to model a workflow and generate the BPEL for it. Things like schema processing/visualization for variable types, helps a lot in manipulating them and to avoid alot of selectionFailuers which are the most common errors I encounter in running a BPEL on BPS.
And things like BPEL exporter, saves a lot of time in deploying a process archive and test it.

Avoid namespace verification in xpath processing

Recently I dealt with a lot of xpath expressions, when implementing and it becomes cumbersome sometime to concern on namespaces when it’s not that much essential. We can use Regular expressions to bypass the namespace verfication on xpath.

eg -

<bpel:from part="payload" variable="profileProcessorInput">
    <bpel:query queryLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0">
        <![CDATA[tns:profiles/ns1:Profile[round($itemIterator)]/ns1:club_code]]>
    </bpel:query>
</bpel:from>  

Can be replaced by

<bpel:from part="payload" variable="profileProcessorInput">
    <bpel:query queryLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0">
        <![CDATA[tns:profiles/*[local-name() = 'Profile'][round($itemIterator)]/*[local-name() = 'club_code']]]>
    </bpel:query>
</bpel:from>

University Memos

Today; while my friend Nuwan Ganganath was using my phone, suddenly found few photos; which were taken around four months back. I captured them at the undergraduate division. :).