Flex Gateway新着情報
Governance新着情報
Monitoring API ManagerSupport Category: Select
Anypoint Connector for Microsoft Dynamics NAV Connector (NAV Connector) enables Mule apps to interact with the Microsoft Dynamics NAV Web Services versions 2013 R2, 2015, 2016, 2017.
July 4, 2025
To support Microsoft Dynamics NAV Connector in CloudHub 2.0, the client must provide SOAP requests in raw XML format instead of using Plain Old Java Objects (POJOs). For more information, refer to Upgrading and Migrating Microsoft Dynamics NAV Connector to Version 3.0.
Application/Service | Version |
---|---|
Mule |
4.6.6 and later |
OpenJDK |
8, 11, and 17 |
August 20, 2024
This connector is now compatible with Java 17.
A new external library called JAXB-XJC is now required for the NTLM and OAuth connection types for Java 8, 11, and 17. For more information, refer to NTLM Connection Type and OAuth Connection Type.
Application/Service | Version |
---|---|
Mule |
4.1.1 and later |
Anypoint Studio |
7.0.0 and later |
OpenJDK |
8, 11, and 17 |
October 3, 2022
Application/Service | Version |
---|---|
Mule |
4.1.1 and later |
Anypoint Studio |
7.0.0 and later |
Issue | ID |
---|---|
The metadata for the Page Operation operation now works as intended. |
W-11791738 |
November 11, 2021
Application/Service | Version |
---|---|
Mule |
4.1.1 and later |
Anypoint Studio |
7.0.0 and later |
Issue | ID |
---|---|
Fixed reported security vulnerabilities. |
CONN-9261 |
September 20, 2021
Application/Service | Version |
---|---|
Mule |
4.0.0 and later |
Anypoint Studio |
7.0.0 and later |
Issue | ID |
---|---|
Optimized the connector to improve its overall stability and performance. |
CONN-8802 |
June 10, 2019
NAV Connector is compatible with:
Application/Service | Version |
---|---|
Mule |
4.0.0 and later |
Anypoint Studio |
7.0.0 and later |
NAV Connector Test Connection fails with Unable to create JAXBContext for generated packages - There were some issues with some dependencies of the connector that were causing this problem with Mule runtime 4.2.0 and later. This was fixed by upgrading some dependencies to newer versions: org.apache.cxf:cxf-rt-transports-http:3.2.1 was updated to org.apache.cxf:cxf-rt-transports-http:3.3.1 and org.apache.cxf:cxf-rt-frontend-jaxws:3.2.1 was updated to org.apache.cxf:cxf-rt-frontend-jaxws:3.3.1. (SE-11902)