13
Sep
Author: Dave Cassel | Category:
Software Development
Suppose you’ve built an application using MarkLogic’s Visualization Widgets. At some point you decide you have too many and decide to remove one. I’ve seen a couple cases where someone does an incomplete removal, so I figured it’s worth laying out the steps. This write-up assumes that you’ve built an application using Application Builder, but […]
30
Apr
Author: Dave Cassel | Category:
Software Development
When you deploy a custom service extension to MarkLogic’s REST API, where does it go? By default, service extensions are put in the Extensions database. This means that an extension is available to all applications on the MarkLogic instance. While I can see use cases where this is helpful, the servers I work on typically […]
04
Dec
Author: Dave Cassel | Category:
Software Development
I’ve gotten very accustomed to using the Roxy with my MarkLogic projects. However, with the new App Builder available with MarkLogic 6, some of my projects are based on JavaScript and the REST API. I still want to use the Roxy deployer, however. The simplicity of deploying configuration and code with a few simple commands […]
27
May
Author: Dave Cassel | Category:
Software Development
The “directory creation” database setting is one of the first things I change for a new database. The default is “automatic”, but I switch it to “manual”, as I was taught by more experienced developers when I joined MarkLogic. The reason given was performance — use manual so that MarkLogic doesn’t bother creating directories. I’ve […]
09
Nov
Author: Dave Cassel | Category:
Software Development
When you point a MarkLogic application server to some source code, that code can either reside on the file system or in a modules database. Here are some reasons why you might pick one of those over the other. Modules Database Deploying code is a transactional update — there’s no need to worry that the […]