I've been using Cairngorm for awhile, through 1.5 beta testing at least and now with Flex 2.0. I understand the concepts it implements and encapsulates, but my problem is with the many files that is needed to implement it. It seems that even a simple call to one cfc that returns a small amount of data is going to take parts of up to 5 files. The only thing that i've found real convenient is the ServiceLocator which makes it easy to switch out Services. I've tried several approaches at skimming this down, making generic command, event and delegate classes for example that can be used with just a bit of work. The problem is that while everything starts out looking real simple when I do this, it turns out, as I'm sure you all are aware of that things get complicated in a hurry. So while making everything it's own class allows all my objects to couple loosely, it makes maintenance a nightmare when all i'm doing is getting data from the server. Also, using Value Objects seems to be a pain because I usually tie them to database column names, and if they change, well, i have to go through all sorts of views, grid columns, forms, etc to get them sorted out My question is how are other people putting together enterprise level applications. We host more than 50 internal business applications. Many of them use alot of the same data. User information, dept lists, plant lists, permission levels and roles etc. Ideally I'd like to just code for these one time and reuse them over every application that needs them. It's a snow day here in Colorado, so any and all input would be greatly appreciated. If I look busy, my girlfriend won't make me shovel the sidewalk! :) Thanks, Brian
*** The information in this e-mail is confidential and intended solely for the individual or entity to whom it is addressed. If you have received this e-mail in error please notify the sender by return e-mail delete this e-mail and refrain from any disclosure or action based on the information. ***
