Well I missed noticing your second part of the email…
The selling point for CAF is mainly due to the tight integration it has with IS. IS flow services can be easily dragged on to your page and you get the basic functionalities implemented without writing any code in your web application.
So the basic guideline for choosing between CAF or JSF is simple…If you have good amount of logic residing in flow services which can be re-used for your web application, CAF “can” be the choice. If there is no IS involved in your web application better develop them using JSF and get them deployed in other web servers.
Also you need to think twice if you are creating new flow services to be used exclusively in your CAF application as IS can often be the bottleneck from performance point of view. We recently had to swtich to pure java/jdbc connectivty (from WS connector) option for our custom reporting application developed in CAF for want of performance.
Hope this gives you some idea.
Regards,
Balachandar
#MWS-CAF-Task-Engine#webMethods#webMethods-BPMS