I tried using <cfproperty> as much as I can for the latest project I'm working on. However, I just realized that if I specify the type attribute in <cfproperty> to point to a CFC that's actually a <cfinterface>, ?wsdl will throw an exception.
The exception is from Apache AXIS: java.lang.NoClassDefFoundError: [path to the CFC that's actually an interface] Hum... this sounds like a bug to me, I've filed it to Adobe. What do you think? Should a wsdl be able to take in an interface? I actually don't need the WSDL for that component, but I didn't want my cfproperty tags to break WSDL generation either... Henry Ho --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
