JPDL or BPEL

This is the question that any Architect developing solutions on JBoss SOA platform encounters. I found some useful insight on this by the JBPM founder http://processdevelopments.blogspot.com/2007/04/bpel-compared-to-jpdl.html which very much states that JBPM-BPEL is more suited to orchestrate web services while JBPM-JPDL is more suited to orchestrate business objects.(POJOs or EJB)

IMHO, I think BPEL over JPDL is better for the following reasons

1. BPEL is a specification that all vendors comply to.
2. Portability. Any solution that complies to BPEL specification should be portable across another vendor's BPEL engine. This is as long as we do not implement any vendor's BPEL extensions which are not portable. Parallels in portability can be drawn to EJB here. I believe that the specification is going to be more mature over the period of time as all the major vendors IBM, Oracle and Microsoft support it.
3. I would think that the same specification would grow to make a natural fit for POJOs so that there is only one robust business process/workflow engine that does not differentiate between a Web Service and a POJO Service.