Useful new preference in DDE 8.5.2 for Java Agents

Having the proper Eclipse Java editor instead of the old style editor was introduced in 8.5.1, but there was one huge annoyance. When you edited a Java file, you had to save that, but then also remember to save the agent as well. Cue plenty of swearing and head scratching when your change wasn’t showing up.

Well in 8.5.2 there is a new preference setting which allows the agent to be automatically saved when you save the Java file:

Just check the “Autosave Java design element on save of individual Java sources” box to make your Java coding a lot less annoying.

A small tip for upgrading your XPages apps from 8.5.1 to 8.5.2

If you have been using Stephan Wissel’s “Web Agents, XPages Style” technique for outputting non-HTML content from your XPages, you may run into a problem when you upgrade your server to 8.5.2.

In the original afterRenderResponse sample code, you would use something like…

    var exCon = facesContext.getExternalContext(); 
    var writer = facesContext.getResponseWriter();
    var response = exCon.getResponse();
    writer.write("Hello World");

What you may find is running that code on your lovely new 8.5.2 server will result in an Error 500 with no detail of the error itself. To fix the problem, simple remove the


line from the source code and you should be good to go.

What’s new with XPages in 8.5.2

Over on XPages101.net I’ve just posted (yet another) video. This time we’re looking at what’s new in 8.5.2 for the XPages developer.

What’s New With XPages in 8.5.2

As a bit of a teaser, I thought I’d post the audio from that recording here as well so that you can hear what you’re missing. As ever, feel free to subscribe if you want to get a jumpstart on your XPages development. There are 30 different videos up on the site covering all the elements you’ll need to get started and then dig a little deeper into XPages development. The full video listing can be found here.

Pleasant 8.5.2 surprise… everything works!

Well maybe that’s too bold a claim, but from the point of view of regression testing IdeaJam and IQJam for XPages issues, a vanilla application works absolutely fine. And better than that, it seems to be faster as well.

Why is this even worth commenting on you ask? Well between 8.5.0 and 8.5.1 there were some quite significant changes in the way XPages worked which meant I had to do some re-coding of my XPages apps to get them to work properly when we migrated up to the new version. But, so far, and all of the usual caveats apply here* (see below for more information), I can simply copy an NSF from my 8.5.1 VM onto my 8.5.2 VM and it works.

We’ve not done any proper testing on the performance side of things, but from my usage of the application everything feels snappier.

So, who needs new features when we’ve got stability between versions. Well OK, I’ll not turn down the spangly new development features (dragging controls into the source XML of an XPage is far and away my favourite), but even without them, I’m a happy camper this morning.

*** 8.5.2 is still in beta things may change between now and when it’s released. Let’s hope not eh?