I see... the reason why I use cfproperty tags to specify a type that's actually an interface is because I was trying to write a validation framework. I thought cfproperty is a great place to specify the metadata of the class, so the validation framework can use the type attribute to check if the property is really of that type.
Regards, Henry Ho On Feb 21, 4:38 pm, Sean Corfield <[email protected]> wrote: > On Fri, Feb 13, 2009 at 11:32 AM, Henry <[email protected]> wrote: > > 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. > > No one answered you so I thought I'd bounce some ideas around... > > An interface is used to specify behavior - methods - that concrete > classes will implement. WSDL is all about concrete types - properties > of objects, not behaviors. A Java stub for a SOAP web service may well > have getFoo() / getBar() methods but really that's just a convention > to encapsulate foo / bar properties. > > So, it *may* be a bug but my gut reaction is that interfaces make no > sense for WSDL data types - they're supposed to be concrete entities. > -- > Sean A Corfield -- (904) 302-SEAN > An Architect's View --http://corfield.org/ > > "If you're not annoying somebody, you're not really alive." > -- Margaret Atwood --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
