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: | Validator not check references in XPath expressions | ||
|---|---|---|---|
| Product: | soa | Reporter: | Andrey Yamkovoy <kaktus> |
| Component: | BPEL Validation | Assignee: | Nikita Krjukov <supernikita> |
| Status: | RESOLVED FIXED | ||
| Severity: | blocker | ||
| Priority: | P2 | ||
| Version: | 5.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
Validation do check references in XPath expression for variables. All other checks is enhancement, not a bug. Part presence is easy to check, thats true, but ideologically this is the same as checking corectness of full xpath expression: $inputVar.inputTypeRenamed/paramA One could check presence part inputTypeRenamed and element paramA in this part. There can be also more elemens in xpath and presence of each element in xpath could be checked. This is the same issue actually. This can be option, not requirement. But this is will be new feature. We don't add new features currently. *** Issue 94913 has been marked as a duplicate of this issue. *** *** Issue 93892 has been marked as a duplicate of this issue. *** Now the variable, part and XPath location steps are checked. The content of predicates is also checked. |
Validator should check references in XPath expressions. Steps to reproduce: - Create Synchronous Sample project. - Open BPEL source editor. - Change one of the message parts to incorrect value () in assignment. For example: <from>$inputVar.inputTypeRenamed/paramA</from> - Save all. - Validate BPEL and notice that no errors was found. - Build and deploy project. - Run test. - Test fails with fault: ... <faultcode>SOAP-ENV:Server</faultcode> ...