Community
Participate
Working Groups
In the TPTP project, for the WSDM tooling, we use the following classes in creating web projects as part of the critical code generation function. Rewriting this function would take a lot of resources and hence we'd like to request that these be made public. org.eclipse.jst.j2ee.internal.web.archive.operations.WebFacetProjectCreationDataModelProvider org.eclipse.wst.common.componentcore.internal.util.IModuleConstants org.eclipse.wst.validation.internal.operations.ValidatorManager All the three above are used in creating web projects - the first two in actually creating the web project, the last one to stop WTP from running validation on the project while we are changing and adding files to the project during code generation).
Balan, can you elaborate on how you use these classes, particularly how the ValidatorManager is related to code generation?
Our code generation consists of creating a web project and copying some files into it that are needed for WSDM. When we create the web project, it automatically starts validating everything in there but our code generation adds files one by one to the project. So today, we turn off validation and turn it back on when we have finished adding all the files we need to, to the web project. The other two classes are used in just creating a web project - unfortunately we could not find any other documentation or way to build web projects and we did not want to rewrite web project building capability.
We don't want to make the entire ValidatorManager class public... but we need to add a public API to turn on and off the validation.
Moving this one to Hari
Created attachment 61424 [details] patch patch that adds fine grained validator enable/disable
Created attachment 61548 [details] updated patch
Created attachment 61609 [details] patch with junit testcase
released. thanks.
This isn't completely finished. The classes used should not have internal package names.
Hi Andrew, We are not allowed to change the package names (even internal ones), since this will break several adopters. Please find the policy here: http://www.eclipse.org/webtools/adopters/main.php#non-api-code-deprecation-policy That said, there is a new validation framework in the works that will be available in the 3.0 time frame, that will provide new and improved api facilitating ease of use. Thanks.
