error for client with database

[ehennum]

In the REST API, a client can specify a different content database with a parameter. On the enode, that's implemented with a rewriter.

That's not available for Data Services First. Thus, the base proxy should throw an error if the database client specifies a database explicitly instead of using the default database for the appserver.

[ehennum]

To prevent the issue you ran into, the proxy service class will now throw an exception if the client passed into the static instantiation factory specifies an explicit database instead of using the default database for the appserver.

I doubt this fix requires a functional test -- the fix just adds error checking on an input argument -- but you're better placed to make that determination.

[georgeajit]

Will run a manual test by changing one of the test to include a database on the DatabaseClient instance.

[kcoleman-marklogic]

Just a bit of unsolicited feedback...

The message says "Client must use the default database instead of: ...". That is going to be confusing if the explicit database is the same as the default database. Would it make sense to say "Client must not explicitly specify a database" or something like that?

[ehennum]

Good catch. How is: "Client cannot specify a database - specified: "