| RE: [corona-dev] ProjectContainer Definition |
|
What software components will use the ‘kind’ attribute http://www.eclipse.org/corona/repositoryKinds/.... What will the ‘kind’ attribute
be used for? I think you are using the type
incorrectly. I think the type tells you it is a TeamMember Repository and
I think the Repository connection information tells you how to connect to
it. So, once we are connected to the repository do we care whether
it is a database or XML? I think we only care about the API to get / set
resources to in the repository. What uses the API for interacting with
the repository? Glenn Everitt From: One more comment: for uri used inside
repository kind attribute should start with http://www.eclipse.org/corona/repositoryKinds/.... From: On the basis of our current project
container model I’ve defined some project container having 2 team members
repositories defined to show why repository kind and type attributes
could/should(?) coexist: <?xml
version="1.0" encoding="UTF-8"?> <sdo:datagraph
xmlns:project="http://www.eclipse.org/corona/container/project"
xmlns:sdo="commonj.sdo"> <changeSummary
xmlns=""/>
<project:project-context-container name="SampleEclipseProject">
<container-uri>http://www.eclipse.org/corona/container/sampleEclipseProject</container-uri>
<container-path>
<container-path-element>http://www.eclipse.org/corona/container/sampleEclipseProject</container-path-element>
</container-path>
<container-type>http://www.eclipse.org/corona/containerTypes/eclipseProject</container-type>
<container-description>Sample eclipse
project</container-description>
<repositories> <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">
<description>Team member xml repository definition</description>
<repository-configurations
default-configuration-name="members_1">
<repository-configuration name="members_1">
<repository-connection-parameters>
<repository-connection-parameter name="fileURI"
value="file:///model/data/teamMembers.xml"/>
</repository-connection-parameters>
<resource-subset selection-criteria="//team/members"
type="http://www.eclipse.org/corona/resourceSubsetTypes/XPathResultSet"/>
</repository-configuration>
</repository-configurations> </repository>
<repository
kind="http://www.eclipse.org/corona/repositoryTypes/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>
</repositories>
</project:project-context-container> </sdo:datagraph> 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)???? From: Thanks Edyta, I had forgotten that the
selection criteria were specified as an attribute the resource-subset. I
was looking for it on repository I couldn’t decide where to put when I
first defined this schema. I mis-typed one of the comments below: . I am sure what is meant by
persistence method regarding repository. Should have read . I am not sure what is meant by persistence method regarding
repository. Regarding this comment 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. The repository definition points to a
repository configuration. The repository configuration points at the
repository implementation. The same repository implementation can be
pointed at by more than one repository definition. For example: - <repository name="CoronaBugRepository" type="Corona Defects" version="01.00.00" repository-configuration="CoronaBugRepositoryConfiguration" /> - <repository-configuration
name="CoronaBugRepositoryConfiguration"> - <repository-connection> <repository-uri>https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Corona </repository-uri>
</repository-connection> </repository-configuration> repository
name="MylarBugRepository" type="Mylar Defects"
version="01.00.00"
repository-cofiguration="MylarBugRepositoryConfiguration"> - <repository-configuration
name="MylarBugRepositoryConfiguration"> - <repository-connection> <repository-uri>https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Mylar</repository-uri>
</repository-connection> Or possibly using URI’s to point to
the definition, but then the user interface would have to look up type
definition before displaying. type="http://org.eclipse.corona.repository.type.defect/CoronaDefects" Glenn Everitt 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. |