Odd Plugin Behavior

Communities ColdBox HMVC
1

Has anyone ever run into an issue where you call one plugin but
receive another? I've seen this happen a couple of times randomly in
one of our apps.

Here's the call to the session plugin in the onRequestStart() method
that threw the error-

Main.cfc line 57 = <cfset var user =
getPlugin('sessionStorage').getVar('user')>

What I received back from CB was the Json plugin.

Here's the stacktrace:

coldfusion.runtime.TemplateProxy$InvalidMethodNameException: The
method getVar was not found in component coldbox.system.plugins.JSON.
  at
coldfusion.runtime.TemplateProxy.throwInvalidMethodNameException(TemplateProxy.java:
749)
  at coldfusion.runtime.TemplateProxy.invoke(TemplateProxy.java:478)
  at coldfusion.runtime.TemplateProxy.invoke(TemplateProxy.java:337)
  at coldfusion.runtime.CfJspPage._invoke(CfJspPage.java:2360)
  at cfMain2ecfc1369041843$funcONREQUESTSTART.runFunction(E:\public
\wwwroot\site.com\handlers\Main.cfc:57)
  at coldfusion.runtime.UDFMethod.invoke(UDFMethod.java:472)
  at coldfusion.filter.SilentFilter.invoke(SilentFilter.java:47)
  at coldfusion.runtime.UDFMethod
$ReturnTypeFilter.invoke(UDFMethod.java:405)
  at coldfusion.runtime.UDFMethod
$ArgumentCollectionFilter.invoke(UDFMethod.java:368)
  at
coldfusion.filter.FunctionAccessFilter.invoke(FunctionAccessFilter.java:
55)
  at coldfusion.runtime.UDFMethod.runFilterChain(UDFMethod.java:321)
  at coldfusion.runtime.UDFMethod.invoke(UDFMethod.java:517)
  at coldfusion.runtime.TemplateProxy.invoke(TemplateProxy.java:496)
  at coldfusion.runtime.TemplateProxy.invoke(TemplateProxy.java:355)
  at coldfusion.runtime.CfJspPage._invoke(CfJspPage.java:2301)
  at coldfusion.tagext.lang.InvokeTag.doEndTag(InvokeTag.java:389)
  at coldfusion.runtime.CfJspPage._emptyTcfTag(CfJspPage.java:2723)
  at

2

Hmm not really. What version of coldbox

Luis Majano
President
Ortus Solutions, Corp

3

I saw that a couple of times when I was on release candidate 1 that had the var-scoping issue (or whatever it was) in wirebox. Occasionally the wrong thing would get autowired into a handler or model.

The problem disappeared with RC2 (and 3.0 final, of course).

I don't know if that's what Sam is experience, but it's a guess.

~Brad

4

Brad,

Yep, we're using RC1 on this project so that's likely the culprit.
Thanks for the reply!

Sam