jira-issues issueshttps://gitlab.ow2.org/chorevolution/jira-issues/-/issues2017-06-22T14:56:12Zhttps://gitlab.ow2.org/chorevolution/jira-issues/-/issues/96Create a reverse proxy for SOAP service2017-06-22T14:56:12Zfrederic motteCreate a reverse proxy for SOAP serviceThe Security Filter is a reverse proxy intercepting request to extract information and validate input elements The Security Filter is a reverse proxy intercepting request to extract information and validate input elements 1.0.0https://gitlab.ow2.org/chorevolution/jira-issues/-/issues/97create datamodel for the service description2017-06-22T14:55:58Zfrederic mottecreate datamodel for the service descriptionCreate the datamodel for the service DescriptionCreate the datamodel for the service Description1.0.0https://gitlab.ow2.org/chorevolution/jira-issues/-/issues/103Implementation of the user provisionning interface2017-06-22T14:57:48Zfrederic motteImplementation of the user provisionning interfaceImplementation of the user provisionning inteface used by the IdM to provide user informationImplementation of the user provisionning inteface used by the IdM to provide user information1.0.0https://gitlab.ow2.org/chorevolution/jira-issues/-/issues/127Create API to push service credential2017-06-22T14:57:35Zfrederic motteCreate API to push service credential1.0.0https://gitlab.ow2.org/chorevolution/jira-issues/-/issues/190define service interface provisionning 2017-06-22T14:57:23Zfrederic mottedefine service interface provisionning 1.0.0https://gitlab.ow2.org/chorevolution/jira-issues/-/issues/195BPMN2 Choreography Validator2017-02-07T11:53:38ZAlexander PerucciBPMN2 Choreography ValidatorProvides a BPMN2 Choreography Diagram validatorProvides a BPMN2 Choreography Diagram validator1.0.0https://gitlab.ow2.org/chorevolution/jira-issues/-/issues/199Adding Class: Bpmn2ChoreographyValidatorResponse2016-10-01T14:15:45ZLorenzo De LauretisAdding Class: Bpmn2ChoreographyValidatorResponseI'll go to add a new class called "Bpmn2ChoreographyValidatorResponse" that will contain the validation results.I'll go to add a new class called "Bpmn2ChoreographyValidatorResponse" that will contain the validation results.1.0.0https://gitlab.ow2.org/chorevolution/jira-issues/-/issues/200Test Case "test_09" error correction2016-09-15T00:23:58ZLorenzo De LauretisTest Case "test_09" error correctionCorrecting an error in test case: "test_09" in the sub-choreography "manageTRVinformation"Correcting an error in test case: "test_09" in the sub-choreography "manageTRVinformation"1.0.0https://gitlab.ow2.org/chorevolution/jira-issues/-/issues/211Build Failure for Unapproved License2016-09-30T15:52:17ZAlexander PerucciBuild Failure for Unapproved LicenseReplication: run the command "mvn clean verify" on the root of projectReplication: run the command "mvn clean verify" on the root of project1.0.0https://gitlab.ow2.org/chorevolution/jira-issues/-/issues/256Add test 13 in Bpmn2ChoreographyValidatorTest.java2016-12-06T17:02:03ZAlexander PerucciAdd test 13 in Bpmn2ChoreographyValidatorTest.java1.0.0https://gitlab.ow2.org/chorevolution/jira-issues/-/issues/257CD Prosumer WSDL Generation2016-12-06T22:35:29ZClaudio PompilioCD Prosumer WSDL GenerationA {{CD Prosumer}} WSDL defines all the operations related to the choreography tasks in which the corresponding prosumer participant is the receiving participant.
The operations are organized into ports based on the nature of the interac...A {{CD Prosumer}} WSDL defines all the operations related to the choreography tasks in which the corresponding prosumer participant is the receiving participant.
The operations are organized into ports based on the nature of the interaction to which they belong. This means that in the {{CD Prosumer}} WSDL there will be a different port for every initiating participant of the choreography tasks in which the prosumer participant is involved.1.0.0https://gitlab.ow2.org/chorevolution/jira-issues/-/issues/258AnyObject search conditions filter not properly working2016-12-07T13:30:32ZGianluca FilipponeAnyObject search conditions filter not properly workingWhen a fiql query for the AnyObject DirectoryDataProvider is set with the AnyObjectFiqlSearchConditionBuilder class, the filter on the AnyObject type does not work if is applied the condition "inGroups()": the query returns all the AnyOb...When a fiql query for the AnyObject DirectoryDataProvider is set with the AnyObjectFiqlSearchConditionBuilder class, the filter on the AnyObject type does not work if is applied the condition "inGroups()": the query returns all the AnyObject which are member of the selected group, without filtering through the AnyObject type. Without using the inGroups() function, the filter works as expected.1.0.0https://gitlab.ow2.org/chorevolution/jira-issues/-/issues/259CD Client WSDL Generation2016-12-06T22:45:00ZClaudio PompilioCD Client WSDL GenerationA {{CD Client}} WSDL defines all the operations related to the choreography tasks in which the corresponding client participant is the initiating participant and the ones in which it is the receiving participant.
The operations are orga...A {{CD Client}} WSDL defines all the operations related to the choreography tasks in which the corresponding client participant is the initiating participant and the ones in which it is the receiving participant.
The operations are organized into ports based on the nature of the interaction to which they belong. This means that in the {{CD Client}} WSDL there will be one port in which are defined all the operations representing the interactions between client and the client participant ({{CD Client}}), there will also be
a different port for every initiating participant of the choreography tasks in which the client participant is involved.1.0.0https://gitlab.ow2.org/chorevolution/jira-issues/-/issues/261Prosumer WSDL Generation2016-12-08T19:18:42ZClaudio PompilioProsumer WSDL GenerationA {{Prosumer}} WSDL defines all the operations in which the corresponding prosumer participant is involved.
For every choreography task in which the prosumer participant is involved, there can be two cases:
- *the prosumer participant is...A {{Prosumer}} WSDL defines all the operations in which the corresponding prosumer participant is involved.
For every choreography task in which the prosumer participant is involved, there can be two cases:
- *the prosumer participant is the initiating participant of the choreography task*, in this case the {{Prosumer}} WSDL exposes an operation that takes as input the choregraphy id value and return as output the message that has be sent to the receiving participant. If the choreography task has a Return Message the {{Prosumer}} WSDL exposes an operation used to receive that message.
- *the prosumer participant is the receiving participant of the choreography task*, in this case the {{Prosumer}} WSDL exposes an operation that takes as input the Initiating Message of the choreography task, and if for that choreography task is defined a Return Message the operation returns that message.1.0.0https://gitlab.ow2.org/chorevolution/jira-issues/-/issues/263Avoid the use of the same messages with different data type for the same part...2017-01-21T03:58:59ZClaudio PompilioAvoid the use of the same messages with different data type for the same participantA message has to have the same Data Type for a specific participant. Every message exchanged from a participant with the same has to to have the same data type definition.A message has to have the same Data Type for a specific participant. Every message exchanged from a participant with the same has to to have the same data type definition.1.0.0https://gitlab.ow2.org/chorevolution/jira-issues/-/issues/264Every sub-choreography and call-choreography representation has to specify al...2017-01-10T01:35:45ZClaudio PompilioEvery sub-choreography and call-choreography representation has to specify all the participants involved in itIn every sub-choreography representation there should be specified all the participants involved in it and also the participants involved in all the nested sub-choreographies, if presentIn every sub-choreography representation there should be specified all the participants involved in it and also the participants involved in all the nested sub-choreographies, if present1.0.0https://gitlab.ow2.org/chorevolution/jira-issues/-/issues/270ChorSpec library: build hangs2017-01-09T10:06:11ZFrancesco ChicchiriccoChorSpec library: build hangsWhen building via Maven the ChroSpec library, the build process hangs during the test execution (-DskipTests is required to complete the build).
I suspect this is due to one or more test cases relying on some remote server which is natu...When building via Maven the ChroSpec library, the build process hangs during the test execution (-DskipTests is required to complete the build).
I suspect this is due to one or more test cases relying on some remote server which is naturally not reachable from my own laptop.
Please either move such test cases into a separate Maven profile, make the server available ubiquitously or remove.1.0.0