This article is Part 10 in a 11-Part Series.
- Part 1 - Servlet Basics
- Part 2 - Servlet Implementation
- Part 3 - Handling Requests in a Servlet
- Part 4 - Interlude for Servlets
- Part 5 - Handling Data in a Servlet
- Part 6 - A Video on Servlets
- Part 7 - From XAgents to Servlets
- Part 8 - Building a Front-End, pt.1
- Part 9 - Building a Front-End, pt.2
- This Post: Part 10 - The Road Goes Ever On and On
- Part 11 - Rebirth: An App of Ice and Fire
The Road Ahead
This past week saw the completion of a series born of a couple discussions at IBM ConnectED at the end of January, combined with my musings on application structure and realizations from having been working on a couple large XPages applications since my first adoption of the platform over three and a half years ago.
My series is imperfect and doesn’t cover ideal ways of rolling an HttpServlet, but it does show the concept and the ability to do so within an NSF with minimal external server configuration. I’m excited for Toby Samples to follow up to his first post on getting JAX-RS up and running on Domino, as it accomplishes considerably more in the realm of automation of endpoint definition, documentation, and some of the hurdles involved with my ridiculously vanilla, NSF only based approach.
This isn’t a bad thing. When I started my series, only a couple proof of concept examples were out there on using a straight javax.servlet.http.HttpServlet, or geared towards OSGi plugins. These are great topics, but I wanted something self-contained and more approachable to those who aren’t as versed in OSGi plugin deployment. OSGi plugins have great power, I’m just not as experienced with them yet and nowhere near comfortable blogging about it.. yet. Tomorrow is always a new day 😃.
Adventure Is Out There!
I forced myself to blog about the subject and hold as few assumptions as possible. When it came to my preference to GSON, I also included a version using the IBM commons library. This sets up a considerable amount more of what I would like to build on. I also wanted to get the conversation away from “how do I start”, to something more constructive, like “what’s the best way to do this?” I think I’ve accomplished establishing a small base of reference from which we can all build off of. That’s what I set out to do.
But Eric, You Didn’t Cover …XYZ!
My AngularJS (side of my) app effectively became a shotgun of a delivery. I was tired of talking about theory, but lots of people have covered AngularJS principles, foundations, and more; so I hit on the key points and just figured you were along for the ride 😉. Several of those people are in the XPages development community and there are many outside who develop AngularJS with <insert back-end> for their RESTful API. That’s the beauty of this approach, you can use all kinds of universal resources to learn, as it’s industry-norm and not specific to our application platform.
So no, I didn’t cover everything explicitly, but to read up on how and why my AngularJS code is how it is, just check out some AngularJS fundamentals in 60-ish minutes and then on using ui-router. Seriously, if you can walk yourself through an AngularJS app and ui-router principles, you’re good to go. I didn’t do much in my demo app far out of the “reading level” of most AngularJS examples and it was a good demonstration of standardization of application structure in the front-end.
Let’s Take a Walk
You never know what you’ll find when you step out of your usual norms. Without stressing ourselves out of our comfort zones, we don’t always find what we’re capable of. I’m still a developer learning many things, I’m just lucky to count myself in the company of those who have a similar thirst for knowledge and willingness to share their triumphs and tribulations.