Something the docs never made clear, but the default "cfusion"
instance is NOT supposed to be used in production. It's there as a
mechanism to create/control your other instances/clusters.
Of course, that's not to say you can't use it, but that isn't it's purpose.
(I had a discussion with a membe
> righto, I've always used the JMC for all this. Just thought
> the new ent mgr deal was going to be a tastier treat. oh
> well, back to JMC land.
Despite the issues mentioned, I still prefer using the CF tools, actually.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
Fig Leaf Sof
righto, I've always used the JMC for all this. Just thought the new ent mgr
deal was going to be a tastier treat. oh well, back to JMC land.
DK
On 8/28/06, Dave Watts <[EMAIL PROTECTED]> wrote:
>
> > Ok, finally upgraded to CF7 this weekend. Something I found
> > out the hard way, and apparentl
> Ok, finally upgraded to CF7 this weekend. Something I found
> out the hard way, and apparently overlooked during the alpha
> and beta programmes! We use JRun/CF clusters. I installed
> CF 7 and hit the new enterprise manager
> tool there. Nice but
>
> 1) You can't include the default CF
Ok, finally upgraded to CF7 this weekend. Something I found out the hard
way, and apparently overlooked during the alpha and beta programmes! We
use JRun/CF clusters. I installed CF 7 and hit the new enterprise manager
tool there. Nice but
1) You can't include the default CF install in the c
5 matches
Mail list logo
