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.
Validation feature does not update the error badges when changes are done in WSDL files. Steps to reproduce: - open the project attached - open the process, the process should have no error badges - go to process WSDL file, find the testProperty property there - delete the type definition for the property, save - this change has to trigger the validation mechanism so the process will be marked with an error badge - switch back to the BPEL process Validation will not mark the process - add an empty activity to the process, wait a bit - the process will be marked. The problem here is that validator does not identify the errors until there is a change in BPEL
Created attachment 32243 [details] refactoring property
Well, I might lobby for this to be an RFE instead of a bug. Of course, we would like the validation system to be able to react autoamtically to changes in other artifacts but I do not consider this to be a strong requirement for a first generation version of validation system. Particularly since we provide users with the manual validation action, I think it is pefectly reasonable to require users to manually invoke validation when they modify other artifacts. Given the number of bugs we have to fix still, I would consider this a lower priority than our other bugs, particularly as there is an easy "workaround" and I'm not even sure it need be called a workaround. I would rather have Praveen work on bugs that do not have workarounds and are indicative of truly broken behavior rather than sub-optimal behavior.
I agree there is a simple workaround, but I still think this is a bug, not RFE. I was expecting the IDE to react somehow after I fix everything according to error message (as IDE does in other validation cases) I will change priority to P3 so we can postpone the fix.
validation bug not a bpel project bug changing subcomponent. When can we have a subcomponent called "validation"?
Vladimir, take a look at this when you finish other bugs. We can waive this bug if we need to. But I thought perhaps you could solve this in siilar way you solved refactoring of filename changes for imports. (i.e BPEL process is notified of change to imported files). After further thought, I am going to apply for waiver. I am a bit concerned that maybe we should just waive this. Otherwise, if we run BPEL validation on every change to imported files we may have very wasteful and innefficient story. At this point, even if we add eager validation it could backfire on us.
to clarify. There are plenty of other events which trigger BPEL validation. Any change to BPEL file. Explicit user invocation of BPEL validation action. Any build or deploy action on BPEL project. Any of those will trigger the validation so I think it is inevitable that user will see the effect of the wsdl or xsd modifications at some point.
This issue should documened and added in limitations section
Added to the RNs as follows: BPEL validation is not started automatically after you modify WSDL files. Click the link to review the wording and location of the issue in the staged Release Notes http://nbstaging.czech/community/releases/55/entpack_relnotes.html#81190
creating new Feature issue 89685
We can close this when we finish implemnenting issue 89685.
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