Eclipse Community Forums: Eclipse Scout » Annotation @ConfigPropertyValue

Help

Home

Home » Eclipse Projects » Eclipse Scout » Annotation @ConfigPropertyValue

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

Annotation @ConfigPropertyValue [message #987340]

Mon, 26 November 2012 08:44

Jeremie Bresson

Messages: 1252
Registered: October 2011

Senior Member

On every getConfiguredXxxx() method there is @ConfigPropertyValue annotation...

AbstractForm:

  @ConfigProperty(ConfigProperty.TEXT)
  @Order(90)
  @ConfigPropertyValue("ScoutTexts.get(\"FormSaveChangesQuestion\")")
  protected String getConfiguredCancelVerificationText() {
    return ScoutTexts.get("FormSaveChangesQuestion");
  }

This annotation is defined for methods and is retained at runtime.

Does this annotation always contain the source code of the getConfiguredXxx() method?

What for is this annotation?

Could it be used when source are missing (see this forum post), to compute the default value in the properties view (see comment 10 in bug 394374).

Report message to a moderator

Re: Annotation @ConfigPropertyValue [message #987462 is a reply to message #987340]

Mon, 26 November 2012 17:22

Matthias Villiger

Messages: 235
Registered: September 2011

Senior Member

The @ConfigPropertyValue annotation is not used by the Scout SDK. Afaik this annotation is obsolete and will be marked deprecated in the future.
Therefore we will not make use of it for populating the Scout Properties View.

I don't know where this annotation is still in use at the moment.

Report message to a moderator

Re: Annotation @ConfigPropertyValue [message #987566 is a reply to message #987462]

Tue, 27 November 2012 08:01

Jeremie Bresson

Messages: 1252
Registered: October 2011

Senior Member

Matthias Villiger wrote on Mon, 26 November 2012 18:22

The @ConfigPropertyValue annotation is not used by the Scout SDK. Afaik this annotation is obsolete and will be marked deprecated in the future.

I opened Bug 395132 to keep trace of this modification.

Matthias Villiger wrote on Mon, 26 November 2012 18:22

I don't know where this annotation is still in use at the moment.

If someone uses this annotation, he can comment on the bug. Otherwise marking the annotation as deprecated makes sense.

Report message to a moderator

Previous Topic:	Page and form lifecycles
Next Topic:	[SDK] Discussion: Proposed text entries and order

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Sep 24 13:20:54 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter