* So, access-type would be an attribute on
the repository-connection-parameters.
* Perhaps we should change the name of subcontainers
to related-containers. The term subcontainers does imply a tree structure
whereas related-containers does not and I think we want to be able to create
and association between containers easily.
Edyta but this is why is it better to
generate code from the Schema rather than manually recode these changes.
From: corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Kalka, Edyta
Sent: Wednesday, July 19, 2006
8:57 AM
To: Corona
development
Subject: RE: [corona-dev]
ProjectContainer Definition updates
It has to be moved even deeper to
repository-connection-parameters element – this element now represents
physical data source location. Repository-configuration can contain more than
one repository-connection-parameters element (resource-subset is also nested
inside repository-connection-parameters).
Edyta
From: corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Everitt, Glenn
Sent: 19 lipca 2006 14:10
To: Corona
development
Subject: RE: [corona-dev] ProjectContainer
Definition updates
I forgot to list one item that was talked
about in another email to corona-dev. I think the access-type needs to
move from the Repository object to the RepositoryConfiguration. If we can
have a Repository that accesses data from more than one location – i.e.
team members from an XML file and a DBMS then I think the Repository
content-type remains the same but the access-type to the different locations is
different. I think this was one of the examples given by Pawel.
Please check with Pawel and let me know.
Glenn Everitt
From: Kalka, Edyta
Sent: Wednesday, July 19, 2006
5:38 AM
To: Everitt, Glenn
Cc: O'Flynn,
Dennis
Subject: FW: [corona-dev]
ProjectContainer Definition updates
And now attachments J
From: Kalka, Edyta
Sent: 19 lipca 2006 11:36
To: Everitt, Glenn
Cc: O'Flynn,
Dennis
Subject: FW: [corona-dev]
ProjectContainer Definition updates
Attached generated models (+ edit and
editor projects) with requested changes (model META-INFs contain schemas).
Regarding commiting to cvs – where
exactly do you want this code checked in – Compuware CoronaIncubator or
Eclipse CoronaIncubator ?
Edyta
From: corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Everitt, Glenn
Sent: 18 lipca 2006 23:56
To: Corona
development
Subject: [corona-dev]
ProjectContainer Definition updates
Edyta:
* I want to change the name of the packages from
org.eclipse.corona.container
org.eclipse.corona.container.project
To
org.eclipse.corona.model.container
org.eclipse.corona.model.container.project
* I also want to change
kind
type
To
content-type
access-type
* I also want the project names changed to match the package
names.
* I also want the GenericContainer_xxxxxx.xsd changed to
context-container-2006-07-18.xsd into the META-INF folder of
org.eclipse.corona.model.container
* I want the ProjectContainer.xsd changed to
project-context-container-2006-07-18.xsd and put into the META-INF folder of
org.eclipse.corona.model.container.project
* I want all of the code checked into (committed to)
CoronaIncubator including the generated Editor.
Thanks
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.
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.