Monthly Archives: November 2015

IBM Connect and what I would like to be announced

I usually write a little post about what I would like to see an announcement about in January

  1. XPages for Bluemix leaves experimental hopefully goes Gold.
    So we can use it in production
  2. Lowering the price for data cache used when scaling XPages applications in Bluemix
    pricing today is a joke, data cache cost almost equal to a full instance. So if you want to scale into more instances you have to pay double the price of the instance.
  3. NSF database enhancements both functionality and speed
    Move indexes out of the database, joins, better and faster fulltext search
  4. Data service for IBM Cloudant directly in XPages
    Leverage the full potential of Bluemix directly inside XPages
  5. Database converter from NSF to Cloudant
    Cloudant is almost the same as an NSF database but with more speed and without the need to a Domino server
  6. IBM Verse replaces iNotes as webmail client
    The customers need something new and fresh
  7. Public release of Outlook as a mailclient thru traveler 
  8. Java 1.8 support for XPages 
  9. Javascript v8 support in SSJS 
  10. Domino Designer becomes a Eclipse plugin
    Yes please, let’s get rid of the old version of eclipse and give us access to everything new and the possibility to upgrade it. and have several versions on the same machine.

You can probably think of more things you would like feel free to make a comment

Wild click events on my XPage

Today I had a strange issue on an XPage application I was working on I it didn’t matter where I clicked
my button on the form got clicked. Very strange. First thing I started to look for was if I had some onClick event that was bind wrong. Nope that wasn’t the case.

Then I went over to the client side and thought I could find what event listener that was making the call but this doesn’t say anything to me.


Then I started to look at the XSP.Attachevents at the bottom of the xpage

But if you have a large xpage and 20 events attached to it, it’s hard to find what is what. The my suggestion is give you components real names. And it was then I found the problem.
Can you spot the difference

The working client side code
his this the XPage with the faulty code


on’t scroll more spoiler alert










Yes, the partial event listener is bound to an object that doesn’t exist view:_id1:_id5
why you might ask, I found that this happens if a button don’t have a name and is set to do a partial refresh.


Then you will get that you will click the button where every you click on the xpage. Hopefully fixed in a future release with an error or a correctly generated id.