This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Better Validation for changes in upstream artifacts | ||
---|---|---|---|
Product: | soa | Reporter: | Michael Frisino <frisino> |
Component: | BPEL Validation | Assignee: | Denis Anisimov <ads> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | ||
Priority: | P2 | ||
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 81190, 86274, 89926 |
Description
Michael Frisino
2006-11-20 16:01:39 UTC
After discussion with Denis we decided on following - most changes to upstream artifacts that will affect BPEL will be picked up by the automatic BPEL validation (aka fast validation). So it is not really necessary to design a solution that will promote the the slow validation. (if we discover that we do need to promote the slow validation, then I suggest going with my idea of badging the Validate XML button, but at this point we think it is a low priority). - So, assuming we need to promote fast validation, then the issue is whether to perform the fast validation eagerly (i.e. in response to changes in upstream artifacts) or lazily (i.e. set dirty flag in response to changes in upstream artifacts, and then perform the fast validation only the next time the BPEL editor gets focus ). From a performance perspective the lazy approach is the safest. The only concern is that it will introduce a slight performance lag in the BPEL editor when the BPEL editor receives focus. However, this wll be no worse than the lag which occurs whenever the fast validation runs today. So I think it will be acceptable. - Current plan is to introduce the laze validation as it is easy and low performance risk. If QE determines that this is not responsive enought then we can evaluate more sophisticated solution based on eager validation and "interruptibility". Note to docs and qe - the current plan "lazy automatic (fast) validation" will have no UI impact. Therefore, it should not require any special documentation. It is really just another instance of the same automatic validation that is already in the product. In this case, it is just happening when editor window gets focus. Previously, it was only happening when user made change to BPEL process. BTW Denis - we might want to run the automatic validation on first opening of the BPEL editor, since changes to upstream artifacts may have occurred before editor was opened (and perhaps before listeners were registered). What do you think? Validation will be triggered now if external artifact was changed before we switch to Design or editor mode for bpel file. Please note that this will not happen if we switch to Navigator panel. May be this is additional feature that should be implemented also. But this is another issue. Verified the issue is fixed in Gavotte daily build 070125_12 |