Handlers aren’t directly invoked, they are run as part of the framework. If you need WSDL, then use proxies. A proxy can directly interact with your services or they can run Coldbox events via process(). Just remember a proxy runs outside the normal Coldbox request lifecycle so it doesn’t trigger interception points like preProcess() so make sure you secure them appropriately if you’re not executing events.
SES (or any other framework setting) has no bearing on Proxys. They just just stand alone CFCs laying around your web root that you hit with Ajax or Flash remoting just like you would if you weren’t using a framework. The just have the ability to conjure up the ColdBox controller and “proxy” requests along if you wish.
Yeah I tried all of that and have read that link. I think the problem may be the SES URL re-writer that we are using to make SES work with tomcat.
My proxy is under the remote folder, going to see if I can put in a filter to the URL re-write rules to exclude proxys.
Can I ask are you using Flex or some other application to call the RPC?
One thing that many people tend to forget, is that an RPC is just an entry point. WSDL is just Adobe’s way of doing RPC’s… If you are using Flex and need WSDL, I would maybe switch to RESTful instead and get access to the entire framework.
At this point I’m just trying to access through the URL of a web browser. I should be able to do www.abc.com/remote/myProxy.cfc?wsdl and get a response. But that is not working. The WSDL is a global file that lets other systems know what functions are available to it. So system like .net need the WSDL to build the reference object.
We are not using Flex. Eventually we will be calling it from different applications including SSIS and other coldbox applications.
Yes I know what a WSDL is, I haven’t used them in 3 years. Basically WSDL is Adobe’s version of SOAP and that is not even worth talking about. There is nothing better than a well documented API that can be called via RESTful.
The Issue was because of the URL re-writing happing on the tomcat side. I was able to add a condition to the re-write filter to exclude any request containing our proxy folder from being re-written.
I can now access my proxy file as an web service. I am looking at the idea of using REST though since it does work better with SES.