At 10:28 AM 7/23/01 -0400, Mark Gebhardt wrote:
>Hi All
>
>We have recently had a look at Webware and selected it as our
>development
>platform for an e-commerce application we are developing.
Great choice :-)
>As we expand the team that is working on the application, I am running
>into one or two hassles and though that someone else might have had
>similar experiences and be able to offer some advice.
>
>We have our code repository stored in CVS and individual developers
>check
>out the entire site and work on their sections. In order to test their
>applications, I have set up Webware with a context pointing to each
>developer's working directory.
>
>The problem arises in that each working directory contains a number of
>packages and the same packages exist in each developer's directory and
>this seems to confuse Webware, as it is accessing packages out of other
>developer's directories. Basically, sys.path gets populated with
>multiple
>directories containing the same package and this causes a problem
>
>I have tried using OneShot.cgi, but this often seems to result in errors
>where WebKit.cgi works perfectly.
>
>Can anyone offer any advice on this?
>
>Thanks
>Mark
My advise would be to just set up totally separate copies of the app server
for each developer to avoid these problems. Contexts are not isolated
enough from one another to allow what you're trying to do.
You can look into the "MakeAppWorkDir.py" stuff that Robin Dunn checked
into CVS recently. Its purpose is to set up independent working
directories that are isolated from one another, but share common Webware
code from a central location. But there's also nothing wrong with making a
full copy of the entire Webware tree for each developer.
--
- Geoff Talvola
[EMAIL PROTECTED]
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webware-discuss
