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.
Error message copied here is correct technically, but does not serve any purpose. No clue what to do. cvc-complex-type.2.4.b: The content of element 'bpws:assign' 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/":targets, "http://schemas.xmlsoap.org/ws/2004/03/business-process/":sources, "http://schemas.xmlsoap.org/ws/2004/03/business-process/":copy, "http://schemas.xmlsoap.org/ws/2004/03/business-process/":extensibleAssign}' is expected.
Related to validation ?
refer to my comments on http://www.netbeans.org/issues/show_bug.cgi?id=96877 One idea is that you can suggest that the file is invalid, because it has this. Typically validation errors have two aspects. 1) What is wrong in the current file? 2) What is correct and/or suggesting How it can be corrected? Again here the most likely thing to suggest is to have a copy.
Marked as INCOMPLETE. Please provide detailed steps to reproduce: 1. open BPEL project 2. create BPEL process 3. ... 4. ... Please provide build number. Please try to reproduce with the latest *Hula* build.
This can be reproduced with 200703050600. 1. open BPEL project 2. create BPEL process 3. Add assign to it 4. validate the business process. 5. It reports two errors. one on Receive/createInstance, second one on Assign. This bug is reported on Assign error. Only part I understand in this error is "Assign" is incomplete, but do not understand rest of the error. Can this be made more helpful to user?
The validation message is pretty clear, is says that "The content of element 'bpws:assign' is not complete. One of '{"http://docs.oasis-open.org/wsbpel/2.0/process/executable":documentation, WC[##other:"http://docs.oasis-open.org/wsbpel/2.0/process/executable"], "http://docs.oasis-open.org/wsbpel/2.0/process/executable":targets, "http://docs.oasis-open.org/wsbpel/2.0/process/executable":sources "http://docs.oasis-open.org/wsbpel/2.0/process/executable":copy, "http://docs.oasis-open.org/wsbpel/2.0/process/executable":extensionAssignOperation}' is expected. So user has to setup one of the missed elements, for example "copy". This message is generated based on schema description and provides detailed information.
The reason I opened this bug is usability. You are right error message is accurate, not easy to reade, needs to scroll horizontally to read it. Our tool does not support support creation of any other child node other than copy, why error canot be explicit? OR Alternatively word it such that missing COPY node indicated first.
Denis, Could you please provide information if usability of output message can be improved? Where and how is the message generated? What module/subsystem generates it?
The problem is that standard validator from jdk is used for validation. We can't modify message from it or improve the validator.
Can't be fixed because we use standard validator from jdk.
What is the purpose of the validation message if is is not helping the user?
Why do you think that the validation message is not helping the user? This message is generated by *standard validator from JDK*, not from bpel. Validator is based on the definition of bpel document, so it provides as much information as possible. I agree that this message is not pretty convenient for user, but *we can not change* the situation (we can not modify the validator from jdk). If you want that messages from the validator would be more clear, please, file bug against *jdk*, not bpel.
The validation message shown above is cominog from bpel schema validation. So as such JDK validation api (which internally using xercers parser for validation) is used which validates bpel file with bpel schema and it reports these generic message based on what is wrong after validating against a schema. Although the argument that the errors message are not very useful is true and I have seen people complain about this but this not an easy problem to solve. Only solution which I can think of is write our own schema based validation on top of netbeans schema model, and provide more meaninful error messages. We need to see if we can register this netbeans schema model based validator as a standard jdk validator provider. This is not an easy task in itself. Hope this helps.
Thanks for the info. I understand the issue now. Can we change this to enhancement? We definitely need this, it should be high priority.
Need to evaluate it more
As it was written we should develop own schema based validator such it was done in xerces. For example, xerces library is about 1.1 Mb, so we need enough resources to implement it. NetBeans schema API module has hard-coded registration of internal xerces validator. We can register any extra validators but can't unregister xerces validator or replace it. Writing of new xml validator is not bpel specific (bpel specific is schema definition only whcich has been already done), so I reassign the issue to xml module. I agree that this is not an easy task.
*** Issue 96877 has been marked as a duplicate of this issue. ***
There are other bugs I filed similar to this one, which are being marked as duplicate of this directly or indirectly. Instead of filing duplicates, if they are referred from here, who ever fixes this one will fix them as well. Otherwise, when this bug is fixed, even though the underlying code might be there, the exact issues which are filed would go un-addressed. I hope you don't close those other bugs marking them duplicate. One thing to note on implementation, re-implementing the jdk validator is not the only solution. You can probably extend it or provide your own listeners (Error handlers, content handlers) to enhance the error messages.