Taffy logging BugLogHQ REST

[Cory Silva]

I am confused; we cannot get taffy to log our exception to BugLogHq.  So far we have:

• followed the taffy\examples\api_BugLogHQ closely (except for using REST)***
  
• tested the BugLogHq REST service and it is working
  
• made sure that this component resolves 
  createObject("component", "bugLog.client.bugLogService")

Note***:

We are using REST because my BugLogHQ is on another server and subdomain is this a correct assumption?  We could have used SOAP, but not the .CFC client right?

Taffy framework variables:

                exceptionLogAdapter = "taffy.bonus.LogToBugLogHQ",

exceptionLogAdapterConfig = {

bugLogListener = "https://buglog.domain.com/listeners/bugLogListenerREST.cfm",

bugEmailRecipients = "in...@domain.com",

bugEmailSender = "donot...@domain.com",

hostname = "DEV",

apikey = "123"

}

Any guidance or advise will be much appreciated.

[Adam Tuttle]

Are you getting any errors?

Adam

--
You received this message because you are subscribed to the Google Groups "Taffy Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to taffy-users...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Cory Silva]

No I am not getting any errors; which is fueling my confusion. 

[Adam Tuttle]

I guess start sticking in some dumps & aborts where Taffy calls out to the exception log adapter, to see where it goes wrong?

Adam

On Wed, Dec 17, 2014 at 6:37 PM, Cory Silva <corya...@gmail.com> wrote:

No I am not getting any errors; which is fueling my confusion. 

--

[Cory Silva]

Oh yeah duh; I am still learning how to debug coldfusion.  I will drill writeDump and abort into my brain!  

I found that one of our developers redefined onError in the application.cfc therefor Taffy's onError was never being called...  Everything is working as it is intended, now I just need to fix some SSL handshake issues on our BugLogHq server.

Thanks!

[Adam Tuttle]

No worries, we all forget it now and then.

You are free to override onError but may want to call super.onError(), too.

Glad you got it sorted!

--