Petals BC REST

Path matching on request (consumes) takes the last match instead of first

View this issue in another formatViewView
- XML
- Word
- Printable

Details

Type: Bug
Status: Resolved
Priority: Minor
Resolution: Fixed
Affects Version/s: 1.0.1-BC
Fix Version/s: 1.1.0-BC
Component/s: Consumer mode
Security Level: Public

Description:

Hide

When a request URL matches multiple paths mapping defined in a consume, instead of taking the first one into account, it takes the last one (and uselessly process all of the matching paths).

It would be more intuitive to take the first one into account.

Show
When a request URL matches multiple paths mapping defined in a consume, instead of taking the first one into account, it takes the last one (and uselessly process all of the matching paths). It would be more intuitive to take the first one into account.

Environment:

-

Activity

Transition

Status Change Time

Execution Times

Last Executer

Last Execution Date

New

Open

42s

1

Victor NOËL

Mon, 9 Jan 2017 - 14:51:14 +0100

Open

In Progress

11s

1

Victor NOËL

Mon, 9 Jan 2017 - 14:51:25 +0100

In Progress

Resolved

1h 33m

1

Victor NOËL

Mon, 9 Jan 2017 - 16:25:16 +0100

People

Assignee:

Victor NOËL

Reporter:

Victor NOËL
Watchers:

0

Dates

Created:

Mon, 9 Jan 2017 - 14:50:32 +0100

Updated:

Mon, 9 Jan 2017 - 16:25:16 +0100

Resolved:

Mon, 9 Jan 2017 - 16:25:16 +0100