Moving an XPages app from a Domino 8.5.3 to Domino 9.0 - keep Dojo 1.6.1?

0
votes

Have anyone done this?

I think this could be a major deal breaker if you need to modify all your JS code to work with later versions of Dojo to be able to upgrade your servers.

I have an application that doesn't work, out of the box, on Dojo 1.8x and need to use the same Dojo version as the old Domino 8.5.3 server does (1.6.1).

When I check the JS-catalog only dojo-1.5.2 is available (for some odd reason). Setting xsp.client.script.dojo.version, in the application, = 1.5.2 will load this version but it seems to be missing everything from XPages - the catalog doesn't contain anything related to XPages, it's missing the ibm-folder.

What do I need to do to make an XPages application use Dojo 1.6.1 on a Domino 9 box, the same way a Domino 8.5.3 box does?

Thanks!

/J

3
javascriptdojoxpageslotus-domino
Joacim, what fails? I've had Dojo code that I converted to use the new Dojo require statements in order for it to work with 1.8 - Per Henrik Lausten
I can convert it, that's not the issue. One of the problems is that it needs to work across domino versions. - jBoive

3 Answers

2
votes

Dojo 1.6.1 was deployed on Domino 8.5 via a plugin. You should be ale to copy that across from a Domino 8.x installation or, if you've upgraded, it may still be there. It should be in \osgi\shared\eclipse\plugins. That's where the file needs adding to R9. It should be com.ibm.xsp.dojo_..., which is the format of the R9 version.

2
votes

As Paul Stephen Withers write You could try to copy Domino\osgi\shared\eclipse\plugins\com.ibm.xsp.dojo_8.5.3.20120628-0936.jar plugin to R9 and then set the property xsp.client.script.dojo.version to 1.6.1.

But I would advise You to try to run Your app in 1.8 dojo. This version is quite compatible with previous and there should not be much work in porting 1.6 code. Im speaking from experience here - we managed to port quite big app in matter of days.

0
votes

What I ended up doing was to extract the DOJO 1.6.1 directory from the JAR and manually copying it into the correct directory (use the same naming conventions as the version(s) already installed).