Why would you want to do this? Doesn't the framework persist the validation state
across sessions?
----- Original Message -----
Never mind, I found the reason why the validate(..) method is
called:
some xml files need to be checked. They are not part of the
'changedFiles', but they are returned by the
validationHelper.getURIs() method.
So, instead, I'd like to ask: how can I force the validation
framework to trigger a validateAll() at workbench startup ?
Thanks.
Best regards,
/Xavier
On Sep 17, 2012, at 4:49 PM, Xavier Coulon wrote:
> Hi !
> The JAX-RS tooling is now aligned on the CDI tooling and relies
on
> the common-validation plugin to validate the JAX-RS elements.
> So far, so good, but I have this issue that I'd like to solve: at
> workbench start-up, the method
> public IStatus validate(Set<IFile> changedFiles, IProject
project,
> ContextValidationHelper validationHelper,
> IProjectValidationContext context, ValidatorManager manager,
> IReporter reporter) throws ValidationException
> of my validator is called, but with an empty set of
'changedFiles'.
> Wouldn't it make more sense to call the
> public IStatus validateAll(IProject project,
> ContextValidationHelper
> validationHelper,
> IProjectValidationContext validationContext, ValidatorManager
> manager, IReporter reporter)
> throws ValidationException
> method instead ?
> I can workaround that and call validateAll(..) when
> changesFiles.isEmpty() in the validate(..) method call, but I don't
> think it's the best approach.
> WDYT ?
>
Thanks.
>
>
Best regards,
>
>
/Xavier
>
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev