>>Do I need to explicitly expose the properties?
>
>Web Services are a stateless, disconnected object. That means that a property would be absolutely useless, since the object doesn't retain state, and thats why only methods can be called.
Mike,
I guess I am intending to use my web service in an un-orthodox manner. The class definition I gave you is really just an example. The real web service I tried to publish and then consume was based on a wrapper around my business object that I use in native vfp. For example, I have a Customer BO that has several methods but also properties. Like, a Query method that accepts an expression valid in a WHERE clause. The BO then queries the customer table. I use methods and properties, then, to access the data (the customer BO has properties that correspond to columns in my table, like BO.Customer_ID, etc.). I thought this would be a slick way to implement a distributed fat-client application. I realize that this model would be stateful - but I'm disappointed that this wont work.
Alan
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only