On Tue, 8 Feb 2005 16:43:13 -0500, Ben Rogers <[EMAIL PROTECTED]> wrote: > > Because they want a J2EE app not a ColdFusion app. > > Which is just a matter of semantics, correct?
I see what you're saying, but not really. A ColdFusion app traditionally is nothing more than a mix of HTML, CFM, CFC, CFR, JS, and perhaps SWF files found under a web root. A J2EE app is much more than that. From Sun's site (http://java.sun.com/j2ee/1.4/docs/glossary.html#120385): "Any deployable unit of J2EE functionality. This can be a single module or a group of modules packaged into an EAR file with a J2EE application deployment descriptor. J2EE applications are typically engineered to be distributed across multiple computing tiers." As you can probably surmise, this additional stuff includes context root definitions, etc -- settings that define the environment as opposed to just the application. > > 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? So as not to inundate the user with the multitude of options provided in the Administrator, for one, and to make sure that a user doesn't change a particular setting or settings that your application relies on, for another. Further, I wouldn't want to dump settings and stuff in a production environment. While developers tend to "cheat" all the time, a production environment should be a pristine version of your application, devoid of all debugging code and settings. > > > 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. > It's not a question of smart vs. dumb or lazy. It's a question of what one is used to and whether or not they are willing to make the effort to learn a different process to deploy a J2EE application. If I have to log in to the JRun Admin Console to administer all my other J2EE apps but then use the CFMX Admin just to administer my CF apps, that's a bother to the sys admin, who, in large shops where standards are prevalent, don't have time for disparate systems. One could argue both sides quite convincingly, I'd wager, but at the end of the day, as I mentioned earlier, this particular feature really caters to pure J2EE admins as opposed to developers like you and me who are used to CF's deployment experience. Regards, Dave. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:193733 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
