> I agree that they _should_ be separated, but it appears that there > would need to be significant refactoring to get a clean separation of > the web app from the core. The organization of Federation would need > to be tackled. Also the caching crosses the boundaries as > IWikiApplication requires references to the core.
I'm not looking at the code right now, so I'm not sure exactly what you mean, but I wasn't implying that the independence need to be bidirectional. That is, while I don't like anything that makes the core (unit tests or code itself) depend on the web app, I think it's okay for the web app (unit tests or code itself) to depend on the core. > While I could create a separate test project it still needs all the > same references as the current UnitTests project in order for > MockWikiApplication to compile. This seems to defeat the value of the > separation in that source code changes may now affect 2 sets of unit > tests rather than a single set. If the tests themselves are orthogonal (which they should be) then I don't think it matters whether they're in one project or two, does it? But maybe I'm missing something here. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Flexwiki-users mailing list Flexwiki-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flexwiki-users
