You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The document [1] provides an example scenario for testing the file connector. However, there are a few discrepancies between the content and the screenshots and the steps outlined for trying out the connector project.
Specific issues identified:
curl -H "Content-Type: application/xml" --request POST --data @body.json http://10.100.5.136:8290/fileconnector/create
1. Inconsistent content-type in curl command [2]:
The provided curl command specifies a "Content-Type" of application/xml, but the data being sent is from a .json file, which creates a conflict.
2. Incorrect file format reference:
The payload format is XML, yet the first step refers to saving it as a data.json file. This mismatch can cause confusion.
3. Incorrect host in the curl command:
The curl command uses an IP address rather than localhost, which is unexpected for a local testing scenario.
4. Mismatched API context:
According to the API request, the context path should be /fileconnector, but earlier in the documentation [3], it instructs users to create the REST API with the context /fileTest, leading to inconsistencies.
5. Missing URI template configuration:
The curl request references /create as the URI_TEMPLATE, yet the documentation does not include any instructions for specifying the URI_TEMPLATE or URL_MAPPING for the API.
6. Complexity in identifying steps:
Many steps are explained only through screenshots, making it difficult to follow. This forces users to manually type configuration values instead of copy-pasting, making the process less user-friendly.
7. No Downloadable project for reference:
There is no link to download the complete project to try out or verify our implementation.
Request for Improvement:
Kindly request a thorough review and update of the entire document to ensure consistency between the instructions and screenshots. This is especially important as the document is referenced in our training materials. A more structured and user-friendly approach would be highly appreciated.
Description
The document [1] provides an example scenario for testing the file connector. However, there are a few discrepancies between the content and the screenshots and the steps outlined for trying out the connector project.
Specific issues identified:
curl -H "Content-Type: application/xml" --request POST --data @body.json http://10.100.5.136:8290/fileconnector/create
1. Inconsistent content-type in curl command [2]:
The provided curl command specifies a "Content-Type" of application/xml, but the data being sent is from a .json file, which creates a conflict.
2. Incorrect file format reference:
The payload format is XML, yet the first step refers to saving it as a data.json file. This mismatch can cause confusion.
3. Incorrect host in the curl command:
The curl command uses an IP address rather than localhost, which is unexpected for a local testing scenario.
4. Mismatched API context:
According to the API request, the context path should be /fileconnector, but earlier in the documentation [3], it instructs users to create the REST API with the context /fileTest, leading to inconsistencies.
5. Missing URI template configuration:
The curl request references /create as the URI_TEMPLATE, yet the documentation does not include any instructions for specifying the URI_TEMPLATE or URL_MAPPING for the API.
6. Complexity in identifying steps:
Many steps are explained only through screenshots, making it difficult to follow. This forces users to manually type configuration values instead of copy-pasting, making the process less user-friendly.
7. No Downloadable project for reference:
There is no link to download the complete project to try out or verify our implementation.
Request for Improvement:
Kindly request a thorough review and update of the entire document to ensure consistency between the instructions and screenshots. This is especially important as the document is referenced in our training materials. A more structured and user-friendly approach would be highly appreciated.
[1] https://apim.docs.wso2.com/en/4.2.0/reference/connectors/file-connector/file-connector-example/
[2] https://apim.docs.wso2.com/en/4.2.0/reference/connectors/file-connector/file-connector-example/#testing
[3] https://apim.docs.wso2.com/en/4.2.0/reference/connectors/file-connector/file-connector-example/#creating-the-integration-logic
Product: MI 4.2.0
<This issue has been transferred from mi-internal>
The text was updated successfully, but these errors were encountered: