Wow, Alan, I'm impressed. Two weeks removed from GLGDW and you're already creating web services!

I've been going nuts trying to start using some of the great stuff, but I've been swamped supporting my now obviously antiquated systems! I did actually break down and purchase two to the books everyone said I had to buy, including the Gamma, Helm, Johnson, Vlissides Desgin Patterns book. It is a GREAT book. I can't believe I ever wrote code without it. Actually, I realize I didn't write code. I was hack! I admit it.

Now for my 2 cents which is probably worthless since I've never created a web service - couldn't you just create a method which returned whichever value you needed?


>I just created my first Web service and published it thru IIS. Then, on another machine through the internet, I registered it and tried to use it. Even though the methods of the web service are accessible, none of the properties of the web service are accessible. I did not make the properties PROTECTED or HIDDEN. The class definition looks like this:
>
>DEFINE CLASS WSTest AS Session OLEPUBLIC
> WSName="WSTest"
>
> FUNCTION SayHello AS String
> RETURN "Hello, from "+This.WSName
> ENDFUNC
>
> FUNCTION SayHelloX (tcName AS String) AS String
> RETURN "Hello, "+tcName+", from "+This.WSName
> ENDFUNC
>ENDDEFINE
>
>When accessing this webserver on a different machine, I can run the following (I didn't include the "automatic code" that is entered by the intellisense)
>
>LOCAL oWS AS WSTest
>
>* Code is automatically entered by my intellisense...
>
>? oWS.SayHello() && ==> displays "Hello, from WSTest"
>? oWS.SayHelloX("Alan") &&==> displays "Hello, Alan, from WSTest"
>? oWS.WSName && ==> Results in an error, unknown name.
>
>Do I need to explicitly expose the properties?
>
>Thanks
>Alan