A comment from Mark Maden on my recent blog "Thoughts on the Problem of XPages" prompted me about a potential area XPages could add value for the future. One of the strengths of XPages from the start has been flexible reporting.

A common request seems to be how do I use XXXX Java or JavaScript project in XPages. One of the strengths of XPages was that it made the approaches more standard. So the answer is often less an XPages question, and more a generic web development question. There are a few caveats, but many of those are standard for web development.

Jesse Gallagher posted a thoughtful blog about the challenges for the way forward with XPages. It's a challenge I've had a number of discussions around, many of which are ongoing. The reason there's not a simple solution - throw whatever resources are required into XPages - is that it simply doesn't make business sense.

In part one we covered Notes Client and XPages. In part two we covered Domino Mobile Apps. Technically, with both the previous parts we’ve covered interacting with a Domino application via a REST service. That’s nothing new – a LotusScript agent could have been a poor man’s REST service endpoint.