Besides unit testing of our services with mock objects we have something which we call stages. A stage is simply a hivemodule which contains environmental specific "settings", e.g. symbol sources that define URLs depending on the specific stage. All other hivemoduls, do not contain such information. So there are stages like: dev, test and production. When running the "application" the appropriate stage is just "linked" to the application, i.e. the stage jar is set on the class path. This work quite well for us. Stefan
________________________________ Von: Joel Trunick [mailto:[EMAIL PROTECTED] Gesendet: Mo 27.06.2005 17:55 An: [email protected] Betreff: Run modes: Dev, Test, Production Does Hivemind have some support for supporting different modes of operation (ie. Dev, Test, Production), or is there a common paradigm to support this with HiveMind? I see Ruby supports such a notion, I find it odd (and time-consuming) that J2EE doesn't support this natively. Joel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
<<winmail.dat>>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
