Petals ESB Container

The registry should be exploded in two parts

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

Details

Type: Improvement Request
Status: Resolved
Priority: Blocker
Resolution: Fixed
Affects Version/s: 3.1
Fix Version/s: 5.0.0
Component/s: Registry
Security Level: Public

Description:
Hide
Currently the registry contains two kind of information:

information needed to route messages,

information about service contract.

So the registry should be exploded in two parts to be optimized against each use cases:

retrieve service contracts. In this use case performances are not critical, the user should be able to get its WSDL under 1 second,

build the endpoints list against message content. Performance and content of this use case are critical,
Show
Currently the registry contains two kind of information:

information needed to route messages,

information about service contract.

So the registry should be exploded in two parts to be optimized against each use cases:

retrieve service contracts. In this use case performances are not critical, the user should be able to get its WSDL under 1 second,

build the endpoints list against message content. Performance and content of this use case are critical,

Environment:

-

Issue Links

Depends

This issue blocks:
~~PETALSREGOVER-1~~ Create a Petals Registry Overlay

Activity

Ascending order - Click to sort in descending order

No work has yet been logged on this issue.

People

Assignee:

Roland Naudin

Reporter:

Christophe DENEUX
Watchers:

0

Dates

Created:

Thu, 9 Sep 2010 - 17:07:57 +0200

Updated:

Mon, 5 Oct 2015 - 15:26:49 +0200

Resolved:

Mon, 5 Oct 2015 - 15:25:18 +0200