First I would ask the customer precisely how he knows that all three instances of Manakin are using something in common. If they are all showing the identical UI when they should not, that is one thing; if they are all showing identical content (communities, collections, items, bitstreams) when they should not, that is something else.
In the latter case I would first check each Manakin instance's context parameter "dspace-config" to ensure that each is pointing at a different DSpace installation. If that is so, then I would next check each DSpace instance to be sure that each is using a different database and a different assetstore. In the former case I'd expect that the wrong .war files were being deployed, since UI changes will be in files packed into the .war. Anyway, please tell us more details of how the three instances fail to differ as expected. -- Mark H. Wood, Lead System Programmer [EMAIL PROTECTED] Typically when a software vendor says that a product is "intuitive" he means the exact opposite.
pgpQXh6mqRMdJ.pgp
Description: PGP signature
------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
