Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [corona-dev] Team Member Repository Descriptor

See my comments within original email…

 


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?

  • [O'Flynn, Dennis]
  •  Both configuration types (client and server) refer to the same TeamMemberRepository.  One is  local access, the other remote.
  • The RepositoryAdapterFactor uses the RepositoryAdapter extension point to match which RepositoryAdapter extension to use based upon the Corona environment type (client/server).

 

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.

[O'Flynn, Dennis] The ContextContainer is shared within a distributed environment.  It must contain the connection parameters for both client and server environments.  Only an administer should update the definition of a ContextContainer.  “If anyone tries to remove a configuration,” they risk breaking the ability to share a common ContextContainer definition within the distributed environment.

 

 

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?

[O'Flynn, Dennis] The RepositoryDescriptor defines a repository type, in this case TeamMemberRepository.  This repository can be accessed locally within a “server” environment, or remotely by a “client” environment.   Regardless, each environment is actually access the same repository.  Since both client and server environments are trying to connect to the same TeamMemberRepository, they each have their own set of connection parameters.

 

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.

Back to the top