Yes, dividing the app might me a solution. Our different applications (based on Cairngorm2) are organized as follow. We prefer to only use 4 main directories : model, view, controller and service (structure we share for our ColdFusion server side applications).
/com/company1/commons/lib (commons libraries) /com/company1/commons/controls (commons controls) /com/company1/domain1/controller/ : CairngormEvents, shared between applications /com/company1/domain1/model/ : ValueObjects (business VO) and business managers, shared between applications /com/company1/domain1/service/ : ValueObjects (request/response service VO) and business delegates, shared between applications /com/company1/domain1/view/ : View components, shared between applications /com/company1/domain1/application/app1/controller/ : Controller and Commands, specific to app1 /com/company1/domain1/application/app1/model/ : ModelLocator, specific to app1 /com/company1/domain1/application/app1/service/ : ServiceLocator, specific to app1 /com/company1/domain1/application/app1/view/ : View components, specific to app1 /com/company1/domain1/application/app2/controller/ : Controller and Commands, specific to app2 /com/company1/domain1/application/app2/model/ : ModelLocator, specific to app2 /com/company1/domain1/application/app2/service/ : ServiceLocator, specific to app2 /com/company1/domain1/application/app2/view/ : View components, specific to app2 ... For several domain applications, sharing CairngormEvents, ValueObjects and Views usually make a lot of sense (for example when building a FrontOffice app and a BackOffice app). But there are so many ways to structure, organize and package applications... Benoit Hediard #affinitiz.com -----Message d'origine----- De : flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] De la part de Wally Randall Envoyé : jeudi 2 novembre 2006 14:28 À : flexcoders@yahoogroups.com Objet : [flexcoders] Large Cairngorm Directory structures I need to construct a directory structure for a MONSTER Flex/CF application. (300 forms, 150 reports). Does anyone have large system directory structures they would be willing to share? We are attempting to divide the system into several separate applications (for obvious reasons). Assuming we have 8 to 10 "sub- systems" sharing a common front-end menu hierarchy, how should we construct a directory structure for cairngorm: applicationroot \assets \com \adobe [why is this node needed?] \subapp1 \business \comand \control \model \view \vo \subapp2 \business \comand \control \model \view \vo ...etc -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/flexcoders/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
