Bugzilla – Full Text Bug Listing
| Summary: | [sites] Changes to a running site don't take effect right away | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Mark Macdonald <mamacdon> |
| Component: | Server | Assignee: | Mark Macdonald <mamacdon> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P2 | CC: | antonm, john.arthorne |
| Version: | 0.2 | ||
| Target Milestone: | 6.0 M1 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
I expect just restarting is our answer for 0.2? (In reply to comment #1) > I expect just restarting is our answer for 0.2? Yes. Restarting is less of a hassle now that you can do it from the same page. Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html |
Orion 0.2M6 1. Create a site. 2. Edit the site, and add an entry that exposes a folder from your workspace (say FolderA) on the site. 3. Start the site. 4. Go back to the edit-site page, and add an entry for a different folder (say FolderB). Hit Save. 5. Although it appears to save correctly, you will not be able to access FolderB on the running version of the site. The new entry you added in Step 4 doesn't take effect until you stop and restart the site. This is confusing, and the right answer is probably to support hot-replacement into a running site. We should also think about how this will affect the (future) use case where the hosting-server and the file-server are different machines. Ultimately this approach should lead toward a clearer separation between a definition of a site ("site configuration") and a record of a site that is running somewhere ("hosted site"). Right now the former is a first-class resource, but the latter is really not.