> Because they want a J2EE app not a ColdFusion app. Which is just a matter of semantics, correct?
> With the new Admin > API you can build a custom console into your app for deployment > instead of the full CF Admin - because you will only need the subset > of admin features necessary for your app. I'm at a loss for why I'd want to duplicate the functionality of the ColdFusion administrator. Let me rephrase that. I think the admin API is useful. I can definitely see uses for that. However, why would I want to disable the ColdFusion administrator? You'd lose access to the log file viewer, the ability to dump settings, etc. I'm sure you could duplicate all this with the admin API, but what would be the purpose? > I demo'd this at Fusebox 2004 and I showed a Flash form-based wizard > that could set up a data source for the freshly installed application. > No source, no CF Admin. Simple to install for a J2EE shop, simple to > configure. I think we have different opinions of J2EE shops. :) I can't imagine a J2EE shop that can't figure out how to set up a data source using the ColdFusion Administrator. Ben Rogers http://www.c4.net v.508.240.0051 f.508.240.0057 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:193729 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
