How we use XPages 

By Sean Cull | 8/19/19 7:43 AM | App Dev - XPages | Added by John Oldenburger

Cameron, Jesse and Paul have been putting a lot of effort into explaining how they use XPages and it has prompted me to post this on how we at FoCul use XPages, something I have been meaning to do for a while. I will hopefully post more about why we like XPages so much but this is a long enough read for now.

Developing Open Liberty Features, Part 2 

By Jesse Gallagher | 8/19/19 12:07 AM | App Dev - XPages | Added by John Oldenburger

In my earlier post, I went over the tack I took when developing a couple extension features for Open Liberty, and specifically the way I came at it with Tycho. Shortly after I posted that, Alasdair Nottingham, the project lead for Open Liberty, dropped me a line to mention how programmatic service registration isn't preferred.

Developing an Open/WebSphere Liberty UserRegistry with Tycho 

By Jesse Gallagher | 8/17/19 11:10 AM | App Dev - XPages | Added by John Oldenburger

In my last post, I put something of a stick in the ground and announced a multi-blog-post project to discuss the process of making an XPages app portable for the future. In true season-cliffhanger fashion, though, I'm not going to start that immediately, but instead have a one-off entry about something almost entirely unrelated.

Upcoming Webinar – How we are using XPages 

By Cameron Gregor | 8/16/19 9:25 AM | App Dev - XPages | Added by John Oldenburger

If, like me, you’ve been following Jesse Gallagher’s blog you will see he has been putting a lot of thought into ‘the XPages problem’ (where to next for those of us still heavily dependant on XPages). I have been following Jesse’s thoughts with interest as I am hoping to make the right decision for our company about where to focus our efforts on next.

A Possible Role For XPages 

By Paul Withers | 8/16/19 8:19 AM | App Dev - XPages | Added by John Oldenburger

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.

How Do I Use XXXX Java / JavaScript in XPages? 

By Paul Withers | 8/16/19 12:52 AM | App Dev - XPages | Added by John Oldenburger

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.

Thoughts on the Problem of XPages 

By Paul Withers | 8/14/19 8:25 AM | App Dev - XPages | Added by John Oldenburger

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.

How Do You Solve a Problem Like XPages? Redux 

By Jesse Gallagher | 8/13/19 3:49 PM | App Dev - XPages | Added by Oliver Busse

The better part of a year ago, I mused about what to do about the XPages problem. For better or for worse, I'm still musing about it to this day, without a good answer. The nice part for me is that it's not actually my job to come up with a real plan to "solve" XPages in a grand scale, but I do have my own set of clients I'm responsible for, and I've been personally invested in it for so long that I'd like to be involved in bringing it to a safe landing.

Modernising Domino Applications: Technical Deep Dive Part Three 

By Paul Withers | 7/25/19 3:30 AM | App Dev - XPages | Added by John Oldenburger

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.