Author Topic: Refresh XML controlled Packages (Read 4101 times)

Stefan · « **on:** January 25, 2005, 08:49:12 pm »

I would like to know what are the best practices for updating XML saved packages which could be potentially be modified by more than one project or more than one person.
I did a small exercise with two projects containing same package controlled as XML file. The first project added one extra attribute to a class contained in the package and saved as XML. The second project reloaded the package, but the new attribute was not reflected.
What is the best way to reload a controlled package, which was changed by other developers and eventually has cross-references to current project packages? Does it matter if two projects share same controlled package?

Stefan

Martin Terreni · « **Reply #1 on:** January 25, 2005, 10:38:12 pm »

I have teams working two ways:

1) concurrency controll (we use ClearCase). we save it within CC and merg it same as we would with code (CC can merge XMI).
2) we have for each package an owner which aproval is needed to change package.
I think you can also use EA replications.

Molto Mike · « **Reply #2 on:** January 25, 2005, 11:05:55 pm »

Martin:

IMHO replication and controlled packages are two different approaches to the same problem of sharing models and control modifications.

Two more options are the concurrent access of the same EAP file (access database file) on a shared folder and the usage of a real database.

I am not sure it is a good idea to mix controlled packages and EA replication. Do you have a certain use-case in mind here?

Martin Terreni · « **Reply #3 on:** January 25, 2005, 11:35:12 pm »

I thought it was clear thet I ment replication as a separate unrrelated way of sharing a process.
(I should have been more clear...).

Any way I doubt if you can open EAP file (which is actualy an MDB) by two diferent users both with R/W permition.

Tjerk · « **Reply #4 on:** January 26, 2005, 12:36:11 am »

EAP (MDB) file can be opened by more than one person at the same time. I've used it e.g. with 5 persons at the same time using EA Corporate edition. Use JET4 (see EA options) for better reliability / stability.

Stefan · « **Reply #5 on:** January 26, 2005, 01:00:14 pm »

Matin, thanks for your reply. Related to 1) What is the procedure used by developers for refreshing the packages managed by different owners. Let's say every morning everybody "Load Package from File". Did you have any issues with this way of updating the whole project?

Stefan

Martin Terreni · « **Reply #6 on:** February 05, 2005, 09:15:22 am »

We refresh it every time we open it.

Sparx Systems Forum

News: