Community
Participate
Working Groups
EMF Validation 1.0.1 does not run standalone (no Eclipse). EMF Validation standalone would allow a much greater deployment flexibility. Our company required using EMF and validation on both standalone and in an Eclipse environment. We have extended EMF Validation 1.0.1 to support standalone deployment. Please review and consider incorporating these changes into future versions of the EMF Validation component. A client that wants to initialize the validation framework in standalone mode, would need to specify a set of URLs pointing to XML documents describing parsers, constraint providers, categories and constraint bindings. For example: // Configure validation framework in standalone mode URL[] urls = new URL[3]; urls[0] = new URL("jar:file:///c:/mydir/lib/org.eclipse.emf.validation_1.0.1.v200609250852.jar!/plugin.xml"); urls[1] = new URL("jar:file:///c:/mydir/lib/org.eclipse.emf.validation.ocl_1.0.1.v200609250852.jar!/plugin.xml"); urls[2] = new URL("file:///c:/mydir/plugin.xml"); EMFModelValidationPlugin.INSTANCE.configureStandalone(urls); // Invoke validation framework as usual IBatchValidator validator = (IBatchValidator) ModelValidationService.getInstance().newValidator(EvaluationMode.BATCH); validator.setIncludeLiveConstraints(true); validator.validate(object, monitor);
Created attachment 55617 [details] Standalone support patch against EMF Validation 1.0.1
Created attachment 55618 [details] EMF Validation with standalone support (Eclipse project)
Deferring examination and consideration of these enhancements to the 1.2 release.
Created attachment 71491 [details] Standalone support patch against EMF Validation 1.1RC2
Created attachment 110276 [details] Standalone support patch against EMF Validation 1.2
Created attachment 110386 [details] Standalone support patch against EMF Validation 1.2 Minimalistic set of changes to run standalone
Chris, Please take a minute to review the proposed patch to run in standalone mode. I've minimized the number of changes required and there are no additional steps to use it (plugin descriptors are picked up from the classpath): // Invoke validation framework as usual IBatchValidator validator = (IBatchValidator) ModelValidationService.getInstance().newValidator(EvaluationMode.BATCH); validator.setIncludeLiveConstraints(true); validator.validate(object, monitor); Best Regards, Horacio
Hi, Horacio, Thanks (again) for the contribution. I shall make a concerted effort (at least more so than in the last release) to review this for 1.3.
I've had a look through the patches. I'm not keen on the idea of reading the constraint metadata from the same plugin.xml files as are used in the Eclipse environment. And, especially, constructing Equinox registries seems fragile. I will rather take the approach of the EMF core, defining registries corresponding to the extension points, that can be populated statically in Eclipse or dynamically. This should work well with the existing dynamic-constraint-provider capability (which is recommended over the plugin.xml provider) as well as bug 240352 which will supersede the plugin.xml as a constraint model.
This can't be completed for M3. Aiming for M4.
Postponing to M5, when we should have the model of constraint meta-data (bug 240352) in hand to provide a unified constraint-provider mechanism.
Cleaning up after the milestones were all deranged.
(In reply to comment #12) > Cleaning up after the milestones were all deranged. Hi, What about a release of the standalone version of EMF Validation Framework??? It is a very useful enhancement !!! Lookink forward to try it !
Rudy, the fix is in HEAD. There will be a milestone release at sometime in the near future. Meanwhile you can try out the latest and greatest from Hudson.
Thanks Boris, (In reply to comment #14) > future. Meanwhile you can try out the latest and greatest from Hudson. Can you be more precise please? I dont understant how to get the good jar from Hudson.
This one: https://build.eclipse.org/hudson/job/cbi-emf-validation-1.4/68/artifact/build/N200911252132/emf-validation-Update-N200911252132.zip should do just fine.
Many many thanks for replying so fast ! You just saved my afternoon !
Hi, I tried this code and i can get ModelValidationService instance :). But getConstraintProviders() return an empty list. I cannot register constraints defined in the plugin.xml file from MyJarWithConstraints.jar, that is in the classpath. I tried calling modelValidationService.loadXmlConstraintDeclarations(); but same issue. I don't know what is wrong... Is there another way to add constraintsProvider in ModelValidationService? Thanks for help.
Hi Rudy, yes.. for the standalone case there is the new so called modeled constraints provider. Have a look at the ModeledConstraintsLoader class. As of now there is not much documentation. You have to provide an URI to a resource with instances of ConstraintsBundle from the new validation meta-model (it is located in org.eclipse.emf.validation plugin). Sorry about the missing documentation, but this feature is new and you are an early adoptert :). Hope that helps and cheers, Boris
(In reply to comment #19) > Hi Rudy, > > yes.. for the standalone case there is the new so called modeled constraints > provider. Have a look at the ModeledConstraintsLoader class. As of now there is > not much documentation. You have to provide an URI to a resource with instances > of ConstraintsBundle from the new validation meta-model (it is located in > org.eclipse.emf.validation plugin). > > Sorry about the missing documentation, but this feature is new and you are an > early adoptert :). > > Hope that helps and cheers, > Boris Thanks Boris for your support :) Yes I knew that i've to wait for a release and i hope that it will be deliver soon. I'll try to make without :). Cheers Rudy
I believe this defect can be closed now. The modeled constraints (EMF Validation 1.4.0) approach provide stand alone support. Thanks for all the good work.
Closing based on the reporter's last comment (from 2010!).
