| Abstract item provider class [message #1022807] |
Fri, 22 March 2013 11:01  |
Eclipse User |
|
|
|
Hi,
sounds philosophical, but still, always wanted to know:
The generated item provider for an abstract class is not abstract. Is there any specific reason for this?
The practical question is: How do I make it abstract? It seems that adding 'NOT' to the @generated annotation will prevent the generator to remove my manually added 'abstract' keyword, but it also seems that this prevents it from doing any modification on the class at all.
Any solution that works better?
Cheers,
Felix
|
|
|
| Re: Abstract item provider class [message #1022891 is a reply to message #1022807] |
Fri, 22 March 2013 14:30  |
| Eclipse User |
|
|
|
Hi, Felix,
If you use lowercase 'not' in '@generated not', then only the class
declaration will be protected from the generator. All of its members
are still subject to re-generation.
But, of course, the question is why is it a problem that the item
provider be abstract? You may want to instantiate the class to use it,
for example, for dynamic EClasses that specialize your generated
abstract EClass (if such a thing is even possible).
HTH,
Christian
On 2013-03-22 15:02:02 +0000, Felix Dorner said:
> Hi,
>
> sounds philosophical, but still, always wanted to know:
>
> The generated item provider for an abstract class is not abstract. Is
> there any specific reason for this?
>
> The practical question is: How do I make it abstract? It seems that
> adding 'NOT' to the @generated annotation will prevent the generator to
> remove my manually added 'abstract' keyword, but it also seems that
> this prevents it from doing any modification on the class at all.
>
> Any solution that works better?
>
> Cheers,
> Felix
|
|
|
Powered by
FUDForum. Page generated in 0.10124 seconds
Home