| WebLogic Workshop Control and IDE Extension Validation - Frequently Asked Questions |
|
 |
|
Q: Why should I have my control/extension validated?
There are numerous benefits to having your Control or IDE Extension BEA-Validated. Of prime importance is that your customers will be assured that the Control or Extension has been validated by BEA as meeting the requirements for working properly within WebLogic Workshop. Hence, the customer can proceed with their development project with the assurance that your Control/Extension will work properly. For more information about how the validation program works, click here.
|
Q: How long does validation take?
Validation Testing typically takes 5-10 business days. Once complete, you will be notified of the result via email.
|
Q: How does this validation process relate to the BEA WebLogic Workshop Controls and Extensibility Program?
Validation is available to BEA partners who are members of the Controls and Extensibility Program. This program complements Workshop's rich extensibility model to bring together an industry-leading coalition of ISVs and SIs interested in leveraging the power of BEA's WebLogic Platform 8.1. The program provides a framework to assist BEA partners in building, testing, distributing, and marketing their custom controls and IDE extensions. For more information on the Workshop Controls and Extensibility Program, please click here.
|
Q: Is the validation testing done using a tool-based test suite, and if so, can BEA provide this test suite to us for “pre-validation” testing?
BEA Validation testing is performed manually on every control and extension. The actual process involved is outlined in the Test Plan overview for Controls and Extensions. The only “test bed” utilized is WebLogic Workshop itself. This is a natural result of the type of testing performed. Remember, the BEA-Validated program is not designed to perform in depth QA testing of your control/extension, but rather to ensure that your control/extension will operate properly within the Workshop environment.
|
Q: What happens to my validation status if I rev my product?
Your product will retain its validation status so long as it receives only minor revisions. Major revisions and/or version changes require the new version of the Control/Extension to be validated. The cost of this validation is discounted based upon the type of revision/version change. For pricing information, please look here.
|
Q: How much does validation cost?
The price varies depending upon whether you are seeking validation for a Control or an Extension, and whether a previous version of the product was validated. For pricing information, please look here.
|
Q: Does my validation ever expire?
Your validation status will never expire. However, in the normal course of software development, products are routinely updated. If you update your product with either a version change or major revision then you will need to obtain validation for the new version. However, as long as the previous version (the one that was validated) remains an active, supported product by you, that version will retain its validation status. For pricing information, please look here.
|
Q: Will my validation status carry over to future versions of WebLogic Workshop?
BEA Validation is based upon a specific version of your product and a specific version of Workshop. If your Control is validated under Workshop V8.1, it will continue to work properly under, say, Workshop V9.0 - due to backward compatibility. However, there are sure to be enhancements to Workshop V9.0 that you will want to leverage with your Control. You would then need to rev your control to take advantage of these features and then be re-validated.
|
Q: My product consists of an IDE Extension and a Control. Do I have to have both validated?
It depends on how the Control and Extension work together. Extensions, by their very nature, provide their functionality at design-time. Controls are instantiated at runtime. While some Extensions actually generate code that is used at runtime, they are still considered design-time tools. As such, if your product includes a Control that is used by the Extension at design-time, the validation of the extension will include validation of the control. However, if your product includes a Control that is used separately at runtime, it would need to be validated separately.
|
