| RE: [corona-dev] ProjectContainer Definition |
|
Please notice one thing: We have repository uri (attribute of repository element) like this: <repository
kind="http://www.eclipse.org/corona/repositoryTypes/teamMemberRepository" name="TeamMemberRepository" type="http://www.eclipse.org/corona/repositoryTypes/xmlRepository" uri="http://www.eclipse.org/corona/repository/TeamMemberRepository"> which serves as repository unique identifier and not as e.g. database
url. We can have for instance multiple jdbc repositories defined within the
same project container that will retrieve from the same database different
resource subsets: <repository
kind="http://www.eclipse.org/corona/repositoryKinds/teamMemberRepository"
name="TeamMemberRepository2"
type="http://www.eclipse.org/corona/repositoryTypes/jdbcRepository"
uri="http://www.eclipse.org/corona/repository/TeamMemberRepository2">
<description>Team member jdbc repository definition </description>
<repository-configurations
default-configuration-name="members_2">
<repository-configuration name="members_2">
<repository-connection-parameters>
<repository-connection-parameter
name="url"
value="jdbc:postgresql://corona:5432/teamMembers2"/>
<repository-connection-parameter name="driver"
value="org.postgresql.Driver"/>
<repository-connection-parameter name="user"
value="anonymous"/>
</repository-connection-parameters>
<resource-subset selection-criteria="select * from users"
type="http://www.eclipse.org/corona/resourceSubsetTypes/JdbcResultSet"/>
</repository-configuration>
</repository-configurations> </repository> <repository
kind="http://www.eclipse.org/corona/repositoryKinds/rightsRepository"
name="RightsRepository"
type="http://www.eclipse.org/corona/repositoryTypes/jdbcRepository"
uri="http://www.eclipse.org/corona/repository/RightsRepository">
<description>Team member jdbc repository definition </description>
<repository-configurations default-configuration-name="rights_2">
<repository-configuration name=" rights_2">
<repository-connection-parameters> <!—we connect
to the same database à
<repository-connection-parameter
name="url"
value="jdbc:postgresql://corona:5432/teamMembers2"/>
<repository-connection-parameter name="driver"
value="org.postgresql.Driver"/>
<repository-connection-parameter name="user"
value="anonymous"/>
</repository-connection-parameters> <!—but we
retrieve different resource subsets à
<resource-subset selection-criteria="select * from rights"
type="http://www.eclipse.org/corona/resourceSubsetTypes/JdbcResultSet"/>
</repository-configuration>
</repository-configurations> </repository> Summing my point of view: repository
uri is the identifier, repository connection parameter containing information
on jdbc url, file uri etc shows physical data source location (but is not
unique and therefore cannot be used as the identifier). Another thing is that we could use
such connection parameter to retrieve information on what type of persistency is
going to be used – but please decide if it is a good way of doing it? Edyta -----Original Message----- > 2. what is the format or access method to storred data (xml file,
data > base, web service call, ...) Wouldn't the URI have this information based upon the URI's scheme?
For example: * http:// * cvs:// * jdbc:// * file:// -----Original Message----- From: corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Marcin Okraszewski Sent: Monday, July 17, 2006 10:06 AM To: Corona development Subject: Re: [corona-dev] ProjectContainer Definition > *Is such situation possible - in other words can we have two
separate > team member repositories defined within the same project container
(in > such situation to receive list of all team members we would have
to > sum results parsed from xml and tuples from database)????* > Event if there is a single repository, we need two information: 1. what is storred within a repository (team members, files, list of bugs or whatever may be storred) 2. what is the format or access method to storred data (xml file, data base, web service call, ...) Currently we call 1. as "kind" and 2. as "type".
The names may be different, but however we call them, we need them. Marcin 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. _______________________________________________ corona-dev mailing list corona-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/corona-dev 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. _______________________________________________ corona-dev mailing list corona-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/corona-dev |