264 Lotus blogs updated hourly. Who will post next? Home | Blogs | Search | About 
 
Latest 7 Posts
Quick Tip: Override Form-XPage Mapping in xsp.properties
Thu, Jun 11th 2015 17
Parsing JSON in XPages Applications
Thu, May 21st 2015 3
Quick PSA: LS2J Problems in 9.0.1 FP3
Tue, May 19th 2015 6
Quick Tip: Re-Enabling Disabled Designer Plugins
Tue, May 19th 2015 10
How I Use JAX-RS in the frostillic.us Framework
Fri, May 1st 2015 10
Musing About Multi-App Structure
Tue, Apr 28th 2015 12
Building on ODA's Maven-ization
Tue, Mar 31st 2015 6
Top 10
Quick Tip: Override Form-XPage Mapping in xsp.properties
Thu, Jun 11th 2015 17
Things I Rarely Use: sessionScope
Thu, Jul 3rd 2014 12
I Hadn't Thought I'd End The Year Getting Into WebSphere
Wed, Dec 31st 2014 12
Auto-OSGi-ifying Maven Projects
Sat, Mar 28th 2015 12
Musing About Multi-App Structure
Tue, Apr 28th 2015 12
Quick Tip: A View-Filtering Search Box
Tue, Sep 16th 2014 11
I Posted My WrapBootstrap Ace Renderkit
Tue, Sep 30th 2014 11
Using the ODA Design API for File-Resource Manipulation
Wed, Nov 19th 2014 11
Swift
Wed, Jun 4th 2014 10
Arbitrary Authentication with an nginx Reverse Proxy
Mon, Sep 22nd 2014 10




Recent Blog Posts
17
Quick Tip: Override Form-XPage Mapping in xsp.properties
Thu, Jun 11th 2015 1:17p   Jesse Gallagher
This is sort of an esoteric feature, but I just ran across it and it fits nicely into an XPages bag of tricks. Specifically, as it turns out, there's a way to override the default "which XPage should be used for this document?" behavior in some cases. The most-commonly-known behavior is the "Display XPage Instead" set on the form (or the default form if-and-only-if the document has an empty Form field). This wins in all cases, and is the only way to get an XPage to open for a document
3
Parsing JSON in XPages Applications
Thu, May 21st 2015 11:47a   Jesse Gallagher
David Leedy pointed out to me that a post I made last year about generating JSON in XPages left out a crucial bit of followup: reading that JSON back in. This topic is a bit simpler to start with, since there's really just one entrypoint: com.ibm.commons.util.io.json.JsonParser.fromJson(...). There are a few variants of this method to provide either a callback to call during parsing or a List to fill with the result, but most of the time you're going to use the variants that take a Strin
6
Quick PSA: LS2J Problems in 9.0.1 FP3
Tue, May 19th 2015 1:25p   Jesse Gallagher
While I'm at it, I realized that it may be useful to further spread information about the problem that led to me fiddling with the latest IFs and JVM patches in the first place: the LS2J problems in 9.0.1 FP3. Specifically, it's borked. The main way most people have encountered this is via an exception dialog when attempting to add new plugins to an Update Site NSF, since that uses LS2J to accomplish its task - it displays several layers of stack and the upshot is that there's a j
10
Quick Tip: Re-Enabling Disabled Designer Plugins
Tue, May 19th 2015 12:58p   Jesse Gallagher
Recently, I had a case where my installed Designer plugins stopped appearing, immediately made obvious by the libraries disappearing from XPages applications and Designer listing hundreds of class-not-found errors. At first, I figured that the local plugins had been deleted, but trying to install from update sites curtly informed me that they contained nothing new for me. It turned out that my local plugins had been somehow marked disabled by Designer. The fix for this was to go to File
10
How I Use JAX-RS in the frostillic.us Framework
Fri, May 1st 2015 5:59p   Jesse Gallagher
Inspired by Toby Samples's new blog series on JAX-RS in Domino, I'd like to share a description of how I made use of it to write the REST services in the frostillic.us Framework. This is not intended to be a from-scratch introduction - Toby is handling that well so far - but instead assumes a certain amount of knowledge with OSGi development and why you would want to do this in the first place. The goal of my REST services is to provide an automatic REST/JSON API for any Framework model
12
Musing About Multi-App Structure
Tue, Apr 28th 2015 11:25a   Jesse Gallagher
One of the projects I'm working on is going to involve laying the foundations for a suite of related XPages applications, and so I've been musing about the best way to accomplish that. I'll also want to do something similar down the line for OpenNTF, so this is a useful track for consideration. Traditionally, Notes and XPages applications are fairly siloed: though they share authentication information and some configuration via groups, integration between them is fairly ad-hoc. I'm no
6
Building on ODA's Maven-ization
Tue, Mar 31st 2015 7:30p   Jesse Gallagher
Over the weekend, I took a bit of time to apply some of my hard-won recent Maven knowledge to a project I wish I had more time to work with lately: the ODA. The development branches have been Maven-ized for half a year or so, but primarily just to the point of getting the compile to work. Now that I know more about it, I was able to go in and make great strides towards several important goals. As a preliminary note: don't take my current implementations as gospel. There are parts that wi
12
Auto-OSGi-ifying Maven Projects
Sat, Mar 28th 2015 3:15p   Jesse Gallagher
In my last post, I discussed some of the problems that you run into when dealing with Maven projects that should also be OSGi plugins, particularly when you're mixing OSGi and non-OSGi projects in the same Maven build (in short: don't do that). Since then, things have smoothed out, particularly when I split the OSGi portion out into another Maven build, allowing it to consume the "core" artifacts cleanly, without the timing issue described previously. But I ran into another layer of th
7
Tycho and Tribulations
Sat, Mar 14th 2015 2:02p   Jesse Gallagher
For the last few weeks, a large part of my work has involved dealing with Maven, and much of that also involves Eclipse. It's been quite the learning experience - very frustrating much of the time, but valuable overall. In particular, any time OSGi comes into play, things get very complicated and arcane, in non-obvious ways. Fair warning: this blog post will likely start out as an even-keeled description of the task at hand and descending into just ranting about Maven. The Actors To sta
10
Quick Tip: Wrapping a lotus.domino.Document in a DominoDocument
Tue, Mar 3rd 2015 3:13p   Jesse Gallagher
In the XPages environment, there are two kinds of documents: the standard Document class you get from normal Domino API operations and DominoDocument (styled NotesXspDocument in SSJS). Many times, these can be treated roughly equivalently: DominoDocument has some (but not all) of the same methods that you're used to from Document, such as getItemValueString and replaceItemValue, and you can always get the inner Document object with getDocument(boolean applyChanges). What's less common,




Created and Maintained by Yancy Lent - About - Planet Lotus Blog - Advertising - Mobile Edition