Critical Masses Technology, Inc.

That’s What Would You Do. I’d write WWJD in the title but I don’t want to offend…

Excuse me for the pedantic nature of this post, but I recently had an issue with developing a fairly complex agent for Notes coded in Java that caused me to revisit a basic understanding of how Java in Notes works. You see, the Java Virtual Machine, JVM for short, is essentially a stack-based emulator that runs bytecode compiled from the Java language source. Without getting into too much detail, the JVM has two memory pools to speak of, the stack and the heap, that can impact the performance and reliability of your Java program.

As an extension of Mikkel's post on how to get started with plugin development, I submit the following:

1. Symphony Developer's Guide PDF (in Symphony SDK) -even though it's not Domino development, it can get a beginner up to speed on creating plugins in the Expeditor platform.

When using LS2J to utilize Java classes from within LotusScript, you may be faced with needing to declare and bind to a method explicitly using its JNI signature. A common case where this is necesary is when your Java class has multiple overridden methods and you need to explicitly use one of them. Instead of wrestling with the JNI syntax, you can use this handy function to bind to the object and print out the signatures for you to copy:

Before I close up shop for the weekend I leave a lazyweb request. I'm developing a Notes plugin using the Expeditor Toolkit for Eclipse (6.2.1) and I can't seem to figure out how to expose the Symphony objects in the IDE for me to code against. Any help is appreciated.

I'm doing some research for a client in using Freemarker to generate documents using templates and Notes data. It turns out that it’s deceptively simple to create a very basic Notes wrapper object to pass into Freemarker’s templating engine for merging document fields with a template. The closest abstract class to implement for a document is Freemarker’s TemplateHashModel.

I thought I had gotten over the major humps to developing supersecret app, but it turns out that the Lotus Expeditor runtime had one more nasty trick up its sleeve: Expeditor’s runtime’s Java Cryptography Extension provider seems to be missing an algorithm for decrypting SSL communications with Google Apps. Bah! This is what happens when the JVM market fragments.

And now, Deep Thoughts, by Jake. Cue soothing music.

REPRINT: ORIGINALLY POSTED ON 3/28/2006