Not sure if this will help but did you check out the manual on cffile, 
http://openbd.org/manual/?/tag/CFFILE

that URIDIRECTORY attribute might be worth a look?



On Friday, July 8, 2016 at 1:50:08 PM UTC-5, John Moss wrote:
>
> I'm having a real struggle when I try to put a cfc on a host behind the 
> google load balancer:
>
> The REST invokation of the methods in the file work just fine, but the 
> SOAP does not work.
> I can add the service reference to the api in Visual Studio and it sees 
> all of the methods, so it successfully reads the WSDL file I think.
> When I make any call to any of the methods it does not work though.
> Looking at the wsdl generated, it looks like the path to the servers 
> behind the load balancer needs to be modified.
> The https is http and the port might need to be changed to 8080 so ok, I 
> didn't want to have to do this but I thought it would be relatively simple 
> to "wget" the wsdl file and modify it, then add it to the <cfcomponent> 
> like so: <cfcomponent name="myapi" 
> wsdlfile="#expandpath('/wsdl')#/myapi.wsdl>
>
> It doesn't seem to ever be able to find the file I specify--I even added a 
> mapping "/wsdl" to see if that made a difference.
> What I get is: *The tag produced the following error: WSDLFILE attribute 
> contains invalid value. Cannot locate: /USR/LOCAL/SITE1/API/24/MYAPI.WSDL*
>
> The location where it says it cannot locate the file is the exact location 
> of the file except it is in upper-case where there are no upper-case 
> characters in the path.
>
> I have tried various ways to do this to no avail.
>
> Does anyone out there have experience with this they could share?
>
> Thanks!
> -John Moss
>

-- 
-- 
online documentation: http://openbd.org/manual/
 http://groups.google.com/group/openbd?hl=en

--- 
You received this message because you are subscribed to the Google Groups "Open 
BlueDragon" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to