jira-issues-migration issueshttps://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues2018-04-28T13:24:18Zhttps://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/800Handle compilation warnings2018-04-28T13:24:18ZDmitri VoitsekhovitchHandle compilation warningsCompilation produces many unimportant warnings which should be corrected whenever possible.Compilation produces many unimportant warnings which should be corrected whenever possible.https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/845Create wrapper libs for remote network access2018-04-28T13:24:19ZDmitri VoitsekhovitchCreate wrapper libs for remote network accessCurrently services which need to acces remote respositories (such as HTTP or WebDAV) need to implement their own methods for doing so. It would be better if such commonly-needed methods were made available in the framework itself. Implem...Currently services which need to acces remote respositories (such as HTTP or WebDAV) need to implement their own methods for doing so. It would be better if such commonly-needed methods were made available in the framework itself. Implementation should use libneon for WebDAV and QHTTP for HTTP access. Other protocols should be considered if needed.https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/864"Lost" attributes in some requests2018-04-28T13:24:19ZDmitri Voitsekhovitch"Lost" attributes in some requestsIn all cases the root node of an incoming resource is missing some attributes. For example a resource containing xsi:type="mode:Document" it ends up (after parsing) with type="model:Document".
This seems to be caused by the Qt4 XML par...In all cases the root node of an incoming resource is missing some attributes. For example a resource containing xsi:type="mode:Document" it ends up (after parsing) with type="model:Document".
This seems to be caused by the Qt4 XML parser and needs further investigation.
A possible workaround is to add an extra node before the first one, containing all namespace declarations.
Note that this bug is only problematic in the case of services which must conserve the original resource(s) in the response (i.e. Analyser).https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/985Improve code generation tool2018-04-28T13:24:19ZDmitri VoitsekhovitchImprove code generation toolThe code generation tool from WSO2 (currently in use) has one major problem: it is unable to generate the skeleton for a service using multiple interfaces. It is very unlikely the developers will solve this bug.
A permanent solution wou...The code generation tool from WSO2 (currently in use) has one major problem: it is unable to generate the skeleton for a service using multiple interfaces. It is very unlikely the developers will solve this bug.
A permanent solution would be to write our own code for the part of the tool where it matters.
Three possible ways to do this:
- delve into the WSO2 code to change what does not work;
- create a layer of code above the tool in order to add missing code;
- leave it as is (not recommended)