Hey Dan,
You probably need to add wsversion=1 attribute to the cfcomponent tag for your custom remote facade. That's now required for any custom remote facade on cf 10 and above.
Marc
--
You received this message because you are subscribed to the Google Groups "mxunit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mxunit+un...@googlegroups.com.
To post to this group, send email to mxu...@googlegroups.com.
Visit this group at http://groups.google.com/group/mxunit.
For more options, visit https://groups.google.com/d/optout.
Nothing has really changed... Which has been the status for some time. Nome of us who contributed heavily to mxunit are working with CF anymore, or at least aren't using it much. I've done a bad job of outreach on this part, due to very limited time (a bad excuse, I know)
Dan,
What happens when you hit localhost/mxunit/framework/remote facade.cfc?
Also, is there an application.cfc in your test folder that might be causing troubles? Basically, if ping doesn't work, the problem is usually in something outside of mxunit, such as application.cfc or a misconfigured server
Marc
Dan,
Your remotefacade should extend mxunit remotefacade, not coldbox base test. Your tests should extend coldbox. Your remotefacade will likely also be empty except for the cfcomponent tag.
You don't need to include application.cfc anywhere. As long as the remotefacade is in the same directory or a subdirectory as the application.cfc, it'll run under that application.cfc context.
Marc