Petals BC Gateway

Can't use gateway between containers with different SharedArea/ServiceEndpoint implementations

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

Details

Type: Bug
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 0.0.5
Fix Version/s: 1.0.0
Component/s: None
Security Level: Public

Description:

Hide

Context: when connecting a container in, for example, a standalone domain (using the implementation from ~~PETALSESBCONT-433~~) to a container in a dynamic domain (using the registry overlay implementation).

Problem: the two shared area implementations use different endpoint implementations and thus when the exchange is deserialized on the standalone domain container, it can't find the exchange's endpoint class.

Show
Context: when connecting a container in, for example, a standalone domain (using the implementation from ~~PETALSESBCONT-433~~) to a container in a dynamic domain (using the registry overlay implementation). Problem: the two shared area implementations use different endpoint implementations and thus when the exchange is deserialized on the standalone domain container, it can't find the exchange's endpoint class.

Environment:

-

Activity

People

Assignee:

Victor NOËL

Reporter:

Victor NOËL
Watchers:

0

Dates

Created:

Tue, 28 Jun 2016 - 16:57:13 +0200

Updated:

Wed, 7 Sep 2016 - 16:28:02 +0200

Resolved:

Wed, 7 Sep 2016 - 16:28:01 +0200