I have questions on Team Member Repository Descriptor.
Why do we join both client and server configuration within
one repository descriptor?
Sample descriptor taken from CoronaDemo container:
<repository-descriptor
content-type="http://www.eclipse.org/corona/contentTypes/teamContent"
name="TeamMemberRepository"
uri="http://www.eclipse.org/corona/repository/CoronaDemoTeamRepository">
<description>Team member repository definition</description>
<repository-configurations
default-configuration-name="WebService">
<repository-configuration
name="WebService">
<repository-connection-parameters
access-type="http://www.eclipse.org/corona/accessTypes/ws"
name="TeamMemberRepositoryConnectionParameters">
<repository-connection-parameter
name="url" value="http://cwpl-0102:3000"/>
</repository-connection-parameters>
</repository-configuration>
<repository-configuration
name="XML">
<repository-connection-parameters
access-type="http://www.eclipse.org/corona/accessTypes/xml"
name="TeamMemberRepositoryConnectionParameters">
<repository-connection-parameter
name="file-path"
value="${CORONA_CONFIG_HOME}/repositories/CoronaDemoTeamRepository.xml"/>
</repository-connection-parameters>
</repository-configuration>
</repository-configurations>
</repository-descriptor>
With such definition we indicate that used configuration is
WebService (default-configuration-name attribute contains WebService value) but…
if anyone tries to remove ‘XML’ configuration (in
theory one not being used), he/she will have no team members listed.
Reason: XML configuration is used by server and WebService
is used by client.
In such case shouldn’t we have two separate repository
descriptors one for client and one for server with valid settings of
default-configuration-name attribute in both cases?
Edyta