Home » Modeling » TMF (Xtext) » Fast, normal and Expensive Java validator checks
Fast, normal and Expensive Java validator checks [message #60163] |
Fri, 17 July 2009 13:24  |
Eclipse User |
|
|
|
Hi,
When the Check validator is used, there is the option to use either
Fast, Normal or Expensive checkss by putting the Checks constraints
into different Chgecks files.
When using the Java validator I cannot find this option. Can you do teh
same with the Java validators?
Jos
|
|
|
Re: Fast, normal and Expensive Java validator checks [message #60185 is a reply to message #60163] |
Fri, 17 July 2009 14:03   |
Eclipse User |
|
|
|
Hi Jos,
Java based checks are annotated with @Check, which has an optional
parameter to indicate the CheckMode (Fast, Normal, Expensive).
You can write something like
@Check(CheckMode.FAST)
void checkSomething(..
Hope that helps,
Sebastian
--
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com
Am 17.07.2009 19:24 Uhr, schrieb Jos Warmer:
> Hi,
>
> When the Check validator is used, there is the option to use either
> Fast, Normal or Expensive checkss by putting the Checks constraints into
> different Chgecks files.
>
> When using the Java validator I cannot find this option. Can you do teh
> same with the Java validators?
>
> Jos
>
>
|
|
| |
Re: Fast, normal and Expensive Java validator checks [message #480382 is a reply to message #60185] |
Sun, 16 August 2009 11:09   |
Eclipse User |
|
|
|
Originally posted by: oba.informatik.uni-kiel.de
Hello,
I came across this mail, while looking for the same (seeting the check
mode in the Java Validator) and done, as told below.
But I got the error, that it "cannot convert CheckMode to CheckType".
Looking in the Check annotation, it really has an "CheckType" attribute,
not a CheckMode.
But there also exists a CheckMode in the validation package. Are there
any important differences between them? Or are CheckModes just deprecated?
Thanks for your answer(s)
myName
Sebastian Zarnekow wrote:
> Hi Jos,
>
> Java based checks are annotated with @Check, which has an optional
> parameter to indicate the CheckMode (Fast, Normal, Expensive).
> You can write something like
> @Check(CheckMode.FAST)
> void checkSomething(..
>
> Hope that helps,
> Sebastian
>
|
|
|
Re: Fast, normal and Expensive Java validator checks [message #480383 is a reply to message #480382] |
Sun, 16 August 2009 11:21   |
Eclipse User |
|
|
|
Hi myName,
seems as if I messed up CheckMode and CheckType in this post.
The actual enum is called CheckType. The CheckMode is used at a
different point in the lifecycle of an editor and has nothing to do with
the static configuration of your check methods.
Hope that helps,
Sebastian
--
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com
Am 16.08.09 17:09, schrieb myName:
> Hello,
>
> I came across this mail, while looking for the same (seeting the check
> mode in the Java Validator) and done, as told below.
>
> But I got the error, that it "cannot convert CheckMode to CheckType".
> Looking in the Check annotation, it really has an "CheckType" attribute,
> not a CheckMode.
>
> But there also exists a CheckMode in the validation package. Are there
> any important differences between them? Or are CheckModes just deprecated?
>
> Thanks for your answer(s)
>
> myName
>
> Sebastian Zarnekow wrote:
>> Hi Jos,
>>
>> Java based checks are annotated with @Check, which has an optional
>> parameter to indicate the CheckMode (Fast, Normal, Expensive).
>> You can write something like
>> @Check(CheckMode.FAST)
>> void checkSomething(..
>>
>> Hope that helps,
>> Sebastian
>>
|
|
|
Re: Fast, normal and Expensive Java validator checks [message #481302 is a reply to message #480383] |
Thu, 20 August 2009 08:10  |
Eclipse User |
|
|
|
Originally posted by: oba.informatik.uni-kiel.de
Thanks, Sebastian. That helped.
Sebastian Zarnekow wrote:
> Hi myName,
>
> seems as if I messed up CheckMode and CheckType in this post.
> The actual enum is called CheckType. The CheckMode is used at a
> different point in the lifecycle of an editor and has nothing to do with
> the static configuration of your check methods.
>
> Hope that helps,
> Sebastian
|
|
|
Goto Forum:
Current Time: Sat Jun 07 12:09:37 EDT 2025
Powered by FUDForum. Page generated in 0.06069 seconds
|