Eclipse Community Forums: Test and Performance Tools Platform (TPTP) » Btm-Muse: what's the rationale for generating setter-methods for read-only properties?

Home » Archived » Test and Performance Tools Platform (TPTP) » Btm-Muse: what's the rationale for generating setter-methods for read-only properties?

Show: Today's Messages :: Show Polls :: Message Navigator

Btm-Muse: what's the rationale for generating setter-methods for read-only properties? [message #92626]

Fri, 16 February 2007 16:18

Michael Moser

Messages: 914
Registered: July 2009

Senior Member

Using the Muse-tools: When I declare a property read-only the generated
server code (interface "IMyCapability" and class "MyCapability")
nevertheless contains a set<foo>-Method for such a property.

What's the rationale behind this? I fully understand, that this method
is only declared "internally" (i.e. is not exposed via the WS/WSDM
interface) but what's the rationale to generate it at all?
Just in case it might be needed for internal use? If so, then IMHO we
should leave to the programmer to add such a method if needed. Doing so
this will hopefully also trigger some considerations re. the necessary
visibility of such a method. Right now it's there and public and it's
just too easy to abuse it (possibly even inadvertedly, i.e. without
realizing that this is supposed to be a read-only property).

Cheers,
Michael

Report message to a moderator

Re: Btm-Muse: what's the rationale for generating setter-methods for read-only properties? [message #96021 is a reply to message #92626]

Mon, 16 April 2007 15:49

Balan Subramanian

Messages: 2
Registered: July 2009

Junior Member

This is a multipart message in MIME format.
--=_alternative 0056EC29852572BF_=
Content-Type: text/plain; charset="US-ASCII"

You are correct, the set method should not be generated or atleast should
be an option. This was a point in time bug we had because the tooling was
using Muse 2.1. It was supposed to be fixed in Muse 2.2 but I will double
check. If so, the tooling won't generate the setter methods. I will post
back wih what I find.
--=_alternative 0056EC29852572BF_=
Content-Type: text/html; charset="US-ASCII"

<br><font size=2 face="sans-serif">You are correct, the set method should
not be generated or atleast should be an option. This was a point in time
bug we had because the tooling was using Muse 2.1. It was supposed to be
fixed in Muse 2.2 but I will double check. If so, the tooling won't generate
the setter methods. I will post back wih what I find.</font>
--=_alternative 0056EC29852572BF_=--

Report message to a moderator

Previous Topic:	What is the difference between FullTraceObject and HeapObject?
Next Topic:	how to transfer generated probeData best

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 06:57:41 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter