>That's only true in a shared environment. I suspect that most Java
>development takes place on dedicated servers.
Probably true, but even in a dedicated environment having to give
all the development teams access to the CFMX web root is not
ideal, not to mention potential naming conflicts from requiring
all apps to store their class libraries off the same root.
And for companies like mine that support clients in both shared
and dedicated environments, it would be nice to be able to use a
single methodology (i.e. CFMX+Java) for all.
>Considering that CFMX is essentially an expanded WAR file itself, I suspect
>that things might be a little more complicated than they might appear at
>first glance.
Yes, I had forgotten about that. That does change things considerably.
I guess I'm just a little disappointed that the current reality
of CFMX+Java falls short of the (heightened) expectations I had
when I first heard about CFMX. I'll get over it :)
Dave Jones
NetEffect
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
