I'm currently having issues with upgrading from Camunda DMN 7.13.0 to 7.15.0.
There is existing logic in my project which "merges" decision table content, which in fact adds new rules to an already existing DMN config.
When I upgrade the version I run into an issue that like this:
ValidationException: DOM document is not valid
Invalid content was found starting with element 'n0:rule'. One of '{"http://www.omg.org/spec/DMN/20151101/dmn.xsd":rule}' is expected.
Any idea how to solve this issue? Did anything change within the Camunda DMN library that i missed?
Without the full DMN file it is hard to help with a specific fix, but to answer your question: Yes, DMN support was upgraded from DMN 1.1. to 1.3.
You seem to be used the DMN API to merge decision table content as you wrote, so this may apply to you:
As of version 7.13.0, the DMN Model API supported the DMN 1.3
specification. However, any generated/exported DMN diagrams still used
the DMN 1.1 specification. As of this version, the DMN Model API now
generates DMN diagrams with the DMN 1.3 specification. Users that rely
on the DMN 1.1 specification from diagrams generated by the DMN Model
API should adjust their logic to use the DMN 1.3 specification.
https://docs.camunda.org/manual/7.15/update/minor/714-to-715/#dmn-model-api-generates-dmn-1-3-diagrams
Related
I'm in the process of migrating an Exist DB app based on 2.1 to 5.x and am having trouble finding replacements for a couple of apparently deprecated / moved functions. They are:
context:get-attribute
context:set-attribute
text:groups-regex
Any guidance on replacements or alternative approaches would be greatly appreciated.
Thanks.
The Context Module was removed in eXist-db 5.0.0 as its only purpose was to allow mutable variable storage within a single running XQuery. This is really just bad-practice, instead your XQuery should be refactored to pass variables around.
Instead of text:groups-regex, you probably want fn:analyze-string.
This is a more specific continuation of my previous Post: Custom Vision on HoloLens
I'm still using the Unity Project from this blogpost: https://mtaulty.com/2018/03/29/third-experiment-with-image-classification-on-windows-ml-from-uwp-on-hololens-in-unity/
I had issues that my own exported models don't work with the the code at some point. Now it is possible to export onnx models of version 1.2, but the the old code seems to not be compatible with the new version.
in the line var evalOutput = await this.learningModel.EvaluateAsync(this.inputData); in the MainScript it throws The binding is incomplete or does not match the input/output description. (Exception from HRESULT: 0x88900002)
Does someone know what I need to change so it works with the new version on HoloLens? Thanks in advance!
You can find a similar question here: Windows ML's OS requirement
In summary, you are right about needing to update the PC and the Hololens, but the build number you need is 17763 to be on the production version of RS5.
You could also be hitting this issue: Cannot load model using WinML
where the binding isn't quite setup properly.
If you're still having issues, please post the SDK and OS version you're on, as well as the ONNX model version.
I want to use Swagger 2.0 to document REST API as this seems to be widely used to document RET APIs.
However, I am not sure how can I keep the documentation and implementation in Sync ? e.g. When I add a new API then I have to make sure that the model (to represent the Response) used in the API documentation should be same as the model created in the REST implementation. Similarly, the resource name given in the documentation should match the resource name in the implementation.
Is there a way to generate just the resource interface and model classes from the documentation produced using swagger 2.0 spec ?
You can generate server source with these tools (they can also generate client source) :
http://studio.restlet.com: online editor, generate server skeleton code for java (Jax-RS and Restlet) and Node.js
http://editor.swagger.io: online editor, generate server skeleton code for java (Jax-RS), Node.js, Scalatra and Java Spring MVC
https://github.com/swagger-api/swagger-codegen: swagger code generator, you can try to implement your own generator module (personally, I'm currently trying to use this one)
I'm again coming up against problems after picking up some tasks on CQ 5.3 but having used nothing but 5.6 before this.
My problem is with client libraries:
In CRXDE Lite in CQ 5.3 I went and set up my client libraries as I normally would at component level and /etc/designs/<project> level (using type cq:ClientLibraryFolder), however after including the line <cq:includeClientLib css="my.category"/> I got a jsp error stating the tag was not defined.
Sure enough, after a quick Google I found this tag wasn't introduced until 5.4, so my question(s) are:
How do you use client libraries in CQ 5.3?
If the answer to #1 is "you can't" then why on earth is the option available to set them up present in 5.3 CRXDE Lite?
Internet searches have turned up no information (or I'm searching for the wrong thing), hence my question here.
Thanks in advance
Yes, the cq:includeClientLib tag was introduced in 5.4 only.
But even without that you can include your clientlibs using the com.day.cq.widget.HtmlLibraryManager service.
The tag was just a convenience wrapper around this service interface.
HtmlLibraryManager htmlMgr = sling.getService(HtmlLibraryManager.class);
if (htmlMgr != null) {
htmlMgr.writeCssInclude(slingRequest, out, "my.category");
}
Refer HtmlLibraryManager API docs for the other methods that are provided.
I need to upgrade an existing rather large application from Symfony 2.0.15 to Symfony 2.4.x (replace with current version).
I'm not quite sure what would be the best strategy to do so. Migration critical features like forms or esi are used, of course :)
Upgrade "step by step" from one major version to another (2.1, 2.2, 2.3, 2.4)
Upgrade directly from 2.0.x to 2.4
Do you have any tips / experience to share ? Would appreciate it :)
Thanks,
Stephan
Each new version comes with an update UPGRADE-2.x.md file containing all intructions to convert your application from the immediately previous version.
I had to do that on my project as well, and I found the step-by-step method more natural and easier to manage. Fact is, there is no file such file as UPGRADE-2.0-to-2.4.md that would help you out for a direct conversion to 2.4.
I shall first recommend to make sure that none of your code uses obsolete functionnalities of Symfony 2.0 (not sure if there are deprecated parts in this version, though), because these can be removed in ulterior versions and will not be included in the UPGRADE file.
If you have done indeep modifications of the core Symfony code, you may find that some undocumented modifications are needed. For instance, there is a custom error handler in my project, extending the Symfony error handler. Well, although it was not documented in the UPGRADE file, the signature of ErrorHandler::handle() was modified and needed to be updated in my custom handler.
Similarly, I had to modify some namespaces because files had been moved in the framework code.
The conversion is still ongoing and I'm currently experiencing a weird error I'm trying to get rid of: The 'request' scope on services registered on custom events generates errors in the logs.