Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 326122

Summary:	DefaultHostContainerFinder creates a container if "service.exported.configs" is null
Product:	[RT] ECF	Reporter:	Markus Kuppe <bugs.eclipse.org>
Component:	ecf.remoteservices	Assignee:	Markus Kuppe <bugs.eclipse.org>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3
Version:	3.3.0
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:	326053
Bug Blocks:

Description Markus Kuppe

2010-09-24 03:46:44 EDT

As described in bug #326053#c5 DefaultHostContainerFinder shows inconsistent behavior WRT to container instantiation. If "service.exported.configs" is null, it creates a (default) container for the first service registered. For a second service registered however, it fails to match config types and subsequently tries to create a second container. This causes a container exception in turn due to a port conflict.

Possible solutions are:

a) Fix AbstractHostContainerFinder.matchExistingHostContainer so that the second service reuses the existing container
b) Add a condition to line 44 in DefaultHostContainerFinder.findHostContainers(ServiceReference, String[], String[], String[]) that checks for "service.exported.configs" == null

Comment 1 Markus Kuppe

2010-09-25 03:40:32 EDT

Going to implement a) as part of bug #326053. Closing this one as WONTFIX.