A very long time ago I wrote a fifty something long blog series about learning XPages where I wrote a simple phonebook type application. It was pretty well received and probably helped a few people get on the road to writing XPage style applications. It was basic, it didn’t involve any Java backend stuff and I know if I was doing it again in XPages I would do it completely different.
Now we have a brand new development stack and I find myself back at the starting blocks again but this time I am armed with the java knowledge I learnt during my time writing XPage apps, I have my development, build and release environment mapped out and it is time to start writing code again.
I’m not going to try and duplicate the old Learning XPages series but I am going to try and work though an entire application from start to finish where the finish line is having the application automatically deployed on our production environment. I won’t be going in to the code at the level I did for Learning XPages but I will point out how similar concepts in XPages translate over to my Java application but this is not a Learning Java series or a Learning Spring series.
This is going to be part Code, part Spring, part Thymeleaf, part DevOps, part VSTS, part Docker, part Rancher. Pretty much everything I have described in the last few blog about what it takes to replace Domino. I’m going to show you how I’m using it so that if you decide on similar parts for your Domino replacement stack you will have a basic understanding of how to get things going.
And I’m not numbering the parts this time 🙂
“Decs Dom Blog” 🙂
Modern dev is all about the DOM tree 🙂
Dec sounds great – that’s stack I use on a daily basis. Thing I find great is mocking up objects and mapping to data structures using JPA – tables created in an in memory sql database – it’s like magic…well maybe not quite.