For instance, I was going to write that indeed your port 8000 sounded more like a web
server port than a debugger port. I wondered if perhaps the tutorial by Dan you'd
mentioned had somehow not made that clear, but I didn't have time to look into it. The
docs will clarify such things, for sure.
Also, failure for a breakpoint to fire is indeed a common source of confusion Besides
the docs, you'll also find value in the knowledge base on the fusion-reactor.com site.
Hope you resolve your issue.
/charlie
> -----Original Message-----
> From: fusio...@googlegroups.com [mailto:fusio...@googlegroups.com] On
> Behalf Of EJ Jaquet
> Sent: Thursday, December 30, 2010 3:52 PM
> To: FusionDebug
> Subject: [fusiondebug] Re: Problem while trying to setup FusionDebug with
> Tomcaton VM
>
In that you said you changed it and it worked, I'm curious: did CF simply not come up
when the wrong port was used? That's what I would expect if it was already in use by
something else. If it came up, but you couldn't access it via FD, then as Kev said,
perhaps it was a firewall issue.
As for your problem stepping, well, it's not generally going to have anything to do
with the code itself. It's all about proper configuration, of both CF, FD, and perhaps
how you've opened the file in Eclipse. I'd rather not relate all the possible things
that could explain it. I had anticipated your problems by pointing out the value of
the docs and the knowledge base. Had you checked those out, especially:
http://www.fusion-reactor.com/support/kb/FDS-4.cfm
http://www.fusion-reactor.com/support/kb/FDS-100.cfm
Hope that helps.
/charlie
> -----Original Message-----
> From: fusio...@googlegroups.com [mailto:fusio...@googlegroups.com] On
> Behalf Of EJ Jaquet
> Sent: Thursday, December 30, 2010 4:28 PM
> To: FusionDebug
> Subject: [fusiondebug] Re: Problem while trying to setup FusionDebug with
> Tomcaton VM
>
> \
Sometimes things go very easily, sometimes people get tripped up. It's almost always a
very simple thing that explains it--once it's understood. The challenge is getting
there, which is all the more difficult to do over email, since there are just so many
little things that you may have done or not done that could be influencing things.
As for the checkbox you see, it could be that that was written for an older version of
FD. I don't work with it quite as much as I used to, so I'll have to leave others to
help you with that and the challenges.
I will say that the FD team has tried to help by providing simple tools/techniques as
part of the install and docs, which should help anyone get things up and running
correctly. I hear you saying you've "gone through the knowledge base" and "have done
everything according to the manual", so I'll understand your annoyance in that you're
still challenged.
As those KB articles haven't helped, perhaps others will come through with more
suggestions. Just be aware that the FD team is in Europe and so about 6 hours ahead of
US ET. You may not hear from them or others in Europe until the morning.
Sorry I couldn't be of more help.
/charlie
> -----Original Message-----
> From: fusio...@googlegroups.com [mailto:fusio...@googlegroups.com] On
> Behalf Of EJ Jaquet
> Sent: Thursday, December 30, 2010 5:36 PM
> To: FusionDebug
> Subject: [fusiondebug] Re: Problem while trying to setup FusionDebug with
> Tomcaton VM
>
> Hi Charlie,
>
You make an interesting point: given that it's new year's eve, there may be few who
will be on today, and perhaps into the weekend. Let's hope though. Along those lines,
I was hoping to convey in my last note that if you can be patient, it should be able
to be sorted, and hopefully it would be worth the wait, for the benefits it would give
you long afterward for being able to do debugging readily. :-)
/charlie
> -----Original Message-----
> From: fusio...@googlegroups.com [mailto:fusio...@googlegroups.com] On
> Behalf Of EJ Jaquet
> Sent: Friday, December 31, 2010 4:10 AM
> To: FusionDebug
> Subject: [fusiondebug] Re: Problem while trying to setup FusionDebug with
> Tomcaton VM
>
> Hi Charlie,
>
Some may recall that in my first email of the thread, I had said (among other things):
"As for your problem stepping, ... it's all about proper configuration, of both CF, FD
...."
It really is nearly always something in the setup that can trip one up. And yes,
differences in local vs remote config can also trip one up. Really, problems like this
have plagued CFML editors going back to CF Studio and Dreamweaver, and their features
to browse code on local vs remote servers (and CF Studio's CFML debugging that lasted
only for CF 4 and 5). It makes it also all the harder to anticipate and help
troubleshoot over email, but again, patience paid off. Enjoy FD.
/charlie
> -----Original Message-----
> From: fusio...@googlegroups.com [mailto:fusio...@googlegroups.com] On
> Behalf Of EJ Jaquet
> Sent: Saturday, January 01, 2011 5:08 AM
> To: FusionDebug
> Subject: [fusiondebug] Re: Problem while trying to setup FusionDebug with
> Tomcaton VM
>
> Hi Charlie,
>