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.
Steps to reproduce: - create a Sync sample - open it in designer - open process wsdl sources - make WSDL not well-formed - save - switch back to BPEL - there will be no changes, validation does not help - close and reopen BPEL - the diagram will change as the WSDL is invalid - switch back to WSDL, correct it, save - switch to BPEL, there will be no changes - close and reopen BPEL - BPEL will be updated I expected BPEL to be 'fixed' as soon as WSDL gets 'fixed'
I'm surprised that expllicit validation does not help. I knew we did not have the real time update but I also thought epxlicit validation would pick up changes. Maybe Denis and Vladimir need to talk. I seem to recall Vladimir adding some listener support for at least some WSDL originating changes. If waived, we should document required workaround.
Will not be fixed in recent Coke release. There is a question will be this is fixed at all. We don't listen changes in external files from BPEL ( wsdl, schema ). This could be performance problem. We have explicit refactoring action for performing changes in external files for reflecting them in BPEL. So we didn't perform automatic refactoting when some change appear in wsdl or schema file. If user perform changes in those without refactoring then he is responsible himself for validness. This issue has the same reasons why we have explicit refactoring. Revalidation starting on each change in wsdl file could cauase performance problem, so we need to understand how it should be done . Explicit validation works fine for this situation.
For future reference: We may be able in next release to provide some automated validation of BPEl when partner sources have changed and BPEL has not been changed. We could, for instance, listen for changes to partner files and set a "partner dirty" flag to true whenever a partner file changes state. Then when user switches back to BPEL process we can run the validation automatically or indicate via some annotation on partner link that they should run the validation explicitly. Those are possible options but this is new feature that would need to be designed and is out of scope for this release. Also, while investigating this bug we observed that there is a slight problem with the explicit validation of partner files when the validation is initated from BPEL process. It seems that if partner file is malformed, the explicit validation of BPEL process does not trigger the XML validation of partner files. I would expect that it would trigger such validation. It seems this is oversight in our current implementation and I will open a different bug for it.
Please doc in troubleshooting.
Issues #81190 and #89685 are related to this issue. They are all about the same behavior with various changes in models from which BPEL OM depends.
More detail on this. I notice that even running explicit validation is not helping to identify new errors (caused by change to WSDL) or clear errors in the BPEL process (caused by change to WSDL). Explicit validation of the BPEL process does not identify or clear the errors. Closing and re-opening the BPEL file does identify or clear the errors. However, if user explicitly modifies the BPEL process, this will also trigger a "good" validation cycle. So - it is not just validation that needs to run. Something must be triggered in the BPEL OM so that the validaton is correct, when it is run. I assume Denis is already aware of this, but i wanted to document it.
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