This could be a blue herring, (ha ha) but I tried calling the "bad" cfc on the OpenBD Installer version machine - but invoking it from the "good" OpenBD tomcat war version machine. Here's the error it threw:
Unrecognized error code: Invalid service locator generated for http://[target domain]/feed/utility.cfc?wsdl. Cannot invoke method: getUtilityCfc. null loader constraint violation in interface itable initialization: when resolving method "manageit.feed.utility_cfc.UtilityCfcSoapBindingStub.getUserInfo(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Lcom/newatlanta/wstypes/StructMap;" the class loader (instance of com/naryx/tagfusion/cfm/xml/ws/dynws/DynamicCacheClassLoader) of the current class, manageit/feed/utility_cfc/UtilityCfcSoapBindingStub, and the class loader (instance of com/naryx/tagfusion/cfm/xml/ws/dynws/DynamicCacheClassLoader) for interface manageit/feed/utility_cfc/Utility have different Class objects for the type com/newatlanta/wstypes/StructMap used in the signature I assume this is probably because the bad web service is returning 500 poo, which is not the object type that the invoker expected. But there it is anyway. Another FYI; there's never been a problem with any cfc being able to generate the wsdl xml component. That part's always worked. Alan K. Holden -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon mailing list - http://groups.google.com/group/openbd?hl=en !! save a network - please trim replies before posting !!
