-
Notifications
You must be signed in to change notification settings - Fork 66
Support for 'Module Location Configuration' #209
Comments
Looking into this. Also missing: schemas, and request-blackouts.. |
@grtjn I try to add in ml-confg.xml:
And execute |
I forget to put
I get the error message: |
Auch, classic mistake trying to pass a sequence of values into xdmp:eval.. |
Bug fix for #209, few other bug fixes..
If
Is it expected or should |
That's a bug. Typical operation is to update the $config by removing those settings, then adding the specified ones. If there's no change, then there's no difference. |
Hmm, the self-test doesn't cover changing settings at the moment. Maybe a good moment to build that in.. |
The logic is a little 'smarter' actually. It tries to detect which ones should be added, which ones should be removed. Taking the blunt approach might indeed be more robust.. |
Ah, it is actually is silly mistake. The mechanism for ns, schemas, and modules is same: ns-prefix, schema-ns, and module-ns need to be unique. So, those with matching prefix or ns-uri are removed first, before adding missing ones. But the logic to delete them passed through the new spec instead of the old one, making delete fail. By explicitly removing those that need to be deleted, and only adding those that are missing, any existing ns, schema or module-location will be preserved.. |
How do I add |
Bootstrap normally replaces <xdbc-server>
<xdbc-server-name>@ml.app-name-xcc</xdbc-server-name>
<port>@ml.xcc-port</port>
<database name="@ml.content-db"/>
<modules name="@ml.modules-db"/>
<authentication>digest</authentication>
</xdbc-server> That does not contain module-locations, and doesn't allow you to add them this way. Bootstrap should however support module-locations for any server type. You could replace the placeholder with the above replacement in |
Adding |
Ability to register some modules.
The text was updated successfully, but these errors were encountered: