Petals SE Activiti

Use the consumes in the descriptor when possible

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 0.5.0
  • Fix Version/s: 1.0.0
  • Component/s: Process service
  • Security Level: Public
  • Description:

    When a request is sent from a process, the SE should use the consumes declared in the descriptor if possible.

  • Environment:
    -

Issue Links

Depends
 

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Victor NOËL added a comment - Thu, 10 Sep 2015 - 15:01:11 +0200

See https://github.com/petalslink/petals-se-activiti/pull/5

Show
Victor NOËL added a comment - Thu, 10 Sep 2015 - 15:01:11 +0200 See https://github.com/petalslink/petals-se-activiti/pull/5
Hide
Permalink
Christophe DENEUX added a comment - Thu, 10 Sep 2015 - 15:29:56 +0200 - edited

Merged in trunk

Show
Christophe DENEUX added a comment - Thu, 10 Sep 2015 - 15:29:56 +0200 - edited Merged in trunk
Hide
Permalink
Christophe DENEUX added a comment - Tue, 15 Sep 2015 - 11:16:25 +0200 - edited

Reopen to clarify and improve usage of the section 'consume' in JBI descriptor:

  • the section 'consume' in JBI descriptor is interesting to define service invocation parameters as time-out or message properties,
  • a section 'consume' identifies service provider, not an operation of a service provider that is required by service tasks of the process.

So:

  • the section 'consume' must not contain the operation definition. It is always defined at process level. If an operation is defined into the section 'consume', it will be ignored.
  • until we will not able to define the MEP to use at process level, the MEP defined in the section 'consume' can be used as default MEP. If no MEP is defined in section 'consume', the MEP InOut is used as default.
Show
Christophe DENEUX added a comment - Tue, 15 Sep 2015 - 11:16:25 +0200 - edited Reopen to clarify and improve usage of the section 'consume' in JBI descriptor:
  • the section 'consume' in JBI descriptor is interesting to define service invocation parameters as time-out or message properties,
  • a section 'consume' identifies service provider, not an operation of a service provider that is required by service tasks of the process.
So:
  • the section 'consume' must not contain the operation definition. It is always defined at process level. If an operation is defined into the section 'consume', it will be ignored.
  • until we will not able to define the MEP to use at process level, the MEP defined in the section 'consume' can be used as default MEP. If no MEP is defined in section 'consume', the MEP InOut is used as default.
Hide
Permalink
Victor NOËL added a comment - Tue, 15 Sep 2015 - 15:07:28 +0200

It's fixed in trunk.

Show
Victor NOËL added a comment - Tue, 15 Sep 2015 - 15:07:28 +0200 It's fixed in trunk.
Hide
Permalink
Christophe DENEUX added a comment - Tue, 15 Sep 2015 - 15:20:24 +0200

It's ok for me, you can change issue state to RESOLVED.

Show
Christophe DENEUX added a comment - Tue, 15 Sep 2015 - 15:20:24 +0200 It's ok for me, you can change issue state to RESOLVED.

People

Dates

  • Created:
    Thu, 10 Sep 2015 - 14:59:03 +0200
    Updated:
    Fri, 5 Aug 2016 - 12:04:31 +0200
    Resolved:
    Thu, 17 Sep 2015 - 17:04:17 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.