I was invited to present portal at the Java CAPS Apostles Conference last week @ Singapore. This conference involves Sun Partners, Sales folks around Java CAPS, some around Portal, Java CAPS System Engineering, Partners and Solution Architects who are responsible for customer implementations, POCs, RFPs etc. The conference usually highlights features of Java CAPS and things being done around it by other products.
This was an opportunity to showcase things being done around the Portal product, Portal around JavaCAPS integrations, NetBeans tooling.
For details regarding what all was presented, which hands on exercises were done, what CDs were distributed, please check out my blog. The conference concluded on a very positive note, giving great food for thought to everybody about integrating Portal with Java CAPS.

In my previous blogs, I referred to my article on how to incorporate
workflow into portals with Java CAPS. The article used portlets as a
mechanism to interact with the user. However, it did assume that the
end user has a knowledge of how to use the Java CAPS APIs.
Traditionally, performing tasks on multiple portals is tedious and
inefficient as enterprises adopt back-end business processes and must then
continually manage them. Hence, demand has steadily mounted for the capability
to perform tasks on just the portal itself instead of on multiple sites with a
single-point solution; that is, a solution that not only handles the process
interactions but also enables end users to seamlessly perform tasks as "hooks"
in the process.



