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 Synchronous sample project. - Open bpel source editor: - Add two empty copy sections to Assign activity: <copy></copy> <copy></copy> - Switch to diagram and wait a few seconds. - Notice that validator mark Assign as broken with 2 identical messages: "cvc-complex-type.2.4.b: The content of element 'copy' is not complete. One of '{"http://schemas.xmlsoap.org/ws/2004/03/business-process/":documentation, WC [##other:"http://schemas.xmlsoap.org/ws/2004/03/business- process/"], "http://schemas.xmlsoap.org/ws/2004/03/business-process/":from}' is expected." - It will be more reasonably to provide only one message because they identical.
Maybe this is an RFE, but it is not a bug imo. The problem is that we are invoking the standard XML Validation and we are only reporting back its messages. We cannot edit the list in the way you wish at this time.
Mike, I see from description that the matter of issue is Design Guidance anottation for Digram Assign element. In this case I believe we CAN and we SHOULD filter the same messages when they are shown to user as hint. The situation is more wide actually. Assign is parent for many copies. Copies are not shown on diagram, so diagram collect all messages at parent for copies - assign. But in this case diagram should not show duplicate messages and this is very simple I think. Such situation appears each time when children are not shown on diagram, not only for assign.
If you think you can improve it, please do so. However, I am not sure if this example of multiple errors for copy rules is a good example. If there are 2 copy rules and each one has an error, perhaps there should be two messages. Even if they are the same message. I know from source file perspective these two messages would point to different line in source file.
I think that for the suggested example, it's ok to have 2 messages (actually saying that there are two places that need a fix). Morover, the example is using source, which is not the primary use case. Maybe we could find an example, where this needs an enhancement more badly. And I suppose that both the copy rules will be badged in the Navigator. Or - in general - I wonder what is the plan for badging of Navigator nodes and their parents, if they are not represented on the diagram directly. Same applies to (multiple invalid) variables and process or scope. - in this example, multiple errors on diagram and multiple badges in Navigator would be also fine, I think.
I am closing for now, it seems like Jirka is arguing that we do not need to do anything. This can be reopened if there is clear use case where improvement would help.
ok ... i'll reopen this issue or cteate new if find clear use case.
ok