I spend a lot of my time working out how best to convey information. Sometimes, this means creating and giving presentations, but I also do quite a bit of writing.
Yet deciding how to structure a written document has gotten harder. Books are too slow for most of what I do--updatable papers on the web are better. Still, no matter how good a paper might be, it has no value if people don't read it.
After you've hopefully read the short little introduction to xPaaS you're excited to try out all the new features and just want to get started without further reading? That is easy. The only true prerequisite for everything you do around xPaaS is an OpenShift account. And believe it or not, it is free. Like in free.
Since Camel version 2.10 there is support for CDI (JSR-299) and DI (JSR-330). This offers new opportunities to develop and deploy Apache Camel projects in Java EE containers but also in standalone Java SE or CDI containers. Time to try it out and get familiar with it.
What exactly is Camel?
I've been reading a lot about Red Hat products lately and being interested in cloud and such since some years now, it's pretty obvious for me to look into the cloud offerings from Red Hat in more detail. Arun did a great overview about JBoss xPaaS back in April this year and I thought it might be time to not only give you an overview but also point you to all the relevant information that interested developers need to know about.
From the ORCL New Features Doc -
The Process Asset Manager (PAM) is BPM’s business process repository used to provide seamless collaboration across BPM Process Composer and BPM Studio clients. Both these clients publish projects to PAM which interfaces with source control for versioning and management of BPM assets. Key attributes of the Process Asset Manager are:
» BPM Project lifecycle management
» Integrated source control and versioning
Let's debug the fault handling demo process, from the previous post - in that scenario
process A (callingProcess) called process B (calledProcess) via the Validate activity.
Here is the calling process