|
| Re: Using EMFT Validation in Standalone Java Environment [message #421722 is a reply to message #421718] |
Tue, 12 August 2008 13:05   |
Eclipse User |
|
|
|
Originally posted by: cdamus.zeligsoft.com
Hi, Lars,
There is an enhancement request for this in Bugzilla:
https://bugs.eclipse.org/167972
It hasn't seen much activity, I'm afraid. This component was originally
designed with the Eclipse run-time in mind and for a particular
application environment. I suspect that it wouldn't take much work to
add an API for manipulation of the constraint-providers and other
registries, but that the greater effort is in removing dependencies on
Eclipse API such as IStatus. Basically, it would pretty much result in
deprecation of most of the component.
EMF Core, as you probably know, provides a generative validation
solution that works in stand-alone deployments. Is that a possibility
for you? Even using OCL in the generated EValidator is quite
straight-forward, with a bit of custom code...
Cheers,
Christian
Lars Heinemann wrote:
> Hi all,
>
> is it possible to use the EMFT Validation Framework (with Java and OCL
> Constraints) in a Standalone Environment (plain Java - without a running
> Eclipse). I am aware of the fact that all constraints are defined via an
> extension point, but is there any way other than reimplementing the
> whole validation?
>
> Regards,
> Lars
|
|
|
|
| Re: Using EMFT Validation in Standalone Java Environment [message #421731 is a reply to message #421724] |
Tue, 12 August 2008 15:50 |
| Eclipse User |
|
|
|
Originally posted by: cdamus.zeligsoft.com
Hi, Tom,
Good point. Of course, one would rather retro-fit the API to use EMF's
Diagnostic, and I haven't yet taken the time to analyze the extent of
the dependencies ... I'm more worried about behavioural dependencies
than structural ones. I wish I had the time to take another look at the
patch on that bug. :-(
cW
Tom Schindl wrote:
> Christian W. Damus schrieb:
>> Hi, Lars,
>>
>> There is an enhancement request for this in Bugzilla:
>>
>> https://bugs.eclipse.org/167972
>>
>> It hasn't seen much activity, I'm afraid. This component was
>> originally designed with the Eclipse run-time in mind and for a
>> particular application environment. I suspect that it wouldn't take
>> much work to add an API for manipulation of the constraint-providers
>> and other registries, but that the greater effort is in removing
>> dependencies on Eclipse API such as IStatus. Basically, it would
>> pretty much result in deprecation of most of the component.
>
> Well JFace also too depends on things like IStatus you can use these
> classes in none OSGi-Envs without problems. You only have to include the
> osgi.jar no matter if you start up the OSGi env or not.
>
> Tom
>
|
|
|
Powered by
FUDForum. Page generated in 0.39844 seconds
] 
Search
Help
Register
Login
Home
