|
|
|
| Re: Generated EObjectValidator class [message #76390 is a reply to message #76375] |
Thu, 13 November 2008 21:55  |
 Ed Merks
Messages: 33141
Registered: July 2009 |
Senior Member |
|
|
John,
Comments below.
John T.E. Timm wrote:
> Ed,
>
> Thanks for the response. Do you think that automatically generating a
> validator method for large models that exceeds the 64k limit is a
> scalability issue?
I assume it's the huge switch statement that's a problem, right? It's
obviously a problem based on size which I think is the definition of a
scalability issue.
> Should I submit an enhancement request to automatically break the
> validator function into validator, validator0, validator1, ... etc. if
> it exceeds a certain size?
That's the problem, is how to know when to do that. You can't know how
much byte code is generated.
Keep in mind too, that the EMF wishlist grows rapidly, so even asking is
not likely to produce results. Contributing is the most likely approach
to produce what you need...
To me the real problem is that folks have created obscenely large
unstructured models. If this were done in Java, no one would ever
consider defining 1500 things in one package...
>
> Thanks,
>
> John
>
> Ed Merks wrote:
>
>> John,
>
>> No that's not possible.
>
>
>> John T.E. Timm wrote:
>>> I understand from:
>>>
>>> http://dev.eclipse.org/newslists/news.eclipse.tools.emf/msg1 6922.html
>>>
>>> and
>>>
>>> http://www.eclipsezone.com/eclipse/forums/m92233851.html
>>>
>>> That an EObjectValidator class gets generated when there are
>>> constraints associated with a particular model. What I would like to
>>> do is turn off the production of this Validator regardless of the
>>> model. Is it possible to force EMF to suppress the generation of
>>> this Validator?
>>>
>>> Thanks,
>>>
>>> John
>>>
>
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
|
| Re: Generated EObjectValidator class [message #603487 is a reply to message #76375] |
Thu, 13 November 2008 21:55 |
Ed Merks
Messages: 33141
Registered: July 2009 |
Senior Member |
|
|
John,
Comments below.
John T.E. Timm wrote:
> Ed,
>
> Thanks for the response. Do you think that automatically generating a
> validator method for large models that exceeds the 64k limit is a
> scalability issue?
I assume it's the huge switch statement that's a problem, right? It's
obviously a problem based on size which I think is the definition of a
scalability issue.
> Should I submit an enhancement request to automatically break the
> validator function into validator, validator0, validator1, ... etc. if
> it exceeds a certain size?
That's the problem, is how to know when to do that. You can't know how
much byte code is generated.
Keep in mind too, that the EMF wishlist grows rapidly, so even asking is
not likely to produce results. Contributing is the most likely approach
to produce what you need...
To me the real problem is that folks have created obscenely large
unstructured models. If this were done in Java, no one would ever
consider defining 1500 things in one package...
>
> Thanks,
>
> John
>
> Ed Merks wrote:
>
>> John,
>
>> No that's not possible.
>
>
>> John T.E. Timm wrote:
>>> I understand from:
>>>
>>> http://dev.eclipse.org/newslists/news.eclipse.tools.emf/msg1 6922.html
>>>
>>> and
>>>
>>> http://www.eclipsezone.com/eclipse/forums/m92233851.html
>>>
>>> That an EObjectValidator class gets generated when there are
>>> constraints associated with a particular model. What I would like to
>>> do is turn off the production of this Validator regardless of the
>>> model. Is it possible to force EMF to suppress the generation of
>>> this Validator?
>>>
>>> Thanks,
>>>
>>> John
>>>
>
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.04437 seconds
] 
Search
Help
Register
Login
Home
