We have thought about some ideas:
* keep pages in the database which override certain html in the .woa. We need to write some code to check the database for relevant html upon each page request. * put the common pages and code into a framework and make changes in the .woa directly. Version control might get a little tricky. * have one project and code, but use subversion to maintain separate html repositories which get copied into the .woa when we deploy. No special deployment code, but some tricks to managing development processes.
Each of these approaches seem to have their pros and cons. Has anyone else had a similar challenge and found a successful solution?
Ari Maniatis --------------------------> ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 PGP fingerprint 08 57 20 4B 80 69 59 E2 A9 BF 2D 48 C2 20 0C C8
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com This email sent to [email protected]
