Trying to figure something out. Hope someone here may have an idea. I am working to port over a legacy app into FW/1. Where I am struggling is a couple hard requirements. The first is that I have to have the app still work with old urls. Second, is that I still have to support webservice WSDL calls. The part I am struggling with is supporting the legacy WSDL urls. They will eventually be converted to rest calls but that is down the road. Normally I would just put in some url rewrites and be done with it. However, I can't (not my decision). URL rewrites are completely off the table as a solution. I have been able to get it working in parts using onMissingTemplate and a redirect. That works, but also doesn't. Redirects on a webservice call causes some odd errors on the caller. So I have to figure it out without using a redirect. Ideally, if I can just call a controller from onMissingTemplate that would probably work. However, I can't seem to get that to work either. So, any ideas? I feel like I am missing something simple that would handle this but ???

Can you use application routes to take an old URL and have it invoke the desired controller & item? You should be able to map multiple URLs to the same handler, so you can have both the old URL and your preferred URL operating at the same time, possibly. Assuming you're collecting the same data through the URL, anyway.

Yea... getting it to invoke a controller would be ideal. However, I can't seem to get that to work properly from inside onMissingTemplate. From what I can tell, inside this function all the "fw/1" parts are not available .

Do your WSDL calls look something like

/foo/bar.cfc?wsdl

It would be the latter. All the legacy code is being put into FW/1. Ultimately we are getting rid of the WSDL urls and converting everything to rest but we need to support the WSDL in the mean time.

I figured it was the latter after posting because you mentioned

onMissingTemplate

. Yeah that's a tricky one - not sure how to handle that at a an app level.

I might be missing something, but if the URL route is defined and pointed to a controller that exists, why is onMissingTemplate in the mix?

Because if you call a script that doesn't exist then the CFML engine will say "no idea what to do with that" so it then calls the onMissingTemplate

I guess i'm used to an Apache rewrite that pushes any request to a non-existent file through to the CF application for handling

yea.. that is a possibility. That was kind of my last resort. But like I said prior, If I could figure out how to call a controller from onMissingTemplate all would be good

I think

onMissingTemplate

is called really early as it's the CF engine calling that - so would be before FW/1 is in the mix.

It is

Wonder if

onCFCRequest

would help...

I can kinda "force" fw/1 to be involved in OnMissing by calling onRequestStart

You may be able to override the action as think that's stored in the request scope. So that when FW/1 runs it uses the 'forced' action.

Thanks for the ideas/input. I have been able to run controller() in onMissingTemplate. However nothing that should be happening happens. Dumping the request scope I do see the controller has been queued in the trace. But that is where the trace ends. Trying to run different combinations of the application "on" functions doesn't seem to work either.