ivan
February 3, 2024, 6:16pm
1
In the past I have integrated logbox 6 into an application outside the coldbox framework. Now I noticed that starting with version 7 of logbox there are so many references to coldbox all over the code. Is there no longer a standalone version?
Here it seems the only dependency is cbproxies.
ivan
February 17, 2024, 4:26pm
3
Ciao Roberto,
}
// Is this a raw CFML Exception?
if (
( isObject( variables.extraInfo ) || isStruct( variables.extraInfo ) )
&&
structKeyExists( variables.extraInfo, "stacktrace" ) &&
structKeyExists( variables.extraInfo, "message" ) &&
structKeyExists( variables.extraInfo, "detail" )
) {
return new coldbox.system.web.context.ExceptionBean( variables.extraInfo ).$toString();
}
// Component XML conversion
if ( isObject( variables.extraInfo ) ) {
return getXmlConverter().toXML( variables.extraInfo );
}
// Complex values, return serialized in json
return getUtil().toPrettyJson( variables.extraInfo );
}
which in the version of LogBox distributed on ForgeBox is:
return new testbox.system.web.context.ExceptionBean( variables.extraInfo ).$toString(); refers to a path that exists only in ColdBox.
Perhaps @bdw429s could correct me on this.
Yes, the TestBox build of LogBox standalone is broken. @lmajano can you address this?
2 Likes