groovy

Change the MetaClass methods to not be bean properties

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: 1.0-JSR-2
  • Fix Version/s: 3.0
  • Component/s: bytecode
  • Labels:
    None
  • Number of attachments :
    0

Description

Currently, each Groovy class has setMetaClass and getMetaClass methods. This makes it a valid javabean property that requires special handling in automated bean handling features of libraries. Imho it would be a good course of action to replace these methods with:
retrieveMetaClass
provideMetaClass

Issue Links

depends upon

Task - A task that needs to be done. GROOVY-2503 MOP 2.0 design inflluencing issues

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.
is duplicated by

New Feature - A new feature of the product, which has yet to be developed. GROOVY-1163 refactor void GroovyObject.setMetaClass() {} to something like Object GroovyObject.become(MetaClass) {}

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
relates to

New Feature - A new feature of the product, which has yet to be developed. GROOVY-1163 refactor void GroovyObject.setMetaClass() {} to something like Object GroovyObject.become(MetaClass) {}

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Geert Bevin added a comment -

Another option would be to create an unlikely parallel class in bytecode that contains the info, for instance:
MyClass.class and MyClass$0$meta.class

and have no artifact methods in bytecode at all

Show
Geert Bevin added a comment - Another option would be to create an unlikely parallel class in bytecode that contains the info, for instance: MyClass.class and MyClass$0$meta.class and have no artifact methods in bytecode at all
Hide
Permalink
John Wilson added a comment -

If we change setMetaClass then we might as well change getMetaClass at the same time

Show
John Wilson added a comment - If we change setMetaClass then we might as well change getMetaClass at the same time
Hide
Permalink
Paul King added a comment -

If this is really a duplicate, shouldn't we close it?

Show
Paul King added a comment - If this is really a duplicate, shouldn't we close it?

People

  • Assignee:
    Unassigned
    Reporter:
    Geert Bevin
Vote (1)
Watch (3)

Dates

  • Created:
    Updated:
    Resolved: