Skip to main content
Known Participant
July 2, 2011
Question

Could not generate stub objects for web service invocation in ColdFusion

  • July 2, 2011
  • 2 replies
  • 8023 views

I was able to call the services on the development box - windows server without any problem at all, everything was working fine but the moment i uploaded to a linux box production server I get this error. "Could not generate stub objects for web service invocation in ColdFusion"

What could be the cause of this problem, i have googled a lot but no solution yet any ideas.

    This topic has been closed for replies.

    2 replies

    Known Participant
    July 3, 2011

    thanks adam for your time

    Inspiring
    July 2, 2011

    Is it a case-sensitivity issue?  If you have /path/to/MyComponent.cfc, you need to always refer to it as path.to.MyComponent. "mycomponent" will work on Windows, but it will not work on case-sensitive file systems.

    --

    Adam

    Known Participant
    July 2, 2011

    Thanks for your response, I have checked the case sensitive issue, the url is in the required case. The entire error is:

    Cannot generate stub objects for web service invocation.

    Name: https://******/TransactionQueryWs.asmx?wsdl. WSDL: https://*********/TransactionQueryWs.asmx?wsdl. java.io.FileNotFoundException: /opt/coldfusion8/stubs/WS334836208/org/tempuri/TransactionQueryWSSoap.java (No such file or directory) It is recommended that you use a web browser to retrieve and examine the requested WSDL document to ensure it is correct. If the requested WSDL document cannot be retrieved or is dynamically generated, it is likely that the target web service has programming errors.

    **Note i have used asterix to max the original url, i used a complete url

    Inspiring
    July 2, 2011

    Aah... I've had this before years ago on a Solaris system.  And I can't - for the life of me - remember what caused it.

    Basically the CFC file is failing to be compiled at all, for some reason... that's why there's a reference to a .java file rather than a .cfm file.

    I wonder was it because we had some UTF-8-encoded characters in the CFC file and had not put the appropriate CFPROCESSINGDIRECTIVE tag in it?

    I'll have a look around to see if I can find anything about this...

    In the mean time, can you browse directly to the CFC and successfully get:

    a) its autogenerated docs (so just browse straight to the CFC);

    b) its WSDL (browse to it, but with ?wsdl on the URL too).

    --

    Adam