| RE: [corona-dev] Team Member Repository Descriptor |
|
The configuration selected depends on the adapters defined
for the "org.eclipse.corona.container.RepositoryAdapter" extension point.
There is a separate instance defined for the client and the server. The
default configuration is no longer
used.
-org.eclipse.corona.container.project defines the
extension point for the client
-org.eclipse.corona.repository.xml.team define the
extension point for access using XML(the server
side).
The old behavior was changed when the new
TeamRepository code was checked in.
The default-configuration can/should be removed from
the descriptor.
Jim Wright
From: corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Kalka, Edyta Sent: Tuesday, February 06, 2007 9:56 AM To: Corona development Subject: [corona-dev] Team Member Repository Descriptor 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 The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. |