We can allow for more than one repository-connection-parameters
element per repository-configuration but in such case we have to also nest
resource-subset inside repository-connection-parameters (resource subset is to
be defined for given physical repository).
Edyta
From:
corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Everitt, Glenn
Sent: 17 lipca 2006 19:02
To: Corona development
Subject: RE: [corona-dev]
ProjectContainer Definition
Could we just change the schema to allow
more than one repository-connection per repository-configuration? This
way you only have one “logical” repository and it can refer to more
than one repository implementations.
Glenn Everitt
From: corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Kalka, Edyta
Sent: Monday, July 17, 2006 8:03
AM
To: Corona
development
Subject: RE: [corona-dev]
ProjectContainer Definition
The reason of adding kind is as follows:
Let’s assume we have team member
repository stored in a xml file. We can set type to something like: http://www.eclipse.org/corona/repositoryTypes/teamRepository
or if we don’t want to use uri to:
teamRepository. But what if we want to change team members repository to
database – or we want to add two seperate repositories having data on
team members – are we going to support such situation or we assume that
such situation will never happen ?
In other words – is type
“teamRepository” enough to define that we have team members inside
xml (and/or other persistence storage) ?
Edyta
From: corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Everitt, Glenn
Sent: 17 lipca 2006 13:49
To: Corona
development
Subject: RE: [corona-dev]
ProjectContainer Definition
When I was putting definition of
ProjectContainer together I was thinking Type was suppose to indicate the type
of repository. I am sure what is meant by persistence method regarding
repository. My thought was that once you knew what type of repository
type you were working with the repository itself would know the kinds of things
it contained. If you wanted only a sub-set of the resources in the repository
you would specify either a resource-subset or a selection-criteria ( which I
can’t find in the definition anywhere).
Is the Kind needed for the user interface
so it doesn’t have to connect to the repository and determine the of
resources it contains?
Glenn Everitt
From: corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of O'Flynn,
Dennis
Sent: Monday, July 17, 2006 6:54
AM
To: Corona
development
Subject: RE: [corona-dev]
ProjectContainer Definition
There are now 3 fields that provide some context to a
ProjectContainer's Repository:
1) Type
2) URI
(specifically the URI scheme)
3) Kind
Only the URI has a specific format. Both Type and Kind are free
format, it is up to the container context (e.g. Project) to define the format and
meaning of these fields. It would be helpful if there were some
guidelines, with examples, on how these fields should be used.
-----Original Message-----
From: corona-dev-bounces@xxxxxxxxxxx
[mailto:corona-dev-bounces@xxxxxxxxxxx]
On Behalf Of Kalka, Edyta
Sent: Monday, July 17, 2006 6:36 AM
To: Corona development
Subject: RE: [corona-dev] ProjectContainer Definition
One more update - kind attribute added to repository definition. Not
needed container-kind removed.
Edyta
-----Original Message-----
From: corona-dev-bounces@xxxxxxxxxxx
[mailto:corona-dev-bounces@xxxxxxxxxxx]
On Behalf Of Kalka, Edyta
Sent: 17 lipca 2006 10:49
To: Corona development
Subject: RE: [corona-dev] ProjectContainer Definition
Container-kind added go Generic Container schema - see attachment.
Edyta
-----Original Message-----
From: corona-dev-bounces@xxxxxxxxxxx
[mailto:corona-dev-bounces@xxxxxxxxxxx]
On Behalf Of Marcin Okraszewski
Sent: 17 lipca 2006 10:17
To: Corona development
Subject: Re: [corona-dev] ProjectContainer Definition
We defenitely need a "kind" attribute in the repository
definition.
Currently there is a "type" attribute which determins what is
a
persistance method for the respository (eg. XML, JDBC, file, etc.). But
we still need to know what kind of information it provides - if it is
team member, artifact or web page repository.
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.
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.
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.
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.